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

Top or Bottom, or somewhere inbetween, entirely depends on the standards at
that development location.
If the developers use QTEMP for what it's meant for, temporary objects that
exist only during the lifetime of the job, and a naming convention that
does not step on other objects, then it really does not matter where it is,
pick a standard and go with it, Consistency is the key.

Now for those of you who like to override production or existing objects by
using QTEMP, has that practice ever been audited? Doubtful, since I highly
doubt it would pass, particularly if you have QTEMP auditing turned off. I
can think of several circumstances where that would lead to the potential
for real damage by a malevolent developer.

In the end it does not matter where you put it, as long as it's consistent.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

On Fri, Jul 1, 2022 at 9:38 AM Richard Schoen <richard@xxxxxxxxxxxxxxxxx>


That's the way it should be or don't use it.

Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx


message: 1
date: Fri, 1 Jul 2022 09:16:37 -0400
from: Richard Reeve <rjrjr64@xxxxxxxxx>
subject: Re: QTEMP position in library list

That is my argument exactly. To make things worse, there are some jobd's
here that specify qgpl first (then qtemp) and others have the reverse.
Consistency would be nice!

All the best,

Richard Reeve

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2023 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.