Barbara, keep in mind that the SAMPLIB IKJTSO reflects a "vanilla" system. Any Program Products may instruct you to update IKJTSO.
CA ENF, zSecure, OPS/MVS, all have a place in mine. Along with remnants from the past that I hesitate to delete. :-) Cheers,,,Steve Steven F. Conway, CISSP LA Systems z/OS Systems Support Phone: 703.295.1926 [email protected] From: "[email protected]" <[email protected]> To: [email protected] Date: 09/12/2013 09:21 AM Subject: Re: TSO Delete in IKJTSOxx Sent by: IBM Mainframe Discussion List <[email protected]> > >I've run into this in the past when deleting GDG bases from ISPF 3.4. I get an authorization failed message, and putting DELETE in IKJTSO00 and a PARMLIB UPDATE(00) fixes it. > > Interesting. This is new for me or I forgot about it. :-) I found this interesting, too, so I went and tried it out. Discovered first that the active IKJTSO member is not compliant with the one in samplib (typical for ADCD!), and that we had delete in it, too. Removed delete from the authcmds and still didn't get any error messages, RACF or otherwise when I deleted an empty GDG base. > Could you be kind to say what that message was? Was it a RACF message on the profile covering the GDG, Catalog or was it about STGADMIN.IGG.DELGDG.RECOVERY? Or something else? Yes, that would be interesting, since I gave myself ALTER authority to just about everything since I am supposed to be both RACF and space admin. Barbara Nitz PS: Now I am checking what we actually have in IKJTSO as opposed to what we should have in there according to sys1.samplib. ---------------------------------------------------------------------- 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
