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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Under review
Workspace IBM i
Categories Core OS
Created by Guest
Created on Mar 26, 2024

Use the Partition/System Name Consistently

The nomenclature SYSNAME is associated with the RTVNETA command since before Partitions existed. It is now often known as the System/Partition or LPAR name.

While IBM does display the System Name on UIM screens and menus, and stores it within created Objects, some interfaces such as SPOOLED files and SQL do not use this value and instead use the Local Control Point name or the RDB Directory Entry name respectively.

An SQL application can use the qsys2.system_status_info View's HOST_NAME column to obtain the actual system/partition name. However, the problem with SQL-only solutions is that it (A) it requires that the application be changed to an SQL compatible source member which adds overhead to the runtime. (evoking SQL vs a simple call to an MI instruction such as MATMATR1, not to mention the lack of SQL support within the CL language. Although I suppose you could use DCLF and RCVF to get the the SYSTEM_STATUS_INFO value.

As mentioned the MATMATR1 or the QWCRNETA API can be used to obtain the actual system/partition name but this request is for IBM to consistently use and assign this actual system/partition name in the following:

  • When an Object is created

  • As the Job system name where as SPOOLED file was initial created

  • As a new Special Register in SQL

  • As the "member added to file on system" system name.

It is not important whether you change the existing values to the system/partition name (unlikely) or create a new attribute that is the actual system/partition name in the above context. I assume it'll be a new attribute.

Idea priority High
  • Guest
    Apr 9, 2024

    I partially aggree to this request, but I would like IBM to take a broader approach.

    There already several different places you can enter a name and they can all be different:

    - System name in Network attribute (DSPNETA)

    - Local control point name in Network attributes (DSPNETA)

    - TCP/IP hostname (CHGTCPDMN)

    - Database name in the Relational Database Directory (WRKRDBDIRE)

    - LPAR name in the LPAR definition on the HMC.

    So introduce a new attribute is not the way to go.

    I would rather see IBM deprecate the use of the names from the Network Attributes (DSPNETA) completely, like System name, Local control point name, etc for non SNA applications.

    These names are legacy from SNA time and have a limitation of 8 characters.

    I think the correct name should be the TCP/IP hostname.

    A change would most likely break a lot of applications, so it needs to be rolled out during several releases, but as a first step maybe a settings if the legacy system name or the TCP/IP host name should be displayed on menus and screens.