× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




On 16/01/2007, at 7:46 AM, Peter Dow (ML) wrote:

Do we know whether OS/400 etc expect QTEMP anywhere in particular in the
library list?

No, and I'm not sure it even has to be in *LIBL. I asked IBM about QTEMP location some time ago and got back no particular recommendation. I haven't received my append back yet but unless you edited it then it looks like the last few paragraphs got chopped by something. Here they are again:

Only two of these objects are visible via DSPLIB QTEMP. All the rest are internal things.

I expect internal code finds QTEMP from the pointer in the WCB rather than the *LIBL but probably not a good idea to remove QTEMP entirely unless you *KNOW* nothing in the job needs it.

For what it's worth I'm in the "stick QTEMP at the top of *USRLIBL" camp and I think those who put it in *SYSLIBL should be shot.

And who (or what) is BL?

Perhaps this makes more sense now you can see the complete sentence?

Regards,
Simon Coulter.
--------------------------------------------------------------------
   FlyByNight Software         OS/400, i5/OS Technical Specialists

   http://www.flybynight.com.au/
   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175                                   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.