EZASOKET leaving the return-code = 1736?

Ed Goodman · Active Member Joined: 08 Jun 2011 Posts: 556 Location: USA

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?

Bill Woodger · Posted: Sat Mar 15, 2014 5:26 am

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".

Ed Goodman · Active Member Joined: 08 Jun 2011 Posts: 556 Location: USA

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.