Write data to a 3600 (3601) logical unit.
SEND (3600-3601) >>-SEND--FROM(data-area)--+-LENGTH(data-value)--+---------------> '-FLENGTH(data-value)-' >--+-----------+--+------+--+--------+--+-----------+---------->< +-LDC(name)-+ '-WAIT-' +-INVITE-+ +-CNOTCOMPL-+ '-FMH-------' '-LAST---' '-DEFRESP---'
Conditions: INVREQ, LENGERR, SIGNAL, TERMERR
SEND writes data to a terminal. This form of SEND also applies to the 4770 and the 3630 plant communication system.
A logical device code (LDC) is a code that can be included in an outbound FMH to specify the disposition of the data (for example, to which subsystem terminal it should be sent). Each code can be represented by a unique LDC mnemonic.
The installation can specify up to 256 2-character mnemonics for each TCTTE, and two or more TCTTEs can share a list of these mnemonics. Corresponding to each LDC mnemonic for each TCTTE is a numeric value (0 through 255).
A 3600 device and a logical page size are also associated with an LDC. “LDC” or “LDC value” is used in this book in reference to the code specified by the user. “LDC mnemonic” refers to the 2-character symbol that represents the LDC numeric value.
When the LDC option is specified, the numeric value associated with the mnemonic for the particular TCTTE, is inserted in the FMH. The numeric value associated with the LDC mnemonic is chosen by the installation, and is interpreted by the 3601 application program.
On output, the FMH can be built by the application program or by CICS®. If your program supplies the FMH, you place it at the front of your output data and specify the FMH option on your SEND command. If you omit the FMH option, CICS will provide an FMH but you must reserve the first three bytes of the message for CICS to fill in.
The use of FMH is optional and is not supported for all terminal types. If not supplied, CICS takes no action, except for 3600/4700 terminals, where an FMH is mandatory. In this case, if FMH is not specified, CICS supplies one and places it in the first 3 bytes of the message, which you must reserve for this purpose.
For the other SEND commands, INVITE specifies that the next terminal control command to be run for this facility is a RECEIVE. This allows optimal flows to occur.
If the WAIT option is not specified, control is returned to the application program when processing of the command starts. A subsequent input or output request (terminal control, BMS, or batch data interchange) to the terminal associated with the task causes the application program to wait until the previous request completes.
Some of the following conditions might occur in combination. If more than one occurs, only the first is passed to the application program. EIBRCODE, however, is set to indicate all the conditions that occurred.
For SEND (APPC), a distributed program link server application specified the function-shipping session (its principal facility) on the CONVID option.
Default action: terminate the task abnormally.
Default action: terminate the task abnormally.
Default action: ignore the condition.
A CANCEL TASK request by a user node error program (NEP) might cause this condition if the task has an outstanding terminal control request active when the node abnormal condition program handles the session error.
Default action: terminate the task abnormally with abend code ATNI.