We have a ten year old version of Micro Focus Cobol Workbench (ver. 4.0) and it is no more installing to windows 2000. We used to have Windows NT 3.51 (GUI Looks like Win 3.11) and were using it for mainframe cobol testing. I have heard that it is necessary to change the installer, after that it can be reinstalled into WIN 2000. The local agent for MF Cobol tries to sell us a much newer version (Mainframe Express), but we could be satisfied with the old one. Our 4.0 licenses are OK, but support is no more valid (we stopped paying the annual fee some years ago). Do you have idea how to install the old version 4.0?

• Micro Focus Cobol User Guide
• Micro Focus Cobol Workbench Downloads For Sale
• Micro Focus Cobol Price

RE: Installing Micro Focus Cobol 4.0 (IS/IT-Management) 7 Jun 05 07:57. Also you can copy an installed version from a machine where it worked ok. I wonder how this will work.

Visual COBOL: A developer's guide to modern COBOL. Written by: Paul Kelly 320+ pages. Download the eBook ›. Visual Studio. Visual COBOL for Visual Studio provides advanced COBOL editing and debugging for application developers. Continuous background compilation, auto complete, code analysis,. The PC 'hangs' when I attempt to move from the 'Debug' build to the 'Release' build option. (Top bar menu) We have a work-a-round from the point of view of building the WHOLE solution in that I can use the batch build option but is not so clever when I need to build individual 'release' components!

Aren't there any important registry entries which should be correct? I'm not sure but I think NT 3.51 had also some kind of registry in it.

I remember that we started all the Workbench programs by clicking desktop icons. In the manual there was given an other alternative: Command-line. If I just copy all the directories (+ subdirectories) and their contents, will that kind of installation work?

If so, it must be a ms-dos program! Actually it is a 32-bit program, but not behaving exactly like the 'real' MS windows programs. With the help of Google I got some information from Micro Focus pages, and printed it. They say that version 4.0 works in Win Millenium, XP., NT 4.0 (WIN 2000 was not listed). Not good, since we have WIN 2000 workstations. I work in a quite big corporation, and I'm not sure if I can get Win XP for this purpose only.

RE: Installing Micro Focus Cobol 4.0 (Programmer) 7 Jun 05 15:18. This is strange, but what you do is copy the whole cobol directory from the old pc to the new one.

Go to cobol exedll wbwg.exe and set up a shortcut for your desktop. You will need to print out your autoexec.bat that is on your old pc and enter the environmental variables in the new win2k PC. We're also running this and since dos is no longer part of Windows 2000, you can't install the old program, but can just copy it and run it. If you need more assistance just ask. Cathy RE: Installing Micro Focus Cobol 4.0 (Programmer) 7 Jun 05 16:08. There were no registry entries made in 4.0.

Environment variables were set up in install.mf and this was triggered when needed rather than being in autoexec.bat. As I recall there was an executable placed in the windows directory named setmfenv.exe. I believe mzkitty is wrong about DOS. DOS is still alive and well in windows 2000 and the mf-dosprompt windows could be used for command line stuff.

Are you setting up for mainframe emulation or to create PC standalone modules? Clive RE: Installing Micro Focus Cobol 4.0 (Programmer). We are emulating mainframe programs and have an EBCDIC version of Workbench, IMS and Cics. There are only a couple of programs running in production (in pure pc platform) in ascii.

The main purpose is to test mainframe programs, specially under CICS. Most programmers stopped using WB many years ago.

It was quite laborous to prepare test files for both pc and mainframe. Actually many people never lerned how to download and prepare DL/1 databases for pc.

I did it and showed it to the few interested guys. In new projects it is more wise to use Cobol WB, but our work mostly consist of maintaining old programs.

We are soon migrating from VSE to zOS, actually starting program conversion just now. We are also running VM (using Xedit), I like most the capabilities of Xedit. I'm afraid of the new zOS, everybody who have seen the new TSO system and the editor which is included there say it's much less powerfull than Xedit. There is a limitation of concurrent sessions in TSO. The current ways how to work will all change. My employer is not going to invest money for mainframe tools, since they are expensive.

We should be satisfied only with those tools which are included in zOS (=MVS+???). RE: Installing Micro Focus Cobol 4.0 (Programmer) 8 Jun 05 09:29.

OK then just copy everything preserving the directory structures. Copy the directory c: install.mf. Copy anything in the windows directory with a prefix of MF (check that you are not overlaying any in case they are not MF modules).

You also need a bat file setmfenv.bat The final step is to make an environment wariable the same as was made on the NT version. I don't have Win 2000 but in XP, for example, it would be control-panel/performance & maintenance/system/advanced/environmental variables.

Clive RE: Installing Micro Focus Cobol 4.0 (Programmer). I just wonder what is the list price of Mainframe Express? I have found some M Focus texts where they promise discount when upgrading from Workbench 4.0 to Mainframe Express. I think I have accidentally found pages which are not for public use - for MF company only. But our local dealer is not telling the price (yet) - I'm from Europe. I'd also like to know what is the price of Mainframe Express.

The dealer likes to sell the Net express, but we do not have our self build systems connected to Internet. We have IBM e-commerce software package for our moderate size of web store. Most of our operative systems are running in IBM mainframe. If there is not a fixed list price (starting price) everywhere in Europe, the discount is bullshit. Buying the product would be the same as buying something in a bazar in Marocco.

