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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Status "Wait Queue" on SMF record
Add the Wait Queue" statuses (WC, WP, WT, and WX) in the SMF records.
Retrofit the Enhancement Request CONDIRECTZ-I-8 "Provide control over who can use the SNODEID parameter" to CD v6.1
This idea CONDIRECTZ-I-8 "Provide control over who can use the SNODEID parameter" was previously raised for CDz CONDIRECTZ-I-8, and it was informed that it would be available in v6.1. However, after the upgrade to V6.1, it was informed that this e...
Propagate source DCB information to SNODE when using DATACLAS= keyword
The beauty of zOS-to-zOS COPYs is the inherent ability to automatically transfer the source DCB information to the SNODE side for proper dataset allocations. If the source DCB changes, the process does not need to be altered. This generic process ...
Write Debug Traces to a Specific DD instead of Creating Dynamic Rnnnnnn DDs
If the process specific Debug Traces can be written to a specific DD or DDs instead of creating dynamic Rnnnnnn DDs, it could be SPINNED dynamically after the trace completion and it will not cause a usage exposure to system SPOOL.
Security Exit must be usable by different SFTs and the STCname should be part of the RACF profile namess
In our environment we run several Connect:Direct stc's in one environment. The provided Security Exits do not offer a possibility to setup separate profiles for these stc's.We would like this to be changed. Second what we ask for is to add the STC...
Add CRL caching support to Connect:Direct z/OS v6.1
We have started to use CRL checking in CDZ via EASERVER and urgently need CRL caching to be in effect similar to what has been implemented for Windows/Linux platforms.
Open MCS.CLIST until either TCP or SNA support available
NDM modify commands will fail before local node sign on complete either via TCP or SNA, so open MCS.CLIST until either TCP or SNA support available is more appropriate especially for users who depend on modify command to monitor NDM.
Suppress the diagnostic data being written to CDESTAE for the SCPA019I error
We observed that there is a dump of the file in DD CDESTAE after the process failed with SCPA019I An input LRECL > output LRECL detected for compressed file. It is an exposure of business data so it would be appreciated if it can be disabled or...
Replace Notify option with email option
Not really a new idea. I am just passing along details on how one can issue an email or text message from an NDM task using RUN TASK PNODE (PGM=IRXJCL) -
Standardize Connect:Direct messages
Currently, Connect:Direct has multiple message qualifiers, making automation difficult. requirement is for the Connect:Direct address-space to use a consolidated standard message prefix
Do not place IBM confidential, company confidential, or personal information into any field.