|
|
|
|
|
This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.
Explanation: Scheduling failed for the missionName mission.
This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure. The IOA Log contains additional messages concerning the reason for failure.
The mission is not placed in the Active Missions file. The system action depends on the severity of the problem. If the New Day procedure ends, it issues a return code of 08.
Corrective Action: Check the IOA Log for the reason.
Explanation: This information message indicates that a mission was placed on the Active Missions file and the mission is now in the WAIT SCHEDULE state.
Corrective Action: No action is required.
Explanation: Internal error. Invalid function code from the CTDMIS New Day procedure internal program.
The mission is not scheduled.
Corrective Action: Have your system programmer call BMC Customer Support for assistance.
Explanation: The table has been corrupted; mission data ended unexpectedly.
The CTDMIS program (the New Day procedure) terminates with a condition code of 08.
Corrective Action: Try to restore the table to its original state. If you cannot, have your system programmer call BMC Customer Support for assistance.
Explanation: The mission definition has been corrupted. Scheduling data do not conform to Control-D valid format.
This message is followed by a number of CTD527 messages, which contain all the statements that belong to the damaged mission order. The symbol * appears in the line under the erroneous data.
The CTDMIS program will terminate with a condition code of 08.
Corrective Action: Try to restore the original mission definition. If you cannot, have your system programmer call BMC Customer Support for assistance. If it is a batch New Day procedure using a permanent Date Control Record, correct the contents of the record before running the New Day procedure again. See also the CTD056S message.
Explanation: The mission definition has been corrupted. This message follows the CTD526 message, and displays each statement in the damaged mission order in the scheduling table. An asterisk * appears in the line under a damaged statement.
The CTDMIS program ends with errors.
Corrective Action: Try to restore the original mission definition. If you cannot, have your system programmer call BMC Customer Support for assistance. If it is a batch New Day procedure using a permanent Date Control Record, correct the contents of the record before running the New Day procedure again. See also the CTD056S message.
Explanation: This information message indicates that the missionName mission was placed on the Active Missions file, and the task is now in WAIT SCHEDULE state.
Corrective Action: No action is required.
Explanation: Scheduling cancelled by User Exit CTDX001, because the member did not pass user checking. User Exit CTDX001 is activated for a mission order before it is placed on the Active Missions file. If the exit specifies to the New Day procedure not to place the mission on the Active Missions file, this message is issued.
The mission order is not placed on the Active Missions file.
Corrective Action: Look for additional messages in the IOA Log clarifying the reason for the cancel. It is usually security. If you cannot find a reason, consult your system programmer.
Explanation: Open of Control-D Active Missions file failed. This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure.
Possible causes are:
Program execution stops with a condition code of 08.
Corrective Action: Correct the JCL for the job or CLIST and rerun it.
Explanation: Highlighted, unrollable message.
Control-D Active Missions file is full. No more space in the Active Missions file for new mission orders.
The mission order is not placed in the Active Missions file.
Corrective Action: Consult your system programmer immediately. Maybe you need to increase the size of the Active Missions file.
Explanation: Severe error on Control-D Active Missions file.
Possible causes are:
The CTDMIS Control-D program, which is activated as part of the New Day procedure, ends with errors.
Corrective Action: Have your system programmer call BMC Customer Support for assistance. Check whether the file was updated from two computers without global ENQ control, or perhaps by an unauthorized program.
Explanation: The Control-D Active Missions file is currently being formatted. The New Day procedure (CTDNDAY) is currently running and is formatting the file.
This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure.
Corrective Action: Try again later.
Explanation: A severe error was found in the scheduling data statements.
This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure.
Scheduling fails for the mission order. The New Day procedure terminates with a condition code of 08.
Corrective Action: Look for additional messages concerning the error, correct the error and rerun.
Explanation: Internal work areas of the New Day procedure have been exhausted. The mission order contains more data than can be handled by the current release of Control-D.
The New Day procedure terminates with a condition code of 08.
Corrective Action: Have your system programmer call BMC Customer Support for assistance.
Explanation: Scheduling failed for the memName mission. This message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure. The IOA Log or the New Day procedure output contains an earlier message concerning the reason for failure.
The mission member is not placed in the Active Missions file.
Corrective Action: Check the IOA Log and the New Day procedure output for the reason.
Explanation: Scheduling was cancelled by User Exit CTDXOO1. The specified member did not pass user checking. User Exit CTDX001 is activated for each mission order before it is placed on the Active Missions file. If the exit specifies to the New Day procedure not to place the mission order on the Active Missions file, this message is issued.
The mission order is not placed on the Active Missions file.
Corrective Action: Look for additional messages in the IOA Log clarifying the reason for the cancel. It is usually security. If you cannot find a reason, consult your system programmer.
Explanation: Loading of Control-D User Exit CTDX001 by the New Day procedure failed.
This could be due to one of the following:
As a result, no user checking is performed for the mission order. For more details, see Control-D exits in the Control-D chapter of the INCONTROL for z/OS Installation Guide.
Corrective Action: Notify the INCONTROL administrator. This is a potentially serious situation that may be an attempt to violate security.
Explanation: An internal error has occurred. The CTDINP module of Control-D issued an unknown return code.
The mission is not placed on the Active Missions file. The New Day procedure terminates with a condition code of 08.
Corrective Action: Ask your system programmer to call BMC Customer Support for assistance.
Explanation: An internal error has occurred. An invalid parameter was passed to the CTDINP Control-D module.
The mission is not placed on the Active Missions file. The New Day procedure terminates with a condition code of 08.
Corrective Action: Have your system programmer call BMC Customer Support for assistance.
Explanation: The Active Missions file is not valid. This error message is issued by the CTDMIS program, which is usually activated as part of the New Day procedure.
Possible causes are:
Program execution stops with a condition code of 08.
Corrective Action: Correct the JCL for the New Day procedure or CLIST, and rerun it.
Explanation: There was insufficient memory to perform a task.
The action that could not be performed accompanies this message. It may vary depending on the environment in which the message was issued.
Corrective Action: For jobs, increase the REGION size. For TSO, log on again using a larger SIZE parameter or exit one of the screens.
Explanation: The function requested is not authorized for the user.
This message is issued by the IOA security mechanism.
Corrective Action: Check with your system security administrator.
Explanation: The IOASMON monitor, a migration job, or the CTVCLMIG utility, failed to connect to the Filetek storage machine because the CONNECT function failed.
The probable cause for this failure is that the maximum number of connections to the storage machine was reached.
The variables in this message are:
If an IOASMON monitor fails, the monitor continually retries to connect until it succeeds, or until the device task is brought down. If a migration job or CTVCLMIG failed, it terminates with errors.
Corrective Action: Check the return code of the CONNECT function against the Filetek documentation, and correct the problem accordingly. This might require reducing the number of active device tasks to reduce the number of connections to the storage machine. If a migration job or CTVCLMIG failed, rerun the job or utility.
Explanation: This information message is issued when a message is received from the Filetek storage machine subsystem.
The variables in this message are:
Corrective Action: No action is required.
Explanation: The IOASMON monitor, migration job, or the CTVCLMIG utility failed to disconnect from the Filetek storage machine because the DISCONNECT function failed.
The variables in this message are:
The connection remains active. In the case of a migration job, or if the CTVCLMIG utility fails to disconnect, the job or utility terminate with errors.
Corrective Action: Check the return code of the DISCONNECT function against the Filetek documentation, and correct the problem accordingly. In the case of a migration job or CTVCLMIG utility failure, rerun the job or utility correspondingly.
Explanation: Initialization of an input media for multistage migration failed.
The attempt to initialize the mediaName media, 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 the mediaName input media for a multistage migration failed.
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 failure occurred while attempting to allocate the fileName input media file that should have been moved to another media.
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 while attempting to open the fileName input media file that should have been moved to another media.
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 while attempting to close the fileName input media file that should have been moved to another media.
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 while attempting to read the fileName input media file that should have been moved to another media.
The migration of the fileName file 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: An internal error has occurred. The CTVAMIG routine received an invalid function code.
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 the CTVAMIG routine.
The CTVAMIG routine 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.
In this message, volser identifies the tape volume that could not be allocated.
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: The migration process failed while rewriting the File Definition 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: A tape migration job failed to obtain the file’s device type.
The DEVTYPE macro 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 (rc). Consult your system programmer. If necessary, contact BMC Customer Support.
Explanation: Tape migration failed to catalog the dsn migrated file. The return code (rc) 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 DSN (dsn) and the return code (rc). Contact BMC Customer Support.
Explanation: Tape migration failed to get the JFCB extension.
Routine IOAT2A, which translates JBCBEXAD from token to address, received the 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 the IOASLOS routine. The IOASLOS routine 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 CTVTPCP routine, which calculates tape lengths, returned a non-zero return code.
Tape migration failed to calculate the length of the data set 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.
The dsn 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 NOCHECK keyword.
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: 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 that 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 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: 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: 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 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: The routineName internal routine 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 prefix 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 the dsn 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 dsn file before rerunning the migration process.
Explanation: The OSREQ IBM macro was unable to carry out ACCESS for the specified OAM.
The variables in this message are:
The system terminates any activity with OAM.
Corrective Action: Refer to IBM documentation. Consult either the OAM Programmer’s Reference or the DFSMSdfp Diagnosis Reference.
Explanation: The OSREQ IBM macro was unable to carry out UNACCESS for the specified OAM.
The variables in this message are:
Corrective Action: For an explanation of the return and reason codes, refer to OAM programmer reference material or DFSMSdfp diagnosis reference material, and take appropriate corrective action.
Explanation: The OSREQ IBM macro was unable to QUERY the objName object in the collName collection.
The variables in this message are:
The system action depends on who issued the message, as follows:
Corrective Action: For an explanation of the return and reason codes, refer to OAM programmer reference material or DFSMSdfp diagnosis reference material, and take appropriate corrective action.
Explanation: This information message relays a message returned from DB2 while processing IBM macro OSREQ.
The variables in this message are:
Corrective Action: For an explanation of DB2 messages, refer to IBM documentation.
Explanation: IBM OAM software was not active. Control-V attempted to initiate a connection to OAM.
The system terminates the action attempted by Control-V.
Corrective Action: Activate OAM.
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: An IBM OAM utility attempted to store an object over a different object with the same name. During migration to OAM, an OAM utility detected an object with the same name but different content. OAM DB2 tables may have been deleted by the user, and objects in the deleted tables may be connected to new collections. The MIG5CUE message immediately follows this message.
The variables in this message are:
The system stops migration for objName collName. DB2 undoes migration actions performed for this collection. A LOCATE Failed Error message is issued for the OAM migrated file.
Corrective Action: Consult your DB2 administrator. Check and fix the DB2 tables.
Explanation: Connection to EMC Centera cannot be established. This message is followed by message CTD5E9I, 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 CTD5E9I 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 CTD5E4E.
The variable in this message is:
Corrective Action: No action is required.
Explanation: The media name specified for a file to be deleted is invalid. The CTVCLMIG utility calls the CTVDEL program to delete specified files and the media on which they reside. Some of the input for CTVDEL was invalid.
The system skips the problematic file, and continues processing.
Corrective Action: Check the media name in IOASPRM, correct the problem, and try again.
Explanation: The media name specified for a file to be deleted is invalid. The CTVCLMIG utility calls the CTVDEL program to delete specified files and the media on which they reside. Some of the input for CTVDEL was invalid.
The system skips the problematic file, and continues processing.
Corrective Action: Check the media name in IOASPRM, correct the problem, and try again.
Parent Topic |