Configuring the Server

The MFBSIEMX module must be defined as an Event Manager user exit and the variable MFBSI_DIR must be specified in the Configuration Information field under the General tab, similar to following example:

[ES-Environment]
ES_EMP_EXIT_1=mfbsiemx
BASE=/home/pringo/mfcobol/mfbsi
MFBSI_DIR=$BASE/$ES_SERVER

Where:

ES_EMP_EXIT_n

n must be a number ranging from 1 to 9, based on the number of Event Manager user exits for the region:

This must be set to 1 if MFBSIEMX is the only Event Manager user exit for the region.
When multiple Event Manager user exits are defined, they must be specified in a sequence starting with ES_EMP_EXIT_1, for example:
```
ES_EMP_EXIT_1=mfbsiemx
ES_EMP_EXIT_2=mfmonemx
ES_EMP_EXIT_3=...
```
Note: mfbsiemx must be in lowercase on UNIX and Linux platforms.

MFBSI_DIR

This identifies the base folder to be used by MFBSI. This is the folder where the MFBSIJCL log files, any semaphore files (JOB#####.sem), and substituted JCL members are written to.

By default, the MFBSIJCL component that is submitting jobs to the enterprise server requires the MFBSI_DIR environment variable with the same folder setting.

When running inside a Performance and Availability Cluster (PAC):

With enterprise server instances running on a multiple hardware virtual machine:
- Specify one MFBSI_DIR directory or folder for each hardware or virtual machine directory or folder names can be freely chosen.
- Copy your mfbsi.cfg into these directories or folders.
With enterprise server instances running on a single hardware or virtual machine:
- Specify one MFBSI_DIR directory or folder for this hardware or virtual machine. Use this directory or folder for each enterprise server instances. The directory or folder name can be freely chosen.
- Copy your mfbsi.cfg into this directory or folder.

When not running in a PAC, there are two ways to specify MFBSI_DIR for a specific enterprise server instance:

Micro Focus recommends that you specifying a folder that has the name of enterprise server instance as the last part of the MFBSI_DIR path.
Note: In previous releases of this product, this was the only way to configure MFBSI_DIR. This constraint has been relaxed from version 3.0 of Enterprise Developer and Enterprise Server.
Alternatively, you can set MFBSI_DIR to any path on your file system. In this case, you must specify the target enterprise server instance name either on the MFBSIJCL command line (by specifying REGION=ESRegionName) or in the mfbsi.cfg configuration file (on a line that starts with REGION=ESRegionName).

When STRIPSPACE=OFF is set in your global EXTFH configuration file, an exception is required for MFBSI. You need to add the following to your extfh.cfg file:

[FOLDER:FullPathtoMFBSI_DIR] 
STRIPSPACE=ON

For example:

On Windows, if MFBSI_DIR=D:\mf\MFBSI\ES\MFBSI, add:
```
[FOLDER:D:\mf\MFBSI\ES\MFBSI]
    STRIPSPACE=ON
```
On UNIX, if MFBSI_DIR=/mf/MFBSI/ES/MFBSI, add:

[FOLDER:/mf/MFBSI/ES/MFBSI] 
    STRIPSPACE=ON

MFBSI_DIR examples

See the following examples of how to specify MFBSI_DIR:

Important: Ensure that the Enterprise Server admin user and the user authority which runs MFBSIJCL have a write access to the MFBSI_DIR location.

MFBSI_DIR supports long and spacey folder names. However, Micro Focus recommends that you avoid using them.

Micro Focus recommends that you use the default settings for MFBSIJCL to specify the enterprise server instance name as part of MFBSI_DIR:

To set MFBSI_DIR to a path that ends with a folder that has the same as the enterprise server instance name and with the default settings for MFBSIJCL:

export MFBSI_DIR=/MF/…/MFBSI/ESRegionName

To set MFBSI_DIR to any folder:

To specify the region name at the MFBSIJCL command line, execute:
```
export MFBSI_DIR=/MF/.../MYDIR
mfbsijcl ...  REGION=ESRegionName
```
To specify the region name in the default mfbsi.cfg file:
1. Ensure mfbsi.cfg includes the following line:
```
REGION=ESRegionName
```
2. Set MFBSI_DIR to the location of mfbsi.cfg:
```
export MFBSI_DIR=/MF/.../MYDIR
```
To specify the region name in a custom configuration file, custom.cfg, located in /MF/.../MFBSICFG/:
1. Ensure custom.cfg includes the following line:
```
REGION=ESRegionName
```
2. Set MFBSI_DIR as follows:
```
export MFBSI_DIR=/MF/.../MYDIR
```
3. Specify the custom configuration file when executing MFBSIJCL as follows:
```
mfbsijcl ... CFG=/MF/.../MFBSICFG/custom.cfg
```
  Or, without specifying the CFG parameter:
```
mfbsijcl ...
export MFBSI_CFG=/MF/…/MFBSICFG/custom.cfg
```

After making these settings in the region configuration, restart the server and check the console log for the message CASAM3006I/CASAM3001I to verify successful initialization of MFBSIEMX. Log entries are similar to:

CASAM3006I Event Filter for (mfbsiemx) has been enabled. Filter string: "1:1,3&3:*&4:1,2"
CASAM3001I Event Manager exit enabled (mfbsiemx)

If an issue occurs, check the messages in the Enterprise Server console.log file to see what the issue is. For example:

JCLSI0300E mfbsiemx initialization failed: MFBSI_DIR not defined in [ES-Environment]

JCLSI0301E STRIPSPACE=OFF set in EXTFH. Not allowed for MFBSI .sem files

Server initialization creates a file named ESRegionName.Started in the MFBSI_DIR location. When the server shuts down, a file named ESregion.shutdown replaces this file, where ESRegionName is the name of the region being used.

In order to restart any submitted jobs, you need to add some additional configuration settings in your enterprise server instance. See Job Restart for more information.