Here's the thing:  I hate to implement something through job auditing,
because it effects the user's system too extensively.  This may be the
solution for some shops, but if they're already doing a RTVJRNE on the job
audit log journal, I could hose them up, big time...

I have several other possible approaches, but unlike other issues we face, I
don't know that any of these are gonna be do-able and/or adequate:

a) Write the interactive portion in ILE RPG, and use condition handlers to
monitor.  Can condition handlers monitor for HLDJOB, SYSREQ...?  (Evidently
not, but I'm still not for sure...)

b) Have the batch job check the status of the interactive job, prior to each
I/O.  Performance killer, but at least it will be in batch.

c) Change/duplicate the IBM commands to handle this functionality.  Easiest
to do (probably be keeping a table of Int/Bch jobs anyway).  I just don't
like modifying IBM commands to implement a feature like this.  I dunno...
Creating some "hook" through MI.  I do NOT like the idea of using MI to
implement the Split 5250 (but do not like the above approaches either).

d) Walden's approach of monitoring the auditing journal

e) Other...

I wouldn't try to do this with a job that loops to check for a job getting

(Thanks, Patrick, but I probably wouldn't monitor QSYSOPR with a
break-message handler.  Again, only because it could overlay existing jobs a
shop runs...)


| -----Original Message-----
| From: midrange-l-admin@midrange.com
| [mailto:midrange-l-admin@midrange.com]On Behalf Of jt
| Sent: Thursday, December 27, 2001 10:58 AM
| To: midrange-l@midrange.com
| Subject: RE: API/Condition handlers in ILE (was RE: Condition Handlers
| and CL)
| Walden,
| Thanks.  Maybe the *JOBDTA auditing will do the trick.
| jt
| | -----Original Message-----
| | [mailto:midrange-l-admin@midrange.com]On Behalf Of Walden H. Leverich
| | Sent: Thursday, December 27, 2001 10:43 AM
| |
| |
| | 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
| |
| |
| | -----Original Message-----
| | From: jt [mailto:jt@ee.net]
| | Sent: Wednesday, December 26, 2001 19:28
| | 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?
| |
| _______________________________________________
| 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.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.