Using Mainframe Express

Environment Variables

Chapter 3: Migration Procedure

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.

3.1 Suggested Procedure

The steps to follow are shown in the order you will probably find most advantageous.

3.1.1 Create the Project

1. Put all the application's source files and input data files into a suitable directory structure.

   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.

   mfuser\project\Myapp
   	cbl	COBOL source files
   	copylib	copybooks
   	bms	BMS maps
   	data	data 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.

2. Use the Project Wizard to create a project for your application in the Myapp folder.

   If you have CICS programs, specify the resource definition file as the one from Workbench+CICS, and select the correct SIT.

3.1.2 Set Workgroup Paths

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.)

1. Add any copybook folders to the Copybook libraries in Workgroup paths.

2. Add any Assembler macro library folders to the Assembler Macro/Copy libraries in Workgroup paths.

   The Workgroups paths to your source files and data files will be set automatically when you add them to the project and catalog, respectively.

3.1.3 Add Source Files to the Project

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:

1. With the project open in the IDE, click Import File List on the Project menu.

2. In the Import File List dialog box, set Files of type to Advanced Organizer Application (*.dat) and go to the folder containing Advanced Organizer's appmnnnn.dat files.

   This will be the folder specified by Workbench's MFORG environment variable, which is \cobol\mforgw by default.

3. Select the application's appmnnnn.dat file and click Open.

   This adds the files listed in the appmnnnn.dat file to the project.

To import a .pop file:

1. In Workbench, create a population (.pop) file for your application, as described in the online help for Workbench.

   Note where you save it, as you will be accessing it from Mainframe Express in a moment.

2. In Mainframe Express, with the project open in the IDE, click Import File List on the Project menu.

3. In the Import File List dialog box, set Files of type to Advanced Organizer Population File (*.pop) and go to the folder where you stored the .pop file.

4. Select the .pop file and click Open.

   This adds the files listed in the .pop file to the project.

3.1.4 Add Data Files to the Catalog

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.

1. If you have files in an mfextmap.dat file from Workbench, add them to the project catalog and convert them to TSO CLISTs, REXX execs, or JCL files, as described in the chapter Your Mfextmap File.

2. If you have files in a PROXMVS catalog, add them to the project catalog as described in the chapter Migrating from PROXMVS.

3. If you have files in an MVS Workbench catalog, add them to the project catalog as described in see the chapter Migrating from MVS Workbench.

4. Add any remaining files - for each, right-click on the Catalog View, and click Add Existing Dataset on the popup menu.

3.1.5 Add Command Files to the Project

1. Add any TSO CLISTs, REXX execs, or JCL files that execute the programs to the project.

2. If you have any Assembler linker command files, change their extensions from .jcl files to .lin.

   Mainframe Express expects .jcl files to contain JES2 or JES3 JCL statements.

3. Add any Assembler linker command files to the project.

3.1.6 Set Build Options

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:

• If you have been using any environment variables or COBOL compiler directives, look in the chapters Environment Variables and COBOL Compiler Directives to see how to set the equivalent options.

• The default COBOL language is set to VS COBOL II release 4.0. This may be different from the default in your previous Micro Focus product or your current mainframe COBOL compiler. In this case, set the desired language dialect as the default in your project settings. Click the COBOL tab, then the General subtab to see this setting.

• For Assembler programs included in .lin files, deselect Automatically link module. Click the Assembler tab, then the Link subtab to see this setting.

• For any Assembler files that have non-standard EPILOG and PROLOG options, or that need SYSPARM settings, or that call IMS, see the chapter Migrating from MF/370 Assembler.

• If your application includes Assembler programs, or you are mixing OS/VS dialect programs with other COBOL dialects, see the chapter AMODE.

3.1.7 Build the Project

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.

3.1.8 Test the Project

1. Use Start Debugging on the Debug menu to debug the application from a TSO prompt, CLIST, REXX exec, or JCL, or via a CICS or IMS transaction.

2. Similarly, use Run on the Debug menu to run the application.

Using Mainframe Express

Environment Variables