Messages BKC400 through BKC4xx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

BKC490I CHECKING OF RESULTS OF MISSION misName ODATE= modate TIMESTAMP= misTime

Explanation: This information message indicates that the backup (migration) mission began checking of the results of the backup (migration) utility run.

The variables in this message are:

• misName - the name of the backup or migration mission
• modate - the original scheduling date of the backup or migration mission
• misTime - the time stamp of the backup or migration mission

Corrective Action: No action is required.

BKC491E INVALID PARAMETERS FOR BACKUP/MIGRATION ANALYZE PROGRAM

Explanation: An invalid parameter is specified in the ANALYZE job step of the generated backup (migration) job.

This may occur because the backup (migration) job skeleton was incorrectly modified by a user.

The backup (migration) mission ends NOTOK.

Corrective Action: Call your INCONTROL Administrator.

BKC492W MISSING VOLUME SERIAL NUMBERS FOR DDNAME "TAPE"

Explanation: The backup job could not find the volume serial numbers (volsers) of the backup tapes. The first step of the backup job backs up the compressed data sets on tapes specified by the DD name TAPE. The second step of the backup job executes the CTDBKC program, which analyzes the output of the backup process. The second step failed to retrieve volume serial numbers from the JFCB control block The volser is required for subsequent restores.

Possible causes are:

• The user-tailored JCL of the backup job may contain errors.
• An error occurred during processing of the first step.
• The site backup and restore facility does not use standard label tapes. This is not an error situation.

For information about the correct JCL, refer to the section on backup mission management in the INCONTROL for z/OS Administrator Guide.

Corrective Action: If there is an error in the JCL of the backup job, correct the JCL skeleton and rerun the backup job. If an error occurred during processing of the first step of the job, refer to earlier messages generated by the first step, correct the problem, and rerun the job.

BKC493E CDAM FILE WAS NOT BACKED UP: dsname BY MISSION misName ODATE= modate TIMESTAMP= misTime

Explanation: The backup utility is unable to backup the dsname data set.

The variables in this message are:

• dsname - the data set name
• misName - the name of the backup mission
• modate - the original scheduling date of the backup mission
• misTime - the time stamp of the backup mission

Possible causes are:

• The data set may have been deleted or uncataloged.
• An I/O error was encountered when backing up the data set.

The backup mission ends NOTOK.

Corrective Action: Check the output of the backup utility.

BKC494E OPEN OF BACKUP/MIGRATE UTILITY MESSAGES FILE FAILED

Explanation: The open of the SYSIN DD statement failed. This message is produced by the ANALYZE step of the backup or migration job.

Possible causes are:

• The SYSIN DD statement has been deleted or its JCL has been modified incorrectly.
• The data set referenced by the SYSIN DD statement cannot be opened for sequential read.

The requested backup or migration is not performed. The status of the Backup or Migration Mission is changed to ENDED NOTOK.

Corrective Action: Do the following:

1. Check the ANALYZE step of the backup or migration job in the library referenced by the DADSKL DD statement.
2. For the correct format for SYSIN JCL, see the BKPDFDSS sample skeleton job in the Control-D or Control-V SKL library.
3. Modify the JCL as required.
4. Rerun the Backup or Migration Mission.

BKC495E NO PENDING BACKUP/MIGRATION MISSION FOUND BY BKPRESET IN ACTIVE MISSION FILE

Explanation: This message indicates that BKPRESET utility did not find any pending backup or migration mission in the Active User file.

The utility resets status of all SYSDATA records pending in backup to WAITING FOR BACKUP.

Corrective Action: No action is required.

BKC496E OPEN OF ACTIVE MISSIONS FILE FAILED. DDNAME "DAAMF"

Explanation: Open of the Active Missions file failed. This file is referenced by the DAAMF DD statement. This message is produced by the ANALYZE step of the backup or migration job. This step executes the CTDBKC program, which analyzes the output of the backup or migration process.

Possible causes are:

