OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide

Recovering From Errors
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide—424822-001
6-24
Common GPI Errors
the GPI returns error code 26, OM-RC-WRONG-VALUE-LENGTH. The secondary
code contains the attribute type.
MHS Manager Communication Problem
If GPI_OPEN_ returns an SPI or SCP-related error then the problem concerns
communications between the GPI library and the MHSMGR. The MGSMGR may not
be available, may not be compatible with the GPI release, or the GIP may not be
configured.
Loopback Configuration Errors
If a message is sent and is intended to be returned to the sender as a loopback test
(addressing the message to yourself) and it does not come back, the cause can usually be
traced to one of the following problems:
•
The destination address may not be exactly the same as the APPL configuration.
Messages can be sent out without having a proper APPL configured, but when
receiving messages, each APPL field is critical for correct routing.
•
If the message is of class probe and the gateway was configured with validation on,
then the OSI/MHS system will reply to the probe instead of delivering it to the GPI.
•
There is a slight time delay between transfer out and the point in time when the
looped back message can be accessed. This is due to the processing that the message
goes through in the GPI and the OSI/MHS systems. A call to GPI_WAIT_ with a
minimum interval of at least 5 seconds is recommended.
GIP Memory Problems
When the GIP process abends mysteriously you may have a memory problem. Check
the EMS events to see if there is a specific event message describing the reason the GIP
process stopped. When insufficient swap file space is available, the MHS subsystem
will return a ZMHS-EVT-NO-MEM event message and include the name of the swap
file.
Entry and Wait Manager Problems
The Gateway Process name (GW-PNAME) refers to the Entry Manager process of the
OSI/GPI configuration. The Gateway Auxiliary process name (GW-AUX-PNAME)
refers to the Wait Manager process used for inbound message processing. If either of
the Entry Manager or Wait Manager cannot properly handle a GIP request during a call
to GPI_OPEN_, GPI_MT_WAIT_, or GPI_MT_START TRANSFER_IN_, the GPI will
return either error code 6014 (ZGPI-RC-GW-AUX-PNAME-ERROR) or 6015 (ZGPI-
RC-GW-PNAME-ERROR). These primary error codes from the GPI interface are
described briefly in the GPI Reference Manual.
When one of these errors is returned at the GPI interface in the primary error code, the
secondary error code will contain the TRANSFER error code returned by the Entry
Manager or Wait Manager. This number will be negative and can be looked up in the
TRANSFER Programming Guide.