Messages BMC56900 through BMC56999

BMC56900E

The STOGROUP name is invalid.

Explanation: The STOGROUP name that you specified is invalid.

User response: Specify a valid STOGROUP name. If the name is a reserved word, enclose the name in double quotation marks.

BMC56901E

The DATABASE name is invalid.

Explanation: The DATABASE name that you specified is invalid.

User response: Specify a valid DATABASE name. If the name is a reserved word, enclose the name in double quotation marks.

BMC56902E

The OWNER name is invalid.

Explanation: The OWNER name that you specified is invalid.

User response: Specify a valid OWNER name. If the name is a valid delimited identifier or a reserved word, enclose the name in double quotation marks.

BMC56903E

The Volume ID is either blank or invalid.

Explanation: The VOLUME ID that you specified is invalid, or is blank.

User response: Specify a valid VOLUME ID.

BMC56904E

There are duplicate volume IDs in the list.

Explanation: The VOLUME ID that you have specified is a duplicate of one in the list.

User response: Correct the VOLUME ID.

BMC56905E

The TABLESPACE name is invalid.

Explanation: The TABLESPACE name that you specified is invalid.

User response: Specify a valid TABLESPACE name. If the name is a reserved word, enclose the name in double quotation marks.

BMC56905E.1

The prefix specified for the auxiliary table space name is too long.

Explanation: When you select to use name prefixing for an auxiliary table space, the length of the prefix is limited to a maximum of four characters. The prefix that you specified is longer than four characters. As a result, the name of the auxiliary table space is too long.

User response: Specify a shorter prefix for the name of the auxiliary table space.

BMC56906E

The DATABASE name may NOT be DSNDB06.

Explanation: You cannot use the database name “DSNDB06”.

User response: Specify a valid DATABASE name.

BMC56907E

Segsize must be zero for partitioned tablespace.

Explanation: A partitioned table space must have a SEGSIZE of 0.

User response: Correct the SEGSIZE value.

BMC56908E

Locksize of TABLE not allowed for non-segmented TSPACE.

Explanation: A nonsegmented table space cannot have a LOCKSIZE value of TABLE.

User response: Correct the LOCKSIZE value.

BMC56909E

VCAT and STOGROUP may not both be blank.

Explanation: You must specify either VCAT or STOGROUP, but these fields are both blank.

User response: Specify VCAT or STOGROUP.

BMC56910E

VCAT and STOGROUP may not both be specified.

Explanation: You cannot specify both VCAT and STOGROUP, but both these fields are specified.

User response: Specify VCAT or STOGROUP.

BMC56911E

Compress must be 'Y' or 'N'.

Explanation: For Db2 11 and earlier, valid values for Compress are Y and N.

User response: Specify a valid value for Compress.

BMC56912E

The VCAT name is invalid.

Explanation: The name that you specified for VCAT is invalid.

User response: Specify a valid VCAT name.

BMC56913E

Primary Quantity must be a numeric value.

Explanation: A nonnumeric value was specified for Primary Quantity.

User response: Specify a numeric value for Primary Quantity.

BMC56914E

Secondary Quantity must be a numeric value.

Explanation: A nonnumeric value was specified for Secondary Quantity.

User response: Specify a numeric value for Secondary Quantity.

BMC56915E

Primary Quantity may not be zero.

Explanation: You have specified a value of zero for Primary Quantity.

User response: Specify a nonzero numeric value for Primary Quantity.

BMC56915W

Primary Quantity exceeds piecesize - press END again to ignore

Explanation: When the value of the primary quantity exceeds the value of the PIECESIZE, space is wasted.

User response: To avoid wasting space, reduce the size of the primary quantity.

BMC56915W.1

Space allocation will result in wasted space; PRIQTY + (N * SECQTY) exceeds or will exceed PIECESIZE - press END again to ignore

Explanation: When the sum of the primary quantity and the secondary quantity is not evenly divisible into the PIECESIZE, space is wasted.

User response: To avoid wasting space, reduce the size of the primary and secondary quantities.

BMC56916E

Free Page must be a numeric value.

Explanation: A nonnumeric value was specified for Free Page.

User response: Specify a numeric value for Free Page.

BMC56917E

Percent Free must be a numeric value.

