5. Maintenance › 5.6 Consolidated Unit Generation (UNITGEN)

5.6 Consolidated Unit Generation (UNITGEN)

The optional consolidated unit generation (UNITGEN) process
is designed primarily to reduce the complexities and number
of job executions normally associated with PSP maintenance.
UNITGEN may also be used for administrative and other
maintenance activities.

Generally, the System Modification section of the Product
Change text (PSP.PC.TEXT members) will instruct you to
execute a series of one or more unit-level generation jobs in
order to implement the Product Change.  Often, you will need
to repeat these steps in multiple database units, for
example, if the product is active in multiple units, or for
CA MICS Base Platform (BAS) product changes.

The optional consolidated unit generation process replaces
the multiple unit-level generation job executions with a
single job: UNITGEN.  UNITGEN performs the same functions as
JCLGENB, JCLGENC, JCLGEND, ALLPGEN, COPYLIBU, CYCLEGEN, and
GDGSGEN.

Usually, the UNITGEN process performs all the functions
mentioned above.  If you choose to generate and print a
composite UNITGEN checklist during the online PSP maintenance
process, a tailored UNITGEN is generated that only performs
the functions necessary for the set of selected product
changes and the specific unit. You must complete such a
checklist, in particular the UNITGEN jobs, before you can
generate and print another composite UNITGEN checklist.

If a UNITGEN process is performed without a composite UNITGEN
checklist, or after a composite UNITGEN checklist is
completed, it contains all the functions mentioned above.

  o  The UNITGEN process actually consists of two jobs:
     UNITGEN and UNITGEN1.

  o  The UNITGEN job generates the UNITGEN1 job based on the
     products that are installed in the unit and the
     generation processes that are required.  Executing the
     UNITGEN1 job performs the actual processing: JCL
     generation, cccPGEN, and so on.

  o  If you specify the UNITGEN AUTOSUBMIT statement in
     sharedprefix.MICS.PARMS(UNITGEN), then UNITGEN will
     automatically submit the generated UNITGEN1 job for
     execution.  Otherwise, you will need to manually submit
     the UNITGEN1 job for execution after UNITGEN completes
     successfully.

  o  Note that the AUTOSUBMIT YES statement in JCLDEF (or in
     JCLDEFC if this unit accepts complex-level defaults) has
     no effect on the UNITGEN process.

  o  Note also that UNITGEN1 may complete with a CC=8 when
     manually submitted.  The occurrence of the CC=8 is only
     on the first run in a new unit.

The following sections document the UNITGEN processing
options and provide a checklist for UNITGEN usage.

  1 - UNITGEN Processing Options
  2 - UNITGEN Checklist