|
Bruce Vining wrote: >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). Bruce, Of course if you use the STRSRVJOB + TRCJOB with an exit program, there's no setup requirement in the target job either. There is some overhead with the servicing stuff, but it's pretty minimal. I use my version of this to get the QTEMP objects of batch server jobs on a daily basis. If anyone else wants the code, send me an email offline (rory dot hewitt at gmail dot com) Rory
This mailing list archive is Copyright 1997-2026 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.