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 Not under consideration
Workspace IBM i
Categories Networking
Created by Guest
Created on Jan 11, 2019

Eliminate an IPL when changing system name

Changing the system name via the CHGNETA command requires an IPL for the system name change to take affect. I would like to see this requirement removed and have the change either become active immediately, or after restarting TCP/IP services.

Use Case:

As part of our disaster recovery process, we need to rename our DR systems to match the production system name. Eliminating an IPL can reduce the recovery process time by 15-30 minutes. I think this DR process is a common requirement for other companies.

Additionally, we use a replication tool for our system migrations to new hardware. When we are ready to migrate onto the new hardware, we need to IPL to change the 'new" system to match the original system name. Removing the IPL would save 15-30 minutes from the migration process.

Idea priority Low
  • Guest
    Jan 14, 2019

    The IBM i network attribute for System name (SYSNAME) and the related parameters Local control point name (LCLCPNAME) & Default local location name (LCLLOCNAME) have a system wide dependency to only activate with an IPL.

    The system name is integral to the core design of the IBM i Base Operating System (BOS) as were its S/36 and S/38 predecessors.
    At its heart, the system name defines the SNA network name for the system,
    They are tightly coupled with the corresponding SNA communication controllers and devices.

    Additionally, there are many IBM i features and functions that utilize this configuration for internal functions as well as presentation (Display screens, spooled files, File systems, DDS, Database, etc).
    It is insufficient for the system to be brought down to a restricted state and Reclaim APPN (RCLAPPN) performed to reset the SNA communications portion of the change.
    There are system jobs that utilize this for their core function which require an IPL.

    The changes to dynamically allow the system name to change without an IPL is beyond the ability for the system to implement.

  • Guest
    Jan 14, 2019

    I've used several different replication products, and at no time did I ever have to swap the system name. None of the apps I had, have ever relied on the system name, and really when you think about it why should they? If you do have to use the system name you should use the IP host name. That you can change on the fly, and can be retrieved just as easily as the system name. I see the system name as something you set when you setup a new system, and then it's never changed again.


  • Guest
    Jan 14, 2019

    Hi All,

    I'm sure there are several Software Based HA Replication vendors (and perhaps more importantly) a significant subset of their customers would like to use this function as part of a Role Swap.

    I can imagine there are ramifications for changing this value whilst the system is in use. So, perhaps the change could take effect the moment a system was brought into a restricted state.