Messages BMC50100 through BMC50199

PART LEVEL COPY DATASETS ARE REQUIRED FOR INLINE COPIES OF PBR RPN

Explanation: The allocation of partition-level data sets is required when you use the LOAD or REORG command to create INLINE copies of partition-by-range (PBR) with the relative page numbering (RPN).

User response: Change the COPYLVL specification to PART or statically allocate the copy data sets at the partition level, and then reorganize or load the table space.

EXPRESSION TOO COMPLEX

Explanation: A table check constraint contains too many parentheses or is too long.

User response: See additional messages for the correct response.

command

Explanation: This message echoes the command statement input lines that the utility read from SYSIN or the ALTER statements that the utility read from a DDLIN data set.

User response: No action is required.

CHARACTER 'c' IS NOT ALLOWED IN COMMAND

Explanation: The indicated character is not valid for a utility command or table check constraint.

User response: See additional associated messages for the correct response.

UNEXPECTED TOKEN 'token' ENCOUNTERED IN COMMAND

Explanation: The utility command is invalid and the job terminated.

User response: Ensure that the utility command keywords are spelled correctly, specified with a valid value, specified in the required order, and not duplicated where prohibited. For syntax requirements, see the reference manual for the utility that you are running. Correct any error and resubmit the job.

UNEXPECTED TOKEN 'token' ENCOUNTERED IN COMMAND

Explanation: The specified DDLIN data set is empty. The utility ignores the data set and continues processing the job.

User response: Add to the DDLIN data set the statements that you want the utility to process and resubmit the job.

PARAMETER 'parameter' IS NOT IN RANGE OF VALUES FOR OPTION 'option'

Explanation: The specified parameter value is not valid for this option. For example, the utility might issue this message when you specify an object name or constant that is longer than the maximum length that the utility supports. The utility terminated.

User response: Correct the error and resubmit the job.

PARAMETER 'parameter' IS NOT IN RANGE OF VALUES FOR OPTION 'option'

Explanation: The specified parameter value is not valid for this option. For example, the utility issues this message when you specify an object name or constant that is longer than the maximum length that the utility supports.

User response: See any additional associated messages for the correct response.

PARTITION NUMBER 'partitionNumber' NOT IN RANGE 1 TO n

Explanation: An invalid partition number is specified on your utility command.

User response: Specify a partition number within the range described in the explanation for this message and resubmit the job.

DUPLICATE PARTITION NUMBER 'partitionNumber' SPECIFIED

Explanation: The same partition number is specified twice.

User response: Remove the duplicate partition number and resubmit the job.

PARAMETER 'parameter' IS IGNORED FOR OPTION 'option'

Explanation: An option was specified with a value that the utility does not use. However, the parameter is allowed for compatibility purposes.

User response: No action is required.

'option1' OPTION SPECIFIED. OPTION 'option2' IGNORED

Explanation: Two options were specified (option1 and option2), but the utility can accept only one option. The utility ignores the second option and continues processing.

User response: No action is required.

INVALID VALUE 'value' SPECIFIED FOR 'option' OPTION

Explanation: The specified value is incorrect for the indicated option.

User response: Correct the value and resubmit the job.

INVALID STRING string

Explanation: The specified string is either empty or has unpaired quotation marks.

User response: Correct the string and resubmit the job.

INVALID STRING string

Explanation: The specified string is either empty or has unpaired quotation marks.

User response: See additional associated messages for the correct response.

'option' OPTION NOT SPECIFIED

Explanation: The utility expected the indicated option. You must specify this option at least once in the command statement.

User response: Specify the option and resubmit the job.

'option' OPTION HAS CHANGED, BUT IS NOT ALLOWED TO CHANGE ON RESTART OF PHASE = 'phase'

Explanation: An option was changed before restarting the job, but you are not allowed to change this option when restarting the phase shown in this message. The utility terminated.

User response: Change the option back to its original value and restart the job. For more information, see Chapter 4 of the reference manual for the utility that you are running.

OPTION 'option' IS NO LONGER SUPPORTED AND IS IGNORED

Explanation: An option was specified that the utility no longer supports. For information about options that the utility currently supports, see the associated reference manual. The utility ignores the option and continues processing.

User response: No action is required.

OPTION 'option' IS NO LONGER SUPPORTED AND IS IGNORED

Explanation: An option was specified that the utility no longer supports. For information about options that the utility currently supports, see the associated reference manual. The utility ignores the option and continues processing.

