Something interesting/confusing I noticed today.
The HLASM Language Reference documents the continuation column as 16.
For an instruction this works:
L R10,4(,R1)comment x
<'x' in column 72>
continued here
For a macro:
SAVE (14
The "fit" part of "conniption fit" is actually redundant.
The definition of 'conniption' reads:
" a fit of rage or hysterics."
Example sentence:
"The casting choice gave the writers a conniption."
(I did not know this either until I looked up the definition of "conniption".)
Which z/os library are these IARBRVER, IARBRVEA, and IARBRVKA macros shipped
in? I don't see them in MACLIB or MODGEN. But they are documented in the z/os
2.5 MVS Programming: Authorized
Assembler Services Reference, Volume 2
(EDT-IXG)
Thank you.
Yes thank you very much this worked:
&WHATSETC 'C''R'''
&WHAT_MNOTE SETC DOUBLE('&WHAT')
MNOTE *,'&&WHAT = &WHAT_MNOTE'
generates the MNOTE:
2111+*,&WHAT = C'R'
Hello:
I have a macro that does this:
&WHATSETC 'C''R'''
The &WHAT is later used in a MVI FIELD,&WHAT instruction and correctly
assembles as MVI FIELD,C'R'
All good.
I am trying to use the &WHAT in a MNOTE like this:
MNOTE *,'&&WHAT = &WHAT'
However this generates
MNOTE *,'&&WHAT
"Others may have very different views; but theirs are, of course,
wrongheaded."
Very similar to "I will respect your opinion no matter how wrong it is."
It needs to be remembered that Mr. Gilmore 'left' this list several years
ago under this same sort of pretense, but surfaced again not-too-long later.
So we only have to wait him out.
Thank you.
Hello:
Suppose I have a macro like this:
MACRO123 FUNC=ABCD,AREA=XYZ
In my program I code it like this:
MACRO123 FUNC=ABCD,AREA=XYZ
Later in the program, I code it like this:
MACRO123 FUNC=EFGH,AREA=XYZ
How can I enforce the requirement that the AREA=parameter is
coded the same in both invo
On Tue, 31 Aug 2010 09:57:02 -0700, Edward Jaffe
wrote:
> On 8/31/2010 9:26 AM, paul schuster wrote:
>>
>> Let me re-ask the question then:
>>
>> have you written ADATA output to a PDS or PDSE member that has more than say
>> 64K records?
>
>I just found a
On Tue, 31 Aug 2010 01:41:25 -0400, Gerhard Postpischil
wrote:
>On 8/31/2010 1:25 AM, paul schuster wrote:
>> Is there a limitation on how many ADATA records can be written? For
>> example, when I define the ADATA file as a PDSE, and the number of records
>> must excee
Hi:
Is there a limitation on how many ADATA records can be written? For
example, when I define the ADATA file as a PDSE, and the number of records
must exceed the 64K PDSE member limit, the assembly fails and I get this
message:
IEC036I 002-AC,IGC0005E,jobname,procname,ADATA,ucb@,volser,adatadsn
On Mon, 2 Aug 2010 14:31:13 -0700, John R. Ehrman (408-463-3543 T/543-)
wrote:
>Specify SECTALGN(16). You'll get a warning message about quad
>alignment, but that's necessary for CMS and VSE users whose
>loaders/linkers don't (yet, anyway) support quad alignments.
>On z/OS, the generated object i
So how can you get QUADWORD alginment?
Trying
QWALGIN DS0LQ
generates this message:
ASMA500E Requested alignment exceeds section alignment
which seems to imply you need to do SECTLALGN(16), but this in turn
requries option GOFF which is not an option.
Thank you.
13 matches
Mail list logo
