> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On > Behalf Of Paul Gilmartin > Sent: Monday, October 23, 2006 11:13 AM > To: [email protected] > Subject: Re: Is the teaching of non-reentrant HLASM coding practices ever > defensible? > > In a recent note, Bruce Black said: > > > Date: Mon, 23 Oct 2006 12:42:18 -0400 > > > > Also, the ORDER statement (which orders csects) has a P option to align > > a specific csect on a page boundary. You can also use it to specify the > > load module that follows it to fill in the rest of the page. > > > "load module" or CSECT? > > It's frustrating that ORDER provides no construct to place a > specified CSECT _last_. > > Here might be a legitimate use for an empty CSECT/load module/ > program object. But, as I note frequently, IBM does a miserable > job of supporting this boundary condition. > > -- gil
As I wrote in another post, I use an empty COM section, because the binder always puts common sections at the end (by default). The assembler looks like this: COMBAR COM , FUBAR CSECT , FUBAR AMODE 31 FUBAR RMODE ANY * Put entry logic here. * Put more CSECTS and data here. ENDBAR END , Just use something like: //SYSLIN DD * ENTRY FUBAR ORDER FUBAR(P) PAGE COMBAR NAME FUBAR /* The CSECT FUBAR is page-aligned first. The empty common section COMBAR is page-aligned last. Any other CSECTs in the module are placed between FUBAR and COMBAR. Problem solved. Jeffrey D. Smith Principal Product Architect Farsight Systems Corporation 700 KEN PRATT BLVD. #204-159 LONGMONT, CO 80501-6452 303-774-9381 direct 303-484-6170 FAX http://www.farsight-systems.com/ comments are invited on my encryption project ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
