Diagnostic documents

Besides the trace file, of the openUTM agent, there are other files which may be helpful in the event of an error:

• UPIC-Trace file

• UPIC-Logging file

• SYSLOG file

UPIC-Trace file

The carries system UPIC enables trace information to be generated for all interface calls. You can control this procedure by setting the job variable UPICTRACE. The call Enable_UTM_UPIC interprets the contents of the job variable. If the job variable is set, the parameters ad the user data are logged project-specific in a file up to a size of 128 bytes.

Activating the UPIC trace

The UPIC-Trace is activated as follows:

/SET-JV-LINK LINK-NAME=*UPICTRA,JV-NAME=UPICTRACE

/MODIFY-JV UPICTRACE,VALUE='-S[X] [-R wrap] [-Dprefix]'

Meaning:

-S	Detailed logging of call, the associated arguments and user data up to a maximum length of 128 bytes (mandatory data)
-SX	Additional internal information at the interface to the transport system are logged.
-R wrap	The decimal number specified by wrap defines the maximum size (in bytes) of the temporary trace file. Default value: 128 bytes
-Dprefix	The trace files are created with the following names: prefix.UPICT<tsn> prefix.UPICU<tsn> If prefix is not specified, "##.USR.TMP" is used as prefix.

Deactivating the UPIC trace

The UPIC-Trace is deactivated using the following two commands:

/DELETE-JV UPICTRACE

/MODIFY-JV UPICTRACE,VALUE=''

UPIC logging file

If the openUTM application terminates a conversation normally, an openUTM error message is written to the UPIC logging file. The UPIC logging file is only opened to write the error message (mode append) and then closed again.

SYSLOG file

When an application is started, openUTM creates an application-specific log file SYSLOG. This file logs events which occur during the application runtime in the form of openUTM- messages.