Configuration Illustrations

This section contains network diagrams for three example configurations.

The first illustration, Figure 4-17 “Example Configuration, One Session Type”, shows one dependent LU session type. The three screens pictured at the bottom of the illustration are the APPC configuration screens used to configure a dependent LU session type.

The dashed lines show the correspondence between configuration items and software entities in the SNA network. The dotted lines show the APPC sessions that are activated at subsystem startup.

Figure 4-17 Example Configuration, One Session Type

The second illustration, Figure 4-18 “Example Configuration, Three Session Types”, shows three dependent LU session types using the same SNA node.

Session types DEPSESS1 and DEPSESS2 share the same five LUs, each of which can communicate with either copy of CICS on the remote system. At subsystem startup, sessions are activated on all five LUs: two of type DEPSESS1 and three of type DEPSESS2. To activate another session of either type, you would have to deactivate a session of the other type in order to free an LU.

Session type DEPSESS3 has guaranteed access to one session, because its LU (LU002) is not configured under any other session type.

Figure 4-18 Example Configuration, Three Session Types

The third illustration, Figure 4-19 “Example Configuration, Four Session Types”, shows four session types using three SNA nodes. The dotted lines represent APPC sessions that are activated at subsystem startup.

Figure 4-19 Example Configuration, Four Session Types

Figure 4-19 “Example Configuration, Four Session Types” shows two SNA networks. AS/400 #2 has intermediate routing capabilities that allow it to connect the HP 3000 in network 1 with AS/400 #3 in network 2.

The APPC subsystem is using three SNA nodes on the HP 3000: HOSTPU, AS4001, and AS4002. Each connection to a remote system requires a separate configured SNA node and a separate copy of SNA/SDLC Link/XL.

Independent LU HPINDLU1 on the HP 3000 is configured to communicate with two independent LUs on AS/400 #1: GREENLU and BLUELU. One session type is configured for each remote independent LU.

The other independent LU on the HP 3000, HPINDLU2, uses the intermediate routing capabilities of AS/400 #2 to communicate with independent LU PURPLELU on AS/400 #3. AS/400 #3 is not directly connected to the HP 3000, and it resides in a different network. The Fully Qualified Remote LU Name configured for HPINDLU2 tells AS/400 #2 the network location of the destination LU, PURPLELU.

The dependent LU session type using HOSTPU has a limit of 4 active sessions. Two of them are configured for automatic activation, so the illustration shows two sessions active between the LUs on the HP 3000 and the LUs on the IBM host.

See Appendix B “Sample Configuration” for sample SNA node configuration screens and APPC configuration screens for the example in Figure 4-19 “Example Configuration, Four Session Types”.