RSECT does have the same effect as the RENT assembler option, in that you get warnings for non-rent code.
I use one assembly JCL (in fact, an ISPF macro generates the JCL), and this way I can let the code decide whether it should be RENT or not. Pieter -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Peter Relson Sent: Tuesday, February 16, 2016 16:18 To: [email protected] Subject: Re: Using macro to set assembler option >if the option is RENT, I define an RSECT, else CSECT. I'm curious. Why? If you're assembling with RENT, then what does RSECT additionally buy you? RSECT can protect you against not assembling with RENT, but that seems to be the flip side of what was stated. Perhaps I'm forgetting something, but IIRC, as far as the binder and z/OS itself is concerned, RSECT matters only for CSECTs in IEANUCxx where they are put into the read-only nucleus. It is ignored for all other situations. Peter Relson z/OS Core Technology Design
