|
works fine until you purchase another application from another vendor with the same brilliant idea (and the same prefix). The point is, that the only reliable way is to have the top program in the application figure out where it is running from, and then pass that info down to all its subprograms (passing it to their subprograms, etc). Everybody down the line now qualify their calls (and all other references to files, data areas, etc) with the library name passed down. Should you run into a name conflict with the top name, you simply rename it (and only it) to your liking. ----- Original Message ----- From: <dgallagher@deloitte.ca> To: <midrange-l@midrange.com> Sent: Wednesday, September 29, 1999 7:53 PM Subject: Determining what library a CL program is called from? > That would explain the practice (a good practice, it seems) I've seen in > some > shops - in-house commands are prefixed with a letter that is not generally > seen > at the beginning of ibm commands. For example, the RUNSQLSTM would be called > ZRUNSQLSTM or XRUNSQLSTM. That way they are never confused with ibm > commands. In > addition, it makes them easy to find on the system - they're always together > (all Z or all X). > > Debbie Gallagher > > ******************** > Original message > ******************** > <snip> under what circumstances one might want two programs in the library > list > and actually want to be executing the one lower in the list? <snip> > > 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. > +--- > | 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 > +--- > +--- | 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 +---
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.