Publication Date:  16 February 1996
System Version:  GCCS 2.1/Update 4
Web Page Created:  15 March 1996

The Marine records are now stored in your user account's Scripts/User_Storage directory in the 900XT_marines file.  It is important to remember that the Create TPFDD File option does not copy scheduling and movement information from the OPLAN data.  Use the Offload Plan option to save all OPLAN information, including scheduling and movement data.

Offload Plan.  To archive or offload an OPLAN to either a tape or a disk file, you use the Offload Plan option under the Plan Management option.  The Offload Plan option does not delete the OPLAN from the database.
You will use the Offload Plan option to archive a training OPLAN to a file in your user account.  Later in the course (lesson 5), you will use the Reload Option to rename it and return it to the database for additional processing.

The plans you can offload from the database automatically post to the Available Plans column.

To offload plans, you mark the applicable plan(s) in the Available Plans list and select the Add to List toggle.

The plan(s) listed in the Offload Plans column are the ones that will be saved to the designated directory in your user account.

If you made a mistake, you can remove a plan from the Offload Plans column by marking it and selecting the Remove From List toggle.

To execute the process, select the Transmit button.

The lesson's focus thus far has been on how to export TPFDDs and OPLANs from the database.  Recall that TPFDDs only have movement requirements information and OPLANs can include scheduling and movement data.  The lesson focus now changes to importing TPFDDs and OPLANs back into the database.

Importing OPLANs/TPFDDs.  OPLANs/TPFDDs can be imported into the JOPES database from tape or disk media via the System Services' reload, load, merge, and external transaction processor (XTP) functions.  The first two options, Load Plan from TPFDD and Reload Plan, are available from the Plan Management tear-off menu.
Load Plan from TPFDD.  The Load Plan from TPFDD option allows you to reload a TPFDD text file.
This type of file was created or can be created by the System Services Create TPFDD File option, or applications such as DART, JFAST, or MAGTF II.

This option will initialize an OPLAN shell in the database to receive the records.

You will load the Marine TPFDD file you created into a 909XS OPLAN shell.

Requirement.  Use the Load Plan from TPFDD option to load the Marine records extracted from 900XT into a new OPLAN (909XS).  Initialize 909XS as an exercise, normal, local, and unclassified OPLAN.

The window requires very little information to start the process.  You only need to enter the target OPLAN number and the source tape or file name.

The process takes place in the background so all you need to do is monitor the window until it is done.

LOAD PLAN FROM TPFDD
7	<POINT AND CLICK (left)> on the Exercise toggle.	Toggle is depressed.
8	<POINT AND CLICK (left)> on Transmit.	Perform Reload of Indicated OPLAN? pop-up window displays.
9	<POINT AND CLICK (left)> on Yes.	The LOAD TPFDD window (Fig. 4-19) redisplays in the background. XTP MESSAGES window displays in the foreground.
10	When processing is complete, <POINT AND DOUBLE CLICK (left)> on the Window Menu button in top left corner of the XTP MESSAGES window to close it.	XTP MESSAGES window closes and the LOAD TPFDD window (Fig. 4-19) redisplays.
11	From the LOAD PLAN FROM TPFDD window, press <F10> or <POINT AND CLICK (left)> on the F10-Back button to return to the previous window.	The previous window displays.

The Load Plan from TPFDD option is functionally the opposite of the Create TPFDD option.  The Reload Plan option, described next, is the opposite of the Offload Plan option.
Reload Plan.  The Reload Plan option reloads OPLANs into the database that were offloaded using the System Services Offload Plan option.  The options allow you to reload data from several types of media.  The Reload Plan option will automatically require you to initiate an OPLAN as part of the reload process.

Note:  The next lesson will demonstrate this option.

You now know how to Offload an OPLAN to disk, but what if you want to store your plan in- definitely?  Next, you will learn how to use a tape to offload and reload your plan(s).

OBJECTIVE.  Given JOPES operating in a GCCS environment, save an OPLAN to a tape and to a file.

Importing/Exporting a Plan to/from Tape.  If your hard drive(s) crash, how are you going to recover your OPLANs?  Having your OPLAN(s) on a tape will definitely make recovery much easier!
Offload Plan to Tape.  To archive or offload an OPLAN to a tape, you use the Offload Plan option under the Plan Management option.  Once again, the Offload Plan option does not delete the OPLAN from the database.
Before continuing, you should ensure that a tape is loaded into the tape drive.  This tape drive is most likely connected to your database server.  Your system administrator will be able to tell you the device name.

Primarily, two types of tapes (or cassettes) are used:  8mm or 4mm. 

8mm tapes are roughly the size of the standard cassettes you may use in your stereo at home.  8mm tapes can hold 5 Giga Bytes (GB) of information - that's 5 billion characters.

4mm tapes are about half the size of an 8mm tape and can hold 2 GB of data.

Note:  Like diskettes, tapes also have a read only or read/write tab.  It is usually well marked on the tape.

The plans you can offload from the database automatically post to the Available Plans column.

To offload plans, you mark the applicable plan(s) in the Available Plans list and select the Add to List toggle.

