COMMAND DEFINITIONS Policy Item
With this policy item you can define which commands you want to monitor and define a maximum time that a command can be blocked by a job or another command before recovery action takes place.
You can also define an action (KEEP, DUMP or NODUMP) to be taken against this command if it is found to be blocking other commands from executing.
When you select the COMMAND DEFINITIONS policy item the "Hung" Command Definition panel is displayed, as shown in Figure 1.
COMMANDS HELP
------------------------------------------------------------------------------
AOFGENQC "Hung" Command Definition Row 1 to 6 of 20
Command ===> SCROLL===> PAGE
Entry Type : Group PolicyDB Name : USER_PDB
Entry Name : SYSPLEX_GROUP_01 Enterprise Name : USER_ENTERPRISE
Define the commands and its parameter(s) together with the elapsed execution
time (30-999 sec) after that a command is treated as a "hung" command and the
action (KEEP/DUMP/NODUMP) to be taken on the blocker of the command.
If resources are excluded a default specification with Command=* and
Command Parameter(s)=* must exist.
Command Command Parameter(s) Time/EXCL Action
(30-999 s)
* * 30 KEEP
D M=CHP(02) 30 NODUMP
D TRACE 60 NODUMP
D M=CHP(01) EXCL
Fill in the following fields:
- Command
- Specify the name of a z/OS system
command that you want to check whether it is a long-running command (for example, the z/OS command SET).
Note: The MODIFY command (F) cannot be processed by hung-command recovery because it does not enqueue on any system resource. There is no need to automate the MODIFY command.
- Command Parameter(s)
- Specify the parameter (or parameters) of a z/OS command that is to be checked whether it is a long running command (for example, PROG as the parameter of the z/OS command SET).
- Time/EXCL
- Defines the execution time that elapses before a command is treated
as a long-running command. Valid value is 30-999 seconds.
If the command should be excluded from long-running command checking, specify
EXCL. - Action
- Defines the action to be taken (KEEP, DUMP or NODUMP) when the
specified command blocks other commands from executing.
The action specified here will be overridden by the action that is specified in the JOB/ASID DEFINITIONS policy item for the job or ASID that issued the blocking command (often *MASTER* or CONSOLE).
For example, if a TSO user named FRED issued a D TRACE command that hung and blocked other commands from executing, and there is a Hung Command Definition of DISPLAY TRACE,30,NODUMP then, after 30 seconds the following would happen for different Job/ASID Definitions:Job/ASID Definition Result FRED,KEEP FRED's D TRACE command would not be canceled but message ING920I would be issued because specific Job/ASID definitions take precedence over COMMAND DEFINITIONs. – The D TRACE command would be canceled without a dump. *,KEEP The D TRACE command would be canceled without a dump because COMMAND DEFINITIONs take precedence over default Job/ASID definitions.