Messages BMC50200 through BMC50299

CAF ERROR RC = returnCode, REASON = X'reasonCode': explanation

Explanation: This message usually accompanies a preceding message and provides more specific information about a Db2 call attachment facility (CAF) error. The following list describes some of the most likely explanations:

• The plan is not bound on the specified Db2 subsystem.

• You are not authorized to run the plan.

• The maximum number of threads has been reached.

• The CAF release level does not match the release level of the Db2 subsystem.

User response: Check the IBM DB2 messages and codes documentation for an explanation of the indicated reason code. Correct the problem and resubmit or restart the job.

CAF ERROR RC = returnCode, REASON = X'reasonCode': explanation

Explanation: This message provides more specific information about a Db2 call attachment facility (CAF) error.

User response: No action is required.

DB2 IS NOT OPERATIONAL

Explanation: The Db2 subsystem is not currently active. For more information, see message BMC50201S.

User response: Resubmit the job when the Db2 subsystem becomes active.

CANNOT CONNECT TO DB2 - module

APIMessage

Explanation: The utility cannot connect to the Db2 subsystem. The message text provides additional information about the connection problem.

User response: Correct the problem and resubmit the job.

CANNOT OPEN PLAN 'planName'

Explanation: The utility cannot open the plan. The following list describes some of the reasons that you might receive this message:

• The plan is not bound on the Db2 subsystem.

• You are not authorized to run the plan.

• The maximum number of threads has been reached.

User response: Correct the appropriate problem, based on this message and BMC50201S, and resubmit the job.

UNEXPECTED SQL ERROR. SQLCODE = SQLCode, STMTID = 'statementID'

Explanation: The utility encountered an unexpected SQL error. The SQL statement is uniquely identified by statementID. The utility terminated processing. For more information, see accompanying message BMC50207I.

User response: In many instances, the utility automatically retries -911 and related timeout-due-to-deadlock errors. If you understand the problem (for example, an SQL timeout error), correct the problem and restart the job.

DSNTIAR RETURNED WITH RC = returnCode

Explanation: An SQL error occurred and Db2's message format routine (DSNTIAR) was invoked to format information from the SQL communication area (SQLCA). However, DSNTIAR returned a nonzero return code.

User response: See message BMC50205S for the SQLCODE. If you cannot determine the error from this information, contact BMC Support.

DSNTIARMessage

Explanation: This message is returned from Db2's message format routine (DSNTIAR).

User response: For more information, see the IBM DB2 messages and codes documentation.

DB2 COMMAND 'command' RC = returnCode, REASON CODE = reasonCode

Explanation: The Db2 command shown in this message returned a nonzero return code. The utility terminated processing.

User response: Resubmit the job. If the job fails again, contact BMC Support.

messageText

Explanation: The text of this message is generated by a non-BMC program that the currently running utility invokes.

User response: For information, see the appropriate product's messages and codes documentation.

UNSUPPORTED COLUMN TYPE OF 'columnType' FOR COLUMN 'columnName', TABLE 'tableCreator.tableName'

Explanation: This version of the utility does not support the column type for this column. The utility terminated processing.

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

[condition] objectType 'objectName' DOES NOT EXIST

Explanation: The object that was specified does not exist. The utility terminated processing. The most likely reason for receiving this message is that the object that was specified on the utility command does not exist. However, you might also receive this message for one of the following reasons:

• The BMC common utility tables were not installed correctly.

• One of the utility's synonyms was renamed.

• An unsupported object type is participating in the utility operation (for example when you are unloading from a view that points to a global temporary table).

• You specified an option that indicates that a particular type of object should exist (for example, CLONE), but the object does not exist.

User response: Ensure that the object is spelled correctly on the utility command and that the correct Db2 subsystem ID was specified. Otherwise, correct the problem based on the information in the explanation for this message. Resubmit the job.

objectType 'objectName' IS NOT PARTITIONED

Explanation: The PART keyword was specified, but the table space or index that was specified is not partitioned. The utility terminated processing.

User response: Ensure that the correct table space or index and the correct Db2 subsystem ID are specified. Resubmit the job.

objectType 'objectName' DOES NOT HAVE A PARTITION NUMBER partitionNumber

Explanation: The PART keyword option with the indicated partition number was specified, but the table space or index that was specified does not have this partition. The utility terminated processing.

User response: Ensure that the correct table space or index, correct partition numbers, and Db2 subsystem ID are specified. Resubmit the job.

NO CLUSTER INDEX DEFINED FOR PARTITIONED TABLESPACE 'databaseName.tableSpaceName'. PROCESSING TERMINATED

Explanation: A partitioned table space was specified that either does not have a table defined or does not have a clustering index defined. The utility terminated processing.

User response: Define the table or clustering index and resubmit the job.

TABLE 'tableCreator.tableName' HAS A PRIMARY KEY, BUT NO UNIQUE INDEX HAS BEEN CREATED FOR THE PRIMARY KEY

Explanation: A table that has a primary key defined was specified, but no unique index exists for the primary key. The utility terminated processing.

User response: Ensure that the correct unique index for the primary key is created and resubmit the job.

