Zero-length strings are only supported for initial values.
A field cannot have zero length, so if the initial value is
an empty string, there must be an explicit length.
> On 2020-04-21, at 01:53:11, Jonathan Scott wrote:
> >
> > Support for zero-length strings was added in HLASM 1.3 in around
>
On 2020-04-21, at 01:53:11, Jonathan Scott wrote:
>
> Support for zero-length strings was added in HLASM 1.3 in around
> 1998, but it was common for a long time after that to include a
> trailing space on an initial value just in case that release had
> not yet been installed.
>
I generally
Support for zero-length strings was added in HLASM 1.3 in around
1998, but it was common for a long time after that to include a
trailing space on an initial value just in case that release had
not yet been installed.
On Mon, Apr 20, 2020 at 8:45 PM -0500, "Paul Gilmartin" wrote:
> Hmmm. HLASM
:45 PM -0500, "Paul Gilmartin"
<0014e0e4a59b-dmarc-requ...@listserv.uga.edu> 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:
>>&
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''
For such a case, I will always code:
DC CL8' '
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''
>> For such a case, I will always code:
>> DC CL8' '
>
> Why not just apply th
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''
For such a case, I will always code:
DC CL8' '
Why not just apply the bug fix?
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' '
>>>
>> Does that truncate properly, but quietly if:
>> o is 8 bytes?
>> o
On 4/20/2020 9:40 AM, Paul Gilmartin wrote:
>> For such a case, I will always code:
>>
>> DC CL8' '
>>
> Does that truncate properly, but quietly if:
> o is 8 bytes?
> o is 9 bytes? (Should warn.)
That's correct, with a warning only if FLAG(TRUNC) is enable
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' '
>>>
>> Does that truncate properly, but quietly if:
>> o is 8 bytes?
>
On 4/20/2020 9:40 AM, Paul Gilmartin wrote:
For such a case, I will always code:
DC CL8' '
Does that truncate properly, but quietly if:
o is 8 bytes?
o is 9 bytes? (Should warn.)
Your "should warn" above is an incorrect assertion.
DC CL8'12345678901234567890' is perfe
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''
>
> For such a case, I will always code:
>
> DC CL8' '
>
Does that truncate properly, but quietly if:
o is 8 bytes?
o is 9 bytes? (Should w
On 4/19/2020 11:24 PM, Windt, W.K.F. van der (Fred) wrote:
DCCL8''
For such a case, I will always code:
DC CL8' '
--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com
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 happ
> 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 4040404040404040 1939 DC
-requ...@listserv.uga.edu]
Sent: Monday, April 20, 2020 3:38 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: CL8''
Nothing strange in the source code:
FQMTEST + TO: E/E/RUS/FQ/AASM COLUMNS
1 00080
Command
02 DC CL8''
4CCCDF77
043338DD
--
...@listserv.uga.edu]
Sent: Monday, April 20, 2020 3:32 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: CL8''
If I assemble this (no variables at all):
FQMTEST RSECT
DCCL8''
DCCL8' '
END
I get this result
: CL8''
If I assemble this (no variables at all):
FQMTEST RSECT
DCCL8''
DCCL8' '
END
I get this result:
Page3
Active Usings: None
R-Loc Object
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
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
> 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''
That's not DC CL8''.
--
Shmuel (Seymour J.) Metz
http://mason.gmu
There is nothing wrong with CL8''.
I guess 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
Hi,
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 DC
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Subject: AW: ** ASMA030E Invalid literal usage - =CL8'MARTINWH'
On Thu, Jul 12, 2012 at 3:58 PM, Peter Relson rel...@us.ibm.com wrote:
I hope that any usage of LPP is solely for theoretical /
experimental purposes. It is not intended for use outside
I hope that any usage of LPP is solely for theoretical / experimental
purposes. It is not intended for use outside of the operating system,
which is presumably part of the reason that it is not in the principles of
operation.
Peter Relson
z/OS Core Technology Design
I am out of the office until Monday 7/16//2012. I will read your note, as time
permits, when I return to the office. If your e-mail is urgent and concerns a
production issue/problem, please send your note to the 'GLO-RETS zOS Content'
mailbox for attention.
Thanks!
On Thu, Jul 12, 2012 at 3:58 PM, Peter Relson rel...@us.ibm.com wrote:
I hope that any usage of LPP is solely for theoretical / experimental
purposes. It is not intended for use outside of the operating system,
which is presumably part of the reason that it is not in the principles of
On Jul 12, 2012, at 08:24, Rob van der Heij wrote:
On Thu, Jul 12, 2012 at 3:58 PM, Peter Relson rel...@us.ibm.com wrote:
I hope that any usage of LPP is solely for theoretical / experimental
purposes. It is not intended for use outside of the operating system,
which is presumably part of
-Original Message-
From: IBM Mainframe Assembler List
[mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Paul Gilmartin
Sent: Thursday, July 12, 2012 10:59 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Subject: AW: ** ASMA030E Invalid literal usage -
=CL8'MARTINWH'
snip
On 2012-07-12 16:33, Edward Jaffe wrote:
On 7/12/2012 9:56 AM, McKown, John wrote:
Which is totally simplistic these days. You bought your cell phone, right? Do
you really think that you can do anything to it that you want to? And that it
is totally documented? In today's IP is __mine__ world,
Maybe there's hope:
http://www.mozilla.org/en-US/b2g/
--
Regards, Gord Tomlin
Action Software International
(a division of Mazda Computer Corporation)
Tel: (905) 470-7113, Fax: (905) 470-6507
On 2012-07-12 19:28, Paul Gilmartin wrote:
On 2012-07-12 16:33, Edward Jaffe wrote:
On 7/12/2012
http://www-01.ibm.com/support/docview.wss?uid=isg1PK87960
From: Walt Farrell walt.farr...@gmail.com
To: ASSEMBLER-LIST@listserv.uga.edu
Date: 07/02/2012 07:44 AM
Subject:Re: ** ASMA030E Invalid literal usage - =CL8'MARTINWH'
Sent by:IBM Mainframe Assembler List ASSEMBLER
Walt,
Where are the LPP described? I don't see them in the
latest PoPs (-08) that I have.
David Stokes posted the link to the documentation of these
instructions.
I haven't checked them en detail- they look like the ones I am using
...and HIS instructions
HIS is hardware
When I compile this
LPP =CL8'MARTINWH' leave a trace that we were here
I get this:
** ASMA030E Invalid literal usage - =CL8'MARTINWH'
Why- There is absolutly no restriction of what can be placed in the
program parameter.
My HLASM is:(PTF UK70680) HLASM R6.0
--
Martin
On Sun, 1 Jul 2012 15:44:53 +0200 Martin Truebner mar...@pi-sysprog.de
wrote:
:When I compile this
: LPP =CL8'MARTINWH' leave a trace that we were here
:I get this:
:** ASMA030E Invalid literal usage - =CL8'MARTINWH'
:Why- There is absolutly no restriction of what can be placed
I don't see LPP in the POP manual. Is it an instruction or a macro? If it's a
macro, then maybe there is an option to get around this error message.
Jon Perryman.
From: Martin Truebner mar...@pi-sysprog.de
When I compile this
LPP =CL8'MARTINWH
Betreff: Re: ** ASMA030E Invalid literal usage - =CL8'MARTINWH'
I don't see LPP in the POP manual. Is it an instruction or a macro? If it's a
macro, then maybe there is an option to get around this error message.
Jon Perryman.
From: Martin Truebner mar...@pi
shipped would be
greatly increased if some customer actually reported the problem
to IBM through normal service channels.
Jonathan Scott
IBM Hursley, UK
When I compile this
LPP =CL8'MARTINWH' leave a trace that we were here
I get this:
** ASMA030E Invalid literal usage - =CL8
On Jul 1, 2012, at 11:35, Jonathan Scott wrote:
Ref: Your note of Sun, 1 Jul 2012 15:44:53 +0200
HLASM does not allow literals unless the relevant instruction
operand in the opcode table is marked to say that a literal is
allowed.
Why? An address expression should be an address
? If it's a
macro, then maybe there is an option to get around this error message.
Jon Perryman.
From: Martin Truebner mar...@pi-sysprog.de
When I compile this
LPP =CL8'MARTINWH' leave a trace that we were here
I get this:
** ASMA030E
Scott,
... maybe the usage of the LPP instruction is not so common ...
You hit the nail rite into the camels back (or so).
z/OS gives you HIS (which covers all aspects and circumstances that LPP
might/can/is usefull to be used) - z/LINUX uses (most of the time) a
different assembler
So
42 matches
Mail list logo
