Previous Topic: &APPC TEST

Next Topic: &APPC TRANSFER_CONNECT

&APPC TRANSFER_ACCEPT

&APPC TRANSFER_ACCEPT accepts the transfer of ownership of an LU6.2 conversation offered by another NCL process.

This verb has the following format:

&APPC TRANSFER_ACCEPT
    [ ID=id ]
    [ NCLID=nclid | SERVER=servername ] 
    [ ARGS | VARS=var |
      VARS=(var1, var2, ..., varn ) |
      VARS=prefix* [ RANGE=(start,end) ] ]

Operands:

TRANSFER_ACCEPT

Indicates this is a request to accept the transfer of ownership of the conversation specified by the ID parameter. If the request completes successfully, the conversation identified is then available to this procedure for operation. See Notes on the &APPC TRANSFER_REQUEST verb for more details about the transfer process.

ID=id

Specifies the conversation identifier (as provided by the N00101 notification message) that references the particular conversation being transferred. This parameter is required to indicate precisely which conversation is being accepted.

ARGS | VARS=var | VARS=( var1,var2,...,varn ) | VARS=prefix* [ RANGE=(start,end) ]

Nominates the NCL variables into which any PIP variable data present in the attach request, will be placed. If none is present, or a previous receive operation has been performed against this conversation, no variable data is set.

Example: &APPC TRANSFER_ACCEPT

&APPC TRANSFER_ACCEPT ID=999

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:

None. The transferred conversation will be in send or receive state which is determined by examining the &ZAPPCSTA system variable.

Note:

The TRANSFER_ACCEPT gains ownership of the conversation being transferred, and logically completes the &APPC TRANSFER_REQUEST for the original owner.

More information:

&APPC Return Code Information

&RETCODE and &ZFDBK