GDSX (Extended General Device Support) Manual

Design and Development
Extended General Device Support (GDSX) Manual—529931-001
2-55
DEBUGFLAGS
Debug^error^trap
Debug^error^trap is used to indicate a file error number, which when detected by
TSCODE will cause TSCODE to take one of two actions:
•
Invoke DEBUG, which is done in case uscode^debug^flag is set to 1
•
Send a warning message with the file error number to the home terminal, in case
uscode^debug^flag is set to 0
If you want TSCODE to trap file errors with numbers greater than 255, use the
TRAPERROR configuration parameter with uscode^debug^flag.
Bounds^checking
Bounds^checking is used to indicate whether TSCODE is to do bounds checking on
buffers used during USCODE service routine calls (pseudo and utility procedures). If
this flag is set to 1, TSCODE ensures that all buffers used for I/O are in global or
extended memory, not in the swappable stack. If this flag is set to 0, TSCODE does
not check the location of the buffers used. See also the description of the
CHECK^BUFFER^BOUNDS utility procedure in Section 8, Service Routines.
Auto^trace^flag
Auto^trace^flag is used to turn on the trace facility at startup. With this flag set,
TSCODE traces all significant events.
Uscode^debug^flag
Uscode^debug^flag is used to indicate what action is to be taken if a fault or a user-
specified file error is detected by TSCODE. If this flag is set to 1, and if TSCODE
detects a fault or a file error specified in debug^error^trap (bits 0-7) or in the
TRAPERROR configuration parameter, then TSCODE calls DEBUG. If this flag is set
to 0, and if TSCODE detects a fault or a file error specified in debug^error^trap (bits
0-7) or in the TRAPERROR configuration parameter, then TSCODE sends a message
with the fault number or file error number to the home terminal. USCODE is also free
to use this flag for application-specific purposes.
Backup^debug^flag
Backup^debug^flag is used to indicate that DEBUG is to be called in the backup
process. If this flag is set to 1, DEBUG is called in the backup process immediately
following process creation. You can then set breakpoints as desired. From then on, a
GDSX process enters DEBUG only if an I/O error occurs during a write to the backup
process. The process does not time out on I/O operations to the backup process.