The plan(s) listed in the Offload Plans column are the ones that will be saved to the designated directory in your user account.

If you made a mistake, you can remove a plan from the Offload Plans column by marking it and selecting the Remove From List toggle.

To execute the process, select the Transmit button.

Reload an OPLAN From Tape.  Reloading an OPLAN from tape is almost exactly like the reload you performed earlier.  The differences are that you select tape vice directory, that the pathname is different, and that you should have the correct tape loaded in the appropriate tape drive.

You now know about moving OPLANs and TPFDDs into and out of the JOPES database.  To make sure you are comfortable with this process, please complete the practical exercise below.

Congratulations on successfully completing the practical exercise.  The lesson continues with file transfer tools available to you to manage your files.

OBJECTIVE.  Given a GCCS environment, manage your personal JOPES OPLAN and TPFDD files.

File Transfer Tools.  The System Services windows provide the capability to transfer TPFDDs and OPLANs to/from the JOPES database.  However, you also need to transfer records and information between host computers and application programs that cannot directly access the JOPES database.  You will review the generic process so you can appreciate where the files come from and how to get them where they need to go.
GCCS File Transfers.  The lesson demonstrates the transfer process from a user's perspective to give you a better idea of how the parts work together.  (Refer to Figure 4-15).

To use the graphic, start with the applicable program and you can determine a file transfer path to or from the application program.  FTPtool, IMS, and RFM can transfer files from sources to destinations/applications.  It also shows that floppy disks can be used to copy some reference files into JFAST.

IMS Capability.  If you are concerned with format requirements for specific application programs, IMS translates (rearranges) and transfers data between GCCS applications and between the server and external systems.
TPFDD Data Transfer/Conversion.  IMS is the tool you use to transfer JOPES TPFDD data to applications like DART and JFAST.  Why?  For those applications that do not directly access the JOPES database, IMS translates the Oracle based data to an ASCII based file format.  IMS will then arrange the data as required by the application receiving the TPFDD.

IMS Admin Tool.  The IMS Admin Tool, which is a separate icon in the Session Manager Launch Window, controls the file sources and destinations that appear on the IMS window.

Since IMS only transfers TPFDD related data, you also need another tool to transfer non-TPFDD data to applications like JFAST or DART.

FTPtool Capability.  FTPtool transfers data between similar or dissimilar operating systems, such as WIS workstations, SUN workstation/servers, DOS PCs, and HPs with a minimum of data conversion.  Think of it as a simple copy utility; it just moves the information and makes it machine readable by the receiving computer.
File Data Transfer.  Copying files to and from different computer hosts is a common task in the GCCS environment.  It may become a frequent task if you want to take advantage of the multitude of Service unique and commercial programs available for off-line planning, graphing, and reporting.

System Format Conversion.  FTPtool can accommodate most system conversion requirements, but there are exceptions caused by the multitude of data formats, character standards, and other file parameters that vary between computers and operating systems.

FTPtool only makes system conversions; it does not change files to specific formats required by some of the applications.  For example, TPFDD format conversions are handled by the Information Management System.

OBJECTIVE.  Given a GCCS environment, manipulate TPFDD files using IMS to provide TPFDD file access for other JOPES applications.

IMS Navigation.  In general, IMS navigation requires you to select a TPFDD source, identify a TPFDD from that source, and select a transfer destination for the TPFDD information.  You begin the IMS transfer process by selecting the IMS icon.

Requirement.  Export 909XS from the GCCS JOPES DB (database), import it to the External destination file, then delete the 909XS file from IMS.  Later in the lesson you will transfer a 909XS TPFDD from the External destination UNIX directory (/h/data/local/tpfdd) to your User_Storage account (/h/USERS/{USERID}/Scripts/User_Storage).

Note:  The System Services' Create TPFDD option can also export a TPFDD from the database; however, only the USERID that exports the file can read/transfer the file.  In order for other users to access a file exported from the database, it must be exported via the IMS process to the External destination file.

TPFDD Source Panel.  The first display you see in the IMS window is the TPFDD Source panel that includes the GCCS JOPES DB as well as other TPFDD sources in the GCCS environment.  The IMS window generates different displays depending on the TPFDD source you select from the list in the TPFDD Source panel.
This panel shows the applications from which you can export information.  The IMS Admin Tool controls what sources display in the panel.  You probably recognize all of them except for the ones titled External and Transactions.

After something has been imported to IMS, it can be a source when sending TPFDDs to other applications.

The External file is a source for data transferred to the server using manual programs like FTPtool or UNIX "copy" or "move" commands.

Note:  The External source file contains files stored in an ASCII text file format for IMS access.  The server's UNIX directory for the External source/destination file (when transferring information to or from the server) is "/h/data/local/tpfdd".

The Transactions source file stores output from applications, like DART, that can generate TPFDD transaction files.

System Status Notification Panel.  The System Status Notification panel tells you what to do and keeps you apprised of what the system is doing behind the scenes.

TPFDD Name Panel.  The TPFDD Name panel allows you to rename the TPFDD being exported from the JOPES database.

