When trying to start ENF with the internal MUF (IMUF), it started to come up but then abended in the Datacom/Muf step. Here are some of the error messages that led up to the abend. Take note of the items in BOLD that identifies the problem leading up to the CAS9234E message and the subsequent ENF U0203 abend.
Any supported z/OS level
CA-ENF r12 or higher running with a Datacom/AD database
Datacom/AD v12 and v14
The problem lies within the SYSIN defined for the Datacom/AD MUF. Specifically within the Datacom/AD CUSTOM.CUSMAC(DBDATIN1) file. This symptom can occur while in the process of upgrading CA Common Services from r11.0 to r12.0 and higher. During the process, the new ENF task is inadvertently started pointing to the old CA Common Services load library (eg. CAILIB) and causes the execution of the old r11.0 version of PGM=CAS9MNGR. The concern is that the old CAS9MNGR program opens SYSIN as output and attempts to write information to the file, thus "corrupting" the contents of the DBDATIN1 file.
The DBDATIN1 member should contain information such as:
You should not see entries for PRIVUSR(*), DEST(ENFDBASE), QUERY(ALL), etc..... as referenced in the above DB01901E messages.
Restore the original copies of DBDATIN1 and DBDATIN2.
DBDATIN1 is created and customized when you installed Datacom/AD r12 and ran INSTJCL job AXCUS01. Please see the Datacom/AD install customization step where the AXCUS01 job is referenced, or the Datacom/AD Multi-User Deployment step in the CA Common Services Installation Guide where the AXDEP03 job is referenced.
DBDATIN2 is created by the Datacom/AD r12 install and is not meant to be customized by the user.
Note: CA Datacom/AD r14 environments will refer to members AXDATIN1 and AXDATIN2
Release: CA90SV00200-12-Common Services-for z/OS