It seems to me that the first reason for the PDSE requirement was their choice to use the Java backend code generator, which always generates GOFF instead of classic object decks, instead of, for instance, the C/C++ backend which can generate simple object decks (so long as only simple pre-GOFF facilities are used), and that the second reason was their decision to use DWARF format for the no-load debugging and other non-executing runtime information that requires program-object-only formats in the binder output executable.
I agree that understanding the path of that decision process leads to many questions. I fervently wish I had been able to participate actively in SHARE over the last few years to help guide such a decision path in different directions (assuming, of course, that the decision makers even cared what SHARE participants' opinions are/were). I do not blame Tom Ross. He is only the messenger, and I would not wish to see him shot for the difficulties that will be brought on us by the message. Peter -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Thomas Conley Sent: Thursday, September 12, 2013 11:22 AM To: [email protected] Subject: Re: PDS/E, Shared Dasd, and COBOL V5 <Snipped> Lizette, Great analysis of some of the operational costs involved in this PDS to PDSE conversion just to support COBOL V5.1. In many shops, this will not be a trivial exercise, as some on IBM-Main have stated. This will be a serious migration effort, and cost significant dollars. I'm still mystified as to why IBM felt it had to impose this completely unnecessary restriction. What reason is there to force COBOL V5.1 executables to come from a PDSE? -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
