Re: 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.

Bruce Vining




"Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx> 
Sent by: mi400-bounces@xxxxxxxxxxxx
02/14/2006 01:55 PM
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






Bruce,

Will the changes in V5R4 or later prevent us from changing our job's
QTEMP to be another job's QTEMP?

Both those APIs appear to be useful for reporting, but sometimes it
would be nice to have complete control including the ability to
add/change/delete objects and data in objects.

-Walden

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

Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)


_______________________________________________
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.