TRANSFER Reference Manual

IPC Request and Reply Headers
Programmatic Interface to the TRANSFER Delivery System
1–6 069139, Update 1 to 40969 Tandem Computers Incorporated
INVALID-VERSION-CODE (1)
indicates that the request contained an IPC version code that the TRANSFER
delivery system could not recognize.
INVALID-SESSION-ID (2)
indicates that the request contained a session ID that the TRANSFER delivery
system could not recognize. For example, the IPC might have referenced a
session that no longer exists.
SERVICE-DENIED (3)
is reserved for use by Tandem.
INVALID-UOW-HDR (4)
indicates that an invalid UOW header appeared in your request. This could
occur if the previous UOW specified the wrong size or if you did not identify
the header with the value UW in the UOW-CODE field of the UOW header
(described in Section 2).
RQST-TOO-LONG (5)
indicates that the request was too long; that is, the request contained more
UOWs than the number specified in the UOWS-TO-PROCESS field, or
contained more data than the TRANSFER buffer allowed.
REPLY-TOO-LONG (6)
indicates that the reply was too long; the buffer space allotted for the reply
was insufficient.
RQST-TOO-SHORT (7)
indicates that the request was too short; that is, the request contained fewer
UOWs than the number specified in the UOWS-TO-PROCESS field, or fewer
bytes were sent than the TRANSFER delivery system expected for the type of
request.
INVALID-REQUEST-CODE (8)
indicates that the REQUEST-CODE field contained an invalid entry.
E-BAD-TRANSACTION (4010)
indicates that the request did not have a TMF transaction and attempted to
perform an operation that required a TMF transaction, or that the transaction
associated with the request is unusable, probably due to the failure of a
component in the system or network. IPC-RETN-CODE-DETAIL contains the
actual GUARDIAN 90 file error code.