>... when IEFBR14 is used to delete a data set ... >Haven't we agreed here that IEFBR14 doesn't delete data sets? Hasn't >IBM learned this yet?
To my way of thinking, the statement in the preview is correct and accurate. (Almost) Everyone at some point or other *uses* an EXEC PGM=IEFBR14 job to delete data sets. The statement does not say that IEFBR14 itself does the deletion. >Of course, to be useful this practically requires 64-bit ESD/RLD support. 64-bit adcons and RLD entries have been supported by the assembler and binder for a long time. >By experiment, I discover that HLASM won't let me create a CSECT >16MiB. It won't let me create a program with multiple CSECTs >totalling >16 MiB(?!) The binder has a restriction of (on the order or) 2G. Obviously HLASM cannot possibly restrict you from combining multiple CSECTs into anything you want, but the binder can. HLASM could have a restriction such as 16M on the cumulative size of CSECTs within a single assemly unit (I have no idea if that is the case) It is the case that a load module cannot exceed 16M. But a program object can. The load module restriction is due to limitations in the PDS directory entry. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
