If problems are experienced with internal openUTM inter-process communication, a dump of the "IPC shared memories" can be prepared while the application is running and output to stdout. No additional editing program is required in order to do this.
It is also possible, while the application is running, to activate or deactivate the IPC trace; this is done regardless of the value of the start parameter TESTMODE=.
The tool writes all information to stdout.
Calling KDCIPC
KDCIPC is called as follows:
utmpath/ex/kdcipc filebase [T] [D] [,tron/troff] (Unix and Linux systems)
utmpath\ex\kdcipc filebase [T] [D] [,tron/troff] (Windows systems)
filebase T | Base name of the KDCFILE in the MAX statement. This operand causes the buffer of the IPC trace area to be output in chronological order to stdout. In other words, the last record in the list is also the most recently generated. Default: no output of the IPC trace area to stdout. |
D | This operand causes the entire IPC shared memory to be output in edited form to stdout. Default: no output of entire IPC shared memory. |
tron/troff | "tron" activates the IPC trace mode; "troff" deactivates it. Default: the IPC trace mode is activated/deactivated according to the start parameter TESTMODE. |