Skip to content

Configuring and Starting the DMSII Client

Complete the following steps to configure and start the DMSII Client to clone the DMSII database.

Note

If you set COMPILE MANUAL (typically used when the DASDL and DMALGOL compilers are not available to the DMSII Client software) in the DMSII Client parameter file, there are several manual steps you must complete as documented in steps 6 through 13 below.

  1. Get the DMSII Client DASDL patch file using CANDE, as follows:

    GET PATCH/DATABRIDGE/DMSIICLIENT/SAMPLE/DASDL AS PATCH/
DATABRIDGE/DMSIICLIENT/clientdbname/DASDL

    where clientdbnameis the name of the client database you are creating. It is strongly recommended 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.

  2. Modify and then save the DMSII Client DASDL patch file to reflect settings for your site. See Modifying the DMSII Client DASDL File.

  3. Get the DMSII Client parameter file using CANDE, as follows:

    GET DATA/DMSIICLIENT/SAMPLE/CONTROL AS DATA/DMSIICLIENT/
clientdbname/CONTROL

    where clientdbnameis the name of the client database you are creating.

  4. Modify and then save the DMSII Client parameter file to reflect settings for your site. See Modifying the DMSII Client Parameter File.

  5. Start the DMSII Client by entering the following command:

    START WFL/DATABRIDGE/DMSIICLIENT ("clientdbname")

    where clientdbnameis the name of the client database you are creating.

    The DMSII Client will generate and compile the DASDL for the client database. The message that appears next depends on your setting for the COMPILE parameter in the DMSII Client parameter (step 2).

    If Then
    COMPILE AUTO The DMSII Client displays the following message and then waits for the DMSupport library to compile:

    Waiting for DMSupport compilation

    After DMSupport is compiled, the client database will be initialized with empty structures and then the DMSII Client will clone the primary database.

    At this point, you are finished with this procedure. Go to “What to Do Next ” below.
    COMPILE MANUAL The DMSII Client displays the following message and then terminates:

    Use WFL/DATABRIDGE/DMSIICLIENT/COMPILEDB to compile clientdbname

    Continue with step 6.

  6. Compile the client database by starting the following

    WFL: WFL/DATABRIDGE/DMSIICLIENT/COMPILEDB ("clientdbname")

    where clientdbnameis the name of the client database you are compiling.

  7. When the COMPILEDB WFL is finished, if the compiled software is on a different pack or usercode than the DMSII Client, copy the following files to the DMSII Client usercode and pack:

    DESCRIPTION/clientdbname
DMSUPPORT/clientdbname
RECONSTRUCT/clientdbname
OBJECT/DATABRIDGE/DMSIICLIENT/LIB/clientdbname

  8. Create the empty database structure by running the following utility:

    SYSTEM/DMUTILITY ("DB= clientdbname INITIALIZE =")

  9. Run the DMSII Client to clone the database by entering the following command:

    START WFL/DATABRIDGE/DMSIICLIENT ("clientdbname")

What to Do Next

The DMSII Client either waits for additional audit information or terminates, depending on the value of the MAXWAIT option in the parameter file. At this point, the client database is ready to use.

If you want to view the status of the DMSII Client, enter the AX STATUS command as described in DMSII Client AX Commands.

You can register the DMSII Client for auto connect so that Databridge Server initiates it when updates are available. To do this, enter the REGISTER command as described Starting and Stopping the DMSII Client.

Modifying the DMSII Client DASDL File

The DMSII Client DASDL file (PATCH/DATABRIDGE/DMSIICLIENT/clientdbname/DASDL) is the source file for the client database. It provides information on where and how the client database will be created.

Although this is not a typical option, if you want to make the client database unaudited for improved performance and reduced disk storage, you could set the \$ UNAUDITED option to compile the library for an unaudited client database. The cost of this is recloning or reloading the database if a failure occurs on the secondary system.

The DMSII Client DASDL file follows the procedure below.

Note

If you are completing step 2 in "Configuring and Starting the DMSII Client," use the following information to configure your DMSII Client DASDL file. After you have configured the DMSII Client DASDL file, continue with step 3 above.

