Re: QSYSOPR message queue segregation

Hi Al Mac -

>You might have some variants ... if this that team library is 
>in *:LIBL then send not to QTESTPLACE but to QTHATEAM or perhaps 
>both

>If you come up with a system, you then apply it to your programming 
>standards for all future development, and let us know so we can do 
>something similar.

I did this very recently on our system.  Right now we are on our own AS/400,
but soon we will be losing it (sob!) and running on a shared AS/400 at
corporate.  We are going to have to change our library names, of which there
was a lot of hard-coding.  Besides breaking the software when changing the
library names, it also meant that there were a lot of jobs that we couldn't
safely run in our test environment because it would access production
libraries.

I created a command called RTVAPPA (ReTrieVe APPlication Attributes) which
returns the names of the main, end-of-day, and end-of-month database library
names for the current environment, a flag indicating if it is a production
environment or a test environment, an operator message queue name, and a
programmer message queue name.  In a production environment, the operator
message queue name returned is QSYSOPR.  In a test environment, the operator
message queue name returned is the same as the programmer message queue.

I went through all of the programs and removed all hard-coded library names,
using names from RTVAPPA in cases where I had to have a specific library
name.  I also changed SNDMSG, SNDPGMMSG, and SNDUSRMSG commands to use
message queue names from RTVAPPA (except that my messages relating to the
tape drive are still deliberately hard-coded to QSYSOPR).

BUT .. this only affects messages that programs deliberately send.  Program
halt messages from batch jobs still go to QSYSOPR and there is no way to
change that behavior.

Ken
Southern Wine and Spirits of Nevada, Inc.
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.

+---
| 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
+---