RE: how to create unsigned hexadecimal initial value

I concur with your conclusion.  Based on what I have seen for the
experiments that you and Gene have done, X' looks a lot more predictable to
me.  It might be interesting to figure out where the H' came from and who
uses it.  Can any bugs be traced back to it challenging nature?

Richard Jackson
mailto:richardjackson@richardjackson.net
http://www.richardjacksonltd.com
Voice: 1 (303) 808-8058
Fax:   1 (303) 663-4325

-----Original Message-----
From: owner-mi400@midrange.com [mailto:owner-mi400@midrange.com]On
Behalf Of Leif Svalgaard
Sent: Friday, August 25, 2000 12:28 PM
To: MI400@midrange.com
Subject: Re: how to create unsigned hexadecimal initial value


> From: <rjd@us.ibm.com>
> To: <MI400@midrange.com>
> Sent: Friday, August 25, 2000 9:50 AM
> Subject: Re: how to create unsigned hexadecimal initial value
>
>
> > Leif and others,
> >
> > Here's (my) better definition for H literals, which I think explains the
> > results seen in all of the examples brought forward so far.  I honestly
> > don't know if the PRM actually implements this definition, but it seems
to.
>

DCL DD NN BIN(2) INIT(H'8000')
Diagnostics
Initial value for data object too large.

DCL DD NN BIN(2) INIT(H'FFFF')
Diagnostics
Initial value for data object too large.

both are wrong, of course. This is closer to Gene's bug,
but different from the other bug I just reported.
Lesson:  H literals are buggy beasts, avoid them if possible.



+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---