Messages BMC50800 through BMC50899

For the Utility products for DB2, this topic explains each message in the designated range.
NumberDescription
BMC50800E

EXPECTING token1 FOUND token2


Explanation: The utility found an unexpected parameter or keyword when processing a command from the XBM Utility Monitor.

User response: Correct the command and resubmit the job.

BMC50801I

parameter VALUE SET TO value


Explanation: The XBM Utility Monitor set the value for the parameter shown in this message.

User response: No action is required.

BMC50802W

TOO LATE TO STOP AFTER INITIALIZATION


Explanation: The log apply control options were changed after the LOGFINAL phase started, which is not allowed.

User response: No action is required.

BMC50803I

LOG APPLY DISPLAY AT timestamp


Explanation: This message is the heading for the DISPLAY command output from the XBM Utility Monitor.

User response: No action is required.

BMC50804I

LOG APPLY TASKS: n TASKS, n STARTED, n FINISHED


Explanation: This message is part of the output for the XBM Utility Monitor DISPLAY command. The message shows the number of log-record apply tasks that have been allocated, started, and completed.

User response: No action is required.

BMC50805I

n RECORDS QUEUED, n RECORDS APPLIED


Explanation: This message is part of the output for the XBM Utility Monitor DISPLAY command. It displays the number of records that have been queued (either table space or index records) and the total number that have been applied.

User response: No action is required.

BMC50806I

INDEX APPLY TASKS: n TASKS, n STARTED, n FINISHED


Explanation: This message is part of the output for the XBM Utility Monitor DISPLAY command. It shows the number of index-record apply tasks that have been allocated, started, and completed.

User response: No action is required.

BMC50807I

TASK taskNumber: taskType


Explanation: This message is part of the output for the XBM Utility Monitor DISPLAY command. It shows the task number and the task type for which you are displaying information.

User response: No action is required.

BMC50808I

PARTITION(S): partitionNumber


Explanation: This message is part of the output for the XBM Utility Monitor DISPLAY command. It shows the set of partitions that are assigned to a task.

User response: No action is required.

BMC50809I

partitionNumber


Explanation: This message is part of the output for the XBM Utility Monitor DISPLAY command. It follows message BMC50808 if more partitions will display.

User response: No action is required.

BMC50810I

INDEX indexCreator.indexName


Explanation: This message is part of the output for the XBM Utility Monitor DISPLAY command. It shows the name of the index.

User response: No action is required.

BMC50811I

taskNumber: ALTER TABLE tableName DATA CAPTURE status


Explanation: The table had its DATA CAPTURE flag status changed to ON, CHANGES, or NONE.

User response: No action is required.

BMC50819E

RBALRSN_CONVERSION value NOT ALLOWED DUE TO reason


Explanation: You specified a value for the RBALRSN_CONVERSION option that the utility does not allow for the indicated reason. The utility terminates.

User response: Correct the problem and rerun the job.

BMC50820I

REORG PARAMETER CHANGE NOT ALLOWED IN LOG FINAL


Explanation: An XBM command was issued after the LOGFINAL processing phase began. The command is ignored.

User response: No action is required.

BMC50821I

LONG LOG DELAY REACHED, CONTINUING TO timestamp


Explanation: The long log delay time has been reached. Processing continues to the next time indicated in this message, based on your request.

User response: No action is required.

BMC50822I

CURRENT PHASE: phase, STARTED: timestamp


Explanation: This message displays the currently executing phase and the time that the phase started.

User response: No action is required.

BMC50823I

CURRENT PHASE: phase


Explanation: This message displays the phase that is currently executing.

User response: No action is required.

BMC50824I

LONG LOG DETECTED AT timestamp


Explanation: This message displays when the utility detects a long log condition.

User response: No action is required.

BMC50825I

LONG LOG ACTION WILL OCCUR AT timestamp


Explanation: This message displays the time when the utility will take the action that the LONGLOG option specifies.

User response: No action is required.

BMC50826I

timestamp: IDCAMS: IDCAMSOutput


Explanation: This message follows message BMC50814 and displays IDCAMs output.

