OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual

Return Codes
OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual—522223-001
B-18
2100 ZGPI-RC-EXCEEDED-MAX-OT-COUNT
Recovery. Determine whether the value syntax OM-S-ONFILE-STRING is supported
for the attribute or that enough disk space is available for the message.
2100 ZGPI-RC-EXCEEDED-MAX-OT-COUNT
Cause. The maximum number of object trees allowed by the GPI will be exceeded if
you create, copy, or transfer in an object.
Effect. Your request is rejected.
Recovery. Delete, transfer out, or finish transferring in some other object, and then try
this operation again.
2101 ZGPI-RC-FOUND-DANGLING-OBJECT
Cause. The root object (message, probe, report, or P1-encoded object) to be transferred-
in or transferred-out contains an object that has been created but not inserted as an
attribute of the root object.
Effect. The transfer-in or transfer-out operations does not succeed.
Recovery. Call GPI_STATUS_ and check the secondary code, which indicates the
number of dangling objects, and the information buffer, which provides additional
information.
2200 ZGPI-RC-BUF-ELMT-NOT-FOUND
Cause. GPI internal protocol elements cannot be found in the interprocess
communication (IPC) buffer.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the error class. Take the recovery action
recommended for the error class.
2201 ZGPI-RC-BAD-IPC-BUF
Cause. The IPC buffer contains invalid information in GPI internal protocol elements.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the error class. Take the recovery action
recommended for the error class.
2202 ZGPI-RC-BAD-REQUEST-TYPE
Cause. The request type of a GPI internal protocol element returned by the GIP is not
the request type expected for the GPI procedure you called.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the error class. Take the recovery action
recommended for the error class.