Verbs and Built-in Functions › &APPC SEND_AND_FLUSH

&APPC SEND_AND_FLUSH

&APPC SEND_AND_FLUSH sends a single data record to the remote conversation partner and flushes any locally buffered information and forces its transmission to the remote conversation partner.

This verb has the following format:

&APPC SEND_AND_FLUSH
    [ ID=id ]
    [ MDO=mdoname [ MAP=mapname ] |
      VARS=var | VARS=(var1, var2, ..., varn ) |
      VARS=prefix* [ RANGE=(start,end) ] ]
    [ CONT={ YES | NO } ]

Operands:

ID=id

Specifies the conversation identifier (as first returned by the system variable &ZAPPCID after successful allocation) that references a particular conversation. If this parameter is omitted, the current (last referenced, or only) conversation is assumed.

MDO=mdoname [ MAP=mapname ] | VARS=var |
VARS=( var1,var2,...,varn ) | VARS=prefix* [ RANGE=(start,end) ]

Indicates how the outgoing data should be formatted. If the MDO operand is used, the data is formatted into an MDO with the name mdoname. If the outgoing data is mapped (that is, a map name is sent with the data), and MAP= is not specified, then the received map name is used to connect to Mapping Services Mapping Support. If the outgoing data is not mapped, then it is the requester's responsibility to connect to Mapping Services Mapping Support, if required, using the MAP operand.

The VARS= operand is used to provide the list of NCL variables that will contain the data received on the conversation. (The usual NCL VARS definitions apply). If the outgoing data is not mapped, or the map name is other than $NCL, then the data stream received will be segmented into the variables nominated. If the data is mapped and the map name is $NCL, then each variable is reconstructed as it was on the send request in the conversation partner. Unused variables are set to null.

CONT={ YES | NO }

Applies to OPERTYPE=GDS conversations only, and indicates whether the current GDS variable is to be continued with the next send. If CONT=NO is specified (or defaulted), the current send is the last or only logical record sent for the GDS variable. CONT=YES indicates that the continuation bit is to be set in the current logical record.

Example: &APPC SEND_AND_FLUSH

&APPC SEND_AND_FLUSH VARS=DATA

Return Codes:

The return codes are as follows:

0

Request successful

4

Request unsuccessful

8

Remote program error

12

State check

16

Request or conversation error

&ZFDBK is also set, plus all APPC system variables.

State Transition:

See &APPC SEND and &APPC FLUSH.

Note:

The SEND_AND_FLUSH is a convenient way of combining two basic APPC operations, that of sending data and of flushing the conversation. It is equivalent to issuing an &APPC SEND_DATA followed by an &APPC FLUSH request.

Relationship to LU6.2 Verb Set:

• &APPC SEND_DATA is equivalent to the LU6.2 verb MC_SEND_DATA.
• The &APPC SEND_DATA operands of VARS and MDO are used in place of the LU6.2 verb SEND_DATA options DATA and LENGTH.
• The &APPC SEND_DATA operand MAP=mapname is equivalent to the LU6.2 verb SEND_DATA option MAP(YES(mapname)).
• The FMH_DATA parameter of the LU6.2 verb SEND_DATA is not supported by &APPC.
• &APPC FLUSH is equivalent to the LU6.2 verb MC_FLUSH.

More information:

&APPC Return Code Information

&RETCODE and &ZFDBK