dssrouterview - DSS 6 | Data Source Solutions Documentation

Documentation: dssrouterview - DSS 6 | Data Source Solutions Documentation

dssrouterview

Usage

dssrouterview [-restrict opts] [-xml opts] [-F] chn [txfile]... Shows the contents of transaction files currently available in the channel's router directory. The output is shown as XML, which is sent to stdout. Options -b, -c, -e, -f, -i, -n, -t and -w can be used to restrict the changes shown. Option -j shows journal files instead of transaction files.
dssrouterview -s [-cloc] [-iloc] [-xml opts] chn Shows the contents of control files as XML.
dssrouterview [-xml opts] chn dssfile... Shows the contents of internal DSS files, such as a *.enroll or *.cap_state file in a router directory, any of the files in a file location's _dss_state directory, a control file (in directory DSS_CONFIG/hubs/hub/channels/chn/control).

Description

Command dssrouterview displays data from internal DSS files such as transaction and journal files in the router directory on the hub machine.

General Options

Parameter	Description
`-F`	Identifies transaction file as captured by a 'blob file' channel (these use a different decompression algorithm). This is seldom necessary, because DSS should deduce the decompression algorithm from the basename of the transaction file.
`-s`	View contents of control files instead of transaction files. Control files are created by dssrefresh with option `-q`, or by command dsscontrol.

Restrict Options

Parameter	Description
`-btime`	Only changes after capture time. Valid formats for `time` are YYYY-MM-DD [HH:MM:SS] in local time or YYYY-MM-DDTHH:MM:SS+TZD or YYYY-MM-DDTHH:MM:SSZ or today or now[[±]SECS] or an integer (seconds since 1970-01-01 00:00:00 UTC). For example, -b "2010-07-29 10:30:21" or -b now-3600 (changes in the last hour). This option is equivalent to -wdss_cap_tstamp>=time.
`-cloc`	Only changes from specific capture location.
`-etime`	Only changes before capture time. Valid formats for `time` are YYYY-MM-DD [HH:MM:SS] in local time or YYYY-MM-DDTHH:MM:SS+TZD or YYYY-MM-DDTHH:MM:SSZ or today or now[[±]SECS] or an integer (seconds since 1970-01-01 00:00:00 UTC). For example, -b "2010-07-29 10:30:21" or -b now-3600 (changes in the last hour). This option is equivalent to -wdss_cap_tstamp>=time.
`-ftxfile`	Contents of a specific transaction file `txfile`. This option can be specified multiple times. Another way to see the contents of a specific transaction file is to list the file(s) after the channel name (as a third positional parameter). The advantage is that 'globbing' can be used for a list of files (e.g. *.tx_l*) whereas `-f` only accepts one file (although it can be supplied multiple times).
`-iloc`	Only changes for a specific integrate location.
`-j`	Show the contents of DSS journal files in directory DSS_CONFIG/hubs/hub/channels/chn/locs/loc/jnl. These files are kept only if action Integrate is defined with parameter JournalRouterFiles.
`-n`	Newest. Only most recent transaction file(s).
`-ty`	Only rows for tables specified by `y`. Values of `y` may be one of the following: tbl : Only table tbl. t1-t2 : All tables that fall alphabetically between t1 and t2 inclusive. !tbl : All tables except tbl. !t1-t2 : All tables except for those that fall alphabetically between t1 and t2 inclusive. Several `-ty` instructions can be supplied together.
`-wwhere`	Where condition which must have form columname operator value. The operator can be either = != <> > < >= or <=. The value can be a number, 'str', X'hex', or a date. Valid date formats are YYYY-MM-DD [HH:MM:SS] in local time or YYYY-MM-DDTHH:MM:SS+TZD or YYYY-MM-DDTHH:MM:SSZ or today or now [[±]SECS] or an integer (seconds since 1970-01-01 00:00:00 UTC). For some operators (= != <>) the value can be a list seperated by '\|'. If multiple `-w` options are supplied then they are AND-ed together.

XML Options

Parameter	Description
`-d`	Show column data type information.
`-h`	Print data values in hexadecimal format.

Extract Options

Parameter	Description
-xtgt	Extract data from transaction files into a target tgt. Value tgt should be either a location name (applicable for channels with tables) or a directory path on the hub machine (applicable for channels without tables).

Examples

This section provides examples of using the dssrouterview command.

Example 1. Show the contents of file

The following command shows the contents of certain transaction files.

{% tabs %}

{% tab label="Linux" %}

dssrouterview myhub mychn $DSS_CONFIG/hubs/myhub/channels/mychn/locs/mysrc/router/loc_mytgt/*.tx_dec01

{% /tab %}

{% tab label="Windows" %}

dssrouterview myhub mychn %DSS_CONFIG%/hubs/myhub/channels/mychn/locs/mysrc/router/loc_mytgt/*.tx_dec01

{% /tab %}

{% /tabs %}

The following command shows the contents of a capture state file named 619eaa9c_5c37b-619eaab9.cap_state.

{% tabs %}

{% tab label="Linux" %}

dssrouterview myhub mychn $DSS_CONFIG/hubs/myhub/channels/mychn/locs/src/router/619eaa9c_5c37b-619eaab9.cap_state

{% /tab %}

{% tab label="Windows" %}

dssrouterview myhub mychn %DSS_CONFIG%/hubs/myhub/channels/mychn/locs/src/router/619eaa9c_5c37b-619eaab9.cap_state

{% /tab %}

{% /tabs %}

Example 2. Show any changes for a table from the journals

The following command shows any changes for a table named cust from the journals.

dssrouterview -j -tcust myhub mychn

Example 3. Show any changes from router files between two transaction sequences

The following command shows any changes for a channel (e.g., mychn) that were captured between two dss_tx_seq values.

dssrouterview -w "dss_tx_seq>='00000000004956275877:00001'" -w "dss_tx_seq<='00000000004956275877:00009'" myhub mychn