Instead of adding function codes to the SVC to allow setting and resetting of the JSCBAUTH bit, add function codes to the SVC to perform the code that requires authorization. As others have mentioned, this type of "magic" SVC destroys any concept of system integrity. ============================================== Wayne Driscoll OMEGAMON DB2 L3 Support/Development wdrisco(at)us(dot)ibm(dot)com All opinions are mine, and do not represent IBM Corporation. ==============================================
IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> wrote on 03/05/2014 09:10:11 AM: > From: dpewen <dpe...@bellsouth.net> > To: IBM-MAIN@listserv.ua.edu, > Date: 03/05/2014 09:10 AM > Subject: [IBM-MAIN] ISPF Storage Protection > Sent by: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> > > Hello, > > I started this thread and I appreciate all the input I received fromthis 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
