Re: New Opcodes - %SETCELL

John,

Please forgive this post, I know it has nothing to do with the main
thrust of your message.

However, these numbers aren't that cryptic to me.... Although I'm
a little curious as to why you're using integers here instead of
named constants (do you plan to change them?)

The parameter that you're sending to open() (the "oflag" parm) is
looked at as a string of bits, each bit specifying a capability.
Theres a O_CODEPAGE bit, a O_TEXTDATA bit, O_CREAT bit, etc.

If you look at a binary representation of this parameter, as its
stored in memory, you'll see that each time you add another one of
the O_xxx flags, you're turning on a bit.

i.e.,               100000000000000000000000 (8388608 in binary)
                 + 1000000000000000000000000 (16777216 in binary)
                  --------------------------
                   1100000000000000000000000 (both flags turned on)


Makes perfect sense to me...



John P Carr <jpcarr@tredegar.com> wrote:
>
> Look at these,
>
>  D     O_CODEPAGE      S             10I 0 INZ(8388608)
>  D     O_TEXTDATA      S             10I 0 INZ(16777216)
>
> Does anyone know why the CODEPAGE is that number?
> No, and you won't see aaaaaaannnnnyyyyyy
> documentation anywhere of what the valid numbers
> are, or why they are those numbers??  Its a
> "Trust me they work,  don't miss key them"
+---
| 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
+---