OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual

Return Codes
OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual—522223-001
B-44
8014 ZGPI-RC-NO-MATCHING-EXTENSION
Recovery. Call GPI_STATUS_ and check the secondary code, which contains the type
value, and the information buffer. Take the recovery action recommended for the error
class.
8014 ZGPI-RC-NO-MATCHING-EXTENSION
Cause. The outbound-mapping module cannot find the required extension for
criticality.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the secondary code, which contains the type
value, and the information buffer. Take the recovery action recommended for the error
class.
8015 ZGPI-RC-BAD-TABLE-OPERATION
Cause. The outbound-mapping module was not able to add or delete an entry from the
PDUID table, because the entry was invalid or the table was too full.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the secondary code, which contains the
current number of PDUID table entries, and the information buffer. Take the recovery
action recommended for the error class.
8016 ZGPI-RC-BAD-KIND
Cause. The outbound-mapping module cannot match a GPI-internal indicator.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the secondary code, which contains the
GPI-internal indicator, and the information buffer. Take the recovery action
recommended for the error class.
8017 ZGPI-RC-DEFAULT-CLASS
Cause. The outbound-mapping module cannot match an object’s class value.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the secondary code, which contains the
unmatched class value, and the information buffer. Take the recovery action
recommended for the error class.
8018 ZGPI-RC-BAD-PDU-OPERATION
Cause. The internal outbound-mapping module made an unsuccessful attempt to create
another PDU in the PDU store.
Effect. The function is not performed.