Messages BMC8700 through BMC8799

CMD nnn: IDCAMS INVALID ON REC WITH AMSPDS DUMMY

Explanation: The AMSPDS DD statement has been specified as DUMMY. This is not allowed when the IDCAMS keyword is used on a REC statement. The job step terminates with user abend U4094.

User response: Specify a valid partitioned data set with VSAM DELETE/DEFINE statements for the databases, or remove the AMSPDS DD statement. Resubmit the job.

DBRC(Y) AND DSALLOC(Y) ARE REQUIRED WHEN MULTIPLE READERS ARE USED

Explanation: The RDRS keyword was found. DSALLOC(Y) or DBRC(Y) was not specified. These keywords are required when multiple readers are used. The job step terminates with user abend U4094.

User response: Specify both DBRC(Y) and DSALLOC(Y) when the RDRS keyword specifies multiple readers.

INVALID ENTRY FOUND FOR ALG KEYWORD. MUST BE 1, 2, or 3

Explanation: The value supplied for the ALG keyword must be 1, 2, or 3. The job step terminates with user abend U4094.

User response: Specify a valid entry for the ALG keyword.

DEDB DATABASES NOT SUPPORTED WITH IMS PRIOR TO 2.2

Explanation: The installed version of IMS is prior to Version 2.2, and a DEDB-type database was encountered. The job step terminates with user abend U4094.

User response: Upgrade IMS to Version 2.2 or later, or do not try to process DEDB-type databases.

groupName,dbdName,dsgName TIMESTAMP yy.ddd hh.mm.ss.t WITHIN ALLOCATION RANGE

Explanation: The specified special recovery time stamp falls between the deallocation time and next allocation time of an allocation record for the specified database. The job step terminates with user abend U4094.

User response: Select a special time stamp recovery time stamp that is at a time when the database is deallocated.

CMD nnn, TIMESTAMP PARAMETER IS INVALID

Explanation: The time stamp entered is invalid. Two formats for the time stamp are available: yy.ddd.hh.mm.ss.t and yydddhhmmsst. The job step terminates with user abend U4094.

User response: Correct the time stamp using either format and resubmit the job.

CMD nnn: NO EXPLICIT DELETE/DEFINE PRESENT FOR INDEX index

Explanation: An index recovery has been generated from a BLDINDEX request. The IDCAMS keyword for the primary database specifies a specific member name; therefore, IDCAMS will only be called during the recovery of the primary database. Processing continues.

User response: No action is necessary. Be sure that the IDCAMS member specified on the REC statement has delete/defines for the correct database data sets. The recommended technique is to use IDCAMS(*) so that BMC Recovery utility will call IDCAMS for each recovered data set, including indexes.

groupName,dbdName,dsgName DSN USER EXIT ENDED WITH NON ZERO RETURN CODE

Explanation: The data set name user exit returned a nonzero return code. This specific data set is disabled. If any other IC data sets are valid and available, the image copy proceeds.

User response: Determine why the user exit is returning a nonzero return code and correct the problem.

groupName,dbdName,dsgName OPEN LOG VOLUME CANNOT BE USED FOR SPECIAL TIMESTAMP RECOVERY

Explanation: The DBRC interface routine has encountered an open log volume while searching for the correct log volume to use for special time stamp recovery. The specified time stamp is greater than the start time of the open volume, and the special time stamp recovery is invalid. The open PRILOG record will be returned as-is to DBRC, and DBRC will proceed as if special time stamp recovery were not in effect. The recovery may be subsequently be cancelled by DBRC for various reasons, or if it is a valid recovery point, the recovery may eventually run when the log volume is archived.

User response: Specify a correct time stamp, or archive the volume required for the recovery.

groupName,ddname,dscbName MODEL DSCB NOT FOUND

Explanation: The error can result in two ways. The data set name specified in the CADSCB or ICDSCB keyword is wrong; or the data set name specified is correct, but it is not cataloged. The allocation attempts for the output data set terminate. The task continues only if there is an alternate usable data set.

User response: Correct the value of the CADSCB or ICDSCB keyword, or catalog the DSCB name.

ddname INDOUBT UPDATES FOR dbdName areaName WILL BE DROPPED. TOKEN IS imsID xxxx xxxx

Explanation: DEDB database update records from the log or change accumulation data set are ignored because there is no corresponding COMMIT or ABORT record. The corresponding recovery token is printed. The product sets condition code 4; processing continues.

User response: Verify that the correct change accumulation input and log input are being used.

taskID ERROR ENCOUNTERED

MODULE module FUNCTION function RC=returnCode

Explanation: The Concurrent Pointer Checking feature found a pointer error. This message is a warning; the job step continues.

User response: Correct the pointer errors, if necessary.

COMPRESSION INITIALIZATION FAILURE

