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 Not under consideration
Categories Runtime
Created by Guest
Created on Aug 14, 2013

CICS Transaction Gateway (CTG) - Transaction flow control

Have ability to issue command to turn off flow of work thru the CICS Transaction Gateway, at the Transaction Level.

/F T8DTGEZ3,APPL=TRANDIABLE,DRP1
/F T8DTGEZ3,APPL=TRANENABLE,DRP1
/F T8DTGEZ3,APPL=TRANSHOW

This would turn off workflow to the backend CICS regions in a coordinated fashion; returning a return code to the application indicating the backend systems are not available at this time.    The transaction could be added/removed to a Java HashTable to Disable/Enable respectively, with Log message indicating the activity for audit purposes.    Also and appropriate return code passed back to application request indicating processing for this transaction not avaliable.<br />Also a display of the contents of the transaction table.

Idea priority Medium
  • Guest
    Reply
    |
    Apr 21, 2017

    We have assessed this requirement. We have no current plans for this to be implemented and so this requirement is being declined at this point. The requirement will be kept in the RFE system and might be reassessed in the future. You also have an opportunity to resubmit in twelve months time if you wish it to be reconsidered then.

  • Guest
    Reply
    |
    Oct 5, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Enterprise Tooling
    Product - CICS Transaction Gateway

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Enterprise Tooling
    Product - CICS Transaction Gateway

  • Guest
    Reply
    |
    Sep 11, 2013

    Would rather see a dynamic enable / disable type of interface. This CA1T method requires the editing of a file; then refresh needs to be done.

    Would rather have something analgous to:
    ;
    CEMT SET TRANID
    rather than CEDA ALTER and CEDA INSTALL.

    Since the change of transaction state is only temporary and dynamic, each dynamic, single command to ENABLE, DISABLE and INQUIRE would be much more desireable. due to usability.

    To use this CA1T method the CTG technician, would need to write a batch rexx program to alter the file for each function and issue the refresh command,

    If could have simple single line command stream, like existing CTG Trace enable/disable would be desirable.

    Steve.

  • Guest
    Reply
    |
    Sep 10, 2013

    CA1T V3.0 added the ability to operate the transaction/program/user validation logic in EXCLUSIVE as well as INCLUSIVE mode. This allows the systems administrator to define list of e.g. TRANSIDs for which any matching ECI requests would be rejected. By editing the policy file and issuing a reload command, ECI requests can effectively be dynamically disabled by trans ID, program ID or user ID.

    For further information, see the CA1T V3.0 README PDF:

    ftp://public.dhe.ibm.com/software/htp/cics/support/supportpacs/individual/ca1t_v300.pdf

    Page 14 includes a description of how CA1T can be configured (with environment variable CTG_HAVALIDATION) to apply validation rules inclusively, or exclusively.


    Would this existing capability be adequate? Or are you specifically looking for this kind of feature to be integrated with DSSPOLICY (rather than CICS request exit)?

  • Guest
    Reply
    |
    Aug 22, 2013

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Enterprise Tooling
    Product - CICS Transaction Gateway
    Component - Runtime

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Transaction Processing
    Product - CICS Transaction Server
    Component - Runtime