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

Setup.  To accomplish this lesson, you will need access to JOPES and the 9000 series plans with the standard JD94TNG functional permissions.  You must be listed in the GNAME file as the SYNC TDBM and in the Special Access File to execute Subsystem/Function D4, Option C, and H2, Option G.  The G- LINK scripts for downloading a file must be installed and operational on your terminal.

Overview.  For the next hour or so, you will be exposed to several topics that could be applicable in a crisis situation.  You will begin this lesson with a quick review of some of the electronic communication capabilities of the system followed by a look at what you might be asked to do regarding an OPLAN in the JOPES TS3 database.  Specifically, you will modify an OPLAN's characteristics, execute a retrieval of specific records, and figure out how to transfer an OPLAN to the Secret GCCS environment.

The system we use today has methods to communicate and pass information electronically.  We will now look at those programs that provide us this capability.

OBJECTIVE.  Given a WWMCCS environment, know how to use a teleconference to support the community of JOPES users.

Note:  TM 245-91, WWMCCS Intercomputer Network (WIN) TELNET, Teleconferencing, and File Transfer Service User Guide, provides detailed information on subject applications.

WWMCCS Teleconference Capability.
Teleconferencing (TLCF).
Purpose.  The purpose of the TLCF system is to allow up to 512 active terminal users at geographically separated locations to participate in up to 31 separate, simultaneous conferences on a host.  Up to 1500 participants, including a chairman and six alternates, can be registered on the conference to carry on a dialogue through the terminals.

TLCF Operations.

Login.  TLCF can be entered directly when logging into the system by replacing TSS with TLCF.  If already in TSS, you must use the direct access connection (JDAC) command.

Modes.  TLCF gives the user the ability to instantaneously provide information in a secure mode to interested parties.  This is accomplished through the use of the four major modes of operation.

Entry Mode.  This mode allows the user to initiate, reconvene, join, or merge.

Command Mode.  From this mode, other activities are selected like "Talk or Listen," DAC to another program, etc.  This is where you end up if you initiate, reconvene, or join a TLCF.

Listen Mode.  This mode allows passive reception of messages.  This mode only recognizes a break command that puts you back into Command mode.

Talk Mode.  This mode allows the user to enter messages into the system to TLCF participants.

Capabilities.  TLCF has the following major capabilities:

Initiating, joining, adjourning, or reconvening a Conference.

Message entry.  ($INSERT can be used to import files into the TLCF.)

Formal (public) TALK message.

"Eyes only " informal COMM message.

Message reviewing.

Notices (event messages).

Saving and printing the minutes of the conference.

Use of DAC program without leaving a conference.

Management of the conference.

Managing keywords and messages.

CAT Support.  FM CAT support can range from a high of initiating and managing the TLCF to merely providing guidance to the director in regards to the teleconference.

TLCF, in many people's opinion, is by far the most used electronic communication support system.  The next mainframe communications support system is the WINMAIL function.

Timesharing WIN FTS Readmail Interface (WINMAIL).
Purpose.  WINMAIL provides each user with a direct electronic communications capability.  It is part of the FTS program that you used in Lesson 10.  There is also a TSS interface with the WIN host software that lets the user access the mailbox READMAIL service of FTS while in TSS.  On entering the WINMAIL command, a TSS user can perform all the READMAIL functions as though logged directly into FTS.

Value Added.  WINMAIL provides a quick capability to communicate with other registered users in the network environment without having to leave your terminal.  This is considered an on-line capability.

Operations.  WINMAIL is entered while in FTS (or in TSS for readmail only).  WINMAIL allows you to do the following:

Broadcast function.

Mail file manipulation.

Deferred delivery.

Automatic acknowledgement of received mail.

Notification of mailbox status upon login to FTS.

CAT Support.  As FMs, you will find that you are the first line of defense for the user.  You are expected to know how to make the mail system work.  What you need to know is where the system is documented and call the TDBM if it needs fixing.

Now that you have reviewed the capabilities of the electronic communications resident within TS3, you will next turn your attention to learning how to modify an OPLAN's characteristics after it has been loaded into the JOPES database.

OBJECTIVE.  Given an operational JOPES environment, modify a plans' access/type and distribution.

Requirement.  You currently have an OPLAN on the database that is a limited access plan resident on the primary (local) host only.  Your task is to change it to a normal access plan so that the appropriate individuals will have access to it and distribute it to the backup site so that it will be on both hosts in the event one of the hosts develops problems.

