SNAX Creator-2 Configuration and Control Manual

Distributed Systems Management
Introduction to SCF for SNAX Creator-2
117143 SNAX Creator-2 Configuration and Control Manual 1–3
SCF Product Module for
SNAX Creator-2
The SCF product module for SNAX Creator-2 runs as a separate process started by
SCF. The object-code file for this product module, shown in the SCF LISTPM
command, is named ZCRESCF and has a file code of 100. This file normally resides in
the $SYSTEM.SYSTEM subvolume.
Because this product module is a separate process, the “execute” attribute for its object
file should be secured for network access. However, the “read,” “write,” and “purge”
security attributes are not significant. Therefore, the ZCRESCF file should be secured
“xxNx” where “x” can be any security level.
System Environment SNAX Creator-2 is supported only on D-series Tandem NonStop systems.
To run SNAX Creator-2, you also need to install the Tandem Transaction
Management Facility (TMF) on your system, and the disk that holds the configuration
database must be audited.
Distributed Systems
Management
This subsection provides a general overview of Tandem’s Distributed Systems
Management (DSM) environment and the role of SCF and the Subsystem Control
Point (SCP). If you are already familiar with DSM and SCF, you can proceed to
Section 2, “Startup and Configuration of SNAX Creator-2.” If you need more
information than is provided here, refer to the manual Introduction to Distributed
Systems Management (DSM).
DSM is a set of products that supports integrated management of system and network
resources and operations. DSM architecture consists of the following:
Operations environment, in which applications and tools are available for you to
perform operations tasks
Subsystem environment, in which subsystems (such as SNAX Creator-2) and the
objects they control are managed
Management services, which are software products that support the
programmatic interface between the two environments
SCF is a DSM management tool in the operations environment. It is a unified
command interface that simplifies the tasks of configuring, controlling, and collecting
information about Tandem subsystems.
When you use SCF, you can choose either to let a person perform an action or to
automate that action; these two options are represented by the terminal and the
command (OBEY) file, respectively, shown in Figure 1-2. SCF returns display and
error-message output to a terminal and/or to a log file.
Subsystem Control Point
(SCP)
As shown in Figure 1-2, SCF communicates with subsystems through a process called
the Subsystem Control Point (SCP). SCP is an intermediate process that receives
commands from SCF and distributes them to subsystems. The default SCP process
name is $ZNET.
Although SCP and SCF can reside on separate Tandem nodes, SCP and
SNAX Creator-2 must reside on the same Tandem node.