View - Turning on ERO on an existing database

Products

• View

Issue/Introduction

We are currently using standard retention on the View database and want to turn on ERO so we can run SARPAC on the database in order to move the tapes to a new VTS.

Also want to make sure we do not lose any of the existing reports. If the parms are set as follows, will the older reports be removed?

Current init parms (not changing):

NGEND=00003 
NGENI=00060 
NGENT=02562 

The ERO parameters will be set to the following:

EROOPT=YES    
EROPRO=NEW    
PRETAIN=INIT  

The SARPATAB table will have only comments, but no entries:

*  THIS TABLE IS NOT USED BUT WAS NEEDED TO RUN THE SARPAC JOB 
*   to CONVERT TO VTS FOR THE PRIMARY TAPE. \

Environment

Release : View 12.2

Resolution

If there is a blank ERO table (containing only comments), with SARINIT parameter PRETAIN=INIT, retention will be determined by what is in the parameters NGEND/NGENT. 

As the client had a setting of NGENI=60, it was recommended that it be set to NGENI=3 (followed by a SARSTC task recycle), permanently, for all databases, as anything above 3 would potentially leave many tapes owned by View having no active reports, and are being kept around due to having an index that meets the NGENI setting.