SEND (3600-3614)

Write data to a 3600 (3614) logical unit.

Read syntax diagramSkip visual syntax diagram
SEND (3600-3614)

                          '-FLENGTH(data-value)-'  '-WAIT-'   

   +-INVITE-+  +-CNOTCOMPL-+   
   '-LAST---'  '-DEFRESP---'   




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.


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 is specified, the RU terminates the chain.
Indicates that a definite response is required when the output operation completes.
An alternative to the LENGTH option. For architectural reasons, this option is limited to a maximum of 32 KB for all terminal-related SEND commands.
Specifies the data to be written to the logical unit, or a partner transaction.
For the SEND (APPC) command, an application can use the INVITE option 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 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 to be run for this facility is a RECEIVE. This allows optimal flows to occur.

Specifies that this is the last SEND command for a transaction.
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.
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 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.

RESP2 values:
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.

Occurs if an out-of-range value is supplied in the LENGTH or FLENGTH option.

Default action: terminate the task abnormally.

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) 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.

dfhp4_send36003614.html | Timestamp icon Last updated: Thursday, 27 June 2019