IST886I
commandinfo [statementname] action resource [TO toname] [FROM fromname] FAILED

Explanation

This message is the first in a group of messages that VTAM® issues to indicate that a dynamic reconfiguration or dynamic change failed. The failure resulted from a MODIFY DR, a VARY DRDS, or a VARY ACT command.

Possible message groups follow:
  • MODIFY DR command 
    IST886I MODIFY DR action resource [TO toname] FROM fromname FAILED
IST523I REASON = reason
    • IST886I
      • commandinfo is always MODIFY DR for this message group.
      • action is the command type:
        • DELETE to delete a physical or logical unit
        • MOVE to move a physical unit and its associated LUs.
      • resource is the name of the physical unit or logical unit affected by the command.
      • toname is the name of the line to which the PU is being moved, and is only displayed when action is MOVE.
      • fromname is the name of the line from which the PU is being moved or deleted, or the name of the PU from which the LU is being deleted.
    • IST523I
      • This message explains the reason for the failure. Possible values of reason are explained later in this message explanation.
  • VARY DRDS command 
    IST886I  DR drname [statementname] action resource [TO toname] [FROM fromname] FAILED
IST523I  REASON = reason
IST368I  FUNCTION GROUP functiongroup FAILED
    • IST886I
      • commandinfo is always DR drname for this message group.
      • drname is the name of the dynamic reconfiguration data set containing the reconfiguration definition statements.
      • statementname, if specified, is the name of the specific definition statement that failed.
      • action is the definition statement:
        • ADD to add a physical or logical unit
        • DELETE to delete a physical or logical unit
        • MOVE to move a physical unit and its associated LUs.
      • resource is the name of the physical unit or logical unit affected by the definition statement.
      • toname is the name of the line to which the PU is being moved or added, or the name of the PU to which the LU is to be added. toname is only displayed when action is MOVE or ADD.
      • fromname is the name of the line from which the PU is being moved or deleted, or the name of the PU from which the LU is being deleted. fromname is only displayed when action is MOVE or DELETE.
    • IST523I
      • This message explains the reason for the failure. Possible values of reason are explained later in this message explanation.
    • IST368I
      • This message names the specific definition statement in the dynamic reconfiguration data set that failed.
      • functiongroup is the name on the ADD, DELETE, or MOVE definition statement in the VARY DRDS deck of the specific definition statement that failed.
  • VARY ACT command 
    IST886I  VARY ACT [statementname] action resource [TO toname] [FROM fromname] FAILED
IST523I  REASON = reason
    • IST886I
      • commandinfo is always VARY ACT for this message group.
      • statementname is the major node name which was specified on the ID operand of the VARY ACT command.
      • action is the action being performed when the failure occurred:
        • ADD to add a resource
        • CHANGE to change an operand value
        • DELETE to delete a resource
        • MOVE to move a physical unit and its associated LUs or to move a logical unit
      • resource is the name of the resource affected by the command.
      • toname is the name of the higher level resource to which the resource is being moved or added. toname is only displayed when action is MOVE or ADD.
      • fromname is the name of the higher level resource from which the resource is being moved or deleted. fromname is only displayed when action is MOVE or DELETE.
    • IST523I
      • This message explains the reason for the failure. Possible values are:
