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


  • Subject: Re: Backward compatibility to V3R2
  • From: boldt@xxxxxxxxxx
  • Date: Thu, 29 Jun 2000 08:12:40 -0400



Colin wrote:
>I'm using RPG 400 at V3R7
>
>This supports fields names > 10,
>But when I try to compile to V3R2 the compile fails and I have to
>Reduce the lengths of the fields to 10.
>
>I thought that V3R2 & V3R7 were essentially the same, but for different
>processors (CISC/RISC)

No, the equivalent releases are V3R2 and V3R6.

>
>Is there anything I can do about this field length issue

No.

(Actually, yes there is something you can do - upgrade your
CISC boxes.)

>or must I change my
>pgms and Standards....

Yes.

>
>Also are there any other issues with backward compatibility to V3R2 that I
>should know about.

Look in the front of your V3R7 ILE RPG reference manual in
the section called "What's New This Release", and avoid
the enhancements listed.

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.