[Info-vax] VMS Software: New US Mailing Address

[Jan-Erik Söderholm]

Den 2022-10-13 kl. 01:22, skrev Arne Vajhøj:
> On 10/12/2022 6:58 PM, Bill Gunshannon wrote:
>> On 10/12/22 17:33, Arne Vajhøj wrote:
>>> On 10/12/2022 4:20 PM, Bill Gunshannon wrote:
>>>> Using a compatibility layer and trying to make PostGres look like
>>>> RDB (or Oracle) would be a major mistake. Better to bite the bullet
>>>> and move into the current century.
>>>
>>> It is a tradeoff.
>>>
>>> There are benefits from doing things the standard way instead of
>>> doing it the compatibility way.
>>>
>>> But there are also huge cost of changing the client applications.
>>
>> Maybe and maybe not as much as you think.  Granted, most of my
>> experience doing it has been with COBOL but I have been able to
>> take programs using databases from other systems and moved them
>> quite easily.  I would  love to have someone send me a COBOL
>> program that uses RDB just for a look-see.
> 
> Cobol embedded SQL is probably one of the more portable. But it is
> not supported by PostgreSQL project itself.
> 
> An extremely simple Cobol embedded SQL to Rdb example:
>    https://www.vajhoej.dk/arne/articles/vmsdb.html#rdb_cob_emb
> 

We usually write applications in two layers.
To top layer is the main application with the UI and businees logic.
That is usually a plain COB file.

That in turns calls an SCO ("Cobol with embedded SQL") that has
specific functions for the database operations.

We usually has one SCO module that collects the SQL operations
for a specific group of database tables. That can then be called
from any aplication that needs to do operations on these tables.

Or, for simple cases, we just write a SCO application including
all database operations...