TABLE 'tableCreator1.tableName1' and TABLE 'tableCreator2.tableName2' DO NOT RESIDE IN THE SAME TABLESPACE

Explanation: The utility cannot perform the action on the requested tables because they do not reside in the same table space. The utility terminated processing.

User response: Ensure that the correct table names are specified and that they are in the same table space. Resubmit the job.

TABLESPACE 'databaseName.tableSpaceName' DOES NOT CONTAIN TABLE 'tableCreator.tableName'

Explanation: The indicated table space does not contain the table that was specified in the SELECT, DELETE, or UPDATE option. The utility terminated processing.

User response: Ensure that the correct table or table space names are specified and resubmit the job.

TABLE 'tableCreator.tableName' DOES NOT CONTAIN COLUMN 'columnName'

Explanation: The indicated table does not contain the column that was specified in the command and the utility terminates processing.

User response: Ensure that the correct column or table was specified. Then, resubmit the job.

TABLE 'tableCreator.tableName' DOES NOT CONTAIN COLUMN 'columnName'

Explanation: A check constraint on the indicated table specifies a column that the table does not contain. The utility continues processing, but does not process any check constraints.

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

TABLE 'tableCreator.tableName' HAS ONE OR MORE UNIQUE CONSTRAINTS, BUT NOT ALL UNIQUE INDEXES HAVE BEEN CREATED

Explanation: The table has one or more unique constraints, but not all of the required unique indexes exist. The utility terminated processing.

User response: Create unique indexes for all unique constraints and resubmit the job.

STOGROUP 'storageGroupName' DOES NOT CONTAIN ANY VOLUMES

Explanation: No volumes are specified in the indicated storage group. The utility terminated processing.

User response: Ensure that the storage group for the table space has volumes and resubmit the job.

DB2 OBJECT DEFINITION(S) HAVE CHANGED PRIOR TO UTILITY RESTART. UNABLE TO PROCEED

Explanation: The utility detected that Db2 internal identifiers have changed since the initial execution of the utility. The utility is unable to proceed.

User response: Terminate the utility and take any other actions to make the affected Db2 objects usable. To determine whether the objects are usable, see the reference manual for the utility that you are running.

TABLE tableCreator.tableName DEFINITION IS INCOMPLETE: explanation

Explanation: The table on which the utility is operating is missing a required object, such as an auxiliary table or index. The explanation provides information about this missing object. The utility terminated processing.

User response: Complete the definition of the table to include the required object. Resubmit the utility job.

query QUERY RETURNED A CHARACTER THAT COULD NOT BE CONVERTED AND THAT WAS REPLACED WITH A SUBSTITUTION CHARACTER

Explanation: The query contains a substitution character for a Unicode character that cannot be represented in EBCDIC. The character cannot be converted back to Unicode, and the job ends with return code 8.

User response: You cannot run the utility on the specified object. If you must run the utility on the object, first change the name of the object and then resubmit the job.

THE SUPPLIED value IS LONGER THAN ALLOWED FOR THIS VERSION OF DB2. TABLE tableCreator.tableName

Explanation: The value indicated in the message is longer than the version of Db2 that you are running supports.

User response: Correct the value and resubmit the job.

PARTITION ADDED BY DB2 BEFORE POINT OF CONSISTENCY ESTABLISHED. PARTITIONS AT UTILITY START: numberOfPartitions CURRENT PARTITIONS: numberOfPartitions

Explanation: Db2 added a partition to a partition-by-growth table space after the utility retrieved the object definition from the Db2 catalog or DBD, but before the utility established a point of consistency.

User response: Rerun the utility job.

RETRY COUNT EXHAUSTED

Explanation: This message follows message BMC50242I if all of the retry attempts failed.

User response: Contact BMC Support.

PRIQTY/SECQTY HAVE CHANGED FOR 'dataSetName' (PRIQTY + 123 * SECQTY < MULTI-DS BOUNDARY)

Explanation: When restarting, the utility detected a change in PRIQTY, SECQTY, or both for the indicated data set. When the utility was initially started, it determined that this data set needed to be a multi-data-set object. The multi-data-set definition requirement is either 2 gigabytes (the traditional size for a multi-data-set object) or PIECESIZE (if this index is nonpartitioned). The utility terminated processing.

User response: If the object is a traditional multi-data-set object, change the PRIQTY or SECQTY (or both) for the data set or corresponding Db2 object so that PRIQTY + 123 * SECQTY is greater than or equal to 2 gigabytes and restart the utility. If the object is an index that is defined with PIECESIZE, the utility will not recognize a change in PIECESIZE between phases. Change the PRIQTY or SECQTY (or both) so that PRIQTY + 123 * SECQTY is greater than or equal to the PIECESIZE value that was in effect when the utility initially started.

'objectCreator.objectName' IS NOT A LOCAL DB2 OBJECT

Explanation: The utility attempted to operate on an object based on an alias that defines the object on a foreign Db2 subsystem. The utility can process only local objects and, therefore, terminates processing.

User response: Change the utility command to operate on a supported object and restart the job.

