. I'm digesting a Share Presentation from March 2015, Session 17096. "Does my address space have enough storage for me ?" . The Author talks about setting up a System LX providing service to "ALL". . Granted this presentation can't cover every aspect of a SYSTEM LX, and this question is probably out side its scope. . It does however identify the steps needed to Restart a Failing Server Address Space - upon abnormal termination. . The Presentation States: "If the server terminates and restarts, it would issue AXSET for the new space and re-issue ETCON (and thus must make sure that the TKLIST and ELXLIST areas are accessible). It would not reissue LXRES." . What if the termination occurred in a PC Service Routine ? And then subsequently corrected ? . Here's a scenario. Lets say that Our ETDEF for a Reusable System LX contains three programs. All Programs are Dynamically loaded into LPA and are defined as Non-Space Switching, PC-cp. . The ETDEFF could have specified the PC Service Routine in LPA either by Name or Address. . If the Sever Address Space Termination occurred in one of the PC Service routines, how does the address space determine how to restart with a new/different entry table, once the program is corrected ?It is m understanding the restart logic requires an ETCON macro and the original entry table is still in affect.Is my assessment correct ? . You would not want to IPL. . How would the Entry Table recognize the new address of the changed PC service routine ? Would another initial start be required ? The corrected routine may have been dynamically loaded into the LPA at a different location. . I'm not talking about Associated Recovery Routines. . I would like to here some thoughts on this. .
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
