Re: Accessing objects in another job's QTEMP

Bob,  I'm trying to think of a way to do this programatically vs with my 
fat fingers.... :)



At 01:36 PM 2/14/2006 -0600, you wrote:
>Don,
>How about STRSRVJOB and then use DSPOBJD or the API QUSLOBJ to get a list of
>objects from the serviced job's QTEMP?
>Does that work? I don't remember... :(
>
>-Bob Cozzi
>www.RPGxTools.com
>RPG xTools - Enjoy programming again.
>
>
>-----Original Message-----
>From: mi400-bounces-Zwy7GipZuJhWk0Htik3J/[email protected] [mailto:mi400-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On Behalf
>Of Walden H. Leverich
>Sent: Tuesday, February 14, 2006 1:20 PM
>To: MI Programming on the AS400 / iSeries
>Subject: Re: [MI400] Accessing objects in another job's QTEMP
>
>Don,
>
>IIRC, if you patch your PCO space and make your QTEMP address the same
>as their QTEMP address then anytime you attempt to access your QTEMP
>you're really accessing their qtemp. This was discussed a little on
>http://archive.midrange.com/mi400/200210/msg00029.html
>
>-Walden
>
>------------
>Walden H Leverich III
>Tech Software
>(516) 627-3800 x3051
>[email protected]
>http://www.TechSoftInc.com
>
>Quiquid latine dictum sit altum viditur.
>(Whatever is said in Latin seems profound.)
>
>
>-----Original Message-----
>From: mi400-bounces-Zwy7GipZuJhWk0Htik3J/[email protected] [mailto:mi400-bounces-Zwy7GipZuJhWk0Htik3J/[email protected]] On
>Behalf Of dr2-8VsyYNX/[email protected]
>Sent: Tuesday, February 14, 2006 11:32 AM
>To: mi400-Zwy7GipZuJhWk0Htik3J/[email protected]
>Subject: [MI400] Accessing objects in another job's QTEMP
>
>
>
>Greetings,
>
>I think we hit this topic back several releases ago and I'd like to see
>if there's anything enhanced in recent history.
>
>The current need is to be able to catalog name, type and size of objects
>in other job's QTEMP for disk and object use analysis.  I don't need to
>necesarily open or assign the objects a lock state, but I do need to be
>able to get thier attributes for systems analysis use.
>
>I'm not aware of an API that allows retrieval of this from a supported
>IBM side, and if it's not there, it probably should be.
>
>And since the list has been quiet for too long I thought I'd drop this
>out there to see if anyone's got a nice way to skin this
>cat...prefereably sans system state pgms...but I'm not excluding
>anything at this point.
>
>Thanks
>
>D.Rima
>
>
>_______________________________________________
>This is the MI Programming on the AS400 / iSeries (MI400) mailing list
>To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected] To subscribe, unsubscribe,
>or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/mi400
>or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
>Before posting, please take a moment to review the archives at
>http://archive.midrange.com/mi400.
>
>
>_______________________________________________
>This is the MI Programming on the AS400 / iSeries (MI400) mailing list
>To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/mi400
>or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/mi400.
>
>
>
>
>_______________________________________________
>This is the MI Programming on the AS400 / iSeries (MI400) mailing list
>To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/mailman/listinfo/mi400
>or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/mi400.
>


_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400-Zwy7GipZuJhWk0Htik3J/[email protected]
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request-Zwy7GipZuJhWk0Htik3J/[email protected]
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.