RE: Determining what library a CL program is called from?

>But I just have to ask... not having years and years of 
>experience under my belt, I have to wonder under what 
>circumstances one might want two programs in the 
>library list and actually want to be executing the one 
>lower in the list?  Now I'll sit back and learn something...

Funny you should bring that up.  Quite a while ago, one of the midrange
magazines had an article on running SQL statements off the command line via
use of QMQRY.  I shamelessly recycled their idea into a reasonably generic
command-line SQL machine which I cleverly called RUNSQLSTM.  Being my
utility, it is in my library.  Time passes and we buy the IBM SQL
development kit.  IBM made their own RUNSQLSTM which is very different from
mine.  Being an IBM command, it's in QSYS.  I never want to RUN IBM's
command, but I often want to run mine, which is lower in the library list.
This forces me to qualify the command call.

I have been burnt in the past by this abnormal sequence of events:
1. Programmer releases a new version of a program into production
2. User runs program (via *LIBL)
3. Program gets an error and issues a message
4. User calls the help desk, who is unaware that someone is 
    working on this program.
5. Original programmer realises he's made a mistake, fixes
    the code and compiles it in the wrong (higher) library.
6. Help desk goes nuts before they realise that the running
    program is lower in *LIBL than they think.

Then there is the hyper-secure installation that refuses to use the library
list because a hacker can place "their" version in a library above the
"real" one.  

Buck Calabro
Aptis; Albany, NY
mailto:Buck.Calabro@aptissoftware.com

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---