Displays a group of NDF names NDFECHO
Two modes are available.
If the NDFs are specified via the NDF parameter, then the NDFs must exist and
be accessible (an error is reported otherwise). The NDF names obtained can
then be modified by supplying a suitable GRP modification expression such as
"_A"
for Parameter MOD.
To list NDFs that may not exist, supply a null (!
) value for Parameter NDF and the main
group expression to Parameter MOD.
TRUE
, any relative NDF paths are
converted to absolute, using the current working directory. [FALSE]
TRUE
, then only display paths for NDFs specified by Parameter MOD
that actually exist and are accessible. [FALSE]
!
) value causes the first
NDF to be used (Index 1). [!]
[]
[!]
"_A"
then the supplied NDF names will be modified by appending "_A"
to them. No modification
occurs if a null (!
) value is supplied.
If a null value is supplied for Parameter NDF then the value supplied for Parameter MOD should not include an asterisk, since there are no names to be modified. Instead, the MOD value should specify an explicit group of NDF names do not need to exist.
The list can be filtered to remove any NDFs that do not exist (see Parameter EXISTS).
[!]
An NDF name, optionally containing wild-cards and/or regular expressions
(""
,
"?"
, "[a-z]"
etc.).
The name of a text file, preceded by an up-arrow character
""
.
Each line in the text file should contain a comma-separated list of elements, each of
which can in turn be an NDF name (with optional wild-cards, etc.), or another file
specification (preceded by an up-arrow). Comments can be included in the file by
commencing lines with a hash character "#"
.
If the value supplied for this parameter ends with a hyphen, then you are re-prompted for further input until a value is given which does not end with a hyphen. All the NDFs given in this way are concatenated into a single group.
If a null (!
) value is supplied, then the displayed list of NDFs is determined by the
value supplied for the MOD parameter.
!
) value causes all NDFs to be displayed. [!]
"Base"
–- The base file name.
"Dir"
–- The directory path (if any).
"Fspec"
–- The directory, base name and file type concatenated to form a full file
specification.
"Ftype"
–- The file type (usually .sdf
but may not be if any foreign NDFs are
supplied).
"HDSpath"
–- The HDS path within the container file (if any).
"Path"
–- The full name of the NDF as supplied by the user.
"Slice"
–- The NDF slice specification (if any).
Note, the fields are extracted from the NDF names as supplied by the user. No missing
fields (except for "Ftype"
) are filled in. ["Path"]
mycont.sdf
. The NDFs must all exist. files.lis
. The NDFs must all exist. files.lis
, but
appending "_a"
to the end of each name. The NDFs must all exist. The listed
NDF names are written to a new text file called log.lis
. base
, but replacing "_a"
with
"_b"
in their names. The NDFs need not exist since they are completely specified by
Parameter MOD and not by Parameter NDF. "[chars]"
–- Matches any of the characters within the brackets.
"[chars]"
–- Matches any character that is not within the brackets (ignoring the initial
""
character).
"."
–- Matches any single character.
"d"
–-
Matches a single digit.
"D"
–-
Matches anything but a single digit.
"w"
–-
Matches any alphanumeric character, and "_"
.
"W"
–-
Matches anything but alphanumeric characters, and "_"
.
"s"
–-
Matches white space.
"S"
–-
Matches anything but white space.
Any other character that has no special significance within a regular expression matches itself. Characters that have special significance can be matched by preceding them with a backslash () in which case their special significance is ignored (note, this does not apply to the characters in the set dDsSwW).
Note, minus signs ("-"
) within brackets have no special significance, so ranges of
characters must be specified explicitly.
The following quantifiers are allowed.
"*"
–- Matches zero or more of the preceding atom, choosing the largest possible number
that gives a match.
"*?"
–- Matches zero or more of the preceding atom, choosing the smallest possible
number that gives a match.
"+"
–- Matches one or more of the preceding atom, choosing the largest possible number
that gives a match.
"+?"
–- Matches one or more of the preceding atom, choosing the smallest possible number
that gives a match.
"?"
–- Matches zero or one of the preceding atom.
"{n}"
–- Matches exactly
occurrences of the preceding atom.
The following constraints are allowed.
""
–-
Matches the start of the test string.
"$"
–- Matches the end of the test string.
Multiple templates can be concatenated, using the "|"
character to separate them.
The test string is compared against each one in turn until a match is found.