Compliance Event Manager task CEMALERT produces CEM_DUMP_EVTNUM messages even though CEM_TRACE=NONE is specified.
Article ID: 106204
CA Compliance Event Manager
After upgrading CEM 6.0 to Incremental Release 4 (IR4), the following messages continually appear after CEMALERT starts even though CEM_TRACE=NONE is specified:: *** map_debug_trc() successfully opened //DD:CEMTRC The env CEM_TRACE=NONE The CEM_TRACE level is 0x0 The CEM_DUMP_EVTNUM is 0 The CEM_DUMP_THD_MATCHLIM is 0 CEM_DUMP_EVTNUM = 13 skipped, configured for 0 only CEM_DUMP_EVTNUM = 11 skipped, configured for 0 only CEM_DUMP_EVTNUM = 11 skipped, configured for 0 only CEM_DUMP_EVTNUM = 13 skipped, configured for 0 only . etc. ****.
CEM 6.0 Incremental Release 4 (IR4) introduced these new messages, and they are intentional.
CEM 6.0 IR4
Removing the //CEMTRC DD during normal execution eliminates the trace and debug records from appearing.
Consideration is being made to move these messages to another logging level. If so, this will be introduced via subsequent maintenance.