A PDS Change Monitor policy has been defined to receive emails for all changes to library SYS3.TSS.PARMLIB. The emails being received do not have the MEMBER listed, just "MEMBER:unknown". The processes used to update the parmlib member(s) are via FTP and IEBCOPY. What is causing this condition?
This condition is caused by the FTP and IEBCOPY jobs performing an EXCP process (changetype=E).
Release : 6.0
Component : CA COMPLIANCE EVENT MANAGER
The cause of the %MEMBER% displaying 'unknown' is due to both FTP and IEBCOPY specifying a 'changetype' of 'E' for EXCP access instead of the standard 'changetype' of A (Add), U(Update), and D(Delete). An EXCP type does not use the standard I/O calls for CEM hooks to process, instead using low level I/O to perform disk R/W. CEM can tell that EXCP is being done and what the dataset name is, but access to the specific member name is unavailable, leaving it blank. When a field in an action references a field that is empty (blank) CEM's MAP process fills the %FIELD_NAME% with FIELD_NAME:unknown, and in this case MEMBER:unknown. This is expected behavior with EXCP, and CEM is working as designed.