Queue Manager Manual

UOWs and UOW Formats
Queue Manager Server Interface
46517 Tandem Computers Incorporated 2–5
Caution If your application receives a value of 2 or 3 in the PW-REPLY-CODE field, the transaction should be
aborted, which will cause a transaction backout. If the transaction is not backed out, consistency in the
Queue file cannot be guaranteed.
VERSION-CODE
In both requests and replies, this field designates the version of the message formats
used. The version code format is defined by Tandem and consists of a letter followed
by a two-digit revision number. You must use the correct version code in each UOW.
IPC-RETN-CODE
In a Request to the Server. This field is ignored.
In a Reply from the Server: One of the following values appears:
IPC-OK (0) indicates the server detected no errors in the IPC header. Warning
indications or errors, however, might have been present in the individual UOWs
in the request.
INVALID-VERSION-CODE (1) indicates the request contained an IPC version
code that could not be recognized by the server.
INVALID-SESSION-ID (2) refers to access validation in TRANSFER servers and is
not applicable to Queue Manager.
SERVICE-DENIED (3) is reserved for use by Tandem.
INVALID-UOW-HDR (4) indicates an invalid UOW header appeared in the
request. This could occur if the previous UOW specified the wrong size or if you
omitted the value UW—which indicates a UOW header—from the header.
RQST-TOO-LONG (5) indicates the request was too long; that is, the request
contained more UOWs than the number specified in the UOWS-TO-PROCESS
field, contained more data than the buffer allowed, or contained more than one
WAITQ UOW. Buffer size is determined by the MAXREPLY and MAXREQUEST
parameters when configuring PATHWAY or when starting the servers.
REPLY-TOO-LONG (6) indicates the reply was too long; the buffer space allotted
for the reply was insufficient.
RQST-TOO-SHORT (7) indicates 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 were expected.
INVALID-REQUEST-CODE (8) indicates 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 one, or that the
transaction associated with the request is unusable, probably due to the failure of