RMOJCL report is receiving Proc Step not found in JCL.

Document ID : KB000045598
Last Modified Date : 14/02/2018
Show Technical Document Details

Problem:

We've run the program coded like this for years; 

//RMOJCL01 EXEC PGM=RMOJCL, 
// PARM='RMO.PROD,CHECK' 

It's come to my attention the RMOJCL report doesn't seem to be correct.  

There is a job that comes up with a 3J code, Proc Step not found in JCL. This code seems to be wrong. 
The proc is found, the step in the JCL and proc are correct, as is the sysout DD.

Environment: 

CA Deliver 12.1

Resolution:

The RMOJCL set up to simply look at job FSQ301, Jobstep SQ35, Procstep UA99, DD ACR, RPT SQ301-BAL1.

When running with the CHECK option, the documentation states: 
The keyword CHECK can be coded as the second subparameter of the PARM field on the EXEC statement (for example, PARM='DELIVER.SYSTEM1,CHECK') to compare job definitions in the database to the production JCL. 

So, it is looking at all the JCL and comparing to the definitions as they are in the Deliver database. 
In the RMOJCL output, do a find on the report mentioned SQ301-BAL1, scrolling over to the right, look at RC = 3J.

Then, max down and see a table in there: 


RMOJCL01 Explanation of reason code determined during PARM=CHECK processing 
RC first character: 
1) Job not found 
2) Step not found 
3) Proc step not found <--------------------------The error indicates 
4) DD name not found 
5) Omitted per 'OMIT' control statement 
RC second character: 
D) in database 
J) in JCL <--------------------------The error indicates 

This looks like that definition in your Deliver DB does not match what is actually in the JCL. 


The report SQ301-BAL! From DD ACR is listed under the member SQ301YE not member SQ301.

Additional Information:

 

As always, please contact CA Technologies support for CA View/Deliver if you have further questions.