Explanation: A nonnumeric value was specified for Percent Free.

User response: Specify a numeric value for Percent Free.

BMC56917E.1

Percent Free for update must be -1, 0-99, <DEFLT>.

Explanation: An invalid value was specified for Percent Free for update, valid values are -1, 0-99, and <DEFLT>.

User response: Specify a valid value for Percent Free for update.

BMC56918E

Volumes may only be specified for VCAT partitions.

Explanation: You can specify volumes only for VCAT partitions.

User response: Correct the error.

BMC56919E

Allocation Unit must be K for Stogroup.

Explanation: Units of space allocation must be specified in kilobytes for STOGROUP.

User response: Specify the space allocation in kilobytes.

BMC56920E

Allocation unit must be K, C, or T. K for Stogroup.

Explanation: Units of space allocation must be specified in kilobytes, cylinders, or tracks, or for STOGROUP, in kilobytes only.

User response: Specify the appropriate space allocation units.

BMC56921E

A Volume must be specified for a VCAT partition.

Explanation: When you specify a VCAT partition, you must specify a volume.

User response: Specify a volume.

BMC56922E

The Volume ID syntax is invalid. Imbedded blanks.

Explanation: Imbedded blanks exist in the volume ID syntax, which is not valid.

User response: Eliminate the imbedded blanks from the syntax.

BMC56923E

The column name syntax is invalid or name is a “reserved” word.

Explanation: The column name that you specified uses invalid syntax.

User response: Correct the syntax. If the name is a valid delimited identifier or a reserved word, enclose the name in double quotation marks.

BMC56924E

The Column definition is unknown or blank. To define a column as a UDT you must edit the column.

Explanation: In the Table Columns List panel, you specified an invalid column type for a column. The definition for the column is unknown or blank.

User response: To define a column as a user-defined type (UDT), perform the following actions:

1. From the Table Columns List panel, type L adjacent an existing column.
2. Edit the column.
3. In the Table Column Detail panel, update the schema and data type for the column.

BMC56925E

Column Length is invalid or inconsistent with column type

Explanation: The column length that you specified is invalid, or is not consistent with the specified column type.

User response: Specify a valid column length.

BMC56926E

Allowable values for the Null field are Y or N. For ROWID and IDENTITY columns, the null value must be N.

Explanation: Null fields must have a value of Y or N. If the column is a ROWID or an IDENTITY column, the null field must have a value of N.

User response: Specify a value of either Y or N.

BMC56927E

Value for Default field is invalid. reason

Explanation: The value entered in the Default field is not valid. The following table lists the possible reasons:

User response: Correct the value entered in the Default field.

BMC56928E

Primary Key column number is a numeric field.

Explanation: The primary key column number has a nonnumeric value specified, which is not valid.

User response: Specify a numeric value for this field.

BMC56929E

The FIELDPROC name is invalid.

Explanation: The FIELDPROC name that you specified is invalid.

User response: Specify a valid FIELDPROC name, and continue.

BMC56930E

INDEX name is invalid.

Explanation: The INDEX name that you specified is invalid.

User response: Specify a valid INDEX name. If the name is a valid delimited identifier or a reserved word, enclose the name in double quotation marks.

BMC56930I.1

The first eight characters of the name of a VCAT-defined auxiliary index must be unique. If you are using name prefixing, specify a 5-character prefix for the index name to ensure uniqueness of the name.

Explanation: The first eight characters of the name of a VCAT-defined auxiliary index must be unique.

User response: To ensure the uniqueness of the name of a VCAT-defined auxiliary index, use name prefixing when you create the index and specify a five-character prefix for the index name.

BMC56931E

TABLE name is invalid.

Explanation: The TABLE name that you specified is invalid.

User response: Specify a valid TABLE name. If the name is a valid delimited identifier or a reserved word, enclose the name in double quotation marks.

BMC56932E

Table VALIDPROC is invalid.

Explanation: The VALIDPROC name that you specified is invalid.

User response: Specify a valid VALIDPROC name.

BMC56933E

Table EDITPROC is invalid.

Explanation: The EDITPROC name that you specified is invalid.

User response: Specify a valid EDITPROC name.

BMC56934E

VIEW name is invalid.

