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
Created by Guest
Created on May 11, 2023

Reduce CLNO errors by adding a parameter to cause the retries to be done over a reasonable time interval, instead of all within one second

Currently, if there is high activity in the datastore task, the 10 retries done when trying to retrieve the joblog all occur within one second, if a slight wait were introduced, the CLNO error could be avoided.

For example from the case mentioned: 

03/22 11.04.35 EQQE036I JOB TMFCATG3(J0064331), OPERATION(0020),

03/22 11.04.35 EQQE036I OPERATION TEXT(TEST 020 TMFCATG3 ), ENDED IN ERROR JCL

03/22 11.04.36 EQQM938W JOBLOG TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.36 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.36 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.36 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.36 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.36 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.37 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.37 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.37 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.37 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.37 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.37 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

03/22 11.04.37 EQQM643W OPERINFO FOR TMFCATG3 (J0064331) NOT RETRIEVED. REASON: 0001

As shown all the retries were done within 1 second, with WINTERVAL set to 1.  If the retries were

only done once per WINTERVAL value, or if a parameter were provided to cause a WAIT of xx seconds

between retries, the CLNO error could be avoided.


 

 

 

Idea priority Medium