Explanation: The CSRCESRV inquiry indicates an operating system or hardware error. Compression capability is not available for the change accumulation or log records. The change accumulation task is cancelled. Other change accumulation tasks continue to process.

User response: Place the CSRCEXA module in the STEPLIB or LNKLIST.

taskID PREVIOUS RUN DATE GREATER THAN PURGE DATE

Explanation: The purge date specified is prior to the time stamp on the input change accumulation. No records will be purged from the output change accumulation. The product issues return code 4. The change accumulation task continues.

User response: Correct the purge date and resubmit the job.

ddname CANNOT BE USED AS A SORT AND A PSORT

Explanation: You have specified the sort identifier as a PSORT and it is actually a SORT, or you have specified the sort identifier as a SORT and it is actually a PSORT. PSORTs are used exclusively for sorting primary index records and cannot be used for sorting log records. SORTs are used for sorting log records and cannot be used for sorting primary index records. Control card scan processing continues. The step terminates with control card errors.

User response: Correct the specification and resubmit the job.

taskID UNMATCHED SPLIT SEGMENT(S)

Explanation: During the extraction of the primary index records, the program encountered either a prefix or a data record for a split segment that could not be matched with its counterpart. The product sets a condition code of 4; processing continues.

User response: Run POINTER CHECKER PLUS or an equivalent on the database to determine if an error condition exists. If no error exists, contact BMC Customer Support.

ddname UNABLE TO DETERMINE MAINTENANCE LEVEL OF CHANGE ACCUMULATION MODULE

Explanation: The change accumulation reader routine reads DFSUCUM0 from the DFSRESLB data set and determines the format for spill records. If the maintenance level is not within the range of instructions the change accumulation reader routine expects, the product issues this message. Processing continues and the program assumes that the most recent format records are being used. If the records are in the older format, the program abends later.

User response: Contact BMC Customer Support.

CMD nnn: INVALID CHARACTER IN MAINSIZE PARAMETER

Explanation: The value specified for the MAINSIZE parameter is not valid. The job step is cancelled with user abend U4094.

User response: Correct the value specified for the MAINSIZE keyword and resubmit the job.

groupName,dbdName,dsgName HSSP IMAGE COPY NOT SUPPORTED FOR FUNCTION

Explanation: The input image copy for the function was an HSSP image copy and it is not allowed for the function. The job step is cancelled with user abend U4094.

User response: The function does not support HSSP input. Use a different function.

groupName,dbdName,dsgName DUMP ONLY RECOVERY GENERATED

Explanation: This message is issued when all of the following conditions are true:

• The data set is registered in DBRC as nonrecoverable.

• The database is not an index database.

• DBRC is active.

• Dynamic allocation is requested.

• LOG and ACCUM keywords are specified individually or together.

User response: Remove the LOG and ACCUM keywords to eliminate the return code.

groupName,dbdName,dsgName function FOR NON-RECOVERABLE DATABASE INVALID

Explanation: An online image copy or incremental image copy has been explicitly requested for a non-recoverable database. These operations require log or change accumulation input during processing or at recovery time. Since neither log or change accumulation input will be available when needed, the online image copy or incremental image copy request is not valid. The task terminates with user abend U4094.

User response: Remove the online image copy or incremental image copy control statement for the non-recoverable database.

dbdName,imsID PDX SPECIFICATIONS MEMBER BYPASSED

Explanation: The PDX member specified has an invalid data length. The PDX member is ignored. Processing continues.

User response: Delete and re-create the PDX member.

identifier LOGICAL GENJCL FAILED RC=returnCode

Explanation: The logical GENJCL.CA has completed with a nonzero return code. The return code is analyzed by the program. If the program is able to continue, it issues the message BMC8723W and return code 4

User response: Read the preceding DBRC-issued DSP messages to determine the cause of the GENJCL failure.

identifier LOGICAL GENJCL FAILED RC=returnCode

Explanation: The logical GENJCL.CA has completed with a nonzero return code. The return code is analyzed by the program. If the program is unable to continue, it issues the message BMC8723C and terminates with user abend U4094.

User response: Read the preceding DBRC-issued DSP messages to determine the cause of the GENJCL failure.

groupName,dbdName,dsgName RECORD LENGTH NOT EQUAL TO VSAM RECSIZE

Explanation: A record read from the database being copied was a different length than that specified in the VSAM cluster. This message appears only for a SHISAM database that does not contain fixed records (that is, records which are not the size specified in the VSAM RECSIZE parameter). The record is processed normally, and the image copy proceeds if no other errors are encountered. However, if this image copy is used to recover the database, the VSAM records may be a different length in the recovered database.

User response: No action is required.

taskID inputDataSetDdname ERROR DURING function

taskID inputDataSetDdname I/O ERROR unit CMD(commandCode) STATUS(status) SENSE(data) text