Explanation: The VIEW name that you specified is invalid.

User response: Specify a valid VIEW name. If the name is a valid delimited identifier or a reserved word, enclose the name in double quotation marks.

BMC56935E

SYNONYM name is invalid.

Explanation: The SYNONYM name that you specified is invalid.

User response: Specify a valid SYNONYM name. If the name is a valid delimited identifier or a reserved word, enclose the name in double quotation marks.

BMC56936E

ALIAS name is invalid.

Explanation: The ALIAS name that you have specified is invalid.

User response: Specify a valid ALIAS name. If the name is a valid delimited identifier or a reserved word, enclose the name in double quotation marks.

BMC56938E

Maximum number of volumes that can be specified is 133.

Explanation: You have specified a number of volumes that exceeds the maximum of 133.

User response: Specify less than 133 for the number of volumes.

BMC56939E

Segsize must be a multiple of 4. (i.e.: 4, 8, 12, etc. ...)

Explanation: You have specified a SEGSIZE that is not a multiple of 4.

User response: Specify a SEGSIZE that is a multiple of 4.

BMC56940E

There are duplicate column names in the list.

Explanation: The list contains duplicate column names, which is invalid.

User response: Eliminate the duplicate name values.

BMC56941E

Duplicate primary key column numbers in the list.

Explanation: The list contains duplicate primary key column numbers, which is invalid.

User response: Eliminate the duplicate name values.

BMC56942E

FLOAT type requires Col Length > 0 and <= 53.

Explanation: For the FLOAT type of data, you have specified a column length that is not greater than 0 and less than or equal to 53, which is invalid.

User response: Specify a valid column length value.

BMC56943E

The subtype field may only be CHANGED to B, S, or blank.

Explanation: You have entered a value other than B, S or blank for the subtype field to be changed to, which is invalid.

User response: Specify a value of B, S, or blank for the subtype field.

BMC56944E

Primary key sequence cannot be set to 0.

Explanation: You have specified a value of 0 for the primary key sequence, which is not valid.

User response: Specify a valid primary key sequence value.

BMC56945E

Constraint name is invalid.

Explanation: The CONSTRAINT name that you specified is invalid.

User response: Specify a valid CONSTRAINT name. If the name is a valid delimited identifier or a reserved word, enclose the name in double quotation marks.

BMC56946E

Sort designation is invalid. Allowable values are value.

Explanation: You have specified an invalid SORT designation for an index key. Valid values are A (ascending), D (descending), and R (random).

User response: Specify A, D, or R.

BMC56947E

Primary key sequence must be numeric. (1-64)

Explanation: You have specified a nonnumeric value or a value outside the range of 1 to 64 for the primary key sequence, which is not valid.

User response: Specify a valid primary key sequence value.

BMC56948E

Primary key column may not be nullable field.

Explanation: You have specified a field as nullable for the primary key column, which is not valid.

User response: Specify a valid value for the field.

BMC56949E

Location name is invalid or does not exist.

Explanation: The location name contains invalid syntax or cannot be found in the SYSIBM.LOCATIONS catalog table.

User response: Correct the location name.

BMC56950E

Volume list can only be obtained for VCAT objects.

Explanation: You may request a volume list only for VCAT objects.

User response: Correct the error.

BMC56951E

A new column length must be specified.

Explanation: You must specify a new column length.

User response: Specify a new column length.

BMC56952E

LONG columns may not be used as primary keys.

Explanation: You have specified a LONG column as a primary key. A LONG column is not a valid primary key.

User response: Specify a valid column as the primary key.

BMC56953E

CO is valid only when used with a TABLE, VIEW, CONSTRAINT, or INDEX

Explanation: You have specified CO (Columns) adjacent to an object other than TB (Table), VW (View), UCU (Unique Nonprimary Constraint), UCP (Primary Constraint), or IX (Index) in the mixed list.

User response: Either specify CO adjacent to the correct object or specify another command.

BMC56953E.1

UC is valid only when used with a DATABASE, TABLESPACE, or TABLE

Explanation: You have specified UC (Unique Constraint) adjacent to an object other than DB (Database), TS (Table Space), or TB (Table) in the mixed list.

User response: Either specify UC adjacent to a DB, TS, or TB, or specify another command.

