Messages BMC40300 through BMC40399

INTERNAL ERROR: routine, CODE = code

Explanation: An internal error has occurred.

User response: Contact BMC Support with the routine and code shown in this message. A snap dump is produced in SYSERR that may be useful in diagnosing the problem.

TABLESPACE = databaseName.tableSpaceName

Explanation: The table space name shown provides additional information for a previous message.

User response: See previous messages.

DSN = dataSetName

Explanation: The data set name shown provides additional information for a previous message.

User response: See previous messages.

INDEX = creator.ixname

Explanation: The index name shown provides additional information for a previous message.

User response: See previous messages.

RETURN CODE = returnCode

Explanation: The return code shown provides additional information for a previous message.

User response: See previous messages.

DSNUM = dsNum

Explanation: The data set number shown provides additional information for a previous message.

User response: See previous messages.

COLLECTING KEYS FOR:

Explanation: This message introduces a list of index names. The list indicates the indexes for which keys are being extracted.

User response: No action is required.

DDNAME = ddname

Explanation: The ddname shown provides additional information for a previous message.

User response: See previous messages.

BACKUP COPY FOR LOCAL SITE CAN NOT BE REGISTERED WITHOUT PRIMARY COPY

Explanation: An attempt was made to create a local backup image copy but no local primary copy was requested.

User response: If you want only one copy registered for local use, request it as the primary copy. If you want two copies, code both primary and backup copies.

BACKUP COPY FOR REMOTE SITE CAN NOT BE REGISTERED WITHOUT PRIMARY COPY

Explanation: An attempt was made to create a remote backup image copy but no remote primary copy was requested.

User response: If you want only one copy registered for remote use, request it as the primary copy. If you want two copies, code both primary and backup copies.

MUST ALSO RECOVER THE FOLLOWING PARTITION(S) FOR databaseName.tableSpaceName:

Explanation: A point-in-time recovery was requested for this table space and the log point selected for recovery is before a REORG or LOAD REPLACE that altered the partitioning key. The point-in-time recovery must include all partitions that were affected by the REORG or LOAD REPLACE.

User response: Rerun the recovery, specifying all of the partitions identified by the following BMC40305 messages.

NONEXISTENT INDEPENDENT DATA SET SPECIFIED FOR:

Explanation: Output to an independent data set was specified for the object named in message BMC40301 or message BMC40303 that follows this message and the data set named does not exist.

User response: Allocate all required independent data sets before running the utility.

MODEL = dataSetName

Explanation: The model data set name coded by the user is given.

User response: This message gives additional information for another message. See other messages.

GROUPNAME = groupName

Explanation: The change accumulation group name is given.

User response: This message gives additional information for another message. See other messages.

REQUIRED DATA SET MISSING FOR SPACE:

Explanation: A data set required to complete the requested action is not defined. One of the following conditions exists:

• A data set for a VCAT-defined object does not exist.

• A log only (either LOGONLY or LOGAPPLY ONLY) recovery was requested for the object, but its VSAM data set is not defined.

• The BACKOUT option was specified for the object, but its VSAM data set is not defined.

• A table space data set required to satisfy a REBUILD INDEX request is not defined.

User response: No action is required.

• Create data sets for all needed VCAT-defined objects.

• If the request was for LOGONLY or LOGAPPLY ONLY, the data set must be restored from a backup before the operation can proceed.

• BACKOUT recovery is not possible when the data set is missing. Use RECOVER TABLESPACE or RECOVER INDEX without BACKOUT or REBUILD INDEX instead.

• Recover any table space for which the data set is missing in the same step as any rebuilds for indexes on that table space.

DUPLICATE NAME = dataSetName FOR:

Explanation: Two independent data set name models for different objects resolved to the same data set name.

User response: Change one of the models so that all objects have a unique data set name.

INDEX REBUILD WITH INDEPENDENT INTABLESPACE CONFLICTS WITH NAME ON INDEPENDENT OUTSPACE FOR TABLE SPACE:

Explanation: The data set name specified with INDEPENDENT INTABLESPACE in a REBUILD INDEX statement is different from the data set name specified with INDEPENDENT OUTSPACE in the RECOVER TABLESPACE statement for the table space over which the index is defined.

User response: Specify the same data set name for the index INDEPENDENT INTABLESPACE and the table space INDEPENDENT OUTSPACE options.