User response: No action is required.

BMC50827I

COMMAND ISSUED FOR MEMBER memberName AT timestamp, 'command'


Explanation: This message displays a DB2 command that the utility issued against the DB2 member shown in this message and the time that the command was issued. The utility issues this message only if MSGLEVEL is 1 and the utility is running in a data sharing environment. This message can be helpful to BMC Customer Support when diagnosing a problem.

User response: No action is required.

BMC50828I

LOGAPPLY TERMINATED DUE TO REORG REQUEST, ELAPSED TIME = time


Explanation: The utility encountered an exceptional condition and terminated the log apply process.

User response: Determine the cause of the original utility error, fix the error, and resubmit the job.

BMC50829I

LOGAPPLY PHASE STARTING AT timestamp


Explanation: The LOGAPPLY execution phase started at the indicated time.

User response: No action is required.

BMC50830I

LOGFINAL PHASE STARTING AT timestamp


Explanation: The LOGFINAL execution phase started at the indicated time.

User response: No action is required.

BMC50831E

LOG RECORDS REQUIRED ARE NOT AVAILABLE ON ACTIVE LOG(S)


Explanation: The log processing exit cannot keep pace with the DB2 logging activity. As a result, some of the records that the exit requires are no longer available on the active log files.

User response: Run the program during a period of decreased activity, or expand the size of the active log data sets.

BMC50832E

MONITOR TRACE CLASS (1) IS NOT ACTIVE


Explanation: The DB2 monitor trace is not active. This problem usually occurs when a STOP TRACE command is issued while running the utility with SHRLEVEL CHANGE.

User response: Resubmit the job and ensure that nothing stops the monitor trace that the utility started.

BMC50833E

XBM INTERFACE FORCED TERMINATION


Explanation: XBM detected a potentially severe problem and signaled the utility to terminate. This message applies only to a utility command with SHRLEVEL CHANGE specified.

User response: For more information, see additional messages.

BMC50834I

COMMAND RESPONSE FOR MEMBER memberName, 'response'


Explanation: The utility, which was specified with SHRLEVEL CHANGE, issued a DB2 command. This message displays the response that the utility received from the DB2 member of the data sharing group.

User response: No action is required.

BMC50835E

COMMAND FAILED FOR MEMBER memberName, 'command'


Explanation: The displayed DB2 command failed for the data sharing group member. Message BMC50834I precedes this message.

User response: To determine the appropriate action, see the response that is supplied in message BMC50834I. If the problem persists, contact BMC Customer Support.

BMC50836E

CONSOLE INTERFACE ERROR, FUNCTION=functionName RC=returnCode


Explanation: An error occurred during a SHRLEVEL CHANGE job while the utility was processing a command through the extended console interface.

User response: For more information, see the system log. If the problem persists, contact BMC Customer Support.

BMC50837E

NO RESPONSE RECEIVED FROM MEMBER memberName


Explanation: Using the extended console interface, the utility issued a DB2 command to the member of a data sharing group. The member did not respond, so the utility terminated.

User response: See the system log for console errors. Check to see if the DB2 member received the command. If you cannot resolve the problem, contact BMC Customer Support.

BMC50838E

REQUIRED MONITOR TRACE CLASS (1) FOR MEMBER memberName NO LONGER ACTIVE


Explanation: A SHRLEVEL CHANGE job requires an active monitor trace. The trace for the member became inactive while the job was still running. The utility ended all monitor traces and terminated. The monitor trace must be active on each member of a DB2 data sharing group to ensure that all log records are collected.

User response: Resubmit the utility job, ensuring that none of the monitor traces are stopped while the utility is running.

BMC50839E

REQUIRED MONITOR TRACES NOT ACTIVE WITH OTHER SHRLEVEL CHANGE REORGS ACTIVE. STOPPING ALL TRACES


Explanation: During a SHRLEVEL CHANGE job, the utility discovered that one or more required monitor traces were not active, issued message BMC50838E, and stopped any active monitor traces for other SHRLEVEL CHANGE jobs that were running in the same data sharing group. The utility stops the monitor traces and terminates the other SHRLEVEL CHANGE jobs that are running in that data sharing group. The monitor trace must be active on each member of a DB2 data sharing group to ensure that all log records are collected.