BMC56954E

PT is valid only when used with a TABLESPACE or INDEX

Explanation: You have specified PT (Partitions) adjacent to an object other than TS (Table Space) or IX (Index) in the mixed list.

User response: Either specify PT adjacent to a TS or an IX, or specify another command.

BMC56955E

KY is valid only when used with an index, primary or unique constraint, or table-controlled partitioned table.

Explanation: You have specified KY (keys) adjacent to an object other than IX (index), UCU (unique nonprimary constraint), UCP (primary constraint), or TBT (table-controlled partitioning table) in the mixed list.

User response: Either specify KY adjacent to the correct object or specify another command.

BMC56955E.1

PK is valid only when used with a TABLE

Explanation: You have specified PK (Primary Key) adjacent to an object other than TB (Table) in the mixed list. Or, you specified PK on the Command line of a panel other than the Table Detail panel or the Table Columns List panel.

User response: If you are specifying PK in a mixed list, either specify PK adjacent to a TB, or specify another command. If you are specifying PK on the Command line, specify PK in the Table Detail panel or the Table Columns List panel, or specify another command.

BMC56955I.1

Select Primary Key Columns or use the “PK” command to create a primary key for the table

Explanation: You have specified to like a table that has a primary key. The new table will not have a primary key; if you want a primary key for the table, you must create it.

User response: From the Create Table panel, select Primary Key Columns or type PK on the Command line to specify the columns for the constraint.

BMC56956E

VT is valid only when used with a VIEW

Explanation: You have specified VT (View Text) adjacent to an object other than VW (View) in the mixed list.

User response: Either specify VT adjacent to a VW, or specify another command.

BMC56957E

A volume ID retained from volume placement is invalid.

Explanation: While using the DASD MANAGER volume placement facility, you entered an invalid volume, which is retained by Specification.

User response: Correct the volume ID before running Analysis.

BMC56958E

FK keys are included on the detail panel. Use line command E.

Explanation: The Foreign Key keys are included on the detail panel.

User response: Use the line command E to display the Foreign Key keys.

BMC56959W

Caution: Segmented TS. SEGSIZE will be ignored if not set to zero.

Explanation: The current SEGSIZE for this segmented table space is invalid. If you run Analysis without changing the SEGSIZE to a valid value for a segmented table space, SEGSIZE will be ignored.

User response: Change the SEGSIZE value to zero before running Analysis.

BMC56962I

Altered objects were not dropped. Issue an undo against them first.

Explanation: Altered objects were not dropped when the DROPALL command was issued.

User response: Issue an UNDO command for altered objects that you want to include in the DROPALL.

BMC56963E

CM is valid only when used with a TABLE, VIEW, INDEX, ALIAS or TRIGGER.

Explanation: You have attempted to update a Comment for an object other than those listed.

User response: Verify that you have used the correct command, or use the Comment command with the listed objects only.

BMC56965I

Limit key changes may be required for this objectType.

Explanation: You made changes to the index or table, and those changes might require changing the limit key of the index or table space. For example:

• Index changes include adding, moving, or dropping either the index keys or partitions in a partitioned index.
• Table changes include adding, moving, or dropping partitioning keys.
• Table space changes include adding, moving, or dropping partitions.

If the table uses table-controlled partitioning, the product stores the values of the limit keys in the table space partitions. If the table uses index-controlled partitioning, the product stores the values of the limit keys in the index partitions.

User response: Determine whether limit key changes are needed, and if so, make the appropriate changes.

BMC56966E

Internal Error - Partition not found in specification tables.

Explanation: The partition may have been dropped.

User response: Determine whether the partition has been dropped. Specify or modify the worklist.

BMC56967E

Internal Error - Key columns not found in specification tables.

Explanation: The key column may have been dropped.

User response: Determine whether the key column has been dropped. Specify or modify the worklist.

BMC56968E

Internal Error - Table columns not found in specification tables.

Explanation: The table column may have been dropped.

User response: Determine whether the table column has been dropped. Specify or modify the worklist.

BMC56969E

No other volumes can be present in list when “*” requested.

Explanation: A storage group volume list contains “*” and other volumes. If “*” is specified, the other volumes are invalid.

User response: Delete the incorrect volumes from the list.

