NAME
seltrc - select traces based on trace header words and an
input value
SYNOPSIS
seltrc [ -Nntap ] [ -Ootap ] [ -vval ] [ -nsnstr ] [ -nenetr
] [ -rsnrst ] [ -renred ] [ -Titwd ] [ -lt ] [ -le ] [ -eq ]
[ -ge ] [ -gt ] [ -neq ] [ -L ] [ -R ] [ -padnpad ] [ -V ] [
-? ]
DESCRIPTION
seltrc selects traces from the input based on a trace header
key (see mnemonic description of header words in scan) and
an integer value both supplied on the command line. Depend-
ing on the logic flag traces will be passed that are either
less than, equal to, or greater than the given value. See
BUGS below.
The operation is done either on the entire data set
(default) or on each successive record. If done record-by-
record the option to pad a user specified number of traces
is available.
seltrc gets both its data and its parameters from command
line arguments. These arguments specify the input, output,
the start and end traces, the key, the value, the flag, and
verbose printout, if desired.
Command line arguments
-N ntap
Enter the input data set name or file immediately after
typing -N unless the input is from a pipe in which case
the -N entry must be omitted. This input file should
include the complete path name if the file resides in a
different directory. Example -N/b/vsp/dummy tells the
program to look for file 'dummy' in directory '/b/vsp'.
-O otap
Enter the output data set name or file immediately
after typing -O. This output file is not required when
piping the output to another process. The output data
set also requires the full path name (see above).
-v val
Enter the value comaped to which the trace header
values will be lt, eq, or gt
-T itwd
Enter the trace header word mnemonic (e.g. DstSgn for
signed trace distance)
-ns nstr
Enter the start trace number. The default is the first
trace of the record.
-ne netr
Enter the end trace number. The default is the last
trace of the record.
-rs nrst
Enter start record number. Default value is the first
record.
-re nred
Enter end record number. Default value is last record.
-lt -le -eq -ge -gt -neq
Enter one of these flags referring to "less than",
"less than and equal to", "equal to", greater than or
equal to", "greater than", and "not equal to" respec-
tively
-R Enter the command line argument '-R' to process
record-by-record. The selection operation is done on
each input record and the output is padded either to
the length of record given by -ns, -ne above or by user
input below.
-pad npad
For record-by-record operation enter length of output
record in traces. Default will be defined by -ns, -ne
entries above. Padding is done after live traces are
written.
-L Enter the command line argument '-L' to process only
live traces
-V Enter the command line argument '-V' to get additional
printout.
-? Enter the command line argument '-?' to get online
help. The program terminates after the help screen is
printed.
EXAMPLES
1. seltrc can be used to select ranges of traces within each
record:
seltrc -Nindata -v2000 -le -TDstSgn -R |
seltrc -Ootdata -v1000 -ge -TDstSgn -R
where the first seltrc passes all traces having signed trace
distances less than or equal to 2000 (padding the rest of
each record to the input record trace length) and the second
seltrc passes all traces having signed trace distances
greater then or equal to 1000. The effect then is to filter
the data to only trace distances between 1000 and 2000.
2. seltrc can be used to select ranges of traces within a
data set:
seltrc -Nindata -v2000 -le -TDstSgn -R |
seltrc -Ootdata -v1000 -ge -TDstSgn -R
where the trace distance filtering operation is the same as
above but now the entire data set is searched for these
traces without regard to record boundaries. The output will
then be a data set comprised of only these traces one after
the other as they were found in the input data. utop must
be run in order to fix up the line header (which will now be
wrong as far as the number of records and the number of
traces per record is concerned). The fButop can be done in
place.
BUGS
Warning: because it is unknown just how many traces will be
output when the line header is written the number of traces
and the number of records will be wrong. Be aware of this
and be prepared to scan the output data set and use utop to
fix the line header. The printout file generated by seltrc
will specify at the bottom just how many total traces were
written.
SEE ALSO
scan, getval
AUTHOR
Paul Gutowski, TRC, x3146
COPYRIGHT
copyright 2001, Amoco Production Company
All Rights Reserved
an affiliate of BP America Inc.
Man(1) output converted with
man2html