Write data to a 3600 (3614) logical unit.

SEND (3600-3614)
>>-SEND--FROM(data-area)--+-LENGTH(data-value)--+--+------+----->
'-FLENGTH(data-value)-' '-WAIT-'
>--+--------+--+-----------+-----------------------------------><
+-INVITE-+ +-CNOTCOMPL-+
'-LAST---' '-DEFRESP---'
Conditions: INVREQ, LENGERR, TERMERR
Description
SEND writes data to a terminal. The
data stream and communication format used between a CICS® application program and a 3614 is
determined by the 3614. The application program is therefore device dependent
when handling 3614 communication.
For further information about designing
3614 application programs for CICS, refer to the IBM® 4700/3600/3630 Guide.
Options
- CNOTCOMPL
- indicates
that the request/response unit (RU) sent as a result of this SEND command
does not complete the chain. If this option is omitted and chain assembly
has been specified, the RU terminates the chain.
- DEFRESP
- indicates
that a definite response is required when the output operation has been completed.
- FLENGTH(data-value)
An alternative to LENGTH. For architectural reasons, this option
is limited to a maximum of 32K for all terminal-related SEND commands.
- FROM(data-area)
- specifies
the data to be written to the logical unit, or a partner transaction.
- INVITE
- For
the SEND (APPC) command, INVITE allows an application program to add a change-direction
indicator to data already sent to a process in a connected APPC system. Control
data is not transmitted by CICS until the subsequent execution of a WAIT or
a SYNCPOINT command, unless CONFIRM or WAIT is also coded on the GDS SEND
INVITE command.
For the other SEND commands, INVITE specifies that the
next terminal control command executed for this facility is a RECEIVE. This
allows optimal flows to occur.
- LAST
- specifies
that this is the last SEND command for a transaction.
- LENGTH(data-value)
- specifies
the length, as a halfword binary value, of the data to be written. For a description
of a safe upper limit, see LENGTH options in CICS commands.
- WAIT
- specifies
that processing of the command must be completed before any subsequent processing
is attempted.
If the WAIT option is not specified, control is returned
to the application program when processing of the command has started. 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 has been completed.
Conditions
Some
of the following conditions may 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.
- INVREQ
- RESP2 values:
- 200
- A distributed program link server application attempted to send on its
function-shipping session (its principal facility).
For SEND (APPC), a
distributed program link server application specified the function-shipping
session (its principal facility) on the CONVID option.
also occurs (RESP2 not set) in any of the following situations:
- The CONFIRM option has been specified, but the APPC conversation is not
sync level 1 or 2.
- The SEND command has been used on an APPC conversation that is not a mapped
conversation or that is not using the EXEC CICS interface.
Default action: terminate the task abnormally.
- LENGERR
- occurs
if an out-of-range value is supplied in the LENGTH or FLENGTH option.
Default
action: terminate the task abnormally.
- TERMERR
- occurs
for a session-related error. Any action on that conversation other than a
FREE causes an ATCV abend.
A CANCEL TASK request by a user node error
program (NEP) may 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.