|
|
|
&APPC CONNECT_NOTIFY allows the requester to start a conversation with an existing NCL process in either the local or a connected APPC system.
CONNECT_NOTIFY indicates that this is a request to connect to an active NCL process. Unless the target system cannot be reached, this request will normally be accepted. However, once accepted, the connection request remains pending a transfer of information to the target process. After such a transfer, the conversation might subsequently fail due to communication failures, or the inability to locate the desired active process.
This verb has the following format:
&APPC CONNECT_NOTIFY
{ NCLID=nclid | SERVER=servername }
[ MODENAME=modename ]
[ SYNC={ NONE | CONFIRM } ]
[ LUNAME=luname | LINK=linkname | DOMAIN=domain ]
Operands:
(Mandatory) Identifies the target process for the APPC connection request by specifying its 6-digit NCL ID. The NCL ID referenced is in the local system or in a connected APPC system.
Provides an alternative way to identify the target process for the APPC connection request by specifying its registered server name.
Nominates the session mode name for the conversation. If omitted, the system CONNECT TCT entry is used to select a default mode name. If present, modename must correspond to a valid one defined for the APPC link or the allocation will fail.
Nominates the synchronization level for the conversation. If omitted, the system CONNECT TCT entry is used to nominate the default SYNC level. If SYNC level of NONE is specified, or defaulted, then the &APPC CONFIRM and CONFIRMED requests, the &APPC PREPARE_TO_RECEIVE TYPE=CONFIRM request, and the DEALLOCATE TYPE=CONFIRM request cannot be used.
The LUNAME operand nominates the network LU name where the process to be connected is executing. When LUNAME is specified, the LINK parameter cannot be used.
If LUNAME=luname is specified then the target system must be connected to the local system with an APPC link, or must have an appropriate entry in the Dynamic Link Table to permit link initialization, otherwise the allocation fails. If luname resolves to the local LUNAME, the process being connected must be within the local system.
The LINK operand nominates the name of the APPC link connecting the local system with the target LUNAME. When LINK is specified then the LUNAME parameter cannot be used. The link must either be active, or be defined in the Dynamic Link Table with an explicit link and LU name (that is, not LUMASK) to allow it to be initialized by the allocate request.
The DOMAIN operand allows the target APPC system to be identified by domain name.
The ENV LUNAME, LINK, and DOMAIN operands are mutually exclusive.
Examples: &APPC CONNECT_NOTIFY
&APPC CONNECT_NOTIFY NCLID=&TARGETID . . . &INTREAD TYPE=REQ VARS=NFYMSG
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.
The system variable &ZAPPCID is also set by this request and returns the system conversation identifier allocated to the conversation. This value is saved and supplied on the ID operand of subsequent &APPC requests to nominate a specific conversation where the NCL process is operating more than one conversation concurrently.
State Transition:
The allocation is deemed to be performed from reset state and following notification and successful completion the conversation enters send state locally. When the remote program or procedure is attached to service the conversation it is in receive state.
Notes:
| Copyright © 2009 CA. All rights reserved. |
|