|
Steve, QWCJBITP will certainly be a significant aid when trying to debug a users job, fix up some problem in a file of another users job, etc. An advantage when using this API over previous approaches (such as break handling programs) is that there is, in general, no need to have some form of setup run in the "other" job (like allocating a *MSGQ). I say "in general" as the system administrators do have some control of the use of this API with system values such as QALWJOBITP (Allow jobs to be interrupted) and job specific APIs to enable/disable job interruption. Bruce Vining "Steve Richter" <srichter@xxxxxxxxxxxxx> Sent by: mi400-bounces@xxxxxxxxxxxx 02/15/2006 08:47 AM Please respond to MI Programming on the AS400 / iSeries <mi400@xxxxxxxxxxxx> To "MI Programming on the AS400 / iSeries" <mi400@xxxxxxxxxxxx> cc Subject Re: [MI400] Accessing objects in another job's QTEMP -----Original Message----- From: mi400-bounces@xxxxxxxxxxxx [mailto:mi400-bounces@xxxxxxxxxxxx]On Behalf Of Bruce Vining Sent: Tuesday, February 14, 2006 3:06 PM To: MI Programming on the AS400 / iSeries Subject: Re: [MI400] Accessing objects in another job's QTEMP >The Call Job Interrupt Program API can do pretty much whatever it's >authorized to in the other job. This includes the ability to really mess >it up -- anyone using this API needs to fully read the documentation and >then think about what they're asking. Reporting was mentioned because >that's what Don was asking about... Change/Create/Delete type operations >certainly could be done. what is the intended use of QWCJBITP? I know in windows there is an API that injects a thread of executing into another process. You would use that API when debugging another process or I guess coding some sort of WRKACTJOB equivalent in Windows. -Steve _______________________________________________ This is the MI Programming on the AS400 / iSeries (MI400) mailing list To post a message email: MI400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/mi400 or email: MI400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/mi400.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.