Multiple answers in one response... >One comment, check the IBMMAIN Archives for discussions on COBOL V5. There= > are many changes to the way this compiler runs. For one thing, the output= > files need to be PDS/E datasets for the compiler and Load libs. =20
Almost right. The compiler outputs can all go into PDS, but the BINDER output, the executable, is a Program Object and can only live in PDSE. >You cannot, as far as I know, copy a compiled COBOL V5 module to a PDS to r= >un. It needs to be a PDS/E. Well, you cannot copy a bound(link edited) COBOL V5 Program Object to a PDS :-) The Object Module output of the compiler can be in PDS. >Also look at SHARE presentation by Tom Ross in August of 2014. And=20 >session presentation 17610, User Experience. Please don't! That is way out of date now, no mention of the latest migration-easing changes we have made. Instead look at my migration presentation from March, 2015: 16615: How to Take Advantage of the New COBOL V5 Compiler - Migration! If you don't have access to SHARE content, this discussion has reminded me to update the COBOL Resource page with my newer presentation. I sent the request to our web page people, it should be updated by next week: http://www-01.ibm.com/support/docview.wss?uid=swg27039560 Cheers, TomR >> COBOL is the Language of the Future! << ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
