Messages UMGM00 through UMGMxx

This group includes messages for the Control-V product.

UMGM01I CONTROL-V UNMIGRATE STARTED

Explanation: This information message indicates that the CTVUNMIG Control-V utility started.

CTVUNMIG returns migrated files to DASD.

Corrective Action: No action is required.

UMGM02I CONTROL-V UNMIGRATE ENDED O.K.

Explanation: This information message indicates that the CTVUNMIG Control-V utility ended normally.

Corrective Action: No action is required.

UMGM03S CONTROL-V UNMIGRATE ENDED WITH ERRORS

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.

UMGM04E LOADING OF CONTROL-{D | V} INSTALLATION PARAMETERS FAILED

Explanation: Load of the CTDPARM or CTVPARM module failed.

Loading of the Control-D or Control-V Installation Parameters failed. Possible causes are:

• The IOA Load library is not in the load modules search list.
• There is insufficient memory to load the IOA Installation Parameters.
• A specified load module does not exist in the Load library.

The CTVUNMIG utility continues without sending messages to the IOA log.

Corrective Action: To produce messages to the IOA log, try one of the following:

• If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.
• If the loading failed because of lack of memory, increase the region size.

Rerun CTVUNMIG.

UMGM05S OPEN OF IOA LOG FILE FAILED

Explanation: The IOA Log file was unable to open the DALOG. DD statement.

Possible causes are:

• The DALOG DD statement is missing.
• The file allocated to the DALOG DD statement is not the IOA Log file.
• The file allocated to the DALOG DD statement is the IOA Log file, but it is of a different version or of a different IOA installation.

The CTVUNMIG utility continues without sending messages to the IOA log.

Corrective Action: To produce messages to the Job log:

1. Check the Job log for additional messages associated with this error.
2. Correct the JCL for the job
3. Rerun CTVUNMIG.

UMGM06E INVALID PARAMETER:- parm

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.

UMGM07E MISSING PARAMETERS

Explanation: The user omitted mandatory parameters from the input to the CTVUNMIG utility.

CTVUNMIG stops executing with an error.

Corrective Action: Specify the required parameters and rerun the utility.

UMGM08S UNABLE TO LOAD MODULE modName

Explanation: Control-V was unable to load the modName module.

Possible causes are:

• The IOA Load library is not in the load modules search list.
• Insufficient storage was available to load the module.
• The modName module does not exist in the IOA Load library.

In this message, modName is the name of the unloadable module.

System action depends on the cause:

• If modName is the IOASPRM module, the CTVUNMIG utility continues without IOA parameters.
• If modName is the LSMCALL module, the utility stops executing with an error.

Corrective Action: No action is required.

• If the IOA Load library is not in the search list, add a STEPLIB DD statement to the library.
• If the loading failed due to lack of memory, increase the REGION size.
• Rerun CTVMIG.

UMGM09S OPEN OF PARAMETERS FILE FAILED. DDNAME SYSIN

Explanation: CTVMIG was unable to open the SYSIN DD statement.

This problem could be due to either of the following:

• The SYSIN DD statement is missing.
• The data set described by the SYSIN DD statement cannot be opened for sequential read.

The utility stops executing with a condition code of 08.

Corrective Action: Correct the CTVUNMIG JCL, and rerun the job.

UMGM10S OPEN OF DDNAME=ddName DSNAME=dsn FAILED

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.

UMGM11I DDNAME=ddName DSNAME=dsn DYNAMIC ALLOCATION FAILED

Explanation: This information message identifies the data set name of an unallocated DD name.

This message follows dynamic allocation error message CTD922E.

The variables in this message are:

• ddName - the unallocated DD name
• dsn - the name of the data set referenced by ddName

Corrective Action: No action is required.

UMGM12I FILE DSNAME=dsn UNMIGRATION ENDED

Explanation: This information message indicates that the specified file was successfully unmigrated.

In this message, 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.

UMGM13E MIGRATED FILE EOD REACHED

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.

UMGM15E INPUT CARD WITH ORIGINAL INDEX FILE NAME IS MISSING

Explanation: A migrated Index file name is specified as a parameter to the CTVUMG utility but the card with the original Index file name and its parameters is missing.

If the message is issued during the restore migrated job run, it means that there are problems with the automatically created restore job. These problems are usually the result of manually editing the job.

The utility stops.

Corrective Action: To correct this problem do one of the following actions:

• If the message is issued during the restore migrated job run, resubmit the restore migrated mission to create a new restore job.
• If the message is issued by the CTVUNMIG utility because the migrated Index file name was manually specified as input parameter, use the restore migrated mission instead of the CTVUNMIG utility to restore Index files together with CDAM files.

UMGM1AS MISMATCH BETWEEN DISK TYPE hdtype AND REQUESTED TYPE rtype (hrtype)

Explanation: The user specified the wrong disk type in the parameter for the CTVUNMIG utility.

There was a mismatch between the disk type hdtype of the original CDAM file and the disk type that is associated with the rtype unit name.

The variables in this message are:

• hdtype - the disk type of the original CDAM
• rtype - the type of the unit requested by the user
• hrtype - the device type associated with rtype

CTVUNMIG stops executing with a condition code of 08.

Corrective Action: Specify the correct disk type in the PARM field and delete the DS name from the disk (as specified in message UNGM1BI) and rerun the job.

UMGM1BI PLEASE DELETE ALLOCATED FILE dsn

Explanation: This information message follows error message UMGM1AS and indicates the DS name to be deleted from the disk.

Corrective Action: Delete the specified file.