If this job is not mission critical, put it in a different jobq than the
mission critical stuff, a job queue where it can sit in an error state
until you get around to it.
Another point is placement of the MONMSG CPF0000. If you put this at
the beginning of the program, it will apply globally to all commands in
the program; if you place it immediately after a particular command, it
will only apply to that command.
So if you really don't care whether the program completes successfully,
you can do a global MONMSG. Also, the ones i've seen also ignore
MCH0000. But the better solution is to handle expected errors by
monitoring for them specifically and doing something appropriate.
*Peter Dow* /
Dow Software Services, Inc.
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /
On 2/13/2014 5:47 AM, Hoteltravelfundotcom wrote:
Sorry if this is a little vague.
I have a small CL that runs daily. It creates a temp file that I use in the
We use the basic IBM Scheduler, they never bought a better product here and
they won't now.
( we tried to make this a view a while back but were unsuccessful).Anyway,
I have the CPF0000
monmsg on there but a couple of weeks ago that file was in use in a diff
view I was creating at that moment so the job aborted. but it hung waiting
for a response. the problem with that is, that other jobs are stuck in the
traffic jam and if my manager had not noticed, they would not have run for
most of the evening.
In such a case, I would like the job to just quit, as the data is not
mission critical, it's just for a report that is run occassionally.
Perhaps someone knows which other monmsg CPF i would add to that CL? I
can't have my jobs holding up others. In fact, this can cause the system to
not come up because of this.
This email is free from viruses and malware because avast! Antivirus protection is active.