Chapter 10: Utilities

This chapter explains how to use the WFL (Work Flow Language) jobs and additional utilities included with Databridge.

BCNotify

Use BCNotify to remotely launch scripts on a machine running the Databridge Client service. BCNotify has two modes of operation, each of which has its own WFL:

Mode	WFL
Standard mode	WFL/DATABRIDGE/SAMPLE/BCNOTIFY
DBNotify compatible mode	WFL/DATABRIDGE/SAMPLE/DBNOTIFY

Standard mode accepts a single string parameter. This string parameter is a list of = pairs that are used to pass items such as the DMSII database (for obtaining the current AFN), the remote command to execute, parameters to pass to the command, and the remote data source.

DBNotify compatible mode also accepts a string parameter. The DBNotify WFL is provided only for back compatibility with the deprecated DBNotify program (OBJECT/DATABRIDGE/DBNOTIFY) and WFL (WFL/DATABRIDGE/DBNOTIFY), which are no longer supported. The BCNotify program is executed in a manner nearly identical to DBNotify.

For information about using BCNotify to automate client operations, see “Automating Client Operations with the Service” in the Databridge Client Administrator's Guide.

BCNotify WFL Parameters

The following table lists parameters to use with the BCNotify WFL.

This parameter	Does this
`CMD` or `COMMAND`	Identifies the script or executable on the remote system. This is a required parameter.
`PARAMETERS` or `ARGS`	Passes the command-line arguments to the command above. This is an optional parameter.
`DATASOURCE` or `DSOURCE`	Identifies the data source of the remote system. `DATASOURCE` is a required parameter and must be a valid data source.
`DATABASE` or `DB`	Identifies the DMSII database. This parameter is optional and is currently used to obtain the current audit file.

Example

START WFL/DATABRIDGE/BCNOTIFY ("CMD=STARTPROCESS ARGS=P1 P2 P3
DATASOURCE=BANKDB")
ST WFL/DATABRIDGE/BCNOTIFY("DB=(DBUSER)TESTDB ON DBASE CMD=PROCESS
DATASOURCE=TDB")

Notify (WFL)

The Notify WFL causes DBServer to notify Enterprise Server that audit files are available for processing. You must run the Notify WFL each time you want to initiate the Databridge Client from the MCP host system. You can automate this process by using the Copy Audit utility to have DBServer automatically notify Enterprise Server each time an audit file becomes available. See Copy Audit Utility.

To run the Notify WFL

Note

For instructions to steps 1-2, see the Databridge Enterprise Administrator’s Guide.

Configure Enterprise Server on the Enterprise Server computer (ClearPath PC or Windows server) to listen at a specific port.
Create a batch file to run the Databridge Client when Enterprise Server is notified by DBServer.
Configure the NOTIFY option in the DBServer parameter file with the Enterprise Server computer’s IP address and port number where Enterprise Server (specifically, the Databridge Director service) is listening. See NOTIFY for instructions.
Run the Notify WFL as follows:

START WFL/DATABRIDGE/NOTIFY ("databasename")

where databasename is the name of the database you are replicating.

Save with Update Level (WFL)

Use this procedure to ensure that the Engine finds the correct software when processing audit files that switch from one update level to another. The Save with Update Level WFL (WFL/DATABRIDGE/ BACKUPTAILORED) provides backup copies of both the DESCRIPTION and DMSUPPORT files, helping you plan ahead for record format or file format database reorganizations. You can run this WFL any time before or after a DASDL update.

To run the Save with Update Level WFL

Start WFL/DATABRIDGE/BACKUPTAILORED using the following syntax:

START WFL/DATABRIDGE/BACKUPTAILORED ("databasename")

where databasename is the name of the database, with or without a leading user code and family name. (This is the same as all of the other WFLs.)

For example:

START WFL/DATABRIDGE/BACKUPTAILORED ("CUSTOMERDB") START WFL/DATABRIDGE/BACKUPTAILORED ("(PROD)CUSTOMERDB ON USERPACK")

If the database update level of both files is 17, the files would be copied using the following filenames:

DESCRIPTION/CUSTOMERDB/17 DMSUPPORT/CUSTOMERDB/17

If the update level of the DESCRIPTION file is 39 and the update level of the DMSUPPORT library is 40, the files would be copied using the following filenames:

DESCRIPTION/CUSTOMERDB/39 DMSUPPORT/CUSTOMERDB/40

The copies will reside on the same families as the original files.

AuditTimer Utility

Databridge AuditTimer is a utility that closes the current audit file when it is older than the limit you specify in the AuditTimer parameter file (DATA/AUDITTIMER/databasename/CONTROL), as shown in the following diagram:

You can use the AuditTimer utility with both Span and Server as a way to periodically force an audit switch for a database.

The files related to the AuditTimer utility are as follows:

OBJECT/DATABRIDGE/AUDITTIMER
WFL/DATABRIDGE/AUDITTIMER
DATA/AUDITTIMER/SAMPLE/CONTROL
DATA/AUDITTIMER/databasename/CONTROL

AuditTimer Parameter File

The AuditTimer parameter file is named as follows:

DATA/AUDITTIMER/databasename/CONTROL

This file contains entries for days and times of a week that indicate how old the audit file can get before it is automatically closed, as in the following example:

day        time             interval
TUESDAY       8 AM         50 MINUTES
THURSDAY   5:00 PM         30 MINUTES
SATURDAY   8:00 AM          1 DAY      SYNC 4 HOURS

The interval (how old an audit file can get) for each entry applies to all times up to the next entry. In the example above, the 50-minute interval applies to all times between Tuesday at 8 a.m. and Thursday at 4:59 p.m. The 30-minute interval applies to all times between Thursday at 5 p.m. and Tuesday at 7:59 a.m.

In addition, the optional SYNC parameter ensures that a sync point will occur if any transactions are completed within a specified SYNC interval. This ensures that Databridge replicates all completed transactions even if there are not enough transactions to trigger the normal sync point mechanism.

When AuditTimer runs, it determines which entry corresponds to the current time. In the example above, if AuditTimer starts running at 9:30 a.m. on Wednesday, it will use the TUESDAY 8 a.m. 50 MINUTES entry. It then computes the age of the current audit file. If the audit file is older than the specified interval (50 minutes in this example), AuditTimer will force an audit close.

Note

These entries do not determine how often AuditTimer runs. To determine how often AuditTimer runs, set the STARTTIME parameter explained in Starting AuditTimer.

Configuring the AuditTimer Parameter File

Complete the following steps to configure AuditTimer.

To configure AuditTimer

Using CANDE or another editor, open the sample AuditTimer parameter file (DATA/AUDITTIMER/SAMPLE/CONTROL).

Using values from the table below, edit day, time, interval, and SYNC interval (optional). The format should be as follows:

daytimeinterval [ SYNC interval ]

For example:

MONDAY 7 PM 12 HOURS SATURDAY 8 AM 1 DAY SYNC 30 MINUTES

Save the sample parameter file as follows:

DATA/AUDITTIMER/databasename/CONTROL

where databasename is the name of the database for which you will be automatically closing the audit files.

Entry	Syntax
day	`SUN` or `SUNDAY MON` or `MONDAY TUE` or `TUESDAY WED` or `WEDNESDAY THU` or `THURSDAY FRI` or `FRIDAY SAT` or `SATURDAY`
time	`HH AM or PM` `HH:MM AM or PM` NOTE: If you omit the AM/PM, a 24-hour time format is assumed. For example, 23:30 is the same as 11:30 PM.
interval	`MIN` or `MINUTES HR` or `HOURS SEC` or `SECONDS DAY` or `DAYS`

Example 1

The following procedure is an example of how to configure AuditTimer to force an audit file close between 5:00 p.m. and 7:00 p.m. each evening.

Using CANDE or another editor, open the sample AuditTimer parameter file (DATA/AUDITTIMER/SAMPLE/CONTROL).
Enter the following values for day, time, and interval:

SUNDAY 5 PM 2 HOURS SUNDAY 7:10 PM 24 HOURS MONDAY 5 PM 2 HOURS MONDAY 7:10 PM 24 HOURS TUESDAY 5 PM 2 HOURS TUESDAY 7:10 PM 24 HOURS WEDNESDAY 5 PM 2 HOURS WEDNESDAY 7:10 PM 24 HOURS THURSDAY 5 PM 2 HOURS THURSDAY 7:10 PM 24 HOURS FRIDAY 5 PM 2 HOURS FRIDAY 7:10 PM 24 HOURS SATURDAY 5 PM 2 HOURS SATURDAY 7:10 PM 24 HOURS
Save the sample parameter file as follows:

DATA/AUDITTIMER/databasename/CONTROL

where databasename is the name of the database for which you will be automatically closing the audit files.
Run AuditTimer as follows:

START WFL/DATABRIDGE/AUDITTIMER ("databasename");

AuditTimer will determine the parameter file entry corresponding to the current time and then compute the age of the current audit file. If the current audit file is too old, it will force an audit switch. Then AuditTimer will compute the next time that an audit file could possibly be too old and re-queues itself for that time.

For example, if AuditTimer starts running Monday at 5:30 p.m., it will ensure that the current audit file is not older than two hours. If it is 90 minutes old, AuditTimer will re-queue itself to run at 6:00 p.m.

On the other hand, if the current audit file is only 10 minutes old, it wouldn't be two hours old until 7:20 p.m., which is after the next parameter file entry (MONDAY 7:10 PM 24 HOURS) takes effect. Since audit files can be 24 hours old during that entry, the audit file created at 5:20 p.m. won’t be too old until 5:20 p.m. the next day, which is after the next parameter file entry (TUESDAY 5 PM 2 HOURS) takes effect. Therefore AuditTimer will re-queue itself for Tuesday at 5:00 p.m.

Example 2

The following example uses the SYNC option to ensure that a sync point is forced every four hours if any transactions are committed within that interval.

Building on the previous example, AuditTimer forces an audit file close between 5:00 p.m. and 7:00 p.m. each weekday evening. On the weekend (Saturday, Sunday, and up to Monday at 5:00 PM), however, the audit file can be up to three days old. AuditTimer ensures that a sync point will occur within four hours of any transaction.

MONDAY      5 PM        2 HOURS
MONDAY      7:10 PM    24 HOURS
TUESDAY     5 PM        2 HOURS
TUESAY      7:10 PM    24 HOURS
WEDNESDAY   5 PM        2 HOURS
WEDNESDAY   7:10 PM    24 HOURS
THURSDAY    5 PM        2 HOURS
THURSDAY    7:10 PM    24 HOURS
FRIDAY      5 PM        2 HOURS
FRIDAY      7:10 PM    24 HOURS
SATURDAY    8 AM        3 DAYS     SYNC 4 HOURS

Sample AuditTimer Parameter File.

Following is the sample AuditTimer parameter file (DATA/AUDITTIMER/SAMPLE/CONTROL).

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%                                                                      %
%          A Series Databridge AuditTimer Parameter File               %
%                                                                      %
%             Source: DATA/AUDITTIMER/SAMPLE/CONTROL                   %
%                                                                      %
%                        Version: 7.0                                  %
%                                                                      %
%     Copyright (C) 2021 Micro Focus or one of its affiliates.         %
%                                                                      %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
%
%     Each entry specifies how "old" the current audit file can be.
%     If the current audit file is older than the given limit for the
%     time of day, the AuditTimer program will force an audit switch.
%     Also, if a syncpoint interval is specified, AuditTimer will
%     ensure that at least one syncpoint occurs within that interval
%     if any transactions were completed.
%
%     Syntax for each entry:
%
%            day time interval [ SYNC interval ]
%
%     where
%
%     'day' is:
%          ---- SUN or SUNDAY ------------|
%            |- MON or MONDAY ----|
%            |- TUE or TUESDAY ---|
%            |- WED or WEDNESDAY -|
%            |- THU or THURSDAY --|
%            |- FRI or FRIDAY ----|
%            |- SAT or SATURDAY --|
%
%     'time' is:
%          -- hh ------------------------|
%                    |- :mm -| |- AM -|
%                              |- PM -|
%
%     If you omit the AM/PM a 24-hour time is assumed.
%
%     'interval' is:
%          -- n --- MIN -----------------|
%                |- MINUTES -|
%                |- HR ------|
%                |- HOURS ---|
%                |- SEC -----|
%                |- SECONDS -|
%                |- DAY ----|
%                |- DAYS ----|
%
%     If you omit 'SYNC interval' AuditTimer will not force any
%     syncpoints.
%
% Some (not necessarily realistic) examples:
%
%     TUESDAY   8 AM      50 MINUTES
%     THURSDAY 12:00       2 HOURS      % noon
%     THURSDAY 5:00 PM    30 MINUTES
%     THURSDAY 19:30      45 MIN        % 7:30 PM
%     SATURDAY 8:00 AM     1 DAY SYNC 30 MINUTES
%             Starting Saturday morning audit files can be a whole
%             day old but force a syncpoint every half hour if any
%             transactions are committed.
%----------------------------------------------------------------------
SUNDAY    1 AM        4 HOURS
MONDAY    9 AM        1 HOURS
MONDAY    5 PM        2 HOURS
TUESDAY   9 AM        1 HOURS
TUESDAY   5 PM        2 HOURS
WEDNESDAY 9 AM        1 HOURS
WEDNESDAY 5 PM        2 HOURS
THURSDAY  9 AM        1 HOURS
THURSDAY  5 PM        2 HOURS
FRIDAY    9 AM        1 HOURS
FRIDAY    5 PM        3 HOURS

Starting AuditTimer

Use the following procedure to start AuditTimer.

To start AuditTimer

Configure the AuditTimer parameter file.
Run the AuditTimer WFL (WFL/DATABRIDGE/AUDITTIMER) to execute AuditTimer, as follows:

START WFL/DATABRIDGE/AUDITTIMER ("databasename" [ , "logicaldatabasename" ] ) [ ; STARTTIME = hh:mm ]

where STARTTIME = hh:mm is an optional command that specifies when AuditTimer starts. AuditTimer will start immediately if you do not specify the optional STARTTIME command. If guard files prevent access to the physical database, specify a logical database name.
If you use AuditTimer for more than one database, execute it once for each database. For example, if you have three DMSII databases for which you want to periodically force an audit file switch, you would run the AuditTimer utility three times, once for each database, as follows: START WFL/DATABRIDGE/AUDITTIMER ("databasename1") START WFL/DATABRIDGE/AUDITTIMER ("databasename2") START WFL/DATABRIDGE/AUDITTIMER ("databasename3")

After AuditTimer starts, it automatically queues itself so that it can periodically check the age of the current audit file. By default, it queues itself to run the next time it expects the audit file might be older than what the parameter file specifies. If you want to override this behavior, configure AuditTimer to run at specified intervals.

To change the frequency of AuditTimer

Modify the STARTTIME option near the bottom of the AuditTimer WFL. The following excerpt shows a STARTTIME value of 2.5 hours:

% schedule this job to run again later
START WFL/DATABRIDGE/AUDITTIMER (DBPARAM, LDB, SYNCTIME, TRANCOUNT,
SYNCCOUNT);
STARTTIME = +2:30 (NOTE);
END JOB.

Forcing an Audit Switch

If you generate less than one audit file a day, you may want to force an audit switch daily and run Span or DBServer so that the secondary (replicated) database is at most one day behind. In this case, you can use the following procedure instead of running AuditTimer.

The following procedure works only for databases that are currently open for updating (that is, one or more programs have done an OPEN UPDATEdatabasename ).

To force an audit switch

From the ODT or action line in MARC, transmit the following:

DBS

A list of active databases and their associated mix numbers appears.
Transmit the following for the database audit file you want to close:

mixnumber SM AUDIT CLOSE FORCE

where mixnumber is the mix number of an active database.

The current audit file is now closed, and a new one is created.

You can also use Audit Close utility to close the current audit file. See Audit Close Utility for more information. For additional information on forcing an audit switch, see the Unisys DMSII Utilities documentation.

Terminating AuditTimer

DBAuditTimer is designed to stay in the mix so that it is always available to check audit files; therefore, it automatically re-queues itself after each run. If for some reason you want to quit DBAuditTimer, follow these steps:

From the ODT or MARC action line, type SQ and click Transmit to determine DBAuditTimer’s next job number (the mix number). The following is an example of the information that appears when you transmit an SQ command. (Note that this example uses a sample database called BANKDB.)

QUEUE 1 (FIRST OF 2 ENTRIES) 2984 50 (usercode) DBAUDITTIMER ("BANKDB ON HOST","") QUEUED: 12/9/2009 AT 15:53:59 STARTTIME=16:53:58 QUEUE 7 NO ENTRIES
Type the following DS command for that job number and click Transmit :

mixnumber DS

where mixnumber is the mix number that you received from the SQ command. For the example above, the DS command is:

2984 DS

The following message appears, indicating that DBAuditTimer is no longer running:

mixnumber OPERATOR DSED FROM QUEUE1

Copy Audit Utility

Typically, each time an audit file closes, the DMSII Accessroutines starts the standard DMSII DATABASE/WFL/COPYAUDIT, which does the following:

Copies the closed audit file to tape
Removes the closed audit file from disk

The Databridge Copy Audit utility (WFL/DATABRIDGE/COPYAUDIT) can intercept the copy audit parameters issued by DMSII, modify them, and then pass the new parameters to DATABASE/WFL/COPYAUDIT.

The Databridge Copy Audit utility enables you to do the following:

Specify the number of closed audit files that should be saved on disk. The default is 2 to accommodate transactions that start in one audit file but end in another. The Copy Audit utility deletes any “REMOVE” from the original DMSII COPYAUDIT parameters and then starts DATABASE/WFL/COPYAUDIT with the modified parameter string.
Automatically notify DBServer, which then notifies Enterprise Server to start a batch file running the Client each time an audit file becomes available. Using this feature keeps the Client database less than one audit file behind your primary database.
Run Databridge Span each time an audit file becomes available.

To use the Copy Audit utility

Using CANDE or another editor, open the Copy Audit WFL (WFL/DATABRIDGE/COPYAUDIT).
To automatically notify Databridge Server and the Client each time an audit file becomes available, set the WANTNOTIFY entry to True.
For Databridge Server to notify the Client when an audit file becomes available, you must also configure the NOTIFY parameter in the DBServer parameter file. See NOTIFY.
To change the number of closed audit files saved on disk, set the CONSTANT KEEP entry to the number of closed audit files that you want to keep on disk.

The default and minimum value is 2 to accommodate transactions that start in one audit file but end in another. In other words, the newly closed audit file and the previously closed audit file remain on disk. Only the third oldest audit file is removed from disk. This means that at all times three audit files (one current, two old) will be available on the host.
To run Databridge Span each time an audit file becomes available, remove the comment sign (%) before the following line and then enter the name of the database you are replicating:

%START WFL/DATABRIDGE/SPAN (databasename);
If you only run one copy of Databridge Server on the host, skip to the last step (8). If you run more than one copy of Databridge Server on the same host, you must create a unique name for the port file (AUDITNOTIFY, by default) that each Databridge Server uses to listen for notifications.

Change the following line

FILE AUDITNOTIFY (FILENAME = AUDITNOTIFY);

to

FILE AUDITNOTIFY (FILENAME = TESTNOTIFY);
Change the corresponding line in the WFL/DATABRIDGE/NOTIFY and/or WFL/DATABRIDGE/COPYAUDIT files from

FILENAME = AUDITNOTIFY,

to

FILENAME = TESTNOTIFY,
Save the WFL.

You can modify the DMSII DASDL to start the Copy Audit utility WFL instead of the DMSII default COPYAUDIT WFL for the database you want to replicate. For instructions, see Modify the DASDL for more information.

Modify the DASDL

You can modify the DASDL to start the Copy Audit utility WFL/DATABRIDGE/COPYAUDIT instead of the DMSII default COPYAUDIT WFL. Full details on modifying DASDLs are available in the Unisys DMSII documentation.

To modify the DASDL, open the DASDL and modify the AUDIT TRAIL section. If you are using the copy option, specify WFL/DATABRIDGE/COPYAUDIT for JOB. If you are not using the copy option, add the JOB declaration as shown in example on the next page.

Following is an excerpt of how your existing DASDL might look:

AUDIT TRAIL ( option option
COPY TO TAPE AND REMOVE option option );

Following is the same excerpt with the correct information to start the Databridge Copy Audit WFL.

AUDIT TRAIL ( option option
COPY TO TAPE AND REMOVE JOB WFL/DATABRIDGE/COPYAUDIT option option
);

Audit Close Utility

The Databridge Audit Close utility enables you to close the current audit file and open a new one.

To close the current audit file, run the Audit Close utility as follows:

START WFL/DATABRIDGE/SAMPLE/AUDITCLOSE ("databasename")

where databasename is the name of the database whose audit file you want to close.

Audit Remove Utility

After a Databridge Accessory processes audit files that were copied to a separate audit pack, you can use the Audit Remove utility to remove the processed audit files.

To configure the Audit Remove utility

Using CANDE or another editor, open the sample Audit Remove WFL (WFL/DATABRIDGE/SAMPLE/REMOVEAUDIT).
Modify the values of KEEP, AUDITPREFIX, and AUDITPACK.
Save the sample WFL as follows:

WFL/DATABRIDGE/REMOVEAUDIT/databasename

where databasename is the name of the database you are replicating.
Configure the AUDIT JOB option in the DBServer or Databridge Span parameter file to specify the following:

WFL/DATABRIDGE/REMOVEAUDIT/databasename

See instructions for Databridge Server AUDIT JOB or Databridge Span AUDIT JOB.
Run the Accessory as usual.

After the Accessory processes the audit file, it will start the REMOVEAUDIT WFL, which removes the specified audit file.

Audit Mirroring

You can find instructions for configuring the audit mirror utility in the Databridge Enterprise Server Administrator Guide.

In this mode

You can

Normal mode

Display the current (active) AFN
Display the current database update level
Return the number of sections in an audit file
Generate a report that includes: various timestamps; update levels; DMSII release level; AFN; ABSN; whether the database uses guard files; and whether INDEPENDENTTRANS is set to true or false for a DMSII database. (This information is gathered from the DESCRIPTION file, the DMSUPPORT file, and the CONTROL file). The report also includes mainframe identification information, DBEngine runtime parameters, and Databridge licenses and software.

Interactive mode

Find the first quiet point in an audit trail from a specified AFN and ABSN (you can run DBInfo in normal mode to determine the current AFN and ABSN).
For each found quiet point, DBInfo displays the AFN, ABSN, SEG, and INX. You can then use this information to configure Databridge Span or the Databridge Client after a rollback.

DBInfo Utility

DBInfo enables you to create reports about a specified DMSII database, along with mainframe identification information and Databridge licenses and software. You can run DBInfo in either normal mode or interactive mode. The following table explains the benefits of each:

Run DBInfo in Normal Mode

Use this procedure to run DBInfo in normal mode. You can run DBInfo in normal mode at any time. This allows you to do any of the following:

Generate a report of various timestamps, update levels, etc., for a DMSII database by reading the DESCRIPTION file, DMSUPPORT file, and CONTROL file.

The report also includes mainframe identification information, runtime parameters that DBEngine uses for tracking a particular database, and Databridge licenses and software.

The runtime parameters reflect default values, values in the global parameter file (DATA/ENGINE/CONTROL), and values in the database-specific parameter file (DATA/ENGINE/databasename/CONTROL or DATA/ENGINE/databasename/logicaldatabasename/CONTROL).
Display the current (active) AFN and ABSN.
Determine the DMSII release level, whether guard files are in use, and the setting for INDEPENDENTTRANS.
Return the number of sections in an audit file (See the REMOVEAUDITFILE subroutine in WFL/DATABRIDGE/SAMPLE/REMOVEAUDIT for an example.).

If you need to find the first quiet point in an audit trail from a specified AFN and ABSN, run DBInfo in interactive mode. See Run DBInfo in Interactive Mode.

If you are interested in the layout of your DMSII database, run the Lister Accessory, explained in Chapter 8: Lister.

To run Info Utility in normal mode

Start DBInfo in normal mode by doing one of the following:
- To display the current (active) AFN for a specific database, type the command (including quotation marks)
START WFL/DATABRIDGE/DBINFO ("databasename", "AFN" [, logicaldatabasename])
- To display the current database update level, type the command (including quotation marks)
START WFL/DATABRIDGE/DBINFO ("databasename", "LEVEL"[, "logicaldatabasename"])

where databasename indicates the title of the DESCRIPTION file without the DESCRIPTION node.

The WFL displays the information (AFN or update level). Since the current audit file number is returned in the DBInfo TASKVALUE attribute, you can alter the WFL to use that value in any way you see fit. You can have DBInfo return values to a WFL.
(Optional) If you want to run DBInfo using your own WFL so that it returns certain values to your WFL, use the following table:

Include this TASKVALUE To return this

2 Current AFN

3 Number of sections in the audit file

4 Database update level

Databridge Database Info
Version 6.6.0.000 compiled Saturday, December 15, 2018 @
01:05:22

Databridge DBInfo Report generated Monday, April 29, 2019 @
13:51:04
LX100:1234 HYLOZOIST SSR 58.150.0453, Microcode 11.609 Thursday,
January 30, 2014

(DB66)DESCRIPTION/BANKDB ON HOST
------------------------------------
Desc. timestamp Tuesday, April 23, 2019 @ 11:36:32
DASDL release 58.189
Property level 050810

DB name BANKDB
DB timestamp Tuesday, April 23, 2019 @ 11:36:32
Update level 1
Update timestamp Tuesday, April 23, 2019 @ 11:36:38
DMSII release 58.189
DB prop. level 050810
ACCESSROUTINES SYSTEM/ACCESSROUTINES
RECOVERY SYSTEM/DMRECOVERY
DATARECOVERY SYSTEM/DMDATARECOVERY
RECONSTRUCT RECONSTRUCT/BANKDB
GUARDFILE <none>
Reorg required False
INDEPENDENTTRANS True
REAPPLYCOMPLETED True
Backout to SYNC False
RDSSTORE False
Statistics False
Is a MODEL False

(DB66)DMSUPPORT/BANKDB ON HOST
----------------------------------
DB name BANKDB
DB timestamp Tuesday, April 23, 2019 @ 11:36:32
Update level 1
Update timestamp Tuesday, April 23, 2019 @ 11:36:38
INDEPENDENTTRANS True
REAPPLYCOMPLETED True
Last structure 56
Phys. structures 41

(DB66)BANKDB/CONTROL ON HOST.
---------------------------------
CF format level 3900
CF release 58.189.8007
CF creation Tuesday, April 23, 2019 @ 11:36:41
DB timestamp Tuesday, April 23, 2019 @ 11:36:32
Update level 1
Update timestamp Tuesday, April 23, 2019 @ 11:36:38
Reorg state 0
INDEPENDENTTRANS True
REAPPLYCOMPLETED True
INUSE False
REBUILD False
ROLLBACK False
RECONSTRUCT False
TRACKER False
FAMILY change False
Audit file nbr. 1
Audit block nbr. 123

Product (installs)           License expiration
--------------------------------------- -------------------------------

- - - - - - - - -
Host (10)                  never
Client (99)                never
Twin (10)                  never
DMSII Client (10)          never
Enterprise (10)            never
AuditMirror (10)           never
File Transfer (10)         never
Databridge Cluster (10)    never

Parameters
----------
AFN change doc record = false
Checkpoint every QPT = false
Checkpoint idle DB = false
Checkpoint Long Trans = false
Consolidate StateInfo = false
Documentation records = false
Don't wait on NO FILE = false
Embedded extracts = false
Filtered item count = false
Ignore reorgs = false
Include link items = false
Mirrored audit = false
Mirrored database = false
Modifies Before-After = false
Offline clone = false
Population in DSInfo = false
Pre-error StateInfo = false
Print statistics = false
Read active audit = false
Read uncached only = false
Remote host readahead = false
Reversals as updates = false
StateInfo update lvl. = false
Unformatted updates = false
Ungrouped updates = false
Wait rather than AX = false
Extract Workers default: 10 (allow 1 - 4095)
Enterprise Workers default: 0 (allow any)
Checkpoint Records default: 1000 (allow any)
Checkpoint Blocks default: 100 (allow any)
Checkpoint Transactions default: 0 (allow any)
Checkpoint Seconds default: 0 (allow any)
Primary audit = (no access)
DMUtility = <default> SYSTEM/DMUTILITY.
DMControl = <default> SYSTEM/DMCONTROL.
DMRecovery = <default> SYSTEM/DMRECOVERY.
DMSIISupport = DMSIISUPPORT
          []
Database available anytime

Version Program
Compile Timestamp
----------------------- ----------------------------------------------
---------------------------- ------------------------------
06.006.0003 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SPAN ON HOST
Wednesday, February 13, 2019 @ 01:01:10
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/DBINFO ON HOST
Saturday, December 15, 2018 @ 01:05:20
06.006.0014 SSR 58.189 (DB66)OBJECT/DATABRIDGE/ENGINE ON HOST
Friday, January 11, 2019 @ 01:02:02
06.006.0014 SSR 58.189 (DB66)OBJECT/DATABRIDGE/ENGINE/DEBUG ON HOST
Friday, January 11, 2019 @ 01:02:02
06.006.0014 SSR 58.189 (DB66)OBJECT/DATABRIDGE/ENGINE/STATS ON HOST
Friday, January 11, 2019 @ 01:01:37
06.006.0014 SSR 58.189 (DB66)OBJECT/DATABRIDGE/ENGINE/NOSTATS ON HOST
Friday, January 11, 2019 @ 01:01:09
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/LISTER ON HOST
Saturday, December 15, 2018 @ 01:04:39
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SAMPLE/SQLGEN ON HOST
Saturday, December 15, 2018 @ 01:05:34
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SAMPLE/READDOC ON HOST
Saturday, December 15, 2018 @ 01:05:45
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SAMPLE/COBOLGEN ON
HOST Saturday, December 15, 2018 @ 01:05:36
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SAMPLE/DASDLGEN ON
HOST Saturday, December 15, 2018 @ 01:05:42
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SAMPLE/REFORMAT ON
HOST Saturday, December 15, 2018 @ 01:05:30
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SAMPLE/AUDITCLOSE ON
HOST Saturday, December 15, 2018 @ 01:05:40
00.000.0000 SSR 58.150 (DB66)OBJECT/DATABRIDGE/SAMPLE/EXTRACTADDRESS
ON HOST Saturday, December 15, 2018 @ 01:05:31
06.006.0007 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SERVER ON HOST
Wednesday, February 13, 2019 @ 01:01:41
06.006.0007 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SERVER/DEBUG ON HOST
Wednesday, February 13, 2019 @ 01:01:41
06.006.0007 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SERVER/STATS ON HOST
Wednesday, February 13, 2019 @ 01:01:31
06.006.0007 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SERVER/NOSTATS ON HOST
Wednesday, February 13, 2019 @ 01:01:22
00.000.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/DCKEYIN ON HOST
Saturday, December 15, 2018 @ 01:00:56
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SUPPORT ON HOST
Saturday, December 15, 2018 @ 01:04:30
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SUPPORT/BANKDB ON HOST
Tuesday, April 23, 2019 @ 11:38:38
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SUPPORT/BANKDB/1 ON
HOST Tuesday, April 23, 2019 @ 11:38:38
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SUPPORT/TESTDB ON HOST
Wednesday, April 10, 2019 @ 17:52:11
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SUPPORT/TESTDB/23 ON
HOST Wednesday, April 10, 2019 @ 17:52:11
06.003.0009 SSR 58.189 (DB66)OBJECT/DATABRIDGE/BCNOTIFY ON HOST
Saturday, December 15, 2018 @ 01:01:07
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/SNAPSHOT ON HOST
Saturday, December 15, 2018 @ 01:05:23
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/GENFORMAT ON HOST
Saturday, December 15, 2018 @ 01:03:53
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/AUDITTIMER ON HOST
Saturday, December 15, 2018 @ 01:04:20
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/CHANGEUSER ON HOST
Saturday, December 15, 2018 @ 01:05:17
06.006.0001 SSR 58.189 (DB66)OBJECT/DATABRIDGE/AUDITMIRROR ON HOST
Saturday, December 15, 2018 @ 01:04:22
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/COBOLSUPPORT ON HOST
Saturday, December 15, 2018 @ 01:05:27
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/DMSIISUPPORT/BANKDB/
DB66 ON HOST Tuesday, April 23, 2019 @ 11:38:10
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/DMSIISUPPORT/TESTDB/
TESTDB ON HOST Wednesday, April 10, 2019 @ 17:26:03
06.006.0001 SSR 58.189 (DB66)OBJECT/DATABRIDGE/LICENSEMANAGER ON HOST
Saturday, December 15, 2018 @ 01:01:00
06.006.0000 SSR 58.189 (DB66)OBJECT/DATABRIDGE/LICENSESUPPORT ON HOST
Saturday, December 15, 2018 @ 01:01:04
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/READER/COMS ON HOST
Saturday, December 15, 2018 @ 01:06:04
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/READER/BICSS ON HOST
Saturday, December 15, 2018 @ 01:06:09
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/READER/SUMLOG ON HOST
Saturday, December 15, 2018 @ 01:05:59
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/READER/TTRAIL ON HOST
Saturday, December 15, 2018 @ 01:06:07
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/READER/LINCLOG ON HOST
Saturday, December 15, 2018 @ 01:06:02
06.006.0000 SSR 58.150 (DB66)OBJECT/FILEBRIDGE/READER/BANKFILE ON
HOST Saturday, December 15, 2018 @ 01:05:57
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/READER/DISKFILE ON
HOST Saturday, December 15, 2018 @ 01:05:55
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/READER/PRINTFILE ON
HOST Saturday, December 15, 2018 @ 01:05:53
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/READER/USERDATAFILE ON
HOST Saturday, December 15, 2018 @ 01:06:14
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/SAMPLE/READER/COMS ON
HOST Saturday, December 15, 2018 @ 01:06:04
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/SAMPLE/READER/BICSS ON
HOST Saturday, December 15, 2018 @ 01:06:09
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/SAMPLE/READER/SUMLOG
ON HOST Saturday, December 15, 2018 @ 01:05:59
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/SAMPLE/READER/TTRAIL
ON HOST Saturday, December 15, 2018 @ 01:06:07
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/SAMPLE/READER/LINCLOG
ON HOST Saturday, December 15, 2018 @ 01:06:02
06.006.0000 SSR 58.150 (DB66)OBJECT/FILEBRIDGE/SAMPLE/READER/BANKFILE
ON HOST Saturday, December 15, 2018 @ 01:05:57
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/SAMPLE/READER/DISKFILE
ON HOST Saturday, December 15, 2018 @ 01:05:55
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/SAMPLE/READER/
PRINTFILE ON HOST Saturday, December 15, 2018 @ 01:05:53
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/SAMPLE/READER/
USERDATAFILE ON HOST Saturday, December 15, 2018 @ 01:06:14
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/INITIALIZE ON HOST
Saturday, December 15, 2018 @ 01:05:48
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/PATCHDASDL ON HOST
Saturday, December 15, 2018 @ 01:05:47
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/COBOLTODASDL ON HOST
Saturday, December 15, 2018 @ 01:05:49
06.006.0000 SSR 58.189 (DB66)OBJECT/FILEBRIDGE/USERDATATODASDL ON
HOST Saturday, December 15, 2018 @ 01:06:11
End of DBInfo report

Displaying the Current AFN

Follow these steps to display the current (active) AFN for a specific DMSII database:

Start DBInfo in normal mode by typing the following command. You must include the quotes.

START WFL/DATABRIDGE/DBINFO ("databasename", "AFN" [, logicaldatabasename]) where databasename indicates the title of the DESCRIPTION file without the DESCRIPTION node.
The WFL displays the current AFN. Since the current audit file number is returned in the DBInfo TASKVALUE attribute, you can alter the WFL to use that value in any way you see fit.

Displaying the Current Database Update Level

Follow these steps to display the current database update level for a specific DMSII database:

Start DBInfo in normal mode by typing the following command. You must include the quotes.

START WFL/DATABRIDGE/DBINFO ("databasename", "LEVEL" [, "logicaldatabasename"])

where databasename indicates the title of the DESCRIPTION file without the DESCRIPTION node.
The WFL displays the current update level. Since the current update level is returned in the DBInfo TASKVALUE attribute, you can alter the WFL to use that value in any way you see fit.

Retrieving the Number of Sections in an Audit File

See the REMOVEAUDITFILE subroutine in WFL/DATABRIDGE/SAMPLE/REMOVEAUDIT for an example of how to determine how many sections an audit file has.

Run DBInfo in Interactive Mode

You can run DBInfo in interactive mode to find the first quiet point in an audit trail from a specified AFN and ABSN and use that information (that is, AFN, ABSN, SEG, and INX) to configure Databridge Span or a Databridge Client after a rollback. (Run DBInfo in normal mode to determine the current AFN and ABSN.)

In interactive mode, DBInfo uses a remote file interface.

To run DBInfo in interactive mode

Start DBInfo in interactive mode by typing the following command. You must include the quotation marks.

START WFL/DATABRIDGE/DBINFO ("databasename", "parameter [ON diskfamilyname] " [, "logicaldatabasename"])

where databasename indicates the title of the DESCRIPTION file without the DESCRIPTION node, parameter is one of the following parameters that initiate interactive mode, and diskfamilyname is the pack DBInfo will use for reading the audit files (the default is the primary audit pack specified in the DASDL).

All of the following parameters initiate interactive mode, so use the parameter that is easiest for you to remember:

FINDQPT FIND QPT FIND QPT FIRSTQPT FIRST FIRST QPT
When prompted, type the AFN and the ABSN in the following format. The ABSN must be a value of two or greater. The ABSN does not have to be in the specified audit file. DBInfo will stop at the first QPT that has an ABSN greater than or equal to the specified ABSN.

Note

If you do not know the ABSN, enter 2 and DBInfo will use the first quiet point in the specified file.

space
Press transmit.

DBInfo returns the AFN, ABSN, SEG, INX, and time stamp for the first quiet point after the specified AFN and ABSN.

For example:

Quiet point found on December 9, 2009 @ 09:12:17 at audit location AFN = 18 ABSN = 17090 SEG = 9 INX = 10 Please enter <AFN> space <ABSN> or ?END
To search for another quiet point, type the AFN and the ABSN and then press transmit. To quit DBInfo, type ?END and then press transmit.

Example

The following example uses a sample database named BANKDB:

START WFL/DATABRIDGE/DBINFO ("(USER)BANKDB ON HOST","QPT")

The following prompt appears:

Please enter <AFN> space <ABSN> or ?END

Enter the AFN and ABSN to specify the starting point of the search. Using the example in step 2, you would enter:

18 17090

DBInfo returns the following:

Searching from AFN 18 ABSN 17090 ... Quiet point found on December 9, 2009 @ 09:12:17 at audit location AFN = 18 ABSN = 17090 SEG = 9 INX = 10 Please enter <AFN> space <ABSN> or ?END

DBInfo WFL

You can modify the DBInfo WFL for the following:

STARTTIME
QUEUE — If you want the program to enter the system through job queue 10, you must modify the WFL to include the QUEUE (or CLASS) = 10 declaration.
BDNAME — This is the default location where the printer backup files are created.

Include this TASKVALUE	To return this
2	Current AFN
3	Number of sections in the audit file
4	Database update level