Micro Focus Enterprise Developer 2.3 Update 2 for Eclipse > Programming > Mainframe Programming > IMS Support > IMS Installation Verification Procedure (IVP) > Prepare the MFDEMO Application

Prepare the MFDEMO Application

Takes you through the process of compiling and generating required MFDEMO source files, loading the IMS database, and importing IMS transactions. All of these tasks are done from the command line.

Although the MFDEMO application is supplied with your application software, you need to perform a number of tasks on the source files to prepare the application for execution:

Copy the MFDEMO files to a working directory
Compile the COBOL programs
Generate the MFSs
Generate the DBD
Generate the PSB
Register the resource definition file
Load the database
Import the IMS transactions

Fastpath: We provide a batch file, build.bat, that performs all of the tasks required to prepare the MFDEMO application with the exception of registering the resource definition file. To use the batch file instead of performing these tasks one at a time as outlined in the following sections, start an Enterprise Developer command prompt, change to the directory where your MFDEMO files are located, and execute build.bat. Then follow the procedure to register the resource definition file.

Copy the MFDEMO Files

Start an Enterprise Developer command prompt
Note: Keep this command prompt open, and use it for each task included in this topic.
Create a new directory to hold your copy of the MFDEMO application files.
Note: From this point forward, we refer to this as your "working directory" in all topics that are part of the IMS Installation Verification documentation.
Copy the MFDEMO application files from their installation location to your working directory. By default, the installation location is %PUBLIC%\Documents\Micro Focus\Enterprise Developer\Samples\Mainframe\IMS\Classic\IVP for 32-bit, and IVP64 for 64-bit (Windows) or $COBDIR/demo/ims/ivp32 for 32-bit, and ivp64 for 64-bit (UNIX) .

Compile the COBOL Programs

At the same Enterprise Developer command prompt in your working directory, enter the following commands, depending on your platform:

Windows:

cobol demo001b dialect(vsc24) noflag anim noobj charset(ascii) outdd"sysout 121 r e";
cobol cdlidemo dialect(mf) osvs cicsecm noflag charset(ascii) anim noobj;
cobol execdemo dialect(mf) cicsecm execdli noflag charset(ascii) anim noobj;
cobol demo001t dialect(vsc24) noflag charset(ascii) anim noobj;
cobol rghtjust dialect(mf) charset(ascii) anim noobj;

UNIX:

cob DEMO001B.cbl -C "dialect(vsc24) noflag anim noobj charset(ascii) outdd(sysout 121 r e)"
cob CDLIDEMO.cbl -C "dialect(mf) osvs cicsecm noflag charset(ascii) anim noobj"
cob EXECDEMO -C "dialect(mf) cicsecm execdli noflag charset(ascii) anim noobj"
cob DEMO001T.cbl -C "dialect(vsc24) noflag charset(ascii) anim noobj"
cob RGHTJUST.cbl -C "dialect(mf) charset(ascii) anim noobj"

Generate the MFS Files

MFDEMO includes the demo90, demo91, and demo92 MFS files. To generate them, do one of the following:

Enter these three commands consecutively:

mfims mfsgen demo90.mfs nocls
mfims mfsgen demo91.mfs nocls
mfims mfsgen demo92.mfs nocls
mfims mfsgen print.mfs nocls

Or,

Enter this command:

for %i in (*.mfs) do mfims mfsgen %i nocls

Generate the DBD File

MFDEMO includes the demo03dd DBD file, which requires generation. The generated files, dbdgen2.dat and dbdgen2f.dat, contain information extracted from the DBD source and formatted into a smaller structure optimized for faster access during execution. They are indexed files and can contain information for one or more generated DBD members.

Important: Do not edit, move or delete the generated files.

Enter this command:
```
mfims dbdgen demo03dd.dbd nocls echo(enderr,0,50)
```
Note: If dbdgen2.dat does not already exist when you generate the DBD, you see the message DBDUT0U35U File not found DBDGEN2.DAT. This message is for information only. In this case, the dbdgen2.dat file is created during generation.

Generate the PSB File

MFDEMO includes the demo001t PSB file, which requires generation. The generated file, psbgen3.dat, contains information extracted from the PSB source and formatted into a smaller structure optimized for faster access during execution. This an indexed file, and can contain information for one or more generated PSB members.

Enter this command:
```
mfims psbgen demo001t.psb nocls echo(enderr,0,50)
```
Note: If psbgen3.dat does not already exist when you generate the PSB, you see the message DBDUT0U35U File not found PSBGEN3.DAT. This message is for information only. In this case, the psbgen3.dat file is created during generation.

Register the Resource Definition File

Enterprise Server supports two transaction types, named /CIC and /IMS respectively. They are defined in a provided resource definition file, dfhdrdat. When you register this resource definition file with Enterprise Server, it enables your enterprise server region to switch back and forth between CICS and IMS modes. This is required to run the MFDEMO application because IMS applications running on Enterprise Server use the automatic message processing region feature provided by our CICS technology.

In general, we recommend that you leave the installed dfhdrdat file intact in its default location, and copy a new instance of the file into your working directory.

Copy the default resource definition file installed with Enterprise Developer, dfhdrdat, from its installation directory to your working directory. The default installation directory for dfhdrdat is %ProgramFiles(x86)%\Micro Focus\Enterprise Developer\etc\cas.
At an Enterprise Developer command prompt, change to your working directory.
Enter the following command:
```
caspcupg /dp=.
```

Load the Database

Enter this command:
```
mfims imsdbu load demo03dd nocls
```

Import IMS Transactions

When you migrate an IMS application from the mainframe to Enterprise Developer, one of the required mainframe files is the stage 1 file containing your IMS transactions. In this demonstration, we have downloaded the MFDEMO stage 1 file for you, and then exported its contents to a flat text file, trancode.txt, which is included in the MFDEMO demonstration files. You need to create the standard data file used by Enterprise Server, imsgen2.dat, and import trancode.txt into it. To do both of these:

Enter this command:
```
mfims stage1imp trancode.txt
```