text

Explanation: An I/O error condition was detected for an input data set. The message text varies according to the I/O error condition that was detected. The following values can be displayed in the message text, depending on the error:

The input data set is disabled and the associated task may terminate. Additional messages follow this warning message to indicate whether the process can continue.

User response: Review the job output for any related error messages that may further describe the I/O error symptoms. Contact BMC Customer Support if further assistance is required.

ddname text

Explanation: The text of this message varies according to the type of processing being done. A problem occurred during output EXCP processing for the indicated ddname while performing the function listed. This message is followed by another message giving details about the problem encountered. Additional messages will be issued indicating the further action taken by the system.

User response: Correct the condition indicated by the message that follows this one and resubmit the job if necessary.

LOGIC CODE code IN CSECT name

Explanation: A catastrophic error has been encountered, and processing cannot continue. The message text provides some basic information needed by BMC Customer Support to diagnose the problem. The job step terminates with user abend U4095.

User response: Save all job documentation relating to this problem (JCL, job listing, and SYSUDUMP). Contact BMC Customer Support.

groupName DBRC NOTIFY ERROR. RC=returnCode

Explanation: A nonzero return code was received from DBRC while attempting to do a NOTIFY.CA. The task terminates with user abend U4095.

User response: Review the job output for any error messages issued by DBRC. DBRC messages are prefixed by the letters DSP.

groupName,ddname MISSING OR INCOMPLETE DETAIL RECORD

Explanation: The flags in the change accumulation record indicate that a detail record has been segmented into two or more logical records, but one or more segments are missing. The task terminates with user abend U4095.

User response: Save all job documentation including the input change accumulation and log files. Contact BMC Customer Support.

groupName,ddname MISSING OR INCOMPLETE SPILL RECORD

Explanation: The flags in the change accumulation record indicate that a spill record has been segmented into two or more logical records, but one or more segments are missing. The task terminates with user abend U4095.

User response: Save all job documentation including the input change accumulation and log files. Contact BMC Customer Support.

groupName PREVIOUS RUN DATE GREATER THAN PURGE DATE

Explanation: The input change accumulation header run date and time are greater than the specified purge date, and the current purge date is different from the previously specified purge date. Any log records that were previously accumulated that are prior to the new purge date are ignored during recovery. Processing continues.

User response: No action is required.

taskID, ddname HISAM UNLOAD NOT VALID FOR HISAM OR A NON-UNIQUE INDEX ORGANIZATION

Explanation: HISAM unload data sets cannot be used for recovery if the HISAM database has an overflow data set. HISAM unload data sets are also invalid for nonunique keyed index databases. The task terminates with user abend U4095.

User response: A standard image copy must be supplied as input to recovery for nonunique keyed database organizations or HISAM databases with an overflow component.

ddname SORT RELATED TASK FAILED

Explanation: The job step is being terminated because a sort task for the indicated ddname has abended. The task terminates with user abend U4094.

User response: Review the other messages to determine the cause of the error.

dbdname, ddname DBD KEY LENGTH DOES NOT MATCH CHANGE ACCUM RECORD

Explanation: The key length defined in the DBD does not match the key length obtained from the change record. Processing continues. The key length from the DBD is used for processing.

User response: Ensure that the correct DBD library is being used and that an image copy was taken after the DBD key length was changed. An attempt to recover the database using this change accumulation will result in a corrupted database.

ddname KEY LENGTH OF nnn IS TOO SHORT. MUST BE AT LEAST nnn

Explanation: The default key length or the key length specified on the SORT control statement is too short. The BMC Change Accumulation utility uses the key length in the DBD in all cases, except when you specify *ALL. The task terminates with user abend U4094.

User response: Ensure that the correct DBD library is being used. If *ALL is specified, resubmit the job and specify a key length of 255. Then review the processing log to determine the highest key length for the run. Add a small cushion to this minimum and use that in future runs. Specifying an unnecessarily large key length can waste sort work space.

ddname DSG nn MISSING FROM ddname

Explanation: The Compare utility found a header record that exists on one change accumulation data set but not the other. All records for that DSG are skipped.

User response: Ensure that the data sets being compared were created with the same input, including the same input control statements.

taskID outputDataSetType DATA SET dsname MATCHES inputDataSetType DATA SET

Explanation: The output data set name matches the input data set name. This error makes the output data set unusable. A following message indicates the final disposition of the job step. outputDataSetType can have a value of IC n or CA n. inputDataSetType can have a value of DUMP or ACUM. The indicated output data set is disabled, and no data is written to that data set.

User response: Check the accompanying message for the final disposition of the job. The program will attempt to continue as long as one output data set is available.

CMD nnn: REQUESTED DB1* FUNCTION IS NOT SUPPORTED

