Introduction to NonStop Operations Management

Change and Configuration Management
Introduction to NonStop Operations Management–125507
7-6
Performing Subsystem Changes
•
SCF allows you to add and change configurations for many (not all) device
types while the system is running. SCF also reduces the need to preconfigure
software changes.
Performing Subsystem Changes
The Tandem environment consists of application and communications subsystems. The
application subsystems enable you to develop and run high-performance, high-volume,
and highly available OLTP applications. The application subsystems that make up the
Tandem application environment include NonStop Transaction Services/MP (TS/MP),
NonStop SQL/MP, and NonStop Transaction Manager/MP (TM/MP). The
communications subsystems provides users with access to a set of communications
services.
Follow these guidelines when changing or creating an application or communication
subsystem:
•
Before starting the change process, create a list of all parameters that will be
changed. Keep this list in case questions arise in the future.
•
You might have to shut down the applications that are using the products before
reconfiguring the products. Refer to the Availability Guide for Change Management
for a description of application changes that can be performed online.
•
Use each product’s command interpreter to reconfigure the application. For
example, use TMFCOM to reconfigure NonStop TM/MP.
•
To reconfigure data communications lines and devices, you can use DSM/SCM or
the Subsystem Control Facility (SCF), depending on the device or line type.
Performing Software Changes
A software change can include installing software purchased from another vendor or
installing software developed in-house. To protect system security, develop procedures
to prevent the installation of any software except the legitimate software. The staff
should answer the following questions before installing new software:
•
Has the software come through ordinary channels?
•
Is the software documented in the way that is standard for the organization?
•
If the software is an update, does it update the particular version of the software you
already have?
•
Do the installation instructions require you to expose your system security?
Exercise similar care when dealing with software created by your system programmers
or application programmers. Review their software carefully, especially if it performs
actions on behalf of other users or uses special privileges. Consider including the
following questions in staff check lists:
•
Has the software been subjected to standard quality-assurance and offline testing?
•
Has the software been reviewed and approved by management?
•
Does the software require privileges for an obscure or unnecessary function?