OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual

Return Codes

OSI/MHS Gateway Programmatic Interface (GPI) Reference Manual—522223-001

B-9

109 MH-RC-QUEUE-EMPTY

Cause. The input queue does not contain any objects that are ready to be transferred in.

Effect. No action is taken.

Recovery. Call the GPI_MT_WAIT_ procedure again.

110 MH-RC-SESSION-BUSY

Cause. The session cannot accommodate any more objects being transferred in. The

maximum number of root objects that can be processed at a time (regardless of the

number of open sessions) is 15. The root objects can be a combination of newly created

objects and reserved objects.

Effect. No action is taken.

Recovery. Call the procedure again after a root object is transferred out, deleted, or

finished transferring in.

111 MH-RC-SESSION-NOT-BUSY

Cause. A transfer in is not in progress in the session; there is no object to finish

transferring in (change to an unreserved state).

Effect. No action is taken.

Recovery. None is required.

113 MH-RC-TOO-MANY-SESSIONS

Cause. The current number of sessions is ZGPI-MAX-SESSION-ID (15). You cannot

establish another session until one of those sessions is ended.

Effect. No action is taken.

Recovery. Try opening the session again later. You can call GPI_STATUS_ , which

returns the internal session identifier in the secondary code.

115 MH-RC-NO-SUCH-SESSION

Cause. The session identifier you specified does not refer to a currently opened session.

Your program might be malfunctioning, for example, specifying an invalid session

identifier. The error might also be caused by the session being closed when the GIP

aborted, and another client using the GIP after it is restarted but before your program

continues its session.

Effect. No action is taken. Depending on the error class, the session might be unusable.

Recovery. Call GPI_STATUS_ to check the error class. GPI_STATUS_ also returns

the invalid session identifier as the secondary code. Depending on the error class, either

call the procedure again, using a valid session identifier that has been returned by a call

to GPI_OPEN_ , or close the invalid session in your application environment.