7. PARAMETERS › 7.3 Unit Level Parameters › 7.3.1 DB2 Processing Options (DB2OPS) › 7.3.1.1 WORK, MULTWORK, and NOMULT Statements › 7.3.1.1.1 Change the Number of WORK Files

7.3.1.1.1 Change the Number of WORK Files

To change the number of work files used in the CA MICS DB2
Analyzer processing in DAY065, follow the checklist provided
below for each unit:

   ****************************************************
   *                                                  *
   *           CHANGE NUMBER OF WORK FILES            *
   *                                                  *
   ****************************************************

___ 1.  Update the WORK statement in
        prefix.MICS.PARMS(cccOPS), where (ccc) is the
        component identifier, to specify the number of work
        data sets required.  Below is an example:

        WORK n STORCLAS=MICSTEMP SPACE=(XXX,(pppp,ssss))

        where:

        n        - is the number of WORK data sets.
        STORCLAS - specifies a storage class for a new data
                   set.  The name can have up to eight
                   characters.
        SPACE    - specifies how much disk space to provide
                   for a new data set being allocated.
        XXX      - is TRK or CYL.
        pppp     - is the primary allocation.
        ssss     - is the secondary allocation.

        You should specify the minimum number of WORK data
        sets to meet your work space requirements.  As a
        start, try incrementing the number gradually
        beginning from the default.

___ 2.  If this is the first time you are implementing
        multiple work files for this product, then continue
        with Step 2.  If you are just changing the number
        currently in use, or simply the space definitions,
        then proceed to Step 3 of this checklist.

        Browse sharedprefix.MICS.PROTOLIB(DYcccnnn) and
        sharedprefix.MICS.PROTOLIB(cccINCR), where (nnn) is
        the job step number and (ccc) is the product ID for
        this product, checking for the presence of the WORK
        symbolic on the EXEC statement to determine if you
        have previously modified this product to increase the
        allocation of SAS WORK space.

___ 2a. If you find a WORK symbolic, simply divide the
        primary and secondary allocation values from the WORK
        symbolic by the number of work files specified above
        (value of n on the WORK statement coded in Step 1).

        Coding the resulting values will yield the same
        aggregate space allocation you have been using with a
        single WORK file.  To double your available WORK
        space, carry out the division, double the results and
        use the values in the WORK definition above.

___ 2b. If you did not find a WORK symbolic in PROTOLIB,
        examine prefix.MICS.PARMS(JCLDEF) for each CA MICS
        unit containing this product.  Find the WORKSPACE
        keyword.  The space allocation specified is used for
        a single SAS WORK file.  Perform the same division as
        described in the previous paragraph to determine the
        quantity that will yield equivalent total allocation
        with multiple WORK files.  Then adjust the values
        upward to meet your needs.

___ 3.  Submit the job in prefix.MICS.CNTL(cccPGEN).

___ 4.  If you specified RESTART YES in the product's cccOPS,
        you are done.  Otherwise, you must do Steps 5, 6, and
        7.

___ 5.  Edit prefix.MICS.PARMS(JCLGENU) so that it contains a
        single line that reads:

        DAILY

        or, if incremental update is enabled for this product
        in this unit database, specify:

        DAILY INCRccc

        where ccc is the product ID.

___ 6.  Submit the job in prefix.MICS.CNTL(JCLGENU).  Ensure
        that there are no error messages in MICSLOG or
        SYSTSPRT, that the MICSLOG contains the normal
        termination message, BAS10999I, and that the job
        completes with a condition code of zero.

___ 7.  The following operational job(s) have changed:

        DAILY

        INCRccc (if incremental update is enabled)

        If your site has implemented the operational CA MICS
        processes in a scheduling product, the JCL 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.