The developer is trying to breakpoint an MQ message initiated transaction with CA Intertest for CICS. The problem is more than one task with that transaction identifier can be spawned. The system jams up first on transaction with eckwaits and then a maxtask ensues when other transactions are invoked.
The MUS= parameter can be used to limit the number of times a program is monitored. This parameter is outline in the CA Intertest for CICS Users Guide.
MUS: Limit the Number of Times a Program Is Monitored
To limit the number of times a program is monitored, enter:
MUS=limit
limit Specifies the number of times a program is monitored. Replace limit with a decimal number from 1 to 65,534.
..
For example
Please have the programmer setup their program as they currently are doing. Then at a clear screen in CICS add the MUS=1 option with the command below.
CNTL=ON,PROG=PGMNAME,MUS=1
The example below is for the COBDEMO program
If you do a breakpoint inquiry on COBDEMO you will notice that the limit is set to 1 with zero for number of times monitored. MUS=(00001,00000)
COBDEMO For userid .ANY
Symbolic file is PROTSYM
MUS=(00001,00000)
Abend Intercept ABI=ON
UBP offset= +00BFE at=#1
from=U005 to=U005
SLB terminal is U005 - Source Listing Breakpoints are on.
Listing window: Titles.
AutoKeep Display is ON
Code Coverage is OFF
* Entry not active
* End of Report *
If you then run the COBDEMO program and inquiry again you will now, see the program was monitored one time. MUS=(00001,00001)
COBDEMO For userid .ANY
Symbolic file is PROTSYM
MUS=(00001,00001)
Abend Intercept ABI=ON
UBP offset= +00BFE at=#1
from=U005 to=U005
SLB terminal is U005 - Source Listing Breakpoints are on.
Listing window: Keep.
AutoKeep Display is ON
Code Coverage is OFF
* Entry not active
* End of Report *
After that if you run the COBDEMO program you will not get breakpoints.
You will have to turn monitoring off for the program and back on again to reset the MUS=LIMIT.