Error Messages › Audience › SARSVR02

SARSVR02

DYNAMIC INTERFACE MISSING FOR xxxxxxxxxxx

Reason:

The dynamic interface verification for the interface xxxxxxxx failed.

Action:

Contact CA Technical Support.

SARSVR03

DYNAMIC INTERFACE RE-EFFECTUATED FOR xxxxxxxx

Reason:

The CA View systems extension interface was installed. The systems extension interface routines are loaded or reloaded and then activated when SARXTD is executed.

Action:

None. This is an informational message.

SARTCH01

INVALID PARM SPECIFICATION: CORRECT JCL AND RESUBMIT JOB

Reason:

The tape sequence number or range specified in the JCL PARM field for the SARTCHK program is invalid. The syntax for the JCL PARM field is as follows:

EXEC PGM=SARTCHK,PARM='database,tapeseq1-tapeseq2'

where:

Action:

Correct the parameter specification, and then resubmit the job.

SARTCH02

NO UNCATALOGUED TAPE DATA SETS WERE FOUND

Reason:

All the tape data sets referenced in the database, referenced by the tape sequence number, or range on the JCL PARM field is catalogued.

Action:

None. This is an informational message.

SARTCH03

NO MATCHING TAPE SEQUENCE NUMBERS FOUND

Reason:

The database does not contain any tape control records, 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.

SARTCP01

Control card error

Reason:

There is an error in the specified control statement.

Action:

Correct the control statement, and then resubmit the job.

SARTCP02

Invalid parm specification

Reason:

The JCL PARM field for the SARTCP program is invalid. The only valid JCL PARM field is COPYASIS.

Action:

Omit or correct the parameter specification, and then resubmit the job.

SARTCP03

ADDHDR parm not valid, tape has a CA View Header

Reason:

Copying a tape using the ADDHDR parameter but the input tape has a CA View Header (SARHDR).

Action:

Remove the ADDHDR parameter and re-run the tape copy.

SARTCP10

Input tape I/O error, ECB=XX, BLOCK=XXXXXXX,SENSE=XXXX
Enter S(kip blk), E(nd), OR C(ancel)

Reason:

A permanent I/O error occurs while reading the specified block from the input tape. The ECB and SENSE codes are provided.

Action:

Reply S to skip the bad block and continue, E to terminate the job, or C to abend the job.

SARTCP11

Output tape I/O error, ECB=XX, BLOCK=XXXXXXX, SENSE=XXXX

Reason:

A permanent I/O error occurs while writing the specified block to the output tape.

Action:

Resubmit the job using a different output tape.

SARTCP12

Write tape mark I/O error, ECB=XX, SENSE=XXXXX

Reason:

A permanent I/O error occurs while writing a tape mark on the output tape.

Action:

Resubmit the job using a different output tape.

SARTCP16

Processing successfully completed

Reason:

Processing has been successfully performed.

Action:

None. This is an informational message.

SARTDO42

Device allocation error - ERR=xxxx, INFO=xxxx
DSNAME=xxxxxxxxxxxxxxxxxx
Reply Y/N to continue processing with new tape

Reason:

Dynamic allocation has failed for the DR tape. The hexadecimal error and information codes are provided.

Action:

Reply Y to the message to allocate a new tape and continue processing. Otherwise, reply N, correct the problem with the tape, and restart the function.

SARTDO43

I/O error forward spacing media - new volume forced

Reason:

A permanent I/O error occurs when attempting to forward space the DR tape. A new tape volume is used and execution continues.

Action:

None. This is an informational message.

SARTDO44

Catalog error on DR tape - DSN=(dataset), RC=nn.nn

Reason:

An error occurs when attempting to catalog the DR tape. The data set name, the return code, and reason code from the catalog management are provided.

Action:

Correct the problem with the catalog structure.

SARTDO46

(dataset name) already exists - new volume forced

Reason:

Allocation of a new DR tape is being attempted for the specified dsname, but the dsname is already cataloged to the system.

Action:

None. A new tape volume and dsname are used.

SARTDO47

Unable to obtain device characteristics for unit

Reason:

The device characteristics for the specified unit are not available by using the DEVTYPE system service.

