MVSFORUMS.com

pradeepg

Hello List,

Is the reserve word RETURN-CODE would be set after each COBOL or DB2 instruction has been executed.

Suppose my code is like this

Move 08 TO RETURN-CODE
CLOSE OTFILE

**** What does RETURN-CODE will contain at this point ???

MOVE 12 TO RETURN-CODE
EXEC SQL
COMMIT
END-EXEC

**** What does RETURN-CODE will contain at this point ???

Appreciate your responses.

- Pradeep

kolusu · Posted: Mon Aug 22, 2005 4:37 pm Post subject:

pradeepg,

It does not matter how many times you move values to the return-code. The last value moved before your program completion will be the condition code of that step.

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

pradeepg · Posted: Tue Aug 23, 2005 1:54 pm Post subject:

So that means any other COBOL statement would have no effect on this reserve word other than execlusively moving some value into it.

One of our colleague is saying before executing an SQL statement it has the value what ever he had moved, but after succesful execution of the SQL the value in the RETURN-CODE has changed to 0. So wondering any other statement's succesful execution would cause this value to become 0.

Thanks,
Pradeep

kolusu · Posted: Tue Aug 23, 2005 2:05 pm Post subject:

Phantom · Posted: Tue Aug 23, 2005 11:17 pm Post subject:

pradeepq,

Just check with your colleague if he is having a sub-program to execute the SQL statement. In that case, the sub-program would have manipulated the value in RETURN-CODE.

Thanks,
Phantom

Bithead · Posted: Wed Aug 24, 2005 7:31 am Post subject:

I tried it. I set the return code to 1 and executed an SQL call. The return code was set to 0 after the call.

kolusu · Posted: Wed Aug 24, 2005 7:47 am Post subject:

Bithead · Posted: Wed Aug 24, 2005 8:13 am Post subject:

But it does show that the RETURN CODE is modified.

pradeepg · Posted: Wed Aug 24, 2005 1:38 pm Post subject:

I tested myself and confirmed that after SQL statement execution, the RETURN-CODE value would change to ZERO. I think the reason has been explained by Kolusu. It is also documented in COBOL manual.
Because SQL statement converts to CALL statement so the subroutine is setting this value back to zero.

- Pradeep