>As best I recall, the subsystem's init routine LOADed a module into common >and put it's entry point address into a CSA control block. When the module >was called by an address space during normal execution, the module was no >longer there.... >There is a way to do this >load such that the module won't be deleted at task termination, but I don't >remember the details.
Either LOAD with ADDR (i.e., "directed LOAD") or (usually better) CSVDYLPA are the right ways to load something to common storage such that it does not get deleted automatically by the system *ever*. It is almost never right to use LOAD with GLOBAL=YES because it is almost impossible to make sure that no code is executing within your common-storage area when your task terminates. And CSVDYLPA is better for diagnostics than LOAD with ADDR, as a name is associated with the area (as might be helpful in setting a SLIP trap). 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
