I am using ACF2, and when this problem occurred, I checked to see if the TSOID had a directory in /u. If there id was not in the /u then I created a directory for them.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Stocker, Herman Sent: Thursday, June 25, 2009 8:43 AM To: [email protected] Subject: Racf And SAS problem G'day, I have a SAS job that I run without any problems. However, when I had a co-worker run it he has been getting errors. First he got error when starting the job: ICH408I USER(IMSSB ) GROUP(@UNIXAPP) NAME(BARKEY, STEVE ) 609 /u/imssb CL(DIRSRCH ) FID(01E3E2D6D4F0F9001627000000000003) INSUFFICIENT AUTHORITY TO CHDIR ACCESS INTENT(--X) ACCESS ALLOWED(OTHER ---) EFFECTIVE UID(0000007096) EFFECTIVE GID(0000007000) This caused the job to fail. This was corrected by deleting the imssb directory in lower case and defining it in upper case - IMSSB. How the job will run to the end of the SAS step and gets the error: ICH408I USER(IMSSB ) GROUP(@UNIXAPP) NAME(BARKEY, STEVE ) 330 /u/IMSSB CL(DIRSRCH ) FID(01E3E2D6D4F0F9001627000000000003) INSUFFICIENT AUTHORITY TO CHDIR ACCESS INTENT(--X) ACCESS ALLOWED(OTHER ---) EFFECTIVE UID(0000007096) EFFECTIVE GID(0000007000) Note that the /u/IMSSB/ is in upper case this was required to allow SAS to start executing. At the time of the error SAS has created the report and the CC is 0 for the step. Our security people have not been able to come up with any reason for this error therefore, they can not correct it. Anyone have any suggestions as to why we are getting this RACF error? Thank you. Regards, Herman Stocker The sender believes that this E-mail and any attachments were free of any virus, worm, Trojan horse, and/or malicious code when sent. This message and its attachments could have been infected during transmission. By reading the message and opening any attachments, the recipient accepts full responsibility for taking protective and remedial action about viruses and other defects. The sender's employer is not liable for any loss or damage arising in any way from this message or its attachments. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] 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 [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
