Since &CSECT isn't a system variable, that behavior would depend on what you set &CSECT to. If you use &SYSECT then the generated alignment should be based on the start of the CSECT.
- mb > -----Original Message----- > From: IBM Mainframe Assembler List <[email protected]> On > Behalf Of Bill Hitefield > Sent: Thursday, November 30, 2023 2:59 PM > To: [email protected] > Subject: [EXTERNAL] Re: BAKR/PR and Linkage Convention > > I have not done any serious research on it. I've had the code since my > early days. > > I do know that if you use it within a location counter, the generated > alignment will be based on the alignment of the start of the location > counter. > > For example, if the location counter starts at +X'0010' (to make the > arithmetic easy) and you issue "ALIGN 256", the alignment will be to > +X'0110', not X'0100'. > > Bill Hitefield > Dino-Software Corporation > 800.480.DINO > www.dino-software.com > > > -----Original Message----- > > From: IBM Mainframe Assembler List <[email protected]> > > On Behalf Of Paul Gilmartin > > Sent: Thursday, November 30, 2023 1:47 PM > > To: [email protected] > > Subject: Re: BAKR/PR and Linkage Convention > > > > On 11/30/23 09:38:19, Bill Hitefield wrote: > > > > > > I have used the following (in a macro) to do that: > > > > > > $ALIGN EQU &VALUE-((*-&CSECT)-(((*-&CSECT)/&VALUE)*&VALUE)) > > > DC ($ALIGN)X'00' SET ALIGNMENT > > >. > > How well does such a thing work under a LOCTR? If such a thing is > > used in a LOCTR, or even two different LOCTRs, I could envision dueling > lookaheads. > > > > -- > > gil
