Post on 19-Aug-2020
transcript
Day 5 (Programming Exercises Continued)
Create a PDS on TESTA
Create PDSes on TSTA similar to those created on SYSA/SYSB on the previous day. Alter the names slightly for ease of copying between
LPARs (e.g., MTA2.PANJOBS.TSTA to MTA2.LOAD.TSTA). This test also gauges whether the system will accept the establishment of a liked
named PDS member in another supersession. The process is similar than the one describe in section 2.
1) In the Supersession Main Menu select TSTA supersession by typing “S” in the line to left of TSOTSTA. Use to scroll down if
necessary. Press .
2) Once in TEST A Primary Option Menu. Type + to get back to the Supersession Main Menu.
3) From the Supersession Main Menu, type “S” next to TSOSYSA. Press .
4) Press again and type “ISPF” below the READY script, as explained in earlier sessions. Press .
5) From the Primary Option Menu in SYSA type “3.4”. Press .
6) You should have reached the Data Set List Utility screen. Move the cursor down to the DSName Level and type “prod.proclib” (no
quotes). Press .
7) Move cursor down to PROD.PROCLIB and type “b” on the space to the left. Press . Make note of the “SYS704” in the right hand
column. That is the volser number you’ll need to enter later .
Type “l FMTCOMP” (or another recent job). Press .
8) Once you confirm FMTCOMP (or target job) press twice to go back to the Primary Options Menu.
9) Once in the Primary Options Menu, hit + to jump to your other active session, TSTA.
10) Go to the Primary Options Menu in TSTA (if not there already) and type “3.3”. Press .
11) You should have arrived at the Move Copy Utility Page. This is where you type where you’re coping from: type “c” in Option; and in
Name type ‘prod.proclib(job name)’ (make sure it’s single quoted); finally, in Volume Serial type “SYS704”. Press
Listcat Sweep’s Input File Naming
Convention
Reformat List via Eagle88
Anything Matching in Table—And
“Below the line”—is Valid For Processing
Submit Dynamic JCL to Internal Reader
Create Dynamic JCL
If Nothing Matching from Table—And/Or “Above the Line”—
No Processing
Compare Reformatted List to Sweep Table
Entry
fig. 1: “Default” Sweep Process Flow
FMCSWBAL Processes Latest GDG for a Group of BAI Files by G00V00 Number. Each GDG Grouping of Files Given FMC
Job number in ’01 Header.
Each BAI File Within Each GDG Grouping
Separates—and Forms Unique DSN, Based on
FMC Job.
FMC Name Looked Up in
Table.
Grand Trailer Record Checked for
Integrity.
If FMC job NOT in Table, it is Entered by
Programmer; also, BAL APP team gets
Automated Error Message.
Grand Trailer Record Checked for
Integrity.
Job FMCFBAL Submitted.
If FMC Job IN Table, Job FMCFBAL
Submitted.
fig. 2: FMCSWBAL Process Flow
To add another dimension to this explanation of how FMCSWBAL works, the screen shots on the following page illustrate how its JCL is
built:
Day 7 (Core Processes Continued)
1.1 PGP Flows
PGP flows function as a means to encrypt or decrypt a file.1 There are two kinds of these processes
which represent the direction of the file to be sent: inbound or PGPIN; and outbound or PGPOUT. In the
simplest terms, the table directly below explains the process both ways. One will notice that the
outbound side carries an additional step: the “F” job, which FTPs the job out via the PGPOUT table.
High Level Review of PGP Flows
Inbound U – Decrypt ↓ G – Application generates job
Outbound G – Application generates job ↓ U — Encrypt ↓ F – Send file to client via PGPOUT Table
fig. 6: High Level Review of PGP Flows
Additionally, there is sometimes a “D” job in play which takes the “U” and “G” job and bundles them
into one job. TRAN Monitoring prefers this more elegant presentation. This also makes PGP sweeps
quicker for clients.2
When PGP files fail to send they most often contain a wrong encryption key.
1.1.1 PGP Load Jobs
PGP load jobs are ones in which a client requests to retrieve an encrypted file. These are
non-production jobs. As a rule, no outside client has access to the UNIX servers. We
must therefore “put” (also called “push”) or “get” the file to and from the client in
decrypted or form respectively. Specifically, TRAN Setup GENERs the application file to
the PGP outbound sweep area for pick-up.
A model for PGP Load can be found at NTSFMC.MODELS (PGPLOAD).3
1 The acronym stands for Pretty Good Privacy but the simple term PGP is almost always used. 2 For a synopsis of this “D” job see Notebook (Day 4). Also see Binder (Day 3) where he provides examples of these bundled PGP sweeps (he calls them “Immediate sweeps”).
Running a Test Sweep (PGPIN/PGPOUT): Steps 1-4
Step 1 Step 2
Step 3: Step 4
On the ISPF Primary Option
Menu enter “2” for Edit.
Within the Edit Entry Panel on the name line enter ‘PROD.SRRJOBS(FMCTESTB)’. This will
create member FMCTESTB under the
PROD.SRRJOBS library.
Copy ‘NTSFMC.TESTJOBS(FMCTESTB)’ To PROD.SRRJOBS(FMCTESTB) by issuing the Copy
command and indicating member to copy.
Go to TVIEW by entering “m” within the ISPF Primary Option Menu and hitting the F1 key
which will take you to Supersession.
fig. 3: Running a Test Sweep (PGPIN/PGPOUT), Steps 1-4
Step 5
Step 6
Step 7
Step 8
Enter “T” in front of your current session for a takedown.Then
hit ENTER.
Tab down until you find TVIEW and then enter “S” to activate your TVIEW session. Then hit ENTER.
Type at Bottom “mvs s srr,job=FMCTESTB” and
hit Enter key.
Go to n.sd by entering “n.sd” on the Option line within the
ISPF Primary Option Menu.
Running a Test Sweep (PGPIN/PGPOUT): Steps 5-8
fig. 4: Running a Test Sweep (PGPIN/PGPOUT), Steps 5-8
Step 8A: Resulting Screen
Step 9:
Step 10 Step 11
Enter “PRE FMCTESTB” on the Command Input line and
hit the Enter key.
Enter “ST” on the Command Input line and hit the Enter key.
FMCTESTB J009657 12082012 1652 12082012
1652
Register the complete output below; copy screen shot, and file document in spreadsheet
(See Larry Walter).
Running a Test Sweep (PGPIN/PGPOUT): Steps 8A-11
fig. 5: Running a Test Sweep (PGPIN/PGPOUT), Steps 8A-11