User response: Resubmit the utility job, ensuring that none of the monitor traces are stopped while the utility is running.

BMC50840I

MONITOR TRACE CLASS (1) STARTED FOR ALL ACTIVE MEMBERS


Explanation: The utility started a monitor trace for each active DB2 member of a data sharing group.

User response: No action is required.

BMC50841I

MONITOR TRACE CLASS (1) ALREADY ACTIVE ON ALL ACTIVE MEMBERS


Explanation: A utility job with SHRLEVEL CHANGE discovered that the monitor traces for all of the members of a data sharing group were already active. This situation occurs when another SHRLEVEL CHANGE job is already running in this data sharing group.

User response: No action is required.

BMC50842I

MONITOR TRACE CLASS (1) STOPPED FOR ALL ACTIVE MEMBERS


Explanation: The utility job with SHRLEVEL CHANGE completed. Because no other SHRLEVEL CHANGE jobs are running in this data sharing group, the utility ended all of the monitor traces.

User response: No action is required.

BMC50843I

MONITOR TRACE CLASS (1) WILL REMAIN ACTIVE ON ALL ACTIVE MEMBERS TO SERVICE OTHER SHRLEVEL CHANGE REORGS


Explanation: More than one SHRLEVEL CHANGE utility job is running in this data sharing group. The job that finished did not end any monitor traces.

User response: No action is required.

BMC50844I

MONITOR TRACE CLASS (1) ALREADY ACTIVE, TRACE NUMBER=traceNumber


Explanation: The utility issued a START TRACE command, but the trace is already active.

User response: No action is required.

BMC50845I

MONITOR TRACE CLASS (1) STOPPED FOR MEMBER memberName


Explanation: A utility job with SHRLEVEL CHANGE stopped the monitor trace for the member of a data sharing group. No other SHRLEVEL CHANGE jobs were running.

User response: No action is required.

BMC50846I

MEMBER memberName ACTIVATED AFTER SHRLEVEL CHANGE REORG BEGAN, REORG TERMINATING


Explanation: The DB2 member was started after a SHRLEVEL CHANGE job started. Because the utility cannot guarantee the integrity of the job, it terminates.

User response: Resubmit the job, ensuring that no members are started or stopped while the SHRLEVEL CHANGE job is running.

BMC50847I

taskNumber: BUFFER ALLOCATIONS: CHANGED PAGE BUFFERS = n, I/O BUFFERS = n, LARGEST BLOCK SIZE = size


Explanation: This message displays the number of changed page buffers, I/O buffers, and the largest block size that the utility initially allocated. The utility issues this message when the utility updates full copy data sets as part of a SHRLEVEL CHANGE job.

User response: No action is required.

BMC50848E

taskNumber: I/O ERROR: functionName, module, lineNumber, reason


Explanation: An I/O routine failed while the utility was updating a full copy data set for a SHRLEVEL CHANGE job. This message contains information that is useful to BMC Customer Support.

User response: Contact BMC Customer Support.

BMC50849E

taskNumber: I/O ERROR: text


Explanation: This message displays information that a failed I/O routine returned. This message contains information that is useful to BMC Customer Support.

User response: Contact BMC Customer Support.

BMC50850I

taskNumber: PARTITION = partitionNumber, PART TOTALS UPDATED PAGES = n, UPDATED BLOCKS = n, APPENDED PAGES = n, APPENDED BLOCKS = n


Explanation: This message displays statistical information for the partition. The utility gathers this information when it updates a full copy data set for a SHRLEVEL CHANGE job. Message BMC50851I follows this message.

User response: No action is required.

BMC50851I

taskNumber: PARTITION = partitionNumber, PART TOTALS DEFERRED WRITES = n, READ IOS = n, WRITE IOS = n, DEFERRED IOS = n, DEFERRED BLOCKS = n


