IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Error explanation - RC status is 04


IBM Mainframe Forums -> FAQ & Basics
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
mitha

New User


Joined: 01 Dec 2021
Posts: 19
Location: India

PostPosted: Fri Dec 03, 2021 1:27 pm
Reply with quote

Code from "procedure name XXXX" to "YYYY" can never
be executed and was therefore discarded. It is showing as warning in my cobol program. And the RC status is 04. Can anybody share what to do for this to not show this warning in my program. I couldn't able to view my output in spool. Please anyone share your thoughts.
Back to top
View user's profile Send private message
Rohit Umarjikar

Global Moderator


Joined: 21 Sep 2010
Posts: 3053
Location: NYC,USA

PostPosted: Fri Dec 03, 2021 7:43 pm
Reply with quote

I assume it’s compilation warnings , Either Delete unwanted code or live with it . I would choose to delete unwanted , dead code. Moved to Students section.
Back to top
View user's profile Send private message
Phrzby Phil

Senior Member


Joined: 31 Oct 2006
Posts: 1042
Location: Richmond, Virginia

PostPosted: Fri Dec 03, 2021 8:04 pm
Reply with quote

A previous developer may have wanted to disable a functionality but retain the code for possible future use.
If so, s/he did it in a very sloppy way.
Better would be to comment it out with a suitable explanation.

OR -

The code is in fact intended to be executable, but erroneously cannot be reached, so the program is not meeting its (presumed) specs.
Back to top
View user's profile Send private message
Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8696
Location: Dubuque, Iowa, USA

PostPosted: Sat Dec 04, 2021 1:06 am
Reply with quote

The message means EXACTLY what it says -- a block of code lines cannot be executed and hence is not generating code in the load module for it. This could be deliberate, or it could be an accident. Since you have complained about no SYSOUT being generated, I suspect it is an accident. Ways this could happen by accident include:
- misplaced period
- PERFORM or GOTO coded wrong
- IF statement conditional is not conditional (that is, it is always true or false and hence one branch of the IF/THEN/ELSE statement could not be executed)
- improperly commented code (such as commenting out a statement that causes the block of code to be executed)

There are other possibilities, but those are certainly the most likely ones. In any case, the way you resolve this is to start reviewing the code looking for why the block of code is not executable. This is not something anyone on this (or any) forum can do for you -- we don't have your source code.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> FAQ & Basics

 


Similar Topics
Topic Forum Replies
No new posts Error to read log with rexx CLIST & REXX 11
No new posts Error when install DB2 DB2 2
No new posts Job completes in JES, but the status ... IBM Tools 1
No new posts CLIST - Virtual storage allocation error CLIST & REXX 5
No new posts Error while running web tool kit REXX... CLIST & REXX 5
Search our Forums:

Back to Top