I have done a rewrite of EBCDIC support. By adding -fsign=ebcdic -fdefault-colseq=ebcdic -febcdic-table=ebcdic500_latin1 as compiler options I presume I can remove the following from the EBCDIC preprocessor COBOL generation. ** STRING ** 'OBJECT-COMPUTER. PROGRAM COLLATING SEQUENCE' ** DELIMITED BY SIZE ** ' IS EBCDIC-CODE.' ** DELIMITED BY SIZE ** INTO ** EBC-TEXT ** MOVE SPACES TO SRC-DATA ** MOVE EBC-TEXT TO SRC-DATA (8:65) ** WRITE NEW-DATA FROM SRC-DATA ** MOVE '1' TO PROC-SPECIAL ** MOVE **...
I have done a rewrite of EBCDIC support. By adding -fsign=ebcdic -fdefault-colseq=ebcdic -febcdic-table=ebcdic500_latin1 as compiler options I presume I can remove the following from the EBCDIC preprocessor COBOL generation. ** STRING ** 'OBJECT-COMPUTER. PROGRAM COLLATING SEQUENCE' ** DELIMITED BY SIZE ** ' IS EBCDIC-CODE.' ** DELIMITED BY SIZE ** INTO ** EBC-TEXT ** MOVE SPACES TO SRC-DATA ** MOVE EBC-TEXT TO SRC-DATA (8:65) ** WRITE NEW-DATA FROM SRC-DATA ** MOVE '1' TO PROC-SPECIAL ** MOVE **...
I have done a rewrite of EBCDIC support. By adding -fsign=ebcdic -fdefault-colseq=ebcdic -febcdic-table=ebcdic500_latin1 as compiler options I presume I can remove the following from the EBCDIC preprocessor COBOL generation. ** STRING ** 'OBJECT-COMPUTER. PROGRAM COLLATING SEQUENCE' ** DELIMITED BY SIZE ** ' IS EBCDIC-CODE.' ** DELIMITED BY SIZE ** INTO ** EBC-TEXT ** MOVE SPACES TO SRC-DATA ** MOVE EBC-TEXT TO SRC-DATA (8:65) ** WRITE NEW-DATA FROM SRC-DATA ** MOVE '1' TO PROC-SPECIAL ** MOVE **...
My post was that of Bard / Gemini (AI) comparing MF to GnuCOBOL. "Ralph Says" is actually what Bard / Gemini stated. A misinterpretation by Juan Carlos. From 2018 on, I (Ralph) have sought to improve GnuCOBOL to embrace more zOS professional Cobol programmer usage. zOS, the platform where 90% + of all COBOL usage is deployed. Given that my focus is that of zOS COBOL professionals I can't really address the screen section idiosyncrasies of COBOL vendor "A" versus COBOL Vendor"B" as such relates to...
Wow ! FreeDOS and now 4DOS Huh ?
I am a wee bit confused. Is this thread in support of Jack's suggestion ? "As part of our migration from MF to GNUCOBOL we need the SCREEN SECTION to work the same as MF. We can only address this for NCURSES and LINUX. We do not have the resources or knowledge to address this for Windows. Would anyone be interested in starting a collaboration for this ? " In the same thread Jack indicates "Changing the program to have 220 accept statements is a rewrite, not a conversion. In the end, " I spent less...
For Juan. Although the . MP4 depicts CICS, the dialog also works for CLI or called. Chuck H has created Linux / Windows versions of the primitives used by the dialog. Ralph
For Juan. Although the . MP4 depicts CICS, the dialog also works for CLI or called. Chuck H has created Linux / Windows versions of the primitives used by the dialog. Ralph