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 Other
Created by Guest
Created on Dec 2, 2011

Locks missing from "DFH" CSD groups

As discussed in ETR Record 18196,999,616.

There are six CICS supplied DFH-prefixed groups in CICS TS 320 for which there is no lock record:
DFH$SOT DFHCBTS DFHDCTG DFHIPECI DFHRP DFHRPCF

There are four CICS supplied DFH-prefixed groups in CICS TS 410 for which there is no lock record:
DFH$SOT DFHCBTS DFHDCTG DFHRPCF

The existence of a lock record is identified when the group is listed by DFHCSDUP; "(IBM PROTECTED)" is shown after the group name.

Without the lock record it is possible to add, modify and even delete these CICS supplied DFH-prefixed groups. These groups should have lock records to protect them like the other CICS supplied DFH-prefixed groups.

I note that in the Resource Definition Guide it states that for DFHCBTS and DFHDCTG, "Note: This group is not protected by a lock. The definitions it contains can be modified if required." However, no such statement exists for the other groups. Either the groups should be locked or the documentation should indicate that they are intentionally not locked.

I would argue perhaps that all DFH groups should be locked, but that is another story.

The response in the ETR was "we agree that the issue of not locking these groups needs to be looked at, possibly as a requirement in the next release." As requested in the ETR, I have raised the requirement in this RFE.

Idea priority Low
  • Guest
    Reply
    |
    Oct 5, 2015

    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

  • Guest
    Reply
    |
    Dec 8, 2011

    It is true that two of the groups mentioned were erroneously unlocked in 3.2, but that was fixed by an APAR. Concerning the remaining four groups:
    DFH$SOT is for sample definitions (as implied by the $ symbol). It contains TCPIPSERVICE definitions that require changing prior to use. The documentation even instructs the reader to change those definitions.
    The documentation for DFHCBTS clearly states: "This group is not protected by a lock. The definitions that it contains can be modified if required."
    The documentation for DFHDCTG makes the same statement.
    The final group, DFHRCPF, only contains one definition, and that is for an example file. The DSNAME involved is "xxxxxxxx.CICSONC.RESOURCE". Clearly it needs customization before it can be used.