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



ILE RPG for AS/400 Reference Appendix A. RPG Restrictions show maximum character fields as follows:

V4R2: 32767 bytes
http://publib.boulder.ibm.com/pubs/pdfs/as400/V4R2PDF/qb3agz00.pdf

V4R4: 65535 bytes
http://publib.boulder.ibm.com/pubs/pdfs/as400/V4R4PDF/QB3AGZ03.PDF

Clearly, 65535 byte character fields were fully documented in V4R4.

I would trust Barbara Morris when she says 65535 character fields were PTFd to V4R2, but that's a moot point for you since you are interested only in V4R5 and later.

I compiled the following on a V5R2 machine with target release V4R5M0. It ran correctly on the V5R2 machine (I don't have a V4R5M0 machine to test on).

H dftactgrp(*NO) actgrp(*new) option(*srcstmt : *nodebugio)
D big             s          65535    varying
C                   eval      big = *all'X'
C                   eval      *inlr = *on
C                   return

Regards,

Mel Rothman
Mel Rothman, Inc.



Brad Stone wrote:
I happened to stumble across a message on
comp.sys.ibm.as400.misc from Barbara Morris where she said
that the max size string RPG can handle has been 64k since
V4R2 (with PTF for early versions), but the compiler and
syntax checker wasn't updated that soon.

Now, I believe its V5R1 where this size was announced.  So,
my question is this.

I create an app on  a V5Rxx machine and use 64k strings.
 If I move that app to a V4R5 machine, will it function
properly?  Or I will I run into "unpredictable results"?

Brad
--



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.