IST863I
MODIFY TABLE COMMAND FAILED–reason

Explanation

This message is the first in a group of messages that VTAM® issues in response to a MODIFY TABLE command. A complete description of the message group follows.
 IST863I  MODIFY TABLE COMMAND FAILED-reason
 IST864I  NEWTAB=newtable, OLDTAB=oldtable, OPT=option,
          TYPE=tabletype
[IST935I ORIGIN=ncpname, NETID=netid, ID=resourcename]
The value of newtable, oldtable, ncpname, netid, and resourcename will be ***NA*** when the following operands are not specified on the command:
newtable
NEWTAB operand
oldtable
OLDTAB operand
ncpname
ORIGIN operand
netid
NETID operand
resourcename
ID operand

IST863I

reason indicates the cause of the failure and can be one of the following:
ABEND DURING TABLE PROCESSING
An abend occurred and the MODIFY TABLE command was not processed.
BOTH FILTER TABLES IN USE
A MODIFY TABLE,TYPE=FILTER,OPTION=LOAD command has been entered, but a previous MODIFY TABLE,TYPE=FILTER has not completed its processing. VTAM cannot execute the MODIFY TABLE,TYPE=FILTER command until the previous command is completed.
CMIP SERVICES IS INACTIVE
CMIP services must be active to issue the MODIFY TABLE,OPTION=LOAD,TYPE=CMIPDDF command.
CURRENT TABLE WILL BE USED
An error was detected when attempting to load the directory definition file using the MODIFY TABLE command. A prior message will indicate the specific failure detected. The current version of the directory definition file will continue to be used by CMIP services security.
ERROR BUILDING TABLE
The table specified by tabletype was not successfully built.
INSUFFICIENT STORAGE
Not enough storage was available to process the MODIFY TABLE command.
I/O ERROR LOADING newtable
An error was detected with table newtable during a load operation.

This message might be received if the table being loaded from VTAMLIB starts in an extent that was known when VTAMLIB was opened, but ends in a new extent that was not known when VTAMLIB was opened. Since VTAMLIB is opened only once during VTAM initialization, the new extents cannot be accessed until VTAM is halted, restarted, and VTAMLIB is opened again. For information on allocating space in the data set or information on extents, see your operating system documentation.

I/O TIMEOUT LOADING newtable
An attempt was made to load table newtable, but a system or hardware problem has caused the table load facility to time out while waiting for I/O to complete.
LOADER INOPERATIVE
This can occur for one of the following reasons:
  • A previous table load never completed
  • The VTAM-directed load subtask, ISTINMLS, abnormally ended during a load request
  • The VTAM-directed load subtask, ISTINMLS, has not completed its initialization.
name NOT FOUND
The resource identified by name does not exist. name might be the new table name newtable, or a node name identified by either the ID (resourcename) or ORIGIN (ncpname) operands of the MODIFY TABLE command.

If name is newtable, this message indicates that the table could not be loaded from storage.

This message might be received if the table being loaded from VTAMLIB is entirely contained in extents that were not known when VTAMLIB was first opened. Since VTAMLIB is opened only once during VTAM initialization, the new extents cannot be accessed until VTAM is halted, restarted, and VTAMLIB is opened again. For information on allocating space in the data set or information on extents, see your operating system documentation.

ncpname HAS NO COS FOR netid
The ncpname NETWORK definition statement for network netid did not have a COSTAB keyword. As such, there was no Class of Service table association to delete for this network.
netid NOT DEFINED FOR ncpname
There was no NETWORK definition statement defining netid in the major node definition for PU type 4 ncpname or the host is a non-gateway SSCP and the network definition statements are ignored. Therefore, the COS association could not be deleted or changed.
NEW TABLE ALREADY IN USE
For OPTION=LOAD, the table indicated by newtable is already in use by another resource. A new version of newtable cannot be loaded (to replace the existing version) until all existing references to the old newtable table have been deleted.
NO APPL/LU/CDRSC BELOW RESOURCE
The major node identified by resourcename had no minor nodes. Therefore, there were no associations to change or delete.
OLD TABLE WAS NOT IN USE
An attempt was made to delete or change the association between oldtable and the resources identified by resourcename in the MODIFY TABLE command or to replace oldtable with newtable. However, no matches were found with oldtable for the specified table type.
OLD & NEW TABLE NAMES IDENTICAL
For the resource specified by resourcename and all of its subordinate nodes, the old table name, oldtable, and the new table name, newtable, were identical. Use MODIFY TABLE,OPTION=LOAD if you want to load a new copy of oldtable.
OPERATION INVALID FOR resourcename
This can occur for the following reasons:
For TYPE=[USSTAB|LOGTAB|MODETAB|MDLTAB| ASLTAB|FLDTAB]
An attempt was made to modify or delete a table associated with a resource. resourcename was specified on the ID parameter. The specified resource was either an invalid resource against which to perform a MODIFY TABLE command or was not eligible for the type of operation requested, for example, TYPE=LOGTAB for an application.
For OPTION=LOAD
An attempt was made to reload old table ISTCFCMM. This table might not be reloaded.
For OPTION=DELETE,TYPE=COSTAB
An attempt was made to delete a COS table association for a resource that was not a PU type 4 or PU type 5, or an attempt was made to delete the association between ISTSDCOS and the host PU.
For OPTION=ASSOCIATE,TYPE=COSTAB
An attempt was made to change a COS table association for a resource that was not a PU type 4 or PU type 5.
TABLE name IS FORMAT=OLD
Table name is a USS table that was assembled using FORMAT=OLD or the table is back-level. A back-level table can be either a USS table or an interpret table that was assembled using pre-VTAM V3R2 macros.
TABLE TYPE CONFLICT
New table newtable has a table type that differs from that specified using the TYPE keyword (tabletype). For example, newtable is a USS table but TYPE=LOGTAB was specified on the MODIFY TABLE command.

