Require tapes to be cataloged on z/OS 1.7

Is there a parmlib option or some other mechanism that enforces a requirement that tape data sets be cataloged when they are created? Our environment is RMM on z/OS1.7. -- For IBM-MAIN subscribe / signoff / archive access instru

Re: Require tapes to be cataloged on z/OS 1.7

Bryce, There is no option like that in a z/OS component, nor in RMM. The closest RMM can get to this is to use VRSes with WHILECATALOG and enforce that all tape data sets are cataloged else they are expired. Create it, then bin it.. An installation exit such as 'File Validate' (IFG019FV) cou

Re: Require tapes to be cataloged on z/OS 1.7

Mike Wood wrote: Bryce, There is no option like that in a z/OS component, nor in RMM. The closest RMM can get to this is to use VRSes with WHILECATALOG and enforce that all tape data sets are cataloged else they are expired. Create it, then bin it.. An installation exit such as 'File Vali

Re: Require tapes to be cataloged on z/OS 1.7

On 7/3/2007 6:24 AM, R.S. wrote: What about CATDSNS in RACF ? Does it work for tape datasets ? BTW: This option can be misleading: a job step which created the dataset can access it despite of catalog disposition. The dataset will be unavailable later. The SETROPTS CATDSNS option in RACF wo