Reason:
A tape created with encryption enabled (initialization parameter ENCRYPT set to ICSF) under r11.6 or higher cannot be processed by View r11.5.
Action:
The database must be versioned back to r11.6 or higher, the tapes must be consolidated (SARPAC) with the initialization parameter ENCRYPT set to NO, then the database can be versioned back to r11.5.
Reason:
The tape on which the selected report resides on is not cataloged, or a dynamic allocation error or an open error occurred in an attempt to access the tape.
Action:
See your system administrator to determine the reason that the tape cannot be found or accessed. The system log of the SAREAS server gives dynamic allocation return codes for problem analysis. Check the system catalog to ensure that the correct volume is cataloged.
Reason:
An attempt is made to view a report on tape using the Expanded Access Server, and the report spans more than 16 tapes.
Action:
SAREAS can accommodate reports spanning 16 or fewer volumes. The report is not viewable unless CA Technical Support can create an optional zap. The entire page record vector is read in before the report can be accessed, so response time could have been slow and memory requirements in a multi-user environment could have been prohibitive.
If software compression was not in effect when the report is written to tape, the system administrator could set the SOFT option of the TAPEOPT parm and SARPAC the volumes containing the report, and the user could try accessing the report again.
Reason:
None of the EASTNAMx parameters currently specifies the unit containing the report. That is, the report is on a tape volume for which no server has been defined.
Action:
Retry the access. The device must be requested directly without the server. Alternatively, ask the CA View administrator to define a server for the unit.
Reason:
The OPEN of the tape data set failed although the dynamic allocation succeeded. Since the device allocation and tape mounts completed successfully, the OPEN failure can be due to security problems or other obvious errors, consult the job logs and/or system logs for other non-CA View messages related to this tape data set.
Action:
An attempt is made to switch to the duplex. Map the original tape using SARTCP to determine if any CA View utility can access this tape dataset without problems. If no obvious problems exist, contact Technical Support at http://ca.com/support to report the problem. Include the job logs showing the problem messages, a SARTCP map of the physical tape volume, a SARTSLST list of the tape sequence number, and the error if no security problems or other obvious errors exist.
Reason:
ERR= is the error code returned by the operating system's Dynamic Allocation function and DSN= is the tape data set name.
Dynamic allocation has failed for the archival tape (DSN). The hexadecimal error is provided. The following are the most common dynamic allocation errors:
Invalid unit specification, a SARTSLST of the failing tape sequence number can be run to determine the unit name originally assigned to the tape when it was created. The following job can be run outside of CA View to determine if this unit name is valid:
// JOB //STEP EXEC PGM=IEFBR14 //TAPE DD DSN=..tape_dsn..,DISP=OLD,UNIT=unitname
The tape volume is currently mounted and in use by another job, as an example, attempting to /LOAD or /PRINT a report from a tape which is currently in use by the Backup Cycle or a tape consolidation utility (SARPAC). Retry after the job holding the tape volume has completed.
The SMS controlled tape is not cataloged. Catalog the tape.
Action:
Attempt to correct the above stated condition. If recovery is unsuccessful, contact Technical Support at http://ca.com/support to report the problem. Include the job logs showing the problem messages, a SARTCP map of the physical tape volume, and a SARTSLST list of the tape sequence number.
Reason:
A permanent I/O error occurs while attempting to position the archival ape. The error can occur for any of the following reasons:
Recovery is attempted by switching to the duplex/primary tape.
Action:
If the I/O error is due to a hardware tape drive failure, rerun the failing job to obtain a different hardware tape drive. If the I/O error is due to a tape media failure, SARTCP can be used to create a new primary tape if a duplex tape exists, or the offending sub-files can be skipped/nulled during a copy to a new physical tape.
If recovery is unsuccessful, contact Technical Support at http://ca.com/support to report the problem. Include the job logs showing the problem messages, a SARTCP map of the physical tape volume, and a SARTSLST list of the tape sequence number.
Reason:
tttt is the tape type, PRIMARY, DUPLEX, or DRTAPE, and nnn is the tape sequence number. The reason is one of the following:
Action:
Use SARTCP to map the tape and attempt to locate the desired Sysout. If the Sysout is found on the tape, SARTDR/TADD the tape to the database.
If recovery is unsuccessful, contact Technical Support at http://ca.com/support to report the problem. Include the job logs showing the problem messages, a SARTCP map of the physical tape volume, and a SARTSLST list of the tape sequence number.
Reason:
The file for the requested SYSOUT group is empty. This is most likely caused by a tape recovery using SARTCP. An attempt is made to switch to the duplex/primary tape.
Run SARTSLST List against the tape sequence number to find the recorded file position number. Use SARTCP Map to determine if the file position contains the desired Sysout or a NULL file.
Action:
If the tape contains the desired Sysout, SARTDR/TADD the tape to the database and retry the failing job. If the tape contains a NULL file at the designated location, attempt to create a PRIMARY tape from a DUPLEX tape if one exists, if not, the data is lost.
If recovery is unsuccessful, contact Technical Support at http://ca.com/support to report the problem. Include the job logs showing the problem messages, a SARTCP map of the physical tape volume, and a SARTSLST list of the tape sequence number.
Reason:
A permanent I/O error occurs when reading the data on the tape. The operating system can also provide an IOS000I I/O error message which can contain additional information concerning the I/O error. Recovery is attempted by switching to the duplex/primary tape.
Action:
Use SARTCP Copy to SKIP/NULL the bad sections of the tape, if the desired Sysout is in the area where the I/O error is occurring than use SARTCP Copy to create a PRIMARY tape from a DUPLEX tape if one exists, if not, the data is lost.
Reason:
In order to recover from an error with the archival tape, a switch to the duplex/primary tape is being made.
Action:
None, this is an informational message. If you do not want the switch to occur, you can reply NO to the tape mount message.
Reason:
When positioning the archival tape, a tape Sysout header record (the Sysout's Group Control Record (GCR)) did not contain the same Sysout designations as the copy in the database, that is, the Sysout Id, generation and/or sequence numbers did not agree with the database copy. If the Sysout spans multiple tapes, the header record on the succeeding tape(s) can be invalid. Recovery is attempted by switching to the duplex tape.
Action:
Run SARTSLST List against the tape sequence number and SARTCP Map against the tape to determine that the correct Sysouts are in the correct positions.
If the tape contains the desired Sysout, SARTDR/TADD the tape to the database and retry the failing job. If the tape does not contain the Sysout, the data can be lost.
If recovery is unsuccessful, contact Technical Support at http://ca.com/support to report the problem. Include the job logs showing the problem messages, a SARTCP map of the physical tape volume, and a SARTSLST list of the tape sequence number.
|
Copyright © 2013 CA.
All rights reserved.
|
|