Explanation: This message follows message BMC50850I and provides additional statistics for the partition. The utility gathers this information when it updates a full copy data set for a SHRLEVEL CHANGE job.

User response: No action is required.

BMC50852I

taskNumber: TASK TOTALS, UPDATED PAGES = n, UPDATED BLOCKS = n, APPENDED PAGES = n, APPENDED BLOCKS = n


Explanation: This message displays statistical information for the indicated task. The utility gathers this information when it updates a full copy data set for a SHRLEVEL CHANGE job. Message BMC50853I follows this message.

User response: No action is required.

BMC50853I

taskNumber: TASK TOTALS, DEFERRED WRITES = n, READ IOS = n, WRITE IOS = n, DEFERRED IOS = n, DEFERRED BLOCKS = n


Explanation: This message follows message BMC50852I and provides additional statistics for the indicated task. The utility gathers this information when it updates a full copy data set for a SHRLEVEL CHANGE job.

User response: No action is required.

BMC50854I

taskNumber: FINAL STATISTICS, COLLECTOR (CALLS = n, TIME = time), PAGES COLLECTED = n, BUFFER WAITS = n, DUPLICATES = n


Explanation: This message displays statistical information for a specific partition. The utility gathers this information when it updates a full copy data set for a SHRLEVEL CHANGE job. Message BMC50855I follows this message.

User response: No action is required.

BMC50855I

taskNumber: FINAL STATISTICS, TOTAL PAGE SLOTS = n, MAXIMUM USED = n, I/O BUFFERS = n, MAXIMUM USED = n


Explanation: This message follows message BMC50854I and provides additional statistics for a particular partition. The utility gathers this information when it updates a full copy data set for a SHRLEVEL CHANGE job.

User response: No action is required.

BMC50856E

CATALOG ACTIVITY DETECTED ON OBJECT, PROCESSING TERMINATED AT LOG RBA rba/lrsn


Explanation: A data definition language (DDL) statement such as CREATE, DROP, or ALTER was issued against the object on which the utility is operating. Utility processing terminated. This message contains the relative byte address (RBA) or the log record sequence number (LRSN) of the associated DB2 log record.

User response: Resubmit the job and ensure that no DDL statements are issued for the object while the utility job is running.

BMC50857E

OBJECT STATUS CHANGE DETECTED ON OBJECT, PROCESSING TERMINATED AT LOG RBA rba/lrsn


Explanation: The status of the object changed while the utility job was running. Utility processing terminated. This message contains the relative byte address (RBA) or the log record sequence number (LRSN) of the associated DB2 log record.

User response: Resubmit the job and ensure that the status of the object does not change while the utility job is running.

BMC50858E

DELETE WITHOUT WHERE CLAUSE DETECTED FOR TABLE tableName AT LOG RBA rba/lrsn


Explanation: While applying log records during the LOGAPPLY phase, the utility detected a mass DELETE operation (an SQL DELETE without a WHERE clause). Utility processing terminated.

User response: Resubmit the job, ensuring that no mass DELETE operation occurs while the utility is running.

BMC50859I

LOG RECORD STORE STATISTICS: MEMORY AVAILABLE = n, MEMORY USED = n


Explanation: This message displays (in kilobytes) the amount of data space memory that is available for log records and the amount that the utility used to store them. The available memory is the amount that the LOGMEM option specifies. The amount of memory that the utility used might be slightly greater than the value of the LOGMEM option because of how the utility allocates the memory.

User response: No action is required. For more information, see message BMC50860I.

BMC50860I

TOTAL WAIT TIME FOR LOG RECORD STORE MEMORY = time DATA = time INDEX = time


Explanation: This message displays the time in seconds that the utility spent waiting for available memory in order to store log records. The total time is the sum of the second and third times displayed.

User response: To reduce the total wait time, increase the amount of available memory by increasing the value of the LOGMEM option.

BMC50861E

taskNumber: operation COULD NOT BE PERFORMED ON ROW FILTERED BY SELECT/DELETE RID: recordID RBA: rba/lrsn KEY: key


