RE: Target release behaving strangely on saves from V5R1

>From: Leif Svalgaard [mailto:leif@leif.org]
>Try to delete observability and see what you get.

CHGPGM RMVOBS(*ALL) changes it to V3R7M0. But to my original question, can I
actually move the program back that far? It might take a couple of steps
because of save restrictions, but could I go V5R1->V4R40->V3R2->V2R3 or
something like that?

-Walden

------------
Walden H Leverich III
President
Tech Software
(516)627-3800 x11
WaldenL@TechSoftInc.com
http://www.TechSoftInc.com



-----Original Message-----
From: Leif Svalgaard [mailto:leif@leif.org]
Sent: Monday, February 11, 2002 11:00
To: midrange-l@midrange.com
Subject: Re: Target release behaving strangely on saves from V5R1


From: Walden H. Leverich <WaldenL@TechSoftInc.com>
> Can someone verify something for me? I have V5R1. If I compile the
> PROOF member in QGPL/QRPGSRC and specify TGTRLS(*CURRENT) I get a
> program that says "Earliest release that program can run: V5R1M0" ok
> that makes sense. HOWEVER, if I specify either *PRV, V4R5M0 or V4R4M0
> (the only other
options)
> then the program object says "Earliest release that program can run:
V2R3M0"
> Yes, Version TWO Release THREE. Do other people see this? How far back
> can
I
> really move this object? Don't give me the book answer which I know is
V4R4,
> but what does practice say?

as long as you have OBSERVABILITY most programs can run as far back as
V1R3M0, so you must be doing something special in order to only get V2R3M0
:-).  Try to delete observability and see what you get.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.