You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 1, 2022. It is now read-only.
TypeCobolBuild has started as a POC (Proof Of Context), To show that it is possible thru a RTC BuildEngine to call the TypeCobol Parser/Generator , and to deliver generated cobol files back to a RTC Stream.
The Idea was to create a Build definition using a Command Line - Jazz Build Engine, which calls via a DOS batch command file the JTCB application to parse and generated a TypeCobol file that has been loaded from a RTC Workspace/Component.
The POC should show that additional Cobol COPY files, could be read directly from an RTC Stream, and the generated COBOL file could be delivered.
The POC has shown that JTCB is able to perform such operations.
So It is necessary to describe all steps from RTC build definition to the DOS Batch command file which launch JTCB and interoperates with the TypeCobol parser/generator.
The text was updated successfully, but these errors were encountered:
TypeCobolBuild has started as a POC (Proof Of Context), To show that it is possible thru a RTC BuildEngine to call the TypeCobol Parser/Generator , and to deliver generated cobol files back to a RTC Stream.
The Idea was to create a Build definition using a Command Line - Jazz Build Engine, which calls via a DOS batch command file the JTCB application to parse and generated a TypeCobol file that has been loaded from a RTC Workspace/Component.
The POC should show that additional Cobol COPY files, could be read directly from an RTC Stream, and the generated COBOL file could be delivered.
The POC has shown that JTCB is able to perform such operations.
So It is necessary to describe all steps from RTC build definition to the DOS Batch command file which launch JTCB and interoperates with the TypeCobol parser/generator.
The text was updated successfully, but these errors were encountered: