Skip to Main Content
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.

Status Delivered
Workspace z/OS
Created by Guest
Created on Mar 27, 2023

Message "EZD1314I TCP/IP AND EXTENDED SERVICES ARE NOW INITIALIZED FOR STACK" not living up to its expectations

EZD1314I is supposed to tell us that TCPIP is ready and waiting for work and that it's ok to start applications that depend on TCPIP to be fully active. We wait for EZD1314I to appear at IPL time and yet our TN3270 servers kick out error message "EZZ6011I TN3270E BPX4CON FAILED, RC = 0000045E RSN = 76630000" which indicates routes aren't available (yet). The situation eventually clears but this is a false alarm.

Idea priority High
  • Guest
    Reply
    |
    Aug 23, 2024
    This was addressed via doc update to 2.5 and 3.1. Updates were made to the message text for EZD1314I and to the IP Diagnosis Guide to clarify the processing.
  • Guest
    Reply
    |
    Apr 6, 2023
    If I understand your text correctly, this is working as designed. The "all TCP/IP subsystems" message processing doesn't check for OMPROUTE directly because it doesn't necessarily know if OMPROUTE will be running (not all customers use dynamic routing) and also even if OMPROUTE is running, there really isn't a way to tell when the routing table is completely populated. However your workaround of using MONINTERFACE DYNROUTE is exactly how we expect users to get around that issue because one of the things that this initialization message looks for is that dynamic VIPAs and sysplex are initialized. Since MONINTERFACE DYNROUTE prevents joining the Sysplex until there is at least one dynamic route over the monitored interfaces, the fact that the processing for this message waits for sysplex initialization is the way to make it wait for dynamic routes.

    We will accept this requirement and fulfill it with a documentation update explaining this aspect better.