Re: RRS trouble usage
Look at profiles in the RACF DSNR class. If you just starting to use RRSAF, you may have profiles of the form: ssid.BATCH (for utilities or call attach). ssid.SASS (for CICS connections). If this is the case, you need to add profiles ssid.RRSAF that will have similar access requirements as ssid.BATCH. Wayne Driscoll Product Developer NOTE: All opinions are strictly my own. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Roland Schiradin Sent: Monday, June 23, 2008 11:31 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: RRS trouble usage Seems to be a security issue Roland 00F30013 Explanation: The requester is not authorized to connect to this DB2 subsystem. This condition might indicate an attempted security violation. This reason code is issued by the following CSECT: DSN3AUCN System action: The connection request is denied. User response: Verify that you have specified the correct RACF authorization ID. If necessary, request authorization to access the DB2 subsystem from your security administrator. System programmer response: Examine the console/SYSLOG output for RACF messages issued when a request is denied. Refer the user to your security administrator if the user should be granted authorization to a DB2 subsystem. Refer to Part 3 (Volume 1) of DB2 Administration Guide for examples of how to authorize users to specific DB2 subsystems. Problem determination: During TCB connection processing, Subsystem Support invokes the RACROUTE service (causing a RACF RACHECK) to verify the authorization ID associated with the requester. If the RACF return code indicates the requester is not authorized to connect to this DB2 subsystem, the connection request is terminated with this reason code. -- 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
RRS trouble usage
Hi everybody, I have this next error (attached file) when i tried to use RRS module to incorporate a product trough JDBC DB2 services on mainframe to a DB2 subsystem located on distinct LPAR (only 2 LPARs on this mainframe) the DB2 subsys is on LPAR #1 and the RSS and the product is on the LPAR # 2, there is an Data Sharing Schema on this Mainframe. Can somebody help me with this? Thanks. _ P.D. Checa las nuevas fotos de mi Space http://home.services.spaces.live.com/ -- 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 1 J E S 2 J O B L O G -- S Y S T E M M E X F -- N O D E G F P T 0 15.57.08 JOB71343 MONDAY,23 JUN 2008 15.57.08 JOB71343 IRR010I USERID XM02028 IS ASSIGNED TO THIS JOB. 15.57.12 JOB71343 ICH70001I XM02028 LAST ACCESS AT 15:40:58 ON MONDAY, JUNE 23, 2008 15.57.12 JOB71343 $HASP373 XM02028M STARTED - INIT 16 - CLASS F - SYS MEXF 15.57.12 JOB71343 IEF403I XM02028M - STARTED - TIME=15.57.12 15.57.46 JOB71343 - --TIMINGS (MINS.)---PAGING COUNTS 15.57.46 JOB71343 -STEPNAME PROCSTEPRC EXCP CONNTCBSRB CLOCK SERV WORKLOAD PAGE SWAP VIO SWAPS 15.57.46 JOB71343 -RIVBASI 12 21741246.08.00 .5 439K BATCH3 0 0 0 15.57.46 JOB71343 -RIVLDAP FLUSH 0 0.00.00 .0 0 BATCH0 0 0 0 15.57.46 JOB71343 -RIVNETW FLUSH 0 0.00.00 .0 0 BATCH0 0 0 0 15.57.46 JOB71343 -RIVRACF FLUSH 0 0.00.00 .0 0 BATCH0 0 0 0 15.57.46 JOB71343 -RIVWN02 FLUSH 0 0.00.00 .0 0 BATCH0 0 0 0 15.57.46 JOB71343 IEF404I XM02028M - ENDED - TIME=15.57.46 15.57.46 JOB71343 -XM02028M ENDED. NAME-SAMJ.INSTALL TOTAL TCB CPU TIME=.08 TOTAL ELAPSED TIME=.5 15.57.46 JOB71343 $HASP395 XM02028M ENDED 0-- JES2 JOB STATISTICS -- - 23 JUN 2008 JOB EXECUTION DATE - 145 CARDS READ - 236 SYSOUT PRINT RECORDS -0 SYSOUT PUNCH RECORDS - 12 SYSOUT SPOOL KBYTES - 0.56 MINUTES EXECUTION TIME 1 //XM02028M JOB (0001), JOB71343 // 'SAMJ.INSTALL', // CLASS=L, // MSGCLASS=X, // REGION=0M, // NOTIFY=XM02028, //TIME=1440 //* /*JOBPARM SYSAFF=MEXF //* //* //* INITIAL VALUE OF SAM/BASIC //* 2 //RIVBASI EXEC PGM=JVMLDM56,REGION=256M,COND=(0,LT) 3 //STEPLIB DD DISP=SHR, // DSN=SYS1.SIEALNKE 4 // DD DISP=SHR, // DSN=LDB2MXD1.DMD1.SDSNEXIT 5 // DD DISP=SHR, // DSN=LDB2MXD1.DMD1.SDSNLOAD 6 // DD DISP=SHR, // DSN=LDB2MXD1.DB2V810.DMD1.SDSNLOD2 7 //SYSOUT DD SYSOUT=* 8 //SYSPRINT DD SYSOUT=* 9 //STDOUT DD SYSOUT=* 10 //STDERR DD SYSOUT=* 11 //CEEDUMP DD SYSOUT=* 12 //ABNLDUMP DD SYSOUT=* 13 //SYSABEND DD SYSOUT=* 14 //ABNLIGNR DD DUMMY 15 //CEEOPTS DD DISP=SHR, // DSN=SYS3.SAMJ.V35.DAT.USER.CNTLLIB(CEEOPTS) 16 //STDENV DD PATHDISP=(KEEP,KEEP), // PATH='/opt/sam/v35/bin/readInitValues.sh' 17 //MAINARGS DD * //* //* INITIAL VALUE OF SECURITY SYSTEM LDAP //* 18 //RIVLDAP EXEC PGM=JVMLDM56,REGION=256M,COND=(0,LT) 19 //STEPLIB DD DISP=SHR, // DSN=SYS1.SIEALNKE 20 // DD DISP=SHR, // DSN=LDB2MXD1.DMD1.SDSNEXIT 21 // DD DISP=SHR, // DSN=LDB2MXD1.DMD1.SDSNLOAD 22 // DD DISP=SHR, // DSN=LDB2MXD1.DB2V810.DMD1.SDSNLOD2 23 //SYSOUT DD SYSOUT=* 24 //SYSPRINT DD SYSOUT=* 25 //STDOUT DD SYSOUT=* 26 //STDERR DD SYSOUT=* 27 //CEEDUMP DD SYSOUT=* 28 //ABNLDUMP DD SYSOUT=* 29 //SYSABEND DD SYSOUT=*
Re: RRS trouble usage
Seems to be a security issue Roland 00F30013 Explanation: The requester is not authorized to connect to this DB2 subsystem. This condition might indicate an attempted security violation. This reason code is issued by the following CSECT: DSN3AUCN System action: The connection request is denied. User response: Verify that you have specified the correct RACF authorization ID. If necessary, request authorization to access the DB2 subsystem from your security administrator. System programmer response: Examine the console/SYSLOG output for RACF messages issued when a request is denied. Refer the user to your security administrator if the user should be granted authorization to a DB2 subsystem. Refer to Part 3 (Volume 1) of DB2 Administration Guide for examples of how to authorize users to specific DB2 subsystems. Problem determination: During TCB connection processing, Subsystem Support invokes the RACROUTE service (causing a RACF RACHECK) to verify the authorization ID associated with the requester. If the RACF return code indicates the requester is not authorized to connect to this DB2 subsystem, the connection request is terminated with this reason code. -- 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
