Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. 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 Is a defect
Categories Runtime
Created by Guest
Created on Oct 9, 2019

Add Client IP address message insert to DFHWB0103

Similar to DFHWB0100 and DFHWB0101, issues resulting in DFHWB0103 can be diagnosed more quickly if the client IP address was output as a message insert.

Idea priority Medium
  • Guest
    Reply
    |
    Oct 21, 2019

    DFHWB0103 is issued when the web alias task has not been attached properly. It is missing the WRB entirely or the WRB eyecatcher is not correct. Both of these situations indicate an internal CICS problem and are not related at all to data sent in by a client. Identifying the client shouldn't make any difference at all.

    The correct cause of action is for the customer to capture a dump on the DFHWB0103 message with trace active (all components at 1 is enough) and raise a case to have it investigated.