Problem:
Trying to put in a new component, MF Connector, but the APPLY CHECK of FMID CC2D771 gives the following MODs to have 'NOT SEL':
ELEMENT SUMMARY REPORT FOR APPLY PROCESSING
ELEMENT ELEMENT ELEMENT CURRENT CURRENT DISTLIB SYSLIB ASSEM LOAD LMOD SYSMOD SYSMOD
TYPE NAME STATUS FMID RMID LIBRARY LIBRARY NAMES MODULE SYSLIB NAME STATUS
MOD GREXCLK NOT SEL AC2DMOD CC2D771 APPLIED MOD GREXCM NOT SEL AC2DMOD CC2D771 APPLIED MOD GREXCT NOT SEL AC2DMOD CC2D771 APPLIED MOD GREXEQ NOT SEL AC2DMOD CC2D771 APPLIED MOD GREXSRT NOT SEL AC2DMOD CC2D771 APPLIED MOD GREXZA NOT SEL AC2DMOD CC2D771 APPLIED MOD GRXERRT NOT SEL AC2DMOD CC2D771 APPLIED MOD GRXEXCOM NOT SEL AC2DMOD CC2D771 APPLIED MOD GRXSVP NOT SEL AC2DMOD CC2D771 APPLIED
I have found that all the above MODs are owned by FMID: CCF3E00 (CA-GREXX).
As Mainframe Connector is part of the CA Common Services r14.1 package, we are trying to put it in the same SMP/e target zone. As a result of this conflict I am not sure how to proceed at this point.
Environment:
Any supported z/OS level
CA Common Services r14.1 with CA-GREXX installed.
Cause:
The CA Mainframe Connector install includes CA Management Services, which in turn delivers some common GREXX modules. None of this is actually utilized by Mainframe Connector which is a stand-alone STC that uses TCPIP to communicate with VM and Linux on one side and OPS/MVS or SOLVE:Operations on the other.
Resolution:
The preferred path is to install CA Mainframe connector in its own SMP/E CSI or Target Zone apart from CA GREXX.
Workaround:
If it was decided to install CA Mainframe Connector into the same environment as CA GREXX, you can ignore the fact that the above mentioned MODS were NOT SEL, but you may want to run some UCLIN to reset the DISTLIB value for these modules in event any new GREXX PTF is delivered that hits one of these MODS.
After the install you will see that the SMP/E zones were updated as follows:
To "reset" the environment, here is some sample UCLIN:
Duplicate the above statements for each MOD listed above.