Explanation: The utility displays this message if an application issues an SQL UPDATE or DELETE statement on a filtered row. If the key value is not available, N/A is displayed as the variable. A dump of any available log images follows this message.

User response: Review the filter criteria that you specified for this job. Resubmit the job to avoid a conflict between the filter criteria and the application that is issuing the UPDATE or DELETE SQL statement.

BMC50862E

taskNumber: DELETE OPERATIONS AGAINST ROWS FILTERED BY SELECT/DELETE EXCEEDED LIMIT OF limit


Explanation: The utility displays this message if the application issues multiple DELETE statements for filtered rows and the number of DELETE statements to be ignored exceeds the limit shown in this message. The job terminated.

User response: Review the filter criteria that you specified for this job. Resubmit the job to avoid a conflict between the filter criteria and the application that is issuing the SQL DELETE statements. If the limit shown in this message is inappropriate for your environment, contact BMC Customer Support.

BMC50863I

LOGMEM OF n SPECIFIED, FOR IMPROVED PERFORMANCE n OR MORE IS RECOMMENDED


Explanation: The amount of data space memory that the LOGMEM option specifies is not enough to achieve optimal performance. This message displays the recommended amount of data space memory in kilobytes.

User response: To improve the performance of the SHRLEVEL CHANGE operation, change the amount of data space memory that the LOGMEM option specifies to the recommended value that is displayed in this message. Resubmit the job.

BMC50864I

[INSUFFICIENT] LOGMEM OF n1K SPECIFIED, CHANGED TO n2K


Explanation: If you receive the INSUFFICIENT LOGMEM version of this message, the first value is the amount of data space memory in kilobytes that was specified on the LOGMEM option. This amount is insufficient for the SHRLEVEL CHANGE operation. The utility changed the value to the second amount so that it could continue processing the job. If you receive the other version of this message, zero was specified as the LOGMEM value, telling the utility to calculate the amount of memory that it needed. This message displays the amount that the utility calculated.

User response: If you receive the INSUFFICIENT LOGMEM version of this message, increase the amount on the LOGMEM option so that it is greater than or equal to the second value (the amount that the utility needed). Alternatively, specify zero as the LOGMEM value to allow the utility to allocate the amount that it needs. If you receive the other version of this message, no action is required.

BMC50865I

TOTAL RECORDS INSERTED INTO LOG RECORD STORE, DATA = n, INDEX = n


Explanation: This message displays the total number of log records that are stored in the log record store for the table space updates (data) and index updates (index).

User response: No action is required.

BMC50866I

TOTAL type STRINGS PROCESSED = n, WHEN NOT FULL = n, FROM SPILL = n


Explanation: This message displays the total number of strings that the utility processed, the number of incomplete strings, and the number of strings that the utility processed from the spill data sets.

User response: No action is required.

BMC50867I

LOG RECORD STORE SPILL REQUESTS = n, HIGH SPILL PAGE = n, SPILL DATASETS CREATED = n


Explanation: This message displays the number of requests to store log records in the spill data sets, the largest amount of data that was stored in the spill data sets, and the number of spill data sets that the utility created.

User response: No action is required.

BMC50868I

component WRITE REQUESTS = n, WRITE WAIT TIME = time, READ REQUESTS = n, READ WAIT TIME = time


Explanation: This message displays the number of read and write requests to the spill data sets, and the time that the log record store or RID map component spent waiting for the read and write requests to complete.

User response: No action is required.

BMC50869I

component: SPILLING TO DATASET 'dataSetName'


Explanation: The log records used all of the data space memory and spilled to the indicated data set, or the existing spill data set could not be extended further. The utility issues this message each time that it creates a new spill data set.

User response: No action is required.

BMC50870E

component COULD NOT CREATE DATASET 'dataSetName'


Explanation: The log record store or RID map component was not able to create the indicated data set, which the component needed in order to store the spilled log records.

User response: For more information about why the component could not create the data set, see the preceding BMC50826I messages. Correct the problem if possible, and resubmit the job.

BMC50871E

component OUT OF SPACE OR DATASET LIMIT REACHED


