Reason:
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.
Action:
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.
|
Copyright © 2014 CA.
All rights reserved.
|
|