Re: Re[2]: SAVOBJ to previous release

[Vern Hamberg <hambergv@xxxxxxxxxxxxxx>]

Buck

At 10:16 AM 12/8/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.
>-snip-
>>>Now, if I take the source code to the target machine, it compiles
>>>and executes just fine.
>-snip
>>>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,
>       Yes, that works, but our developers won't be too happy
>having to override all their compiles; especially when the CL
>program doesn't use any "new" functionality!
>
>Do you have any idea why SAVOBJ TGTRLS() works
>differently than CRTCLPGM TGTRLS()?

As far as the CRTxxxPGM commands, create dupes of the various commands in a
library that'll reside above QSYS in the system portion. Then use CHGCMDDFT
CRTCLPGM 'TGTRLS(V3R2M0)' to set the TGTRLS for all creates. Do the same
for all CRTxxxPGM and CRTxxxMOD and CRTBNDxxx commands.

Save files have different formats at different release levels, apparently.
Target release for programs has no relationship to that for save files. You
can save v3r7 programs, e.g., to a v3r2 save file, but you won't be able to
restore them to a v3r2 machine.

Cheers

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