&APPC TRANSFER_REJECT rejects the transfer of ownership of an LU6.2 conversation offered by another NCL process.
This verb has the following format:
&APPC TRANSFER_REJECT
[ ID=id ]
[ NCLID=nclid | SERVER=servername ]
[ RETRY={ YES | NO } ]
Operands:
Indicates that this is a rejection of the conversation transfer of ownership offered by another NCL process through the &APPC TRANSFER_REQUEST option. The original owner of the conversation maintains ownership. Whether you can retry the condition, or not, is indicated when the conversation is rejected.
Specifies the conversation identifier (as provided by the N00101 notification message) that references the particular conversation being rejected for transfer. This parameter indicates precisely which conversation is being rejected.
Nominates the target NCL process to which ownership of the LU6.2 conversation is to be transferred. The notification message (see below) is queued to the internal environment of this process to indicate it has been targeted for a transfer request.
SERVER=servername is an alternative way to nominate the target NCL process. If this operand is used, a search is performed for the server name registered for the region, user or system, in that order.
Indicates whether or not you can retry the reject condition. The default is RETRY=YES, and this is reflected to the remote end in the APPC return code:
TRANS_PGM_NOT_AVAIL_RETRY
Otherwise the return code is set to:
TRANS_PGM_NOT_AVAIL_NO_RETRY
Example: &APPC TRANSFER_REJECT
&APPC TRANSFER_REJECT ID=999 RETRY=NO
Return Codes:
The return codes are as follows:
Request successful
Request unsuccessful
Remote program error
State check
Request or conversation error
&ZFDBK is also set, plus all APPC system variables.
Note:
The TRANSFER_REJECT formally rejects ownership of the conversation being transferred, and logically completes the &APPC TRANSFER_REQUEST for the original owner.
| Copyright © 2009 CA. All rights reserved. |
|