If the CALL actually seems to be working and EZASOKET doesn't document such a CC, then it sounds to me as if this is the old "not clearing register 15" problem documented at:
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/igy3pg32/4.2.4.1 where it says, "You might need to think about this handling of the RETURN-CODE special register when control is returned to a COBOL program from a non-COBOL program. If the non-COBOL program does not use register 15 to pass back the return code, the RETURN-CODE special register of the COBOL program might be updated with an invalid value. Unless you set this special register to a meaningful value before your Enterprise COBOL program returns to the operating system, a return code that is invalid will be passed to the system." There are a number of documented cases (CICS and DB2 - if I recall correctly, but maybe others) where IBM products have this "problem". Try checking the Return-Code special register in your COBOL program IMMEDIATELY after the CALL. If it has a non-zero value and the values aren't documented by the program that you call, then this is probably what is happening. "Tom Simons" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > What does CC 2912 mean? My Cobol test program returns CC 2912 when I add > these EZASOKET calls: > > SOCKET > CONNECT > WRITE > READ > CLOSE > > FWIW, the EZASOKET calls are working - tcpdump at the other end of the > connection shows the outbound & inbound blocks. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
