Publication Date: 16 February 1996
System Version: GCCS 2.1/Update 4
Web Page Created: 26 March 1996
| PRACTICAL EXERCISE - PERMISSIONS SCENARIOS (Appears on page 3-3 in the Training Manual) |
|||
|---|---|---|---|
| Number | Scenario | Problem | Solution |
| 3.1 | An individual assigned to J3 has created a TPFDD in the JOPES Oracle database using the System Services application and has merged force records into it using the Requirements Development and Analysis application. She has also used the Ad Hoc Query application to run and print several reports. However, the External Systems Interface application refuses to start. Where is the trouble? | The trouble could be in one of two places. It is possible that the ESI application is loaded on a machine that the current user does not have access to, i.e., the machine on which the ESI application is loaded is not in the users .rhosts file. The other possibility is that the user does not have access to the application at system level. | Both problems are the SA's to correct. System level access to ESI should be checked first as that is the most likely culprit. If not, then check the .rhosts file. |
| 3.2 | An individual in J2 has completed updating a TPFDD using RDA. With a little extra time on his hands, he has been wandering around in the System Services application just to see what is there. In his travels, he inadvertently turned off the JOPES Transaction Processor. Why was he able to do this? | The ability to start and stop the transaction processor should be limited to the SA and/or the DBA. It is controlled by the use of group membership. | This USERID is a member of the JADMIN group when it should not be. The ISSO must remove the USERID from the JADMIN group. |
| 3.3 | An individual in J4 has been assigned the task of conducting a transportation feasibility assessment of a TPFDD using the JOPES application JFAST. However, JFAST does not access the JOPES Oracle database and he has no way to move the TPFDD to JFAST. What is the trouble? | He does not have access to the Information Management System Icon on his Launch Window. After being granted access, the option of JOPES database to JFAST must be available. | The SA must access the Profile Manager and add this ICON to the user's Launch Window. The FM needs to ensure that the JOPES database to JFAST option is on the IMS application. |
| PRACTICAL EXERCISE - DELETE PERMISSIONS (Appears on page 3-16 in the Training Manual) |
||
|---|---|---|
| Step | Problem | Navigation/Action |
| 3.4 | Delete USERID jd9resxx and all associated functional permissions that you created earlier from JOPES. | Enter the USERID, Delete, Transmit. |
| 3.5 | Review the User Permission Report to ensure the USERID is deleted. | F10-Back, Select User Permission Report on the cascade menu. |
| 3.6 | Return to the Launch Window. | <F12>, Yes. |
| 3.7 | Can a TPFDD in the JOPES database be made available for the DART application? If NO, why not? If YES, will the import be monitored in an xterm window? | Answer: YES, YES, Quit. |
| 3.8 | Is the TUCHA reference file in the JOPES database available to the DART application? If NO, why not? If YES, what date will be displayed in RFM for the TUCHA file? | Answer: YES, The date the TUCHA reference file was copied from the database to RFM, Quit. |
| 3.9 | Exit all applications remaining open and return to only the Launch Window. | Select File and Exit on JNAV Window. |
| PRACTICAL EXERCISE - CREATE A TPFDD FILE (Appears on page 4-43 in the Training Manual) |
||
|---|---|---|
| Step | Problem | Solution |
| 4.1 | Create a TPFDD file containing only Army records from 900XT and save them in a file located in your personal storage area. | Follow the keystrokes and information starting with paragraph IV.A.1 on page n and ending with keystroke step 9 of the Create TPFDD File keystroke table on page n. Only exception to these keystrokes is to change every occurrence of the Service from Marines to Army. |
| 4.2 | After the instructor verifies your efforts to create a TPFDD file, please exit System Services. | <POINT AND CLICK (left)> on F12-Exit then <POINT AND CLICK (left)> on F6-Yes. |
| PRACTICAL EXERCISE (Appears on page 4-82 in the Training Manual) |
||
|---|---|---|
| Step | Problem | Solution |
| 4.3 | Upload the floppy disk file to your user storage area. | From the Session Manager Menu bar, Select Tools > Folder > Options > Import from floppy, Select file name and OK. Select Options > Eject floppy. Select File > Exit. |
| 4.4 | Rename the file to remove the numbers added by the foldering system. | Open an XTerm window, change directory to /h/USERS/{userid}/User_Storage, type ls -al to display the file names, type mv {old file name} {new file name}, type ls -al to verify {new file name}, type exit. |
| PRACTICAL EXERCISE - SSF/PIF CHANGES (Appears on page 5-26 in the Training Manual) |
||||
|---|---|---|---|---|
| Step | Problem | Action | Action | Action |
| Given the situation, determine which flags need to be changed, who can change them, and what subsystem would be used? | What Flag needs to be changed? | Who does the change? | What Menu Option? | |
| 5.1 | Invalidate the Hawk unit. | Remove "T" from Hawk ULN | USTC | USTC Status/Problem Flags Override |
| 5.2 | Validate the A-10 unit. | Add "A" to A-10 ULN | Supported CINC | Supported CINC Validation |
| 5.3 | Pull the A-10 unit. | Add "T" to A-10 ULN | USTC | USTC Requirements Pull or USTC Status/Problem Flags Override |
| PRACTICAL EXERCISE - TCCESI APPLICATION (Appears on page 5-76 in the Training Manual) |
|||
|---|---|---|---|
| Step | Problem | Action/Solution | Accomplished By |
| 5.4 | Delete carrier information | Reports and Utilities | Supported Command or USTRANSCOM |
| 5.5 | Reset Schedule Status and Problem Indictor Flags | USTC Status/Problem Flags Override | USTRANSCOM |
| 5.6 | Delete TCCESI application created files | Reports and Utilities | Supported Command and USTRANSCOM |
| 5.7 | Save OPLAN/TPFDD data to user storage area. | SS - Create a TPFDD or Offload OPLAN option. | Supported Command or USTRANSCOM |
| PRACTICAL EXERCISE - Functional Permissions (Appears on page 9-2 in the Training Manual) |
||
|---|---|---|
| Step | User Requirement | Functional Permission Required |
| 9.1 | Must be able to read data from the database, add records to the database, and print reports. | QRY, UPD, RPT |
| 9.2 | Must be able to retrieve specific records to the screen for review. | QRY |
| 9.3 | Must be able to add a new OPLAN to the database and load data into it. | QRY, UPD, IRM |
| 9.4 | Must be able to extract specific data from OPLANs, print it, and generate graphs from that data. | QRY, RPT, GPH |
| 9.5 | Must be able to update the database, print reports, and grant users functional permissions. | QRY, UPD, RPT, GRT |
| 9.6 | Must be able to execute a batch update to an OPLAN. | QRY, UPD, CAT |
| 9.7 | Which functional permission has no significance? Why? | TCC, OPLAN execution will not occur using this system. |
| PRACTICAL EXERCISE - DELETE FUNCTIONAL PERMISSIONS (Appears on page 9-9 in the Training Manual) |
||
|---|---|---|
| Step | Problem | Solution |
| 9.8 | The reservists have finished their tour with their active duty counterparts. Your requirement is to review and delete the functional permissions of the reservists. | Use HQ on the JOPES MASTER MENU, type "b" in ENTER ONE OPTION, <RETURN>. Type "r" at FUNCTION CODE, "e" at ENTER DATABASE CODE, "jd94fmtngx" at ENTER USERID, <RETURN>. |
| 9.9 | Delete the user permissions from the JOPES database. | Type "d" at FUNCTION CODE, <RETURN>. Type "u" and "j" at Spawn Batch screen, <RETURN>. Press <SPACE>, <RETURN>. |
| PRACTICAL EXERCISE - DELETE FUNCTIONAL PERMISSIONS (Appears on page 9-10 in the Training Manual) |
||
|---|---|---|
| 9.10 | Monitor the spawned job. | Exit JOPES and type "jmon {snumb}" at TSS prompt, <RETURN>. Wait until job is completed. |
| 9.11 | JOUT the job and review the appropriate report code for the deletion of the FILSYS permissions. | Type "jout {snumb}", <RETURN>. At FUNCTION?, type "prin 12", <RETURN>. Use SPACE, TRANSMIT to page through the screens. |
| 9.12 | Release the job from JOUT. | Type "rele" at FUNCTION?, <RETURN>. |