Error Messages › Audience › SARTDR30

SARTDR30

DSK2DRVR Driver initialization error

Reason:

The secondary driver initialization function did not perform the required initializations due to some definition error.

Action:

Verify the initialization parameters associated with the secondary disk driver are correct.

SARTDR49

Permanent I/O error reading tape

Reason:

An I/O error occurs while loading a SYSOUT group to disk.

Action:

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

SARTIA01

Expanded access tape server is not active

Reason:

TAPEOPT=EAST for the CA View database and the SAREAS server whose name appears in the EASTNAME parameter is not active.

Action:

See your system administrator to determine why SAREAS is not active. Generally, CA View attempts to directly mount the volume containing the report.

SARTIA02

Expanded access primary tape server is not active

Reason:

The primary server (responsible for mounting volumes and performing I/O) is not active.

Action:

See your system administrator to determine why SAREAS is not active. Generally, CA View attempts to directly mount the volume containing the report.

SARTIA03

Expanded access tape server abended

Reason:

The server has abended while the user's request was outstanding.

Action:

Collect the appropriate information for problem analysis, and then see your system administrator to restart the server.

SARTIA05

EASTMAXW timeout exceeded - retry later

Reason:

An attempt is made to view a report directly from tape, using the Expanded Access Server. The EASTMAXW parameter, which specifies a time-out time, was exceeded.

Action:

Retry later.

SARTIA06

Unable to locate page record vector

Reason:

You are viewing a tape report, and the Expanded Access Server was unable to locate a page record vector.

Action:

See your system administrator. Each report's page record vector is located using a field in the GCR in the DASD database. The tape could have been damaged. The system administrator can be successful in running SARPAC on just the volume containing the report, after which you can access it.

SARTIA08

End of data

Reason:

A report on tape was being viewed using the expanded access server. The END OF DATA was unexpectedly reached.

Action:

See your system administrator about running SARPAC on the volume containing the report. The report's mapping information could have been overwritten. SARPAC writes new mapping information for each report on the tape.

SARTIA09

Sysout group is not on expanded access tape

User: uuuuuuu
Gen: ggggg
Seq: sssss
ID: nnnnnnnnnnnn
ArchDate: dd/mm/yy
Database HLQ: dddddddddddddddd
TapeSeq: ttttt
Src: rrrrrrrr

Where:

uuuuuuu - Userid
ggggg - Generation
sssss - Sequence
nnnnnnnnnnnn - Report ID
dd - day
mm - month
yy - year
ddddddddddddddddd - Database High-Level Qualifier
ttttt - Tape Sequence
rrrrrrrr - Source of access

Reason:

An attempt is made to view a report on a tape that is not created with TAPEOPT=EAST or TAPEOPT=3480.

Action:

See your system administrator about running SARPAC on the volume containing the report.

SARTIA11

Logical I/O error on tape

Reason:

An attempt is made to view a report on tape using the expanded access server, and an I/O error was encountered.

Action:

See your system administrator about running SARPAC on the volume containing the report.

SARTIA12

EAS server request cancelled

Reason:

A client (DocView or DVWeb) issues a request for report data which is on tape and the CA View DRAS agent waits for EAS to return the data. But, a communications timeout has occurred and the request is cancelled.

Action:

See your system administrator to determine the reason that the timeout has occurred. A timeout value can be set too low for the requested action to complete.