• The DAAMF DD statement is missing.
• The data set referenced by the DAAMF DD statement is not the Active Missions file.
• The data set referenced by the DAAMF DD statement is the Active Missions file for another Control-D or Control-V monitor or a different version of Control-D or Control-V.

Backup or migration of the requested data sets is not performed. The status of the backup or migration mission remains BACKUP or MIGRATE IN PROCESS. This status will change to ENDED OK after the backup or migration job is corrected and rerun.

Corrective Action: Do the following:

1. Check the ANALYZE step of the backup or migration job in the library referenced by the DADJOB DD statement.
2. Modify or add the DAAMF DD statement.
3. Rerun the job.
4. To prevent a recurrence of this problem, make the same modification to the backup or migration skeleton JCL in the library referenced by the DADSKL DD statement.

BKC497E UNABLE TO UPDATE STATUS OF MISSION misName ODATE= misoDate TIMESTAMP= misTime (RC= rc)

Explanation: where rc is the return code of the Active Mission file service.

Backup or migration job cannot update, in the Active Mission file, the status of the mission indicated in the message.

The mission remains in status IN PROCESS.

Corrective Action: Use the appropriate utility (BKPRESET or MIGRESET) to reset the mission status. If the problem recurs, prepare the IOA LOG and contact BMC Customer Support.

BKC498I RESULT OF MISSION misName ODATE= modate TIMESTAMP= misTime IS OK

Explanation: This information message indicates that the backup (migration) mission has finished successfully.

The variables in this message are:

• misName - the name of the backup (migration) mission
• modate - the original scheduling date of the backup (migration) mission
• misTime - the time stamp of the backup (migration) mission

Corrective Action: No action is required.

BKC499E RESULT OF MISSION misName ODATE= modate TIMESTAMP= misTime IS NOT OK

Explanation: This message indicates that an error was encountered in the backup (migration) mission execution. The detailed description of the error is given in the previous printed messages.

The variables in this message are:

• misName - the name of the backup (migration) mission
• modate - the original scheduling date of the backup (migration) mission
• misTime - the time stamp of the backup (migration) mission

The backup (migration) mission ends NOTOK.

Corrective Action: Check the report of mission execution in the IOALOG and in the output of the backup (migration) job.

BKC49BE CDAM FILE WAS NOT MIGRATED : dsname BY MISSION misName ODATE= modate TIMESTAMP= misTime

Explanation: The migration utility was unable to migrate the dsname data set.

The variables in this message are:

• dsname - the data set name
• misName - the name of the migration mission
• modate - the original scheduling date of the migration mission
• misTime - the time stamp of the migration mission

Possible causes are:

• The data set may have been deleted or uncataloged.
• An I/O error was encountered when migrating the data set.

The migration mission ends NOTOK.

Corrective Action: Check the output of the migration utility.

BKC49CE INDEX FILE WAS NOT MIGRATED : dsname BY MISSION misName ODATE= modate TIMESTAMP= misTime

Explanation: The migration utility was unable to migrate the dsname data set.

The variables in this message are:

• dsname - the data set name
• misName - the name of the migration mission
• modate - the original scheduling date of the migration mission
• misTime - the time stamp of the migration mission

Possible causes are:

• The data set may have been deleted or uncataloged.
• An I/O error was encountered when migrating the data set.

The migration mission ends NOTOK.

Corrective Action: Check the output of the migration utility.

BKC49DS INVALID THIRD PARAMETER WAS SUPPLIED IN PARM FOR ANALYZE.PRIMARY OR SECONDARY MUST BE SPECIFIED

Explanation: During a generated migrating reports job, an invalid parameter was found in the PARM field of the ANALYZE job step.

The reports migration fails.

Corrective Action: Call your INCONTROL administrator.

BKC49ES ERROR WHEN ISSUING CTDBKC ENQ. RC : rc

Explanation: While backing up reports or performing a reports migration mission, an internal error occurred.

In this message, rc is the internal return code of the error.

The backing up or reports migration mission fails.

Corrective Action: Call your INCONTROL administrator.

BKC49FS MIGRATION JOB RERUN IS NOT ALLOWED

