That did it. The combination of changing to *SYS naming and using a cl:
command to add the production library is getting me exactly what I need.
I can take scripts straight from programs and test and tweak them.
Thanks Vern and Buck.
Senior Programmer Analyst
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Sent: Tuesday, December 22, 2015 12:27 PM
To: Midrange Systems Technical Discussion
Subject: Re: ACS Run SQL Scripts library list.
I've not worked too much here yet, so consider that when your read this.
The Run SQL Scripts in the classic Access has help text - I believe
there must be something similar here.
There's a setting, I believe, to use *LIBL in there - it might depend on
the naming, where *SQL or *SYS - so dig around for help in the product.
On 12/22/2015 11:24 AM, Kevin Bucknum wrote:
I downloaded the 1.1.5 version of ACS to play around with the new Run
SQL Scripts. Is there a way to easily add a library to your library
list? Our environment loads many libraries via the QUSRLIBL setting
that hold common data. We then add a client specific library that
holds data that is specific to the client. Do I have to put all the
libraries that I want to search in the Schema list, or is there some
way to let it use the QUSRLIBL setting and just add the one client
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l