Change OPLAN Type/Access/Distribution.  When a plan is initialized, the creator sets several plan attributes.  These include type/access (close hold, limited, or normal) and distribution (local or network).  When circumstances warrant a change, then these attributes need to be changed.  S/F H2 allows you to change these attributes.  H2 covers three different areas with its seven options.  You are allowed to change category of access, review and update current access, and adjust distribution.  To effectively allow you to work with real information, you will not take them in the screen order.  A review of user access will be first.  Figure 11-1 shows the H2 screen.

Note:  Navigate to the H2 screen.

Review/Update USERID Access to OPLAN, Option D.  This option allows the plan originator or Network FM to review and update access to a close hold or limited access plan.  Selecting this option takes you to another menu to select further options.

Review User Access, Option A.  This option allows you to review the users, by Project Code (User ID), that have access to the specified plan.

Delete User Access, Option B.  This option allows you to delete specific users from the plan access list.

Add User Access, Option C.  This option allows you to add users to the plan access list.

Add User Access From OPLAN {xxxxx}, Option D.  This option allows you to copy a plan access list from one plan to another.  This comes in handy if you are creating another plan and the same people are involved.

Note:  This figure shows those who currently have access to this OPLAN.  You do not want to add any specific users to the plan, but you want it to become a normal access networked OPLAN.  You will go back to the other options now to change your plan to normal access.

Change Close Hold OPLAN to Normal, Option A.  Selecting this option changes the entered OPLAN from a close hold to a normal plan, which grants access to users with that plan series permissions.  The next screen (IF-205, Fig. 11-4) would then appear which allows for verification of the PID and option selected before the transaction is actually sent.

Change Close Hold OPLAN To Limited Access, Option B.  Selecting this option changes the entered OPLAN from a close hold to limited access, allowing the plan to be networked.  Again Screen IF-205 (Fig. 11-4) would follow, which allows for verification of the PID and option selected before the transaction is actually sent.

Change Limited Access OPLAN to Normal, Option C.  Selecting this option changes the entered OPLAN from a limited access to a normal access, granting access to all of those individuals with that plan series permissions.  You will now execute this option for the OPLAN that you are using.

Review/Update Host/Terminal ID Restrictions to OPLAN, Option E.  This option allows you to update specific host/terminal access to close hold or limited access plans.  The host space is a carry over from the days when there were 15 to 20 host mainframes because terminals could have the same IDs at different hosts.  If you have a local plan of either type, the host entry is still a required entry.

Change Current OPLAN Distribution, Option F.  This option is used to change a networked OPLAN's distribution and is restricted to the Network FM.  You can review or delete a site from an OPLAN distribution list, but you cannot add a site.  Sites can be added to the OPLAN routing by the Network TDBM.  When deleted, transactions are no longer sent to the site specified.

Note:  Navigate to S/F D4.

Ready Plan For Distribution.  When a local OPLAN is initialized, the PLAN- INFO (200) and the AC-INDEX_REC (020) records are generated throughout the system.  This means that both hosts know that the PID exists, preventing anyone else from creating that same plan number.  If the plan needs to be networked, the plan originator must ready the plan for distribution using S/F D4, Option C.

The job executes with no further action on your part.

The system generates a transaction that creates the missing subfile headers at the backup site, that are required for a networked plan, but not for a local plan.  The subfiles are Access Control/Sync (0-99 series), Unit Information (400 series), Requirements (500 series), Scheduling and Movement (600 series), Nonstandard Cargo (700 series), currently not used (800 series), and Force Module (900 series).  These header records must exist at each site prior to the Network FM distributing the plan information.

Note:  Navigate to S/F H2.

Distribute Local OPLAN to Specified Network Site(s), Option G.  This option takes a local plan and networks it.  Only the Network FM can do this.  The plan must have been readied for distribution using D4, Option C.  The Network FM selects Option G and deletes those sites to which the OPLAN should not go.

Note:  Any site deleted will result in no OPLAN transactions of that plan being routed to that site.

Note:  HV is where you could go to monitor the distribution of the OPLAN to the selected sites.

At this point, you have accomplished what you set out to do.  The OPLAN is now accessible to those who need access, and a backup copy is at the backup site.  Note that you did not do it alone, but it took a coordinated effort of the OPLAN originator, the local and Network FMs, and perhaps the TDBMs.  Another task that you may be asked to do is retrieve specific records for a report or some other purpose.

