Re: SAVOBJ to previous release

[Pete Massiello <pmassiello@xxxxxxxxxxxxxxxx>]

Buck Calabro wrote:
> 
> Hi!
> 
> 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.
> 
> Specifically, I have a CL program that has only a RUNSQLSTM
> in it.  When I do my SAVOBJ, I get:
> 
> Message ID:   CPD6427
> Object CRT_PROC type *PGM cannot be saved for the specified
> target release.
> 
> Cause: Object CRT_PROC type *PGM is not compatible with the
> specified target release.  The earliest release for which
> this object can be saved is V3R7M0.
> 
> Recovery: Create the object again, specifying a target release
> compatible with the operating system release for the system
> where the object is to be restored.
> 
> 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?
> 
> Buck Calabro
> Commsoft, Albany, NY
Buck,

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

HTH

-- 
Pete Massiello
OS Solutions International 
Phone: (203)-744-7854  Ext 11.
http://www.os-solutions.com
mailto:pmassiello@os-solutions.com
+---
| 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
+---