IST864I

option is one of the following values:
ASSOCIATE
Change table association with resources
DELETE
Delete table association with resources
LOAD
Load or refresh a table, change associations
tabletype is one of the following values. When tabletype is not applicable, for example, specifying OPT=LOAD, ***NA*** will be displayed.
ASLTAB
Associated LU table
COSTAB
Class-of-service table
CMIPDDF
CMIP directory definition file
FILTER
Session awareness data filter
FLDTAB
Message flooding table
LOGTAB
Interpret table
MDLTAB
Model name table
MODETAB
Logon mode table
USSTAB
USS table

IST935I

This message contains additional identification information for certain types of tables.
  • ncpname is the name of the PU type 4 or PU type 5 specified on the ORIGIN operand.
  • netid identifies the network specified on the NETID operand.
  • resourcename is the name of the resource specified on the ID operand.

System action

No table associations were changed except for the following reasons:
  • If reason is BOTH FILTER TABLES IN USE, the previous command will complete eventually.
  • If reason is LOADER INOPERATIVE, all subsequent MODIFY TABLE commands that require the loader will fail. If the I/O load operation eventually succeeds, load operations will again be enabled.

Operator response

  • When reason is ABEND DURING TABLE PROCESSING, save the system log and dump for problem determination.
  • When reason is BOTH FILTER TABLES IN USE, try the command again when the previous command has completed.
  • When reason is CMIP SERVICES IS INACTIVE, restart CMIP services. The new definitions will be loaded.
  • When reason is INSUFFICIENT STORAGE, reenter the MODIFY TABLE command when more storage is available. If problems persist, enter a DISPLAY BFRUSE command. Issue the DISPLAY STORUSE command to display storage usage for storage pools. Save the system log and request a dump for problem determination.
  • For the following values of reason, save the system log for problem determination:
    • CURRENT TABLE WILL BE USED
    • ERROR BUILDING TABLE
    • I/O ERROR LOADING newtable
    • I/O TIMEOUT LOADING newtable
    • LOADER INOPERATIVE
    • TABLE name IS FORMAT=OLD
  • For the following values of reason, verify that the MODIFY TABLE operands were entered correctly:
    • name NOT FOUND
    • ncpname HAS NO COS FOR netid
    • netid NOT DEFINED FOR ncpname
    • NEW TABLE ALREADY IN USE
    • NO APPL/LU/CDRSC BELOW RESOURCE
    • OLD TABLE WAS NOT IN USE
    • OLD & NEW TABLE NAMES IDENTICAL
    • OPERATION INVALID FOR resourcename
    • TABLE TYPE CONFLICT

    See z/OS Communications Server: SNA Operation for a description of command operands. The DISPLAY COS, DISPLAY ID, and DISPLAY TABLE commands can be used to obtain the current table associations for the specified resources.

System programmer response

  • When reason is ABEND DURING TABLE PROCESSING review the contents of the system dump to determine the correct problem determination action. See the z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for information on the abend procedure.
  • When reason is CURRENT TABLE WILL BE USED, correct the error indicated by message IST1444I.
  • When reason is ERROR LOADING TABLE, this message is preceded by message IST979I. See the explanation of that message for additional information.
  • When reason is INSUFFICIENT STORAGE, review the output from the operator to determine the cause of the problem.
    If the MODIFY TABLE operation is critical, have the operator cancel other jobs or deactivate some major nodes in order to free up storage for the command, and then reenter the MODIFY TABLE command.
  • When reason is I/O ERROR LOADING newtable or I/O TIMEOUT LOADING newtable, examine the definition library to make sure the requirements for the VTAM system are correct for your system. Enter a DISPLAY BFRUSE command to determine storage utilization.
  • When reason is LOADER INOPERATIVE, review the contents of the system dump to determine the correct problem determination action. See the z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures for information on the abend procedure.
  • When reason is TABLE name IS FORMAT=OLD, you need to code FORMAT=DYNAMIC on the USSTAB macro and reassemble the table using the current VTAM macro libraries.
  • For all other values of reason, no response is required.

Routing code

2

Descriptor code

5