OBJECTIVE.  Given an operational system, design a retrieval for a group of records meeting specific criteria.

The Retrieval/Graphics Process.  Detailed information on retrieval/graphics procedures can be found in the following application software documents:  the JOPS Users' Manual, CSM UM 200-85, and the JOPES Users' Manual, TD 18-14-1, Vol. 8.  In some cases, the instructions are very detailed, while in others detail is virtually non-existent.  We will review what we have!
FM's Role as Super User.  Many of the personnel required to work within the JOPES community and most people involved with the TS3 environment are required to attend at least some training before they are granted system access.  However, many (probably including yourself) do not use the system on a daily basis, and those that do, often use only an isolated portion of it.  Like any software, "use it or lose it" applies.  As the FM, it is perceived you deal daily with the system; users look to you as the expert.  Expertise with ad hoc retrievals will help you be in a position to offer guidance.

Review Retrieval/Graphics Actions.

JOPS F11F Report.  The F11F Ad Hoc TPFDD Report module of JOPS provides the capability to design and print reports containing only those items specified by column data reference code.  All records, or user qualified records, may be included in the report.  This module allows the user to store and reuse the retrieval.  The TPFDD/SRF must be loaded into either temporary or permanent file space to execute a retrieval.

JDS F6 Report.  The F6 Ad Hoc Report of JDS provides you the capability to design and print reports and graphics containing only those record fields identified.  This subsystem also allows you to store and reuse the retrieval.  F6 operates using the JDS active database and consists of a three step process.

Data Selection.  In the data selection phase, you will be offered several selections that result in the extraction of certain portions of the database. 

Note:  In data selection, it is important to note that once these records are extracted, other records cannot be looked at unless the data selection phase is repeated.

Data Qualification.  Data qualification is the second step in the retrieval process.  In this step, you further qualify the data selected.  Data qualification reduces that amount of data by narrowing what you want to look at.

Output Selection.   Once the exact data you wish to view has been selected, the final step, output selection, is entered.  During this step, you will identify elements to appear, select a format for the report, and a location for it to be sent.

F6 has over 20 different output formats.  As a quick introduction, you will review some of those used most often.  They will be discussed in more detail later.

F6 Output Options.
Screen Displays.  Allows on-line viewing before executing a save or print.

Hard Copy.  Sends reports to the printer.

ASCII Files.  This file may then be posted to a personal workstation and input into a commercial software package.

QRFs AND USFs.  QRFs and USFs are special files created by the user. 

A QRF is a file containing data.  It is a snapshot of data that you extract and set aside for future use.

A USF is a file that stores the format you have selected.

Force Modules.  F6 also provides the ability to retrieve requirements from the database and place them in a force module.  You would then be able to track the FM through its deployment using any of the appropriate subsystem/function codes that have already been discussed.

Now that you have had a quick review of the capabilities of F6, it is time to execute a retrieval.

Requirement.  There have been several questions regarding the port capabilities of some of the planned PODs in your OPLAN.  The CAT Chief has requested a report displaying the Army and Air Force units planned to be flown by AMC to the PODs of El Borma (GEOCODE FTZH), Tozeur (GEOCODE TPAL), and Jerba (GEOCODE JEAH) within the first ten days of this OPLAN.  Sort the report by LAD and Service, include:  ULNs, Unit Names, Bulk STONS, PAX, and POD.

Generate an F6 Retrieval to the Screen. 
Data Selection Phase.
Retrieval Mode Selection (Fig. 11-8).

Data Selection Main Menu.  This identifies a broad category of data to be retrieved.  Once you select one of these subsets, the remainder of the database is no longer accessible for the retrieval.  However, you can always return to data selection and change your selection criteria or input sources.
Option "A" retrieves data on ULNs, CINs, and PINs.

Option "B" is not applicable because TS3 does not contain S&M data.

Option "C" retrieves data about specific units.  It may include SORTS and TUCHA data.

Options "D" and "E" are no longer applicable because TS3 does not use the S&M data.

Option "F" will use the criteria from a previously saved USF to retrieve data during the data selection phase.

                         Option "G" is not applicable.  JOPES Standard Save Files are no longer available.

Option "H" will use the criteria from a previously saved Graphic Data File to retrieve data during the data selection phase.  Output can be to a tabular report or graph.

Option "I" creates, edits, or reviews a Movement Allocation Table.  Movement Allocation Tables are user created data tables to assist in planning and defining a graphic product.

