Run a job with TYPRUN=SCAN on the JOB statement.
This will have the effect of OS scanning your job for JCL errors without
actually executing it. MicroFocus has a different way to scan for errors
- 1) Your job has three steps:
- a) The first executes PROG1 that needs 97K of storage and receives two
parameters: JAN 1997 and 21K.
- b) The second executes PROG2 that takes at the most a minute to execute.
- c) The third executes PROG3 only if the return code from the
1st step is between 70 & 100 inclusively or if the rc from the 2nd step is
greater than 71.
- PROG1 reads a card input and the current generation of
UNI.I.MY.MASTER from tape.
The card file may contain // in the 1st 2 columns.
- PROG1 writes a temporary data set to disk with the same
characteristics as UNI.I.MY.MASTER
except for the 4 buffers required and the density deleted (refer back). Let the system give
it a name. Round up the number of cylinders.
- PROG1 also writes the next generation to UNI.I.MY.MASTER to tape
which extends to two
reels to be mounted in sequence. The density is 800. Retain it for three months. Retain
it also for the next step.
- PROG2 reads 3 files: the temporary data set (refer back), the
previous generation (before the current), and the
generation just created of UNI.I.MY.MASTER starting only from its 2nd volume.
- PROG2 writes a report on special form F222 which should not extend
to more than 12 pages.
- PROG2 also writes a data set DS to be catalogued even if PROG1 fails.
DS needs at least 1000
contiguous cylinders and may span to a second volume to be mounted in parallel.
- PROG3 reads DS and writes another generation to UNI.I.MY.MASTER to
a 3380 disk file to be
put on the same volume as some catalogued file UNI.I.CAT.FILE.
Don't forget comments and a system flowchart...
To return to Dr. Caftori's
or to send her note