RECOVER TOLOGPOINT LASTQUIESCE FOR OBJECT

Explanation: TORBA/TOLOGPOINT LASTQUIESCE was specified for the table space or index. Subsequent messages identify the table space or index name. This message introduces information about copies not considered because they are registered after the quiesce.

User response: No action is required.

DISCARDING COPY:

Explanation: This message might be issued for one of the following reasons:

• The image copy shown was ignored during TORBA LASTQUIESCE recovery processing because it was made after the last quiesce for the data set shown in the accompanying message BMC40302.

• The image copy shown was ignored because the copy did not complete before the recovery point. The PIT_RBA column in SYSIBM.SYSCOPY contains the logpoint at which the copy completed.

• An inline copy was ignored because of limitations on the use of inline copies.

• A message explaining the reason for discarding follows.

• The image copy shown was ignored because the PIT_RBA of the image copy is greater than the oldest inflight transaction. The image copy could contain updates that were inflight at the recovery point.

User response: No action is required.

RECOVER TOCOPY LASTCOPY SPECIFIED BUT NO USABLE COPY FOUND IN SYSIBM.SYSCOPY:

Explanation: No usable image copy for the space shown in the accompanying message BMC40301 was found in SYSIBM.SYSCOPY (for table spaces and COPY YES indexes) or BMCXCOPY (for COPY NO indexes).

User response: If sufficient log records exist to recover the space, you may attempt a recovery to the required log point. Otherwise, the space is not recoverable.

RECOVER TORBA LASTQUIESCE SPECIFIED BUT NO QUIESCE FOUND:

Explanation: No quiesce point was found in SYSIBM.SYSCOPY for the table space shown in the accompanying messageBMC40301; or if the accompanying message is BMC40303, naming an index, no quiesce point was found in SYSIBM.SYSCOPY for the related table spaces.

User response: You must select a log point for your recovery rather than specifying LASTQUIESCE.

RECOVER FROMRBA LASTQUIESCE SPECIFIED BUT NO QUIESCE FOUND:

Explanation: No quiesce point was found in SYSIBM.SYSCOPY for the table space shown in the accompanying message BMC40301; or if the accompanying message is BMC40303, naming an index, no quiesce point was found in SYSIBM.SYSCOPY for the related table spaces.

User response: You must select a log point for your recovery rather than specifying LASTQUIESCE.

RECOVER FROMRBA LASTCOPY SPECIFIED BUT NO COPY FOUND:

Explanation: No image copy was found in SYSIBM.SYSCOPY (for table spaces and COPY YES indexes) or BMCXCOPY (for COPY NO indexes) for the space shown in the accompanying message (BMC40301 or BMC40303).

User response: You must select a log point for your recovery rather than specifying LASTCOPY.

RECOVER TOLOGPOINT LASTQUIESCE FOR MULTIPLE SPACES BUT LAST QUIESCE IS NOT COMMON

Explanation: The utility requires that all spaces recovered in a single RECOVER statement have a common last quiesce point if TORBA/TOLOGPOINT LASTQUIESCE is requested.

User response: If you want to process spaces to different last quiesce points, use multiple RECOVER statements.

QUIESCE = X'logPoint'

Explanation: This message provides additional information for a previous message.

User response: No action is required.

UNABLE TO RECORD FALLBACK IN BMCSYNC - COLUMN SIZE EXCEEDED

Explanation: An internal error has occurred.

User response: Contact BMC Support.

COPIES NOT REGISTERED FOR databaseName.tableSpaceName BECAUSE OF keyword KEYWORD IN RECOVER STATEMENT

Explanation: The utility cannot register copies made because of the keyword shown.

User response: No action is required.

TABLESPACE SCAN FOR SYSTABLEPART STARTED FOR n OBJECTS

Explanation: Fast Catalog Access failed or was not attempted for the number of objects specified. SYSTABLEPART is scanned to obtain necessary information.

User response: No action is required.

TABLESPACE SCAN FOR SYSINDEXPART STARTED FOR n OBJECTS

Explanation: Fast Catalog Access failed or was not attempted for the number of objects specified. SYSINDEXPART is scanned to obtain necessary information.

User response: No action is required.

function STARTING datetime

Explanation: The specified function began executing at the date and time shown.

