A system abend is an error detected by CA VM:Backup that prevents the CA VM:Backup software from continuing. It may be a software or system problem in CA VM:Backup or CP. When a system abend occurs, CA VM:Backup does the following:
0026I VM:BACKUP SYSTEM ABEND code OCCURRED AT address
This chapter lists the abend codes that may appear in place of code in message 00261.
This section contains the following topics:
When possible, the text that accompanies the codes listed in this chapter indicates the cause of the abend listed and suggests a corrective course of action. For other abend codes, the text directs you to Contact Technical Support.
Before you call about an abend, make sure that you have the following information on hand:
Also, make sure that the dump is available; you may be asked to send it to CA if your problem cannot be resolved over the telephone.
Note: Any abends not documented in this chapter are caused by internal logic or other unexpected errors. If any undocumented abends occur, report them to Technical Support.
Abend messages with a code of DMSxxx are CMS abends. For information about these abends, see the appropriate IBM documentation.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
An error occurred when CA VM:Backup tried to open a DETAIL file on the catalog disk to remove references to a volser that is being reused. Contact Technical Support.
An error occurred when CA VM:Backup tried to read a DETAIL file on the catalog disk to find references to a volser that is being reused. Contact Technical Support.
An error occurred when CA VM:Backup tried to rewrite a DETAIL file on the catalog disk after removing references to a reused volser from the file. Contact Technical Support.
An error occurred when CA VM:Backup tried to close a DETAIL file it had opened and possibly modified. Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
While creating a catalog during a backup job, CA VM:Backup found that the catalog minidisk is full. For information about increasing the catalog minidisk size and using the CONDENSE and DISCARD commands, see the System Programmer Reference Guide and the Administration Guide.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
While creating a catalog during a backup job, CA VM:Backup found that the catalog minidisk is full. For information about increasing the catalog minidisk size and using the CONDENSE and DISCARD commands, see the System Programmer Reference Guide and the Administration Guide.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
CA VM:Backup encountered an error reading the CP directory. This error usually occurs when minidisk caching is used on the CP directory volume. Ensure that the CP directory volume is not cached and initialize CA VM:Backup again. If the problem persists, contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Look up the reason code in the CMS application development reference documentation to determine the cause of the problem. If necessary, contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
An error occurred when CA VM:Backup used the CP SPOOL command to spool a device to a user ID. An accompanying CP message is sent to the CA VM:Backup console indicating why the CP SPOOL command failed. If the CP message does not identify the problem with the CP SPOOL command, contact Technical Support.
Contact Technical Support.
Contact Technical Support.
An error occurred when CA VM:Backup used the CP SPOOL command to spool a device to a user ID. An accompanying CP message is sent to the CA VM:Backup console indicating why the CP SPOOL command failed. If the CP message does not identify the problem with the CP SPOOL command, contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup minidisk have been erased, renamed, or altered in some way so that the structure is invalid.
Initialize CA VM:Backup with the NOCHECK option. If this fails, initialize CA VM:Backup with the SUSPEND option. Then, run the CHECK command against the catalog minidisk to find any errors.
If errors are found, contact Technical Support and have the output from the CHECK command available. If no errors are found, END CA VM:Backup, erase the four INDEX files from the catalog disk and reinitialize CA VM:Backup as you normally do. This may take some time since CA VM:Backup will rebuild the index files when it restarts.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
CA VM:Backup attempted to perform an I/O operation on a minidisk but the minidisk was not available (a condition code 3 was returned by a Start I/O Fast or Start Subchannel operation). Verify that all DASD and related devices are enabled and available to your VM system and operating correctly. Restart CA VM:Backup and resubmit the job. If the abend recurs, contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Abends with this prefix are CMS abends. For information about these abends, see the appropriate IBM documentation.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
An internal CA VM:Backup command, normally used only after initialization, was called before initialization completed. Enter the IPL CMS command on the CA VM:Backup service virtual machine and restart CA VM:Backup.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
The CA VM:Backup service virtual machine needs more virtual storage to run. A virtual machine size of at least 12M is recommended. Either use the CP DEFINE STORAGE command or change the CA VM:Backup directory entry to define a larger virtual machine size.
If you receive this abend during CA VM:Backup system initialization, you may have attempted to initialize CA VM:Backup with a set of catalog index files that are incompatible with your CA VM:Backup release. Either erase the catalog index files and reinitialize CA VM:Backup with the REINDEX option, or initialize the compatible CA VM:Backup release.
Contact Technical Support.
The CA VM:Backup service virtual machine needs more virtual storage to run. A virtual machine size of at least 12M is recommended. Either use the CP DEFINE STORAGE command or change the CA VM:Backup directory entry to define a larger virtual machine size.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
This abend will occur if someone either detaches a tape drive while a job is running or detaches a minidisk that CA VM:Backup. was using in a backup job. This condition may also be caused by a hardware error. Restart CA VM:Backup and allow the job to be restarted. If the problem recurs, contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
The CA VM:Backup system minidisk either contains invalid data or is improperly formatted. Reformatting the minidisk may provide a temporary solution. If you want to keep the files on the system minidisk, dump the minidisk to tape with the CMS TAPE DUMP command, reformat it with the CMS FORMAT command, and then reload the files with the CMS TAPE LOAD command. Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
This abend can be caused by the report disk filling up during a CA VM:Archiver job.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
CA VM:Backup reserves a total of 2,304 virtual addresses with which to attach the tape drives used to process backup and restore jobs. The number of jobs running concurrently requested the use of more tape drives than CA VM:Backup has addresses reserved. Reduce the number of concurrent jobs or the number of tape drives needed by a single job, and allow the jobs to be restarted.
Contact Technical Support.
Someone may have detached a tape drive while a job was running. Restart CA VM:Backup and resubmit the job. If the problem recurs, contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
An error occurred when CA VM:Backup used the CP SPOOL command to spool a device to a user ID. An accompanying CP message is sent to the CA VM:Backup console indicating why the CP SPOOL command failed. If the CP message does not identify the problem with the CP SPOOL command, contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Initialize CA VM:Backup with the NOCHECK option, then run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Someone may have detached a virtual printer or the status of a virtual printer changed to not ready while a job was running. Restart CA VM:Backup and resubmit the job. If the problem recurs, contact Technical Support.
System spool space is full. Restart CA VM:Backup and resubmit the job when your system support staff has cleared some spool space.
Contact Technical Support.
An error occurred when CA VM:Backup used the CP SPOOL command to spool a device to a user ID. An accompanying CP message is sent to the CA VM:Backup console indicating why the CP SPOOL command failed. If the CP message does not identify the problem with the CP SPOOL command, contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
One or more of the CA VM:Backup minidisks are linked with the wrong link mode. For example, a minidisk that should be linked read/write is linked read-only instead. Because CA VM:Backup verifies the minidisk link modes during initialization, the minidisk has probably been relinked incorrectly since initialization. Restart CA VM:Backup. The initialization process will issue error messages for minidisks that are incorrectly linked.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
The CA VM:Backup service virtual machine needs more virtual storage to run. A virtual machine size of at least 12M is recommended. Either use the CP DEFINE STORAGE command or change the CA VM:Backup directory entry to define a larger virtual machine.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
CA VM:Backup is not authorized by the security system at your site to use the alternate user ID facility. Although CA VM:Backup was authorized at initialization, authorization has since been removed or the security system is not currently available. If the security system is available, either give CA VM:Backup the proper authorization or change the VMBACKUP CONFIG file so that CA VM:Backup does not try to use the alternate user ID facility. For more information, see SURROGAT Record in the chapter "Configuration File Records" in the System Programmer Reference Guide.
Contact Technical Support.
CA VM:Backup was using your site's security system when the security system became unavailable. Restart CA VM:Backup and resubmit the job when the security system becomes available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Someone detached a tape drive while a job is running, or a hardware error occurred. Restart CA VM:Backup and allow the job to be restarted. If the problem recurs, contact Technical Support.
Contact Technical Support.
The CSW received was not expected. The CSW stored in response to an I/O operation to a tape drive had an unusual or invalid combination of status. This generally indicates a tape drive hardware problem. Contact Technical Support.
Contact Technical Support.
This condition is usually caused when multiple CPUs have access to the same tape drive and both CPUs try to use the drive at the same time. Contact Technical Support to discuss your system configuration.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
The TAPEPOOL VMBACKUP macro returned incorrect information. If you have modified this EXEC, get a copy of it from the distribution tape, restart CA VM:Backup, and resubmit the job. If the problem recurs, contact Technical Support.
Contact Technical Support.
Someone may have detached the resource pool disk while CA VM:Backup was running. Make sure the minidisk defined on the POOLDISK record in the VMBACKUP CONFIG file is linked to CA VM:Backup and formatted. If there is no POOLDISK record in the VMBACKUP CONFIG file, 1C0 is the default virtual address for the resource pool disk.
Contact Technical Support.
Someone erased, created, or altered a resource pool while CA VM:Backup was running. Restart CA VM:Backup and look up the messages that are issued by the initialization process in as shown in the section Resource Pool Errors. After taking the corrective action described in the table, restart CA VM:Backup and resubmit the job. If the abend recurs, contact Technical Support.
Someone may have detached the resource pool minidisk while CA VM:Backup was running. Make sure the minidisk defined on the POOLDISK record in the VMBACKUP CONFIG file is linked to CA VM:Backup and formatted. If there is no POOLDISK record in the VMBACKUP CONFIG file, 1C0 is the default virtual address for the resource pool minidisk.
Contact Technical Support.
Someone may have detached the resource pool minidisk while CA VM:Backup was running. Make sure the minidisk defined on the POOLDISK record in the VMBACKUP CONFIG file is linked to CA VM:Backup and formatted. If there is no POOLDISK record in the VMBACKUP CONFIG file, 1C0 is the default virtual address for the resource pool minidisk.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
One or more of the CA VM:Backup minidisks are linked with the wrong link mode. For example, a minidisk that should be linked read/write is linked read-only instead. Because CA VM:Backup verifies the minidisk link modes during initialization, the minidisk has probably been relinked incorrectly since then. Restart CA VM:Backup. The initialization process will issue error messages for minidisks that are incorrectly linked.
Contact Technical Support.
Contact Technical Support.
Someone may have detached a virtual printer or the status of a virtual printer changed to not ready while a job was running. Restart CA VM:Backup and resubmit the job. If the problem recurs, contact Technical Support.
System spool space is full. When your system support staff has cleared some spool space, restart CA VM:Backup and resubmit the job.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
An error occurred while attempting to punch the tape pull list for a restore job to the requesting user ID. Restart CA VM:Backup and use the VOLIST command to regenerate the tape pull list. If the error recurs, spool a device to the requesting user ID from the CA VM:Backup service virtual machine. If the response from the CP SPOOL command does not identify the problem with the CP SPOOL command, contact Technical Support.
One or more of the catalog component files on your CA VM:Backup catalog minidisk have been erased, renamed, or altered in some way so that the catalog structure is invalid. Run the CHECK command against the catalog minidisk to find any errors. Contact Technical Support and have the output from the CHECK command available.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
Contact Technical Support.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|