DEVSUPxx, member sys1.parmlib conflict with Top Secret TAPE control option

Products

• Top Secret

Issue/Introduction

When testing tape dataset level protection and setting TAPEAUTHDSN=YES,TAPEAUTHF1=YES in the DEVSUPxx member in SYS1.PARMLIB, does this in any way effect the usage of Top Secret?

Resolution

Setting TAPEAUTHDSN=YES will make DFSMSdfp issue additional security calls against DATASET resource class. Top Secret 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. Top Secret will respond to those dataset security calls.

With TAPE(DSN), Top Secret will perform data set name checking using the full data set name supplied on the DSNAME keyword of the JCL. If Top Secret cannot determine what the DSNAME is, such as when creating an NL tape from an SL tape, 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.