Skip to Main Content
IBM Power Ideas Portal


This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. 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
Workspace IBM i
Categories Db2 for i
Created by Guest
Created on Apr 26, 2017

Add who created PF and LF members in DSPF command

For security as well as maintenance/cleanup reasons, it would be helpful to know the user name associated with creating members within a physical and/or logical file.


Use Case:

When a duplicate member was present in a control file that is used for End of Day/Week/Month/Year functions, it caused our process to go into a status of message wait (MSGW). Since we run separate EOD functions for the different divisions within our company, we couldn't just remove the member as we could cause another process to fail, and possibly corrupting processes that involve General Ledger, Payable, Receivables, etc. After several hours of trying to investigate who had created this member, we ended up desk checking the many programs that lead up to this error. We found that an OVRDBF was not present to point to the correct member for this particular process. Had we known who had created the member, then we would've found this error in a significantly shorter amount of time.


Idea priority Low
  • Guest
    Reply
    |
    Mar 23, 2021

    IBM does not intend to provide a solution to this request at this time, so it is being closed. The database team has many higher priority requirements, so this request is not likely to be implemented anytime soon.

    There is an alternative approach for accessing this information. If the file is journaled, the creator of the member can be found by looking for the associated F-MC journal entry.

  • Guest
    Reply
    |
    Apr 22, 2020

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - Db2 for i
    Operating system - IBM i
    Source - None

    For recording keeping, the previous attributes were:
    Brand - Servers and Systems Software
    Product family - Power Systems
    Product - IBM i
    Component - System Management
    Operating system - IBM i
    Source - None

  • Guest
    Reply
    |
    May 1, 2017

    This would be a useful modification, albeit a low priority one.

    Recategorized by T Duncan

  • Guest
    Reply
    |
    Apr 27, 2017

    From my experince I found that it is better not to use multiple members DB Files, other than storing Source Members.

    If You develop an application that is using multi-member DB files, here are the thiing You get stuck:

    1. Logicals: When You create a logical that includes all members, when a new member is added, The logical does not get updated automatically.

    2. Limit of 32 members that a logical is based on.

    3. Limim of 32000 logical members.

    4. SQL does not use members directly.

    Back in the System38 days, IBM was very excited about members, but did not continue to develop it.