z/OS Communications Server: SNA Network Implementation Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Subarea configuration

z/OS Communications Server: SNA Network Implementation Guide
SC27-3672-01

The system programmer responsible for identifying the network subareas and their adjacent subareas must provide a configuration of the network subareas. Each network subarea must be defined in the logon manager configuration definition using one of the following formats:

Read syntax diagramSkip visual syntax diagram
>>-SA--=--x--+--------------------------+----------------------><
             +-,--ADJSA--=--a-----------+   
             |                 .-,-.    |   
             |                 V   |    |   
             '-,--ADJSA--=--(----a-+--)-'   

x
The address for a subarea (SA).
a
The address for an adjacent subarea (ADJSA). The subarea must be adjacent to subarea x.

You can specify multiple adjacent subarea addresses by enclosing them within parentheses and separating them with a comma.

All network subareas that you are defining to the logon manager must have their addresses appear in SA definition statements as either x or a.

Note: The value of MAXSUBA specified on the EXEC statement in the logon manager JCL must be at least as great as the number of different network subareas addressed as x or a in the SA definition statements in the logon manager configuration definition.

The SAs supplied by the system programmer are used by the logon manager to build a HOP table. The HOP table contains the minimum distance between subareas and is used for multitask support.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014