Option "J" permits rapid build of a QRF database using up to 15 OPLANs.

Data Sources Selection.  Possible data sources include OPLANs, TPFDDs (tape, sequential, and random), and QRFs.  When using OPLANs or TPFDDs, the more specifically you define the selection parameters, the faster the retrieval will run.

Note:   A family is a method of comparing two sets of data such as OPLANs, FMs, etc.  It is a grouping of up to 15 sources.  A family does not have to be related in any way, but could represent a deployment scenario.  Loading plans to two families facilitates comparison of two scenarios.  You may select OPLANs from both exercise and real world for a family.  An OPLAN family can run the gamut from those in support of a geographic region to a general war plan.  In F6, OPLAN families are determined solely by entries on this screen.

Data Selection - OPLAN Criteria Menu.

Note:  Selects data to be retrieved by LAD based on the C-Days specified.  Display of the Retrieval Monitor screen may be very brief with the Data Qualification (Fig. 11-13) screen displaying without entry.

Retrieval Monitor.  This screen advises that your retrieval is being done.  No entry is required on this screen and you will be sent automatically to the next screen when the retrieval is complete.  If the retrieval is done in batch, note the SNUMB.

Data Qualification Phase.  This is where you will select additional limiting parameters to narrow the scope of the retrieval.
Data Qualification.  Note the total number of requirements currently extracted.
Option "A" returns you to Retrieval Mode Selection (Fig. 11-8) to restart your session.

Option "B" returns you to the Data Selection Main Menu (Fig. 11-9) to make another choice in selecting data.

Option "C" takes you to the appropriate data qualification menu depending on whether you want to qualify requirements or unit information data.

Option "D" takes you to the Load from User Save File screen where you select a USF to use for the retrieval.

Options "E", "F", and "G" take you to the Output Selection Menu screen (Fig. 11-19).  Option "E" will use existing qualification criteria for the retrieval.  If no qualification criteria exists, it will automatically exclude medevac, NEO, retrograde, shortfall, oncall, and inplace records just like Option "G."  Option "F" will use no qualification criteria.

Requirements Quick Qualification.  This screen is the beginning of a series of data qualification screens.  The Requirements Quick Qualification screen allows you to qualify on any of the most often used data elements.
A "?" in the Function Code will display HELP screens.

The requirement outlined makes it necessary to further qualify your data.  Only one POD can be entered on this screen.  To further qualify your data, or enter more than one POD, you must place an "X" in the block labeled "Enter 'X' to Proceed to Extended Qualification Menu," so additional screens would post.

An "N" in Service and an "X" in the Not column retrieves all records other than Navy.

Requirements Data Qualifications Menus.  Page movement is done by placing a page number in the block provided on the upper-right side of the screen.
Page 1 of 4.  On this screen, enter the data elements from the Requirements.
The titles displayed are predefined and may not reflect titles commonly used.

The lower half of the screen allows you to request further qualification screens by placing an "X" opposite those fields.

Page 2 of 4.  Provides a list of codes on which to further qualify the report.

Requirements Qualification POD GEO and Country Codes.  This screen allows you to enter the POD GEOCODEs that you want to use to narrow the data for your retrieval.  This screen appears because you selected GEO/Country Code (POD) on page 2 of the Requirements Data Qualification Menu.

Qualification Criteria Summary.  This is an information screen outlining your selection criteria for information.  Read it carefully because it also offers you an opportunity to return to the Data Qualification screen and begin again.
Several commands are available for use on this screen.

Help explains the remaining command line options.

TP takes you to the next page.

Restart returns you to Data Qualification (Fig. 11-13) to restart qualification selection.

Append displays the System Qualification Menu.

Load displays the Load From User Save File.

Delete NN deletes a numbered set, then redisplays this screen with the renumbered sets.

Change NN redisplays the first qualification screen for the set being changed.  Upon summary redisplay, the system renumbers the changed condition and appends to the summary at the end.

Output Selection Phase.
Output Selection Menu.  Notice the number of requirements you have now compared to the number posted previously on the Retrieval Monitor.
This screen marks the beginning of the Output Selection Screens.  Options available on this screen are:  sending your work to one of several printing locations, storing your work on magnetic media, previewing it on a screen, or returning to several starting points.

The options available for use in the bracket below Subsystem and Function Code are:

"R" = Restart, (Retrieval Mode Selection).  Allows you to restart session.  (Fig. 11-8).