VIEW DEFINITION FOR VIEW 'viewCreator.viewName' NOT SUPPORTED, REASON CODE=reasonCode

Explanation: The utility encountered an unsupported view definition for the reason code shown in this message. The following table describes the reason codes that might be displayed with this message:

User response: Use a view that does not violate the restrictions indicated by the reason codes, or unload the data directly from the table that the view references.

UNSUPPORTED TABLESPACE TYPE 'tableSpaceType' for 'databaseName.tableSpaceName'

Explanation: The utility attempted to run on a table space that is defined with the indicated type, which the utility does not support. The utility terminated processing.

User response: If the wrong table space was specified, correct the command and resubmit the job.

CANNOT LOAD EDITPROC 'editProcedure', TABLE = 'tableCreator.tableName'

Explanation: The utility attempted to load the EDITPROC but could not find it, or the utility did not have enough memory to load the EDITPROC. The utility terminated processing.

User response: Ensure that the module is available in your LINKLIST, JOBLIB, or STEPLIB. The module is usually found in the load library ssid.DSNEXIT. Ensure that you specified a large enough region size. Correct the problem and resubmit the job.

CANNOT LOAD VALIDPROC 'validationProcedure', TABLE = 'tableCreator.tableName'

Explanation: The utility attempted to load the validation routine but could not find it, or the utility did not have enough memory to load the VALIDPROC. The utility terminated processing.

User response: Ensure that the module is available in your LINKLIST, JOBLIB, or STEPLIB. The module is usually found in the load library ssid.DSNEXIT. Ensure that you specified a large enough region size. Correct the problem and resubmit the job.

CANNOT LOAD FIELDPROC 'fieldProcedure', TABLE = 'tableCreator.tableName', COLUMN = 'columnName'

Explanation: The utility attempted to load the FIELDPROC but could not find it, or the utility did not have enough memory to load the FIELDPROC. The utility terminated processing.

User response: Ensure that the module is available in your LINKLIST, JOBLIB, or STEPLIB. The module is usually found in the load library ssid.DSNEXIT. Ensure that you specified a large enough region size. Correct the problem and resubmit the job.

CANNOT LOAD DATE/TIME ROUTINE 'routineName'

Explanation: The utility attempted to load the indicated routine but could not find it, or the utility did not have enough memory to load the routine. The utility terminated processing.

User response: Ensure that the module is available in your LINKLIST, JOBLIB, or STEPLIB. The module is usually found in the load library ssid.DSNEXIT. Ensure that you specified a large enough region size. Correct the problem and resubmit the job.

EDITPROC 'editProcedure' RETURN CODE = returnCode, REASON CODE = reasonCode

Explanation: The EDITPROC returned a nonzero return code. The utility terminated processing.

User response: Contact the author of the EDITPROC to correct the problem. (The EDITPROC is not part of the utility product.) Resubmit the job if appropriate.

EDITPROC 'editProcedure' HAS MODIFIED STORAGE BEYOND THE END OF THE OUTPUT AREA

Explanation: The EDITPROC encountered an error. The utility terminated processing. For more information, see Db2 reason code 00C90103 in the IBM DB2 messages and codes documentation.

User response: Contact the author of the EDITPROC to correct the problem. (The EDITPROC is not part of the utility product.) Resubmit the job if appropriate.

EDITPROC 'editProcedure' RETURNED LENGTH = length; EXPECTING LENGTH <= THE MAXIMUM ROW LENGTH

Explanation: The EDITPROC encountered an error. The utility terminated processing. For more information, see Db2 reason code 00C90103 in the IBM DB2 messages and codes documentation.

User response: Contact the author of the EDITPROC to correct the problem. (The EDITPROC is not part of the utility product.) Resubmit the job if appropriate.

DATE/TIME ROUTINE 'routineName' RETURN CODE = returnCode, REASON CODE = reasonCode

Explanation: The routine returned a nonzero return code. The utility terminated processing.

User response: Contact the author of the routine to correct the problem. (The date/time routine is not part of the utility product.) Resubmit the job if appropriate.

FIELDPROC 'fieldProcedure' RETURN CODE = returnCode, REASON CODE = reasonCode, MESSAGE TOKEN = 'text'

Explanation: The FIELDPROC returned a nonzero return code. The utility terminated processing.

User response: Contact the author of the FIELDPROC to correct the problem. (The FIELDPROC is not part of the utility product.) Resubmit the job if appropriate.

VALIDPROC 'validationProcedure' RETURN CODE = returnCode, REASON CODE = reasonCode

Explanation: The VALIDPROC returned a nonzero return code. The utility terminated processing.

User response: Contact the author of the VALIDPROC to correct the problem. (The VALIDPROC is not part of the utility product.) Resubmit the job if appropriate.

CANNOT LOAD DB2 AUTHORIZATION EXIT 'DSNX@XAC', USING DB2 CATALOG FOR UTILITY AUTHORIZATION

Explanation: The utility attempted to load the Db2 security exit but could not find it, or memory was insufficient to load the exit. The utility should find this exit even if the utility is not actively using the exit for Db2 security authorization. However, the utility continues processing.

