Messages BMC50700 through BMC50799
For the Utility products for DB2, this topic explains each message in the designated range.
Number | Description |
---|---|
BMC50700S | INTERNAL ERROR: FILE fileName, LINE lineNumber Explanation: An internal error occurred during processing. User response: Contact BMC Customer Support with the file and line information. Additional diagnostic messages and trace information might also be displayed. If a DD statement is present for SYSERR, the utility produces a snap dump that can be useful in diagnosing the problem. |
BMC50701I | DIAGNOSTICS: text Explanation: This message displays diagnostic information for analyzing internal errors. User response: Contact BMC Customer Support with this information and any information from preceding diagnostic messages. |
BMC50702I | LOG PROCESSING STARTED AT timestamp Explanation: The log control task started. User response: No action is required. |
BMC50703I | LOG PROCESSING COMPLETED, RC = returnCode, AT timestamp, ELAPSED TIME = time Explanation: The log processing for the reorganization completed. User response: If the return code is not zero, check the preceding messages. |
BMC50704E | ATTACH FAILURE, RC = returnCode, TASK = taskType, AT timestamp Explanation: The log control task cannot attach a subtask. The return code value was received from MVS attach. User response: Check the return code value in the MVS documentation. |
BMC50705I | text Explanation: The text shown in this message is output from a facility that this product uses (for example, DB2 SQL, DB2 call attachment facility, DB2 instrumentation facility, or IDCAMS). User response: Examine the context of this message to determine whether any action is required. |
BMC50705I | SQL PREPARE LOCK STARTED AT 00D83F098FDBDABCA000 Explanation: The SQL Prepare Lock has been started so that the Dynamic SQL will be forced to wait or fail. User response: No action is required. |
BMC50705I | SQL PREPARE LOCK TERMINATED AT 00D83F09905855997800 Explanation: The SQL Prepare Lock has been terminated so that the Dynamic SQL can proceed. User response: No action is required. |
BMC50706I | MONITOR TRACE CLASS (1) STARTED, TRACE NUMBER = traceNumber Explanation: A trace with the number shown in this message has been started to capture DB2 log records. User response: No action is required. |
BMC50707E | ERROR STARTING MONITOR TRACE CLASS (1), RC = returnCode Explanation: An error occurred during an attempt to start the DB2 log capture trace. User response: Review the diagnostic messages that follow this message to determine whether you can correct the error. If you need additional assistance, contact BMC Customer Support. |
BMC50708I | DB2CA RC=returnCode REASON CODE=reasonCode Explanation: This message displays the return code and reason code from the DB2 communications area for a failed DB2 command. User response: Use this data and the messages that precede and follow this message to determine the nature of the error. |
BMC50709I | MONITOR TRACE CLASS (1) TRACE NUMBER = traceNumber STOPPED Explanation: The DB2 log capture trace with the number shown in this message has been stopped. User response: No action is required. |
BMC50710W | ERROR STOPPING MONITOR TRACE CLASS (1), RC = returnCode Explanation: An error occurred during an attempt to stop the DB2 log capture trace. User response: Review the diagnostic messages that follow this message to determine whether you can correct the error. You can manually terminate the trace by using the following command, where traceNumber is the trace number:
|
BMC50711W | UNABLE TO STOP MONITOR TRACE CLASS (1) DUE TO END-OF-TASK CONDITION Explanation: The utility cannot stop the DB2 log capture trace due to an end-of-task condition (for example, the job was canceled). User response: You can manually terminate the trace by using the following command, wheretraceNumber is the trace number:
|
BMC50712E | ERROR SETTING UP LOGSCAN ESTAE, RC = returnCode Explanation: The initialization of an ESTAE failed with the return code indicated in this message. User response: Contact BMC Customer Support. |
BMC50713E | USER LACKS SUFFICIENT MONITORING AUTHORITY Explanation: The primary authorization ID of the process that runs the program must have MONITOR1 or MONITOR2 privileges. User response: Obtain the proper privilege, or run the program with a different authorization ID. |
BMC50714E | ERROR PROCESSING LOG RECORDS, IFI RC = returnCode LOG RBA = rba/lrsn Explanation: An error occurred during processing of a DB2 instrumentation facility interface (IFI) call. User response: Review the diagnostic messages that follow this message to determine whether you can correct the error. If you need additional assistance, contact BMC Customer Support. |
BMC50715S | UNSUCCESSFUL CONNECT TO DB2 SUBSYSTEM/GROUP ssid USING PLAN planName IN LOGSCAN Explanation: The program cannot connect to the indicated subsystem or group attach name using the plan name indicated in this message and using the DB2 call attachment facility (CAF). User response: Review the accompanying DB2 CAF diagnostic messages. Possibly, the plan is not bound on the subsystem, or you are not authorized to execute the plan. If the plan name is incorrect, check the assembled options module to determine the plan name. |
BMC50716I | taskNumber: text Explanation: This message is displayed in conjunction with messages BMC50717I and BMC50718I. This message provides the heading that describes the type of statistics being displayed from the buffer manager (for example, PARTITIONING IX BUFFER STATISTICS). User response: No action is required. |
BMC50717I | taskNumber: DATASET=dataSetName Explanation: This message is displayed in conjunction with messages BMC50716I and BMC50718I. This message displays the data set name for which the buffer manager statistics apply. User response: No action is required. |
BMC50718I | statisticTypevalue | statisticTypevalue Explanation: This message is displayed in conjunction with messages BMC50716I and BMC50717I. This message provides buffer manager statistics (for example, read counts, write counts, wait counts, and number of new pages) for the data set listed in message BMC50717I. User response: No action is required. |
BMC50719I | n LOG APPLY TASKS, n INDEX APPLY TASKS, AVAILABLE MEMORY: nK Explanation: This message displays the maximum number of log apply tasks and index apply tasks that the utility will attempt to allocate for the log apply process. This message also displays the amount of memory available for the log apply process. User response: No action is required. |
BMC50720I | taskNumber: n NEW LOG APPLY BUFFERS, n REUSED, n INITIAL MAXIMUM, n WAITS, BUFFER SIZE=size Explanation: This message displays buffer information for the log apply process. The initial maximum value is the number of buffers that the utility determined that it needs for each log apply task. User response: No action is required. However, the information displayed in this message can help you tune performance of the utility. |
BMC50730S | taskNumber: WRITE ECB ABNORMAL COMPLETION CODE = X'completionCode' Explanation: A write operation on a data set completed with the abnormal return code shown in this message. An accompanying message displays the data set name. User response: Contact BMC Customer Support. |
BMC50731S | taskNumber: ECB ABNORMAL COMPLETION CODE = X'completionCode' Explanation: A write operation on a data set completed with the abnormal return code shown in this message. An accompanying message displays the data set name. User response: Contact BMC Customer Support. |
BMC50732I | taskNumber: I/O REQUEST ELEMENT FLAG = X'flag' Explanation: This message provides more information for an I/O error. User response: Review the accompanying messages and contact BMC Customer Support. |
BMC50733S | taskNumber: WRITE REQUEST ERROR, RC = returnCode Explanation: A write error occurred with the return code shown in this message. User response: Contact BMC Customer Support. |
BMC50734S | taskNumber: READ REQUEST ERROR, RC = returnCode Explanation: A read error occurred with the return code shown in this message. User response: Contact BMC Customer Support. |
BMC50736S | taskNumber: ERROR DURING AUTHORIZATION SWITCH, RC = returnCode, FUNCTION = functionName Explanation: The options for this utility indicate that the utility is to use DB2's RACF security authorization to open DB2 data sets. A failure occurred while attempting to switch the RACF authorization ID. User response: If your security system is not RACF, specify OPNDB2ID=NO in the options module for the BMC utility that you are running. Ensure that you have the required authorization on the necessary data sets. If you are using RACF, contact BMC Customer Support. |
BMC50737I | taskNumber: EXTEND SUCCESSFUL FOR DATASET dataSetName Explanation: A VSAM EXTEND was successful for the indicated data set. User response: No action is required. |
BMC50738I | taskNumber: ATTEMPTING ALLOCATION FOR NEW MULTI DATASET dataSetName Explanation: A VSAM CREATE is being attempted for the indicated data set in a multi-data-set table space. User response: No action is required. |
BMC50739I | taskNumber: ALLOCATION SUCCESSFUL FOR NEW MULTI DATASET dataSetName Explanation: A VSAM CREATE was successful for the indicated data set. User response: No action is required. |
BMC50740E | FAILURE IN REORG/LOG APPLY INTERFACE, RC = returnCode Explanation: The interface received invalid data. User response: Contact BMC Customer Support. |
BMC50741I | taskNumber: LOGAPPLY STATISTICS Explanation: This message is the header message for statistics from a log apply task. User response: No action is required. |
BMC50742I | taskNumber: PROCESSED TRANSACTIONS Explanation: This heading message indicates that the following messages refer to counts for log records that were received at the log exit. User response: No action is required. |
BMC50743I | taskNumber: CONSOLIDATED TRANSACTIONS Explanation: This heading message indicates that the following messages refer to counts for log records that were calculated after multiple records for the same row were combined. User response: No action is required. |
BMC50744I | taskNumber: INSERTS: n INSERTS (COMPENSATION): n Explanation: This message displays the number of insert records that were found in both the regular and rollback portions of the transactions. User response: No action is required. |
BMC50745I | taskNumber: UPDATES: n UPDATES (COMPENSATION): n Explanation: This message displays the number of update records that were found in both the regular and rollback portions of the transactions. User response: No action is required. |
BMC50746I | taskNumber: DELETES: n DELETES (COMPENSATION): n Explanation: This message displays the number of delete records that were found in both the regular and rollback portions of the transactions. User response: No action is required. |
BMC50747I | taskNumber: PAGES UPDATED COUNTERS FOR databaseName.tableSpaceName Explanation: This message is the heading for information that subsequent messages (BMC50748I and BMC50749I) report for the indicated table space. User response: For the data, see subsequent messages. |
BMC50748I | taskNumber: PART TOTAL PAGES DATA PAGES SPACE MAPS HEADER PAGES Explanation: This message accompanies message BMC50747I and provides the heading for the information that follows in message BMC50749I. The information shows the number of pages that were updated by partition. If the table space is nonpartitioned, the partition number is zero. User response: No action is required. |
BMC50749I | statistics Explanation: This is the page count data for the table space partitions that are related to the heading information provided in messages BMC50747I and BMC50748I. User response: No action is required. |
BMC50750I | taskNumber: IGNORED TRANSACTIONS DUE TO SELECT/DELETE Explanation: If you specified SELECT or DELETE on the utility command, the utility might display this message as each LOGAPPLY task ends. Messages BMC50744I, BMC50745I, and BMC50746I follow this message and display the number of ignored log records. User response: No action is required. |
BMC50751E | taskNumber: ERROR EXTENDING OUTPUT DATASET dataSetName, RC = returnCode Explanation: A request to extend the indicated data set failed with the return code shown in this message. User response: Check the target DASD volumes for the data set to ensure that enough space is available for extension. If you need additional assistance, contact BMC Customer Support. |
BMC50752S | ERROR IN CALL OF EDITPROC editProcedure, RC = returnCode, REASON = reasonCode Explanation: The EDITPROC returned the error code shown in this message. User response: Consult the EDITPROC documentation. |
BMC50753S | COMPRESSION SYSTEM functionName FAILED - RC=returnCode, REASON=reasonCode Explanation: The indicated compression system function failed with the return code shown in this message. User response: Contact BMC Customer Support. |
BMC50756I | XBM RESPONSE BUFFER OVERFLOW Explanation: A message was too large for the XBM response buffer. User response: Contact BMC Customer Support. |
BMC50757I | AUTO DETECTED XBMID (xbmSubsystem), ENABLED FOR function Explanation: The utility detected the indicated XBM subsystem. This subsystem is enabled for the indicated function. User response: No action is required. However, if you want to use a different XBM subsystem for this function in a future job, specify a value for the XBMID option. |
BMC50770S | LOG APPLY ABNORMAL TERMINATION, SYSTEM COMPLETION CODE = completionCode, RETURN CODE = returnCode Explanation: During a SHRLEVEL CHANGE operation, the LOG APPLY component encountered an unrecoverable error. Utility processing terminated. User response: Contact BMC Customer Support. |
BMC50771S | UNABLE TO ALLOCATE LOG APPLY MEMORY Explanation: Insufficient memory is available to allocate a minimum set of log apply tasks. User response: Increase the region size above the line and resubmit the job. |
BMC50772S | MEMORY AVAILABLE: nK, memoryType MEMORY REQUIRED: nK Explanation: This message follows message BMC50771S and indicates the memory that is available, the type of memory that is required, and the minimum amount that is required. User response: Subtract the amount of available memory from the amount of required memory. Multiply the result by two and increase the region size above the line by this amount. Resubmit the job. |
BMC50773I | taskNumber: taskType TASK STARTED AT timestamp Explanation: The indicated log apply task started at the indicated time. User response: No action is required. |
BMC50774S | taskNumber: UNEXPECTED TASK TERMINATION, SYSTEM COMPLETION CODE=completionCode, RETURN CODE=returnCode Explanation: A log apply task ended unexpectedly. User response: Check the preceding messages for more information. |
BMC50775E | taskNumber: NEW MULTI DATASET CANNOT BE ALLOCATED FOR databaseName.spaceName, MAXIMUM NUMBER OF DATASETS REACHED Explanation: The utility required a new multi-data-set for the indicated space, but the space already reached its maximum number of data sets. User response: If the maximum number of data sets has not been reached or more space is available, contact BMC Customer Support. |
BMC50776E | taskNumber: VSAM CREATE FOR 'dataSetName' FAILED, RC=returnCode Explanation: An error occurred during a VSAM DEFINE operation for the indicated data set. User response: Look for accompanying messages that indicate the nature of the error. Correct the problem and resubmit the job. |
BMC50777E | taskNumber: UPDATES TO DATASET 'dataSetName' WILL EXCEED THE MAXIMUM SIZE OF n PAGES Explanation: The update activity to a partitioned table space during the LOGAPPLY phase caused the utility to expand the partition beyond the physical size of the object. Utility processing terminated. This problem might occur if changes are made to the definition of the object before running the utility. Examples are changes in compression or altering the MAXROW value , or if you need to move rows between partitions in a PBG object. User response: Examine the changes made to the object definition to determine the probable cause of the problem. |
BMC50778I | LOG RECORD QUEUE SIZE AT OR BELOW THRESHOLD Explanation: The number of records in the log record queue is at or below the user-specified threshold (LOGTHRESHLD). Therefore, the LOGFINAL phase has started. User response: No action is required. |
BMC50779I | LOG APPLY CAN BE COMPLETED WITHIN MAXRO TIME SPECIFIED Explanation: The utility estimates that the LOGAPPLY phase can complete within the user-specified maximum read-only time (MAXRO value). Therefore, the LOGFINAL phase has started. User response: No action is required. |
BMC50780I | LONG LOG DETECTED AT timestamp, WILL DELAY UNTIL timestamp Explanation: Log records are arriving faster than they can be applied, causing a long log condition. The utility delays until the specified time before taking the action that the LONGLOG option specifies. The utility continues to apply log records. User response: No action is required. |
BMC50781E | LONG LOG DELAY REACHED AT timestamp, TERMINATING Explanation: The long log condition persisted until the specified delay time. Therefore, the utility takes the action that the LONGLOG option specifies, which was to terminate the job. User response: No action is required. |
BMC50782I | LONG LOG DELAY REACHED AT timestamp Explanation: The long log condition persisted until the specified delay time. Therefore, the utility takes the action that the LONGLOG option specifies, which is to begin the LOGFINAL phase. User response: No action is required. |
BMC50783I | LONG LOG NO LONGER DETECTED AT timestamp Explanation: The arrival rate of the log records no longer exceeds their apply rate. The utility resets the delay time. User response: No action is required. |
BMC50784E | UNABLE TO COMPLETE PROCESSING BY DEADLINE, TERMINATING Explanation: The utility calculated that it cannot complete the LOGAPPLY phase by the deadline that the DEADLINE option specifies. The utility terminated. User response: No action is required. |
BMC50785E | UNABLE TO QUIESCE SPACE, RC = returnCode, LOGFINAL PHASE BYPASSED Explanation: The quiesce of the space failed, and the utility will not perform LOGFINAL phase processing. User response: For more information, see the preceding messages. |
BMC50786I | taskNumber: taskType TASK ENDED AT timestamp, ELAPSED TIME = time Explanation: This message reports when the indicated task ended and how long the task took to process. User response: No action is required. |
BMC50787I | taskNumber: DSN = dataSetName Explanation: This message reports the data set name for accompanying messages. User response: For the appropriate action, see the accompanying messages. |
BMC50788S | taskNumber: INDEX MAINTENANCE ON indexName CANNOT BE PERFORMED BECAUSE THE INDEX IS EMPTY Explanation: The utility cannot update the index because the index is not initialized. User response: Contact BMC Customer Support. |
BMC50789W | taskNumber: THERE ARE NO KEY VALUES FOR INDEX indexName Explanation: The index contains no keys. User response: No action is required. |
BMC50790E | XBM ssid ERROR, RC=returnCode Explanation: The utility received an error code from the XBM subsystem that is identified by the subsystem ID (ssid). User response: Check for XBM error messages. |
BMC50791I | taskNumber: statisticType value statisticType value Explanation: This message provides index update statistics. User response: No action is required. |
BMC50792S | taskNumber: FLAG BYTE/LAST BYTE DISCREPANCY: INDEX indexName ; moreInformation Explanation: The utility encountered an error in an index page. This message provides information about the index in error. User response: Contact BMC Customer Support. |
BMC50793S | taskNumber: PAGE MARKED 'READ WITH I/O ERROR': INDEX indexName ; moreInformation Explanation: The page in the index is marked as having an I/O error. This message provides information about the index in error. User response: Correct the I/O error range and resubmit the job. |
BMC50794I | taskNumber: INDEX MAINTENANCE STATISTICS FOR INDEX indexName Explanation: This message is the heading message for the index update statistics that follow. User response: No action is required. |
BMC50795I | XBM COMMAND RECEIVED AT timestamp FROM userID Explanation: This message is the heading message for the displayed XBM command and response that follows. User response: No action is required. |
BMC50796I | XBMCommand Explanation: This messages displays an XBM command and response, and follows message BMC50795I. User response: No action is required. |
BMC50797W | UNABLE TO POST RESPONSE TO XBM SUBSYSTEM, RC X'returnCode' Explanation: The utility cannot send a response to an XBM command. User response: Check the status of the XBM subsystem. |
BMC50798I | taskNumber: CATALOG RETURN CODE returnCode (FEEDBACK CODE = X'feedbackCode') LISTING dataSetName Explanation: An error occurred while accessing catalog information for the indicated data set. User response: Note the values of the return code and feedback code, and contact BMC Customer Support. |
BMC50799S | taskNumber: UNABLE TO RETRIEVE DEVICE TYPE, DDNAME = ddname, RC = returnCode Explanation: An internal error occurred. The utility cannot read the device type information for the indicated ddname. User response: Contact BMC Customer Support. |
Comments
Log in or register to comment.