At 11:07 AM 12/5/97 -0500, you wrote:
>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?

Have you tried TGTRLS on the CRTCLPGM command?

We compile all our programs to the earliest release needed. This limits us
somewhat, but that's the cost of having multiple releases, I guess.


Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN 55401
(612) 371-1111 x480

| 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

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].