>(The module must not have been previously loaded into CSA with different >attributes by the same job step, the module must also be reentrant and must >reside in an APF-authorized library.)
Yes, the documentation could be improved. As with many things, the system likes to use a copy on the job pack queue. If it finds a "potential match" but then finds that the current request is a load to global, it checks if the new request is compatible with the old request. An existing copy "in private" is not compatible with a new request for global. Similarly, an existing copy in pageable CSA is not compatible with a request for fixed CSA. More or less, removing "into CSA" makes this correct when referring to GLOBAL=YES or GLOBAL=(YES,xxx). Given the sentence's placement within the LOAD parameter section (where it shows all the GLOBAL=xxx options, including GLOBAL=NO), I believe it would be correct and complete to have that sentence be: (When the module is to be loaded into CSA, the module must not have been previously loaded with different attributes by the same job step, the module must also be reentrant and must reside in an APF-authorized library.) I will get this updated. 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
