Getting Started with BlueZone Desktop

Configuration Management

Automatically Configuring Sessions

BlueZone is capable of automatically loading configuration files that are identified using a specific naming convention.  The advantages of this method are; automatically configure all sessions identically, automatically configure multiple sessions differently, and the ability to 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.

Using 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 is run for the first time, a configuration will not exist in the registry.  If BlueZone does not file a configuration in the registry, BlueZone will automatically look for a Start.zxx configuration file and will “auto-open” the file if it exists.  Each time a new session is launched, BlueZone will load the settings contained in the Start.zxx file.

If a valid configuration already exists in the Registry for that session, the Start.zxx file will be ignored.

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.  See the table below for BlueZone configuration file extensions.

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 will be ignored if they are placed in the Config directory.

The following table shows the valid BlueZone file extensions that can be used with a Start.zxx files.

BlueZone Configuration File Extensions

Using the Sx Configuration File

If you want to distribute BlueZone pre-configured for more than one BlueZone session, simply us 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.  

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.

Example: S1.zmd automatically loads the configuration for Session S1. S2.zmd automatically loads the configuration for Session 2.

Using 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.

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.

Related Topics:

Configuration Files

Resetting Configuration Items