Explanation: The BMC Change Accumulation utility does not support the function requested on the DB1 SYSIN control statement. Only the *OTHER function is supported if a DFSUDD1 DD statement is present in the JCL. The *ALL and DBDNAME functions are always invalid. The program continues scanning control statements but terminates at the end of the statement scan with scan errors.

User response: Remove or disable the invalid DB1 control statements, or if you have specified *OTHER, ensure that a DFSUDD1 DD statement is present in the JCL.

LOG ddname /DYNAMIC NOT REFERENCED ON A GROUP CONTROL STATEMENT.

Explanation: A LOG command for the indicated ddname has been specified in the input control statement stream, but there are no explicit or implicit references to it by any CA or IIC commands. The program continues scanning control statements but terminates at the end of the statement scan with scan errors.

User response: Remove the extraneous command, or correct the incorrect references on the CA or IIC control statements.

taskID KEY ID ON DDNAME ddname DOES NOT EXIST ON DATABASE

taskID MISSING KEY IS key

Explanation: An encountered log data set or a change accumulation data set record has a key that does not exist in the recovered data set. The probable cause is missing log data sets. The first message gives the ddname of the log or change accumulation data set; the second message gives the missing key. The recovery terminates abnormally.

User response: Rerun the recovery job with correct log input data sets.

SPECIAL TIMESTAMP RECOVERY IS NOT ALLOWED WITH TIMESTMP(LASTIC)

Explanation: You used the STR(Y) keyword (requests a special time stamp recovery) and the TIMESTMP(LASTIC) keyword (time stamp of the last image copy). You cannot use the LASTIC value and request a special time recovery at the same time. The job step terminates with user abend U4094.

User response: Depending on the type of recovery that you need, select the correct keywords and keyword value. Resubmit the job.

DBRC IS REQUIRED FOR TIMESTMP(LASTIC)

Explanation: You used the TIMESTMP(LASTIC) keyword (time stamp of the last image copy), but DBRC was not active. DBRC(Y) is required when you specify TIMESTMP(LASTIC). The job step terminates with user abend U4094.

User response: Depending on the type of recovery that you need, select the correct keywords and keyword value. Resubmit the job.

ROLL-FORWARD RECOVERY NOT ALLOWED WITH TIMESTMP(LASTIC)

Explanation: You requested a roll-forward recovery (by omitting the DUMP keyword) and also specified TIMESTMP(LASTIC) keyword. You cannot use the LASTIC value and request a roll-forward recovery at the same time. The job step terminates with user abend U4094.

User response: Depending on the type of recovery that you need, select the correct keywords and keyword values. Resubmit the job.

TIMESTMP(LASTIC) NOT ALLOWED ON HIC/PIC COMMAND

Explanation: You included a HIC or PIC control statement and used the TIMESTMP(LASTIC) keyword (time stamp of the last image copy). You cannot use the LASTIC value and a HIC or PIC control statement at the same time. The job step terminates with user abend U4094.

User response: Depending on the type of recovery that you need, select the correct keyword values and control statements. Resubmit the job.

REQ'D RECOVERY FUNCTION FOR dbdName NOT SPECIFIED

Explanation: You requested a roll-forward recovery for a HIDAM primary database, specified BLDINDEX(Y), and the primary index is not being recovered. BLDINDEX(Y) cannot be specified for a primary index. A REC or AREC control statement is required for a roll-forward recovery of the primary index. BLDINDEX(Y) only works for a secondary index of a HIDAM database when the primary index is also recovered. The job step terminates with user abend U4094.

User response: Use BLDINDEX(Y) and specify a recovery function for the HIDAM primary index or do not use BLDINDEX(Y).

groupName CA AS OF timestamp WILL NOT BE USED FOR STR RECOVERY TO yy.ddd hh.mm.ss.t

Explanation: The DBRC interface module detected a change accumulation data set that extends beyond the time stamp to which the special time stamp recovery is effective. The change accumulation data set RECON record is internally marked in error and the recovery continues using the prior change accumulation data set and any intervening log data sets. The RECON data set is not modified.

User response: No action is required.

{PRDR groupName,dbdName,dsgName REQUIRED VOLUME volser IN USE BY ANOTHER JOB; REPLY R OR C |group,dbdName, WAITING FOR VOLUME volser TO CANCEL WAIT REPLY 'C'}

Explanation: The input tape data set is not available; it is probably being used by another job. A message has been sent to the console operator indicating possible actions. This message is issued only if the product is running in an authorized environment. The task goes into a WAIT condition after the message is issued. If there is no reply to this message, the product will wait for one minute and then try again to dynamically allocate the data set.

User response: Allow the product to try again, or select one of the following replies:

groupName, dbdName, dsgName DYNAMIC ALLOCATION OF OSAM DATASETS IS REQUIRED WITH IDCAMS PROCESSING

