SNAX/HLS Configuration and Control Manual

Starting SNAX/HLS
Operating SNAX/HLS
5–6 104705 Tandem Computers Incorporated
needed, and is frequently a more economical way to run the subsystem. When
operating in this mode, an initial allocation at program startup guarantees enough
storage to start the subsystem. Storage is then extended as needed until one of the
following happens:
The limit set by the Tandem NonStop Kernel on segment size has been reached.
The underlying disk file space is unavailable.
Virtual memory space is exhausted.
Although dynamic allocation might seem advantageous, the danger always exists that
memory cannot be extended after the subsystem has been running for some time.
Therefore, if you believe that you can reasonably predict the amount of memory
needed beforehand, you should probably use this parameter with a real value.
DATAPAGES is an integer in the range 0 through 2,046. The default value is 0, which
means dynamic allocation. Since only an even number of pages is supported, any odd
value is increased by one.
DATA^SEG^SIZE. Is retained for compatibility with earlier versions of SNAX/HLS.
Users are encouraged to use the DATAPAGES parameter.
DEBUGONERROR. Allows control over the action taken by the program when a fatal
error is detected by explicit internal logic tests. If set TRUE, then the DEBUG
procedure is called instead of ABEND. Care should be taken when using this feature,
because a backup does not actually take over until the offending primary really exits.
To enable DEBUGONERROR set TRUE, ON, or YES. To disable this parameter set
FALSE, OFF, or NO. The default value is FALSE.
Note that if DEBUGONERROR is set to FALSE, an ABEND will not create a
SAVEABEND file unless INSPECT SAVEABEND was specified in either a SET
command or the RUN HLSOBJ command.
DEBUG^BACKUP. Is retained for compatibility with earlier versions of SNAX/HLS.
Users are encouraged to use the BACKUPDEBUG parameter.
INITIAL^TRACE. Establishes the tracing enabled on logical units when they are initially
allocated. This tracing, however, takes effect only when the tracing file has been
defined and started. Care should be exercised with the use of this parameter; it can
cause a very large trace file to be generated very quickly. It is most useful when you
are tracking down a problem that is reproducible with a small number of LUs and that
you suspect occurs at BIND time.