User response: Ensure that the module is available in your LINKLIST, JOBLIB, or STEPLIB. The module is usually found in the load library ssid.DSNEXIT. Ensure that you specified a large enough region size. Correct the problem and resubmit the job if necessary.

WILL RETRY n MORE TIMES

Explanation: The utility was unable to complete the operation identified in preceding messages. The utility retries the operation until it reaches the number of retries specified in the SQLRETRY installation option.

User response: No action is required.

CLONED PARTITION-BY-GROWTH OBJECT PAIR DOES NOT HAVE AN EQUAL NUMBER OF PARTITIONS. NUMBER OF PARTITIONS AT UTILITY START: startingNumber, CURRENT PARTITIONS: currentNumber

Explanation: You were running a utility on a partition-by-growth table space and one of the following conditions occurred:

• While the utility was running on a clone table, a partition was added to the base table.

• While the utility was running on a base table that is participating (or has participated) in a clone relationship, a partition was added to the clone table.

User response: Rerun the utility.

PROCESSING PAGESET DBID(dbid) PSID(psid) PART(partitionNumber) THAT MIGHT CONTAIN VERSIONED DATA

Explanation: The utility is processing an object that might contain table rows that are not at the current version. This message provides diagnostic information for message BMC50246S.

User response: No action is required.

REGISTERING type PAGE - pageNumber FOR DBID(dbid) PSID(psid)

Explanation: The utility is processing an object that might contain table rows that are not at the current version. This message provides diagnostic information for message BMC50246S.

User response: No action is required.

UNABLE TO PROCESS ROW recordID FOR OBID obid. REASON: explanation

Explanation: The utility was unable to process the row. This error usually occurs for one of the following reasons:

• The utility expected the row to be at the current version of the table.

• The utility was unable to convert the row's version to the current version of the table.

User response: Contact BMC Support and provide the information in this message and any preceding diagnostic messages such as BMC50244I and BMC50245I.

taskNumber: PAGE pageNumber IN 'dataSetName' HAS PGLOGRBA rba/lrsn WHICH IS GREATER THAN THE CONSISTENCY RBA, FAILURE IN SNAPSHOT

Explanation: The software snapshot function of XBM or SUF failed to provide a consistent copy of the object. The utility terminated processing.

User response: If you are in a data sharing environment, ensure that each active Db2 member of the data sharing group in which you are running also has an active XBM subsystem. Each active XBM subsystem must be joined to the same XBM group. After you have established the correct XBM environment, resubmit the job. If your XBM environment is correct and you still receive this message, contact BMC  Support. If you are not running in a data sharing environment, contact BMC Support.

taskNumber: PAGE pageNumber IN 'dataSetName' IS A ZERO PAGE

Explanation: While attempting to read a data page from the indicated data set in a nonsegmented table space, the utility encountered a page (pageNumber) numbered zero. The task number identifies the task that is associated with the error.

User response: No action is required. The utility continues normal execution.

taskNumber: PAGE pageNumber PGCOMB INCONSISTENT WITH TRAILER BYTE

Explanation: The utility found that the PGCOMB field is inconsistent with the page trailer byte for the specified page, indicating that the page might not have been successfully written. The indicated page number is the physical page for which the inconsistency occurred.

User response: Recover the table space and resubmit your job.

THE HEADER PAGE INDICATES THE objectType objectName IS status, BUT THE CATALOG SAYS IT IS status

Explanation: Status information on the object's header page does not match the information in the Db2 catalog. This error occurs, for example, when the following information does not match:

• compression status

• table space type

  This error usually occurs when DSN1COPY was used to copy data into a table space that is not defined in the same way as the table space from which the data was copied.

User response: Verify the information (for example, table space type or compression definition) that was specified when the table space or index space was created. Recover the object.

taskNumber: PAGE pageNumber IN 'dataSetName' IS UNRECOGNIZABLE, DATA = X'data'

Explanation: The utility encountered a page (pageNumber) that it did not expect. This problem might be due to an inline or incremental copy issue. The task number identifies the task that is associated with the error. The data that this message displays is nine bytes long, starting at offset X'08' in the page. The page number includes settings of high-order bits for individual partitions in a partitioned table space.

User response: For utilities that support this syntax, specify the INFILE ddname FULL INLINE YES option for inline copies or the INFILE ddname INCREMENTAL option of incremental copies, and resubmit the job. Otherwise, if you have determined that the Db2 data set does not contain any errors, contact BMC Support.

taskNumber: PAGE pageNumber IN 'dataSetName' IS BROKEN

Explanation: The utility encountered a page that is marked broken. The task number identifies the task that is associated with the error.

User response: Recover the table space and resubmit the job.

taskNumber: DBID 'dbid' AND/OR PSID 'psid' DO NOT MATCH THOSE FOUND IN DATASET 'dataSetName'

Explanation: The database identifier (DBID) and the page set identifier (PSID) do not match the identifiers in the indicated data set. The task number identifies the task that is associated with the error.

User response: If you use DSN1COPY, ensure that the data set was recovered correctly and that the DBID and the object IDs were not changed. For REORG PLUS and UNLOAD PLUS users, if you receive this message and want to restart the job without making any changes, specify the ON MESSAGE option for this message and restart the job.

