Troubleshooting Exit Procedures

Using the DEBUG Facility

To use the DEBUG facility, you must declare the DEBUG intrinsic in your exit procedure:

Intrinsic debug;

Then, at the appropriate points in your procedure you can execute calls to DEBUG.

Note, however, that calls to DEBUG are ignored in batch jobs. You must first run the NRJEMON program from a session. To do this you must replace the stream job that runs NRJEMON with a job that does nothing. For example:

     !Job debugit,manager/pass.sys,nrje;outclass=,1
     !Comment ** Use to debug an exit procedure
     !Tellop ; RUN THE MONITOR FROM YOUR TERMINAL NOW.
     !eoj>

Then, execute a command to start your workstation:

:NRJECONTROL START;WSID=Wsid

The stream job then runs. When the job is done, you should run NRJEMON from a terminal while logged on as MANAGER.SYS,NRJE:

:RUN NRJEMON;INFO=Wsid

You will then be placed in whenever your procedure calls the DEBUG intrinsic. See the MPE Debug/Stack Dump Reference Manual for additional information.

Using the PRINTOP Intrinsic

As an alternative to using DEBUG and setting breakpoints in your procedure, you can use the PRINTOP intrinsic to display variable values. Note that the PRINT intrinsic will be of little use because PRINT writes to $STDLIST only, and the PRINTOP intrinsic writes to the system console. See the MPE Intrinsics Reference Manual for additional information.