OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual

Return Codes
OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual—522223-001
B-39
6036 ZGPI-RC-GW-NAME-NOT-CONFIGURED
6036 ZGPI-RC-GW-NAME-NOT-CONFIGURED
Cause. No configuration record was found for the gateway name passed to the GPI as a
parameter in GPI_OPEN_. It is assumed that the gateway name is therefore invalid.
There is no secondary code.
Effect. The function is not performed.
Recovery. Check the gateway name which was configured and ensure it is the same as
the name passed by the client as a parameter to GPI_OPEN_.
6037 ZGPI-RC-NO-PDU-MEMORY-BUFFER
Cause. Memory is not available for PDU manipulation.
Effect. The function is not performed.
Recovery. Check memory availability on the system and swap file allocations.
6038 ZGPI-RC-ENCODED-MSG-TOO-LONG
Cause. The inbound message received from the MTA has exceeded the limit specified
by the client application. A maximum message limit of 2 MB through 10 MB is set with
the max-table-data parameter of the GPI-INITIALIZE_ procedure. For additional
information about setting message size, refer to the description of GPI_INITIALIZE_
on
page 4-7.
Effect. An empty root object is returned from the call to
GPI_MT_START_TRANSFER_IN_.
Recovery. Call GPI_FINISH_TRANSFER_IN_ with the appropriate option to remove
the message from the input queue. If the message is on a P1-EXIT input queue,
Compaq recommends the MH-TRANSFER option, which resubmits the message to the
MTA and causes the MTA to generate a non-delivery report (if the APPL recipient is not
configured to receive a message of this length). If the message is on a NORMAL input
queue, Compaq recommends the MH-ARCHIVE option, which removes the message
from the input queue but saves the message in the PDU store for later analysis. The
message originator can be determined using diagnostic tools and can be notified of the
non-delivery of the message by the client.
6039 ZGPI-RC-QUEUE-ENTRY-ARCHIVED
Cause. The queue entry found on the input queue is bad and has been archived.
Effect. The bad PDU is removed from the input queue, an event message with the PDU
ID is generated, a log record is generated, and the PDU is physically left in the PDU
store.
Recovery. Call GPI_MT_START_TRANSFER_IN_ or GPI_MT_WAIT_ again to see
if there is anything else on the input queue. If desired, you can use diagnostic tools to
investigate the bad PDU in the PDU store. To identify the PDU, check the log record.