Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Delivered
Created by Guest
Created on Mar 1, 2012

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.

Idea priority Medium
  • Guest
    Reply
    |
    Nov 19, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Development Tooling
    Product - IBM Application Performance Analyzer

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Tooling
    Product - IBM Application Performance Analyzer

  • Guest
    Reply
    |
    Mar 5, 2014

    We have completed initial research on this RFE which asks that threshold requests be able to trigger another measurement request.  That is, the ability to enter the TR line command against a Threshold request is required. We are considering this for APA v14 (or a APA v13 feature PTF).

    Our research determines that this is possible, but with a restriction for multi-step threshold requests. APA currently provides the ability to create both single-step and multi-step threshold requests. Multi-step threshold requests are created by entering an asterisk '*' in the Step No field in Panel 1, in which case APA will create a measurement for every step in the job that exceeds the threshold criteria. 

    This enhancement can support a trigger on a single-step threshold request. It can also support a trigger on a multi-step threshold request, however only the first step that exceeds the threshold criteria in a multi-step threshold request will initiate the triggered request.

    Please let us know if this solution satisfies your requirement.