Messages BMC50000 through BMC50099

UTILITY EXECUTION STARTING date time...

Explanation: The utility started running at the indicated date and time.

User response: No action is required.

UTILITY ID = 'utilityID'. DB2 SUBSYSTEM ID = 'ssid'. OPTION MODULE = 'module'.

Explanation: This message confirms the utility ID, Db2 subsystem ID, and installation options module that you specified. If you specified a group attachment name in your EXEC statement parameters, that name is the Db2 subsystem ID. For details about specifying these parameters with your EXEC statement, see Chapter 4 of the reference manual for the utility that you are using.

User response: No action is required.

RESTARTING UTILITY: COMMAND = 'command', PHASE = 'phase'

Explanation: The utility that the command indicates is restarting at the indicated phase.

User response: No action is required.

phase PHASE COMPLETE. ELAPSED TIME = time

Explanation: The indicated phase completed in the elapsed time that this message displays.

User response: No action is required.

utility COMMAND EXECUTION PAUSING BEFORE PHASE = 'phase'

Explanation: The indicated utility execution is pausing as the utility command requested.

User response: After modifying your JCL, reallocating Db2 data sets, or changing the utility command, use the RESTART utility parameter and restart the job.

UTILITY EXECUTION COMPLETE, RETURN CODE = returnCode

Explanation: The utility execution completed. A return code that is greater than zero indicates a warning or a problem. For more information about return codes, see the reference manual for the utility that you are running.

User response: If the return code is not zero, check the preceding messages to determine the problem. Otherwise, no action is required.

OBJECT(S) RESET TO ORIGINAL STATUS; STOPPED OUTAGE ELAPSED TIME = time

Explanation: This message indicates how long the objects were in STOP status for a SHRLEVEL CHANGE job. The objects are reset to their original status.

User response: No action is required.

WTOMessage

Explanation: The utility writes the user-defined text of this message to the MVS system log to indicate that the snapshot initialization process completed successfully.

User response: No action is required.

UNABLE TO RESTART UTILITY IN 'phase' PHASE DUE TO PREVIOUS WARNING OR ERROR

Explanation: You attempted to restart the utility but, due to a previously issued warning or error, the job cannot be restarted.

User response: Check preceding warning or error messages or the job log to determine the problem. If you understand the problem, correct it and resubmit the job with the NEW restart parameter. Otherwise, you must recover the table space and any associated indexes and then resubmit the job. For more information associated with restarting your job, see Chapter 4 of the reference manual for the utility that you are running.

UTILITY WITH ID 'utilityID' IS BEING TERMINATED. THE UTILITY CANNOT BE RESTARTED.

Explanation: The utility encountered a problem, described in a previously issued message, and is terminating the current job. Due to the state of the objects, an option value, or the phase of the job, the job cannot be restarted.

User response: Check the preceding messages for information about the problem. Correct the problem, if necessary, and resubmit the utility with the NEW restart parameter.

UTILITY WITH ID 'utilityID' ALREADY EXISTS

Explanation: The utility ID that you specified is in use.

User response: If you are restarting the utility, specify the RESTART utility parameter. Otherwise, choose a different utility ID.

UTILITY EXECUTION TERMINATING, RETURN CODE = returnCode

Explanation: The execution of the utility ended with an error. For more information about the return code, see the reference manual for the utility that you are running.

User response: Check preceding messages to determine the problem. Correct the problem and restart the utility.

UTILITY EXECUTION ABENDED, SYSTEM CODE = abendCode, REASON CODE = reasonCode

Explanation: The execution of the utility ended abnormally. The system abend code and reason code can help determine the reason for the abend.

User response: Check preceding messages or the job log to determine the problem. If you understand the problem (for example, your job was canceled because of insufficient time), correct the problem and restart the utility. Otherwise, contact BMC Support.

UTILITY EXECUTION ABENDED, USER CODE = abendCode, REASON CODE = reasonCode

Explanation: The execution of the utility ended abnormally. The user abend code and reason code can help determine the reason for the abend. For information about these codes, see the 'Codes' chapter of this manual.

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

utility UTILITY WITH ID 'utilityID' NOT FOUND IN BMCUTIL/BMCSYNC

Explanation: You specified the RESTART parameter. Either the utility ID that you specified as the UTILID parameter cannot be found in the BMCUTIL or BMCSYNC table, or the utility ID belongs to another utility.

User response: Ensure that you specified the correct utility ID and restart your job.

utility UTILITY WITH ID 'utilityID' NOT FOUND IN BMCUTIL/BMCSYNC

Explanation: You specified the TERM parameter. Either the utility ID that you specified as the UTILID parameter cannot be found in the BMCUTIL or BMCSYNC table, or the utility ID belongs to another utility.

