DEBUG command

The command syntax is provided in the following diagram.

Note: You can specify only one option at a time. To enable multiple debug options, issue the DEBUG command multiple times. The DEBUG command can be run from the operator console or from the parmlib.

Debug

Read syntax diagramSkip visual syntax diagramAllNoneMAINNOMAINANALYTICSNOANALYTICSBUFFERNOBUFFERBUFLOCKNOBUFLOCKIONOIOCPOOLNOCPOOLRPHNORPHRACF(ALLNONEAUTHFASTAUTHVERIFY)NORACFCKRCARLAPARAMETER(' parameter;')
The keywords and variables have the following values:
All
Write all diagnostic messages to the console. ALL is the default setting for displaying messages if you do not specify a parameter on the DEBUG commands. Most of these messages are intended to assist during problem determination, and are not intended for routine customer use. The messages resulting from a DEBUG BUFFER command can be used routinely to determine the minimum size needed for the data buffers.
None
Deactivates creation of all diagnostic messages.
MAIN
Write diagnostic messages related to mainline processing to the console. This includes responding to operator commands, initialization and management of all subtasks, and major buffer management functions.
NOMAIN
Do not write diagnostic messages related to mainline processing to the console. This setting suppresses the following types of messages:
  • Responses to operator commands
  • Initialization and management of all subtasks
  • Major buffer management functions.
ANALYTICS
Write diagnostic messages related to analytics file processing to the console.
NOANALYTICS
Do not write diagnostic messages related to analytics file processing to the console.
BUFFER
Write buffer usage statistics to the console (and to joblog and syslog) at the end of each reporting interval. These messages can help determine the number of Access Monitor records captured, and the amount of storage required. You can use these messages to track the minimum and maximum amount of buffer storage needed.
NOBUFFER
Do not write buffer usage statistics to the console.
BUFLOCK
This debug option is intended to assist in diagnosing the reason that a task could not save a record in the C2PACMON buffers. If such a situation occurs, an SVC dump is created of the address space where the event occurred. The BUFLOCK option is automatically disabled until the DEBUG command is issued again, either through an operator command or from PARMLIB.
Note that the SVC dump is not an indication that any error occurred. The dump is created only to assist in determining why the task could not save the record.
NOBUFLOCK
The BUFLOCK debug option is not used.
IO
Trace all operations processed by the Access Monitor interface routine to CKRCARLA using SYSLOG. Using this parameter might result in large numbers of writer-to-operator (WTO) messages. This function is intended to help IBM® Software Support personnel diagnose internal problems in the product.
NOIO
Do not generate I/O diagnostic messages.
CPOOL
Show the number of cell pool extents at the end of each reporting interval. The messages that this generates helps to determine the number of concurrent users of these cell pools. Activate this debug option only on request of zSecure support.
NOCPOOL
Do not show the number cell pool extents.
RPH
Show diagnostic messages about use and management of the resolved path cache.
NORPH
Do not show diagnostic messages about use and management of the resolved path cache.
RACF®
Specifies the RACF events for which diagnostic information about the collected data is shown on the system operator console. The subkeyword specifies the type of event. If no event is specified, diagnostic information for all events types is shown. This function is intended to help IBM Software Support personnel diagnose internal problems in the product.
NORACF
Messages for events related to the RACF data collection process are not issued. This function is intended to help IBM Software Support personnel diagnose internal problems in the product.
CKRCARLAPARAMETER
Specifies a string that is to be passed to all instances of CKRCARLA that are used within the C2PACMON started task. The string as specified must end with a semicolon, and must be enclosed in quotation marks. This parameter is intended for IBM Software Support personnel to diagnose problems. The maximum length of the string is 63 characters.