"IBM Mainframe Assembler List" wrote on
11/30/2023 03:10:36 PM:
> 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.
Yes, my layout is according to
Ref: Your note of Thu, 30 Nov 2023 11:46:44 -0700
> $ALIGN EQU &VALUE-((*-&CSECT)-(((*-&CSECT)/&VALUE)*&VALUE))
If you use an alignment expression like this, the alignment is
relative to whatever &CSECT is. If you use &SYSECT as in the
CORG macro then it is relative to the current control se
f Of Bill Hitefield
> Sent: Thursday, November 30, 2023 2:59 PM
> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
> 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
ist
> On Behalf Of Paul Gilmartin
> Sent: Thursday, November 30, 2023 1:47 PM
> To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
> 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:
> &
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,
Ed,
I have used the following (in a macro) to do that:
$ALIGN EQU &VALUE-((*-&CSECT)-(((*-&CSECT)/&VALUE)*&VALUE))
DC ($ALIGN)X'00'SET ALIGNMENT
&VALUE is whatever boundary you want (256, 512, 8, 4, …).
&CSECT is the name of the csect (or location counter).
DC or DS can be
