|
|
|
An APPC link can be started from either the remote or the local domain as a result of a conversation allocation request (for example, an &APPC ALLOCATE) or an operator command (for example, LINK START). In either case the relevant DLT entry is located using the link name or LU name depending on which one was provided.
A DLT definition is needed for each remote LU that is to be connected to your product region using LU6.2 sessions.
Link activation processing will then locate the OSCT entry nominated in the DLT definition and its associated MCT entries. The information from these tables is used to activate a link with the desired properties (for example, parallel sessions). If no OSCT or MCT entries are associated with a DLT definition default options and modes are used.
Example: APPC Table Interactions
When an NCL procedure issues an allocation request the transaction ID is used to locate the TCT entry. If no destination information was provided in the &APPC ALLOCATE verb the link name or LU name in the TCT are used (if defined) to determine if the link is active. If the link is not active, the LU name or link name is used to locate the relevant DLT entry and link activation then proceeds as described in the following figure.
This figure show APPC table interactions during the activation of links.
| Copyright © 2010 CA. All rights reserved. |
|