Mainframe, MVS and zOS Discussion

We have a automated rexx script which will submit job every 5 seconds or something
Of around 3800 jobs
When I submit the rexx script
It floods my spool
When no of jobs in my spool goes beyond 300
Operator calls me for more no of jobs
So I want to purge jobs once it is completed via batch jcl itself
You have any idea on this.

What is the operator's concern -- the number of jobs in the system or the amount of spool output?

Talk to your site support group about using a MSGCLASS that does not retain the output on the spool. If your site has a product that supports batch processing of spool data, you MIGHT be able to do what you want - you would have to check with the product vendor.

For plain z/OS, there really is no way to do what you want.

Thanks Robert.

We can purge them using REXX though, I think. I am not REXX expert but that's what one of my friend's suggest.

Get your friend's help to code up the REXX -- I don't use it often enough to provide any assistance.

OK, I'm going to put my sysprog's hat on and ask you the question that I would ask if I were maintaining the system you're running on...

What exactly are you doing that needs a job submitting every five seconds?

The problem with jobs is that you've got absolutely no guarantee as to when they are going to run. If this is something that is timing critical, then you are likely to run into issues as well as annoying other users and the people running the system. From my perspective, and without knowing what's going on, the spooled output sounds like the consequences of a design issue rather than something that needs to be worked around.

All the question makes sense, though I don not have very accurate answer for them. As I am just made part of the project and have this situation with me.

Just now I am thinking to answer what is being asked to do rather then tweaking the process which definitely requires a second look. Though right now I am thinking if I keep on purging the jobs also, then that might help.

Thanks for all your help. For bow we have just brought the number of jobs to a lower number per REXX execution.