SNAX/HLS Configuration and Control Manual

Reporting Events
Operating SNAX/HLS
104705 Tandem Computers Incorporated 5–11
Values Used in the
Examples
In both Example 1 and Example 2, the following values result:
ABEND^ON^ERROR (see reverse of DEBUGONERROR)
BACKUP^CPU (see BACKUPCPU)
DATA^SEG^SIZE (see DATAPAGES)
BACKUP^DEBUG (see BACKUPDEBUG)
MAX^LUS 40
MAX^POCB 80
INITIAL^TRACE 0
COLLECTOR $0
DATAPAGES dynamic
BACKUPCPU 4
BACKUPDEBUG OFF
DEBUGONERROR OFF
SWAPVOL $TEXAS
Log file none
RDT file $BIGD.DALLAS.RDTDATA
Messages file $SYSTEM.SNAXHLS.HLSMSGS
Note that the value of 80 for the MAX^POCB parameter is augmented by SNAX/HLS
to allow for SPI opens. The MAX^POCB parameter represents the number of opens
that SNAX/HLS can support for session activity. The total number of opens
supported, including SPI, is MAX^POCB plus 16.
Note The value of MAX^POCB is subject to change from release to release, or IPM to IPM.
Reporting Events SNAX/HLS reports events in two distinct ways:
LOG file—a textual output
EMS collector—a tokenized output
The two facilities can be independently configured. In addition, the installation can
select any combination of output media for individual events through the HLSMSGS
file. (See Section 3, "Installing SNAX/HLS.")