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

EZASOKET leaving the return-code = 1736?


 
IBM Mainframe Forums -> ABENDS & Debugging
Post new topic   Reply to topic
View previous topic :: :: View next topic  
Author Message
Ed Goodman

Active Member


Joined: 08 Jun 2011
Posts: 556
Location: USA

PostPosted: Sat Mar 15, 2014 3:21 am
Reply with quote

I have a weird one.

I created a very simple Enterprise COBOL program to do some socket calls. When I run the program, I am getting a step return code of 1736. I get no messages, no helpful output...nothing else but the return code.

The sample code was a dynamic link, so I tried changing it to static, then I got return code 2736.

It turns out the EZASOKET call is working just fine, but the program is returning with that weird value in the return-code.

What is allowing EZASOKET to change that value?

I had a similar error when testing a vendor supplied assembler routine. If they didn't initialize R8 or R15 upon startup, but incremented it. They fixed the code to do the init and the trouble went away.

Do you think EZASOKET is doing something like that?
Back to top
View user's profile Send private message
Bill Woodger

Moderator Emeritus


Joined: 09 Mar 2011
Posts: 7312
Location: Inside the Matrix

PostPosted: Sat Mar 15, 2014 5:26 am
Reply with quote

Check that the number of parameters you are passing is correct. I think the CALLed program is changing something which the CALLing program thinks is the RETURN-CODE, but itsn't.

EZASOKET seems to have an odd arrangement of parameters, where it must "know" from the first parameter, how many parameters (a variable number) before the last two. If you don't give the correct amount, I think you'll get a the RETURN-CODE in the CALLer mangled.

Try adding another parameter, see if the problem "goes away".
Back to top
View user's profile Send private message
Ed Goodman

Active Member


Joined: 08 Jun 2011
Posts: 556
Location: USA

PostPosted: Sat Mar 15, 2014 8:06 am
Reply with quote

Thanks Bill, I'll give that a shot. I know what you mean about the odd parameter list. I'll double check that I have the right manual for the version I'm running too, that may have changed.

I feel like a fool for 'wasting' 3 hours diagnosing something that wasn't really a problem. The reason I didn't get any error messages was because nothing went wrong.
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 -> ABENDS & Debugging
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 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
No new posts trying to set return code in PROC JCL & VSAM 15

Back to Top