User response: No action is required.

function FINISHED.

Explanation: The specified function finished executing. Subsequent messages display the elapsed and CPU times for the function.

User response: No action is required.

FAILURE IN UTILID BUILD, RETURN VALUE = returnCode

Explanation: A job failed while trying to build the default utility ID. Your utility ID should be in the form jobName.userID.

User response: Contact BMC Support.

FROMRBA > TOLOGPOINT:

Explanation: A FROMRBA was specified with TORBA/TOLOGPOINT in a LOGAPPLY ONLY recovery. The TORBA occurred before the FROMRBA, making the recovery invalid.

User response: Modify the specified log point value so the FROMRBA occurs before the TORBA/TOLOGPOINT event. Make sure that TORBA or TOLOGPOINT specifies an RBA for a non-data-sharing system or an LRSN for a data sharing system.

ESTIMATION PARAMETER MISMATCH ON LOGSORT STATEMENTS, VALUES WILL BE TREATED AS ESTIMATED

Explanation: Multiple LOGSORT statements are coded in a job step. At least one statement specifies NUMREC ABS while another specifies NUMREC EST. If one statement specifies EST, all statements must follow this strategy.

User response: No action is required. The utility assumes the EST strategy for all statements.

AVERAGE LOG RECORD SIZE GREATER THAN 32756 WAS CODED, CHANGED TO 32756

Explanation: A LOGSORT statement is coded with an AVGRECSZ value greater than 32,576.

User response: No action is required. The utility assumes an average record size of 32,576.

MAY NOT SPECIFY WILDCARDED TABLESPACE WITH SPECIFIC DSNUM

Explanation: A wildcard appeared in place of a table space name. A DSNUM was also coded. This combination is not allowed. If you are performing change accumulation, each partition of partitioned spaces will have separate log ranges recorded.

User response: Remove the DSNUM specification and resubmit the job.

SPACE = databaseName.tableSpaceName

Explanation: The space shown applies to a preceding message.

User response: See preceding messages.

INDEXSPACE = creator.ixname

Explanation: The index space shown applies to a preceding message.

User response: See preceding messages.

VOLUME = volume

Explanation: The volume shown applies to a preceding message.

User response: See preceding messages.

DATA SET dataSetName WAS SUCCESSFULLY ALLOCATED TO DDNAME ddname ELAPSED = hh:mm:ss

Explanation: The data set named was dynamically allocated to the ddname shown in this message. The elapsed time is roughly the amount of time required for a tape mount, if one was required. This message is displayed when the amount of time required to mount a tape is greater than 30 seconds.

User response: No action is required.

FAILURE IN DYNAMIC ALLOCATION OF DATASET dataSetName

Explanation: The utility dynamically allocates input image copies, logs, input and output change accumulation files, table spaces and index spaces, and data sets specified as output data sets independent of Db2. An allocation has failed.

User response: If the utility does not recover from the error, review messages that follow for failure information. Consult SVC99 references or contact BMC Support.

DDNAME ddname (DSN dataSetName) WAS SUCCESSFULLY UNALLOCATED

Explanation: A dynamically allocated data set is released.

User response: No action is required.

FAILURE IN DYNAMIC UNALLOCATION OF DATASET dataSetName

Explanation: The utility dynamically allocates input image copies, logs, input and output change accumulation files, table spaces and index spaces, and data sets specified as output data sets independent of Db2. A dynamic deallocation failed.

User response: If the utility does not recover from the error, review message BMC40361 that follows the failure codes. Consult SVC99 references or contact BMC Support.

IDCAMS FAILURE IN command WITH RC returnCode. OUTPUT FOLLOWS:

Explanation: The IDCAMS command shown in this message failed with the return code shown.

User response: Review the output to see if you can recover from the error.

AN IDCAMS 'command' OPERATION WAS SUCCESSFUL ON DATASET dataSetName

Explanation: The command shown in this message was successful for the data set.

User response: No action is required.

ALLOCATION INFORMATION RETRIEVAL FOR DDNAME ddname FAILED WITH RC returnCode - ERROR CODE = code, INFO CODE = code

Explanation: The utility failed to retrieve allocation information for a data set specified in the JCL.

User response: Contact BMC Support.

