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


Article ID: 49910


Updated On:


CA Cleanup CA Datacom CA DATACOM - AD CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA Datacom/AD CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Top Secret CA Top Secret - LDAP CA Top Secret - VSE



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?


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:

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.


Component: AWAGNT