User response: If the utility ignoring the option will produce results that you do not want, use the information in the message and the associated reference manual to determine what action to take. Otherwise, no action is required.

'option1' OPTION SPECIFIED. OPTION 'option2' CANNOT BE USED

Explanation: The option option1 was specified, which is incompatible with option2. The utility terminated.

User response: Correct the utility command and resubmit the job. For information about options that the utility currently supports, see the associated reference manual.

OPTION 'option1' IS IGNORED. OPTION 'option2' IS ASSUMED

Explanation: The option option1 was specified, which the utility ignored and replaced with option2. The utility continues processing.

User response: No action is required.

INVALID DBCS/DELIMITED IDENTIFIER identifier

Explanation: The double-byte character set (DBCS) or delimited identifier is not a valid identifier. The utility terminated.

User response: Correct the problem with the identifier and resubmit the job.

INVALID DBCS/DELIMITED IDENTIFIER identifier

Explanation: The double-byte character set (DBCS) or delimited identifier is not a valid identifier.

User response: See additional associated messages for the correct response.

DUPLICATE DDNAME 'ddname' FOUND IN DDN OPTIONS

Explanation: The utility found two or more identical ddnames that were specified in the default name override command or installation options (for example, LOADDN or ERRDDN). The utility terminated.

User response: Ensure that each ddname that you specified in the command or installation options is unique. Restart or resubmit the job.

'option' SPECIFIED. 'requirement' REQUIRED

Explanation: The indicated option was specified, which requires requirement. The utility terminated.

User response: Correct your command statement and resubmit the job. For information about the option's requirements, see the reference manual for the utility that you are running.

'option' OPTION HAS CHANGED, BUT IS NOT ALLOWED TO CHANGE ON 'RESTART' OF PHASE = 'phase', USE 'RESTART(PHASE)'

Explanation: Before restarting the job, the value of the option shown in this message was changed. You cannot change this particular option before restarting this phase with the RESTART parameter. The utility terminated.

User response: If the change to the option is required, use RESTART(PHASE) to restart your job. Otherwise, revert to the original value of the option and restart the job.

LENGTH OF COLUMN 'columnName' IS TOO LONG FOR 'comparison' COMPARISON

Explanation: The column that was specified in the comparison is longer than the maximum length that your version of DB2 allows. The utility does not support this type of comparison and terminates.

User response: If you specified the wrong column, correct the column and resubmit the job.

LENGTH OF COLUMN 'columnName' IS TOO LONG FOR 'comparison' COMPARISON

Explanation: The column that was specified in the comparison is longer than the maximum length that your version of DB2 allows.

User response: For the correct response, see additional associated messages.

FOR 'option' COLUMN 'columnName', CONSTANT IS WRONG TYPE OR COLUMN IS NOT NULLABLE: 'constant '

Explanation: The data type of the constant that was specified is not compatible with the data type of the column, or you specified NULL for a column that is defined as NOT NULL. The utility terminated.

User response: See the description of the option in the reference manual for the utility that you are running. Correct the constant and resubmit the job.

FOR 'option' COLUMN 'columnName', CONSTANT IS WRONG TYPE OR COLUMN IS NOT NULLABLE: 'constant'

Explanation: The data type of the constant that was specified is not compatible with the data type of the column, or you specified NULL for a column that is defined as NOT NULL.

User response: See the description of the option in the reference manual for the utility that you are running. See additional associated messages for the correct response.

FOR 'option' COLUMN 'columnName', CONSTANT IS NOT IN RANGE OF COLUMN DATA TYPE: 'constant'

Explanation: The constant that was specified is not valid for the data type of the indicated column. For example, the value is too small or too large, or the length is too long. The utility terminated.

User response: Correct the constant and resubmit the job. For more information, see the reference manual for the utility that you are running.

FOR 'option' COLUMN 'columnName', CONSTANT IS NOT IN RANGE OF COLUMN DATA TYPE: 'constant'

Explanation: The constant that was specified is not valid for the data type of the indicated column. For example, the value is too small or too large, or the length is too long.

User response: See any additional associated messages for the correct response.

INVALID VALUE 'value' SPECIFIED FOR 'option' OPTION, COLUMN 'columnName'

Explanation: The utility terminated because an incorrect value was specified for the designated option. For example, in POSITION(start:end), the end value must be greater than or equal to the start value. Also, the length derived from (start:end) must match the explicit or implicit length of the input data type. If the mismatch is between an UPDATE SET value and a decimal column definition, this message accompanies message BMC50196.

