The ISDEC() problem in HLASM I mentioned before is PMR 13359 now.
(There seems to be a related APAR already: PK15306.)
Thomas Berg
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED]
When trying to use the new HLASM function ISDEC I found it causing the asm step
to (apparently) loop. (NOTE! It's the assemblation step that loops. I'm NOT
trying to execute the module.)
The test program:
TEST2CSECT
TEST2AMODE31
TEST2RMODEANY
USING *,12
BRU
Thomas,
Stick an MNOTE before and after to make sure that you are looping when HLASM
is processing the ISDEC function.
If so, it's PMR time...
Later,
Ray
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Berg
> Sent: Thursday No
n: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Ray Mullins
Skickat: den 10 november 2005 18:03
Till: IBM-MAIN@BAMA.UA.EDU
Ämne: Re: ISDEC do the loop...
Thomas,
Stick an MNOTE before and after to make sure that you are l
That's not good...
I'd call IBM and open a PMR. Good luck!
Best regards,
Ray
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Berg
> Sent: Thursday November 10 2005 11:05
*snip*
> ... I get only this in the //SYSPRINT output
Thats intersting.
I took your source and my assemble step gets an S0C1 abend immediately.
I have up to PUT 0510 maintenance on the assembler.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [E
> I found it causing the asm step to (apparently) loop.
Check your JCL. Just by chance, is the TEST2 source in a member
called "DECTEST2", and is the source library also in the SYSLIB
concatenation? In other words, could you be calling your own macro
recursively?
-
Nope - see my other reply with JCL etc.
-Ursprungligt meddelande-
Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Martin Kline
Skickat: den 10 november 2005 19:20
Till: IBM-MAIN@BAMA.UA.EDU
Ämne: Re: ASM: ISDEC do the loop...
> I found it causing the asm step
> &XDECSETB (ISDEC(123))
ISDEC expects a character string. For example:
&XDECSETB ISDEC('123')
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET I
Sorry if this is a duplicate message. I couldn't find where my first
attempt was even acknowledged.
ISDEC expects to be given a string, not a number. For example:
&XDECSETB (ISDEC('123')) * Should return 1
--
For IBM
sion List [mailto:[EMAIL PROTECTED] För Martin Kline
Skickat: den 10 november 2005 20:37
Till: IBM-MAIN@BAMA.UA.EDU
Ämne: Re: ASM: ISDEC do the loop...
Sorry if this is a duplicate message. I couldn't find where my first attempt
was even acknowledged.
ISDEC expects to be given a str
MACRO
DECTEST2
.*---
&XDECSETB (ISDEC('123'))
MEND
Don't you have to declare &XDEC with a LCLB or GBLB instruction?
--
For IBM-MAIN subscribe / si
No, and not for a very long time. It is contextually declared by its
appearance in a SETB statement.
John Gilmore
Ashland, MA 01721-1817
USA
From: Martin Kline <[EMAIL PROTECTED]>
Reply-To: IBM Mainframe Discussion List
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: ASM: ISDEC do the loop..
13 matches
Mail list logo