Explanation: The log record store or RID map component could not allocate the spill data set, or the component reached the maximum number of spill data sets.

User response: For more information about why the component could not create the data set, see the preceding BMC50826I messages and message BMC50870I. Correct the problem if possible, and resubmit the job.

BMC50872I

component primary/secondary ALLOCATION CHANGED FROM n1 TO n2


Explanation: The log record store or RID map component found that the primary or secondary DASD allocation that was specified for the spill data sets is insufficient. The component increased the allocation to the minimum amount that it needs to allocate the data space.

User response: To improve performance, change the amount specified on the LOGSPILL option to at least as much as the component allocated.

BMC50873I

LOGMEM REDUCED FROM n1 TO n2 DUE TO DATASPACE ALLOCATION LIMITS


Explanation: The amount of data space that was requested on the LOGMEM option exceeded the system-allowed limits for maximum data space count or maximum data set size. The log record store component decreased the amount of data space that it used to remain within the system limits.

User response: Contact BMC Customer Support.

BMC50874S

process TERMINATION IN PROGRESS


Explanation: An abend occurred during log processing or index update processing, causing the component to invoke its termination routine. The termination routine performs cleanup activities before the utility terminates the job.

User response: Contact BMC Customer Support.

BMC50875E

MINIMUM REQUIRED LOGMEM nK CANNOT BE OBTAINED DUE TO DATASPACE ALLOCATION LIMITS


Explanation: The utility calculated that it needs n kilobytes of storage to hold the log records. However, the maximum amount of available memory is set by multiplying the value of the LOGRMAXD option by the value of the LOGRDSSZ option. If the result is less than the minimum amount of storage that the utility needs, the utility terminates the job.

User response: Increase the values of the LOGRMAXD and LOGRDSSZ options so that when they are multiplied, the resulting value is greater than the number shown in this message.

BMC50876S

RIDMAP INITIALIZATION FAILED RC=returnCode


Explanation: The utility failed while initializing the RIDMAP component and terminated with the indicated return code.

User response: To determine whether you can correct the problem, see previous messages. If you cannot correct the problem, contact BMC Customer Support.

BMC50877I

POINT OF CONSISTENCY ESTABLISHED AT RBA/LRSN = rba/lrsn


Explanation: The utility externalized page set buffers for all of the required objects, establishing a point of consistency at the displayed relative byte address (RBA) or log record sequence number (LRSN).

User response: No action is required.

BMC50878I

taskNumber: operation CANNOT BE PERFORMED ON ROW DISCARDED DUE TO ALTERED MAXIMUM LIMIT KEY, RBA: rba KEY: key


Explanation: During SHRLEVEL CHANGE processing, an INSERT, UPDATE, or DELETE was attempted on a row that the utility had already discarded because of an altered limit key. The utility continues processing.

User response: If you want to complete the action, ensure that the application is enforcing new limit key assignments. If the application is not enforcing the new limit keys, the application might be in error or the altered definition of the table space partitions is incorrect. The utility leaves the table space in its original state.

BMC50878E

taskNumber: operation CANNOT BE PERFORMED ON ROW DISCARDED DUE TO ALTERED MAXIMUM LIMIT KEY, RBA: rba KEY: key


Explanation: During SHRLEVEL CHANGE processing, an INSERT, UPDATE, or DELETE was attempted on a row that the utility had already discarded because of an altered limit key. The utility terminated.

User response: Ensure that the application is enforcing new limit key assignments. If the application is not enforcing the new limit keys, the application might be in error or the altered definition of the table space partitions is incorrect. The utility leaves the table space in its original state. Correct the problem and resubmit the reorganization.

BMC50879I

formatType FORMAT CONVERSION IGNORED DUE TO reason


Explanation: A conversion was requested either implicitly (for example, based on a DB2 DSNZPARM value) or explicitly by specifying a utility option. However, conditions exist that preclude the utility from performing the conversion. The job continues, but no conversion occurs.

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

BMC50880I

RIDMAP: {SUMMARY | PART partitionNumber}: ROWS=n, PAIRS=n, STORAGE=nK, MEM WAITS=n, WAIT TIME=time


