VI.e.2 Exec Scripts
-------------------
When parameters are required, or more generally in any case including the non-
parameterized script, an EXEC Script is used.  To define a EXEC Script, the
path must specify a DCL command file with .SCRIPT as its extension as an exec
file resource, as in the following link tuple:

	Name=Another dynamic "About" File
	Type=0
	Port=+
	Host=+
	Path=exec:parm1 parm2:[_dynamic_documents]_demonstration.script

In this example, parameters are specified between a pair of colons (":"), and
the resource type is the keyword "exec" instead of the character "0".   Notice
the Type= specification remains "0"; clients apparently don't understand a
Type=e specification, and it turns out to be irrelevant in this case.  Now of
course another Type=1 or Type=9 or whatever could indeed be allowed, provided
the path=exec:... specified produces the correct information in its output.
Arguments are optional; "Path=exec::scriptfile" is perfectly acceptable. The
server will execute the following command in a subprocess:

   $ @[_dynamic_documents]_demonstration.script/output=xxx "parm1 parm2"

and the script file can interpret the parameter symbol P1 to secure the
parameters.  The temporary file "xxx" will again be written to by the script
file, and when the script file completes execution the server will write the
file back to the client.

.