The traces of the openUTM-LU62 Gateway are written in binary format.
You can convert and display all the openUTM-LU62 Gateway traces and log files in the Management Console:
Choose the following nodes in the navigation tree of the proxy:
Advanced Features - Diagnosis - Output - General Diagnostic InfoSelect one of the following entries:
LU62 Gateway Instance Traces
LU62 Gateway Instance Protocol Flow
LU62 Gateway XAP-TP Traces
LU62 Gateway Protocol Files
Click the Show File button.
The Management Console transfers the converted text file to the local diagnostic path and displays the file in a Text File panel.
Two files result from the conversion of a binary instance trace:
generated instance trace
instance log flow
In addition to the trace files the openUTM-LU62 Gateway writes messages into log files:
On Solaris and Linux systems:
/opt/lib/utmlu62/PROT/prot.<lu_name>
On Windows systems:
<gateway_home>\PROT\prot.<lu_name>.txt
Here <lu_name>
stands for a local LU alias name and <gateway_home>
indicates the directory where the openUTM-LU62 Gateway is installed.
The names of the log files and the generated traces in the local diagnostic path are as follows:
instance traces:
inlog.*.txt
instance protocol flow:
inlog.*.flow.txt
XAP-TP traces:
xaplog.*.txt
log files:
prot.*.txt
Instance protocol flow
In the instance protocol flow files you will find an abbreviated description of the protocol flow (LU6.2 and OSI-TP protocol).
The openUTM-LU62 Gateway uses the APPC interface for communication via the LU6.2 protocol and the XAP-TP interface for communication via the OSI-TP protocol.
On the side of the LU6.2 protocol, the following information is displayed in the protocol flow for every message:
name of the APPC call
TP-ID which is assigned by the SNAP-IX or the IBM Communications Server
direction of processing
additional parameters
The direction of processing is indicated by an arrow. An arrow pointing to the left indicates a message sent by the openUTM-LU62 Gateway and an arrow pointing to the right indicates a message received by the openUTM-LU62 Gateway.
The administration data is exchanged between the openUTM-LU62 Gateway and the LU6.2 partner while the openUTM-LU62 Gateway is starting up or if a connection error occurs. The transaction code X'06F2' is used for this purpose. These protocol flows are indicated by a single arrow (->). A protocol flow of an application program is indicated by a double arrow (==>).
Each message contains a correlation number in order to make it easier to associate an LU6.2 conversation and a parallel connection via XAP-TP. Protocol flows that are not associated with a conversation are assigned the correlation number zero.
Additionally, every message is output with the time and the corresponding line number in the original output file. The protocol flow does not contain user data. This user data can only be found in the original output file.