echo off
.                                _runme3.bat        revised 14-aug-83  16:55
slash/lll
echo    Having dispensed (with) the fundamentals, let's move on to a discussion
echo    of ways to improve the performance of DOS 2.0 Batch Files -- especially
echo    large ones, which you will soon be writing.  Since we're going to get
echo    rather verbose, let's continue by displaying a text file, using
echo    DOS 2.0's MORE filter.
slash/ll
echo    We'll turn "echo" on so that you can see each Batch File line as it
echo    is executed:
echo on
pause
more <_perform.rem
pause
rem                                     ---
rem     With "echo" on, each line of the Batch File is displayed as it is
rem     executed.  There are several ways to display comments.  I'm using
rem     the "rem" statement now.  Notice that all lines are double-spaced.
rem     This is caused by "rem" -- sometimes it's desirable to double-space
rem     and sometimes it's not, but we have no choice while using "rem".
rem
pause
.       Another method of displaying comments with "echo" on is to use a "."
.
.       (DANGER!  THIS METHOD IS UNDOCUMENTED AND MAY DISAPPEAR IN A SUB-
.       SEQUENT REVISION OF DOS ).
.
.       Having done my duty and made that disclaimer, please notice that
.       the comments are single-spaced.  Nice.  They probably won't
.       change it anyway so let's cheat and use ".",too.  But, I warned us.
.
.       Remember that "rem" and "." do not display when echo is "off".
.
pause
echo    We can also use echo subcommand for comments, but with echo "on" it
echo    can certainly get confusing
echo    confusing ...
echo    confusing ...
pause
echo    off
echo    But having turned echo off, I can now use the echo subcommand to
echo    display neat single-spaced comments.  I'll turn it on again so that
echo    we can clearly follow what is going on.
echo    on
.
.       Let's get to the meat of this tutorial and discuss the utilities
.       on this diskette.  By the way, I've already used most of them
.       while echo was "off" and you couldn't see. Let's "chain" to
.       the next Batch File (because this one has grown large enough to
.       have an annoying response time if we branch).  All we do to run
.       another Batch File from this one is just give its name as a
.       command line.  The next file's name is  " _query.bat " .
.
.       When you chain your own Batch Files, be sure to pass any parameters
.       that the next Batch File needs in the command line.
.
.       Here goes ...
pause
_query
                                                                                           
