Closed Reinhard-Prehofer closed 6 years ago
meanwhile we have implemented an Exec-Adabas-PreProcessor which comments out the exec-adabas ... end-exec statements in the Cobol sources and replaces it by the name of a cobol copy book. This cobol copy book will be filled by issuing various batchmode predict statements, all of them resulting into legitimate cobol declarations. ... thus I am closing that issue.
Noone expects you to implement a preprocessor for Adabas for example, however there are a lot of sources around where calls to be resolved by differente preprocessors are written into the cobol sources following a pattern of for example:
EXEC ADABAS <adabas-statement> END-EXEC.
(sure there is a similarity to
exec sql <sql-statements> end-exec.
A third approach - easiest for your ;) - would be the implementation of an own preprocessor, which resolves all the exec adabas ... end-exec statements by calling the SAG-Preprocessor (an application running in "PREDICT") and
only this resolved cobol code is to be parsed by the cobol85parser.
Any suggestion/recommandation as of how to proceed with such sources? Source snippets are like following: