×
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 20-Apr-2016 07:17 -0500, David Gibbs wrote:
I'm curious ... does anyone put QTEMP in their system library list?
Are there any strong reasons to not put QTEMP in the system library
list?
If by "system library list", the /system-portion/ of the library list
is meant, then AFaIK, that library name is prevented from being
specified in all interfaces for the setting of, i.e. from appearing as
an entry in, the SYS part of the *LIBL. It is my recollection, and I
expect none of following allow that effect:
• Change System Library List (CHGSYSLIBL)
• Change Subsystem Description Description (CHGSBSD) [for SYSLIBLE
parameter, per msg CPD0090 yielding "Parameter SYSLIBLE value cannot be
QTEMP."]
• Change System Value (CHGSYSVAL) to QSYSLIBL [whereby the value
QTEMP in the string for VALUE(), or as entered on the panel for Work
With System Values (WRKSYSVAL), I expect would be diagnosed as an error,
but I can not test].
If instead the the User-portion of the library list [the USR part of
*LIBL], alluding to the System Value QUSRLIBL to define the
/user-portion/ of the library list was meant, then there have been
several past discussions here about the good and the bad with regard to
if\not and where within the User part of the library list that QTEMP
should appear. FWiW, the *only* library I have in my User portion other
than my Current (CURLIB) is QTEMP; I depend on library-qualifying
anything not in a library in the System portion, and that the command or
program that is invoked will properly establish a Product (PRD) library
or otherwise add\remove the necessary libraries for its proper operation.
midrange.com
