Actually, maybe not necessary, but I figured out my answer. CORG -32,256
Thanks, Dave Clark On Mon, Feb 23, 2026 at 5:49 PM David Clark <[email protected]> wrote: > >> All your modifiable data should be in the dsect DFHEISTG > > It is. > > >> Constant data is not an issue as the cache does not get corrupted. > > OK, thanks. > > Sincerely, > Dave Clark > > > On Mon, Feb 23, 2026 at 5:29 PM Tony Thigpen <[email protected]> wrote: > >> Dave, >> >> All your modifiable data should be in the dsect DFHEISTG, which is not >> located anywhere near your program object. CICS then handles storage >> allocation, so you don't have to worry about cache alignment. >> >> Constant data is not an issue as the cache does not get corrupted. >> >> >> Tony Thigpen >> President >> Thigpen Enterprises >> >> David Clark wrote on 2/23/26 5:09 PM: >> > I have been aligning my assembler data areas and code areas with the >> > following macro. >> > >> > CORG 0,256 >> > >> > But now I'm looking at an assembler program for CICS and I see that the >> > alignment is off by 32 bytes. That accounts for the EAI stub that is >> > linked onto the beginning of my program. I also see 56 bytes added on >> to >> > the end of my program. >> > >> > What do y'all, that care about cache alignment, use for a program in >> CICS? >> > >> > Sincerely, >> > Dave Clark >> >
