IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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.

Add a new idea Subscribe
Status Not under consideration
Workspace z/OS
Categories Communications Server
Created by Guest
Created on Nov 29, 2025

RELATED IDEAS

Create a command that will permit do a clean up and force the PORTNAME

We have two environments that share the same OSA card, but they were codified with different PORTNAME, then when the first came up, a PORTNAME was defined, when the second came up, it don't work because it was using a different PORTNAME. The solution is set the same PORTNAME, deactivate the majornode, addresses assigned to the OSA and their respective chpids, including vary off/on inside of the HMC. A couple of weeks ago we opened the case TS020828664, where we did all this process with no success, we performed these actions including IPL's but nothing changed the PORTNAME. Then I introduced a different TRLENAME, a new IPL and after that the issue was fixed. I understood that until we maintained the same TRLENAME, for some reason the system ignored all actions performed by us, when we changed the TRLENAME, some pointer or any other thing like that, change the system behavior and we finally get a fix.

Idea priority Low
  • Guest
    Jan 20, 2026
    This a procedural issue rather than a requirement for a new function, as explained below.

    An OSA TRLE cannot be activated (ACT) or inactivated (INACT) using a VTAM modify command. The OSA TRLE will show an INACT status when the interface at the TCP/IP layer is not started. It will automatically change to ACT status once the OSA interface is successfully started at the TCP/IP layer.
    To modify a VTAM TRLE for OSA connectivity, the TRLE state must be inactive from a VTAM perspective. When the last TCP/IP OSA interface using that TRLE is stopped, the control READ and WRITE associated with the OSA TRLE keep the TRLE active for two minutes. Therefore, you must wait two minutes before the OSA TRLE becomes inactive. Once the VTAM TRLE state becomes inactive, then you may modify the TRLE definition in VTAM to make the portname change.

    For future changes to the VTAM TRLE, try the following:
    1. Stop all the interfaces at the TCPIP layer that reference the TRLE majornode.
    2. V TCPIP,tcp_jobname,STOP,interface_name for each OSA interface using the TRLE.
    3. Wait 2 minutes (This is required to allow the OSA control channels (READ/WRITE) to quiesce.)
    4. Display the OSA TRLE to ensure the OSA TRLE has become inactive:
    - D NET,ID=TRL_majornde_name,E
    - Verify the OSA TRLE displays STATUS = INACT
    5. Once the TRLE is inactive, you may proceed to modify your OSA TRLE definition.
    6. Update the TRLE major node as follows:
    - V NET,ACT,ID=TRL_majornde_name,UPDATE=ALL
    7. Start your interfaces:
    - V TCPIP,tcp_jobname,START,interface_name

    The IBM z17 introduced the Network Express feature as the next generation ethernet adapter (ie OSA) and RoCE adapter. The Network Express provides the functionality of both the OSA-Express feature and RoCE Express feature into a single adapter.
    The OSA CHPID type for the Network Express feature is OSH. The new OSH interface no longer requires a portname (like the OSD interfaces) so this becomes a non-issue with the new Network Express features starting on IBM z17. In fact, the VTAM TRLE for the OSH connectivity is dynamically built by VTAM when the OSH interface is started removing this network administrative task.
    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.