At 18:11 -0400 on 06/03/2011, Farley, Peter x23353 wrote about Re:
Legal syntax for multiple-operand continued DC statemen:
Agreed, that is a reasonable solution. Thanks for the tip.
Peter
You're welcome. Since your requirement was for neatly formatted and
easily read/human-parsed input (not the layout of the actual
statements the assembler will use), I figured that thinking slightly
out-side-the-box via use of a macro would meet your needs. I leave
the design to you if you want to use this method (although I provided
some guidance).
-----Original Message-----
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-
[email protected]] On Behalf Of Robert A. Rosenberg
Sent: Friday, June 03, 2011 5:08 PM
To: [email protected]
Subject: Re: Legal syntax for multiple-operand continued DC statements?
At 14:28 -0400 on 05/31/2011, Farley, Peter x23353 wrote about Legal
> syntax for multiple-operand continued DC statements?:
>Sincebytes):
> >
> DC A(0),CL7'NAME1 ',X'00',X'09',X'03',AL1(typ_X)
> DC AL1(0+bitFlag1+bitFlag222+bitFlag3333+bitFlag44444)
> DC AL1(0+bitFlag5555555),AL1(0),AL1(0+bitF6),AL1(0)
>
>Please help cure my ignorance (or memory failure) here.
Here is a simple solution. Create a $DC macro to use in lieu of the
DC. That will allow you to format your DC as you want (ie: Macro
continuation format). Inside the macro you can generate each parm as
a separate DC (to avoid the need to emit end of line characters). By
using a PUSH/POP bracketing the DCs you can suppress the display of
the string of DCs if you want. Since there are no keyword parms, you
> can just count the parms and loop through them.
