DSM/SCM Quick
Reference Guide
Abstract
This guide provides concise, task-oriented procedures for configuring Distributed
Systems Management/Software Configuration Manager (DSM/SCM). It is intended for
experienced DSM/SCM users who manage and update the software configuration on
HP NonStop™ systems.
Product Version
DSM/SCM G02
DSM/SCM H02
Supported Release Version Updates (RVUs)
This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all
subsequent H-series RVUs, and G06 and all subsequent G-series RVUs, until
otherwise indicated by its replacement publications.
Part Number
Published
529847-005
May 2008
Document History
Part Number
Product Version
Published
520611-005
DSM/SCM D31 and D46
December 2003
520611-006
DSM/SCM D31 and D46
April 2004
520611-007
DSM/SCM D31 and D46
December 2004
529847-003
DSM/SCM G01 (ABP) and H01
July 2005
529847-005
DSM/SCM G02 and H02
May 2008
Legal Notices
 Copyright 2008 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. The only warranties for HP
products and services are set forth in the express warranty statements accompanying such products
and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be
liable for technical or editorial errors or omissions contained herein.
Export of the information contained in this publication may require authorization from the U.S.
Department of Commerce.
Microsoft, Windows, and Windows NT are U.S. registered trademarks of Microsoft Corporation.
Intel, Itanium, Pentium, and Celeron are trademarks or registered trademarks of Intel Corporation or its
subsidiaries in the United States and other countries.
Java is a U.S. trademark of Sun Microsystems, Inc.
Motif, OSF/1, UNIX, X/Open, and the "X" device are registered trademarks and IT DialTone and The
Open Group are trademarks of The Open Group in the U.S. and other countries.
Open Software Foundation, OSF, the OSF logo, OSF/1, OSF/Motif, and Motif are trademarks of the
Open Software Foundation, Inc.
OSF MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THE OSF MATERIAL PROVIDED
HEREIN, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
OSF shall not be liable for errors contained herein or for incidental consequential damages in
connection with the furnishing, performance, or use of this material.
© 1990, 1991, 1992, 1993 Open Software Foundation, Inc. This documentation and the software to
which it relates are derived in part from materials supplied by the following:
© 1987, 1988, 1989 Carnegie-Mellon University. © 1989, 1990, 1991 Digital Equipment Corporation.
© 1985, 1988, 1989, 1990 Encore Computer Corporation. © 1988 Free Software Foundation, Inc.
© 1987, 1988, 1989, 1990, 1991 Hewlett-Packard Company. © 1985, 1987, 1988, 1989, 1990, 1991,
1992 International Business Machines Corporation. © 1988, 1989 Massachusetts Institute of
Technology. © 1988, 1989, 1990 Mentat Inc. © 1988 Microsoft Corporation. © 1987, 1988, 1989,
1990, 1991, 1992 SecureWare, Inc. © 1990, 1991 Siemens Nixdorf Informationssysteme AG. © 1986,
1989, 1996, 1997 Sun Microsystems, Inc. © 1989, 1990, 1991 Transarc Corporation.
This software and documentation are based in part on the Fourth Berkeley Software Distribution
under license from The Regents of the University of California. OSF acknowledges the following
individuals and institutions for their role in its development: Kenneth C.R.C. Arnold,
Gregory S. Couch, Conrad C. Huang, Ed James, Symmetric Computer Systems, Robert Elz. © 1980,
1981, 1982, 1983, 1985, 1986, 1987, 1988, 1989 Regents of the University of California.
Printed in the US
DSM/SCM Quick Reference
Guide
Index
Legal Notices
What’s New in This Manual v
Manual Information v
New and Changed Information
vi
About This Guide vii
Who Should Use This Guide vii
What’s in This Guide vii
Other DSM/SCM Information Sources
Notation Conventions viii
viii
1. Configuring a Host or Physical Target System
Preliminary Task: Install the DSM/SCM PC Files 1-1
Task 0.1: Ensure TCPIP and LISTNER Are Installed 1-1
Task 0.2: Transfer DSM/SCM PC Files From the SUT to the PC 1-1
Task 0.3: Ensure Winsock Is Installed 1-1
Task 0.4: Run SETUP.EXE 1-2
Task 1: Configure the DSM/SCM System Environment 1-2
Task 2: Configure the Host Database 1-3
Task 2.1: Add and Set Planner Security 1-3
Task 2.2: Update the System Profile 1-3
Task 2.3: Update Host System Volume Usage 1-4
Task 2.4: Set Security for Host Database Administrators 1-4
Task 2.5: Update the Configuration Manager Profile 1-5
Task 2.6: Move the Archive (Optional) 1-5
Task 3: Configure the Target Database 1-6
Task 3.1: Update the Target Profile 1-6
Task 3.2: Update Target Volume Usage 1-6
Task 3.3: Add and Set Security for Operators 1-6
Task 3.4: Add and Set Security for Target Database Administrators 1-7
Task 4: Modify Profile Information for the Logical Target 1-7
Task 4.1: Update the Target Profile 1-7
Hewlett-Packard Company—529847-005
i
1. Configuring a Host or Physical Target
System (continued)
Contents
1. Configuring a Host or Physical Target System (continued)
Task 5: Initialize the Target on the System 1-7
Task 5.1: Register the Target 1-8
Task 5.2: Set Target Output Defaults 1-8
Task 5.3: Set Target System Generation Defaults 1-8
Task 6: Receive Software 1-8
Task 6.1: Receive Software 1-8
Task 6.2: Create Software Revision 1-9
Task 7: Build/Apply Software Configuration 1-9
Task 7.1: Indicate Type of Build 1-9
Task 7.2: Receive the Target Snapshot Into the Host Database
Task 7.3: Resolve Discrepancies 1-10
1-9
2. Creating an Alternate System Volume and Adding and
Deleting Logical Targets
Creating an Alternate System Volume 2-1
Adding Additional Logical Targets 2-2
Deleting a Logical Target 2-3
3. Updating a System’s Software Configuration
Procedure 1: Receive the Software Into the Archive 3-1
Preliminary Task 1: Save the Existing Configuration Database 3-1
Preliminary Task 2: Log On to DSM/SCM 3-1
Task 1: Receive Software Into the Archive 3-1
Procedure 2: Create a New Software Revision 3-2
Task 1: Review Information About Products 3-2
Task 2: Review Release Documents and Softdocs 3-3
Task 3: Create a New Software Revision 3-4
Task 4: Copy Products to the New Software Revision 3-5
Task 5: Change the Software Revision Notes 3-5
Procedures 3 and 4: Build and Apply the Configuration Revision 3-5
Task 1: Initiate the Build/Apply Request 3-5
Task 2: Indicate a Build or Build/Apply Request 3-5
Task 3: Specify the SYSnn Subvolume 3-5
Task 4: Edit the Planner Instructions to Operator 3-5
Task 5: Schedule the Request 3-6
Task 6: Set Output Options 3-6
Task 7: Set the System Generation Options 3-6
Task 8: Set Target Subvolume Locations 3-6
DSM/SCM Quick Reference Guide—529847-005
ii
3. Updating a System’s Software
Configuration (continued)
Contents
3. Updating a System’s Software Configuration (continued)
Task 9: Set File Placement Options 3-6
Task 10: Submit the Request 3-7
Task 11: Apply Software to the Target System 3-7
Task 12: Receive the Snapshot Into the Host Database 3-7
Procedure 5: Activate the New Software on the Target System 3-8
Task 1: Print the Planner Instructions to Operator 3-8
Task 2: Perform Planner Instructions to Operator 3-8
Task 3: Rename Product Files Using ZPHIRNM 3-8
Procedure 6: Renaming the Managed SYSnn (Optional) 3-9
4. Backing Out a Revision
Backing Out If DSM/SCM Is Running 4-1
Task 1: Start DSM/SCM 4-1
Task 2: Start and Log On to the Target Interface 4-1
Task 3: Perform Backout Activities 4-1
Task 4: Monitor the Backout Process 4-2
Task 5: Stop All Applications 4-2
Task 6: Rename Software Files Using ZPHIRNM 4-2
Task 7: Stop the System by Halting the Processors 4-3
Task 8: Load the System From a Saved Version of the Configuration File 4-3
Task 9: Check Processor Status 4-4
Task 10: Start TMF and Your Other Applications 4-5
Backing Out If a Previous Configuration Does Not Exist or If DSM/SCM Does Not
Run 4-6
Task 1: Run ZPHIRNM 4-6
Task 2: Stop the System by Halting the Processors 4-7
Task 3: Load the System From the Saved Configuration 4-7
Task 4: Run ZPHIRNM 4-7
Task 5: Back Out to the Previous Revision 4-7
Backing Out After Renaming the SYSnn 4-7
If the System Load and DSM/SCM Restart Succeed 4-7
If the System Load Fails or DSM/SCM Does Not Run Correctly 4-9
5. Generating Reports
Viewing a Report Online 5-1
Printing a Report 5-3
Modifying a Standard Report 5-4
Creating a System Report 5-5
DSM/SCM Quick Reference Guide—529847-005
iii
5. Generating Reports (continued)
Contents
5. Generating Reports (continued)
Creating a Custom Report
5-6
6. Managing DSM/SCM
Changing the ZDSMSCM Subvolume 6-1
Moving the ZDSMSCM Subvolume to Another Volume 6-1
Switching From One ZDSMSCM Subvolume to Another 6-1
Renaming a DSM/SCM Managed Volume 6-2
Moving a DSM/SCM Database 6-2
Moving the DSM/SCM Archive 6-3
Verifying a Target System Database 6-3
Creating a Snapshot of a Target System 6-4
DSM/SCM Quick Reference Guide—529847-005
iv
What’s New in This Manual
Manual Information
DSM/SCM Quick Reference Guide
Abstract
This guide provides concise, task-oriented procedures for configuring Distributed
Systems Management/Software Configuration Manager (DSM/SCM). It is intended for
experienced DSM/SCM users who manage and update the software configuration on
HP NonStop™ systems.
Product Version
DSM/SCM G02
DSM/SCM H02
Supported Release Version Updates (RVUs)
This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all
subsequent H-series RVUs, and G06 and all subsequent G-series RVUs, until
otherwise indicated by its replacement publications.
Part Number
Published
529847-005
May 2008
Document History
Part Number
Product Version
Published
520611-005
DSM/SCM D31 and D46
December 2003
520611-006
DSM/SCM D31 and D46
April 2004
520611-007
DSM/SCM D31 and D46
December 2004
529847-003
DSM/SCM G01 (ABP) and H01
July 2005
529847-005
DSM/SCM G02 and H02
May 2008
DSM/SCM Quick Reference Guide—529847-005
v
New and Changed Information
What’s New in This Manual
New and Changed Information
Changes in the H06.14/J06.03 manual:
•
•
Added a new checkpoint in the Task 1: Configure the DSM/SCM System
Environment on page 1-2.
Supported release statements have been updated to include J-series RVUs.
Changes to the 520611.007 Manual
•
•
Remove D-series information
Add a system load procedure for NonStop NS-series systems
DSM/SCM Quick Reference Guide—529847-005
vi
About This Guide
This guide provides experienced DSM/SCM users with concise procedures for
common DSM/SCM tasks that involve configuring DSM/SCM and using DSM/SCM to
manage software configuration.
Who Should Use This Guide
Only experienced DSM/SCM users should use this guide. If you have not performed a
certain task before, use the DSM/SCM User’s Guide at least the first time.
This guide provides only a concise, quick view of common procedures. It does not
explain how to perform basic tasks or how to decide which options to perform. Also, it
does not explain some of the less common DSM/SCM tasks. If a procedure in this
guide does not provide sufficient information for you, see the corresponding section of
the DSM/SCM User’s Guide.
What’s in This Guide
This guide contains concise procedures for performing common DSM/SCM tasks. The
procedures correspond directly to this information:
DSM/SCM Quick Reference
Guide
DSM/SCM User’s Guide
Section 1, Configuring a Host or
Physical Target System
Section 5, Configuring DSM/SCM
Section 2, Creating an Alternate
System Volume and Adding and
Deleting Logical Targets
Section 5, Configuring DSM/SCM
Section 3, Updating a System’s
Software Configuration
Part III, Installing Software Updates
Section 4, Backing Out a Revision
Section 16, Backing Out a Revision
Section 5, Generating Reports
Section 18, Generating DSM/SCM Reports
Section 6, Managing DSM/SCM
Section 17, Managing DSM/SCM
DSM/SCM Quick Reference Guide—529847-005
vii
Other DSM/SCM Information Sources
About This Guide
Other DSM/SCM Information Sources
The provides detailed step-by-step procedures for performing the various tasks
possible through each of the DSM/SCM interfaces and tools. It also provides an
overview of using the DSM/SCM interfaces and tools, organizing your DSM/SCM
usage, and making system and personnel assignments.
The DSM/SCM Messages Manual provides detailed cause, effect, and recovery
information for messages that might arise while you use DSM/SCM.
The DSM/SCM Online Help provides context-sensitive information about using the
interfaces. Online help is available for the Planner Interface, the Maintenance
Interfaces, the Target Interface, and CNFGINFO.
The DSM/SCM Event Management Programming Manual provides information about
the token-oriented event messages from the programmatic interface to DSM/SCM. It is
a reference manual for DSM/SCM event message token information and for
programmers writing applications and filters to select DSM/SCM event messages.
Notation Conventions
Hypertext Links
Blue underline is used to indicate a hypertext link within text. By clicking a passage of
text with a blue underline, you are taken to the location described. For example:
This requirement is described under Backup DAM Volumes and Physical Disk
Drives on page 3-2.
General Syntax Notation
This list summarizes the notation conventions for syntax presentation in this manual.
UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words. Type
these items exactly as shown. Items not enclosed in brackets are required. For
example:
MAXATTACH
lowercase italic letters. Lowercase italic letters indicate variable items that you supply.
Items not enclosed in brackets are required. For example:
file-name
computer type. Computer type letters within text indicate C and Open System Services
(OSS) keywords and reserved words. Type these items exactly as shown. Items not
enclosed in brackets are required. For example:
myfile.c
DSM/SCM Quick Reference Guide—529847-005
viii
General Syntax Notation
About This Guide
italic computer type. Italic computer type letters within text indicate C and Open
System Services (OSS) variable items that you supply. Items not enclosed in brackets
are required. For example:
pathname
[ ] 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 can 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. For example:
FC [ num ]
[ -num ]
[ text ]
K [ X | D ] address
{ } Braces. A group of items enclosed in braces is a list from which you are required to
choose one item. The items in the list can 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. For example:
LISTOPENS PROCESS { $appl-mgr-name }
{ $process-name }
ALLOWSU { ON | OFF }
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
INSPECT { OFF | ON | SAVEABEND }
… Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you
can repeat the enclosed sequence of syntax items any number of times. For example:
M address [ , new-value ]…
[ - ] {0|1|2|3|4|5|6|7|8|9}…
An ellipsis immediately following a single syntax item indicates that you can repeat that
syntax item any number of times. For example:
"s-char…"
Punctuation. Parentheses, commas, semicolons, and other symbols not previously
described must be typed as shown. For example:
error := NEXTFILENAME ( file-name ) ;
LISTOPENS SU $process-name.#su-name
DSM/SCM Quick Reference Guide—529847-005
ix
Notation for Messages
About This Guide
Quotation marks around a symbol such as a bracket or brace indicate the symbol is a
required character that you must type as shown. For example:
"[" repetition-constant-list "]"
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, no
spaces are permitted between the period and any other items:
$process-name.#su-name
Line Spacing. If the syntax of a command is too long to fit on a single line, each
continuation line is indented three spaces and is separated from the preceding line by
a blank line. This spacing distinguishes items in a continuation line from items in a
vertical list of selections. For example:
ALTER [ / OUT file-spec / ] LINE
[ , attribute-spec ]…
!i and !o. In procedure calls, the !i notation follows an input parameter (one that passes data
to the called procedure); the !o notation follows an output parameter (one that returns
data to the calling program). For example:
CALL CHECKRESIZESEGMENT (
segment-id
, error
) ;
!i
!o
!i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that both
passes data to the called procedure and returns data to the calling program). For
example:
error := COMPRESSEDIT ( filenum ) ;
!i:i.
!i,o
In procedure calls, the !i:i notation follows an input string parameter that has a
corresponding parameter specifying the length of the string in bytes. For example:
error := FILENAME_COMPARE_ (
filename1:length
, filename2:length ) ;
!i:i
!i:i
!o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a
corresponding input parameter specifying the maximum length of the output buffer in
bytes. For example:
error := FILE_GETINFO_ (
filenum
, [ filename:maxlen ] ) ;
!i
!o:i
Notation for Messages
This list summarizes the notation conventions for the presentation of displayed
messages in this manual.
DSM/SCM Quick Reference Guide—529847-005
x
Notation for Messages
About This Guide
Bold Text. Bold text in an example indicates user input typed at the terminal. For example:
ENTER RUN CODE
?123
CODE RECEIVED:
123.00
The user must press the Return key after typing the input.
Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or
returned exactly as shown. For example:
Backup Up.
lowercase italic letters. Lowercase italic letters indicate variable items whose values are
displayed or returned. For example:
p-register
process-name
[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. For
example:
Event number = number [ Subject = first-subject-value ]
A group of items enclosed in brackets is a list of all possible items that can be
displayed, of which one or none might actually be displayed. The items in the list can
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. 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 can 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. For example:
obj-type obj-name state changed to state, caused by
{ Object | Operator | Service }
process-name State changed from old-objstate to objstate
{ Operator Request. }
{ Unknown.
}
| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in
brackets or braces. For example:
Transfer status: { OK | Failed }
DSM/SCM Quick Reference Guide—529847-005
xi
Change Bar Notation
About This Guide
% Percent Sign. A percent sign precedes a number that is not in decimal notation. The
% notation precedes an octal number. The %B notation precedes a binary number.
The %H notation precedes a hexadecimal number. For example:
%005400
%B101111
%H2F
P=%p-register E=%e-register
Change Bar Notation
Change bars are used to indicate substantive differences between this manual and its
preceding version. Change bars are vertical rules placed in the right margin of
changed portions of text, figures, tables, examples, and so on. Change bars highlight
new or revised information. For example:
The message types specified in the REPORT clause are different in the COBOL85
environment and the Common Run-Time Environment (CRE).
The CRE has many new message types and some new message type codes for old
message types. In the CRE, the message type SYSTEM includes all messages
except LOGICAL-CLOSE and LOGICAL-OPEN.
DSM/SCM Quick Reference Guide—529847-005
xii
1
Configuring a Host or Physical
Target System
This section describes configuring DSM/SCM on a system. For more information on
configuring and initializing DSM/SCM, see the DSM/SCM User’s Guide.
Before you use this procedure, check that the system name and number are set to
where you want to keep them.
Preliminary Task: Install the DSM/SCM PC
Files
If DSM/SCM is not already installed on your PC or if you are installing a newer version
of DSM/SCM, you must complete this task. This task assumes you are using Winsock.
For more information, see the DSM/SCM User’s Guide.
Task 0.1: Ensure TCPIP and LISTNER Are Installed
Ensure that the TCPIP file and its LISTNER program are installed in the current host
system SYSnn subvolume. To determine what SYSnn is running, on the host system:
> sysinfo
Task 0.2: Transfer DSM/SCM PC Files From the SUT to the PC
1. On the host system, make ZDSMSCM the current subvolume:
> VOLUME $volume.ZDSMSCM
2. Using IXF or a similar method, copy the ZDSMEXE file from the ZDSMSCM
subvolume on the HP NonStop host to a subdirectory called \DSMSCM on the PC.
The subdirectory can be on any drive with sufficient space. Place the file in an
empty folder and directory.
3. Rename the file ZDSM.EXE.
4. Double-click the ZDSM.EXE file to decompress the DSM/SCM files you just
transferred to your PC.
Task 0.3: Ensure Winsock Is Installed
Ensure Winsock is installed on the PC and that WINSOCK.DLL is in the \WIN,
\WINDOWS, or another directory.
DSM/SCM Quick Reference Guide—529847-005
1 -1
Configuring a Host or Physical Target System
Task 0.4: Run SETUP.EXE
Task 0.4: Run SETUP.EXE
1. Double-click the SETUP.EXE file in the DSMSCM directory.
DSM/SCM displays the Setup Logo screen followed by licensing information, then
opens a series of dialog boxes.
2. Enter the Object Manager server class name if needed; then click OK.
3. Enter the Software Product Group type (Shared or Private); then click OK.
4. Enter the CNFGINFO process name if needed; then click OK.
SETUP asks whether you will use RSC or Winsock.
5. Click the Winsock button; then click OK.
SETUP asks for the full path name of the WINSOCK.DLL file.
6. Enter the full path name of the WINSOCK.DLL file.
7. Enter the IP address or name of the host system; then click OK.
8. Enter the IP port number for the DSM/SCM Winsock service; then click OK.
9. Enter the host system name; then click OK.
SETUP updates the DSMSCM.INI file on your PC with the information you entered.
10. Indicate no when prompted to start the Planner Interface.
Task 1: Configure the DSM/SCM System
Environment
You must use INITENV if you are changing:
•
•
•
•
•
•
•
•
The system name or number
A host system to a target system (can change only once)
The DSM/SCM database and Pathway environment owner
The DSM/SCM hometerm
The host system interface to the PC from Winsock to RSC
The HP NonStop Transaction Management Facility (TMF) volume
The SQL system catalog volume
The DSM/SCM server processes priority
This task assumes you will use Winsock, not RSC:
1. Log on to your system as the super ID (255,255).
2. Make ZDSMSCM the current subvolume; then run INITENV.
DSM/SCM Quick Reference Guide—529847-005
1 -2
Configuring a Host or Physical Target System
Task 2: Configure the Host Database
3. Provide the information INITENV prompts you for.
When you answer the last question, INITENV ends the dialog, begins processing
the information, and stops after successfully completing its tasks.
Task 2: Configure the Host Database
This task describes the steps to perform on the Planner Interface. To initialize a host
system, use the host Maintenance Interface for Task 2.1: Add and Set Planner
Security.
Task 2.1: Add and Set Planner Security
For more information, see the DSM/SCM User’s Guide.
For initializations, use the host Maintenance Interface:
1. Run the host Maintenance Interface.
2. Log on to the host Maintenance Interface using the DSM/SCM user ID or alias.
3. Select the Security Maintenance Menu (selection 3); then press F1.
DSM/SCM displays the Security Maintenance menu.
4. Select Planner Security Maintenance (selection 1).
DSM/SCM displays the Planner Security Maintenance screen.
5. Follow the instructions on the Planner Security Maintenance screen to add
planners and to specify their permissions.
6. When all planners are added, press F16.
DSM/SCM returns to the Security Maintenance menu.
If you are not initializing a system but want to add or change planner security:
1. Run and log on to the Planner Interface, using the DSM/SCM user ID.
2. Select Maintain>Security Maintenance>Planner list.
3. To add a planner, click the Add button.
4. Select the DSM/SCM activities the planner is permitted to perform.
5. Click OK.
Task 2.2: Update the System Profile
For more information, see the DSM/SCM User’s Guide. Perform this task when you are
adding a system.
1. Choose Maintain>System Maintenence>Add.
DSM/SCM Quick Reference Guide—529847-005
1 -3
Configuring a Host or Physical Target System
Task 2.3: Update Host System Volume Usage
2. Review the system information and enter the default values.
3. Click OK.
Task 2.3: Update Host System Volume Usage
For more information, see the DSM/SCM User’s Guide.
1. Select the system you are configuring from the Configuration Revisions window.
2. Select Maintain>Volume Maintenance... and review the host system volume
usage.
To change volume usage:
1. Select the volume name you want to change volume usage for.
2. Click the Change Usage button.
3. Click OK to submit the changes.
4. Click OK to exit.
Task 2.4: Set Security for Host Database Administrators
For more information, see the DSM/SCM User’s Guide.
1. If not already highlighted, select the system you are configuring from the
Configuration Revisions window.
2. Select Maintain>Security Maintenance>DB Admninistrator list.
3. To review or modify a database administrator’s profile:
a. Select a database administrator user ID or alias from the list.
b. Click the Modify button.
c. Set activities the database administrator can perform.
d. Click OK.
4. To add a database administrator:
a. Click the Add button.
b. Type a database administrator user ID or alias to add.
c. Set activities the database administrator can perform.
d. Click OK to exit.
5. Close the window when you are finished reviewing the database administrator list.
DSM/SCM Quick Reference Guide—529847-005
1 -4
Configuring a Host or Physical Target System
Task 2.5: Update the Configuration Manager Profile
Task 2.5: Update the Configuration Manager Profile
For more information, see the DSM/SCM User’s Guide.
1. Select the system you are configuring from the Configuration Revisions window.
2. Select Maintain>Configuration Manager.
3. Review and change information as needed.
4. Click OK to exit.
Task 2.6: Move the Archive (Optional)
For more information, see the DSM/SCM User’s Guide.
1. Run and log on to the host Maintenance Interface.
2. Select Archive Relocation (selection 8); then press F1.
DSM/SCM displays the Archive Relocation screen.
3. Enter the current node (optional) and volume in the From field.
4. Enter the new node (optional) and volume in the To field.
5. Press F1.
DSM/SCM changes the archive volume. The move might take several minutes to
complete.
6. Press F16.
DSM/SCM returns to the main menu.
7. Press Shift-F16 to exit the host Maintenance Interface.
DSM/SCM Quick Reference Guide—529847-005
1 -5
Configuring a Host or Physical Target System
Task 3: Configure the Target Database
Task 3: Configure the Target Database
You must run and log on to the target Maintenance Interface to perform this task.
Task 3.1: Update the Target Profile
For more information, see the DSM/SCM User’s Guide.
1. Select System Maintenance (selection 1); then press F1.
DSM/SCM displays the System Maintenance screen.
2. Enter the system name; then press F2.
3. Review the system information and change the default values, as needed.
4. Press Shift-F2 to enter any changes.
5. Press F16.
DSM/SCM returns to the Maintenance Interface main menu.
Task 3.2: Update Target Volume Usage
For more information, see the DSM/SCM User’s Guide.
1. Select Volume Maintenance (selection 2); then press F1.
DSM/SCM displays the Volume Maintenance screen.
2. Specify the volume usage.
3. Press Shift-F2 to enter the data.
4. Press F16 to return to the main menu.
Task 3.3: Add and Set Security for Operators
For more information, see the DSM/SCM User’s Guide.
1. Select Security Maintenance Menu (selection 3); then press F1.
DSM/SCM displays the Security Maintenance menu.
2. Select Operator Security Maintenance (selection 1); then press F1.
3. Follow the instructions on the Operator Security Maintenance screen to add
operators to DSM/SCM and to specify their permissions.
4. When all operators are added, press F16.
DSM/SCM returns to the Security Maintenance menu.
DSM/SCM Quick Reference Guide—529847-005
1 -6
Configuring a Host or Physical Target System
Task 3.4: Add and Set Security for Target Database
Administrators
Task 3.4: Add and Set Security for Target Database
Administrators
For more information, see the DSM/SCM User’s Guide.
1. Select Database Administrator Security Maintenance (selection 2); then press F1.
2. Follow the instructions on the Database Administrator Security Maintenance
screen to add target database administrators to DSM/SCM and to specify their
permissions.
3. After you add all database administrators, press F16 twice.
DSM/SCM returns to the Maintenance Interface main menu.
4. Press Shift-F16 to exit the target Maintenance Interface.
Task 4: Modify Profile Information for the
Logical Target
You must run and log on to the Planner Interface to perform this task. The main
Planner Interface screen displays the Software in Archive and Configuration Revisions
windows.
Task 4.1: Update the Target Profile
For more information, see the DSM/SCM User’s Guide.
1. In the Configuration Revisions window, select the configuration name for the target.
2. Select Maintain>Target maintenance>Modify....
DSM/SCM displays the Target Information dialog box.
3. Change the description of the target if necessary.
4. Select the Manage OSS Files check box to manage OSS files on this target. If you
are not managing OSS files, make sure that the box is cleared.
5. Change the target output and system generation values if necessary.
6. Click OK.
DSM/SCM returns to the Configuration Revisions window.
Task 5: Initialize the Target on the System
If you are creating the initial configuration for the target on the host or physical target
system, perform this task. To perform this task, you must log on to the Planner
Interface.
DSM/SCM Quick Reference Guide—529847-005
1 -7
Configuring a Host or Physical Target System
Task 5.1: Register the Target
Task 5.1: Register the Target
1. In the Configuration Revisions window, select the configuration name for the target.
For a new target, the name has the form:
\system_name DEFAULT
2. Select Maintain>Target maintenance>Initialize target system.
3. Click Profile.
4. Enter a descriptive target name.
5. Select the Manage OSS Files check box if you will manage OSS files on this
target. If you are not managing OSS files, you must make sure that the box is
cleared.
Task 5.2: Set Target Output Defaults
1. Change the target output and system generation values if necessary.
a. Click Output....
DSM/SCM displays the Output Defaults dialog box.
b. Enter values in the data fields as needed.
c. Click OK.
DSM/SCM returns to the Target Information dialog box.
Task 5.3: Set Target System Generation Defaults
1. Change the target system generation values if necessary.
a. Click SYSGEN....
DSM/SCM displays the SYSGEN Defaults dialog box.
b. Enter values in the data fields as needed.
c. Click OK.
DSM/SCM returns to the Target Information dialog box.
2. Click OK in the Target Information dialog box.
DSM/SCM returns to the Configuration Revisions window.
Task 6: Receive Software
Task 6.1: Receive Software
1. Load the SUT onto the tape drive.
DSM/SCM Quick Reference Guide—529847-005
1 -8
Configuring a Host or Physical Target System
Task 6.2: Create Software Revision
2. Click the Software in Archive window.
3. Receive software into the Archive. For more information on how to receive the
software, see Section 3, Updating a System’s Software Configuration.
4. After you receive software into the archive, select the target from the Configuration
Revisions window.
5. Select Maintain>Target maintenance>Initialize target system.
Task 6.2: Create Software Revision
1. Click Software....
DSM/SCM displays an empty New Revision window.
2. On the Software in Archive window, select the SUT that contains the software on
which the target is currently running; then click Copy to.
DSM/SCM copies the contents of the SUT to the new revision.
3. Click Build/Apply....
DSM/SCM saves the new software revision and displays the Indicate Type of Build
dialog box.
Task 7: Build/Apply Software Configuration
Task 7.1: Indicate Type of Build
1. Select one of the two buttons to indicate whether you will send an initialization
package or a full activation package to the logical target on the host system.
2. Click OK.
DSM/SCM displays the Build/Apply Request dialog box.
3. Click Scheduling... to schedule the request if necessary.
4. Click OK.
5. If Manage OSS Files is selected for this logical target, DSM/SCM displays a
message verifying that it will manage OSS files on this logical target.
6. Click OK. DSM/SCM processes the request as scheduled.
Task 7.2: Receive the Target Snapshot Into the Host Database
If you created a Build/Apply request, this task was performed automatically:
From the Initialize Target System dialog box, click Snapshot....
DSM/SCM Quick Reference Guide—529847-005
1 -9
Configuring a Host or Physical Target System
Task 7.3: Resolve Discrepancies
Task 7.3: Resolve Discrepancies
If you applied a full activation package instead of an initialization package, this task is
not necessary.
1. From the Initialize Target System dialog box, click Discrepancies....
DSM/SCM displays the Prepare Request dialog box.
2. Change the system name run-time parameter:
a. Select the parameter; then click Modify parameter....
b. On the Modify Parameter Value dialog box, enter the name of the configuration
in the Value field.
c. Click OK.
DSM/SCM returns to the Prepare Request dialog box.
d. Prepare the report for printing or online viewing; then click OK to submit the
Prepare Report request.
If there are no discrepancies:
DSM/SCM displays the No Software Discrepancies dialog box.
1. Click Yes to mark the system as initialized.
DSM/SCM displays the Initialized Target dialog box.
2. Click OK.
Initialization is now complete.
3. Select File>Exit.
DSM/SCM exits the Planner Interface.
Configuration of the host system and its logical target is now complete.
If there are discrepancies:
DSM/SCM displays the Software Discrepancies Found dialog box.
1. Create a discrepancy report:
a. Click Report request....
DSM/SCM displays the Prepare Report Request dialog box.
b. Select Discrepancy from the reports list.
c. Click Continue....
DSM/SCM displays the Prepare Report dialog box.
d. Change the system name run-time parameter.
DSM/SCM Quick Reference Guide—529847-005
1- 10
Configuring a Host or Physical Target System
Task 7.3: Resolve Discrepancies
2. Resolve the discrepancies.
Note. You are not required to resolve discrepancies to continue. You only need to be aware of
the differences and understand what they mean when the next configuration is applied.
a. From the Initialize Target System dialog box, click Software....
DSM/SCM displays the product list.
b. Change the product list so that it matches the software on the target
system. Include software product revisions (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.)
c. Rerun the discrepancy report to see if all discrepancies are resolved.
d. Repeat these steps until no discrepancies remain.
e. When no discrepancies remain, perform another Build/Apply of the
modified software revision.
3. Select File>Exit.
DSM/SCM exits the Planner Interface.
Configuration of the host system and its logical target is now complete.
DSM/SCM Quick Reference Guide—529847-005
1- 11
Configuring a Host or Physical Target System
Task 7.3: Resolve Discrepancies
DSM/SCM Quick Reference Guide—529847-005
1- 12
2
Creating an Alternate System
Volume and Adding and Deleting
Logical Targets
This section describes adding and deleting logical targets from a DSM/SCM host or
target system, and adding an alternate $SYSTEM:
Procedure
Page
Creating an Alternate System Volume
2-1
Adding Additional Logical Targets
2-2
Deleting a Logical Target
2-3
Considerations
Before adding additional logical targets, remember that:
•
•
•
•
You cannot maintain more than six logical targets on a single system.
Each logical target requires its own $SYSTEM and a unique alternate volume. The
primary volume name for each logical target must be $SYSTEM, and the alternate
volume name for each of these targets must be different to differentiate between
the disks.
Each time you switch from one logical target to another, you must perform a
system load.
You cannot perform an initialization Build/Apply if it has been previously performed
on any other logical target created on that particular physical target system.
Creating an Alternate System Volume
1. Change the primary volume name to $SYSTEM. See these manuals:
•
•
NonStop NS-Series Hardware Installation Guide
NonStop S-Series Hardware Installation and Fast Path Guide
For more information on the SCF ALTER DISK command, see the SCF Reference
Manual for the Storage Subsystem.
DSM/SCM Quick Reference Guide—529847-005
2 -1
Creating an Alternate System Volume and Adding
and Deleting Logical Targets
Adding Additional Logical Targets
2. Run Verify Database from the Target Interface. (See Verifying a Target System
Database on page 6-3.).
Note. If $DATA00 is a scratch volume, Verify Database stops in a restartable state. If
$DATA00 is an archive volume, after successful completion of Verify Database,
update the volume usage information using the Target and Host Maintenance
Interface.
For details, see the DSM/SCM User’s Guide.
3. Create an independent snapshot. (See Creating a Snapshot of a Target System on
page 6-4.)
4. Add a logical target system for the alternate system volume.
5. Perform a Build/Apply for the alternate system volume.
6. For the remaining steps, return to these manuals:
•
•
NonStop NS-Series Hardware Installation Guide
NonStop S-Series Hardware Installation and Fast Path Guide
Adding Additional Logical Targets
For more information, see the DSM/SCM User’s Guide.
1. In the Configuration Revisions window, select the system to which you are adding
the new logical target.
2. Select Maintain>Target maintenance>Add....
3. In the New Target dialog box, enter a name for the new logical target in the Target
name field. When creating multiple logical targets, distinguish targets by using
meaningful names.
4. In the Copy profile data from list, select another logical target from which to copy
profile data.
5. Click Setup....
DSM/SCM displays the Target Information dialog box.
6. Enter a description of the target in the Target description field.
7. Change the profile output defaults as needed:
a. Click Output....
DSM/SCM displays the Output Defaults dialog box.
b. Enter values in the data fields as needed.
c. Click OK.
8. Change the profile system generation defaults:
DSM/SCM Quick Reference Guide—529847-005
2 -2
Creating an Alternate System Volume and Adding
and Deleting Logical Targets
Deleting a Logical Target
a. Click SYSGEN....
DSM/SCM displays the SYSGEN Defaults dialog box.
b. Enter values in the data fields as needed.
c. Click OK.
9. Click OK in the Target Information dialog box.
The new logical target is now defined to DSM/SCM, and its name appears on the
Configuration Revisions window with a revision number of 1.
Note. If you are using multiple targets on a system, always run DSM/SCM from the first
ZDSMSCM subvolume installed on the target system. To ensure that the correct installation
files are used, this ZDSMSCM subvolume must also be the one from which INITENV was run.
After the new logical target is defined, you can modify the product list as necessary.
Then build and apply its initial revision, as described in the DSM/SCM User’s Guide.
Deleting a Logical Target
You can remove a logical target, its profile information, and all of its associated
software revisions from DSM/SCM by first deleting the logical target from the host and
then deleting the logical target from the target system. For more information, see the
DSM/SCM User’s Guide.
Deleting a Logical Target From a Host System
After you delete a logical target from the host, it no longer appears in the Configuration
Revisions window. From the Planner Interface:
1. Select a configuration revision from the Configuration Revisions window.
2. Select Maintain>Target maintenance>Delete....
Deleting a Logical Target From a Target System
Deleting the logical target from the host does not delete the logical target from the
target system. You must delete the logical target itself from the target system:
1. Check that ZDSMSCM is the current subvolume; then run the Target Interface:
> VOLUME $volume.ZDSMSCM
> RUN ZPHITI
2. Log on to the Target Interface.
3. Select 3 (Perform target activities); then press F1.
4. Select a target; then press F1. The current SYSnn appears at the top of the next
screen. Note the SYSnn.
DSM/SCM Quick Reference Guide—529847-005
2 -3
Creating an Alternate System Volume and Adding
and Deleting Logical Targets
Deleting a Logical Target
5. Press Shift-F16 to exit the Target Interface.
6. Purge the entire SYSnn or purge only the ZPHI6030 file in this SYSnn.
7. Run Verify Database from the Target Interface. (See Verifying a Target System
Database on page 6-3.)
DSM/SCM Quick Reference Guide—529847-005
2 -4
3
Updating a System’s Software
Configuration
This section describes placing new software on a system. This procedure is valid for
configuring RVUs, SPRs, and third-party software.
Procedure 1: Receive the Software Into the
Archive
Preliminary Task 1: Save the Existing Configuration Database
1. Run SCF.
2. Save the current system configuration.
Preliminary Task 2: Log On to DSM/SCM
1. Determine the current SYSnn.
2. Start TMF if it is not already running.
3. Start DSM/SCM if it is not already running.
4. On your host PC, double-click the DSMSCM icon to start the Planner Interface.
5. Log on to the Planner Interface using the super ID (255,255) or a planner ID.
DSM/SCM displays the main Planner Interface screen.
Task 1: Receive Software Into the Archive
1. Click Receive software... in the Software in Archive window.
DSM/SCM displays the Receive Software Request dialog box.
2. Enter a description of the software input in the Request description field.
3. Enter a name for the software input in the Software name box.
4. Select Receive only changed files or Receive all files in the Receive Options
box.
5. Click Input source....
DSM/SCM displays the Request Source Options dialog box.
6. Indicate the type of input source.
DSM/SCM Quick Reference Guide—529847-005
3 -1
Updating a System’s Software Configuration
Procedure 2: Create a New Software Revision
If the source is a tape that has an external physical label, enter the ID in the
Optional external tape ID box.
7. Click OK.
DSM/SCM returns to the Receive Software Request dialog box.
8. Click Scheduling....
DSM/SCM displays the Request Scheduling Options dialog box.
9. Schedule the request; then click OK.
DSM/SCM returns to the Receive Software Request dialog box.
10. Click OK.
DSM/SCM closes the Receive Software Request dialog box and processes the
request as scheduled.
11. After the request has run, select Window>Refresh.
The name of the new input appears in the Software in Archive window.
Procedure 2: Create a New Software Revision
Task 1: Review Information About Products
1. Double-click a configuration in the Configuration Revisions window.
DSM/SCM displays the list of products for the selected configuration.
2. List the files belonging to a product in an existing revision.
a. Select a product in the existing revision.
b. Select Products>List files....
DSM/SCM displays the Files dialog box.
3. View the version details of a product.
a. Select a product in the existing revision.
b. Select Products>List version details....
DSM/SCM displays the Version Detail dialog box.
4. List the files belonging to an SPR.
a. Select an SPR in the Version Detail dialog box.
b. Click List files....
5. View software revision notes for an existing revision.
a. Select a configuration revision in the Configuration Revisions window.
DSM/SCM Quick Reference Guide—529847-005
3 -2
Updating a System’s Software Configuration
Task 2: Review Release Documents and Softdocs
b. Select File>Show revision notes....
Task 2: Review Release Documents and Softdocs
This task assumes you will view softdocs and release documents online instead of
printing them.
Task 2.1: View Release Documents
NonStop S-series system and Integrity NonStop system users should also review this
release documentation for the appropriate release version update (RVU):
•
•
•
Gxx.xx Software Installation and Upgrade Guide
Hxx.xx Software Installation and Upgrade Guide
Interactive Upgrade Guide 2
1. In the Software in Archive window, select the input name of the SUT.
2. Select Requests>Prepare release documents....
DSM/SCM displays the Prepare Release Documents Request dialog box.
3. Check the Viewable formatted file subvolume location check box.
4. Click OK.
DSM/SCM prepares and formats the documents for online viewing and adds them
to the list of prepared documents.
5. Select File>View prepared documents....
DSM/SCM displays a list of reports and documents that have been prepared for
online viewing.
6. Select a release document from the list.
7. Click View.
DSM/SCM displays the selected document.
Task 2.2: View Softdocs for Changed Products
1. Open an existing target by double-clicking its name in the Configuration Revisions
window.
DSM/SCM displays a window for the revision listing the existing software.
2. Open the new software input by double-clicking its name in the Software in Archive
window.
DSM/SCM displays a window for the input listing the software in the input.
3. Click Select changes in the window of the software input.
DSM/SCM Quick Reference Guide—529847-005
3 -3
Updating a System’s Software Configuration
Task 3: Create a New Software Revision
DSM/SCM highlights differences between the software input and the existing
revision.
4. Select Requests>Prepare softdocs....
DSM/SCM displays the Prepare Softdoc Request dialog box.
5. Check the Viewable formatted file subvolume location check box if it is not
already checked; then click OK.
DSM/SCM prepares and formats the softdocs for online viewing and adds them to
the list of prepared documents.
6. Select File>View prepared documents....
DSM/SCM displays a list of reports and documents that have been prepared for
online viewing.
7. Select a softdoc from the list.
8. Click View.
DSM/SCM displays the selected softdoc.
Task 3: Create a New Software Revision
Task 3.1: List the Revision History of an Existing Revision
1. Select a revision in the Configuration Revisions window.
2. Select File>Show revision history....
DSM/SCM displays the Revision History window.
3. Select a revision.
4. To list products, review revision notes, or copy products to a new revision:
•
Select Products>List products....
DSM/SCM lists the products in the software revision.
•
Click Show revision notes....
DSM/SCM displays the notes describing the revision.
•
Click Copy to to copy the products to the new software revision.
Task 3.2: Create the New Software Revision
1. In the Configuration Revisions window, select the configuration on which you are
basing the new revision.
2. Click New software revision....
DSM/SCM opens the New Software Revision window.
DSM/SCM Quick Reference Guide—529847-005
3 -4
Updating a System’s Software Configuration
Task 4: Copy Products to the New Software Revision
3. Modify the list as necessary by copying products to the new software revision.
Task 4: Copy Products to the New Software Revision
1. Select software in the Software in Archive window.
2. Click Copy to.
Task 5: Change the Software Revision Notes
1. In the New Software Revision window, click Edit revision notes....
DSM/SCM displays the Revision Notes dialog box. The dialog box shows the notes
previously entered for the revision upon which the new one is based.
2. Enter text in the box.
3. Click OK.
Procedures 3 and 4: Build and Apply the
Configuration Revision
Task 1: Initiate the Build/Apply Request
In the New Software Revision window, click Build/Apply....
DSM/SCM displays the Build/Apply Request dialog box.
Task 2: Indicate a Build or Build/Apply Request
Indicate under Perform Steps whether this is a Build request or a Build, apply &
process snapshot request.
Task 3: Specify the SYSnn Subvolume
1. Click List SYSnn....
DSM/SCM displays a scrollable list of the SYSnns currently in use.
2. Select a SYSnn; then click OK.
DSM/SCM returns you to the Build/Apply Request dialog box.
Task 4: Edit the Planner Instructions to Operator
1. Click Edit instructions....
DSM/SCM displays the Planner Instructions dialog box.
2. Change the text in the space provided; then click OK.
DSM/SCM Quick Reference Guide—529847-005
3 -5
Updating a System’s Software Configuration
Task 5: Schedule the Request
DSM/SCM returns you to the Build/Apply Request dialog box.
Task 5: Schedule the Request
1. Click Scheduling....
DSM/SCM displays the Request Scheduling Options dialog box.
2. In the Build portion of the dialog box, schedule the Build.
3. In the Apply portion of the dialog box, schedule the Apply; then click OK.
DSM/SCM returns you to the Build/Apply Request dialog box.
Task 6: Set Output Options
1. Click Output....
DSM/SCM displays the Output Options dialog box.
2. Change the information shown in the dialog box options as needed; then click OK.
DSM/SCM returns you to the Build/Apply Request dialog box.
Task 7: Set the System Generation Options
1. Click SYSGEN....
DSM/SCM displays the SYSGEN Options dialog box.
2. Change the information shown on the dialog box as needed; then click OK.
DSM/SCM returns you to the Build/Apply Request dialog box.
Task 8: Set Target Subvolume Locations
1. Click TSV Location....
DSM/SCM displays the TSV Locations dialog box.
2. Change the information shown in the dialog box as needed; then click OK.
DSM/SCM returns you to the Build/Apply Request dialog box.
Task 9: Set File Placement Options
1. Click File Placement....
DSM/SCM displays the File Placement Options dialog box.
2. Indicate where files are to be retrieved from, which files will be replaced, and which
files will be transferred to the target from the given options.
3. Click OK.
DSM/SCM Quick Reference Guide—529847-005
3 -6
Updating a System’s Software Configuration
Task 10: Submit the Request
Task 10: Submit the Request
Click OK to submit the request.
DSM/SCM begins the appropriate processes. Depending on the size of software
changes, this could take several hours.
Task 11: Apply Software to the Target System
If you submitted a Build/Apply request, the apply and receive snapshot processes run
automatically. Proceed to Procedure 5: Activate the New Software on the Target
System.
1. From the Target Interface on the target system, retrieve the planner instructions to
operator.
a. At the main menu, enter 3; then press F1.
DSM/SCM displays the Target Menu - Select Target screen.
b. Enter the number for the logical target; then press F1.
DSM/SCM displays the Target Menu - Select Action screen.
c. Enter 1; then press F1.
DSM/SCM displays the S/W Apply - Get Operator Instructions screen.
d. Enter the location of the activation package; then press F1.
DSM/SCM retrieves the operator instructions from the activation package and
displays the S/W Apply - Getting Instructions screen. When finished,
DSM/SCM displays the S/W Apply - Submit Apply screen.
2. Press F9.
DSM/SCM prints the planner instructions to operator.
3. Carry out the operator instructions for running the Apply.
4. Verify that all data fields on the S/W Apply - Submit Apply screen are correct.
5. Change data fields as necessary.
6. Press F1.
DSM/SCM applies the software.
7. Monitor the status of the Apply.
8. When the Apply is completed, transfer the snapshot to the host system.
Task 12: Receive the Snapshot Into the Host Database
1. On the Configuration Revisions window in the Planner Interface, select the target.
DSM/SCM Quick Reference Guide—529847-005
3 -7
Updating a System’s Software Configuration
Procedure 5: Activate the New Software on the
Target System
2. Select Requests>Receive snapshot....
DSM/SCM displays the Receive Snapshot Request dialog box.
3. Click File or Tape. The default input location appears.
4. Specify the exact input location; then click OK.
DSM/SCM receives the snapshot into the host database.
Procedure 5: Activate the New Software on the
Target System
Task 1: Print the Planner Instructions to Operator
1. In the Target Interface main menu, enter 3 in the Selection number field; press F1.
DSM/SCM displays the Target Menu - Select Target screen.
2. Enter the number for the logical target on which you want to activate software in
the Selection number field; then press F1.
DSM/SCM displays the Target Menu - Select Action screen.
3. Enter 3 in the Selection number field; then press F1.
DSM/SCM displays the operator instructions.
4. Print the operator instructions. Verify the output location; then press F9.
5. Press Shift-F16 to exit the Target Interface.
Task 2: Perform Planner Instructions to Operator
1. Stop all applications:
a. Stop DSM/SCM.
b. Stop all other applications.
c. Stop TMF.
2. Perform all specified operator instructions, including running ZPHIRNM. (These
instructions vary based on each release and planner input at each workplace.)
3. Restart all applications:
a. Start TMF.
b. Start all other applications.
Task 3: Rename Product Files Using ZPHIRNM
When indicated by the operator instructions:
DSM/SCM Quick Reference Guide—529847-005
3 -8
Updating a System’s Software Configuration
Procedure 6: Renaming the Managed SYSnn
(Optional)
1. Check that you are in the target system ZDSMSCM subvolume.
2. Review the detailed list of every file that ZPHIRNM will rename.
3. Run ZPHIRNM in PREVIEW mode:
> RUN ZPHIRNM [$vol.]SYSnn , PREVIEW [STRICT] [,option]...
4. If the process generates errors, correct them and run ZPHIRNM in PREVIEW
mode again. When no errors remain, continue.
5. Run ZPHIRNM with the appropriate extensions (without PREVIEW).
If you did not specify a log file, a prompt asks whether to use a log file.
6. Enter Y; then press Enter.
A prompt requests a log file name.
7. Enter a disk file name.
A prompt indicates the log file was created. ZPHIRNM issues an EMS message
when it has successfully completed.
Procedure 6: Renaming the Managed SYSnn
(Optional)
After you configure an update on a different SYSnn, you can rename that SYSnn to
the one from which you always want to load your system. For example, to always load
your system from SYS00, configure your update on SYS01; then rename SYS01 to
SYS00:
1. Perform an Apply on the new SYSnn (in this example, SYS01).
2. Run ZPHIRNM on the new SYSnn (SYS01).
3. Rename the running SYSnn (SYS00) to another unused SYSnn (SYS20).
4. Rename the running CSSnn (CSS00) to another unused CSSnn (CSS20).
5. Rename the new SYSnn (SYS01) applied by DSM/SCM to your usual SYSnn
(SYS00).
6. Rename the new CSSnn (CSS01) applied by DSM/SCM to your usual CSSnn
(CSS00).
7. Perform a system load on your usual SYSnn (SYS00), which now contains the
updated software configuration.
8. Restart DSM/SCM.
9. Update the DSM/SCM database with the new SYSnns. (You do not have to do this
immediately, but do it as soon as possible in case you need to back out to the
previous revision.)
DSM/SCM Quick Reference Guide—529847-005
3 -9
Updating a System’s Software Configuration
Procedure 6: Renaming the Managed SYSnn
(Optional)
a. Before the next Apply to the system, run Verify Database so DSM/SCM can
resolve the current names of the SYSnns. (See Verifying a Target System
Database on page 6-3.)
b. Create an independent snapshot of the target. (See Creating a Snapshot of a
Target System on page 6-4.)
c. Receive the independent snapshot into the host database.
If you have to back out after renaming the SYSnn, see Backing Out After Renaming
the SYSnn on page 4-7.
DSM/SCM Quick Reference Guide—529847-005
3- 10
4
Backing Out a Revision
This section describes backing a system out to its previous configuration revision:
Procedure
Page
Backing Out If DSM/SCM Is Running
4-1
Backing Out If a Previous Configuration Does Not Exist or If DSM/SCM Does Not
Run
4-6
Backing Out After Renaming the SYSnn
4-6
For more information, see the DSM/SCM User’s Guide.
Backing Out If DSM/SCM Is Running
Task 1: Start DSM/SCM
1. Start TMF if it is not already running.
2. Start DSM/SCM if it is not already running.
Task 2: Start and Log On to the Target Interface
1. Start the Target Interface.
DSM/SCM displays the Target Interface Logon Menu.
2. Enter your password; then press F1.
DSM/SCM displays the Target Interface Main Menu.
Task 3: Perform Backout Activities
1. Enter 3 (Perform target activities) in the Selection number field; then press F1.
DSM/SCM displays the Target Menu - Select Target screen.
2. Enter the number corresponding to the name of the target system; then press F1.
DSM/SCM displays the Target Menu - Select Action screen.
3. Enter 2 (Perform backout to S/W) in the Selection number field; then press F1.
DSM/SCM displays the Backout - Verify Request screen.
4. Press F1 to submit the Backout request.
DSM/SCM displays the Backout-Processing Backout screen. The screen is
updated with current status approximately every 15 seconds.
•
While waiting for the request to finish, you can press F4 to view current EMS
messages related to the request.
DSM/SCM Quick Reference Guide—529847-005
4 -1
Task 4: Monitor the Backout Process
Backing Out a Revision
•
If a message indicates 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 then resumes processing.
After the Backout finishes, the Backout - Complete Backout screen appears,
displaying the SYSnn, name, date, and timestamp of the activation package that
has been reapplied to the system. This screen also contains the operator
instructions originally sent for activating the current revision. These are not
necessarily the instructions to use to back out to a previous configuration. For
detailed fallback procedures for products that have changed, consult the release
documents.
5. Choose a printer to receive the instructions.
6. Press Shift-F16 to exit the Target Interface.
Task 4: Monitor the Backout Process
1. On your PC, start the Planner Interface.
2. Log on using the super ID (255,255).
DSM/SCM displays the Planner Interface main screen.
3. Select Requests>Request list.
DSM/SCM displays the Requests list screen.
4. Double-click the backout activity in the Request list.
5. Select Status details.
DSM/SCM displays the Request Activity Summary screen.
6. Monitor the backout processing by watching the timestamp in the upper-right
corner of the screen. To get an update at any time, select Show EMS events.
7. When the backout is complete, exit the Planner Interface.
Task 5: Stop All Applications
1. Stop DSM/SCM.
2. Stop all other applications.
3. Stop TMF.
Task 6: Rename Software Files Using ZPHIRNM
1. Run ZPHIRNM in PREVIEW mode:
> RUN ZPHIRNM [$vol.]SYSnn , PREVIEW [STRICT] [,option]...
If no arguments are entered, help text appears.
DSM/SCM Quick Reference Guide—529847-005
4 -2
Task 7: Stop the System by Halting the Processors
Backing Out a Revision
2. If the process generates errors, correct them and run ZPHIRNM in PREVIEW
mode again. If no errors occur, continue.
3. Run ZPHIRNM on the SYSnn for the configuration revision you are backing out to.
If you did not specify a log file, a prompt appears asking whether to use a log file.
4. Specify Y; then press Enter.
A prompt appears asking for a log file name.
5. Enter a disk file name.
A prompt indicates the log file was created. ZPHIRNM issues an EMS message
when it has successfully completed.
Task 7: Stop the System by Halting the Processors
If the configuration revision that you are backing out to does not require system
generation or a system load, skip Task 7 and 8. Proceed to Task 9.
Tasks 7 and 8 describe using OSM or TSM on a NonStop S-series server. For
NonStop NS-series systems, use OSM.
1. Log on to either the OSM or TSM Low-Level Link.
2. On the Low-Level Link toolbar, click Processor Status.
3. Shift-click to select all of the running processors.
4. From the Processor Actions list, select Halt.
5. Click Perform Action.
6. Click OK to dismiss the confirmation dialog box and initiate the action.
Task 8: Load the System From a Saved Version of the
Configuration File
The procedure to load the system varies depending on the type of system:
•
•
Loading a NonStop S-Series System on page 4-3
Loading a NonStop NS-Series System on page 4-4
Loading a NonStop S-Series System
1. In the OSM Low-Level Link, click the Start System button on the toolbar. The Start
System dialog box appears.
2. In the Start System dialog box:
a. In the SYSnn field, enter the number of the system subvolume that contains
the version of the operating system you will load.
DSM/SCM Quick Reference Guide—529847-005
4 -3
Task 9: Check Processor Status
Backing Out a Revision
b. Under SYSnn and CIIN Option, verify that the CIIN Disabled check box is
cleared.
c. Under Configuration File, select Saved version and enter the appropriate
value.
3. Click Start system. Do not close the System Startup dialog box. Two EMS event
stream windows and two startup TACL windows appear.
When the system load is complete (the operating system is loaded successfully
into the memory of processor 0 or processor 1), the Detailed box on the System
Load dialog box displays:
SYSTEM STARTUP COMPLETE,
NSK RUNNING ON PROCESSOR n
Loading a NonStop NS-Series System
1. In the OSM Low-Level Link, click the Start System button on the toolbar. The
System Load dialog box appears.
2. In the System Load dialog box:
a. From the Configuration drop-down list in the System Load Configuration box,
select a system volume to load from.
b. In the SYSnn field, enter the number of the SYSnn subvolume that contains
the version of the operating system you will load.
c. Under SYSnn and CIIN Option, verify that the CIIN Disabled check box is
cleared.
d. Under Configuration File, select Saved version and enter the appropriate
value.
3. Ensure that all the check boxes for all paths are selected.
4. Click Load. Do not close the System Load dialog box. The system load begins.
When the system load is complete (the operating system is loaded successfully
into the memory of processor 0 or processor 1), the Detailed box on the System
Load dialog box displays:
SYSTEM STARTUP COMPLETE,
NSK RUNNING ON PROCESSOR n
Task 9: Check Processor Status
1. Log on to either the OSM Low-Level Link.
2. On the Low-Level Link toolbar, click Processor Status.
3. Check that all processors are loaded.
DSM/SCM Quick Reference Guide—529847-005
4 -4
Task 10: Start TMF and Your Other Applications
Backing Out a Revision
Task 10: Start TMF and Your Other Applications
1. Start TMF.
2. Start all other applications.
DSM/SCM Quick Reference Guide—529847-005
4 -5
Backing Out If a Previous Configuration Does Not
Exist or If DSM/SCM Does Not Run
Backing Out a Revision
Backing Out If a Previous Configuration Does
Not Exist or If DSM/SCM Does Not Run
Note. You can also use this procedure if you have to back out from your first DSM/SCM
configuration, and you performed your previous configuration activities using Install.
Task 1: Run ZPHIRNM
1. Run ZPHIRNM in PREVIEW mode:
> RUN ZPHIRNM [$vol.]SYSnn , FROM [$vol.]SYSnn, PREVIEW
[STRICT] [,option]...
If no arguments are entered, help text appears.
2. If the process generates errors, correct them and run ZPHIRNM in PREVIEW
mode again. If no errors occur, continue.
3. Run ZPHIRNM:
> RUN ZPHIRNM SYSnn, from SYSnn
where SYSnn 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.]SYS01
Use SYS01 for both entries even though you are backing out to SYS00. Using the
same SYSnn after FROM is a special directive for DSM/SCM.
ZPHIRNM displays this prompt:
Do you want to use a log file with this session? (Y/N)
4. Type Y, and press Enter.
ZPHIRNM displays this prompt:
You may use any file for logging. If you request to use a
disk file that doesn’t exist, it will be created as an entrysequenced file.
Please enter a filename:
5. Enter a disk file name.
ZPHIRNM displays this message:
Log file, filename, was successfully created.
ZPHIRNM then renames the applied files. If ZPHIRNM notifies you of any errors,
correct them and run ZPHIRNM again.
DSM/SCM Quick Reference Guide—529847-005
4 -6
Task 2: Stop the System by Halting the Processors
Backing Out a Revision
ZPHIRNM must run without errors to complete the software activation. ZPHIRNM
issues an EMS message when it has successfully completed.
Task 2: Stop the System by Halting the Processors
You must use OSM for NonStop NS-series servers.
1. Ensure that DSM/SCM, all other user applications, TMF, and all other subsystems
are stopped, and that the spooler is drained.
2. Log on to either the OSM or TSM Low-Level Link.
3. On the Low-Level Link toolbar, click Processor Status.
4. Shift-click to select all of the running processors.
5. From the Processor Actions list, select Halt.
6. Click Perform Action.
7. Click OK to dismiss the confirmation dialog box and initiate the action.
Task 3: Load the System From the Saved Configuration
1. On the toolbar of the OSM or TSM Low-Level Link, click System Startup. The
System Startup dialog box is displayed.
2. Under Startup Configuration>Configuration File, select Saved version and
enter the appropriate value.
3. Click Start system. Do not close the System Startup dialog box. Two EMS event
stream windows and two startup TACL windows appear.
Task 4: Run ZPHIRNM
If you could not run ZPHIRNM successfully in Task 1, run it again now.
Task 5: Back Out to the Previous Revision
See Backing Out If DSM/SCM Is Running on page 4-1.
Backing Out After Renaming the SYSnn
To back out after renaming the SYSnn in Procedure 6: Renaming the Managed SYSnn
(Optional) on page 3-9, the procedures are slightly different, depending on whether or
not you can successfully restart DSM/SCM after the system load.
If the System Load and DSM/SCM Restart Succeed
1. Run ZPHITI to perform a backout as described in Backing Out If DSM/SCM Is
Running on page 4-1 (Tasks 1 through 5).
DSM/SCM Quick Reference Guide—529847-005
4 -7
If the System Load and DSM/SCM Restart Succeed
Backing Out a Revision
2. Run ZPHIRNM on the previous SYSnn (in this example, SYS20). The previous
SYSnn is the configuration that was running before the current 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. Rename the previous SYSnn to the name it had at the completion of the Apply.
For example:
> FUP
> RENAME $SYSTEM.SYS20.*, $SYSTEM.SYS00.*
> RENAME $SYSTEM.CSS20.*, $SYSTEM.CSS00.*
5. Perform a system load on your usual SYSnn (SYS00), which now contains the
revision before the last update.
6. Restart DSM/SCM.
7. Update the DSM/SCM database with the new SYSnns:
a. Before the next Apply to the system, run Verify Database so that DSM/SCM
can resolve the current names of the SYSnns.
b. Create an independent snapshot of the target.
c. Receive the independent snapshot into the host database.
DSM/SCM Quick Reference Guide—529847-005
4 -8
If the System Load Fails or DSM/SCM Does Not Run
Correctly
Backing Out a Revision
If the System Load Fails or DSM/SCM Does Not Run Correctly
1. Perform a system load from the previously working SYSnn (renamed to SYS20).
2. Rename the current SYSnn (SYS00) and CSSnn (CSS00) back to the last built
SYSnn (SYS01) and CSSnn (CSS01), respectively. For example:
> FUP RENAME $SYSTEM.SYS00.*, $SYSTEM.SYS01.*
> FUP RENAME $SYSTEM.CSS00.*, $SYSTEM.CSS01.*
3. Rename the previous SYSnn to the name it had at the completion of the Apply. For
example:
> FUP
> RENAME $SYSTEM.SYS20.*, $SYSTEM.SYS00.*
> RENAME $SYSTEM.CSS20.*, $SYSTEM.CSS00.*
4. Run ZPHIRNM to reverse the ZPHIRNM performed before the renaming of the
SYSnn.. For example:
> RUN ZPHIRNM $volume.SYS00, FROM $volume.SYS01
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 Target Interface backout step (Tasks 2 through 4 of
Backing Out If DSM/SCM Is Running on page 4-1) to back out to SYS00.
DSM/SCM Quick Reference Guide—529847-005
4 -9
Backing Out a Revision
If the System Load Fails or DSM/SCM Does Not Run
Correctly
DSM/SCM Quick Reference Guide—529847-005
4- 10
5
Generating Reports
Procedure
Page
Viewing a Report Online
5-1
Printing a Report
5-3
Modifying a Standard Report
5-4
Creating a System Report
5-5
Creating a Custom Report
5-6
For more information on DSM/SCM reports, see the DSM/SCM User’s Guide.
Viewing a Report Online
1. Select the report to view:
a. In the Planner Interface, select Requests>Prepare report....
DSM/SCM displays the Prepare Report Request dialog box listing the standard
reports and any custom reports you have added to DSM/SCM.
b. Select a report from the list.
c. Click Description....
DSM/SCM displays the Show Report Description dialog box.
d. Click Continue....
DSM/SCM displays the Prepare Report Request dialog box.
2. Supply values for run-time parameters as necessary:
a. Select the parameter.
b. Click Modify parameter....
DSM/SCM displays the Modify Parameter Value dialog box.
c. Enter a value for the parameter in the Value field.
d. Repeat the preceding three steps for each parameter to be given a value.
e. Click OK.
DSM/SCM returns to the Prepare Request dialog box.
3. Prepare the report for online viewing:
a. Check the Viewable formatted file subvolume location check box if it is not
already checked.
DSM/SCM Quick Reference Guide—529847-005
5 -1
Viewing a Report Online
Generating Reports
b. To write the report to a location other than the default, enter a subvolume name
in the subvolume location field.
4. Schedule the request:
a. The default is to prepare the report immediately. To change the default
scheduling, click Scheduling...; then schedule when you want the report to be
formatted for online viewing.
b. Click OK. The report is prepared and formatted for online viewing as
scheduled. It is also added to the list of prepared reports.
5. Click OK to submit the Prepare Report request.
6. View the report online:
a. Select File>View prepared documents....
DSM/SCM displays a list of reports and documents that have been prepared
for online viewing.
b. Select the report from the list; then click View.
DSM/SCM displays the selected report.
DSM/SCM Quick Reference Guide—529847-005
5 -2
Printing a Report
Generating Reports
Printing a Report
1. Select the report to print:
a. In the Planner Interface, select Requests>Prepare report....
DSM/SCM displays the Prepare Report Request dialog box listing the standard
reports and any custom reports you have added to DSM/SCM.
b. Select a report from the list.
c. Click Description....
DSM/SCM displays the Show Report Description dialog box.
d. Click Continue....
DSM/SCM displays the Prepare Report Request dialog box.
2. Supply values for run-time parameters as necessary:
a. Select the parameter.
b. Click Modify parameter....
DSM/SCM displays the Modify Parameter Value dialog box.
c. Enter a value for the parameter in the Value field.
d. Repeat the preceding three steps for each parameter to be given a value.
e. Click OK.
DSM/SCM returns to the Prepare Request dialog box.
3. Prepare the report for printing:
a. Check the Print formatted output location check box if it is not already
checked.
b. To print the report at a location other than the default, enter a spooler name in
the output location field, using standard spooler naming conventions.
4. Schedule the request:
a. The default is to prepare the report immediately. To change the default
scheduling, click Scheduling...; then schedule when you want the report to be
formatted for online viewing.
b. Click OK.
The report is prepared and formatted for printing as scheduled.
5. Click OK to submit the Prepare Report request.
DSM/SCM Quick Reference Guide—529847-005
5 -3
Modifying a Standard Report
Generating Reports
Modifying a Standard Report
Task 1: Edit the Report
1. Go to the database subvolume containing the standard report you need to change.
2. Copy the existing IN_file.
3. Edit the new IN_file. For more information on changing report formats, see the
SQL/MP Report Writer Guide.
Task 2: Bring the Modified Report Into DSM/SCM
1. Log on to the Planner Interface.
2. Select Maintain>Report list....
DSM/SCM displays the Maintain Report dialog box, which lists the available
reports.
3. Select the report that is being modified.
4. Change the report description:
a. Click Description....
DSM/SCM displays the Modify Report dialog.
b. In the SQLCI report IN_file field, change the IN_file name to the name of the
new IN_file containing the modified report definition (if you created a new
IN_file).
c. In the Description field, enter a description of the report; then click OK.
5. Update the parameter list if necessary:
a. Click Parameter list....
DSM/SCM displays a list of parameters, including the parameter names and
descriptions.
b. Delete parameters from the list as needed:
1. Select the parameter you want to delete.
2. Click Delete param....
DSM/SCM displays a confirmation box asking you to confirm or cancel the
deletion.
c. Add parameters to the list as needed:
1. Click Add param....
DSM/SCM Quick Reference Guide—529847-005
5 -4
Creating a System Report
Generating Reports
DSM/SCM displays the Add Parameter dialog box. A message reminds
you that the parameter must be added to the SQLCI IN_file and that the
parameter definition must be consistent with the definition in the IN_file.
2. Enter a name in the Parameter name field.
3. Select a type for the parameter you are adding from the list of parameter
types.
4. In the Description field, enter a description of the parameter; then click
OK.
6. Update the parameter type and description in DSM/SCM if necessary:
a. Click Parameter list....
b. Select the parameter you want to modify.
c. Click Modify param....
DSM/SCM displays the Modify Parameter Definition dialog, which contains a
scrollable list of parameter types.
d. Select a new parameter type from the Type list.
e. Change the parameter description in the Description field; then click OK.
7. Click OK.
Creating a System Report
1. At the Target Interface main menu, enter 1 (Create system report) in the Selection
number field; then press F1.
DSM/SCM displays the System Report screen.
2. Specify the output location for the report:
•
To write the report to disk, enter the system, volume, and subvolume location;
then press F1.
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; then press
F1.
3. Press F16.
DSM/SCM returns you to the main menu.
4. Press Shift-F16 to exit the Target Interface.
DSM/SCM Quick Reference Guide—529847-005
5 -5
Creating a Custom Report
Generating Reports
Creating a Custom Report
Task 1: Create the Custom Report
1. Make a copy of an existing DSM/SCM IN_file in the SQL catalog subvolume.
2. Using a text editor, make your changes to the file:
a. Add a SELECT statement to extract values from the database to include in the
report.
b. Modify the default format to any format you want.
c. Define parameters to be used as input to the report.
3. Store the IN_file in the SQL catalog subvolume.
Task 2: Add the Report to DSM/SCM
1. Enter the Planner Interface.
2. Select Maintain>Report list....
3. Click Add report....
DSM/SCM displays the Add Report dialog box.
4. Enter a name for the report in the Report title field.
5. In the SQLCI report IN_file field, enter the fully qualified name of the SQLCI
IN_file you created to define the report.
6. In the Description field, enter up to three lines of text describing the report.
7. Define any parameters used by the report:
a. Click Parameter list....
b. Click Add param....
DSM/SCM displays the Add Parameter dialog box.
c. Enter a name for the parameter in the Parameter name field.
d. Select a type from the parameter type list.
e. Enter a parameter description in the Description field; then click OK.
8. Click OK.
DSM/SCM Quick Reference Guide—529847-005
5 -6
6
Managing DSM/SCM
Procedure
Page
Changing the ZDSMSCM Subvolume
6-1
Renaming a DSM/SCM Managed Volume
6-2
Moving a DSM/SCM Database
6-2
Moving the DSM/SCM Archive
6-3
Verifying a Target System Database
6-3
Creating a Snapshot of a Target System
6-4
For more information on managing DSM/SCM, see the DSM/SCM User’s Guide.
Changing the ZDSMSCM Subvolume
Moving the ZDSMSCM Subvolume to Another Volume
1. Copy the existing ZDSMSCM subvolume to a new volume:
> FUP DUP $oldvol.ZDSMSCM.*, $newvol.*.*,saveall
2. Edit the PATHCOOL file to point to the $newvol.PATHSCM and the
\system.$newvol.ZDSMSCM.PATHMAIN.
3. Replace all occurrences of $oldvol.ZDSMSCM with $newvol.ZDSMSCM in the
PATHTARG or PATHHOST file.
4. Run PATHCOLD from $newvol.ZDSMSCM to create $newvol.PATHSCM.*.
5. Run STARTSCM from $newvol.ZDSMSCM.
6. If using Winsock, update Winsock with the new volume name.
7. Run Verify Database. (See Verifying a Target System Database.)
8. Create an independent snapshot. (See Creating a Snapshot of a Target System.)
9. Receive the snapshot into the host database.
Switching From One ZDSMSCM Subvolume to Another
1. Check that both ZDSMSCM subvolumes 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 from which you want to run.
3. Place these files with proper security under the proper owner.
DSM/SCM Quick Reference Guide—529847-005
6 -1
Renaming a DSM/SCM Managed Volume
Managing DSM/SCM
4. Edit the PATHCOOL file to point to the $newvol.PATHSCM and the
\system.$newvol.ZDSMSCM.PATHMAIN.
5. Replace all occurrences of $oldvol.ZDSMSCM with $newvol.ZDSMSCM in the
PATHTARG or PATHHOST file.
6. Run PATHCOLD from $newvol.ZDSMSCM to create $newvol.PATHSCM.*.
7. Run STARTSCM from $newvol.ZDSMSCM.
8. Give ownership of the CBEXE program to the super ID (255,255).
9. Set the PROGID of the CBEXE program to the super ID (255,255).
10. Give ownership of the TAEXE program to the super ID (255,255).
11. Set the PROGID of the TAEXE program to the super ID (255,255).
Renaming a DSM/SCM Managed Volume
1. Rename $OLDVOL to $NEWNAME.
Note. If $DATA00 is a scratch volume, Verify Database stops in a restartable state. If
$DATA00 is an archive volume, after successful completion of Verify Database,
update the volume usage information using the Target and Host Maintenance
Interface. For details, see the DSM/SCM User’s Guide.
2. Run Verify Database. (See Verifying a Target System Database on page 6-3.)
3. Create an independent snapshot and transfer it to the host. (See Creating a
Snapshot of a Target System on page 6-4.)
Moving a DSM/SCM Database
1. Stop all servers through PATHCOM and all processes running from PHIHDBMG
(PHITDBMG for a target database).
2. On the Maintenance Interface main menu, enter 6 (Database Relocation) in the
Selection Number field; then press F1.
DSM/SCM displays the Database Relocation screen.
3. Enter the name of the volume where the database currently resides.
4. Enter the name of the new volume for the database; then press F1.
The move can take a while. The Maintenance Interface waits for the compile to
finish. No other DSM/SCM activities can be performed while the compile is in
progress.
5. Run STOPSCM.
6. Run STARTSCM.
DSM/SCM Quick Reference Guide—529847-005
6 -2
Moving the DSM/SCM Archive
Managing DSM/SCM
Moving the DSM/SCM Archive
1. Configure free-space table (FST) caching for the new archive volume. See the
SCF Reference Manual for the Storage Subsystem. (This step is not required, but
it improves system performance.)
2. At the host Maintenance Interface main menu, enter 8 (Archive Relocation) in the
Selection Number field; then press F1.
DSM/SCM displays the Archive Relocation screen.
3. Estimate the maximum amount of disk space that will be freed by moving the
archive:
a. For a single subvolume, enter a node (optional), volume, and subvolume in the
From field.
b. For all subvolumes, enter a node (optional) and volume in the From field.
c. Press F5.
DSM/SCM shows the estimate in the Disk Space field.
4. Move archive subvolumes:
•
To move an archive subvolume:
a. Enter the current node (optional), volume, and subvolume in the From
field.
b. Enter the new node (optional) and volume in the To field; then press F1.
•
To move all archive subvolumes on a specific volume:
a. Enter the current node (optional) and volume in the From field.
b. Enter the new node (optional) and volume in the To field; then press F1.
Verifying a Target System Database
1. At the Target Interface main menu, enter 5 (Perform database verify) in the
Selection number field; then press F1.
DSM/SCM displays the Verify Database - Submit Request screen.
2. Press F1 to submit the request.
DSM/SCM displays the Processing Verification screen. The screen is updated
approximately every 15 seconds.
3. Press F4 to view current EMS messages related to the request issued as it runs.
When the Verify Database request finishes successfully, DSM/SCM displays an
informational message.
DSM/SCM Quick Reference Guide—529847-005
6 -3
Creating a Snapshot of a Target System
Managing DSM/SCM
4. Create an independent snapshot and transfer it to the host. (See the following
subsection.)
Creating a Snapshot of a Target System
1. At the Target Interface main menu, enter 2 (Perform system snapshot) in the
Selection number field; then press F1.
DSM/SCM displays the Create Snapshot - Submit Request screen.
2. Change the location where the snapshot is to be placed if necessary.
3. Press F1 to submit the request.
DSM/SCM creates the snapshot. DSM/SCM displays the Create Snapshot - Taking
Snapshot screen. The screen is updated approximately every 15 seconds.
4. Press F4 to view current EMS messages related to the request issued as it runs.
When the request is finished, a completion message is issued.
5. Transfer the snapshot to the host system, either on tape or by using a file-transfer
process if you stored the snapshot on disk.
DSM/SCM Quick Reference Guide—529847-005
6 -4
Index
A
P
Adding 2-2
Planner Interface
deleting
targets 2-3
target systems
changing profile information 1-8
deleting a target 2-3
Profiles
target
changing information 1-8
B
Backing out a revision
after renaming SYSnn
if DSM/SCM will not run or coldload
fails 4-9
Build type, specifying 1-7
Build/Apply request
specifying the type of build 1-7
T
C
CIIN file
disabled 4-4
Configuration revision
performing initial revision 1-7
Target systems
changing profile information 1-8
D
Deleting
target 2-3
I
Initialization build/apply
additional logical targets 2-1
Install
backing out to a configuration made
by 4-6
L
Logical target
deleting from system 2-3
DSM/SCM Quick Reference Guide—529847-005
Index -1
T
Index
DSM/SCM Quick Reference Guide—529847-005
Index -2
Content Feedback
First Name: __________________
Phone: _____________________
Company: ___________________
Last Name: _________________
e-mail address: ______________
(All contact information fields are required.)
If you’re reporting an error or omission, is your issue:
Minor: I can continue to work, but eventual resolution is requested.
Major: I can continue to work, but prompt resolution is requested.
Critical: I cannot continue to work without immediate response.
Comments (give sufficient detail to help us locate the text):
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
Thank you for taking the time to provide us with your comments.
You can submit this form online, e-mail it as an attachment to [email protected], fax it to
408-285-5520, or mail it to:
Hewlett-Packard Company
NonStop Enterprise Division
19333 Vallco Parkway, MS 4421
Cupertino, CA 95014-2599
Attn.: Product Manager, Software Publications