I am sorry for the typo, I was expecting (0,15),(2,8) and not (0,15),(8,2) long 0 long 15 long 2 long 8
I ran it in z/OS which should default to normal numbers so all classic LE languages would understand it correctly 19819478 | 00 00 00 00 00 00 00 00 00 00 00 0F 00 00 00 00 | 19819488 | 00 00 00 02 00 00 00 00 00 00 00 08 00 00 00 00 | However, your suggestion that "For whatever reason, each long seems to be ordered as low order word followed by high order word." seems to answer the issue. If you are correct, then, the library provides an integer and a filler of 4 bytes. This explanation seems to be reasonable. Could anybody who is more C savvy and proficient with the runtime library usage, point to any proof that this is indeed the answer? Thanks ZA ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
