|
|
|
The internal NCL request, &APPC ALLOCATE, can be sourced from any executing NCL procedure to request an APPC conversation with some remote LU. If no suitable sessions are available to that LU, and the session limit (as defined in the MCT) has not yet been reached, then the product region issues a session setup request to VTAM using the logmode name from the MCT, whereupon session initiation proceeds as for an external logon request.
Note: Wherever your product initiates a session, it is the primary session partner, and no logmode is required because the LU6.2 BIND is formatted according to the options for the link.
Sessions where your product region is the secondary session partner must be initiated by the other (primary) session partner. This does not restrict any session usage as it is a peer relationship, and aspects regarding session polarity (such as which LU is contention winner) are negotiable.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |