[Fwd: Restricted Interactive RUNQRY]

[John Earl <johnearl@xxxxxxxxxxxxxxx>]

--
John Earl                    johnearl@400security.com
The PowerTech Group      --> new number --> 253-872-7788
PowerLock Network Security   www.400security.com
--

---

• Subject: Re: Restricted Interactive RUNQRY
• From: John Earl <johnearl@xxxxxxxxxxxxxxx>
• Date: Mon, 11 Sep 2000 00:57:06 -0700
• Organization: The PowerTech Group

Al,

MacWheel99@aol.com wrote:

> To test the theory, use EDTLIBL to edit the sequence of libraries while you
>   are signed on.
>

Just to be clear, EDTLIBL will not allow you to affect libraries in the system
portion of the library list.  EDTLIBL only works on the user portion of the
library list.


> > I can't change the order of the libs in the
> >  System Libl for particular users, can I?
>
> I don't see why not.  I thought SYSVAL was the default before anyone mucked
> with their library list.
> GO CMDLIBL to see the LIBL commands available, then incorporate some in a CL.

<snip>

> I have several CL which
> 1. Add some library to *LIBL & specify if *FIRST or whatevr in the list
> 2. Run some software that uses objects in that library that are not qualified
> & often in the form of submit some job
> 3. Remove that library from *LIBL

I know that this is a popular method for directly qualifying objects, but I 
curse
whenever I run accross it in code.   Hard-coded libraries make testing a much
more difficult and error prone procedure.  It is like a little booby trap in the
code that is going to jump up and bite some unsuspecting programmer someday.

If you need to add a library, or qualify an object to a library, you should use 
a
JOBD, or the PSDS, or a softcoded record or data area.  Anything but a
specifically named library.

IMHO,

jte

--
John Earl                    johnearl@400security.com
The PowerTech Group          206-575-0711
PowerLock Network Security   www.400security.com
--

---