>We're in the process of upgrading to Enterprise COBOL 5.1 and one of our=20 >development groups has decided to re-compile all their COBOL modules even=20 >though it is not deemed necessary - that's their prerogative.=20
I think it is an excellent idea to recompile all of an application and test it when moving to COBOL V5. 1) You get more performance benefit than only recompiling changed programs and 2) you complete the migration for that application and find any oddities in your code that might behave differently in COBOL V5 than in earlier compilers. >One of their programs is exhibiting strange behaviour on the development=20 >LPAR that I have been unable to replicate on our sandbox system. > >If they code the LE libraries SCEERUN and SCEERUN2 in their JOBLIB=20 >statement, their program runs OK. However, if they allow the LE libraries= >to come from link list (as they should) their program abends with S0C4 -=20 >the address of the offending instruction is way outside of the module=20 >reported in the dump - probably a wild branch, I guess. > >Has anyone encountered anything similar? Why should coding LE libraries=20 >in your JOBLIB (the same with STEPLIB, incidentally) cause a module to=20 >work when it doesn't work from link list? If the LE libraries pointed to by LNKLST are different from the ones pointed to by STEPLIB/JOBLIB you could get this behavior. Is it possible that the required LE service for COBOL V5 is not installed on the SCEERUN that is pointed to by LNKLST? Cheers, TomR >> COBOL is the Language of the Future! << ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
