At 08:37 PM 12/7/97 -0500, you wrote:
>I am pretty sure that once an object is on V4R1 it should be able to be
>saved once again for release V3R7 , though What cannot be done is going
>from Release V4r1 back to V3R2. 

For once, and for all, let's put this issue to rest.  There are three
things required to be able to save an object to a previous release.

1.      The object type must be supported in the previous release.  If an object
is first created in release 'n', you cannot save it to release 'n-1'.

2.      Certain type of objects need to be created so that they can be restored
to a prior release.  These objects are *PGM, *MOD and *SRVPGM.  The way to
specify this is using the TGTRLS parameter.  (Examples of TGTRLS follow.)
You cannot create any program (for example) using TGTRLS(*PRV).  For
example, if a CL command exists in release 'n', but not in release 'n-1',
it will not compile for the prior release, and the compile will blow up
with an escape message (CPF0815, I think, but my 400 is not up currently to
check).

3.      If all objects that need to be created using the TGTRLS parameter were
created properly, then the SAVxxx command must also specify the TGTRLS
parameter.  
The original plans for TGTRLS was that it would only support *CURRENT (the
default for all commands where this parameter appears), and (*PRV).  Then
the folks in Rochester got cute, and decided to have 'point' releases, more
frequent releases, go to RISC, and ultimately have the V3R1 fiasco; so the
acceptable values got expanded.  As far as I can determine, here are the
acceptable values (do not assume that this list is gospel, it's based on my
memory [which has been sometimes been known to page fault]):

Current *PRV            Other Acceptable Values
Release Release
V4R1M0          V3R7M0          V3R7M0  V3R6M0  V3R2M0  V3R1M0
V3R7M0          V3R6M0          V3R6M0  V3R2M0  V3R1M0  V3R0M5          
V3R6M0          V3R1M0          V3R1M0  V3R0M5  V2R3M0
V3M2M0          V3R1M0          V3R1M0  V3R0M5  V2R3M0                  
V3R1M0          V2R3M0          V3R0M5  V2R3M0
V3R0M5          V2R3M0          V2R3M0  V2R2M0

I hope this helps.

Al



Al Barsa, Jr. - Account for Midrange-L
Barsa Consulting, LLC.  
400 > 390

Phone:  914-251-9400
Fax:    914-251-9406





Private mail should be sent to barsa@ibm.net
+---
| 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 ...

Replies:

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