--- how to install master hotfix ---

1. copy the jar file (master-3.10.0-21.jar) in $ACTISEDI/lib/jcontroller/

2. edit the file $ACTISEDI/lib/jcontroller/config/jcontroller.classpath and replace the line:
master-3.10.0-xx.jar   (for example master-3.10.0-18.jar)
with
master-3.10.0-21.jar

3. master stop

4. Set the value of accounting_in_file parameter in ediboss.par,"to the desired value.
The default value of the parameter is "n" , so the write of accounting information in a file on disk will be disabled, if no value is set in ediboss.par
For more information please see below the description of the correction for #TSIM-3777, that is included also in this hotfix

5. master start




--- Additional info ---

This hotfix includes the fixes from SP15-P06 , plus the fixes 

JIRA Ticket #TSIM-3660
Customer Case ##01099145, ##01076112, ##01075611
Title: JOB parameters are loosing their value at master reconfig
Fixed: This problem affects only the jobs that are active during reconfig.
To solve it, it was moved the reload of event params in the same method that reloads job parameters,
to avoid the creation of an object that doesn't contain event attributes.
Also log a warning in logb and madeb when event attributes are null.

JIRA Ticket #TSIM-2956
Customer Case #01028341
Title: Master reconfig blocked - wait for time thread termination
Fixed: Decrease the priority of Remove threads, to ensure that Runtime threads do not get stuck waiting for resources.

JIRA Ticket #TSIM-3777
Title: Enabling accounting parameters on both DB and files
Fixed: Added a new parameter in ediboss.par: accounting_in_file. This parameter enables/disables accounting in file.
Default value is "n". Accepted values: "n" and "y".
Now should be possible to have accounting in file and in database in the same time.
Limited the scope of old accounting_in_db parameter to only enable/disable accounting in database.
The functionality of the new and existing parameters will be the following:
- if accounting_on=y, accounting_in_db=y and accounting_in_file=y, accounting information is stored in both DB and file.
- if accounting_on=y, accounting_in_db=n and accounting_in_file=y, accounting information is stored only in file. 
- if accounting_on=y, accounting_in_db=y and accounting_in_file=n, accounting information is stored only in DB. 
- if accounting_on=n, accounting information is not stored regardless of the values of the other two parameters.
- if accounting_on=y, accounting_in_db=n and accounting_in_file=n, accounting information will not be stored.

