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 General TM
Created by Guest
Created on Jan 26, 2024

Lock Manager incompatibility between PI and IRLM

We are implementing IMSPLEX configuration for a customer (see diagram attached). Currently we have IMSP instance running on MVS2 LPAR and we are going to add IMSO (IMSP clone) into another new LPAR, using Shared Databases and Shared Queue. See details in teh attached presentation. The current IMSP is still using Program Isolation (PI) and we know the first step to IMSP participate in a IMSPLEX configuration is to migrate to IRLM.

Before migrating IMSP to IRLM, we brought IMSO up on MVS4 with no workload (No BMPs, No MPPs) to fix and improve any wrong parameter in the IMSO. IMSO is using already the IRLM. 

After few days alive, one of the IMS database online reorganization jobs issued a /STA DB command for some databases and the databases became unavailable for IMSP and IMSO (DFS047A unauthorized). see details in the attached word. We took a while to realize the issue was caused by PI-IRLM compatibility since the messages are not clear. Meantime, the production environment was unavailable for the users.

My suggestion is to create a clear message for PI-IRLM incompatibility for the futures sites still using PI and migrating to IMSPLEX with database sharing. 

Idea priority Low
  • Admin
    Carol Degrace
    Reply
    |
    Jun 18, 2024

    Unfortunately, we are going to reject this idea because we believe a doc change is sufficient for this and as mentioned in the Case, a doc change has been submitted as follows:

    In the 'Programmer Response' section from the section of the IMS manuals that explain the DFS047A message, which can be found here -

    https://www.ibm.com/docs/en/ims/15.3.0?topic=dfs050a-dfs047a

    The following text will be added:

    >>> - The incompatibility between the requested state and the current authorization state

    may be caused by the use of different Lock Managers (PI vs IRLM) when accessing

    the same database from different IMS subsystems. For more information, see https://www.ibm.com/docs/en/ims/15.4.0?topic=requirements-data-sharing-software.

    (RC 01) <<<