TPFDD Destination Panel.  The TPFDD Destination panel displays all of the available TPFDD destinations to which you have import permissions.
IMS is just one of several import destinations.  Thus, you can send a TPFDD from one source directly to a destination without selecting IMS as the source or destination.  However, IMS always stores a copy of it for future reference and sourcing.

IMS converts the information to the correct format for each destination application.

The destination, titled External, stores data to the /h/data/local/tpfdd disk directory for manual transfers to other computers that cannot be completed using the IMS process.  Just like before, the information is stored in an ASCII text file format.

The selected destination is outlined or highlighted.

Transfer Button.  Pressing the Transfer button under the Destination panel starts the process to export a TPFDD from the designated source and imports it to a designated destination.

The 909XS TPFDD is now available in the server's /h/data/local/tpfdd directory and it is also available in the IMS directory (/h/IMS_RFM/imsdata).  To review the plan you just transferred through IMS to the External destination file, you select IMS in the TPFDD Source panel.

Note:  The IMS file format includes all the Comments, IMS Information, and Operating System (O.S.) File Information that is not available in the ASCII text file format.

All files you transfer to or through IMS are stored in the IMS file system and must be managed to preclude filling the computer with old files and to preclude unauthorized (no need to know) access to TPFDD files.

Once a TPFDD is stored in IMS, you can rename it, delete it, or import copies of it to other applications.

When you select IMS as a TPFDD source, IMS generates additional information panels to help you manage the export/import process.

TPFDDS Panel.  The TPFDDS panel shows you all the TPFDDs on file in IMS.

Note:  IMS users with IMS export permissions have access to all the TPFDDs.  TPFDDs in IMS are not controlled by the OPLAN number series access permissions designated in the System Services application.

Delete Button.  To remove a TPFDD from IMS, you highlight the name in the TPFDDS panel and select the Delete button.  This action deletes the TPFDD from the IMS database.  It does not delete the TPFDD from the JOPES database.

Rename Button.  Renaming a TPFDD with the Rename button does not change the real OPLAN number of the TPFDD or the UNIX file name on the server.  If you import it to another application, the new name gets transferred along with the old OPLAN number.  The TPFDD Name is only an IMS naming tool.

Note:  WARNING.  Renaming a TPFDD does not change the UNIX filename.  If you transfer a TPFDD to IMS that has the same name as the original name of a renamed TPFDD, the newly transferred TPFDD will overwrite the renamed one.  Both TPFDD names will show in IMS, but they both point to the same file (filename); the file for the renamed TPFDD is overwritten.

IMS TPFDD Version Number.  Duplicate names in the TPFDDS panel are identified with a unique name and version number.  Version numbers are assigned by IMS according to the order stored in IMS.

The naming convention helps you differentiate one TPFDD from another.

The rest of the information panels in the window help you identify the correct TPFDD for processing.

To view the specific information regarding your TPFDD, you must select it on the TPFDDs panel.

IMS TPFDD Information.  The information shown in the IMS TPFDD Information section tells you where the TPFDD came from, when it was received, when it was transferred to an application (downloaded), when it was imported to the JOPES database (uploaded), and record information.

O. S. File Information.  The O.S. File Information section contains the UNIX file information.  The Owner is the USERID of the person who created the UNIX file.

TPFDD Comments Panel.  The TPFDD Comments panel is one of the most important areas of the window because it can provide a wealth of management information about the TPFDD highlighted in the TPFDDS panel.

IMS automatically enters a minimum amount of information concerning the PID and its origin.  The planner who transfers a TPFDD into IMS should activate the panel and type comments.  Up to 4000+ characters can be used (about 800 words).

Save Comments Button.  You have to save your comments with the Save Comments button.

Clear Comments Button.  To start with an empty panel, you can select the Clear Comments button.

IMS Status & Error Messages.  During the IMS process you will see numerous status messages and, hopefully, no error messages.  The messages are very descriptive and should tell you what to do to finish the process.

Messages can occur at any time during the process and may require you to press <ENTER> to continue.

To remedy some situations, you may have to restart IMS.

You have completed the IMS section of this lesson so please quit IMS.

You know how to use IMS to move TPFDD files.  The next tool you will use is the FTPtool.  FTPtool allows you to move ASCII files from one directory to another across the GCCS network.

OBJECTIVE.  Given a JOPES environment, use the FTPtool software to copy a file from one host to another host computer.

FTPtool Characteristics.  You can use FTPtool to manage file activity in the GCCS environment.
UNIX File Permissions.  The FTPtool allows you to view, copy, and delete files as long as the parent directories and the files have the appropriate UNIX file permissions assigned.
UNIX Read permissions allow you to view and copy files.

UNIX Write permissions allow you to write and delete files.

View/Delete Files.  If you can see a file name in your user account via the FTPtool window, you will probably be able to view and/or delete the contents of the file.  If you are reviewing files outside your user account, you can only view the ones to which you have read permissions.

Copy Files.  You can also use FTPtool to copy file(s) from one directory to another directory.

The directories can exist on the same host or different hosts.

The host you originally logged into is called the local host and the host you connect to is called the remote host.

You must have a user account at both the local and remote host.