taskNumber: DBID 'dbid' AND/OR PSID 'psid' DO NOT MATCH THOSE FOUND IN DATASET 'dataSetName'

Explanation: The database identifier (DBID) and the page set identifier (PSID) do not match the identifiers in the indicated data set. The task number identifies the task that is associated with the error. For REORG PLUS users, REORG PLUS resets the DBIDs and PSIDs to match the identifiers that are in the catalog.

User response: No action is required.

taskNumber: UNEXPECTED EOF (PAGE= pageNumber) IN DATASET 'dataSetName'

Explanation: The utility encountered an end-of-file (EOF) when it expected more data. The task number identifies the task that is associated with the error. For LOADPLUS and REORG PLUS, if the job terminates during ANALYZE processing, this message might indicate that some system pages have not been externalized. For REORG PLUS users, receiving this message might have one of the following explanations:

• If REORG PLUS terminates during ANALYZE processing for a table space reorganization with ANALYZE, ANALYZE ONLY, or ANALYZE PAUSE specified, this message might indicate that an index space does not contain valid Db2 pages.

• If REORG PLUS terminates during UNLOAD phase processing, this message might indicate that the primary (PRIQTY) or secondary (SECQTY) quantity for the table space or index space was altered before the reorganization began. This alteration makes the multi-data-set table space or index space a nonmulti-data-set table space or index space.

User response: For LOADPLUS and REORG PLUS users, if you receive this message during ANALYZE processing, try resubmitting the job. If the problem continues, consider running a QUIESCE on the object to force externalization of all system pages, and resubmit the job. If the problem continues, the message indicates a different problem. For REORG PLUS users who receive this message due to changing PRIQTY and SECQTY, ALTER the PRIQTY and SECQTY values back to the original values to create a multi-data-set table space or index space and restart the reorganization. For other scenarios, the table space or index might be in error and you might need to recover the object. For REORG PLUS and UNLOAD PLUS users, if you receive this message and want to restart the job without making any changes, specify the ON MESSAGE option for this message and restart the job. For an index space reorganization, consider an appropriate recovery scenario.

taskNumber: DATASET 'dataSetName' DOES NOT CONTAIN AN INDEX

Explanation: The data set does not contain a Db2 index. The task number identifies the task that is associated with the error.

User response: If you use DSN1COPY, ensure that the data set was recovered correctly. If you understand the problem, correct it and restart the job. For more help, contact BMC Support.

taskNumber: A KEY OR RID MISMATCH WAS FOUND FOR INDEX 'indexCreator.indexName' , KEY = X'key'. 'REBUILD INDEX' MAY BE REQUIRED

Explanation: The utility attempted to use one or more partitions of a partitioned table space that required the utility to update corresponding entries in the indicated index. However, either too few or too many key/RID pairs were found in the index for the specified partitions.

User response: Rebuild the index after the partitions are successfully reloaded.

taskNumber: A DUPLICATE KEY VALUE HAS BEEN DETECTED IN UNIQUE INDEX 'indexCreator.indexName', RID = X'recordID'

Explanation: For REORG PLUS, this message indicates one of the following conditions:

• For a clustering index, REORG PLUS detected a duplicate key while rebuilding the table space. REORG PLUS built the index using only the first RID of the duplicate keys and placed the index in rebuild pending (RBDP) status. The rows corresponding to the duplicate key entries remain in the table space. Message BMC50259E follows this message and provides the affected key.

• For a nonclustering index, REORG PLUS detected a duplicate key while building the index and terminated. The status of the objects depends on the value of the SHRLEVEL option:

  • If SHRLEVEL CHANGE was in effect, the object is available but the duplicate key still exists.

  • If SHRLEVEL REFERENCE was in effect, the object is left in read-only status but the duplicate key still exists.

  • If SHRLEVEL NONE was in effect, REORG PLUS stopped the table space and index and placed the index in RBDP status.

User response: For REORG PLUS users, consider the following responses:

• For a clustering index, correct the duplicate entries in the table space and rebuild the index.

• For a nonclustering index when SHRLEVEL REFERENCE or SHRLEVEL CHANGE was in effect, correct the duplicate entries and rebuild the index.

• For a nonclustering index when SHRLEVEL NONE was in effect, recover the table space, correct the duplicate entries, and rebuild the index.

• If the job completed with return code 8, either reload the data correctly (use UNIQUECHECK YES or correct your input data) or recover the table space and indexes.

• If the job completed with return code 0, LOADPLUS deleted your duplicates; therefore, LOADPLUS did not load some of the data that you expected it to load. This message and message BMC50259E provide information to help you identify the duplicate key and table space rows.

KEY = X'key'

Explanation: This message provides the affected key for the error described in message BMC50258E.

User response: See the user response for message BMC50258E.

SPACE 'databaseName.spaceName' IS NOT STARTED ACCESS(RO)

Explanation: When you restarted the utility, it determined that the space was not started in ACCESS(RO) state, as it should have been.

