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 Delivered
Categories Runtime
Created by Guest
Created on Aug 16, 2016

CICS Install job DFHCOMDS should allocate DFHCSD with secondary extents

The CICS installation process only allocates a primary
space for the DFHCSD in the DFHCOMDS job which creates the
DFHCSD dataset.

Looking back it seems this has been the case for some time.
I looked at the 5.3 DFHCOMDS job, and can see it still does
the same thing:
DEF CLUSTER(NAME(@dsindex@.DFHCSD) -
IXD -
REC(12000)-
RECORDSIZE(200 2000)-
FREESPACE(5 5)-
VOLUME(@dsvol@) SHR(2)) -
.
The CICS TS 4.2 doc and the 5.3 doc both contain a section:
Initializing the CSD
For the 4.2 kc, see url:
http://www.ibm.com/support/knowledgecenter/SSGMCP_4.2.0/com.ib
m.cics.ts.doc/dfha2/topics/dfha2_initialize_csd.html
.
This section: "Initializing the CSD"
has a subsection entitled: Creating a larger CSD
That tells customers
"To avoid the CSD filling while CICS is running, ensure that
you define the data set with primary and secondary space
parameters, and that there is sufficient DASD space available
for secondary extents."
.
So looks like we are not following our own advice.
This is probably the same for all versions.

Idea priority Medium
  • Guest
    Reply
    |
    Jun 16, 2017

    This RFE is satisfied by CICS TS 5.4 which is generally available from today June 16th 2017.
    For more information see the announcement letter https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS217-113

  • Guest
    Reply
    |
    May 16, 2017

    This RFE is satisfied by CICS TS 5.4 which was announced on May 16th 2017 with a planned general availability date of June 16th 2017.
    For more information see the announcement letter https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?infotype=an&subtype=ca&supplier=897&letternum=ENUS217-113

  • Guest
    Reply
    |
    Oct 11, 2016

    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.