Explanation: This message displays statistics for a full table space, for all partitions in a partitioned table space (SUMMARY), or for an individual partition (PART). The statistics show the maximum amounts for the following resources:

Statistic

Description

ROWS

Number of rows that are represented in the RID map

PAIRS

Number of RID pairs (old RID and new RID) that are stored

STORAGE

Total amount in kilobytes of storage that was used (DASD and data space memory)

MEM WAITS

Number of times that a wait was issued for memory

WAIT TIME

Total amount of time (in seconds) that was spent waiting for memory


User response: No action is required.

BMC50881I

RIDMAP: {SUMMARY | PART partitionNumber}: TRANS=n, ADDS=n, DELS=n, SPILL READS=n, WAIT TIME=time


Explanation: This message displays statistics for a full table space, for all partitions in a partitioned table space (SUMMARY), or for an individual partition (PART). The statistics show the amount of activity in the RID map for the following operations:

Statistic

Description

TRANS

Number of RID translations that were performed

ADD

Number of RID pairs that were inserted

DELS

Number of RID pairs that were deleted

SPILL READS

Number of read requests that were made against a spill data set

WAIT TIME

Total amount of time (in seconds) that was spent waiting for I/O operations to complete


User response: No action is required.

BMC50882I

RIDMAP: SUMMARY: MAX DATASPACES=n, USED DATASPACES=n, RIDMAPMEM=nK, USED MEM=nK


Explanation: This message displays the following information about data spaces:

Statistic

Description

MAX DATASPACES

Maximum number of data space that the utility was allowed to use

USED DATASPACES

Number of data spaces that the utility actually used

RIDMAPMEM

Value that you specified for RIDMAPMEM in kilobytes

USED MEM

Total amount in kilobytes of data space memory that the utility used


User response: No action is required.

BMC50883I

RIDMAP: SUMMARY: MAX PIPES=n, PIPES USED=n, PIPES BUFFER SIZE=n, PIPE WAITS=n, WAIT TIME=time


Explanation: This message provides information that BMC Customer Support can use to resolve problems with the RID map.

User response: No action is required

BMC50884E

RIDMAP: MINIMUM VALUE FOR RIDMAPMEM SHOULD BE nK


Explanation: The value that you specified for the RIDMAPMEM option is insufficient for the utility to continue processing.

User response: Change the value of RIDMAPMEM to a value that is equal to or greater than the value in this message, and resubmit the job.

BMC50885I

RIDMAP: SPILLING OCCURRED BECAUSE explanation


Explanation: The utility used the spill data sets because it either exceeded the amount of memory that it could use (specified on RIDMAPMEM) or exceeded the number of data spaces that it was allowed to allocate.

User response: If the utility exceeded the amount of memory, increase the value of the RIDMAPMEM option, and resubmit the job. If the utility exceeded the number of data spaces, make the following adjustments:

  1. Try increasing the size of the data space gradually by adjusting the value of the RIDMDSSZ option.
  2. If you reach the maximum allowed value for RIDMDSSZ but still need more space, adjust the value of the RIDMMAXD option.


BMC50886E

RIDMAP: INTERNAL ERROR, text


Explanation: The utility failed with an internal error. This message provides diagnostic information for BMC Customer Support.

User response: Contact BMC Customer Support.

BMC50887I

RIDMAP: RIDMAPMEM CHANGED TO nK


Explanation: The amount of memory that was specified for the RIDMAPMEM option is insufficient. The utility changed the value to the amount shown in this message in order to continue processing the job.

User response: No action is required.

BMC50890I

taskNumber: ATTEMPTING TO action DATASET 'dataSetName'...


Explanation: The utility issues this message during the rename and delete operations that are associated with the staging data sets when you specify one of the following options:

  • For REORG PLUS, SHRLEVEL REFERENCE or SHRLEVEL CHANGE

  • For LOADPLUS, SHRLEVEL REFERENCE, LOAD REPLACE SHRLEVEL CHANGE, or LOAD RESUME YES SHRLEVEL CHANGE PART n REPLACE