This function allows you to copy files from other user accounts into your account.

You will use FTPtool to copy a TPFDD from the IMS External destination directory (/h/data/local/tpfdd) into your user account.

Requirement.  Using the FTPtool, login to a remote host from your local host, copy a TPFDD to your user account, and view it.

FTPtool Main Menu.  The opening FTPtool window starts the navigation path for connecting to a host and transferring a file.  After you connect to a host, this window displays the directory and file structure for your review at the remote host.

Login.  The Host Information window is the sign-in point for the remote host.  This is actually a split window.  The left side is for login activity and the right half, not visible yet, allows you to enter additional login parameters.

Login Parameters.  You can use this half of the Host Information window to specify the directory names accessed by FTPtool when you login.
Remote CD To.  The "Remote CD to:" line specifies the directory level to initially display at the remote host; the CD stands for "change directory."  The dot () on the line represents a UNIX code for the "current directory" specified for the login user account.  Unless you know the exact directory name of the file you are looking for, the current directory is a good place to start.

Note:  Directory names and file names are case sensitive in UNIX.

Local CD To.  The "Local CD to:" line specifies the directory FTPtool will initially access on your local computer.
Again the dot () represents your current directory.  You can enter directory path information here or change it later during the transfer process.

Note:  The current directory for a normal GCCS user account, represented in UNIX commands by a dot (), is /h/USERS/{USERID}/Scripts where {USERID} is a user defined variable.

This lesson uses the /h/USERS/{USERID}/Scripts/User_Storage directory as a common storage area for all FTPtool and System Services processing.  Thus, the User_Storage directory is the common directory for user account activity because the Session Manager applications, under the Tools option, also import and export files to the User_Storage directory by default.

You stored an OPLAN (9096M) in the User_Storage directory earlier when you offloaded it using System Services, so you will setup FTPtool to automatically change to that directory on your local host.

FTPtool
8	<POINT AND CLICK (left)> on the dot () in the Local CD to:  line.
9	Type "/User_Storage".	Directory string posts to entry line.
10	<POINT AND CLICK (left)> on the dot () in the Remote CD to:  line.
11	Type "/User_Storage".	Directory string posts to entry line.
12	<POINT AND CLICK (left)> on the Connect to Host button.	Ftptool Version 4.3 - {Remote Host} window (Fig. 4-27) displays.

Remote Directory List.  The FTPtool window now shows your working directory on the Remote Directory line and the directory/file structure in the panel below.  Files are shown with a letter icon and directories are folders with bolded titles.

Local Directory List.  You can also display your local directory list at the same time.  Reading the window titles will help you identify a remote directory list from a local directory list.

Directory List Navigation.  From the remote and local directory lists, you can display the contents of other directories.
To move to a lower directory level, you <POINT AND DOUBLE CLICK (left)> on a directory in the list to add the directory to the Remote Directory line.

To move to a higher directory level, you <POINT AND DOUBLE CLICK (left)> on the bold up arrow to remove the directory from the Remote Directory line.

You will now move to the /h/data/local/tpfdd directory on the remote host.  Then you can access the plan put there by another student and copy that plan from the remote host to the local host directory.  The local host directory is the directory you specified earlier (Local CD to:) when you connected to the remote host.

Since the OPLAN (9096M) was offloaded to your User_Storage directory earlier, you should store the other student's TPFDD there also.  That way they will be grouped in the same location and you can manage them together.

Note:  OPLAN files offloaded by System Services (Offload Plan) are identified with a .OFF suffix (xxxxx.OFF).  TPFDD files created by System Services (Create TPFDD) reflect the file name specified.  IMS TPFDDs exported from the JOPES DB are identified by the TPFDD name without the .OFF suffix.

When the FTPtool transfer is complete, you will view the file to see what was moved into your account.

To begin the transfer process, you <POINT AND CLICK (right)> on the File button.

The File button and other buttons with arrowheads on them are selected by the right mouse button.

If you <POINT AND CLICK (left)> on an arrowhead button, the first activity in the button's pull-down menu is selected by default.

You can now switch to your local host computer's user account directory and view the TPFDD you transferred from the /h/data/local/tpfdd directory.

Text Editor.  The text editor allows you to view and edit the file as desired.  Most of the options are available by clicking right on the option buttons.

After you see the text, you can exit the Text Editor, return to your local host directory, and delete the other student's 909XS TPFDD from your User_Storage directory.

FTPtool
27	From Ftptool:  Local Host window, <POINT AND DOUBLE CLICK (left)> on Text Editor V3.3 - {OPLAN} Window Menu button to close the window.	Ftptool:  Local Host -...  displays (similar to Figure 4-27).
28	Scroll as necessary and <POINT AND CLICK (left)> on the TPFDD file you transferred from the /h/data/local/tpfdd directory.	Plans are highlighted.  Note:  Besides recognition of the TPFDD file name, you can identify the most recently copied file by using the date/time stamp.
29	<POINT AND CLICK (right)> on File.	Pull-down menu displays File options.
30	<POINT AND CLICK (right)> on Delete.	Local File option displays.
31	<POINT AND CLICK (left)> on Local File.	Pop-up requests confirmation to delete the file.
32	<POINT AND CLICK (left)> on Delete.	File is removed from the local host's directory.

