I am running Datacom/AD for use with CA 11. My CAL7 started task shows the DB00139I message.
What does it mean?
This is part of my CAL7 STC Jes log:
DB00135I - CONNECT TO DATACOM ADMUF12P STC18251 SYS4 R12 SP0 0008 R12 SP0
DB00101I - STARTED JOB-CAL7 NUMBER-50767 CXX=AD12CXX MUFNAME=ADMUF12P SVC=246
DB00118I - XCF TOGROUP=P12GRP01 SYSTEM=SYS4
DB00139I - XCF REQUESTS 3 ERRORS 0 0 0 0
DB00136I - DISCONNECT DATACOM ADMUF12P STC18251 SYS4 R12 SP0 0008 R12 SP0
In your case, the DB00139I message is informational, showing that there were three XCF requests made by CA 11 to the Datacom Multi-user (MUF) at that time. It also shows that there were no errors with any XCF request.
When CA 11 is not running on the same Lpar as the Datacom/AD MUF, you are employing XCF to communicate with the MUF. The Datacom/AD MUF resides on SYS4 Lpar while CA 11 is running on SYS9 Lpar and the DB00139I message is occurring, as expected, on your CAL7 that runs on your SYS9 Lpar.
The CA-Datacom/DB Message Guide documents DB00139I as follows:
XCF REQUESTS n1 ERRORS n2 n3 n4 n5
The message can be displayed when an application has closed all URTs. The message is only displayed if XCF was used. Each CA Datacom/DB request in these statistics represents one XCF message-send request. In the message text the following apply:
The n1 indicates the number of CA Datacom/DB requests (using XCF) issued by the application.
The n2 indicates the number of times a CA Datacom/DB request failed (with a return code of 68 or 86), after all retries, because of XCF environmental problems.
The n3 indicates the number of times a CA Datacom/DB request failed due to a system shortage of XCF buffers.
The n4 indicates the number of times a CA Datacom/DB request failed due to busy XCF signaling paths.
The n5 indicates the number of times a CA Datacom/DB request failed due to other XCF system environmental problems.
Sending a CA Datacom/DB request to the MUF using XCF is attempted (retried) multiple times before failing. The total number of retries before failing is indicated by n3+n4+n5.
Large numbers of XCF environmental errors seriously degrade the performance of XCF-based applications and can have a negative impact on the performance of the entire SYSPLEX. From a performance viewpoint, however, small numbers of these errors are probably not going to be noticed,
In z/OS environments, use the z/OS console command, D XCF, with various parameters, to determine the current system XCF parameters.
None. This message is for information only. However, it may be necessary to address large numbers of errors, if indicated by the previously described statistics.