To be able to start a CICS or JES region, a region startup file must first be created and associated with the region in the Enterprise Server for .NET Administration UI. The region startup file defines the characteristics of the region to be started and the locations of programs and data used by the region at run time.
Region start-up files are created and edited using the Enterprise Server for .NET Administration UI's Region Startup File Editor. These files can be persisted either to a local/network file system or to a cross-region database. A region startup file may be shared by multiple regions.
In addition to region startup files, CICS regions must also have a resource definition file associated with them. 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.
A region database is created the first time a region is cold-started. A region database will always be re-configured each time the region is cold-started using the information in the region startup and, for CICS regions, resource definition files. When a region is warm-started, it starts using the configuration held within the region database rather than the region startup and resource definition files.
The user interface cannot connect to the region database. This typically appears when you first define a region and have not yet started it. The region database for a new region is not created until you start it.
An existing region database is not associated with a region startup file.
The region has a startup file and an associated database.
This icon appears while the system determines the region's state.