Re: Re[2]: SAVOBJ to previous release

["Al Barsa, Jr." <barsa2@xxxxxxx>]

At 06:17 PM 12/8/97 -0500, you wrote:
>> Sending the source is not a good option for us.  We're looking to package
>> an entire library for the end-user to RSTOBJ to their system: load 'n go.
>> If they have to compile all the CL source, that'd be a bit messy.
>
>> We *could* compile to the earliest release we support, but the
>> developers won't be happy having to override all their CL compiles
>> for the sake of the few that don't SAVOBJ properly.

We have a program that we run whenever we put on a new release.  It creates
a library called QSYSCHANGE which sits on top of QSYSLIBL with our changed
command defaults.

It creates another library, QSYSPRVCMD,  that is designed for developers
who specifically develop code for prior releases.  It duplicates every
command containing a TGTRLS parameter and changes that parameter to
TGTRLS(*PRV).  The library is AUT(*USE).  We then have a command that puts
this library on the top of QSYSLIBL using the CHGSYSLIBL command (the CPP
needs to adopt).  The philosophy seems to work perfectly.

Al



Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:  914-251-9400
Fax:    914-251-9406





Private mail should be sent to barsa@ibm.net
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@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
+---