Did you know what other 'ENF dependent' STCs will also need to be recycled when adding new or will those products dynamically re-connect to the ENF STC once it is again active?
After updating CA Common Services for z/OS ENF PARM CICSREL to add new CICS/TS release values, you are wondering what will be required to recycle the ENF STC.
What other 'ENF dependent' STCs will need to be restarted or will those products dynamically reconnect to the ENF STC once it is again active?
You are running with a z/OS environment with CA Common Services r14.1, CA-7, CA-11, CA-Datacom and CICS.
Once you have updated your CICSREL parameter with 68 and 69, you have to recycle ENF with these commands to activate the change:
P ENF - command to stop the ENF address space. You will need to respond 'Y' to the WTOR prompt.
S ENF,,,REINIT - command to start the ENF address space with the REINIT option.
Information for your CA-7 product:
Before pausing and restarting ENF, you have to check that no CA-7 controlled batch jobs are running and classes are held.
It will ensure good job tracking. You don't have to pause and restart CA-7 after ENF is restarted.
Information for your CA-11 product:
CA-11 does not utilize ENF so you don't have to pause and restart CA-11 product after ENF is restarted.
Information for your CA Datacom product:
There is no need to pause and restart the MUF after ENF is restarted.
CA Datacom is only dependent on CAIRIM/CAMASTER components.
Information for your CICS:
There is no requirement to pause your CICS before/after ENF is restarted. If you are using ENF/CICS for
CA security products (CA-Top Secret or CA-ACF2), there won't be any security issues within your CICS regions.