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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
Thank you for raising this RFE. I hope that the suggestions we provided, will help you to get the checksum details you require.
Hi Curtis, Note that the CICS CM Package List view provides details of the Key Association Checksum as explained here:
• When a resource is packaged (i.e. the KEYASSOC record created) checksum x'00000000' is assigned to the KEYASSOC record.
The value of x'00000000' indicates that this is a Not ready, new object.
• When READY is performed, the definition on the CSD/context is read, a checksum calculated say x'8DA5BF65' to overwrite the KEYASSOC record's value.
• When MIGRATE occurs, as the resource is copied the KEYASSOC record is propagated for association with the target Config and the checksum reset to x'00000000'.
That is, for the target Config it is Not ready, new object.
• When READYLST processing occurs, the KEYASSOC checksum is compared to a recalculated checksum for the CSD/context definition:
• If KEYASSOC checksum is x'00000000' the packaged resource is shown as Not ready, new object
• If the CSD/context resource is not found, the packaged resource is shown as Not ready, object not found
• If the KEYASSOC checksum matches the CSD/context resource checksum, the packaged resource is shown as Ready
• If the KEYASSOC checksum does not match the CSD/context resource checksum, the packaged resource is shown as Not ready, object changed
So CICS CM is interpreting the checksum information for you and providing the status for each object. If you still need to review the Checksum for each resource in the list,
and the actual resources on the CSD you can use the Menu pulldown and Option 3 CICS Configurations - then review the resources by specifying the Group name for the
resources in the object list and using CHECKSUM FULL command to display the Checksums.
Please let us know if this helps.
Checksum facility is currently available only in report sections. In case of packages containing many similar definitions, there should be fast way to compare it (via checksum) directly within package (in object list) - to check if definitions are the same, or mistakenly contain some differences. Comparing it via reports is time-consuming and error prone. Suggested enhancement would dramatically improve/fasten package verification.