Date: 02-28-2006 Subject: RELEASE 9.1 Runtime Files Files included with this release are: SUNFM.EXE 9.1 28 Feb 2006 9,1,0,0 SUNWSRV.DLL 9.1 28 Feb 2006 9,1,0,0 *============================================================================== Notes for some NEW Items: - The SUNFM file manager has been modified to support a replication network. - The Windows version of SUNFM has been modified to open managed files one time. - The SUNFHSYS DLL is not implemented for the 9.1 release. The 9.1 SUNFM does not require/use a SUNFHSYS DLL. *============================================================================== The following files have been changed as follows: ------------------------------------------------------------------------------- SUNFM - The SUNFM file manager has been modified to allow a file manager logon rollover sequence when the client uses the PLB_FMALTIP keyword. See the 'rel91.rfm' for more information on the PLB_FMALTIP keyword. - Modified the file manager to provide logon child count data to the ADMIN services. This information is provided via the ADMGETINFO instruction to determine the largest server child count since the server has started. - A new keyword named 'FM_OPENONCE={on|off}' has been added for the Windows SUNFM file manager. If this keyword is not specified in the SUNFM.CFG file, then by default this keyword setting is 'on'. When this keyword is set to be 'on' or it is not specified in the SUNFM.CFG file, then managed files at the SUNFM server are only opened one time at the server. This means that the server opens the file one time for all clients that access the same managed file and the file CAN NOT be opened by any applications that do not use the SUNFM file manager. If the FM_OPENONCE keyword is set to 'off', then the SUNFM file manager opens a file multiple times. This means that each client open operation causes the file to be opened. Note: The 9.1A release is to support the open once file capability for Unix/Linux. - A new keyword named 'FM_OPENONCE_FLUSH={on|off}' has been added for the SUNFM file manager. If this keyword is not specified, then the keyword setting is set to be 'off'. When this keyword setting is 'off' and the FM_OPENONCE setting is 'on', then the text file data is not flushed to the physical server disk after each PLB WRITE operation. This implementation for the files opened once can provide improved performance when writing to a managed file. If the FM_OPENONCE_FLUSH is set to 'on' then the text file data is flushed to the physical server disk after each PLB WRITE operation. - Corrected a problem where a MFD file could destroyed when a FILE, AFILE, or IFILE prep was executed using the MFD file and the PLB_PREPUSEIP keyword is being used. - Modified the PREP IFILE operation to perform a Windows OS file commit operation after the ISI header has been written. This corrects a problem where the ISI could be truncated when the ISI/TXT files existed on a Win95/98/ME system and were being accessed via a network-shared drive. ------------------------------------------------------------------------------- SUNFM REPLICATION SUPPORT - The SUNFM file manager has been modified to allow communication between multiple SUNFM file managers. This allows data files opened and written on a primary SUNFM to be replicated on secondary SUNFM file manager systems that have a TCP/IP network connection with the primary SUNFM server. The following SUNFM command line options have been added or changed for the replication network support. Command Line Options: -b The 'SUNFM -b' command line option is used to start a SUNFM server and to ignore the current replication settings. This causes a SUNFM server to be started in a special situation to allow users to logon to a SUNFM server without requiring the secondary SUNFM servers to be on line. -f The 'SUNFM -f' command line option executes the same as documented for the SUNFM server operations. When the primary SUNFM server stops executing, then all of the secondary SUNFM servers detect that the primary has logged off and they wait indefinitely for the primary to be restarted. -fa The 'SUNFM -fa' command line option executes the same as for the '-f' option except it causes all of the secondary/backup SUNFM servers to terminate in addition to the primary server. When this command line is executed for the secondary/backup SUNFM servers, then the command only executes as a single '-f' command. -fx The 'SUNFM -fx' command line option executes the same as for the '-f' option. When this command line is executed at the primary SUNFM server, then the primary SUNFM server is force to terminate and replication primary control is transferred to the first secondary server that currently exists in the network. When this command is executed at a secondary/backup SUNFM server, then the command only executes as a single '-f' command. -q The 'SUNFM -q' command line option executes the same as the '-f' command except it waits for any active FILEPI operations to be completed -qa The 'SUNFM -qa' command line option executes the same as the '-fa' command except it waits for any active FILEPI operations to be completed -qx The 'SUNFM -qx' command line option executes the same as the '-fx' command except it waits for any active FILEPI operations to be completed -s The 'SUNFM -s' command line option starts the SUNFM server and uses the current 'sunfmrep.fm' settings to start the SUNFM replication network. If replication is configured and the 'sunfmrep.fm' file does not exist, then the replication control file is created. If changes are made to the SUNFM CFG, then those changes automatically take affect during the SUNFM startup process. -t The 'SUNFM -t' command line option executes the same as documented for the SUNFM server operations. When the primary SUNFM server stops executing, then all of the secondary SUNFM servers detect that the primary has logged off and they wait indefinitely for the primary to be restarted. -ta The 'SUNFM -ta' command line option executes the same as documented for the SUNFM server operations. When this command line is executed at the primary SUNFM server, then all of the secondary/backup SUNFM servers also terminate. When this command is executed at a secondary/backup SUNFM server, then the command only executes as a single '-t' command. -tx The 'SUNFM -tx' command line option executes the same as documented for the SUNFM server operations. When this command line is executed at the current network primary SUNFM server, then the current primary SUNFM server is terminated and replication primary control is transferred to the next available secondary server. When this command is executed at a secondary/backup SUNFM server, then the command only executes as a single '-t' command. -u The 'SUNFM -u' command line option forces the primary SUNFM server to reprocess the keyword settings and update all of the replication server and file/directory settings for the network. The SUNFM replication network is setup by adding a [replication] section to the SUNFM.CFG file. The SUNFM replication network can be setup and used without having to make any changes to the user PLB applications. The following keywords can be placed in the [replication] section in a SUNFM.CFG file. Configuration Keywords: MANAGED_RECURS_DIRnn MANAGED_RECURS_DIRnn is used when the files in a directory are ONLY opened and written to when using PL/B applications to access the files through the SUNFM file manager. Replication processing for this mode of operation causes all files and sub-directories to be replicated when declared with the MANAGED_RECURS_DIRnn keyword. The 'nn' value for this keyword can be defined from '01' to '99'. This keyword must be specified in the 'replication' section that is included in the SUNFM.CFG configuration file for the Primary file manager server that is included in the replication network. Format: MANAGED_RECURS_DIRnn={primary}[ |{second1}[ |{second2}[...]]] Where: {primary} This parameter is a drive/directory specification that defines the replication directory to be used at the primary SUNFM server. The primary SUNFM is determined by the 'HOST00' keyword setting found in the SUNFM.CFG file. The {primary} is an OS specification. Any drives that are specified MUST be the physical drive specifications. {second1} This parameter is a drive/directory specification that defines the replication directory to be used at the first secondary/backup SUNFM server that is identified by the 'HOST01' keyword setting found in the SUNFM.CFG file. The {second2} is an OS specification. Any drives that are specified MUST be the physical drive specifications. {second2} This parameter is a drive/directory specification that defines the replication directory to be used at the second secondary/backup SUNFM server that is identified by the 'HOST02' keyword setting found in the SUNFM.CFG file. The {second2} is an OS specification. Any drives that are specified MUST be the physical drive specifications. Examples: MANAGED_RECURS_DIR01=c:\reptest In this case, all of the file managers in the replication network must have the exact same drive/directory to be used. MANAGE_RECURS_DIR02=c:\onprimary|d:\onsecondary In this case, the primary file manager is replicating the directory 'c:\onprimary'. The 'c:\onprimary' directory is mapped to replicate on the first secondary file manager in the 'd:\onsecondary' directory. Note: 1. When any {secondN} parameter is not specified in this keyword specification string, then the {primary} parameter is used as the default. 2. These keywords can be in any numerical order and can have any numerical 'nn' values. UNMANAGED_RECURS_DIRnn UNMANAGED_RECURS_DIRnn is used to invoke strict mode processing for the files and subdirectories that exist in a directory. The strict mode is used when files in a directory are being modified by applications that DO NOT use the SUNFM file manager. The SUNFM replication processing in this mode uses OS file time stamps and specialized comparison techniques to determine when files have been changed. Identified changes are transferred from the primary SUNFM to the secondary/backup SUNFM replication servers. The 'nn' value for this keyword can be defined from '01' to '99'. This keyword must be specified in the 'replication' section that is included in the SUNFM.CFG configuration file for the Primary file manager server that is included in the replication network. Format: UNMANAGED_RECURS_DIRnn={primary}[ |{second1}[ |{second2}[]]] Where: {primary} This parameter is a drive/directory specification that defines the replication directory to be used at the primary SUNFM server. The primary SUNFM is determined by the 'HOST00' keyword setting found in the SUNFM.CFG file. The {primary} is an OS specification. Any drives that are specified MUST be the physical drive specifications. {second1} This parameter is a drive/directory specification that defines the replication directory to be used at the first secondary/backup SUNFM server that is identified by the 'HOST01' keyword setting found in the SUNFM.CFG file. The {second2} is an OS specification. Any drives that are specified MUST be the physical drive specifications. {second2} This parameter is a drive/directory specification that defines the replication directory to be used at the second secondary/backup SUNFM server that is identified by the 'HOST02' keyword setting found in the SUNFM.CFG file. The {second2} is an OS specification. Any drives that are specified MUST be the physical drive specifications. Note: 1. When any {secondN} parameter is not specified in this keyword specification string, then the {primary} parameter is used as the default. 2. These keywords can be in any numerical order and can have any numerical 'nn' values. MANAGED_DIRnn MANAGED_DIRnn is used when the files in a directory are ONLY opened and written to when using PL/B applications to access the files through the SUNFM file manager. Replication processing for this mode of operation causes only the files in the specified directory to be replicated. Any subdirectories that exist under the specified directory are NOT replicated when the MANAGED_DIR is used. The 'nn' value for this keyword can be defined from '01' to '99'. This keyword must be specified in the 'replication' section that is included in the SUNFM.CFG configuration file for the Primary file manager server that is included in the replication network. Format: MANAGED_DIRnn={primary}[ |{second1}[ |{second2}[...]]] Where: {primary} This parameter is a drive/directory specification that defines the replication directory to be used at the primary SUNFM server. The primary SUNFM is determined by the 'HOST00' keyword setting found in the SUNFM.CFG file. The {primary} is an OS specification. Any drives that are specified MUST be the physical drive specifications. {second1} This parameter is a drive/directory specification that defines the replication directory to be used at the first secondary/backup SUNFM server that is identified by the 'HOST01' keyword setting found in the SUNFM.CFG file. The {second2} is an OS specification. Any drives that are specified MUST be the physical drive specifications. {second2} This parameter is a drive/directory specification that defines the replication directory to be used at the second secondary/backup SUNFM server that is identified by the 'HOST02' keyword setting found in the SUNFM.CFG file. The {second2} is an OS specification. Any drives that are specified MUST be the physical drive specifications. Note: 1. When any {secondN} parameter is not specified in this keyword specification string, then the {primary} parameter is used as the default. 2. These keywords can be in any numerical order and can have any numerical 'nn' values. UNMANAGED_DIRnn UNMANAGED_DIRnn is used to invoke strict mode processing for the files that exist in a single directory. Any subdirectories that exist in the specified directory are NOT replicated when this keyword is used. The strict mode is used when files in a directory are being modified by applications that DO NOT use the SUNFM file manager. The SUNFM replication processing in this mode uses OS file time stamps and specialized comparison techniques to determine when files have been changed. Identified changes are transferred from the primary SUNFM to the secondary/backup SUNFM replication servers. The 'nn' value for this keyword can be defined from '01' to '99'. This keyword must be specified in the 'replication' section that is included in the SUNFM.CFG configuration file for the Primary file manager server that is included in the replication network. Format: UNMANAGED_DIRnn={primary}[ |{second1}[ |{second2}[]]] Where: {primary} This parameter is a drive/directory specification that defines the replication directory to be used at the primary SUNFM server. The primary SUNFM is determined by the 'HOST00' keyword setting found in the SUNFM.CFG file. The {primary} is an OS specification. Any drives that are specified MUST be the physical drive specifications. {second1} This parameter is a drive/directory specification that defines the replication directory to be used at the first secondary/backup SUNFM server that is identified by the 'HOST01' keyword setting found in the SUNFM.CFG file. The {second2} is an OS specification. Any drives that are specified MUST be the physical drive specifications. {second2} This parameter is a drive/directory specification that defines the replication directory to be used at the second secondary/backup SUNFM server that is identified by the 'HOST02' keyword setting found in the SUNFM.CFG file. The {second2} is an OS specification. Any drives that are specified MUST be the physical drive specifications. {secondN} The secondary parameters can continue to be declared for each secondary SUNFM file manager that is to be used. Note: 1. When any {secondN} parameter is not specified in this keyword specification string, then the {primary} parameter is used as the default. 2. These keywords can be in any numerical order and can have any numerical 'nn' values. HOSTnn HOSTnn is used to specify the Sunbelt serial number, IP/URL address, and port number for the file manager servers that are to be connected for the replication network. All of the HOSTnn definitions must be defined in the SUNFM.CFG configuration file of the primary file manager for the replication network. Only the HOST00 need be specified in the SUNFM.CFG configuration file of the secondary file managers in the replication network. Additional HOSTnn information is transferred from the primary file manager to the secondary file managers during the startup processing. The 'nn' value for this keyword can be defined from '00' to '03'. This keyword must be specified in the 'replication' section that is included in the SUNFM.CFG configuration file for each file manager server that is included in the replication network Format: HOSTnn="dynamic" | [[serialnum]:{ip | URL}[:{portnum}] Where: ':' The ':' (colon) character is used in the HOSTnn data string as a delimiter separator between the serial number field, the IP/URL field, and the port number field. "dynamic" If the HOST01, HOST02, or HOST03 keywords are set to a string "dynamic", then this allows a backup SUNFM server to log on to the primary using a dynamic IP address. The feature is being implemented where the backup server does not have a static IP address. In this case, the serial number, IP/URL, and port number fields are not specified/used. {serialnum} The parameter is the Sunbelt 'Nnnnnnn' or the 'Dnnnnnn' serial number for the SUNFM file manager being used. The serial number can be found in the SUNFM header information or in a log file if a log is being used. If the SUNFM file manager is installed using the Sunbelt SUNFM Installation with the serial number specified as "demo", then the serial number for that demo file manager is automatically set to be 'D999999'. In the HOST00, this field defines the serial number for the Primary master file manager in the replication network. If the serial number has the format 'Dnnnnnn', then the Primary master file manager is executing in a demo mode. For the HOST00 keyword, this field is optional and if it not specified, then the current SUNFM serial number is used for the primary. For a Secondary file manager, this field is not used. This field in the HOST01 keyword data string defines the serial number for the first Secondary file manager in the replication network. If the serial number has the format 'Dnnnnnn', then the replication file managers execute in a demo mode. For the HOST01 keyword, this field must be specified. This field in the HOST02/HOST03 keywords defines the serial numbers for the second and third Secondary file managers in the replication network. For the HOST02/HOST03 keywords, this field must be specified. A 'Dnnnnnn' serial number is not allowed for the HOST02/HOST03 keyword settings. If the serial number in the HOST00 or HOST01 keywords is defined to be 'Dnnnnnn', then the SUNFM file manager replication network executes in a demo mode with the following restrictions: 1. The SUNFM replication network can only have a primary and one secondary replication server. 2. A single managed replication directory as specified by the 'MANAGED_DIR01' is replicated. 3. A single unmanaged replication directory as specified by the 'UNMANAGED_DIR01' is replicated. 4. All other replication directory keywords are ignored. 5. Additionally, any SUNFM file manager with the 'Dnnnnnn' serial number executes with a demo mode that has restrictions. These file managers have an elapsed time expiration date applied that prevents the file manager from loading/executing when the elapsed time expires. The 'Sunfm -e' command can be used to determine the expiration date. Also, these file managers are limited to two managed file logons at any given time. {ip | URL} This parameter is an IP address or the URL of the server executing the file manager task. The IP address is provided as a 'nnn.nnn.nnn.nnn' identifier. The HOST00 keyword defines the setting for the Primary master file manager in the replication network. The HOST01 keyword defines the setting for the first Secondary file manager in the replication network. The HOST02 keyword defines the setting for the second Secondary file manager in the replication network. The HOST03 keyword defines the setting for the third Secondary file manager in the replication network. {port number} This parameter is optional and it specifies the IP port number assigned to the file manager task. The 3934 port number has been assigned as a registered user port number by IANA (Internet Assigned Numbers Authority) and is the default port number used if the HOSTnn keyword does not have the port number field specified. This field for the HOST00 keyword defines the port number for the Primary master file manager in the replication network. This field for the HOST01, HOST02, and HOST03 keywords define the port number for the first, second, and third Secondary file managers in the replication network. Example1 (Primary) HOST00=N123456:63.162.221.99 HOST01=N000001:www.sunbelt-plb.com HOST02=dynamic HOST03=N000099:63.162.1.2:52105 Example2 (Primary) HOST00=:63.162.221.99 HOST01=N000001:www.sunbelt-plb.com Example3 (Primary Demo) HOST00=N123456:63.162.221.99 HOST01=D999999:210.211.1.2 Example4 (Secondary) HOST00=N123456:63.162.221.99 Example5 (Secondary) HOST00=:63.162.221.99 Notes: 1. The HOSTnn IP/URL settings identify the remote URL/IP address that is to be used when one replication server connects with another replication server. The HOSTnn settings MUST NOT be set to '0.0.0.0' or '127.0.0.1'. TYPE The TYPE keyword is used to specify the replication type for a file manager task that is being used in a replication network. This keyword must be specified in the 'replication' section that is included in the SUNFM.CFG configuration file for each file manager server that is included in the replication network. Format: TYPE={PRIMARY | SECONDARY | BACKUP} Where: { PRIMARY | SECONDARY | BACKUP } This keyword specifies the file manager type when it is being used in a replication network. Examples: TYPE=Primary IDLE_CLOSE The IDLE_CLOSE keyword identifies the number of seconds that a secondary/backup SUNFM server is to keep a file opened. This keyword is specified in the primary SUNFM.CFG configuration file and the setting is transferred to the secondary/backup SUNFM servers when they logon to the primary server. If this keyword is not specified, then the default of 120 seconds is used. Format: IDLE_CLOSE={IdleSeconds} Where: {IdleSeconds} The {IdleSeconds} is the number of seconds that a secondary/backup SUNFM server keeps a file opened while waiting for the next file IO operation. If the {IdleSeconds} is less than 10, then the minimum of 10 seconds is used. Examples: IDLE_CLOSE=25 FAIL_TIME The FAIL_TIME keyword identifies the number of seconds that a secondary SUNFM waits while processing a connection failure to a primary SUNFM server before the secondary SUNFM server invokes rollover and takes primary control of the replication network. This keyword is specified in the primary SUNFM.CFG configuration file and the setting is transferred to a secondary SUNFM server when it logs onto the primary server. If this keyword is not specified, then the default of 180 seconds is used. Format: FAIL_TIME={FailSeconds} Where: {FailSeconds} The {FailSeconds} is the number of seconds that a secondary SUNFM server waits before invoking the primary rollover action. If the {FailSeconds} is less than 20, then the minimum of 20 seconds is used. Examples: FAIL_TIME=60 TRANSACTION_WINDOW The TRANSACTION_WINDOW keyword identifies the number of IO transactions that can be buffered at the primary SUNFM server before requiring a communications session to transfer the transactions to the secondary/backup servers. The default number of buffered transactions is 100. The minimum number allowed is 10 and the maximum number allowed is 200. Format: TRANSACTION_WINDOW={TransactionCount} Where: {TransactionCount} The {TransactionCount} is the number of transactions that can be buffered at the primary server. If this value is less than 10, then the minimum of 10 is used. If this value is greater than 200, then the maximum of 200 is used. Examples: TRANSACTION_WINDOW=150 VALIDATE_ADDR The VALIDATE_ADDR keyword identifies a TCP/IP address or a URL that a third party network site that is to be used to validate that a primary to secondary network communications failure is truly valid. The {ip|URL} is accessed via a ping action to determine if a secondary rollover is to be invoked. Format: VALIDATE_ADDR={ip|URL} Where: {ip|URL} This parameter is an IP address or the URL of the network site that is to be pinged to determine if a primary to secondary communications failure has occurred. The IP address is provided as a 'nnn.nnn.nnn.nnn' identifier. Examples: VALIDATE_ADDR=63.162.221.125 VALIDATE_ADDR=www.sunbelt-plb.com SCAN_TIME The SCAN_TIME keyword defines the number of seconds that the primary server waits between the points in time when it performs the process of scanning the files in the UNMANAGED_RECURS_DIRnn and UNMANAGED-DIRnn directories. This keyword is specified in the primary SUNFM.CFG configuration file and the setting is transferred to a secondary SUNFM server when it logs onto the primary server. If this keyword is not specified, then the default of 20 seconds is used. The minimum number of seconds that can be specified is 10 seconds. Format: SCAN_TIME={ScanSeconds} Where: {ScanSeconds} The {ScanSeconds} is the number of seconds that a primary SUNFM server waits before invoking the primary scan directory action. If the {ScanSeconds} is less than 10, then the minimum of 10 seconds is used. Examples: SCAN_TIME=60 SCAN_ON_ROLLOVER The SCAN_ON_ROLLOVER keyword is used to specify whether a secondary SUNFM server is to perform the scan directory action for the UNMANAGED_RECURS_DIRnn and UNMANAGED-DIRnn directories after a primary rollover has occurred. If this keyword is not specified, then the default setting is OFF. Format: SCAN_ON_ROLLOVER={on|off} Where: {on|off} If this parameter is set to ON, then a secondary SUNFM server continues to scan directories after it has taken primary control of a replication network by a rollover action. If this parameter is set to OFF, then a secondary SUNFM server does not scan directories after a rollover action has occurred. Examples: SCAN_ON_ROLLOVER=ON LOGON_HOST The LOGON_HOST keyword identifies an IP/URL address and a required port number to be used for the replication logon task. This {ip|URL} allows the user application logon address to be different than the replication logon address. The {portnum} port number must be supplied for this keyword. Format: LOGON_HOST={ip|URL}:{portnum} Where: ':' The ':' colon separator character is required to separate the IP/URL from the port number. {ip|URL} This parameter is an IP address or the URL of the server executing the file manager task that allows another replication server to logon to this replication server. The IP address is provided as a 'nnn.nnn.nnn.nnn' identifier. {portnum} The {portnum} setting is used to specify the IP port number assignment for a replication server logon task. The port number must be specified for the LOGON_HOST keyword. The specified {portnum} MUST NOT be the same as the port number associated with FM_HOSTNAME! Examples: LOGON_HOST=63.162.221.125:2134 LOGON_HOST=www.sunbelt-plb.com:52105 Notes: 1. The use of this keyword for a Unix replication server is required. 2. The use of this keyword for a Windows replication server is optional. If this keyword is not used for a Windows replication server, then the HOSTnn {ip|URL} settings are used for the replication logon. 3. This keyword is only used for the logon process and is only required for server to server communications. Getting Started: 1. Define Primary/Secondary/Backup SUNFM replication IP and Port number requirements. 2. Define the Primary/Secondary/Backup replication directories to be used. The 'MANAGED_RECURS_DIRnn', 'UNMANAGED_RECURS_DIRnn', 'MANAGED_DIRnn', and 'UNMANAGED_DIRnn' keywords are to be specified in the primary SUNFM CFG file. 3. Add a [replication] section to the 'SUNFM.CFG' file for the primary SUNFM server that defines the setup keyword parameters as follows: [replication] # # Define the SUNFM replication type # TYPE=Primary # # Define the Sunbelt Serial Number, TCP/IP, and Port # Number (optional) for the file managers used in the # SUNFM replication network. In this case, there is a # primary SUNFM and one secondary SUNFM replication # server. Also, in this case, the Port Number is not # being specified. # HOST00=N123456:192.168.0.3 HOST01=N987654:192.168.0.100 # # Define all of the replication directories to be used # for all SUNFM replication servers. In this case, # there are replication directories being used. # MANAGED_RECURS_DIR01=c:\reptest MANAGED_RECURS_DIR02=c:\reptest1|d:\mydir 4. Add a [replication] section to the 'SUNFM.CFG' file for each secondary/backup SUNFM server that defines the setup keyword parameters as follows: [replication] # # Define the SUNFM replication type # Backup can be also be specified. # TYPE=Secondary # # Define the Sunbelt Serial Number, TCP/IP, and Port # Number (optional) for the file managers used in the # SUNFM replication network. In this case, only the # primary data settings is needed. # HOST00=N123456:192.168.0.3 # 5. If a Unix replication server is being used, then the [replication] section in the "SUNFM.CFG" file on the Unix executing the replication server must be modified to include the LOGON_HOST keyword settings. 6. Start the primary SUNFM file manager with the '-s' option. This creates the master replication file named 'sunfmrep.fm' in the directory where the SUNFM EXE file is located. The replication control file is created using the settings in the SUNFM.CFG file. NOTE: Any changes to the SUNFM CFG file appear in the replication control file after a '-s' or a '-u' SUNFM command is executed. 7. Start the secondary SUNFM file managers with the '-s' option. The replication master file data is transferred to secondary/backup replication file managers as they log on to the primary. Getting Started (DEMO Mode): 1. Install a SUNFM file manager using the Sunbelt SUNFM installation with the serial number specified as "DEMO". You can either install the primary and secondary as DEMO or just the secondary and use your current 9.1 SUNFM as the primary for testing. 2. Define Primary/Secondary/Backup SUNFM replication IP and Port number requirements. 3. Define the Primary/Secondary/Backup replication directories to be used. Only the 'MANAGED_DIR01' and 'UNMANAGED_DIR01' keywords are to be specified in the primary SUNFM CFG file. 4. Add a [replication] section to the 'SUNFM.CFG' file for the primary SUNFM server that defines the setup keyword parameters as follows: [replication] # # Define the SUNFM replication type # TYPE=Primary # # Define the Sunbelt Serial Number, TCP/IP, and Port # Number (optional) for the file managers used for the # SUNFM replication network. In this case, there is a # primary SUNFM and one secondary SUNFM replication # server. Also, in this case, the Port Number is not # being specified. The N123456 in this example is your # current SUNFM license number. If both the primary # and secondary/backup file managers are DEMO, then you # would use D999999 for both numbers. # HOST00=N123456:192.168.0.3 HOST01=D999999:192.168.0.100 # # For the demo version only one MANAGED and one # UNMANAGED directory is allowed. These keywords must # be changed to reflect the two directories you want to # test. # MANAGED_DIR01=c:\reptest UNMANAGED_DIR01=c:\reptest1 5. Add a [replication] section to the 'SUNFM.CFG' file for the secondary/backup SUNFM server that defines the setup keyword parameters as follows: [replication] # # Define the SUNFM replication type # Backup can be also be specified. # TYPE=Secondary # # Define the Sunbelt Serial Number, TCP/IP, and Port # Number (optional) for the primary file manager in the # SUNFM replication network. The secondary SUNFM data # settings come from the replication control data that # is received from the primary file manager. # HOST00=N123456:192.168.0.3 # 6. If a Unix replication server is being used, then the [replication] section in the "SUNFM.CFG" file on the Unix executing the replication server must be modified to include the LOGON_HOST keyword settings. See details on LOGON_HOST above. 7. Start the primary SUNFM file manager with the '-s' option. This creates the master replication file named 'sunfmrep.fm' in the directory where the SUNFM EXE file is located. The replication control file is created using the settings in the SUNFM.CFG file. The log file identifies that the replication is processing in a 'demo' mode. NOTE: Any changes to the SUNFM CFG file appear in the replication control file after a '-s' or a '-u' SUNFM command is executed. 8. Start the secondary SUNFM file managers with the '-s' option. The replication master file data is transferred to secondary/backup replication file managers as they log on to the primary. The log identifies that the replication is processing in a 'demo' mode. Errors: I81 SubCode 18 An I81 subcode 18 error can occur when a PL/B program attempts to open a managed file on a primary file manager in a replication network. This error and subcode occurs when the primary file manager is waiting to synchronize the data during the startup processing with secondary file managers in the replication network. SubCode 19 An I81 subcode 19 error can occur when a PL/B program is attempting to logon to a secondary SUNFM server. PLBWIN/PLBSERVE Description: The PLBWIN and PLBSERVE runtimes have been modified to use the PLB_FMALTIP keyword to control alternate access to different file manager servers that are to be used when a server fails. Configuration Keywords: PLB_FMALTIP PLB_FMALTIP is used to specify the IP addresses or the URL for a primary file manager server and the alternate file managers that are to be accessed in case the primary file manager server fails. The PLB_FMALTIP can have multiple primary file manager servers specified along with the alternate file managers for each primary server specified. This keyword can be specified in the 'environment' section that is included in the PLBWIN or PLBSERVE INI files. This keyword allows for alternate file manager switching without having to change any of the other keywords that deal with file manager addresses. In fact, this is the only place where an alternate file manager address can be specified. So there are no changes to the .MFD files, the OPEN/PREP statements where an IP address is specified, or the PLB_xxxxUSEIP keywords. This keyword must be used for any client expecting to use the rollover capability of a file manager in a replication network. However, note that the PLB_FMALTIP keyword can also be used when accessing file manager servers that are not in a replication network. Format: PLB_FMALTIP={primary1}[|{sec1A}[ | {sec1B}[...]]] [ ;{primary2}[|{secd2A}[|{sec2B}[...]]]... Where: {primaryN} The {primaryN} data can be formatted either as 'ip:port' or as a URL. The {primaryN} data identifies the ip address of the primary file manager servers that the user program might access under program control. When the multiple primary file manager servers are being used, then the ';' character is used to separate one primary file manager server from the next. {secNA} The {secNA} data can be formatted either as 'ip:port' or as a URL. The {secNA} data identifies the ip address of the 1st secondary file manager associated with the {primaryN} server. {secNB} The {secNB} data can be formatted either as 'ip:port' or as a URL. The {secNB} data identifies the ip address of the 2nd secondary file manager associated with the {primaryN} server Examples: PLB_FMALTIP=192.168.0.200|192.168.0.201 PLB_FMALTIP=1.1.0.100|1.1.0.101;1.1.0.200|1.1.0.201 IMPLEMENTATION NOTES: 1. A secondary replication/backup file manager CAN NOT have the same product serial number as the primary file manager. If a conflict is detected, then the conflicting secondary file manager terminates immediately.