SCAN - subsystem for inspecting remote batch output.

SCAN verb summary:

F or FIND[/<string>/][;n] P or PRINT[/<string>/][;n|;*]
S or SPACE [n]            B or BACK [n]
LINE [n]                  E or ERROR[n]
U or UNDE                 FLAG [x]
LOAD                      C or CODE abcde
EDIT                      DONE
LIST [n]                  REM [text]
BATCH                     BYE


SCAN allows the selective printing of the contents of BCD files or the output of a report under JOUT. One can scan a file by typing "scan filename" at command level or one can scan a report from a batch job by replying "scan rc" to JOUT's "FUNCTION?" prompt. "rc" is a two-digit report code or "$$".

SCAN responds with the question "FORM?". Possible replies include

FORT - for Fortran compilations
GMAP - for GMAP assemblies
LOAD - for loader output
COBOL - for Cobol compilations
USER - for all others
DUMP - same as USER, but no CODE prompt

For the answers GMAP, LOAD, COBOL and FORT, SCAN responds with the number of errors that occurred. For the answer USER, SCAN responds with the question "CODE?". The normal answer to this is a carriage return; if any characters are typed in, subsequent FIND and PRINT commands will ignore any lines that do not begin with these characters. Any characters typed are referred to as the line code.

The next question that SCAN asks is "EDIT?". You may respond YES to get multiple-blank suppression or NO for printing multiple blanks as is. A null response is the same as a NO response.

SCAN should then prompt with a question mark, at which point you may enter any of the following SCAN verbs:

F or FIND[/<string>/][;N]
The slash (/) represents any desired delimiter chosen by the user. The string is a pattern of characters to be searched for. N (any integer) is used to find the Nth occurrence of a string. The FIND verb is used to locate text in a report and to advance the search pointer. It operates only from where the pointer is to the end of the file. Beginning with the line currently pointed to, it moves the search pointer to the nth line containing the literal string (which may be null). If N is not given, 1 is assumed. If no literal string is given, all lines are assumed to match.

The FIND verb accepts all standard Honeywell Text Editor forms. Here are some examples:

find/format/  find next line containing "format"
f/format/     same
find;1        will do nothing
f;2           move the pointer ahead ONE line
find/x/;4     find the 4th line with an "x" in it
P or PRINT[/<string>/][;N|;*]
N is the number of lines to print. If N is the character string "all", then all lines from the current line to the end are printed. If the string "*" is used, all lines containing a string matching the <string> will be printed. If no arguments are given, only the current line is printed.

PRINT allows you to inspect the next N lines of text in a report, or the next N lines that match a specified character string. The search pointer does not move. Lines are printed with a scan line number that can be used with the LINE verb.

The PRINT verb accepts all standard Honeywell Text Editor forms. Here are some examples:

S or SPACE [N]
This spaces the pointer ahead N lines. If N is not specified, the pointer will advance one line. If you attempt to position the file beyond its end, the file will be positioned at the beginning and a warning message will be issued at the terminal (EOF).
B or BACK [N]
This spaces the pointer back N lines. If N is not given, the pointer is moved back to line 1. Here are some examples:
b             return to top of report
back 1        back up one line
b 25          back up 25 lines
As each line is listed, an automatically generated line number will be typed with it. The LINE verb repositions the pointer to the specified line number N. (The line number used need not have been printed prior to being referred to.)
E or ERROR [N]
This requests a list of the next N error printouts of the form corresponding to the output format in question. In USER mode, you get .FXEM error messages (Fortran chicken tracks). The absence of N implies all such messages.
This command (no argument) is used to list all undefined symbols encountered while scanning GMAP assemblies.
This lists all lines of a GMAP assembly having the error flag specified by X (X equals A, U, M, O, etc). The absence of a specific error tag implies that the user wishes a list of all flagged instructions.
This prints out an abbreviated load map. Only primary SYMDEFs are listed, and library routines are omitted.
C or CODE abcde
This is used with the USER format to change the line code. The argument "abcde" is a one to five character code of BCD characters. A null argument "turns off" line codes, i.e. all line codes are accepted until the CODE verb is used to resume with a valid line code.
This returns you to the "EDIT?" level.
This gets you out of SCAN and back to what you were doing before.
LIST is synonymous with PRINT in all respects.
REM [text]
The REM verb provides a means of placing a remarks line on the terminal session log, if it is being taken on a hardcopy terminal.
WARNING: at Waterloo, the DRL SPAWN system call used by the batch verb has been made privileged. Unless you are a privileged user, you will get blown to the previous level if you try to use it. Also, BATCH has no effect if you called SCAN from JOUT.

The BATCH verb asks STATION CODE? The user replies "ab" or simply a carriage return, where "ab" is the station code of a remote-batch terminal. At Waterloo, you must type carriage return.

The system then asks, "$IDENT?", to which you reply with the variable field of your batch $IDENT card (e.g. USER1$USER1,BANNER).

The system then asks, "$USERID?", to which you reply with the variable field of your $USERID card (e.g. USER1$USER1).

The BATCH verb initiates a Bulk Media Conversion (BMC) job which will transfer the entire contents of the file to remote printer "ab". If the station-code reply is null, the output will be printed at the central site.

Needless to say, there are more convenient ways to get a listing (at Waterloo).

This terminates the user's current session with TSS.

Copyright © 1996, Thinkage Ltd.