Messages BKP400 through BKP4xx

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

BKP475I BACKUP/MIGRATE TASK STARTED

Explanation: This information message indicates that a backup or migration task is starting.

Corrective Action: No action is required.

BKP476I MISSION {STARTED | RESTARTED} WITH TIMESTAMP= misTime

Explanation: This information message indicates which backup (migration) mission is starting or restarting, and its time stamp.

In this message, misTime is the identity of the backup (migration) mission that is starting or re-starting.

Corrective Action: No action is required.

BKP477E INSUFFICIENT STORAGE TO COMPLETE THIS bkup/migrate MISSION

Explanation: There is insufficient storage to complete the bkup/migrate backup or migration mission.

The status of this mission is set to ENDED NOTOK.

Corrective Action: Increase the REGION size for the Control-D or Control-V monitor and rerun the backup or migration mission. If the REGION size cannot be increased, make sure the backup or migration mission does not run concurrently with other missions. If the problem persists, contact your INCONTROL administrator.

BKP478I bkup/migrate MISSION ENDED OK

Explanation: This information message indicates that a backup or migration mission finished executing with status ENDED OK.

In this message, bkup/migrate is the identity of the backup or migrate mission that has ended.

Corrective Action: No action is required.

BKP479E bkup/migrate MISSION ENDED NOT OK

Explanation: This message indicates that a backup or migration mission finished executing with status ENDED NOTOK. The IOA Log file and the backup or migration job should contain one or more messages indicating the reason.

In this message, bkup/migrate is the identity of the backup or migrate mission that has ended.

Corrective Action: No action is required.

BKP47BI {BACKUP | PRIMARY | SECONDARY} jobId SUBMITTED WITH TIMESTAMP= misTime

Explanation: This information message indicates that the backup (migration) job generated by the backup (migration) mission is submitted for execution.

The variables in this message are:

• jobId - the system identifier of the submitted job.
• misTime - the identity of the backup (migration) mission. It is copied to the generated job.

Corrective Action: No action is required.

BKP47CI {BACKUP | PRIMARY | SECONDARY} JOB PLACED IN CONTROL-D JOB LIBRARY WITH TIMESTAMP= misTime

Explanation: This information message indicates that the backup (or the migration) job generated by the backup (or the migration) mission is placed to the Control-D JOB library.

In this message, misTime is the identity of the backup (migration) mission. It is copied to the generated job.

Corrective Action: No action is required.

BKP480E NO REPORTS TO BE BACKED UP/ MIGRATED BY THIS MISSION

Explanation: The Active User Report List file was searched for backup or migration requests. No backup or migration request with this mission name was waiting to be executed.

The status of this mission is set to ENDED NOTOK.

Corrective Action: No action is required.

BKP481E INVALID RETURN CODE rc FROM USER EXIT CTDX010 - missionName STOPPED

Explanation: The Control-D or Control-V exit CTDX010 ended with a return code of rc.

Possible values of rc are:

The status of this mission is set to ENDED NOTOK.

Corrective Action: Do the following:

1. Correct the problem in the CTDX010 exit.
2. Assemble and link-edit this exit.
3. Rerun the backup or migration mission. Control-V will call the new version of the exit automatically.

BKP482E INVALID RETURN CODE rc FROM CTMMEM - missionName STOPPED

Explanation: Control-D or Control-V received a return code of rc from the CTMMEM internal module, while trying to update the backup or migration job JCL library referenced by the DADJOB DD statement. The member name is the same as the name of the backup or migration mission.

The variables in this message are:

• rc - the return code from the CTMMEM module
• missionName - the identity of the problematic backup or migration mission

Possible return codes and their causes are:

The status of this mission is set to ENDED NOTOK.

Corrective Action: Do the following:

1. Look for additional messages in the IOA Log file.
2. Correct the problem with the library.
3. Shut down Control-D or Control-V and reactivate it.
4. Rerun the backup or migration mission.

BKP483E INVALID RETURN CODE rc FROM CTDCND - missionName STOPPED

Explanation: Control-D or Control-V received the invalid return code rc from the CTDCND internal Control-D module while trying to add the %COND% prerequisite condition to the IOA Conditions file.

The variables in this message are:

• rc - the return code from the CTDCND module
• missionName - the identity of the problematic mission

