Report on the PVL statements found in a file label.
- This help message.
- Report the PVL statement contents of the file.
- Count the number of parameters in the file.
- Add value counts to the parameter count listing.
- Find the named parameter.
If name is
@filename get the parameter names from the file.
The input file is processed by the PPVL module to obtain an aggregate ("The Container") of all PVL parameters found the in the file header label. Then the file is checked for the presence of a PDS EOL label (a PVL label block that is not in the file header), which is appended to the aggregate if present.
If the input file is not specified,
stdin is read
by default. Note: EOL
labels in a file read from a pipe currently can not be accessed.
-report option (the default if no options
are specified), all of the
PVL parameters found in the file are listed using formal PVL syntax
be different than the syntax of the file).
-count option provides a listing of the name of
each aggregate parameter
and the number of parameters contained within it. The
-values option adds to
this listing the name of each parameter
and the number
of values it contains.
-count option is implicit with
-values option; i.e. both
do not need to be specified.
At the end of these listings the total number
parameters - and also values for the
-values option -
in the file is listed.
-find option lists all occurances of parameters
that match the specified name (completely -
not a pattern match - but without regard to case),
with all of the parameter's values. If the parameter is an aggregate
contents are listed. If the name is immediately preceeded by the
then it is used as the name of a file containing a list of parameter
per line, to find.
Note: Parameter names may specified as the full path that
parent parameters (aggregates) starting with the top file aggregate
(denoted by an initial
'/' character) with additional
slash characters separating each parent in the path leading to
desired parameter. Parameter names, including parent paths, that are
anchored to the top file aggregate (with a leading slash) may occur
locations. Parameter names specified by the user may be anchored or
Parameter names in program listings are always anchored with all
parents in the