Datasheet

Release Notes - New Features included in Release 2.4.0
Page 74 of 89
DREQ - New Error Message Enquiry
The searching criteria has been enhanced, so that all fields may be used. With the exception of the
Module field, partial values may be entered into each field, which will display all entries ‘starting’
with the entered string. If the first character entered is a ‘%’, then all entries ‘containing’ the entered
string will be returned. In addition, the ‘Error message’ field will perform a case insensitive search.
DRSx - Custom Scroll Line transactions
These will now display a list of datanames and their position numbers. Following this the event
details will be displayed in the format that will appear on the screen / report.
DREx - New Error Message transactions
The warning message about the length of the message will now only be displayed if the message is
being added / changed. Changes have also been made to correctly update the ‘next number’
message.
4.3.5.16 Processor Monitor - Dynamic Instance Reconfiguration (SR2570)
The Processor Monitor has been enhanced to allow a TROPOS instance to be dynamically
reconfigured, i.e. to have various aspects of its run-time configuration changed without the need to
restart it. Dynamic reconfiguration is not expected to be a regular requirement. It is however
expected to be useful on occasion, particularly when it is required to increase the maximum number
of concurrent Clients, Online Servers and/or Background Servers, which can now be achieved
without disruption.
Dynamic reconfiguration is achieved in 2 stages. First, the appropriate instance configuration must
be changed as required by using the appropriate transactions from the XSMN group. When the
required new configuration has been set up the second stage is to impose it onto the running
instance. This is done either from the Manager Client, using the OPEC transaction, or from a
control-mode Operator Interface, using the ‘reconfigure’ command.
Dynamic reconfiguration is not ‘open-ended’, i.e. the maximum numbers of concurrent Clients,
Online Servers, Background Servers and Operator Interfaces cannot be increased beyond the
absolute configured limits with which the instance was started. These absolute limits are a new part
of the configuration parameters for each instance. They can be changed on the database by the
XSIC transaction but any such changes can only be applied to the instance itself by restarting it.
These limits are only picked up from the database configuration when an instance is started up, not
when it is dynamically reconfigured.
Note: It is still the value for the maximum number of clients, not the new client limit, which must not
exceed the licence value.
Apart from these absolute limits, all of the instance configuration parameters can be reset during a
dynamic reconfiguration. Most changes will affect how the Processor Monitor controls the instance
following the reconfiguration and some of these will also require the Processor Monitor to take
some immediate action to adjust the current configuration to fit the changes. A few possible
changes will have no effect because they only define the instance start-up status, e.g. whether the
Online Servers are brought up when the Processor Monitor initialises.
The configuration values which may be changed, and the effect they have when changed by a
dynamic reconfiguration are described below: