Messages UBK900 through UBK9xx

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

UBK9C0I CTDUPBKP UTILITY STARTED

Explanation: This information message indicates that the CTDUPBKP utility has started.

Corrective Action: No action is required.

UBK9C1I CTDUPBKP UTILITY COMPLETED SUCCESSFULLY

Explanation: This information message indicates that the CTDUPBKP utility has completed without errors.

Corrective Action: No action is required.

UBK9C2S CTDUPBKP UTILITY ENDED WITH ERRORS

Explanation: This information message indicates that the CTDUPBKP utility has ended with errors.

Corrective Action: Check all the messages issued by the CTDUPBKP utility and proceed accordingly.

UBK9C3I FILE=ACT WAS SPECIFIED. ACTIVE USER FILE WILL BE PROCESSED

Explanation: This information message indicates that FILE was set to ACT in the input parameters of the CTDUPBKP utility, and as a result the Active User file is processed.

Corrective Action: No action is required.

UBK9C4I FILE=HST WAS SPECIFIED. HISTORY USER FILE WILL BE PROCESSED

Explanation: This information message indicates that FILE was set to HST in the input parameters of the CTDUPBKP utility and, as a result, the History User file is processed.

Corrective Action: No action is required.

UBK9C5I FILE=MIG WAS SPECIFIED. MIGRATION USER FILE WILL BE PROCESSED

Explanation: This information message indicates that FILE was set to MIG in the input parameters of the CTDUPBKP utility and, as a result, the Migration User file is processed.

Corrective Action: No action is required.

UBK9C6E NO FILE PARAMETER WAS SPECIFIED

Explanation: The FILE parameter was not specified in the input parameters of the CTDUPBKP utility.

The FILE parameter is mandatory.

The CTDUPBKP utility terminates

Corrective Action: Specify the FILE parameter and rerun the utility.

UBK9C7E NO $SYSDATA RECORDS FOUND IN THE {ACTIVE | HISTORY | MIGRATION} USER FILE

Explanation: The CTDUPBKP utility did not find any $SYSDATA records in the specified user file to update.

The CTDUPBKP utility terminates.

Corrective Action: Check the input FILE parameter of the utility for the correct user file, and rerun the utility.

UBK9C8E SELECT CARD WAS NOT SPECIFIED

Explanation: A SELECT statement was omitted from the input parameters of the CTDUPBKP utility.

The CTDUPBKP utility terminates.

Corrective Action: Add a SELECT statement to the CTDUPBKP input statements of the CTDUPBKP utility, and rerun the utility. For more information, see the INCONTROL for z/OS Utilities Guide.

UBK9C9I input_parm WAS SPECIFIED

Explanation: This information message displays the input parameter that the user specified for the CTDUPBKP utility.

Corrective Action: No action is required.

UBK9CAI NO VOLSER WAS FOUND FOR THE {ACTIVE | PERMANENT | HISTORY} USER FILE

Explanation: This information message indicates that a detailed report ordered by the user was not produced because the $SYSDATA record of the identified user file was not found.

Corrective Action: No action is required.

UBK9CBI input_control_stmt

Explanation: This information message displays the input control statement that the user specified for the CTDUPBKP utility.

If the input control statement is in error, this message is followed by message UBK9CCE.

Corrective Action: No action is required.

UBK9CCE ERROR IN CONTROL STATEMENT

Explanation: An error was found in the input control statement specified by the user for the CTDUPBKP utility.

The input control statement is displayed in message UBK9CBI which precedes this message.

The CTDUPBKP utility terminates.

Corrective Action: For a description of the input parameters, see the CTDUPBKP utility in the INCONTROL for z/OS Utilities Guide. Correct the input control statement accordingly and rerun the utility.

UBK9CDW THERE IS NO CONTROL RECORD FOR BKPMIS backupMissionName

Explanation: The CTDUPBKP utility could not find the Backup Control record for the backup mission of the current $SYSDATA record.

