I tried to start ENF but received: *CAS9202E - CA-ENF REQUIRED MODULE NOT FOUND -- CAS9EVT

Document ID : KB000029791
Last Modified Date : 14/02/2018
Show Technical Document Details


Attempting to start ENF but receiving the following message:


You have defined CAW0LOAD to the STEPLIB concatenation, and see that module CAS9EVT is present in this library. So why can it not be found?



The most likely problem is that older CA Common Services modules are being picked up either from steplib or the linklist and this is affecting the load of other modules. To be more specific, a back-leveled version of module CAS9LPAM is being pickup up. This will directly impact how CCS modules are loaded.

As documented, the CAW0LINK library must be apf-authorized and must defined to the system linklist. In addition, this library must be defined ahead of any library containing older releases of CA Common Services. It is advisable that any library containing older common services modules be removed from the linklist to avoid the possibility of introducing a "mixed-module" environment.

Use whatever tool you have at your disposal to search your linklist. One common tool is ISRFIND or ISRDDN. These are entered as TSO commands (usually entered from ISPF option 6).

Using ISRFIND, on the resulting display enter CAILPAM in the Member Name field and a 'Y' in the LOADMOD field just below that. Specifying "Y" will expand the search to include LPA, LINKLIST, etc.  

After hitting <enter> Scroll down and you will should find the member name to the right of the library where it is found.

If you enter a 'B' to the left of the dataset name, you can select the member for browse.                            

Using ISRDDN, on the resulting display, enter LPA;M CAILPAM on the command line.

After hitting <enter> you may be prompted to answer YES to proceed with the search. If the module is found it will be shown to the left of the library in which it exists.

If you enter "B" under the Action column to the left of the dataset name, you will browse the module. Here you should be able to identify information tying back to the CCS release.