Problem Determination

Control‑O is supplied with internal debugging (trace) facilities that provide the ability to print an internal debugging trace and to print the contents of Control‑O internal data areas. Under normal circumstances, the trace facilities are dormant. However, if required (that is, if BMC Customer Support has requested debugging information), you can activate the trace facilities by performing the following steps:

Do one of the following:

1. Start a new Control‑O monitor with the following operator command:

   S CONTROLO,TRACE=level

   The Control‑O monitor passes control to the new Control‑O monitor and shuts down.

2. Issue the following operator command:

   F CONTROLO,TRACE=level

   The required trace level is supplied by BMC Customer Support. It can be any value from 000 to 255 (000 specifies no debugging).

   Note: You should not regularly activate Control‑O with the TRACE parameter, because a JES problem may cause Control‑O to become suspended while waiting for JES.

   Debugging information is printed to files referenced by DD statements DATRACE and DADUMP of the Control‑O procedure.

3. When you finish your problem determination procedures, start a new Control‑O using operator command

   S CONTROLO

   or specify operator command

   F CONTROLO,TRACE=00