Diagnosis information for the openUTM-LU62 Gateway

The following information is required when diagnosing errors:

• The status of the openUTM-LU62 Gateway. Check this using the Management Console. Select the Check Availability command from the context menu of the openUTM-LU62 Gateway.

  The openUTM-LU62 Gateway and its availability are displayed in a table. If the openUTM-LU62 Gateway is available, you can display detailed information by double-clicking on this item or by using the button Result Details.

  The following information is relevant:

  • LLU-NAME: Alias name of the local LU via which the EIS partner is identified. It consists of

    • the value specified for the EIS partner in the Management Console in the Prefix field on the General tab of the Edit Properties of EIS Partner property sheet

    • another generated name part to ensure that names are unique.

  • atot: The number of parallel connections established between the proxy container and the openUTM-LU62 Gateway.

  • stot: The number of established connections (sessions) between the openUTM-LU62 Gateway and the CICS application.

  The number of control sessions is also output. If the number of control sessions is 0, then a configuration error has occurred. If atot indicates the value 0, then a configuration error has occurred or the proxy container has not been started. If stot indicates the value 0, then a configuration error has occurred or the communication service has not been started or the EIS partner is not running. If stot indicates the value 2, then a configuration error has occurred and the specified mode is not known in VTAM on the z/OS.

• The description of the error situation.

• All available diagnosis files:

  • On Solaris and Linux systems:

    • instance trace files
/opt/lib/utmlu62/PROT/inlog.<lu_name>.<suff>

    • XAP-TP trace files
/opt/lib/utmlu62/PROT/xaplog.<lu_name>.<suff1>.<suff2>

    • log files
/opt/lib/utmlu62/PROT/prot.<lu_name>

  • On Windows systems:

    • instance trace files
<gateway_home>\PROT\inlog.<lu_name>.<suff>

    • XAP-TP trace files
<gateway_home>\PROT\xaplog.<lu_name>.<suff1>.<suff2>

    • log files
<gateway_home>\PROT\prot.<lu_name>.txt

  Here <lu_name> stands for a local LU alias name, <suff>, <suff1> and <suff2> are numerical suffixes and <gateway_home> indicates the directory where the openUTM-LU62 Gateway is installed.

If you restart an openUTM-LU62 Gateway, the following diagnostic files in the subdirectory <gateway_home>/PROT are deleted:

• in.dump.<lu_name>

• xaplog.<lu_name>.*

• xap.dump.<lu_name>.*

• prot.<lu_name>.old

• prot.<lu_name>.*.old

• core.<lu_name>

This means that you must save the diagnostic files before restarting the openUTM-LU62 Gateway.

The files prot.<lu_name> and inlog.<lu_name>.* are saved with the suffix .old. On Windows systems, the file prot.<lu_name> has the additional suffix .txt.