Modify the DASDL file settings by completing the following steps:

  1. Set the FAMILYNAME attribute in the AUDIT TRAIL section.

  2. For any primary-side sets you want declared on the client side, declare the following somewhere near the top in the DASDL file:

    $ SET setname1 setname2 setname3 ...

  3. For any primary-side subsets you want declared on the client side, declare one of the following somewhere near the top in the DASDL file:

    $ SET ALLSUBSETS

    ---or---

    $ SET subsetname1 subsetname2 subsetname3 ...

  4. Change other parameters and audit trail attributes indicated in the comments of the DASDL file, if desired. If you decide to change any of these parameters and audit trail attributes, refer to your Unisys DMSII Data and Structure Definition Language (DASDL) Programming Referencemanual for detailed information about the parameters and audit file attributes.

Sample DMSII Client DASDL File

Following is the sample DMSII Client DASDL file (PATCH/DATABRIDGE/DMSIICLIENT/clientdbname/DASDL) that you must modify by replacing the items in angle brackets with your entry.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%                                                                 %
% A Series Databridge DMSIIClient DASDL Skeleton                  %
%                                                                 %
% Source: PATCH/DATABRIDGE/DMSIICLIENT/SAMPLE/DASDL               %
% Object:                                                         %
%                                                                 %
% Copyright (C) 2012 Attachmate Corporation                       %
% All Rights reserved                                             %
%                                                                 %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
This is the user-modifiable DASDL skeleton for the Databridge
Client program for DMSII.
Before generating a database with the DMSII Client, you may modify
this file with local preferences.
The PARAMETERS and AUDIT TRAIL attributes can be adjusted as desired.
The DMSII Client can function with any settings in these sections.
By default, the DMSII Client database will not have any of the sets
found in the original database. The generated DASDL, however, does
contain the declarations for these sets surrounded by a pair of
$ SET OMIT = ^ <setname> and $ POP OMIT. The <setname> is the original
name of the set minus any hyphens. If you want to include any of these
sets in the client database you should put $ SET <setname> in this
file *before* the insertion point, which is marked by "@".
For example, if you want to include the sets CUSTNAMESET and ORD-BY-DATE
in the client database you should put the following
lines in this file:
$ SET CUSTNAMESET
$ SET ORDBYDATE
Important! Save this file as
PATCH/DATABRIDGE/DMSIICLIENT/<clientdb>/DASDL.
Modification history
--------------------
Version 40.461
Initial version.
Version 41.471
1 Added POPULATIONINCR = 100 to avoid waiting entries messages
about population increases.
Version 42.491
1 Added $ UNAUDITED for compiling an unaudited database.
Version 50.503
1 Removed the FAMILYNAME option from the DEFAULTS declaration
because the DMSII Client now generates it from the CLIENT
DATABASE option. Similarly, the CONTROL FILE declaration
has been removed because it is now generated.
End History
$ POP OMIT
DEFAULTS
(
%- SECURITYGUARD = <guardfiletitle>,
CHECKSUM = TRUE,
DATASET
(
%- SECURITYGUARD = <guardfiletitle>,
BUFFERS = 0 + 0 PER RANDOM USER
OR 2 PER SERIAL USER,
REBLOCK = TRUE,
POPULATIONINCR = 100,
POPULATIONWARN = 0,
LOCK TO MODIFY DETAILS
)
SET
(
%- SECURITYGUARD = <guardfiletitle>,
CHECKSUM = TRUE
)
);
%=============================================================
% Don't change any OPTIONS
%=============================================================
OPTIONS
(
$ SET OMIT = UNAUDITED
AUDIT,
INDEPENDENTTRANS,
REAPPLYCOMPLETED,
$ POP OMIT % UNAUDITED
ADDRESSCHECK % ADDRESSCHECK must be set
);
%=============================================================
% Change PARAMETERS as desired for better performance.
%=============================================================
PARAMETERS
(
$ SET OMIT = UNAUDITED
SYNCPOINT = 100 TRANSACTIONS,
CONTROLPOINT = 20 SYNCPOINTS,
$ POP OMIT % UNAUDITED
ALLOWEDCORE = 500000,
OVERLAYGOAL = 5
);
%=============================================================
% Change AUDIT TRAIL as desired for better performance.
%=============================================================
$ SET OMIT = UNAUDITED
AUDIT TRAIL
(
%=============================================================
% Set FAMILYNAME to the pack for the audit files.
%- FAMILYNAME = <auditpack> COPY TO TAPE AND REMOVE,
%=============================================================
AREAS = 10,
AREASIZE = 1000 BLOCKS,
BLOCKSIZE = 4080 WORDS,
UPDATE EOF = 100 BLOCKS,
CHECKSUM = TRUE
);
$ POP OMIT % UNAUDITED
%=============================================================
% Audit location data set for keeping track of our position
% in the primary database.
%
% *DO NOT MODIFY*
%=============================================================
AUDITLOCATION DATASET
(
AL-STRNUM NUMBER (4) INITIALVALUE 0;
AL-RECTYPE NUMBER (3) INITIALVALUE 0;
AL-MODE NUMBER (1) INITIALVALUE 0;
AL-AFN NUMBER (4) INITIALVALUE 0;
AL-ABSN REAL (S11) INITIALVALUE 0;
AL-SEG REAL (S11) INITIALVALUE 0;
AL-INX REAL (S11) INITIALVALUE 0;
AL-TIME REAL INITIALVALUE 0;
AL-HOSTINFO REAL INITIALVALUE 0;
),
BLOCKSIZE = 30 RECORDS;
ALSET SET OF AUDITLOCATION
KEY
(
AL-STRNUM,
AL-RECTYPE
)
NO DUPLICATES;
%=============================================================
% Select predefined sets
%=============================================================
% Put $ SET <setname> here for any desired sets from the
% primary database.
%$ SET CUSTNAMESET
% The following line is the "insertion point" where the
% generated structures will be inserted.
@ Insertion point -- Do NOT delete this line.
%=============================================================
% Logical databases and physical attributes
%=============================================================
% Put any logical databases or physical
% attributes of specific structures here.
%=============================================================
% End DMSII Client DASDL
%=============================================================

