Well, restricted state is just like an IPL without the IPL. You still have to kick the users off the system, and that usually takes a lot of coercion and coordination!
Sounds like the exit programs work like routing programs-- the system checks to see if it needs to use the exit program when the job begins, and never checks again. A subsystem only checks for the routing program once, and then has a pointer right to the program. Change the routing entry; move or rename the program, and it still has a pointer right to the program. You have to end the subsystem to make it check for routing programs again. (You can delete/recreate the program, but you also have to remove the old program from QRPLOBJ (which is where the subsystem pointer points)).
Paul E Musselman
PaulMmn@xxxxxxxxxxxxx
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Gary Monnier
Sent: Thursday, August 23, 2018 10:44 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: RMVEXITPGM needs an IPL??
Admittedly it has been a while but you may be able to remove the exit
program and then bring the system to a restricted state. Then restart the
controlling subsystem.
Gary Monnier
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
