SNAX Creator-2 Configuration and Control Manual

Starting SNAX Creator-2
Startup and Configuration of SNAX Creator-2
2–4 117143 SNAX Creator-2 Configuration and Control Manual
parameters is omitted or specified with no value, output designated for this
collector is suppressed.
The default value is no value, which indicates output designated to these
collectors is suppressed.
CONFIG filename
specifies a file that contains the SNAX Creator-2 configuration database. If the file
does not exist, it is created by SNAX Creator-2.
SNAX Creator-2, as distributed, has no function assigned to these alternate
collectors. Installations may, however, route certain events to alternate collectors,
in which case these parameters are relevant.
If this parameter is not specified, a temporary configuration file is assigned;
however, this temporary file disappears when the SNAX Creator-2 process stops.
If SNAX Creator-2 is running as a process pair and only the primary process stops,
the temporary file (and hence the configuration) is retained.
LOG | LOGFILE } [ { filename | * } ]
specifies the logging file. The logging file is used primarily during development
and should not be used in production environments. Instead, EMS should be used
to collect messages (see the COLLECTOR and COLLECTOR- n startup parameters).
The parameter may be specified in three ways:
Keyword omitted or specified with no value No logging output is produced.
Specified with a valid filename Logging output is sent to this file (see
discussion below on types of files)
Specified with value as asterisk (*) Logging output is sent to the standard
output file (see OUT run option)
If a logging file is specified, it will generally be a terminal, a printer, a spooler or
process file, or a disk file. In production environments, you should avoid
specifying a terminal or printer, because logging output uses waited I/O
operations−terminals and printers are frequently unavailable while in use and, if a
printer becomes not ready, it will impair the SNAX Creator-2 performance.
Generally, the best type of file to use is a spooler or process file (assuming the
process file acts like the spooler). The resultant files can be examined online or
printed after a new log file has been assigned through the LOG or LOGFILE
attribute of the ALTER SUBSYS command.
To use a disk file for logging, the file must be preallocated, and the file type must
be entry-sequenced with a minimum record size of 132. This type of file could be
created with a command such as the following example:
FUP CREATE filename , TYPE E, REC 132, EXT( pri , sec )
where filename identifies the file being created, and pri and sec define the size
of the primary and secondary extents.