Modifying the DMSII Client Parameter File

The DMSII Client parameter file (DATA/DMSIICLIENT/clientdbname/CONTROL) is a SEQDATA file. It provides information on where and how to locate the Server Accessory SOURCE for the primary database.

Note

If you are completing step 4 in Configuring and Starting the DMSII Client, use the following information to configure your DMSII Client parameter file. After you have configured the DMSII Client parameter file, continue with step 5.

The following is the sample DMSII Client parameter file that you must modify by replacing the items in angle brackets with your entry.

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%                                                                     %
% A Series Databridge DMSII Client Parameter File                     %
%                                                                     %
% Source: DATA/DMSIICLIENT/SAMPLE/CONTROL                             %
%                                                                     %
% Version: 6.3                                                        %
%                                                                     %
% Copyright (C) 2014 Attachmate Corporation                           %
% All Rights reserved                                                 %
%                                                                     %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Name of the *** Client *** database.
% The client database files will be created on the
% <dbpack> family under the <usercode> usercode.
CLIENT DATABASE "(<usercode>)<clientdb> ON <dbpack>"
% Client database DMSUPPORT title.
% Default: (<usercode>)DMSUPPORT/<clientdb> ON <dbpack>
% DMSUPPORT "<DMSupporttitle>" % (Optional)
% Client database Reconstruct title.
% Default: (<usercode>)RECONSTRUCT/<clientdb>
%   ON <dbpack>
% RECONSTRUCT "<Reconstructtitle>" % (Optional)
% DMSII software titles
DMCONTROL     "SYSTEM/DMCONTROL ON DISK"
DMUTILITY       "SYSTEM/DMUTILITY ON DISK"
DMALGOL     "SYSTEM/DMALGOL ON DISK"
DASDL       "SYSTEM/DASDL ON DISK"
BUILDREORG     "SYSTEM/BUILDREORG ON DISK"
REORGSYM        "DATABASE/REORGSYMBOLIC ON DISK"
PROPERTIES     "DATABASE/PROPERTIES ON DISK"
% How to locate the Server Accessory SOURCE ...
SOURCE <sourcename>   % SOURCE name in the Server Accessory parameter file
AT <host>             % the Server Accessory's hostname or IP address
VIA TCPIP       % network protocol: TCPIP, HLCN, BNA
PORT <portnumber>     % the Server Accessory's port number, e.g. 3000
% example: SOURCE BANKDB AT PRODHOST VIA TCPIP PORT 3000
% When waiting for an audit file ...
RETRY 60     % seconds delay between retries
MAXWAIT FOREVER % max total seconds to wait
% (FOREVER means to retry indefinitely;
% DONTWAIT means do not retry at all)
COMPILE AUTO   % automatically compile% COMPILE MANUAL % user is responsible for compiling
% the client database using
% WFL/DATABRIDGE/DMSIICLIENT/COMPILEDB
% Disable the following data sets ...
% DISABLE dataset1, dataset2, ...
% DISABLE ALL EXCEPT dataset1, dataset2, ...