There are a couple things to consider to have the most effective configuration. First, each LPAR that will be recording events for other CA products (like CA Jobtrac, CA 7, CA Scheduler, etc.) will have its own MUF running in LOCAL mode for CA ENF - using DBSIDPR setting CONNECT_ALLOW_PRIORITY=(LOCAL). If you are not recording events in ENF, then you would use the NODB and RECORD(NO) settings in your ENF startup, and you don't need a CA Datacom/AD MUF in that LPAR.
Then, if you have other products like CA Jobtrac or CA 7, the CA Common Services Best Practices Guide indicates that you should have a separate MUF for these applications, and that you should not share the ENF MUF with them. There are a couple reasons for this:
- The other applications usually run cross-LPAR, and need to use XCF, which ENF cannot use at this time.
- Having the ENF MUF running standalone allows you to use the IMUF configuration (the MUF runs in the ENF address space), which provides much better performance.
There is no issue with multiple MUFs running in an LPAR – one for ENF and one or more for other CA products; as long as they all have unique MUF and CXX names, they will work fine together.
To summarize and repeat:
- Each LPAR that ENF will record events needs its own LOCAL-only MUF, dedicated to ENF
- Other CA applications like CA Jobtrac or CA 7 or CA 11 can share a different MUF and use XCF.
As always, please contact CA Technologies support for CA Datacom if you have further questions.