Yes, I was way off base chasing the RACF problem. Turns out, somebody coded up a little program that goes out and checks a hard coded list of user names to see who should get to run the program.
Ken Klein Sr. Systems Programmer Kentucky Farm Bureau Insurance - Louisville kenneth.kl...@kyfb.com 502-495-5000 x7011 -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Chase, John Sent: Thursday, July 02, 2009 12:10 PM To: IBM-MAIN@bama.ua.edu Subject: Re: Command program from the cbt > -----Original Message----- > From: IBM Mainframe Discussion List On Behalf Of Mark Zelden > > On Thu, 2 Jul 2009 10:15:28 -0400, Klein, Kenneth <kenneth.kl...@kyfb.com> > wrote: > > > No, that's why the RACF guy tells me it's not his problem. No RACF > >messages. Just the cmd913e error message from the command program. I can > >see in the code that he does a rackroute and the BH command sends > >control straight to the error message and abends. > > > > Your RACF guy is wrong, it's a RACF issue. I use COMMAND in my sandbox > LPARs for startup and shutdown and have the source. It checks the > RACF FACILITY class for a profile called COMMAND to see if you have > access. I don't have anything defined, so it works without it. But your > system must have a COMMAND profile defined in the FACILITY class and > you are not authorized. > > Here is a snippet of source: > > *********************************************************************** > * * > * CHECK THE AUTHORITY OF THE USER TO SAF CLASS "FACILITY' FOR * > * ENTITY "COMMAND". NOTE THAT FASTAUTH IS USED. TO AVOID THE * > * SITUATION WHERE SPECIAL ATTRIBUTES OF THE USER MAY ALLOW THE * > * ACCESS WITH LOGGING, A CHECK IS MADE FOR A NON-ZERO REASON * > * CODE. THIS CONDITION WILL BE CONSIDERED A FAILURE. * > * * > *********************************************************************** > AUTHTST RACROUTE REQUEST=FASTAUTH,WORKA=RACWORK,WKAREA=FRACWORK, X > ENTITY=RESOURCE,CLASS=FACILITY,ATTR=READ, X > MF=(E,RACROUTE) > CH R15,=H'4' TEST THE RETURN CODE > BE EXTRACT NO DECISION POSSIBLE, OK > BH NOTAUTH GREATER THAN 4, NOT AUTHORIZED > CLC RACROUTE+4(4),=F'0' TEST THE REASON CODE > BE EXTRACT ZERO, AUTHORIZED > NOTAUTH WTO 'CMD913E UNAUTHORIZED USE OF THE COMMAND PROGRAM - JOB AX > BORTED',ROUTCDE=(2,11) > ABEND X'913',,,SYSTEM,REASON=0 ABEND THE JOB Based on the OP's subsequent post showing SAFRC04, his job is failing somewhere after the EXTRACT label. Absence of the COMMAND profile in FACILITY appears not to be the problem. -jc- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
