MVSFORUMS.com

[semigeezer]

In general, having a program submit a job is bad practice because the program has no way of knowing if or when the job will run and if, when it finally does run, if it was successful. If job card requirements change, or data set names or many other things, the program needs to be recompiled. There are many other reasons not do do this (job classes, authorization, authentication, etc, etc, etc). In this case, you should use dynamic allocation to delete the data set, or if you know the name ahead of time, just use an extra step in the job. Search this board for examples of dynamic allocation.

By the way, the correct terminology is "submit JCL", not "submit a JCL". If you need the article, then the terminology is to submit a job or a job stream. I only mention this because the term "a JCL" is new within the last few years or so and identifies the user as a "newbie" (and usually as an employee of an outsourcing contracting firm). Using correct terminology will often get you better, more accurate, more complete answers because that particular term does not sit well with many of us old timers for reasons better left alone but which should be obvious.

[avid_lrner]

Hi semigeezer,

Noted your reply and will make sure to use the right terminology.

Thanks for the correction.


regards,
avid_lrner.