The second message in each message group is IST523I, and this message explains the reason for the failure. reason can be one of the following:
DUPLICATE STATION ID
An attempt was made to perform a DR CHANGE of IDBLK or IDNUM for a switched PU, but the resulting station ID was not unique in the network.
DR DELETE INVALID FOR INDEPENDENT LU
An attempt was made to perform a DR DELETE on an independent LU which is not associated to the adjacent link station specified on the FROM operand. This is not a valid request.
DR NOT SUPPORTED
An attempt was made to perform a DR function for a resource that does not support DR or this function of DR.
INSUFFICIENT STORAGE
VTAM was unable to allocate storage during a DR operation.
INVALID MACRO
A definition statement was read that is not a valid member in this type of definition deck. For example, a GROUP definition statement is not a valid member in a DR deck.
INVALID NAME
functiongroup is invalid for the PU or LU definition statement.
INVALID PARAMETER
An operand was found in a definition statement that is not valid or allowed.
INVALID RESOURCE CURRENT STATE
An attempt was made to move, delete, or change a resource whose current state will not allow it. This error occurs because the resource is not in an inactive, reset, release, or defined state. Also, a model CDRSC must not have clone CDRSCs associated with it.
Note: This reason can be issued for an active minor node when a VARY ACT,UPDATE=ALL command is entered for that resource's major node. This is probably not a definition error and usually requires no action. The most frequent cause is that an operand on a definition statement for the minor node resource in message IST886I was changed using a VTAM command such as VARY LOGON, VARY NOLOGON, or MODIFY DEFAULTS before the VARY ACT,UPDATE=ALL command was entered for the major node. This occurs only when action in message IST886I is CHANGE. See z/OS Communications Server: SNA Operation for additional information about these commands.
INVALID RESOURCE TYPE
An attempt was made to move or delete a resource for which dynamic reconfiguration is not allowed. DR ADD, DELETE and MOVE may be performed for SNA type 1, 2, or 2.1 PUs and their subordinate LUs, as well as for dependent LUs and some independent LUs.
INVALID TO/FROM RESOURCE TYPE
An attempt was made to add, delete, or move a resource to or from a target resource that does not allow dynamic reconfiguration. DR ADD is allowed to lines and PUs. DR DELETE is allowed from lines and PUs. DR MOVE is allowed both to and from lines and PUs.
INVALID VALUE
An operand on a definition statement was found to have a coded value that is invalid for this operand.
INVALID VALUE FOR ADDR
The value coded in a PU definition statement for the ADDR operand was found to be a duplicate of a PU ADDR already under the target line.
LUGROUP CANNOT BE ADDED DYNAMICALLY
An attempt was made to dynamically add the LUGROUP operand to a PU definition statement. However, VTAM cannot add this operand using dynamic change. If you need to add this operand, use dynamic reconfiguration to delete the PU and then add it back with LUGROUP in the definition.
MACRO SEQUENCE ERROR
A DR definition deck contained definition statements that were out of sequence. Line targets must be followed by PUs; PU definition statements must be followed by LUs. PU definition statements must follow additions to lines, moves to lines, moves from lines, and deletions from lines. LU definition statements must follow additions to PUs, moves to PUs, and deletions from PUs.
MISSING MACRO
A DR definition deck was missing a definition statement. VBUILD definition statements are required. Null definition decks are invalid (a VBUILD definition statement with nothing following). Null function groups are invalid (a function group with no PU or LU definition statements).
MISSING NAME ON PU OR LU MACRO
A PU or LU definition statement in a DR definition deck did not have a name coded. The name is required on all PU and LU resources being added, deleted, or moved.
MISSING PARAMETER
A definition statement in a DR definition deck did not contain a required operand.
NO RESOURCES FOUND UNDER FROM LINE/PU
The line or PU resource for which a DR DELETE or DR MOVE function was requested had no resources under it.
OPERANDS COULD NOT BE ADDED DYNAMICALLY
An attempt was made to dynamically add APPN operands to a PU, but these APPN operands cannot be added dynamically to this PU. Instead, use dynamic reconfiguration to delete the PU and then add it back with the desired APPN operands in the definition.
PUDR=NO OR LUDR=NO CODED ON RESOURCE DEFINITION
An attempt was made to dynamically delete or move a resource that had either PUDR=NO or LUDR=NO coded on its definition statement. PUDR=NO or LUDR=NO indicates that no dynamic reconfiguration can be performed on the resource.
PUTYPE CANNOT BE CHANGED DYNAMICALLY
An attempt was made to change the value of PUTYPE on the specified resource.
RESOURCE NOT FOUND WHERE SPECIFIED
An attempt was made to delete or move a resource that does not exist under the specified target fromname.
SYNTAX ERROR
There is a syntax error in the DR definition deck.
TO/FROM RESOURCE NOT IN SAME NCP
An attempt was made to DR move a PU or LU from a line in an NCP to a line in a different NCP.
TO/FROM RESOURCE UNKNOWN
An attempt was made to add or move a resource to a target that does not exist or to delete or move a resource from a target that does not exist.
UPDATE=ALL REQUIRED - UPDATE=ADD VIOLATES HIERARCHY
An attempt was made to update an Enterprise Extender XCA major node with a VARY ACT,UPDATE=ADD command after one of the following changes was made to the definitions:
  • A second PU was added under a LINE
  • A PU name was changed
  • The PU prefix was added or changed on the AUTOGEN keyword on a GROUP definition statement.

System action

  • For MODIFY DR, processing of that command is terminated.
  • For VARY DRDS, the functiongroup specified in message IST368I is not processed. Any other function groups in the DR data set drname are processed.
  • For VARY ACT, this resource and its subordinate resources are skipped, but the remaining definition statements are processed.

Operator response

Enter a DISPLAY command for resource in message IST886I. Save the system log for problem determination.

If reason is INSUFFICIENT STORAGE, enter the DISPLAY BFRUSE or DISPLAY STORUSE command. Save the system log and request a dump for problem determination.

If reason is UPDATE=ALL REQUIRED - UPDATE=ADD VIOLATES HIERARCHY, do the following:
  • If a second PU was added under a LINE, remove the second PU from the definitions. There can only be one PU defined per LINE.
  • If a PU name was changed, re-enter the VARY ACT command with UPDATE=ALL instead of UPDATE=ADD.
  • If the PU prefix was added or changed on the AUTOGEN keyword on a GROUP definition statement, re-enter the VARY ACT command with UPDATE=ALL instead of UPDATE=ADD.

System programmer response

Use the output from the operator to correct the command issued and the definition statements (if appropriate).

If reason is INSUFFICIENT STORAGE, increase storage as required. For insufficient storage errors, you might want to redefine your buffer pool or CSA start options. If the start option cannot be modified using the MODIFY VTAMOPTS command, you must modify the VTAM start options file (ATCSTRxx) and restart VTAM to use the start option.

Routing code

2

Descriptor code

5

Parent topic: IST messages for VTAM network operators IST800I – IST1199I