Action:

Normally, an invalid device name as specified by the DRUNITB or DRUNITP initialization parameter causes this condition. Otherwise, consult your systems programming group to determine why the DEVTYPE system service cannot be performed against the unit.

SARTDO49

Permanent I/O error writing DR media, new restart OPT=NEW

Reason:

A permanent I/O error occurs while writing to the 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.

SARTDO54

Tape to be mounted needs write capability

Reason:

The DR 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.

SARTDO56

DR tapes must be created on 3480 or higher tape units

Reason:

DR tapes require a 3480 or higher device type.

Action:

Correct the tape unit name in the DRUNITB or DRUNITP definition.

SARTDO59

Bad block ID, using SEQUENTIAL reading to locate append point

Reason:

For best performance, CA View uses a block ID to locate the appendage point on a tape volume. Because CA View did not find the correct information at that point on the tape volume, it rewound the volume and used sequential read to locate the point to append.

Action:

Contact Technical Support at http://ca.com/support to report the problem. This message is informational only. If the locate by sequential reading succeeds, the only impact is on performance. If the located by forward space file fails, a new tape volume is requested.

SARTDO60

Error closing DR tape

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 the tape can cause a locate block ID (SARTDO59) error if additional backup cycles are written to this tape.

Action:

The tape can be used to recreate the DR tape.

SARTDR00

TADD of tape "tape dsn" to database "dbname" is NOT RECOMMENDED
Report dates and generations will be out of sequence and a MERGE will be required
Reply "C" to continue or "S" to stop

Reason:

SARTDR allows any backup tape to be added to any DATABASE. If the tape was from another database, it often causes date selection errors where users are unable to locate some reports within a date range. After this occurs a MERGE must be run to correct these date selection errors. Tape "tapedsn" contains dates and/or generation numbers which are inconsistent with dates and generation numbers on database "dbname". A response is required.

Action:

Reply with either a C to continue with the TADD Utility or S to terminate the TADD Utility. If option C is selected to continue, execute a SARDBASE MERGE at the earliest convenience.

SARTDR01

INVALID REPLY

Reason:

The console reply to the SARTDR00 message is invalid.

Action:

When the SARTDR00 message is reissued, reply Y to authorize the execution of SARTDR, or N to cancel the execution of SARTDR.

SARTDR02

Tape sequence number does not match that of sysout group xxxxxxxx Recorded=nnnnn Actual=nnnnn

Reason:

The actual tape sequence number obtained from the data set name for the tape does not match that recorded with the SYSOUT group or page layout RESOURCE that is being added. The SYSOUT group or RESOURCE is not added.

Action:

Verify the data set name for the tape.

SARTDR03

Invalid or misplaced control card, control statement must begin with a "/"

Reason:

The specified control statement contains an error in its syntax.

Action:

Correct the statement, and then resubmit the job.

SARTDR04

POSITIONOF SYSOUT GROUP xxxxxxxx INVALID RECORDED=nnnnn

ACTUAL=nnnnn

POSITION OF RESOURCE xxxxxxxx INVALID RECORDED=nnnnn

ACTUAL=nnnnn

Reason:

The actual position of the SYSOUT group or page layout RESOURCE on the tape does not match that recorded with it. The SYSOUT group or RESOURCE is not added.

Action:

USE SARTCP to correct the problem with the tape.

SARTDR05

I/O error positioning tape

Reason:

A permanent I/O error occurs while attempting to position the archival tape to retrieve the SYSOUT group.

Action:

Salvage the data on the tape using the SARTCP utility, and then resubmit the job.

SARTDR06

Tapes not added in order for SYSOUT GROUP xxxxxxxx GEN=nnnnn SEQ=nnnnn

Tapes not added in order for RESOURCE xxxxxxxx GEN=nnnnn SEQ=nnnnn

Reason:

A multi-tape SYSOUT group or page layout RESOURCE is being added but the tapes for it have not been added in ascending order.

Action:

Re-add the tapes for the SYSOUT group or RESOURCE in ascending order.

SARTDR07

Authorization denied by operator

Reason:

The operator replies N to message SARTDR00.

Action:

Obtain authority to run SARTDR from the operator, and then resubmit the job.

SARTDR08

TAPE DD statement not found

Reason:

The DD statement for the tape cannot be found.

Action:

Add the DD statement to the JCL, and then resubmit the job.

SARTDR09

Invalid tape data set name

Reason:

The data set name for the tape to be added does not conform to the naming conventions for archival tapes.

Action:

Correct the problem, and then resubmit the job.

SARTDR10

Current generation set to nnnn

Reason:

The addition of the tape requires the current generation number to be reset.

Action:

None. This is an informational message.

SARTDR11

Tape added - dsname Seq=nnnn Lgen=nnnnn Hgen=nnnnn TM=nnnnn

Reason:

The specified archival tape is successfully added to the master index file. The tape sequence number, low generation number, high generation number, and number of tape marks are given in the message.

Action:

None. This is an informational message.

SARTDR14

Tape error processing sysout group xxxxxxxxxx Gen=xxxxx Seq=xxxxx

Tape error processing resource group xxxxxxxxxx Gen=xxxxx Seq=xxxxx

Reason:

An error occurs when loading the SYSOUT group or page layout RESOURCE from tape.

Action:

Consult the associated tape error message that is written to the job log for the appropriate action.

SARTDR15

Invalid function name

Reason:

A control statement was encountered with an invalid function name in the SYSIN DD statement of the SARTDR utility. The only valid functions are /TADD and /TLOAD.

Action:

Correct the control statement specification, and then resubmit the job.

SARTDR16

Invalid keyword name "xxxxxxxx"

Reason:

A control statement is encountered with an invalid keyword name in the SYSIN DD statement of the SARTDR utility.

Action:

Correct the control statement specification, and then resubmit the job.

SARTDR17

Invalid parameter data "xxxxxxx" for keyword xxxxxxxx

Reason:

A control statement is encountered with an invalid parameter specification for the specified keyword in the SYSIN DD statement of the SARTDR utility.

Action:

Correct the control statement specification, and then resubmit the job.

SARTDR18

Unbalanced parentheses encountered in parameter data for keyword xxxxxxxx

Reason:

Parameter data for the specified keyword did not contain an ending parenthesis on a control statement in the SYSIN DD statement of the SARTDR utility.

Action:

Correct the control statement specification, and then resubmit the job.

SARTDR19

Tape load successfully completed

Reason:

The /TLOAD function of the SARTDR utility completed successfully.

Action:

None. This is an informational message.

SARTDR20

Tape load ended with errors

Reason:

The /TLOAD function of the SARTDR utility completed unsuccessfully.

Action:

Review previous error messages to determine the appropriate action, and then resubmit the job.

SARTDR21

NO REPORTS ADDED TO DATABASE

Reason:

No reports are added to the database as a result of the /TADD function of the SARTDR utility.

Action:

The /TADD control statement could have specified a GEN, ID, or RESOURCE specification that does not exist in the specified backup tape. If so, change the parameter specification, and then resubmit the job.

SARTDR23

SYSOUT GROUP xxxxxxxx ADDED/LOADED to disk GEN=nnnnn

SEQ=nnn

RESOURCE xxxxxxxx ADDED/LOADED to disk

Reason:

The specified Sysout group or page layout Resource has been successfully added or loaded to primary or secondary disk.

Action:

None. This is an informational message.

SARTDR24

Database is already in use

Reason:

Another archival task with the same database is already executing.

Action:

Correct the problem.

SARTDR26

Specified identifier, resource, generation, and/or tape not found in database

Reason:

The master index does not contain any SYSOUT groups that match the ID, RESOURCE, GEN, and/or TAPESEQ parameter specification on the TLOAD control statement.

Action:

SYSOUT groups must be previously added to the master index by using the TADD control statement. If an invalid identifier name, resource name, generation, or tape sequence number was specified, correct the specification, and then resubmit the job.

SARTDR27

Storage group "xxxxxxxx" not defined

Reason:

The storage group name specified on the TADD control statement of the SARTDR utility was not found in the database.

Action:

Change the TADD control statement to reference a valid storage group name or remove the STORGRP parameter from the TADD control statement and resubmit the request.