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


  1.  Home
  2. RPG400-L
  3. March 2005

Re: Making sense of 4-byte binary fields

> All RPG fields (except float) are declared
> according to the number of digits
> that fit in them.

Only true if you use the size notation.  If you use positional
notation (e.g. '1  4b 0') then you specify the size as a number of
bytes.  At issue is backward compatibility.  Believe it or not, I
recently compiled a program from System/3 RPG.  It has program
described files using positional notation (obviously).  The main
change was DISK44 to DISK.  The point is that we still have positional
notation for backward compatibility's sake.

IBM _could_ have chosen some different mechanism to represent integers
and then people would be complaining that there are THREE ways to
define a number (position, length and the new one.)

For the original poster, the FAQ has some help in this regard, as well
as a link to an excellent page describing how to convert from C data
types to RPG IV data types by the esteemed Barbara Morris.
http://faq.midrange.com
  --buck

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.