BlueZone is capable of automatically loading configuration files that are identified using a specific naming convention.
Using this method, you can automatically configure all sessions identically, automatically configure multiple sessions differently,
and automatically update configurations that are locked from user tampering. In BlueZone, these automatically loading configuration
files are universally called start files. There are several types of start files.
Use a start configuration file
System administrators and users can pre-configure a BlueZone session by saving the desired configuration settings to a file
named start and then including the file on the BlueZone distribution diskette. When a BlueZone session runs for the first time, a configuration
does not exist in the registry. If BlueZone does not file a configuration in the registry, BlueZone automatically looks for
a Start.zxx configuration file and auto-opens the file if it exists. Each time a new session is launched, BlueZone loads the settings
contained in the Start.zxx file.
If a valid configuration already exists in the Registry for that session, the Start.zxx file is ignored.
For example, if you want your end users to automatically load a specific BlueZone Mainframe display session, create a BlueZone
Mainframe configuration and name it
start.zmd.
CAUTION
The
Start.zxx file or files must be located in the same directory as the main BlueZone program files. Not the
Config directory. The
Start.zxx files are ignored if they are placed in the
Config directory.
All BlueZone file extensions can be used with a Start.zxx files.
Use the Sx configuration file
If you want to distribute BlueZone pre-configured for more than one BlueZone session, use the following syntax. Instead of
creating one file with the name Start.zxx. You can create as many files as you need with the name Sx where x is the session identifier.
For example, to pre-configure two BlueZone Mainframe display sessions, create the first configuration file and name it S1.zmd. Then create the second one and name it S2.zmd.
The same rules that apply to start files apply to Sx files except that each Sx file only configures one session with that corresponding session number.
For example, S1.zmd automatically loads the configuration for session S1. S2.zmd automatically loads the configuration for session 2.
Use the SxLOCK configuration file
An additional option is available to administrators who need to be able to pre-configure sessions that load every time a BlueZone
sessions is launched. The main purpose for this option is to provide a way to update BlueZone sessions when the BlueZone
global lock feature is used.
For example, to pre-configure two locked BlueZone Mainframe display sessions, create the first configuration file and name
it S1LOCK.zmd. Then create the second one and name it S2LOCK.zmd.