FWIW, subpool one isn't all of LE's storage, but it is the part that your C modules need.
It's certainly true that if you want to be able to do a subpool freemain, then you wouldn't want to use a subpool that "something else" obtained storage from. So that's where "not subpool 0" comes from and also "subpool 1". I have no idea why they chose subpool 1 for writeable static instantiation. But they did. Of course, if you're authorized you almost always want to avoid "any subpool that is part of the user region" unless you want to be bound by region size limits. <snip> 105 FREEMAIN RU,A=(1),LV=(0) *** ,SP=(R2) 107+ DS 0H @P2A ... Hmmm. Where did line 106 go? </snip> Line 106 is from "SYSSTATE TEST" issued within FREEMAIN. It's a macro invocation within a macro so in the absence of PRINT MCALL doesn't get shown in the listing. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
