AUTOHERR function—HSM error reporting
BMC AMI Storage Reporting intercepts DFSMShsm log records as they are being written to the DFSMShsm log data sets. As each record is intercepted, it is passed to the SVOS address space and interrogated to determine if it represents a data set error. If it represents an error, it is processed against the AUTOHERR function filter and rule list statements. DFSMShsm processing is not impeded by the Automation function.
AUTOHERR filter and rule list statements can be used to issue events, system commands, HSM commands, SVOS commands, or cause submission of batch job JCL. The events, commands, and JCL can include elements from the error record. Errors can be selected for processing according to return code, reason code, data set size, data set age, and other metrics.
BMC AMI Storage interrogates records that are written to the DFSMShsm log files to recognize errors occurring in HSM. There are two ways in which an error is recognized from these records. The first way is the Functional Statistics Record (FSR). For any data set-level activity taken by HSM, an FSR record is written. This record indicates success or failure of the activity along with information about the data set involved and the activity taken. When an FSR record contains a nonzero return code, it signifies that the activity was not completed successfully and is determined to represent an error. These FSR records are processed against the AUTOHERR FLST/RLST statements and also appear in the BMC AMI Storage HSM Error Summary and Error Detail views. However, for some errors, an FSR is not written by DFSMShsm. Instead, a text message is written. In this situation, BMC AMI Storagewill use the text message to represent the error. These selected text messages are processed against the AUTOHERR FLST/RLST and also appear in the BMC AMI Storage HSM Error Summary and Error Detail views.
An overlap can exist between the AUTOHERR function and the AUTOHMSG function. The AUTOHMSG function can be used to initiate automation based on any text message written by HSM. The text messages do not necessarily indicate an error, but using AUTOHMSG to respond to error messages is a common usage of the function. It is recommended, although not required, that the AUTOHERR function be used to initiate automation on HSM data set level errors. This procedure allows better management of automation activity by using the BMC AMI Storage Error Summary and Error Detail views. BMC recommends that the AUTOHMSG function be used to respond to non-data set-level errors or other types of text messages.
In certain cases some of the metrics available in FLST/RLST cannot be determined by BMC AMI Storage. This problem can be due to the usage of a text message as opposed to an FSR. For example, when a text message is used to represent the error, the jobname of the job incurring the error is not available. In situations where a metric is not available, any filter on the metric in the AUTOHERR FLST/RLST will be ignored. So, for example, if an AUTOHERR RLST INC statement filters on JOBNAME=JOESMITH RC=30, and the jobname is not available, the filter on jobname is ignored and any error with RC=30 will match the INC statement. The fields that can be unavailable are noted in the documentation of each FLST/RLST keyword. The Error Detail view can be used to determine what fields are or are not available for any given error.
For more information, see: