I have inherited a largish RM/COBOL ERP system with about 900 .COB files and 150 .DAT files.
I know a number of different languages and I am familiar with the business, but I have no previous experience with COBOL.
I find lots of COBOL help documents on the web but little of it is RM/COBOL specific.
Finding and bringing an outside developer up to speed on our company and programs will take time and money.
So I need to decide between the two options of hiring or doing it myself. I charge the company by the hour so I think that part is a wash for the company.
Thanks for any suggestions.
What is your Used rmcobol compiler? In Netexpress 5.x the rm syntax is integrated and I remember to have migrate a big project greater then yours to netexpress. Also visual cobol is able to do this! are the files index-sequential? There must be a reflection if it is no better to move to sql database?
Give us more information, a cobol source program as example and a data files! Are there text-oriented screens or windows screen? Are the printings text-oriented or graphical printings? What do you want in future?
You must share more information so that we are able to help you more!
I have inherited a largish RM/COBOL ERP system with about 900 .COB files and 150 .DAT files.
I know a number of different languages and I am familiar with the business, but I have no previous experience with COBOL.
I find lots of COBOL help documents on the web but little of it is RM/COBOL specific.
Finding and bringing an outside developer up to speed on our company and programs will take time and money.
So I need to decide between the two options of hiring or doing it myself. I charge the company by the hour so I think that part is a wash for the company.
Thanks for any suggestions.
If you have .COB files and .DAT files, then you do not appear to have any COBOL source files. The .COB files are the (interpretive) object files.
RM/COBOL compiles .CBL source files to .COB (object) files. The runcobol program uses the .COB files to run the applications. RM/COBOL uses uses a compile-once, run anywhere, interpretive model much like Java.
The names of the .COB files might give a hint about whether your ERP system is a well known ERP system implemented in RM/COBOL (such as MCBA) or a 'home grown' bespoke system.
I have inherited a largish RM/COBOL ERP system with about 900 .COB files and 150 .DAT files.
I know a number of different languages and I am familiar with the business, but I have no previous experience with COBOL.
I find lots of COBOL help documents on the web but little of it is RM/COBOL specific.
Finding and bringing an outside developer up to speed on our company and programs will take time and money.
So I need to decide between the two options of hiring or doing it myself. I charge the company by the hour so I think that part is a wash for the company.
Thanks for any suggestions.
Programming is easy, commercial processes are simple, compilers are easy to use, doing it yourself without in-depth knowledge is a big risk that can only fail, but 100% of the winners took their chance! Good luck!
What is your Used rmcobol compiler? In Netexpress 5.x the rm syntax is integrated and I remember to have migrate a big project greater then yours to netexpress. Also visual cobol is able to do this! are the files index-sequential? There must be a reflection if it is no better to move to sql database?
Give us more information, a cobol source program as example and a data files! Are there text-oriented screens or windows screen? Are the printings text-oriented or graphical printings? What do you want in future?
You must share more information so that we are able to help you more!
We are planning on using Codewatch. I will look into Netexpress. Had not heard of that one. I believe the files are index-sequential. Having reviewed the paths to SQL I plan on using Relativity for data access by other tools like Excel.
All the SQL tools seemed to be expensive and slower than the native files. I could use Relativity to scrape the data into our MS-SQL server if needed. I plan to review if updating the file formats to version 4 to reduce the chance we get shut down by a corrupted data file makes sense.
It makes extensive use of the SCREENS functions that are part of the RM/COBOL dialect. It is my understanding that SCREENS is part of RM/COBOL that is a rewrite to get into Visual COBOL.
If you have .COB files and .DAT files, then you do not appear to have any COBOL source files. The .COB files are the (interpretive) object files.
RM/COBOL compiles .CBL source files to .COB (object) files. The runcobol program uses the .COB files to run the applications. RM/COBOL uses uses a compile-once, run anywhere, interpretive model much like Java.
The names of the .COB files might give a hint about whether your ERP system is a well known ERP system implemented in RM/COBOL (such as MCBA) or a 'home grown' bespoke system.
I have all the source files. Many versions of them in fact. I think I have every version of every source file going back all 35 years. The system started out as a program called Telemerchant, but at this point more than half the code is bespoke.
Programming is easy, commercial processes are simple, compilers are easy to use, doing it yourself without in-depth knowledge is a big risk that can only fail, but 100% of the winners took their chance! Good luck!
My focus at this point is more maintain than rewrite. If I stumble onto the right programmer I might feel differently. I am glad to see replies here in this forum. Makes me feel less like I am standing at the bottom of a well.
My focus at this point is more maintain than rewrite. If I stumble onto the right programmer I might feel differently. I am glad to see replies here in this forum. Makes me feel less like I am standing at the bottom of a well.
My suggestion is if the applications are running weel and with no errors, why don't modernize the application with newer RM tools, like wow extension, relativity, instant SQL. Each of them can help you to expose the application to a modern environment and open all Data to others third tools like ODBC tools, excel, etc.
My suggestion is if the applications are running weel and with no errors, why don't modernize the application with newer RM tools, like wow extension, relativity, instant SQL. Each of them can help you to expose the application to a modern environment and open all Data to others third tools like ODBC tools, excel, etc.
I plan on using Relativity. I don't know what the wow extension thing is. Instant SQL seems redundant with Relativity.
I plan on using Relativity. I don't know what the wow extension thing is. Instant SQL seems redundant with Relativity.
The only thing common to Relativity and InstantSQL is the use of ODBC.
Relativity provides ODBC access to data stored in native COBOL files. No change to the COBOL application is required to allow this access.
InstantSQL allows COBOL programs access to relational databases that provide an ODBC interface. The data are stored in whatever format is used by the specific database. One must add/modify the COBOL application to add logic to connect to the database, and SQL queries to manipulate the data.
Relativity is a separately licensed product. InstantSQL is distributed with the RM/COBOL development system.
Ask questions...
The only thing common to Relativity and InstantSQL is the use of ODBC.
Relativity provides ODBC access to data stored in native COBOL files. No change to the COBOL application is required to allow this access.
InstantSQL allows COBOL programs access to relational databases that provide an ODBC interface. The data are stored in whatever format is used by the specific database. One must add/modify the COBOL application to add logic to connect to the database, and SQL queries to manipulate the data.
Relativity is a separately licensed product. InstantSQL is distributed with the RM/COBOL development system.
Ask questions...
Cobol WOW Extensions is a tool for development GUI applications basically with standard windows controls and where you can also expand the toolbox by adding ActiveX controls. These ActiveX controls can then be added to your windows and used by your programs. This capability provides an outstanding opportunity to add GUI features to your user interface. This visual approach makes building interactive applications and easily integrating your program logic with Windows GUI.
As Tom says, Relativity and InstantSQL are two different ways to get into SQL world. Relativity allows access to your Indexed Files through ODBC tools and InstantSQL allows you to access almost any SQL Data Base from you Cobol programs.
Cobol WOW Extensions is a tool for development GUI applications basically with standard windows controls and where you can also expand the toolbox by adding ActiveX controls. These ActiveX controls can then be added to your windows and used by your programs. This capability provides an outstanding opportunity to add GUI features to your user interface. This visual approach makes building interactive applications and easily integrating your program logic with Windows GUI.
As Tom says, Relativity and InstantSQL are two different ways to get into SQL world. Relativity allows access to your Indexed Files through ODBC tools and InstantSQL allows you to access almost any SQL Data Base from you Cobol programs.
A slight correction
Relativity will provide access to all COBOL file types: sequential, relative, and indexed.
Indexed is by far the most common, of course. The SQL engine in Relativity can use the indexed file keys to optimize queries. 99% plus of all my work has been on indexed files.
Relative files have only the relative key so optimizations are limited.
Sequential files have no key structure, so don't expect joins to a table defined on a sequential file to perform well. However, I have found Relativity useful for pulling data from log files and configuration files, as long as the full table scan is not an issue.
A slight correction
Relativity will provide access to all COBOL file types: sequential, relative, and indexed.
Indexed is by far the most common, of course. The SQL engine in Relativity can use the indexed file keys to optimize queries. 99% plus of all my work has been on indexed files.
Relative files have only the relative key so optimizations are limited.
Sequential files have no key structure, so don't expect joins to a table defined on a sequential file to perform well. However, I have found Relativity useful for pulling data from log files and configuration files, as long as the full table scan is not an issue.
All file Type make Sense, but analyzing with many data a sql database is the Best Choice.
i works over 20;years with sql Database and embeded sql, very easy and Best Performance, easy to learn and Best Performance. To do this in cobol will Need many Lines of Code!
100% from winners has try there chances!
I have inherited a largish RM/COBOL ERP system with about 900 .COB files and 150 .DAT files.
I know a number of different languages and I am familiar with the business, but I have no previous experience with COBOL.
I find lots of COBOL help documents on the web but little of it is RM/COBOL specific.
Finding and bringing an outside developer up to speed on our company and programs will take time and money.
So I need to decide between the two options of hiring or doing it myself. I charge the company by the hour so I think that part is a wash for the company.
Thanks for any suggestions.
We are currently using RM/COBOL v12.18 with Flexus SP2 for screen design.
I recommend you recompile and verify that you can run the existing application with your changes.
Possibly check the Flexus add-ons, we use these.
https://flexus.com/cobol-sp2/
Post any code specific questions here if you need assitance.
We are currently using RM/COBOL v12.18 with Flexus SP2 for screen design.
I recommend you recompile and verify that you can run the existing application with your changes.
Possibly check the Flexus add-ons, we use these.
https://flexus.com/cobol-sp2/
Post any code specific questions here if you need assitance.
John Aukema Thanks for the tip. I want to finish moving the system to Windows before I get to updating the UI.
John Aukema Thanks for the tip. I want to finish moving the system to Windows before I get to updating the UI.
Hi Brian,
How is your project going?
Regards,
------------------------------
Juan Urraburu
Director, Information Technology
ProRM Uruguay
Montevideo UY
------------------------------
