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 Future consideration
Categories Other
Created by Guest
Created on Dec 19, 2023

improve messages from DFH$MOLS job when they encounter "CONNECTOR NOT DEFINED" error.

It is not clear at all from current messages, when customers encounter the good old missing a dictionary record problem, when running the DFH$MOLS job.

They get something like: X'019E' - CONNECTOR NOT DEFINED; REPORT IS TERMINATED 

The reason for the error is because they had not created a dictionary record by running the DFHMNDUP  job for the region.   

But the customer expressed concern and we agree that the message is not at all helpful and provides no indication as to which 

region it was processing when it found the record with a x'019E' connector.   Including the region name or the applid involved in 

the error could be helpful, for messages U0108 ,  U0109 and U0110.   Customers can then check their DFHMNDUP jobs and rerun 

the DFHMNDUP job to create a dictionary record for the missing region.

 
 

Idea priority Low
  • Guest
    Reply
    |
    Dec 20, 2023
    CICS Development: This is a candidate for a future release.