Skip to content

DMSII Client Parameters

Note the following for the format of the DMSII Client parameter file:

  • You can list the options in the parameter file in any order.

  • You can list multiple options on a single line.

  • You can split options across multiple lines.

  • There is no termination character.

  • There is no continuation character.

  • The comment character is the percent sign (%). The comment character can appear anywhere on a line and anything after the comment character is ignored.

  • If you name any entry the same as a parameter file keyword, enclose the name in "quotation marks." For example, if you create a filter named SOURCE (which is also the name of a keyword in the DMSII Client parameter file), enclose SOURCE in "quotation marks" as follows:

    FILTER "SOURCE"

The remainder of this section explains each option in the DMSII Client parameter file.

CLIENT DATABASE "title"

Required: Enter the name you want to use for the client database. It is strongly recommend that the name of the client database be different from the name of the primary database so that there is no confusion as to which database you are using.

If you specify the optional usercode and dbpack, they apply to the DMSII CONTROL file and the database files, as in this example:

CLIENT DATABASE "(DBRIDGE)BANKCLIENTDB ON DBPACK"

In this example:

  • The generated client database files (CONTROL file, data sets, and sets) will have the DBRIDGE usercode and reside on DBPACK.

  • By default, DMSUPPORT will have the DBRIDGE usercode and reside on DBPACK.

  • The DESCRIPTION file will be on the database family under the usercode the DMSII Client is running under.

DMSUPPORT "title"

Required: If you want the DMSupport library for the client database to have a specific name, enter that name in this parameter. The default support library is as follows:

(dbusercode)DMSUPPORT/clientdbname ON dbpack

RECONSTRUCT "title"

Optional: If you want the Reconstruct program for the client database to have a specific name, enter that name in this parameter. The default program name is as follows:

(dbusercode)RECONSTRUCT/clientdbname ON dbpack

DMS Software Titles

Optional: The DMSII Software Titles parameter allows you to specify a different title for a variety of DMSII-related programs. This allows you to use nonstandard names for these programs, in addition to specifying usercodes and pack names, as in the following examples:

DMCONTROL   "(500)SYSTEM/DMCONTROL ON SYSPACK"
DMUTILITY   "SYSTEM/500/DMUTILITY ON SYSPACK"
DMALGOL   "*SYSTEM/DMALGOL ON SYSPACK"
DASDL       "SYSTEM/DASDL ON SYSPACK"
BUILDREORG   "SYSTEM/BUILDREORG ON SYSPACK"
REORGSYM    "DATABASE/REORGSYMBOLIC ON DBPACK"
PROPERTIES   "DATABASE/PROPERTIES ON DBPACK"

SOURCE

Required: The SOURCE parameter is a four-part parameter that enables the DMSII Client to link up with DBServer. The syntax of the SOURCE parameter is as follows:

SOURCE sourcename AT host VIA protocol PORT portnumber
Where Is
sourcename The name of the SOURCE in the DBServer parameter file associated with the database you want to replicate.
host The host name or the IP address where DBServer or DBEnterprise is running.

NOTE:The host name can contain multiple nodes separated by periods.
protocol TCPIP
portnumber The DBServer port number usig TCP/IP

RETRY

Optional: The default is 60 seconds. Enter the number of seconds you want the DMSII Client to wait before it retries its available audit check. If more audit is unavailable, the DMSII Client will wait the number of seconds you specify before checking again.

MAXWAIT

Optional: The default is FOREVER. Enter the maximum number of seconds you want the DMSII Client to wait for more audit to become available. Since the DMSII Client is designed to run continuously, you can use the default of FOREVER to indicate there is no limit to the waiting time. You can also enter DONTWAIT to indicate that the DMSII Client should immediately terminate when no updates are available.

When you enter a value, the DMSII Client will check for more audit every nnseconds, where nnis the value of the RETRY option. If the MAXWAIT time expires before more audit becomes available, the DMSII Client terminates. Once the DMSII Client terminates, you must restart it manually, unless you enabled the auto connect feature.

See REGISTER in Starting and Stopping the DMSII Client for instructions on registering the DMSII Client for auto connect.

COMPILE

Optional: The default is COMPILE AUTO. This parameter determines whether or not the DMSII Client will automatically compile the client database and support library when the client database is created or in the event of a reorganization. If the DASDL and DMALGOL compilers are not available to the DMSII Client software, use the COMPILE MANUAL option.

When you run the DMSII Client with the COMPILE MANUAL option set, the DMSII Client will generate the client database DASDL source and the patch files for the support library and then terminate with the following message:

"Use WFL/DATABRIDGE/DMSIICLIENT/COMPILEDB to compile clientdbname"

For instructions, see When COMPILE Is Set to MANUAL.

INSERT SERVER TIMESTAMP

Optional: This parameter adds a timestamp to each data set record that contains the time the application on the primary system last updated the record.

If you want to use the INSERT SERVER TIMESTAMP parameter, you must add it to the DMSII Client parameter file. By default, it does not appear in the file.

DISABLE

Optional: This parameter allows you to exclude specific data sets from being replicated to the client database. Use this parameter when you want to exclude a portion of a database from being replicated.

To exclude a portion of a database, enter the data sets that you want to exclude in this field, separated by commas, as in the following example:

DISABLE CUSTOMER, ACCOUNT, EMPLOYEES

When the client database is generated, any disabled data sets are omitted from the DASDL. If a data set is disabled after the initial client database is generated it remains in the client database but none of its updates are replicated.

DISABLE ALL EXCEPT

Optional: This parameter allows you to exclude all data sets except the ones listed from being replicated to the client database. Use this parameter when you want to include only a portion of a database.

To replicate a portion of a database, enter the data sets that you want to replicate in this field, separated by commas, as in the following example:

DISABLE ALL EXCEPT CUSTOMER, ACCOUNT, EMPLOYEES

When the client database is generated, any disabled data sets are omitted from the DASDL. If a data set is disabled after the initial client database is generated it remains in the client database but none of its updates are replicated.