Explanation: IDCAMS(*) has been specified. The AMSPDS DD data set has a member for the data set referenced in this message and a DD statement for the data set is specified in the JCL. It is not possible to have the OSAM DD statements in the JCL and delete/allocate the OSAM data sets safely. Unlike VSAM, OSAM data sets may or may not be cataloged, and reside on several volumes. Therefore, OSAM data sets cannot be deallocated and allocated like VSAM data sets. (An S213-04 abend can occur.) The job step terminates with user abend U4094.

User response: Either remove the OSAM DD statements from the JCL or do the delete/allocate in a prior step and remove the member from the AMSPDS DD data set.

groupName,dbdName,dsgName INVALID DSORG - DATA SET NOT INITIALIZED

Explanation: The database data set cannot be opened because the data set control block does not contain a valid data set organization code. The most likely cause for this problem is that the data set has not been properly allocated and initialized. The job step terminates with user abend U4094.

User response: Look at the IEC161I preceding message to determine why the database data set could not be opened, or ensure that the database data set has been allocated and initialized correctly.

groupName,dbdName,dsgName ddname STACK MUST BE ALLOCATED TO A TAPE DEVICE

Explanation: Stacked output data sets have been requested to the indicated ddname. A DD statement has been provided in the JCL, but the device allocated for the DD statement is not a tape or cartridge device; therefore, stacking is not possible. The output stack is disabled; processing continues with any remaining output data sets.

User response: Use dynamic allocation, or correct the JCL statement.

OSAM DELETE/ALLOCATE USING IDCAMS REQUIRES APF AUTHORITY OR SUBSYSTEM ssid ACTIVE

Explanation: Using the IDCAMS keyword with OSAM DELETE/ALLOCATE statements requires that the BMC Recovery utility obtain APF authorization. The job step terminates with user abend U4094.

User response: Ensure that the BMC Recovery utility is being executed from an authorized environment.

groupName,dbdName,dsgName CRITICAL ERROR DURING function PROCESSING - RC=returnCode

Explanation: A critical error was detected during output EXCP processing for the indicated database and data set group. The indicated I/O function received the the indicated return code; continued processing is not possible. The job step terminates with user abend U4095.

User response: Save all job documentation relating to this problem (JCL, job listing, and SYSUDUMP). Contact BMC Customer Support.

groupName,dbdName,dsgName PRILOG RECORD date time IS OPEN

Explanation: The primary log (PRILOG) record for the indicated date and time has not been closed. Possibly an active allocation period has been found, or the log was not closed. The job step terminates with user abend U4094.

User response: If a time stamp recovery has been requested, ensure that the time stamp is a valid recovery timestamp. Ensure that the database is not currently allocated to another job.

groupName,dbdName,dsgName ROLL FORWARD RECOVERY STARTING AT date time

Explanation: A roll forward recovery is being performed because there is no input image copy data set. Processing continues.

User response: No action is required.

groupName,dbdName,dsgName NUMBER OF BYTES PROCESSED xxxxxxxx IS LESS THAN HIGH USED RBA yyyyyyyy

Explanation: The calculated number of bytes processed is less than the high used RBA for the indicated database and data set group. This indicates a possible subsystem problem. The task terminates with user abend U4095.

User response: Save all job documentation relating to this problem (JCL, job listing, and SYSUDUMP). Contact BMC Customer Support.

groupName,dbdName,dsgName FORCER SPECIFIED AND REQUESTED DSN DOES NOT MATCH RECONS

groupName,dbdName,dsgName REGISTERED DSN IS dataSetName1

groupName,dbdName,dsgName REQUESTED DSN IS dataSetName2

Explanation: The RECON data sets have the FORCER option specified, but the data set name that was requested (through JCL or dynamic allocation) does not match the data set name that is registered to the data set group in the RECON DBDS record. In the message text, dataSetName1 is the data set name that was recorded in the DBDS record; dataSetName2 is the data set name that was requested through JCL or dynamic allocation. The job step terminates with user abend U4094.

User response: Check the JCL or dynamic allocation for the data set name that is associated with the data set group. Correct the name and resubmit the job.

groupName,dbdName,dsgName KEYS OUT OF SEQUENCE ON DDNAME ddname

Explanation: While attempting to image copy a VSAM KSDS, the program detected a key-out-of-sequence condition. The current key and previous key are dumped in the PLUSOUT data set list. The task terminates with a user abend.

User response: Recover the VSAM KSDS to fix the key-out-of-sequence condition. After the KSDS is recovered, resubmit the image copy job.

groupName SEQUENCE ERROR CREATING CA RECORD FOR DBD(dbdName) DDN(ddname) RBA(relativeByteAddress)

Explanation: A sequence check has detected an error in writing a change accumulation detail or spill record. This is probably an internal logic error. The job step terminates with user abend U4095.

