From your response under the recorded bug - PREPARE and EXECUTE are often used SQL for a program or module that will be used in production applications as they improve speed of execution against the RDB.
All of my applications are now in free format for both readability and ease of programming / typing.
Needless to say I use the '*>' comment option heavily within and after a cobol statement line to hold notes and other memory helpful comments.
If I get a change I will take a look at adding both PREPARE and EXECUTE to the cobclient C code library. - My C is somewhat rusty :)
Also need to look at what SQL processes are available for connecting to other tables within the same run unit as SET CONNECTION is not in use with MySQL.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When processing a source file that is in free format the following problems appear:
Testing stopped as errors are too great to continue.
This has been sent to the tracker system along with the source and listing files etc..
Last edit: Vincent (Bryan) Coen 2016-06-04
From your response under the recorded bug - PREPARE and EXECUTE are often used SQL for a program or module that will be used in production applications as they improve speed of execution against the RDB.
All of my applications are now in free format for both readability and ease of programming / typing.
Needless to say I use the '*>' comment option heavily within and after a cobol statement line to hold notes and other memory helpful comments.
If I get a change I will take a look at adding both PREPARE and EXECUTE to the cobclient C code library. - My C is somewhat rusty :)
Also need to look at what SQL processes are available for connecting to other tables within the same run unit as SET CONNECTION is not in use with MySQL.