Skip to main content

Nowadays, when I want to offer a solution in Visual Cobol, the first question that the interested person asks me is on which data system the application is developed, if COBOL IDXFORMAT files or on a standard DB system, such as SqlServer, DB2, Possgresql, MySql, .....

It is more complicated to sell the solution based on the classic cobol files, and they demand solutions based on more open and modern systems...

Is it possible to have an example of the steps to be done in an application, so that a file defined in the SELECT as CUSTOMERS and a Value-id "CUSTOMERS.DAT" is generated on a DB "COMPANY_AG" is created and managed automatically with the MFDBFH tool, without changing source programs?


Regards.

Nowadays, when I want to offer a solution in Visual Cobol, the first question that the interested person asks me is on which data system the application is developed, if COBOL IDXFORMAT files or on a standard DB system, such as SqlServer, DB2, Possgresql, MySql, .....

It is more complicated to sell the solution based on the classic cobol files, and they demand solutions based on more open and modern systems...

Is it possible to have an example of the steps to be done in an application, so that a file defined in the SELECT as CUSTOMERS and a Value-id "CUSTOMERS.DAT" is generated on a DB "COMPANY_AG" is created and managed automatically with the MFDBFH tool, without changing source programs?


Regards.

Have a look at this video giving a good overview and demonstration using MFDBFH : https://youtu.be/fNMpRwLOvBQ

Nowadays, when I want to offer a solution in Visual Cobol, the first question that the interested person asks me is on which data system the application is developed, if COBOL IDXFORMAT files or on a standard DB system, such as SqlServer, DB2, Possgresql, MySql, .....

It is more complicated to sell the solution based on the classic cobol files, and they demand solutions based on more open and modern systems...

Is it possible to have an example of the steps to be done in an application, so that a file defined in the SELECT as CUSTOMERS and a Value-id "CUSTOMERS.DAT" is generated on a DB "COMPANY_AG" is created and managed automatically with the MFDBFH tool, without changing source programs?


Regards.

this is very easy to move data from sequential, relative or indexed files to sql database as ms sqlserver or other

And there a many ways. You can create the sql database with cobol with index and the insert directly the data in the database

i have many experience with this, have move vor 20 years all data in sql databases...

Have a look at this video giving a good overview and demonstration using MFDBFH : https://youtu.be/fNMpRwLOvBQ

Hello,

I have watched the video several times, but I can't manage to keep the basic steps, to be able to test the example that I propose.

this is very easy to move data from sequential, relative or indexed files to sql database as ms sqlserver or other

And there a many ways. You can create the sql database with cobol with index and the insert directly the data in the database

i have many experience with this, have move vor 20 years all data in sql databases...

Hello,

I know how from VCVS or NE, you can access and query tables in SQL Server, but it requires modifying the programs to access tables through an ODBC link.
What I am interested in is to know a practical example of how to use MFDBFH, which reportedly, with a few minor changes in the SELECT, and the use of some configuration files of MFDBFH, does not require any change in the programs.

Hello,

I know how from VCVS or NE, you can access and query tables in SQL Server, but it requires modifying the programs to access tables through an ODBC link.
What I am interested in is to know a practical example of how to use MFDBFH, which reportedly, with a few minor changes in the SELECT, and the use of some configuration files of MFDBFH, does not require any change in the programs.

Hi,

If you send me an email directly to chris.glazier@microfocus.com I will send you a tutorial walk-thru of the steps to set up mfdbfh.

Terms & ConditionsAccessibility statement