> -----Original Message----- > From: IBM Mainframe Assembler List [mailto:ASSEMBLER- > [email protected]] On Behalf Of John Ehrman > Sent: Tuesday, May 31, 2011 3:14 PM > To: [email protected] > Subject: Re: Legal syntax for multiple-operand continued DC statements? > > Peter Farley wrote: > > I had thought that the following would be a legal syntax for > multiple-operand continued DC statements, but HLASM is complaining about > it. Here is what the source looks > like: > > > > DC A(0),CL7'NAME1 ',X'00',X'09',X'03',AL1(typ_X), X > > AL1(0+bitFlag1+bitFlag222+bitFlag3333+bitFlag44444), X > > AL1(0+bitFlag5555555),AL1(0),AL1(0+bitF6),AL1(0) > > It's not your fault! Unfortunately, HLASM supports two different > continuation syntaxes: for macro invocations, you can put each argument > on a separate line in much the way you wrote your DC statement (with > spaces after an operand up to the continuation marker). > > The syntax for ordinary statements -- like your DC -- require that the > operand characters be continuous up to the column (usually 71) before > the continuation character. > > Having a single uniform continuation syntax -- preferably, that used > for macros -- has been on the HLASM "Wish List" for a while. I regret > that we haven't had time or resources to fix it. > John Ehrman
Thanks for the clarification John. I might just go ahead and use several DC's instead of one to keep thinks simpler. Thanks to all for your help. Peter P.S. -- Ray B., there really are 15 spaces before the DC and before each of the continuation lines, even if the email doesn't look like it. Thanks anyway for the warning because you're right, HLASM can be "fussy" about stuff. It's why we love it, right? -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