Using FTPtool, you were able to copy, view, and delete a file.  But what do you do if things don't go so well?  The first thing you may want to check is the file properties.
Checking File Properties.  You can use the Properties menu option to review file permissions.  This way you can find out what kind of permissions are associated with a file (and whether you can read, delete, or perform other actions on the file). 

Only the owner of this particular file can read and write to it.  No one else has access.

This window will allow you to appear to modify the permissions associated with the file; however, the file permissions are not really modified.  If you were to refresh the window, the original permissions would display.

Note:  Modification of permissions associated with files will be discussed later in the lesson.

You have completed the FTPtool portion of the lesson, so please exit FTPtool.

FTPTOOL:  EXIT
Step	Activity	Anticipated Result
1	From the Ftptool Version 4.3 - {Remote Host} window, <POINT AND CLICK (left)> on Disconnect.	Directory/File display is cleared.
2	<POINT AND DOUBLE CLICK (left)> on the Ftptool Version 4.3 - {Remote Host} window Menu Button	LAUNCH WINDOW (Fig. 2-1) redisplays.

So far, all of the file management instruction described transfers information to or from internal files, tape storage, and disk drives.  However, there may be occasions when you need to save files to floppy disks for transfer to computers that are not on the network.  If the files are too large, there are commercial compression and decompression programs available that permit storing large files on floppy disks.

Note:  Available compression/decompression tools:  FTPtool programs are in the File option.  The WWS can use a program called StuffIt.  The DOS based computers can use a program called PKZIP that comes packaged in the JFAST \Utils directory.  SPARCstations can use either compress/uncompress or pack/unpack.  There are UNIX manual pages available for compress and pack that describe how to use these commands.

Transferring Files to/from Floppy Disks.  The lesson now describes the interface navigation for transferring files to/from DOS floppy disks and demonstrates how to save a TPFDD file to floppy disk.  The Session Manager Menu has a Save to Floppy option, but it only works with files that the Session Manager has created.  The DOS format is demonstrated because it should be common to most of the GCCS application computers.
Save File to Floppy Disk.  To save a System Services/FTPtool created file to DOS floppy disk, you can use PC-NFS software commands available on the JFAST host computers.  (Refer to Figure 4-15).

Note:  To export (save) a file(s) to a DOS disk from a WWS, you can first use the FTPtool to access the server where the file resides.  Then use FTPtool to copy the file(s) from the remote machine to your client machine.  From a WWS, you then use the "doscp <filename> -d /dev/rfloppy0" (DOS copy) command to copy the file to a DOS formatted disk.  If you have access to a command line on a SPARCstation, you can use a program called "filemgr" located in the /usr/openwin/bin directory.  "filemgr" operates somewhat like Microsoft Windows.  If you need help, see a System Administrator for assistance when using the UNIX commands.

To use the JFAST computer, you must first login through Tigersafe before you can access the PC-NFS software that allows you to download files from the server and save them to a floppy disk.  PC-NFS is installed on the computer so JFAST can directly access TPFDD files on the database server.

Requirement.  Save the 900XT_marines file in your User_Storage directory to floppy disk (DOS format).

PC-NFS provides many navigation paths for saving a file to floppy disk from a server.  The fastest way is to use the file transfer protocol (FTP) commands to copy the 900XT_marines file from your user account's User_Storage directory directly to the floppy disk.

The 900XT_ma file is now stored on a DOS floppy disk for use as a source for other GCCS applications like JFAST or MAGTF II.  If the file were too large to fit on one floppy disk, you could have saved it to the PC's hard drive, then used a compression program like PKZIP to save it to floppy disk(s).

While the Session Manager cannot save a System Services and/or FTPtool created file to floppy disk, the Session Manager can import files from floppy disk for System Services and/or FTPtool access. 

Load File from Floppy Disk.  There are many ways to import files from DOS floppy disks.  Each method is system specific, some more complex than others.  The easiest way to import a file from a floppy disk is to use the Session Manager Folder options.  The Session Manager can use DOS or UNIX file formats.  It loads the file into your user account's User_Storage directory.  (Refer to Figure 4-15).

Requirement.  Import a file from the instructor provided floppy.  This file contains Air Force TPFDD records in transaction format that will be used in the next lesson to update the JOPES database.

After loading a file from floppy disk into your user account, the User_Storage directory path can then be used on the System Services menus (Load a TPFDD/Merge TPFDD) to import TPFDD data into the JOPES database.

You can also access the file in the User_Storage directory via the FTPtool functions demonstrated earlier.

But there is a catch!  The SESSION MANAGER:  Folder system attaches additional information onto the filename.  For example, the SESSION MANAGER:  Folder may show you a file named 909XT.AF, but it's true filename, to all other applications, is 909XT.AF_353950002.AF. 

So, if you give another application, like System Services, the SESSION MANAGER:  Folder filename, the other application will not find the file. 

