The stage 2 deck is made up of eight groups of jobs:
SYS1.MACLIB. Job 64 renames the dataset to its final name.
IEBCOPY; this one populates
SYS1.TELCMLIB. This is the job that will most likely blow up if any of those datasets are underallocated.
IEBCOPY; it adds the compilers, assembler, and link editor to
SYS1.LINKLIB, and populates the language libraries,
SYS1.PROCLIB. If you've run successfully through this job, then you're basically set, as the last group is not likely to fail.
IEHIOSUPagainst the generated
SYS1.SVCLIB; job 122 creates two error recording datasets; job 123 adds them to the catalog; and job 124 renames the generated datasets from their temporary names to the actual names they'll use during execution of the target MVT system.
The stage 2 jobstream may be run in the same manner as the other jobs.
You'll probably want to copy it from
stage2.jcl first, just to keep things from getting overwritten
when you least expect it. I suggest leaving the P1 initiator running while
you read the deck in; this will result in the jobs being read in one at a
time, then executed before the next one is read in. This process will take
None of these jobs are expected to generate complaints. The
ZEND step isn't executed if the associated job ends with
condition code 0, and is if the condition code is greater than 0 (or 4 for
linkedit jobs). Since the
ZMSG program referenced in that step
doesn't actually exist, it gets an S806 ABEND. This ABEND isn't itself a
problem, but it indicates something else that might be. If you receive one
of these ABENDs, look over the job's output to determine the reason.
Up to table of contents Previous: Running the stage 1 sysgen Next: Final MVT setup
Last updated 12 February 2003