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 Nov 19, 2018

Allow INITPARMs to be specified on PLT entry; allow > 60 characters

Allow an INITPARM string to be specified on the DFHPLT TYPE=ENTRY card for the program it is to be associated with. This is to accomplish three principal objectives: (1) Place the INITPARM text in the same parmlib member as the associated program name, rather than being separated to the SIT input; (2) overcome the current 60-byte limitation, via continuation syntax on the DFHPLT TYPE=ENTRY macro statement; and (3) allow the same PLT program to be invoked multiple times, with different INITPARM strings.

The EXEC CICS ASSIGN INITPARM command should be able to return an INITPARM string from either the SIT (for compatibility purposes) or from the DFHPLT TYPE=ENTRY statement.

This is a follow-on to RFE 115241, delivered with CICS TS 5.5.

Idea priority High
  • Guest
    Reply
    |
    Feb 10, 2022

    This requirement has been re-assessed. It is not likely that this will be implemented in the near future and so it 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
    |
    Feb 4, 2019

    Our primary interest in this RFE is for allowing multiple invocations of the same PLT program, with a different parm string presented each time. Since exceeding the current 60-byte length limit would require a different mechanism (e.g., channel/container), we would be open to retaining the 60-byte limit, if that would simplify implementation/delivery. A continuation syntax could be designed into a PLT program anticipating a longer parm string, whereby the program would concatenate parm strings from successive calls, and perform the intended processing once the final substring is received (e.g, containing a termination character/string, or lacking a continuation character).