Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Submitted
Workspace z/OS
Categories LE
Created by Guest
Created on Apr 16, 2025

Better control of STACK and HEAP allocation in CICS.

We want better control of the AUTODST parameter behaviour in CICS.

 

We want to be able to control the maximum initial and incremental sizes.

We also want to be able to control the percentage of the expected total sizes that goes to initial and incremental sizes.

I.e.

 

AUTODST=(YES,20,10,5M,3M,10,10,10M,4M)

 

YES => Auto tuning is on.

20    => Percentage of the measured total STACK size to be allocated for the initial STACK

10    => Percentage of the measured total STACK size to be allocated for the STACK increments

5M   => Maximum amount of storage that AUTODST can calculate for initial STACK  size

3M   => Maximum amount of storage that AUTODST can calculate for incremental STACK  size

 

10      => Percentage of the measured total HEAP size to be allocated for the initial HEAP

10      => Percentage of the measured total HEAP size to be allocated for the HEAP increments

10M  => Maximum amount of storage that  AUTODST can calculate for initial HEAP  size

4M     => Maximum amount of storage that AUTODST can calculate for incremental HEAP  size

 

The Minimum sizes should taken from the Language Environment runtime options.

 

Examples:

if AUTODST have found the an enclave has a total stack size of 50mb and heap size of 100Mb, the actual sizes would be

In the examples we assume that we have

HEAP=((128K,64K,ANYWHERE,KEEP,4K,4080),OVR),  

STACK=((128K,64K,ANYWHERE,KEEP,4K,4080),OVR)

 

 

20% of 50mb=10mb, maximum initial stack 5mb                                  => Initial stack 5mb.

10% of 50mb=5mb,   maximum incremental stack 3mb                    => Increamental stack 3mb

10% of 50mb=5mb                                                                                                     => Initial heap 5mb

10% of 50mb=5mb maximum incremental heap 4mb                        => Increamental heap 5mb

 

if AUTODST have found the an enclave have a toal stack size of 20mb and heap size of 1Mb, the actual sizes would be

 

20% of 20mb=4mb,                                                                                                    => Initial stack 4mb.

10% of 20mb=2mb,                                                                                                    => Increamental stack 2mb

10% of 1mb=102k,                                                                                                      => Initial heap should be taken from LE-runtime options =>128K

10% of 10mb=102k                                                                                                   => Increamental heap 102K

 

This should be applicable for the HEAP and STACK in 31-bit storage.

The calculated sizes should be rounded up to nearest 4k boundary.

For larger extents(>500K) it may also be desireable to round to nearest 1mb boundary. This could be applicable when using TRANISO=YES.

 

Idea priority Medium
  • Guest
    Reply
    |
    Apr 16, 2025

    I want to make it clear that

    1) CICS AUTODST as it stands today is hard to use if not practical to use. This doc explains why: not DFHSM0133 short on storage after setting AUTODST ON (ibm.com) explains the AUTODST issues.

    2) Discussions with the CICS and LE teams made it clear that this an LE function and not CICS. So, the IDEA should be assigned to z/OS LE