User response: See the description of the option in the reference manual for the utility that you are running. Correct the value and resubmit the job.

INVALID VALUE 'value' SPECIFIED FOR 'option' OPTION, COLUMN 'columnName'

Explanation: The value of the option that was specified is incorrect. For example, the end position in POSITION(start:end) must be greater than or equal to the start position. Also, the length derived from (start:end) must match the explicit or implicit length of the input data type.

User response: See additional associated messages for the correct response.

TYPE OF COLUMN 'columnName' IS NOT ALLOWED FOR 'option' OPTION

Explanation: The utility cannot use the type of column that was specified with the option. For information about the column types that are allowed with this option, see the reference manual for the utility that you are running. The utility terminated.

User response: Choose a different column, if possible, and resubmit the job.

TYPE OF COLUMN 'columnName' IS NOT ALLOWED FOR 'option' OPTION

Explanation: The utility cannot use the type of column that was specified with the option. For information about the column types that are allowed with this option, see the reference manual for the utility that you are running.

User response: See additional associated messages for the correct response.

'FORMAT CSV' WAS SPECIFIED WITH THE 'TERMINATEDBY' CHARACTER EQUAL TO ONE OF THE 'ENCLOSEDBY' CHARACTERS

Explanation: With the FORMAT CSV option, the same character was specified for the field delimiter (the TERMINATEDBY option) as was specified for one or both of the characters that enclose the data (the ENCLOSEDBY and AND options). The utility terminated.

User response: Change the specifications in your utility command to ensure that your TERMINATEDBY value is different from both your ENCLOSEDBY and AND values. Then, ensure that your input file is compatible with the specification in your utility command. Resubmit the job.

LENGTH OF type STRING EXCEEDS MAXIMUM ALLOWED LENGTH OF length

Explanation: While processing DDL input, the utility encountered a string constant that exceeded the maximum length that the utility grants for the string type. This error can also occur when the indicated string contains a shift-in character with no corresponding shift-out character. For limitations regarding string constants in DDL input, see the reference manual for the utility that you are running.

User response: Ensure that the following conditions exist:

• The indicated string is the correct length for its type.

• You punctuated the input statement correctly.

• Any shift-in character has a corresponding shift-out character.

TOKEN THAT EXCEEDS MAXIMUM SIZE CAUSED PRE-PARSER BUFFER TO OVERFLOW PAST n BYTES

Explanation: The utility encountered invalid DDL syntax such as a keyword; a user token; or a character, graphic, or hexadecimal string constant that exceeds the maximum size and cannot fit into the pre-parser buffer. The utility terminated.

User response: Correct the DDL as follows and restart the job:

• Ensure that the DDL includes opening and closing apostrophes or opening and closing quotation marks that match.

• On a MIXED=YES system, ensure that a shift-out (X'0E') character is paired with a shift-in (X'0F') character in the first of a subsequent double-byte pair. (An X'0F' character in the second of a double-byte pair is not considered a shift-in character.)

rangeType RANGE VALUES start:end INVALID. RANGE VALUES MUST BE ASCENDING.

Explanation: A range of values was specified in which the start value is greater than the end value. This specification is invalid. The rangeType provides additional information about the type of range that you specified. For example, a rangeType of PARTITION indicates that the PART specification of your command statement is invalid. The utility terminated.

User response: Specify a range in which the end value is greater than or equal to the start value and resubmit the job.

'ORDER YES' OPTION REQUIRED FOR A MULTI-TABLE SEGMENTED TABLESPACE

Explanation: With the following exceptions, you cannot specify ORDER NO when you are reorganizing or loading a multi-table, segmented table space. The exceptions to this restriction are when you are loading a single table of a multi-table, segmented table space or when you are running an SQLAPPLY load.

User response: Specify ORDER YES or, for REORG PLUS users, remove the ORDER option from the command statement (to use the default of ORDER YES). Resubmit the job.

'ASSOCIATE BYCLUSTERKEY' CANNOT BE USED FOR A MULTI-TABLE SEGMENTED TABLESPACE

Explanation: You cannot specify ASSOCIATE BYCLUSTERKEY in the command statement when you are reorganizing or loading a multi-table, segmented table space. The utility terminated.

User response: Specify ASSOCIATE BYTABLE (or remove the ASSOCIATE option from the command statement because ASSOCIATE BYTABLE is the default for ORDER YES) and resubmit the job. For REORG PLUS users, you can alternatively remove the ORDER and ASSOCIATE options from the command statement because ORDER YES ASSOCIATE BYTABLE is the default.

