I had already gone through the OPERCMDS and TSOAUTH classes and added the IDs to what I thought might fix consprof.
It was not until the TSO Segment (and all I did was do UNIT(SYSDA) nothing else) it was not working. The manual, in my opinion, only alluded to TSO segment without coming out right and saying To use CONSPROF, you need a TSO SEGEMENT on the ID issuing it. That would have been much more clear to me. Lizette > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Jesse 1 Robinson > Sent: Friday, June 07, 2019 2:04 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: How to grant access to CONSPROF - Conclusion > > Lizette, I had forgotten about your 'hanging post'. A colleague had the same > problem just this week. He wrote a CONSOLE REXX that worked for me but not > for him. The problem: I had a TSOE segment and he did not. He added a TSOE > segment to his userid, and his job worked fine. > > I am however intrigued that besides updating some OPERCMDS profiles, you did > not have to make any other changes. My understanding has been that if a > userid contains a TSOE segment, RACF assumes total control of logon. I.e. > UADS no longer has any role. But a few attributes need to be supplied to > complete the userid, TSOPROC for one. Now you may have a generic proc like > (*) already defined with UACC(READ) such that anyone could logon with any > proc. (I have not experimented with that.) I'm just surprised that you had no > problem with nothing else defined. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > robin...@sce.com > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Lizette Koehler > Sent: Friday, June 7, 2019 12:23 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: (External):Re: How to grant access to CONSPROF - Conclusion > > The steps needed was > > Add a TSO Segment by coding UNIT(SYSDA) in TSO section. No other options > were updated (I.e. no TSOPROC coded) > > Grant any additional OPERCMDS class entities - for example MVS.VAR.* > > Once this was done and SETR REFRESH completed > > My job now runs successfully > > IBM Documentation is not really clear. But at least now it works. > > Lizette > > > > > -----Original Message----- > > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On > > Behalf Of Elardus Engelbrecht > > Sent: Wednesday, March 20, 2019 12:38 AM > > To: IBM-MAIN@LISTSERV.UA.EDU > > Subject: Re: How to grant access to CONSPROF > > > > Lizette Koehler wrote: > > > > >I am trying to run a batch REXX that issues CONSPROF or CONSOLE commands. > > >I have set up everything in IKJTSO00 for CONSOLE, I have updated the > > >RACF TSOAUTH for the ID issuing the commands The process will VARY > > >OFFLINE and VARY ONLINE Dasd volumes > > > > >Yet I am still getting > > >IKJ55353I THE CONSPROF COMMAND HAS TERMINATED.+ IKJ55353I USER > > >USER001 DOES NOT HAVE CONSOLE COMMAND AUTHORITY. > > > > >Any other places to check? > > > > You have gotten good replies, but I would like that you please check > > out this > > URL: > > > > > https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3. > > ieag300/iea3g3140.htm > > > > Above describe how to setup everything (in RACF) to use Consoles: > > > > Class OPERCMDS. Profile - MVS.MCSOPER.<console>. > > Class TSOAUTH. Profile - CONSOLE. > > > > Please also review this ancient APAR II08610. > > > > Unless you have a weird exit which Walter described. > > > > Groete / Greetings > > Elardus Engelbrecht > > > ---------------------------------------------------------------------- > 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
