OSI/MHS Management Programming Manual

Event Messages
OSI/MHS Management Programming Manual—424824-001
6-91
23: ZMHS-EVT-BAD-OSI-RESOURCE
ZMHS-TKN-X25-DATA
has the value ZSPI-VAL-TRUE if the X25 error information is present, ZSPI-VAL-
FALSE if the X25 error information is not present. It is only true if the lower comm
level is provided by X25AM.
ZMHS-TKN-X25-DISC-REASON1 ... 4
are only present if ZMHS-TKN-X25-DATA has a value of ZSPI-VAL-TRUE. They
are the reasons for the circuit disconnection as returned by APS_STATUS in the
structure ZAPS-DDL-LL-BUFFER. For further details see the OSI/AS
Programming Manual.
ZMHS-TKN-X25-CLEAR-CAUSE
is only present if ZMHS-TKN-X25-DATA has a value of ZSPI-VAL-TRUE. It
specifies the clear cause. For further details see the OSI/AS Programming Manual.
ZMHS-TKN-X25-DIAG-CODE
The ZMHS-TKN-DIAG-CODE token is only present if ZMHS-TKN-X25-DATA has a
value of ZSPI-VAL-TRUE. It specifies the diagnostic code. For further details see the
OSI/AS Programming Manual.
Cause. A resource problem exists for the named device or for the OSI stack as a whole;
also, an OSI resource problem has started or stopped. The OSI/MHS might continue to
attempt to use the device until the resource is available.
Recovery. Inspect the configuration of the OSI stack for errors specified in the error
codes, then change the configuration to correct the error. Look for an error or
mismatch, depending on the API error subcode displayed.
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 the OSI Transport Services (OSI/TS), and
the NSP to the Compaq X.25 Access Method (X25AM) or 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.
Considerations
OSI/MHS RTS or ROS processes can issue this event message.
This event message is reported to the primary collector.