User response: Perform the following actions:

• Save all of the job output.

• Save the input change accumulation and log data sets.

• Copy (REPRO) the RECON data sets to a backup data set.

• Iimage copy the database that is indicated in the message

• Resubmit the job.

• Contact BMC Customer Support for further instructions.

groupName, dbdName, dsgName OIC AND REUSEABLE IC WITH UNCHANGED RUN TIME IS NOT ALLOWED

Explanation: All of the following conditions are true:

• The Online Image Copy function was requested.

• The image copy data set is marked as REUSE in DBRC.

• The run time has not changed since the last image copy.

User response: No action is required.

DBD dbdName HAS TOO MANY TRACKS FOR BDAM PROCESSING, SEQUPD(Y) IS BEING FORCED

Explanation: A BDAM restriction limits the size of BDAM processable data sets to 65535 tracks. The product forces SEQUPD(Y) and processes the database sequentially.

User response: No action is required.

GRP.DBD.DSG DBRC NOTIFICATION BYPASSED DUE TO VERIFY(N)

Explanation: NOTIFY(Y) and VERIFY(N) keywords are not compatible. VERIFY(N) causes the BMC Change Accumulation utility to bypass DBRC notification even when you specify NOTIFY(Y). DBRC will not be notified. The job ends with condition code 4.

User response: BMC Change Accumulation utility jobs that require the VERIFY(N) keyword should also use NOTIFY(N).

SNAPSHOT COPY PROCESSING TERMINATED WITH ERRORS

Explanation: An error was encountered during Snapshot Copy processing; a batch (or non-fuzzy) image copy cannot be created. You specified SNAPSHOT(R), which indicates that an online image copy is not acceptable. The image copy task terminates with user abend U4094.

User response: Review the additional messages in the processing log to determine the cause of the Snapshot Copy failure.

ONLINE IMAGE COPY WILL BE CREATED

Explanation: An error was encountered during Snapshot Copy processing; a batch (or non-fuzzy) image copy cannot be created. You specified SNAPSHOT(P), which indicates that an online image copy is acceptable. The image copy task continues; however, the image copy is recorded in DBRC as an online image copy.

User response: Review the additional messages in the processing log to determine the cause of the Snapshot Copy failure.

SNAPSHOT COPY PROCESSING ERROR

explanatoryText

Explanation: An error was encountered during Snapshot Copy processing; a batch (or non-fuzzy) image copy cannot be created. This message is accompanied by another BMC8765W message that explains the error. Snapshot Copy processing is stopped. If you specified SNAPSHOT(R), the image copy task terminates; if you specified SNAPSHOT(P), an online image copy is created.

User response: Review all messages in the processing log for the cause of the Snapshot Copy failure. In addition, check the EXTENDED BUFFER MANAGER system and processing logs for additional messages. If you need further assistance, contact BMC Customer Support.

SNAPSHOT COPY ERROR POSTED BY XBM

explanatoryText

Explanation: The EXTENDED BUFFER MANAGER (XBM) system has notified the BMC Image Copy utility of an error; and a batch (or non-fuzzy) image copy cannot be created. This message is accompanied by another BMC8766W message that explains the error. Snapshot Copy processing is stopped. If you specified SNAPSHOT(R), the image copy task is terminated. If you specified SNAPSHOT(P), an online image copy is created.

User response: Review all messages in the processing log for the cause of the Snapshot Copy failure. In addition, check the XBM system and processing logs for additional messages. Contact BMC Customer Support if you need further assistance.

CONSISTENCY GROUP groupName, JOB jobName HAS BEEN STARTED

Explanation: Snapshot copy processing has been started for all databases in the indicated consistency group for the indicated job. Snapshot copy processing continues. Any updates to the databases in the consistency group will cause EXTENDED BUFFER MANAGER (XBM) to save the preimages before allowing the updates to be written to disk.

User response: Online and batch activity can now be started for the databases in the consistency group.

NOTIFY TIME DIFFERENT THAN IC HEADER TIME

Explanation: Spill records were encountered when processing the input change accumulation data set during Incremental Image Copy (IIC) processing. The time stamp of the earliest spill record is used as the time stamp recorded in DBRC; this time is earlier than the time recorded in the image copy header. Processing continues.

User response: Do not use this image copy data set with the IMS Database Recovery utility. The IMS Database Recovery utility will fail with message DFS2804A HEADER RECORD ON DFSUDUMP IS INCONSISTENT WITH RECON FOR FUNCTION RV. To recover with this image copy, you must use the BMC Recovery utility or the Recovery function in IMAGE COPY PLUS.

IODRIVER type ERROR FOR (errorNumber) FOR DATASET dataSetName