One possible work around is to remove the offending appendage!  Later in this lesson you will use a UNIX command to rename the files.  For now, remember that with SESSION MANAGER:  Folder, all is not always as it seems!

Security Cautions.  You must be aware of the procedures that apply to the handling of classified information.  This is especially true when dealing with diskettes.  As a general rule, diskettes should be marked with a classification sticker and, if the classification is confidential or above, diskettes should be controlled.  Different sites follow different procedures so check with your security officer back home if you have questions.

The focus of the lesson moves from OPLAN/TPFDD transfers to reference file administration.

OBJECTIVE.  Given a GCCS environment, manipulate the reference files using RFM to provide access to other JOPES applications.

Reference File Administration.  There are two main reference file tools available with JOPES:  the Reference File Administration (RFA) application and the Reference File Manager (RFM).
The RFA Application.  RFA provides the capability to update and maintain reference tables in all the JOPES Core databases from a central location.
JOPES has a number of data files that are OPLAN-independent and are fairly static.  These files, collectively known as the Reference Files, are:  GEO, TUCHA, TUDET, ASSETS/CHSTR, LFF, PORTS, and APORTS.

Even though these data stores are fairly static, they do change.  Services and agencies submit changes to these data stores in accordance with the Joint Reporting Structure (JRS) established for each Reference File.  The RFA software is available only on the NMCC application server, and is only executed by DISA/JIEO/JEXNCP personnel.

Once JRS transactions have been verified and processed by RFA, JEXNCP personnel update the Reference Files stored on the JOPES Core database (JCDB), present on all JOPES database severs within GCCS.

RFM Capability.  Some JOPES applications cannot directly access the JOPES database, but they still need the JOPES reference files.  For these applications, the reference file data is transferred using a program called Reference File Manager (RFM).

Reference File Transfer/Conversion.  RFM provides the transfer and translation of reference file information from the JOPES database to the application program.  A copy of the reference file is reformatted specifically for the selected application, then transferred to a different file location.

Reference Manager Admin Tool.  RFM also has an Admin Tool just like IMS.  The Admin Tool for the Reference File Manager specifies the file names that may be selected for transfer into the application programs.

Other Sources of Reference Data.  Not all reference information is available from the JOPES database through the RFM.  For those cases where the data comes from sources external to the GCCS network, manual procedures must be used to transfer the information.

JFAST Reference Files.  For JFAST, USTRANSCOM gathers the JFAST reference data from JOPES and its transportation component commands, formats it to meet JFAST FOXPRO database requirements, and provides the information and installation instructions to registered JFAST users.
Floppy Disk or Data Lines.  The files can be transferred on floppy disk or via encrypted data lines.  You use DOS commands to transfer the files to JFAST.

Source:  USTC J3-OPJ DSN 576-6898.  You can contact USTC directly to coordinate where and how to effect the transfer.  USTC will advise all registered users when DISA becomes the distribution source agency in the near future.

FAPES Reference Files.  The data to support FAPES exists in Joint, OSD, and non-Defense Department mobilization systems.  Some of the reference data is exported from the JOPES database and some comes on tape.  Contact the DISA GCCS hotline at DSN 653-8681 if you need additional details.

Now that you know when to use the file transfer tools, the lesson describes and demonstrates how to do it.

The lesson now demonstrates how to use the Reference File Manager to copy reference files from the server to applications on the server or other host computers.

Reference File Manager (RFM) Navigation.  The RFM process is similar to the IMS process, but the window navigation is different.  RFM also has an Admin Tool to control the information that appears in the RFM window.

The RFM window allows you to select the reference file available in the JOPES database, select the application to receive the file, then transfer it to an application.

Unlike IMS where all options are selected and then the entire transfer process occurs, the RFM process is sequential; you update the data first, then you transfer it.

Reference File and Date Panel.  The information shown in the Reference File and Date panel shows you what RFM does and does not have available for transfer to the applications.
The names of the files listed in the panel reflect files resident in the JOPES database.

The date entry column in the panel shows several types of information.

"No File" means the file has not been downloaded from the JOPES database to the RFM server.

A year/month/day entry shows the date stamp of the reference file itself.

If a file does not have a date stamp, RFM adds an asterisk and records the date the file was loaded onto the RFM server.

Update Button.  The Update button starts the requested update from the JOPES database to the RFM server.

Application and Last Transfer Date Panel.  The applications that can receive the reference files are listed in the Application and Last Transfer Date panel.

Application selection is necessary since each application has different requirements for the standard files, e.g., file format.

The date shows the last date the file was transferred into the application.  This is very useful information because you can compare this date with the date stamp on the file to see if the application is using the latest file available on the server.

Transfer Button.  The Transfer button causes the actual transfer of the file to the selected application.

System Status Notification Panel.  The system gives you immediate feedback concerning RFM system progress by displaying messages in the System Status Notification panel.

Note:  Unless someone has updated the RFM server's reference files, the RFM window probably reflects the first set of reference files that were installed with the GCCS environment.

Your review of RFM is complete so please exit RFM.

You should have a greater understanding of the reference file tools available in GCCS.  The next section of the lesson discusses UNIX, the operating system found on the GCCS servers and some of the client workstations.