'ORDER YES' IS MEANINGLESS FOR A SINGLE-TABLE TABLESPACE WITHOUT A CLUSTERING INDEX; CONVERTING TO ORDER NO

Explanation: Because you have a single-table table space with no clustering index, the utility has no sorting to perform. Therefore, ORDER YES has no meaning. The utility operates as if you specified ORDER NO.

User response: No action is required.

'ASSOCIATE BYCLUSTERKEY' IS MEANINGLESS WITHOUT ANY CLUSTERING INDEXES

Explanation: Because you do not have any clustering indexes, ASSOCIATE BYCLUSTERKEY has no meaning. The utility terminated.

User response: Specify ASSOCIATE BYTABLE (or remove the ASSOCIATE option from the command statement because ASSOCIATE BYTABLE is the default for ORDER YES) and resubmit the job. For REORG PLUS users, you can alternatively remove the ORDER and ASSOCIATE options from the command statement because ORDER YES ASSOCIATE BYTABLE is the default.

'option' OPTION HAS CHANGED, BUT IS NOT ALLOWED TO CHANGE ON RESTART OF PHASE = 'phase' FOR DDTYPE 'ddtype'

Explanation: Before restarting the job, the value of the option shown in this message was changed. This particular option cannot change before you restart this phase. The ddtype identifies the specification of the option that you need to revise. The utility terminated.

User response: Revert to the original value of the option and restart the job.

DEFAULT option1 INCOMPATIBLE WITH DEFAULT option2; CHANGED TO option3

Explanation: Two of the installation options that you specified have incompatible values. This message displays the options and their values. The utility changes option1 to option3 and continues processing.

User response: No action is required.

'CENTURY' PARAMETER VALUES 'ccyy' AND 'ccyy' ARE INVALID

Explanation: The values that were specified with the CENTURY option on the command or as part of the field specification are invalid. The first value is larger than the second value, the two values do not span 100 years, or at least one of the values specified is in an invalid format. The utility terminated processing.

User response: Correct the values for the CENTURY option and resubmit the job.

'keywordString1' CHANGED TO 'keywordString2' DUE TO reason

Explanation: The utility changed the first combination of keywords (keywordString1) to the second string (keywordString2) for the indicated reason. For more information, see the description of the keywords in Chapter 3, Chapter 4, or Appendix A of the reference manual for this utility. Processing continues.

User response: No action is required.

'keywordString1' CHANGED TO 'keywordString2' DUE TO reason

Explanation: The utility changed the first combination of keywords (keywordString1) to the second string (keywordString2) for the indicated reason. Processing continues, but you might not obtain the results that you want.

User response: If this change will produce results that you do not want, correct the problem and restart or rerun the job. Otherwise, no action is required. If the value of reason is DASD MANAGER LICENSE NOT FOUND, OR HAS EXPIRED, ensure that your utility job includes the BMCPSWD data set in the STEPLIB. For information about how to correct the problem for other reasons, see the keyword descriptions in Chapter 3, Chapter 4, or Appendix A of the reference manual for this utility.

'option1' IS OBSOLETE AND HAS BEEN CHANGED TO 'option2'

Explanation: The utility no longer supports option1. The utility uses option2 and continues processing.

User response: No action is required.

'keywordString1' HAS BEEN CHANGED TO 'keywordString2'

Explanation: The keywords in keywordString1 are not compatible. The utility uses the keywords in keywordString2 instead and continues processing. For more information about which keywords you can specify together, see Chapter 3 of the reference manual for this utility.

User response: No action is required.

'option' IGNORED DUE TO explanation

Explanation: The utility ignores the option for the indicated reason and continues processing. For example, REORG PLUS ignores the ANALYZE BMCSTATS option if you do not have the BMC Database Performance for DB2 solution installed.

User response: No action is required.

OUTPUT DESCRIPTOR 'descriptorName' HAS INVALID VALUE FOR keyword

Explanation: An incorrect value was specified for a keyword in the output descriptor shown in this message. The utility terminated processing.

User response: Correct the value for the keyword and resubmit the job.

OUTPUT DESCRIPTOR 'descriptorName' DSNAME PATTERN 'pattern' CAUSES INVALID NUMBER OF DATASETS FOR TYPE dataSetType

Explanation: The physical number of data sets that the utility created for the primary output descriptor does not match the physical number of data sets that the utility created for the secondary output descriptor. The utility terminated processing.

User response: Correct your OUTPUT statement and resubmit the job.

