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



On Wed, 2014-10-15 at 13:57 +0000, Gary Thompson wrote:
V7R1
I have a question about how binary fields can/should be defined in RPGLE.

Starting with a good example from a post on CODE 400 by Jamief > Thank You! <
I was able to quickly use QUSCRTUS to create a user space.

As I developed the program I made changes, and, at a point, the program failed
to create the user space, with the job log showing:

CPF3C2C: Value 268435456 for size parameter is not valid.

The change that caused this was changing the size parameter for QUSCRTDS
from a DS to a stand-alone field:

d DS
d ds_IniSiz 1 4B 0 Initial Size bytes

D wk_IniSiz S 4B 0 Initial Size bytes

I use EVAL to set both field wk_IniSiz and ds_IniSiz = 4096.

Apparently, the difference between the two D Specs changes the value received by the API ?

With ds_IniSiz, the user space is successfully created.

With wk_IniSiz, the user space is not created and I get the 'Value 268435456' message in the job log.

Yet an EVAL of either field in debug returns 4096 ?

With the second instance, the field becomes a packed decimal format
equivalent to 4B, this PD is then passed to the called program and as
such is misaligned/defined.

I think you need I or U (Can't remember the exact "type", or length)...
an unsigned integer if I recall correctly, which is then passed as a
binary format numerical.



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.