>Why Cann't you do Storage Obtain with ALET of Master that do MVCS to move the Address of >the Module
>Sorry forgot you have to issue RESMGR in Asid 1 okay >Can you execute the resmgr macro in the subsystem initlization routine for *MASTER* You have not yet grasped the concept of a memterm resmgr. It runs in ASID 1 on behalf of some terminating address space. You issue RESMGR to define your resmgr from within the application and you define the resmgr so that it applies to the termination of that application. You do not issue it "for *MASTER*". You do not "issue RESMGR in ASID 1". As to storage obtain: You can only use ALET if you have an ALET. It is far from typical to want to have *MASTER* accessible on your DU-AL or PASN-AL (placed there by ALESERV ADD).. MVCS works "to secondary". An ALET that you ALESERV ADDed is not going to be secondary. And unless you were PC'd to from *MASTER*, *MASTER* will not be your secondary. You could do a simple AR-mode move if you have everything set up. But if moving a "module", then the module better not have any relocation requirements (such as A-cons). All this is why no one bothers to do this. Either the resmgr is in LPA, or you have it LINKed to or PC'd to. You can get the resmgr into LPA either by the way your application is installed (perhaps part of that install is to copy some of your modules into a data set in the LPALST) or by use of CSVDYLPA. 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
