IST979I
BUILD FAILED FOR TABLE tablename

Explanation

This message is the first in a group of messages that VTAM® issues in response to a major node activation or a MODIFY TABLE command when the activation of table tablename failed.
 IST979I BUILD FAILED FOR TABLE tablename
 IST523I REASON = reason
[IST323I LABEL = labelname – MACRO = macrotype – KEYWORD = keyword]
IST979I
  • tablename is the name of the table that failed and is a model name table, an associated LU table, or a message flooding table.
IST523I
  • reason indicates the cause of the failure.
    • Most of the reasons involve macro coding errors, which may show up at this time because the tables are not pre-assembled.
    • Other errors such as insufficient storage and open failures cause activation to fail even though there are no errors in the table definition.
    reason can be one of the following:
    DUPLICATE ENTRY LABEL
    The same label appears on more than one table entry macro (MDLENT or ASLENT) in the table.
    DUPLICATE PARAMETER
    A valid keyword has been coded multiple times on a single macro.
    DUPLICATE PLU VALUE
    The same PLU name appears on more than one PLU subentry macro (MDLPLU or ASLPLU) following a single entry macro (MDLENT or ASLENT).
    EXTRA VALUE
    Multiple values were coded on a keyword that does not allow multiple values.
    INSUFFICIENT STORAGE
    VTAM was unable to allocate storage for the table.
    INVALID LABEL
    The label on the macro is invalid or a MDLENT or ASLENT macro was coded without a label.
    INVALID MACRO
    The resource definition contains an invalid macro or multiple MDLTAB or ASLTAB macros.
    INVALID PARAMETER
    The macro has an invalid keyword.
    INVALID VALUE
    The keyword has an invalid value coded.
    LIST VALUE **** IS IN CIRCULAR LIST OR MULTIPLE LISTS
    The LIST keyword on a FLDENT macro in the message flooding table referred to a message that was in more than one list.
    LIST VALUE **** WAS NOT FOUND
    The LIST keyword on a FLDENT macro in the message flooding table referenced a message that was not also in the table.
    MACRO SEQUENCE ERROR
    The second macro in the resource definition is either MDLPLU or ASLPLU. These macros must be preceded by a table entry macro (MDLENT or ASLENT).
    MISSING PLU PARAMETER
    A MDLPLU or ASLPLU macro has been coded without the PLU keyword.
    OPEN FOR VTAM DATA SET SYS1.VTAMLST FAILED
    VTAM could not open the member of the data set containing the table.
    SYNTAX ERROR
    A keyword on a macro has a syntax error.
    TABLE CONTAINS NO USEFUL INFORMATION
    The table is logically empty.
    • For a model name table, VTAM could not find a MDLENT or MDLPLU macro with a valid MODEL keyword value.
    • For an associated LU table, VTAM could not find an ASLENT or ASLPLU macro with a valid PRINTER1 or PRINTER2 keyword value.
    • For a message flooding table, VTAM could not find a FLDENT macro with a valid MESSAGE keyword value.
    TABLE SIZE OF X'xxxxxxxx' IS INVALID
    The table has exceeded the limitation of 16 megabytes (hexadecimal 00FFFFFF).
IST323I
  • If this message is displayed, it identifies the location of the error in tablename.

System action

Processing continues, but tablename cannot be used to supply model terminal support information.

Operator response

Issue the DISPLAY BFRUSE command to display information about the common service area (CSA). Save the system log for problem determination.

System programmer response

  • If reason is INSUFFICIENT STORAGE, increase storage as required. You might want to redefine your CSA start options using the MODIFY VTAMOPTS command.

    See z/OS Communications Server: SNA Operation for more information on the DISPLAY BFRUSE and DISPLAY VTAMOPTS commands. The z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures provides additional information.

  • If reason is OPEN FOR VTAM DATA SET SYS1.VTAMLST FAILED, review system definition and VTAM data set and allocation. When the error condition has been corrected, reactivate the table.
  • For all other reasons, correct the resource definition error indicated by message IST523I.

Routing code

2

Descriptor code

5