OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual

Return Codes
OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual—522223-001
B-8
100 MH-RC-FEATURE-CONFLICTS
100 MH-RC-FEATURE-CONFLICTS
Cause. The requested feature conflicts with an existing feature of the session. For
example, when finishing a transfer-in operation, you specified that you want to retain an
object without specifying that you want to remove it from the input queue.
Effect. The function is not performed.
Recovery. Reconsider the requested feature within the context of the procedure you
called. You can call GPI_STATUS_ , which returns in the secondary code the position
of the parameter that is causing the conflict.
106 MH-RC-NOT-RESERVED
Cause. You tried to perform an operation in which an object must be reserved, but the
specified object is not reserved. For example, an object you specify in a
GPI_MT_FINISH_TRANSFER_IN procedure must be reserved.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the error class. Take the recovery action
recommended for the error class.
107 MH-RC-NOT-UNRESERVED
Cause. You tried to perform an operation in which an object must not be reserved, but
the specified object is reserved. For example, you cannot transfer a reserved object out
to the GPI service output queue.
Effect. The function is not performed.
Recovery. Call GPI_STATUS_ and check the error class. Take the recovery action
recommended for the error class.
Table B-2. Return Code Values for Message Handling
Constant (MH-RC-) Value Meaning
FEATURE-CONFLICTS 100 Requested feature conflicts with existing session
feature.
NOT-RESERVED 106 Specified object not reserved.
NOT-UNRESERVED 107 Specified object is reserved.
QUEUE-EMPTY 109 No objects in input queue awaiting transfer in.
SESSION-BUSY 110 Exceeded maximum number of transfers in.
SESSION-NOT-BUSY 111 No transfer-in operations in progress.
TOO-MANY-SESSIONS 113 Maximum of 15 sessions already in progress.
NO-SUCH-SESSION 115 Specified session does not exist.