Allow TR command with a Threshold request. Currently only works with SCHED request.

In an actual customer situation (Quest Diagnostics)- a batch job sends synchronous MQ requests to CICS. Generally the batch program runs in a few minutes. Occasionally, it runs for a very long time. The slowdown is likely in the CICS transactions.

We need to define a TR request against a THRESH (TNEW) request. When I tried this on V10, it appeared to work. However, when I tried to save the request, it failed with "Invalid Request". F1 Help indicated "The request failed. Reason: Triggered request cannot be added , associated
Triggering request status is invalid."

Allowing this request to be entered would solve the problem.

Explanantion: “TR” Create a new request to be Triggered when this request starts. This can only be used on a request that is in SCHED status. (This is part of the APA User's Guide.) So, if a batch job sends data to CICS, then we can initiate an APA session on the CICS region, when the batch job starts. The TR (Trigger) Command is used to initiate an APA session based on the initiation of another event.
However, it does not make sense to run APA against every job. The MQ transactions are synchronous. If CICS can not process the MQ request (waiting on some sort of resources), it makes sense to initiate APA. This can be determined, since the batch job runs longer than anticipated. Therefore, TNEW request against the job will detect when the job runs too long, and the TR request will initiate an APA session tracking the CICS transaction.