Passing Return Code to PROC

Mr.Niceguy · New User Joined: 16 Jun 2005 Posts: 63

Hi Guys,

Anybody tried passing the return code from Cool:gen to PROC as how we usually do in COBOL to PROC as shown below?

MOVE 300 TO RETURN-CODE.

I got a scenario to set the return code from Cool:Gen and I want my JCL to capture it.

Any suggestions will be appreciated.

Thanks,

dick scherrer · Posted: Fri Jun 07, 2013 1:47 am

Hello,

Is the Cool:Gen process running on the mainframe?

If so, look in the documentation to see if there is a way for the "user" to control the return code.

If the Cool:Gen process sets the return code, the JCL can use it just as though it was set by a COBOL progeram.

Mr.Niceguy · New User Joined: 16 Jun 2005 Posts: 63

Hi,

Yes, Generated COBOL code runs on the mainframe environment. I have verified the documents, so far no luck. I will post if I find something. I also do not see this kind of scenario to pass Return code from cool gen to JCL in all my existing applications.

Thanks,

dick scherrer · Posted: Fri Jun 07, 2013 3:34 am

Hello,

Generated COBOL code IS able to set the return-code. You may need to intercept the generated code and add the setting of the return code. Which may be a "people" issue.

If you see nothing in the documentation, suggest you open an issue with CA Support.

Mr.Niceguy · New User Joined: 16 Jun 2005 Posts: 63

Yes, that is also a good idea and even I thought of including the return code statement in the generated COBOL code. But every time, the same return code statement needs to be added along with the future changes. Because those added lines make out of sync between code in the endevor and code in the encyclopedia. If third person retrieves the code for future changes from encyclopedia, then the added line will be lost and that might create some issues in the PROC as it would behave based on the return code .

Thanks,

dick scherrer · Posted: Fri Jun 07, 2013 6:27 am

Hello,

If you go with the option of including the return-code this should be automated and a required part (and well documented) of the source management process.

I would surely ask CA as they will be aware of options we might not.