If I faced a similar problem, I would want the log of the job in question.
With that log, I would have a much better chance of handling the error and
ending the job "correctly".
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Hoteltravelfundotcom
Sent: Thursday, February 13, 2014 6:47 AM
To: Midrange Systems Technical Discussion
Subject: need for a new CPF catch MONMSG
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 Reporting tool.
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 is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l