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 Jun 14, 2024

Issue another message if job is Auto Recvered - EQQE036I replaced by EQQE036A

Issue another message if job is Auto Recvered - EQQE036I replaced by EQQE036A

EQQE036I message replaced if auto recovery is in job and error code tested for is in play. EQQE036I should only be issued when the job ends in error queue and will not be auto recovered (anymore). If this is the case, EQQE036I indicates, that the job is in error and will not be recovered. EQQE036A indicates, that the job has an error and is being Auto Recovered (this is a suggestion).

Example:

 //TESTJOB  JOB (336000,00),'PROD',                                    

//         CLASS=4,                                                  

//         MSGCLASS=G,                                               

//         REGION=0M                                                 

//*                                                                  

//EQQDELDS EXEC EQQDELDS                                             

//*---------------------------------------------------------------   

//* OPC KOMMANDOER TIL AT LAVE AUTOMATISK RECOVERY.                  

//*---------------------------------------------------------------   

//*%OPC SCAN                                                         

//*%OPC RECOVER JOBCODE=1234,ERRSTEP=IEFBR14,                    

//*%OPC RESSTEP=IEFBR14,RESTART=Y                                

//*  

//IEFBR14  EXEC PGM=IEFBR14

//*==============================================================

 

If the unlikely happens, that STEP=IEFBR14 ends with errorcode 1234, then OPC Controller issues:

00.56.33 STCnnnnn  EQQE036I JOB TESTJOB (JOB12345), OPERATION(0001), ENDED IN ERROR 1234.  092

   092               PRTY=9, APPL = TESTING        , WORK STATION = CPU1, IA = 2406141300

And then the job will be resubmitted (and probably ends with same error code) issuing another:

00.57.33 STCnnnnn  EQQE036I JOB TESTJOB (JOB67890), OPERATION(0001), ENDED IN ERROR 1234.  092

   092               PRTY=9, APPL = TESTING        , WORK STATION = CPU1, IA = 2406141300

The idea is, that since IzWS already nows, that if the jobs ends with error code 1234 it will be recovered 1 time. Then it should be possible to issue another message instead of EQQE036I. In example:

 00.57.40 STCnnnnn  EQQE036A JOB TESTJOB (JOB12345), OPERATION(0001), AUTORECOVERED.  092

   092               PRTY=9, APPL = TESTING        , WORK STATION = CPU1, IA = 2406141300

Idea priority High
  • Guest
    Reply
    |
    Jun 17, 2024

    This could greatly enhance our user experience with the ITSM systems system automation and possible other solutions to handle these type of automatic reruns.