The error processing routine has been called to perform the action indicated in the message. The module calling the error processing routine is modname. If modname is UNKNOWN, the module that has issued this error could not be determined accurately. The error code being trapped is errcode.
The message is issued when an error occurs that has either occurred before or for which there is an entry in the trap table as a result of a prior TRAP command for that exact condition.
If errcode is a number from 400–499, a second message appears with the same error condition but a different module name. This error represents an internal error in a module-to-module path. Search problem reporting databases for a fix for the problem. If no fix exists, contact the IBM® Support Center.
If the modname is ARCZWRIT and the errcode is 8, the message indicates that a record with a duplicate key already existed when DFSMShsm tried to write the record. This condition is an error.
More information about modules and error codes can be found in z/OS DFSMShsm Diagnosis, in Appendix A, in the topic "Diagnosing from Return Codes and Reason Codes", in Figure 5, "Entries that Pass Error Codes to ARCERP."
The system issues this message as a result of an error occurring in one of the DFSMShsm processes. ARCERP determines what error action is taken in response to that error. The user can change the designed action by issuing a TRAP command. For information concerning the TRAP command, see z/OS DFSMShsm Diagnosis.
A log entry of the error is written to the DFSMShsm log and message ARC0900I is issued to the operator.
The DFSMShsm task that had the error is abnormally ended (abended) with a dump request.
A log entry of the error is written to the DFSMShsm log and message ARC0900I is issued to the operator.
DFSMShsm is shut down immediately.
The number specified by MAXLIMIT has been exceeded for this day.
The DFSMShsm task that had the error has been abended with a dump request.
A log entry of the error is written to the DFSMShsm log and message ARC0900I is issued to the operator.
DFSMShsm is shut down immediately.
NODUMP ONCE is an internally set error trap that requires the current task to abend (if this is the first occurrence of the error), but does not process a dump of the abend. ABEND ONCE will process a dump.
The DFSMShsm task that had the error is abended if this is the first occurrence of the condition. If this is not the first occurrence of the condition, the count of this abend condition is incremented by 1.
A log entry of the error is written to the DFSMShsm log and message ARC0900I is issued to the operator.
No action is taken, but the table entry containing the number of times this error has occurred is incremented by 1.
A log entry of the error is written to the DFSMShsm log.
A SNAP dump of the DFSMShsm address space is taken and the count of the error condition is incremented by 1.
A log entry of the error is written to the DFSMShsm log and message ARC0900I is issued to the operator.
The DFSMShsm task that had the error is snapped if this is the first occurrence of the condition. Otherwise, no system action is taken, but the count of this error condition is incremented by 1.
A log entry of the error is written to the DFSMShsm log and message ARC0900I is issued to the operator.
The DFSMShsm task that had the error is abended. The count of this error condition is incremented by 1.
A log entry of the error is written to the DFSMShsm log and message ARC0900I is issued to the operator.
A log entry of the error is written to the DFSMShsm log.
If FATAL ONCE or nnn MAXLIMIT is the DFSMShsm action, restart DFSMShsm. Otherwise, no action is necessary.
If you want DFSMShsm to stop issuing this message, issue the TRAP command with the OFF parameter.
DFSMShsm