We are currently in a disaster recovery exercise and in our DR environment SAR is abending with the error below.
We have modified our storage groups to avoid altering tapes and overwriting production data by directing all archive TAPE allocation to DASD/DISK, but we can create new tapes.
When we start View with "START SARVIEW1,OPT=NEW" (which has worked in the past), we get the same abend as when we start it without that additional parm.
Messages shown in the View task log:
IEF695I START SARVIEW1 WITH JOBNAME SARVIEW1 IS ASSIGNED TO USER CAIUSER , GROUP EXPRESS
$HASP373 SARVIEW1 STARTED
IEF403I SARVIEW1 - STARTED
SARSTC00 CA View 14.0.02 is initialized
SARBKT00 Interim backup cycle started for Gen 8824 on 10/18/2022 at 12:08:45
SARBKT61 Interim backup cycle starting phase 1
SARTP056 Immediate tape access requires 3480 devices
CCSR010E SARSDAPI U0056 at 1B875A6A LMOD SARTPO CSECT SARTPO +004D82 SARVIEW1 N/A SARVIEW1
CCSR021I OWNER = CA VIEW R14.0
CCSR022I MODULE = SARTPO FMID = CBRME00 RMID = CBRME00
CCSR061I PSW: 00000000 00000000 078C1000 9B875A6A
CCSR062I ILC: 02 INTERRUPT CODE: 0D
CCSR067I COMPLETION CODE U0056 REASON CODE 00000000
CCSR064I DATA AT PSW 1B875A64 : 00181610 0A0D1FFF 58E0D004
14.0, View, CA View, SARTP056
ACS routines were altered to direct all TAPE allocations to DISK
The archival functions in View, which would include both the BACKUP function as well as the direct to tape archival function of the TAPECLSL parameter, require a unit allocation of TAPE (Or VTS simulated TAPE), in order for the archival function to work. This is in part due to the fact that the specified unit must be able to support fast positioning using BLOCK ID processing.
A more technical explanation of the above requirement is contained in the following excerpt, which was provided by View SE in another case involving a SARTP056 error...
"The SARTPO56 message is a result of looking at the UCB Device Type after a
Dynamic Allocation to the tape device unit specified in the STORGRPx
parameter. The field UCRTYP3 (Device Class) must be X'80' (Tape), and field
UCBTYP4 (Device code) must have its high order bit on (3480 Processing). The
device code indicates that this device is capable of handing LOCATE BLOCK ID
and SEARCH BLOCK ID tape commands".
Considering the above, based on your statement indicating you "can create new tapes" on your DR system, there is nothing wrong with the way you have your SARINIT TAPEOPT and STORGRP0 parameters configured, provided that you have an esoteric definition on your DR system for UNIT=3490 and a TAPE unit is allocated.
SARINIT for NAME=VIEW.DBNAME:
- Our recommendation for resolving the problem would be for you to modify your ACS routines so that a TAPE (or simulated TAPE) unit is allocated, rather than a DISK unit.
- Once your ACS routines have been modified, upon restarting View use the "START SARVIEW1,OPT=NEW" command.
The TAPEOPT parameter specifies EAST, but the tape unit does not support block ID processing. The abend is accompanied by the following message:
SARTPO56 IMMEDIATE TAPE ACCESS REQUIRES 3480 TAPES
Correct the tape unit name in the STORGRPx definition, correct the tape unit's system definition, or change TAPEOPT to use 3420 processing.