Position of QTEMP in library list

Tags:
Development
I am creating programming standards for a new Iseries partition. We have a disagreement among the team members, as to where QTEMP should reside in the library list. Some want to see it at the top, others want to see it at the bottom. As I rarely use QTEMP, I have no personal preference. Does anyone have any input on where QTEMP should reside - and what reasoning was used in the decision? Thanks!
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

It would depend on your requirements of course. For example, if you have objects residing in QTEMP that your interactive programs need to access on a regular basis (and your library list is large) you may want to move it to the top – not that it makes much of a difference nowadays with machines being as fast as they are.

I have seen programs that temporarily move QTEMP to the top.

Like I said, depends on your requirements. If there’s no pressing need I would leave it at the bottom.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Byimw02
    The placement of QTEMP depends on your programming standards or app requirements. Traditionally in my experience, QTEMP was the first library in the user portion of the library list and used as a job's temporary library. This allowed apps to create temp files without qualifying libraries or using the override file command. I worked in a few shops where the standard was to create QTEMP work files as subsets of larger production tables for batch report and other production processes. This was in the early days where OPNQRYF and SQL performance were a larger issue so we created temp PF and LF using the same name of production tables. QTEMP is also used by vendor utilities as a repository for job-related temp objects. The placement of QTEMP in our shop is dependent upon the application's design but is usually the first in the list. Whatever you decide, you can begin by setting the basic user library list in the system value QUSRLIBL. From that point, the apps can adjust the list according to the need. There is also the flexibilty to consider changing libraries in the system, product, current portions of the library list. Now that the list was expanded to hold up to 250 libraries, the constant adjusting of the user list is unnecessary. You should also consider the operational standards in addition to the programming standards since operation's library list may be different from a programmer's list. Hope this helps.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: