Re: OA49446 changed RACF behavior for ALIAS, PATH, and AIX

On Thu, 21 Sep 2017 16:39:41 -0400, John Eells wrote: > >"Code is added to require SAF ALTER authority to the entry name when >defining an alias related to a nonVSAM or generation data set, or a VSAM >PATH or AIX. SAF ALTER authority is required to the entry name when >defining an ALIAS when the

Re: OA49446 changed RACF behavior for ALIAS, PATH, and AIX

Correction: A check was added for defining data set aliases: DEFINE ALIAS(NAME(dataset1) RELATE(dataset2)) ...but not for user catalog connector aliases: DEFINE ALIAS(NAME(hlq) RELATE(usercat)) Note that the new checks are in IDCAMS DEFINE. From the PTF: "Code is added to require SAF ALTER

Re: OA49446 changed RACF behavior for ALIAS, PATH, and AIX

Your post confused me, so I just verified that my understanding was correct. The checks for PATH and AIX were added to the base name check, and do not replace it. Also, I am told nothing was added for ALIAS. Pinnacle wrote: I'm looking at the HOLDDATA for OA49446. RACF was changed to do

Re: OA49446 changed RACF behavior for ALIAS, PATH, and AIX

YMMV, but we've been running with that APAR applied for well over a year without any fallout and didn't define that RACF profile. Pinnacle September 18, 2017 at 2:04 PM I'm looking at the HOLDDATA for OA49446. RACF was changed to do authorization checks