Re[2]: SAVOBJ to previous release

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

><SNIP>
>
>> Now, if I take the source code to the target machine, it compiles
>> and executes just fine.  I also get this problem with other CL
>> programs (mainly ones that use RTVJOBA and RTVSYSVAL).  In all
>> cases, the CL compiles just fine on the target, but the object
>> cannot be SAVOBJ'd.
>>
>> How are you folks handling this?  Do you really keep a separate
>> library for each OS level you want to deploy to?

>We build a library of objects to be distributed (including source), then
>recompile to target release.  This also finds prior release incompatibilities.
>Then after distribution, we compile on the machine which will execute the code
>(sort of like wearing a belt with your suspenders)

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.

Buck Calabro
Commsoft

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