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



Evan Harris wrote:

it seems to me that the rationale behind the existence of QTEMP is to provide a scratchpad area for each job that runs in the system without the inconvenience of having to create a temporary library using some naming convention to avoid collisions between jobs. Sooner or later jobs run by any meaningful system are going to require the creation of temporary objects that are unique to that job and need to exist for the duration of that job only. QTEMP handles these requirements pretty well.

Hi, Evan.

But keep in mind that QTEMP is created for the job and is accessible by that job _regardless_ of whether it's listed in the job's library list. The only reason to place it in the list is so that it gets _searched_ when an object needs to be located and no library is given.

For example:

  rmvlible QTEMP
  cpyf QIWS/QCUSTCDT QTEMP/tmpcust crtfile(*yes)
  chkobj *LIBL/tmpcust *file

...gives CPF9801 "Object TMPCUST in library QTEMP not found." (assuming one isn't unexpectedly elsewhere in the list.)

But that's not because the 'scratchpad' doesn't exist. QTEMP is still there and TMPCUST is still in it. That can be shown by:

  chkobj QTEMP/tmpcust *file

No CPF9801. Object was found just fine.

Removing QTEMP from the library list doesn't delete the library; it just makes library list searches shorter. Granted, the searches also fail to find objects in QTEMP; but I was trying to understand why jobs would create objects that _needed_ to be "searched" for in the first place. Especially if they'll _only_ be found at the very last place that can be searched.

It seems to be deliberately worsening performance for no benefit.

I wondered if anyone had good reasons, ones that I'd failed to imagine.

Tom Liotta


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.