User response: If you are sure that no changes have been made to the space or associated objects (such as dropping or creating an index or updating via SQL), you can start the space ACCESS(RO) and restart the job. If you are not sure whether changes have been made, terminate the utility and start again. If you terminate the utility, you might have to recover the table space and any associated indexes first and then resubmit the job. For specific information about restarting the job, see the reference manual for the utility that you are running.

SPACE 'databaseName.spaceName' ALREADY IN USE BY A DB2 UTILITY

Explanation: The table space or associated index spaces that you requested to use are already marked UTRO, UTRW, or UTUT.

User response: Wait for the Db2 utility to complete or terminate the Db2 job before restarting the BMC utility job.

SPACE 'databaseName.spaceName' ALREADY IN USE BY A BMC UTILITY, UTILID = 'utilityID'

Explanation: A BMC utility is currently using the table space or associated index spaces that you requested.

User response: Wait for the other utility to complete or terminate the job. Review the restart parameter that is included in the job and ensure that the value is appropriate for the job. Resubmit the job.

SPACE 'databaseName.spaceName' IS IN 'CHECK PENDING' STATE

Explanation: The space is marked CHECK pending (CHKP).

User response: Run the CHECK PLUS product or the IBM CHECK DATA utility to remove the CHKP status and resubmit the job.

SPACE 'databaseName.spaceName' IS NOT STARTED

Explanation: The table space or associated index space that you requested to use is not started RW, RO, or UT.

User response: Start the table space or index space that is shown in this message and restart the job.

SPACE 'databaseName.spaceName' CANNOT BE STOPPED. IT MAY BE IN USE

Explanation: The table space or index space (or both) that you requested to use cannot be stopped. The utility issued the STOP command and is waiting for execution.

User response: The space is marked stop pending (STOPP) until no other jobs are using it. Wait for the object to be stopped and then restart the job. Other activity within the Db2 subsystem, such as active log dumps, can delay processing of the STOP command. Examine any BMC50209I messages (which might display outstanding locks on the space) or the DSNMSTR address space to identify the currently running jobs that are preventing the command from being processed. For REORG PLUS users, if you specified ON FAILURE TERMINATE, REORG PLUS attempts to start the space in its original status. Because other activity within the Db2 subsystem can interfere with this attempt, you should verify that all spaces are in the appropriate status before resubmitting your job. If you receive this message and you are operating on a large number of partitions, consider increasing the value of your STOPRETRY installation option. For guidelines, see the reference manual for the utility that you are running.

SPACE 'databaseName.spaceName' IS NOT STOPPED

Explanation: When you restarted the utility, it determined that the space was not stopped when it should have been.

User response: If you are sure that no changes have been made to the space or associated objects (such as dropping or creating an index), you can stop the space and restart the job. If you are not sure whether changes have been made, terminate the utility and start again. If you terminate the utility, you might have to recover the table space and any associated indexes first and then resubmit the job. For specific information about restarting the job, see the reference manual for the utility that you are running.

SPACE 'databaseName.spaceName' CANNOT BE STARTED ACCESS(RO). IT MAY BE IN USE

Explanation: The utility attempted to start a Db2 space with START ACCESS(RO). The table space could not be started with ACCESS(RO).

User response: The table space might have been in use. Because of the failure, the table space might now be in RO state. Start the table space in the correct state and resubmit the job.

SPACE 'databaseName.spaceName' [PART partitionNumber] IS IN 'status' STATE AND WILL NOT BE QUIESCED

Explanation: No quiesce on the space will be performed because the space is in the indicated state.

User response: To ensure that all updated pages in the buffer pool are processed, issue a STOP and then START on the space before running the job.

CHECK PENDING STATUS HAS BEEN action FOR databaseName.tableSpaceName [PART partitionNumber]

Explanation: The status for the table space or partition has changed as indicated in this message. The specified action can be either SET (ON) or RESET (OFF).

User response: If CHECK pending status (CHKP) is set, run CHECK PLUS with the CHECK DATA option, or run the Db2 CHECK DATA utility with SCOPE ALL on the corresponding table space or table space partition. Doing so ensures that no referential integrity or Db2 table check constraints are violated.

ATTEMPTING TO START SPACE 'databaseName.spaceName'...

Explanation: You specified the ON FAILURE TERMINATE option and the utility is terminating due to an error. The utility is attempting to start the space.

User response: No action is required.

SPACE 'databaseName.spaceName' IS STARTED

Explanation: The utility successfully started the space after terminating due to an error. Message BMC50271I always precedes this message.

User response: No action is required.

SPACE databaseName.tableSpaceName PART partitionNumber WILL REMAIN IN CHECK PENDING STATUS

Explanation: The table space or partition was already in CHECK pending status (CHKP), and the utility responded in one of the following ways:

• The utility processed the object but did not reset CHKP. This occurs, for example, when you specify LOAD RESUME.

• The utility bypassed the object.

User response: No action is required.

SPACE 'databaseName.spaceName' IS IN 'status' STATE AND PREVENTS UTILITY FROM RUNNING

Explanation: The utility that you are running cannot complete the job because the table space or index space is in the indicated pending state.

