1GTS_COMPARE(1)                   User Commands                  GTS_COMPARE(1)
2
3
4

NAME

6       gts_compare - manual page for gts_compare
7

DESCRIPTION

9       NAME    gts_compare
10
11       DESCRIPTION
12
13              Compare  GTS  messages  contained in two files.  If some differ‐
14              ences are found it fails returning an error code.   Default  be‐
15              haviour: bit-by-bit compare, same order in files.
16
17       USAGE
18
19              gts_compare [options] file file
20
21       OPTIONS
22
23       -b key,key,...
24
25              All  the  keys  in  this  list  are  skipped  in the comparison.
26              Bit-by-bit compare on.
27
28       -d     Write different messages on files
29
30       -c key[:i|d|s|n],key[:i|d|s|n],...
31
32              Only the listed keys or namespaces (:n) are  compared.  The  op‐
33              tional  letter  after the colon is used to force the type in the
34              comparison: i->integer, d->float, s->string, n->namespace.   See
35              -a option. Incompatible with -H option.
36
37       -S start
38              First field to be processed.
39
40       -E end Last field to be processed.
41
42       -a       -c option modifier. The keys listed with the option -c will be
43              added to the list of keys compared without -c.
44
45       -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
46
47              Where clause.  Messages are processed only if they match all the
48              key/value  constraints.  A valid constraint is of type key=value
49              or key!=value.  For each key a string (key:s), a double  (key:d)
50              or  an  integer  (key:i)  type can be specified. Default type is
51              string.  In the value you can also use the forward-slash charac‐
52              ter  '/' to specify an OR condition (i.e. a logical disjunction)
53              Note: only one -w clause is allowed.
54
55       -f     Force. Force the execution not to fail on error.
56
57       -V     Version.
58
59       -7     Does not fail when the message has wrong length
60
61       -v     Verbose.
62
63       NAME    gts_compare
64
65       DESCRIPTION
66
67              Compare GTS messages contained in two files.   If  some  differ‐
68              ences  are  found it fails returning an error code.  Default be‐
69              haviour: bit-by-bit compare, same order in files.
70
71       USAGE
72
73              gts_compare [options] file file
74
75       OPTIONS
76
77       -b key,key,...
78
79              All the keys  in  this  list  are  skipped  in  the  comparison.
80              Bit-by-bit compare on.
81
82       -d     Write different messages on files
83
84       -c key[:i|d|s|n],key[:i|d|s|n],...
85
86              Only  the  listed  keys or namespaces (:n) are compared. The op‐
87              tional letter after the colon is used to force the type  in  the
88              comparison:  i->integer, d->float, s->string, n->namespace.  See
89              -a option. Incompatible with -H option.
90
91       -S start
92              First field to be processed.
93
94       -E end Last field to be processed.
95
96       -a      -c option modifier. The keys listed with the option -c will  be
97              added to the list of keys compared without -c.
98
99       -w key[:{s|d|i}]{=|!=}value,key[:{s|d|i}]{=|!=}value,...
100
101              Where clause.  Messages are processed only if they match all the
102              key/value constraints.  A valid constraint is of type  key=value
103              or  key!=value.  For each key a string (key:s), a double (key:d)
104              or an integer (key:i) type can be  specified.  Default  type  is
105              string.  In the value you can also use the forward-slash charac‐
106              ter '/' to specify an OR condition (i.e. a logical  disjunction)
107              Note: only one -w clause is allowed.
108
109       -f     Force. Force the execution not to fail on error.
110
111       -V     Version.
112
113       -7     Does not fail when the message has wrong length
114
115       -v     Verbose.
116
117
118
119gts_compare                      November 2023                  GTS_COMPARE(1)