Explanation: An internal processing error of the indicated type (OPEN or READ) has occurred while processing the indicated database data set. If the warning form of the message (BMC8769W) is issued, another access method is used and processing may complete normally. If the critical-error form of the message (BMC8769C) is issued, the start I/O access method is required for processing and the task is terminated with user abend U4094.

User response: Record the indicated error number. Contact BMC Customer Support for further assistance.

AUTHORIZATION FAILED. AUTHORIZE STEPLIB OR START THE DBUSS

Explanation: An authorized environment is required for the utility functions and features you are trying to use. The job step terminates with user abend.

User response: Ensure that the utility can obtain APF authorization by using a technique that is described in the user guide. If you cannot resolve the problem, contact BMC Customer Support for further assistance.

INTERFACE MODULE DLIGINTR IS NOT IN SEARCHED LIBRARIES

Explanation: A required BMC application interface module was not found in any of the searched libraries. The job step terminates with user abend.

User response: Ensure that all of the necessary libraries are available to the job step. Contact BMC Customer Support for further assistance.

CA AS OF timestamp1 WILL NOT BE USED FOR PIT RECOVERY TO timestamp2

Explanation: While a point-in-time (PIT) recovery is executing using timestamp2, a change accumulation data set with timestamp1 was found with fewer than two logs. The change accumulation data set is not used in the recovery, and the PIT job continues.

User response: No action is required. However, this message may be useful if a change accumulation data set will be selected as input for a PIT recovery when the recovery is run with the SCAN(Y) keyword.

ddn 'TZERO' INPUT. THE FOLLOWING AREA DATASET(S) WILL NOT BE RECOVERED

Explanation: For recovery using a T0 copy that was created by the Data Base Image Copy 2 Utility from IBM (program DFSUDMPT0), only the first area data set is restored. If multiple area data sets are specified, the remaining data sets are ignored and not restored. Processing continues. Additional area data sets are not recovered.

User response: If you must use multiple area data sets, use Snapshot Copy or Image Copy 2 input with the IMS Restore utility.

USER NOT AUTHORIZED TO ACCESS DATASET dataSetName FOR INPUT PROCESSING

Explanation: A Security Access Facility (SAF) request to access the data set for input processing issued a return code indicating that the user is not authorized for such access. The task terminates with user abend U4094.

User response: Either authorize the user to access the data set for input processing or specify another user. Resubmit the job.

DATASET dataSetName BWO FLAGS flags INVALID FOR OIC

Explanation: The Backup While Open (BWO) flags for the indicated KSDS indicate that an online image copy (OIC) cannot be started or that a completed OIC is possibly invalid because of CI/CA split activity. The task terminates with return code 4.

User response: Resubmit the OIC when the data set is not likely to be heavily updated.

RVPSYSIN, dbdName, ddname nnn EXTENTS EXCEEDS OSAM MAXIMUM (RVP)

Explanation: The number (nnn) of extents for the indicated database data set exceeds the maximum total number of primary and secondary extents on all volumes that IMS permits for OSAM data sets. For more details about the IMS restrictions on OSAM data sets, see the OSAM usage information in the IMS documentation from IBM. The task terminates with user abend U4094 and reason code 16.

User response: Increase the primary space, secondary space, or both space allocations, or specify the use of direct access storage devices that contain more free space.

CONCURRENT IMAGE COPY FOR KSDS: dataSetName

Explanation: The following conditions are true:

• The FALLBACK(Y) keyword was specified.

• A failure occurred so that fallback processing was required.

• The Image Copy utility performed a concurrent image copy for the indicated KSDS.

User response: Review the situation to determine whether the output image copy is usable. If it is not, take another image copy of the indicated data set.

INCONSISTENT DATA, LOG DATA OFFSET OUTSIDE THE FSE BOUNDARY

Explanation: The Backout Recovery function of the BMC Recovery utility encountered inconsistent log data. The task is terminated with user abend U4094.

User response: Determine the cause of the bad log data, correct the problem, and resubmit the job or perform a forward recovery. Sometimes this error can occur if a backout recovery is attempted twice on a database for which backout recovery has been partially or completely accomplished. In this situation, a forward recovery may be required.

POINTER ERRORS FOR ddname RETURN CODE=returnCode

Explanation: Pointer errors were found for the indicated data set group (ddname). The task is terminated with user abend U4094.

User response: Check the Concurrent Pointer Checking function reports for explanatory error messages.

groupName,dbdName,dsgName INCOMPLETE, NON-RECOVERABLE ERROR. THIS TASK CAN NOT BE RESTARTED AUTOMATICALLY

Explanation: During the current execution or any previous execution of the job step, an error occurred during backout recovery or image copy processing for the indicated data set group. The error cannot be resolved without manual intervention. Therefore, the Automatic Restart feature cannot restart the process automatically. The task terminates with the original abend code.

