IBM Mainframe Forum

This is not something which i look for output. This is basically timer job which will be run continuously. This has to be up and running every time. Without seeing spool, can i achieve this?

Have you bothered reading any of the earlier replies which suggest checking TWS rather than the spool?

Delli wrote:... This is basically timer job which will be run continuously. This has to be up and running every time. ...

And the customer pick up the tab for excessive CPU usage. Nice one...

Hello,

This has to be up and running every time. ...

Well managed systems will not permit some user/programmer task to do this. . .

Why does someone believe this needs to be running all the time? I believe you need to reconsider the design or even the "requirement". I don't yet understand why you cannot accomplish what you want using the system scheduling software

What is TWS? I'm not sure about this?

What is TWS? I'm not sure about this?

Did you actually try to find out yoursef? If not - try Google with "TWS & mainframe"

You can write a REXXSDSF that can check the jobs in the spool and check if executing via the DA tables

Delli wrote:I agree, going to spool and checking the status is very simple. ...

Obviously written by someone with little experience. Just exactly what kind of "status" is Deli looking for? This seems to be missing in all the comments so far.

"Going to spool" raises major security concerns just by the statement: whoever defined the "requirement" seems to be more of a newbie than Delli.

Doesn't OPC have a batch interface? All the schedulers I've used had one.

We use Control-M here, and for this kind of attention, you can add a line to all of the schedule entries to let someone know when something abends. You can also send messages for when jobs finish.

The best part is, you don't need to set up additional long running jobs, because guess what the scheduler is already doing...it's WATCHING FOR JOBS TO RUN AND FINISH!!