INPUT KEY FILE ddname IS INVALID. CHECK YOUR JCL TO ENSURE THAT THE DATASET CAME FROM A SUCCESSFUL UNLOADKEYS

Explanation: The ddname shown is specified as an input key data set for RECOVER BUILDINDEX. However, this data set is not in the correct format for a data set written during RECOVER UNLOADKEYS execution.

User response: Check your JCL to ensure that all input key data sets were written by a RECOVER UNLOADKEYS job. If the JCL was not correct, correct and submit the RECOVER BUILDINDEX job again. If you believe the data set is correct, contact BMC Support.

ERROR DURING JSCB ACCESS, RC = returnCode, FUNCTION = function

Explanation: An internal error has occurred.

User response: Contact BMC Support.

ERROR CODES: codes

Explanation: The codes shown are diagnostic codes that go with previous messages.

User response: See preceding messages.

ddname CODED IN REGISTER LIST, BUT NOT IN COPY DDNAME LIST

Explanation: ddname was included in the REGISTER ddname list option but is not coded in either the OUTCOPYDDN or RECOVERYDDN lists. Also, ddname is not the default ddname for any copy.

User response: Include ddname in the appropriate copy list.

REORG LOG(NO) INLINE COPY, STYPE='W'

Explanation: The utility is summarizing information about a copy and has identified it to be an inline copy.

User response: No action is required.

BUFFER CREATED FOR PAGE SIZE nK, REFRESH = flag

Explanation: This message provides information about the utility's buffers. The page size is 4K, 8K, 16K, or 32K. The refresh flag indicates whether pages in the buffer need to be refreshed from disk.

User response: No action is required.

RANDOM BUFFER: NUMBER OF PAGES = pages, MINIMUM CLEAN = cleanPages, NUMBER TO WRITE PER I/O = writes

Explanation: This message provides information about utility buffers.

User response: No action is required.

RANDOM BUFFER: MAXIMUM OUTSTANDING WRITES = writes, MAXIMUM OUTSTANDING READS = outreads, HASH HEADS = heads

Explanation: This message provides information about utility buffers.

User response: No action is required.

SEQUENTIAL BUFFER: NUMBER OF CYLINDERS = cylinders, IDLE CYLINDERS = idleCylinders, CI'S PER CYLINDER = cis

Explanation: This message provides information about utility buffers.

User response: No action is required.

BUFFER MANAGER TERMINATION, GET PAGE COUNT = gpCount, RANDOM SEARCH COUNT = rpCount

Explanation: This message provides buffer manager performance statistics. gpCount is the number of get pages requested. rpCount is the number of random pages requested.

User response: No action is required.

CYLINDERS WRITTEN = cylCount

Explanation: This message provides buffer manager performance statistics. cylCount is the number of cylinders written.

User response: No action is required.

TOTAL WAITS IN BUFFER MANAGER = wtCount

Explanation: This message provides buffer manager performance statistics. wtCount is the total number of buffer waits including random read waits, random write waits, and cylinder write waits.

User response: No action is required.

RANDOM WRITE WAITS = wrCount, RANDOM READ WAITS = rdCount, RANDOM SYNC WAITS = syncCount

Explanation: This message provides buffer manager performance statistics.

User response: No action is required.

CYLINDER WAITS = cylCount, SEQUENTIAL SYNC WAITS = ssCount

Explanation: This message provides buffer manager performance statistics. cylCount is the number of waits for cylinder writes. ssCount is the number of synchronous waits for cylinder writes.

User response: No action is required.

RANDOM READS = rdCount, HITS = htCount

Explanation: This message provides buffer manager performance statistics. rdCount is the number of read I/Os issued for random buffer. htCount is the number of random page requests found in the buffer.

User response: No action is required.

PREFETCH COUNT = pfCount, HITS CAUSED BY PREFETCH = cpCount, HITS ON PREFETCH = hpCount

Explanation: This message provides buffer manager performance statistics. pfCount is the number of prefetch requests. cpCount is the number of prefetched pages used. hpCount is the number of hits on attempted prefetches.

User response: No action is required.

I RANDOM WRITES = wrCount IN grCount GROUPS

Explanation: This message provides buffer manager performance statistics. wrCount is the number of random pages written. grCount is the number of write groups written.

User response: No action is required.

TOTAL WAIT TIME = time1, RANDOM WRITE TIME = time2, RANDOM READ TIME = time3

