Manualshelf

OSI/MHS Management Programming Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series
481482483484485486487488489490
Event Messages
OSI/MHS Management Programming Manual—424824-001
6-86
22: ZMHS-EVT-BAD-OSI-CONFIG
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. The first form of this message indicates a problem in the interaction between the
OSI/MHS and the OSI/AS. A configuration problem has blocked the OSI/MHS from
using the specified device. The OSI/MHS might continue to attempt to use the device
until the configuration is corrected. The second form of this message indicates that the
problem was solved.
Recovery. Check the configuration for OSI and for the OSI/MHS subsystem. Look for
an error or mismatch, depending on the Application Programmatic Interface (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 generate this event message.
This event message is reported to the primary collector.