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 tape must be consolidated (SARPAC) with the initialization parameter ENCRYPT set to NO, then the database can be versioned back to r11.5.
Reason:
xxxxxx is the requested hardware Block Id, and yyyyyy is the Block Id of the block after the hardware LOCATE BLOCK ID command is issued to the tape.
A hardware failure has occurred while CA View was trying to position to a report on tape. The operating system can also provide an IOS000I I/O error message which can contain additional information concerning the I/O error.
Action:
CA View attempts to read the tape sequentially rather than using high-speed record positioning LOCATE BLOCK ID command.
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:
Dynamic allocation has failed for the backup tape. The hexadecimal error and information codes are:
The error code returned by the operating system's Dynamic Allocation function.
The Dynamic Allocation function REASON Code.
The tape data set name.
The following are the most common dynamic allocation errors:
021C
Invalid unit specification, the unit specification is defined in the STORGRP Initialization parameter:
STORGRPn=/db/maxgent/primary-unit,duplex-unit/
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=NEW,UNIT=unitname
0220
The requested volume is not available which can be the result of a code defect.
0270
Request requires more non-sms-managed volumes than are eligible. Assistance from the group managing SMS can be required.
0484
Request denied by operator.
04E5
The system cannot allocate tape devices, because a tape allocation subsystem eliminated all eligible devices from consideration. Assistance from the group managing SMS can be required.
1708
The request tape is not in the catalog.
9700
A severe Storage Management Subsystem (SMS) error occurred which can be the result of SMS rules for the dataset name and unit specifications and can require assistance from the group managing SMS.
9704
A severe Storage Management Subsystem (SMS) error occurred which can be an internal SMS code defect.
Action:
Reply Y to the message to allocate a new tape and continue processing. Otherwise you can reply N and correct the problem with the tape, and restart the function.
Reason:
A permanent I/O error occurs when attempting to forward space the archival tape. A new tape volume is used and execution continues. This message is normally accompanied by messages SARTPO59 and IOS000I which must provide addition information.
Action:
None. This message is informational.
Reason:
An error occurs when attempting to catalog the archival tape. The data set name, the return code, and reason code from catalog management are provided.
The tape dataset name.
The LOCATE Macro return (rr) and reason (SS) codes.
The Z/OS LOCATE Macro return codes are:
4 Either the required catalog does not exist or it is not open.
8 One of the following happened:
20 There is insufficient space in the catalog data set.
28 One of the following happened:
The Z/OS LOCATE Macro reason codes are:
Unable to allocate a required catalog.
Either the data set was not found or the catalog could not be opened.
There was an I/O or unrecoverable error on locate.
There was an I/O or unrecoverable error on nonlocate.
Insufficient space was supplied.
The function was not valid.
Security or password verification failure.
ESTAE or GETMAIN return code was nonzero.
Action:
Correct the problem with the catalog structure.
Reason:
A primary tape with archival data normally appends with more archival data, however; tape duplexing has been requested. Since the primary and duplex tape volumes must be exact copies of each other, a new primary tape is forced. This can be due to a system failure while writing the Duplex Tape Control Record and the count of Sysouts on each tape are not identical.
Action:
None. This message is informational.
Reason:
Allocation of a new backup tape is being attempted for the specified dsn, but the dsname is already cataloged to the system.
Action:
None. A new tape volume and dsname are used.
Reason:
The device characteristics for the specified unit are not available by using the DEVTYPE system service. Recovery is attempted by switching to the duplex tape.
Action:
Normally, this condition is caused by an invalid device name as specified by the UNITT sub-parameter of the STORGRPx initialization parameter. Otherwise, consult your systems programming group to determine why the DEVTYPE system service cannot be performed against the unit.
Reason:
A permanent I/O error occurs while writing to the primary, duplex, or DR tape. The backup cycle abnormally terminates with a user U '0049'.
Action:
Restart the archival task (SARSTC) with a 'NEW' or 'INEW' parameter to allocate new tapes. The archival task can also be restarted with the 'STOPBU' parameter followed by the system modify command 'F SARSTC,NEW' or 'F SARSTC,'INEW' to allocate new tapes.
Reason:
The archival tape to be mounted is written on and requires a write enabled cartridge.
Action:
Verify that the tape to be mounted is not write-protected. If tapes are not write-protected, this message can be eliminated by setting the TPO54 initialization parameter to NO.
Reason:
The DSK2PARM specifies a unit that is not a tape device.
Action:
Correct the DSK2DRVR name to use the correct driver if it is in error, correct the DSK2PARM to use a tape device, or correct the tape unit's system definition.
Reason:
The TAPEOPT parameter specifies EAST, but the tape unit does not support block ID processing.
Action:
Correct the tape unit name in the STORGRPx definition, correct the tape unit's system definition, or change TAPEOPT to use 3420 processing.
Reason:
CA View must create a tape volume, but the specified range has been exhausted.
Action:
Define new volumes and modify the range in the STORGRPx or STORGRXx parameter.
Reason:
CA View writes several blocks to a tape volume simultaneously. The maxblks specification in the STORGRXx parameter is below this number (currently 10).
Action:
Correct the maxblks specification in the STORGRXx parameter.
Reason:
For best performance, CA View uses a block ID to locate the appendage point on a tape volume. CA View did not find the correct information at that point on the tape volume, so it rewound the volume and used forward-space-file to locate the point to append.
Action:
Contact Technical Support at http://ca.com/support to report the problem. The message is informational only, and, if the locate by forward-space-file succeeds; the only impact is on performance. If the locate by forward-space-file fails, a new tape volume is requested.
Reason:
An unrecoverable hardware I/O error occurred while writing the tape's End-of-File Label, or one of the two required tape marks. The tape is usable as a backup media for reports and Master Index copies, but can cause a Locate Block ID (SARTPO59) error if additional backup cycles are written to this tape. This message is normally accompanied by an IOS000i message.
Action:
The tape can be consolidated using the SARPAC utility (if you are an EAS site) or SARTCP utility to create new primary and/or duplex tapes.
Reason:
CA View queues up to 100 'tape write block' commands while the tape sub-system is writing the data to the physical tape, and waits until 100 blocks are queued while the tape catches up and issues 'block id sync' command to test the tape drive's progress. If the tape drive's block id status does not change after 100 sync commands, message SARTP099 is issued, all I/O is canceled and the task, either the Backup Cycle or the SARPAC Consolidation Utility is terminated with a Return Code 4.
Action:
This is a hardware error and the function must be re-tried. For assistance, contact Technical Support at http://ca.com/support.
Reason:
The tape sequence number or range specified in the JCL PARM field for the SARTSLST program is invalid. The syntax for the JCL PARM field is as follows:
EXEC PGM=SARTLSLT,PARM='database,tapeseq1-tapeseq2'
where:
|
database |
Specifies the high‑level prefix name of the database |
|
tapeseq1 |
Specifies the starting tape sequence number |
|
tapeseq2 |
Specifies the ending tape sequence number (optional) |
Action:
Correct the parameter specification, and then resubmit the job.
Reason:
The CTLCARDS DD statement is required for the SARTSLST program when a tape sequence number or range is specified on the JCL PARM field.
Action:
Add the CTLCARDS DD statement to the JCL and resubmit the job.
Reason:
The database does not contain any tape control records or the tape sequence number or range specified in the JCL PARM field is not in the database.
Action:
If the tape sequence number or range specified in the JCL PARM field is incorrect, correct the parameter specification and resubmit the job.
|
Copyright © 2013 CA.
All rights reserved.
|
|