IST1016I DYNAMIC DEFINITION OF nodename FAILED

Explanation

This message is the first in a group of messages that VTAM® issues when an error is detected while building a dynamic switched physical unit, logical unit, or transport resource list entry (TRLE). A complete description of the message group follows. 
 IST1016I DYNAMIC DEFINITION OF nodename FAILED
[IST1061I FAILURE OCCURRED ON puname AT locaddr]
 IST523I REASON = reason
 IST314I END
IST1016I
  • nodename is the name of the PU, LU, or TRLE that cannot be built. nodename can be *NA* if the name contains non-printable characters.
IST1061I
  • VTAM issues message IST1061I when the SDDLU dynamic definition of an LU fails.
  • puname is the name of the PU for which a dynamic LU could not be built.
  • locaddr is the address of the LU that could not be built.
IST523I
  • reason indicates the reason for the failure and is one of the following:
    ERROR IN SDDLU EXIT OR EXIT NOT AVAILABLE
    Either the selection of definitions for dependent LUs (SDDLU) exit routine has not been activated, or there was an error in SDDLU exit processing. Errors that the SDDLU exit routine can detect include:
    • The SDDLU exit routine could not generate an LU name.
    • The SDDLU exit routine could not determine which model LU name to use.
    INSUFFICIENT DEVICE ADDRESSES
    There were not enough device addresses to create the TRLE identified by nodename.
    INSUFFICIENT STORAGE
    Storage could not be obtained for the dynamic resource.
    INVALID NAME
    Either the node name or the model name returned by the configuration services XID exit routine or the SDDLU exit routine is not valid. Resource definition fails for the node with the name that is not valid.
    INVALID RESOURCE TYPE
    The definition for the independent LU was attempted. This is not a valid resource type.
    MODEL LU GROUP lugroup NOT FOUND
    The model LU group specified on the PU definition statement of puname is not active, or the LU group name entered on the VARY ACT command is not a valid VTAM name.
    MODEL modelname NOT FOUND
    The model PU or LU could not be found.
    MODEL modelname TYPE DOES NOT MATCH NODE TYPE
    The type of the model is incorrect. A PU model was specified when describing an LU node, or an LU model was specified when describing a PU node. modelname is the name of a model PU or LU.
    NO MODEL MATCHES modelname
    The model name of the powering on device does not match any of the model LUs in the LUGROUP specified on the PU. modelname is the machine type and model number.
    puname DOES NOT SUPPORT DEPENDENT LOGICAL UNITS
    Switched PU puname does not support dependent LUs because the link from the remote PU is not configured to support dependent LUs (ACTPU is suppressed).
    VALUE FOR LOCADDR NOT VALID
    An address override of LOCADDR was requested but the new value was not valid.

System action

INSUFFICIENT DEVICE ADDRESSES
The definition of the TRLE cannot be completed. The TRLE cannot be used by any TCP/IP stack.
  • If nodename is IUTIQXxx or IUTIQ6xx, the OSX interface for CHPID xx and its associated TRLE remain active, but no associated IQDX interface or IQDX TRLE exists. Other active dynamic IQDX interfaces and TRLEs are not affected.
  • If nodename is IUTIQCxx or IUTIC6xx, the OSD interface for CHPID xx and its associated TRLE remain active, but no associated IQDC interface or IQDC TRLE exists. Other active dynamic IQDC interfaces and their associated TRLEs are not affected.

Without taking an action to make more device addresses available, all subsequent dynamic definitions of IQDX or IQDC TRLEs will fail.

All other reasons
The definition of this resource cannot be completed. If resource definition fails for an LU, VTAM attempts to define any remaining LUs. If resource definition fails for a PU, VTAM does not attempt to define any LUs associated with the failed PU.

Operator response

INSUFFICIENT STORAGE
Enter a DISPLAY BFRUSE or DISPLAY STORUSE command. Save the system log and request a dump for problem determination.
MODEL LU GROUP lugroup NOT FOUND
Enter a VARY ACT command to activate the LUGROUP definition that contains the lugroup model LU group. Save the system log for problem determination.
MODEL modelname NOT FOUND
Enter a DISPLAY MODELS command to list all defined models. Either the model major node has not been activated or the name requested by the exit is incorrect.
  • Activate the model major node if it has not been activated. After the model major node has been activated, dial in can be attempted again.
    Note: The dial in must be done by the remote device; the operator generally cannot perform the dial in.
  • If the model major node name is incorrect, save the system log for problem determination.
puname DOES NOT SUPPORT DEPENDENT LOGICAL UNITS
No action is necessary unless this host should be identified as the owner of dependent LUs off of the remote PU. If this is the case, the remote PU must be reconfigured so it will indicate to this host that ACTPU should not be suppressed.
All other reasons
Save the system log for problem determination.

System programmer response

ERROR IN SDDLU EXIT OR EXIT NOT AVAILABLE
Verify that the exit is in the VTAMLIB and that the exit has been activated. If the exit is active, there is an error in the exit that must be corrected. See z/OS Communications Server: SNA Customization for more information on the SDDLU exit routine.
INSUFFICIENT DEVICE ADDRESSES
Increase the number of subchannel addresses for the channel path ID (CHPID) associated with the TRLE identified by nodename. If nodename is IUTIQXxx or IUTIQ6xx, see Steps for enabling HiperSockets access to the intraensemble data network in z/OS Communications Server: IP Configuration Guide to determine the number of subchannel addresses required and how to define them.
INSUFFICIENT STORAGE
Increase storage as required.
INVALID NAME
Correct the name returned by the exit routine. After the exit routine has been corrected, dial in can be attempted again.
INVALID RESOURCE TYPE
Ensure that the exit routine does not specify an LU model with a LOCADDR of 0 or an address override of 0.
MODEL LU GROUP lugroup NOT FOUND
Activate the LUGROUP definition that contains the model LU group lugroup. Specify an active LU group on the LUGROUP keyword in the PU definition statement for puname.
MODEL modelname NOT FOUND
The switched connection installation exit routine, ISTEXCCS, incorrectly specified the model name. Ensure that the exit routine specifies a valid model name. After the exit routine has been corrected, dial in can be attempted again.
MODEL modelname RESOURCE TYPE DOES NOT MATCH NODE TYPE
Ensure that the exit routine specifies a PU model when defining a PU, and an LU model when defining an LU. After the exit routine has been corrected, dial in can be attempted again.
NO MODEL MATCHES modelname
Add a model LU definition statement under the appropriate LUGROUP that will match the model acronym in question.
VALUE FOR LOCADDR NOT VALID
Correct the exit routine. After the exit routine has been corrected, dial in can be attempted again.

Routing code

2

Descriptor code

5