That's a reasonable suggestion. Many pitfalls to watch out for (like the branch gates example I gave earlier), but like you said, possibly 75% coverage for the code portion. System macro conversion could be a big headache too, but at least feasible to try.
Trickier could be conversion of the DSECT and non-reentrant variable storage area definitions. I would expect much of that to need careful human review and manual adjustment. Unlike HLL's, assembler allows many hardware-specific "tricks" that make automated analysis, like classical compiler construction to generate "parse trees" and "directed graphs" and such, much more difficult. It may be possible to do, but the work involved to create and validate such a beast would be massive. Peter -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of W Mainframe Sent: Saturday, July 9, 2022 10:23 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Converting assembler to COBOL help Hi,A suggestion... I did similar thing some years ago using z390 Macro Language. In summary you can create macros and replace used macros by Cobol statements.The macros just punch Cobol statements to an output.I converted about 250 critical Cobol code.Main question... Is it 100%, of course not... But I would say 75%. RegardsDan Sent from Yahoo Mail for iPhone On Friday, July 8, 2022, 8:53 PM, Paul Gilmartin <0000042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: On Fri, 8 Jul 2022 22:51:38 +0000, Farley, Peter x23353 wrote: > > ... The business logic was totally scrambled, sometimes by "old-timer" >tricks like non-reentrant branch gates and other such no-no's under current >maintainability and pipeline-flush avoidance rules, other times just by >flagrantly awful spaghetti code even a human would struggle to understand. > Was that merely faithfully replicating deficiencies in the input? What architecture level? What might it do with such as RISBG? -- 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN