Re: CL type conversion error

I don't see why you'd get blanks in &RC....

However, adding 240 is a kludge and will only work for single-digit return codes. It's completely unneeded here, because your CHGVAR will convert from numeric to character. You don't need to muck around with calculating what the EBCDIC code would be.


John McKee wrote:

This is so dumb. I have done type conversions in CL before and not encountered
this. First time with CLLE, though.

Given this:

DCL VAR(&RETURNCODE) TYPE(*DEC) LEN(5 0)
DCL VAR(&RC) TYPE(*CHAR) LEN(5)
.
.
.
CHGVAR VAR(&RETURNCODE) +
VALUE(%BIN(&MSGDTA 1 4))
CHGVAR VAR(&RETURNCODE) +
VALUE(&RETURNCODE + 240)
CHGVAR VAR(&RC) VALUE(&RETURNCODE)


A DMPCLPGM produces this for the two variables:

&RC *CHAR 5 ' '
&RETURNCODE *DEC 5 0 0

The HEX code for &RC is 4040404040
There is no HEX code for &RETURNCODE

I am trying to get the return code from a QSH session into a printable form, for
a message. From previous attempts, I learned that in order to compare
&RETURNCODE to a numeric zero, I had to add 240, to make it F0. That works
now. But, why is &RC still blanks?

Thanks for the extra eyes.

John McKee