SUNDM Command Line

 

SUNDM is the data manager that provides file I/O support for data file operations for a client workstation. When a client successfully logs on to the data manager task, a task is spawned at the server to interface with the client. This server task performs file access operations for managed files. Managed file accessing is initiated through MFD files created by the MAKEMFD utility or by using a special PL/B file name format during OPEN or PREPARE statements. The command line format of the SUNDM program is as follows:

 

     sundm [cfgname] -{options}]

Parameters:

cfgname
The optional configuration file name.
options
A required option described below that controls the action of the program.

Note the following:

  1. The SUNDM utility must be installed at the server before it can be used. A valid authorization number must be obtained from Sunbelt and provided during the installation process. When SUNDM is installed, the data manager task can only be loaded or executed once for a specific authorization number.

  2. The SUNDM server may execute as a Windows service. This requires the use of the SUNWSRV.DLL file that must be placed in the same location as the SUNDM.EXE file.

  3. Program {options} are as follows:

    4.  

    Option

    Action

    b

    Start the server and immediately allow for users to log in if using replication. This mode allows for replication synchronization to occur in parallel with normal data manager operations or for the data manager to start if the secondary data manager is not available.

    c

    Continue from a paused state. When the server is executing as a service, the '-c' command line option, the services control panel, or the SC.EXE command can continue the server operations. For stand-alone servers, only the '-c' command line option is available.

    d

    deletes the server as a Windows Service.

    e

    Reports any current expiration date information without affecting the current operational state of the server. If the server was installed using an authorization number with an expiration date, that expiration date is reported.

    f

    Forces the immediate termination of the server and any associated connections. Use of this option may not release system resources correctly. A shutdown of the server may be required to free those resources. When using replication and the primary server stops executing, all of the secondary servers will detect that the primary has logged off and they wait indefinitely for the primary to be restarted.

    fa

    When executed at the primary server, this command forces the immediate termination of the server and causes all of the secondary servers to terminate also. When this command line is executed for a secondary server, the command only terminates that server.

    fx

    When executed at the primary server, this command forces the server to terminate and replication primary control is transferred to the first secondary server. When this command is executed at a secondary server, the command only terminates that server.

    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, the NT Service is not created. An appropriate Windows Error Code is provided when an error occurs.

    p

    Pauses the server logon process. While in a paused state, no new child or administrative tasks are created. All existing users continue to run. The '-p' command line option pauses the server logon task when the server is executing as a Windows service or as a stand-alone server. The services control panel or the SC.EXE command can also pause the server when running as a Windows service.

    q

    Forces the immediate termination of the server and any associated connections after any pending FILEPI operations are complete.. Use of this option may not release system resources correctly.

    qa

    When executed at the primary server, this command forces the immediate termination of the server and causes all of the secondary servers to terminate as well after any active FILEPI operations are complete. When this command is executed at a secondary server, the command only terminates that server.

    qx

    When executed at the primary server, this command forces the server to terminate and replication primary control is transferred to the first secondary server after any active FILEPI operations are complete. When this command is executed at a secondary server, the command only terminates that server.

    r

    Resets license information without restarting the server. Use this option after modifying the configuration file to add additional connections.

    s

    Starts the server and uses the current 'sundmrep.DM' settings to start the replication network. If replication is configured and the 'sundmrep.DM' file does not exist, the replication control file is created. If changes are made to the SUNDM CFG, those changes automatically take affect during the SUNDM startup process.

    t

    Terminates a currently executing data manager task. When the primary server stops, all of the secondary servers detect that the primary has logged off and they wait indefinitely for the primary to be restarted.

    ta

    Terminates a currently executing data manager task. When this command line is executed at the primary server, all of the secondary servers also terminate. When executed at a secondary server, only that server terminates.

    tx

    Terminates a currently executing data manager task. When this command line is executed at the primary server, the server is terminated and replication primary control is transferred to the next available secondary server. When this command is executed for a secondary server that has the replication primary control, the server is terminated and the replication primary control is transferred to the original primary server if it is on line. Otherwise, the replication primary control is transferred to the next available secondary server. When this command is executed at a secondary server without replication primary control, only that secondary server is terminated.

    u

    Forces the primary server to reprocess the keyword settings and update all of the replication server and file/directory settings for the network.

     

  4. The SUNDM data manager uses a configuration file with a default name of 'sundm.cfg' or an optionally named configuration file name from the command line. The data manager first tries to open the configuration file in the current working directory. If this first attempt is unsuccessful, the data manager attempts to open the configuration file in the directory from which the SUNDM task was loaded.

  5. The SUNDM configuration file contains keywords that control the server functions. At a minimum, the DM_HostName is required. A more normal configure would also specify the DM_PortNum and PLB_Path keywords. If administrative capabilities such as the use of the Watch utility are required, the Admin_Hostname and Admin_PortNum keywords are required. A sample configuration file might appear as follows:

 

[version]

SUNDM=8.7

[environment]

DM_HostName=130.137.144.1

DM_PortNum=3934

PLB_PATH=d:\qatest

ADMIN_HOSTNAME=130.137.144.1

ADMIN_PORTNUM=503

 

  1. The 3934 port number has been assigned as a registered user port number by IANA (Internet Assigned Numbers Authority) and is the default.

  2. The SUNDM data manager task will not process a MFD file for file redirection. That is, an MFD cannot specify another MFD as the managed file. Any file opened by the data manager is processed as a normal FILE/IFILE/AFILE. Therefore, an AFILE/IFILE open results in an IO error if an MFD is specified as the target. However, a FILE open operation will open the MFD file directly without an IO error if a MFD is specified as the target.

  3. The FILELIST instructions DELETE, UPDATE, and WRITE are performed by the Data Manager to give the best performance possible.

  4. The data manager can only PREP files at the server when the filename uses the MFD redirector format.

  5. The SUNDM utility requires the SUNFHSYS.DLL before it can begin execution.

  6. The Windows (PLBWIN) and Linux (PLB) runtimes optionally support message compression and encryption when communicating with SUNDM data managers. Additional information is available in the PLB Language Reference under Managed File Support.

  7. A SUNDM service can be started by one of three ways:

    1. Automatically.

    2. Using the services control panel

    3. Using the SC.EXE (Service Control) utility

      1. A SUNDM server service can be stopped using one of the following:

    4. The '-t' command line option

    5. The '-f' command line option

    6. The services control panel.

    7. The SC.EXE command

  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.

  5. The "r" option resets the license information within the server task. This eliminates the need to bring the server down and restart it to change the supported number of connections. Note that no more than five reset errors are allowed. After five reset errors have been detected, the server must be restarted to reset an authorization license.

  6. When the Data Manager is installed and loaded by the Windows Services Manager, there is an internal runtime option '-l' that must be used in the service command line. This '-l' option cannot be used directly by an end-user in a Data Manager command line to start the Windows service.

 

 

See Also: SUNDM Keywords, SUNADMIN, MAKEMFD, WATCH


about_sundm SUNDM Keywords