The DFSMShsm primary address space has issued an MVS™ CANCEL command to cancel a secondary address space. The time allotted for an address space to start has been exceeded, the ABARS control task has abnormally ended (abended) when secondary address spaces are active, or a recursive abend has occurred in the ABARS subtasks when the secondary address spaces are active.
"C ABARnntt,A=asid"
where:The aggregate backup or aggregate recovery function is held if the CANCEL is a result of a secondary address space not starting within an allotted time interval. This is dependent upon which command has been processing. In this case the command that has been processing will not be purged from DFSMShsm’s work queue. If the cancel is issued as a result of an abnormal end, the affected function is not held, but the command being processed will be purged from DFSMShsm’s work queue. DFSMShsm processing continues.
Ensure that the address space for which the MVS CANCEL command has been issued is cancelled. If the task is still active in the system, issue an MVS FORCE command to cancel the address space.
In the case of a timing failure, verify that the procedure name used by DFSMShsm to start a secondary address space exists. In this case, the aggregate backup or aggregate recovery command remains on the queue. When the problem is corrected, release the function that has been held. If the message has been issued as a result of a timing problem, verify that the maximum amount of time allowed for an ABARS secondary address space to start is sufficient. (This is verified by using the DFSMShsm DISPLAY command for .ARCABRCB.+494.)
This full word contains the hexadecimal equivalent of 300 (X'12C'), which signifies that 5 minutes are allowed for the ABARS secondary address space to start. This field is patchable by the DFSMShsm PATCH command: PATCH .ABRCB.+494 x‘nnnnnnnn’, where ‘nnnnnnnn’ is the hexadecimal time value in seconds that you are allowing for ABARS’ secondary address spaces to start.
DFSMShsm