How to Provide Security for CA View Database Extended Format Databases

Document ID : KB000124024
Last Modified Date : 31/12/2018
Show Technical Document Details
With the use of SARDBASE ADDDS ... ABOVE to create large View database extents, beyond the 4369 cylinder limit, there will be a physical-sequential (PS) file created, which can affect what security can be used on those datasets. 

With the use of the maximum of 4369 cylinders, and a direct-access (DA) file being created, typical access methods
were not allowed to read that format. 

With the DSORG=PS, that leaves open the possibility of access to the data using non-View methods. 

With that, other security may need to be considered, and SARXTD's dataset security function can be used to protect the database extents. 
CA View - Releases 12.2 and higher
From the previous maximum of 4369 cylinders (65535/15) allowed per View database extent, the limit was increased to 32760 cylinders, for large datasets.

The continuing client requests for being able to allocate larger database extents necessitated having to make the change of the type of dataset from DA to PS, due to IBM restrictions.

With the change in dataset type, the need for security changes, if the larger extents are to be used.

This dataset security can be provided by CA View Systems Extensions, SARXTD.

With the SARXTD dataset security feature, access can be limited to the database extents.

With use of PARM='index,...', the high-level index (one or more qualifiers are separated by periods with a maximum length of 17 characters), data security will be activated for the CA View data sets. 

After the data set security feature is activated, any program (other than CA View) that has not been marked in the program properties table to bypass password protection is restricted from accessing any data set whose name begins with the specified high-level index.
Additional Information:
Please see the View Reference Guide, regarding the SARXTD dataset security feature, for further information.