Explanation: This message is issued when the user tries resubmit the primary or secondary migration job from the CTD.JOB library after this job has already been run.

The migration job fails with a return code of 20.

Corrective Action: Check if the previous run of this job ended successfully.

• If the job ended successfully, do not rerun this job but run the secondary job if this is primary or the primary job if this is secondary.
• If the job has not ended successfully before and it is necessary rerun it, perform following steps:
• Run the MIGRESET utility several times until the BKC495E message is issued.
• Rerun the migration mission from the Active Missions screen.

BKC49GS SECONDARY RUN IS REQUIRED AND SECPREF= IS NOT DEFINED IN IOASPRM

Explanation: This message identifies an internal error that occurred during a reports migration mission.

The reports migration mission fails.

Corrective Action: Call your INCONTROL administrator.

BKC49HE mig_stage WAS NOT SUBMITTED - ERROR

Explanation: An error occurred during a reports migration mission, and the mission failed.

In this message, mig_stage identifies the migration stage at which the mission failed. Valid values are:

• PRIMARY
• SECONDARY

Corrective Action: Call your INCONTROL administrator.

BKC49JI mig_stage ENDED [NOT] OK

Explanation: This information message indicates that a reports migration mission stage has ended.

In this message, mig_stage identifies the migration stage.

Valid values are:

• PRIMARY
• SECONDARY

Corrective Action: If the message indicates that the reports migration mission ended NOT OK, call your INCONTROL administrator.

BKC49KE INDEX FILE WAS NOT BACKED UP: dsname BY MISSION misName ODATE= modate TIMESTAMP= misTime

Explanation: The backup utility was unable to back up the dsname data set.

The variables in this message are:

• dsname - the data set name
• misName - the name of the backup mission
• modate - the original scheduling date of the backup mission
• misTime - the time stamp of the backup mission

Possible causes are:

• The data set may have been deleted or uncataloged.
• An I/O error was encountered when backing up the data set.

The backup mission ends NOTOK.

Corrective Action: Check the output of the backup utility.

BKC49ME NO PENDING MISSION WITH TIMESTAMP= misTime FOUND IN ACTIVE MISSION FILE

Explanation: This message indicates that the backup (migration) job did not find the related pending backup (migration) mission in the Active Mission file.

This may occur because the backup (migration) mission was removed from the Active Mission file or was reset by the BKPRESET utility before the job finished.

In this message, misTime is the time stamp of the backup (migration) mission.

The backup (migration) job only prints the LOG of the backup (migration) utility.

Corrective Action: Check the IOALOG.

BKC49NI {BACKUP | PRIMARY | SECONDARY} MISSION misName ODATE= modate TIMESTAMP= misTime IS RESET

Explanation: This information message indicates that the BKPRESET utility successfully reset the backup (or primary migration or secondary migration) mission in the Active Mission file.

The variables in this message are:

• misName - the name of the backup (migration) mission
• modate - the original scheduling date of the backup (migration) mission
• misTime - the time stamp of the backup (migration) mission

Corrective Action: No action is required.

BKC49PS DUE TO SEVERE ERROR POINTED ABOVE NEITHER SYSDATA NOR INDEX RECORD IS COPIED TO HISTORY/MIGRATION FILE

Explanation: Due to a severe error that occurred during the backup (migration) job execution, neither the SYSDATA nor INDEX record was copied to the History (Migration) User file.

This message is displayed with the previous messages in the backup (migration) job's output.

The backup (migration) job only prints the LOG of the backup (migration) utility.

Corrective Action: Check the output of the backup (migration) job.

BKC49QE UNABLE TO UPDATE STATUS OF MISSION misName ODATE= misoDate TIMESTAMP= misTime (UPDATE QUEUE OVERFLOW)

Explanation: Backup or migration job cannot update, in the Active Mission file, the status of the mission indicated in the message because of overflow of the update queue in the Active Mission file service.

The mission remains in status IN PROCESS.

Corrective Action: Use the appropriate utility (BKPRESET or MIGRESET) to reset the mission status. If the problem recurs, prepare the IOA LOG and contact BMC Customer Support.