Hi Paul,
OPCMDS preceded OPERCMDS. Here is some information:
Under ESA 3.1.3, IBM decided to start using OPERCMDS instead of OPCMDS.
If you didn't have security setup for OPERCMDS, then IBM would check for
OPCMDs. This allowed user to transition from OPCMDS to OPERCMDS slowly.
If IBM ever decides in a future release of z/OS to stop checking OPCMDS
because OPERCMDS security was not setup, your users with OPCMD permission
will start to receive security violations for those operator commands.
So if you have a mix of OPERCMDS and OPCMDs PERMITs in place, OPERCMDs are
checked first by IBM. If not present, then OPCMDs security checks will be
issued by IBM. Please note, the newer operator commands post ESA 3.1.3 may
not check OPCMDS, since it was being phased out.
The OPCMD(LOGON) is specific to TSO.
Are you receiving CAS9320E messages?
If so, I found some information about ENF that may be helpful:
CAS9320E messages are usually related to leaving out any of the steps in holdaction for RO54507, which was PEed and corrected by RO62370 and is part of CCS 14.1 S1401. RI69562 is also pointing to this holddata from RO54507.
Have a nice day!
Eileen K. Becht
Top Secret Level 1 Support