OSI/MHS Management Programming Manual

Event Messages
OSI/MHS Management Programming Manual—424824-001
6-94
24: ZMHS-EVT-FTL-OSI-CONFIG
ZMHS-TKN-REM-SSEL
is the remote OSI SSEL; maximum length is 32 characters.
ZMHS-TKN-REM-PSEL
is the remote OSI PSEL; maximum length is 32 characters.
ZMHS-TKN-ERROR-DATA
has the value ZSPI-VAL-TRUE if the first error information is present, ZSPI-VAL-
FALSE if the first error info is not present.
ZMHS-TKN-FIRST-DEVICE
is the fully qualified device name on which the first error in the current error
situation occurred. It is only present if the token ZMHS-TKN-ERROR-DATA has
the value ZSPI-VAL-TRUE.
ZMHS-TKN-FIRST-CODE
is the first error that occurred on the device named in the token ZMHS-TKN-FIRST-
DEVICE in the current error situation. It is only present if the token ZMHS-TKN-
ERROR-DATA has the value ZSPI-VAL-TRUE.
ZMHS-TKN-FIRST-SUBCODE
further describes ZMHS-TKN-FIRST-ERROR. It is only present if the token
ZMHS-TKN-ERROR-DATA has the value ZSPI-VAL-TRUE.
Cause. This event indicates that the OSI services configuration problem was detected at
start up of an OSI/MHS GROUP. No retry attempts are made and the process stops.
Recovery. Ensure that the device name specified in the message is correctly configured.
Look for an error or mismatch, depending on the API error subcode displayed. Restart
the GROUP object.
If the subcode in the operator message is in the range 103106, check the specified
attribute in the definition of the message transfer agent (MTA) object and the underlying
OSI configuration. If the subcode is in the range 107113, check the configuration and
status of the underlying subsystem and its components. The TAPS refers to the OSI
Application Services (OSI/AS), the TSP to OSI Transport Services (OSI/TS), and the
NSP to the Compaq X.25 Access Method (X25AM) or the Compaq LAN Access
Method (TLAM). The layer 3 and 4 profiles are defined in commands to the OSI/AS.
If the problem is not caused by a mismatch between the OSI/MHS and OSI/AS
addresses or the omission of OSI/AS addresses from the configuration, then check for a
lower-layer connection problem, such as rejected packet-switch network call requests.
To determine whether the problem is at a lower layer, run a trace of the remote transfer
service (RTS) process and examine it using the PTrace utility. Use the statistics
counters of the RTS processes to identify and verify which processes are having the
connection problem.