Comments on: Best way to monitor a job

By: jaymz69

jaymz69 — Fri, 28 Jan 2011 14:51:00 +0000

I use the iseries Navigator now but when the system shutsdown and reboots over the weekend my job never starts back up.

I read to add &START in the name but that still did not work.

By: jaymz69

jaymz69 — Thu, 27 Jan 2011 14:45:54 +0000

We have V6r1 now

By: jaymz69

jaymz69 — Thu, 27 Jan 2011 14:44:45 +0000

Yes QINTER Jobs

By: Featured Member: Mariodlg - ITKE Community Blog

Featured Member: Mariodlg - ITKE Community Blog — Thu, 27 Jan 2011 06:33:03 +0000

[...] Best way to monitor a job [...]

By: tomliotta

tomliotta — Wed, 26 Jan 2011 02:44:33 +0000

What not have the MSGW break in QSYSOPR…

Probably because these are “…job(s) in QINTER”.

Tom

By: hmssl2k

hmssl2k — Wed, 19 Jan 2011 21:41:19 +0000

What not have the MSGW break in QSYSOPR, that way your ops team will notify the correct person to fix the problem.

By: tomliotta

tomliotta — Wed, 19 Jan 2011 20:06:32 +0000

There are different ways, depending on your OS VRM and other elements. For some background, see iSeries *MSGW error message capture. As noted, it can be a little easier starting with i 6.1.

Or you might consider a Management Central ‘Job Monitor’. You should be able to select all jobs in subsystem QINTER with a metric of job status ‘Waiting for message’. You’d probably need to experiment to get the monitor fine-tuned for what you actually need.

Still, “best” might be to purchase some product that does the job.

But “best” is hard to pin down from any distance. Make sense?

Tom

By: tomliotta

tomliotta — Tue, 18 Jan 2011 23:44:04 +0000

What is the best way…

“Best”?

I learned something many years ago — “We can do it cheap, we can do it fast, and we can do it good. Pick any two.”

The more you focus on any one area, the more the other areas will suffer. “Best” needs to address elements of all three areas, but how do you want to split them up?

What do you mean by “best”? Fewest false positives? Fewest false negatives? Least intrusive? Fastest performance? Easiest creation? Least future maintenance?

Who will be coding and maintaining it? (How knowledgeable is that person?) What languages are appropriate? What versions/releases of the OS need to be supported?

What are you expecting it actually to do? Should it notify someone, or should it do something about the job? Should it run on demand, or are you wanting it to run at all times automatically? (Should it run if QINTER isn’t active? What if a different interactive subsystem is used?)

What are you needing the system to do?

Tom