|
|
|
|
|
This group includes messages for the Control-M/Tape product.
Explanation: This message is generated in the event of an unexpected tape switch or a short cartridge.
This message follows message MIG5B7W and provides the information listed below:
Variable |
Explanation |
|---|---|
dsnLength |
Length in feet of the data set being written when the unexpected tape switch occurred. |
tapeLength |
Length of the tape in feet (taken from IOASPRM). |
unusedLength |
Estimated free space on the tape in feet when the unexpected tape switch occurred. |
The file is continued on the next tape and becomes a multivolume file. Subsequent files of this migration job will be written to a new scratch volume.
Corrective Action: Check the values provided in this message and determine a new value for tape length in the IOASPRM member.
Explanation: Initializing an input media for multistage migration failed.
The attempt to initialize media mediaName, in order to copy files from it to the target media, failed.
Files that should have been copied from this input media to the target media are skipped. Subsequent files are processed.
Corrective Action: Check other messages received in the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.
Explanation: The process of terminating media mediaName for multistage migration failed.
This media is the input media for the migration job.
Subsequent files in the migration job are processed.
Corrective Action: Check other messages received in the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.
Explanation: A file that should be moved to another media could not be allocated.
A failure occurred while attempting to allocate an input media file.
Subsequent files in the migration job are processed.
Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.
Explanation: A file that should be moved to another media could not be opened.
A failure occurred while attempting to open an input media file.
Subsequent files in the migration job are processed.
Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.
Explanation: A file that should be moved to another media could not be closed.
A failure occurred while attempting to close an input media file.
Subsequent files in the migration job are processed.
Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.
Explanation: A file that should be moved to another media could not be read.
A failure occurred while reading an input media file.
The migration of file filename is stopped. Subsequent files in the migration job are processed.
Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and reorder or rerun the migration mission.
Explanation: A failure occurred in a routine used for scanning migrated file names.
This message indicates that an internal error has occurred.
The file to be migrated, dsn, is skipped and subsequent files are processed.
Corrective Action: Record the return code and notify BMC Customer Support.
Explanation: Routine CTVAMIG received an invalid function code.
This message indicates that an internal error has occurred.
The migration job continues processing but does not use “continuous migration”. A scratch volume is used for files migrated in this migration job.
Corrective Action: Notify BMC Customer Support. Reorder or rerun the migration mission.
Explanation: A failure occurred in routine CTVAMIG.
Routine CTVAMIG reads and updates migration stages in sequence without skipping a stage.
The migration job continues processing but does not use “continuous migration”. A scratch volume is used for files migrated in this migration job.
Corrective Action: Check other messages generated by the migration job to determine the cause for the failure. Fix the problem and rerun or reorder the migration mission.
Explanation: This information message indicates that an attempt to allocate a tape volume in order to perform continuous migration failed.
The migration job attempted to allocate a specific volume that was used in a previous migration job in order to add files migrated by the current migration job after the last file on the volume.
A scratch volume is allocated for the files migrated by current migration job.
Corrective Action: Check other messages to determine the cause for the failure.
Explanation: This information message indicates that a DD statement for the migrated user file is missing.
For each migration mission, a record that specifies information about continuous migration is saved in the migrated user file. This information enables files migrated by the current migration job to be written in the same volume used by a previous migration job for the same migration mission.
Continuous migration is not performed. Files migrated by the current migration job are written to a new scratch volume.
Corrective Action: Add DAMIG and DAMIGI DD statements for the migrated user file in migration job step MIGRAT.
Explanation: The migration process failed while rewriting the File Description Block (FDB).
During the migrate-to-disk process, several extents may be written. After writing the last extent, the FDB is rewritten to the first extent.
All migrated file extents are deleted. The migration for this CDAM terminates with an error.
Corrective Action: Determine the cause of the rewrite failure and rerun the migration job.
Explanation: This information message indicates that the dsn index migrated successfully.
The message identifies the volume serial number and, for OSS migration, the platter ID to which the index migrated. This message is issued for each index file.
Corrective Action: No action is required.
Explanation: This information message indicates that the dsn index has previously migrated to the same target media.
This message identifies the volume serial number and, for OSS migration, the platter ID to which the index migrated.
Any previously unfinished action relating to this index migration is performed now.
Corrective Action: No action is required.
Explanation: A tape migration job failed to obtain the device type of the file.
The macro DEVTYPE for the DDOPT DD statement failed. This macro is used after a file is written to tape so that the device type can be used for cataloging the file. The return code is the hexadecimal return code in register 15 from the DEVTYPE macro.
The migration process is terminated.
Corrective Action: Record the return code. Consult your system programmer. If necessary, contact BMC Customer Support.
Explanation: Tape migration failed to catalog the migrated file. The return code is the hexadecimal return code in register 15 from the CATALOG macro.
This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.
Corrective Action: Record the values of dsn and rc. Contact BMC Customer Support.
Explanation: Tape migration failed to get the JFCB extension.
Routine IOAT2A, which translates JBCBEXAD from token to address, received return code rc.
This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.
Corrective Action: Record the return code. Contact BMC Customer Support.
Explanation: OSS migration failed to build platter and volume tables using routine IOASLOS.
Routine IOASLOS failed to sort platter and volume tables.
The migration process is terminated.
Corrective Action: Check the migration skeleton job. If you cannot resolve the problem, contact BMC Customer Support.
Explanation: The migrated file expanded to another tape volume.
A file that was expected to fit on one volume, or in the space available on the current volume, has expanded to another volume.
Corrective Action: Check the tape length definition in the IOASPRM member. If it is too short, specify the correct length. If hardware compression is utilized, the actual compression factor may be lower than the estimated compression factor.
Explanation: Routine CTVTPCP, which calculates tape lengths, returned a non-zero return code.
Tape migration failed to calculate the data set’s length on tape.
The migration process is terminated.
Corrective Action: Record the return code. Contact BMC Customer Support.
Explanation: The number of CDAM blocks exceeds 32767.
The OSS migration process cannot migrate files which contain more than 32767 blocks.
This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.
Corrective Action: Reduce the report size or divide the report so that the number of CDAM blocks required does not exceed 32767.
Explanation: The PARM parameter is not specified in the migration job.
The user must specify a media name and prefix or the keyword “NOCHECK”.
The migration process is terminated.
Corrective Action: Add the PARM parameter and specify a media name and prefix or the keyword NOCHECK.
Explanation: The migration process received an invalid media name in the PARM field.
The media name should be specified in the NAME parameter of the IOASPRM member in the IOA PARM library.
The migration process is terminated.
Corrective Action: Change the IOASPRM member or the migration skeleton job so a valid media name is specified in the migration job.
Explanation: This information message indicates that the migration process has started.
Corrective Action: No action is required.
Explanation: The OPT file was successfully allocated and opened, but RDJFCB for a migrated file failed or no volumes were found in the JFCB.
This CDAM data set is not migrated. The migration process continues to migrate other CDAM files.
Corrective Action: Ask your system programmer to contact BMC Customer Support.
Explanation: An error occurred while writing a CDAM extent or an index file.
Possible causes include:
This CDAM data set or index is not migrated. The migration process continues to migrate other CDAM files and indexes.
Corrective Action: Check the job’s system log and SYSPRINT for error messages. Correct the problem and resubmit the migration job.
Explanation: This information message indicates that OSS migration found a platter side with enough space for the CDAM file but no volume was available.
The migration process could not allocate the file on platter platterId because no empty volume was available.
Another platter or side is used.
Corrective Action: Define more volumes for platter platterId side x so that it can be used for migration.
Explanation: The OSS device could not be obtained for OSS migration, or the tape drive could not be allocated for tape migration.
The CTVSRVD program must execute before OSS migration to ensure that the IOA Archive Server releases the first device defined for OSS. A tape drive must be allocated for tape migration.
The migration process is terminated.
Corrective Action: For OSS migration, ensure the CTVSRVD program executes before the migration step. For tape migration, check if the device is available for allocation. If no error is discovered, contact BMC Customer Support.
Explanation: The migration process did not identify the file name.
A blank is expected at the end of the file name on the SYSIN DD statement.
The migration process is terminated.
Corrective Action: Check the migration skeleton job for an error in the SYSIN data set definition. If no error is found, contact BMC Customer Support.
Explanation: The migration process encountered a data set that could not be located.
A CDAM extent or index file was not cataloged.
The entire CDAM data set or index file is not migrated. Other data sets continue to migrate.
Corrective Action: Correct the problem and rerun the Migration Mission.
Explanation: A file could not be obtained on the device to which it was cataloged.
The migration process uses LOCATE and OBTAIN macros to get file attributes. The OBTAIN macro failed.
The entire CDAM data set or index file is not migrated. Other data sets continue to migrate.
Corrective Action: Correct the problem and rerun the Migration Mission.
Explanation: The CDAM file for the dsn data set spans more than five tape volumes.
Before writing each file, the migration process determines if the file will fit on a volume, based on the media capacity specified in the IOASPRM member. If the file is larger than the specified volume capacity, the migration process uses as many volumes as needed (up to a maximum of five).
The CDAM file is not migrated.
Corrective Action: Modify the report (for example, by subdividing it into two or more reports) or the decollating mission (for example, by specifying migration to a different media) so that the migrated file will not require more than five tape volumes.
Explanation: The file block size is larger than 100K bytes.
BLKSIZE must not exceed 100K bytes.
This data set is not migrated.
Corrective Action: Redefine the block size and rerun the Migration Mission.
Explanation: A CDAM TTR could not be converted to BBB.
IOASTBT calculates the BBB of the CDAM. The conversion failed for this CDAM file.
This CDAM file is not migrated. Other CDAM files continue to migrate.
Corrective Action: Correct the problem and rerun the Migration Mission. If the problem cannot be resolved, contact BMC Customer Support.
Explanation: The unit name of the target media is unknown to the migration process. The TYPE parameter in the IOASPRM member contains an invalid value.
The migration process is terminated.
Corrective Action: Correct the TYPE parameter. Rerun the Migration Mission.
Explanation: No more space is available on the deviceId device.
There is no volume with enough space for this migration.
The migration process is terminated.
Corrective Action: Free space on the volumes available to the migrated files allocation. Rerun the migration mission.
Explanation: The IOASLOS module failed.
OSS migration uses the IOASLOS module to load OSS platter and volume tables to memory.
The migration process is terminated.
Corrective Action: Check the OSS migration skeleton for errors and rerun the Migration Mission. If the problem persists, contact BMC Customer Support.
Explanation: This information message indicates that a Migration Mission completed successfully.
The message identifies the volume serial number and, for OSS migration, the platter ID to which the CDAM data set migrated. This message is issued once for each CDAM extent.
Corrective Action: No action is required.
Explanation: The data set referenced by the ddName DD statement could not be opened.
Possible causes are:
The migration process is terminated.
Corrective Action: Check the migration skeleton job for errors and rerun the Migration Mission.
Explanation: This information message indicates that a Migration Mission started processing the CDAM data set whose name is dsn.
Corrective Action: No action is required.
Explanation: This information message indicates that a Migration Mission finished processing the CDAM data set whose name is dsn.
The CDAM data set migrated successfully. This message is issued once after all extents of the CDAM file have migrated.
Corrective Action: No action is required.
Explanation: This information message indicates that CDAM data set dsn has already migrated to the same target media.
The message identifies the volume serial number and, for OSS migration, the platter ID to which the CDAM data set migrated. This message is issued once for each CDAM extent.
Any previously unfinished action relating to this CDAM migration is performed now.
Corrective Action: No action is required.
Explanation: This information message indicates that the time for ending the migration process has passed. The stop time defined in the MIGENDTM parameter in the IOASPRM member in the IOA PARM library prevents the migration process from interfering with online work during the day.
The migration process is terminated when the currently migrating CDAM data set finishes migrating.
Corrective Action: In the future, start the migration process earlier, or change the MIGENDTM parameter to a later time. Order the migration mission again the next night to complete the migration.
Explanation: Internal routine routineName failed.
The migration process terminates with a return code of 16 in register 15.
Corrective Action: Contact BMC Customer Support.
Explanation: An attempt to write a data set on disk failed because the data set requires more space than is available on any disk with the specified prefix.
The data set is not written or cataloged.
Corrective Action: Do one or more of the following:
Explanation: The migration job has encountered a file which could not be deleted.
The migration job could not delete a file during cleanup after an error occurred while writing a migrated file to DASD.
The file is not deleted.
Corrective Action: Determine why the delete failed. Delete the file before rerunning the migration process.
Explanation: This warning message is issued when a BLKSIZE definition causes disk space to be wasted.
The CDAM file’s BLKSIZE becomes the BLKSIZE of the migrated file. The disk migration process discovered that the migrated file BLKSIZE wastes a large number of bytes on each track.
The file is migrated.
Corrective Action: Consider redefining the CDAM file’s BLKSIZE to minimize wasted disk space after migration.
Explanation: The Filetek storage machine WRITE function that is activated by a migration job failed.
In this message, rc is the return code from the WRITE function.
The migration job skips the problematic file and continues with the next file.
Corrective Action: Check the return code of the WRITE function against the Filetek documentation, and correct the problem accordingly.
Explanation: The Filetek storage machine WRITE function that is activated by a migration job failed.
In this message, rc is the return code from the WRITE function.
The migration job skips the problematic file and continues with the next file.
Corrective Action: Check the return code of the WRITE function against the Filetek documentation, and correct the problem accordingly.
Explanation: The migration job failed to locate a file in the Filetek storage machine.
The variables in this message are:
The migration job skips the problematic file and continues with the next file.
Corrective Action: Check the messages the migration job issues for the locate failure, and correct accordingly.
Explanation: The Filetek storage machine START_SEARCH function that was activated by a migration job failed.
The variables in this message are:
The migration job skips the problematic file and continues with the next file.
Corrective Action: Check the return code of the START_SEARCH function against the Filetek documentation, and correct the problem accordingly.
Explanation: The Filetek storage machine END_SEARCH function that was activated by a migration job failed.
The variables in this message are:
The migration job skips the problematic file and continues with the next file.
Corrective Action: Check the return code of the END_SEARCH function against the Filetek documentation, and correct the problem accordingly.
Explanation: OAM MEDIA issued a warning that the total size of the object exceeds the maximum.
The user-defined number of blocks in an object was multiplied by the block size. The result exceeded the maximum allowed size. The maximum size allowed by Control-D is 3,000,000 bytes.
The object size is automatically set to be the maximum possible size. This value is both a multiple of blocksize and a number less than 3,000,000.
Corrective Action: Consider reducing the value of the OBJSIZ parameter in IOASPRM.
Explanation: During LOCATE processing in OAM, Control-D found a collection without a first object.
IBM macro OSREQ was issued with a QUERY request to OAM on the first object in the collection. This object was not found. However, the reason code returned was other than x2C01 (“DIRECTORY ENTRY NOT FOUND”).
In this message, collName is the name of the collection with the missing first object.
The system treats the file as an empty file. The migration attempts to re-migrate file collName to OAM.
Corrective Action: See the OAM Programmer’s Reference or the DFSMSdfp Diagnosis Reference for an explanation of this warning.
Explanation: Control-V was unable to load the DSNALI module.
The DSNALI module verifies updates to OAM files. There are two responses to an attempt to update an OAM file:
The migration program terminates.
Corrective Action: Make the DSNALI module available to Control-V. Note the error message and consult your DB2 administrator.
Explanation: This information message is an internal message that Control-V uses to transfer information from one program to another.
Corrective Action: No action is required.
Explanation: This information message is issued for each Centera clip created during Control-V migration to the EMC Centera storage system.
In this message, clipId is the name of the clip.
Corrective Action: No action is required.
Explanation: Connection to EMC Centera cannot be established. This message is followed by message MIG5E9I, which issues the Centera pool value used for connection.
The variables in this message are:
The job terminates with a nonzero return code.
Corrective Action: Refer to EMC Centera documentation for a description of the received reason code.
Check the pool value printed in the accompanying MIG5E9I message. If the IP addresses are not correct, update them in parameters POOL1-POOL4 in the IOASPRM member. Then rerun the migration mission or the utility that issued this message.
Explanation: An error was detected during creation of a new EMC Centera clip for a migrated CDAM or index file.
The variables in this message are:
The dsn dataset is not migrated.
Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.
Explanation: An error was detected while writing a block of the migrated dataset to the EMC Centera clip.
The variables in this message are:
The dsn dataset is not migrated.
Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.
Explanation: An error was detected while closing an EMC Centera clip.
The variables in this message are:
The dsn dataset is not migrated.
Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.
Explanation: An error was detected during termination of the EMC Centera device.
The variables in this message are:
The EMC Centera connection is not terminated.
Corrective Action: Refer to the EMC Centera documentation for a description of the received reason code. If you cannot resolve the problem, contact the EMC Centera experts.
Explanation: This information message follows message MIG5E4E.
In this message, pool is the pool value specified in parameters POOL1-POOL4 in the IOASPRM member.
Corrective Action: No action is required.
Explanation: This information message is issued for each Centera clip deleted by the CTVCLMIG utility. This message is followed by message MIG5E3I, which contains the deleted clip name.
The variables in this message are:
Corrective Action: No action is required.
Explanation: A className error was detected while retrieving the retention period for the specified retention class. Usually this message is issued when the specified retention class does not exist in the EMC Centera definitions.
The migration job stops with a return code of 12. Files are not migrated.
Corrective Action: Check the specified className in the migration mission definition CENTERA RETENTION CLASS field. If the specified className is incorrect, correct it and reorder the migration mission. Otherwise contact EMC Centera technical support.
Explanation: This message is issued by the CTVCLMIG utility if the media name kept in the $SYSDATA record is not found in the IOASPRM member.
The CTVCLMIG utility stops with a return code of 8.
Corrective Action: Add the specified mediaName in the message media to the IOASPRM member and rerun the CTVCLMIG utility.
Explanation: This information message is issued for each deleted file migrated to UFS. This message is followed by message MIG5EFI, which contains the name of the deleted file. The message includes the return code (rc) and reason code (rsn).
Corrective Action: No action is required.
Explanation: This is an informative message that follows several UFS-related messages. The message specifies the name of the migrated file.
Corrective Action: No action is required.
Explanation: An error was detected while attempting to create a file migrated to UFS. The file is not created. The message includes the return code (rc) and reason code (rsn) for the error.
This message is followed by message MIG5EFI.
Corrective Action: Ensure that the address space that is trying to create the file has sufficient permissions to create the file.
Explanation: An error was detected while attempting to delete a file migrated to UFS. The file is not deleted. The message includes the return code (rc) and reason code (rsn) for the error.
This message is followed by message MIG5EFI.
Corrective Action: Ensure that the file exists and that the deleting address space has sufficient permissions to delete the file.
Explanation: No pool file with the name specified by the POOL parameter was found in the primary and secondary migration target folders pointed to by the PATHPRI and PATHSEC parameters.
Corrective Action: Ensure that the file exists and that the remote NFS is mounted.
Explanation: UFS media initialization has failed. The message includes the return code (rc) and reason code (rsn) for the error.
Corrective Action: Check the UFS media configuration in the IOASPRM parameter member and re-check the UFS media setup steps described in the INCONTROL for z/OS Administrator Guide.
Explanation: Control-V has failed to perform an action in the PATHPRI or PATHSEC folder.
This message is followed by message MIG5EFI.
Corrective Action: Ensure that the address space has sufficient permissions to perform the action.
Explanation: An error was detected while writing a file to UFS. The message specifies the name of the original data set and also includes the return code (rc) and reason code (rsn) for the error.
This message is followed by message MIG5EFI.
Corrective Action: Ensure that the address space has sufficient permissions to perform the action.
Explanation: An error was detected while reading a file migrated to UFS. This message contains the following variables:
This message is followed by message MIG5EFI.
Corrective Action: Ensure that the address space has sufficient permissions to perform the action.
Explanation: An error was detected while closing a file migrated to UFS. The message specifies the name of the original data set and also includes the return code (rc) and reason code (rsn) for the error.
This message is followed by message MIG5EFI.
Corrective Action: Ensure that the address space has sufficient permissions to perform the action.
Explanation: UFS media termination has failed. The message includes the return code (rc) and reason code (rsn) for the error.
Corrective Action: Check the UFS media configuration in the IOASPRM parameter member and re-check the UFS media setup steps described in the INCONTROL for z/OS Administrator Guide.
Explanation: An error was detected while reading a file migrated to UFS. This message contains the following variables:
This message is followed by message MIG5EFI.
Corrective Action: Ensure that the address space has sufficient permissions to perform the action.
Parent Topic |