OBJECTIVE.  Given an operational GCCS environment with access to an X-Term Icon, demonstrate the use of basic UNIX commands in support of JOPES operations.

Sun - UNIX Environment.  For this portion of the lesson, you will review selected UNIX commands.  The purpose here is not to make you UNIX proficient.  Air Education and Training Command (AETC) provides courses to help out with that.  What this portion of the course does is acclimate you to this environment, using some of the commands that you might be interested in.  It should show you that many of the things you do using any operating system, such as DOS or TSS (like getting a display of files), are supported by UNIX.  These commands may be useful to you in your current job.

You will use commands that deal with file structure, permissions, devices, network commands, and commands to monitor a program.  But first you need to open an X-Term window where you will enter these commands.

Directory and File Structures.  Throughout this lesson you have saved plans to files.  You have probably already caught on to the hierarchical structure used by UNIX (and most other operating systems, such as DOS).  To see an example of a UNIX directory structure, you will use the "pwd" command.  The "pwd" command is useful when you want to find out which directory you are currently viewing.
"pwd".  As you move around within a directory structure, "pwd" (print working directory) can be used to find out where you are, i.e., the current directory.

When you first enter the UNIX directory structure, you will start at your home directory.  In most cases, it is /h/USERS/{Userid}/Scripts, where {Userid} is the userid you used when you first logged on to the system.

Your home directory is the default location for files you create.

"cd".  The "cd" (change directory) command, followed by a directory name, enables you to change the working directory to another directory.

"cd .." backs up to the next higher directory.

"cd /" backs all the way up to the root directory.

"cd" by itself returns you to your home directory.

The lesson will now use variations of the "cd" command to move up and down within the directory structure.  On the way up, you will use the "ls" command to list the contents of these directories.

"ls".  The "ls" (list) command lists the contents of a directory, much like a "dir" command does within DOS.

This abbreviated list only shows you the contents of the directory.  It only offers a minimum amount of information.

The "ls" command has many options.  Two options you may want to use are the "-a" and "-l" (letter l) options.

A "-" tells the system that options will follow.  More than one option can be preceded by a single "-".

The "a" tells UNIX to display all the files.  Unless the "a" is used, files preceded by a dot () do not display.

The "l" tells UNIX to display the files in long format, giving permissions, number of links to other files or directories, owner, group, byte size, time modified, and file name.

File Commands and Access Permissions.  When you use the "ls" command with the "-l" option, the string of characters on the left side provides a wealth of administrative information.  As depicted in Figure 4-38.

List Entry Types.  In the file list, if the first character is a "d", the line describes a directory.  If the first character is a "-", the line describes a file.

Permissions.  The next nine characters consist of three sets of three characters each.

The first set refers to the owner's permissions:  r=read, w=write, and x=execute.

The next set refers to the primary group's permissions (r,w,x).  Only one group at a time may be granted access to the directory/file.

The last set (r,w,x) refers to the others' permissions.

This concept is key to understanding permissions in the GCCS environment.

You may need to review files to check settings.  You will use a file you built earlier in this lesson to demonstrate some of the UNIX file commands.

"more".  The "more" command displays the contents of a text file one screen at a time.  It is a valuable tool when trying to determine what is in a file before copying it, using it, or deleting it.  Additionally, keep in mind that UNIX is case sensitive.  You must type the filename exactly as it appears.

"cp".  The "cp" (copy) command copies files within and between directories.
The copy command only works if you have write permissions for the source file and write permissions in the target file/directory.

This command could be useful when trying to save a copy of a TPFDD to your home directory.  The TPFDD could then be deleted from IMS, precluding access by other users.

Note:  IMS stores TPFDDs in the /h/IMS_RFM/imsdata directory.

Remember earlier in this lesson when you used the SESSION MANAGER:  Folder system to import a file from a DOS diskette?  Your instructor told you that you would be using a UNIX command to remove the offending appendage.  Well, the time has come to use the "mv" command to rename the files.
"mv".  The "mv" (move) command is used to move a file between directories.  It can also be used to rename a file.
First though, you will use the "ls" command to list the complete filenames you will change.

Notice that your file has been renamed.  In the next lesson, you will use this file with the System Services application.

"find".  The "find" command is used to find a file somewhere in a directory hierarchy.

It is not unusual to save a file and then have no idea where the program stores it.  The "find" command enables you to look for it.

There are numerous search parameters you can use with the "find" command.  You will use three of them to search for your new 900xt_USMC_bkup file.

The "." after "find" tells it to start in the current directory.  "-name" provides the name to search for.  "-print" tells it to display the results on screen.

To search into all the directories you have permissions for, replace the "." with "/".  This starts the search in the root directory.

"chmod".  File permissions control access to a file by the user, the group, and all others.  You have seen permissions of files when you used the "ls" command.  To add or change the permissions on a file, use the "chmod" (change mode) command.
It is often necessary to use this command when copying files because both the source and target must have write permissions.

It is also very useful when protecting files in your home directory.  If you change the permissions of copied TPFDDs and planning files to owner access only, other users cannot view, copy, or change them.

