>We ran into a program that was compiled and executed in a COBOL2 >environment successfully. When we re-compiled and executed the program >with Enterprise COBOL, it returned a S0C4 abend (rc4). The load module >is a combination of COBOL and assembler code. Anyone know if this is a >COBOL issue or LE?
The first thing I would check is if you have the (typical) invalid LNKLST concatenation order of VS COBOL II (COB2LIB) ahead of LE (SCEERUN). Both libraries have the same names except for the bootstrap routine, so if COB2LIB is ahead of SCEERUN and you try to run an Enterprise COBOL program you will get the LE library starting up and then VS COBOL II trying to run! 0C4 would be a typical result. See the COBOL Migration Guide, it was never supported to have VS COBOL II ahead of SCEERUN for Enterprise COBOL programs. I recommend migrating to LE first (remove COB2LIB from LNKLST) and then you can start using the new compiler. Note that COB2LIB is not supported at all, even behind LE in LNKLST. If you want to create a real mess, start using STEPLIB for each program that gets recompiled from VS COBOL II to Enterprise COBOL!! Cheers, Tom Ross >> COBOL is the Language of the Future! << ---------------------------------------------------------------------- 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
