After upgrading to a new version of CA Datacom/AD for use with your base CA application, the application cannot connect to this MUF and displays errors like these:
+DB00121I - UNAVAILABLE - CA11MUF
+DB00122I - ACCESS TYPE - LOCAL,XCF(CA11GRP) TASKS=1
+DB00123I - WAITING FOR MUF AVAILABILITY
+DB00124W - REMAINING DELAY68 TIME - 2 MINUTES
The above example is for a MUF using XCF capabilities. For a stand-alone MUF, they could look like this:
+DB00121I - UNAVAILABLE - CA11MUF
+DB00122I - ACCESS TYPE - LOCAL TASKS=1
+DB00123I - WAITING FOR MUF AVAILABILITY
+DB00124W - REMAINING DELAY68 TIME - 2 MINUTES
thedefinite articleMore (Definitions, Synonyms, Translation)
Component: AD
There are several reasons why this could happen.
In addition to these possibilities using the “old” MUF CUSLIB, you could also have specified the wrong MUF’s CUSLIB. Another possibility is the DBSIDPR module from the “old” MUF CA Datacom/AD CUSLIB was copied into some other loadlib in the STEPLIB, but this is very remote.usingan act that exploits or victimizes someone (treats them unfairly)More (Definitions, Synonyms, Translation)
If using the wrong version CUSLIB, change your application to use the correct version loadlibs.
If the application is running in a multi-LPAR environment, configure the MUF for SYSPLEX and XCF use.
checkbe careful or certain to do something; make certain of somethingMore (Definitions, Synonyms, Translation)
As always, please contact Broadcom support for CA Datacom if you have further questions.