IBM Mainframe Forum Index
 
Register
 
IBM Mainframe Forum Index Mainframe: Search Log in to check your private messages Log in
 

Passing Return Code to PROC


 
IBM Mainframe Forums -> CA Products
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Mr.Niceguy

New User


Joined: 16 Jun 2005
Posts: 63

PostPosted: Fri Jun 07, 2013 1:36 am
Reply with quote

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,
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19251
Location: Inside the Matrix

PostPosted: Fri Jun 07, 2013 1:47 am
Reply with quote

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.
Back to top
View user's profile Send private message
Mr.Niceguy

New User


Joined: 16 Jun 2005
Posts: 63

PostPosted: Fri Jun 07, 2013 2:23 am
Reply with quote

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,
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19251
Location: Inside the Matrix

PostPosted: Fri Jun 07, 2013 3:34 am
Reply with quote

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.
Back to top
View user's profile Send private message
Mr.Niceguy

New User


Joined: 16 Jun 2005
Posts: 63

PostPosted: Fri Jun 07, 2013 4:06 am
Reply with quote

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,
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19251
Location: Inside the Matrix

PostPosted: Fri Jun 07, 2013 6:27 am
Reply with quote

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.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic All times are GMT + 6 Hours
Forum Index -> CA Products
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Forum Replies
No new posts JCL for replacing code in Cobol JCL & VSAM 8
No new posts Proc print in Mainframe All Other Mainframe Topics 4
No new posts Easytrieve EZABX007 with error code 0... CA Products 7
This topic is locked: you cannot edit posts or make replies. VSAM I/O - Extended Addressability - ... JCL & VSAM 12
No new posts Force a Return Code and print error m... SYNCSORT 30

Back to Top