Posted: Fri Mar 03, 2017 1:38 pm Post subject: Why no ICH408I's when RC2035?
Novice
Joined: 18 Jan 2017 Posts: 10
Why is it that we don't see a SYSLOG ICH408I "User Not Authorized" message when a MQ RC 2035 is received. For example, if a user is unauthorized to a queue protected with a RACF MQQUEUE profile, why wouldn't we get a ICH408I if an unauthorized user receives a RC 2035 inside of MQ?
A specific case is a batch job submitted from z/OS TSO to a single QMGR.
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
That's odd. It should be in the MSTR log. Check with your RACF team.
I'm not sure if its possible to receive reason code 2035 without MQ invoking RACF. _________________ Glenn
Posted: Tue Mar 07, 2017 7:13 am Post subject: Problem resolved
Novice
Joined: 18 Jan 2017 Posts: 10
After some rechecking, I was able to successfully test an unauthorized GET against a MQQUEUE profile that generates an ICH408I into the SYSLOG. Thanks for your help.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum