5. Maintenance › 5.6 Consolidated Unit Generation (UNITGEN) › 5.6.2 UNITGEN Checklist

5.6.2 UNITGEN Checklist

The instructions in the following checklist guide your usage
of the UNITGEN process for regenerating unit-level
parameters, JCL, and SAS macros.

__  1. Review/Modify UNITGEN Options

        Review sharedprefix.MICS.PARMS(UNITGEN) for the
        options in effect.

        +---------------------------------------------------+
        |  Reference(s):  Section 5.6.1                     |
        +---------------------------------------------------+

__  2. Execute UNITGEN

       Submit the following job:

         'prefix.MICS.CNTL(UNITGEN)'

       Ensure that there are no error messages in MICSLOG or
       SYSTSPRT and that the MICSLOG contains the normal
       termination messages, BAS10999I or BAS11999I.

       If the UNITGEN NOAUTOSUBMIT, or UNITGEN AUTOSUBMIT and
       NOOPJCL parameters have been specified, UNITGEN will
       complete with a normal return code of 4.  Otherwise,
       UNITGEN and UNITGEN1 should complete with a return
       code of 0.

__  3. (CONDITIONAL) Execute UNITGEN1

       Perform this step only if your installation has
       specified

       UNITGEN NOAUTOSUBMIT

       You must manually submit the UNITGEN1 job to perform
       the required JCL and parameter generations.

       After the UNITGEN job from the previous step
       completes successfully, submit the following job:

         'prefix.MICS.CNTL(UNITGEN1)'

__  4. Verify UNITGEN1 Results

       Verify that the UNITGEN1 job executed successfully.

       The UNITGEN1 job contains multiple steps that perform
       COPYLIBU, CYCLEGEN, JCLGEN, cccPGEN, and GDGSGEN
       processing or part of it.

       Ensure that there are no error messages in MICSLOG or
       SYSTSPRT and that the MICSLOG contains the normal
       termination messages, BAS10999I or BAS11999I.

       All steps should complete with a return code of zero.

       If errors are encountered during UNITGEN1 job
       execution, correct the errors and rerun UNITGEN and
       UNITGEN1 jobs respectively.

       +--------------------------------------------------+
       |  Reference(s):  Sections 5.6 and 5.6.1           |
       +--------------------------------------------------+

__  5. (OPTIONAL) Execute JCLGEND

       Perform this step only if your installation has
       specified

       UNITGEN NOOPJCL

       If NOOPJCL is specified, UNITGEN1 did not generate the
       CA MICS operational jobs.

       To generate these jobs, submit the following job:

         'prefix.MICS.CNTL(JCLGEND)'

       Ensure that there are no error messages in MICSLOG or
       SYSTSPRT and that the MICSLOG contains the normal
       termination messages, BAS10999I or BAS11999I.

       All steps should complete with a return code of zero.

       +---------------------------------------------------+
       |  Reference(s):  Section 5.6.1                     |
       +---------------------------------------------------+

__  6. (OPTIONAL) Update the CA MICS Jobs

       If JCLGEND was executed, then all the CA MICS
       operational jobs have changed for this unit.  If a
       tailored UNITGEN requested by a composite UNITGEN
       checklist was executed, then some of the operational
       jobs may have changed.  This includes the following
       jobs in prefix.MICS.CNTL:

       AUDIT     BACKUP    BACKUPM   DAILY     DAILYRPT
       DAYSMFR   EXCFULL   HISTM     HISTW     INCRccc
       MONTHLY   MONTHRPT  RESTORE   SCHEDULE  WEEKLY
       WEEKRPT   YEARACT   YEARLY

       If your site has implemented the operational CA MICS
       processes in a scheduling product, the jobs may have
       to be refreshed in that product.  See the scheduling
       product's administrator for the exact processes
       involved in updating that product's representation of
       the CA MICS jobs.

__  7. (OPTIONAL) Update the CA MICS PROCs

       Depending on the JCLDEF parameters, the following
       CA MICS PROCs may have changed:

       MICSSHRx  MICSDBx  MICSNDBx  MICSDUx

       where x is the CA MICS database unit id.

       If you maintain PROCs in a production PROCLIB, copy
       the regenerated procedures listed above to your
       production PROCLIB.