User response: Ensure that you specified the correct utility ID and restart your job.

RESTART OF 'utility' UTILITY ATTEMPTED WITH UTILITY COMMAND 'command'

Explanation: The utility was restarted with a command that is different from the command that was used for the original execution of the utility. The job terminated.

User response: Submit the job with the correct command to restart the utility.

UTILITY CANCELLED BY USER

Explanation: The row for this utility ID was deleted from the BMCUTIL table. This action canceled the utility.

User response: For UNLOAD PLUS users, the DB2 table or table space that the utility was unloading was not affected. No action is required in this case. For all other utilities, see the associated reference manual for information about making the DB2 object usable after terminating or canceling the utility.

UTILITY REQUESTED TO TERMINATE DUE TO FAILURE IN PHASE 'phase'

Explanation: You specified the ON FAILURE phase TERMINATE option and the utility is terminating abnormally. The utility starts all spaces (when appropriate), and removes the utility ID from the BMCUTIL table.

User response: No action is required.

UTILITY TERMINATED DUE TO 'option' SPECIFICATION

Explanation: The specified option caused the utility job to end.

User response: Review the option information in the reference manual for the utility that you are running. Change the option or object as needed and restart or resubmit the job.

UTILITY TERMINATED DUE TO 'option' SPECIFICATION

Explanation: The specified option caused the utility job to end.

User response: No action is required.

UTILITY PARM 'parameter' IS LONGER THAN n CHARACTERS

Explanation: The parameter on the utility EXEC statement is longer than the maximum number of allowed characters.

User response: Correct the parameter and resubmit the utility job.

SPECIFIED parameter IS NULL. USING DEFAULT.

Explanation: Because you did not specify the indicated parameter on the EXEC statement, the utility is using the default value. For more information about EXEC statement parameters, see the reference manual for the utility that you are running.

User response: No action is required. See also message BMC50002I.

INVALID UTILITY PARM: 'parameter'

Explanation: The indicated EXEC statement parameter was specified incorrectly.

User response: Correct the parameter and resubmit the job.

CONNECTED TO SUBSYSTEM 'ssid'

Explanation: You specified a group attachment name in your EXEC statement parameters, and you are running the utility in a data sharing environment. This message tells you the actual subsystem to which you are connected within the group. This message follows BMC50002I.

User response: No action is required.

OPERATING SYSTEM NOT AT MINIMUM LEVEL OF operatingSystem versionNumber

Explanation: You attempted to run the utility on a version of the operating system that this version of the utility does not support. The utility terminated processing. This message is displayed on the console only.

User response: Upgrade your operating system or use an earlier version of the utility that supports your current operating system.

Z/ARCHITECTURE NOT AVAILABLE ON SYSTEM

Explanation: You attempted to run the utility on a system that is not running in z/Architecture mode, which this version of the utility requires. The utility terminated processing. This message is displayed on the console only.

User response: Upgrade your system or use an earlier version of the utility that does not require z/Architecture mode.

SYSTEM NOT RUNNING IN 64-BIT MODE

Explanation: You attempted to run the utility on a system that is not running in 64-bit mode, which this version of the utility requires. The utility terminated processing. This message is displayed on the console only.

User response: Upgrade your system or use an earlier version of the utility that does not require 64-bit mode.

DB2 MODE = mode [(SKIP MIGRATION PERFORMED)]

Explanation: You are running in the indicated mode (for example, NFM) of the Db2 version that message BMC50471I indicates. If you migrated directly from Db2 version n to Db2 version n + 2 (for example, Db2 Version 8 to Db2 Version 10), this message states that skip migration was performed.

User response: No action is required.

action FOR MODULE 'moduleName' FAILED, CODE = returnCode, RSN = reasonCode

Explanation: The utility tried to perform the specified action on the module but was not successful. Some modules, such as the BMC Common Statistics API, might provide additional messages with more detail about the problem. If you receive this message as a WTO message before the utility starts execution, the most likely reason is that the product was not installed properly.

User response: If action in the message text is LOAD, ensure that the module is available in your LINKLIST, JOBLIB, or STEPLIB. For any other action, if you are able to determine the problem, correct it and rerun the job. Otherwise, contact BMC Support.

MATERIALIZED DOCID COUNT n1 DOES NOT MATCH measure COUNT n2 FOR INDEX databaseName.indexSpaceName

Explanation: You ran the utility after adding an XML column via an ALTER statement, causing the utility to generate values for the document ID index. The utility compared the number of document ID (DOCID) values that it generated against the measure indicated in this message, and they do not match. This discrepancy indicates either a problem with the document ID index or an internal error.

User response: Contact BMC Support.

utility periodType PERIOD WILL EXPIRE IN n DAYS REASON CODE = reasonCode

