Examine use of the CMDS ABEND command

Description: Before z/OS V1R13, the CMDS ABEND command ended an executing command if the command was hung. In z/OS V1R12, the command processors were allowed to specify the new non-abendable attribute to set themselves non-abendable. When the new attribute was specified for a target command, the CMDS ABEND command rejected with the following message: CNZ6002I COMMAND command WITH ID id NOT ABENDABLE. The CMDS ABEND attempted to terminate the hung command. Starting in z/OS V1R13, the new parameter FORCE is added to the CMDS command so that a CMDS FORCE specification overrides the non-abendable attribute and the command will be terminated as it is today. Separating the ABEND and FORCE requests allow different RACF profiles to be defined so that installations can allow CMDS ABEND, but not CMDS FORCE. FORCE is intended to be used where the only alternative is to re-IPL the system.

Steps to take: Automation that uses the CMDS ABEND command is affected because the termination of a running command can be rejected. For some commands, this rejection is important because it can prevent a system or sysplex outage. If you use the CMDS ABEND command or have automation that does, certain commands will no longer be terminated by the CMDS ABEND command.
Reference information: