RE: API/Condition handlers in ILE (was RE: Condition Handlers and CL)

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

I'm not aware of an exit program that would report this. An API wouldn't
help since you'd have to call the API to get the answer -- actually I guess
the API would work, but you'd have to call it in a loop. How often depends
on how soon you need to know that the job got held.

However, job hold and release shows up in the history log so you could look
there, and if you're auditing *JOBDTA job holds show up there.

-Walden

------------
Walden H Leverich III
President
Tech Software
(516)627-3800 x11
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com



-----Original Message-----
From: jt [mailto:jt@ee.net]
Sent: Wednesday, December 26, 2001 19:28
To: midrange-l@midrange.com
Subject: API/Condition handlers in ILE (was RE: Condition Handlers and CL)


Tom/anyone

Is there an API that can monitor for a job getting held, or can the
condition handler API do this.

IOW, can I prevent a job from getting held?

jt

| -----Original Message----- [mailto:midrange-l-admin@midrange.com]On
| Behalf Of thomas@inorbit.com
| Sent: Wednesday, December 26, 2001 7:04 PM
| Subject: Re: Condition Handlers and CL
|
|
| On Tue, 25 December 2001, "Carsten Flensburg" wrote:
|
| > You could use the QMHSNDSM (Send scope message) API - it'll let
| you register
| > a program to run at job end (or call stack entry end or TFRJOB).
|
| This is a cool API that gets little attention. Two uses I've seen for
| it are for cleanup, especially for a job that abends, and for restarts
| of jobs you always want running -- the scope program simply resubmits
| the job which then sends a new scope message. (Of course, that last
| bit takes some planning for when you really want it to end.)
|

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.