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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Servers and Systems Software
Product family - Transaction Processing
Product - CICS Transaction Server
For recording keeping, the previous attributes were:
Brand - WebSphere
Product family - Transaction Processing
Product - CICS Transaction Server
This requirement is satisfied by CICS TS 5.2 which is generally available from June 13th 2014.
This requirement is satisfied by CICS TS 5.2 which was announced 7th April 2014 with a planned general availability date of June 13th 2014. For more information see the IBM CICS Transaction Server for z/OS, V5.2 announcement letter
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS214-107
INQUIRE PROGRAM, SET PROGRAM, DISCARD PROGRAM, INQUIRE TRANSACTION, SET TRANSACTION, DISCARD TRANSACTION,INQUIRE SYSTEM, SET SYSTEM,INQUIRE DISPTACHER, SET DISPATCHER,INQUIRE MVSTCB are all now threadsafe.
This requirement is satisfied by CICS TS 5.2 which was announced 7th April 2014 with a planned general availability date of June 13th 2014. For more information see the IBM CICS Tools for z/OS, V5.2 announcement letter
http://www.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS214-107
INQUIRE PROGRAM, SET PROGRAM, DISCARD PROGRAM, INQUIRE TRANSACTION, SET TRANSACTION, DISCARD TRANSACTION,INQUIRE SYSTEM, SET SYSTEM,INQUIRE DISPTACHER, SET DISPATCHER,INQUIRE MVSTCB are all now threadsafe.
This is something we would like to address. The RFE is being moved into 'Planned for Future release' status. Please note:
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
Making the INQUIRE PROGRAM command threadsave would also help the IBM DEBUG product! The IBM DEBUG product is active in virtually all of my shop's test regions. Every time an application program does an EXEC CICS LINK to a program, IBM DEBUG gets invoked and issues an EXEC CICS INQUIRE PROGRAM command. Since this cmd is not threadsave, the task is frequently forced from the L8 to the QR mvs tcb. This wastes some cpu. but more important, this impacts me when I am doing analysis on what vendor programs I can/should mark as threadsafe, or required, to prevent tcb mode switches. With IBM DEBUG's repeated use of the EXEC CICS INQUIRE PROGRAM cmd, the number of tcb mode changes can be drastically different in a cics region running IBM DEBUG than in a prod region where we do not run IBM DEBUG. Making the INQUIRE PROGRAM cmd threadsave would eliminate this difference. Also, my shop also runs a vendor application that does an EXEC CICS INQUIRE PROGRAM once within every program it executes to obtain the address of a load module(which is used as a table of values). All other commands executed by this application are threadsafe. Making INQUIRE PROGRAM cmd threadsave would permit me to run this application's tasks/pgms completely on an L8 mvs tcb. I have asked the vendor to change the EXEC CICS INQUIRE PROGRAM to EXEC CICS LOAD PROGRAM to obtain threadsafe processing. But I do not know if they are going to make the change.
Making the INQUIRE PROGRAM command threadsave would also help the IBM DEBUG product! The IBM DEBUG product is active in virtually all of my shop's test regions. Every time an application program does an EXEC CICS LINK to a program, IBM DEBUG gets invoked and issues an EXEC CICS INQUIRE PROGRAM command. Since this cmd is not threadsave, the task is frequently forced from the L8 to the QR mvs tcb. This wastes some cpu. but more important, this impacts me when I am doing analysis on what vendor programs I can/should mark as threadsafe, or required, to prevent tcb mode switches. With IBM DEBUG's repeated use of the EXEC CICS INQUIRE PROGRAM cmd, the number of tcb mode changes can be drastically different in a cics region running IBM DEBUG than in a prod region where we do not run IBM DEBUG. Making the INQUIRE PROGRAM cmd threadsave would eliminate this difference. Also, my shop also runs a vendor application that does an EXEC CICS INQUIRE PROGRAM once within every program it executes to obtain the address of a load module(which is used as a table of values). All other commands executed by this application are threadsafe. Making INQUIRE PROGRAM cmd threadsave would permit me to run this application's tasks/pgms completely on an L8 mvs tcb. I have asked the vendor to change the EXEC CICS INQUIRE PROGRAM to EXEC CICS LOAD PROGRAM to obtain threadsafe processing. But I do not know if they are going to make the change.
Making the INQUIRE PROGRAM command threadsave would also help the IBM DEBUG product! The IBM DEBUG product is active in virtually all of my shop's test regions. Every time an application program does an EXEC CICS LINK to a program, IBM DEBUG gets invoked and issues an EXEC CICS INQUIRE PROGRAM command. Since this cmd is not threadsave, the task is frequently forced from the L8 to the QR mvs tcb. This wastes some cpu. but more important, this impacts me when I am doing analysis on what vendor programs I can/should mark as threadsafe, or required, to prevent tcb mode switches. With IBM DEBUG's repeated use of the EXEC CICS INQUIRE PROGRAM cmd, the number of tcb mode changes can be drastically different in a cics region running IBM DEBUG than in a prod region where we do not run IBM DEBUG. Making the INQUIRE PROGRAM cmd threadsave would eliminate this difference. Also, my shop also runs a vendor application that does an EXEC CICS INQUIRE PROGRAM once within every program it executes to obtain the address of a load module(which is used as a table of values). All other commands executed by this application are threadsafe. Making INQUIRE PROGRAM cmd threadsave would permit me to run this application's tasks/pgms completely on an L8 mvs tcb. I have asked the vendor to change the EXEC CICS INQUIRE PROGRAM to EXEC CICS LOAD PROGRAM to obtain threadsafe processing. But I do not know if they are going to make the change.