× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



V5R1 does suport V4R4 as a target release. If you use the new Bif, your code 
will not be portable to the V4R4 machine. We have a similar situation in my 
company (about 40 AS/400 that share the same software). What we did is change 
the default valut of the TRGRLS parameter of all CRT* command to V4R2. You 
could do something similar.

Denis Robitaille
Directeur services techniques
Cascades Inc
819 363 5187
fax 819 363 5177


>>> CyndiB@IHFA.ORG 10/31/01 05:59pm >>>
All,
I'm having a brain freeze. We are currently on a Mod730 with V4R4. Our old
Mod510 with V4R4 is stored in another city as a D/R box. We would like to go
to V5R1 on the 730, but - what gotchas will come along if we try to restore
UserPrf & User Libs to the 510 ?  Does V5 support V4R4 as a Target Release
for the CRTXXXPGM Commands ?  What about using the new bifs in V5 ?
I don't want to be locked into V4R4 just because it costs $10K to bring the
510 up to snuff.
TIA,
Cyndi B.
Boise, ID
_______________________________________________
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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.