OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual

Return Codes
OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual522223-001
B-49
8511 ZGPI-RC-UNREADABLE-PDU
8511 ZGPI-RC-UNREADABLE-PDU
Cause. The inbound-mapping module could not read the inbound PDU from the PDU
store.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the information buffer. Take the recovery
action recommended for the error class.
8512 ZGPI-RC-UNSUPPORTED-BODY-PART
Cause. A body part has been encountered that is not supported by the GPI. The
secondary code contains the kind code of the unsupported body part.
Effect. The GPI decodes the entire message except the body part that is unsupported.
Recovery. You can process the message without the body part decoded, or you can
archive the message and analyze it using diagnostic tools.
Secondary Codes
Secondary codes provide detailed information about the conditions reported by codes
returned in the status and primary-code parameters.
Table B-13 through Table B-24 summarize the secondary code values you can receive
from a GPI procedure and explains what they mean. The second segment of the
secondary code prefix (following ZGPI-) indicates the return code that caused the
secondary codes, as follows:
FDC- OM-RC-FUNCTION-DECLINED
MIC- OM-RC-MEMORY-INSUFFICIENT
NSOC- OM-RC-NO-SUCH-OBJECT
PIC- OM-RC-POINTER-INVALID
SEC- OM-RC-SYSTEM-ERROR
TMVC- OM-RC-TOO-MANY-VALUES
WVNC- OM-RC-WRONG-VALUE-NUMBER
PEC- ZGPI-RC-PROTOCOL-ERROR
IRDC- ZGPI-RC-ILLEGAL-RECIPIENT-DR
WVMC- OM-RC-WRONG-VALUE-MAKEUP
NPC- OM-RC-NOT-PRESENT
IGIC- ZGPI-RC-INVALID-GATEWAY-INFO
PFIC- ZGPI-RC-PDU-FILE-INACCESSIBLE