Retrieve values from an LUTYPE6.1 attach header.
EXTRACT ATTACH (LUTYPE6.1) >>-EXTRACT ATTACH--+----------------+--+--------------------+---> +-ATTACHID(name)-+ '-PROCESS(data-area)-' +-CONVID(name)---+ '-SESSION(name)--' >--+---------------------+--+---------------------+-------------> '-RESOURCE(data-area)-' '-RPROCESS(data-area)-' >--+----------------------+--+------------------+---------------> '-RRESOURCE(data-area)-' '-QUEUE(data-area)-' >--+-------------------+--+--------------------+----------------> '-IUTYPE(data-area)-' '-DATASTR(data-area)-' >--+------------------+---------------------------------------->< '-RECFM(data-area)-'
Conditions: CBIDERR, INVREQ, NOTALLOC
EXTRACT ATTACH retrieves a set of values that are held in an attach header control block, or that have been built previously. For the command to retrieve information from a received attach Function Management Header (FMH), EIBATT must have been set during a RECEIVE or CONVERSE command.
For communication between two CICS® systems, no particular significance is given by CICS to the data stream profile field in an attach FMH. For most CICS applications, the option can be omitted.
0-7 reserved - must be set to zero
8-11 0000 - user-defined
1111 - SCS data stream
1110 - 3270 data stream
1101 - structured field
1100 - logical record management
12-15 defined by the user if bits 8-11
are set to 0000; otherwise reserved
(must be set to zero)
For communication between two CICS systems, no particular significance is attached by CICS to the interchange unit field in an attach FMH. For most CICS applications the option can be omitted.
0-10 reserved - must be set to zero
11 0 - not end of multichain interchange unit
1 - end of multichain interchange unit
12,13 reserved - must be set to zero
14,15 00 - multichain interchange unit
01 - single-chain interchange unit
10 - reserved
11 - reserved
For communication between two CICS systems, a transaction running in one system can acquire a session to the second system and can identify the transaction to be attached; in the second system the identification is carried in the first chain of data sent across the session.
In general, the first four bytes of data identify the transaction to be attached. However an attach FMH, identifying the transaction to be attached, can be built and sent. The receiving CICS system uses just the first four bytes of the process name as a transaction name.
No significance is attached by CICS to process names in attach FMHs sent in chains of data other than the first.
For communication between a CICS system and another subsystem, refer to documentation supplied by the subsystem about how to use the process name field in an attach FMH.
For communication between two CICS systems, no significance is attached by CICS to the queue name in an attach FMH.
For communication between a CICS system and another subsystem, refer to documentation supplied by the subsystem about how to use the queue name field in an attach FMH.
For communication between two CICS systems, no particular significance is attached by CICS to the deblocking algorithm field in an attach FMH. For most CICS applications, the option can be omitted.
For communication between a CICS system and another subsystem, refer to documentation supplied by the subsystem about how to use the interchange unit field in an attach FMH.
0-7 reserved - must be set to zero
8-15 X'00' - reserved
X'01' - variable-length
variable-blocked
X'02' - reserved
X'03' - reserved
X'04' - chain of RUs
X'05' through X'FF' - reserved
For communication between two CICS systems, no significance is attached by CICS to the resource name in an attach FMH.
For communication between a CICS system and another subsystem, refer to documentation supplied by the subsystem about how to use the resource name field in an attach FMH.
For communication between two CICS systems, no significance is attached by CICS to the return process name in an attach FMH.
For communication between a CICS system and another subsystem, refer to documentation supplied by the subsystem about how to use the return process name field in an attach FMH.
For communication between two CICS systems, no significance is attached by CICS to the return resource name in an attach FMH.
For communication between a CICS system and another subsystem, refer to documentation supplied by the subsystem about how to use the return resource name field in an attach FMH.
Default action: terminate the task abnormally.
Default action: terminate the task abnormally.
Default action: terminate the task abnormally.