This chapter presents information you might need to be aware of when deciding how to install Mainframe Express. Details of how to start the installation process are contained in the Installation Notes, which you can view when installing Mainframe Express.
You can install Mainframe Express in a number of different ways:
The following table shows the advantages and disadvantages of each different method of installing Mainframe Express:
The Protection System is software that ensures that your Mainframe Express runs on only as many computers as a site has licenses for.
Mainframe Express can run only if a valid license is present on the computer. A permanent license is known as a full license. A license lasting for a limited time is called a time-limited license. With some products, a time-limited license is installed with the product for evaluation purposes.
Users can manually request a license directly from MERANT International. Administrators responsible for multiple users can use a License Server to generate licenses automatically or manually .
Licenses obtained from MERANT International
When a user loads Mainframe Express without a full license, he or she receives a request key which should be sent to MERANT International. A response key will be generated by MERANT International and returned to the user. The user can then load Mainframe Express using this response key.
Licenses obtained using the License Server
If a user's license expires:
Online help information can be accessed from the Mainframe Express Protection System screen. This screen is displayed when you load Mainframe Express if it is not fully licensed. Otherwise you can access online help information from the Mainframe Express Protection System Configuration screen. You can access the Mainframe Express Protection System Configuration screen from the Windows Start menu.
If you have set up a number of Mainframe Express users, you might want them all to use a certain set of files to make sure they are all peforming the same standard functions. You can distribute files to ensure that multiple users have the same:
If you are working on a large project containing many different files, defining that project on each Mainframe Express user's PC would be a very time-consuming task. Fortunately, once you have created a project (.mvp) file on one machine, you can copy it to any other machine where it is instantly usable.
To copy a project from one machine to another, all you need to do is copy the relevant .mvp file in exactly the same way as you would copy any other file between machines. You might want to create a project folder structure on the target machine similar to that on the source machine, which is typically \mfuser\projects\project-name.
Note: The location of files on the source machine must be the same as the location of those files on the target machine. For example, if you are copying a project from machine A to machine B, where the source code on machine A is in subfolders of the folder f:\bankapp, machine B must also have a folder f:\bankapp.
Mainframe Express provides skeleton CLISTs in the folder mfuser\sysproc. These skeleton files, of the form userxxxx.tso, show how you customize initalization and termination logic for TSO, CICS Option and IMS Option modules.
If you have edited these CLISTs and want to make them generally available to other users you simply need to copy the relevant .tso files into the mfuser\sysproc subfolder on the target machine.
When you install Mainframe Express onto a server, you need to run the Client Install Configuration utility to configure the client install. Full instructions are given in the Introduction to the Read-Me, which you can view when installing Mainframe Express. When you run this utility, the Mainframe Express Tools settings on the server are automatically made available for inclusion on the client machine.
To ensure that current and future client installations remain consistent you should do the following:
Copyright © 1999 MERANT International Limited. All rights reserved.
This document and the proprietary marks and names used herein are protected by international law.