Note:  Read permissions do not include search activities.  Execute permissions for directories include search activities within the directory.

The "777" is the sum of the matrix table numbers defining who has read, write, and execute permissions.  See Figure 4-39.

The 'hundreds' column of the number 700 is the sum of 400 for user read, 200 for user write, and 100 for user execute permissions.
You can use any combination of the three numbers, 400, 200, or 100 to indicate the permissions being granted to an owner of the file.

A sum of 500 would indicate the owner has read and execute permissions.

The group and other permissions are granted using the same methodology for the 'tens' and 'units' columns.

"rm".  You can now remove the 900xt_USMC_bkup file from your directory with the "rm" (remove) command.

The "rm" command removes one or more files or directories.  You must have write permissions to remove a file/directory.

The "-i" option causes the system to ask for confirmation.

Note:  To completely remove a users' directory and all subsequent data and directories beneath, you can use the "-r" option of the remove command.  However, once a file is removed in UNIX it cannot be restored.  When it is gone, IT IS GONE!

Storage.  The amount of free storage on the system is also a very important consideration for system administration.
Monitoring.  As the system storage devices start to fill up, efficiency goes down.  Monitoring system storage can provide clues concerning potential problems.  Experience shows you when things are slowing down.  Check the disk space and consult the technical staff if the numbers do not seem right.

"df".  The "df" command displays the amount of free space on the disk.  Each disk block is equal to 512 bytes.

The "df" command enables you to see if the system has room to store your TPFDDs or reference files.

The "df" command can also be used to see if a system is failing because the drives are filled to capacity.  A full or highly fragmented disk can slow system response considerably.

Note:  UNIX commands and their options can be different between different hardware vendors.  For example, the "df" command on the Sun server supports a "-k" option to show all disk space, in kbytes, used and unused.  On the WWS, the "-k" option is not supported.

Network.  Throughout this course, you have heard about the GCCS network.  This section of the lesson shows you additional commands you may want to use to access the network.
"telnet" Remote Access.  Many of you may have used Telnet on another computer., e.g., the old DPS 8000.  "telnet" is also supported in the GCCS environment to access a remote computer.
It can be useful to establish a "telnet" link with the server or a different workstation to monitor and/or change the operating environment (accounts, passwords, permissions on files, etc.) at a remote location.

You cannot use "telnet" to access a different JOPES location and use the JOPES applications there.

Note:  To run JOPES applications remotely you would use the RREM application which is taught later in this lesson.

You have used the "telnet" command.  Let's move on and cover other items of interest with network commands, such as finding out what other machines, or hosts, are up on the local network.
"rup".  The "rup" command can be used to find out if a remote system is up on your local network before you try and "telnet" to it.

"finger".  To find out who is logged onto a system, you can use the "finger" command. 

Note:  You can perform many of the same functions as rup and finger if the Monitors icon, found on the launch window, is available to you.

In the networking portion of this lesson, you have accessed remote machines and used other networking commands.  You will now exit the X-Term window.  The lesson continues with a discussion of running JOPES applications at a different site.

OBJECTIVE.  Given a GCCS environment, know how to establish and use the capability for a user to access a remote host and run an application.

Using Run Remote (RREM).  If, for whatever reason, you cannot access RDA or other JOPES applications from your site, GCCS offers you a way to run them from your workstation using another sites' server. 
Purpose.  With Run Remote you can:
Access a GCCS application not available at your site.

Allow selected off-site users access to your local only plan.

Allow a network FM access to a local plan on a local server so that the network FM can distribute the plan network wide.

RREM Capabilities.  To use the RREM capability, follow the keystrokes in the Run Remote table below.  Keep in mind that to be allowed access to the remote sites applications, you must supply RREM with a valid remote host name.  You must also use a valid login (userid) name for that remote host.

If you select number 3, JOPES, a JNAV window will display on your workstation.  You then follow the common operating procedures for the JNAV window to start the JOPES application of your choice.

To return to the Run_Remote window, you will have to close the JNAV window.  To close the JNAV window, you <POINT AND DOUBLE CLICK (left)> on the JNAV window Menu Button [-]. 

Before switching topics on you, it is time to accomplish a practical exercise.

Requirement.  Using the disk supplied by the instructor, upload the data (a file in TPFDD format) into your personal user storage area using the Session Manager Foldering system.  Rename the file so that it does not have the numbers on it that the foldering system automatically puts there.

Summary.  During this lesson, you were exposed to the JOPES capability to monitor the Receive Queue and the Send Queue for processing problems.

You also monitored the TDS and checked on whether or not the JOPES database was synchronized.  You even did a little investigation on how well the TP and TDS were functioning.

Then you explored journalization and auditing to discover the who, what, where, and when concerning record changes to the JOPES database.  With JOPES, this means you created history files and then used the auditing capabilities to view the history files.

Next you used the tools available for moving data, such as OPLANs, throughout the GCCS.  These file transfer tools included parts of the System Services application, FTPtool, IMS, RFM, and the session manager Folder.

This lesson concluded with a review of the UNIX environment where you used several UNIX commands that might be helpful to you as you troubleshoot a problem.