VI.e.1 Text File Scripts
------------------------
It is *STRONGLY RECOMMENDED* that you not use Text File Scripts.  They seem to
be a holdover from long ago, and all of its functionality is provided by the
EXEC script processing facility.  However, some users may feel a need to
define non-parameterized Text File Scripts.

To define a Text File Script, the path must specify a DCL command file with
.SCRIPT as its extension as a text file resource, as in the following link
tuple:

	Name=A dynamic "About" File
	Type=0
	Port=+
	Host=+
	Path=0[_dynamic_documents]_demonstration.script

No parameters to the script are allowed as part of this specification.  The
server will execute the following command in a subprocess:

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

The script is expected to perform its tasks, any the entire log of the
execution is will be saved in the temporary file "xxx."  After completion of
the script, the contents of the temporary file "xxx" are transmitted to the
client, instead of the script itself.  Care must be taken to insure that the
script is fully debugged and foolproof, since subtle error conditions can
result in the script failing and not producing a usable log file.  If the
server cannot sucessfully open the log file, the server will pass back the
*script file* as the results of the client's request, possibly causing great
consternation and confusion to the client's user.

.