If this is part of a vendor product, and we were looking at said product, and I learned that it did this, I would _strongly_ recommend against acquiring the product. Having this around is like having small bottles of fulminate of mercury scattered around in the kids' play room. It is most likely going to explode and do a lot of damage.
On Wed, Mar 5, 2014 at 9:12 AM, Rob Scott <[email protected]> wrote: > Do NOT do this ! > > This is a serious system integrity exposure. > > Rob Scott > Lead Developer > Rocket Software > 77 Fourth Avenue . Suite 100 . Waltham . MA 02451-1468 . USA > Tel: +1.781.684.2305 > Email: [email protected] > Web: www.rocketsoftware.com > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of dpewen > Sent: 05 March 2014 15:10 > To: [email protected] > Subject: ISPF Storage Protection > > Hello, > > I started this thread and I appreciate all the input I received from this > list. > I have solved the problem by adding code to my user svc that is part of > the product. > I added two functions to the svc: > 1. to turn on the APF-auth bit in the job step TCB 2. to turn off the > APF-auth bit in the job step TCB > > This allows me to issue the MODESET svc successfully. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- Wasn't there something about a PASCAL programmer knowing the value of everything and the Wirth of nothing? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