SYMBOLIC 'variable' IS INVALID IN OUTPUT DESCRIPTOR 'descriptorName'

Explanation: The utility found a symbolic variable that it does not support in the output descriptor. The utility terminated processing. To obtain information about using symbolic variables to construct a valid data set name, see the reference manual for the utility that you are running.

User response: Correct the data set name value in the OUTPUT statement and resubmit the job.

DSNAME TOO LONG IN OUTPUT DESCRIPTOR 'descriptorName'

Explanation: The data set name that was constructed for the specified output descriptor exceeds the maximum number of bytes that the utility allows. The utility terminated processing. If you used symbolic variables, the variables resolved to a data set name that is too long. For detailed information about using symbolic variables to construct a data set name for an output descriptor, see the reference manual for the utility that you are running.

User response: Specify a shorter data set name in the command. Resubmit or restart the job.

DSNAME CONFLICT BETWEEN OUTPUT DESCRIPTORS 'descriptorName1' AND 'descriptorName2' FOR DATASET TYPE dataSetType

Explanation: When the utility resolved the data set names of two different output descriptors, the names were identical. The utility terminated processing. The real value of each data set name must be unique for different data set types.

User response: Change the data set name of one of the output descriptors so that when the utility resolves them, each data set name is unique. Resubmit the job.

SYMBOL 'variable' MUST BE PREFIXED BY ALPHA OR NATIONAL CHARACTER IN OUTPUT DESCRIPTOR NAME 'descriptorName'

Explanation: A symbolic variable was specified that is not prefixed with an alphanumeric or national character, which is not valid. The utility terminated processing.

User response: Use the appropriate prefix for the symbol and resubmit the job. For information about using symbolic variables to construct the data set name, see the reference manual for the utility that you are running.

UNABLE TO CONTINUE, DUPLICATE DATASET EXISTS FOR OUTPUT DESCRIPTOR 'descriptorName', DSN='dataSetName'

Explanation: The utility found a data set name in one output descriptor that is already cataloged. The utility terminated processing.

User response: Change the name of one of the data sets and resubmit the job.

INVALID DSNAME 'dataSetName' BUILT FROM OUTPUT DESCRIPTOR 'descriptorName'

Explanation: The utility determined that the data set name that was provided in the output descriptor is not valid. The utility terminated processing.

User response: Ensure that the name meets operating system requirements. For information about using symbolic variables to construct the data set name, see the reference manual for the utility that you are running.

INVALID UNIT 'unitName' SPECIFIED IN OUTPUT DESCRIPTOR NAME 'descriptorName'

Explanation: A device type (disk or tape) was specified that the utility does not support for dynamic allocation. The utility terminated processing.

User response: Correct the syntax and resubmit the job.

NUMBER OF VOLUMES (n) EXCEEDS VOLCNT (n) FOR OUTPUT DESCRIPTOR 'descriptorName'

Explanation: The number of volumes that the utility processed for the dynamically allocated data set exceeded the number of volumes that was specified for the integer in the VOLCNT option. The value for VOLCNT must be large enough to accommodate the number of volumes that the utility produces for the single largest data set.

User response: Increase the VOLCNT value and resubmit the job.

SMS ERROR ON DESCRIPTOR descriptorName RETURN CODE returnCode REASON CODE reasonCode

Explanation: An SMS error occurred when the utility attempted to retrieve SMS values from the SMS subsystem. This message shows the return code number and the SMS reason code.

User response: The SMS return and reason codes are described in the IBM DFSMS documentation. Use the SMS return code and the reason code shown in this message to determine and fix the cause of the problem. Resubmit the job.

FOR DESCRIPTOR descriptorName, DATASET dataSetName WILL BE SMS MANAGED

Explanation: The utility determined that SMS will manage the data set that will be dynamically allocated. Message BMC50158I follows this message.

User response: No action is required.

DATACLAS dataClass MGMTCLAS managementClass STORCLAS storageClass

Explanation: The utility determined that SMS will manage the data set that will be dynamically allocated. This message lists the SMS classes that the system Automatic Class Selection (ACS) routines supplied.

User response: No action is required.

STORAGE GROUP storageGroupName

Explanation: This message shows the name of the SMS storage group that the utility is processing.

User response: No action is required.

NO STORAGE GROUP CONTAINS n MB, USING AVAILABLE SPACE FROM STORGROUP storageGroupName

Explanation: The utility determined that none of the storage groups that the system returned contain sufficient space for the file that the previous message (BMC50157I) shows. The utility will base its space calculations on the first eligible storage group.

