The main MFBSI documentation is in the Enterprise Developer product help (see Micro Focus Batch Scheduler Integration) and applies to the native Enterprise Server product. The architecture of Enterprise Server for .NET implementation is slightly different although the main functionality is the same.
The main things schedulers need that aren't provided by cassub/ cassout are a way to determine when a job has finished, and what the results of the job (status, exit code, output) were. MFBSI does this by creating files in an MFBSI work directory as jobs are processed.
The default MFBSI user exit called mfbsiemx.dll has been compiled into managed code and is included in the \binAnyCPU\SEE folder and will be on the path provided by the Enterprise Server command prompt.
The mfbsijcl utility is common to Enterprise Server andEnterprise Server for .NET and should be on the path set by the Enterprise Developer command prompt.
mfbsiemx and mfbsijcl both need two environment variables set in order to function correctly. Setting environment variables for mfbsiemx means setting them in the seepubsub environment (as discussed below). For mfbsijcl, you can set them in the command session where you are running mfbsijcl, if you have started it manually. If you want to run it under control of a scheduler, you might want to put it in a script.
The variables are:
These variables can be included in the seepubsub.exe.config file as described in the section seepubsub Configuration File.
As described in the MFBSI documentation, you need to create an MFBSI configuration file, which you'll put in the MFBSI work directory. This is a text file named mfbsi.cfg with a simple format covered in the MFBSI documentation.
The following is an example mfbsi.cfg file:
* Configuration file for MFBSI * How to contact the server ES-Server=-stcp:localhost:9122 * How to submit JCL, and path to folder containing it JCL-Submit=-jD:\dev\jcldemo * Extension for JCL files JCL-Ext=jcl * Let MFBSIJCL wait for region startup if a job is pending ES-SHUTDOWN-JWAIT=continue * Request JESYSMSG log from ES and write it to file <sjobid>.log JESYSMSG * Form sjobid from the ES job number SJobID=JobNo
The critical parameter for Enterprise Server for .NET is ES-Server, which specifies how to connect to the region for the cassub and the casout commands. It must use the "-s" form (for example - "-s:tcp:localhost:9022"), because Enterprise Server for .NET does not support the other options.
This is the development configuration, similar to running self-hosted dispatcher and SEPs. The main advantages are:
Interactive mode is not ideal for production use, but might be useful when developing an MFBSI configuration.
This is the recommended production configuration.
To see MFBSI in action, you can run mfbsijcl manually to have it submit a job, and then check the results. You can also execute it using a third-party scheduler.
In either case, the JCL source you wish to submit must be in the directory specified by the JCL-Submit directive in your MFBSI configuration file. You can use the JCLDEMO.JCL sample that comes with Enterprise Server (located in \etc\SEE\files\sysunder your product installation directory).
Running mfbsijcl manually