.-HOSTSA--=--1------------------. >>-+-------------------------------+--------------------------->< | (1) | '-HOSTSA--=--subarea_number-----'
range: | 1– to the maximum number of subareas allowed for the network |
If HOSTSA= is coded and SACONNS= is not coded or SACONNS=YES is coded, then this VTAM will provide subarea function. If HOSTSA= is not coded, or HOSTSA= is coded and SACONNS=NO is coded, then this VTAM will not provide subarea function.
The combination of start options HOSTSA, NODETYPE, and SACONNS determines the overall node configuration and level of function support. The start options and resulting node configurations are intended to provide a smooth migration for existing subarea hosts.
See Table 1 for a summary of the node type functions. When the node is configured as a network node or end node, attempts to activate FID4 (PU types 4 or 5) connections will fail. However, if the node is a migration data host or an interchange node, FID4 connections are allowed.
Node type | NODETYPE | HOSTSA | SACONNS | CP-CP sessions | SSCP-SSCP sessions | NCP ownership | Interchange function |
---|---|---|---|---|---|---|---|
Subarea Node | (not coded) | n 1 | n/a | no | yes | yes | no |
Interchange Node | NN | n 1 | (not coded) or YES | yes | yes | yes | yes |
Migration Data Host | EN | n 1 | (not coded) or YES | yes | yes | no | no |
Network Node | NN | (not coded) | n/a | yes | no | no | no |
Network Node | NN | n 1 | NO | yes | no | no | no |
End Node | EN | (not coded) | n/a | yes | no | no | no |
End Node | EN | n 1 | NO | yes | no | no | no |
Note:
|
HOSTSA must be less than or equal to the maximum number of subareas specified (MXSUBNUM start option). See MXSUBNUM start option for more information on the MXSUBNUM start option.