Hi
I'm wondering how you deal with sapuxuserchk and/or why SAP does not cope with the below problem:
* When we installed SAP Systems / SAP Kernel patches manually in the past we executed saproot.sh, which sets sticky bit and permissions for the file sapuxuserchk in ASCS and DVEBMGS kernel folders
* If we now do updates/kernel patches via SUM oder elselike I more often realise these sapuxuserchk executables are never overwritten, because normally this takes care via sapcpe which cannot overwrite these files due to root-ownership
Currently, we deployed newest kernels via SUM SPS maintenance; files sapuxuserchk however, are still dated 2014 :)
Of course, I can do this manually; with >100 SAPSIDs this kind of a time consuming task.
How do you cope with that?
Why does SAP not make sure a new copy of sapuxuserchk is written to DIR_EXE if I execute saproot.sh or cope with that problem during SUM runs or the like?
Do I still need to execute saproot.sh / set sticky-bits and ownership in current kernel at all? Because all I can find in official SAP notes refers to old 720-kernels
Curious regards
Michael