Date: 07-02-2007 Subject: RELEASE 9.2 Data Manager Files These release notes pertain to the following programs or files: SUNDM.EXE 9.2 02 Jul 2007 9,2,0,0 SUNWSRV.DLL 9.2 02 Jul 2007 9,2,0,0 *============================================================================== Notes for some NEW Items: - The SUNFM File Manager has been replaced by the SUNDM Data Manager. *============================================================================== Notes for WARNINGS: - SUNDM uses the new configuration file named 'sundm.cfg' by default. *============================================================================== The following files have been changed as follows: ------------------------------------------------------------------------------- SUNDM - Modified the Data Manager to provide start, restart, and terminate icons that are available as resources. - The SUNFM file manager has been replaced by the SUNDM data manager. All of the operations provided by the SUNDM data manager are the same as previously implemented for the SUNFM file manager. - Added a log message to give the current Logon User Name that starts the data manager. - The log file name format for SUNDM has been modified to support a leading '#' control character. When a leading '#' character is specified, then the log file startup causes any new log entries to be appended to the end of a currently existing log file. Example of SUNDM.CFG log name entry: FM_LOGNAME=#dm.log In this case, the current logfile named 'dm.log' is used. If the 'dm.log' exists when the server is started, then any new log data is appended to the end of the exists log file. - The log file name format for SUNDM has been modified to support an embedded control named '@T' or '@t'. This new control is replaced with the current clock time in the log file name. This new control can be used in addition to other file name controls. Example of SUNDM.CFG log name entry: FM_LOGNAME=dm@D_@T.log In this case, the current logfile name includes the current date and time as part of the log file name. This gives a unique log file name that should never conflict with any previously existing log files. The log file name could resolve to a name like: "dm070620_110823.log" - Modified the SUNDM '-i' option to allow a logon user account and password to be specified for an NT Service that is created. This change allows Logon ownership for the data manager process and optional mapped drives. Formats of '-i' command line option: '-i' Create an NT Service for the server and the Logon user account is the Windows OS 'Local System' account. '-il' Create an NT Service for the server and the Logon user account is the Windows OS 'Local Service' account. '-in' Create an NT Service for the server and the Logon user account is the Windows OS 'Network Service' account. 'i=UserName;Password' Create an NT Service for the server and the Logon user account is a current user logon and password that has been created for the system where the server NT Service is created. The username and password is authenticated. If they are bad or do not exist, then the NT Service is not created. An appropriate Windows Error Code is provided when an error occurs. Note: 1. The 'Local System' logon account is a Windows OS built-in service logon that is global to all users on a workstation. Any mapped drives added for the 'Local System' logon are visible to any users that are logged on to the workstation. However, any mapped UNC network drives added under the 'Local System' can not be managed by any logged on users. In addition, a mapped UNC network drive can cause possible conflicts. This is documented as expected behavior by the Windows OS documentation. 2. The 'Local Service' logon account is a Windows OS built-in service account. This logon account restricts privileges to provide access to the local system. Any mapped drives using this logon account are not visible to any normal users logged on to the server system. 3. The 'Network Service' logon account is a Windows OS built-in service account. This logon account allows privileges that allow process to access a network beyond the scope of the local server system. Any mapped drives using this logon account are not visible to any normal users logged on to the server system. 4. Normal user logon accounts can be used for an NT Server and any mapped drives are not visible to any other users logged on to the server system. - Added mapped drive support for the Windows version. A new section named '[mapdrives]' can be added to the SUNDM CFG file. Mapped drive assignments can be specified in the mapdrives section. The SUNDM data manager uses the mapped drive settings to redirect either network drives or local DOS drives. Format: {drv}:=[~]{redir} Where: {drv} - Drive device letter ( a to z ) inclusive. {redir} - Drive device redirection string. This string can be a UNC path or a DOS drive path. [~] - Optional character before the {redir} string to prevent removal of the {drv}. Example of section in CFG file: [mapdrives] f:=c:\temp g:=\\server\sharename\directory h:=~c:\sunbelt i:=~\\server\sharename\directory Notes: 1. When the {redir} string start with the '\' character, then the redirection string identifies a network UNC path name. In this case, the {drv} is redirected as a network drive. If the {drv} already exists, then the mapped drive redirection does not occur and no changes are made. 2. When the {redir} string is a DOS drive path string, then the mapped drive redirection is executed as a local DOS drive device. In the {drv} already exists, then the mapped drive redirection does not occur and no changes are made. The local DOS drive substitution is NOT support for the Windows 95, 98, and ME OS versions. The mapped drives are ignored for these Windows version. 3. The mapped drives redirection support can be used to declare drive specifications when an NT server is started. 4. By default, the data manager removes the {drv} mapped drive when the data manager is terminated. If the '~' character is specified as the leading character before the {redir} string, then the data manager DOES NOT remove the {drv} when it is terminated. 5. When the data manager starts the mapped drives are logged and the mapped drives are logged when the server terminates. - In release 9.1C the file manager was modified to improve the efficiency for the execution of all child threads. The change in 9.1C caused any excess OS idle time to be used by any SUNFM child threads that were attempting to lock a file. There were side affects for the 9.1C changes. 1. The CPU usage for the SUNFM main process would increase as more user applications attempted to lock more files. 2. As more child threads were attempting to lock file, then other child threads that were not locking would execute slower. This symptom was caused because all of the Windows OS idle time was being distributed across all active child threads attempting to lock files. 3. When a large number of child threads were attempting to lock files, then the server system could become slower than normally expected. To avoid the side affects caused by the 9.1C SUNFM changes, the 9.2 version of SUNDM has been changed to waste some time while a program is waiting to lock a file. This change is being made to allow more Windows OS idle time to exist. With the change for 9.2, the runtime waits for 1ms after a lock has failed. In addition, a new keyword named 'PLB_OSIDLETIME={ms}' has been added. The {ms} setting can have of value of 0 to 10. If a value larger then 10ms is specified, then the maximum of 10ms is used. If this keyword is not specified, then the default of 1ms is used for the OS idle time setting. A general interpretation for the PLB_OSIDLETIME setting values is defined as follows: {ms} Windows OS Idle Time Affect 0 - The Windows OS Idle time is minimized. The SUNDM child threads DO NOT waste any time. 1 - The SUNDM child threads waste 1ms time. This is the default value when the PLB_OSIDLETIME keyword is not specified. ... ... 10 - The Windows OS Idle time is maximized. The SUNDM child threads waste 10ms time. - Corrected a problem where the INDEX instruction was overwriting an ISI file that was already opened as a managed file by the data manager. ------------------------------------------------------------------------------- SUNDM - In release 9.1D, there was a problem that could cause an IFILE (Unix) operation to fail for some logic sequences. This problem was caused by changes made in the 9.1D release and the problems were corrected in the release 9.1E. Example: OPEN IFILE... READ IFILE,KEY;; ;Ok READKS IFILE;Data ;Ok . UPDATE IFILE;NewData ;Premature Failure with an OVER flag! ------------------------------------------------------------------------------- SUNDM REPLICATION SUPPORT - Added a new keyword named 'NO_FILE_DELETES={on|off}'. By default this keyword is set to OFF when it is not specified in the Primary replication SUNDM CFG file. This keyword is only specified in the [replication] section of the SUNDM CFG file for the Primary data manager. When this keyword is set to ON, then files on any Secondary/Backup replication data managers are not deleted and they are renamed as '_.' instead. - Added a new keyword named 'SECONDARY_SCAN={on|off}'. By default this keyword is set to OFF when it is not specified in the Primary replication SUNDM CFG file. This keyword is only specified in the [replication] section of the SUNDM CFG file for the Primary data manager. When this keyword is set to ON, then files on any Secondary/Backup replication data managers are scanned using the current file list and the following scanning actions are performed: 1. Any files or directories in the current file list that have been deleted from the Secondary/Backup system are restored from the Primary replication data manager. 2. Any files that have been changed are restored from the Primary replication data manager. 3. When extra files or directories are detected on the Secondary/Backup replication data managers and these files do not exist in the current file list, then they are renamed using the '_.' format. - When the NO_FILE_DELETES and SECONDARY_SCAN keywords are used, then they take affect for all Secondary/Backup replication data managers. However, these keywords can be turned OFF or ON for individual servers by appending additional configuration flag settings to the end of the HOSTnn keywords. This is done by appending a ':' character after the port number and flags can be set or cleared. The flags are represented by alpha characters in a comma separated list. A leading '-' character indicates that the flag is to be cleared. The flags in the HOSTnn keyword override the global NO_FILE_DELETES and SECONDARY_SCAN keyword settings. The currently supported flags can be specified as follows: N or n The NO_FILE_DELETES is set to be ON for a specific HOSTnn server. -N or -n The NO_FILE_DELETES is set to be OFF for a specific HOSTnn server. S or s The SECONDARY_SCAN is set to be ON for a specific HOSTnn server. -S or -s The SECONDARY_SCAN is set to be OFF for a specific HOSTnn server. Examples: HOST01=N999999:192.168.110.99:3934:S,N HOST02=N999999:192.168.110.98:3934:S,-N - Added a new keyword named 'ALLOW_ALL_FILES={on|off}'. By default this keyword is set to OFF when it is not specified in the Primary replication SUNDM CFG file. This keyword is only specified in the [replication] section of the SUNDM CFG file for the Primary data manager. By default, any files and directories with a leading '_' character are ignored by the scanning process. By setting this keyword to ON, then files with a leading '_' character are not ignored and are included in the scanning process. - Modified the secondary replication server processing to allow the last modified time to be updated when the 'ALLOW_CHILD_LOGON=ON' keyword is being used when using a Unix version of a replication server. -------------------------------------------------------------------------------