10. MODIFICATION › 10.1 Parameter Modification › 10.1.7 Change the Number of Work Files for DAYnnn
10.1.7 Change the Number of Work Files for DAYnnn
NOTE: nnn is 090 for VCA component
or 095 for HSM component
ccc is VCA or HSM component
Follow the checklist below to change the number of work files
used in the CA MICS Space Analyzer or its HSM component:
****************************************************
* *
* CHECKLIST 1 - CHANGE NUMBER OF WORK FILES *
* *
****************************************************
___ 1. Update the WORK statement in
prefix.MICS.PARMS(cccOPS) to specify the number of
work file pairs required.
+----------------------------------------------------+
| Reference 7.3.1 for VCA Processing options (VCAOPS)|
| 7.3.2 for HSM Processing options (HSMOPS)|
+----------------------------------------------------+
Below is an example:
WORK n XXX pppp ssss
where: n (0-9) is the number of SAS WORK data sets
XXX is TRK or CYL
pppp is the primary allocation
ssss is the secondary allocation
examples: 1) WORK 6 TRK 800 100
2) WORK 4 CYL 100 20
In example 1, 6 SAS WORK data sets are specified,
each with 800 tracks primary and 100 tracks
secondary allocation.
In example 2, 4 SAS WORK data sets are specified,
each with 100 cylinders primary and 20 cylinders
secondary allocation.
You should specify the minimum number of WORK
data sets to meet your work space requirements.
As a start, try specifying 2 or 3 work data sets.
___ 2. If this is the first time you are implementing
multiple work files in CA MICS Space Analyzer or its
HSM component, 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) 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 SAS 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 the desired VCA or HSM component.
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. Edit prefix.MICS.PARMS(JCLGENU) so that it contains a
single line that reads:
DAILY
___ 5. 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.
___ 6. The following operational jobs have changed:
DAILY
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.