User response: Start the space in an allowable state and resubmit the job, or specify different utility options (for example, REORG SHRLEVEL NONE instead of REORG SHRLEVEL CHANGE) and resubmit the job. For information about allowable statuses for various utility options, see the object status section of the reference manual for the utility that you are running.

SPACE 'databaseName.spaceName' HAS AN ERROR RANGE. RECOVERY IS NEEDED

Explanation: The table space or index space has an error range indicated by Db2.

User response: Recover the table space or index space by using the ERROR RANGE option of the Db2 RECOVER utility.

XBM 'requestType' ERROR. RC=returnCode, REASON=reasonCode, DSN='dataSetName'

Explanation: The indicated XBM error occurred during the snapshot process. Message BMC50278E might accompany this message.

User response: Correct the error and resubmit the job. For questions about the XBM error, contact BMC Support.

XBM STATISTICS: DSN='dataSetName', READS=n, HITS=n, WRITES=n, CACHE=n

Explanation: The snapshot function is complete. This message provides statistical information about the snapshot operation.

User response: No action is required.

XBMMessage

Explanation: XBM experienced an error and passed this message text to the utility for output.

User response: Take corrective action appropriate to the XBM error that is reported and resubmit the job. If you received the message that Instant Snapshot is not allowed by the SSI component, complete one of the following actions:

• Enable Instant Snapshot in your SSI component options. For additional information, see the EXTENDED BUFFER MANAGER and SNAPSHOT UPGRADE FEATURE User Guide.

• Using the XBMID option of the utility that you are running, specify an XBM subsystem on which Instant Snapshot is already enabled.

SPACE 'databaseName.spaceName' CANNOT BE STARTED ACCESS(UT). IT MAY BE IN USE

Explanation: The utility attempted to start a Db2 space in ACCESS(UT) state. The attempt failed.

User response: The space might be in use. Start the table space in the correct state and resubmit the job.

keywords NOT SUPPORTED IN A DATA-SHARING DB2 SUBSYSTEM

Explanation: In a data sharing Db2 subsystem, you cannot use the keywords that this message displays.

User response: Correct the command and resubmit the job.

THE BMCUTIL SUBTASK HAS TERMINATED OR TIMED-OUT

Explanation: The utility attempted a SYNC request but the SYNC subtask failed.

User response: To determine the problem, see the preceding messages.

THE BMCUTIL SUBTASK ABNORMALLY TERMINATED WITH SYSTEM ABEND CODE = abendCode

Explanation: The utility SYNC subtask abended.

User response: Review preceding messages or the job log to determine the problem. If you understand the problem (for example, an SQL timeout), correct it and restart the job. Otherwise, contact BMC Support.

THE BMCUTIL SUBTASK ABNORMALLY TERMINATED WITH RETURN CODE = returnCode

Explanation: The utility SYNC subtask abended.

User response: Review preceding messages or the job log to determine the problem. If you understand the problem (for example, an SQL timeout), correct it and restart the job. Otherwise, contact BMC Support.

RETRYING SQL -911 ON STMT description. RETRIES REMAINING=n. WAIT TIME = time SECS PLUS DB2 WAIT TIME

Explanation: The utility encountered an SQL -911 return code while processing the SQL statement indicated in this message, performing the specified serialization function, or processing a drain. The utility retries the SQL statement, serialization function, or drain until the utility reaches the number of retries specified in the SQLRETRY or DRNRETRY installation option. The interval between retries (WAIT TIME) is the amount of time specified with the SQLDELAY or the DRNDELAY installation option plus the time that Db2 waits for a timeout or a deadlock, whichever circumstance caused this -911. When the STMT description is PREVENT xx, the utility is performing a drain task. A STMT description that contains an actual statement ID value indicates a SELECT, DELETE, or UPDATE statement.

User response: No action is required.

SQL -911 RETRIES UNSUCCESSFUL. RETRY ATTEMPTS = n

Explanation: This message follows message BMC50284I if all of the SQL retry attempts were unsuccessful. The utility retried the statement the displayed number of times.

User response: Try to restart the utility.

SQL -911 RETRY SUCCESSFUL

Explanation: The utility encountered an SQL -911 return code and retried the statement. This message follows BMC50284I if one of the retries was successful.

User response: No action is required.

REXX ENVIRONMENT FAILURE AT 'description' RETURN CODE = returnCode, REASON CODE = reasonCode

Explanation: A problem occurred while the utility was establishing the environment for a REXX user exit. The utility terminated the job.

User response: If the stated description and reason provide sufficient information for you to correct the problem, correct the problem and resubmit the job. Check your job log for any IRX messages that the REXX environment manager might have issued. If you cannot correct the problem, contact BMC Support.

CANNOT LOAD USER EXIT 'module', TABLE = 'tableCreator.tableName', FIELD = 'fieldName'

Explanation: You specified a user-written exit routine for conversion but the utility cannot load the requested module.

User response: Ensure that the user-written exit routine module is available in your LINKLIST, JOBLIB, or STEPLIB. Ensure that you specify a large enough region size.

