Explanation
Either the COS table name (defined by the COSTAB
operand) or the maximum subarea value (defined by the MAXSUBA operand)
on the BUILD or NETWORK definition statement could not be defined
to VTAM®.
configname specifies
the name of the NCP definition; netid specifies
the network identifier coded on the NETID operand on the BUILD or
NETWORK definition statement that has encountered an error.
text indicates
the specific reason for the failure of either operand, as described
as follows:
- COSTAB CONFLICT
- The COS table for the netid and for this NCP
has already been defined by another BUILD or NETWORK definition statement
in this or another NCP definition.
- COSTAB NOT LOADED
- A table-load error occurred or the COS table could not be found.
- COSTAB OVERFLOW
- VTAM has exceeded the ability
to record NCP sharing of the COS table identified by the COSTAB operand.
- MAXSUBA CONFLICT
- The maximum subarea value (MAXSUBA) for the netid has
already been defined by another BUILD or NETWORK definition statement
in this or another NCP definition.
- NO STORAGE FOR COSTAB
- The COS table name cannot be saved because of the lack of available
storage.
- NO STORAGE FOR MAXSUBA
- The maximum subarea value (MAXSUBA) cannot be saved because of
the lack of available storage.
System action
- COSTAB CONFLICT
- The COS table name is ignored and processing of the NCP definition
continues. The original COS table name for the NETID defined in this
NCP definition is used.
- COSTAB NOT LOADED
- The COS table name is ignored and processing of the NCP definition
continues. Following this activation, all cross-network sessions destined
to the network identified by the NETID will fail except for SSCP-SSCP
sessions and for LU-LU sessions that use the default blank COS entry.
- COSTAB OVERFLOW
- The COS table name is ignored and processing of the NCP definition
continues. Following this activation, all cross-network sessions destined
to the network identified by the NETID will fail except for SSCP-SSCP
sessions and for LU-LU sessions which use the default blank COS entry.
Even though the Class of Service table is defined for other active
NCPs, it still cannot be used for this NCP definition, since its usage
cannot be recorded to VTAM.
- MAXSUBA CONFLICT
- The maximum subarea value is ignored and processing of the NCP
definition continues. A different value has already been defined successfully
to this host, and cannot be changed or redefined for the network identified
by the coded NETID unless all sessions which depend on this maximum
subarea are terminated.
- NO STORAGE FOR COSTAB
- The COS table name is ignored and processing of the NCP definition
continues. Following this activation, all cross-network sessions destined
to the network identified by the NETID will fail except for SSCP-SSCP
sessions and for LU-LU sessions which use the default blank COS entry.
- NO STORAGE FOR MAXSUBA
- The maximum subarea value is ignored and processing of the NCP
definition continues. If this host resides in the gateway NCP’s
native network, and will own links or link stations in the network
identified by the NETID operand, it will be impossible to activate
those links or link stations without knowledge of that network’s
maximum subarea value. However, if the definition of another NCP has
successfully defined the maximum subarea for the network, such link
and link station activations will be possible, as long as that other
NCP remains defined (that is, not deactivated).
Operator response
Save the system log for problem determination.
If text is NO
STORAGE FOR COSTAB or NO STORAGE FOR MAXSUBA, try this
activation at a later time when storage becomes available. If problems
persist, enter a DISPLAY BFRUSE command or a DISPLAY STORUSE command.
Save the system log and request a dump for problem determination.
If text is COSTAB NOT LOADED, COSTAB CONFLICT,
or COSTAB OVERFLOW, enter a DISPLAY COS,ORIGIN=configname,NETID=*
command, and save the system log for problem determination.
System programmer response
- COSTAB CONFLICT
- Review the output from the DISPLAY COS command. Inspect all the
BUILD and NETWORK definition statements preceding the definition statement
specified for the indicated network to identify the COSTAB name coded
for the same NETID. Code only a single COSTAB name for any one network
in this NCP definition. Use the MODIFY TABLE command to correct problems.
- COSTAB NOT LOADED
- Review the output from the DISPLAY COS command. Check to determine
whether the Class of Service table identified by the COSTAB operand
on the BUILD or NETWORK definition statement for the indicated network
exists in the NCP definition. Use the MODIFY TABLE command to correct
problems.
- COSTAB OVERFLOW
- Review the output from the DISPLAY COS command. Restrict the usage
of the COSTAB name for each network and NCP to less than 256. If many
NCPs need to be active simultaneously, use different COSTAB names,
each defining COSTABs for many other networks. Use the MODIFY TABLE
command to correct problems.
- MAXSUBA CONFLICT
- Check to determine whether the maximum subarea value specified
on the MAXSUBA keyword for the BUILD or NETWORK definition statement
for the indicated NETID start option is valid. This value must also
be identical to the maximum subarea values on all other BUILD or NETWORK
definition statements in this or another NCP definition that have
ever been activated.
- NO STORAGE FOR COSTAB
- Increase storage as required. Also, have the operator cancel nonessential
jobs or deactivate an unused part of the network.
- NO STORAGE FOR MAXSUBA
- Increase storage as required. Also, have the operator cancel nonessential
jobs or deactivate an unused part of the network.
Routing code
Descriptor code