OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide

Recovering From Errors
OSI/MHS Gateway Programmatic Interface (GPI) Programming Guide—424822-001
6-25
Common GPI Errors
An example of a TRANSFER error code is 59535 decimal (E88F in hexadecimal, equal
to -6001 in unsigned decimal). This common error (returned from the Entry Manager)
sometimes indicates that the ADMIN queue is empty. Normally, a Message Relay
process (MRP) will register itself by placing an administration entry on the ADMIN
queue. The GIP will read this administration entry in order to establish communication
with the MRP. If the ADMIN queue is empty, the GIP cannot contact the MRP and a
6015 (ZGPI-RC-GW-PNAME-ERROR) error will occur. Possible reasons why the
MRP registration message is not on the ADMIN queue include:
•
The MRP is still starting up and has not registered yet.
•
The MRP has shut down and has removed its registration message from the ADMIN
queue or is in the process of shutting down and de-registering.
•
The MRP was never started.
If an entry manager or wait manager process is properly configured but has not been
started, the GPI_OPEN_ call will fail. The error returned is 2521,
ZGPI_RC_OPEN_ERROR and the secondary code will contain the standard operating
system error of 14, 201, or 60.
Incorrectly Configured Gateway
ZGPI_RC_INVALID_GATEWAY_INFO
The returned value is 6024.
The Gateway Auxiliary process name (GW-AUX-PNAME) refers to the Wait Manager
process used for inbound message processing. MHS and SCF do not check for the
presence of this attribute because the auxiliary name is regarded as optional for a
GATEWAY object. When a client tries to initialize or open a GPI gateway that has been
configured without a GW-AUX-PNAME attribute, the GPI returns error code 6024,
ZGPI-RC-INVALID-GATEWAY-INFO, and a secondary code 1603, ZGPI-IGIC-BAD-
AUX-PNAME. When converting an MHS configuration file from using a TRANSFER
gateway to using a GPI gateway, add the GW-AUX-PNAME attribute to keep this error
from occurring.