There is nothing wrong with CL8''.
I guess &RQS has a value.
//Mikael
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Windt, W.K.F. van der (Fred)
Sent: den 20 april 2020 08:24
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: CL8''
Hi,
Does anybody know why this happens
> Does anybody know why this happens:
Not without showing us the macro definition and the macro call.
> I expected CL8'' to generate 8 spaces as well
It does.
> The source code is
> DCCL8'&RQS'
That's not DC CL8''.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
_
If I assemble this (no variables at all):
FQMTEST RSECT
DCCL8''
DCCL8' '
END
I get this result:
Page3
Active Usings: None
R-Loc Object Code
The generated code is:DC CL8’’
The assembler is supposed to generate character spaces if a character-type DC
statement Has a null nominal value.
Keven
On Mon, Apr 20, 2020 at 2:22 AM -0500, wrote:
There is nothing wrong with CL8''.
I
Jus incase somebody is wondering about settings:
No Overriding ASMAOPT Parameters
No Overriding Parameters
No Process Statements
Options for this Assembly
NOADATA
ALIGN
ASA
BATCH
CODEPAGE(047C)
Look at your source code with a hex editor.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Windt, W.K.F. van der (Fred)
[0782fe4a8c02-dmarc-requ...@listserv.
Nothing strange in the source code:
FQMTEST + TO: E/E/RUS/FQ/AASM COLUMNS
1 00080
Command ===> Scroll
===> CSR
** * Top of Data
*
Looks like an HLASM bug. Try it without the CODEPAGE option.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List [ASSEMBLER-LIST@LISTSERV.UGA.EDU] on behalf
of Windt, W.K.F. van der (Fred)
[0782fe4a8c02-dmarc-
> Does anybody know why this happens:
>
> Active Usings: None
> R-Loc Object CodeAddr1 Addr2 Stmt Source Statement
> HLASM R6.0 2020/04/20 08.13
> 00 0A00404040401938 DCCL8''
> 08 40404040404040401939 DCCL8' '
This is a bug w
Thanks Jonathan,
I'll ask our support department to install this APAR.
Fred!
-Original Message-
From: IBM Mainframe Assembler List On Behalf
Of Jonathan Scott
Sent: maandag 20 april 2020 9:54
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: CL8''
> Does anybody know why this happens:
On 4/19/2020 11:24 PM, Windt, W.K.F. van der (Fred) wrote:
DCCL8'&RQS'
For such a case, I will always code:
DC CL8'&RQS. '
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/
--
On 2020-04-20, at 10:29:30, Ed Jaffe wrote:
>
> On 4/19/2020 11:24 PM, Windt, W.K.F. van der (Fred) wrote:
>> DCCL8'&RQS'
>
> For such a case, I will always code:
>
> DC CL8'&RQS. '
>
Does that truncate properly, but quietly if:
o &RQS is 8 bytes?
o &RQS is 9 bytes? (Should warn.)
Is the
On 4/20/2020 9:40 AM, Paul Gilmartin wrote:
For such a case, I will always code:
DC CL8'&RQS. '
Does that truncate properly, but quietly if:
o &RQS is 8 bytes?
o &RQS is 9 bytes? (Should warn.)
Your "should warn" above is an incorrect assertion.
DC CL8'12345678901234567890' is perfectl
On 2020-04-20, at 11:09:46, Ed Jaffe wrote:
>
> On 4/20/2020 9:40 AM, Paul Gilmartin wrote:
>>
>>> For such a case, I will always code:
>>>
>>> DC CL8'&RQS. '
>>>
>> Does that truncate properly, but quietly if:
>> o &RQS is 8 bytes?
>> o &RQS is 9 bytes? (Should warn.)
>
> Your "should warn"
On 4/20/2020 9:40 AM, Paul Gilmartin wrote:
>> For such a case, I will always code:
>>
>> DC CL8'&RQS. '
>>
> Does that truncate properly, but quietly if:
> o &RQS is 8 bytes?
> o &RQS is 9 bytes? (Should warn.)
That's correct, with a warning only if FLAG(TRUNC) is enabled.
Edward E Jaffe writes:
On 2020-04-20, at 14:05:06, Jonathan Scott wrote:
>
> On 4/20/2020 9:40 AM, Paul Gilmartin wrote:
>>> For such a case, I will always code:
>>>
>>> DC CL8'&RQS. '
>>>
>> Does that truncate properly, but quietly if:
>> o &RQS is 8 bytes?
>> o &RQS is 9 bytes? (Should warn.)
> That's correct, with
On 2020-04-21 02:29, Ed Jaffe wrote:
On 4/19/2020 11:24 PM, Windt, W.K.F. van der (Fred) wrote:
DCCL8'&RQS'
For such a case, I will always code:
DC CL8'&RQS. '
Why not just apply the bug fix?
On 2020-04-20, at 18:31:19, robi...@dodo.com.au wrote:
>
> On 2020-04-21 02:29, Ed Jaffe wrote:
>> On 4/19/2020 11:24 PM, Windt, W.K.F. van der (Fred) wrote:
>>> DCCL8'&RQS'
>> For such a case, I will always code:
>> DC CL8'&RQS. '
>
> Why not just apply the bug fix?
>
Possible need to supp
On 2020-04-21 11:44, Paul Gilmartin wrote:
On 2020-04-20, at 18:31:19, robi...@dodo.com.au wrote:
On 2020-04-21 02:29, Ed Jaffe wrote:
On 4/19/2020 11:24 PM, Windt, W.K.F. van der (Fred) wrote:
DCCL8'&RQS'
For such a case, I will always code:
DC CL8'&RQS. '
Why not just apply the bug f
I think the fix for APAR PH08424 is the one that corrects this issue.
The fix for APAR PH06572 addressed an issue with truncation of constants and
introduced the padding issue being discussed here.
Keven
On Mon, Apr 20, 2020 at 8:45
20 matches
Mail list logo
