In Figure 1, assume that HOST21 is a gateway VTAM®. Also assume that HOST11 sends only the alias name to HOST21 in the session initiation request. The following steps occur:

• HOST21 dynamically defines a CDRSC for TERM1 or uses a predefined CDRSC.
• HOST21 attempts to determine the real name of TERM1 using the NetView® alias name translation facility or the session management exit routine.
• HOST21 routes the session setup request to HOST31 using the adjacent SSCP tables, and the request leaves the first gateway.
• When the request leaves the first gateway, VTAM does the following actions:
  • If the real name and network identifier are not determined using the NetView alias name translation facility or the VTAM session management exit routine, VTAM sends out a search using the alias name to find the real name and network identifier.
  • The alias CDRSC representation (TERM1 in NET1) is updated to reflect the real CDRSC representation (TERM1 in NET3).
• In SSCP21, a CDRSC is defined or dynamically created for APPL1 also. Because APPL1 is the originating LU, its real name and network identifier are known. The predefined CDRSC can be defined with or without a network identifier.
• HOST31 receives the session initiation request from HOST21, which contains both real and alias names for TERM1. HOST31 then determines that it owns TERM1.
• HOST31 locates a CDRSC representation for APPL1 or dynamically defines one using the real name (APPL1 in NET1). If you have defined a CDRSC definition statement for APPL1 in NET3, HOST31 will use that CDRSC definition statement and will not use the dynamically defined CDRSC.
• When the CDRSC is found, HOST31 merges any pertinent information from the alias CDRSC representation with the real representation.
• If session initiation request processing is successful, HOST31 sends a positive response.
• HOST11 receives the response, and further processing depends on how TERM1 is defined in HOST11.
  • If TERM1 is dynamically allocated, VTAM merges the acquired information (real network ID and owning SSCP name) into the existing CDRSC.
  • If TERM1 is predefined using its alias name, the predefined CDRSC representation is updated with the real name, network identifier, and owning SSCP.
  • If TERM1 is predefined using its real name and network identifier, no further processing is required. Session setup continues, and resources are recognized by their real names, alias names, and network identifiers.

If both the real and alias names are passed in the session initiation request, either a predefined real CDRSC representation for TERM1 in NET3 is located, or a dynamic CDRSC is allocated. A predefined CDRSC without a network identifier specified can be located. In any case, the resource name is not passed to the alias name translation facility to perform name translation. However, VTAM can invoke the facility to determine if the owning SSCP is defined to the alias name translation facility.

With interconnected networks, defining CDRSCs becomes more complex as cross-network sessions, alias name translation, and adjacent SSCP rerouting are introduced. The configuration in Figure 1 shows two interconnected networks.

Figure 1. Example of two interconnected networks

          NETWORK   NETID=NETA
HOST1     CDRM      CDRDYN=YES,CDRSC=OPT
          GWPATH    GWN=GWNCP1,ADJNETSA=10,ADJNETEL=1,…
          GWPATH    GWN=GWNCP2,ADJNETSA=10,ADJNETEL=1,…

          NETWORK   NETID=NETB
HOST2     CDRM      CDRDYN=YES,CDRSC=OPT
          GWPATH    GWN=GWNCP1,ADJNETSA=20,ADJNETEL=1,…
          GWPATH    GWN=GWNCP2,ADJNETSA=20,ADJNETEL=1,…