disponibile IBM Traveler 9.0.1.8

Disponibile su fixcentral IBM Traveler 9.0.1.8 che introduce un nuovo comando "tell dbmain ... ".

le fix di questo rilascio sono le seguenti:

APAR #	Abstract
LO85584	Explicit commit is not needed for database select statements.
LO86339	Warning may be displayed for redirect to SSL setting that is not in effect.
LO86341	Add covering index to improve performance of update queries.
LO86366	User may stop syncing after migration to HA environment AND change mail template.
LO86445	Traveler syncs attachments in very small chunks causing mail delays and possible server crash.
LO86448	Enable Calendar ghosting for ActiveSync devices when running on Domino 8.5.3 server.
LO86466	Get Error 400 trying to read encrypted e-mail on Companion app for Apple devices.
LO86496	Server crash on buffer over run error if log message is too long.
LO86500	Shake to undo folder move in native Apple mail client may not be reflected on server.
LO86516	PDF attachment not viewable if missing pdf extension.
LO86521	Principal field is blank on draft e-mail created by IBM Verse mobile client.
LO86530	Unnecessary error logging e-mails with attachments with no file name.
LO86562	Individually delete all instances of repeating meeting in IBM Verse mobile client will not delete all entries from server copy.
LO86610	Threaded e-mail move to folder not shown in new folder in IBM Verse client.

inoltre qui è possibile trovare la lettera di rilascio.

Il nuovo comando "tell dbmaint ...." supporta al mantenimento dei database, per la verifica dei livelli di frammentazione e per impostare e schedulare manutenzioni per ridurre la frammentazione degli indici delle tabelle.
Qui si travano alcune informazioni sul comando dbmaint  e di seguito la sintasssi completa (vedi anche l'elenco dei comandi traveler):

Usage: tell traveler DBMaint
Where includes:
Run                                  - Immediately performs online maintenance. If the server is standalone, then it will configure maintenance to run on restart.
Show                                 - Displays various database maintenance scheduling information.
Fragmentation                        - Recommends database maintenance based on fragmentation levels.
Set Interval                  - Sets the interval of days in which automatic database maintenance will perform.
Set Time                     - Sets the time in 24-hour format in which automatic database will perform.
Set Day          - Sets the day of the week for the first scheduled automatic maintenance to start from.
                                        Set to off if you want the first scheduled maintenance to be based off of the last maintenance time.
 Set Threshold               - Configures automatic database maintenance to check fragmentation levels before it will execute.
 Set Auto                    - Enablement for automatic database maintenance.
                                        Re-enablement will reschedule maintenance if either the time or interval have changed.
 Set Indexes                 - Configures the number of fragmented indexes for the fragmentation threshold.
 Set Ownership                        - Configures ownership of database maintenance to this server. This server will be
                                        the only server that can perform automatic database maintenance.
 Set Percent <0-100>                  - (ONLY FOR SQL SERVER) Configures the fragmentation percentage of indexes for the fragmentation threshold.
 Set Functions <1-4>                  - (ONLY FOR DB2) Configures the number of functions that are used to determine if an index is fragmented for the fragmentation threshold.    

previsto inoltre per il 14 Ottobre un webinar con Corey Quinn del team Traveler che presenterà tutte le novità incluso dbmaint.