ENABLE Reference Manual

THE GENERAL SERVER
Variable Portion of the Request
-----------------------------------------------------------------
| |
| |
| RECORD-IMAGE PIC X(n) (codes 1,2,3,4) |
| |
| RECORD-IMAGE-2 PIC X(m) (code 2) |
| |
| The presence of record images is dependent on specific |
| transactions; relevant transaction codes are shown in |
| parentheses. RECORD-IMAGE-2, for example, is present only |
| on UPDATE (TRANS-CODE=2). |
| |
| You do not need to supply RECORD-IMAGE for code 0. You do |
| not need to supply RECORD-IMAGE for code 1 if the operation |
| is a READ FIRST or if the data file is not key-sequenced. |
| You must supply RECORD-IMAGE for all other operations. |
| |
| RECORD-IMAGEs always begin on a word boundary. |
| |
-----------------------------------------------------------------
Figure E-2. Variable Portion of a General Server Request
The following list describes what the requester must supply in
RECORD-IMAGE and RECORD-IMAGE-2 (see Figure E-2) depending upon
the transaction.
• READ SEQUENTIAL (TRANS-CODE=1 and FUNCTION-CODE=NX or NN):
--The requester must supply the current record image in
RECORD-IMAGE.
--For READ NEXT by a new key (FUNCTION-CODE=NN), the requester
must indicate the selected key in KEY-SPECIFIER.
• READ RANDOM (TRANS-CODE=1 and FUNCTION-CODE=FR, EX, AP, AG, or
GN):
--For symbolic keys (alternate keys and the primary key for
key-sequenced files), the requester must supply the
candidate key value in its appropriate position in
RECORD-IMAGE; the General Server ignores the remainder of
the record. The requester must set KEY-SPECIFIER to
indicate the appropriate key. If FUNCTION-CODE=FR, however,
the requester need not supply a record image.
--The requester must set RECORD-KEY to the primary key value
for files that are not key-sequenced but are being read by
the primary key. The requester must set KEY-SPECIFIER to
binary zero to indicate the primary key.
E-13