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 Future consideration
Categories Runtime
Created by Guest
Created on Feb 14, 2022

CICS statistics fields sometimes turn negative or don't make sense

One of the fields this problem happens to is Storage Manager: Dynamic Storage Areas Statistics field SMSGMREQ ( Getmain Requests ). By common sense, this field should never be negative.

But the Cobol version of DFHSMSDS defines this field as signed:

PICTURE S9(8) USAGE IS COMPUTATIONAL

As the 4-byte native field that holds the number of getmains for a DSA increments from x'7FFFFFFF' to x'80000000' and beyond, products and programs that interpret this number report negative, or weird, and different results.

For instance, take the following raw field x'A08AC7CB'. The table below shows that raw field interpreted as unsigned, as signed, and it shows how different IBM programs and products interpret it.

Unsigned: 2,693,449,675
Signed: -1,601,517,621
DFHSTUP: 1517621
WUI: -1,601,517,621
CICSPA: -160151762
DFH0STAT: 1,601,517,621

You can see that each of these different products/programs has a different interpretation of the same raw field!

The ask for this requirement is that all statistics fields be defined as unsigned fields so that they will never be interpreted as negative, and that all statistics fields are sufficiently large such that they will never wrap back around to 0 before being reset.

Idea priority High
  • Guest
    Reply
    |
    Mar 2, 2022

    This is a candidate for a future release