User response: No action is required.

PRIMARY SPACE p RECORDS SECONDARY SPACE s RECORDS ON u UNITS SELECTED FOR STORGROUP storageGroupName

Explanation: The utility used the space available in storage group storageGroupName to calculate the number of primary and secondary records and the number of units that are required for the data set.

User response: No action is required.

NUMBER OF UNITS REQUIRED IS r BUT RESTRICTED BY UNIT COUNT OR VOLUMES OF n

Explanation: The utility calculated that it needs the indicated number of units (r) to accommodate the data set for SMS dynamic allocation. However, either UNITCNT= n was specified or volume serial numbers were specified, limiting the number of units that the utility can use. The utility proceeds with allocation and issues message BMC50165I.

User response: No action is required.

INSUFFICIENT PRIMARY SPACE AVAILABLE TO ALLOCATE PCTPRIM OF percent REQUIRED r MB AVAILABLE a MB

Explanation: The utility calculated that it needs r megabytes for the primary extent for the PCTPRIM parameter, but the largest available extent is only a megabytes. The utility job terminated. When you are running UNLOAD PLUS and the unload data set record length is greater than half a track, the value that this message shows for the required amount of space does not include unused space in a track.

User response: Either reduce the PCTPRIM value or remove the option, and resubmit the job.

NO STORAGE GROUP CONTAINS ANY USABLE SPACE

Explanation: After collecting all information for the storage group, the utility determined that none of the storage groups that the Automatic Class Selection (ACS) routines returned have any usable space.

User response: Consult the SMS or DASD administrator at your site.

DATACLASS dataClass SPECIFIES VSAM EXTENDED ADDRESSABILITY WHICH WILL CAUSE ALLOCATION TO FAIL

Explanation: While attempting to dynamically allocate a sequential file, the utility determined that the data class that was implicitly or explicitly specified contains the VSAM extended addressability attribute. This attribute causes allocation of a sequential file to fail. The utility ends allocation and the job terminates.

User response: Specify a different data class and resubmit the job.

dataSetSpace EXCEEDS 2097152 MB

Explanation: The utility determined that the space that it requires for a data set exceeds 2 terabytes. The utility job terminated.

User response: Move the data set to tape and resubmit the job.

PARAMETER 'parameterName' NOT VALID WITH reorganizationType

Explanation: LAST was specified with the PART command option; however, LAST is valid only when you are reorganizing a partition-by-growth table space. LAST is not valid for an index-only reorganization or a table space reorganization of a range-partitioned table space.

User response: Remove LAST, specify a partition number, and resubmit the job.

CANNOT EXTEND PARTITION-BY-GROWTH TABLESPACE databaseName.tableSpaceName BECAUSE explanation (RSN=reasonCode)

Explanation: The utility reached the specified partition limit and cannot extend the object with additional partitions. One of the following reason codes is displayed in this message:

• For LOADPLUS, if the value of MAXPARTITIONS is less than 4096, alter the table space to increase the value. Resubmit the job.

• For REORG PLUS, the recommended response depends on the type of reorganization you are running:

  For a single-phase SHRLEVEL NONE reorganization, either decrease PCTFREE or FREEPAGE or increase MAXROWS, and then restart the job.

  For a single-phase reorganization with any SHRLEVEL value except NONE, or for any two-phase reorganization, run a new job with decreased values for PCTFREE or FREEPAGE or increased values for MAXNEWPARTS or MAXPARTITIONS.

PARTITION partitionNumber variableText ADDED TO PARTITION BY GROWTH OBJECT databaseName.tableSpaceName

Explanation: A new physical or logical partition has been added to the specified object, either by the utility or by DB2, as follows:

• No variable text: REORG PLUS and LOADPLUS issue this variation of the message when they add a new physical partition.

• DB2 (REORG PLUS only): REORG PLUS issues this variation of the message when you are running a SHRLEVEL CHANGE reorganization and REORG PLUS detects that DB2 added a partition.

• LOGICALLY (LOADPLUS only): LOADPLUS issues this variation of the message when it adds a logical partition during the PRELOAD phase.

User response: No action is required.

PARTITION BY GROWTH OBJECT database.tableSpace MAY NEED n ADDITIONAL PARTITIONS

Explanation: The utility has determined that the partition-by-growth table space on which it is operating might need additional partitions. This message indicates how many partitions the utility might add during processing.

User response: No action is required.

