If overlay is a concern then just use ORG *,2,1
to move the location counter to the next byte after the half-word boundary. Kind Regards John R Dravnieks From: Tony Thigpen <t...@vse2pdf.com> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Date: 23/08/2016 12:24 Subject: Re: Friday puzzle: CNOP 1,2 Sent by: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> Won't this possibly overlay the previous field if the ORG happens to land on a half-word boundary? Maybe a set of ORGs: ORG *+1 ORG *,2,-1 Tony Thigpen John Dravnieks wrote on 08/22/2016 10:16 PM: > Why not use ORG to do this for you? > > ORG *,2,-1 take current position (*), > align to 2 byte boundary (if required), and move back one byte > > > Kind Regards > > John R Dravnieks > > > > > From: "Ngan, Robert" <rn...@csc.com> > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Date: 23/08/2016 03:03 > Subject: Re: Friday puzzle: CNOP 1,2 > Sent by: IBM Mainframe Assembler List > <ASSEMBLER-LIST@LISTSERV.UGA.EDU> > > > > I was trying to avoid generating an extra filler byte when one was not > required. > > -----Original Message----- > From: IBM Mainframe Assembler List [ mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU > ] On Behalf Of Robin Vowels > Sent: Friday, August 19, 2016 20:18 > To: ASSEMBLER-LIST@LISTSERV.UGA.EDU > Subject: Re: Friday puzzle: CNOP 1,2 > > From: "Ngan, Robert" <rn...@csc.com> > Sent: Saturday, August 20, 2016 4:47 AM > > > I'm writing a macro to build length prefixed character strings. The > length is one byte, and the actual string is referenced by LARL so it > needs to be halfword aligned. > So I coded (what would be a CNOP 1,2 - if it was valid): > > DC (1-(*-&SYSECT)/2)X'00' Simulate a CNOP 1,2 > > However, this generates ASMA067S Illegal duplication factor. > > > what's wrong with DS 0H followed by DC X'00' or some such? > > > --- > This email has been checked for viruses by Avast antivirus software. > https://www.avast.com/antivirus > > CSC - This is a PRIVATE message - If you are not the intended recipient, > please delete without copying and kindly advise us by e-mail of the > mistake in delivery. NOTE: Regardless of content, this e-mail shall not > operate to bind the Company to any order or other contract unless pursuant > to explicit written agreement or government initiative expressly > permitting the use of e-mail for such purpose. > >