After upgrading the CA Datacom/AD MUF to a new version, the CA Jobtrac application does not connect to the MUF and displays DB00121 and DB00122 messages about a connection to the wrong MUF.

Document ID : KB000047304
Last Modified Date : 14/02/2018
Show Technical Document Details

Issue:              

After upgrading to the new version of CA Datacom/AD for use with CA Jobtrac, the Jobtrac application cannot connect to this MUF and displays errors

+DB00121I - UNAVAILABLE - CA11MUF
+DB00122I - ACCESS TYPE - LOCAL,XCF(CA11GRP) TASKS=1
+DB00123I - WAITING FOR MUF AVAILABILITY
+DB00124W - REMAINING DELAY68 TIME - 2 MINUTES

Cause:

There are a few reasons why this could happen.

  1. Either you have a CUSLIB for the "old" CA Datacom/AD version in your LINKLIST
  2. Your CLIST has an allocation for the "old" CA Datacom/AD CUSLIB
  3. Your TSO proc has the "old" loadlibs allocated there.

In addition to these possibilities using the “old” MUF CUSLIB, you could also have specified the wrong MUF’s CUSLIB. Another remote possibility is that someone copied the DBSIDPR module from the “old” MUF CA Datacom/AD CUSLIB into some other loadlib, but this is very remote.

Resolution:

To correct this problem, you should check each of the above possibilities and make the necessary changes to your environment.

Additional Information:

Note that we do not recommend the use of Linklist for CA Datacom loadlibs, and have a Knowledge Base article that addresses this: TEC532058, titled "Does CA Recommend Using the LinkList for CA Datacom Libraries?"

As always, please contact CA Technologies support for CA Datacom if you have further questions.

***