Previous Topic: Transaction Identifier

Next Topic: Allocation and Sessions

Destination Selection

The TCT entry can contain default destination information, by way of a link name or network LU name, to be used for the request. However the LINK or LUNAME parameters on the allocate verb can be used to override any TCT destination information (and will be required if the TCT has no default destination information).

Once a destination has been isolated resources are allocated to set up the communication path, and eventually a procedure or program is attached in the target system to service the request.

If the target system is the local system, an NCL procedure is started as an attached procedure. Such procedures are generally written to perform a specific function, or possibly a range of functions, on behalf of the invoking procedure.

If the target system is outside of the local system, an SNA LU6.2 session connecting the remote destination must be located. This session is then allocated to the conversation for the conversation duration. The fact that a session is interposed between the communicating procedures is completely transparent to the allocating procedure.