"D" = Data Select (Data Selection Main Menu).  Allows you to reselect data.  (Fig. 11-9).

"Q" = Data Qualify (Data Qualification).  Allows you to requalify the retrieval data.  (Fig. 11-13).

"E" = Execute Queue (Retrieval Print and Remote Spawn Option).  Used if any activities (reports, graphs, etc.) are in the queue.

"S" = Save (User Save File Update).  Allows you to save your format in USF.

"C" = Adjust C-Day (Relative C-Day Specification).  This option no longer applies.

As mentioned before, there are 23 different output selections grouped into five types of media.

Options "1" & "4" send your data to storage on magnetic media.

Option "4" allows the saving of an ASCII Data File.  ASCII stands for the American Standard for Computer Information Interchange and serves as a standard for communication between computers.  ASCII files provide a generic, but limited, communication tool for computer software.  As you may be aware, many commercial off-the-shelf software packages such as WordPerfect, WINGZ, and Harvard Graphics use ASCII files to communicate.  For example, you could develop a tabular report to provide raw data on port work load requirements versus throughput capabilities.  Download it as an ASCII data file via this option, then upload into Harvard Graphics to draw/display graphs for briefings, etc.

Another important feature found on the Output Selection Menu screen is Option "7" - Create/Update Force Module.

Several options ("12," "13," "20," & "21") allow the storage of GDFs or Graphic Display Files.  These files are used to store graphic data in much the same way as a QRF stores alphanumeric data.  Keep in mind that special equipment may be required to display graphics on your terminal.

If you need a hard copy, use options "3," "6," "9," "11," "17," or "19."  Selection of any of these options sends the product to the F6 Batch Queue for holding.  The "execute" command on the Output Selection Menu screen allows you to set up the output on the Spawn Batch Job screen and produce the required product.

The remaining options send the report to the screen.

Note:  Equipment Count applies to Army equipment only since the Army is the only service that consistently uses the equipment identification code (EIC).  This function reads the first six characters of the EIC of Level 4 cargo data records and, if those six characters match the code for a piece of equipment as requested in any of the column definitions, then the count for that column will be incremented.  The report generated displays counts of types of equipment associated with the retrieved data.  Equipment count is the only F6 function that expresses type of equipment by quantity.  You must have previously selected Level 4 Cargo Equipment Quantity Data on the Data Selection - OPLAN Criteria Menu screen to select output options 16, 17, 20, or 22.  Unit Count allows you to receive a count of the number of impacted units in a selected category in an OPLAN or OPLAN family.  The unit count adds dual-tasked units only once, and the system counts each unsourced UIC as a unique unit.  However, the system disregards split-shipment cargo.  Unit count applies to ULNs only.  The Additional Column Values Screen allows you to select up to ten unit type combinations for retrieval.  On the Output Selection Menu, choose options 18, 19, 21, or 23 for a unit count tabular report, graphic data file, or an online graph.

Produce an Ad Hoc Formatted Report to Screen.

Output Format Specification.
Title Selection.  On this screen, enter or change up to three lines of title.
Enter "X" To Continue with no Further Editing takes you directly to the output report if in timesharing or to the Output Selection Menu if in batch.  Enter "X" To Return to Output Control Main Menu allows you to return to the Output Selection Menu.

The last block allows you to determine the number of parts per page you want for your retrieval/report.  You cannot exceed two parts if in timesharing; four parts in batch.  If you select subtotals, the timesharing retrieval will always default to one, no matter what you select.

Depending on your selections on the Data Field Selection screen, you will go one of three places.  Because you selected Requirements, you are sent to the Requirement Output Format Specification screen.

Requirement Output Format Specification - Data Field Selection (Part 1 of 4).

This is the first of four screens that allow you to select the exact data fields that appear on your report.  Page through the screens by placing the page number in the To View Additional Parts block.

Some data elements may be identified differently, therefore, they may not be familiar to you.

Page through all four of these screens to view various options.  Output selections are not required on all four screens.

You can return to any part of the Requirement Output Format Specification - Data Field Selection screens by entering the appropriate part number.  When you are satisfied with your selections, leave the Part field blank and press <RETURN>.

Display Retrieval.  This screen (Ad Hoc Formatted Report) has the title you selected for your report.
Page through your report.  The page commands at the bottom are somewhat different than what you have used in the past.
Parts are page extensions in the width dimension, like a panoramic foldout in a travel magazine.  Determine if a report has more than one part by looking at the upper right corner of the screen for the words "Part n of n" (where n is a number).