Explanation: This message provides buffer manager performance statistics. It displays the time spent waiting for I/O, performing random writes, and performing random reads.

User response: No action is required.

CYLINDER WAIT TIME = time

Explanation: This message provides buffer manager performance statistics. It displays the time spent performing cylinder wait.

User response: No action is required.

text

Explanation: This message explains a failure in dynamic allocation.

User response: See previous message.

UNABLE TO RETURN ALLOCATION MESSAGES, RETURN CODE returnCode, REASON CODE reasonCode, FUNCTION ID function

Explanation: This message explains a failure in dynamic allocation.

User response: See previous message.

FROMLRSN > TOLRSN

Explanation: A request has been passed to the utility such that the starting LRSN for the objects overall range is higher than the ending LRSN. This message will be followed by additional messages, giving the range of LRSNs, the space name, and the partition if necessary.

User response: If you have specified TOLOGPOINT or TORBA, check the value coded and correct it if necessary. Consider changing an incorrect FROMRBA value if you coded one. If this is not the problem, run REPORT RECOVERY for the space and contact BMC Customer Support.

DUPLICATE VOLUME DETECTED/SKIPPED (volumeSerialNumber) WHILE PARSING OPTIONS STOGROUP XXXXX USEORDER(...)

Explanation: A duplicate volume name was found in the USEORDER specification. This volume name is ignored.

User response: No action is required.

RECOVER TOLOGPOINT LASTCOMMONQ

Explanation: TORBA/TOLOGPOINT LASTCOMMONQ was specified for the activity of the table space or index identified in subsequent messages. This message introduces information about copies not considered because they are registered after the quiesce.

User response: No action is required.

ELIMINATING WRITE KEYS STEP FOR:

Explanation: A restore or merge phase failed. The index keys cannot be written.

User response: Determine how to recover the table space objects and resubmit the unloadkeys recovery.

SKEY FILE ddname1 AND ddname2 REFLECT DIFFERENT KEY LENGTHS

Explanation: The SKEY files input into the RECOVER BUILDINDEX contain different maximum key lengths. The indexes in the RECOVER BUILDINDEX SYSIN must correspond with the indexes from a single set of RECOVER UNLOADKEYS. If index1 part 1 and index2 part 1 of a given table space were unloaded in separate jobs, they cannot be recovered with the same RECOVER BUILDINDEX.

User response: Verify that the input files are correct. If multiple RECOVER UNLOADKEYS jobs were generated for different indexes, run multiple RECOVER BUILDINDEX jobs.

PART n OF creator.ixname HAS BEEN UNLOADED MUTLIPLE TIMES

Explanation: A RECOVER BUILDINDEX has found the keys of a given partition and index in multiple input unloadkeys files.

User response: Check the input SKEYDDN statements to be sure that a data set has not been named multiple times. Check the RECOVER UNLOADKEYS output to see if the keys were unloaded properly.

NO KEYS WERE FOUND FOR creator.ixname

Explanation: A RECOVER BUILDINDEX was requested using unloadkeys as input. The input SKEYDDN data sets did not contain any keys for the named index.

User response: Check the input SKEYDDN statements to be sure that the data set names are correct. Check the RECOVER UNLOADKEYS output to see if the keys were unloaded properly.

KEYS FOR PART n OF creator.ixName ARE MISSING

Explanation: A RECOVER BUILDINDEX was requested using unloadkeys as input. The input SKEYDDN data sets did not contain any keys for the named partition and index.

User response: Check the input SKEYDDN statements to be sure that the data set names are correct. Check the RECOVER UNLOADKEYS output to see if the keys were unloaded properly.

LOG RECORD AT RBA X'hexValue' CREATED PRIOR TO DB2 V3.1 NOT SUPPORTED

Explanation: The utility has found a log record that was created by a version of Db2 earlier than version 3.1. This log record is not supported by the current release of the utility.

User response: Contact BMC Support.

LOAD REPLACE LOG(YES) INLINE COPY, STYPE='R'

Explanation: The utility is summarizing information about a copy and has identified it to be an inline copy.

User response: No action is required.

LOAD REPLACE LOG(NO) INLINE COPY, STYPE='S'

Explanation: The utility is summarizing information about a copy and has identified it to be an inline copy.

User response: No action is required.