How does DEVSUPxx, member of sys1.parmlib conflict with TSS TAPE() control option?

Document ID : KB000049910
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Testing tape dataset level protection.

Setting TAPEAUTHDSN=YES,TAPEAUTHF1=YES in DEVSUPxx parmlib member.

Does this in any way effect the usage of CA Top Secret?

Solution:

Setting TAPEAUTHDSN=YES will make DFSMSdfp issue additional security calls against DATASET resource class.

CA Top Secert will respond accordingly based on the dataset PERMITs made for this dataset.

TAPEAUTHF1 will make DFSMSdfp issue security calls against the DATASET class for other datasets on the tape. CA Top Secret will respond to that dataset security call.

With TAPE(DSN), CA Top Secret will perform data set name checking using the full data set name supplied on the DSNAME keyword of the JCL. If CA Top Secret cannot determine what the DSNAME is, such as when creating an NL tape from an SL tape, CA Top Secret supplies a data set name of:
$$.UNKNOWN.TAPE.DSN

TAPE(DSN) and the TAPEAUTHDSN=YES work independently of each other. You can run with both turned on.

Use of TAPEAUTHDSN=YES and/or TAPE(DSN) will still allow tape management tools like CA-1 or CA-TLMS to manage and/or secure the tapes.