Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

Other diagnostic aids

&pagelevel(3)&pagelevel

In addition to VMDUMP, VM2000 also offers internal trace functions.


Trace functions of VM2000

VM2000 offers the following internal trace functions in the monitor system:

  • The execution trace for runtime logging

  • The error trace for error logging

  • $VMCONS trace for runtime logging in $VMCONS

The trace functions are called by VM2000 at specific execution points to log a run or a detected error.

VM2000 writes trace entries into separate buffers, the execution trace buffer, the error trace buffer and the $VMCONS trace buffer. The contents of these buffers are output by means of the utility routine VMDUMP.


Control of the trace functions

TRACE-LEVEL=*OFF is set after VM2000 READY. The scope of trace logging can be defined with /MODIFY-VM-ATTRIBUTES TRACE-LEVEL=*OFF/*STD/*MAXIMUM.

When *OFF is specified, only system errors such as inconsistent table states or undefined return codes after VM2000 hypervisor calls are logged in the execution and error trace buffers.

When *STD is specified, important execution points in the execution trace buffer are also logged.

Specifying *MAX causes even more execution points in the execution trace buffer to be logged.


The following BS2000 diagnostic aids are also available for use in the monitor system:

  • CONSLOG file (also contains the VM2000 commands and messages)

  • REPLOG file (also contains the VM2000 REP corrections)