I think that DTS Software can enforce JCL statements based on DSN or a product like ThruPut manager (I think).
Basically default JCL DISP is NEW Delete Delete (yes - there are variations, see the JCL Reference manual) The best way is to have JCL standards that are enforced in the shop. And to have a promotion package (like Endevor or Changeman) ensure they are there before the job can be placed into production. I did have a case in a past shop where a programmer was running a batch IMS job in production, using the production RESLIB. He/She failed to notice that the DISP=SHR had a blank instead of a comma. This cause the default JCL DISP to take affect. The next time the IMS regions were cycled (2 weeks later) the Production IMS Reslib was deleted. Fortunately we had a current backup and could restore it. But that cause my shop to rethink how JCL would be handled on adhoc jobs. So, depending on how controlled your environment is, there can always be a way to make life interesting. Personally I feel it is better to have an enqueue out there to indicate a problem, then masking the fact you could have a problem show up later. Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
