utodebug server-name

Requests to activate a debugger-interlocked UAP and identifies the window used to execute the utodebug command as an I/O interface with the debugger.

When executing the utodebug command, add $DCDIR/bin, /usr/bin, and /bin to the search path name when specifying the prcsvpath operand for the process service definition or the prcpath command.

Execute the utodebug command in a window on the machine where the OpenTP1 system is operating. One window allows to test one UAP interlocked with the debugger. The other commands are unexecutable in this window until the debugger terminates.

The command fails if neither target nor simmhp is specified for the test_mode operand in the user service definition on the specified server. The command also fails if the specified server is already active.

The utodebug command is available only when the tester service is active.

• server-name ~<identifier of 1-8 characters>
  Specify the name of the server corresponding to the UAP to be tested by interlocking the debugger.
  

• When the debugger-interlocked UAP terminates normally or abnormally, be sure to terminate the debugger.
• If a debugger process is terminated forcibly with the debugger interlocked, the debugger-interlocked UAP process may terminate incompletely, leaving part of the process unprocessed. Terminate the remaining process using the command.
• If the utodebug command is terminated forcibly while the debugger is interlocked, I/O operations for the debugger process coexist with I/O operations for the shell, disabling debugger control. To solve this, forcibly terminate the debugger process and the debugger-interlocked UAP process.
• If the debugger becomes uncontrollable during a test interlocked to the debugger, forcibly terminate the utodebug command process, the debugger process, and the UAP process interlocked to the debugger. If necessary, reexecute the utodebug command. Executing the prcls command shows the ID of the UAP process interlocked to the debugger process.