BMC56970E

Existing DB cannot be changed to or from READONLY.

Explanation: You cannot change an existing database to or from ROSHARE READ.

User response: If the ROSHARE value is READ, leave it unmodified. If it is OWNER or NONE, correct it, and press Enter.

BMC56971E

OBID must be numeric non-zero and <= 65535

Explanation: The object identifier for tables in a read-only shared database must be nonzero and less than 65535.

User response: Correct the value.

BMC56972E

OBID change not valid on existing TABLE in OWNER DB.

Explanation: You cannot change the OBID for an existing table in a ROSHARE OWNER database.

User response: Correct the error.

BMC56973E

Mixed subtype may only be specified on mixed defined DB2 systems.

Explanation: You have specified the data subtype value for a character column as MIXED, and the product is not installed on a MIXED system.

User response: Modify the data subtype value.

BMC56974E

Space estimation is only available when DASD Manager is installed.

Explanation: You cannot invoke the space estimation function unless DASD MANAGER is installed.

User response: Do not attempt to run space estimation before DASD MANAGER is installed.

BMC56975E

DASD Manager default options module name is all spaces as passed.

Explanation: The installation options module name passed to DASD MANAGER consists of all spaces. This error could indicate that the product was installed incorrectly for supporting DASD MANAGER.

User response: Specify a nonblank DASD installation option name.

BMC56976E

Object types to be compared must be identical

Explanation: The compare specifies two unlike object types.

User response: Correct one of the object types.

BMC56976E

Object type is invalid for catalog to catalog comparison

Explanation: The object that you selected is not valid for a catalog to catalog comparison. Valid objects include storage groups, databases, table spaces, tables, indexes, views, synonyms, and aliases.

User response: Select a valid object type.

BMC56977E

Owner field valid only for database or tablespace

Explanation: The owner field can be specified only if a database or a table space is the highest level object to be compared.

User response: Correct the response.

BMC56978E

Field not numeric or value is invalid

Explanation: The specified field requires a numeric value.

User response: Correct the value.

BMC56979E

Average key length greater than max key length; press PF1 for more help

Explanation: The value of the average key length must be less than the value for the maximum key length. One of the following actions caused the average key length to exceed the maximum key length:

• You specified a greater value for the average key length.
• The length of a column decreased, or an index key was dropped.

If the change occurred before you selected space estimation on the index, space estimation obtained the average key length from the BMCSTATS or IBM RUNSTATS utility. Otherwise, space estimation saved the average key length when you exited space estimation.

User response: Specify a valid average key length.

BMC56983I.1

Child Table is being created new or in receiving DB2 catalog.

Explanation: You have edited a foreign key that was created by selecting the Child Table created new or in receiving DB2 Catalog option in the Create Foreign Key panel.

User response: No action is required.

BMC56984E

Primary quantity may not exceed 67108864 kilobytes.

Explanation: The value of the Primary Quantity integer is too large. The integer value for a primary quantity cannot exceed 67108864 kilobytes.

User response: Either change the buffer pool specification or reduce the requested primary space allocation.

BMC56984E.1

PRIQTY may not exceed number alloc units for device deviceType

Explanation: In the table space and index partitions list, a combination of allocation quantity and allocation unit has been entered that exceeds the maximum for the device type that is associated with that partition.

User response: Change the allocation quantity, unit, or device type to comply with the limitations.

BMC56984I

Some estimates exceeded PRIQTY limits and were not applied

Explanation: An error occurred when the estimated space was being propagated because the value of the space exceeded the limit for the primary quantity.

User response: Decrease the number of rows or change the allocation unit.

BMC56985E

Secondary quantity may not exceed 4194304 kilobytes

Explanation: The value of the Secondary Quantity integer is too large. The integer value for a secondary quantity cannot exceed 4194304 kilobytes.

User response: Either change the buffer pool specification or reduce the requested secondary space allocation.

BMC56985E.1

SECQTY may not exceed number alloc units for device deviceType

Explanation: In the table space and index partitions list, a combination of allocation quantity and allocation unit has been entered that exceeds the maximum for the device type that is associated with that partition.

User response: Change the allocation quantity, unit, or device type to comply with the limitations.

BMC56986E.1

