I am running the ENFIMUF procedure, and I see some "DB01922W - BEST PRACTICE SUGGESTION " messages. Do I need to update the MUF options to fix these, and what settings do I use?
Release : 15.1
Component : Datacom/AD
For the Best Practices, the first thing to note is that the full developer product - Datacom/DB - is often used with hundreds or thousands of tables with a variety of lengths and sizes, and with a MUF that has some very high transaction rates. In these systems, optimum performance over all areas of the MUF is critical to the success of the business.
However, with Datacom/AD, there are often only a small handful of databases, and the design of this environment means the end user has little or no control over some of the table attributes or database definitions. In addition, the Datacom/AD configuration we supply was established by internal development here to be more than adequate to support the various products using the database.
As a result, while there is some optimization and tuning you can make to your Datacom/AD system, the limited usage of your MUF means that some of the Best Practices will not provide much, if any, benefit to you, and in fact, could recommend changes to settings that work against your goals. Here are those suggestions with my comments for your ENF MUF (note that this could be different with other Broadcom products in use):
6) DATAPOOL DATA2 LT 1000, TARGET 1K-20K
>> Since you are only using one application database with ENF, there is no need to allocate any extra buffers in memory for other larger databases. This setting is fine and the message can be ignored.
24) HISTORY MISSING
>> While this is quite useful in tuning the database tables for in-house applications using persistent data, it really does not offer any benefit to transient data like that in ENF. This setting is fine and the message can be ignored.
25) LOGRCV SET AS YES/NEVER
>> Again, with ENF, there is no need to capture transaction log data for a forward or backward recovery, and the Common Services/ENF documentation direct you to use NEVER. This setting is fine and the message can be ignored.
31) LOG_RECORD_USER_CMPRS NOT YES
>> Since you are not using LOGRCV, this is not relevant. This setting is fine and the message can be ignored.
26) LOG_ROLLBACK_RECORDS LESS THAN 2000
>> With CA ENF, the nighty purge process is the only one that might have a possibility of being a "long transaction". This setting only benefits you if this purge process fails and the purged records need to be restored. This is not likely to be any problem for you. This setting is fine and the message can be ignored.
27) LOG_ROLLBACK_MINUTES LESS THAN 5
>> As above, this is not relevant to CA ENF. This setting is fine and the message can be ignored.
14) PXXSTATS NOT EOJPRT, TARGET EOJPRT
>> Because you are running the MUF inside the ENF address space using the IMUF configuration, this option does not provide any significant benefit to you. This setting is fine and the message can be ignored.
20) SYSPOOL IXX LT 1000, TARGET 10K-20K
21) SYSPOOL DXX LT 1000, TARGET 10K-25K
>> The nature of ENF processing and the use of its data means that allocating more memory blocks to hold more index entries in memory may not be very beneficial to you. This setting is fine and the message can be ignored.
In summary here, these messages do not indicate any problem, and there is no action needed for you on them. Although we do not recommend this, if you want to suppress these Best Practices messages (for these and any future messages that could be more relevant), you can add this setting to your MUF Startup Options in the AXDATIN1 member:
MESSAGE NO,DB01922 TURN OFF BEST PRACTICE SUGGESTIONS
Once you make this change, the next time you start your ENFIMUF task, these messages should not be seen.
As always, please contact Broadcom support for Datacom if you have further questions.