Yes, that's correct. The ACS routines get control for new individual GDG generations at allocation time, not for catalog entries. The GDG base is a catalog entry and is created at IDCAMS DEFINE GDG time. So while the systemwide defaults can be set in IGGCATxx, they can be overridden by anyone defining a GDG by simply specifying the desired values in the DEFINE GDG control statement.
Using ACC, which gets control at SVC 26 (DEFINE) time, one can set policy rules which will take precedence over both the IGGCATxx defaults and the IDCAMS DEFINE GDG specification. So if you wanted to force GDGs to be defined as extended-format, NOSCRATCH, FIFO, etc., you'd specify this in the ACC policy rules. You could also do things like have ACC check some arbitrary RACF resource to see if a user is authorized to specify SCRATCH or NOSCRATCH, etc. Similarly, ACC policy rules can control the use of pretty much any IDCAMS parameter on DEFINE or DELETE as well as overriding any JCL or dynamic allocation values (space, VOLSER, UNIT, etc) for ordinary non-VSAM or VSAM datasets. Steve Pryor DTS Software, LLC [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
