HSM OPTIONS Statement
The OPTIONS statement is optional; if coded, both operands must be coded.
rm
OPTIONS sysid default_duration
The OPTIONS statement is optional; if coded, both operands must be coded.
Valid values for sysid are 4-character SMF SYSIDs of HSM systems at your site or an asterisk (*). The value of sysid must match an SMF SYSID coded in prefix.MICS.PARMS(SYSID).
Valid values for default_duration are integers from 1 to 999, representing hours. This value is used for the very first inventory of DFHSM resources performed by VCC. After this first data collection, all records produced for HSM by VCC will contain the "current" data collection time and the previous data collection time. Hence, the actual DURATION is computed by
MICS
and this default duration will be ignored. Since HSM data collection is usually once per day, this parameter is less important in HSMOPS than its corresponding usage in VCAOPS. In VCA, the default duration will be used when a new VOLSER is placed into service and there has never been a previous scan time for that volume.The default is "OPTIONS * 24" where * means any SYSID and 24 is the duration in hours. While the default choice is highly recommended, managing multiple data centers and MVS images requires flexibility so the following discussion elaborates on syntactical details.
If your site restricts the data coming into VCA or if the duration between VCC runs is not a constant, code individual OPTIONS statements for each SMF SYSID. OPTIONS statements must be grouped together.
The examples below illustrate valid and invalid VCAOPS coding:
Valid Example: | Invalid Example: |
ACCOUNTING DETAIL | OPTIONS TST1 24 |
OPTIONS SYS1 12 | ACCOUNTING DETAIL |
OPTIONS TST1 24 | * COMMENT IS OK HERE |
OPTIONS REMT 12 | OPTIONS REMT 12 |
The example on the right causes improper code to be generated during the HSMPGEN process and unpredictable results during DAILY processing because the OPTIONS statements are not adjacent to each other.