A region startup file defines the characteristics of the region and the locations of programs and data used by the region at run time. You must have a region startup file before you can create or start a CICS or a JES region. Afterwards, you can edit the region startup file to provide further configuration.
A single region startup file may be shared across multiple regions.
Startup files are in XML format with a filename extension of .config. The information stored in a region startup file varies depending on the type of region it describes - CICS or JES.
You can create and edit region startup files using the Region Startup configuration editor in the Enterprise Server for .NET Administration UI. These files can be saved to a local or network file system or to a cross-region database.
When you create a new region startup file, Enterprise Server for .NET populates it with default settings. Most of these settings do not require further consideration; however, you can customize a new startup file by altering the default settings as you see fit.
CICS only:
JES only:
You can create a CICS region startup file from scratch, or use the provided sample CICS region startup file, Region_ESDEMO.config as a template. Region_ESDEMO.config is used by the sample ESDEMO region, and is located by default in the %ProgramData%\Micro Focus\Enterprise Developer\7.0\SEE\config directory.
In addition to a region startup file, a CICS region might also have a resource definition file associated with it. The location of the resource definition file is specified in the region startup file. Resource definition files are created and edited using the Enterprise Server for .NET Administration UI's CICS Resources File Editor. These files can be persisted either to a local/network file system or to a cross-region database. A resource definition file may be shared by multiple CICS regions.