To display a part, use the Page command (nnn/nn).  The first set of numbers represents the desired page number, and the numbers on the right represent the part number, i.e., the command "Page 45/2" would display part 2 of page 45.

If the report is unsatisfactory, you could use the commands listed at the bottom of the screen to go to the appropriate screen to make the changes.
"Formats" or "FO" will return you to the Report Format Specification screen you just left.

"Fields" or "FI" will return you to the screen (either of three Format Specification screens) where you defined the fields.  If you selected a screen report, you are looking at your report.

"Title" or "TI" returns you to the title selection screen.

"Next", "NP", or pressing <SPACE> <RETURN> will take you to the next page.

"Search" or "SE" looks for specific items within the report.  Search 1 XXXXX (where ULNs are the first column) will locate the page where that specific ULN first appears.

"Help" or "HE" brings up the help screens.  These help screens explain the various paging commands and options, including the search feature.

"Menu" or "ME" returns you to the Output Selection Menu (Part 1 of 3) where you began defining your output format.

Return to Output Selection Menu.  The Output Selection Menu is the screen where you can design how your report looks.

Report Format Specification.
Report Format Specification (Part 1 of 2).
Output Order posts without numbers but defaults to the order they appear on the screen.  If you wish to change their order, enter numbers representing the order you wish them to appear.  "1" represents the first column reading left to right, "2" the second, etc.

Sort Order/Seq determines the priority and method for sorting those records included in the report.  1A is the primary sort with the A indicating ascending order; 2A depicts a secondary sort in ascending order.  The requirement was to have the report in LAD/Service sort in ascending (i.e., C000 to C009) order.

Subtotal Break is used to include subtotals after a particular set of records and ignore subtotals unless the totals are requested.  For example, subtotal breaks may be used to post subtotals for a particular day or a particular location.  Subtotal breaks are not allowed unless a "Sort Order/Seq" is specified.

Expand Codes will print the expanded code for those areas marked.

Total Fields will total the requested items at the end of the report.

On All Parts places the field indicated as the first field on all parts of the report.  It is a good idea to check this block (for the ULN field) in case your report runs into multiple parts.  Usually the ULN field is selected because it is a unique identifier.

Column Heading will overwrite the existing field title with a new column heading if desired.  Change these to headings you are more familiar with, e.g., change Req Nr to ULN.

Review Part 2 of this screen.

Part 2 allows you to truncate columns in the Print From Character Interval.  You specify the beginning and ending characters you want to print out.  You can also change column headings on this screen.

The width of your display is a function of the width of the column headings and the width of the data fields themselves.  If you title the Req Nr field "Requirement Number," the system reserves 18 spaces for that column even though the field itself is only seven characters wide.  You can also use a "/" to create a multi- line heading.

Spend some time using Parts 1 and 2 of Output Format to design your retrieval to your satisfaction.  A good exercise is to try to reduce it to one page and one part.  When finished, return to the Output Selection Menu.

Note:  You may now exit F6 back to the JOPES Master Menu.

Now that you know how to extract specific data from an OPLAN, there is one more item you may be asked to do in a crisis situation.  If this OPLAN is going to be executed, then it will be downgraded to the appropriate classification level and transferred to GCCS/JOPES. 

OBJECTIVE.  Without references, identify, in specific terms, the method used to export a JOPES OPLAN to a floppy disk.

Air Gap (Sneaker Net) Procedures.  There is no way to automatically and/or electronically transfer a TPFDD from the TS3 (Top Secret) environment to the GCCS (Secret) environment.  The only way is to save the TPFDD to a floppy disk or a tape and then "air gap" or "sneaker net" it into the other system.
Specific Procedures.  You must use some of the JOPES software resident on the mainframe to prepare the TPFDD for downloading to your terminal.  When that is complete, you will need to transfer the TPFDD to the hard drive on your PC.  The entire process can be broken down into the following six steps.
TPFDD to DPS 8000 Sequential Permfile.  Use the JOPES S/F B8 to generate a copy of the TPFDD in the JOPES database and store the copy in a file on the mainframe.

DPS 8000 Sequential Permfile to PC Hard Drive.  Use the G-LINK software to transfer a copy of the TPFDD file from the mainframe to the hard drive of your PC workstation.