Explanation: This message is displayed during the last 30 days before the license expiration date that was set when the installation media was created. The periodType is either GRACE or TRIAL. Processing continues.

User response: Contact a BMC sales representative for assistance.

component LICENSE PERIOD WILL EXPIRE IN n DAYS REASON CODE = 0

Explanation: This message is displayed during the last 30 days before the license expiration date for the indicated component. Utility processing continues, but completes with return code 4.

User response: Contact a BMC sales representative for assistance.

utility periodType PERIOD HAS EXPIRED

Explanation: Your grace or trial period has expired.

User response: Contact a BMC sales representative for assistance.

utility NOT ACTIVATED

Explanation: You specified a command for a utility that is not activated on your system.

User response: Contact a BMC sales representative for assistance.

INCONSISTENCY FOUND IN SECURITY CHECK RETURN CODE=returnCode REASON CODE=reasonCode

Explanation: The utility found an inconsistency, most likely due to the CPU ID, during the security check. The utility terminated processing.

User response: Contact BMC Support.

NOT APF AUTHORIZED

Explanation: This message indicates that the utility is not running as an MVS-authorized program. The utility must run from a library that is an Authorized Program Facility (APF) library.

User response: Contact your system programming staff to copy the utility to an APF-authorized library.

CANNOT ESTABLISH SECURITY ENVIRONMENT

Explanation: The utility cannot establish the RACF environment that it needs. The utility terminated processing.

User response: Contact BMC Support.

THIS RELEASE OFutility DOES NOT SUPPORT RELEASES OF DB2 PRIOR TO VversionNumber

Explanation: You ran the utility against a version of Db2 that this release does not support. The utility terminated processing.

User response: To determine the supported versions of Db2 for this version of the utility, see the documentation for the utility.

THIS RELEASE OF utility DOES NOT SUPPORT RELEASES OF DB2 AFTER VversionNumber

Explanation: You ran the utility against a version of Db2 that this release does not support.

User response: To determine the supported versions of Db2 for this version of the utility, see the documentation for the utility.

dataSetName : ENTRY n OF HLSM PAGE X'pageNumber' POINTS TO status LLSM PAGE X'pageNumber'

Explanation: The utility encountered a problem with the specified data set and processing terminated.

User response: Contact BMC Support and provide the information in this message.

taskNumber : ZIIP [NOT] ENABLED (xbmReturnCode) [USING XBM SUBSYSTEM ssid]

Explanation: This message indicates whether the utility enabled IBM z Integrated Information Processor (zIIP) processing. If the utility discovered the XBM subsystem, the message displays the ID of that subsystem. The message displays the return code that XBM issues. If zIIP processing was not enabled, possible return codes are as follows:

User response: Perform one of the following actions, depending on the return code:

For any return code other than 0: zIIP enablement or disablement was not successful, so to offload processing to a zIIP, correct the problem and restart or rerun the utility job. If you cannot correct the problem, contact BMC Support.

For 0 return code: No action is required. During certain phases of processing, zIIP offloading is disabled and enable when that phase is completed.  

D2UETALC 'TEST ALLOCATION' RETURNED RC=returnCode, REASON='reasonCode', MIM STATUS=status

Explanation: You are running a utility using SHRLEVEL REFERENCE. The utility encountered an unexpected condition and displays this message for diagnostic purposes.

User response: No action is required.

BMCSORT LICENSE WILL EXPIRE SOON. CALL BMC SUPPORT

Explanation: This message is displayed during the last 30 days before the license expiration date for the BMCSORT component. Utility processing continues but completes with return code 4.

User response: Ensure that maintenance for your product is current. Then contact BMC Support for assistance.

BMCSORT LICENSE HAS EXPIRED. CALL BMC SUPPORT

Explanation: The BMCSORT component is not licensed for use on this CPU. The utility terminated.

User response: Contact BMC Support for assistance.

utility NOT ALLOWED ON SYSTEM OBJECT 'databaseName.spaceName'

Explanation: A Db2 system table, table space, or index was specified in the command statement. This utility cannot operate on a Db2 system object.

User response: If applicable, change the command option to specify a supported object. Otherwise, no action is required.

'userID' DOES NOT HAVE SUFFICIENT PRIVILEGES TO EXECUTE 'utility' ON DATABASE 'databaseName'

Explanation: You need sufficient authorization to run the utility on the database that this message shows. Message BMC50053E, BMC50054E, or both might accompany this message. The utility terminated.

User response: Obtain the necessary authorization and resubmit the job. For information about the authorization that you need, see the reference manual for the utility that you are running.

USER DOES NOT HAVE 'privilege' PRIVILEGE ON TABLE 'tableCreator.tableName'

Explanation: You and all of your secondary authorization IDs need the indicated privilege to run the utility on the table shown in this message. The utility terminated.

