The following is a suggested procedure to follow in migrating an application from Workbench and its add-ons to Mainframe Express. It is not intended to cover every eventuality, but to provide an outline procedure and draw attention to some points to watch out for.
Note that the word "project" is not only used to mean the project file, but is also used to mean the whole application, with all its files, folders, and settings.
The steps to follow are shown in the order you will probably find most advantageous.
We recommend a directory structure such as the one shown below. Here, Myapp is the project folder, and all your files go in folders within it.
|cbl||COBOL source files|
|reg||dfhdrdat* from the Workbench CICS region (if application includes CICS programs)|
But note that because you can specify complete paths to your source files and data files in the Workgroup View and the catalog, you can if you prefer use the folders where you have been keeping your files previously. This may save you some work in creating your catalog, since the utilities (see below) that create catalog entries from existing entries in your Workbench mfextmap.dat or your PROXMVS or MVS Workbench catalog will pick up the existing paths.
If you have CICS programs, specify the resource definition file as the one from Workbench+CICS, and select the correct SIT.
The Workgroup View shows the paths to the folders containing your different file types in the project.
For copybooks and macros, you should add these paths before adding your source files to the project, so that when Mainframe Express scans the source files and finds dependencies on these files, it will know where to look for them. (Otherwise you might have to run the dependency scan several times.)
The Workgroups paths to your source files and data files will be set automatically when you add them to the project and catalog, respectively.
You can use Add Files on the Project menu to add each file, but Mainframe Express includes features specially for importing Workbench applications.
Each application you created in Advanced Organizer has a file called appmnnnn.dat (with an index file appmnnnn.idx). This contains details such as the files that make up the application and the dialect used by those programs.
Population files are flat text files you can create in Workbench, containing a list of the files in an application, and their types. Their extension is .pop.
You can import either of these files into Mainframe Express, adding the files listed in it into the Mainframe Express project.
To import a appmnnnn.dat file:
This will be the folder specified by Workbench's MFORG environment variable, which is \cobol\mforgw by default.
This adds the files listed in the appmnnnn.dat file to the project.
To import a .pop file:
Note where you save it, as you will be accessing it from Mainframe Express in a moment.
This adds the files listed in the .pop file to the project.
You can use Add Existing Dataset to add each file, but Mainframe Express includes features specially for importing catalog entries from Workbench, PROXMVS and MVS Workbench.
Mainframe Express expects .jcl files to contain JES2 or JES3 JCL statements.
The default options are set by the Project Wizard when you create the project, and these may be adequate. However, you can use the Project menu to customize options. Use Build Settings for Project to set options common to all programs.
To set options specific to an individual program, select that program in the right-hand pane of the Files View, and use Build Settings for.... For that program, these options will override those set in Build Settings for Project.
Check the Contents and Index of this book for any options you think you might need to change. Some options you are likely to need to look at are:
Use Build on the Build menu to build the project.
This compiles all your source files of any kind, including not only .cbl, .pli, and .mlc, but also .lin, .jcl, .rex, .bms, and so on.
Copyright © 2001 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.