Explanation
VTAM® could
not add the major node
configname to the network
for one of the following reasons:
- The MAXSUBA start option value in effect at the time the major
node was first activated does not equal the value specified in the
MAXSUBA start option.
- If the major node is a communication controller, the MAXSUBA value
specified in the NCP BUILD generation definition statement does not
equal the value specified in the MAXSUBA start option.
MAXSUBA is used only for migration purposes in order to communicate
with a pre-V3R1 level of VTAM.
System action
VTAM does
not include major node configname in the VTAM network.
Operator response
Save the system log for problem determination.
System programmer response
The MAXSUBA values must match. Change
the appropriate VTAM definition
in the definition library.
- If the MAXSUBA value in the start option does not match the value
that was in effect when the major node was activated, restart VTAM with the correct MAXSUBA value.
- For a communication controller, if the MAXSUBA value specified
in the BUILD definition statement is incorrect, correct the BUILD
definition statement, and regenerate the NCP.
Note: MAXSUBA can be coded on the NETWORK definition statement
in the NCP. In a nonnative network, this is the MAXSUBA value that
must match.
See the z/OS Communications Server: SNA Resource Definition
Reference for more
information on the MAXSUBA start option and the BUILD definition statement.
Routing code
Descriptor code