dick scherrer wrote:
The reasons for KEEP are endless.
There are usually endless bad
reasons to do something. There are Very few acceptable reasons to specify (new,keep,whatever) and i can think of none that would be acceptable for regularly run Production Applicaton jobs.
The simple answer for using KEEP is the application does not want a dataset Cataloged/CATLG.
The decision in well-managed organizations has been removed from "what the application wants". Well-managed systems have formal Storage Management support the determines what is and is not acceptable specification of the storage resources.
Dick, since you cannot think of any regularly run Production Application jobs that would use NEW,KEEP,DELETE let me give you just 1 example from my experience.
When I worked for IBM I was contacted out to the Navy in San Diego. Some of the regularly run Production Application job datasets HAD to be NEW,KEEP,DELETE since they did not want anyone accidently keying the dataset name in, for example, 3.4 and pocking around these sensitive datasets. There was security on the datasets too but the good decision to not Catalogued/CATLG was an extra security measure.
In my opinion IBM and the Navy are very well-managed organizations.