|
View previous topic :: View next topic
|
| Author |
Message |
rohanthengal
Active User
.jpg)
Joined: 19 Mar 2009
Posts: 206
Location: Globe, India
|
|
|
|
I want to know the difference between the term :
STEP ABNORMALLY ENDING.
If step returns RC = 4 and in the subsequent step i have coded COND=ONLY, then will that subsequest step work ?
IBM Manual says that COND=ONLY will work only if any of the previous step abnormally ends.
Requesting experts to explain me this. |
|
| Back to top |
|
 |
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Did you try this condition test before posting.
Clue - is a non zero RC an ABEND |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
| Quote: |
| STEP ABNORMALLY ENDING. |
Where did you see this?
Was there a message id associated with this?
| Quote: |
| IBM Manual says that COND=ONLY will work only if any of the previous step abnormally ends. |
Yes, this is true. You need to make sure that your understanding of "abnormally ends" is the same as IBM intended.
If some program detects something that causes the program to gracefully end while setting a return code (even if the program produces a message that the program is abnormally ending), this is not an IBM abnormal termination.
Keep in mind that a return code is neither a System abend nor a User abend. |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| Quote: |
| Difference between abnormal end, RC, ABEND |
If I go by your subject line then two terms "abnormal end" and "ABEND" are actually same. And RC is - Return-Code. JCL refers to the return code as COND ("condition code"), and can use it to decide whether to run subsequent steps. However, unlike most modern programming languages, conditional steps in JCL are not executed if the specified condition is true, that's why this is remembered as "If it's true, pass on through (without running the code).
Return code specifies how successful the program was. The most common conventional values are:
0 = all is well.
4 = minor errors or problems
8 = significant errors or problems
12 = major errors or problems
16 = very serious problems, do not use the results! |
|
| Back to top |
|
|
|
|