When FILE is set to HST in the input parameters of the CTDUPBKP utility, the utility attempts to read the backup control record for the backup mission of the current $SYSDATA record. In this case, the backup control record could not be found in the History file.

The CTDUPBKP utility continues with processes that do not require the backup control record.

Corrective Action: To create a backup control record, in the input parameters of the CTDUPBKP utility specify the backup mission name in the BKPMIS parameter, and the number of backup generations to retain in the GENER parameter. Rerun the CTDUPBKP utility.

For more information, see the CTDUPBKP utility in the INCONTROL for z/OS Utilities Guide.

UBK9CEE RETPD CANNOT BE CHANGED

Explanation: The RETPD parameter was specified as an input parameter for the CTDUPBKP utility but the generation number found in the Backup Control record was not 0.

When activating the CTDUPBKP utility, the user specified the RETPD parameter without setting GENER to NONE. The backup mission in question was previously run using the NUMBER OF DAYS TO KEEP method. Once a mission has been run using NUMBER OF DAYS TO KEEP method, it cannot be run using the RETPD method.

The CTDUPBKP utility continues with other processes.

Corrective Action: Either change the method in the parameters to NUMBER OF DAYS TO KEEP then rerun the utility, or define a new backup mission defined with the RETPD parameter.

UBK9CFE INVALID RETURN CODE FROM SORT. RC=rc

Explanation: The SORT utility called by the CTDUPBKP utility ended with errors.

The CTDUPBKP utility terminates.

Corrective Action: Refer to the section on return codes in the SORT utility documentation in the INCONTROL for z/OS Utilities Guide. Correct the cause accordingly and rerun the CTDUPBKP utility.

UBK9CGW THE NEW RETENTION PERIOD (numDaysNew) DIFFERS FROM THE VALUE (numDaysOld) IN THE MIGRATION MISSION missionName

Explanation: The new retention period that you set through the CTDUPBKP utility is compared with the current value in the corresponding migration mission. This warning message alerts you that the newly specified value differs from the value in the corresponding migration mission.

Corrective Action: Ensure that the new retention period matches your needs or adjust it as necessary.

UBK9CHW THE MIGRATION MISSION missionName IS NOT FOUND IN THE USER FILE

Explanation: The new retention period that you set through the CTDUPBKP utility could not be compared with the current value in the corresponding migration mission, because the corresponding migration mission was not found in the user file.

Corrective Action: None.

UBK9F0I CONTROL RECORD FOR BKPMIS backupMissionName HAS BEEN CREATED

Explanation: This information message indicates that a backup control record was recreated for the backup mission identified in the message.

A backup control record is recreated when the FILE parameter was set to HST for the backup mission, and when the original backup control record is missing.

Corrective Action: No action is required.

UBK9F1I CTDUPBKP IS RUNNING IN SIMULATE MODE:

Explanation: This information message indicates that the CTDUPBKP utility is running in simulation mode. The report listing the selected records and specified updates is produced, but no updates are actually performed.

Corrective Action: Analyze the report. If all requested updates are correct, run the utility in production mode (with parameter SIMULATE=NO).

UBK9F2I MIGMIS missionName PRIMARY/SECONDARY VOLSER volser IS CHANGED TO SCRATCH.

Explanation: This information message indicates that the volume serial number for the specified migration mission is cleaned by the CTDUPBKP utility. The next migration mission run will request a scratch tape volume for migration.

The variables in this message are:

• missionName - migration mission name for which the action is performed.
• volser - the old volume serial number which is changed to scratch.

Corrective Action: No action is required.

UBK9F3E NO MIGMIS PARAMETER WAS SPECIFIED.

Explanation: This error message is issued when the SCRATCHVOL or SCRATCHSECVOL parameter is specified, but no MIGMIS selection parameter was previously specified.

The CTDUPBKP utility terminates.

Corrective Action: Specify the MIGMIS selection parameter with the migration mission name or with the value ALL if you want to perform the action for all migration missions.