Value out of range allowed for column base type type

Explanation: A column specified as an identity column in the Table Column list has a start or increment value that is out of range for the column’s associated column type. The field descriptions in the associated help panel will explain these ranges.

User response: Change the invalid value to comply with the acceptable ranges for the associated column type.

BMC56986E.3

Value out of range allowed for attribute

Explanation: A column specified as an identity column in the Table Column list has an increment value that exceeds the allowed ranges. Regardless of the associated column type, the increment value cannot exceed the maximum ranges allowed for an integer (+/- 2G).

User response: Change increment value to comply with the acceptable ranges allowed.

BMC56986E.5

Minimum value must be less than or equal to maximum value.

Explanation: The minimum value in the identity column is greater than or equal to the maximum value. The minimum value must be less than or equal to the maximum value.

User response: Change the minimum value for the identity column.

BMC56986W

Start outside range of minimum and maximum values

Explanation: The start value in the identity column exceeds the maximum value or is less than the minimum value.

User response: No action is required. However, unpredictable or undesirable results might occur.

BMC56988I

The string specified on the Find command was not found.

Explanation: The specified string was not found in the list.

User response: No action is required.

BMC56989E

A string is required on the first invocation of Find.

Explanation: You used the FIND command without specifying a search string.

User response: Specify a search string with the command.

BMC56990E

The parm specified on the Find command is invalid.

Explanation: You specified an invalid value for the parameter that follows the search string of the FIND command. Valid values are FIRST, NEXT, PREV, and LAST.

User response: Specify a valid value for the parameter.

BMC56991E

The string specified on the Find command is invalid.

Explanation: The search string syntax is invalid.

User response: See the ALTER and CHANGE MANAGER for DB2 Reference Manualfor the correct syntax. Correct the search string.

BMC56993E

Rows per key cannot be zero

Explanation: The number of rows per key of an index must be greater than zero.

User response: Enter a quantity or rows per key that is greater than zero.

BMC56994E

Device type must be 3390, 3380, 3375, 3350, 3340, or 3330

Explanation: The specified DASD type is unknown.

User response: Type one of the listed device types.

BMC56995E

Partition partitionName is full. Repartition, adding additional partition(s) to tablespace.

Explanation: The current partition is full. One or more additional partitions are necessary for Space Estimation requirements.

User response: Repartition the table space and index, and resequence the index limit keys.

BMC56995I

Partition partitionName requires partitionName datasets

Explanation: The nonpartitioned table space data set is full. An additional data set is necessary for Space Estimation requirements.

User response: If the object is VCAT defined, edit the worklist to add another -AMS command to define an additional data set. If the object is STOGROUP defined, no action is necessary.

BMC56996E

Partition partitionName requires more than 7257 extents.

Explanation: In space estimation, you entered a combination of data (rows, alloc & units) that has caused the required extents to exceed the maximum allowed.

User response: Edit the data entered to comply with the limitations.

BMC56996W

One or more partitions require more than 123 extents; DFSMS v1.5, or higher, required - press PF3 to ignore or ENTER to continue.

Explanation: In space estimation, you entered a combination of data (rows, alloc & units) that has caused the required extents to exceed 123.

User response: This is a warning. If the client is not running DFSMS v1.5 or higher, when attempting to run the worklist during execution, an MVS error will be returned.

BMC56997E

Partition partitionName has insufficient space

Explanation: Space Estimation has determined that the specified partition will require more than the primary quantity of space for allocation, and no secondary allocation has been specified.

User response: Increase the primary allocation or specify a secondary allocation.

BMC56998I

Tablespace has no tables, Space Estimation not performed

Explanation: You cannot perform Space Estimation on a table space that does not have any tables.

User response: Specify tables for the table space, and then do space estimation.

BMC56999E

Value of average row length must be between 1 and maximum; press PF1 for more help

Explanation: One of the following actions caused the average row length to be either 0 or greater than the maximum allowed:

• You specified a greater value for the average row length.
• The length of a column decreased, or a column was dropped.

If the change occurred before you selected space estimation on the table space, space estimation obtained the average row length from the BMCSTATS or IBM RUNSTATS utility. Otherwise, space estimation saved the average row length when you exited space estimation.User response: Specify a valid average row length.