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 Under review
Created by Guest
Created on Apr 17, 2025

Please provide IMS components compatible with partitioning functionality

Please provide IMS components compatible with partitioning functionality

Would it be possible to have the IMS components make use of the PROFILE='IMS' and add the missing GENERATE PARTITIONING statements to take full advantage of the partitioning out of the box ?

As of now IMS components are delivered with PROFILE='GROWTH' stock from SDRLDEFS library and don’t allow us to use the partitioning functionality easily.
We must make custom versions in LOCAL.DEFS library of each IMS DRLx members to make them compatible. This doesn't simplify maintenance.

As far as I can tell, the PROFILE='IMS' could be made compatible with the provided DRLSYS.GENERATE_KEYS as the IMS tables all comes with the ‘MVS_SYSTEM_ID’ column and most with the 'IMS_SYSTEM_ID' column (the latter is the provided choice). Making use of PROFILE='IMS' would be more self-explanatory for IMS components users.

To make this compatible, one would require relying on the ‘MVS_SYSTEM_ID’ range column of DRLSYS. GENERATE_KEYS, which is already fully available within all IMS tables but not captured from the IMS LOG. However, one can SET this property in batch mode through the COLLECT CSQ* SYSIN.
Furthermore, the value for 'MVS_SYSTEM_ID' must be populated if you want to use the CP_IMS% tables as it is needed for the VIEWs and the Cognos framework to work.

Switching from not partitioned to partitioned would require to change value column ‘TABLESPACE_TYPE’ from ‘GROWTH’ to ‘RANGE’ for the PROFILE=IMS entry in DRLSYS. GENERATE_PROFILES table.

However, I realize that this request would go against what was modified in APAR PH41689 for tables CP_IMS_* and KPM_IMS_ATF_* due to the lack of column 'IMS_SYSTEM_ID' in these tables.

Here are the identified tables delivered stock with PROFILE='GROWTH':

TSNAME NAME_TS TYPE MEMBER_NAME PROFILE NAME_IX
-------- ------------------ ---- ----------- ------- ------------------
DRLSIA10 IMS_PSB_ACCOUNT_H G DRLSIA02 GROWTH IMS_PSB_ACCOUNT_HX
DRLSIA11 IMS_PSB_ACCOUNT_D G DRLSIA02 GROWTH IMS_PSB_ACCOUNT_DX
DRLSIA12 IMS_PSB_ACCOUNT_W G DRLSIA02 GROWTH IMS_PSB_ACCOUNT_WX
DRLSIT10 IMS_TRAN_H G DRLSIT01 GROWTH IMS_TRAN_HX
DRLSIT11 IMS_TRAN_D G DRLSIT01 GROWTH IMS_TRAN_DX
DRLSIT12 IMS_TRAN_W G DRLSIT01 GROWTH IMS_TRAN_WX

Same goes for the following tables and associated indexes:

  • CP_IMS_REGN_%

  • IMS_CHKPT_%

  • IMS_HALDB_OLR_%

  • IMS_PSB_ACCOUNT2_%

  • IMS_TRAN_QUEUE_%

  • IMS_SYSTEM_TRAN2_%

  • IMS_SYSTEM_TRAN_%

  • IMS_AVAILABILITY_%

  • KPM_IMS_ATF_%

Idea priority High