Guardian User's Guide

Managing Your Spooler Jobs Using Peruse
Guardian User’s Guide—425266-001
13-10
Finding TAL Errors
Finding TAL Errors
Instead of waiting for your TAL compilation to finish, you can use the FIND, PAGE,
and LIST commands to search for errors. Because all TAL compilation errors begin
with the string **** ERROR, you can use this string to search for errors in your
program. For example:
Continue using the FIND command to find any remaining errors; if you don’t specify a
new string, FIND continues to search for the same string. Determine the page on which
each error occurs with the PAGE command and then display the page, with the LIST
command:
Continue searching for the error string until there are no more occurrences of it in the
program. For example:
When you have found all the errors in the program and are through with this TAL
listing, delete it with the DEL command and exit Peruse:
Correct the errors in your source file and run TAL again.
The following example shows a TAL compilation with the compiler listing sent to
location $S.#HOLD:
_FIND /**** ERROR/
**** ERROR 27 **** Illegal syntax
_FIND
**** ERROR 54 **** Illegal reference parameter
_PAGE
PAGE: 8 LINE: 12
_LIST *
_FIND
**** ERROR 72 **** Indirection must be supplied
_FIND
_DEL ; EXIT
11> TAL /IN PROG, OUT $S.#LOOK/ TALOBJ
12> PERUSE
PERUSE - T9101D10 - (08JUN92) SYSTEM \WEST
Copyright Tandem Computers Incorporated 1978, 1982, 1983, 1984, 1985, 1986,
1987, 1988, 1989, 1990, 1991
JOB BATCH STATE PAGES COPIES PRI HOLD LOCATION REPORT
136 READY 130 1 4 #HOLD TAL USER