z/OS MVS System Messages, Vol 3 (ASB-BPX)
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


ATB048E

z/OS MVS System Messages, Vol 3 (ASB-BPX)
SA38-0670-00

ATB048E
THE MAXIMUM NUMBER OF APPC ACTIVE CONVERSATIONS FOR ASID num1 HAS BEEN REACHED. APPC ACTIVE CONVERSATION THRESHOLD: num2.

Explanation

The APPC active conversations threshold specified by the CONVMAX parameter has been reached. No new conversations will be allowed to start in this address space until conversations have been deallocated or cleaned up.

For each APPC active conversation on the system, APPC reserves a certain amount of system storage. A runaway transaction program, which creates many conversations but never deallocates them, could potentially exhaust the fixed amount of this system storage that APPC has obtained. To inform the installation of such a program and to optionally prevent new conversations from being started up until the problem is solved, APPC allows the installation to specify a threshold that will cause APPC to take actions when this problem in encountered.

You can define the APPC active conversation threshold limit on the CONVMAX subparameter of the PARM parameter on the EXEC statement in the APPC member of SYS1.PROCLIB. The CONVMAX value is a 1- to 5-digit number indicating the maximum number of APPC active conversations a single address space can have before APPC prevents new conversations from starting in the address space, if CMACTION has been set to HALTNEW.

In the message text:
num1
The address space identifier.
num2
The APPC active conversation threshold.

System action

The system prohibits new conversations from starting in the address space identified in the message.

Operator response

Contact the system programmer.

System programmer response

Investigate whether the critical action console message is caused by a programming error in an APPC transaction program or by some APPC stress workload for this address space. A transaction program that allocates conversations but fails to deallocate them results in many dangling conversations, which could exhaust APPC storage.
  • If it is a programming error, cancel the problem transaction program, fix it and rerun it.
  • If it is not programming error, and the required number of conversations exceeds the conversation threshold limit for that transaction program, you can change the CONVMAX parameter to a reasonably higher value, and then rerun the transaction program.
When conversations have been deallocated from the address space, this condition goes away and the message is ended.

Module

ATBVSCM

Source

APPC/MVS

Routing Code

2

Descriptor Code

7,11

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014