ATTRIBUTE attributeName ALTERED BEFORE RESTART -- ALTER IGNORED; ORIGINAL VALUE attributeValue USED

Explanation: If you change the value of the MAXPARTITIONS option after a failed job and before restarting the job, REORG PLUS ignores the change to MAXPARTITIONS and continues processing using the original value.

User response: No action is required.

DSNUTILB IS REQUIRED BUT PRECLUDED FROM RUNNING. REASON reason

Explanation: You are using a feature that requires the utility to invoke DSNUTILB. However, your JCL specifies a utility option or parameter that is not valid when the utility invokes DSNUTILB. The utility terminated. For details about these restrictions, see the documentation for the utility that you are running.

User response: Correct your utility command or JCL, or change the type of object on which you are operating so that the utility does not invoke DSNUTILB. Resubmit your job.

USING DSNUTILB REQUIRES ACTIVE YES TO BE SET FOR ALL FILE DDTYPES THE JOB USES. ddtype FOUND SET TO ACTIVE NO

Explanation: You are using a feature that requires that the utility invoke DSNUTILB. However, you have not enabled dynamic allocation for all data sets that the utility job needs, which is required for a DSNUTILB job. The message lists the first data set for which the utility found ACTIVE set to NO. The utility terminated.

User response: Activate dynamic allocation for all data sets that your job requires and resubmit your job, or change the type of job that you are running so that the utility does not invoke DSNUTILB.

TO RUN DSNUTILB, DYNAMIC ALLOCATION MUST BE ACTIVE FOR DDTYPE LOCPFCPY WHEN COPY YES IS SPECIFIED

Explanation: You are using a feature that requires that the utility invoke DSNUTILB and you specified COPY YES. However, you did not enable dynamic allocation for the local primary copy data set (DDTYPE LOCPFCPY), which is required in this case. The utility terminated.

User response: Activate dynamic allocation for at least the LOCPFCPY DDTYPE and resubmit your job, or change the type of object on which you are operating so that the utility does not invoke DSNUTILB.

DSNUTILB REQUIRED: feature object

Explanation: You are using a feature that the utility supports by invoking DSNUTILB. In this message:

• The feature variable represents the feature that causes the utility to invoke DSNUTILB.
• The object variable represents the object that uses the feature.

User response: No action is required. For information about utility jobs that invoke DSNUTILB, see the space for the utility that you are using.

SMARTSWITCH PRECLUDED FROM SWITCHING. REASON: reasondescription

Explanation: SmartSwitch did not switch the job to BMC AMI utility. See the reasondescription in the message for details as to why the job did not switch.

User response: To enable the switch to BMC AMI utility, change the specification listed in reasondescription.

SMARTSWITCH PROCESSING status RETURN CODE=returnCode. UTILITY OUTPUT CAN BE FOUND IN BMC AMI UTILITIES DD CDBPRINT, SUMMARY AND OBJREPRT.

 Explanation:   The status is either successful or unsuccessful, depending on the BMC AMI Utilities return code. If the BMC AMI Utilities return code is neither 0 nor 4, the status is unsuccessful.

 User response:   No action is required.

SMARTSWITCH SYNTAX VERIFICATION RC=returnCode : messageText

Explanation: BMC AMI Utilities SmartSwitch syntax verification has returned a successful or unsuccessful return code:

• RC=00000000—The BMC AMI Utilities can process this OUTPUT, LOAD, REORG, or UNLOAD statement.
• RC=00000004—The BMC AMI Utilities will call DSNUTILB for LOAD or REORG.
• RC=00000008—A syntax error has occurred. For more information, see the messageText.
• RC=00000012—A severe error has occurred. For example:
  • LOAD failed for BMC AMI Utilities modules.
  • There is a missing parsed parameter.
  • The product code is incorrect (that is, not LOAD, UNLOAD, REORG, or OUTPUT).

For more information about return codes, see Job completion and return codes .

User response: If the return code is greater than 4, correct the syntax error and resubmit the job.  For more assistance, contact BMC Software support.

SMARTSWITCH PROCESSING status. QUICKEXIT OUTPUT CAN BE FOUND IN BMC AMI Utilities DD SYSERROR. QUICKEXIT RC=returnCode

Explanation: If the return code is greater than 4, the QUICKEXIT was unsuccessful. RC=00000008 means that the UTILITY-ID was not found.

The return code (returnCode variable) from a job with a restart parameter value of QUICKEXIT can take the following values:

• RC=00000000, if all objects completed
• RC=00000004, if any object was not processed
• RC=00000008, if QUICKEXIT failed, or the UID was not found
• RC=00000016, if QUICKEXIT failed while in the copy phase of reorganization or load

User response: If RC=00000016, run TERM again. For more information about return codes, see Job completion and return codes.

SMARTSWITCH PROCESSING {SUCCESSFUL | UNSUCCESSFUL}. FORCEID OUTPUT CAN BE FOUND IN BMC AMI Utilities DD SYSERROR. FORCEID RC=returnCode

Explanation: If the the return code is equal to or less than 4, the FORCEID was successful. If the return code is greater than 4, the FORCEID was unsuccessful.

User response: If the return code is greater than 0, see the explanation in BMC AMI Utilities DD SYSERROR.

SMARTSWITCH FORCEID COMMAND NOT EXECUTED BECAUSE PHASE NOT = 'NGTUTIL' OR OPTION SETTING SMARTSWITCH=NO

Explanation: The FORCEID restart parameter has not processed because the SMARTSWITCH option in the options module is set to NO or the utility phase name is not NGTUTIL.

User response: If SMARTSWITCH=NO in the product options module, change the setting to SMARTSWITCH=YES and rerun the job.

SMARTSWITCH FORCEID COMMAND NOT EXECUTED BECAUSE UTILID utilityID IS IN USE BY ANOTHER JOB.

Explanation: The utility requested for FORCEID by the indicated utility ID is in EXECUTION PHASE (PHASE = X) and cannot be terminated. The utility ID will remain in the NGT checkpoint, and in the BMCSYNC or BMCUTIL table in the classic utility.

User response: Retry the FORCEID command when the utility is not in the EXECUTION PHASE.

ERROR PARSING TABLE CHECK CONSTRAINT: constraintName

Explanation: The utility cannot parse the check constraint. The text of the table check constraint immediately follows this message. The utility might have encountered conditions that it does not allow when parsing table check constraints. An @ sign is displayed under the symbol that caused the parsing error. Processing continues as though you had specified ENFORCE NO, and the utility sets CHECK pending (CHKP) if applicable. A previous message usually describes the error.

User response: If you received this message when running CHECK PLUS, run the IBM CHECK DATA utility to remove the CHKP status. If you received this message when running any other utility, run CHECK PLUS or the IBM CHECK DATA utility to remove the CHKP status. Resubmit the job, if required.

'keywordString1' CHANGED TO 'keywordString2' DUE TO reason FOR PART partitionNumber

Explanation: The utility changed the first combination of keywords (keywordString1) to the second string (keywordString2) for the indicated reason. For more information, see the description of the keywords in Chapter 3 or in Appendix A of the reference manual for this utility. Processing continues.

User response: No action is required.

UNEXPECTED END-OF-LINE REACHED IN CHECK CONSTRAINT

Explanation: The utility encountered an unexpected end-of-line while processing table check constraints. Processing continues, but the utility does not check table check constraints and sets the status to CHECK pending (CHKP). (For LOADPLUS users, LOADPLUS sets CHKP only when the value of the CHECKPEND option is YES.)

User response: If you received this message when running CHECK PLUS, run the IBM CHECK DATA utility to remove the CHKP status. If you received this message when running any other utility, run CHECK PLUS or the IBM CHECK DATA utility to remove the CHKP status. Correct the problem and resubmit the job, if required.

COLUMN 'columnName1' AND COLUMN 'columnName2' DO NOT HAVE IDENTICAL COLUMN DEFINITIONS

Explanation: Two columns have table check constraints defined but their column definitions are not identical. Processing continues, but the utility does not check table check constraints and sets the status to CHECK pending (CHKP). (For LOADPLUS users, LOADPLUS sets CHKP only when the value of the CHECKPEND option is YES.)

User response: Run CHECK PLUS or the IBM CHECK DATA utility to remove the CHKP status. Correct the problem and resubmit the job, if required.

SCALE IS NOT ALLOWED FOR 'columnName' BECAUSE IT REFERENCES A DECFLOAT COLUMN

Explanation: You included the SCALE option on a field specification for a column that is defined with the DECFLOAT data type. The utility terminated.

User response: Correct your field specification and resubmit the job.

VALUE 'value' IS INCOMPATIBLE WITH DECIMAL(precision,scale) DEFINITION

Explanation: You specified a value for the SET keyword of the UPDATE statement, but the value is not compatible with the column definition. Message BMC50124 provides additional information.

User response: Correct your UPDATE statement and resubmit the job.