I'm not used to this kind of Business. We need minimun 2 copies, maximum 10. Let's see, if I can reinstall the old WB 4.0 this summer. We are used to work without it for years now. Thank you for all your advice. Greetings, Ari.

Migrating from COBOL Workbench COBOL Workbench was designed for developing applications for PC or mainframe, and also includes features for backward compatibility with much older Micro Focus products. Mainframe Express supersedes COBOL Workbench for developing mainframe applications.

This chapter describes differences between COBOL Workbench and Mainframe Express that might require you to make alterations in existing applications that you are migrating, or to change familiar methods of working. The COBOL Workbench versions covered are V3.4 and V4.0. These are functionally more-or-less equivalent - V3.4 is 16-bit and V4.0 is 32-bit, but this difference is not likely to be relevant for developing mainframe applications, since on your workstation you are interested only in the development environment.

In this book, we make no distinction between V3.4 and V4.0. We generally use the term 'Workbench' to mean both COBOL Workbench V3.4 and V4.0. Certain self-contained areas of Workbench are covered in the separate chapters, and. All other areas of Workbench are covered in this chapter.

The following Workbench components have no equivalent in Mainframe Express:. Analyzer, Application Configuration System, Banner, Base Animator, Batch File Facility, Btrieve Support (Xfh2btr and Btr2xfh), Class Browser, Class Library, Co-MFS, Color, Communications Module (MCS), Data File Filter, Dialect Compatibility Tools (Convert3 and Convert5), GNT Analyzer, Hexedit, Interface Programs, Keystroke Macro, Linein, Menu Handler, Object Orientation, Setup (character), Screens, Source Comparison Utility (Diff), Structure Animator, Xilerator. A few components that you may have used in Workbench are not available from the IDE, but can be run from the Mainframe Express Command Prompt, which you start by clicking Programs on the Start menu, then Micro Focus Mainframe Express, then Mainframe Express Command Prompt. Not all are supplied as.exe files - you use the run command to run those that aren't.

For example, to run the Source Converter (module name MDECONV), enter: run mdeconv. Represents the component's command line, given in the online help or online books.

If you use one of these components a lot, you can add it to the IDE's Tools menu yourself. Click Customize IDE on the Options menu, then click the Tools tab and click New Tool to see how to do this. This section advises on what to use where a Workbench feature is not in Mainframe Express or has changed. Where we believe you can continue using a feature without change, it is not mentioned. This book does not cover enhancements.

Compile-time statements (BASIS, INSERT, DELETE) in COBOL to insert and delete source lines temporarily. Status in Mainframe Express: Included, but handled by a preprocessor not by the compiler itself. To migrate your application: You must use the PREPROCESSOR(BASIS) or P(BASIS) directive. Click Build Settings for. On the Project menu, then click the COBOL tab, then the Preprocess subtab.

Micro Focus Cobol User Guide

Put a check mark by Use additional preprocessor and directives, type BASIS in the field below it, then click OK. Character mode tools such as Editor and Animator included in Workbench for convenience of users familiar with earlier products. Status in Mainframe Express: Not included. What to use in future: All desirable functionality is included in the IDE. Support for Oracle databases. Status in Mainframe Express: Not included.

Mainframe Express supports only IBM DB2 (via Host Compatibility Option) or DB2 emulation (via SQL Option). Optional add-on support for SQL Server databases. Status in Mainframe Express: Not included. Mainframe Express supports only IBM DB2 (via Host Compatibility Option) or DB2 emulation (via SQL Option). Editor for editing in hexadecimal, useful especially for program files and other files with no record structure. Status in Mainframe Express: Not included. What to use in future: For data files, use the hex editing features in the Data File Editor.

Facility to pass parameters to a program. Status in Mainframe Express: Not included. What to use instead: Use the PARM= string in the JCL EXEC PGM= statement or a parameter on a CALL statement in a CLIST. This section answers questions that may arise in the course of migrating. Population files created by Advanced Organizer in Workbench are supported by Mainframe Express to help you migrate from Workbench. Look up Population files in the index of the Mainframe Express help for details of how to use them.

Mainframe Express assumes that source files use the ANSI character set. When it downloads source files from a mainframe (using Micro Focus's Mainframe Access product), it automatically converts them from EBCDIC to ANSI. If you've downloaded using other software, it may have been converted to ASCII not ANSI. Earlier Micro Focus software converted to ASCII.

See the chapter in your for details of how to convert your ASCII files to ANSI. Most characters are the same in ASCII and ANSI, so this is only likely to affect you if you're using accented characters, from the extended ASCII character set. Source code used in Workbench for deployment on a mainframe is compatible with Mainframe Express. Source code using Micro Focus extensions such as Object Orientation is not compatible Although.int code produced by Workbench will run in Mainframe Express, you cannot debug it. You will need to recompile your programs to allow them to be debugged using Mainframe Express, and to ensure the executable(.int and.gnt) files are put into the correct locations (the loadlib folder within the project folder). However,.gnt code produced by Workbench is not compatible with Mainframe Express.obj code is not used by Mainframe Express. If CCITCP2 is installed as an NT service, it will be started automatically when the NT system is restarted.

Micro Focus Cobol Workbench Downloads For Sale

If you have added CCITCP2 Server to the Startup group on your Start menu, you should remove it and run it only when needed. Otherwise Windows NT will try to start a second instance of CCITCP2. Copyright © 2001 Micro Focus International Limited. All rights reserved.

Micro Focus Cobol Price

This document and the used herein are protected by international law.