×
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.
Can we leave it at this? As a software vendor you're probably going to
get stepped on if you try to enforce a shop standard throughout all your
clients that QTEMP
a - Has to be in the library list.
b - Has to be in a specific part of the library list (like top or bottom)
As vendor distributed code, if you mean QTEMP, then qualify QTEMP (if at
all possible).
In Crispin's example of the CL program that was written to be used for
either one then I'd wager there had to be a program previously called, or,
ran from the command line, that had to create the object in QTEMP in the
first place. That first program should do the proper overrides.
Like
CL1:
PGM
CRTDUPOBJ MYFILE TOLIB(QTEMP)
OVRDBF MYFILE TOLIB(QTEMP)
CALL CL2
DLTOVR MYFILE
DLTF QTEMP/MYFILE /* Don't assume CL1 is last in job stream */
ENDPGM
CL2:
/* Program designed to use either QTEMP, or 'real' library */
PGM
/* real work */
ENDPGM
There are exceptions to every rule, like the rare CL command that does not
respect overrides.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
