It sounds like that presentation is trying to cater for the situation where the PC number is stored somewhere and must not change by design, which also hints that a reusable LX is not being employed.
I would suggest using a reusable LX and then make sure the caller can locate the sequence number as easily as the PC number(s). When the server ASID restarts, you AXSET to 1, reissue the LXRES, ETDEF, ETCON as before. In other words, your init routine is agnostic to whether it is being started for the first time or not. I would also suggest that your server perform a CSVQUERY for the LPA module(s) and re-use any existing versions found rather than CSVDYLPA ADD every time. Do not CSVDYLPA DELETE on server termination. If maintenance is applied to the LPA modules, get the operator to issue the SETPROG commands to update LPA prior to server restart. Rob Scott Rocket Software -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of esst...@juno.com Sent: Monday, February 18, 2019 7:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Retart after a Failed PC Service Routine with a sysem LX . 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 ================================ Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