User response: Check the job log report in the SYSPRINT data set for a more specific error message that explains the cause of the problem. Correct the condition that led to the error and resubmit the job. If any other tasks have failed in the job step and have errors that can be resolved without manual intervention, the Automatic Restart feature restarts those tasks automatically when you resubmit the job.

ONE OR MORE DSGS HAD NON-RECOVERABLE BACKOUT ERRORS IN A PREVIOUS EXECUTION

THE JOB CAN NOT BE RESTARTED AUTOMATICALLY, MANUAL INTERVENTION REQUIRED

RESUBMITTING THE JOB FOR EXECUTION NOW WILL FORCE A COLD START

Explanation: The checkpoint task of the Automatic Restart feature has detected that all pending backout recovery tasks for the job step have errors that cannot be resolved without manual intervention. Therefore, the Automatic Restart feature cannot restart these backout recovery tasks automatically. At this point, the Automatic Restart feature prepares the checkpoint file for a cold-start during the subsequent execution of the job step. The task terminates with user abend U4094.

User response: Check for any error messages in the previous runs. Correct the error and resubmit the job step, or run a forward recovery for only those databases that are in error.

PARTITION partitionName WILL BE RESCHEDULED DURING RESTART TO BUILD THE SEC INDEXES

Explanation: This message is issued when all partitions and primary indexes are recovered successfully for a HALDB but the rebuilding of one or more secondary indexes failed. The indicated partition is rescheduled so that the Index Rebuild function can be reinvoked from the Recovery utility. The utility selects the smallest partition to reschedule during restart process. Other error messages are issued to explain why the Index Rebuild process failed. In most cases, the task terminates with user abend U4094.

User response: Review all messages in the processing log for the cause of the failure of the Index Rebuild function. After you have identified the cause and corrected the problem, take one of the following actions:

• Resubmit the job. The Recovery utility automatically invokes the Index Rebuild function to rebuild the secondary indexes.

• If you have a license that allows you to run the Index Rebuild function as a standalone utility, you can prepare JCL to rebuild the secondary indexes in a standalone job.

dsgtid {UNABLE TO FIND MATCHING DATA SET ENTRY IN seclog/secsld RECORD |seclog/secsld MISSING FOR logDataSetName}

Explanation: If dual logging is in effect, the RECON contains PRILOG and SECLOG records or PRISLD and SECSLD records. These records match. Every data set entry in a PRILOG record has a matching data set entry in the SECLOG record. Every data set entry in a PRISLD record has a matching data set entry in the SECSLD record. A serious DBRC problem is indicated by a missing data set entry in a SECLOG or SECSLD record. The job is terminated abnormally.

User response: Determine the cause of the error in the RECON data set, correct the problem, and resubmit the job.

SMARTCA(Y) PROCESSING {IGNORED | ENDED} - errorReasonText

Explanation: During BMC utility processing, the IC Triggering by CA feature (controlled by the SMARTCA(Y) keyword) was unable to establish communications with the designated BMC Advisor for IMS region or with the IC Triggering by CA feature in Recovery Advisor. Possible causes of this problem can include the following conditions:

• IMS RECON data sets are unknown to the Advisor region.

• CPC or BRI modules are missing from the job STEPLIB (or z/OS LNKLST).

• A problem has occurred in the Advisor region.

User response: To address the problem, take the following actions:

• Verify that the IMS RECON data sets are defined to the Advisor region.

• Verify that the appropriate modules can be found in the job STEPLIB (or z/OS LNKLST).

• Check the CPCLOG output of the Advisor region for problems.

SMARTCA(Y) PROCESSING STOPPED - 'ANALYZE CA GROUP TO TRIGGER ICS' THRESHOLD OPTION SET TO NO

SMARTCA(Y) - ALL MEMBERS OF CA GROUP groupName WILL BE IMAGE COPIED

Explanation: In the BMC Advisor for IMS region, the Analyze CA Group to Trigger ICs parameter was disabled (set to No ), indicating that the current CA group should not be analyzed for change accumulation file size or selection criteria. The BMC Change Accumulation utility job and any subsequent BMC Image Copy utility jobs continue as if SMARTCA(N) has been specified.

User response: If you want to use the IC Triggering by CA feature, verify that the IC Triggering by CA parameters are specified correctly in the console. If you do not want to use the feature, change the SMARTCA(Y) option to SMARTCA(N).

JOBHIST(Y) PROCESSING IGNORED - NON-IMS ADVISOR RECON: reconDataSetName

Explanation: This message is issued when you have specified JOBHIST(Y), which causes the job statistics to be sent to IMS Recovery Advisor, but the system could not connect to the IMS Recovery Advisor. Processing continues.

User response: Make sure that the RECON data sets are defined to the IMS Recovery Advisor. If the job statistics data is not important, you can specify JOBHIST(N).