Re[2]: SAVOBJ to previous release

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

>> We're distributing objects to systems at previous release
>> levels.  What we do is SAVOBJ xxx TGTRLS(V3R2M0) from our
>> V4R1M0 machine.  This works fine except for some CL programs.

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

>  It sounds like your programs is using functions that are in the new
>OS, but may not be able to be performed in a previous version. Since you
>are saving your objects for a previous release, why not create them that
>way as well. When you compile the program, all you need to do is
>specifiy TGTRLS(v3R2M0).

Alas, we're NOT using any new function; that's what's so wierd.
The same source will recompile and execute just fine on the
earlier release machine.  That's what's annoying the developers:
the fact that 
a) Sending the source, compiling it on the early release works,
b) CRTCLPGM TGTRLS() works, but
c) SAVOBJ TGTRLS() doesn't.

Their question to me was "Why doesn't SAVOBJ work for these
programs, when clearly, they work as-is on the earlier release?"
They really didn't like the idea of having to override all their
CL compiles, but if that's what it takes...

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