The task number identifies the task that is associated with the operation. The value for action can be either RENAME or DELETE.


User response: No action is required. However, you should ensure that the utility subsequently issues a corresponding message, BMC50891I, which indicates that the operation for that data set completed successfully.

BMC50891I

taskNumber: DATASET 'dataSetName' IS status


Explanation: The utility issues this message during the rename and delete operations that are associated with the staging data sets when you specify one of the following options:

  • For REORG PLUS, SHRLEVEL REFERENCE or SHRLEVEL CHANGE

  • For LOADPLUS, SHRLEVEL REFERENCE, LOAD REPLACE SHRLEVEL CHANGE, or LOAD RESUME YES SHRLEVEL CHANGE PART n REPLACE

The utility issues this message in conjunction with BMC50890I, indicating that the operation for the data set completed successfully. The task number identifies the task that is associated with the operation. The value for status can be either RENAMED or DELETED.


User response: No action is required.

BMC50892I

OBD UPDATE HAS FAILED FOR OBJECT 'objectName'


Explanation: An error occurred during FASTSWITCH processing. The utility tries again to update the object descriptor (OBD) for the indicated object.

User response: If the retries fail and the utility terminated, attempt to restart the job. If you cannot restart the job, contact BMC Customer Support.

BMC50893I

HDELETE FAILED FOR 'dataSetName' RC=returnCode, REASON=reasonCode


Explanation: The staging data set is archived. The utility issued a DFSMShsm service request to invoke HDELETE to delete the data set; however, the HDELETE request failed. The return code and reason code can help determine the reason for the request failure. For information about these codes, see your DFSMShsm documentation. The utility continues processing.

User response: No action is required

BMC50894I

process PROCESS STARTING AT timestamp


Explanation: This message marks the beginning of the indicated process. If this process completes successfully, the utility issues message BMC50895I.

User response: No action is required.

BMC50895I

process COMPLETE. ELAPSED TIME = time


Explanation: The indicated process completed successfully in the amount of time shown in this message.

User response: No action is required.

BMC50896E

DATASET 'dataSetName' requirement


Explanation: The utility encountered a data set that does not meet the requirement shown in this message. The following information describes the requirements that this message displays:

Requirement displayed

Explanation

MUST BE EA ENABLED DUE TO DSSIZE

For a table space that is defined with DSSIZE greater than 4 gigabytes, the indicated data set must be an SMS-managed staging data set that is defined with extended addressability.

MUST NOT BE STRIPED

The indicated data set is an SMS-managed staging data set that is defined as striped, which the utility does not support.


User response: Your response depends on the requirement that this message displays:

Requirement displayed

Response

MUST BE EA ENABLED DUE TO DSSIZE

Ensure that the staging data set is defined correctly, and resubmit the job.

MUST NOT BE STRIPED

Ensure that the SMS STORCLAS for the staging data set does not specify a sustained data rate (which indicates a striped data set). Resubmit the job.


BMC50897I

FASTSWITCH PROCESSING BYPASSED DUE TO TOTAL DATASETS n LESS THAN FSTHRESHOLD n. RENAMES WILL BE PERFORMED


Explanation: You specified a value greater than 0 for the FSTHRESHOLD option, and the number of staging data sets required for this execution of the utility is less than this threshold. The utility performs rename processing on the staging data sets instead of FASTSWITCH processing.

User response: No action is required.

BMC50898S

FSTHRESHOLD PROCESS FOUND NO DATASETS


Explanation: The utility found no staging data sets, indicating an internal error.

User response: Contact BMC Customer Support.

BMC50899I

FASTSWITCH PROCESS FAILED AND SUCCESSFULLY BACKED OUT. ATTEMPTING RENAMES DUE TO FSFALLBACK YES


Explanation: The following conditions occurred:

  • FASTSWITCH processing failed.

  • If applicable, the utility successfully backed out FASTSWITCH changes.

  • FSFALLBACK YES is in effect.

Utility processing continues, using rename processing for the staging data sets.


User response: No action is required.

Was this page helpful? Yes No Submitting... Thank you

Comments