TRANSFER Programming Manual

Request Format
Designing and Writing a Client
9–6 069138, Update 1 to 040970 Tandem Computers Incorporated
Request Format The data buffer for each request consists of the following:
A request header that denotes the session on whose behalf the request is being
made and that provides space for reply and return codes
One or more UOWs, each of which specifies a code for an operation plus any
necessary parameters (For example, the operation ADD-RECIP would include the
name of the recipient to be added.)
Reply Format The TISERV reply, which is written in the same format as the request to which it
responds, consists of the following:
A reply header, with reply and return codes supplied by TISERV
One or more response UOWs that return requested data to the correspondent (For
example, the response to a CREATE-ITEM UOW request would include the item
ID for the new item.)
For each UOW in the request there is a corresponding response UOW in the reply.
TISERV processes UOWs in the order in which they appear in the request. Thus, the
response UOWs are returned in the same order as the corresponding UOWs in the
request.
For certain errors, however, no response UOWs are included. The number of UOWs
in the reply is indicated by a field in the reply header.
Where to Find
Structure Definitions
Complete Data Definition Language (DDL) and COBOL definitions of fields and
structures used in TRANSFER interprocess messages are supplied as part of the
standard software on the distribution subvolume. The files are:
GCOB—contains COBOL source code for commonly used TRANSFER elements,
such as the IPC header and UOW definitions.
GLNK—contains the same definitions as GCOB, but without INITIAL-VALUE
clauses so that the definitions can be used in the Linkage Section as parameters
between the TRANSFER system and the application.
GDDL—contains DDL definitions for these elements; you can use the DDL
definitions to generate definitions in any of the supported languages.