Read-Only variables updating - syncsort_allocation_control_center

The values of the ACS read-only variables for RECORG, DSNTYPE, NVOL, SIZE, and MAXSIZE may be updated as a result of the data class assigned by the ACS routines.

If SETDCVARS(YES) is specified, any of these variables which have values present in the assigned data class, and which were not explicitly specified in the testcase, will be given the data class values.

Thus, if SETDCVARS(YES) is specified, the storage class routine may receive a different value for, say, RECORG, or SIZE / MAXSIZE, than the (null) value that the data class routine did.

If any of the variables are assigned by the data class routine, messages ACC80240 and ACC80241 will indicate this, for example:

ACC80240-I DSORG SET BY DATA CLASS DCTEST TO PS FOR CDS1
ACC80241-I SIZE SET BY DATA CLASS DCTEST TO 500 FOR CDS1
ACC80241-I MAXSIZE SET BY DATA CLASS DCTEST TO 2000 FOR CDS1

For each testcase, the results are shown, with the results for CDS1 on the left and those for CDS2 on the right. The messages from each testcase are shown following the class names and exit codes.

Tip: An asterisk in column one indicates a mismatch in either class names, exit codes, or messages. Message ACC80103 following the testcase output also indicates a mismatch. All exit codes are shown in decimal.

In the example below, the ACS routines for CDS1 indicate successful completion of all four ACS routines (data class, storage class, management class, and storage group) for the testcase member named ALLVARS1.

The names of the constructs assigned are shown, along with the ACS routine exit codes (all zero for CDS1) and the number of messages issued from each routine. In the case of CDS1 below, one message was issued from the storage group routine.

Note: Because the messages may be up to 110 bytes in length, they are displayed below the ACS routine results.

For CDS2 in the example below, the data class routine did not assign a data class (the construct name is null), and ended with exit code decimal 98, along with five messages.

Important: Because of the nonzero exit code returned by the data class ACS routine, the storage class, management class, and storage group routines were not run.

Note the asterisk in the first column of the ACS routine results display. This asterisk indicates a mismatch between either the assigned SMS construct name, exit code, or number of messages for each routine.

Following the display of the constructs/exit codes/message counts and the data class updates is a side-by-side display of the return and reason codes from the ACS installation exits (IGDSMSDC, IGDSMSSC, and IGDSMSMC).

Note: If, as in this case, the ACS exits were not invoked (the EXITS1 and EXITS2 parameters were defaulted or specified as NO), the ACS exit return and reason codes are displayed as zero.

Note that each ACS installation exit can re-invoke its corresponding ACS routine one time. If this occurs, the construct names shown in the results are those assigned after the ACS routine has run the second time.

Following the ACS routine results display and the ACS installation exit return and reason codes are the messages, if any, from the ACS routines. For each ACS routine, the CDS1 messages are displayed first, followed by the CDS2 messages, again for easy comparison.

Note: As with the ACS routine results display, an asterisk in column one indicates a mismatch between the messages issued by the ACS routine for CDS1 vs. that for CDS2. If an ACS routine for one CDS issued a message while the same ACS routine for the other CDS did not, an asterisk on an otherwise blank line indicates this.

In the example below, the data class routine for CDS2 issues 5 messages (in a sort of 'message box') while the data class routine for CDS1 did not issue any messages. Similarly, the storage group routine for CDS1 issued one message while the same routine for CDS2 did not.

Read-Only variables updating - syncsort_allocation_control_center - Latest

Syncsort™ Storage Management Sms/Debug User Guide