SEND (MRO)

Send data on an MRO conversation.

SEND (MRO)

Read syntax diagramSkip visual syntax diagramSENDSESSION( name)WAITINVITELASTATTACHID( name)FROM( data-area)LENGTH( data-value)FLENGTH( data-value)FMHDEFRESPSTATE( cvda)

Conditions: CBIDERR, INVREQ, LENGERR, NOTALLOC, TERMERR

 

Description

SEND sends data to a conversation partner on an MRO conversation.

Options

ATTACHID(name)
specifies that an attach header (created by a BUILD ATTACH command) is to precede, and be concatenated with, the user data supplied in the FROM option. “name” (1–8 characters) identifies the attach header control block to be used in the local task.
DEFRESP
indicates that a definite response is required when the output operation has been completed.
FLENGTH(data-value)
A fullword alternative to LENGTH.
FMH
specifies that a function management header has been included in the data in the FROM area. If the ATTACHID option is specified as well, the concatenated FMH flag is set in the attach FMH.
FROM(data-area)
specifies the data to be written to the logical unit or terminal.
INVITE
specifies that the next terminal control command to be executed for this facility is a RECEIVE. This allows optimal flows to occur.
LAST
specifies that this is the last output operation for a transaction and therefore the end of a bracket.
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.
SESSION(name)
specifies the symbolic identifier (1–4 characters) of a session TCTTE. This option specifies the alternate facility to be used. If this option is omitted, the principal facility for the task is used.
STATE(cvda)
gets the state of the transaction program. The cvda values returned by CICS® are:
  • ALLOCATED
  • FREE
  • PENDFREE
  • RECEIVE
  • ROLLBACK
  • SEND
  • SYNCFREE
  • SYNCRECEIVE
  • SYNCSEND
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

62 CBIDERR
occurs if the requested attach header control block named in ATTACHID cannot be found.

Default action: terminate the task abnormally.

16 INVREQ
RESP2 values:
200
occurs if a distributed program link server application attempted to send on its function-shipping session (its principal facility)

Default action: terminate the task abnormally.

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

Default action: terminate the task abnormally.

61 NOTALLOC
occurs if the facility specified in the command is not owned by the application.

Default action: terminate the task abnormally.

81 TERMERR
occurs for a terminal-related error, such as a session failure. This condition applies to z/OS® Communications Server-connected terminals only.

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 (DFHZNAC) handles the session error.

Default action: terminate the task abnormally with abend code ATNI.