DSM/SCM User’s Guide Abstract This guide describes the Distributed Systems Management/Software Configuration Manager (DSM/SCM) and explains how to configure DSM/SCM and use it to manage and configure the software on your system. Product Version DSM/SCM G02 DSM/SCM H02 Supported Release Version Updates (RVUs) This guide supports J06.03 and all subsequent J-series RVUs, H06.
Document History Part Number Product Version Published 529846-008 DSM/SCM G02 (ABU)/H02 February 2007 529846-009 DSM/SCM G02 and H02 May 2008 529846-010 DSM/SCM G02 and H02 August 2009 529846-011 DSM/SCM G02 and H02 February 2011 529846-012 DSM/SCM G02 and H02 September 2011 529846-013 DSM/SCM G02 and H02 September 2012 529846-014 DSM/SCM G02 and H02 June 2014
Legal Notices Copyright 2007, 2014 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
DSM/SCM User’s Guide Glossary Index Examples Figures Legal Notices What’s New in This Manual xv Manual Information xv New and Changed Information About This Guide xix DSM/SCM xix Who Should Use This Guide What’s in This Guide xx Notation Conventions xxiv xv xix Part I. DSM/SCM Overview 1.
3. Hardware and Software Requirements Contents Using the DSM/SCM Interfaces 2-4 Planner Interface 2-4 Maintenance Interfaces 2-6 Target Interface 2-11 Using Tools for DSM/SCM Procedures 2-15 ZPHIRNM Tool 2-15 INITENV Tool 2-15 CLEANOSS Tool 2-17 SPRCHECK Tool 2-17 CLONE Utility 2-17 Using Online Help 2-18 Help for the Graphical User Interfaces 2-18 3.
5. Configuring DSM/SCM Contents Task 2.4: Run SETUP.EXE 4-8 Task 3: Planning DSM/SCM Users and Security 4-9 Guidelines for Assigning DSM/SCM Security Settings Database Administrator Tasks 4-13 Planner Tasks 4-14 Operator Tasks 4-16 4-10 5.
7. Receiving and Managing Software Inputs Contents 7. Receiving and Managing Software Inputs Preparing to Receive Software 7-2 Receiving Software Into the Archive 7-3 Specifying the Location of the Software Input Source Scheduling a Time to Run a Request 7-7 Checking the Status of the Request 7-8 Managing Software Inputs 7-9 Changing the Software Input Description 7-9 Limiting the Software Inputs to Display 7-10 Managing Software Input Groups or Product Groups 7-6 7-11 8.
10. Activating New Software on a Target System Contents File Locations 9-3 Creating a Configuration Revision 9-4 Preparing for a Build and Apply Request 9-4 1. Check If Additional Disk Space Is Required 9-5 2. Check That the Spooler Is Active 9-5 3. Collect the Information Needed for the Build 9-5 4. Specify PARAMs as Needed 9-6 5.
13. Troubleshooting Contents Stopping the System by Halting the Processors Loading the System 12-3 Running PATHCOLD 12-4 12-3 Part IV. Troubleshooting and Recovery Procedures 13.
15.
16. Managing Requests Contents Part V. Supplemental Procedures 16. Managing Requests Submitting a Request 16-2 Types of DSM/SCM Requests 16-2 Scheduling a Request 16-2 Checking Requests 16-3 Displaying the Request Window 16-3 Restricting the Requests Displayed 16-4 Checking the Status of a Request 16-4 Restarting a Request 16-7 Canceling a Request 16-8 Deleting a Request (ZPHIHMI or ZPHITMI) 16-8 17.
Contents 19.
20. Installation of Web Interfaces (H-Series and JSeries Only) Contents Creating a Clone Group Software Configuration 19-5 Building and Applying a Clone Group Configuration Revision 19-5 Renaming Product Files for a Clone Group 19-6 Creating a Noncloning Configuration on a Master or Clone 19-7 Removing a System From a Clone Group 19-8 Removing a Master From a Clone Group 19-8 Removing a Clone From a Clone Group 19-8 20.
D. Required Processes and Files Contents Task 2: Open or Create an A0CINFO File C-5 Task 3: Specifying Product or File Information C-6 Specifying Product Attributes C-6 Specifying Product Dependencies C-8 Specifying File Information C-9 Task 4: Log Off C-16 D.
Tables Contents Figures (continued) Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 4-1. Figure 4-2. Figure 4-3. Figure 4-4. Figure 8-1. Figure 8-2. Figure 9-1. Figure 15-1. Figure 16-1. Figure 17-1. Figure 19-1. Figure A-1. Figure A-2. Figure A-3.
Contents DSM/SCM User’s Guide — 529846-014 xiii
What’s New in This Manual Manual Information DSM/SCM User’s Guide Abstract This guide describes the Distributed Systems Management/Software Configuration Manager (DSM/SCM) and explains how to configure DSM/SCM and use it to manage and configure the software on your system. Product Version DSM/SCM G02 DSM/SCM H02 Supported Release Version Updates (RVUs) This guide supports J06.03 and all subsequent J-series RVUs, H06.
Changes to the 529846-013 manual: What’s New in This Manual Changes to the 529846-013 manual: Added a note in the section, Who Should Use This Guide, on page -xix. Changes to the 529846-012 manual: Added a note under the Loading the System section on page 12-3. Added Enabling Object Manager Tracing heading under the Enabling Traces section on page 14-5. Added Disabling Object Manager Tracing heading under the Disabling Traces section on page 14-6.
Changes to the H06.09 Manual What’s New in This Manual Added a step in Task 1: Changing Default Settings Using INITENV on page 5-3. Added a checkpoint in the table Changing Default Settings Checklist on page 5-4. Added an interface and its function in the table Changing DSM/SCM Default Parameters on page 5-15. Added a checkpoint in the table Reinitialization Checklist on page 5-31. Removed the text “port” from Starting the Application on page 20-2.
Changes to the H06.
About This Guide This guide provides task-oriented instructions for using the DSM/SCM interfaces to perform the activities associated with installing and managing software revisions. This guide documents DSM/SCM T6031G02 for G-series RVUs and T6031H02 for Hseries and J-series RVUs. DSM/SCM The Distributed Systems Management/Software Configuration Manager (DSM/SCM) is a tool for managing and configuring software installation on distributed target systems.
Who Should Use This Guide About This Guide Note. The DSM/SCM User’s Guide is applicable if you are using DSM/SCM Planner Interface. The go forward solution for NonStop software management is NonStop Software Essentials, which replaces the DSM/SCM Planner Interface in addition to certain Host Maintenance Interface functions. NonStop Software Essentials works with DSM/SCM server, providing a web-based interface that is more secure, easier to use, and overcomes other shortcomings of DSM/SCM.
What’s in This Guide About This Guide What’s in This Guide Table i. Summary of Contents (page 1 of 3) Section Title This section . . . PART I DSM/SCM Overview 1 Introduction to DSM/SCM Provides an overview of the functions and capabilities of DSM/SCM and defines the terms and concepts needed to understand DSM/SCM. 2 DSM/SCM Interfaces and Tools Provides an overview of the DSM/SCM interfaces and tools.
What’s in This Guide About This Guide Table i. Summary of Contents (page 2 of 3) Section Title This section . . . 10 Activating New Software on a Target System Provides an overview of procedures to activate software on a target system. 11 Renaming Product Files Using ZPHIRNM Provides step-by-step procedures for running ZPHIRNM. 12 Loading the System Provides procedure to perform a system load.
What’s in This Guide About This Guide Table i. Summary of Contents (page 3 of 3) Section Title This section . . . C Running CNFGINFO Provides information about using CNFGINFO to create a configuration information file for software. D Appendix D, Required Processes and Files Describes the preconfigured subsystem contents for DSM/SCM. E Appendix E, ASSIGNs and PARAMs Describes how to use ASSIGNs and PARAMs related to DSM/SCM.
Using This Guide About This Guide Using This Guide The sections you should read depend on the tasks you perform using DSM/SCM: If you are...
Notation Conventions About This Guide the Maintenance Interfaces (ZPHIHMI and ZPHITMI), the Target Interface (ZPHITI), and CNFGINFO. The DSM/SCM Messages Manual provides detailed cause, effect, and recovery information for messages that you might encounter while using DSM/SCM. The DSM/SCM Quick Reference Guide provides concise procedures for common DSM/SCM tasks. It is intended only for expert DSM/SCM users.
General Syntax Notation About This Guide [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines.
Notation for Messages About This Guide Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In this example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing.
Change Bar Notation About This Guide horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: proc-name trapped [ in SQL | in SQL file system ] { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Part I.
Part I.
1 Introduction to DSM/SCM The Distributed Systems Management/Software Configuration Manager (DSM/SCM) provides centralized planning, management, and installation of software on distributed (target) NonStop systems.
Major DSM/SCM Features Introduction to DSM/SCM Major DSM/SCM Features DSM/SCM offers many features that enable you to better manage software configuration on your systems, including: Feature Description Centralized control A planner at a central site (host system) can manage software on multiple remote target systems.
Configuring DSM/SCM Introduction to DSM/SCM Configuring DSM/SCM To plan the organization of systems managed by DSM/SCM, see Task 1: Planning the DSM/SCM Environment on page 4-2. For the procedures for configuring or reconfiguring the DSM/SCM environment, see Section 5, Configuring DSM/SCM. DSM/SCM Environment You can use DSM/SCM from a central host system to manage software on distributed target systems. This overview describes concepts you need to understand before you set up the DSM/SCM environment.
DSM/SCM Environment Introduction to DSM/SCM Host System From a host system, use the Planner Interface on the host system to perform these tasks: Transfer software files to target systems Receive software into the DSM/SCM environment Archive the software Plan and create software revisions Package and initiate the placement of software on distributed target systems One host system can centrally control the configurations of many target systems or several host systems can manage different system
DSM/SCM Archive Introduction to DSM/SCM Logical Targets A logical target is a specific software configuration on a target system. Every system, including the host system, contains at least one logical target. The host activates and manages its own software as it does for any of its target systems. To manage different software configurations independently can manage different software configurations independently on a single system, use multiple logical targets.
DSM/SCM Security Introduction to DSM/SCM Target Database Each target database contains information about the files in a logical target, including file names, attributes, and fingerprints (checksum-type file identifiers). The target database for the host system is typically kept on the host system in the same volume as the host database. Target databases should reside on their respective target systems.
Installing and Configuring Software Introduction to DSM/SCM Installing and Configuring Software Use DSM/SCM to install and manage new and revised software products from HP or third-party vendors. HP delivers release version updates (RVUs) on a site update tape (SUT) on one or more tapes. SPRs are usually delivered on a backup tape or through a network connection. Caution. Inputs to the archive must be received as delivered from HP.
Installing and Configuring Software Introduction to DSM/SCM The temporary file naming allows files to be applied while the system is running without interfering with the existing files on the running system. If the system needs to be backed out to the previous revision, ZPHIRNM is run during the Backout process to give the actual file names back to the files from the previous revision.
Managing the SYSnn Subvolumes Introduction to DSM/SCM Managing the SYSnn Subvolumes DSM/SCM creates a new operating system image, if needed during the Build request. For software updates that do not require system generation, you can use the current SYSnn. When system generation is required for an RVU or SPR, you must specify a new SYSnn. However, you should minimize the number of SYSnn subvolumes on each target. DSM/SCM requires only one SYSnn in order to operate.
Comparing DSM/SCM to COPYOSS/PINSTALL/PCleanup Introduction to DSM/SCM Comparing DSM/SCM to COPYOSS/PINSTALL/PCleanup PCleanup removes only old files that OSS products specify to remove. DSM/SCM removes all files that are not still in the configuration. COPYOSS only installs software. DSM/SCM installs and manages the software in parallel with your Guardian products. COPYOSS installs every file every time, overwriting existing files.
2 DSM/SCM Interfaces and Tools This section contains descriptions of the DSM/SCM interfaces and tools and provides information on basic use, logging on and exiting, and using the menu functions (if any) available at startup. The online help in each interface provides detailed technical information for interface commands and functions.
Starting and Stopping DSM/SCM DSM/SCM Interfaces and Tools Starting and Stopping DSM/SCM You start and stop DSM/SCM from an HP Tandem Advanced Command Language (TACL) prompt. The STARTSCM and STOPSCM files are startup and shutdown programs located in the ZDSMSCM subvolume. Normally, you start DSM/SCM only when you need to use it and shut it down when finished. However, you can include commands to run STARTSCM and STOPSCM in your system load and shutdown files.
Stopping DSM/SCM DSM/SCM Interfaces and Tools 3. If a TMF process is not running, start it: Note. For Steps 2 and 3, if you are unsure if TMF or DSM/SCM is running, enter the provided commands. If they are already running, they continue to run unaffected. > TMFCOM START TMF 4. Run STARTSCM: > RUN STARTSCM Stopping DSM/SCM You must stop DSM/SCM before: Running INITENV Moving a DSM/SCM database Running ZPHIRNM To stop DSM/SCM: 1.
Using the DSM/SCM Interfaces DSM/SCM Interfaces and Tools 3. Stop the TMF process: > TMFCOM STOP TMF Using the DSM/SCM Interfaces DSM/SCM includes these interfaces: Planner Interface on page 2-4 Maintenance Interfaces on page 2-6 Target Interface on page 2-11 Planner Interface The Planner Interface is a PC-based graphical user interface to DSM/SCM that communicates with the host system.
Planner Interface DSM/SCM Interfaces and Tools 2. On your PC desktop, select Start>Programs>Dsm_scm>DSMSCM. DSM/SCM displays the Logon dialog box. 3. Enter your host user name and password. (DSM/SCM passwords are casesensitive.) 4. Click OK. DSM/SCM displays the Planner Interface main window (Figure 2-1). You can begin the Planner Interface activities.
Maintenance Interfaces DSM/SCM Interfaces and Tools Below these windows is an area called the parking lot. After submitting a request, you can minimize its status window. The icon for the minimized status window appears in the parking lot. You can restore the status window to check the status of a request at any time during the session. For more information on managing requests, see Section 16, Managing Requests. At the top of the window is the Planner Interface menu bar.
Maintenance Interfaces DSM/SCM Interfaces and Tools The Target Maintenance Interface (ZPHITMI) manages target system databases. Use the ZPHITMI to manage the target database for the logical target on the host system. You can perform operator security maintenance only from the ZPHITMI (and not from the ZPHIHMI). From either Maintenance Interface, you can: Add new target systems to DSM/SCM Manage the DSM/SCM archive, databases, profiles, and target systems.
Maintenance Interfaces DSM/SCM Interfaces and Tools Figure 2-2. Maintenance Interface Logon Screen VST022.vsd 4. On the Logon screen, enter this initial User ID and Password, and press F1. (Maintenance Interface passwords are case-sensitive.) DSM/SCM initializes the Maintenance Interface with all database administration functions set to the user ID you established with INITENV. Therefore, that ID must be the first ID to log on to the Maintenance Interface.
Maintenance Interfaces DSM/SCM Interfaces and Tools Figure 2-3. Maintenance Interface Target System Main Menu VST023.vsd Navigating the Maintenance Interface The Maintenance Interface screen consists of three main areas: The upper area displays data fields in which you enter information. Use the tab key to move from field to field. The middle area provides instructions for performing tasks from the screen. The lower area shows the function keys that are active on the screen.
Maintenance Interfaces DSM/SCM Interfaces and Tools Figure 2-4. Maintenance Interface Screen Example Data Entry Instructions Function Keys Advisory Messages VST024.vsd To use the Maintenance Interface: 1. Start the Maintenance Interface. DSM/SCM displays the Logon screen. 2. Log on to the Maintenance Interface. DSM/SCM displays the main menu. 3. From the main menu, select a task, then press F1. DSM/SCM displays the requested screen. 4. Perform maintenance tasks using the data fields in the interface.
Target Interface DSM/SCM Interfaces and Tools Target Interface The Target Interface (ZPHITI) is a menu-driven, block-mode interface to DSM/SCM that runs on each target system. ZPHITI does not require a PC. It can run on any NonStop character-based terminal or terminal emulator that supports block-mode display. You can use ZPHITI on a target system to: Review operator instructions sent with the activation package. Apply software from an activation package to the target system.
Target Interface DSM/SCM Interfaces and Tools Figure 2-5. ZPHITI Logon Screen VST055.vsd After a successful logon, DSM/SCM displays the ZPHITI Main Menu (Figure 2-6). To begin all ZPHITI activities from the main menu: 1. Entering a number in the Selection number field. 2. Press F1. To check EMS messages generated by a currently running request, press F4. If no request is being processed, DSM/SCM displays the EMS messages for the last completed request.
Target Interface DSM/SCM Interfaces and Tools Figure 2-6. ZPHITI Main Menu VST026.vsd Navigating the ZPHITI The ZPHITI screen consists of four main areas: The upper area displays data fields in which you enter information. Use the tab key to move from field to field. The second area provides instructions for performing tasks from the screen. The third area provides messages or menu list items. The lower area shows the function keys that are active on the screen.
Target Interface DSM/SCM Interfaces and Tools Figure 2-7. ZPHITI Screen Example Data Entry Instructions Messages Menu or List Items Function Keys Advisory Messages VST027.vsd To use the ZPHITI: 1. Start the ZPHITI. DSM/SCM displays the Logon screen. 2. Log on to the ZPHITI. DSM/SCM displays the main menu. 3. From the main menu, select a task and then press F1. DSM/SCM displays the requested screen. 4. Perform your target tasks using the data fields in the interface.
Using Tools for DSM/SCM Procedures DSM/SCM Interfaces and Tools Using Tools for DSM/SCM Procedures In addition to the DSM/SCM interfaces, you use these tools during certain DSM/SCM procedures. ZPHIRNM Tool Before you can use new software after you apply a new configuration to a target system, you must run ZPHIRNM to activate the software.
INITENV Tool DSM/SCM Interfaces and Tools 3. Run the INITENV tool: > RUN INITENV To use INITENV to change only the host name for a target system: > RUN INITENV CHANGE-HOST new-host new-host is the name of the new host name for the target system. Configuration Verification As its last step, INITENV automatically runs STARTSCM (which is required by VERIFYI), then runs VERIFYI to verify the configuration update.
CLEANOSS Tool DSM/SCM Interfaces and Tools CLEANOSS Tool Use the CLEANOSS tool before your next Apply if INITENV informs you that it is required. If DSM/SCM tries to manage an OSS hierarchy containing old DSM/SCM work files, your next Apply fails. CLEANOSS removes these files. SPRCHECK Tool Use the SPRCHECK command line tool to confirm whether the recommended SPRs for your current configuration are installed on the system.
Using Online Help DSM/SCM Interfaces and Tools Using Online Help The DSM/SCM online help systems supplement the information in this guide by providing detailed technical information about the use of each interface. Help for the Graphical User Interfaces DSM/SCM provides help for a window or dialog box, menu commands, buttons, and data fields. A list of help topics, index of keywords, and glossary are also available. For help on a: You must: Window Select Help>This window. Dialog box Click Help.
DSM/SCM Interfaces and Tools Help for the Graphical User Interfaces display help information for a screen, press F15 while the screen is active. To return to the interface from the help screen, press F16.
DSM/SCM Interfaces and Tools Help for the Graphical User Interfaces DSM/SCM User’s Guide — 529846-014 2 - 20
3 Hardware and Software Requirements This section describes the hardware and software required to run DSM/SCM: Required Hardware on page 3-2 Required Software on page 3-2 DSM/SCM Interaction Between Integrity NonStop and NonStop S-Series Systems on page 3-4 DSM/SCM User’s Guide — 529846-014 3-1
Hardware and Software Requirements Required Hardware Required Hardware All Integrity NonStop systems and NonStop S-series systems include all the memory and disk space required to run DSM/SCM. For DSM/SCM, you need a network connection to: Connect to a host from the Planner Interface (located on the PC). Manage a remote target over an Expand network. You can also use a tape to communicate between the host and the target.
SQL/MP Hardware and Software Requirements SQL/MP DSM/SCM uses an SQL database to manage software. A version of HP NonStop SQL/MP is installed automatically with DSM/SCM.
Hardware and Software Requirements TCP/IP TCP/IP The Planner Interface connects to its host system using TCP/IP. A version of TCP/IP is installed automatically with DSM/SCM. DSM/SCM Interaction Between Integrity NonStop and NonStop S-Series Systems A NonStop S-series host system can be used to manage Integrity NonStop target systems running, if the NonStop S-series system is running: G06.27 or later RVUs G06.21 through G06.
Part II.
Part II.
4 Planning the DSM/SCM System Environment and User Security Before you configure DSM/SCM, you need to plan: Which systems should serve as DSM/SCM host systems or target systems Whether to create multiple logical targets on a system Where to locate the database for each system and the DSM/SCM archive Which DSM/SCM users to designate as planners, operators, or database administrators Topics discussed in this section include: Task 1: Planning the DSM/SCM Environment on page 4-2 Task 2: Insta
Planning the DSM/SCM System Environment and User Security Task 1: Planning the DSM/SCM Environment Task 1: Planning the DSM/SCM Environment You must configure a system managed by DSM/SCM as either a host system or a target system. Each host manages one or more logical targets. At lease one host system is required, and every system must have at least one logical target on it – including the host system. The location of databases can vary based on convenience, network connections, and available disk space.
Multiple Logical Targets Planning the DSM/SCM System Environment and User Security Generally, the host system contains the host database and a target database, and each target system contains a target database. However, you can put the target databases on the host system if it is network connected, or put several target databases on one target. A remote target system is not network connected to the host system.
Planning the DSM/SCM System Environment and User Security System Environment Examples In this example: \SYSA is a host system with one logical target, TARGA. \SYSB is a physical target system with two logical targets: TARGB1, TARGB2. \SYSC is a physical target system with one logical target, TARGC. \SYSD is a physical target system with one logical target, TARGD.
System Environment Examples Planning the DSM/SCM System Environment and User Security Figure 4-2. Typical DSM/SCM Environment User Interface Winsock or RSC connection Host \A system DSM/SCM Archive Host Database Target 1 \A Target Database tape Stand-alone target system uses tape to communicate with host User Interface User Interface Block-mode interface \B Target Database \B system \C system Target 2 Target 3 Block-mode interface \C Target Database VST042.
System Environment Examples Planning the DSM/SCM System Environment and User Security Figure 4-3. Host and Target Databases \SYSA Host $DSMSCM \TARGC Database $DSMSCM Host Database Target 1 \SYSA Database Expand Tape $DSMSCM \TARGB Database \TARGB Target 2 \TARGC Target 3 \TARGD Target 4 $DSMSCM \TARGD Database VST008.
Planning the DSM/SCM System Environment and User Security Task 2: Install the Planner Interface on the PC Task 2: Install the Planner Interface on the PC The Planner Interface installed is installed on system consoles shipped with new NonStop S-series servers and Integrity NonStop servers. To install the Planner Interface on another PC or to install a newer product version, copy the Planner Interface from the SUT to the PC. The Planner Interface runs on Windows 3.
Planning the DSM/SCM System Environment and User Security Task 2.1: Ensure TCPIP and LISTNER Are Installed and Running Task 2.1: Ensure TCPIP and LISTNER Are Installed and Running Check that the TCPIP file and its LISTNER program are installed in the current host system SYSnn subvolume. To learn what SYSnn is running, on the host system: > sysinfo Task 2.2: Transfer DSM/SCM PC Files From the SUT to the PC Load the Planner Interface from the subvolume on the host system where DSM/SCM will be placed: 1.
Planning the DSM/SCM System Environment and User Security Task 3: Planning DSM/SCM Users and Security For more information on software inputs and product groups, see Managing Software Input Groups or Product Groups on page 7-11. 4. Enter the CNFGINFO process name (optional); then click OK. SETUP asks if you will use RSC or Winsock. 5. Select Winsock: a. Click the Winsock button; then click OK. SETUP asks for the full path name of the WINSOCK.DLL file. b.
Planning the DSM/SCM System Environment and User Security Guidelines for Assigning DSM/SCM Security Settings For more information, see Database Administrator Tasks on page 4-13. Training Site Personnel If DSM/SCM users at your site have not previously used the HP NonStop SQL/MP or HP NonStop Transaction Management Facility (TMF) products, they will need training in those areas. For information about courses that HP offers, contact your HP representative.
Planning the DSM/SCM System Environment and User Security Guidelines for Assigning DSM/SCM Security Settings Small Work Environments In small work environments—those where DSM/SCM manages only one or two systems—one person can perform the tasks of the planner, database administrator, and operator. If the planner has time constraints, or if preferable, a separate person can assume the duties of the operator.
Planning the DSM/SCM System Environment and User Security Guidelines for Assigning DSM/SCM Security Settings production systems and six development systems, you can configure two production operators and two development operators. Large Sites With Remote Systems As at large sites with network-connected systems, having one planner helps maintain an overall picture of the configuration planning for the entire work environment, and having one database administrator is efficient.
Planning the DSM/SCM System Environment and User Security Database Administrator Tasks In this example: The assigned roles for the development systems and production systems are distributed identically although they can be different people for each set of systems. One planner is assigned to each host system, \SYSA. One operator is assigned to all local targets, including the logical targets on \TARGB, \TARGC, and the logical target on \SYSA.
Planning the DSM/SCM System Environment and User Security Planner Tasks Activity Definition Maintenance for Systems Perform system profile maintenance. Maintenance for Volumes Specify how DSM/SCM is to use volumes on the system. Maintenance for CM Profile Make changes to configuration manager profiles.
Planning the DSM/SCM System Environment and User Security Planner Tasks Determines the dependency relationships in planned changes. For example, the planner would determine that the product T9545AAA requires including the products T6556AAI and T9544G01 in the new software revision. Builds a configuration revision containing new software for a target system. Resolves discrepancies between target and host file information.
Planning the DSM/SCM System Environment and User Security Activity Definition Export Files Export files. Receive Software Receive software inputs. Maintain Groups Create and maintain groups. Operator Tasks Operator Tasks An operator can perform tasks only on the assigned target systems. An operator primarily uses the ZPHITI and might use ZPHIRNM in certain situations. An operator for a remote system might have more tasks to perform than an operator for a networkconnected system.
5 Configuring DSM/SCM This section describes the initial configuration and initialization of DSM/SCM host and target systems or a subsequent adjustment. DSM/SCM is configured with default values when you receive a new NonStop S-series system or Integrity NonStop system. The first time you use the Planner Interface on a NonStop S-series system or Integrity NonStop system, software is already received into the archive and one target system, DEFAULT, already exists in the Configuration Revisions window.
Configuring a Host or Target System Configuring DSM/SCM Configuring a Host or Target System HP sets up a DEFAULT configuration on NonStop S-series systems and Integrity NonStop systems. Use this procedure to check the default settings. As needed, update the DSM/SCM profiles, user security, and device defaults. Make any changes to the configuration on the DSM/SCM host system and the physical and logical targets on the host system before using DSM/SCM to manage software.
Task 1: Changing Default Settings Using INITENV Configuring DSM/SCM For information on how to change the system name and number: System Manual Integrity NonStop system SCF Reference Manual for the Kernel Subsystem NonStop NS-Series Hardware Installation Guide NonStop S-series system SCF Reference Manual for the Kernel Subsystem NonStop S-Series Hardware Installation and FastPath Guide Checking the Site ID HP assigns the site ID. To identify the site ID for this system: > fup copy $volume.SYSnn.
Task 1: Changing Default Settings Using INITENV Configuring DSM/SCM Change the DSM/SCM hometerm. Change the DSM/SCM server priority. To change the default settings: 1. Make sure that you have a unique system name and number. See Changing the System Name and Number on page 5-2. 2. Log on to your system as the super ID (255,255) or as the DSM/SCM user ID. > logon 255.255 password: 3. Make ZDSMSCM the current subvolume: > VOLUME $volume.ZDSMSCM 4. Check that TMF is running: > TMFCOM START TMF 5.
Task 2: Configure the Host Database Configuring DSM/SCM Table 5-1. Changing Default Settings Checklist (page 2 of 2) ___ What is the host system name for this target system? \host-name This is displayed only if the system is a target system. ___ DSM/SCM user ID. The default DSM/SCM user ID is the super ID (255,255). dsmscm-user-id ___ Hometerm for use by DSM/SCM Pathway servers and other processes. The default is $ZHOME, a virtual terminal that always runs in the paused state.
Configuring DSM/SCM Task 2: Configure the Host Database 4. Designate the archive volume and scratch volumes for this system. See Updating the Volume Usage on page 17-11. 5. Set security for database administrators for this host system. See Setting Security for Database Administrators on page 5-11. 6. Update the Configuration Manager Profile. See Configuration Manager Profile on page 17-2. All target information that you update in the host database must also be updated in the target database.
Task 3: Configure the Target Database Configuring DSM/SCM Task 3: Configure the Target Database Both host systems and target systems contain a target database. Use ZPHITMI to check the defaults for the DSM/SCM target database information and update it as necessary: 1. Configure the target system profile. For more information, see Updating theTarget Profile (Planner Interface) on page 17-6. 2. Designate scratch volumes for this target system.
Setting DSM/SCM Security Configuring DSM/SCM Setting DSM/SCM Security The security settings for planners, database administrators, and operators specify what tasks they can perform.
Setting Security for Planners Configuring DSM/SCM After you run INITENV with the initialization option on a host system, you must use the ZPHIHMI. See Setting Planner Security (ZPHIHMI) on page 5-9. Otherwise, you can use either the Planner Interface or ZPHIHMI to set security for planners. Setting Planner Security (Planner Interface) 1. Log on to the Planner Interface (see Entering the Planner Interface on page 2-4) using the DSM/SCM user ID.
Setting Security for Planners Configuring DSM/SCM : VST061.vsd 3. Select 3 (Security Maintenance); then press F1. DSM/SCM displays the Security Maintenance menu. 4. Select 1 (Planner Security Maintenance); then press F1. DSM/SCM displays the Planner Security Maintenance screen: VST064.vsd 5. Press Shift-F4. DSM/SCM displays a list of all the planners for this host system.
Setting Security for Database Administrators Configuring DSM/SCM To page through the list, use the PgUp and PgDn keys. Press F16 to return to the Planner Security Maintenance screen. 6. To check the security information for a planner, enter the planner’s user ID; then press F2. To check information about the next planner in the list, press F3. 7. Add or change security permissions for a planner: a. Enter the planner’s user ID or alias; then press F2 to check information about the planner. b.
Setting Security for Database Administrators Configuring DSM/SCM c. In the DB Administrator Security Profile dialog box, select the tasks the administrator is permitted to perform. d. Click OK to exit. To check a database administrator’s profile: a. In the DB Administrator List dialog box, double-click a database user ID or alias from the list. b. After you finish checking the database administrator list, close the window. To modify a database administrator’s profile: a.
Setting Security for Operators Configuring DSM/SCM a. Enter the database administrator’s user ID or alias and press F2 to check the user’s permissions. b. To grant a permission, enter Y in its data field. To deny a permission, enter N in its data field. DSM/SCM is usually configured by the initial database administrator. By default, each database administrator has full permission to access the ZPHITMI. To apply restrictions, set the appropriate flags on the Database Administrator Security screen. c.
Setting Security for Operators Configuring DSM/SCM By default, each operator has full permission for ZPHITI access. To apply restrictions, set the appropriate flags on the Operator Security screen. b. When all permissions are set, press Shift-F2 if you are updating an existing operator or F7 if you are adding an operator. To check the security information for an operator, enter the operator’s user ID or alias; then press F2. To check information about the next operator in the list, press F3.
Managing the DSM/SCM Configuration Configuring DSM/SCM Managing the DSM/SCM Configuration Changing DSM/SCM Default Parameters on page 5-15 Managing Logical Targets on page 5-17 Adding a Logical Target on page 5-17 Initializing a Logical Target on page 5-18 Deleting a Logical Target on page 5-21 Creating an Alternate System Disk on page 5-22 Reinitializing DSM/SCM on page 5-30 Changing DSM/SCM Default Parameters You can use the various DSM/SCM interfaces to change the default values.
Changing DSM/SCM Default Parameters Configuring DSM/SCM Table 5-2. Changing DSM/SCM Default Parameters (page 2 of 3) Processor type (TNS, TNSR, TNSE). Planner Interface System Maintenance Profile Whether the target should use a network connection to the host. Planner Interface System Maintenance Profile If Safeguard is required to be running.
Managing Logical Targets Configuring DSM/SCM Table 5-2. Changing DSM/SCM Default Parameters (page 3 of 3) DSM/SCM tasks the operators can perform.
Managing Logical Targets Configuring DSM/SCM You cannot perform an initialization Build/Apply if it was previously performed on any other logical target created on that particular physical target system. Note. If you use multiple logical targets on a system, always run DSM/SCM from the first ZDSMSCM subvolume installed on the target system. To ensure the correct installation files are used, this ZDSMSCM subvolume must also be the one from which INITENV was run. To add a logical target: 1.
Managing Logical Targets Configuring DSM/SCM 3. Select Maintain>Target maintenance>Initialize target system. 4. Click Profile. DSM/SCM Displays the Naming the Target dialog box. 5. From the Naming the Target dialog box: a. Enter a descriptive target name. b. Click OK. DSM/SCM displays the target Information dialog box. 6. From the target Information dialog box, configure the target profile as needed. (DSM/SCM displays the Target Information dialog box. on page 17-6).
Managing Logical Targets Configuring DSM/SCM perform a normal Build/Apply of an RVU, SPR, or other software on any host or target system on which DSM/SCM has been newly configured. 19. From the Build/Apply Request window: a. Select a build request or build, apply, and snapshot request. See Task 2: Indicate a Build/Apply or Build Request on page 9-10. b. Specify a different SYSnn. subvolume. See Task 3: Specify the SYSnn Subvolume on page 9-11. c.
Managing Logical Targets Configuring DSM/SCM Deleting a Logical Target Note. A physical target system must have at least one logical target. Therefore, you cannot delete the last logical target using the Planner Interface. To remove an entire target system, use the System Maintenance option in the Maintenance Interface. If you delete a logical target through the Maintenance Interface, the target still appears in the Configuration Revisions window but has a revision level of 1 and an empty product list.
Creating an Alternate System Disk Configuring DSM/SCM Creating an Alternate System Disk 1. Prepare and rename the volume using the subsystem control facility (SCF). See these manuals: NonStop NS-Series Hardware Installation Guide NonStop S-Series Hardware Installation and Fast Path Guide 2. Run Verify Database from the ZPHITI. See Verifying the Target System Database (ZPHITI) on page 17-18.
Configuring a Backup Host System Configuring DSM/SCM Configuring a Backup Host System Caution.
Configuring a Backup Host System Configuring DSM/SCM Selecting Primary and Backup Systems Selecting which system to use as the primary host for this setup is the same as selecting a host system in any environment. See Task 1: Planning the DSM/SCM Environment on page 4-2. Because your backup host needs to fully perform as the primary if needed, consider the same guidelines in choosing it as for the primary host.
Configuring a Backup Host System Configuring DSM/SCM Location of TCP/IP startup macros Location of DSM/SCM SQL databases (usually same volume as ZDSMSCM subvolume) Location of CONFTEXT file Location of ZDSMSCM subvolume (must be same on both systems) 2. Initialize the primary host system if needed. This is the normal initialization when you configure your host system. You do not need to change anything for this procedure.
Configuring a Backup Host System Configuring DSM/SCM b. Copy the startup files for starting Expand lines, if any, from the primary host to the working subvolume on the backup host. c. Copy the TCP/IP configuration file TCP00 from the $SYSTEM.LAN4PORT subvolume on the primary host to the working subvolume on the backup host. d. Because some of the processes such as Spooler and TACL might be different on the backup host, add them to the copied files.
Configuring a Backup Host System Configuring DSM/SCM 6. Drop the host database manager program file PHIHDBMG: >SQLCI DROP PROGRAM $DSMSCM.XPHIHDB.PHIHDBMG; EXIT; 7. Drop the host database catalog: >SQLCI DROP CATALOG $DSMSCM.XPHIHDB; EXIT; 8. Check that the ADDTDEFS file reflects the proper system: a. Check the system name in the file to see if it lists your backup host or your old primary host. Check ADD DEFINE lines such as: ADD DEFINE =PHITDB, SUBVOL \sysname.$DSMSCM.Xsystem b.
Configuring a Backup Host System Configuring DSM/SCM 2. Rename and renumber the backup host system to the system name and number of the primary host system: a. Check that the primary host system is down. b. On the backup host system: > SCF -> ASSUME SUBSYS $ZZKRN -> ALTER, SYSTEM_NAME\primary-host-name -> ALTER, SYSTEM_NUMBER\primary-host-number -> EXIT 3. Edit the startup file to start necessary processes. 4. Restart the backup host system: a.
Configuring a Backup Host System Configuring DSM/SCM a. Load the backup tape you made from the primary host. b. Restore the backed up files: > RESTORE/OUT $S.#LOG/ $tapedrive-name,*.*.*, open, audited, listall, nounload Because you are not restoring the SQL catalog tables, you receive errors. c. Check the out file for errors other than SQL catalog tables not being restored. 7. Restart the backup host system. See Step 4. 8. Bring up the network.
Reinitializing DSM/SCM Configuring DSM/SCM Check that the Planner Interface is pointing to the CONFTEXT file for the backup host system, not for the original primary host. Purge the ZMP99999 file from $SYSTEM.SYSTEM. The backup host system is successfully converted to serve as the primary host system. Treat it as the primary host system for future DSM/SCM operations. Reinitializing DSM/SCM Reinitializing erases all information in the host database, target database, and archive.
Reinitializing DSM/SCM Configuring DSM/SCM Table 5-3. Reinitialization Checklist (page 1 of 2) ___ Would you like to read the introduction? Yes or No ___ Are you changing or initializing the system? I Choose to reinitialize to: ___ Change a target system to a host system Change the TMF volume or the SQL system catalog volume Initialize after reinstalling DSM/SCM because of an operational error.
Reinitializing DSM/SCM Configuring DSM/SCM Table 5-3. Reinitialization Checklist (page 2 of 2) ___ Compress files? If disk space is limited, enter yes. No The default is to not compress archive files because it improves I/O time as compared to compressing the files. Compressing archive files reduces their size about fifty percent and reduces transmit time to remote systems over Expand if space is more important at your site.
Reinitializing DSM/SCM Configuring DSM/SCM Task 2: Reconfigure the Host Database Only a host system contains a host database. If you reinitialized a target system, proceed to Task 3: Reconfigure the Target Database on page 5-34. Reinitializing a host system removes all the default host and target system information in the host database. You must reconfigure the host database to set the defaults for DSM/SCM operations such as user security, file transfer, and scheduling options.
Reinitializing DSM/SCM Configuring DSM/SCM To change volume usage: ___ Select the volume name to change usage for. ___ Click the Change Usage button. ___ Click OK to submit the changes. ___ Click OK to exit. Task 2.4: Set Host Database Administrator Security ___ Select Maintain>Security Maintainence>DB Administrator List. To modify a database administrator: ___ From the list, select a database user ID or alias. ___ Click the Modify button.
Reinitializing DSM/SCM Configuring DSM/SCM 2. Designate volumes to be used as scratch on this target system. See Updating Target Volume Usage (ZPHITMI and ZPHIHMI) on page 17-12. 3. Add operators and database administrators for this target system. See Setting Security for Target Database Administrators (ZPHITMI) on page 5-12. Task 3: Configure the Target Database on page 5-7 Task 3.1: Update the Target System Profile ___ Run the ZPHITMI: > Volume $DSMSCM.
Reinitializing DSM/SCM Configuring DSM/SCM ___ Enter an operator user ID or alias to add. authorized-DSM-user or alias123 ___ Set the DSM/SCM tasks the operator can perform. All set to yes ___ Add operator. F7 ___ After all operators are added, return to main TMI menu. Shift-F16 Task 3.4: Set Target Database Administrator Security ___ Select Security Maintenance. 3 and press F1 ___ Select Database Administrator Security Maintenance.
Reinitializing DSM/SCM Configuring DSM/SCM HP recommends that you perform an initialization Build/Apply before you perform the full Build/Apply. A full Build/Apply builds a new SYSnn and places the new software in the TSVs. Task 7: Activate the New Software on the Target System After the software is placed in the appropriate TSVs, you need to activate the new software. Run ZPHIRNM to rename the old software files to fabricated names while the new software is renamed to the appropriate real name.
Reinitializing DSM/SCM Configuring DSM/SCM However, a discrepancy might result because an incorrect SPR is in the initial configuration, and the data file is different from the one in the configuration. Even if the correct SPR is copied to the configuration, this file is not sent to the target again until a new version of the file with a different original fingerprint is added to the configuration.
Reinitializing DSM/SCM Configuring DSM/SCM 1. Create a discrepancy report: If you are running an initializing a target: From the Initialize Target System dialog box, click Discrepancies. If you are running a normal build/apply: a. From the Planner Interface, select Requests>Prepare Reports. b. Click Report request. DSM/SCM displays the Prepare Report Request dialog box. For more information about generating DSM/SCM reports, see Section 18, Generating DSM/SCM Reports. 2.
Reinitializing DSM/SCM Configuring DSM/SCM Resolving Discrepancies Resolve the discrepancies. 1. Change the product list so that it matches the software on the target system. Include SPRs and other software you have installed on the target system. (Any software you add to the list must have already been received into the archive.) 2. Rerun the discrepancy report to see if all discrepancies are either resolved or considered acceptable. 3. Repeat Steps 1 through 3 until no discrepancies remain. 4.
Part III. Software Installation and Management This part of the guide provides an overview of installing and managing software on your system and describes the procedure in detail.
Part III.
6 Managing Software With DSM/SCM HP periodically issues new and revised software products. Use DSM/SCM to install, plan, and manage the new software on your local and distributed systems. From your host system, you can control the installation and configuration of the software on all your systems, local or remote, network connected or not.
Managing Software With DSM/SCM Managing Software to Avoid a System Load Managing Software to Avoid a System Load DSM/SCM requires a system load whenever the OSIMAGE changes. However, to avoid system downtime, you can reinitialize DSM/SCM without performing a system load when: For some SPRs, DSM/SCM assumes the OSIMAGE changed when it is unchanged. You modify the CONFTEXT file for comments only. You perform a backout to a previous configuration and use an identical configuration for a Build/Apply.
Creating a Software Revision Managing Software With DSM/SCM Creating a Software Revision A software revision is a list of products in the archive that updates the system’s software configuration. Use the Planner Interface to create a software revision: Check the product softdocs and release documents to determine if any conflicts might arise. The softdocs describe new features, corrected problems, remaining known problems, dependencies on other software, and other product information.
Managing Software With DSM/SCM Building and Applying the New Configuration Revision Building and Applying the New Configuration Revision The planner builds a configuration on the host system. DSM/SCM builds a new configuration revision to: Transfer the products listed in a software revision from the archive to the target system. Merge the distribution files into executable or usable formats. Create the activation package.
Transferring and Receiving the Snapshot Into the Host Database Managing Software With DSM/SCM A Build/Apply, and the activation package location is set to disk, the file transfer, apply, and snapshot are executed automatically after the Build finishes. Host/Target Connection Activation Package Transfer to the Target System Apply Request Initiator Expand network Across the Expand network. If the connection is not fast, tape transfer might be faster.
Managing Software With DSM/SCM Activating the New Software on the Target System temporary file names so they do not interfere with any existing versions of the software. This helps minimize downtime for your applications. Activating the new software on the target system. This can involve a variety of steps including updating firmware, performing a system load, and starting and stopping applications at certain times.
7 Receiving and Managing Software Inputs This section describes how to receive the software (input) into the DSM/SCM archive. A software input consists of one or more products from HP, customer, or third-party software on either disk or tape. When software is received, the files from each product are stored in the archive, and the file attributes are stored in the database.
Receiving and Managing Software Inputs Preparing to Receive Software Preparing to Receive Software Note. All received software files must have an associated A0CINFO file. HP always includes an A0CINFO file with its software, but third-party software might not. Define Product Attributes for Third-Party Products For a third-party product with no A0CINFO file, you must use the CNFGINFO tool to create one before receiving the product into the DSM/SCM archive.
Receiving and Managing Software Inputs Receiving Software Into the Archive Log On to DSM/SCM 1. Log on to DSM/SCM using the DSM/SCM user ID. For more information, see Starting and Stopping DSM/SCM on page 2-2. 2. On your host PC, start the Planner Interface. 3. Log on to the Planner Interface using the super ID (255, 255) or a planner ID. The Planner Interface displays the Software in Archive and Configuration Revisions windows.
Receiving and Managing Software Inputs Receiving Software Into the Archive 3. From the Software in Archive window, click Receive software. DSM/SCM displays the Receive Software Request dialog box: VST082.vsd 4. From the Receive Software Request window: a. Enter the information as needed. See Table 7-1, Receive Software Request, on page 7-5. b. Click OK.
Receiving and Managing Software Inputs Receiving Software Into the Archive Table 7-1. Receive Software Request Parameter Action Request description Enter a description of the software input. For example: \CHINOOK TARGET1 2000-02-28:15:03 G06.07, YG \host_name targetname date, RVU, planner initials This description appears in the Request Status window whenever you check the status of this request.
Receiving and Managing Software Inputs Specifying the Location of the Software Input Source EMS Events or Status windows), close the window. The Software in Archive window shows the newly received software products. 6. If you are installing third-party products, delete the distribution subvolume because the software it contains is in the archive. After the software has been received into the archive: Manage the software in the archive. See Managing Software Inputs on page 7-9.
Receiving and Managing Software Inputs Scheduling a Time to Run a Request Specifying a Tape Location as the Input Source If the software is on tape: 1. In the Request Source Options dialog box, click Tape drive if it is not already selected. 2. To override the default tape drive, enter the tape drive name in the Tape drive field or select a drive from the scrollable list of host tape drives. 3. If the tape has an external physical label, enter the ID in the Optional external tape ID field.
Receiving and Managing Software Inputs Checking the Status of the Request a. In the Request Scheduling Options dialog box, click Later. b. In the appropriate fields, enter the date and time for the request to start. c. Click OK. To view other options, see Checking Requests on page 16-3. VST084.vsd Checking the Status of the Request 1. Check the status of the request in the status window DSM/SCM displays. If you close the status window, you can reopen it later by selecting Requests> Requests list...
Receiving and Managing Software Inputs Managing Software Inputs The number in quotes is the EMS message number. If you receive an error, see the DSM/SCM Messages Manual for cause, effect, and recovery information. For troubleshooting, see Software Configuration Troubleshooting on page 13-11. 3. After the status display indicates that the request is complete, select Window> Refresh. 4. Close the status window after you finish checking the request status.
Receiving and Managing Software Inputs Limiting the Software Inputs to Display 3. Make changes as needed: To change the software input name, enter a new name in the Software name field. To change the software description, enter up to three lines of text in the Description field. 4. Click OK. Limiting the Software Inputs to Display The list of software inputs in the Software in Archive window might become extensive.
Receiving and Managing Software Inputs Managing Software Input Groups or Product Groups Managing Software Input Groups or Product Groups You can group archived software inputs or products before building a software revision. Grouping lets you work with a single, named entity instead of separately manipulating several inputs or products.
Receiving and Managing Software Inputs Managing Software Input Groups or Product Groups Creating a Product Group To create a new group containing selected products: 1. Display a list of products by doing one of: In the Software in Archive window, double-click an input. In the Software in Archive window, select an input; then select Products>List products.... In the Configurations Revisions window, double-click a revision to open it.
Receiving and Managing Software Inputs Managing Software Input Groups or Product Groups When only certain inputs (such as SPRs) are displayed, some input groups that actually have members might appear empty if they do not contain any of the selected input types, and others might appear to be missing members. You specify the inputs to display from the View Software By dialog box. See Limiting the Software Inputs to Display on page 7-10.
Receiving and Managing Software Inputs Managing Software Input Groups or Product Groups Managing Group Members You can add and remove inputs or products from groups and control how group members are displayed. Displaying and Hiding Members of a Group To list all the members of an input or product group in the Software in Archive window or any other window that lists software inputs or products: 1. Click Show inputs by group or Show products by group. DSM/SCM displays the group names.
Receiving and Managing Software Inputs Managing Software Input Groups or Product Groups Removing Members From a Group You can remove software inputs or products from the group containing them. You can remove the same member from several groups, different members from one group, or different members from several groups: 1. In the Software in Archive window or any window that lists products, click Show inputs by group or Show products by group to toggle it to Show by inputs or Show by products.
Receiving and Managing Software Inputs Managing Software Input Groups or Product Groups DSM/SCM User’s Guide — 529846-014 7 - 16
8 Creating and Managing Software Revisions A software revision is a list of products stored in the archive that together are built into a configuration revision. After you receive all required inputs in the DSM/SCM archive, plan and create a new software revision for the target system.
Creating and Managing Software Revisions Checking Product Information Checking Product Information Before creating a software revision, check that all products you plan to include are compatible with each other and that all requisite SPRs are accounted for.
Creating and Managing Software Revisions Checking for Recommended Software Product Revisions (SPRs) Running SPRCHECK 1. Check that you are in the ZDSMSCM volume: > VOLUME $volume.ZDSMSCM volume is the volume containing the DSM/SCM TSV. 2. Run the SPRCHECK macro: > RUN SPRCHECK [ OUT /out-file/ ] supnote sysh-file out-file is the printer, spooler, or file location to send the SPRCHECK output to. If omitted, SPRCHECK output appears on your screen. supnote is the Support Note for the RVU you are running.
Creating and Managing Software Revisions Checking for Recommended Software Product Revisions (SPRs) When used with newer Support Notes, SPRCHECK output is similar to: $DSMSCM ZDSMSCM 10> run sprcheck sprtest.S0108TXT sysh0001 SPRCHECK v2.3 (2001-11-12) Configuration Name: Configuration Revision: Software Release: Apply Date: Site Id: System Name: Logical Target Name: Prod \NSSD2 DEFAULT 2 G06.15 2001-12-06:02:59:51 000003 \NSSD2 DEFAULT Prod BASE UPDT A. SPRs for SUT-based Products 1.
Creating and Managing Software Revisions Checking for Recommended Software Product Revisions (SPRs) When used with older Support Notes, SPRCHECK output is similar to: $DSMSCM ZDSMSCM 9> run sprcheck sprtest.S9908TXT sysh0001 SPRCHECK v2.3 (2001-11-12) Configuration Name: Configuration Revision: Software Release: Apply Date: Site Id: System Name: Logical Target Name: Prod \NSSD2 DEFAULT 2 G06.15 2001-12-06:02:59:51 000003 \NSSD2 DEFAULT Prod BASE UPDT Section 1.
Creating and Managing Software Revisions Listing Products and Product Files Listing Products and Product Files Check all information provided about the products in existing revisions and in new inputs. You can list: The products in a software input or in a revision The product files in a software input or in a specific product Listing Products in a Software Input To list the products in a software input : 1. From the Software in Archive window, do one of: Double-click a software input name.
Creating and Managing Software Revisions Listing Products and Product Files View Product By Dialog Box You can list products by processor type, product name, or product number. 1. Select View>View products by. DSM/SCM displays the View Products By dialog box. 2. Select the processor type and sort order: To display products by processor type, select TNS for CISC processors, TNS/R for RISC processors, TNS/E for Intel Itanium® processors, or ALL for all processors.
Creating and Managing Software Revisions Checking the Product Version Details VST091.vsd To export files from the product version, select files to export, click Export. See Exporting Files From the Archive on page 17-24. Checking the Product Version Details The version details include the base version of a product in a specific software revision and all SPRs applied to it. To check the version details of a product. 1. Select a product in the software revision. 2. Select Products>List version details.
Creating and Managing Software Revisions Checking the Product Version Details VST092.vsd Product number and base version ID Base release—RVU ID (if the base product was received on a SUT) and the last SPR applied (if any) to the product Base SPR Archive source—Name of the software input on which the base product was received Each SPR applied to the product and the name of the input (archive source) containing the SPR Listing the Files in an SPR From the Version Detail dialog box: 1.
Creating and Managing Software Revisions Checking Softdocs and Release Documents Checking Softdocs and Release Documents Check the product changes and dependencies to learn of any issues that might affect your software configuration. The softdoc for each NonStop product describes new features, corrected problems, and remaining known problems. It also gives the product name and number; the required hardware, firmware, and software; and the names of product manuals.
Creating and Managing Software Revisions Checking Softdocs and Release Documents a. Check the Print formatted output location check box if it is not already checked. b. To print the documents to a location other than the default, enter a different spooler name in the output location field. 4. Checking the Revision History of a Software Configuration on page 8-13 Checking Softdocs for Products Changes To check all the softdocs for products that changed between two configuration revisions: 1.
Creating and Managing Software Revisions Checking Softdocs and Release Documents VST093.vsd 3. By default, all documents are selected. To clear any documents you do not want to print or view, Ctrl-click them. If needed, Ctrl-click the documents again to reselect them. 4. Prepare the release documents for either printing or online viewing: To prepare the release document for viewing online: a. Check the Viewable formatted file subvolume location check box. b.
Creating and Managing Software Revisions Checking the Revision History of a Software Configuration Checking the Release Documents 1. Format the selected documents for printing: 2. Checking the Revision History of a Software Configuration on page 8-13 Viewing the Document Online To view the document online: 1. Select File>View prepared documents. DSM/SCM displays a list of documents prepared for online viewing. 2. Select the release document from the list; then click View.
Creating and Managing Software Revisions Checking the Revision History of a Software Configuration Revision History Window : VST094.vsd 1. From the Revision History window, select a revision. 2. Select Products>List products. DSM/SCM lists the products in the software revision. 3. Click Show revision notes to display the notes describing the revision.
Creating and Managing Software Revisions Creating Software Revisions Creating Software Revisions On the host system, the planner creates a new software revision identifying the products to install on the logical target. 1. From the Configuration Revisions window: a. Select the logical target for which you are creating a new revision. b. Click New software revision to copy the product list from the most recent revision to the new software revision. 2. From the Software in Archive window: a.
Creating and Managing Software Revisions Task 1: Create a New Software Revision Task 1: Create a New Software Revision In most cases, you should create a new software revision based on the most recent revision. However, you can also create a new software revision based on an older revision on the same target system or another target system. NonStop S-series systems and Integrity NonStop systems are shipped with an initial software revision that contains the RVU you ordered.
Creating and Managing Software Revisions Task 1: Create a New Software Revision 6. Click Copy to to copy the products to the new software revision if it is open. Note. When a Gxx SUT that contains both the heap manager products (T8431 and T1269) is copied to the new software revision, the Heap Manager Selection dialog box is displayed. This feature is supported only on systems running G06.29 and later G-series RVUs.
Creating and Managing Software Revisions Task 2: Copy Products to the New Software Revision Task 2: Copy Products to the New Software Revision You can modify the contents of a new software revision by copying products from a software input, revision, or group on any target to the New Software Revision window. DSM/SCM highlights products in the source when you select them.
Creating and Managing Software Revisions Task 2: Copy Products to the New Software Revision Figure 8-1. Non-SUT Products Dialog Box VST510.vsd c. To retain independent products and third-party products from your current configuration in the new revision: Click Select All to include all products. Select one or more products individually. d. Click Continue.
Creating and Managing Software Revisions Task 2: Copy Products to the New Software Revision Figure 8-2. Heap Manager Selection Dialog Box VST002.vsd e. Select the desired heap manager (T8431 or T1269) that must be installed on to the target system. Click Continue to copy the SUT (with the selected heap manager) to the new software revision. Click Cancel to cancel the Copy to operation. Note. The Heap Manager Selection feature is supported only on systems running G06.29 and later G-series RVUs. f.
Creating and Managing Software Revisions Task 3: Check the Product Version Details of the New Revision Task 3: Check the Product Version Details of the New Revision From the New Software Revision window: 1. List the product files. See Listing Products in a Revision on page 8-6 2. Check the product version details (applied SPRs). Checking the Product Version Details on page 8-8.
Creating and Managing Software Revisions Managing Software Revisions Managing Software Revisions Although not part of the normal procedure, you might otherwise need to save, close, cancel, or delete a new software revision, or delete a past software revision. Saving a New Software Revision If you leave the Planner Interface before building and applying the new revision, you must save any changes you make to the new revision.
Modifying the New Revision Creating and Managing Software Revisions Modifying the New Revision You can modify the new software revision by adding or deleting new products or inputs, individually or by group. These changes update that product’s display. SPRs are added to the product. A new base version replaces the product. For example, if you add two SPRs, ADD and ADG, to a software revision originally containing the product PROD1 received on a G05.
Creating and Managing Software Revisions Deleting a New Software Revision Deleting a New Software Revision After you delete a new software revision from DSM/SCM, you cannot recover it. To delete a new software revision: 1. In the Configuration Revisions window, select a configuration revision for which a new software revision exists (indicated by an asterisk [*] next to the configuration name). 2. Select File>Delete revision.DSM/SCM displays a dialog box asking you to continue with or cancel the deletion.
Creating and Managing Software Revisions Sharing Software Revisions VST096.vsd To delete an old software revision: 1. In the Configuration Revisions window, select the logical target containing the software revision to delete. 2. Select File>Show Revision History. DSM/SCM displays the Revision History window. 3. Select the revision to delete. 4. Select File>Delete revision. DSM/SCM displays a dialog box asking you to continue with or cancel the deletion. 5. Click Continue.
Sharing Software Revisions Creating and Managing Software Revisions This Configuration Revisions window shows various configuration revisions for each target: VST112.vsd The asterisk (*) indicates that a new software revision you created was defined for the target and is waiting for you to build it. The @ symbol indicates that a new software revision created by a planner in the same planner group as you was defined for the target but is not built.
Creating and Managing Software Revisions Sharing Software Revisions Adding Members to a Planner Group 1. Select Maintain>Security Maintenance>Planner List.... 2. From the Planner List, select a planner user ID to add to an existing planner group. 3. Select Group>Add member to group.... 4. Scroll through the list of group names and select the one to add a member to. 5. Click OK. Removing Members From a Planner Group 1. Select Maintain>Security Maintenance>Planner List.... 2.
Creating and Managing Software Revisions DSM/SCM User’s Guide — 529846-014 8 - 28 Sharing Software Revisions
9 Building and Applying a New Configuration After creating a new software revision, build a new configuration revision. You create a package containing information about all the products listed in your new software revision and transfer it to the target system where the software is placed during the Apply process.
Building and Applying a New Configuration Build Types Build Types Normal Build/Apply on page 9-2 Initialization Build/Apply on page 9-2 FRABIBAB on page 9-3 Normal Build/Apply In most cases, you perform a normal build and apply. This is required to migrate to a new RVU. Initialization Build/Apply When you initiate the Build/Apply from the Initialize target system dialog box, DSM/SCM displays the Indicate Type of Build window instead of the Build/Apply Request window.
Building and Applying a New Configuration FRABIBAB Build/Apply. You do not need to resolve all discrepancies before accepting them, but you will have a record of the differences in the software configuration in case of problems. Before accepting the discrepancies, you can add SPRs or additional software as needed.
Building and Applying a New Configuration Creating a Configuration Revision Because only changed files are sent in most Apply requests, the number of temporary files is representative of the number of changes made to the TSV in the last Apply. Target Directory Location (TDL) DSM/SCM places packaged OSS files that it manages in a TDL on a logical target. Unlike a TSV, a TDL specifies an absolute path. You cannot control the location of a TDL.
Building and Applying a New Configuration 1. Check If Additional Disk Space Is Required 1. Check If Additional Disk Space Is Required Before performing a Build/Apply, check the amount of additional disk space you might need on the volume for new and changed files.
Building and Applying a New Configuration 4. Specify PARAMs as Needed 4. Specify PARAMs as Needed If needed, you can specify PARAMs before performing the Build/Apply. In most cases, you can use the defaults. See PARAM Summary on page E-6. Using Guardian File Security Instead of Safeguard If Safeguard is running on the target system, you can choose to protect the files in your new configuration with Guardian security instead of Safeguard. See IGNORESAFEGUARD-PROTECTION Param on page E-11.
Building and Applying a New Configuration 5. Assemble the Planner Instructions to the Operator Thus you avoid repeatedly opening and closing the dialog box for each copy and paste. To use Notepad to assemble planner instructions from multiple documents: a. Double-click the document you are copying information from to open it. b. Select the text to be copied; then press Ctrl-C (or right-click and select Copy) to copy it to the clipboard. c.
Building and Applying a New Configuration Task 1: Initiate the Build/Apply Request Task 1: Initiate the Build/Apply Request Typically, you initiate a Build/Apply request as described in Initiating the Normal Build and Apply on page 9-8. However, additional steps are required the first time after you initialize a target system. Initiating the Normal Build and Apply 1. From the New Software Revision window in the Planner Interface, click Build/Apply.
Building and Applying a New Configuration Build/Apply Request Dialog Box DSM/SCM indicates whether system generation and a system load (cold load) are required. However, DSM/SCM is not always able to determine if a new configuration can be applied to a running SYSnn subvolume accurately until after the Apply. For more information, see the DSM/SCM Help. If the changes require a new operating system image, the Build/Apply Request dialog box displays this message.
Building and Applying a New Configuration Task 2: Indicate a Build/Apply or Build Request Task 2: Indicate a Build/Apply or Build Request From the Build/Apply Request dialog box: 1. Enter a description of the software input; for example: \CHINO TARGET1 2000-02-28:15:03 G06.07, YG \host_name targetname date, RVU, planner initials 2. Select either a Build, apply & process snapshot request or a Build request.
Building and Applying a New Configuration Task 3: Specify the SYSnn Subvolume 3. Submit a Receive Snapshot request on the host to receive the snapshot into the host database. Task 3: Specify the SYSnn Subvolume To specify a SYSnn subvolume: 1. Check the current SYSnn subvolume: To use TACL, see Determine the Current SYSnn on page 7-2. To use DSM/SCM: On the Build/Apply Request window, click List SYSnn. DSM/SCM displays a list of the SYSnn subvolumes currently in use.
Building and Applying a New Configuration Task 4: Set the Options for the Build and Apply Request Task 4: Set the Options for the Build and Apply Request Use the defaults for these options or change the values as needed: Setting Target Subvolume Locations on page 9-12 Setting Output Options on page 9-14 Setting System Generation Options on page 9-18 Setting File Placement Options on page 9-19 Setting Target Subvolume Locations Note.
Building and Applying a New Configuration Setting Target Subvolume Locations VST105.vsd 3. Change the target subvolume (TSV) locations as necessary. See Changing the Location of a TSV on page 9-13. 4. If you are not making any changes, click OK. Changing the Location of a TSV Note. Before making any changes, note that: To avoid discrepancies, identify TSV locations correctly during the initialization Build/Apply.
Building and Applying a New Configuration Setting Output Options To change the TSV locations from the TSV Locations dialog box: 1. Select one or more TSV names To remove a volume, click Remove from volume. To place a copy of the TSV on another volume: a. Click Add to volume. b. DSM/SCM displays a list of volumes. From the volumes list, select the volume to add or move the TSVs to, or enter the primary and alternate names of the volume.
Setting Output Options Building and Applying a New Configuration DSM/SCM displays the Output Options dialog box: VST094.vsd 2. Change these output options as needed: Activation Package/Snapshot Location on page 9-15 (tape or disk). Output Location for Target Reports on page 9-17 Target Volume for New Subvolumes on page 9-17. Primary and alternate names of the target system volume where new TSVs are placed when DSM/SCM applies new software. Guardian Default for New Files on page 9-17.
Setting Output Options Building and Applying a New Configuration For host systems and target systems that are connected by a network other than Expand, write the activation package and snapshot to disk when submitting the Apply request. For example: $DSMSCM For host and target systems that are not network-connected, write the activation package to tape. When you select a tape drive, these options become available: The optional External Tape ID (Handwritten) is handwritten on the tape.
Building and Applying a New Configuration Setting Output Options Output Location for Target Reports The subvolume location for reports to be viewed online. When you request a report, you can override the default location you specify here. From the Output Options dialog box, type the name of the volume. For example: $S.#TARG.OUTPUT Target Volume for New Subvolumes New subvolumes created during DSM/SCM processing are placed in the target volume. The default is $SYSTEM.
Building and Applying a New Configuration Setting System Generation Options Setting System Generation Options The target profile provides the default system generation options for all Build/Apply requests. Check the system generation options and change as needed for this Build/Apply. This procedure changes these values for an individual Build/Apply request only. The defaults in the target profile are not changed. To change the system generation options for this Build/Apply: 1.
Building and Applying a New Configuration Setting File Placement Options speed system generation processing. For G-series, H-series, and J-series RVUs, the DEFINE statements are optional in the CONFTEXT file. Specifying a Subvolume for System Generation Work Files By default, the work files are temporary and managed by a system generation program. You can use this option to specify whether system generation work files are temporary or permanent, or managed by a system generation program.
Setting File Placement Options Building and Applying a New Configuration DSM/SCM displays the File Placement Options window: VST102.vsd 2. Select which files to place and where to retrieve the files from: 3. Click OK. DSM/SCM returns you to the Build/Apply Request window. Performing Extra Verification By default, DSM/SCM adopts files with the same EOF and modification time.
Building and Applying a New Configuration Setting File Placement Options Place all files using host files If you select this option, all files are copied. This requires a lot of time and disk space. The Apply and ZPHIRNM take much longer. After the Apply completes, two sets of every file (one for the current configuration, one for the previous) are on the target system, thus taking up more disk space. Only the next Build that does not use this option frees the disk space.
Building and Applying a New Configuration Task 5: Schedule the Request Task 5: Schedule the Request By default, the Build/Apply request runs immediately. To avoid disrupting other system activities if you are installing a SUT, you can schedule the Build to run at night (based on host system time) and the Apply to run immediately after the Build. Available scheduling options are based on the type of request you indicated in Task 2: Indicate a Build/Apply or Build Request on page 9-10.
Building and Applying a New Configuration Task 6: Edit the Instructions Task 6: Edit the Instructions DSM/SCM generates a basic set of instructions for applying new software on the target system. You can edit them to include instructions specific to your software installation.
Building and Applying a New Configuration Task 7: Submit the Request Task 7: Submit the Request DSM/SCM processes the request as scheduled and begins the appropriate processes. Depending on the number of software changes, this could take several hours. For information on managing requests, such as canceling or restarting a request, see Section 16, Managing Requests. For Build/Apply/Snapshot requests, DSM/SCM creates the activation package and places the new software on the system’s subvolumes.
Building and Applying a New Configuration Task 8: Apply Software to the Target System The number in quotes is the EMS message number. For error cause, effect, and recovery information, see the DSM/SCM Messages Manual. For troubleshooting hints, see Software Configuration Troubleshooting on page 13-11. If any OSS products in the configuration being built are not DSM/SCM-enabled, a “Completed Successful” message is generated. 4.
Building and Applying a New Configuration Task 8: Apply Software to the Target System d. At the S/W Apply - Get Operator Instructions screen: 1. Enter the location of the activation package: If the activation package is on tape, mount the tape if it isn’t mounted already, enter the tape drive name in the From field, and press F1. If the activation package is on disk, enter the system, volume, and subvolume location in the From field and press F1.
Building and Applying a New Configuration Task 9: Transfer and Receive the Snapshot Into the Host Database To check current EMS messages related to the request while waiting for it to finish, press F4. Note. To check the status of an Apply as it is processing, you must use the ZPHITI. The Planner Interface can display only the status of host activities. The ZPHITI can display only the status of target activities. This is true for all logical targets, including the logical target on the host system.
Building and Applying a New Configuration Transferring the Snapshot to the Host System Note. For systems not connected using Expand, you can transfer the snapshot before or after you activate the new software, but HP recommends that you do it before. After the snapshot has been received into the host database, you can proceed to Activating New Software on a Target System on page 10-1.
Building and Applying a New Configuration Receiving the Snapshot From Disk or Tape DSM/SCM displays a list of DSM/SCM requests. In this window: a. Select the name of the original Build request and click Status details. DSM/SCM displays the status of the request. b. Click Show EMS events to check any EMS messages generated during the Apply. (See the DSM/SCM Messages Manual.) c. Check the status of the request in the status window DSM/SCM displays. 6.
Building and Applying a New Configuration Receiving the Snapshot From Disk or Tape DSM/SCM User’s Guide — 529846-014 9 - 30
10 Activating New Software on a Target System Activating the new software involves preparing the system for the new software and starting the new software. After an activation package is applied to a target system, you must activate the software before it can be used. Use the target interface (ZPHITI) to see the operator instructions for activating software. The operator instructions included with the activation package vary depending on the software being installed.
Activating New Software on a Target System Summary of Activating the Software Summary of Activating the Software The operator instructions are transferred to the target system in the activation package. Most activities performed outside of DSM/SCM that are mentioned in your operator instructions are not documented in detail here because these procedures can change for different RVUs. For more information, you are referred to other manuals as appropriate. 1.
Activating New Software on a Target System Print the Instructions for Activating the Software Print the Instructions for Activating the Software To print the operator instructions: 1. Log on to the ZPHITI. 2. At the ZPHITI main menu, enter 3 (Perform target activities) in the Selection number field, and press F1. DSM/SCM displays the Target Menu - Select Target screen. 3.
Activating New Software on a Target System Example: Planner Instructions to Operator If only a few files are being changed, stopping only the changed applications minimizes down time. In this case, the planner might specify in the instructions only certain applications to be stopped. To stop all applications before running ZPHIRNM or stopping the system: 1. Stop DSM/SCM: > VOLUME $volume.ZDSMSCM > RUN STOPSCM 2. Stop all other applications. 3. Stop TMF: > TMFCOM STOP TMF 2.
Activating New Software on a Target System Example: Planner Instructions to Operator Run ZPHIRNM to change the temporary names of the new product files to their actual names, as explained in Section 11, Renaming Product Files Using ZPHIRNM. 5. Run merge_whatis if ZPHIRNM indicates it is needed.
Activating New Software on a Target System Example: Planner Instructions to Operator 8. RUN INSTALL^TEMPLATES to update EMS template files. EMS templates format EMS messages. The Run INSTALL^TEMPLATE instruction is generated only on the basis of product files present in the software configuration.
11 Renaming Product Files Using ZPHIRNM When you apply software to a target system, DSM/SCM places the product files in their destination TSVs with temporary file names so the new files do not conflict with the file names of currently running programs on the target system. Before you can use the new software you applied, run ZPHIRNM to rename the files that currently have actual file names. These files are renamed to the fabricated names and become available only in the case of a backout.
Renaming Product Files Using ZPHIRNM Run ZPHIRNM in Preview Mode where [$vol.] SYSnn is the subvolume that you just applied software to or backed out to. Note. If you are using multiple logical targets on a system with alternate system disks, and are performing ZPHIRNM on a SYSnn created after BUILD/APPLY on an alternate logical target system, the ZPHIRNM will skip the execution of ZMODGP script. Otherwise, ZMODGP may change the environment of the current target system.
Prepare to Run ZPHIRNM Renaming Product Files Using ZPHIRNM option is one of: TSV tsv-subvol Specifies a single TSV to be tested in PREVIEW mode. tsv-subvol is an 8-character subvolume name. TDL directory Specifies a single directory to be tested in PREVIEW mode. Only the specified directory is processed. DETAIL-TO-SCREEN or DET or DTS Lists all files that are being renamed to the screen. FROM [$vol.
Run ZPHIRNM Renaming Product Files Using ZPHIRNM running ZPHIRNM.) To avoid any possibility of conflict, stop all applications currently running on the target system until after ZPHIRNM finishes. Note. For some software revisions, you must leave certain applications running, such as TMF or Safeguard. ZPHIRNM in PREVIEW mode displays a message if TMF must be running to rename certain files. 3. Check that you are in the ZDSMSCM subvolume: > VOLUME $vol.
Run ZPHIRNM Renaming Product Files Using ZPHIRNM parameter is given in the operator instructions which is included in the activation package. option is one of: DEFAULTS Suppresses all prompts and uses default values. You cannot run ZPHIRNM interactively with this option set. DETAIL-TO-SCREEN or DET or DTS Lists on screen all files that are being renamed. FROM [$vol.
Renaming Product Files Using ZPHIRNM Error Handling 6. If the activating SYSnn is the running cold load SYSnn, the following note is displayed after ZMODGP and ZPHIRNM run successfully: Note. If the system is not cold loading, start the generic processes manually. If generic processes that ZMODGP added are not started and those altered are stopped (aborted), then check the ZMODGP output. The output must be checked on screen or in log file to identify added or altered generic processes.
12 Loading the System When activating software that required system generation and a new operating system image, you must perform a system load.
Renaming the Managed SYSnn (Optional) Loading the System Renaming the Managed SYSnn (Optional) If you prefer to load your system from the same SYSnn subvolume such as SYS00: You can configure the update on the current SYSnn without problems if the software update does not require system generation. If system generation is required, configuring the update on the current SYSnn would cause the Apply request to stop with errors.
Stopping the System by Halting the Processors Loading the System Stopping the System by Halting the Processors The method you use to halt the processors varies depending on the type of system. For more information, refer to the OSM online help. This example describes halting the processors on a NonStop system: 1. Check that DSM/SCM, all other user applications, TMF, and all other subsystems are stopped, and that the spooler is drained. 2. Log on to OSM Low-Level Link. 3.
Running PATHCOLD Loading the System 3. Re-enter all ALTER commands to the $YPHI PATHMON. 4. Run STARTSCM from the same subvolume to restart DSM/SCM the next time it is needed.
Part IV. Troubleshooting and Recovery Procedures This part of the guide provides troubleshooting information and information for backing out of an update in case of problems. Section 13, Troubleshooting Provides troubleshooting information in case you encounter problems while using DSM/SCM Section 14, Special Troubleshooting and Recovery Procedures Provides special troubleshooting and recovery operations for severe problems.
Part IV.
13 Troubleshooting This section provides helpful hints and troubleshooting information for problems that might arise while you use DSM/SCM. For other helpful information, see Required Processes and Files on page D-1.
Checking History Troubleshooting Checking History When a problem arises, check the revision history and the status of requests to find the last successful activity completed. Checking the Revision History 1. From the Planner Interface, select the software revision you were working on in the Configuration Revisions window. 2. Select File>Show revision history. Review past revisions and their current state. Checking Requests 1.
Checking EMS Messages Not Related to the Current Request Troubleshooting Checking EMS Messages for the Current Request (Planner Interface) 1. Log on to the Planner Interface. 2. Select Requests>Requests list.... 3. To display the EMS Events dialog box, do one of: Select a request name; then select Requests>Show request EMS events.... Select a request name, click Status details...; then click Show EMS events. 4.
Printing EMS Messages Troubleshooting 2. Select Requests>Show other EMS events. DSM/SCM opens the DSM/SCM Server Events dialog box, which displays the EMS events. 3. To update this dialog box with current information, click Refresh. To display EMS Messages not related to the current request from ZPHITI: 1. Log on to the ZPHITI 2. From the Show EMS Messages screen, press F4 (Show nonrequest-related errors). DSM/SCM displays the Show Non-Request-Related Errors screen.
Volume Management Troubleshooting Troubleshooting Volume Management Troubleshooting Alternate System Volume Troubleshooting When you create multiple logical targets, or when you are running out of space on the current $SYSTEM, you can create an alternate system volume for new SYSnn subvolumes. When you create an alternate system volume: $SYSTEM must be the permanent name, not the alternate name, for the alternate volume to be loadable.
Alternate System Volume Troubleshooting Troubleshooting Problem Recovery (page 1 of 2) DSM/SCM stops and issues an EMS message stating that a conflict exists between volume/alternate volume name pairs. Volume and alternate volume name pairs must be unique. (For example, $DATA $SYSTEM and $SYSTEM $DATA are not allowed.
Alternate System Volume Troubleshooting Troubleshooting Problem Recovery (page 2 of 2) SPI Definition, EMS Template and Privileged Declaration files are missing after a BUILD/APPLY is performed. In the DSM/SCM output options dialog box, you cleared or did not select the options under Create Subvolume(s) for. Create a new software revision with the options selected: 1. Log on to the Planner Interface. 2. Create a new software revision. 3.
Database Management Troubleshooting Troubleshooting Database Management Troubleshooting Problem Recovery Performance slows during actions that reference the database. On certain backward migrations, the Database Managers need SQLCOMP run to be compatible with the SQL PVU. If performance slows, the SQL statistics might be out of date for the tables. In either case, run SQLCOMP for the Database Manager. Enter: > VOLUME $volume.ZDSMSCM > RUN UPDATES UPDATES is installed only on the host system.
Network Troubleshooting Troubleshooting Network Troubleshooting Problem Recovery The Build, Apply, Process Snapshot option in the Build/Apply dialog box is not available when you are working on the host system. The Use network connection flag indicates whether to perform Apply requests automatically or write the activation package to tape or disk. An Apply is started from the host but does not start on the target.
DSM/SCM Configuration Troubleshooting Troubleshooting DSM/SCM Configuration Troubleshooting INITENV does not change a site’s existing TMF configuration and does not detect whether the audit trail is big enough. However, the configuration in use might not be adequate. INITENV creates audit trails large enough for 118 megabytes of audit. When applying DSM/SCM to DSM/SCM, always use the original TSV.
Software Configuration Troubleshooting Troubleshooting INITENV then runs STARTSCM. If TCP/IP and its LISTNER process are not running, STARTSCM indicates that you must start TCP/IP and its LISTNER process before using the Planner Interface. Problem Recovery A No Software for Target warning window appears. The site ID in the target profile might not match the site ID on the RVU. A failure occurs in STARTSCM when you try to run DSM/SCM from a TSV other than the original ZDSMSCM TSV. 1.
Migration Troubleshooting Troubleshooting To upgrade to a new RVU, you must select Copy to of the new RVU from the Software in Archive window (not from List Products of the contents of the RVU). Note. If you only select and copy products from the RVU, no indication is sent as to the proper RVU level. When upgrading to a new RVU, you must select one of: The RVU from the Software in Archive window; then click Copy to.
Build/Apply Troubleshooting Troubleshooting Build/Apply Troubleshooting Problem Recovery A Build error occurs indicating unprocessed A7CINFO files. OSS software was received into the Archive with a pre-D46 DSM/SCM PVU, resulting in unprocessed A7CINFO files. Receive the OSS software into the Archive again with the Receive All Files option, using a D46 or later DSM/SCM PVU. An Apply request stops in a restartable state with a message that an expected fingerprint was not found or with an error 179.
Build/Apply Troubleshooting Troubleshooting You might get error 5025 during an Apply if: See the DSM/SCM Messages Manual. Any time a Build completes successfully, system generation was unnecessarily performed: Modifying comments in the CONFTEXT file forces system generation. When the fingerprint of the CONFTEXT file indicates that the file changed but the system generation instructions in the file did not change. For example: Configuration DEFAULT 7 was applied to SYS00.
Build/Apply Troubleshooting Troubleshooting During a Build, an Object Manager error communicating with SWID occurs. The specified CONFTEXT file has either been deleted, renamed, or secured so that DSM/SCM cannot read it. When a Build/Apply dialog box is opened, DSM/SCM runs SWID to determine whether the CONFTEXT file has changed and a system generation is therefore required. This error might also indicate a SWID error such as unresolved externals.
Build/Apply Troubleshooting Troubleshooting When you perform a Build only, without an Apply, including all files and creating the activation package on a disk on the host, an error 43 occurs. Not enough disk space is available on the host disk where you are creating the activation package. When creating an activation package that includes all files, use a disk with at least 1 gigabyte of space. The default for a Build/Apply is to send only changed files.
Discrepancy Troubleshooting Troubleshooting Discrepancy Troubleshooting Problem Recovery (page 1 of 2) TSV Discrepancies The first part of the discrepancy report lists TSVs under the heading DUPLICATE TSV INFO. DSM/SCM assumes that if it finds at least one file in a TSV that is also in the configuration, that TSV is a candidate for management by DSM/SCM. However, if DSM/SCM also finds the TSV on more than one volume, it cannot determine the correct volume to use.
Request Troubleshooting Troubleshooting Problem Recovery (page 2 of 2) The discrepancy report shows many products not found on the system although they are there, or the report shows many products found on the system although they are not there. For the Initialization Build/Apply, you used an RVU other than the RVU actually installed on the target. Use the RVU you installed on the target when you submit an Initialization Build/Apply request. An SPR was not included in the configuration.
Request Troubleshooting Troubleshooting Problem Recovery (page 2 of 2) The Planner Interface does not allow the restart or cancellation of a target activity. To restart or cancel a target activity, you must use the ZPHITI. A snapshot request from the target system stops in a restartable state. You cannot restart it from the ZPHITI. If the Snapshot request appears in the Planner Interface, you can restart it there.
Interface Troubleshooting Troubleshooting Interface Troubleshooting Planner Interface Troubleshooting Problem Recovery Performance of the Planner Interface slows significantly, or a loss of available memory occurs. Exit the Planner Interface and restart it. A general protection fault (GPF) occurs. Exit Windows on the PC and restart it before restarting the Planner Interface. Otherwise, memory corruption might lead to more failures.
Maintenance Interface Troubleshooting Troubleshooting Problem Recovery The New Revision Window or Build/Apply dialog box does not appear. The New Revision window can take a while to appear as the data on the configuration is retrieved and sent to the PC. The Build dialog box also takes several minutes to appear because many activities are going on to get the information that is displayed to the user: 1. SWID is run on CONFTEXT to see if changes imply that a system generation must be done. 2.
ZPHITI Troubleshooting Troubleshooting Problem Recovery (page 2 of 2) A profile is overwritten by a snapshot. The Target maintenance>Modify... item of the Maintain menu entry was used to change the profile values for a logical target, and a snapshot was received from the target before another Build/Apply to that system.
CNFGINFO Troubleshooting Troubleshooting Problem Recovery (page 2 of 2) An Initiate Audit request stops before it finishes. Check any error messages appearing on the screen, and take corrective action. You can restart the audit (press F3) or cancel it (press F6). The Audit function does not seem to be doing anything. The Audit function in the ZPHITI might take a long time because SWID is run on the files for all subvolumes specified. This fingerprinting is time consuming.
Recovery Operations Troubleshooting Recovery Operations Cleaning Target Work Files for OSS if you ran INITENV when OSS was not running, use the CLEANOSS macro when OSS becomes available to remove certain DSM/SCM target work files from the currently running OSS hierarchy. Otherwise, old DSM/SCM target work files remain that will cause your next Apply to fail. Excluding the /G and /E directories, CLEANOSS removes: zzDSMSCM.Managed .dsmscm.ZPHIFI .dsmscm.ZMPccncc .dsmscm.ZFBccncc .dsmscm.
14 Special Troubleshooting and Recovery Procedures This section provides troubleshooting and recovery procedures that should only be used under the direction of HP support personnel.
Special Troubleshooting and Recovery Procedures Running Traces Running Traces Note. The trace function slows DSM/SCM processing and uses significant disk space. It should be enabled only under the direction of HP support personnel. You can start a trace for any DSM/SCM component on the host system or on any target system that is network connected to the host. The Planner and Maintenance Interfaces provide trace functions to trace the execution of their requests.
Enabling Traces Special Troubleshooting and Recovery Procedures Enabling Traces Enabling Component Tracing (Planner Interface) on page 14-3 Enabling Tracing of All Planner Interface Activities (Planner Interface) on page 14-4 Enabling Component Tracing (ZPHIHMI or ZPHITMI) on page 14-4 Enabling Component Tracing (ZPHITI) on page 14-4 Enabling Host Database Manager Tracing on page 14-4 Enabling Object Manager Tracing on page 14-5 Enabling Component Tracing (Planner Interface) 1.
Special Troubleshooting and Recovery Procedures Enabling Traces Enabling Tracing of All Planner Interface Activities (Planner Interface) Select Tandem>Support info>Planner Interface trace. The menu item is selected, and tracing starts. Trace information is written to the file PITRACE.LOG. Enabling Component Tracing (ZPHIHMI or ZPHITMI) 1. On the main menu, enter 99 (Trace) in the Selection Number field; then press F1. DSM/SCM displays the Trace screen. 2. Enter 1 in the Selection Number field. 3.
Special Troubleshooting and Recovery Procedures Disabling Traces Host database managers check for this file each time they start up or receive a request, so the trace file is not created until a host database manager receives a request. Trace files are named ZZDHnnnn and stored in the ZDSMSCM subvolume. Only limited tracing is available for host database managers, mainly to track database queries regarding whether a system generation is required for Build/Apply procedures.
Special Troubleshooting and Recovery Procedures Filtering Traces Disabling Component Tracing (ZPHIHMI or ZPHITMI) 1. On the main menu, enter 99 (Trace) in Selection Number field; then press F1. DSM/SCM displays the Trace screen. 2. Enter 2 in the Selection Number field; then press F1. Trace is disabled. Disabling Component Tracing (ZPHITI) 1. On the main menu, enter 9 (Enable trace) in the Selection number field; then press F1. DSM/SCM displays the Enable Trace screen. 2.
Special Troubleshooting and Recovery Procedures Trace Levels 4. If instructions exist, they are followed. If no instructions exist, the trace for that component is not filtered. Trace Levels You can select from five levels of tracing detail for a DSM/SCM trace. Level 5 contains the most detailed information. Level 1 contains only the high-level tasks (stages) being executed. Levels 2 through 4 successively increase the amount of detail.
Trace Levels Special Troubleshooting and Recovery Procedures All tracing is enabled for the Configuration Builder. (Level 5 is on by default.) All tracing is enabled for the Input Supervisor for any information matching the indicated strings. For the Target Activator, tracing is enabled for levels 1 and 2, and level 1 has a selective requirement of including 210.
Trace Levels Special Troubleshooting and Recovery Procedures Table 14-1.
Trace Levels Special Troubleshooting and Recovery Procedures Table 14-1.
Trace Levels Special Troubleshooting and Recovery Procedures Table 14-1.
Trace Levels Special Troubleshooting and Recovery Procedures Table 14-1.
Trace Levels Special Troubleshooting and Recovery Procedures Table 14-1.
Special Troubleshooting and Recovery Procedures Recovering Installed Products Using SIT2SCM Recovering Installed Products Using SIT2SCM Caution. You cannot use this procedure for Integrity NonStop systems.
Special Troubleshooting and Recovery Procedures Task 2: Start All Processors a. Under External SCSI Controller, enter the appropriate Group, Module, and Slot. b. Under Options, check that the CIIN Disabled box is selected. 8. Click Load. 9. Repeat Steps 4 through 8 for other processors if necessary. Task 2: Start All Processors Start all processors that will execute system resources. These might only be processors 0 and 1, depending on how you distribute system resources.
Task 5: Create Input Files Special Troubleshooting and Recovery Procedures Task 5: Create Input Files Run SIT2SCM to create input files for the RESTORE and FUP utilities. The file for RESTORE restores all files needed for running DSM/SCM and places them in the correct subvolume. The file for FUP licenses and sets the PROGIDs for the files. Mount the SUT on tape drive $TAPE0. > RUN $SYSTEM.SYS00.SIT2SCM $TAPE0 $SYSTEM.subvol.CUSTFILE RESTIN FUPIN subvol is the subvolume that contains the CUSTFILE.
Special Troubleshooting and Recovery Procedures Task 8: Start Required Processes Task 8: Start Required Processes Use SCF to configure and start the QIOMON, ZZLAN, and SCP processes before you can start the 4PORT LAN card and the network: -> ASSUME PROCESS $ZZKRN -> ADD PROCESS #QIOMON, AUTORESTART 10, CPU ALL, DEFAULTVOL $SYSTEM.SYSTEM, HOMETERM $ZHOME, OUTFILE $ZHOME, NAME $ZM, PRIORITY 199, PROGRAM $SYSTEM.SYSTEM.
Special Troubleshooting and Recovery Procedures Task 11: License SQL/MP Files 2. In SCF: -> ASSUME PROCESS $ZTC00 -> ALTER, HOSTNAME "CHINOOK_LAN00.TANDEM.COM" -> ADD SUBNET #SN1, TYPE ETHERNET, IPADDRESS 172.17.22.128, DEVICENAME LAN00 -> ALTER SUBNET #SN1, SUBNETMASK %Hffffff00 -> ALTER SUBNET #LOOP0, IPADDRESS 127.1 -> START SUBNET * -> ADD ROUTE #GW, DESTINATION 0, GATEWAY 172.17.22.1, DESTTYPE BROADCAST -> START ROUTE * -> EXIT 3. From a TACL prompt: > RUN $SYSTEM.SYS00.
Special Troubleshooting and Recovery Procedures Task 13: Create the System Catalog Task 13: Create the System Catalog Use SQLCI to create and initialize the system catalog before you can use DSM/SCM: >> CREATE SYSTEM CATALOG $DSMSCM.SQL; >> INITIALIZE SQL; >> EXIT Task 14: Create a SPLCONF File and Start the Spooler Create a SPLCONF file to start the spooler, which you must start before DSM/SCM can run (you must customize the information in this example for your system): > VOLUME $SYSTEM.
Special Troubleshooting and Recovery Procedures Task 15: Set Up DSM/SCM Profiles and Environment DSM/SCM User’s Guide — 529846-014 14 - 20
15 Backing Out a Revision If problems arise with the current revision of software on a target system, you can submit a DSM/SCM request to return to the previous revision applied to that logical target. DSM/SCM makes the current revision inaccessible, reapplies the previous revision, and displays the instructions for activating the previous revision. The backout only restores the software to the previous revision.
Backing Out If DSM/SCM Is Running Backing Out a Revision Backing Out If DSM/SCM Is Running To back out a revision only if DSM/SCM is correctly running on your system: Task 1: Start DSM/SCM Task 2: Start and Log On to the ZPHITI Task 3: Perform Backout Activities Task 4: Monitor the Backout Process Task 5: Stop All Applications Task 6: Run ZPHIRNM in Preview Mode Task 8: Stop and Load the System Task 9: Start TMF and Your Applications Note. You should not need to fall back to previous firmware versions.
Task 3: Perform Backout Activities Backing Out a Revision Task 3: Perform Backout Activities 1. Enter 3 (Perform target activities) in the Selection number field, and press F1. DSM/SCM displays the Target Menu - Select Target Screen. 2. On the Target Menu - Select Target Screen, enter the number corresponding to the name of the target system, and press F1. 3. On the Target Menu - Select Action screen, enter 2 (Perform backout to S/W) in the Selection number field, and press F1. Note.
Task 4: Monitor the Backout Process Backing Out a Revision The screen is updated with current status information approximately every 15 seconds. While waiting for the request to finish, you can press F4 to view current EMS messages related to the request. If a message appears indicating that the request is awaiting a tape mount, press F4 to view the EMS messages for tape and tape drive information; then mount the tape. DSM/SCM resumes processing. 5.
Task 5: Stop All Applications Backing Out a Revision 6. DSM/SCM displays the Request Activity Summary screen. Monitor the backout processing by watching the timestamp in the upper-right corner of the screen. Select Show EMS events to obtain an update at any time. 7. When the backout is complete, exit the Planner Interface. Task 5: Stop All Applications Before running ZPHIRNM, you must stop all applications, including DSM/SCM and TMF. For more information, refer to Stopping All Applications on page 2-3.
Task 9: Start TMF and Your Applications Backing Out a Revision 2. Load the system. The method you use varies depending on the type of system. For more information, refer to Loading the System on page 12-3. For NonStop S-series systems and Integrity NonStop system, load the system using a saved system configuration. Task 9: Start TMF and Your Applications After you are back to your previous software configuration and system configuration, you can start your applications, including TMF.
After Renaming the SYSnn Backing Out a Revision Task 3: Run ZPHIRNM Running ZPHIRNM now renames the files in the previous revision from their saved file names to their actual file names. Enter this command: > RUN ZPHIRNM [$vol.]SYSnn , FROM [$vol.]SYSnn SYSnn is the same number for both in this command. For example, if you first used DSM/SCM to apply SYS01 to a system running SYS00 (not applied by DSM/SCM), you need to back out to SYS00: > RUN ZPHIRNM [$vol.]SYS01 , FROM [$vol.
After Renaming the SYSnn Backing Out a Revision 2. Run ZPHIRNM on the previous SYSnn (in this example, SYS20). For more information, refer to Run ZPHIRNM on page 11-4. The previous SYSnn is the software configuration that was running before the current software configuration. 3. Rename the current SYSnn (SYS00) and CSSnn (CSS00) to an unused SYSnn (SYS01) and CSSnn (CSS01), respectively. For example: > FUP RENAME $SYSTEM.SYS00.*, $SYSTEM.SYS01.* > FUP RENAME $SYSTEM.CSS00.*, $SYSTEM.CSS01.* 4.
Backing Out to an Older Configuration Backing Out a Revision 5. Perform a system load from the newly renamed working SYSnn (now renamed to SYS00). 6. Start DSM/SCM. 7. Run ZPHITI to perform the backout step (Tasks 2 through 4 of Backing Out If DSM/SCM Is Running on page 15-2) to back out to SYS00.
Removing OSS Management Information From the DSM/SCM Databases Backing Out a Revision You performed a backward migration from T6031ABK or later to pre-D46. In this case, in addition to the new security tables, FALLBACK also removes OSS management information from the DSM/SCM databases. (For details, see Removing OSS Management Information From the DSM/SCM Databases.) The FALLBACK macro is run in the same manner as explained on page 12-2.
Backing Out a Revision Removing OSS Management Information From the DSM/SCM Databases 3. Run the FALLBACK macro immediately after you back out to a pre-D46 PVU but before you run STARTSCM. You need to run the macro separately for the host and target systems, but only for whichever systems have been backed out. For example, if your target system is still running the D46 PVU, do not run the macro on the target system.
Backing Out a Revision Removing OSS Management Information From the DSM/SCM Databases DSM/SCM User’s Guide — 529846-014 15 - 12
Part V.
Part V.
16 Managing Requests This section describes managing requests.
Submitting a Request Managing Requests Submitting a Request To initiate any task in DSM/SCM, submit a request. You initiate requests from dialog boxes in the Planner Interface (Planner Interface) or menu commands in the Target Interface (ZPHITI), from which you set up, schedule, and submit a batch process. You can run multiple requests concurrently and check the status of requests. If you exit DSM/SCM while a request is running, the request continues to run.
Checking Requests Managing Requests 2. Schedule the request. To run the request immediately, by default no action is necessary. To schedule a later time for the request to run, click Later and enter a time and date using the format shown in the date and time fields. Note. The default time is immediately for all requests except the Apply request on systems connected to the host by Expand, where the default is to run immediately after the Build request finishes. 3. Click OK.
Restricting the Requests Displayed Managing Requests Restricting the Requests Displayed To restrict the request list: 1. From the Requests window, select View>View requests for. DSM/SCM displays the View Requests For dialog box, at the top of which is a summary of the choices. 2. Select the check boxes of the request types to be displayed: Request Type Selects...
Checking the Status of a Request Managing Requests 2. To open the Request Status window, use either of these methods: Double-click a request name Check the status details a. Select a request name. b. Click Status details. VST073.vsd The status display includes summary information for each stage of the request. You can minimize request status windows and later restore them for a quick status check. Status for the entire window is updated approximately every 90 seconds.
Checking the Status of a Request Managing Requests The current activity status detail displays the current stage of the active request. 3. Click Show EMS events to check the messages issued by the request: To check additional messages, click Refresh. If necessary, exit the Planner Interface to correct any errors that occurred. Otherwise, click Close to return to the Request Status window.
Restarting a Request Managing Requests These messages indicate that an error occurred, user intervention is required, or both: Message Meaning Awaiting operator tape mount The request resumes when the tape is mounted. Cancel processing stopped in restartable state You canceled the request, but the cancel activity stopped before it could complete restoring DSM/SCM to a consistent state. After taking corrective action, you can restart the cancel.
Canceling a Request Managing Requests 2. To restart the request, select Requests>Restart request.... You do not need to reenter any data required by the request. If the request is stopped in a restartable state, DSM/SCM determines the last stage of the request that completed successfully, cleans up any partial processing of the failed stage, and continues processing at the beginning of the previously failed stage. If the request was cancelled, processing starts over. Note.
Managing Requests Deleting a Request (ZPHIHMI or ZPHITMI) 3. On the main menu, enter 5 (Request Deletion) in the Selection Number field, and press F1. 4. DSM/SCM displays the Request Deletion screen, which lists all deletable requests. 5. To delete one or more requests, enter any character in the Selection field of the requests to delete, and press F6. Side effects might result from deleting a problematic request.
Managing Requests Deleting a Request (ZPHIHMI or ZPHITMI) DSM/SCM User’s Guide — 529846-014 16 - 10
17 Managing DSM/SCM You can perform management tasks in DSM/SCM using the Planner Interface, Maintenance Interface (ZPHIHMI or ZPHITMI), or Target Interface (TI), depending on the task. Whenever possible, use the Planner Interface because of its ease of use. It incorporates most functions of the other interfaces in one application.
Updating DSM/SCM Profile Information Managing DSM/SCM Updating DSM/SCM Profile Information DSM/SCM profiles contain default information that DSM/SCM uses when processing requests. These defaults reduce the amount of information the planner must enter when using DSM/SCM.
Configuration Manager Profile Managing DSM/SCM Table 17-1. Configuration Profile Information Parameter Description Default tape drive Select a tape drive name from the list or enter a tape drive name. Specifying the node name is optional. The default is the host system node. You must specify a drive that is compatible with your SUTs and with the other systems in your network. For example, if a host system uses a cartridge tape drive, its target systems must also use cartridge drives.
System Profile Managing DSM/SCM System Profile Whether you maintain system profiles from the host or target systems depends on whether your site practices centralized or local system management. You can update system profile information from either: The Planner Interface or ZPHIHMI on a host system. After changing a target or system profile on a host system, send the updated information to the target system in an activation package to synchronize the target database.
System Profile Managing DSM/SCM To update the default values, review the system profile information and change as needed. See Table 17-2, System Profile Information, on page 17-5. To delete a system from DSM/SCM, press F6 To view the profile for the next system in the list, press F3. 4. For host systems, press Shift-F4 to list all the target systems managed by DSM/SCM. Use PgUp and PgDn to page through the list. 5. Press Shift-F2 to enter any changes. 6. Press F16 to return to the main menu.
Target Profile Managing DSM/SCM Target Profile Updating theTarget Profile (Planner Interface) To update the profile information for a logical target: 1. Log on to the Planner Interface. 2. From the Configuration Revisions window, select the target configuration. For a new target, the name has the form: \system_name DEFAULT 3. Select Maintain>Target maintenance> To add system profile information, select Add.
Target Profile Managing DSM/SCM 7. When you have finished making all changes, click OK in the Target Information dialog box to return to the Configuration Revisions window. 8. After changing a target profile on a host system, send the updated information to the target system in an activation package to synchronize the target database. Setting the Target Output Defaults After you run INITENV with the initialize option, you must specify the output values.
Target Profile Managing DSM/SCM Table 17-3. Output Defaults (page 2 of 2) Parameter Description Target volume for new subvolumes The volume in the logical target where new subvolumes created during DSM/SCM processing are placed. The default is $SYSTEM. Guardian defaults for new files Include in activation package The DSM/SCM user ID is the default owner for all new files on the logical target. Files that replace existing files assume the same ownership as the old file.
Target Profile Managing DSM/SCM Setting the Target System Generation Defaults After you run INITENV with the initialize option, you must specify the output values. Otherwise, you can review the defaults and change as necessary. 1. From the Target Information dialog box, click SYSGEN. DSM/SCM displays the SYSGEN Defaults dialog box: VST611.vsd 2. From the SYSGEN Defaults dialog box: a. Enter values in the data fields as needed (Table 17-4, System Generation Information, on page 17-10). b.
Target Profile Managing DSM/SCM Table 17-4. System Generation Information Parameter Description CONFTEXT file name The default location where the configuration (CONFTEXT) file is placed during a Build. The default is $SYSTEM.SYS00.CONFTEXT. For example: $SYSTEM.subvolume.CONFTEXT Expand CONFTEXT DEFINE statements For G-series, H-series, and J-series RVUs, the DEFINE statements are optional in the CONFTEXT file. DEFINE statements set up string variables. The default is to not expand them.
Managing Volumes Used by DSM/SCM Managing DSM/SCM Managing Volumes Used by DSM/SCM To address space or organizational issues on your system, you can manage the volumes used by DSM/SCM on your system: Procedure Page Updating the Volume Usage 17-11 Moving the ZDSMSCM Subvolume to Another Volume 17-13 Renaming a Volume Managed by DSM/SCM 17-14 Deleting a SYSnn Subvolume 17-15 For information about the preinstalled DSM/SCM configuration, see Required Processes and Files on page D-1, which specifies
Updating the Volume Usage Managing DSM/SCM Updating the Volume Usage (Planner Interface) To change volume usage information 1. Log on to the Planner Interface. 2. From the Configuration Revisions window, select the system you are configuring. 3. Select Maintain>Volume maintenance. DSM/SCM displays the Volume Usage dialog box, listing host system DSM/SCM volumes, including whether the volume is a scratch volume, archive volume, or both. 4.
Moving the ZDSMSCM Subvolume to Another Volume Managing DSM/SCM Moving the ZDSMSCM Subvolume to Another Volume You should normally use the first ZDSMSCM subvolume installed on the system, regardless of how many subvolumes are created by subsequent additions of targets. However, you can run DSM/SCM from a volume other than the one on which INITENV was run. You can create ZDSMSCM subvolumes on other volumes, but the subvolume name cannot change.
Renaming a Volume Managed by DSM/SCM Managing DSM/SCM Switching From One ZDSMSCM Subvolume to Another To switch from one ZDSMSCM subvolume to another: 1. Check that both ZDSMSCM subvolumes (the one you are using and the one you will switch to) contain the same version of DSM/SCM. 2. Copy the INITSTAT, PATHCOOL, and PATHTARG (or PATHHOST if this is the host system) files from the $oldvol.ZDSMSCM subvolume to the $newvol.ZDSMSCM subvolume you are switching to. 3.
Deleting a SYSnn Subvolume Managing DSM/SCM Note. If $DATA00 is a scratch volume, Verify Database stops in restartable mode, giving an EMS message that no scratch volumes are configured on the target system. Define at least one scratch volume using the Target Maintenance and restart the Verify Database activity. After the successful completion of Verify Database, update the volume usage information using the ZPHIHMI also.
Managing DSM/SCM Databases Managing DSM/SCM Managing DSM/SCM Databases Canceling the Check-Out of a Database Object Note. Before canceling the check-out of an object, be sure the planner or operator who checked out the object is not available to complete the task. Cancel the check-out only if you cannot free the resource any other way.
Moving a DSM/SCM Database (ZPHIHMI or ZPHTMI) Managing DSM/SCM 3. To cancel the check-out of the Configuration Manager profile, from the Configuration Manager Profile Check-Out screen, press F4. To cancel the check-out of a target system profile, a software input, or a configuration revision, on the appropriate Check-Out screen, enter any character in the Selection field of each item to cancel the check-out; then press F4.
Updating DSM/SCM Databases Managing DSM/SCM Updating DSM/SCM Databases You might need to perform these activities periodically to ensure the target database is updated and synchronized with the host database. Keeping the databases updated and synchronized is crucial for effectively managing your system configuration. 1. Update a target database with the information regarding all TSVs. See Verifying the Target System Database (ZPHITI) on page 17-18. 2. Create an independent snapshot.
Creating an Independent Snapshot of the Target System Managing DSM/SCM When the Verify Database request finishes successfully, DSM/SCM displays an informational message. Note. If $DATA00 is a scratch volume, Verify Database stops in restartable mode giving an EMS message that no scratch volumes are configured on the target system. Define at least one scratch volume using the Target Maintenance and restart the Verify Database activity.
Managing DSM/SCM Creating an Independent Snapshot of the Target System The host and target databases are not synchronized because of a recent DSM/SCM process; for example, after an audit or database verification was performed on the target system. To create an independent snapshot of a target system: 1. At the ZPHITI main menu, enter 2 (Perform system snapshot) in the Selection number field and press F1.
Managing the DSM/SCM Archive Managing DSM/SCM Managing the DSM/SCM Archive The three areas of managing the DSM/SCM archive and its contents are: Managing Files (Software Inputs) in the Archive 17-21 Exporting Files From the Archive 17-24 Moving the DSM/SCM Archive (ZPHIHMI) 17-27 Managing Files (Software Inputs) in the Archive To efficiently manage archive space, first understand how DSM/SCM archives files. To optimize archive space, DSM/SCM ensures files are not duplicated in the archive.
Managing Files (Software Inputs) in the Archive Managing DSM/SCM The 440 identical files are stored with the first input and referenced by pointers from the second input. The 20 new files are the only additions to the archive for the second input. If you delete RVU X20.00, only the 10 files not referenced by X20.01 are removed from the archive. The 440 shared files remain. To determine which configurations use a specific product in the archive, generate a Configurations Using a Product report.
Managing Files (Software Inputs) in the Archive Managing DSM/SCM Deleting a Software Input (ZPHIHMI) Deleting a software input removes it from the archive, and removes its entry from the database. However, you cannot delete an input that is referenced by any configuration revision. To delete a backed-up input without first restoring it: 1. To find out which software inputs you can delete, generate the Configs Using a SW Input report. See Section 18, Generating DSM/SCM Reports. 2.
Exporting Files From the Archive Managing DSM/SCM 3. If necessary, obtain the name of the backed-up input by using the FUP COPY command for the first 200 bytes of the tape. 4. Enter the name of the tape drive to be used for the backup tape; then press F9. Exporting Files From the Archive Exporting files copies and converts files stored in the DSM/SCM internal archive format to standard system files.
Exporting Files From the Archive Managing DSM/SCM VSTA17.
Bringing an Exported File Back Into the Archive After the File Has Been Modified Managing DSM/SCM 2. As necessary, change the values for: The destination volume (enter the name or select one from the scrollable list). The default security information. Developer files: The developer file types (SPI definitions, EMS template source files, and Privileged declarations) are preselected. To clear a file type, clear its check box. You must select at least one type.
Managing DSM/SCM Moving the DSM/SCM Archive (ZPHIHMI) Moving the DSM/SCM Archive (ZPHIHMI) By default, the DSM/SCM archive on NonStop S-series systems and Integrity NonStop systems is located in the $AUDIT volume. If you need more space, you can move the DSM/SCM archive to a different volume. Moving the archive can provide more space for storing software inputs or other archive volume contents. Most users choose to move the archive to another volume when they configure DSM/SCM.
Moving the DSM/SCM Archive (ZPHIHMI) Managing DSM/SCM 2. Enter the current node (optional), volume, and subvolume (if you are moving a single subvolume) in the From field, and press F5. In the Disk Space field, DSM/SCM shows an estimate of the maximum amount of disk space that moving the archive will free. 3. Move all archive subvolumes or the specified archive subvolume from the volume: a. Enter the current node (optional), volume, and subvolume (if moving a subvolume) in the From field. b.
18 Generating DSM/SCM Reports This section describes DSM/SCM reports: DSM/SCM Reports on page 18-2 Viewing and Printing DSM/SCM Reports on page 18-7 Creating Reports on page 18-10 Adding and Deleting Reports on page 18-15 Shorthand Views of the DSM/SCM Database on page 16 For information about generating a report on the requisite SPRs for a software update, see Creating Software Revisions on page 8-15.
DSM/SCM Reports Generating DSM/SCM Reports DSM/SCM Reports You can generate a variety of reports to help you analyze software and resources managed by DSM/SCM. Report information describing the status of software configurations managed by DSM/SCM is extracted from the DSM/SCM database and formatted by SQL: Report Type Interface for Generating Standard Planner Interface System Target Interface DSM/SCM reports are located at $volume.subvolume.ZZRScncc.
Standard Reports Generating DSM/SCM Reports Table 18-1. Standard DSM/SCM Reports (page 2 of 5) Report name Contents Usage Configuration Product Files Provides a detailed picture of the contents of a configuration by product, shows the TSV locations of all product files in the configuration, and gives the software input name for each product component file. Use to determine what software versions exist on a system when you are planning an update.
Standard Reports Generating DSM/SCM Reports Table 18-1. Standard DSM/SCM Reports (page 3 of 5) Report name Contents Usage Input & Config Differences Gives file information for files found in a specified DSM/SCM software input and in a specified configuration revision. Shows differences in file function, destination, and fingerprint. Use to determine whether a given configuration contains everything from a given input and to determine what the differences are between the configuration and the input.
Standard Reports Generating DSM/SCM Reports Table 18-1. Standard DSM/SCM Reports (page 4 of 5) Report name Contents Usage Required IPMs for a Group Lists the minimum required SPRs missing in the selected software input (RVU) for all SPRs associated with the selected group. This report does not list the requisite SPR of any SPR in the group if it is already in the software input. Use to determine the requisite SPRs to add to a configuration.
Standard Reports Generating DSM/SCM Reports Table 18-1. Standard DSM/SCM Reports (page 5 of 5) Report name Contents Usage Software Product Files Shows the destination of all files in all products contained in a specified software input. Use when preparing to update a systems’ software configuration. The input name, product name, product number, product version, base SPR, and update SPR appear at the head of each group of product files.
Viewing and Printing DSM/SCM Reports Generating DSM/SCM Reports Viewing and Printing DSM/SCM Reports Default values are provided for the Report Request options. Preparing a Report for Printing or Viewing 1. Select the report to view or print. a. In the Planner Interface, select Requests>Prepare report.... DSM/SCM displays the Prepare Report Request dialog box. It lists the standard reports and any custom reports you have added to DSM/SCM. VST131.vsd b. Select a report from the list. c.
Preparing a Report for Printing or Viewing Generating DSM/SCM Reports VST132.vsd 2. Supply values for run-time parameters, as necessary. (For example, the Software Contents report requires you to specify the name of a software input as a parameter. The report then lists the files contained in the specified software input.) a. Select the parameter. b. Click Modify parameter....
Viewing a Report Online Generating DSM/SCM Reports a. Check the Viewable formatted file subvolume location check box if it is not already checked. b. To write the report to a location other than the default, enter a subvolume name in the subvolume location field, using standard HP naming conventions: If the host and target systems are network connected, the output location for target reports can be on the host system, the target system, or another system connected to both systems.
Creating Reports Generating DSM/SCM Reports Creating Reports Modifying Standard Reports You can modify any report in the DSM/SCM report list except: Discrepancy Report Required SPRs Replaced SPRs System Report You can modify reports in several ways: Change the content, style, formatting, or description of a report. Add parameters to or delete them from a report’s parameter list. Change the type or description of a parameter.
Modifying Standard Reports Generating DSM/SCM Reports c. Edit the new file. For more details on changing report formats, see the SQL/MP Report Writer Guide. 2. Bring the modified report file into DSM/SCM: a. Log on to the Planner Interface. b. Select Maintain>Report list. DSM/SCM displays the Maintain Report dialog, which shows the list of available reports. c. Select the report being modified. d. Change the report description: 1. Click Description. DSM/SCM displays the Modify Report dialog. 2.
Creating Custom Reports Generating DSM/SCM Reports f. Update the parameter type and description in DSM/SCM if you changed the type or usage of a parameter when customizing a report. 1. Click Parameter list.... (You can also click this button from the Modify Report dialog box.) 2. Select the parameter to modify. 3. Click Modify param....
Creating a System Report Generating DSM/SCM Reports To create a custom report: 1. Create a new IN_file, or make a copy of an existing DSM/SCM IN_file in the SQL catalog subvolume to use as a template. If you do the latter, work from a copy of the IN_file. Do not modify the original IN_file. 2. Use a text editor to change the file.
Creating a Discrepancy Report for a Clone Generating DSM/SCM Reports To write the report to disk, enter the system, volume, and subvolume location and press F1. For example: \devsys2.$dev2.data3 DSM/SCM assigns a file name to the disk file. The file name is returned in an EMS message. To send the report to a spooler location, enter the spooler location and press F1. For example: \devsys2.$s.#prt1 3. To return to the main menu, press F16. To exit the ZPHITI, press Shift-F16.
Adding and Deleting Reports Generating DSM/SCM Reports Adding and Deleting Reports After you create an SQLCI IN_file defining a new report, you can add the report to the list of reports displayed in DSM/SCM. You can also delete from DSM/SCM any reports you no longer use. Adding a Report to DSM/SCM (Planner Interface) 1. From the Planner Interface; select Maintain>Report list. 2. Click Add report. DSM/SCM displays the Add Report dialog: Enter a name for the report in the Report title field.
Shorthand Views of the DSM/SCM Database Generating DSM/SCM Reports Shorthand Views of the DSM/SCM Database Shorthand views of the DSM/SCM database provide a means for selecting data from the database to include in the DSM/SCM reports you create, as described in Creating Custom Reports on page 18-12. Each view represents a subset of information in the database, organized in tables. For more information about the organization and structure of SQL databases, see the SQL/MP Report Writer Guide.
Activity Code Descriptions Generating DSM/SCM Reports Column Name Description (page 2 of 2) Host_Node_Name The host system name, for activities run on the host Operator_Logon If the request was submitted by a operator, the user ID of the operator Planner_Logon If the request was submitted by a planner, the user ID of the planner Request_Name The name of the request; for example, Receive Software Request_Desc_Text Text describing the request Stage_Code A code indicating the current processing
Activity Param View Generating DSM/SCM Reports Status Code Meaning 220 Awaiting specified time to start 230 Awaiting start 240 Awaiting operator tape mount 250 Awaiting completion of activity 260 Awaiting shutdown, rename, system load, and startup 300 Processing stopped in restartable state 310 Cancel processing stopped in restartable state 400 Processing stopped in nonrestartable state 410 Cancel processing stopped in nonrestartable state 500 Complete 510 Complete with warnings 52
Configuration Manager View Generating DSM/SCM Reports Configuration Manager View The Configuration Manager View (=PHIH_CNFG_MGR_PRF_SVIEW) contains Configuration Manager profile information: Column Name Description Host_Node_Name The name of the host system Revision The version number of this revision of the profile Days_Retain_Requests Maximum time (days) that will elapse between the time a request stops and the time it is deleted Export_Arch_Files_Node The system DSM/SCM is using as a destinati
Configuration Products Versions View Generating DSM/SCM Reports Column Name Description Product_Version The version number of the product; for example, G06 File_Name The name of a file in the specified product File_Fingerprint An 8-character hexadecimal value used to uniquely identify the file File_Fingerprint_Vers The version of the file fingerprint TSV_Name1 The name of the target subvolume on which the file will be placed TSV_Name2 The name of a second target subvolume, if any, used by a s
Configuration View Generating DSM/SCM Reports Column Name Description Base_Product_Version Product version; for example, G01 Base_Product_Description Brief description of the product Subsystem_Class_Code Not used TNS_TNSR_DSV_Type Value indicating the processor type for which the product was designed: Y All R TNS/R only E TNS/E only Vendor_Name Name of the product’s vendor. Default is Tandem Computers, Inc.
EMS View Generating DSM/SCM Reports Column Name Description Instruction_Text Instructions to the target system operator (written by the planner in the Planner Interface) Config_Text_Seq_Nbr Internal sequence number assigned to a 240-character block of configuration description text Instruction_Text_Seq_Nbr Internal sequence number assigned to a 240-character block of operator instruction text EMS View The EMS View (=PHIH_EMS_LOG_SVIEW) contains information about the EMS messages on a target system
Logical Target Profile View Generating DSM/SCM Reports Column Name Description (page 2 of 3) Backout_Allowed_Flag Internal flag indicating whether a backout is allowed for the target Conftext_File_Node Name of the default system on which the CONFTEXT file for this target resides Conftext_File_Vol Name of the default volume on which the CONFTEXT file for this target resides Conftext_File_Subvol Name of the default subvolume in which the CONFTEXT file for this target resides Conftext_File Name of
Snapshot Files View Generating DSM/SCM Reports Column Name Description (page 3 of 3) Target_Output_Vol Volume on the target system containing the Backup output file Target_Output_Subvol Subvolume on the target system containing the Backup output file Target_Output_File File used for Backup output when run on the target system Host_TSV_Default_Vol Default volume for new TSVs that do not have a volume specified Include_All_Files_Flag Flag indicating whether the default is for DSM/SCM to include a
Software Input Files View Generating DSM/SCM Reports Column Name Description Audited_Subvol Name of the subvolume where the file resides File_Fingerprint Eight-character hexadecimal value uniquely identifying the file File_Fingerprint_Vers Version number of the file’s fingerprint Software Input Files View The Software Input Files View (=PHIH_SW_INPUT_FL_SVIEW) contains information about the files in a particular product: Column Name Description (page 1 of 2) Input_Name Name of the software inpu
Software Input Products View Generating DSM/SCM Reports Column Name Description (page 2 of 2) Dest_File_Name1 Dest_File_Name2 Dest_File_Name3 Special destination file names, as required by File_Function1, File_Function2, and File_Function3 TSV_Name1 TSV_Name2 TSV_Name3 Special TSVs, as required by File_Function1, File_Function2, and File_Function3 File_Fingerprint Eight-character hexadecimal value that uniquely identifies the file File_Fingerprint_Vers Version number of the file fingerprint
System View Generating DSM/SCM Reports Column Name Description Input_Type The type of the software input: S N I SUT (RVU) NPV (Initial PVU) IPM (SPR) Vendor_Name The name of the product’s vendor. For HP software, the value is Tandem Computers, Inc.
TSV View Generating DSM/SCM Reports TSV View The TSV View (=PHIH_TSV_SVIEW) contains TSV information for logical targets: Column Name Description System_Name Target system name Target_Name Logical target name TSV_Vol A TSV volume on the logical target TSV_Name A TSV subvolume name on the logical target Volumes View The Volumes View (=PHIH_VOL_SVIEW) contains information about volumes for a selected target system: Column Name Description System_Name The name of a target system Vol_Node_Name
19 Simplified Installation and Management of Multiple Identical NonStop Servers (Cloning) Cloning is the simplified use of DSM/SCM for installation and management of multiple NonStop systems with identical hardware and software configurations. In DSM/SCM you can create a clone group, consisting of a master system and one or more clone systems. Any software configuration applied to the master is also applied to all the clones in that master’s clone group.
Simplified Installation and Management of Multiple Identical NonStop Servers (Cloning) Creating a Clone Group Discrepancy Reports can be generated for clone targets only through a special process. See Creating a Discrepancy Report for a Clone on page 18-14. Creating a Clone Group You create a Clone Group by modifying the target description text for logical targets in the Planner Interface. Task 1: Define a Master Target 1.
Examples: Clone Groups Simplified Installation and Management of Multiple Identical NonStop Servers (Cloning) This system is now defined as a clone for the specified master. 5. Repeat this task for all the systems that will be clones in this clone group.
Examples: Clone Groups Simplified Installation and Management of Multiple Identical NonStop Servers (Cloning) Display of Masters and Clones When clone groups exist, the Planner Interface Configuration Revisions window adds a clone group column indicating the clone group membership for each system. Indicator Description M This system is a master. C This system is a clone. n A number appears to the left of every M or C in a valid group.
Simplified Installation and Management of Multiple Identical NonStop Servers (Cloning) Applying a Software Configuration to a Clone Group Applying a Software Configuration to a Clone Group Most of the process for applying a new software configuration to a clone group is similar to the normal DSM/SCM process. Caution. Any software configuration installed for a clone group is indicated in the Planner Interface only on the master target.
Renaming Product Files for a Clone Group Simplified Installation and Management of Multiple Identical NonStop Servers (Cloning) Renaming Product Files for a Clone Group To activate the updated software configuration on all systems in a clone group, use the CLONE utility to run ZPHIRNM. You can run ZPHIRNM individually for each target, but using the CLONE utility automatically runs ZPHIRNM in parallel on all targets. Note.
Simplified Installation and Management of Multiple Identical NonStop Servers (Cloning) Creating a Noncloning Configuration on a Master or Clone Creating a Noncloning Configuration on a Master or Clone It is unusual to update the configuration of a single member of a clone group. But if needed, you can update the software configuration for an individual master or clone system. To create a software configuration to apply to a master but no other clone group members: 1.
Simplified Installation and Management of Multiple Identical NonStop Servers (Cloning) Removing a System From a Clone Group Removing a System From a Clone Group Removing a Master From a Clone Group To remove a master target from a clone group: 1. Remove the text from its target description in the Planner Interface. 2. Do one of three things: Make this target a master for the group again.
20 Installation of Web Interfaces (HSeries and J-Series Only) DSM/SCM provides web interfaces for SCOBOL screens namely Host Maintenance Interface (HMI), Target Maintenance Interface (TMI), and Target Interface (TI). Note. This feature is supported only on systems running H06.09 and all subsequent H-series, and J-series RVUs.
Installation of Web Interfaces (H-Series and J-Series Only) Installation Procedure for DSM/SCM Web Interfaces After the installation of iTP WebServer is complete, do not delete or modify the versionspecific directory (/usr/tandem/webserver/) or its sub-directories. Because the OSS symbolic links present in the directory, where the iTP WebServer was installed, point to the directory tree.
Installation of Web Interfaces (H-Series and J-Series Only) Starting the Application Filemap /tmi $root/root/dsmscm/tmi/MI_LOGON_START.html Filemap /ti $root/root/dsmscm/ti/OI_LOGON_START.html 4. Start the WebServer (using ./start) 5. Open the browser and specify the DSM/SCM you want to open. For example, to open the Target Maintenance interface, specify: http://16.107.191.
Installation of Web Interfaces (H-Series and J-Series Only) DSM/SCM User’s Guide — 529846-014 20 - 4 Starting the Application
A DSM/SCM Architecture and Environment This appendix provides an overview of the architecture of DSM/SCM. Most of what it describes is invisible to users during normal DSM/SCM processing.
Architecture Overview DSM/SCM Architecture and Environment Architecture Overview Figure A-1. DSM/SCM Architecture Overview SUT $volume Planner Interface Winsock Winsock File Manager Pathway Env.
Architecture Overview DSM/SCM Architecture and Environment Figure A-2. DSM/SCM Host System Environment SUT Planner Interface PC Winsock Winsock Tape Rdr File Mgr SWID NonStop System Host Pathway Env. $YPHI Archive PDP LINKMON PATHMON IS-001 Backup File Mgr SYSGEN SWID RSC RSC API $volume TDP OM-001 SM-001 CB-001 TCP-H MISERVER Expand Host DB Mgr TARGET System Maintenance Interface Host Database VST071.
Architecture Overview DSM/SCM Architecture and Environment Figure A-3. DSM/SCM Target System Environment Target Pathway Env. $YPHI Target Interface TCP-T Rename Process PATHMON LINKMON NonStop System TISERVER MISERVER Backup File Mgr Tape Rdr SWID SM-T-001 Maintenance Interface TA-001 SYSnn SYSTEM Zuser TDB Mgr Target Database VST072.
DSM/SCM Architecture and Environment $YPHI Pathway Servers $YPHI Pathway Servers Schedule Manager (SM) The Schedule Manager is a host and target static server that: Ensures activities take place in the proper order Provides delayed scheduling of requests Provides persistence for the other server classes Input Supervisor (IS) The Input Supervisor runs as a host dynamic server class.
DSM/SCM Architecture and Environment Utility Server (US) Utility Server (US) The Utility Server runs as a host and target dynamic server class.
B DSM/SCM Differences This appendix describes: The differences between DSM/SCM product versions The differences between running DSM/SCM on different NonStop systems Upgrading to DSM/SCM T6031G02 Individual SPR features and options Topics discussed in this appendix include: Comparing DSM/SCM Product Versions on page B-2 Upgrading to DSM/SCM T6031G02 on page B-3 DSM/SCM User’s Guide — 529846-014 B-1
Comparing DSM/SCM Product Versions DSM/SCM Differences Comparing DSM/SCM Product Versions If possible, always install the most recent DSM/SCM product version supported for the type of NonStop system and RVU. For example, NonStop S-series systems support the DSM/SCM G02 product version. The G02/H02 planner interface supports both T6031G02 and T6031H01. This subsection compares different DSM/SCM product versions.
Upgrading to DSM/SCM T6031G02 DSM/SCM Differences Upgrading to DSM/SCM T6031G02 To manage an Integrity NonStop target from a NonStop S-series host system, you must install the DSM/SCM G02/H02 planner interface on your PC and the T6031G02 on the NonStop S-series system. A new version of SWID is also required. For more information, see the softdoc. Task 1: Install the DSM/SCM G02/H02 Planner Interface Task 1.1: Copy Setup to your PC 1.
Task 2: Start TMF and DSM/SCM DSM/SCM Differences 10. Check the Planner Interface startup screen to ensure you are running the G01/HO1 product version of the Planner Interface. Task 2: Start TMF and DSM/SCM Check that TMF and DSM/SCM are running: > TMFCOM START TMF > VOLUME $volume.ZDSMSCM > RUN STARTSCM Task 3: Log On to DSM/SCM Start the Planner Interface and log on to DSM/SCM. The main Planner Interface screen appears. Task 4: Receive DSM/SCM T6031G02 Into the Archive 1.
Task 5: Upgrade Your Host and Target Systems to T6031G02 DSM/SCM Differences b. Add a description of the changes. c. Click OK. Task 5.2: Build and Apply the Configuration Revision 1. From the window displaying the new software revision, click Build/Apply. DSM/SCM displays the Build/Apply Request dialog box. It might take several minutes for this dialog box to appear. 2. In the Activation SYSnn box, enter the current SYSnn. No system generation is required. 3. Schedule the request.
Task 5: Upgrade Your Host and Target Systems to T6031G02 DSM/SCM Differences Task 5.4: Restart All Applications Restart all applications, including DSM/SCM: > VOLUME $volume.
C Running CNFGINFO Note. If you do not work with third-party or customer-developed software, you are unlikely to ever run CNFGINFO. This appendix describes using the DSM/SCM Configuration Information (CNFGINFO) tool to create or modify a product’s A0CINFO or A7INFO file. Use CNFGINFO to define or modify installation information (file or product attributes) for third-party or customerdeveloped software applications for systems to be managed by DSM/SCM.
Preparing to Run CNFGINFO Running CNFGINFO Preparing to Run CNFGINFO To run CNFGINFO, the file CNFGI.EXE must be installed on a PC with a Winsock connection to a NonStop host system. (See Section 5, Configuring DSM/SCM.) If you are running CNFGINFO outside DSM/SCM, you must run the server program file CNFGINFO from the ZDSMSCM subvolume using these parameters: NOWAIT, NAME $ZPHC, TERM, IN, and OUT.
Entering CNFGINFO Running CNFGINFO Entering CNFGINFO 1. If running CNFGINFO by itself, run STARTCFG on your PC: > STARTCFG Otherwise, check that DSM/SCM is started. See Starting DSM/SCM on page 2-2. 2. To run CNFGINFO either: Select Start>Programs>Dsm_scm>CNFGINFO. In the Planner Interface main window, select Tandem>Run CNFGINFO tool. CNFGINFO displays the CNFGINFO Tool Logon dialog box. 3. Enter your user ID or alias and password and then click OK.
CONFIGINFO Summary Running CNFGINFO CONFIGINFO Summary To prepare the product for DSM/SCM, the planner: 1. Log on to CNFGINFO by selecting Tandem>Run CNFGINFO tool. 2. Specify the location of the distribution subvolume containing the product files. 3. Specify these product attributes: Product name Product version Subvolume where the files are to be placed 4.
Task 2: Open or Create an A0CINFO File Running CNFGINFO 3. Click OK. CNFGINFO displays the Select DSV Location dialog box: VST142.vsd Task 2: Open or Create an A0CINFO File 1. In the Select DSV Location dialog box, enter the location (system, volume, and subvolume) of the DSV that contains the product files for which you are creating or modifying an A0CINFO file. The system name defaults to the system you are logged on to. 2. Click View/modify product info....
Task 3: Specifying Product or File Information Running CNFGINFO Task 3: Specifying Product or File Information From the DSV Information dialog box, you can enter or modify information about the product and its files. The fields are described in the online help. The boxes on the DSV Information dialog box correspond to product attributes. 1. To add or change information in the A0CINFO file: Product information, enter the information in the boxes in the DSV Information dialog box.
Specifying Product Attributes Running CNFGINFO Attribute Description DSV Category Required; the category of the product. A product is either a base version or an update. Choose one of: Base Version Default; indicates that the software is a base version containing a complete set of files. Includes a complete set of product files and therefore replaces all previous base versions and SPR udpates applied to that product.
Specifying Product Dependencies Running CNFGINFO Specifying Product Dependencies A product’s A0CINFO file optionally contains two dependency lists: The Requires list contains the product number, version ID, and SPR code of other product SPRs that must accompany the current product in the new software revision. The Replaces list contains the product number, version ID, and SPR code of earlier versions of the product that are superseded by this version.
Specifying File Information Running CNFGINFO Adding a Product to the Replaces List 1. Enter the three-letter SPR identifier in the IPM update code field. To replace multiple SPRs, enter each separately. 2. Click Add. Removing a Product from the Replaces List 1. Scroll through the list of product versions in the Replaces list. 2. Select a product. 3. Click Remove next to the list.
Specifying File Information Running CNFGINFO 3. From the distribution files dialog box, click either Modify function, Delete function, or Add function. Click Add function... to add a new function for a file. Click Modify function... to modify a file’s information. Click Delete function.... to delete a function from the selected file. CNFGINFO displays the Confirm Deletion warning box. Click Yes to proceed with the deletion. Note. You cannot delete the last entry for a file.
Specifying File Information Running CNFGINFO Specifying a Destination Subvolume or File Name Enter or modify the information in the Subvolume and New filename fields as needed. The TSV where the file will be placed depends on the file’s function.
Specifying File Information Running CNFGINFO 1. Define a dummy product file that has no function but has the same name and interface as the optional product file. 2. Specify the optional product on a DELIF list for the dummy product file so it is included in the software revision only if the optional product is not present. To require that the file’s inclusion in the software revision depends on the presence of another product: 1. Click ADDIF....CNFGINFO displays the ADDIF dialog box.
Specifying File Information Running CNFGINFO Function Meaning DOCPRINT File is a TGAL-formatted softdoc or release document. INSTALL File is used by DSM/SCM during its processing; for example, as a tool to build an activation package. MIGRATION File is used during migration processing. Use only under direction of HP support personnel. See Specifying the Migration Function on page C-15.
Specifying File Information Running CNFGINFO Specifying System Generation Usage for the File 1. In the DSV File Information dialog box, click SYSGEN....CNFGINFO displays the SYSGEN Usage dialog box, which shows a list of system generation options. 2. To select one of the listed options, click the corresponding button. These options are mutually exclusive, except for SYSGEN COPY (copy file to SYSnn) and SYSGEN PROCESS (system process file).
Specifying File Information Running CNFGINFO Table C-1. System Generation Options Option Indicates that... (page 2 of 2) System library file A system generation program binds the file into the system code or library segments in OSIMAGE; for example, system-callable procedures and interrupt handlers. You must also indicate a bind group number between 0 and 9. System process file The file is a system process that runs under its own process identification number (PIN) from OSIMAGE.
Task 4: Log Off Running CNFGINFO If a file has the Migration Tool function, you must specify the migration to and optionally the migration from RVUs. The default for the migration from RVU is any RVU preceding the migration to RVU. 1. In the DSV File Information dialog box, click Migration....CNFGINFO displays the Migration Tool Usage dialog box. 2. Enter the ID of the RVU being migrated to; for example, G06.26. 3. Enter the ID of the RVU being migrated from.
D Required Processes and Files This appendix describes the contents of the $SYSTEM, $DSMSCM, and $AUDIT disk volumes, as preconfigured on all NonStop S-series servers and Integrity NonStop servers. DSM/SCM requires these permanent and temporary files to function correctly. Do not purge or alter subvolumes or files as noted. Doing so can cause serious performance problems and might require a reinitialization of DSM/SCM.
Required Processes Required Processes and Files Required Processes DSM/SCM requires these processes: CNFGINFO Server $ZPHC EMS Collector $ZPHI PATHMON Name $YPHI Required Volumes You need at least three disk volumes available for DSM/SCM: System load volume $SYSTEM (location for SYSnn subvolume and target subvolumes) $DSMSCM (location of the DSM/SCM application and database) $AUDIT (location of the archive and TMF audit trails) System Load Volume $SYSTEM is the recommended volume name.
System Load Volume Required Processes and Files Subvolume Description Contains Files PURGEME Temporary files created and purged by DSM/SCM. DO NOT PURGE OR ALTER THIS SUBVOLUME. Guardian files renamed by TA to PURGEME subvolume $volume.PURGE ME.ZPGccncc OSS files renamed by TA to PURGEME subvolume .dsmscm.ZPGcc ncc Files renamed by ZPHIRNM to PURGEME subvolume $volume.PURGE ME.filename The filename variable is already present in PURGEME subvolume $volume.PURGE ME.
System Load Volume Required Processes and Files Subvolume Description Contains Z* DSM/SCM target subvolumes. BE CAREFUL BEFORE YOU DELETE ANYTHING IN THESE SUBVOLUMES. For example, do not delete any ZMP* or ZFB* files. Software product files and files added by DSM/SCM for software configuration management purposes. ZAnnnn Activation package subvolumes, left when a user: Files Performs a Build and never performs a successful Apply. Cancels or deletes an Apply request.
DSM/SCM Application and Database Volume Required Processes and Files DSM/SCM Application and Database Volume $DSMSCM is the recommended name for the disk volume that contains the DSM/SCM application and databases. Use $DSMSCM as the volume name to avoid confusion. Subvolume Description Contains... PATHSCM Contains Pathway control and log files.
DSM/SCM Application and Database Volume Required Processes and Files Subvolume Description Contains... ZDSMSCM DSM/SCM target subvolume (product subvolume). DO NOT ALTER OR PURGE THIS SUBVOLUME. Product Subvolume (TSV). See DSM/SCM Application and Database Volume on page D-5. $volume.ZDSMSCM.* (.dsmscm.ZFBccncc for OSS files) To copy this subvolume, see Switching From One ZDSMSCM Subvolume to Another on page 17-14 and Renaming a Volume Managed by DSM/SCM on page 17-14. TACL Start File $volume.
Archive and Audit Volume Required Processes and Files INITLOG from previous versions of DSM/SCM.) You can view this file which provides a permanent record of INITENV activities. Each time you run INITENV, it logs to the next unused ILOGnnnn file in the ZDSMSCM subvolume, in ascending order. If all files ILOG0000 through ILOG9999 exist, you get a message prompting you to purge some of the ILOGnnnn files.
Scratch Volume Required Processes and Files attributes through CNFGINFO, enter information and select options in the CNFGINFO dialog boxes. A1CINFO Files DSM/SCM requires an A1CINFO configuration file for shared run-time library (SRL) products on NonStop S-series systems. A1CINFO configuration files are distributed with SRL products. CNFGINFO has not been updated to handle A1CINFO files. Otherwise, you should be able to treat any A1CINFO file that you see just as you would any A0CINFO file.
Required Files Required Processes and Files Activation Package $scratch.ZAnnn.ZZAnnnnn Snapshot Subvol $scratch.ZPHISNAP.
ZPHIRNM Rename Work Files Required Processes and Files Located in SYSTEM subvol Points to last rename SYSnn ZPHISYS Points to last rename SYSnn (for OSS TSVs) ZPHIOSS Located in SYSnn Directory file for current revision ZSSLIST Directory file for current revision containing OSS files ZOSSLIST Directory file for previous revision ZWKccncc * Directory file for previous revision containing OSS files ZWOccncc * Directory file for the previous configuration when a FRABIBAB is performed ZWKFRAB Di
ZPHIRNM Rename Work Files Required Processes and Files subvolume is a subvolume managed by DSM/SCM.
ZPHIRNM Rename Work Files Required Processes and Files DSM/SCM User’s Guide — 529846-014 D - 12
E ASSIGNs and PARAMs This appendix describes using ASSIGNs and PARAMs: Assigning and Activating Tools on page E-2 Adding ASSIGN Statements for Tools on page E-2 Specifying a PARAM From the Planner Interface on page E-5 Specifying a PARAM From PATHCOM on page E-5 DSM/SCM User’s Guide — 529846-014 E-1
Assigning and Activating Tools ASSIGNs and PARAMs Assigning and Activating Tools Note. Perform these activities only as directed by HP support personnel or release documentation. They are performed only to help resolve a migration problem or to help troubleshoot certain situations. PARAMs and ASSIGNs are not normally required in procedures. Removing PARAMs or ASSIGN Statements From the List 1. In the Tool Assigns dialog box, select a PARAM or ASSIGN name. 2. Click Remove. 3.
Adding ASSIGN Statements for Tools ASSIGNs and PARAMs 8. Deactivate Tool ASSIGNS. From the Build/Apply Request dialog box, select Tandem>Support info>Activate tool assign again. Table E-1 lists the tools that DSM/SCM uses and the file ASSIGNs that you can use to direct DSM/SCM to use a file from a different location. Some tools have multiple assigns, so different versions of tools can be used for different tasks. Assigns are mostly limited to the Build/Apply activities.
Adding ASSIGN Statements for Tools ASSIGNs and PARAMs Table E-1.
Specifying a PARAM From the Planner Interface ASSIGNs and PARAMs Specifying a PARAM From the Planner Interface DSM/SCM uses a set of appropriate PARAMs when running a system generation program. For G-series RVUs, you can pass a PARAM to a system generation program. PARAMs specified from the planner interface are not persistent. Each new Build and Apply starts with no PARAMs. For available PARAMs for system generation, refer to the System Generation Manual for G-Series RVUs. Note.
PARAM Summary ASSIGNs and PARAMs server is the appropriate PATHWAY server, IS-001, CB-001, TA-001, or OM-001. See $YPHI Pathway Servers on page A-5. param-name param-value See PARAM Summary on page E-6. PARAM Summary AP^BACKUP "backup-program-file " Pass this PARAM to the PATHWAY server CB-001. If a tool assign was not specified for the BACKUP tool, DSM/SCM uses the BACKUP program specified in the PARAM to create the AP on tape. backup-program-file is a fully qualified file name in the form $volume.
PARAM Summary ASSIGNs and PARAMs YES specifies that the last-logon timestamp for the user that logged into DSM/SCM is not updated in the SAFEGUARD logs. NO specifies that the timestamp is updated. This is the default. FORCE-PUBLIC-DLL-BUILD "system logical_target revision " builds public DLLs for the configuration specified. Pass this PARAM to CB-001. For example: "TARG DEFAULT 47" system is the target system. logical_target is the logical target name.
PARAM Summary ASSIGNs and PARAMs FP-MFG-F--VERSION =999 Delphi fingerprints (LMT and EOF) are calculated for this file. FP-MFG-F--VERSION = -1 Real fingerprints are calculated for this file, getting the latest version for the file. FP-MFG-F--VERSION = 1 Real fingerprints are calculated for this file, getting version 1 for the file. FP-MFG-SYSNN-VERSION = 999 Delphi fingerprints(LMT & EOF) are calculated for files in a temporary SYSnn subvolume*.
PARAM Summary ASSIGNs and PARAMs FP-MFG-PUB-DLL-VERSION = 1 Real fingerprints are calculated for files in a temporary Public DLL sv*, getting version 1 for the file. FP-MFG-VERSION = 999 Delphi fingerprints (LMT & EOF) are calculated for all manufactured files*. FP-MFG-VERSION = -1 Real fingerprints are calculated for all manufactured files*, getting latest version for the file. FP-MFG-VERSION = 1 Real fingerprints are calculated for all manufactured files*, getting version 1 for the file.
PARAM Summary ASSIGNs and PARAMs NO-DB-OWNER-SERVER specifies to use the Super ID (255,255) to communicate across the EXPAND network for the Build, Apply, Create snapshot, and Receive snapshot. Pass this PARAM to the PATHWAY server CB-001 or TA-001. By default, all communication between a host system and a target system uses the DSM/SCM user ID.
ASSIGNs and PARAMs IGNORE-SAFEGUARD-PROTECTION Param SYSGEN-SPOOLER-OUTPUT-OWNER-ID "user-id " DSM/SCM makes the Planner ID the owner of the system generation spooler output unless this PATHWAY PARAM is specified. Pass this PARAM to the PATHWAY server CB-001.
KEEP-OBSOLETE-SYSNN Param ASSIGNs and PARAMs This PARAM remains active for all Apply requests for the target until you delete it using PATHCOM. KEEP-OBSOLETE-SYSNN Param DSM/SCM normally deletes the obsolete SYSnn as part of normal cleanup during a Build/Apply. However, you can choose to keep the obsolete SYSnn. subvolume. 1.
OVERRIDE-SYSNN and OVERRIDE-SYSNNDIFFERENT-OS Params ASSIGNs and PARAMs 4. Build/Apply and system load SYS03: SYS01 and CSS01 become obsolete and unmanaged but are not purged. SYS02 becomes the previous configuration. 5. Delete the KEEP-OBSOLETE-SYSNN PARAM. 6. Build/Apply and system load SYS04: SYS02 and CSS02 are purged. SYS01 and CSS01 are not purged by DSM/SCM, but you can purge them manually at any time.
OVERRIDE-SYSNN and OVERRIDE-SYSNNDIFFERENT-OS Params ASSIGNs and PARAMs Configuration Need Params Used Results Normal update, system load is acceptable None Overriding is not allowed. (Never use this PARAM by itself) OVERRIDE-SYSNNDIFFERENT-OS Overriding is not allowed. You can create the same configuration, system load not acceptable OVERRIDE-SYSNN If the new and target OSIMAGE EOFs are the same, overriding is allowed. Otherwise, overriding is not allowed.
OVERRIDE-SYSNN and OVERRIDE-SYSNNDIFFERENT-OS Params ASSIGNs and PARAMs Considerations After using the OVERRIDE-SYSNN PARAM once, you must specify the PARAM for every Apply until you perform a system load. A Discrepancy Report still shows the OSIMAGE on the system is different from that in the configuration. However, a Verify Database does not detect a difference.
OVERRIDE-SYSNN and OVERRIDE-SYSNNDIFFERENT-OS Params ASSIGNs and PARAMs Check that the OSIMAGE EOF is the same. Otherwise, OVERRIDE-SYSNNDIFFERENT-OS is required. Compare the old and new configuration dial-out reports (SYSHnnnn files in ZDSMSCM). This report contains all products and their versions in the configuration. To Apply to the executing SYSnn after initializing DSM/SCM, capture the old configuration report before initializing. Check the CONFLIST and CONFAUX files.
ASSIGNs and PARAMs OVERRIDE-SYSNN and OVERRIDE-SYSNNDIFFERENT-OS Params If all other lines in both files match, they are the same. Checking the OSIMAGE Files After System Generation To verify that the new and running OSIMAGEs are the same after running a system generation program at the end of a series of configuration revisions, do one of: After a Build/Apply with the OVERRIDE-SYSNN PARAM finishes, run a Configuration Differences report.
ASSIGNs and PARAMs OVERRIDE-SYSNN and OVERRIDE-SYSNNDIFFERENT-OS Params DSM/SCM User’s Guide — 529846-014 E - 18
Glossary A0CINFO file. A DSV file that contains information about a product and each of its files, including product and file dependencies, how the files are used and where they are placed, and which type of processor the product runs on. Every product and SPR to be managed by DSM/SCM is distributed in a subvolume, and that subvolume must contain the product's A0CINFO file. A1CINFO file.
audit Glossary audit. An activity initiated by the operator at a target system that updates the target database with the fingerprints of all the files in a selected set of target subvolumes (TSVs). backout. The DSM/SCM action of making the last configuration applied to the target system inaccessible and replacing it with the previous configuration. base SPR. Last SPR (if any) that was applied to the product before it was received into the archive. base version. The version of a specific product.
cloning Glossary cloning. A DSM/SCM feature allowing for simplified installation and management of software configurations on multiple identical NonStop systems. compression. The process of reducing the size of files by about one half by using algorithms to indicate how repeating characters (such as spaces) should be stored. configuration file. See CONFTEXT file. Configuration Information Tool (CNFGINFO).
DEFINE statements Glossary DEFINE statements. A set of optional statements in the CONFTEXT file that lets you set up string variables. When system generation runs, it substitutes actual strings for the variables. DELIF list. A list of other products which, if they are in a software revision, cause a particular file in a product to be excluded from the revision. The file is included only if none of the listed products is in the revision. The DELIF list is an optional part of each product’s A0CINFO file.
Expand network Glossary Expand network. The NonStop operating system network that extends the concept of fault-tolerant operation to networks of geographically distributed NonStop systems. If the network is properly designed, communication paths are constantly available even if a single line or component fails. export. The act of transferring files from the DSM/SCM archive to a standard NonStop operating system format.
Glossary HP NonStop™ Transaction Management Facility (TMF) HP NonStop™ Transaction Management Facility (TMF). HP software that provides transaction protection and database consistency in demanding online transaction processing (OLTP) and decision-support environments. It gives full protection to transactions that access distributed SQL/MP and Enscribe databases, as well as recovery capabilities for transactions, online disk volumes, and entire databases. INITENV.
network connected Glossary network connected. Multiple computer systems (or nodes) communicating with each other by means of an Expand or other network connection. To use a network other than one with an Expand connection, you must transmit objects (such as the activation package or snapshot) outside of DSM/SCM. new product version (NPV). A complete set of product files that contains new functions or major updates.
privileged declarations files Glossary privileged declarations files. A set of files containing data structures and calling sequences for use by customers when writing privileged code to make direct use of some set of system resources. privileged process. A process that performs privileged operations, such as direct use of a set of system resources or invoking callable procedures. process ID (PID). A number that uniquely identifies a process.
release version update (RVU) Glossary release version update (RVU). A collection of compatible revisions of NonStop operating system software products, identified by an RVU ID, and shipped and supported as a unit; for example, the G06.18 RVU. When HP releases a new RVU, you receive either the entire RVU or selected products from the RVU off of its SUT. An RVU is distributed on a site update tape (SUT) from which you can receive either the entire RVU or selected products.
SIT Glossary SIT. See system image tape (SIT). site ID. A unique 6-digit number assigned by HP to identify a particular system. site-specific subvolume. A subvolume containing files unique to the target system, such as a list of products belonging to the target. Its format is Annnnnn, where nnnnnn is the system site ID. site update tape (SUT). One or more tapes that contain a target system’s site-specific subvolume and various products. Each product contains a softdoc and a complete set of files.
SQL/MP Glossary SQL/MP. An HP relational database management system that uses ANSI-standard Structured Query Language (SQL) to describe and manipulate data. You use SQL/MP to define, manipulate and control databases. In the DSM/SCM environment, you use the SQL/MP command interpreter (SQLCI) to define reports against the DSM/SCM database. SQLCI IN file. A file containing the set of SQLCI statements used to produce a report. The statements contain both static and variable information.
TACLSEGF Glossary TACLSEGF. A segment file containing directories for all HP products on the system that have TACL code. TACLSEGF is shared by all users of the system and is automatically attached to each TACL at log on time. target. A name that defines a specific system usage, such as WEEKEND, PRODUCTION, or DEVELOPMENT. You can define multiple logical targets for a target system. The target name is part of the configuration revision name. target directory location (TDL). See TDL.
TNS/R Glossary TNS/R. Refers to fault-tolerant HP computers that support the HP NonStop™ operating system and are based on 32-bit reduced instruction-set computing (RISC) technology. TNS/R systems run the MIPS-1 RISC instruction set and can run TNS object files by interpretation or after acceleration. TNS/R systems include all HP systems that use NSR-x processors. Contrast with TNS and TNS/E. Transaction Delivery Process. A host process that delivers and receives host transactions.
ZPHIRNM Glossary DSM/SCM User’s Guide — 529846-014 Glossary - 14
Index Numbers 12-3 12-3 A A0CINFO file adding or changing product information C-6 attributes, description of C-10 creating for exported files 17-26 dependency information C-11 destination subvolumes C-11 functions C-12/C-15 opening or creating C-5 overview D-7 product attributes, description of C-6 product dependency lists C-8 security for C-5 Activating new software 10-1 tools E-5 Activation package contents of 9-4 specifying location of 9-15 transmitting 6-4/6-5 Activity Code descriptions 18-17 ADDIF fil
C Index using 5-26 Build request See Build/Apply request Build type, indicating 5-18, 9-2 Building/Applying a configuration revision examples of 6-4 overview of 6-4, 9-1 Build, FRABIBAB 5-8, 9-3 Build, result of 6-4, 9-5 Build/Apply request changing system generation options 9-18 changing TSV locations 9-12 editing planner instructions for 9-23 indicating type of build 5-18, 9-2 initialization host system 5-18 purpose of 16-2 scheduling 9-22 See also Requests submitting 9-8/9-24 C Canceling checked-out o
D Index starting C-3 starting in Planner Interface C-4 TACL directory C-15 Cold load See System load Configs Using a SW Input report 18-2 Configuration changing individual settings 5-15 current 8-24 previous 8-24 Configuration Differences report 18-2 Configuration Manager profile changing defaults of 5-15 check-out management 17-16 initializing 5-6, 5-33 maintaining 17-2 overview 17-2 updating from Maintenance Interface 5-6, 5-33 from Planner Interface 17-2 Configuration Product Files report 18-3 Configur
E Index Decompressing files 4-8 Default values, changing 5-15 Deleting entire software configuration 17-23 logical target 5-21 new software revision 8-24 old software revisions 8-24 products from new revision 8-24 requests 13-18, 16-8 software inputs 17-23 SYSnn 17-15 target 5-21 DELIF file, usage C-11 Destination subvolume, description of C-11 Developer files, exporting 17-24/17-26 Disaster recovery 14-14 Discrepancies during initialization 5-39 initial report of 5-39 resolution of 5-37/5-38, 13-17 revie
G Index TACLSEGF C-15 File placement options 9-19 File security See Security or Safeguard Files exporting See Exporting files listing in a product 8-7 listing in an SPR 8-9 returning to archive 17-26 Files not to purge ZFB* D-9 ZPHIRNM work files D-10 Filtering traces 14-6 Firmware, updating 10-4 FRABIBAB defined 9-3 file ownership 5-8, 9-3 FSTCACHING modifier, for archive volumes 17-11, 17-27 G Groups adding members to 7-14 disbanding 7-15 displaying members of 7-14 forming for products 7-12 forming for
L Index Input groups See Groups Installation Planner Interface 5-3, 5-30 Planner Interface, restoring files from SUT B-4 Installation Procedure for DSM/SCM Web Interfaces 20-2 Installing user template 9-6 Instructions See Operator instructions IN_file See SQLCI IN_file L Logical target adding 5-17 definition 1-4 deleting from system 5-21 Logoff CNFGINFO tool C-3, C-16 Maintenance Interface 2-10 Planner Interface 2-6 Target Interface 2-14 Logon CNFGINFO tool C-3, C-4 ID 2-15 Maintenance Interface 2-7 Plan
O Index New software See also Software revisions activating on target system overview 10-1 running ZPHIRNM 11-1 standard operator instructions 10-3 New Software Revision screen, closing 8-22 Notepad, using to edit planner instructions 9-7/9-23 disabling 17-6 enabling 17-6 falling back 15-10 upgrading to B-3 Output options changing 9-14 changing defaults 17-7, 17-9 overriding 9-14 OVERRIDE-SYSNN 6-2 OVERRIDE-SYSNN-DIFFERENT-OS 6-2 O P Obsolete SYSnn, keeping 6-2 Online help context-sensitive help 2-18
P Index PHIH_TSV_SVIEW 18-28 PHIH_VOL_SVIEW 18-28 Planner 4-14 activities 4-13 editing instructions 9-23 groups 8-25 list 5-10 responsibilities 1-6, 4-14 security setting initial 5-10 updating 5-9 Planner Interface assigning and activating tools E-5 Build/Apply request changing output options 9-14 changing system generation options 9-18 scheduling 9-22 submitting 9-8/9-24 canceling requests 16-8 revisions 8-22 changing TSV locations 9-12 choosing requests to display 16-4 Configuration Revisions screen 2-5
R Index changing output defaults 17-7, 17-9 changing system generation defaults 17-9 target systems adding new logical target 5-17, 5-18 changing profile information 17-7 deleting a target 5-21 viewing list of requests 16-3/16-6 other EMS events 13-3 request EMS events 13-2, 16-7 software in Archive 7-3 status of requests 16-4 Prepare Documents request, purpose of 16-2 Prepare Report request, purpose of 16-2 Privileged declarations files, exporting 17-24 Product groups See Groups Products applying SPRs to
S Index Configuration Differences 18-2 Configuration Product Files 18-3 Configuration Products 18-3 Configurations Using a Product 18-2 Contents of All Configs 18-3 customized adding 18-15 deleting 18-15 overview 18-12 deleting 18-15 deleting parameters 18-11 Discrepancy 18-3 displaying list of 18-7 list of available reports 18-2/18-6 parameters adding to report 18-11, 18-15 defining for new report 18-15 deleting from report 18-11 entering values for 18-8 preparing for viewing or printing 18-7/18-9 overvi
S Index Export Files 17-24/17-26 options 7-7 overview 16-2 Prepare Report 18-9 Receive Software 7-7 Security setting default for new files 9-17 setting for database administrator 5-11, 5-12 setting for operator 5-13, 5-14 setting for planner 5-9, 5-10, 5-13 settings for DSM/SCM users 1-6 using Guardian instead of Safeguard 9-15 SETUP.
S Index receiving, overview of 7-1 restoring from tape 17-23 specifying source options 7-6 types of 6-2 viewing by group 7-12/7-13 viewing description of 7-9 Software product revision see SPR Software revisions canceling new revisions 8-22 changing revision notes 8-21 choosing display order of products 8-6, 8-7 closing new revision 8-22 copying products to 8-18/8-23 creating 8-1, 8-15 definition 6-3, 8-1 deleting products from 8-24 deleting revision 8-24 initial contents 6-3 listing files in product versi
T Index changing defaults 17-9 errors in the output file 13-4 file function C-14 forcing a 9-18 options changing defaults 17-9 overriding 9-18 output, deleting from archive 17-22 usage, specifying C-14 System load avoiding 6-2 in operator instructions 10-5 reinitializing DSM/SCM without 6-2 System profile check-out management 17-16 displaying checked-out profiles 17-16 updating 17-4/17-5 System report creating 18-13 definition 18-13 Systems, listing 17-5 T TACL directory for DSV C-15 TACL Macro, UPDATES
U Index requesting a snapshot of 17-19 See also Logical target setting passwords for 1-4 verifying database of 17-18 Target work files, cleaning 13-24 Tool ASSIGN E-5 adding statements for E-2 button activating E-2, E-5 removing statements for E-2 Trace disabling 14-5 enabling 14-3 filtering 14-6 levels 14-7 search strings 14-8 TRACEINI file 14-6 TSVs adding to a volume 9-14 changing location of 9-12, 9-15 discrepancy 13-17 moving to new volume 9-14 removing from a volume 9-14 working files D-9 Version d
Special Characters Index in Preview mode 11-2 on actual files 11-4 overview 11-1 starting 2-15, 11-1 work files D-10 Special Characters $AUDIT volume D-2 $DSMSCM volume D-2 $SYSTEM volume D-6 DSM/SCM User’s Guide — 529846-014 Index - 15