The status of this mission is set to ENDED NOTOK.

Corrective Action: Note the return code (rc) and the mission name (missionName). Contact your INCONTROL administrator.

BKP484W ONLY number DATASETS WILL BE BACKED UP.

Explanation: The number of data sets selected by the backup mission exceeded the maximum number of data sets that can be handled within one mission execution.

In this message, number is the specified number of data sets to be backed up.

Only number data sets will be backed up during the current mission execution.

Corrective Action: Order an additional appropriate backup mission (or order the same backup mission once again) to back up the remaining data sets.

BKP487S MIGRATION FILE WAS FORMATTED WITH INCORRECT COMPRESSION TABLE

Explanation: A migration file was opened for multistage migration, but the migration file was formatted with an old compression table.

A multistage migration mission stores log data about the last three migration stages in the SYSDATA record. If a migration file formatted with an old compression table is used, this data is lost.

The migration mission ends NOTOK.

Corrective Action: Do the following:

1. Use the CTDUFDUL job from the Control-D JCL library to unload the migration file.
2. Reformat the migration file.
3. Use the CTDUFRST job from the Control-D JCL library to reload the migration file.

BKP488W MIGRATION OF "cdamName" FROM OSS TO OSS REJECTED

Explanation: While building a migration mission, the Control-D monitor found a request to migrate a CDAM file from one OSS media to another OSS media, but this type of migration is not allowed.

In this message, cdamName is the identity of the CDAM file that was to be migrated.

The cdamName CDAM file is deleted from the list of CDAM files to be migrated.

Corrective Action: Change the migration path of the problematic migration mission.

BKP489I SHUT DOWN UPON REQUEST OF MAIN TASK

Explanation: This information message indicates that the Control-D monitor is shutting down. The Control-D internal backup task is run upon request of the Control-D main task.

The Control-D monitor shuts down.

Corrective Action: No action is required.

BKP48AE skelName SKELETON MEMBER missionName NOT FOUND IN SKL LIBRARY

Explanation: The specified backup or migration skeleton is not in the DADSKL member of the Control-D or Control-V monitor. For each backup and migration mission, a unique skeleton job (member) with the same name must exist in the DADSKL member.

The variables in this message are:

• skelName - the identity of the problematic skeleton
• missionName - the identity of the problematic mission

The problematic mission does not run.

Corrective Action: Rename the problematic mission, or create the required mission skeleton. Resubmit the mission.

BKP48BE CONTROL-D JOB LIBRARY FULL, COMPRESS THE JOB LIBRARY AND RERUN THE MISSION

Explanation: Control-D discovered that its JOB library was full when trying to backup, migrate or restore a file.

The file is not backed up, restored, or migrated.

Corrective Action: Compress the Control-D job library and rerun the backup, migrate, or restore mission.

BKP48CE BACKUP MISSION WAS CHANGED FROM GENERATION TO NUMBER OF DAYS TO KEEP

Explanation: When running a backup job, the user changed the backup mission fields from NUMBER OF GENERATIONS TO KEEP to NUMBER OF DAYS TO KEEP. When at least one backup has been executed, the user cannot change the type of backup in this way.

The backup is not executed.

Corrective Action: Define a new backup mission specifying the NUMBER OF DAYS TO KEEP.

BKP48DE SECONDARY MIGRATION SKELETON skel WAS NOT SUBMITTED RC rc - MISSION CONTINUES

Explanation: An error occurred during the generation of a secondary migration job.

More information about the error is provided in accompanying messages.

The variables in this message are:

• skel - the name of the problematic migration job skeleton
• rc - the return code of the error

The secondary migration job is not submitted.

Corrective Action: Call your INCONTROL administrator.

BKP48EE SECONDARY MIGRATION SKELETON skel DOES NOT CONTAIN %LEVEL% PARAMETER

Explanation: The skeleton of a secondary migration mission job does not contain the mandatory %LEVEL% parameter.

In this message skel is the name of the problematic migration mission job skeleton.

The secondary migration mission job is not submitted.

Corrective Action: Call your INCONTROL administrator.

BKP48FE INVALID SKELETON MEMBER skel

Explanation: A long line (more than 80 characters) is built by resolving variables in the skel skeleton member.

The problematic mission does not run.

Corrective Action: Fix the skeleton member and then resubmit the migration mission.