|
|
|
|
|
This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.
Explanation: The CTVUNMIG Control-V utility ended with errors.
CTVUNMIG terminates.
Corrective Action: Check the job log or the IOA log for the other messages generated by this error. Correct the problem, and rerun the CTVUNMIG utility.
Explanation: Load of the CTDPARM or CTVPARM module failed.
The loading of Control-D or Control-V Installation Parameters failed. Possible causes are:
The CTVUNMIG utility continues without sending messages to the IOA log.
Corrective Action: Do the following:
Explanation: The user specified an invalid parameter for the CTVUNMIG utility.
The utility stops executing with an error.
Corrective Action: Correct the parm parameter and rerun the utility.
Explanation: The user omitted mandatory parameters from the input to the CTVUNMIG utility.
The CTVUNMIG utility stops executing with an error.
Corrective Action: Specify the required parameters and rerun the utility.
Explanation: Control-V was unable to load the modnam module.
Possible causes are:
In this message, modnam is the name of the module that could not be loaded.
The system action is determined by the module (modnam):
Corrective Action: No action is required.
Rerun CTVMIG.
Explanation: The user specified a DD name that could not be opened.
The utility stops executing with a condition code of 16.
Corrective Action: Check the system log for messages generated in response to this failure. If you are unable to solve the problem, report the contents of the messages to BMC Customer Support.
Explanation: This information message indicates that the specified file was successfully unmigrated.
dsn is the last extent of a CDAM file that was unmigrated. The unmigrated file can be found on DASD.
Corrective Action: No action is required.
Explanation: This information message indicates that the size of the migrated file did not correspond to the information in the header of that file.
The job stops executing with a condition code of 08.
Corrective Action: Contact BMC Customer Support and send the complete log of the job.
Explanation: This information message indicates that a foreign report was successfully restored as a Control-D report.
Corrective Action: No action is required.
Explanation: The CTDFOR utility failed to restore the foreign report file.
The CTDFOR utility terminates. The foreign report is not restored.
Corrective Action: Examine other messages to determine the cause of the failure. Fix the problem, and rerun the CTDFOR utility.
Explanation: The same parameter was specified twice for the CTDFOR utility.
The CTDFOR utility terminates.
Corrective Action: Remove the redundant parameter, and rerun the CTDFOR utility.
Explanation: A product name specified in the PRODUCT parameter is unknown to the CTDFOR utility. It is not the name of a product supported by the utility.
The CTDFOR utility terminates.
Corrective Action: Set the PRODUCT parameter to the name of a supported product.
Explanation: The conversion routine called by the CTDFOR utility failed to convert the report file to a CDAM file.
The CTDFOR utility terminates.
Corrective Action: Examine other messages to determine the cause for the conversion routine failure. Correct the problem and rerun the CTDFOR utility.
Explanation: This information message indicates that the CTDUFMDV utility has started.
Corrective Action: No action is required.
Explanation: Another application (such as the CTDDELRP or CTVCLMIG utilities or a MIGRATION mission) is updating a migrated User Report List file. The CTDUFMDV utility cannot be submitted with the PART parameter at the same time.
The CTDUFMDV utility ends with an error.
Corrective Action: Resubmit the CTDUFMDV utility with the PART parameter again. If the Migrated User File (MUF) became unavailable as a result of the CTDUFMDV utility failure, submit the CTDUFMDV utility with the RESET parameter, to restore full accessibility to the old MUF.
Explanation: The data set referenced by the ddName DD statement could not be opened.
The CTDUFMDV utility ends with an error.
Corrective Action: Check other messages generated by the CTDUFMDV job to determine the cause for the failure. Correct the problem and rerun the utility.
Explanation: The sequence of dates defined in the SYSIN stream for the CTDUFMDV utility, which was submitted with the EXEC statement parameter PART, is not in ascending order.
The CTDUFMDV utility ends with an error.
Corrective Action: Correct the input parameters and rerun the utility.
Explanation: The value of the CTDUFMDV EXEC statement parameter param is not valid.
The CTDUFMDV utility ends with an error.
Corrective Action: Correct the invalid parameter and rerun the utility.
Explanation: This information message is issued to the JES log of the job for the CTDUFMDV utility as a header before the following CTDMP6I message or messages.
Corrective Action: No action is required.
Explanation: This information message displays the input parameters that were specified in the SYSIN stream and issued to JES log of the job for the CTDUFMDV utility.
Corrective Action: No action is required.
Explanation: The value of parameter that was displayed in the last CTDMP6I message is not valid.
The CTDUFMDV utility ends with an error.
Corrective Action: Correct the invalid input parameter and rerun the utility.
Explanation: There is not enough memory available to run the CTDUFMDV utility.
The utility ends with an error.
Corrective Action: Do one of the following:
Explanation: A sort program that was activated internally by the CTDUFMDV utility ended with an unexpected return code of rc.
The CTDUFMDV utility ends with an error.
Corrective Action: For details about the reason for the failure, refer to the documentation for the sort program and to the job’s sort messages.
Explanation: The fileType User Reports List file does not contain any SYSDATA record.
In this message, fileType is the type of User Reports List file. Valid values are:
The CTDUFMDV utility ends with an error.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDUFMDV utility has successfully updated a User Report List file.
In this message, fileType is the type of User Reports List file. Valid values are:
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDUFMDV utility has successfully separated an old Migrated User Report List file to different partitions or updated a new Migration User Report List in secondary execution.
Corrective Action: No action is required.
Explanation: A duplicate record was found in the data file. The duplicate record might be the result of an updating target Migrated User Report List after a previous CTDUFMDV execution.
The CTDUFMDV utility continues processing. The duplicate record that was updated first is removed. The record that was updated later contains more current data, and remains in the data file.
Corrective Action: No action is required.
Explanation: The CTDUFMDV is submitted for Migrated User Report List which was already separated (CTDUFMDV was submitted with parameter PART for the same MUF).
The CTDUFMDV utility ends with an error.
Corrective Action: If you need to separate the original MUF again, first submit CTDUFMDV with the RESET parameter.
Explanation: This information message displays the number of processed VSA records from Migrated User Report List.
Corrective Action: No action is required.
Explanation: This message indicates that no input statements were specified in the SYSIN stream for the CTDUFMDV utility submitted with MODE=PART or (COPYOLD,DATE) or (COPYNEW,DATE).
The CTDUFMDV utility ends with an error.
Corrective Action: Add the required input statements under DD card SYSIN and rerun the utility.
Explanation: This information message indicates that the CTDUFMPR utility started or restarted with the function specified in the input parameters (COPY or DELETE) in the specified mode (PROD or TEST).
The first time the utility is submitted for a specified function, the term STARTED is displayed in the message.
If the utility did not end with RC=0 in the previous run and now is starting again with the same function, the term RESTARTED is displayed in the message.
An example where the utility does not end with RC=0 is where the utility does not process all the required records in the previous run because the time limit, specified by the TIMELIM parameter, was exceeded.
Corrective Action: No action is required.
Explanation: This error message is issued when the CTDUFMPR utility did not find the MIGPART record in the file pointed to by the DAMIG DD statement.
The utility stops with RC=8.
Corrective Action: Check whether the DAMIG DD statement points to the correct Migrated User File. Do not submit the CTDUFMPR utility if the Migrated User file is not divided into partitions.
Explanation: The parm input parameter specified in the CTDUFMPR utility JCL EXEC statement is not valid.
The utility stops with RC=12.
Corrective Action: Correct the invalid input parameter (parm) in the JCL and resubmit the job.
Explanation: This error message is issued when the user submits the CTDUFMPR utility with the COPY function after the COPY stage has aleady ended with return code 0, but the DELETE stage has not yet been submitted yet.
The utility stops with return code 8.
Corrective Action: Submit the CTDUFMPR utility with the DELETE function to complete the repartition process.
Explanation: This information message is issued as a header before printing the parameters specified in the SYSIN DD stream. The statements specified in the SYSIN DD stream are printed after this message.
Corrective Action: No action is required.
Explanation: The parm input parameter, specified in the SYSIN DD stream for CTDUFMPR, is not valid.
The utility stops with RC=12.
Corrective Action: Correct the invalid input parameter (parm) in the JCL and resubmit the job.
Explanation: The number of new partition last dates specified in the SYSIN DD stream for the CTDUFMPR utility is not equal to the number of existing partitions in the Migrated User file.
The utility stops with RC=12.
Corrective Action: Correct the invalid input parameters specified in the SYSIN DD stream and resubmit the job.
Explanation: This information message indicates how many partitions exist in the Migrated User File.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDUFMPR utility has started the stage of copying records to other Migrated User File partitions. Records located in partitions that do not match the date ranges of the new partitions will be copied to appropriate partitions.
Corrective Action: No action is required.
Explanation: This information message indicates how many records have been read from partition x of the Migrated User File. Such a message is issued only for partitions which are candidates for moving records from them because their date ranges have been changed by the input parameters.
Corrective Action: No action is required.
Explanation: This information message indicates how many records have been copied from partition x to partition y by the CTDUFMPR utility.
Corrective Action: No action is required.
Explanation: This information message indicates that the stage of copying the records, which were added or updated while the CTDUFMPR utility was running, has started. The Migrated User File records added or updated in partitions that do not match the date ranges of the new partitions will be copied to appropriate partitions.
Corrective Action: No action is required.
Explanation: This error message is issued when the user submits the CTDUFMPR utility with the DELETE function, before the COPY function is submitted and completed.
The utility stops with RC=8.
Corrective Action: Ensure that the CTDUFMPR utility with the COPY function has been submitted and completed, before re-submitting the CTDUFMPR utility with the DELETE function.
No action is required.
Explanation: This information message indicates how many records have been deleted from partition x by the CTDUFMPR utility.
Corrective Action: No action is required.
Explanation: This warning message indicates that the CTDUFMPR utility ended because the time limit, specified in the input parameter, was exceeded. Not all the records, which were specified to be copied or deleted, were processed.
The utility stops with RC=4.
Corrective Action: Re-submit the utility with the same FUNCTION parameter as before.
Explanation: This information message indicates the existing (OLD) last report date1 for partition x and the new last report date2 that will take its place for partition x after repartition process is completed. The dates are displayed in YYYYMMDD format. The CTDUFMPR utility issues this message for each existing partition of the Migrated User File.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDUFMPR utility ended without errors. The return code, rc,can be 00 or 04. RC=00 indicates that all the required records of the Migrated User File have been processed and the submitted utility function is completed. RC=04 indicates that the utility stopped because the time limit was exceeded.
Corrective Action: If RC=00, no action is required. If RC=04, re-submit the utility with the same FUNCTION parameter as before.
Explanation: This information message indicates that the CTDUFMPR utility ended with errors. Additional error messages, describing the errors, precede this message.
Corrective Action: Perform the actions described in the additional error messages.
Explanation: This information message indicates that the CTDUFMPR utility started the step of deleting the records that were copied to the other Migrated User File partitions.
Corrective Action: No action is required.
Explanation: This error message is issued by a Control-D application (such as migration mission, CTDDELRP, or CTVCLMIG), which cannot work in parallel with the CTDUFMDV or CTDUFMP utilities when they are updating the Migrated User file partitions. For more information about synchronization of Control-D components with the CTDUFMDV and CTDUFMPR utilities, see the INCONTROL for z/OS Administrator Guide.
The Control-D application stops after issuing this message.
Corrective Action: Re-submit the stopped Control-D application after CTDUFMDV, with function PART, or CTDUFMPR, with function COPY, is completed.
Explanation: The CTDUFMPR utility issues this error message, when it is started with the DELETE function while a restore operation from a migrated mission is in process. The DELETE function can only be started after the restore operation has been completed. For more information about synchronization of Control-D components with the CTDUFMPR utilities, see the INCONTROL for z/OS Administrator Guide.
The utility stops with RC=8.
Corrective Action: Re-submit the CTDUFMPR utility with the DELETE function after all restore missions are completed.
Explanation: This warning message is issued at the completion of a run of CTDUFMPR utility with the COPY function. It is intended to remind the user that some additional actions must be performed before starting the CTDUFMPR utility with the DELETE function.
The utility ends with RC=0 after issuing this message.
Corrective Action: Perform the actions described in the INCONTROL for z/OS Administrator Guide and then submit the CTDUFMPR utility with the DELETE function.
Explanation: This information message indicates that the CTDUPMIS utility started.
Corrective Action: No action is required.
Explanation: This information message indicates that the CTDUPMIS utility completed successfully.
Corrective Action: No action is required.
Explanation: This error message indicates that the CTDUPMIS utility discovered problems during processing. Additional information on the problems is available in the job log.
The utility stops.
Corrective Action: Examine the job log for error messages describing the problems. Make any necessary corrections and rerun the utility.
Explanation: The parameter parm is specified in the CHANGE TO statement to be updated, but the similar parameter for selecting values to be updated is not specified.
The utility stops.
Corrective Action: Correct the input parameters in the JCL and rerun the job.
Explanation: The parm input parameter specified in the JCL for the CTDUPMIS utility is not valid.
The utility stops.
Corrective Action: Correct the invalid parm input parameter in the JCL and rerun the job.
Explanation: The parm input parameter for the CTDUPMIS utility is required, but it is missing.
The utility stops.
Corrective Action: Add the missing parameter to the JCL and rerun the job.
Explanation: The parm input parameter for the CTDUPMIS utility has already been specified.
The utility stops.
Corrective Action: Remove the extra input parameter from the input parameter stream in the JCL and rerun the job.
Explanation: At least one SELECT statement must be specified in the input parameters stream, but none are specified.
The utility stops.
Corrective Action: Correct the input parameters in the JCL and rerun the job.
Explanation: The parm input parameter for the CTDUPMIS utility exceeds the maximum allowable length.
The utility stops.
Corrective Action: Correct the invalid parm input parameter in the JCL and rerun the job.
Explanation: There are no parameters specified in either the SELECT or the CHANGE TO statement. At least one parameter must be specified.
The utility stops.
Corrective Action: Correct the input parameters in the JCL and rerun the job.
Explanation: This information message indicates the number of decollation mission definition members and categories selected during the CTDUPMIS utility run.
Corrective Action: No action is required.
Explanation: This information message indicates the number of decollation mission definition members and categories updated during the CTDUPMIS utility run.
Corrective Action: No action is required.
Explanation: This information message indicates that the value of the parm decollation mission parameter is changed from old_value to new_value.
Corrective Action: No action is required.
Explanation: This information message indicates that the old_value of the parm decollation mission parameter is deleted.
Corrective Action: No action is required.
Explanation: This information message indicates that the new_value of the parm decollation mission parameter is added.
Corrective Action: No action is required.
Explanation: This warning message issued by the CTDUPMIS utility when the CHANGE TO statement includes instructions to add a new decollation parameter value to the decollation mission definition, but that parameter value already exists in the selected decollation block.
The new value is not added and the decollation mission definition is not updated.
Corrective Action: Examine the input parameters. Change the parameters and rerun the utility if necessary.
Explanation: This warning message issued by the CTDUPMIS utility when the CHANGE TO statement includes instructions to delete class x from the ON-CLASS or ON-TRNCLASS decollation mission definition, but x is the only class in this statement. It cannot be deleted because this statement must contain at least one class value.
The x class value is not deleted and the decollation mission definition is not updated.
Corrective Action: Examine the input parameters. Change the parameters and rerun the utility if necessary.
Explanation: This information message is issued before these messages: CTDMSGW, CTDMSHW, CTDMSOE, and CTDMSPE. It indicates which decollation member and category the following message is related to.
Corrective Action: No action is required.
Explanation:The STORE=CAT input parameter is specified for the CTDUPMIS utility, but the OUTLIB parameter is not specified. The STORE=CAT parameter can only be specified when the OUTPUT parameter is specified.
The utility stops.
Corrective Action: Correct the input parameters in the JCL and rerun the job.
Explanation: The MEMBER parameter is specified in the CHANGE TO statement for the CTDUPMIS utility, but the OUTLIB parameter is not specified or the OUTLIB library is the same as the REPLIB library. The member name can only be changed when the OUTPUT parameter specifies a library different from the input REPLIB library.
The utility stops.
Corrective Action: Correct the input parameters in the JCL and rerun the job.
Explanation: The CTDUPMIS utility issues this message when the invoked SORT utility ended with errors.
The utility stops.
Corrective Action: To identify the problem, examine the messages issued by the SORT utility to SYSOUT. Make the appropriate changes in the JCL and rerun the job.
Explanation: This information message indicates that the decollation member is stored in the library specified in the OUTLIB parameter with the name: new_member.
Corrective Action: No action is required.
Explanation: The CTDUPMIS utility attempts to change the class value to x or add class x to a generic decollation mission definition, but the class x is not specified in the list of generic classes in the CTDPARM parameters member.
The decollation mission definition is not updated.
Corrective Action: Examine the input parameters. Change the parameters and rerun the utility if necessary.
Explanation: The CTDUPMIS utility attempts to change the class value to x or add class x to a non-generic decollation mission definition, but the class x is specified in the list of generic classes in the CTDPARM parameters member.
The decollation mission definition is not updated.
Corrective Action: Examine the input parameters. Change the parameters and rerun the utility if necessary.
Explanation: There are no decollation mission definitions found in the REPLIB library satisfying the selection parameters specified for the CTDUPMIS utility.
The decollation mission definition is not updated.
Corrective Action: Examine the input parameters. Change the parameters and rerun the utility if necessary.
Explanation: The parm parameter is specified in the CHANGE TO statement to be updated, but this parameter is only available as a selection parameter in the SELECT statement.
The utility stops.
Corrective Action: Correct the input parameters in the JCL and rerun the job.
Parent Topic |