USER EXIT 'routineName' RETURN CODE = returnCode, REASON CODE = reasonCode, MESSAGE TOKEN = 'text'

Explanation: The user-written exit routine produced a nonzero return code.

User response: Contact the author of the user-written exit routine. (The user-written exit routine is not part of the utility product.)

DB2 REAL-TIME-STATISTICS - function - FOR utility UTILITY status

Explanation: The function for the utility completed with the status shown in this message. If the status indicates that the real-time statistics function failed, one of the following conditions occurred:

• This feature is not available for the type of utility job that you are running.

• An error with the utility or with Db2 restricted the ability to update the real-time statistics tables.

• The real-time statistics database, tables, or table spaces are not defined.

• The real-time statistics table space is in a restricted status.

User response: No action is required.

BLDL FOR MODULE 'module' FAILED WITH RC = returnCode, REASON = reasonCode

Explanation: The utility issued a BLDL request and the request failed.

User response: Check the job log for more information. Ensure that you specified a large enough region size.

ATTACH FOR 'module' FAILED WITH RC = returnCode

Explanation: The utility tried to attach the module. Either the utility could not find the module, or the utility did not have enough memory.

User response: Ensure that the module is available in your LINKLIST, JOBLIB or STEPLIB. Ensure that you specified a large enough region size.

CANNOT LOAD MODULE 'module' [CODE = X'abendCode' ; RSN = X'reasonCode']

Explanation: The utility tried to load the module. Either the utility could not find the module or the utility did not have enough memory. If you receive this message as a WTO message before the utility starts execution, the most likely reason for receiving this message is that the product was not installed properly.

User response: Ensure that the module is available in your LINKLIST, JOBLIB, or STEPLIB. Ensure that you specified a large enough region size.

CANNOT LOAD MODULE 'module' [CODE = X'abendCode' ; RSN = X'reasonCode']

Explanation: The utility tried to load the module. Either the utility could not find the module or the utility did not have enough memory. If you receive this message as a WTO message before the utility starts execution, the most likely reason for receiving this message is that the product was not installed properly.

User response: Ensure that the module is available in your LINKLIST, JOBLIB, or STEPLIB. Ensure that you specified a large enough region size.

SYSTEM CATALOG INFORMATION ROUTINE FAILED WITH RC = returnCode, REASON = reasonCode IN MODULE 'module'. DSN = 'dataSetName'

Explanation: The utility tried to retrieve system catalog information for a data set, but the system routine returned a non-zero return code.

User response: Make sure that the indicated data set has not been deleted, uncataloged, or archived. (For example, if the utility's attempt to redefine an object fails in the RELOAD phase of REORG PLUS or the LOAD phase of LOADPLUS, you must manually define the object and restart the job. If none of these circumstances apply, contact BMC Support.

IDCAMS status DURING OBJECT REDEFINITION. SEE JOBLOG FOR IDC MESSAGES

Explanation: IDCAMS succeeded or failed during VSAM data set redefinition. The IDCAMS input and output are displayed in the job log.

User response: No action is required. If the message indicates a failed status, the utility retries the redefinition until it succeeds. If the job ends with a condition code 4, the IDCAMS messages indicate that other volumes in the storage group were used for data set placement.

IDCAMS status DURING OBJECT REDEFINITION. SEE JOBLOG FOR IDC MESSAGES

Explanation: IDCAMS succeeded or failed during VSAM data set redefinition. The IDCAMS input and output are displayed in the job log.

User response: Check the job log for the error. If you understand the problem, correct it and restart the job. If you need assistance, contact BMC Support.

UNABLE TO INVOKE SMS SERVICE ROUTINE 'routineName'

Explanation: The utility cannot use the indicated storage management subsystem (SMS) service routine.

User response: Check the job log for additional messages and ensure that the SMS routines are running from an APF-authorized library. For other problems, contact BMC Support.

SMS SERVICE ROUTINE 'routineName' FAILED WITH RC = returnCode, REASON = reasonCode

Explanation: The indicated storage management subsystem (SMS) service routine failed for the specified reason.

User response: If you recognize the problem, correct it and resubmit the job. Otherwise, contact BMC Support.

LINK TO MODULE 'module' FAILED WITH RC = returnCode, REASON CODE = reasonCode

Explanation: A link to the module failed with the indicated return code and reason.

User response: Check preceding messages or the job log to determine the source of the problem. Review the explanation of the indicated return code and reason in the appropriate manual. If you understand the problem, correct it and restart the job. Otherwise, contact BMC Support.

DYNAMIC ALLOCATION FAILED IN 'module' FOR DDNAME 'ddname', S99ERROR = errorReasonCode, S99INFO = infoReasonCode

Explanation: A dynamic allocation failure occurred.

User response: Check the job log for allocation errors and see the IBM z/OS MVS Programming: Authorized Assembler Services Guide for more information about S99ERROR and S99INFO reason codes. Also, check the job log for messages related to the error. For example, a dynamic allocation error can occur because of an invalid unit specification on the WORKUNIT option in the utility installation options. The IBM TSO/E messages documentation describes messages beginning with IKJ. Correct the problem and restart the job.