Only other thing I can think of offhand is that AOPSTC on the 2.5 system is a member of the OMVSGRP and on the 3.1 it is not.
However, you already stated that RACF looks the same. On Tue, 23 Jul 2024 09:43:00 -0400, David Spiegel <[email protected]> wrote: >Hi John, >Thank you for the suggestion. >Unfortunately, the only thing displayed was the Permission Bits. > >$ getfacl /usr/lpp/Printsrv/bin/aopstop >#file: /usr/lpp/Printsrv/bin/aopstop >#owner: OMVSKERN >#group: OMVSGRP >user::rwx >group::r-x >other::--- > >Thanks and regards, >David > >On 2024-07-23 07:18, John S. Giltner, Jr. wrote: >> If you have not you may want to see if somebody set a file ACL >> >> getfacl /usr/lpp/Printsrv/bin/aopstop >> >> On both systems and see if they are the same >> >> >> On Mon, 22 Jul 2024 09:23:32 -0400, David Spiegel <[email protected]> >> wrote: >> >>> Hi, >>> In z/OS V3.1, I issued (via SDSF) S AOPSTOP and it failed because AOPSTC >>> (taken from STDATA) has UID(1) and GID(24), and >>> /usr/lpp/Printsrv/bin/aopstop has its Permission Bits set to 750. The >>> file is owned bu UID(0) GID(1). This is expected. >>> >>> On z/OS V2.5, however, AOPSTOP works (with the same STARTED Class >>> Profile and Permission Bits.) >>> Can someone explain why it works on 2.5? (Based upon UID/GID and >>> Permission Bits, it seems like it shouldn't.) >>> I looked at the DBSYNC output comparing the 2.5 and 3.1 RACF Databases >>> and did not notice anything that would explain this behaviour. >>> >>> Thank you in advance. >>> >>> Regards, >>> David >>> >>> ---------------------------------------------------------------------- >>> For IBM-MAIN subscribe / signoff / archive access instructions, >>> send email to [email protected] with the message: INFO IBM-MAIN >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