User response: Obtain the necessary privilege and resubmit the job. For information about the privileges that you need, see the reference manual for the utility that you are running.

utility NOT ALLOWED ON TEMP OR WORK DATABASE databaseName FOR TABLE creatorName.tableName

Explanation: The indicated utility operation was attempted on a table in a temporary or work database. This operation is not allowed.

User response: No action is required.

functionality NOT SUPPORTED FOR 'option'

Explanation: The utility does not support the specified functionality for the option that you specified. The utility terminated.

User response: Change your utility job and restart or resubmit the job. For restrictions that apply to the specified option, see the reference manual for the utility that you are running.

objectName IS NOT A CLONE OBJECT

Explanation: You requested that the utility operate on a clone object, but the object that you specified is not a clone object. The utility terminated.

User response: Change your utility job and restart or resubmit the job. For more information about clone support, see the reference manual for the utility that you are running.

UNSUPPORTED KEY TARGET DATATYPE: X'dataType', DATABASE: databaseName, INDEXSPACE: indexSpaceName

Explanation: The utility detected an XML index key definition that it does not recognize, or an internal error or storage overlay occurred. The hexadecimal data type value comes from the DBD, and it represents the data type of a component (key target) of an XML index.

User response: Contact BMC Support.

D2UEFRTP - n ENTRIES FOUND IN FORCE HISTORY ARRAY. DISPLAYING RELEVANT THREAD DETAIL

Explanation: You requested that the utility cancel threads that might prevent a successful drain and that the utility display a report of those threads. The FORCE option controls these requests.

User response: No action is required. For more information about this option, see the reference manual for the utility that you are running.

action timestamp THDTOKEN=threadToken SSID=ssid SPACE=spaceName PART=partitionNumber CORRID=correlationID

Explanation: This message displays information about the threads that were canceled, skipped, or identified as duplicates as a result of the FORCE option that you specified. The variable action indicates the action (CAN, SKIP, or DUP) that was taken against the indicated thread.

User response: No action is required.

D2UEFRPT - END OF FORCE HISTORY DETAIL DISPLAY [- NO RELEVANT FORCE HISTORY FOUND]

Explanation: This message identifies the end of the thread cancelation report. If no threads were canceled, skipped, or identified as duplicates, the message indicates that the utility found no relevant FORCE history.

User response: No action is required.

NO USABLE FULL COPY FOUND FOR CATALOG OBJECT 'tableSpaceName'

Explanation: For the indicated table space, one of the following problems occurred:

• The utility did not find a full copy entry (ICTYPE F) in the SYSIBM.SYSCOPY table.

• A full copy entry existed but a function was performed on the table space that made that copy unsuitable for a forward recovery.

User response: Create a full copy of the object that you want to reorganize and resubmit the job.

utility name IS NOT ALLOWED ON TABLESPACE databaseName.tableSpaceName CONTAINING A DATACAPTURE CHANGES TABLE    

Explanation: Db2 subsystem UTILS_BLOCK_FOR_CDC parameter is set to YES so that the identified utility is not allowed on a table with the DATACAPTURE attribute or on a table space that contains such a table. This prevents the replication target tables from becoming inconsistent until a refresh is done.   

User response: If utility execution is required, contact the Db2 system administrator. 

tableCreator.tableName has DATACAPTURE attribute 

Explanation: This message follows message BMC50066E and identifies tables with the DATACAPTURE attribute.   

User response: No action is required.

DYNAMIC STATEMENT CACHE INVALIDATED, REASON=text

Explanation: This message indicates one of the following reasons for ignoring INVALIDATECACHE=NO and for invalidating the dynamic SQL statement cache:

User response: No action is required.

zIIP Initialization failed text Return/Reason = returnCode reasonCode

Explanation: Initialization of a zIIP SRB environment failed. The text contains diagnostic information as does returnCode and reasonCode for diagnosing the error with initialization.

User response: Contact a BMC Support for assistance.

zIIP Initialization failed D2UZIIPS SRB routine missing

Explanation: Initialization of a zIIP SRB environment failed.

User response: Contact a BMC Support for assistance.

zIIP Initialization warning text Return/Reason = returnCode reasonCode text

Explanation: Initialization of a zIIP SRB environment was partially successful. The text contains diagnostic information as does returnCode and reasonCode for diagnosing the error with initialization. Offloading to a zIIP processor is not possible but processing continues.

User response: Contact a BMC Support for assistance.

zIIP Cleanup failed text Return/Reason = returnCode reasonCode

Explanation: Cleanup of a zIIP SRB environment was partially successful.  The text contains diagnostic information as does returnCode and reasonCode for diagnosing the error with initialization. Termination of the utility continues.

User response: Contact a BMC Support for assistance.