CA View - SARJSA05 Message Received at DR
Article ID: 193945
Updated On:
Products
Issue/Introduction
The client was running CA View during a Disaster Recovery (DR) exercise, and received the following messages:
SARSTC00 CA View 12.2 (IN05) is initialized
SARJSA05 Subsystem get request failed - RPL feedback 0C0204
$HASP708 SARSLF SYS05397 OPEN ERROR - DATA SET WAS NOT CLOSED
RC=06 I/O ERROR READING DATA BUFFER
DSNAME=CMASM90A.CMASM90A.STC00298.D0000101.?
SARJSA05 Subsystem get request failed - RPL feedback 080298
SARJSA05 Subsystem get request failed - RPL feedback 0C0204
$HASP708 SARSLF SYS05407 OPEN ERROR - DATA SET WAS NOT CLOSED
RC=06 I/O ERROR READING DATA BUFFER
DSNAME=STCCP00.CICP1AW1.STC00355.D0000004.JESYSMSG
The View task stopped and would not restart.
How do you get the task started?
If a View first index extent and first data extent are defined on the same volume, could that cause this issue?
Environment
Release : 12.2
Component : CA View
Resolution
. Recycle the affected SARSTC task, starting it with "/S sarstc,OPT=STOPBU".
. From the start of the task until the end of the DRP, the SARSTC task ran with no problems.
. A database review showed there to be no reports in OPEN status.
. A SARDBASE STATUS FULL was run on the database in question.
. The results were RC=00, showing that the database is stable with no problems.
. Output from the client showed the DR SARSTC task to have the following $HASP708 and SARJSA05 messages.
$HASP708 SARSLF SYSnnnnn OPEN ERROR - DATA SET WAS NOT CLOSED
RC=06 I/O ERROR READING DATA BUFFER
DSNAME=STCMVS.CMSC.STC00029.D0000101.?
SARJSA05 Subsystem get request failed - RPL feedback 080298
. The $HASP708 message indicates that an application job, creating a report that was being sent to CA View, did not close the output file (SYSnnnnn), and the SARJSA05 message occurred as a result.
There was a snapshot of a database taken in production, which was used as the source for the DR exercise. There were several reports that were in the process of being collected when the snapshot was taken. When now running at DR, View was looking to finish collecting those reports, but their ends were not to be found and View responded accordingly.
---------------------------------------------------------------------------------------------------------------------------------------------------------
For a View database, the first index extent (....I0000001) and the first data extent (....D0000001) should never be placed on the same volume, as there could be performance issues.
Feedback
