TRACE To resume operation of the virtual machine, the BEGIN command must
be entered. If theRUN operand is specified, the virtual machine is
not.stopped after each output message.
4. Iftrace output is beinq recorded on a virtual spooled printer, a CLOSE command must be issued to that printer output to be printed on the real printer.
.,... • u 5. Successful branches to the next sequential instruction and
branch-to-self instructions are not-detectedby TRACE.
6.RUN and RORUN can be specified in different TRACE commands with no
conflict as lonq as the functions being traced are different.
7. Instructions that modify or examine the first two bytes of the next
sequential instruction cause erroneous processing forBR&NCH and INSTRUCT tracinq.
8.When tracing on a virtual machine with only one printer, the trace
data is intermixed with other data sent to the virtual printer. To
separate trace information from other data, define another printer
with a lower virtual address than the previously defined printer.For example, on a system with OOE defined as the only printer,
define a second printer asOOB. The regular output goes to OOE and
thetrace output goes to OOB. 9. If the BRANCH, INSTRUCT, or ALL activities are being traced by a virtual machine using a shared system, the user receives a warning
message and the virtual machine is unshared from (given a private
copy of) the named system.Other users of the segment continue to
operate with an unchanged copy of that segment.10. 110 for virtual channel-to-channel adapters, with both
ends connected to the same virtual machine, cannot be traced.11. Use the TRACE command to trace specified virtual machine activity
and to record the results at the terminal, at a virtual printer, or
at both. This command is useful in debugging programs because itallows you to trace only the information that pertains to a
particular problem.
12. Ifyour virtual machine is doing I/O that results in
program-controlled interruptions(PCls), and you are tracing I/O or CSW activity, some of the PCls may not be traced. This situation
arises when the system is extending its free storage area and the
additional demand on available free storage could cause a system
abend.
13. The PA1key on a 3270 display terminal shOUld not be pressed with trace all run active while the display screen indicates status as a subsequent CP command entered from the console may result in interleaved output.
section 5. Format of CP Commands 163
be entered. If the
not.stopped after each output message.
4. If
.,
branch-to-self instructions are not-detected
6.
conflict as lonq as the functions being traced are different.
7. Instructions that modify or examine the first two bytes of the next
sequential instruction cause erroneous processing for
8.
data is intermixed with other data sent to the virtual printer. To
separate trace information from other data, define another printer
with a lower virtual address than the previously defined printer.
define a second printer as
the
message and the virtual machine is unshared from (given a private
copy of) the named system.
operate with an unchanged copy of that segment.
ends connected to the same virtual machine, cannot be traced.
and to record the results at the terminal, at a virtual printer, or
at both. This command is useful in debugging programs because it
particular problem.
12. If
program-controlled interruptions
arises when the system is extending its free storage area and the
additional demand on available free storage could cause a system
abend.
13. The PA1
section 5. Format of CP Commands 163