PC Hard Drive to Disk/Tape.  Use DOS commands to copy the TPFDD from your workstation hard drive to a 3 1/2 inch floppy disk or an 8mm tape.

Sneaker Net.  Hand carry the 3 1/2 inch floppy disk or 8mm tape to a GCCS/JOPES terminal.

Disk/Tape to a GCCS Terminal/Server Hard Drive.  If it is a 3 1/2 inch floppy disk, upload the TPFDD to your user storage area.  If it is an 8mm tape, proceed to the next step.

GCCS Terminal/Server Hard Drive to GCCS JOPES Database.  Use the System Services software to transfer a copy of the TPFDD into the GCCS/JOPES database.

Demonstration.

Requirement.  You have been notified that your OPLAN has been downgraded to Secret and that execution is pending a National Command Authority decision.  You have been directed to upload a copy of the TPFDD into the GCCS/JOPES database.

B8 (Create a JOPS TPFDD).  Subsystem/function B8 (Create JOPS TPFDD) is used to create a copy of your TPFDD in a mainframe disk file or to a 9-track tape.

This screen allows you to copy your OPLAN to either a magnetic tape (9-track) by identifying the tape number or to a permanent disk file by identifying the catalog/file string.  You may identify or change the OPLAN you wish to copy.

If the entries on the two screens do not match, you will receive an error message and Create JOPS TPFDD Tape/File redisplays for reentry of your data.

Next, you can limit the data that you copy.  You can limit data by types of records (e.g., force, nonunit personnel, or nonunit cargo) and by specific force modules that exist in your OPLAN.  If you do not identify any force modules, the system defaults to all.  You will copy the entire OPLAN.

When the job has run to completion, a copy of your OPLAN will reside in the file that you identified.  Now you need to transfer a copy to your workstation hard drive.
Copy a File to Your Hard Drive.  The starting point for executing a file download is the Timeshare (*) prompt.

Note:  During the following G-LINK file transfer process, several delays will be experienced.  All delays that can take more than 60 seconds are noted on the screen and that amount of time must be allowed before assuming that something is wrong.  The user must allow the noted amount of time for the long delays and at least 60 seconds for each short delay as premature script termination leaves various components of the TS3 network in undefined states.

The top of the screen provides a warning.  If you are in JOPES, you should exit this screen, exit JOPES, and then execute this script from the Timeshare (*) prompt.

The six options immediately below the warning provide the capability to upload or download files in either text or binary format.  If the file to be downloaded is in any WWMCCS standard text format (ASCII, BCD, CARD, etc.), then use the text file option.  If the file is in binary format (previously uploaded using Option B), use the binary Option I.  If the file was uploaded using Option C, then use Option E.

Note:  If Option D is used, then the KERMIT G-LINK script will automatically convert the file to ASCII format prior to the actual transfer.  If the file needs to be maintained as a binary file, then it should be copied first and the copy uploaded to the host.

The last selection on the menu is the Exit this Menu Option.

Note:  The G-LINK script expects all file transfers to be between the full Cat/file string on the host and the C:\XFERS DOS directory on your workstation.  The name of the file transferred to your \XFERS directory will be the same as the file name on the mainframe.

Note:  If a premature script termination occurs, then you should run the LOGON.SCR script to attempt to correct the problem (may require multiple runs).  Once back on the host, if the host KERMIT program is still running, pressing <Alt-B> will often terminate that program and allow you to continue your operations.

A copy of your TPFDD file now resides on the hard drive of your workstation in the XFERS directory.  It can be downloaded to a 3 1/2 inch floppy disk or an 8mm tape, depending on your workstation's capabilities.
Copy Your TPFDD File to a Floppy Disk.  The starting point for copying your TPFDD file to a floppy is the DOS prompt.

Now that you know how to get a copy of your TPFDD to a floppy disk, it is time for you to "sneaker net" (hand carry) it to a GCCS/JOPES terminal for upload.
The procedures for the upload of a TPFDD from a floppy disk to the GCCS JOPES database were taught previously in Lesson 4 of this course.

Summary.  The overall focus of this lesson was on how you may be called on to use the TS3 software to support activities in some type of a crisis.  You should now be familiar with the system TLCF capabilities, how to modify an OPLAN's characteristics to make it accessible by the appropriate users, and how to network it to the backup host.  You also covered how to extract information concerning specific records from the database and display that data in a report on your screen.  In addition, you are able to make a copy of your TPFDD and store it on a floppy disk.