Does CA View exploit a tape's archival capacity?
search cancel

Does CA View exploit a tape's archival capacity?

book

Article ID: 121304

calendar_today

Updated On:

Products

OM Deliver OM View

Issue/Introduction



Does CA VIEW automatically write to an archive tape until it is completely full before it asks for a new tape?

Are there any initialization parameters to ensure that the archival tape has been fully utilized?

Environment

z/OS

Resolution

* In terms of archive tapes associated to a standard backup cycle, View will write to a particular tape/volser until that tape/volser is full. 

The only parameter that would force View to start writing a standard backup to a NEW tape (even if the previous volser is not full) is the MAXGENT sub-parameter of the STORGRP0 SARINIT parameter. 

The value for the MAXGENT sub-parameter dictates the maximum number of backup cycle generations that can be written to one tape volume. When the MAXGENT value has been exceeded, the next standard backup cycle will automatically request a NEW scratch tape be mounted. 

* In terms of archive tapes associated to the SARPAC tape consolidation process, View will write to a particular tape/volser until it is full. There are no parameters that would prevent SARPAC from filling up a tapes capacity. 

* In terms of archive tapes created by the DUPLEX & Disaster Recovery (DR) tape create functions, please refer to the documentation for the DRMOD SARINIT parameter as the value specified for this parameter can affect Views ability to exploit a DR tapes capacity.

Additional Information

CA View 14.0 Reference - Initialization, Database, and Batch Processing Initialization Parameters

DRMOD