ClearPath HMP IX Series Installation, Configuration, and Migration ...

ClearPath HMP IX Series
Installation, Configuration,
and Migration Guide
May 1997
Printed in U S America
Priced Item 7848 4078–004

ClearPath HMP IX Series
Installation, Configuration,
and Migration Guide
Copyright
All rights reserved.
1997 Unisys Corporation.
Unisys is a registered trademark of Unisys Corporation.
Release ClearPath HMP IX 2.0
May 1997
Printed in U S America
Priced Item 7848 4078–004

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THE DOCUMENT. Any product and related
material enclosed herein are only furnished pursuant and subject to the terms and conditions of a duly
executed agreement to purchase or lease equipment or to license software. The only warranties made
by Unisys, if any, with respect to the products described in this document are set forth in such an
agreement. Unisys cannot accept any financial or other responsibility that may be the result of your
use of the information in this document or software material, including direct, indirect, special, or
consequential damages.
You should be very careful to ensure that the use of this information and/or software material complies
with the laws, rules, and regulations of the jurisdictions with respect to which it is used.
The information contained herein is subject to change without notice. Revisions may be issued to
advise of such changes and/or additions.
RESTRICTED RIGHTS LEGEND—Use, reproduction, or disclosure is subject to the restrictions set forth
in DFARS 252.227–7013 and 252.211–7015/FAR 52.227–14 and 52.227–19 for commercial
computer software, as applicable.
Unisys Corporation is interested in receiving your comments and suggestions about this information.
You can send your comments in four ways: the Business Reply Mail form in the printed document; our
Internet e-mail address (rsvldoc@rsvl.unisys.com); our fax number (1-612-635-7523); or our postal
address (Unisys Corporation, PI Response Card, P.O. Box 64942, St. Paul, MN 55164–0942, U.S.A.).
TRADEMARKS—All terms mentioned in this document that are known to be trademarks or service
marks have been appropriately capitalized. Unisys Corporation cannot attest to the accuracy of this
information. Use of a term in this document should not be regarded as affecting the validity of any
trademark or service mark.

Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Section 1. Introduction
1.1. Introduction to ClearPath HMP IX Servers . . . . . . . . 1–1
1.1.1. The ClearPath IX Environment . . . . . . . . . . . . . . . . . 1–1
1.1.2. Software Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
1.2. CSE Installation Overview . . . . . . . . . . . . . . . . . . . . . . . 1–4
Section 2. Preinstallation Planning
2.1. Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
2.2. Submitting SCMS Configuration Information . . . . . . 2–2
2.3. Additional Requirements . . . . . . . . . . . . . . . . . . . . . . . . 2–2
2.3.1. PathMate Workstation Requirement . . . . . . . . . . . . . 2–2
2.3.2. SysAdmin Web Browser Requirement . . . . . . . . . . . 2–3
2.3.3. Enterprise Backup and Restore (EBRS) License
and Workstation Requirements . . . . . . . . . . . . . . . . . 2–3
Entering the EBRS Site License Number . . . . 2–3
EBRS Workstation Requirements . . . . . . . . . . 2–3
2.3.4. DEPCON Workstation Requirement . . . . . . . . . . . . . 2–4
2.4. Migration Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
2.4.1. Hardware Migration Issues . . . . . . . . . . . . . . . . . . . . 2–4
2.4.2. OS 2200 Print Queue Configuration Requirement . 2–5
2.5. Planning to Use an Existing SPO/ESE Server . . . . . 2–5
2.6. Defining Network Parameters . . . . . . . . . . . . . . . . . . . 2–6
2.6.1. Planning Network Configuration (Sites With
an Existing Network) . . . . . . . . . . . . . . . . . . . . . . . . . 2–6
2.6.2. Planning Network Configuration (Sites
Without an Existing Network) . . . . . . . . . . . . . . . . . . 2–8
2.6.3. Reconfiguring CMS 1100 . . . . . . . . . . . . . . . . . . . . . 2–11
2.7. Preinstallation Checklist . . . . . . . . . . . . . . . . . . . . . . . . 2–13
2.8. Obtaining a CSE Installation Checklist . . . . . . . . . . . .
2–23
7848 4078–004 iii

Contents
iv
Section 3. Configuring and Using the Monitor Concentrator
3.1. Configuring the Monitor Concentrator . . . . . . . . . . . . 3–1
3.2. Using the Monitor Concentrator . . . . . . . . . . . . . . . . . 3–2
Section 4. Installing Windows NT on the Intel Node
4.1. Running the SCU (If Required) . . . . . . . . . . . . . . . . . . . 4–2
4.2. Steps to take if Windows NT is Preinstalled . . . . . . . 4–2
4.3. Configuring the RAID Controller . . . . . . . . . . . . . . . . . 4–8
4.4. Creating a Bootable MS-DOS Partition . . . . . . . . . . . 4–13
4.5. Installing and Configuring Windows NT
(Not Preinstalled) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–15
4.5.1. Installing Windows NT . . . . . . . . . . . . . . . . . . . . . . . . 4–15
4.5.2. Configuring Windows NT . . . . . . . . . . . . . . . . . . . . . . 4–21
4.6. Logging On as the Administrator . . . . . . . . . . . . . . . . . 4–30
4.7. Configuring the Hosts File . . . . . . . . . . . . . . . . . . . . . . . 4–31
4.8. Installing the Windows NT Service Pack . . . . . . . . . . 4–32
4.9. Installing and Configuring RAID Software . . . . . . . . . 4–33
4.10. Installing and Configuring Video Drivers . . . . . . . . . . 4–33
4.11. Installing IOE Software Products . . . . . . . . . . . . . . . . . 4–35
4.12. Configuring the Tape Drive Unit . . . . . . . . . . . . . . . . . . 4–35
4.13. Setting Balanced Server Priorities . . . . . . . . . . . . . . . 4–36
4.14. Creating or Updating an Emergency Repair Disk . . 4–37
Section 5. Installing UNIX on the Intel Node
5.1. Scope of the Procedures . . . . . . . . . . . . . . . . . . . . . . . . 5–3
5.2. Steps to Take if Software is Preinstalled . . . . . . . . . . 5–3
5.3. Configuring the RAID Controller . . . . . . . . . . . . . . . . . 5–13
5.4. Installing the UNIX Operating System . . . . . . . . . . . . 5–20
5.5. Copying IOE Products to the Spooling Directory . . . 5–32
5.5.1. Copying from Tape or Diskette . . . . . . . . . . . . . . . . . 5–33
5.5.2. Copying the GDM Developer’s Package . . . . . . . . . 5–33
5.5.3. Products Not Copied to the Spooling Directory . . . 5–34
5.6. Logging On as Superuser . . . . . . . . . . . . . . . . . . . . . . . 5–34
5.7. Installing and Running the Tuning Script
(Site-Installed UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5–35
7848 4078–004

Section 6. Installing SPO/HMP Console and Related Software
Contents
6.1. Running the System Configuration Utility (SCU) . . . 6–2
6.2. Steps to Take If Software Is Preinstalled . . . . . . . . . . 6–3
6.3. Installing UNIX on the SPO Server . . . . . . . . . . . . . . . 6–11
6.4. Logging On as the Superuser . . . . . . . . . . . . . . . . . . . . 6–23
6.5. Installing UNIX Operating System Patches . . . . . . . . 6–24
6.6. Installing X Terminal Software (Done at SPO
Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–25
6.7. Installing the Multiport Card Driver . . . . . . . . . . . . . . . 6–28
6.8. Installing the SPO/HMP Console Software . . . . . . . . 6–30
6.9. Installing and Running the Tuning Script
(Site-Installed UNIX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–34
6.10. Copying the Hosts File (Done at 2200 System
Consoles) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38
6.11. Copying and Activating the AMS Database (Done
at 2200 System Consoles) . . . . . . . . . . . . . . . . . . . . . . 6–43
6.11.1. Remotely Installing the AMS Database (Done
at SPO Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–43
6.11.2. Activating the SPO/HMP AMS Database (Done at
System Consoles) . . . . . . . . . . . . . . . . . . . . . . . . . . 6–45
6.11.3. Changing the Start-up Session to Systems
Operations (Done at System Consoles) . . . . . . . . . . 6–45
Section 7. Enabling Use of the X Terminal
7.1. Starting and Stopping the SPO Daemons . . . . . . . . . 7–1
7.2. Configuring Each X Terminal . . . . . . . . . . . . . . . . . . . . 7–2
7.3. Enabling SPO Server Communications and Remote
Access to Fonts (Done at Each X Terminal) . . . . . . . 7–5
7.4. Enabling Monitoring (for Windows NT) . . . . . . . . . . . . 7–6
7.4.1. Installing URM Files on the SPO Server . . . . . . . . . . 7–6
7.4.2. Configuring the FTP Server Service . . . . . . . . . . . . . 7–9
7.4.3. Transferring the Windows NT Agent . . . . . . . . . . . . . 7–10
7.4.4. Installing the Windows NT Agent . . . . . . . . . . . . . . . 7–12
7.5. Enabling Monitoring and Control (for UNIX) . . . . . . . 7–14
7.5.1. Creating URM Files . . . . . . . . . . . . . . . . . . . . . . . . . . 7–14
7.5.2. Installing URM Agents and Redirecting
Console Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–17
7.6. Starting Normal SPO X Terminal Operations . . . . . . 7–22
7.6.1. Windows Displayed by SPO/HMP Console . . . . . . . 7–23
7.6.2. Starting Single Point Status . . . . . . . . . . . . . . . . . . . 7–23
7.6.3. Activating the SP-AMS Database . . . . . . . . . . . . . . .
7–24
7848 4078–004 v

Contents
vi
Section 8. Installing the Basic OS 2200 IOE
8.1. Read-and-Reply Message Format . . . . . . . . . . . . . . . . 8–4
8.2. Performing the Initial Boot . . . . . . . . . . . . . . . . . . . . . . 8–4
8.2.1. Initial Boot Steps if Boot Partition Is Not
Activated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–5
8.2.2. Initial Boot Steps if Partition Is Up and
Exec Is Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–5
8.2.3. Completing the Boot Procedure . . . . . . . . . . . . . . . . 8–6
8.3. Installing Products from Fast-Load Tape CPIX-OE1 8–8
8.4. Establishing the Performance Level (IX4600 and
IX4800) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8–10
Section 9. Verifying Interconnect Communications
9.1. Installing HLC2 Microcode . . . . . . . . . . . . . . . . . . . . . . 9–1
9.2. Installing Channel Adapter Microcode (CSIOP) . . . . 9–3
9.3. Installing the CEC Tape . . . . . . . . . . . . . . . . . . . . . . . . . 9–5
9.4. Testing Interconnect Communications . . . . . . . . . . . . 9–6
9.5. Hardware Ready for Use (RFU) . . . . . . . . . . . . . . . . . . 9–6
Section 10. Installing the Remaining IOE
10.1. Installing OPE and SysAdmin . . . . . . . . . . . . . . . . . . . . 10–1
10.2. Installing PathMate Software . . . . . . . . . . . . . . . . . . . . 10–2
10.3. Installing Default UDS Application Group 3
from Fast-Load Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3
10.3.1. Installing TIPUTIL, MCB, and DPS from
Fast-Load Tape CPIX-OE2 . . . . . . . . . . . . . . . . . . . . . 10–4
10.3.2. Setting Up the TIP Environment . . . . . . . . . . . . . . . . 10–5
10.3.3. Setting Up Application Group 3 . . . . . . . . . . . . . . . . 10–6
10.3.4. Installing UDS Application Group 3 from
Fast-Load Tape CPIX-UDS3 . . . . . . . . . . . . . . . . . . . . 10–8
10.4. Installing UREP Workstation . . . . . . . . . . . . . . . . . . . . . 10–10
10.5. Installing OADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–10
10.6. Installing TeamQuest Online . . . . . . . . . . . . . . . . . . . . . 10–10
10.7. Installing EBRS (UNIX on Intel Node Only) . . . . . . . . . 10–10
10.8. Installing Remaining UNIX IOE Products . . . . . . . . . . 10–11
10.8.1. Installing UUIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10–11
10.8.2. Installing WebTX . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10–11
7848 4078–004

Section 11. Site Customization
Contents
11.1. Using PathMate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–1
11.2. Installing Optional OS 2200 Software from the
Package Tapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–2
11.2.1. Registering the OS 2200 Product Key Tape . . . . . . 11–9
11.2.2. Optional OS 2200 Product Installation . . . . . . . . . . 11–10
11.3. Customizing SPO/HMP Console and the X
Terminal Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 11–10
11.3.1. Permanently Changing the X Terminal
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–11
11.3.2. Editing the Hosts Files . . . . . . . . . . . . . . . . . . . . . . . 11–12
11.3.3. Copying the New Hosts File to the System
Consoles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–13
Copying the New Hosts File to Diskette . . . . . 11–13
Loading the New Hosts File . . . . . . . . . . . . . . 11–13
11.3.4. Reconfiguring the Host Representations . . . . . . . . . 11–15
11.3.5. Reinstalling the Agent Software . . . . . . . . . . . . . . . . 11–19
11.4. Testing TCP/IP Communications . . . . . . . . . . . . . . . . . 11–22
11.5. Installing Optional UNIX Products . . . . . . . . . . . . . . . . 11–23
Appendix A. Communication Settings Specific to ClearPath
Appendix B. Enabling System Controlled Performance
B.1. Initial Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–1
B.2. Normal Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–2
B.3. Model Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–3
B.4. Recovery Boots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–3
B.5. MODELNUM Keyin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–3
B.6. Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–4
Appendix C. SPO/HMP IX Interface License Key Registration
C.1. How to Obtain a Permanent Key . . . . . . . . . . . . . . . . . C–2
C.2. Upgrades to SPO/ESE . . . . . . . . . . . . . . . . . . . . . . . . . . C–2
C.3. SPO/HMP IX Interface License Key Registration
Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C–2
7848 4078–004 vii

Contents
viii
Appendix D. Migrating from ClearPath Release 1.0 to 2.0
D.1. New and Changed Software for Release 2.0 . . . . . . D–2
D.2. Installing OS 2200 Products from Fast-Load
Tape CPIX-OE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–6
D.3. Updating the UNIX Node (UNIX on Intel Node) . . . . . D–9
D.4. Migrating SPO/HMP Console Software . . . . . . . . . . . D–11
D.4.1. Use of Login Names . . . . . . . . . . . . . . . . . . . . . . . . . D–11
D.4.2. Installation Scenarios . . . . . . . . . . . . . . . . . . . . . . . . D–11
Scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–11
Scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–12
Scenario 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–12
D.4.3. Changing the Logging Directory . . . . . . . . . . . . . . . . D–13
Appendix E. Request for Comments (RFC) 1918
Appendix F. Configuring the FDDI Interconnect
F.1. Configuring the 2200 FDDI Connection . . . . . . . . . . . F–1
F.1.1. IX4400 Server Component Configuration (HLC2) . . F–2
F.1.2. IX4600 or IX4800 Component Configuration . . . . . F–5
F.2. Configuring the UNIX Node FDDI Connection . . . . . . F–5
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Bibliography . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
7848 4078–004

Figures
1–1. The ClearPath HMP IX Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
1–2. Installation Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–5
1–3. ClearPath IX Server Default Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–6
2–1. Example Use of Private LAN Addresses
(Not Recommended Except for Sites Without an Existing Network) . . . . . . 2–9
3–1. Default Monitor Concentrator Port Name Assignments . . . . . . . . . . . . . . . . 3–1
4–1. Easy Configuration–ARRAY SELECTION MENU . . . . . . . . . . . . . . . . . . . . . . . 4–9
4–2. Logical Drives Configured Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–10
5–1. Drive Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–14
6–1. Possible Connections to the SPO/HMP Server . . . . . . . . . . . . . . . . . . . . . . . 6–28
6–2. System Console F3 Utilities Session Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 6–38
6–3. Single Point Interface Utility Session Window . . . . . . . . . . . . . . . . . . . . . . . . 6–40
6–4. Specify Load Diskette Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–40
6–5. Add Router Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–42
7–1. X Terminal Login Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7
7–2. Selecting a Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–7
7–3. Single Point Configuration Routine Main Menu . . . . . . . . . . . . . . . . . . . . . . . 7–7
7–4. Maintain UNIX Agents Window (SPO Server Only) . . . . . . . . . . . . . . . . . . . . . 7–8
7–5. Entering the Host Name for Transferring the Agent . . . . . . . . . . . . . . . . . . . 7–11
7–6. Defining the Administrator for Installation of the Agent . . . . . . . . . . . . . . . . 7–11
7–7. SPO/HMP Console TopCluster Window (Single 2200 Partition) . . . . . . . . . . 7–13
7–8. Maintain UNIX Agents Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–15
7–9. URM Policies Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–15
7–10. SPO/HMP Console Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7–23
10–1. PathMate Program Group in Windows 95 Environment . . . . . . . . . . . . . . . . 10–3
D–1. Package Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–6
D–2. Runstream Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–7
D–3. Registered Package Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–8
D–4. Product Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D–9
7848 4078–004 ix

Tables
2–1. Required Network Names and Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 2–7
2–2. Example Use of Private LAN Addresses
(Not Recommended Except for Sites Without an Existing Network) . . . . . 2–10
2–3. Preinstallation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–13
5–1. Boot Disk (Disk 0) Required Configuration Values . . . . . . . . . . . . . . . . . . . 5–2
5–2. Disk 1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
6–1. Boot Disk Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6–11
8–1. Tape CPIX-OE1 Fast-Load Tape Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 8–2
10–1. Tape CPIX-OE2 Fast-Load Tape Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 10–3
10–2. Tape CPIX-UDS3 Fast-Load Tape Contents . . . . . . . . . . . . . . . . . . . . . . . . . 10–4
11–1. Package Tape Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11–3
A–1. IP Addresses and Host Names Used by the Internal FDDI LAN . . . . . . . . . A–1
A–2. TSAM Configuration Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–2
D–1. New Products for ClearPath Release 2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . D–2
D–2. Changed Products for CPIX-2.0 (SB6D2 Based Release) . . . . . . . . . . . . . . D–2
D–3. Changed Products for CPIX2.0-SB5
(SB5R4D2 Based Release) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D–4
7848 4078–004 xi

Examples
2–1. Sample CMS 1100 Configuration After Modification by PathMate . . . . . . . 2–11
11–1. Default X Terminal Configuration File Contents . . . . . . . . . . . . . . . . . . . . . . . 11–11
11–2. SPO Server Hosts File Format before Editing . . . . . . . . . . . . . . . . . . . . . . . . 11–12
11–3. SPO Server Hosts File Format after Editing . . . . . . . . . . . . . . . . . . . . . . . . . 11–12
11–4. UNIX Node Hosts File Format before Editing . . . . . . . . . . . . . . . . . . . . . . . . . 11–13
11–5. UNIX Node Hosts File Format after Editing . . . . . . . . . . . . . . . . . . . . . . . . . . 11–13
A–1. Default UNIX Node and OPE UNIX Hosts File . . . . . . . . . . . . . . . . . . . . . . . . .
A–2
7848 4078–004 xiii

About This Guide
Purpose
Scope
This guide summarizes how to install, configure, and activate the integrated operating
environment (IOE) software for a ClearPath HMP IX server (which for the rest of this
document will be referred to as a ClearPath IX server).
This guide also provides procedures existing ClearPath IX server sites can use to migrate
from ClearPath release 1.0 to release 2.0
This guide describes how to install the following software:
Windows NT Server or the UNIX operating system and related IOE software on the
Intel node
Single Point Operations (SPO)/HMP software including the operating system and
related software on the SPO server and the LT501 X terminal or terminals
OS 2200 and related IOE software on the 2200 node
This guide also provides overviews of certain hardware topics such as site preparation
requirements and hardware interconnections that relate to successful software
installation.
The goal of these procedures is to achieve hardware ready for use (RFU) so the client
can begin customizing the software for the site. PathMate software is provided to aid in
further customization. This guide gives procedures for installing PathMate, and briefly
describes its use.
To successfully install and customize optional software, sites may need many documents
in the ClearPath IX server product libraries. Most documents are available electronically
on CD-ROM. Refer to ClearPath HMP IX Series Getting Started Guide for details about
product documentation.
Note: For initial installation, procedures in this guide replace procedures in the
following Windows NT or UNIX operating system documents: Microsoft
Windows NT Server Version 4.0 Start Here, Basics and Installation or UNIX
Software Installation Guide.
7848 4078–004 xv

About This Guide
Audience
xvi
This online version of the guide supersedes the printed version (7848 4078-002).
In addition, additional information is documented in the following problem list entries
(PLE):
PLE 16976431—This PLE documents technical changes not available at the time this
online version was published to the Web.
PLE 17000624—This PLE documents correct Windows NT hardware configuration
information. Appendix G “Windows NT Hardware Configuration” has been deleted
from this guide because of volatility of that information.
Your Unisys representative can provide you with a copy of either PLE.
The audience for this document includes Unisys customer support engineers (CSE) or
service providers who install, configure, and make operational a ClearPath IX server.
Site administrators or other personnel at the site also need this document when
installing new levels of software.
Prerequisites
Some knowledge of OS 2200, Windows NT (if applicable), and UNIX operating system
installation, configuration, and operations is helpful.
Before reading this overview you should read the ClearPath HMP IX Series Getting
Started Guide.
How to Use This Guide
Sections 1 through 3 provide essential overview and preliminary information. Complete
the checklists in Section 2 before performing any installation procedures.
Use Section 4 or Section 5 depending on whether you are installing Windows NT
(Section 4) or UNIX (Section 5) on the Intel node. Other sections apply to all
installations except as noted.
Organization
This guide is organized as follows:
Section 1. Introduction
This section introduces the ClearPath IX server and provides an overview of the
installation steps.
7848 4078–004

About This Guide
Section 2. Preinstallation Planning
This section provides preinstallation planning steps for migration to the ClearPath IX
server, for defining networking parameters, and for obtaining needed installation
information. A checklist is provided that should be completed before starting
installation.
Section 3. Configuring and Using the Monitor Concentrator
This section describes procedures for configuring the monitor concentrator port
assignment names and for using the monitor concentrator.
Section 4. Installing Windows NT on the Intel Node
This section describes how to configure the redundant array of independent disks
(RAID) controller and install and configure the Windows NT server operating system and
related IOE software on the Intel node. You need this section only if installing a
ClearPath IX server with Windows NT.
Section 5. Installing UNIX on the Intel Node
This section describes how to configure the RAID controller and install and configure
the UNIX operating system and related IOE software on the Intel node. You need this
section only if installing a ClearPath IX server with UNIX.
Section 6. Installing SPO/HMP Console and Related Software
This section describes how to install the UNIX operating system and related Single Point
Operations (SPO)/HMP Console software on the SPO server. It also describes how to
copy the hosts file and Autoaction Message System (AMS) database to the 2200 node
system consoles and how to activate the AMS database.
Section 7. Enabling Use of the X Terminal
This section describes how to configure the X terminal, how to log on and enable
communications with the SPO server, and how to enable communications with the Intel
node (Windows NT or UNIX) for normal SPO monitoring.
Section 8. Installing the Basic OS 2200 IOE
This section describes how to install the basic OS 2200 IOE software from fast-load tape
CPIX-OE1. This is the minimum set of 2200 node software required to achieve hardware
ready for use (RFU) for the ClearPath IX server.
Section 9. Verifying Interconnect Communications
This section describes how to perform the communication test required to verify
hardware RFU.
Section 10. Installing the Remaining IOE Software
This section describes how to install the remaining IOE software, including the Open
Programming Environment (OPE) and SysAdmin software required for system
administration. Procedures in this section are performed by site personnel after
hardware RFU.
7848 4078–004 xvii

About This Guide
xviii
Section 11. Site Customization
This section describes how to install PathMate software, which automates many site
customization tasks. It also describes how to perform TCP/IP communications tests and
how to customize the X terminal or SPO/HMP Console configurations. Procedures in
this section are performed by site personnel after hardware RFU.
Appendix A. Communication Settings Specific to ClearPath
This appendix describes system names, IP addresses, and TSAM configuration values
used by the ClearPath IX server internal network.
Appendix B. Enabling System Controlled Performance
This appendix (for IX4600 or IX4800 servers only) describes how to register the
contracted System Controlled Performance (SCP) performance level of the 2200 node.
Appendix C. SPO/HMP IX Interface License Key Registration
This appendix contains the form used by SPO Enterprise Server Edition (SPO/ESE) sites
to request the permanent software license key needed to manage a ClearPath IX server
using SPO/ESE software.
Appendix D. Migrating from ClearPath Release 1.0 to 2.0
This appendix describes new and changed software for ClearPath release 2.0. It also
describes how existing ClearPath release 1.0 sites can migrate to ClearPath release 2.0 to
use the new capabilities of that release.
Appendix E. Request for Comments (RFC) 1918
This appendix contains the entire text of the Internet Engineering Task Force (IETF)
Request for Comments (RFC) 1918. RFC 1918 provides guidance on the use of internet
addresses for sites that are new to TCP/IP networking.
Appendix F. Configuring the FDDI Interconnect
This appendix explains how to recreate the fiber distributed data interchange (FDDI)
interconnect configuration in the Site Configuration Management System (SCMS)
database if it must be recreated for some reason. The database is provided prebuilt from
the factory so this should not be necessary.
Related Product Information
The following documents are provided with ClearPath release 2.0:
ClearPath HMP IX Series Conceptual Overview (7848 4052)
This overview provides a high-level view of ClearPath HMP IX servers to help customers
understand the key attributes of ClearPath IX servers and the key technologies used.
This information is intended to help customers determine how ClearPath IX servers can
be of benefit to their existing information infrastructure.
7848 4078–004

About This Guide
ClearPath HMP IX Series Getting Started Guide (7848 4060)
This guide tells how you begin using your ClearPath HMP IX server once initial
installation and configuration of the hardware and software have occurred. It describes
what you do next and tells you where to go for complete information about all aspects of
the system.
ClearPath HMP IX Series Open/OLTP Pathway Installation and Operations
Guide (7848 4409)
This guide describes how to install and use the Pathway client software that runs on the
UNIX and Windows NT nodes of ClearPath HMP IX servers. The client software
communicates with the Open/OLTP Transaction Manager software running on the 2200
node of ClearPath HMP IX servers to provide a distributed transaction processing (DTP)
environment.
ClearPath HMP IX Series Operations Guide (7848 4094)
This guide provides an overview of the ClearPath IX server hardware. It also describes
how to accomplish the following tasks for each component: system start-up and
shutdown, system reboot and recovery, partition management, and integrated operations
monitoring and control using the SPO/HMP Console product.
ClearPath HMP IX Series SysAdmin Administration Guide (7848 4086)
This guide provides an overview of the system administration application, SysAdmin. It
describes how to use SysAdmin for managing users, groups, and accounts across the
ClearPath HMP IX environment and for managing distributed transactions across
multiple platforms. SysAdmin is available by using a World Wide Web browser. The
browser, along with a menu interface, provides the system administrator with an
interface to the Open Programming Environment (OPE), OS 2200, UNIX, and Windows
NT environments.
ClearPath HMP IX Series Installation, Configuration, and Migration Guide
(7848 4078)
This guide summarizes how to install, configure, and activate the integrated operating
environment (IOE) software for a ClearPath HMP IX server. That software includes the
basic Windows NT Server or UNIX operating system, OS 2200, Single Point Operations
(SPO), and PathMate IOE software. This guide also describes migration from ClearPath
release 1.0 to 2.0 and provides overviews of certain hardware topics that relate to
successful software installation.
ClearPath HMP IX Series Web Servers User’s Guide (7848 4458)
This guide provides programming information for the various World Wide Web servers
and Web support tools available on ClearPath HMP IX servers. For some products,
configuration, administration, or installation information is also included. While this
guide does not cover the basic principles of the Web in any detail, it does contain an
extensive reading list of material in several languages.
7848 4078–004 xix

About This Guide
xx
ClearPath HMP IX Series Web Transaction Enabler (WebTx) User’s Guide
(7850 4230)
This guide is an online help system that can be viewed with any Web browser. It
provides information on installation, configuration, and administration of WebTx
software, a component of the Web Commerce Server Solution Package for ClearPath
HMP IX servers. WebTx works with UNIX or Windows NT Web server software to
provide Web access to files and transactional applications on ClearPath HMP IX servers.
This guide is distributed with the WebTx software for the Windows NT or UNIX
operating environment.
ClearPath HMP IX Series Web Transaction Server (WebTS) Administration
Guide (7850 4073)
This guide provides task-oriented information to help system administrators set up Web
Transaction Server (WebTS) software. WebTS is an OS 2200 Web server that allows
desktop users with Web browsers to access static Web pages and transaction programs
in the OS 2200 environment of a ClearPath HMP IX server. You use WebTS
administration software (WebTSA) on a Windows 95 or Windows NT workstation to
administer the WebTS server software.
ClearPath HMP IX Series Web Transaction Server (WebTS) Programming
Guide (7850 4248)
This guide describes the interface between a Web browser and transaction programs
running on the ClearPath IX server. Part of this interface is a new software component,
called WebTS. This guide describes WebTS and provides information enabling
application programmers to develop the interface between a Web browser and the
transaction programs.
ClearPath HMP IX Series SPO/HMP Console Administration and Operations
Overview (7846 0540)
This overview provides operators and administrators an introduction to the use of
SPO/HMP Console for managing the ClearPath HMP IX server. It is a prerequisite to
using SPO/HMP Console. The overview refers to the Single Point Operations/Enterprise
Server Edition 4.0 library for detailed information about configuring, administering, and
operating SPO/HMP Console.
ClearPath HMP IX4400 Server Configuration Guide (7848 4334)
This guide tells how to configure new ClearPath HMP IX4400 servers and how to
upgrade or expand existing ClearPath HMP IX4400 servers. This guide is a companion
to the ClearPath HMP IX4400 Server I/O Channel Assignment Planning Guide and
ClearPath HMP IX4400 Server Peripheral Subsystems Configuration Guide. Use these
documents together to properly configure the central electronics complex and
peripheral subsystems for the server.
7848 4078–004

About This Guide
ClearPath HMP IX4400 Server I/O Channel Assignment Planning Guide
(7848 4888)
This guide gives configuration guidelines for the channel assignment of the various
channel types. Other related information includes channel rack configuring, I/O channel
characteristics, I/O performance, subsystem configuration, peripheral partitioning, and
channel cabling. This guide assists system analysts in establishing an initial channel
configuration assignment and in expanding existing configurations. You can use this
guide to optimize a system configuration for best channel usage.
ClearPath HMP IX4400 Server Peripheral Subsystems Configuration Guide
(7848 4391)
This guide is for Unisys ClearPath HMP IX4400 server clients who are interested in new
peripheral subsystems or who want to upgrade or expand their current peripheral
subsystems. This guide is a companion manual to the ClearPath HMP IX4400 Server
Configuration Guide. Use these documents together to properly configure and order
the central electronics complex and peripheral subsystems.
ClearPath HMP IX4800 Server Configuration Guide (7847 5746)
This guide tells how to configure new ClearPath HMP IX4800 servers and how to
upgrade or expand existing ClearPath HMP IX4800 servers. This guide is a companion
to the ClearPath HMP IX4800 Server Peripheral Subsystems Configuration Guide and
ClearPath HMP IX4800 Server I/O Channel Assignment Planning Guide. Use these
documents together to properly configure the central electronics complex and
peripheral subsystems for the server.
ClearPath HMP IX4800 Server I/O Channel Assignment Planning Guide
(7848 4896)
This guide gives configuration guidelines for the channel assignment of the various
channel types. Other related information includes channel rack configuring, I/O channel
characteristics, I/O performance, subsystem configuration, peripheral partitioning, and
channel cabling. This guide assists system analysts in establishing an initial channel
configuration assignment and in expanding existing configurations. You can use this
guide to optimize a system configuration for best channel usage.
ClearPath HMP IX4800 Server Peripheral Subsystems Configuration Guide
(7847 5704)
This guide is for Unisys ClearPath HMP IX4800 server clients who are interested in new
peripheral subsystems or who want to upgrade or expand their current peripheral
subsystems. This guide is a companion manual to the ClearPath HMP IX4800 Server
Configuration Guide. Use these documents together to properly configure and order
the central electronics complex and peripheral subsystems.
The following documents contain detailed information summarized in this overview.
Use the version that corresponds to the hardware model or level of software at your site.
ClearPath HMP IX Series Open Programming Environment (OPE)
Configuration Guide (7831 1032)
This guide contains installation and configuration information for the Open
Programming Environment (OPE).
7848 4078–004 xxi

About This Guide
xxii
ClearPath SMP61000 Series System Configuration Utility User’s Guide
(4619 7901)
This guide describes operation of the system configuration utility (SCU) that must be
run to reconfigure the SMP61000 component if its hardware configuration changes.
ClearPath 2200/3000 Series System Control Facility (SCF) Operations Guide
(7844 8560)
This guide describes how to load operational database (ODB) files, and boot and operate
the 2200 node from the SCF workstation (2200 node system console). If you have a
Model IX4400 ClearPath HMP IX server, refer to the 2200/500 System System Control
Facility (SCF) Operations Guide (7833 3622).
DEPCON Application Configuration and Operations Guide (7833 3960)
This guide describes in detail how to install, configure, and operate DEPCON software.
Microsoft Windows NT Server Version 4.0 Concepts and Planning (69940)
This document describes in detail how to plan a Windows NT server domain.
Open Application Development Environment (OADE) for Windows User Guide
(7848 3989)
This guide describes how to install and use the Open Application Development
Environment (OADE) program development tool.
Open Systems Terminals LT500 X Terminal Software Installation Guide
(4621 5372)
This guide describes SPO X terminal configuration options.
OS 1100 SX 1100 Network File System (NFS) Administrator’s Guide
(7833 2392)
The Network File System is an SX 1100 facility for sharing files among a variety of
hardware systems and operating systems in a network. This guide describes how to
administer NFS, including how to prepare NFS for use, make files available to remote
users, monitor system operations, and troubleshoot problems.
OS 2200 Communications Management System (CMS 1100) Configuration
Reference Manual (7830 9853)
This manual provides detailed explanations of the network definition statements used to
configure CMS 1100.
OS 2200 Communications Management System (CMS 1100) Installation and
Configuration Guide (7830 9846)
This guide describes the overall CMS 1100 installation and configuration process and
explains the required tasks.
7848 4078–004

About This Guide
OS 2200 Enterprise Backup and Restore DOS/Windows Installation and
Operations Guide (3495 3091)
This guide describes installation of the Enterprise Backup and Restore (EBRS) software
workstation module.
OS 2200 Enterprise Backup and Restore Host Installation Guide (3495 3067)
This guide describes installation of the EBRS 2200 node software module.
OS 2200 Enterprise Backup and Restore UNIX Server Installation and
Operations Guide for Windows (3498 1308)
This guide describes installation and operation of the EBRS UNIX server module.
OS 2200 Exec System Software Installation and Configuration Guide
(7830 7915)
This guide describes the stream generation statements needed to reconfigure the
OS 2200 Exec.
OS 2200 Software Library Administrator (SOLAR) End Use Reference Manual
(7831 0604)
This manual describes the SOLAR processor used to register and install OS 2200
software products.
OS 2200 Software Products Installation Guide (7831 0612)
This guide describes how to install OS 2200 software products.
OS 2200 System Base Software Planning and Migration Overview (7831 0349)
This overview describes detailed migration information when moving from earlier
OS 2200 releases to the release levels supported by a ClearPath IX server.
Single Point Operations Console/Enterprise Server Edition Installation Guide
(7833 4075)
This guide provides detailed instructions for installing and configuring Single Point
Operations (SPO) server and console software.
SMP5400 Series System Configuration Utility User’s Guide (7441 4731)
This guide describes operation of the system configuration utility (SCU) that must be
run to reconfigure the SMP5400 (SPO server) if its hardware configuration changes.
TeamQuest Baseline and TeamQuest Online Administration and End Use
Reference Manual (7830 7717)
This manual describes how to install and use TeamQuest Baseline and TeamQuest
Online.
Unisys Volume Manager Installation Guide (4358 5322)
This guide describes procedures for installing Unisys Volume Manager (UVM) software.
UVM provides advanced disk management capabilities for the UNIX node.
7848 4078–004 xxiii

About This Guide
xxiv
UNIX System V Release 4.0 Software Installation Guide (7442 0373)
This guide describes in detail how to install and configure the UNIX operating system on
the UNIX node.
UNIX System V Release 4.0 System Administrator’s Guide (7436 1742)
This guide describes in detail how to perform administrative tasks at computers running
the UNIX System V Release 4.0 operating system.
UNIX System V Release 4.0 User’s Guide (3914 9398)
This guide contains an overview of the UNIX system and tutorials on several basic
utilities (for example, the vi editor).
UREP-WS End Use Guide (7830 8103)
This guide describes how to install and use the Unisys Repository Manager (UREP)
workstation software.
U6000 Series UNE6000-ETH Ethernet Controller Installation Guide
(7441 2842)
This manual describes how to reconfigure the Ethernet controller for the type of TCP/IP
connection being used to connect to the SPO server.
2200 Series Site Configuration Management System (SCMS) Administration
Guide Volume 1, Reference Information (7832 8861)
2200 Series Site Configuration Management System (SCMS) Administration
Guide Volume 2, Tutorial (7833 2434)
These guides describe how to create and maintain configuration information for the
2200 node using the Site Configuration Management System (SCMS).
2200/XPA Systems Migration Guide (7830 9697)
Provides information about migrating to the 2200 node of a ClearPath IX server from an
existing 1100 or 2200 Series system.
Notation Conventions
To simplify and clarify procedures, the following conventions are used throughout this
guide:
If a sample response to a prompting message is shown in a procedure, it is shown as
bold text on the same line as the prompt. For example:
Your system IP Address has been set to xxx.xxx.xxx.xxx
Is that correct [y/N]: Y
If the default value is entered, nothing is shown.
7848 4078–004

About This Guide
The explanation of what you are to enter follows the prompting message and any
sample entry. For example:
1. You are prompted to confirm that the IP address you entered is correct.
Your system IP Address has been set to xxx.xxx.xxx.xxx
Is that correct [y/N]: Y
2. Enter yes (Y) if the entry is correct. Enter no (N) if it is incorrect.
In addition to document titles and notes, plain italic text also is used in two
different contexts as follows:
− It is used to identify the names of windows, as in the Single Point Interface
Utility Session window.
− It also is used to indicate information that may vary. For example:
Your system IP Address has been set to xxx.xxx.xxx.xxx
Is that correct [y/N]:
Bold italic text indicates variable input. For example:
Your system IP Address is? xxx.xxx.xxx.xxx
If the variable input must be formatted in a certain way, as in the above example, the
format is shown.
Reader Response
If you have any questions or comments about this document, you can either mail or fax
the Business Reply Mail Form at the back of this document or send comments to the
following Internet e-mail address:
rsvldoc@rsvl.unisys.com
You can help us by including the following information:
Your name
Your company’s name (optional)
Your Internet e-mail address
The document title and the 11-digit part number for the document (if applicable)
The SB level or software level (software documents only)
The system number and plateau level (hardware documents only)
Any additional information that will help us in responding to your comments
7848 4078–004 xxv

Section 1
Introduction
This introduction briefly describes the following:
Introduction to the ClearPath IX server (1.1)
Summary of the overall system installation procedure (1.2)
1.1. Introduction to ClearPath HMP IX Servers
Heterogeneous multiprocessing (HMP) represents the latest step in the evolution of
client/server computing. Unisys ClearPath HMP IX servers integrate the open
environment of Intel processors with the speed and capacity of custom complementary
metal-oxide semiconductor (CMOS) processors.
An Intel node provides the flexibility and choice of a UNIX or Windows NT Server
environment. An OS 2200 node provides the high-performance stability and resiliency of
an enterprise server environment.
1.1.1. The ClearPath IX Environment
A ClearPath IX server is much more than just a box. It includes an arsenal of tools that
address system administration, operations, and application development. ClearPath IX
servers provide a “total system” solution (see Figure 1–1).
7848 4078–004 1–1

Introduction
1–2
Figure 1–1. The ClearPath HMP IX Environment
7848 4078–004

1.1.2. Software Options
Introduction
One way ClearPath IX servers address the challenge of client/server integration is by
grouping software into predefined packages. Each package has all the software you
need for a specific purpose. A variety of optional software is also available.
Integrated Operating Environment Software
The software foundation of ClearPath IX servers is the integrated operating environment
(IOE). The following table lists some of the highlights of the IOE:
Software Description
DEPCON Integrated printing services
SysAdmin Integrated administration software
SPO/HMP Console Integrated operations software
Pathmate An online integration assistant that helps you set up ClearPath
IX servers and implement cross-product solutions
Enterprise Backup and
Restore System (EBRS)
Open Application Development
Environment (OADE)
A backup and disaster recovery solution for workstations and
servers throughout an enterprise.
Workstation software that enables programmers to develop
OS 2200 applications from a Motif or Windows workstation
TransIT Open/OLTP X/Open compliant OLTP software that allows you to access
OS 2200 data using GUI desktop software
Spyglass and CERN Web
servers
Interoperability Packages
Web server software that enables a ClearPath IX server to
function as a reliable World Wide Web (WWW) or intranet server
Interoperability packages provide cohesive software sets for specific types of
applications. The following interoperability packages are available:
Package Description
Distributed Transaction
Processing (DTP) package
Enables you to distribute transactions across both environments of
the ClearPath IX server as well as other platforms running Tuxedo
software or other X/Open compliant DTP software.
Oracle Database package Provides an Oracle gateway that allows Oracle tools and
applications to access the data in Relational Database Management
System (RDMS) databases.
7848 4078–004 1–3

Introduction
1–4
Solution Enabler Packages
Solution enabler packages deliver software sets for specific solutions. The following
solution enabler packages are available:
Package Description
Enterprise Messaging Server
package
Provides Microsoft Exchange clients with access to an X.400
mail backbone and an X.500 global address book.
Distributed MAPPER package Provides MAPPER software for distributing MAPPER data and
processing across both environments of the ClearPath IX server
Web Commerce Server
package
Optional Software
Enables clients with Web browsers to access transaction
applications over the World Wide Web and private intranets.
In addition to the ClearPath IX software packages, you can also choose from a broad
spectrum of optional software, including off-the-shelf desktop software,
industry-standard databases, premium OS 2200 applications, 3GL compilers, and LINC,
the Unisys 4GL application builder.
1.2. CSE Installation Overview
This subsection provides an overview of the steps taken by a Unisys customer service
engineer (CSE) to make ClearPath IX server hardware ready for use (Hardware RFU).
Refer to the sections referenced in the procedure for more information. Figure 1–2
illustrates these steps.
Hardware components referenced in this procedure are illustrated in the block diagram
in Figure 1–3.
Notes:
Most Windows NT and UNIX integrated operating environment (IOE) software
and 2200 Series system console software is preinstalled on servers shipped to U.S.
sites. Those sites receive IOE media (tapes or CD-ROM), but need not perform
some of the software installation steps shown. Software is not shipped
preinstalled to most non-U.S. sites, and must be installed from installation media.
Monitor concentrator port names referred to in the procedure are default names
assigned as described in 3.1.
7848 4078–004

Figure 1–2. Installation Process Overview
Introduction
7848 4078–004 1–5

Introduction
1–6
Figure 1–3. ClearPath IX Server Default Configuration
Cautions
The ClearPath IX server internal fiber distributed data interchange (FDDI) local
area network (LAN) must not be connected (routed or bridged) to your
production LAN or to the Internet.
See 2.6.2 for cautions regarding selection of IP addresses.
7848 4078–004

These are the steps to follow:
Introduction
Note: Refer to the appropriate IX4400 or IX4000 Series Installation Checklist in
the PLANNET FSS library (see 2.8).
1. Install and cable all ClearPath IX server hardware. Refer to the applicable hardware
installation document for additional information:
ClearPath HMP IX4400 Installation and Service Reference
ClearPath HMP IX4600/4800 Installation and Service Reference
2. Configure the monitor concentrator (switch box). Refer to 3.1.
3. Switch the monitor concentrator to the SCF master position, power on the SCF
master console, and install and configure SCF workstation software. For all SCF
software installation steps, use procedures described in the applicable plateau
definition reference manual (PDRM) as follows:
IX4400 server—Refer to the 2200/500 System Plateau Definition Reference
Manual.
IX4600 or IX4800 server—Refer to the 2200/3000 System Plateau Definition
Reference Manual.
Note: While system console software is loading, you can switch the monitor
concentrator to the Intel node position and install Windows NT or UNIX
IOE software (step 7).
4. Take the following steps to load the SCMS database and operations database (ODB)
files:
a. Reboot the master console in site data facility (SDF) online mode, and load the
factory-built customer SCMS database.
b. Reboot the master console in SCF offline mode and load the factory-built
customer ODB files.
c. Reboot the master console in SCF online mode.
5. Repeat steps 3 and 4 for optional backup master SCF console. Repeat step 4 for
optional slave SCF consoles.
Note: Once the operating system tape has been loaded on the master system
console, you can remove the boot diskette and tape and start loading the
operating system tape on the next system console.
6. Perform a 2200 node system check as follows:
a. Power on the 2200 nodes.
b. Run microdiagnostics.
c. Boot and run SUMMIT.
7. Run SUMMIT to verify intercabinet connections. Note that the minimum level of
CEC500 (model IX4400) is 1R8 and the minimum level of CC3000 (model IX4600 or
IX4800) is 1R1.
7848 4078–004 1–7

Introduction
1–8
8. Run the applicable FDDI LAN Test under UPTS-OS2200 interface sender to
Sxxxxxxx receiver as follows:
IX4400 server—Run SRLANF
IX4600 or IX4800 server—Run CALANF
9. Switch the monitor concentrator to the Intel node position and install and configure
the Windows NT (Section 4) or UNIX (Section 5) IOE as follows:
If Windows NT IOE software is preinstalled, take the following steps:
Configure the hosts file.
Install Windows NT basic IOE packages.
Configure the tape drive unit.
Set balanced server priorities.
If Windows NT IOE software is not preinstalled, take the following steps:
Configure the redundant array of independent disks (RAID) controller and
install RAID controller software.
Create a bootable MS-DOS partition.
Install the Windows NT operating system if it is not already preinstalled. During
this procedure you enter site-specific time zone and networking information.
Install the Windows NT service pack and the Windows NT basic IOE packages.
Configure the hosts file.
Configure the tape drive unit.
Set balanced server priorities.
If UNIX IOE software is preinstalled, you only must install and run the tuning script.
If UNIX IOE software is not preinstalled, you must take the following steps:
Configure the RAID controller.
Install the UNIX operating system if it is not already preinstalled. During this
procedure you enter site-specific time zone and networking information.
Copy UNIX basic IOE packages into the specified spooling directory on disk if
not already preloaded (the packages are preloaded if the operating system is
preinstalled). These include the following:
− Veritas VxFS file system
− Simple network management protocol (SNMP) agent
− EISA FDDI driver
− Graphical Desktop Metaphor (GDM) developer’s kit for internationalization
− Open/OLTP Pathway
− Unisys Volume Manager (UVM)
7848 4078–004

Introduction
Copying the packages does not install them. The Veritas file system, EISA FDDI
driver, and Open/OLTP Pathway are installed when the tuning script is run.
Install and run the tuning script.
Note: UVM provides advanced disk management capabilities (for example, disk
striping, mirroring, and spanning) that cannot be adequately covered by
the tuning script. Refer to the Unisys Volume Manager Installation Guide
for installation procedures.
10. Sites using SPO/HMP Console install and configure SPO/HMP Console and related
software (Section 6). Sites using SPO/ESE must take the steps described in 2.5.
If SPO/HMP Console and related software are preinstalled, take the following steps:
Install and run the tuning script from diskette.
Copy the hosts file to the system consoles.
Remotely install Autoaction Message System (AMS) databases on the 2200 node
system consoles.
If SPO/HMP Console and related software are not preinstalled, take the following
steps:
Install the UNIX operating system on the SPO server (if not already
preinstalled). During this procedure you enter site-specific time zone and
networking information.
Install UNIX operating system patches.
Install X terminal software.
Install the multiport card driver software.
Install the SPO/HMP Console software.
Install and run the tuning script from diskette.
Copy the hosts file to the system consoles.
Remotely install Autoaction Message System (AMS) databases on the 2200 node
system consoles.
11. Enable use of the LT501 X terminal or terminals as follows (Section 7):
a. Start the SPO daemons.
b. Configure the X terminals.
c. Enable communication between the SPO server and each X terminal.
d. Enable remote access to fonts at each X terminal.
7848 4078–004 1–9

Introduction
1–10
e. Enable monitoring (Windows NT), or monitoring and control (UNIX) from the X
terminal:
For Windows NT take the following steps:
− Install UNIX Resource Monitor (URM) agent files on the SPO server so that
SPO/HMP Console can monitor the SPO server.
− Configure the Windows NT FTP server service so that the Windows NT
agent can be transferred.
− Transfer the Windows NT agent to the Intel node using the Single Point
Configuration routine.
− Install the Windows NT agent.
For UNIX take the following steps:
− Create UNIX resource monitor (URM) agent files on the SPO server.
− Copy and install the URM agent files to the UNIX node and redirect console
output by running a script at the UNIX node (7.5.2).
f. Start normal SPO/HMP Console operations.
12. Install OS 2200 software on the 2200 node (Section 8):
a. Open an OS 2200 session as follows:
− If using SPO/HMP Console, click the master console icon (cp_cons01) to
open an OS 2200 session window on the SPO X terminal.
− If using SPO/ESE Console, switch the monitor concentrator to the SCF
master position.
b. Reboot the 2200 node and install the OS 2200 IOE software products from
fast-load tape CPIX-OE1.
c. Establish the contracted System Controlled Performance (SCP) level (model
IX4600 and IX4800 only)
13. Run the interconnect test to verify that the 2200 node and Intel node can
communicate using the FDDI connection (Section 9).
14. Hardware RFU—CSE turns the ClearPath IX server over to the site. Site personnel
must complete the installation by taking the following steps:
a. Install the remaining IOE software (Section 10).
b. Install PathMate and customize the site to their requirements (Section 11).
See 11.1 for a brief description of PathMate features.
7848 4078–004

Section 2
Preinstallation Planning
Prior to installation you must
Prepare the site (2.1)
Submit SCMS configuration information (2.2)
Obtain required hardware and software (2.3)
Prepare for migration to the ClearPath IX server (2.4)
If you are an existing Single Point Operations (SPO) Enterprise Server Edition
(SPO/ESE) site, optionally plan for use of the existing SPO/ESE system for
monitoring the ClearPath IX server (2.5).
Establish networking parameters (2.6)
Obtain a CSE installation checklist (2.8)
Gather required installation information and media (2.7)
2.1. Site Preparation
Refer to the ClearPath HMP IX4400 Installation and Service Reference for detailed
hardware installation information. As indicated by that document—and preinstallation
checklists—you must ensure that the site is ready for installation as follows:
Refer to the following documents for detailed hardware installation information:
ClearPath HMP IX4400 Installation and Service Reference
ClearPath HMP IX4600/4800 Installation and Service Reference
As indicated by those documents, and preinstallation checklists, you must ensure that
the site is ready for installation as follows:
The system layout has been approved.
The peripheral configuration has been approved.
Floor loading and floor-plan layout have been specified.
Doors, hallways, elevators, and other access considerations are met.
The system control facility (SCF) layout has been approved.
The 60-day and 7-day site-readiness checklist requirements have been met.
7848 4078–004 2–1

Preinstallation Planning
2.2. Submitting SCMS Configuration Information
2–2
Several weeks before installation, submit customer-specific configuration information so
that a new Site Configuration Management System (SCMS) database and operations
database (ODB) can be created and shipped to the site. A Technical Information
Bulletin (TIB) will identify
The World Wide Web location from which to obtain configuration forms
The Unisys organization and location to which to submit the forms
2.3. Additional Requirements
Sites also must provide hardware or software to meet the requirements of various
ClearPath IX server products as follows:
PathMate workstation requirement (2.3.1)
SysAdmin Web browser requirement (2.3.2)
Enterprise Backup and Restore (EBRS) license and workstation requirements (2.3.3)
DEPCON workstation requirement (2.3.4)
2.3.1. PathMate Workstation Requirement
The workstation on which PathMate software is run requires
VGA or higher resolution monitor
keyboard, and mouse
486 processor or better
Microsoft Windows 95, Windows NT 3.51 or higher, or Windows for Workgroups 3.11
compatible
Win32s, version 1.30 minimum, for workstations running Windows 3.11 (See the
README file on the PathMate software CD-ROM for information and limitations.)
CD-ROM drive
3-1/2-inch floppy disk drive
32 MB of memory (16 MB with Windows 3.11)
512-MB (.5 GB) mass storage disk
Ethernet TCP/IP network connection
7848 4078–004

2.3.2. SysAdmin Web Browser Requirement
Preinstallation Planning
Sites must provide a Web browser to access the SysAdmin system administration
interface. The browser software can be installed on any workstation within the Ethernet
TCP/IP network. The following Web browsers have been proven to work:
Netscape Navigator 2.0 (Netscape Corporation)
Internet Explorer 2.0 (Microsoft Corporation)
See the SysAdmin Administration Guide for information about additional
requirements.
2.3.3. Enterprise Backup and Restore (EBRS) License and
Workstation Requirements
The EBRS product consists of host, server, and workstation modules. The EBRS
workstation module must be installed on a workstation connected to the same LAN as
the ClearPath IX server. That workstation can be the PathMate workstation if it is
connected to the same LAN as the ClearPath IX server.
Entering the EBRS Site License Number
The EBRS installation media includes a cover letter that identifies the site license
number and the number of workstations allowed by the license. During installation of
EBRS, you must enter the site license number using instructions given in the cover letter.
Record that license number here:
EBRS Site License Number:
EBRS Workstation Requirements
If the EBRS software must be installed on a workstation other than the PathMate
workstation, the requirements are minimal. The EBRS workstation module supports any
workstation with Microsoft Windows, version 3.1 or higher. The use of the MS Anti-Virus
function requires MS-DOS 6.2x or higher. For other restrictions and known limitations
refer to the Enterprise Backup and Restore 2R3 Release Notes.
Caution
To correctly run EBRS software the workstation must be connected to the same
LAN as the ClearPath IX server.
7848 4078–004 2–3

Preinstallation Planning
2.3.4. DEPCON Workstation Requirement
2–4
Sites must provide a workstation on which to run DEPCON. Requirements are as
follows:
486 processor or better
Windows 95 or Windows NT 3.51 or higher
3-1/2-inch floppy disk drive or access to a network for installation
A minimum of 8 MB memory (12 MB with Windows NT)
A hard disk with a minimum of 6 MB available for the DEPCON software (20 MB for
a full installation) and enough space for the files you want to print
A mouse (needed during configuration but not operation)
Note: If you use DEPCON with Windows NT or Windows 95, all printing through
local ports must use the Windows Print Manager. Also, you cannot connect
block multiplexer channel (BMC) printers to the DEPCON workstation.
Refer to the DEPCON Application Configuration and Operations Guide for detailed
information.
2.4. Migration Preparation
If a site is not already using the System Base (SB) software level that will be used on the
ClearPath IX server (for example, SB5R4D2 or SB6D2), it is recommended that they
migrate their existing 1100 or 2200 Series system to that SB level before implementing
the ClearPath IX server. First the site should migrate to the new software environment,
then migrate to the new hardware environment. For general information on migrating
to the appropriate SB, see one of the following documents:
System Base Software Planning and Migration Overview, SB5R4D2
(7831 0349–016)
System Base Software Planning and Migration Overview, SB6D2 (7831 0349–017)
Note: Refer to Appendix D for a list of the OS 2200 software product levels
applicable to ClearPath IX server releases.
2.4.1. Hardware Migration Issues
A site may have issues to deal with when migrating from current 1100 or 2200 Series
hardware to the 2200 hardware component of the ClearPath IX server. For information
on migrating to the 2200 node of the ClearPath IX server, see the 2200/XPA Systems
Migration Guide (7830 9697–002).
7848 4078–004

2.4.2. OS 2200 Print Queue Configuration Requirement
Preinstallation Planning
The OS 2200 master and boot tapes provided with a ClearPath IX server contain new
required station local statements that define print queues for DEPCON. The queues
EMAIL, WINDOC, and DEPERR are required by the PathMate software. For PathMate to
operate correctly, the station local statements that establish those queues must be
included if the site performs a system generation.
2.5. Planning to Use an Existing SPO/ESE Server
The purchase of a ClearPath IX server entitles the site to use SPO/HMP Console
software to operate a stand-alone ClearPath IX server or alternatively to manage one
ClearPath IX server from one or more SPO Enterprise Server Edition (SPO/ESE) servers.
If SPO/ESE is already installed, the site can use the temporary key provided in
Appendix C to enable the SPO interface that allows integration with the ClearPath IX
server.
To enable control of a ClearPath IX server from an existing SPO/ESE server, the site
must
Migrate to SPO/ESE level 4.0 or higher (must be at that level to manage a ClearPath
IX server).
Install UNIX operating system patches if using UNIX System V Release 4.0
version 1.4 (see 6.5).
Customize existing SPO/ESE configurations to add host representations for the
ClearPath IX nodes (2200 and Windows NT or UNIX nodes).
Modify existing Autoaction Message System (AMS) databases to add ClearPath IX
server automation logic and to ensure that it does not conflict with existing
automation logic.
Copy and install agent files to enable communication with the Windows NT or UNIX
node (see Section 6).
Other SPO/ESE installation instructions are contained in the following documents:
Single Point Operations Console/Enterprise Server Edition Installation Guide
Single Point Operations Console/Enterprise Server Administration and
Configuration Guide
1100/90 and 2200 Systems Single Point Interface Installation and Configuration
Guide
Integration of an existing SPO/ESE server with the ClearPath IX server is the
responsibility of the site or is a purchased service available from Unisys.
7848 4078–004 2–5

Preinstallation Planning
2.6. Defining Network Parameters
2–6
During software installation you will be prompted for the following networking
information to configure server components:
Internal FDDI LAN host name or IP address of a node—If prompted for this, you
must enter the applicable predetermined information listed in Appendix A. The
FDDI LAN is a private internal LAN used by the server. Do not connect this LAN in
any way (for example, by a gateway) to any external network.
TCP/IP (Ethernet) host name or IP address of a node—This information identifies a
ClearPath IX server component to the site’s external network. Prior to installation,
work with the site’s network administrator to determine the required information as
follows:
− Sites with an existing network—Use Table 2–1 (see 2.6.1) to plan the
information to enter.
− Sites without an existing network—Identify and configure host names and IP
addresses as described in 2.6.2.
In addition, sites must configure CMS 1100 for the 2200 node and system consoles as
described in 2.6.3.
2.6.1. Planning Network Configuration (Sites With an Existing
Network)
Before starting installation, use Table 2–1 to define network parameters for the
ClearPath IX server. To prevent rework, ensure that
Network names and addresses defined do not conflict with existing network names
and addresses at the site.
All information is accurate.
As shown in Table 2–1, aliases are automatically assigned to the host names you specify.
Those aliases are used in the predefined SPO/HMP Console configurations. If you must
change an alias for some reason, perform the steps described in 11.3 to modify the
SPO/HMP Console default configuration. For example, if an existing ClearPath IX server
on the same LAN is using the default names, you could change the names for an
additional ClearPath IX server to CP_NT2, CP_UNIX2, and IXSPO2.
Caution
Table 2–1 is provided as an installation aid to prevent conflicts with existing
network names and addresses at the site. To prevent rework, ensure that
Table 2–1 contains accurate information before starting installation.
7848 4078–004

Component
Table 2–1. Required Network Names and Addresses
Ethernet
Host Name
Ethernet
IP Address
Preinstallation Planning
Alias Assigned
Automatically for
SPO/HMP
Console*
Windows NT node (if applicable) CP_NT
UNIX node (if applicable) CP_UNIX
SPO server IXSPO
First SPO LT501 X terminal cp_xterm
Additional SPO LT501 X terminals
(optional)
2200 node
2200 system console 1 cp_cons01
(Not prompted)
2200 system console 2 (optional) cp_cons02
(Not prompted)
2200 system console 3 (optional) cp_cons03 through
cp_cons12
(Not prompted)
External router (optional)
Domain name server (DNS)
(optional)***
Additional DNS (optional)
Domain name (for example,
rsvl.unisys.com)
Netmask (optional; only required if
site uses subnet masking)
Not applicable
(not prompted)
Not applicable
(not prompted)
continued
* These are the alias names automatically assigned for the SPO/HMP Console default configurations. If you
need to change this alias, customize the SPO/HMP Console configuration as described in 11.3.
** These names are predetermined. If you need to change them, customize the SPO/HMP Console
configuration (see 11.3).
*** The DNS host name is prompted for when installing UNIX but not Windows NT.
7848 4078–004 2–7

Preinstallation Planning
2–8
Component
Primary Windows Internet Name
Service (WINS) (optional)
Table 2–1. Required Network Names and Addresses (cont.)
Ethernet
Host Name
Not applicable
(not prompted)
Secondary WINS (optional) Not applicable
(not prompted)
Ethernet
IP Address
Alias Assigned
Automatically for
SPO/HMP
Console*
* These are the alias names automatically assigned for the SPO/HMP Console default configurations. If you
need to change this alias, customize the SPO/HMP Console configuration as described in 11.3.
** These names are predetermined. If you need to change them, customize the SPO/HMP Console
configuration (see 11.3).
*** The DNS host name is prompted for when installing UNIX but not Windows NT.
2.6.2. Planning Network Configuration (Sites Without an Existing
Network)
Cautions
IP numbers reserved for private internets by the Internet Assigned Numbers
Authority (IANA) can be used to initially configure the ClearPath IX server; but,
to connect to the external internet in the future, the site must get official IP
addresses and then reconfigure all ClearPath IX server components with those
addresses.
Sites must not use numbers in the range 192.168.57.xxx. Unisys has
selected numbers in that range for the ClearPath IX server’s internal FDDI LAN
(see Appendix A).
Sites without an existing TCP/IP network can initially select IP numbers reserved by the
IANA for private internets. The block of addresses available ranges from 192.168.1.xxx
to 192.168.255.xxx. Using addresses reserved for private networks is an easy way to get
started; but, to connect to the external Internet in the future, the site must get official IP
addresses and reconfigure all ClearPath IX server components with those addresses,
except for the private FDDI interconnect.
7848 4078–004

Preinstallation Planning
Appendix E contains the entire text of the Internet Engineering Task Force (IETF)
Request for Comments (RFC) 1918, which provides guidance on the use of internet
addresses in private TCP/IP networks. Sites without an existing network should read
that appendix before selecting addresses as described in this subsection.
Figure 2–1 illustrates how ClearPath IX server components are connected to an Ethernet
hub when installed. It also illustrates examples of IP addresses that could be assigned to
server components if using numbers available for private LANs.
As indicated in that figure, system console IP addresses are configured according to
instructions described in the applicable Plateau Definition Reference Manual. Other
addresses are prompted for during procedures described elsewhere in this guide.
A suggested methodology for using addresses reserved for private LANs is to use
Ethernet IP addresses in the range 192.168.58.xxx. That ensures that the Ethernet
addresses identify a different LAN segment than the internal FDDI LAN which uses
numbers in the range 192.168.57.xxx. Table 2–2 illustrates how numbers could be
assigned using that methodology.
All sites also must reconfigure CMS 1100 to support IP addresses for the 2200 node and
system consoles (see 2.6.3).
Figure 2–1. Example Use of Private LAN Addresses
(Not Recommended Except for Sites Without an Existing Network)
7848 4078–004 2–9

Preinstallation Planning
2–10
Caution
The IP addresses shown in Figure 2–1 and Table 2–2 are meant to illustrate the
use of IP addresses reserved for private networks. Those addresses are not
necessarily valid addresses for your site. The technique of using private LAN
addresses is not recommended except for sites that currently have no network
and are aware of the requirement to reconfigure the network once official IP
addresses are obtained.
Table 2–2. Example Use of Private LAN Addresses
(Not Recommended Except for Sites Without an Existing Network)
Component
Ethernet
Hostname
Ethernet IP
Address
Alias Assigned
Automatically for
SPO/HMP
Console*
Windows NT node (if applicable) eth1ntsr 192.168.58.3 CP_NT
UNIX node (if applicable) eth1uxsr 192.168.58.4 CP_UNIX
SPO server ixspo 192.168.58.15 IXSPO
First SPO LT501 X terminal ixterm1 192.168.58.16 cp_xterm
Second SPO LT501 X terminal
(optional)
ixterm2 192.168.58.17
2200 node eth122sr 192.168.58.5
2200 system console 1 cp_cons01
(Not prompted)
2200 system console 2 (optional) cp_cons02
(Not prompted)
2200 system console 3 (optional) cp_cons03 through
cp_cons12
(Not prompted)
192.168.58.11
192.168.58.12
192.168.58.13
* These are the alias names automatically assigned for the SPO/HMP Console default configurations. If you
need to change this alias, customize the SPO/HMP Console configuration as described in 11.3.
** These names are predetermined. If you need to change them, customize the SPO/HMP Console
configuration (see 11.3).
7848 4078–004

2.6.3. Reconfiguring CMS 1100
Preinstallation Planning
Following hardware RFU, sites with an existing CMS 1100 configuration can use
PathMate to automatically insert required statements into their CMS 1100 configuration
(assuming at least one TCP/IP path has been established to the 2200 node—see 10.2).
Sites without an existing TCP/IP network, however, must create the CMS 1100
configuration themselves. Example 2–1 shows a partial example of CMS 1100
configuration statements set up by PathMate.
For detailed information about configuring CMS 1100, refer to the CMS 1100
Installation and Configuration Guide.
. Client’s communications setup details
MAX–USERS DEMAND,30 BATCH,3 TIP,10
PROCESS,RSDCSU INTERNET–ADR,IPAD
PROCESS,TIPCSU INTERNET–ADR,IPAD
PROCESS,DDP TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,DDP ;
T–SELECTORS,’DDP$$RT68’,’MTAMHS’,X
RSI BLOCKING–FACTOR,35,10 TIME–OUTS,YES
ADMIN KEYIN–NAME,CMS
TRACE MEDIUM,C ASG,*TRACE(+1).,F///250 SIZE,1792 STATE,LOW
.
. Client’s ethernet configuration statements (uses HLC2–ETH except added FDDI)
LAN,HLC1B INPUT–NODE,HL1B01 OUTPUT–NODE,HL1B02 STATUS,UP
IP,IP1 LINK–LAYER,HLC1B GATEWAY,192.61.248.250
INTERNET–ADR,IPAD IP,IP1,192.61.248.187 IP,V$IP,192.168.57.5 . FDDI ref added
INTERNET–ADR,IPAT IP,IP1,192.61.248.40
.
. CLEARPATH FDDI INTERCONNECT FOLLOWS:
LAN,FDDIVI INPUT–NODE,HLVI01 OUTPUT–NODE,HLVI02 STATUS,UP
IP,V$IP LINK–LAYER,FDDIVI INTERFACE–TYPE,FDDI
. The following NDS is for OPE, and includes a reference to the client’s
. external ethernet network for telnet access. FDDI is for FTP/NFS/etc.
INTERNET–ADR,IPAM IP,V$IP,192.168.57.6 IP,IP1,192.61.248.209
.
. DEPCON CONFIGURATION
PROCESS,V$DEP TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,DEPCON ;
T–SELECTORS,’DEPCON’
.
. OPE CONFIGURATION
. requires special internet–adr for unique addresses to both LANs
PROCESS,AMTSAA TYPE,TSAM INTERNET–ADR,IPAM ;
PASSWORD,SCRAMBLED–EGGS–WITH–HASH–BROWNSA
.
. OPEN/OLTP SHARED IP–ADDRESS CONFIGURATION (uses different port on clients)
PROCESS,V$TM2 TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,TM2200
.
. OPEN/OLTP UNIQUE EXTERNAL IP–ADDRESS & TEST CONFIGURATION
PROCESS,HUBTST TYPE,TSAM INTERNET–ADR,IPAT PASSWORD,VISTATEST
Example 2–1. Sample CMS 1100 Configuration After Modification by PathMate (cont.)
7848 4078–004 2–11

Preinstallation Planning
. UNIACCESS CONFIGURATION (shared demand IP address)
PROCESS,UACP TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,UA
.
. INFOACCESS CONFIGURATION (SHARED DEMAND IP ADDRESS)
PROCESS,IASOCK TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,IA
.
. ORACLE TRANSPARENT GATEWAY CONFIGURATION (SHARED DEMAND IP ADDRESS)
PROCESS,ORALSN TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,ORA
.
. HP OPEN/OLTP SHARED IP–ADDRESS CONFIGURATION (uses different port on clients)
PROCESS,HPTPX TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,OSI–TP ;
T–SELECTORS,’HPTSEL’
. CPFTP SHARED IP–ADDRESS CONFIGURATION (uses FTP port)
PROCESS,CPFTP TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,CPFTP ;
INPUT–QUE–LIMIT,30000
. EBRS PROCESS CONFIGURATION (SHARED DEMAND IP ADDRESS)
PROCESS,EBR0 TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,EBR0
PROCESS,EBR1 TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,EBR1
PROCESS,EBR2 TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,EBR2
PROCESS,EBR3 TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,EBR3
PROCESS,EBR4 TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,EBR4
PROCESS,EBR5 TYPE,TSAM INTERNET–ADR,IPAD PASSWORD,EBR5
.
. Client’s TIP & MAPPER communications definition
TIP CORE–BLOCK–SIZE,112 DRUM–BLOCK–SIZE,112 CMS–NUMBER,1
PID,200,300 PID–POOL,POOLB
APPLICATION,APPONE OWNER,TIPCSU APP–NO,1 PID–POOL,POOLB
PID,400,500 PID–POOL,POOLC
APPLICATION,UDSSRC OWNER,TIPCSU APP–NO,3 PID–POOL,POOLC
.
. CLIENT–DEFINED DCP NETWORK
. following configures the client’s DCP connection
FEP,FRTQ PATHS,PRTQ ;
LOAD,DEV*ABSDEV.TOTAL$RTQ ;
STATUS,UP ALL–CONS–MSGS,YES
PATH,PRTQ INPUT–NODE,RTQDVI OUTPUT–NODE,RTQDVO ; . I0BL00
CHECKSUM,ON OWNER,FRTQ STATUS,UP TYPE,BLOCK
.
STATIC–BANKS DEMAND,DNS,TCP/IP,TIP–MCB,OSI
2–12
Example 2–1. Sample CMS 1100 Configuration After Modification by PathMate
7848 4078–004

2.7. Preinstallation Checklist
Preinstallation Planning
Table 2–3 shows installation media you need and information you must enter during the
installation procedures described in this guide. During several procedures you must
enter the networking information you gathered in Table 2–1. To prevent redundancy, the
required networking information is not listed in Table 2–3.
Note: You must log in several times during installation procedures outlined in
Table 2–3. Default passwords to use are as follows: administrator (for the
Windows NT node if applicable) and unisys1234 (for the SPO server, SPO X
terminal, and UNIX node if applicable). To prevent unauthorized access, the
site must change those passwords following hardware RFU.
Table 2–3. Preinstallation Checklist
Information or Media Required
Section 4. Windows NT IOE
If Windows NT is preinstalled perform only the procedures in 4.2. If Windows NT is not
preinstalled, perform the procedures in all subsections other than 4.2.
Time estimate:
With this checklist completed, all installation software media readily available, and Windows
NT not preinstalled, the procedures in this section take about 1 hour.
4.1 Running the SCU (If Required)
If the hardware configuration of the Intel node has been changed by the site, you need to
run the system configuration utility (SCU) applicable to the model Intel node being installed.
Media needed:
• SCU software diskette
• Driver software (optional)—SCU prompts for diskettes containing driver software
other than those described elsewhere in this checklist.
4.2 Steps to take if Windows NT is Preinstalled
If Windows NT is preinstalled you must complete the installation by configuring site-specific
information.
Media needed:
A blank diskette for creating an emergency repair disk.
continued
7848 4078–004 2–13

Preinstallation Planning
2–14
Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
Name and Organization screen
Name __________________________
Determine the name the site wants identified with the Windows NT node (for example, the
administrator’s name or the Windows NT owner name).
Organization _____________________________
Determine the organization name the site wants identified with the Windows NT node.
Registration screen
Windows NT Registration Number:
The Windows NT registration number is found on a Certificate of Authentication provided
with the installation media.
Server Type screen
Determine the Windows NT server type:
Primary Domain Controller (PDC)
Directly maintains security and user account information in the master copy of the
domain’s directory database.
Backup Domain Controller (BDC)
Maintains a replicated copy of the directory database maintained by the PDC. Can be
promoted to serve as a PDC.
Standalone Server (default recommendation)
Recommended in the following circumstances:
if the server is to perform time critical tasks and the site does not want it spending
time authorizing domain logon attempts or receiving synchronized copies of the
domain’s directory database.
If the site wants this server to have a different administrator or different user
accounts from the rest of the servers in the domain.
A standalone server can participate in a domain, although that is not required.
For more information, see the domain planning information in Microsoft Windows NT Server
Version 4.0 Concepts and Planning.
4.4 Configuring a Bootable MS-DOS Partition
Create a bootable MS-DOS partition on RAID drive 0 to ensure that the Intel node can be
recovered in case of failure, .
Media needed:
An MS-DOS diskette that contains fdisk.exe and format.com.
continued
7848 4078–004

Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
4.5. Installing and Configuring Windows NT (if not preinstalled)
Preinstallation Planning
Media needed:
• Setup diskettes—labeled “Microsoft Windows NT Server Setup Disk x” (where x is 1,
2, and 3)
• Windows NT CD-ROM—labeled “Microsoft Windows NT Server”
• RAID drivers diskette—labeled “MegaRAID Drivers and Utilities Diskette Windows NT
4.0X”
• Video drivers diskette—labeled “NT 4.0 Supplementary Drivers Diskette”
• Blank 3-1/2 inch diskette (label this diskette “Emergency Repair Disk”)
Name and Organization screen
Name __________________________
Determine the name the site wants identified with the Windows NT node (for example, the
administrator’s name or the Windows NT owner name).
Organization _____________________________
Determine the organization name the site wants identified with the Windows NT node.
Registration screen
CD-KEY ______________________________________
To register Windows NT, you need the key number printed on a label on the back of the
Windows NT CD-ROM jewel case.
SNMP Properties screen
System administrator name __________________________
Phone number __________________________
Location (room number) __________________________
Date/Time Properties screen; Time Zone tab screen
Time zone at the site _____________________________
Daylight saving time
Check the checkbox provided on the Time Zone tab screen to indicate daylight saving
time is used. Leave empty if daylight saving time is not used.
4.8 Installing the Windows NT Service Pack
Install the Windows NT service pack from CD-ROM.
Media needed:
CD–ROM labeled “Windows NT 4.0 Service Pack 1”
continued
7848 4078–004 2–15

Preinstallation Planning
2–16
Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
4.9 Installing and Configuring RAID Software
Install the RAID controller software from diskette.
Media needed:
Diskette labeled “MEGARAID Drivers and Utilities Diskette Windows NT 4.0X”
4.10 Installing and Configuring the Video Drivers
Install the video driver software from diskette.
Media needed:
Diskette labeled “NT 4.0 Supplementary Driver Disk” (part number 3815036-000).
4.11 Updating the Emergency Repair Disk
Create a new emergency repair disk (if Windows NT preinstalled) or update the previously
created repair disk (if Windows NT not preinstalled).
Media needed:
A blank diskette or the emergency repair disk previously created when configuring
Windows NT.
4.12 Installing IOE Software Products
Install Open/OLTP Pathway.
Media needed:
Open/OLTP Pathway distribution tape.
4.13 Configuring the Tape Drive Unit
Configure the tape drive in the Intel node.
Media needed:
Windows NT CD-ROM labeled “Microsoft Windows NT Server”
continued
7848 4078–004

Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
Section 5. UNIX IOE
Preinstallation Planning
If UNIX is preinstalled perform only the procedures in 5.2. If UNIX is not preinstalled,
perform the procedures in all subsections other than 5.2.
Time estimate:
With this checklist completed, all installation software media readily available, and UNIX not
preinstalled, the procedures in this section take about 2 hours.
5.2 Steps to take if UNIX is Preinstalled
If the UNIX operating system is preinstalled, you install and run the tuning script from
diskette as described in this subsection. The tuning script prompts for site-specific
information that cannot be provided at the factory.
Media needed:
Tuning diskette—Labeled “CPTUNE 2.0 SMP61000, SMP5400”
Time zone at the site ______________________
Daylight saving time Yes ___ No ___
You are prompted whether or not you want daylight saving time support.
Do you want SNMP agent installed? (optional) Yes _____ No _____
If the site wishes to control the ClearPath IX server using an SNMP manager such as
HP OpenView, you must install the SNMP agent. Otherwise, you do not need to install
SNMP agent.
Do you want GDM installed? (optional) Yes _____ No _____
If the site will be developing X Window applications, you must install the GDM
development package. Otherwise, you do not need to install the GDM development
package.
5.3. Configuring the RAID Controller
Install and configuring the RAID disk array controller (DAC).
Media needed:
• System configuration utility (SCU) diskette
• DACCFG utility diskette labeled “DAC960P Configuration and Utilities”
continued
7848 4078–004 2–17

Preinstallation Planning
2–18
Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
5.4. Installing the UNIX Operating System (if not preinstalled)
Media needed:
• Boot diskette—labeled “U6000 & SMP Systems, UNIX System Release 4.0 Boot
Diskette”
• Operating system CD-ROM—labeled “U6000 Series UNIX System V Release 4.0
Software”
• Operating system tape—labeled “OS SVR4 Release 1.4-Runtime”
• Driver software (optional)—If the hardware configuration has been modified at the
site, the System Configuration Utility (SCU) must be run. SCU prompts for the driver
diskettes. Refer to the applicable System Configuration Utility User’s Guide for
detailed instructions.
Keyboard type (language) to use __________________________
Time zone at the site ________________________
Daylight saving time—Yes ___ No ___
You are prompted whether or not you want daylight saving time support.
5.5. Copying IOE Products to the Spooling Directory (if not preinstalled)
Media needed:
If software is not preinstalled, copy the following IOE products from the installation media
into the default spooling directory for later installation by the tuning script:
• Unisys FDDI driver (SK-FDDI) (diskette)
• Veritas VxFS file system (tape)
• Simple Network Management Protocol (SNMP) agent (tape)
• Open/OLTP Pathway (tape)
• Volume manager (tape)
• Graphical Desktop Metaphor (GDM) developer’s kit (located on the UNIX operating
system CD-ROM or tape 2 if the operating system is on tape)
If software is preinstalled, those products already reside in a spooling directory.
5.7. Installing and Running the Tuning Script (Site-Installed UNIX)
After installing the UNIX operating system (software was not preinstalled), install and run the
tuning script from diskette as described in this subsection.
The tuning script asks whether you want to install SNMP agent and GDM software. It does
not prompt for information you already provided during operating system installation.
Media needed:
Tuning diskette—Labeled “CPTUNE 2.0 SMP61000, SMP5400”
continued
7848 4078–004

Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
Do you want SNMP agent installed? (optional) Yes _____ No _____
Preinstallation Planning
The SNMP agent software copied to the spooling directory when the UNIX operating
system is installed needs to be installed by the tuning script only if the site wishes to
control the ClearPath IX server using an SNMP manager such as HP OpenView.
Otherwise, you do not need to install SNMP agent.
Do you want GDM installed? (optional) Yes _____ No _____
The GDM development package copied to the spooling directory when the UNIX
operating system is installed needs to be installed by the tuning script only if the site will
be developing X Window applications. Otherwise, you do not need to install the GDM
development package.
Section 6. Installing SPO/HMP Console and Related Software
If SPO/HMP Console and related software are preinstalled, perform only the procedures
in 6.2. If software is not preinstalled, perform the procedures in all subsections other than
6.2.
Time estimate:
If SPO/HMP Console and related software are not preinstalled, the required procedures
(including those in Section 7 which are performed contiguously) take from 4 to 6 hours.
If the software is preinstalled, the remaining procedures take about 1 hour.
6.1 Running the SCU (If Required)
If the hardware configuration of the SPO server has been changed by the site, you need to
run the system configuration utility (SCU).
Media needed:
• SCU software diskette
• Driver software (optional)—SCU prompts for diskettes containing driver software
other than those described elsewhere in this checklist.
6.2 Steps to Take if Software is Preinstalled
If the UNIX operating system and SPO/HMP Console software are preinstalled on the SPO
server, install and run the tuning script from diskette as described in this subsection.
The tuning script prompts for site-specific information that cannot be provided at the
factory.
Media needed:
• Tuning diskette—Labeled “SMP5400 Tuning Scripts”
• Empty (formatted) MS DOS diskette (3-1/4 inch)—Diskette on which to save the hosts
files for copying to the system consoles.
Keyboard type (language) to use ________________________
continued
7848 4078–004 2–19

Preinstallation Planning
2–20
Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
Time zone at the site ________________________
Daylight saving time Yes ___ No ___
You are prompted whether or not you want daylight saving time support.
Number of 2200 node system consoles (1 through 12) ___________
Enter the number of 2200 node system consoles.
Number of X terminals ________
Enter the number of LT501 X terminals.
6.3 Installing UNIX on the SPO Server (if not preinstalled)
Media needed:
• Boot diskette—labeled “U6000 & SMP Systems, UNIX System Release 4.0 Boot
Diskette”
• Operating system CD-ROM—labeled “U6000 Series UNIX System V Release 4.0
Software”
Keyboard type (language) to use ________________________
Time zone at the site ________________________
Daylight saving time Yes ___ No ___
You are prompted whether or not you want daylight saving time support.
6.5 Installing UNIX Operating System Patches (if not preinstalled)
Media needed:
Tape containing UNIX operating system patches—labeled “SPO Server OS 1.4 Patches”
6.6 Installing X Terminal Software (if not preinstalled)
Media needed:
Tape containing the LT501 X terminal software—labeled “LT500-SW”
6.7. Installing the Multiport Card Driver (if not preinstalled)
Media needed:
Diskette containing multiport card driver software—labeled “US6000–ACD”
6.8. Installing the SPO/HMP Console Software (if not preinstalled)
Media needed:
Tape containing the SPO/HMP Console and Electronic Documentation software—labeled
“SP Operation”
continued
7848 4078–004

Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
6.9. Installing and Running the Tuning Script (Site-Installed UNIX)
Preinstallation Planning
After installing the UNIX operating system on the SPO server (software not preinstalled),
install and run the tuning script from diskette as described in this subsection.
The tuning script does not prompt for information you already provided during operating
system installation.
Media needed:
• Tuning diskette—Labeled “SMP5400 Tuning Scripts”
• Empty (formatted) MS DOS diskette (3–1/4 inch)—Diskette on which to save the
hosts files for copying to the system consoles.
Number of 2200 node system consoles (1 through 12) ___________
Enter the number of 2200 node system consoles.
Number of X terminals ________
Enter the number of LT501 X terminals.
6.10. Copying the Hosts File (Done at System Consoles)
Media needed:
You need the diskette created when the tuning script was run (6.2 or 6.9) that contains
the hosts files for copying to the system consoles.
Section 7. Enabling Use of the X Terminal
After installing SPO/HMP Console software (Section 6), you must configure each X terminal
and enable monitoring of the Windows NT node or monitoring and control of the UNIX node
(whichever is applicable).
7.2. Configuring Each X Terminal
Keyboard type (language) to use ________________________
Time estimate:
Section 8. OS 2200 IOE
With this checklist completed and all installation software media readily available, the
procedures in this section take about 2 hours.
8.2. Performing the Initial Boot
Media needed:
Boot tape EXEC-BOOT.
continued
7848 4078–004 2–21

Preinstallation Planning
2–22
Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
8.2.1. Initial Boot Steps if Boot Partition is Not Activated
If you need to activate a partition, you must enter the partition name to be activated.
Partition name ____________________________
8.3. Installing Products from Fast-Load Tape CPIX-OE1
Media needed:
Fast-load tape—labeled “CPIX-OE1” (may be a single tape or a two-tape set)
Reel number for CPIX-OE1 tape 1 ___________________
Reel numbers can be any character string up to six characters in length.
Reel number for CPIX-OE1 tape 2 of 2 ___________________
This is applicable only if CPIX-OE1 is a two-tape set.
8.4. Establishing the Performance Level (IX4600 and IX4800)
Media needed:
Exec key tape—labeled “System Controlled Performance Key Tape” (applicable to
models IX4600 and IX4800 only)
Time estimate:
Section 9. Verifying Interconnect Communications
With this checklist completed and all installation software media readily available, the
procedures in this section take 2 hours.
Media needed:
Applicable tape containing microcode and the “ping” test for verifying communications as
follows:
• Model IX4400
CEC500 tape (minimum level of 1R8)
Host LAN Controller-2 (HLC2) microcode on cartridge tape. Found in the HLC2-FMK
package which comes with the HLC2.
• Model IX4600/ IX4800
CC3000 tape (minimum level of 1R1)
Channel adapter microcode tape
The Diagnostic Software Peripheral Equipment Routines (DSPER) also should be installed
following installation of the CEC tape.
continued
7848 4078–004

Table 2–3. Preinstallation Checklist (cont.)
Information or Media Required
9.1. Installing HLC2 Microcode (if applicable)
Reel number for tape ___________________
Reel numbers can be any character string up to six characters in length.
9.2. Installing Channel Adapter Microcode (CSIOP) (if applicable)
Reel number for tape ___________________
Reel numbers can be any character string up to six characters in length.
9.3. Installing the CEC Tape
Reel number for tape ___________________
Reel numbers can be any character string up to six characters in length.
2.8. Obtaining a CSE Installation Checklist
Preinstallation Planning
Installation checklists for CSEs are available online from PLANNET either from a Milton
Keynes (MK) MAPPER system or Elk Grove (E2) MAPPER system that contains the
PLANNET files. The checklists provide the order of installation for a style of equipment
and include the time needed to perform each step. Access the checklists as follows:
1. Sign on to the MAPPER system.
2. Type PLANNET and press Enter (or the transmit key).
3. Use the Tab key to select the Field Support Service (FSS) Library and press Enter.
You now have access to the FSS Master Index.
4. Tab to the Major System Bulletins selection and press Enter.
5. Tab or roll to the applicable ClearPath HMP IX server installation checklist
document and press Enter. For convenience, print a copy of the document for quick
reference during the installation.
Note: The PLANNET program contains a PLANNET HELP file. If necessary, use
that file to become proficient with the PLANNET program.
Checklists and other support documents also are available on the Internet. Search for
TIB LGS-0627 (use the keyword Internet) for instructions on logging on to the site.
7848 4078–004 2–23

Section 3
Configuring and Using the Monitor
Concentrator
For easy identification of each system being monitored, you should assign unique names
to each port of the monitor concentrator as described in 3.1. Use of the monitor
concentrator is described in 3.2.
3.1. Configuring the Monitor Concentrator
The procedure for assigning names to each port of the monitor concentrator
(see Figure 3–1) is as follows:
1. Press Print Screen. The On Screen Configuration and Activity Reporting (OSCAR)
selection screen appears in the upper left corner of the display.
2. Press F2. The ADVANCED MENUS screen appears.
3. Use the left and right arrow keys to select the Setup menu. Then use the up and
down arrow keys to select Names and press Enter. A PORT NAMING window
similar to Figure 3–1 appears.
4. Use the arrow keys to select the port whose name you want to enter or change.
Type in the desired name. Up to 12 characters can be entered. Legal characters are
A–Z, 0–9, and the hyphen character (-). Lowercase letters are converted to
uppercase. Press Backspace to delete an incorrect entry.
5. When done, press Enter.
6. Press Escape to exit.
Figure 3–1. Default Monitor Concentrator Port Name Assignments
7848 4078–004 3–1

Configuring and Using the Monitor Concentrator
3–2
Note: Procedures in this document refer to ports by the default assignments shown
in Figure 3–1. Refer to the Apex Outlook Concentrator User Guide for detailed
information on configuring the monitor concentrator.
3.2. Using the Monitor Concentrator
In normal operating mode, the number of the port being monitored appears in the upper
left corner of the monitor screen. To switch to a different port, take the following steps:
1. Press Print Screen. The port selection menu appears in the upper left corner of the
monitor screen.
2. Use the arrow keys to select the desired system, then press Enter.
Switching disconnects the keyboard, mouse, and monitor from one system and switches
them to the selected system.
7848 4078–004

Section 4
Installing Windows NT on the
Intel Node
The Windows NT integrated operating environment (IOE) includes the Windows NT
operating system and application packages that run under Windows NT. To prepare for
installation you must gather information and media needed during the installation (see
Section 2). You also must determine if the Windows NT operating system is preinstalled.
To determine whether or not the Windows NT operating system is preinstalled, take the
following steps:
1. Power the Intel node on and allow it to fully boot (takes about 2 minutes).
2. If the Windows NT Software License Agreement screen appears, the operating
system is installed.
If Windows NT is preinstalled, perform the steps described in 4.2.
If Windows NT is not preinstalled, take the following steps
1. Run the System Configuration Utility (SCU) if required (4.1).
2. Configure the RAID controller (4.3).
3. Create a bootable MS-DOS partition (4.4).
4. Install the Windows NT operating system (4.5).
5. Log on to Windows NT (4.6).
6. Configure the hosts file (4.7).
7. Install Windows NT service pack (4.8).
8. Complete RAID configuration (4.9).
9. Install video drivers (4.10).
10. Install IOE software products (4.11).
11. Configure the tape drive unit (4.12).
12. Set balanced server priorities (4.13).
13. Update the emergency repair disk (4.14).
7848 4078–004 4–1

Installing Windows NT on the Intel Node
4.1. Running the SCU (If Required)
4–2
You need to run the system configuration utility (SCU) only if the hardware
configuration of the Intel node has changed since the node was installed (for example,
if a new circuit card has been installed). If no changes have been made, you need not
run SCU.
You must run SCU per the System Configuration Utility User’s Guide applicable to the
model of Intel node in the server. SCU procedures are model specific.
4.2. Steps to take if Windows NT is Preinstalled
If Windows NT is preinstalled, you need to complete the installation by configuring
site-specific information. Take the following steps:
Note: Before powering on the Intel node, verify that the preloaded RAID diskettes are
installed into the correct bays as labeled on the disks. See the Aquanta QR/6
system map for the location and layout of the drive bays.
1. Power the Intel node on and allow it to fully boot (takes about 2 minutes).
During the boot, the following message may occur:
Configuration of NVRAMM and drives mismatch
Run View/Add Configuration option of configuration utility
Press any key to enter the Configuration Utility
That message indicates that the RAID configuration saved in non-volatile memory by
the RAID controller does not match the current configuration. Take the following
steps to correct the problem (if that message does not appear, proceed to step 2):
a. As indicated by the message, press any key to enter the configuration utility.
The Management Menu for configuring RAID appears as follows:
––––Management Menu––––
Configure
Initialize
Objects
Format
Rebuild
Check Consistency
Disable BIOS
b. Select Configure, then press Enter.
7848 4078–004

A Configure Menu appears as follows:
––––––Configure–––––
Easy Configuration
New Configuration
View/Add Configuration
Clear Configuration
c. Select View/Add Configuration, then press Enter.
A popup menu appears.
d. Select View Disk Configuration, then press Enter.
Installing Windows NT on the Intel Node
A screen similar to appears, except the disks say ONLIN A1-1 and ONLIN A1-2
instead of READY.
e. Press F10.
A Save Configuration? menu appears.
f. Select YES, then press Enter.
You are returned to the previous menu.
g. Press any key to continue.
h. Press Esc three times to back out of all menus.
The following prompt appears:
––––––EXIT?–––––
YES
NO
i. Select YES, then press Enter.
j. Press Ctrl-Alt-Del to reboot.
A Software License Agreement screen appears.
2. Have the client, or a representative of the client, accept the license agreement as
follows:
a. Read the contents of the first page, then press the Page Down key to read the
next page.
b. When you have read the entire agreement, click I agree.
c. Click Next to proceed.
After a few seconds, a Windows NT Setup screen appears, followed by a Name and
Organization screen.
7848 4078–004 4–3

Installing Windows NT on the Intel Node
4–4
3. Enter Name and Organization as follows:
a. Name field—Enter the user name the site wants identified with the Windows NT
environment.
b. Press the Tab key to advance to the Organization field.
c. Organization field—Enter the organization the site wants identified with the
Windows NT environment.
d. Click Next to proceed to the next screen.
A Registration screen appears asking for the registration number from the
Certificate of Authentication.
4. Enter the registration number as recorded in Table 2–1, or directly from the
Certificate of Authentication, as follows:
a. Type the required digits in each field.
b. Click Next to proceed.
The Computer Name screen appears.
5. In the Name field, enter the host name from Table 2–1 by which the Windows NT
node will be identified on the external TCP/IP network. Click Next to proceed to the
next screen.
The Server Type screen appears.
6. Click Primary Domain Controller (PDC), Backup Domain Controller (BDC), or
Standalone Server as chosen by the site (see Table 2–1). Then click Next to proceed.
Note: Standalone Server was chosen as the option for this procedure. If you
choose the PDC or BDC option you may need to respond to additional
prompts. See Microsoft Windows NT Server 4.0 Concepts and Planning for
more information.
The Administrator Account screen appears.
7. Enter and confirm the password for the administrator’s account as follows:
a. In the Password field, type the password administrator.
b. Press the Tab key to go to the Confirm Password field. Type administrator in
that field.
c. Click Next to proceed.
Note: Following installation, the site must change the default password
(administrator) to a different password (see the caution in 4.6).
After about 1 minute, a Windows NT Setup screen for configuring networking
appears.
8. Click Next.
7848 4078–004

Installing Windows NT on the Intel Node
After a brief wait during which the setup program searches for network adapters,
the following message appears:
SK-NET FDDI EISA Adapter Card Setup
Continue Cancel Help
9. Click Continue.
An error message appears as follows:
The IP Address key has an invalid IP address.
Please correct the problem after the property
sheet is displayed.
10. Click OK.
After about 1 minute, a tabbed Microsoft TCP/IP Properties screen appears.
11. Set networking information for the 3Com Ethernet adapter card and the SK-NET
FDDI adapter card as follows:
a. Use the scroll bar to select the 3Com Ethernet adapter from the drop-down list
of adapters
3Com Fast EtherLink PCI 10/100BASE-T Adapter
b. Click the IP Address tab, then enter the following IP address information:
− Click Specify an IP address.
− In the IP Address field enter the IP address for the Windows NT node from
Table 2–1, then press Tab.
− Change the subnet mask to the mask address from Table 2–1, or skip this
field (accept the default).
− If the site has a gateway (router), click Advanced (otherwise skip this step)
and take the following steps:
− Click Add.
− In the New Gateway field, type the gateway address from Table 2–1.
− Click Add.
The address appears in the Installed gateways: list box.
− Repeat these steps for each additional gateway required, then click OK
when done.
c. Skip this step if the site does not wish to implement the Windows Internet Name
Service (WINS). If they do choose to implement WINS, click the WINS Address
tab, then enter the following WINS information:
− In the Primary WINS Server field, type the address from Table 2–1, then
press Tab.
7848 4078–004 4–5

Installing Windows NT on the Intel Node
4–6
− If applicable, type the IP address of the Secondary WINS Server from
Table 2–1.
d. Use the scroll bar to select the SK-NET FDDI adapter card from the drop-down
list of adapters
SK-NET FDDI Adapter
e. Click the IP Address tab, then enter the following IP address information:
Caution
Do not enter a gateway address for the FDDI adapter. The FDDI LAN is a private
internal network used solely for the ClearPath HMP IX server nodes.
− Click Specify an IP address.
− In the IP Address field enter 192.168.57.3 as the IP address for the Windows
NT node (see Appendix A), then press Tab.
− Change the subnet mask to 255.255.255.0.
f. If the site has a domain name server (DNS), click the DNS tab (otherwise skip
this step), and take the following steps:
− Enter the IP address for the first DNS from Table 2–1.
− Click Add.
The DNS address is added to the search order list box.
− Repeat these steps for each additional DNS server.
12. Click OK.
The following message appears:
At least one adapter cards has an empty WINS address.
Do you want to continue?
13. Click YES.
Windows NT configures the network, then the following message appears:
Windows NT has been installed successfully.
Remove floppies and choose Restart Computer.
14. Click Restart Computer.
After a few seconds, the Windows NT Server logo appears and you are prompted to
press Ctrl-Alt-Del to log on.
15. Complete the installation by taking the steps described in the following subsections:
7848 4078–004

a. Log on to Windows NT (4.6).
b. Configure the hosts file (4.7).
c. Complete the RAID controller configuration (4.9).
d. Install IOE software products (4.11).
e. Configure the tape drive unit (4.12).
f. Set balanced server priorities (4.13).
g. Create an emergency repair disk (4.14).
Installing Windows NT on the Intel Node
In addition, you need to configure site-specific characteristics of Windows NT such as
the following:
Local date and time
Network services such as WINS, DNS, file transfer protocol (FTP) security, and
others
Windows NT license mode
For instructions
Refer to Windows NT help for the specific characteristic that you wish to
reconfigure.
For reconfiguring the RAID controller, see the MegaRAID and MegaRAID Ultra PCI
SCSI Disk Array Controller User’s Guide.
7848 4078–004 4–7

Installing Windows NT on the Intel Node
4.3. Configuring the RAID Controller
4–8
After running SCU (if necessary), configure the RAID disk controller for RAID level 1
(mirroring) for two disks units—even if more units are available.
Sites can reconfigure a different RAID level following hardware RFU if desired. For
detailed information see the MegaRAID and MegaRAID Ultra PCI SCSI Disk Array
Controller User’s Guide.
Notes:
Switch the monitor concentrator to the Intel node position before beginning
(see 3.2).
In step 2, you must press Ctrl-M within a few seconds to enter the RAID controller
configuration procedure, otherwise the normal boot procedure continues.
Take the following steps to run the RAID controller configuration utility:
1. Power on or reboot the Intel node.
Several start-up messages appear including a prompt to press Ctrl-M as follows:
MEGARAID ULTRA PCI ADAPTER BIOS VERSION x.xx
Copyright(c) AMERICAN MEGATRENDS INC.
Host Adapter–1 Firmware Version x.xx DRAM size xxx MB
1 Logical Drives found on the Host Adapter
1 Logical Drives handled by BIOS
>
2. Press Ctrl-M to start the RAID BIOS configuration utility.
A Management Menu for configuring RAID logical arrays appears as follows:
––––Management Menu––––
Configure
Initialize
Objects
Format
Rebuild
Check Consistency
Disable BIOS
3. Select the Configure option using the arrow keys, then press Enter.
A Configure menu appears:
––––––Configure–––––
Easy Configuration
New Configuration
View/Add Configuration
Clear Configuration
7848 4078–004

Installing Windows NT on the Intel Node
Note: Unless noted otherwise, use the arrow keys to select menu options
throughout the rest of this procedure.
4. Select Clear Configuration, then press Enter:
Note: This step clears from non-volatile memory any RAID configuration that
may have been set at the factory.
The following prompt appears:
––––Clear configuration?––––
YES
NO
5. Click Yes.
The configuration is cleared and you are returned to the Configure menu
6. Select the Easy Configuration option, then press Enter.
After a brief wait, an Easy Configuration–ARRAY SELECTION MENU appears
showing the available disk drive units (Figure 4–1 shows two units available).
Figure 4–1. Easy Configuration–ARRAY SELECTION MENU
7848 4078–004 4–9

Installing Windows NT on the Intel Node
4–10
7. Select the first drive unit (ID 0), then press the spacebar key.
The ID 0 drive indicator changes from READY to ONLIN A1-1. A1-1 (which blinks)
indicates that drive unit 1 is selected for array 1. The cursor automatically moves to
the next drive unit.
8. Select the Channel-2 ID 4 drive unit, then press the spacebar to select that drive unit
for array 1.
The ID 4 drive indicator changes from READY to ONLIN A1-2.
9. Press Enter to stop selection of the drive units.
A Logical Drives Configured window appears together with a smaller Logical
Drive 1 menu (Figure 4–2).
10. Select RAID= in the Logical Drive 1 menu, then press Enter.
A list of available RAID levels appears.
11. Select RAID level 1, then press Enter.
Note: Do not change any settings in the Advanced Menu. The default parameters
are acceptable for RAID level 1.
Figure 4–2. Logical Drives Configured Screen
7848 4078–004

12. Select Accept, then press Enter.
Installing Windows NT on the Intel Node
The Logical Drives Configured window shows the configuration (Figure 4–2).
13. Press Esc.
The following prompt appears:
Save Configuration?
YES
NO
14. Highlight YES and press Enter.
You are returned to the Management Menu and Configure menu screens.
15. Press Esc twice to escape from the other screens and return to the Management
Menu.
16. Select Initialize, then press Enter.
A screen appears showing the logical drives configured. Also, a Logical Drives
menu appears as follows:
––––Logical Drives––––
Logical Drive 1
17. Press the space bar to select Logical Drive 1 (if it is not already selected), then press
F10 to initialize it.
The following prompt appears:
––––Initialize Drives?––––
YES
NO
18. Select YES, then press Enter.
A bar graph message shows progress of the initialization (takes about 30 minutes).
19. When initialization is complete, press any key to continue.
You are returned to the Management Menu screens.
20. Press the Esc key twice to exit.
The following prompt appears:
––EXIT?––
YES
NO
7848 4078–004 4–11

Installing Windows NT on the Intel Node
4–12
21. Select YES, then press Enter.
The following prompt appears:
Configuration has changed. Press Ctrl-Alt-Del to reboot.
22. Before pressing Ctrl-Alt-Del to reboot, insert the diskette for booting MS-DOS
(see 4.4).
23. Press Ctrl-Alt-Del to reboot. After booting, proceed with the procedures for creating
a bootable MS-DOS partition in 4.4.
7848 4078–004

Installing Windows NT on the Intel Node
4.4. Creating a Bootable MS-DOS Partition
To ensure that you are able to recover the Intel node in case of failure, create a bootable
MS-DOS partition as follows:
1. Boot from an MS-DOS diskette that contains fdisk.exe and format.com.
2. At the A: prompt, type fdisk Enter.
The following menu appears:
Choose one of the following:
1. Create DOS partition or Logical DOS Drive
2. Set active partition
3. Delete partition or Logical DOS Drive
4. Display partition information
Enter choice: [1]
3. Type 1, then press Enter.
The following menu appears:
Choose one of the following:
1. Create Primary DOS Partition
2. Create Extended DOS Partition
3. Create Logical DOS Drive(s) in the Extended DOS
Partition
Enter choice: [1]
4. Type 1, then press Enter.
The following message appears:
Do you wish to use the maximum available size for a primary
DOS partition and make the partition active (Y/N)...?
5. Type N, then press Enter.
A message stating total available disk space appears, followed by this prompt:
Enter partition size in Mbytes or percent of disk space (%) to
create a Primary DOS partition. . . . . . . . . . . . . . . .[69]
6. Enter 20 as the partition size, then press Enter.
A message appears describing the partition just created.
7848 4078–004 4–13

Installing Windows NT on the Intel Node
4–14
7. Press Esc to return to the Fdisk options screen.
The following menu appears:
Choose one of the following:
1. Create DOS partition or Logical DOS Drive
2. Set active partition
3. Delete partition or Logical DOS Drive
4. Display partition information
Enter choice: [1]
Press Esc to exit FDISK
8. Type 2, then press Enter.
A message describing current partitions appears, followed by this prompt:
Enter the number of the partition you want to make
active. . . . . .:[ ]
9. Type 1, then press Enter.
10. Press Esc to return to the Fdisk options screen.
11. Press Esc to exit the FDISK program.
12. Press any key to reboot
13. When the MS-DOS prompt appears, type format c: /s then press Enter.
A:\format c: /s
You are prompted whether to proceed:
WARNING, ALL DATA ON NON-REMOVABLE DISK
DRIVE C: WILL BE LOST!
Proceed with Format (Y/N)?
14. Type Y then press Enter to proceed with the formatting.
You are prompted to enter a volume label:
Volume label (11 characters, ENTER for none)?
15. Type DOS_VOL, then press Enter.
16. Before rebooting, take the following steps:
a. Gather the Windows NT installation media.
b. Insert the Windows NT CD-ROM (labeled “Microsoft Windows NT Server”) in
the CD-ROM drive.
c. Install the first Windows NT setup diskette (labeled “Microsoft Windows NT
Server Setup Disk 1”) in the drive unit.
17. Reboot and proceed with the Windows NT installation procedures in 4.5.
7848 4078–004

Installing Windows NT on the Intel Node
4.5. Installing and Configuring Windows NT
(Not Preinstalled)
After creating a bootable MS-DOS partition, you can boot the Intel node and install the
Windows NT server operating system.
The installation process consists of a text phase in which prompts appear as text
messages and a graphical user interface (GUI) phase in which prompts are presented as
graphical screens. The following subsections describe the steps to take during each
phase.
Notes:
Switch the monitor concentrator to the Intel node position before beginning
(see 3.2).
Configuration settings are chosen to minimize problems during initial
installation. After hardware RFU, the site may wish to customize the
configuration to meet their needs.
4.5.1. Installing Windows NT
Begin Windows NT server installation as follows:
1. Insert the Windows NT CD-ROM (labeled “Microsoft Windows NT Server”) and the
diskette labeled “Microsoft Windows NT Server Setup Disk 1” into the drive units.
2. Reboot or turn power on the Intel node.
The following message appears at the top of the screen:
Windows NT Setup
================
After about 2 minutes, you are prompted to insert the next setup disk.
Windows NT Setup
================
Please insert the disk labeled
Windows NT Server Setup Disk #2
into Drive A:
*Press ENTER when ready
3. Insert the diskette labeled “Microsoft Windows NT Server Setup Disk 2” into the
drive unit, then press Enter.
After 1 minute, a message similar to the following appears briefly:
Microsoft(R) Windows NT(TM) Version 4.0 (Build xxxx).
1 System Process [xxx MB memory] multiprocessor kernel
7848 4078–004 4–15

Installing Windows NT on the Intel Node
4–16
Then, a Setup welcome menu appears as follows:
4. Press Enter to begin setting up Windows NT.
The following screen appears asking whether you want to skip mass storage
autodetection.
7848 4078–004

Installing Windows NT on the Intel Node
5. Enter S to skip autodetection and manually select the SCSI adapter
A screen appears to indicate that no adapter has been found or selected.
6. Enter S to manually specify the SCSI adapter.
A window for selecting an adapter appears.
7848 4078–004 4–17

Installing Windows NT on the Intel Node
4–18
7. Select adapters in that window as follows:
a. Press Enter to select the highlighted “Other” entry. You are prompted to insert a
diskette containing the RAID controller drivers diskette.
Windows NT Setup
================
Please insert the disk labeled
Manufacturer - supplied hardware support disk
into Drive A:
*Press ENTER when ready
b. Insert the diskette containing the RAID drivers (labeled “MegaRAID Drivers and
Utilities Diskette Windows NT 4.0x”) and press Enter to continue.
After a brief wait, the MEGARAID driver is listed in the adapter window.
c. Press Enter to to select the highlighted “MEGARAID NT SCSI Driver” entry.
A message indicates that Setup has recognized the MEGARAID adapter.
d. Enter S to specify an additional SCSI adapter.
The adapter window reappears.
e. Use the up arrow key to scroll up the list of adapters until you highlight the
following adapter:
Adaptec AHA-294X/AHA-394X/AIC-78XX SCSI Controller
f. Press Enter to to select the highlighted “Adaptec AHA-294X/AHA-394X/
AIC-78XX SCSI Controller” entry.
You are prompted to insert disk 3 as follows:
Windows NT Setup
================
Please insert the disk labeled
Windows NT Server Setup Disk #3
into Drive A:
*Press ENTER when ready
A message confirms that both adapters have been recognized.
7848 4078–004

Installing Windows NT on the Intel Node
8. Insert the diskette labeled “Microsoft Windows NT Server Setup Disk 3” into the
drive unit, then press Enter to continue.
The following message appears at the top of the screen:
Windows NT Server Setup
=======================
After a brief wait, a message appears asking you to insert the Windows NT operating
system CD-ROM.
Windows NT Setup
================
Please insert the compact disk labeled
Windows NT Server CD-ROM
into your CD-ROM Drive
*Press ENTER when ready
9. Insert the Windows NT CD-ROM in the drive unit, then press Enter to continue.
A license agreement text screen appears.
10. Read the contents of the license agreement as follows:
a. Read the contents of the first page, then press the Page Down key to read the
next page.
b. When you reach the last page, press F8 to indicate that you agree with the terms
of the license agreement.
The following message appears at the top of the screen:
Windows NT Server Setup
=======================
After 2 minutes, a hardware and software components list appears for you to verify.
11. Press Enter to continue.
A screen appears that identifies the MS-DOS partition created in 4.4 and the
remaining unpartitioned disk space.
7848 4078–004 4–19

Installing Windows NT on the Intel Node
4–20
12. Use the arrow key to highlight the Unpartitioned space, then press Enter.
A message asks you to select a file system for the partition.
Format the partition using the FAT file system
Format the partition using the NTFS file system
13. Use the up and down arrow keys to select the NT file system (NTFS), then press
Enter.
A message indicates that the disk is being formatted. After the disk is formatted, a
message appears asking for the directory in which to install Windows NT.
7848 4078–004

14. Press Enter to accept the default directory (WINNT).
Installing Windows NT on the Intel Node
A message asks whether you want an exhaustive examination of the hard drives.
15. Press Enter to perform an exhaustive examination of the hard disk.
The examination takes less than a second, then the following message appears:
Windows NT Setup
================
Please insert the disk labeled
MEGARAID NT RAID DRIVER
into Drive A:
*Press ENTER when ready
16. Insert the diskette containing the RAID drivers (labeled “MegaRAID Drivers and
Utilities Diskette Windows NT 4.0x”), then press Enter to continue.
Setup begins copying files. When done, a message asks you to remove the diskette
in preparation for rebooting.
17. Remove the diskette and the CD-ROM from the drive units, the press Enter.
Two reboots occur. First Windows NT boots using the file allocation table (FAT) file
system. Then the FAT file system is converted to the desired NTFS and Windows NT
reboots again.
Following reboot, the Windows NT Setup GUI screen appears. Continue by configuring
Windows NT as described in 4.5.2.
4.5.2. Configuring Windows NT
Note: This procedure follows immediately after, and is continuous with, the
installation procedure in 4.5.1.
After Windows NT reboots (see 4.5.1), a Windows NT Setup screen appears with a
message box saying to insert the Windows NT CD-ROM. Take the following steps:
1. Insert the Windows NT CD-ROM (labeled “Microsoft Windows NT Server”) into the
drive unit, then click OK.
A prompt indicates files are needed from the Windows NT server CD-ROM. A scroll
box identifies the directory from which they will be copied.
2. Click OK to proceed.
After a few seconds, a Windows NT Setup screen indicates that setup includes
Gathering information about your computer
Installing Windows NT networking
7848 4078–004 4–21

Installing Windows NT on the Intel Node
4–22
Finishing setup
3. Click Next to proceed to the next screen.
A Name and Organization screen appears.
4. Enter Name and Organization as follows:
a. Name field—Enter the user name the site wants identified with the Windows NT
environment.
b. Press the Tab key to advance to the Organization field.
c. Organization field—Enter the organization the site wants identified with the
Windows NT environment.
d. Click Next to proceed to the next screen.
A registration screen appears asking for the registration number from the
Certificate of Authentication.
5. Enter the registration number as recorded in Table 2–1, or directly from the
Certificate of Authentication, as follows:
a. Type the required digits in each field.
b. Click Next to proceed.
The Computer Name screen appears.
6. In the Name field, enter the host name from Table 2–1 by which the Windows NT
node will be identified on the external TCP/IP network. Click Next to proceed to the
next screen.
The Server Type screen appears.
7. Click Standalone Server, then click Next to proceed.
The Administrator Account screen appears.
8. Enter and confirm the password for the administrator’s account as follows:
a. In the Password field, type the password administrator.
b. Press the Tab key to go to the Confirm Password field. Type administrator in
that field.
c. Click Next to proceed.
Note: Following installation, the site must change the default password
(administrator) to a different password (see the caution in 4.6).
An Emergency Repair Disk screen appears.
7848 4078–004

Installing Windows NT on the Intel Node
9. Click Yes, create an emergency repair disk option to select it. Then click Next to
proceed.
Note: Later you will be prompted to insert a diskette for creation of the
emergency repair disk. Have a labeled diskette ready for that purpose.
The Select Components screen appears with the following defaults selected:
Accessibility options
Accessories
Communications
Multimedia
Note: You can also select Windows Messaging and Games if desired by the site.
10. Click Next to proceed.
The Windows NT Setup screen indicates that “Installing Windows NT Networking” is
about to begin.
11. Click Next to proceed to the next screen.
A screen appears with the option Computer will Participate in Network selected.
The following check boxes also appear:
Wired to the network
Remote access to the network
12. Click Wired to the network, then click Next.
A screen appears with a check box labeled “Install Microsoft Internet Information
Server” already checked.
13. Click Next.
A screen for selecting network adapters appears.
14. Select network adapters as follows:
a. Click Start Search.
The 3Com Fast EtherLink PCI 10/100BASE-T adapter is detected and added to
the list box.
b. Click Find Next.
The SysKonnect SK-NET EISA FDDI adapter is detected and added to the list
box.
7848 4078–004 4–23

Installing Windows NT on the Intel Node
4–24
c. Click Find Next again.
The following message appears:
No more adapters were found.
d. Click Next.
A Network Protocols screen appears. The only required protocol is the TCP/IP
protocol. The NWLink IPX/SPX compatible transport and NetBEUI Protocol are not
required for initial installation, but they may be selected if required by the site.
15. Ensure that the TCP/IP protocol is selected. If not, click TCP/IP protocol to select it,
then click Next.
A screen for selecting Network services appears. The following networking
components are listed in the list box by default:
Microsoft Internet Information Server 2.0
Remote procedure call (RPC) configuration
Network Basic Input/Output System (NETBIOS) Interface
Workstation
Server
In addition, the following network services also are required:
Simple TCP/IP service
Simple Network Management Protocol (SNMP) service
Windows Internet Name Service (WINS)
16. Add the additional services to the list as follows:
a. Click Select from list . . .
b. Scroll down the list of services (use the scroll bar) and highlight Simple TCP/IP
Service.
c. Click OK.
The service is added to the list of services already in the list box.
d. Repeat steps a, b, and c for SNMP Service and WINS.
e. Review the list of services to ensure that it contains the following:
− Microsoft Internet Information Server 2.0
− Remote procedure call (RPC) configuration
− Network Basic Input/Output System (NETBIOS) Interface
− Workstation
− Server
7848 4078–004

− Simple TCP/IP service
− SNMP service
− WINS
f. Click Next to proceed.
Installing Windows NT on the Intel Node
A Windows NT Server Setup screen indicates that “Windows NT is now ready to
install networking components.”
17. Click Next.
A screen for setting FDDI parameters appears:
18. Click Continue to accept the defaults.
Installation of networking components begins. A message box asks if you want to
use Dynamic Host Configuration Protocol (DHCP) server.
19. Click No.
Messages indicate software is being installed. After about 1 minute, you are
prompted with a tabbed SNMP Properties screen.
20. Set the SNMP properties as follows:
a. Agent tab—Click this tab, then enter the name, room number, and phone
number of the system administrator. Accept the service defaults (Applications,
Internet, and End–to–End).
b. Security tab—Click this tab, then click on the Send Authentication trap check
box to remove the check mark. Leave the Accept SNMP Packets from Any Host
option set.
c. Click OK.
After about 1 minute, a tabbed Microsoft TCP/IP Properties screen appears.
21. Set the TCP/IP properties for the internal FDDI network adapter card as follows:
a. Use the scroll bar to select the following adapter from the drop-down list of
adapters
SK-NET EISA FDDI Adapter
b. Click the IP Address tab, then enter IP address information as follows:
− Click Specify an IP address: (a dot appears in the circle to indicate it is
selected).
− In the IP Address field type 192.168.057.003 (this is the Intel node FDDI
address as described in Appendix A), then press Tab.
− A default address of 255.255.255.0 is automatically calculated for the Subnet
Mask field. Do not change that address.
7848 4078–004 4–25

Installing Windows NT on the Intel Node
4–26
22. Set the TCP/IP properties for the external TCP/IP network adapter card as follows:
a. Use the scroll bar to select the following adapter from the drop-down list of
adapters
3Com Fast EtherLink PCI 10/100BASE-T Adapter
b. Click the IP Address tab, then enter the following IP address information:
− Click Specify an IP address.
− In the IP Address field enter the IP address for the Windows NT node from
Table 2–1, then press Tab.
− Change the subnet mask to the mask address from Table 2–1, or skip this
field (accept the default).
− If you have a gateway (router), click Advanced (otherwise skip this step)
and take the following steps:
− Click Add.
− In the New Gateway field, type the gateway address from Table 2–1.
− Click Add.
The address appears in the Installed gateways: list box.
− Repeat these steps for each additional gateway required, then click OK
when done.
c. If the site chooses to implement WINS, click the WINS Address tab (otherwise
skip this step), then enter the following WINS information:
− In the Primary WINS Server field, type the address from Table 2–1, then
press Tab.
− If applicable, type the IP address of the Secondary WINS Server from
Table 2–1.
d. If the site has a domain name server (DNS), click the DNS tab(otherwise skip
this step), and take the following steps:
− Enter the IP address for the first DNS from Table 2–1.
− Click Add.
The DNS address is added to the search order list box.
− Repeat these steps for each additional DNS server.
23. Click OK.
The following message appears:
At least one adapter cards has an empty WINS address.
Do you want to continue?
24. Click YES.
7848 4078–004

Installing Windows NT on the Intel Node
A screen appears that allows you to confirm the network bindings.
25. Click Next to proceed.
A screen appears indicating that Windows NT is ready to start the network.
26. Click Next to proceed.
A setup screen identifies the host name of the Windows NT node and asks whether
the node is to participate in a workgroup or domain.
27. Click Workgroup, enter a workgroup name of CLEARPATH, then click Next to
proceed.
The Windows NT Setup screen indicates it is ready to Finish Setup.
28. Click Finish.
A message indicates that Setup is configuring Windows NT. Then a Microsoft
Internet Information Server 2.0 Setup screen appears.
29. Set the Internet Information Server (IIS) properties as follows:
a. Click OK to accept the defaults.
A prompt asks if you want to create an inetsrv directory.
b. Click Yes to create the directory.
A list of publishing directories appears.
c. Click OK to accept the default Publishing Directories.
A prompt says directories do not exist.
d. Click Yes to create the directories.
Directories are created and a prompt appears to install drivers.
e. Click SQL Server, then click OK to install the ODBC driver.
Files are copied, then a tabbed Date/Time Properties screen appears.
30. Click the Time zone tab and, if necessary, take the following steps for each field:
a. Time zone—To change the time zone, click on the scroll bar arrow and scroll up
or down to select the correct time zone. The map shifts over the time zone
selected.
b. Daylight saving time—Click the check box to select daylight saving time if it
applies to the time zone.
7848 4078–004 4–27

Installing Windows NT on the Intel Node
4–28
31. Click the Date and Time tab and, if necessary, take the following steps for each field:
a. Month field—Click the scroll bar arrow and scroll up or down to select the
correct month.
b. Year field—Click the scroll bar arrow and scroll up or down to select the correct
year.
c. Day of the month—Click the correct date to set it on the calendar.
d. Time—Click the scroll bar arrow and scroll up or down until the correct time
appears.
e. Click Close when done with both the date and time. The clock automatically
adjusts for daylight saving time if selected.
A message box appears that indicates the type of video adapter.
32. Click OK to continue.
A screen appears for configuring the video display.
33. Configure the video display as follows:
a. Click Test to ensure that the default settings work.
A message box indicates that a test will be performed with the video mode
selected (default VGA mode with 16 colors).
b. Click OK to proceed.
A color test pattern briefly appears followed by a message box asking if you saw
the test pattern properly.
c. Click Yes to proceed.
A message box says to click OK to save the settings.
d. Click OK to save the display properties settings.
You are returned to the display properties screen.
e. Click OK to proceed.
Files are copied from the CD-ROM. Messages appear to indicate progress. After
about 2 minutes, a message indicates you should label a floppy disk as the
“Emergency Repair Disk” and insert the diskette into the drive unit.
34. Insert the diskette into the drive unit and click OK.
The emergency diskette is created (takes about 2 minutes). When done, a screen
with the following message appears:
“Windows NT 4.00 has been installed successfully.
Remove disks from floppy drives and choose Restart Computer.”
7848 4078–004

Installing Windows NT on the Intel Node
35. Remove the diskette and the CD-ROM from the drive units, then click Restart
Computer.
Ignore messages for selecting the Windows NT mode and allow Windows NT to start
automatically. The Windows NT Server logo appears and a message box prompts
you to press Ctrl-Alt-Del to log on.
36. Press Ctrl-Alt-Del.
A logon dialog box appears.
37. Log on as described in 4.6.
The Windows NT desktop appears with a Welcome to Windows NT screen.
Following logon, you can complete installation as described in the rest of this section.
7848 4078–004 4–29

Installing Windows NT on the Intel Node
4.6. Logging On as the Administrator
4–30
Caution
To prevent unauthorized access to the Windows NT node following initial
installation, the site must change the default password (administrator) to a different
password.
Whenever you restart or power on the Windows NT node during installation, the
Windows NT Server logo appears and you are prompted to press Ctrl-Alt-Del to log on.
Take the following steps to log on:
Notes:
The logon information is case sensitive.
If the Windows NT node is part of a domain, a domain name also must be entered.
1. Press Ctrl-Alt-Del.
A logon screen appears.
2. Enter the following information on that screen:
a. User name—Enter administrator.
b. Press the Tab key to advance to the password field.
c. Password—Enter administrator (the installation password)
d. Press the Tab key to advance to the workgroup field.
e. Workgroup—Enter CLEARPATH.
f. Click OK.
The Welcome to Windows NT screen on the Windows NT desktop.
Following logon, you can complete Windows NT installation as follows:
Install Windows NT service pack (4.8)
Complete RAID configuration (4.9)
Create an emergency repair disk (4.14)
Install IOE software products (4.11)
Configure the tape drive unit (4.12)
Note: To enable monitoring of Windows NT by SPO/HMP Console software you must
change the default configuration of the FTP server service to copy Windows
NT agents (7.4.2). After they have been copied, the FTP server service can be
reset to the defaults or modified per the requirements of the site.
7848 4078–004

4.7. Configuring the Hosts File
Installing Windows NT on the Intel Node
Following installation of Windows NT, you must set up a hosts file so that the Windows
NT node can communicate using the external TCP/IP network. Take the following steps
to set up a hosts file:
1. If you are not currently logged on, power on or restart the Windows NT node and log
on as the Administrator (4.6).
2. Click Start.
A popup window appears.
3. Select Programs, the Accessories program group, then Notepad.
The Notepad editor starts.
4. From the menu bar of Notepad, click File, then select Open.
5. In the File Name box, type:
D:\Winnt\system32\drivers\etc\hosts
6. Click Open.
7. Use the arrow keys, or click the mouse, to position the cursor at the line following
this line:
127.0.0.0 localhost
8. Type in the following 4 lines:
Note: Type hostnames with no spaces. For example, type fddiuxsr not fddi uxsr.
192.168.57.4 fddiuxsr
192.168.57.5 fddi22sr
192.168.57.6 fddi22am
192.168.57.7 fddi22mr
9. From the menu bar of Notepad, click File, then Save.
10. From the menu bar of Notepad, click File, then Exit.
7848 4078–004 4–31

Installing Windows NT on the Intel Node
4.8. Installing the Windows NT Service Pack
4–32
Perform the following steps to install the Windows NT service pack:
1. Insert the service pack CD–ROM (labeled “Windows NT 4.0 Service Pack 1”) in the
CD–ROM reader.
2. Click Start.
A popup window appears.
3. Select RUN.
A Run dialog box appears.
4. Click Browse.
A Browse dialog box appears.
5. Change the drive to the CD–ROM drive (D:).
6. Change the directory to the i386 directory.
7. Select UPDATE.EXE, then click OK.
You are returned to the Run dialog box.
8. Click OK.
A setup messages indicate the version of security you have.
9. Click Cancel.
A setup message asks if you are going to update Windows NT.
10. Click OK.
The service pack software is installed from CD-ROM. When done, a prompt appears
asking you to restart the computer.
When done, remove the CD-ROM and continue by installing the RAID controller
software as described in 4.9.
7848 4078–004

Installing Windows NT on the Intel Node
4.9. Installing and Configuring RAID Software
After installing and configuring Windows NT and the service pack, install and configure
RAID controller software as follows:
1. If you are not currently logged on, power on or restart the Windows NT node and log
on as the Administrator (4.6).
2. Insert the diskette containing the RAID drivers (labeled “MEGARAID Drivers and
Utilities Diskette Windows NT 4.0x”).
3. Click Start.
A popup window appears.
4. Select RUN.
A Run dialog box appears.
5. Type A:setup and click OK.
A Welcome screen appears.
6. Click Next.
A FLEXRAID Install Destination Path screen appears.
7. Click Next.
A Confirm New Directory screen appears.
8. Click Yes, then Current to continue. The following message appears when software
installation is done:
MegaRAID Power Console has been successfully installed.
You can now run the FlexRAID utility software when desired.
4.10. Installing and Configuring Video Drivers
To enable console monitor resolution higher than VGA, you must install video drivers on
the Windows NT node as follows:
1. If you are not currently logged on, power on or restart the Windows NT node and log
on as the Administrator (4.6).
2. Insert the diskette containing the video drivers (labeled “NT 4.0 Supplementary
Driver Disk” part number 3815036-000) into the drive unit of the Windows NT node.
3. Right click on the desktop, then click on Properties in the popup menu that appears.
A tabbed Display Properties screen appears.
7848 4078–004 4–33

Installing Windows NT on the Intel Node
4–34
4. Click the Settings tab to bring it to the front, then click Display Type.
A Display Type screen appears. The Adapter Type field shows the current adapter
type (most likely “VGA compatible display adapter”).
5. Click Change for the Adapter Type field.
A Select Device screen appears with a list of currently available adapter models.
6. Click Have Disk.
An Install From Disk screen appears that instructs you to insert the manufacturers
disk in the drive unit. The A: prompt should appear in the scroll box by default.
7. In the scroll box type the following path, then click OK to copy files from the
diskette:
a:S3Inc
The list of adapters in the list box is updated with those from the diskette.
8. Click the following adapter to highlight it:
S3 Incorporated Trio32/Trio64/Trio64V+”
9. Click OK, then Yes to proceed with the third–party driver installation
The following message appears:
Drivers were successfully installed
10. Click OK, then Close on each open screen to close it.
When the last screen is closed, the following message appears:
Reboot the server?
Yes No
11. Remove the diskette from the drive unit, then click Yes to reboot the server
12. After the server reboots, log in again as administrator (4.6).
The following message appears:
Invalid display settings.
13. Click OK.
14. Right click on the desktop, then click on Properties in the popup menu that appears.
A tabbed Display Properties screen appears.
7848 4078–004

Installing Windows NT on the Intel Node
15. Click the Settings tab to bring it to the front, then select the desired video resolution,
color depth, and refresh rate.
16. Click Test.
A test screen appears.
17. If the test screen appears to be correct, click Yes to confirm the setting is OK.
18. Click Apply to apply the new settings. You may have to reboot the server depending
on the settings you have chosen; otherwise, click OK on the Display Properties
screen.
4.11. Installing IOE Software Products
After the Windows NT operating system is installed (or if already preinstalled), you must
install Open/OLTP Pathway according to instructions in the Open/OLTP Pathway
Installation and Operations Guide.
4.12. Configuring the Tape Drive Unit
If the Windows NT node has a tape drive unit, configure it as follows:
1. If you are not currently logged on, power on or restart the Windows NT node and log
on as the administrator (4.6).
2. Insert the Windows NT CD-ROM (labeled “Microsoft Windows NT Server”) in the
CD-ROM drive.
3. Click Start, Settings, then Control Panel.
A Control Panel window opens.
4. Double click Tape Devices.
A Tape Drives window opens.
5. Click OK to install the driver now.
6. Click OK.
7. Click Start, then select Programs, Administrative Tools, Backup.
An Operations menu appears.
8. Select Hardware Setup...
A list appears. Verify that the following entry, followed by a version number (for
example, 330B) is in that list
SCSI 0, Bus 0, Id 3, Lun 0 SONY SDT–5000
7848 4078–004 4–35

Installing Windows NT on the Intel Node
4–36
9. Click OK.
An operations menu appears.
10. Select Exit.
4.13. Setting Balanced Server Priorities
To set up the Windows NT node for balanced file and application server priorities take
the following steps:
1. If you are not currently logged on, power on or restart the Windows NT node and log
on as the administrator (4.6).
2. Click Start, Settings, then Control Panel.
A Control Panel window opens.
3. Double click the Network icon.
A Network window opens.
4. Click the Services tab, and in the window that opens set the properties as follows:
a. Click the Server line to select it.
b. Click Properties.
c. Click the Balance option to select it.
d. Click OK to apply the selection and close the window.
5. In the Network window, click Close to apply the changes and close the window.
6. Click YES to reboot the server.
7848 4078–004

Installing Windows NT on the Intel Node
4.14. Creating or Updating an Emergency Repair
Disk
To ensure that you have a final copy of your Windows NT configuration, you should
create an emergency repair disk or update a previously created disk (4.5) as follows:
1. If you are not currently logged on, power on or restart the Windows NT node and log
on as the Administrator (4.6).
2. Click Start. A popup window appears.
3. Select RUN. A Run dialog box appears.
4. Type in \winnt\system32\rdisk.exe and click OK. The Repair Disk Utility window
appears.
5. Click Update Repair Info. A window appears warning you that the previously saved
repair information will be deleted.
6. Click Yes. A window appears asking if you want to create an Emergency Repair
Disk.
7. Click Yes. A window appears instructing you to insert a diskette into the drive unit.
8. Place a diskette in the drive unit and click OK. The Repair Disk Utility window
appears.
9. Click Exit.
7848 4078–004 4–37

Section 5
Installing UNIX on the Intel Node
The UNIX integrated operating environment (IOE) includes the UNIX operating system
and several application packages that run under UNIX. To prepare for installation you
must gather information and media needed during the installation (see Section 2). You
also must determine if the UNIX operating system is preinstalled as follows:
1. Ensure that the front panel system key is in the unlocked (running) position and not
the maintenance position.
2. Reboot the system (for example, press the soft boot switch on the front panel) or
power on the system if it is off. If the following console login prompt appears, the
UNIX operating system is installed:
Console Login:
Otherwise, the system displays the following error message:
Missing operating system
Cannot boot UNIX.
If UNIX is preinstalled, you need to perform the steps described in 5.2.
If UNIX is not preinstalled, you must take the following steps:
1. Configure the RAID controller (5.3).
2. Install the UNIX operating system (5.4). If you install the operating system, you
must partition the boot disk as described in Table 5–1.
3. Copy UNIX IOE products to the spooling directory (5.5).
4. Log on as the superuser (5.6).
5. Install and run the tuning script from the tuning scripts diskette (5.7).
Related procedures for installing the UNIX resource monitor (URM) agent files that
enable communication with SPO/HMP console are described in Section 7. Procedures
for installing optional application packages are described in Section 10.
The default (and minimum) hard disk configuration of the UNIX node is two
disks—disk 0 (the boot disk) and disk 1. Those disks are partitioned as follows:
Disk 0 must be partitioned as described in Table 5–1 (it is partitioned that way when
UNIX is preinstalled).
Disk 1 is partitioned automatically (Table 5–2) by the tuning script when it is run
(5.2 or 5.7).
7848 4078–004 5–1

Installing UNIX on the Intel Node
5–2
Notes:
The values for the boot disk (disk 0) slices 5 through 9 are arbitrary defaults that
can be modified without impacting the installation process. For example, you
could select other partition or block sizes.
Table 5–1 is for a 4-GB drive while installing the UNIX System V Release 4.0
run-time version.
Slice Size Type
Table 5–1. Boot Disk (Disk 0) Required Configuration Values
Block
Size
Mount
Point
Comments
1 950 MB vxfs 4 KB / Should provide a large enough root directory
to support ClearPath optional packages.
2 32 MB bfs ––– /stand File system type bfs is selected
automatically by the system.
3 520 MB ––– ––– Not
prompted
(/dev/swap
by default)
4 400 MB vxfs 4 KB /opt
5 800 MB vxfs 4 KB /home
6 800 MB vxfs 4 KB /home1
7 800 MB vxfs 4 KB /home2
8 800 MB vxfs 4 KB /home3
9 Remaining
disk
space
vxfs 4 KB /home4 Remaining space.
Primary swap area twice the size of base
memory (256MB). Although the /swap
device needs to be twice the size of
memory, it can span multiple file systems.
If your system is larger than 256MB you
need to configure a secondary swap area on
another file system to expand the swap
space.
The tuning script determines if there is
adequate swap space. If not, it calculates
how much additional swap to configure
(see 5.3.2).
7848 4078–004

Table 5–2. Disk 1 Configuration
Slice Mount Point Description
1 /dev/rdsk/1s1 Dump disk partition for taking crash dumps
2 /dev/rdsk/c0.0d4s2 Transaction log (TLOG) partition
Installing UNIX on the Intel Node
3 /dev/rdsk/c0.0d4s3 X Open Application Program Interface log file (XAPLOG) partition
4 Remaining disk space for user directories and files
5.1. Scope of the Procedures
The procedures in this section replace the procedures described in the UNIX Software
Installation Guide. These procedures create a basic default ClearPath UNIX IOE
configuration that supports a wide variety of user environments.
You must use the detailed procedures in the UNIX Software Installation Guide instead
of procedures in this section if you are
Configuring reliability, availability, and serviceability (RAS) features such as disk
mirroring, striping, or media archiving—RAS features are provided by Unisys
Volume Manager, which is installed later by the client when customizing the
installation
Reinstalling UNIX to produce a disk configuration different from the required
configuration described in Table 5–1
Note: In the procedures given in this section, sample responses to prompting
messages are shown in bold on the same line as the sample prompt. The step
following the sample response or prompting message describes what to enter.
See “About This Guide” for more information about notation conventions.
5.2. Steps to Take if Software is Preinstalled
If the UNIX operating system and SPO/HMP Console software are preinstalled, you must
take the following steps:
1. Log on as the superuser (5.6).
2. Install and run the tuning script as described in this subsection.
Note: Perform this procedure only if the UNIX operating system has been installed
at the factory (you have not installed the operating system). If you installed
the UNIX operating system, install and run the tuning script using the
procedure in 5.7.
7848 4078–004 5–3

Installing UNIX on the Intel Node
5–4
The tuning scripts diskette contains a script that you must run to complete installation
and configuration of the UNIX operating system IOE. Take the following steps to install
and run that tuning script:
1. If you are not already logged on, log on as root (superuser) (see 5.6).
2. Insert the tuning scripts diskette into the disk drive and enter the following
command to install and execute the tuning script (cptune):
# pkgadd -d diskette1 cptune
Messages appear prompting you to enter commands to change directories and start
the tuning script:
ClearPath tuning and configuration script
Version 1.0 TAKE 3 (UN6000/U)
Copyright (c) 1996 Unisys, Inc. All Rights Reserved.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
Installing ClearPath Tuning and configuration script as
## Installing part 1 of 1.
[ verifying class ]
## Executing postinstall script.
Please enter the following commands to comlete the Clearpath tuning:
cd /var/sadm/pkg/cptune/install
sh CP_tune
Installation of was successful.
3. Enter the cd and sh commands as indicated in the message:
# cd /var/sadm/pkg/cptune/install
# sh CP_tune
Note: Your responses are not echoed on the screen so you do not see them.
You are asked whether the operating system was installed by you or by the factory.
If you installed the UNIX OS, you have already
configured it. If the OS was installed at the
factory, you need to customize it for your site.
Did you install the UNIX OS? [Y/n]: y
4. Enter no (N) to indicate that you did not install the UNIX operating system (that it
was preinstalled by the factory).
The tuning script prompts you to select the time zone for your site.
7848 4078–004

Timezone Selection
––––––––––––––––––
Installing UNIX on the Intel Node
1) Greenwich Meantime (GMT) 9) Alaskan, USA (AST)
2) Atlantic, Canada (AST) 10) Hawaiian, USA (HST)
3) Eastern, USA (EST) 11) Eastern European (EST)
4) Central, USA (CST) 12) Middle European (MET)
5) Mountain, USA (MST) 13) Western European (WET)
6) Pacific, USA (PST) 14) Indian (IST)
7) Yukon, Canada (YST) 15) New Zealand (NZST)
8) Bering, USA (BST) 16) Japanese (JST)
Please select by option number: [1]:
5. Select the appropriate time zone. If your time zone is not listed, pick a zone and
correct the time in the next step. A prompt asks whether daylight saving time is
applicable to your time zone selection.
Is daylight saving time observed in your locale? [Y/n]:
6. The default is yes (Y). Enter no (N) if you do not want to have daylight saving time
support. You are prompted to confirm that the current date and time are correct.
Setting System Date and Time
––––––––––––––––––––––––––––
Current date is Tue Mar 5 18:23:25 MST 1996.
Is this correct? [Y/n]:
7. The default entry is yes (Y). If you answer no (N), enter a new date and time.
After entry of a correct date and time, you are prompted to set and confirm a default
password that will be used by several users.
Setting Default System Passwords
––––––––––––––––––––––––––––––––
The password you are about to enter will be used for the following users:
– root (superuser)
– install
– bin
– dtadm
– mlsadmin
– sysadm
– makefsys
– checkfsys
– mountfsys
– unmountfsys
– setup
– powerdown
IMPORTANT: After installation you should assign unique passwords to these
users. Use the System Administration (OAM) menus or the passwd(1) command.
New Password:
7848 4078–004 5–5

Installing UNIX on the Intel Node
5–6
8. Enter unisys1234 (the default installation password). The password does not
appear on the screen as you type it. The site later changes the password during site
customization (the new password must be at least eight characters in length and
include at least two alphabetic characters and one numeric or special character).
You are asked to reenter the password to confirm it.
After entry of the password, you are asked whether you want to configure
networking.
Do you want to configure networking?
9. Enter yes (Y). You are prompted to enter a site-defined system name and to confirm
the selection.
Setting System and Node Names
–––––––––––––––––––––––––––––
Please enter a System Name for this system. This will set
the ”node” name and the ”system” name. This name will be
used for uucp(1) and networking. This name cannot be ”unix”,
an empty string (””) or more than 8 characters in length.
Please enter the System Name: xxxxxx
The System Name chosen was ”xxxxxx”
Is this correct? [Y/n]: y
10. Enter a site-defined system name for the UNIX node. You are prompted to enter the
internet protocol (IP) address that identifies the UNIX node to your external
Ethernet production LAN.
Internet Protocol (IP) Address Selection
––––––––––––––––––––––––––––––––––––––––
Please enter your local system IP Address. The IP Address is the
address by which your system will be known on the Internet.
These addresses must be administered by a central authority on
your network. IP Addresses are written as four decimal integers,
separated by decimal points and no spaces (e.g. 128.10.2.70).
Your system IP Address is? : xxx.xxx.xxx.xxx
Your system IP Address has been set to xxx.xxx.xxx.xxx
Is this correct? [Y/n]: y
7848 4078–004

Installing UNIX on the Intel Node
11. Enter the IP address of the UNIX node and confirm the entry. You are asked to
confirm or change your Netmask value.
Internet Protocol Netmask Selection
–––––––––––––––––––––––––––––––––––
Your local system Netmask is set to : xxx.xxx.xxx.xxx
You can either use this value, calculated from your system
IP Address, or you can enter a new value if you use
subnet addressing and wish to overide it.
Please select a new Netmask value or press enter to use the
calculated default: [ xxx.xxx.xxx.xxx ] xxx.xxx.xxx.xxx
Your local system Netmask has been set to xxx.xxx.xxx.xxx
Is this correct? [Y/n]:
12. Enter yes (Y) to confirm that the Netmask value is correct, and continue with
network setup. You now asked whether you want to identify a default gateway
service.
Default Gateway System Selection
––––––––––––––––––––––––––––––––
You can select a system to provide a Gateway service between
your local subnet and any backbone networks on your site.
This is sometimes the Internet Address of another computer acting
as a Gateway, or more often the Internet Address of a dedicated
standalone Router system.
Do you wish to provide an IP Address for a Gateway? [y/N]:
13. The default is no (N). If you enter yes (Y) you are prompted to enter and then
confirm the IP address for the gateway.
You then are prompted to enter a network domain name and confirm your choice.
Network Domain Name Selection
–––––––––––––––––––––––––––––
Please enter a Network Domain Name for this system. This will
be used by the Domain Name Services as a name suffix for
system names that do not include a period (.) character
in them.
This name will also be used to identify the local network
in the /etc/networks database file.
The name slc.unisys.com would be a suitable example of a valid
Domain Name.
Please enter the Domain Name: xxx.xxx.xxx.xxx
The Domain Name chosen was xxx.xxx.xxx.xxx
Is this correct? [Y/n]:
7848 4078–004 5–7

Installing UNIX on the Intel Node
5–8
14. Enter the network domain name and confirm your choice. You then must decide
whether you want to identify a Domain Name Services (DNS) host.
Directory Name Services (DNS) Host Selection
––––––––––––––––––––––––––––––––––––––––––––
You can elect to use Directory Name Services (DNS) host or a
statically configured /etc/hosts file for resolving
system names to Internet Addresses. If you choose to use a DNS
host, then you will be prompted for the Internet Address of the
DNS server systems on your network. The DNS host chosen here is
the Primary DNS host. Further hosts can be configured in the
/etc/resolv.conf file after installation.
Do you wish to use a DNS host? [y/N]:
15. The default is no (N). If you answer yes (Y), you are prompted to enter more
information (not shown).
Following that entry, the values you have selected are stored in the system and a
series of messages indicate that kernel parameters are being set, products are being
installed, network parameters are being set, and partitions are being set up on disk.
The messages end with a prompt asking whether you want to add the SNMP agent
package.
Tuning SEMMNI 500
Tuning SEMMNS 800
Tuning SEMMNU 400
Tuning SEMMSL 400
Tuning SHMMNI 256
Tuning MSGMNI 128
Tuning SHMMAX 150000000
Tuning NPROC 1000
Tuning MAXUP 1000
Tuning SDATLIM 0x7FFFFFFF
Tuning HDATLIM 0x7FFFFFFF
Tuning SVMMLIM 0x7FFFFFFF
Tuning HVMMLIM 0x7FFFFFFF
Tuning SFSZLIM 0x7FFFFFFF
Tuning HFSZLIM 0x7FFFFFF
Tuning SFNOLIM 512
Tuning HFNOLIM 2000
Tuning NUMTIM 512
Tuning NUMTRW 512
Tuning UFSNINODE 2000
Tuning NINODE 1000
Tuning NREGION 350
Tuning NCALL 400
Tuning SSTKLIM 0x7FFFFFFF
Tuning HSTKLIM 0x7FFFFFFF
Tuning STRTHRESH 0
pkgadd –r /var/sadm/pkg/cptune/install/skfe skfe
Processing package instance from
UNISYS SysKonnect FDDI UNIX Driver
Version 3.1 (UN6000/U)
7848 4078–004

Copyright (C) Schneider & Koch & Co. 1989–1993
Copyright (C) SysKonnect 1993
All Rights Reserved.
## Processing package information.
## Processing system information.
## Verifying package dependencies.
## Verifying disk space requirements.
Installing UNISYS SysKonnect FDDI UNIX Driver as
## Installing part 1 of 1.
[ verifying class ]
## Executing postinstall script.
Installing UNIX on the Intel Node
The system configuration has been changed since the last US6000–ETD
device driver configuration was entered. The installation script
will be executed again.
Press any key to continue...
16. If this message appears, press Enter to continue with the tuning script. More
messages appear.
Welcome to the SK–FDDI device driver installation program for UNIX System
V
Release 4. This program assumes you have executed the SCU for each
SK–FDDI adapter you plan to use. This device driver can only be
configured
for adapters which have been configured with the SCU. This program also
assumes that this device driver is not currently installed.
If you have not run the SCU, please exit this program and execute it now.
If the skfe device driver is installed, please remove it before installing
this device driver. Use the command ’pkgrm skfe’.
If the skfe device driver is currently installed, please exit this
program and and remove it now.
Do you want to install the SK–FDDI device driver? [y,n]
Note: The message “Do you want to install the SK-FDDI device driver? [y,n]:”
(as in this example) indicates that the tuning script has detected that the
IRQ/DMA setup for the FDDI card is different from what it expects. If that
message appears, enter yes (Y) to continue. Your response is not echoed
on the screen, and the tuning script continues processing.
Searching for SK FDDI Controllers...
SK–FDDI Driver Configuration
============================
Adapter 1 type: SK–FDDI
IRQ: nn
DMA: n
SCU information read successfully.
Do you want to install with this configuration? [y,n]
7848 4078–004 5–9

Installing UNIX on the Intel Node
5–10
Note: The message “ Do you want to install with this configuration? [y,n]:”
(as in this example) indicates that the tuning script has detected that the
IRQ/DMA setup for the FDDI card is different from what it expects. If that
message appears, enter yes (Y) to continue. Your response is not echoed
on the screen, and the tuning script continues processing. In about 15
seconds more messages appear.
Loading skfe ... done.
***************************************************************
Installation of SysKonnect SK–5341 FDDI Driver passed.
Please refer to the Release Notice on how to set up the strcf
file to run TCP/IP on FDDI
***************************************************************
Installation of was successful.
pkgadd vxfs
Processing package instance from
VERITAS File System
Version 1.2.3 Advanced MP Take–3 (UN6000/U)
Copyright (c) 1991, 1992 VERITAS SOFTWARE CORP. ALL RIGHTS RESERVED.
THIS
SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS
SOFTWARE, AND/OR ITS SUPPLIERS.
pkgadd pathway
Copyright (c) 1996 UNISYS, Inc. All rights reserved.
## Processing package information.
## Processing system information.
37 package pathnames are already properly installed.
## Verifying disk space requirements.
Installing VERITAS File System as
## Executing preinstall script.
## Checking for acceptable OS version.
Saving the vxfs lite files
## Installing part 1 of 1.
[ verifying class ]
## Executing postinstall script.
Installing VERITAS File System vxfs module ...
The UNIX Operating System will now be rebuilt.
This will take some time. Please wait.
Root for this system build is /
The UNIX Kernel has been rebuilt.
Removing temporary packaging files ...
Installation of was successful.
*** IMPORTANT NOTICE ***
If installation of all desired packages is complete,
the machine should be rebooted in order to
ensure sane operation. Execute the shutdown
command with the appropriate options and wait for
the “Console Login:” prompt.
pkgadd pw3–1–0
7848 4078–004

Installing UNIX on the Intel Node
Processing package instance from
Pathway
Version 3.1.0SVR4 (UN6000/U)
Using as the package base directory.
Copyright (c) 1987–1990 AT&T
Copyright (c) 1991–1994 UNIX System Laboratories, Inc.
(a wholly–owned subsidiary of Novell, Inc.)
Copyright (c) 1989–1994 Unisys Corporation
All Rights Reserved
## Processing package information.
## Processing system information.
## 3 package pathnames are already properly installed.
## Verifying disk space requirements.
Installing Pathway as
## Installing part 1 of 1.
[ verifying class ]
Installation of was successful.
Would you like to add the SNMP agent package? [Y/n]: y
pkgadd agent
17. Enter yes (Y) or no (N) to indicate whether you want to install the SNMP agent
package. The SNMP agent needs to be installed only if the site wishes to control the
ClearPath IX server using an SNMP manager such as HP OpenView.
More messages appear (such as “Installation of was successful”) followed
by a prompt asking whether to install the GDM developer’s kit.
Would you like to add the GDM Development package? [Y/n]:
18. Enter yes (Y) or no (N) to indicate whether you want to install the GDM
development package. The GDM developer’s kit needs to be installed only if the site
will be developing X Window applications. If you answer yes (Y), you should see the
following message:
Installation of was successful.
More messages appear, followed by a prompt asking if a RAID controller is installed.
Adding ClearPath defaults to /etc/hosts
Adding ”fddi22am” to /etc/hosts.equiv
Changing the host name of the FDDI interface to fddiuxsr in
/etc/inet/rc.inet
Configuring dump disk and checking swap partitions ....
Setting up partitions on disk 1 ....
Is a raid controller installed? (Y/n)
19. Enter yes (Y) unless you are reinstalling software at a ClearPath release 1.0 site that
does not have a RAID controller—then you should enter no (N).
7848 4078–004 5–11

Installing UNIX on the Intel Node
5–12
More messages appear.
scsiformat –u /dev/rdsk/c0.0d1 desc.drv1_raid
/dev/rdsk/1s1 not mountable and not in use by kdm
– OK to use for dump disk.
Making dump disk on /dev/rdsk/1s1.
/dev/rdsk/1s1 will be configured as a dump disk partition.
This partition will be exclusively used for taking crash dumps.
Any existing data in this partition will be lost.
Do you wish to continue?
Yes or No [y,n,?,q] Thank you.
Configuring /dev/rdsk/1s1 as a dump disk.
Modifying sassign file.
done.
Creating device node for the dump disk.
done.
/dev/rdsk/1s1 configured as the dump disk partition.
The running kernel has been modified for this.
Rebuilding unix kernel to make this change permanent.
done.
The UNIX Operating System will now be rebuilt.
This will take some time. Please wait.
The UNIX Kernel has been rebuilt.
Checking Swap configuration
Setting up NFS ....
Creating mount directory ”/rmnt”
Changing ”initdefault” value from 2 to 3 in /etc/inittab
Changing ”initdefault” value . . . in /etc/conf/ef.d/init.base
Changing the value of VX_NINODE from 500 to 2000 in
/etc/conf/pack.d/vxfs/space.c
The UNIX Operating System will now be rebuilt.
This will take some time. Please wait.
Root for this system build is /
The UNIX Kernel has been rebuilt.
****************************************************
The system must be rebooted to load the new kernel.
****************************************************
Finished running the ClearPath tuning script.
Press return to shutdown and reboot.
20. Press Enter to reboot the system. Reboot takes about 7 minutes.
After the reboot, proceed to Section 6 to install SPO server and LT501 X terminal
software.
See Section 10 for a description of how to install optional application software packages
on the UNIX node.
7848 4078–004

5.3. Configuring the RAID Controller
Installing UNIX on the Intel Node
The basic steps for installing and configuring a new RAID disk array controller (DAC)
are:
1. Install the drive units:
Install Port 0 drives in slots 1, 2, and 3
Install Port 1 drives in slots 1 and 2.
2. Load the system configuration utility (SCU) from diskette as follows:
a. Insert the SCU diskette in drive A: and power on or reboot.
b. From the SCU main menu select View, Edit, then disable the boot controller (see
the System Configuration Utility User’s Guide for instructions).
c. Save the configuration and Exit SCU.
d. Reboot.
3. Start the DACCF utility as follows:
a. Insert the diskette labeled “DAC960P Configuration and Utilities” in the drive
unit.
b. Change directories by typing CD DACCFG, then press Enter.
A:\cd daccfg
c. Start the DACCF utility by typing DACCF, then press Enter.
Note: If more than one DAC is installed, a list is displayed so you can select the
DAC to be configured.
On a new system, an “Installation aborted” message lists the drives detected as
follows:
Installation Aborted
Channel # Target ID Original State Current State
0 0 DEAD DEAD
0 1 DEAD DEAD
0 2 DEAD DEAD
1 3 DEAD DEAD
1 4 DEAD DEAD
d. Press any key.
A drive matrix showing the current configuration appears (Figure 5–1).
7848 4078–004 5–13

Installing UNIX on the Intel Node
5–14
Figure 5–1. Drive Matrix
e. Press S to save the current configuration.
A message indicates you should reboot.
f. Insert the SCU diskette in the drive unit and reboot.
g. Follow steps a through f to reload the DACCF utility.
h. The DACCF utility Main Menu appears as follows:
Main Menu
01. Automatic Configuration
02. New Configuration
03. View/Update Configuration
04. Rebuild
05. Initialize System Drive
06. Consistency Check
07. Tools
08. Select DAC960
09. Advanced Functions
10. Diagnostics
7848 4078–004

Installing UNIX on the Intel Node
4. Use the arrow keys to select 02 (New Configuration), then press Enter.
The New Configuration menu appears as follows:
New Configuration
1. Define Pack
2. Define System Drive
5. Use the arrow keys to select 1 (Define Pack), then press Enter.
A screen containing a drive matrix and the Pack Definition menu appears:
Pack Definition
1. Create Pack
2. Cancel Pack
3. Arrange Pack
4. Device Information
6. Use the arrow keys to select 1 (Create Pack), then press Enter.
A small cursor moves to the drive matrix so you can select the drives to be included
in the pack.
7. Select the drives for drive pack 1 as follows:
a. Use the arrow keys to move the cursor to drive 0,0
b. Press Enter to select the drive.
c. Repeat steps a and b for drive 0,1, drive 1,0, and drive 1,1.
d. Press Esc to finish creating the pack.
You are returned to the Pack Definition menu.
8. Use the arrow keys to select 1 (Create Pack), then press Enter.
9. Select the drives for drive pack 2 as follows:
a. Use the arrow keys to move the cursor to drive 0,2
b. Press Esc to finish creating the pack.
Because all of the drives have been defined in packs, the cursor automatically jumps
to the Arrange Pack option in the Pack Definition menu.
10. Press Enter to select the Arrange Pack option.
The cursor moves to the drive matrix.
11. Press Enter again to arrange the pack.
The pack being arranged moves to the pack table on the screen.
12. Press Enter again to arrange the next pack.
7848 4078–004 5–15

Installing UNIX on the Intel Node
5–16
The second pack moves to the pack table. All packs are now arranged and the New
Configuration menu is redisplayed.
New Configuration
1. Define Pack
2. Define System Drive
13. Select 2 (Define System Drive), then press Enter.
Two tables are displayed on the left side of the screen. The top left table lists all the
arranged packs and their sizes. The bottom left table is empty (no system drives
have been defined).
A System Drive Definition menu is displayed on the right side as follows:
System Drive Definition
1. Create System Drive
2. Toggle Write Policy
14. Select 1 (Create System Drive), then press Enter.
All arranged packs that are not part of a system drive are selected for the system
drive.
A RAID Level window is displayed:
RAID Level
RAID 0
RAID 1
RAID 5
RAID 6
RAID 7
15. Select RAID 5, then press Enter.
A window appears that displays the maximum possible size for the system drive to
be defined.
16. Press Enter to use the entire disk.
An information window describes the drive being created, followed by a
confirmation window.
17. Select Yes, then press Enter.
The system drive is created and the system drive table on the bottom left is updated.
18. Repeat steps 14 through 17 for the other disk pack, except select RAID 7 as the
RAID level.
7848 4078–004

Installing UNIX on the Intel Node
19. Change the write policy for both drives from write thru (write cache not enabled) to
write back (write cache enabled) as follows:
a. Select 2 (Toggle Write Policy) from the System Drive Definition menu, then
press Enter.
The cursor jumps to the Write Mode column in the system drive table.
b. Press Enter to toggle the write mode.
c. Move the cursor to the next drive, then press Enter to toggle its write mode.
20. Press Esc to return to the System Drive Definition menu.
21. Press Esc again to return to the Main Menu.
A confirmation window appears asking whether you want to save the configuration.
22. Select Yes, then press Enter.
The Main Menu is redisplayed.
Main Menu
01. Automatic Configuration
02. New Configuration
03. View/Update Configuration
04. Rebuild
05. Initialize System Drive
06. Consistency Check
07. Tools
08. Select DAC960
09. Advanced Functions
10. Diagnostics
23. Select 05 (Initialize System Drive), then press Enter.
A screen appears that lists all of the defined system drives on the left side. The
following messages appear on the right side and below the list:
More than one System Drive can be
initialized simultaneously. Select
to start initialization of the selected
System drives.
!!WARNING!! Initialization of the System
Drives will destroy data on the drives.
Select System drive(s) using cursor keys, hit , to Previous
Menu
24. Initialize both system drives as follows:
a. Use the arrow keys (or press Tab) to highlight one of the system drives, then
press Enter.
b. Highlight the other system drive and press Enter.
7848 4078–004 5–17

Installing UNIX on the Intel Node
5–18
c. Move the cursor to the START box at the bottom of the list, then press Enter.
A confirmation message appears.
d. Select Yes, then press Enter.
The system drives are initialized simultaneously. A progress bar appears for
each drive.
Once initialization is complete, a message to that effect is displayed.
25. Press any key to return to the Main Menu.
26. Select 03 (View/Update Configuration), then press Enter.
A View/Update Configuration menu appears as follows:
View/Update Configuration
1. Define Pack
2. Define System Drive
27. Select 2 (Define System Drive), then press Enter.
The System Drive Definition screen and menu appear.
28. Change the write policy for both drives back to write thru from write back as
follows:
a. Select 2 (Toggle Write Policy) from the System Drive Definition menu, then
press Enter.
The cursor jumps to the Write Mode column in the system drive table.
b. Press Enter to toggle the write mode.
c. Move the cursor to the next drive, then press Enter to toggle its write mode.
29. Press Esc to return to the System Drive Definition menu.
30. Press Esc again to return to the Main Menu.
A confirmation window appears asking whether you want to save the configuration.
31. Select Yes, then press Enter.
The Main Menu is redisplayed.
7848 4078–004

32. Use the arrow keys to select 07 (Tools), then press Enter.
The Tools menu appears as follows:
Tools
1. Bad Block Table
2. Error Counts
3. Format Drive
4. Make Online
5. Kill Drive
6. Backup/Restore Conf
7. Clear Configuration
8. Print Configuration
Installing UNIX on the Intel Node
33. Use the arrow keys to select 6 (Backup/Restore Conf), then press Enter.
The Backup/Restore Conf menu appears as follows:
Backup/Restore Conf
Backup Configuration
Restore Configuration
34. Select the Backup Configuration option, then press Enter.
You are prompted to enter a filename where the configuration is to be stored.
35. Insert a diskette (a blank diskette or the DAC960P Configuration and Utilities
diskette can be used) in the drive unit, then enter the file name and press Enter.
A confirmation message indicates that an existing file of the same name (if any) will
be overwritten.
36. Click Yes.
The configuration is saved to diskette.
37. Remove the diskette and reinsert the SCU diskette, then press any key to continue.
38. Press Esc to return to the Main Menu.
An exit confirmation screen appears.
39. Select Yes to exit.
The A:\ prompt is displayed.
40. Remove the diskette and reboot.
You may now install the UNIX operating system as described in 5.4.
7848 4078–004 5–19

Installing UNIX on the Intel Node
5.4. Installing the UNIX Operating System
5–20
If you determined that you must install the UNIX operating system software, take the
following steps:
Notes:
Cautions
This procedure should be used only to initially install the operating system.
Because this is a destructive procedure, make sure you have read and
understand the procedure before proceeding.
During the procedure, be sure the Caps Lock key does not become locked in
the uppercase position while making entries. Use the Shift key if you want to
enter an uppercase password.
Switch the monitor concentrator to the Intel Node position before beginning
(see 3.2).
Use default responses unless otherwise noted.
1. With the system powered off, turn the system key counterclockwise to the
maintenance position (wrench symbol). In the maintenance position you can select
the boot media during the boot process.
2. Power the system on.
3. Insert the boot diskette and UNIX operating system CD-ROM or tape into the
appropriate drive unit. They are labeled as follows:
The boot diskette is labeled “U6000 & SMP Systems, UNIX System Release 4.0
Boot Diskette.”
The operating system CD-ROM is labeled “U6000 Series UNIX System V Release
4.0 Software.”
The operating system tape is labeled “OS SVR4 Release 1.4-Runtime.”
You are prompted to select the boot media.
SMP61000 Option Select Menu
Version 6.0.0 04/11/96
1) Load New Firmware
2) Run Embedded Diagnostics
3) Select Diagnostic Console
4) Boot From Diskette
5) Boot From Tape
6) Boot From Disk
Enter option number:
7848 4078–004

Installing UNIX on the Intel Node
4. Enter 4 to select a boot from diskette. Please wait. After about 7 minutes,
a message appears asking if you have a color monitor.
UNISYS SVR4/MP–HA Installation, Console Monitor Type Selection
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
_________________________________________
| | | | |
|_________|_______|__________|___________|
Do you see colours in the box drawn above? [Y/n]:
5. Enter yes (Y) to indicate that you see colors. You are prompted to confirm the entry.
You appear to have a “COLOUR” monitor.
Is this correct? [Y/n]
6. Enter yes (Y) to confirm that you have a color monitor. A welcome message
appears.
WELCOME TO THE UNISYS U6000(tm) SERIES
––––––––––––––––––––––––––––––––––––––
This is the Installation and Maintenance Interface
for the UNISYS UNIX(tm) SVR4/MP–HA
(Multi–Processor / High Availability) O/S.
Press Control–C at any time to cancel
and restart the Operating System installation.
Copyright (C) 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996 UNISYS Corp.
Copyright (C) xxxx, xxxx, xxxx, . . .
All Rights Reserved.
Press RETURN to continue or ? for help:
Note: As indicated by the welcome message, you can press CTRL-C to abort the
boot at any time that media is not being loaded.
7. Press Enter, to continue. You are prompted to select a keyboard type and confirm
the selection.
Keyboard Type Selection
–––––––––––––––––––––––
1) American (English/ASCII) 10) Latin–American
2) Belgian 11) Norwegian
3) Canadian (English) 12) Portuguese
4) Canadian (French) 13) Spanish
5) Danish 14) Swedish
6) Dutch 15) Swiss (German)
7) French 16) Swiss (French)
8) German 17) United Kingdom
9) Italian
Please select by option number: [1]: x
7848 4078–004 5–21

Installing UNIX on the Intel Node
5–22
You have selected a xxxxxx keyboard.
Note the selection of the wrong keyboard may result
in difficulty answering etc
Is this correct? [Y/n]
8. Enter the number of the keyboard type you wish to use. After selecting a keyboard
type, you are asked whether you have run the system configuration utility (SCU) and
whether you want to terminate this installation procedure.
System Configuration and Preparation
––––––––––––––––––––––––––––––––––––
If you have not configured this system with the System
Configuration Utility (SCU), you should do so at this
time. This installation will not proceed correctly
unless the SCU utility has been run (and the system
suitably configured).
If this is a system with an existing software
installation, it should be fully backed–up and archived
before continuing with this installation.
Do you wish to terminate this installation? [y/N]:
9. Enter no (N). The SCU already has been run for all cards installed at the factory.
You need to run SCU again only if you add a hardware feature or change the
hardware configuration.
A message appears asking whether this is a new installation or a system upgrade:
Installation and Maintenance Selection
––––––––––––––––––––––––––––––––––––––
1) New Installation (This will erase ALL disk contents!)
2) 1.2(.X) or 1.3(.X) System Upgrade
3) Help
Please select by option number: [1]: 1
10. Enter 1 to select New installation. You are prompted to select the type of
installation.
Installation Options Selection
––––––––––––––––––––––––––––––
1) Easy Installation
2) Configurable Installation
3) Help
4) Return to Main Menu
Please select by option number: [1]: 1
7848 4078–004

Installing UNIX on the Intel Node
11. Enter 1 to select Easy installation. You are prompted to enter the time zone for the
site.
Timezone Selection
––––––––––––––––––
1) Greenwich Meantime (GMT) 9) Alaskan, USA (AST)
2) Atlantic, Canada (AST) 10) Hawaiian, USA (HST)
3) Eastern, USA (EST) 11) Eastern European (EST)
4) Central, USA (CST) 12) Middle European (MET)
5) Mountain, USA (MST) 13) Western European (WET)
6) Pacific, USA (PST) 14) Indian (IST)
7) Yukon, Canada (YST) 15) New Zealand (NZST)
8) Bering, USA (BST) 16) Japanese (JST)
Please select by option number: [1]: x
12. Select the appropriate time zone. If your time zone is not listed, pick a zone and
correct the time in the next step. A prompt asks whether daylight saving time is
applicable to your time zone selection.
Is daylight saving time observed in your locale? [Y/n]:
Answer yes (Y) if you want to have daylight saving time support.
13. Confirm that the current date and time are correct.
Setting System Date and Time
––––––––––––––––––––––––––––
Current date is Tue Mar 5 18:23:25 MST 1996.
Is this correct? [Y/n]:
7848 4078–004 5–23

Installing UNIX on the Intel Node
5–24
If you answer no (N), enter a new date and time. After entry of the correct date and
time, you are prompted to set and confirm a default password that will be used by
several users.
Setting Default System Passwords
––––––––––––––––––––––––––––––––
The password you are about to enter will be used for the following users:
– root (superuser)
– install
– bin
– dtadm
– mlsadmin
– sysadm
– makefsys
– checkfsys
– mountfsys
– unmountfsys
– setup
– powerdown
IMPORTANT: After installation you should assign unique passwords to these
users. Use the System Administration (OAM) menus or the passwd(1) command.
New Password:
14. Enter unisys1234 (the default installation password). The password does not
appear on the screen as you type it. The site later changes the password during site
customization (the new password must be at least eight characters in length and
include at least two alphabetic characters and one numeric or special character).
You are asked to reenter the password to confirm it.
After entry of the password, you are prompted to enter a site-defined system name
and to confirm the selection.
Setting System and Node Names
–––––––––––––––––––––––––––––
Please enter a System Name for this system. This will set
the ”node” name and the ”system” name. This name will be
used for uucp(1) and networking. This name cannot be ”unix”,
an empty string (””) or more than 8 characters in length.
Please enter the System Name: xxxxxx
The System Name chosen was ”xxxxxx”
Is this correct? [Y/n]: y
7848 4078–004

Installing UNIX on the Intel Node
15. Enter the system name determined by your site, and confirm that it is correct. You
are prompted to configure enhanced reliability, availability, and serviceability (RAS)
features.
RAS Features Determination
––––––––––––––––––––––––––
The system can be configured to take advantage of many enhanced
Reliability, Availability and Serviceability features during
installation.
These features include Disk Mirroring, Spanning, Striping and
RAID5 operation, enhanced error logging and event handling and
media archiving.
If not configured at installation time, these features may be
configured at a later time.
Do you wish to configure the enhanced RAS features? [y/N]:
16. Enter no (N). Do not configure the RAS features at this time. Alternate RAS
features are provided by the Unisys Volume Manager, which is installed later. You
are asked whether you want to manually configure the boot disk.
Disk Configuration Options
––––––––––––––––––––––––––
This installation can be performed using a default boot disk
partitioning scheme, such that the disk layout will be dependent
upon the boot disk size and type. Optionally the boot disk can
be manually configured for an optimal disk layout.
Do you wish to manually configure the system boot disk? [y/N]:
17. Enter yes (Y) (not the default) to manually configure the boot disk. You configure
disk drive 0 according to the required values given in Table 5–1. The system
suggests a configuration and asks whether you want to change the layout.
Note: Display may vary depending on device type.
Disk Layout Selection
–––––––––––––––––––––
This is disk drive #0 (Size: 4150MB, Type: UM293).
Currently, this disk will be partitioned according to the
following layout:
Slice # Size (MB) FS Type Block Size Mount Point
––––––– ––––––––– ––––––– –––––––––– –––––––––––
1 200 ufs 4k /
2 17 bfs –– /stand
3 242 –––– –– /dev/swap
4 923 ufs 4k /home
5 923 ufs 4k /home1
6 923 ufs 4k /home2
7 923 ufs 4k /home3
Do you want to change the layout of disk drive #0? [Y/n]:
7848 4078–004 5–25

Installing UNIX on the Intel Node
5–26
Caution
Ignore disk partitioning recommendations provided by prompting messages.
Successful operation of the tuning script requires that you set up the boot disk
configuration as described in Table 5–1.
18. Enter yes (Y) to change the layout of disk drive 0. You are prompted to enter the
number of slices that should be created.
How many slices should be created on disk drive #0 [3–15]:
19. Enter 9 as the number of slices to create. A message similar to the following gives
disk partitioning information (to be ignored).
Disk #0 Partition Sizing Information
––––––––––––––––––––––––––––––––––––
Slice #1 on the boot disk is reserved for the root file system
(/) and must be at least 100MB in size. If the disk is
large enough 200MB is recommended for a full installation,
without GDM. Increase this to 300MB for GDM inclusion.
Note: specifying very small root partitions will require
the use of separate /var, /tmp, /usr and /home partitions.
Slice #2 on the boot disk is reserved for the boot file system
.
.
Press RETURN to continue:
When you press Enter to continue, you are prompted to enter information about the
first slice.
Partition Information for Disk #0, Slice #1
-------------------------------------------
Disk #0, xxxMB (of xxxMB) remaining . . .
Select the size (MB) for slice #1 (200 for “/”):
20. Enter 950 as the size of slice 1 (see Table 5–1). You are prompted to select the file
system type.
Select file system type for slice #1.
1) UNIX Fast File System (ufs)
2) UNISYS Bitmapped System V File System (s5bm)
3) Standard AT&T System V File System (s5)
4) Veritas File System (vxfs)
5) No File System (raw)
6) Secondary Swap Area (swap)
Please select by option number: [1]:
7848 4078–004

Installing UNIX on the Intel Node
21. Enter 4 to select the Veritas File System (vxfs). You are prompted to enter the block
size for the slice.
Select block size for file system type vxfs on slice #1.
1) Block Size 1KB
2) Block Size 2KB
3) Block Size 4KB
4) Block Size 8KB
Please select by option number: [1]:
22. Enter 3 to select a block size of 4 KB. You are prompted for information about
slice 2.
23. Enter the information shown in Table 5–1 for slice 2 and the remaining slices.
Notes:
Slice 2 and 3 prompt only for the partition size; the rest is assigned
automatically.
Slice 4, 5, 6, 7, and 8 prompt for partition size, file system type, block size,
and mount point.
Slice 9 prompts for file system type, block size, and mount point—the size of
the partition is automatically the remaining space.
A message appears confirming the disk layout and asking whether you want to
change it:
Disk Layout Selection
–––––––––––––––––––––
This is disk drive #0 (Size: xxxxMB, Type: UST31).
Currently, this disk will be partitioned according to the
following layout:
Slice # Size (MB) FS Type Block Size Mount Point
––––––– ––––––––– ––––––– –––––––––– –––––––––––
1 950 vxfs 4k /
2 32 bfs –– /stand
3 520 –––– –– /dev/swap
4 400 vxfs 4k /opt
5 800 vxfs 4k /home
6 800 vxfs 4k /home1
7 800 vxfs 4k /home2
8 800 vxfs 4k /home3
9 xxx vxfs 4k /home4
Do you want to further change the layout of disk drive #0? [y/N]:
Note: The remaining disk space shown in slice 7 may vary.
7848 4078–004 5–27

Installing UNIX on the Intel Node
5–28
24. Enter no (N) to indicate that you do not want to change the layout. A message then
asks whether you want to format the disk.
Caution
The disk drive has been formatted at the factory. To prevent wasted time, do not
format the disk drive at this time.
Do you want to format disk drive #0? [y/N]:
25. Enter no (N); the drive is already formatted. Next, you are asked whether you want
to install the Graphical Desktop Metaphor package (gdmusr).
Graphical Desktop Metaphor (GDM), X Server Configuration
––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Your system is equipped with a VGA capable (or better) graphics
controller.
You can automatically install gdmusr etc. . . .
Do you wish to automatically install the gdmusr package? [Y/n]: Y
Note: A GDM developer’s kit will be copied to the disk drive later in this
procedure.
26. Enter yes (Y). A message describes the network driver configuration.
Configuration Of The Network Adapter Drivers
––––––––––––––––––––––––––––––––––––––––––––
Configuring the d140 Ethernet device driver for the
PCI 32-bit 10/100MB/S Ethernet Controller(s).
Press RETURN to continue:
27. Press Enter to continue. After pressing Enter, you are prompted to establish your
networking configuration.
Host Network Configuration Selection
––––––––––––––––––––––––––––––––––––
Your system is equipped with a Local Area Network controller.
You can either configure the basic networking configuration
during this installation, or you can configure them after the
system has been completely installed.
Do you wish to configure the Local Area Networking now? [Y/n]: Y
7848 4078–004

Installing UNIX on the Intel Node
28. Enter yes (Y). You are prompted to enter the internet protocol (IP) address that
identifies the UNIX node to your external Ethernet production LAN. You are asked
to confirm the address entered.
Internet Protocol (IP) Address Selection
––––––––––––––––––––––––––––––––––––––––
Please enter your local system IP Address. The IP Address is the
address by which your system will be known on the Internet.
These addresses must be administered by a central authority on
your network. IP Addresses are written as four decimal integers,
separated by decimal points and no spaces (e.g. 128.10.2.70).
Your system IP Address is? : xxx.xxx.xxx.xxx
Your system IP Address has been set to xxx.xxx.xxx.xxx
Is this correct? [Y/n]:
Note: IP addresses must be administered by a central administrator at the site.
29. Enter the IP address of the UNIX node and confirm the entry. You are prompted to
confirm the default calculated Netmask value or enter a new value.
Internet Protocol Netmask Selection
–––––––––––––––––––––––––––––––––––
Your local system Netmask is set to : xxx.xxx.xxx.xxx
You can either use this value, calculated from your system
IP Address, or you can enter a new value if you use
subnet addressing and wish to overide it.
Please select a new Netmask value or press enter to use the
calculated default: [ xxx.xxx.xxx.xxx ] xxx.xxx.xxx.xxx
30. Change the calculated value if necessary; otherwise press Enter. You are asked to
confirm the entry.
Your local system Netmask has been set to xxx.xxx.xxx.xxx
Is this correct? [Y/n]:
31. Enter yes (Y) to confirm that the value is correct and continue with network setup.
You are asked whether you want to identify a default gateway service.
Default Gateway System Selection
––––––––––––––––––––––––––––––––
You can select a system to provide a Gateway service between
your local subnet and any backbone networks on your site.
This is sometimes the Internet Address of another computer acting
as a Gateway, or more often the Internet Address of a dedicated
standalone Router system.
Do you wish to provide an IP Address for a Gateway? [y/N]:
7848 4078–004 5–29

Installing UNIX on the Intel Node
5–30
32. The default is no (N). If you enter yes (Y) you are prompted to enter and then
confirm the IP address for the gateway.
You are then prompted to enter a network domain name to identify the local
network.
Network Domain Name Selection
–––––––––––––––––––––––––––––
Please enter a Network Domain Name for this system. This will
be used by the Domain Name Services as a name suffix for
system names that do not include a period (.) character
in them.
This name will also be used to identify the local network
in the /etc/networks database file.
The name slc.unisys.com would be a suitable example of a valid
Domain Name.
Please enter the Domain Name: xxx.xxx.xxx.xxx
The Domain Name chosen was xxx.xxx.xxx.xxx
Is this correct? [Y/n]: y
33. Enter the network domain name and confirm your choice. You then must decide
whether you want to identify a Domain Name Services (DNS) host.
Directory Name Services (DNS) Host Selection
––––––––––––––––––––––––––––––––––––––––––––
You can elect to use Directory Name Services (DNS) host or a
statically configured /etc/hosts file for resolving
system names to Internet Addresses. If you choose to use a DNS
host, then you will be prompted for the Internet Address of the
DNS server systems on your network. The DNS host chosen here is
the Primary DNS host. Further hosts can be configured in the
/etc/resolv.conf file after installation.
Do you wish to use a DNS host? [y/N]:
34. The default is no (N). If you answer yes (Y), you are prompted to enter and then
confirm the IP address for the DNS. Following that entry, the values you have
selected are stored in the system and you are prompted whether to continue or start
over. There is no default answer to this question.
System Installation Confirmation
––––––––––––––––––––––––––––––––
The installation of the UNIX System V Release 4/MP Operating
System will now begin. It will take about an hour to complete.
A negative answer to this question will terminate the
installation procedure.
Do you want to proceed? [y/n]: y
7848 4078–004

Installing UNIX on the Intel Node
35. Enter yes (Y) to continue. The software repartitions the disk and installs the
software in the configuration you have defined.
Note: The complete installation may take up to 1 hour, depending on your
system configuration. Messages appear during the installation that
contain information about the operating system release.
When package installation is completed, the following appears:
Package Installation
––––––––––––––––––––
Package installation is now complete.
Rewinding the tape ... done.
Operating System Kernel Build
–––––––––––––––––––––––––––––
The UNIX Operating System will now be rebuilt.
This will take some time. Please wait.
The UNIX Kernel has been rebuilt.
Messages resulting from package installation are captured in a log file,
(/var/sadm/install/logs/INSTPKG.log). Many of these message contain useful
information you might want to review.
36. The system is configured for the new kernel and you are prompted to reboot the
system.
System Installation, Configuring System
–––––––––––––––––––––––––––––––––––––––
Configuring the system as a result of the new kernel ... done.
System Reboot
–––––––––––––
Please remove all CD–ROMs, tapes and diskettes from their
respective devices.
Press RETURN to reboot:
37. Remove the installation media, turn the key to the unlocked position, and press
Enter to reboot the system. The console login prompt appears following the reboot.
Console Login:
38. Log on as superuser (5.6). The UNIX root prompt (#) appears.
#
39. Copy the UNIX operating system IOE products from the installation media into the
default spooling directory using the procedures described in 5.5.
7848 4078–004 5–31

Installing UNIX on the Intel Node
5.5. Copying IOE Products to the Spooling
Directory
5–32
Notes:
Procedures in this subsection immediately follow step 38 in 5.4, so there is no
need to reboot or log on again as superuser.
To ensure procedures that are consistent with the preinstalled software
procedures, you must copy all UNIX IOE products into the spooling directory
(except those indicated in 5.5.3) even though you later may choose not to install
some products when the tuning script is run. For example, the tuning script does
not install the Volume Manager package and it prompts whether you want to
install SNMP agent and the GDM developer’s kit (see 5.7).
In any order, copy the following UNIX operating system IOE products from tape or
diskette into the default spooling directory using the procedures in 5.5.1:
FDDI driver (SK-FDDI)—The driver for the EISA FDDI card (located on diskette
media—copies to disk in about 1 minute)
Veritas VxFS file system—The file system used for several boot disk (disk 0)
partitions (located on tape media—copies to disk in about 1 minute)
Simple Network Management Protocol (SNMP) agent (located on tape
media—copies to disk in about 2 minutes)
Open/OLTP Pathway (located on tape media—copies to disk in about 2 minutes)
Volume Manager (located on tape media—copies to disk in about 4 minutes)
Also copy the Graphical Desktop Metaphor (GDM) developer’s kit for
internationalization using the procedures in 5.5.2. GDM is located on the UNIX
operating system CD-ROM or on tape 2 if the operating system came on tape.
GDM copies to disk in about 5 minutes.
UNIX IOE products that are not copied at this time are listed in 5.5.3.
After copying the last base product to the spooling directory, remove all media from
drive units and run the tuning script (5.7).
7848 4078–004

5.5.1. Copying from Tape or Diskette
Installing UNIX on the Intel Node
Note: When copying from tape, the tape is done loading when the pound sign (#)
prompt reappears and the light on the tape unit has stopped blinking.
Take the following steps to copy the FDDI driver from diskette or the Veritas file system,
SNMP agent, Volume Manager, or Open/OLTP Pathway from tape:
1. Enter the pkgadd command as follows:
# pkgadd –s /var/spool/pkg –d media all
where media is diskette1 or ctape1 depending on the media from which the
product is being copied.
A prompt to insert the diskette or tape appears:
Insert xxxxx into xxxxx drive.
Type [go] when ready,
or [q] to quit:
2. Insert the diskette or tape for the product into the drive unit, then type go and press
Enter.
5.5.2. Copying the GDM Developer’s Package
To copy the GDM developer’s package from CD-ROM, take the following steps:
1. Insert the CD-ROM in the drive unit and enter the following command to mount it:
# mount -f cdfs /dev/cdrom/d0 /mnt
2. Enter the following command to copy the package:
# pkgadd –s /var/spool/pkg –d /mnt/cdpkgs/gdmdev gdmdev
3. Unmount the CD-ROM by entering the following command:
# umount /mnt
If the operating system comes on tape, you can copy the GDM developer’s package by
inserting tape 2 in the drive unit and entering the following command:
# pkgadd –s /var/spool/pkg –d ctape1
Select the GDM developer’s package from the list provided.
7848 4078–004 5–33

Installing UNIX on the Intel Node
5.5.3. Products Not Copied to the Spooling Directory
5–34
The following products are part of the UNIX IOE, but are not copied or installed at this
time:
Unisys UNIX Internet Package (UUIP)
Web Transaction Enabler (WebTX)
After hardware RFU, install those products according to procedures in 10.8.1 and 10.8.2.
5.6. Logging On as Superuser
Caution
To prevent unauthorized access to the UNIX node following initial installation, the
site must change the default password (unisys1234) to a different password.
Note: Switch the monitor concentrator to the Intel Node position before beginning
(see 3.2).
Several installation and configuration procedures require you to log on as root
(superuser). Do that as follows:
1. Ensure that the system key in the front panel is in the unlocked position and not the
maintenance position.
2. Power on the system if it is off, or reboot the system by pressing one of the boot
switches on the front panel. In response, the console login prompt appears as
follows:
Console Login: mlsadmin
3. Enter mlsadmin in response. You are prompted to enter a password:
Password:
4. Enter unisys1234 (the default installation password). This password will be
changed later during site customization. The password does not appear on the
screen as you type it.
The UNIX shell prompt ($) appears as follows:
$
At this point, you can begin using the UNIX operating system. When you log in as
mlsadmin, the C2 Commercial Secure feature prevents you from logging in as root.
To complete installation and configuration of the UNIX node IOE software, you
must log in as superuser.
7848 4078–004

Installing UNIX on the Intel Node
5. Enter the su command (type su and press Enter) to log in as superuser. You are
prompted to enter a password:
Password:
6. Enter the same password you used for mlsadmin. The UNIX root prompt (#)
appears.
#
Once the UNIX root prompt (#) appears, you can enter any command that requires
superuser capabilities.
5.7. Installing and Running the Tuning Script
(Site-Installed UNIX)
Note: Perform this procedure only if you installed the UNIX operating system and
entered site-specific information as described in 5.4. If the UNIX operating
system was preinstalled, install and run the tuning script as described in 5.2.
The tuning scripts diskette contains a script you must run to complete installation and
configuration of the UNIX operating system IOE. Take the following steps to install and
run that tuning script:
1. If you are not already logged on, log on as root (superuser) (see 5.6).
2. Insert the tuning scripts diskette into the disk drive and enter the following
command to install and execute the tuning script (cptune):
# pkgadd -d diskette1 cptune
Messages appear prompting you to enter commands to change directories and start
the tuning script:
ClearPath tuning and configuration script
Version 1.0 TAKE 3 (UN6000/U)
Copyright (c) 1996 Unisys, Inc. All Rights Reserved.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
Installing ClearPath Tuning and configuration script as
## Installing part 1 of 1.
[ verifying class ]
## Executing postinstall script.
Please enter the following commands to comlete the Clearpath tuning:
cd /var/sadm/pkg/cptune/install
sh CP_tune
Installation of was successful.
7848 4078–004 5–35

Installing UNIX on the Intel Node
5–36
3. As indicated in the message, enter the cd and sh commands as follows:
# cd /var/sadm/pkg/cptune/install
# sh CP_tune
You are asked whether the operating system was installed by you or by the factory.
If you installed the UNIX OS, you have already
configured it. If the OS was installed at the
factory, you need to customize it for your site.
Did you install the UNIX OS? [Y/n]: y
4. Enter yes (Y) to indicate that you installed the UNIX operating system. A series of
messages appear relating to kernel parameters being set, product installation, the
setting of network parameters, and the setting up of partitions on disk. The
messages end with a prompt asking whether you want to add the SNMP agent
package.
Tuning SEMMNI 500
Tuning SEMMNS 800
Tuning SEMMNU 400
Tuning SEMMSL 400
Tuning SHMMNI 256
Tuning MSGMNI 128
Tuning SHMMAX 150000000
Tuning NPROC 1000
Tuning MAXUP 1000
Tuning SDATLIM 0x7FFFFFFF
Tuning HDATLIM 0x7FFFFFFF
Tuning SVMMLIM 0x7FFFFFFF
Tuning HVMMLIM 0x7FFFFFFF
Tuning SFSZLIM 0x7FFFFFFF
Tuning HFSZLIM 0x7FFFFFF
Tuning SFNOLIM 512
Tuning HFNOLIM 2000
Tuning NUMTIM 512
Tuning NUMTRW 512
Tuning UFSNINODE 2000
Tuning NINODE 1000
Tuning NREGION 350
Tuning NCALL 400
Tuning SSTKLIM 0x7FFFFFFF
Tuning HSTKLIM 0x7FFFFFFF
Tuning STRTHRESH 0
pkgadd –r /var/sadm/pkg/cptune/install/skfe skfe
Processing package instance from
UNISYS SysKonnect FDDI UNIX Driver
Version 3.1 (UN6000/U)
Copyright (C) Schneider & Koch & Co. 1989–1993
Copyright (C) SysKonnect 1993
All Rights Reserved.
## Processing package information.
## Processing system information.
## Verifying package dependencies.
## Verifying disk space requirements.
7848 4078–004

Installing UNISYS SysKonnect FDDI UNIX Driver as
## Installing part 1 of 1.
[ verifying class ]
## Executing postinstall script.
Installing UNIX on the Intel Node
The system configuration has been changed since the last US6000–ETD
device driver configuration was entered. The installation script
will be executed again.
Press any key to continue...
5. If this message appears, press Enter to continue with the tuning script. More
messages appear.
Welcome to the SK–FDDI device driver installation program for UNIX System
V
Release 4. This program assumes you have executed the SCU for each
SK–FDDI adapter you plan to use. This device driver can only be
configured
for adapters which have been configured with the SCU. This program also
assumes that this device driver is not currently installed.
If you have not run the SCU, please exit this program and execute it now.
If the skfe device driver is installed, please remove it before installing
this device driver. Use the command ’pkgrm skfe’.
If the skfe device driver is currently installed, please exit this
program and and remove it now.
Do you want to install the SK–FDDI device driver? [y,n]
Note: The message “Do you want to install the SK-FDDI device driver? [y,n]:”
(as in this example) indicates that the tuning script has detected that the
IRQ/DMA setup for the FDDI card is different from what it expects. If that
message appears, enter yes (Y) to continue. Your response is not echoed
on the screen, and the tuning script continues processing.
Searching for SK FDDI Controllers...
SK–FDDI Driver Configuration
============================
Adapter 1 type: SK–FDDI
IRQ: nn
DMA: n
SCU information read successfully.
Do you want to install with this configuration? [y,n]
Note: The message “ Do you want to install with this configuration? [Y/n]:”
(as in this example) indicates that the tuning script has detected that the
IRQ/DMA setup for the FDDI card is different from what it expects. If that
message appears, enter yes (Y) to continue. Your response is not echoed
on the screen, and the tuning script continues processing. In about 15
seconds more messages appear.
7848 4078–004 5–37

Installing UNIX on the Intel Node
5–38
Loading skfe ... done.
***************************************************************
Installation of SysKonnect SK–5341 FDDI Driver passed.
Please refer to the Release Notice on how to set up the strcf
file to run TCP/IP on FDDI
***************************************************************
Installation of was successful.
pkgadd vxfs
Processing package instance from
VERITAS File System
Version 1.2.3 Advanced MP Take–3 (UN6000/U)
Copyright (c) 1991, 1992 VERITAS SOFTWARE CORP. ALL RIGHTS RESERVED.
THIS
SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS
SOFTWARE, AND/OR ITS SUPPLIERS.
pkgadd pathway
Copyright (c) 1996 UNISYS, Inc. All rights reserved.
## Processing package information.
## Processing system information.
37 package pathnames are already properly installed.
## Verifying disk space requirements.
Installing VERITAS File System as
## Executing preinstall script.
## Checking for acceptable OS version.
Saving the vxfs lite files
## Installing part 1 of 1.
[ verifying class ]
## Executing postinstall script.
Installing VERITAS File System vxfs module ...
The UNIX Operating System will now be rebuilt.
This will take some time. Please wait.
Root for this system build is /
The UNIX Kernel has been rebuilt.
Removing temporary packaging files ...
Installation of was successful.
*** IMPORTANT NOTICE ***
If installation of all desired packages is complete,
the machine should be rebooted in order to
ensure sane operation. Execute the shutdown
command with the appropriate options and wait for
the “Console Login:” prompt.
pkgadd pw3–1–0
Processing package instance from
Pathway
Version 3.1.0SVR4 (UN6000/U)
Using as the package base directory.
7848 4078–004

Copyright (c) 1987–1990 AT&T
Copyright (c) 1991–1994 UNIX System Laboratories, Inc.
(a wholly–owned subsidiary of Novell, Inc.)
Copyright (c) 1989–1994 Unisys Corporation
All Rights Reserved
## Processing package information.
## Processing system information.
## 3 package pathnames are already properly installed.
## Verifying disk space requirements.
Installing Pathway as
## Installing part 1 of 1.
[ verifying class ]
Installation of was successful.
Would you like to add the SNMP agent package? [Y/n]: y
pkgadd agent
Installing UNIX on the Intel Node
6. Enter yes (Y) or no (N) to indicate whether you want to install the SNMP agent
package. The SNMP agent needs to be installed only if the site wishes to control the
ClearPath IX server using an SNMP manager such as HP OpenView.
More messages appear (such as “Installation of was successful”) followed
by a prompt asking whether to install the GDM developer’s kit.
Would you like to add the GDM Development package? [Y/n]:
7. Enter yes (Y) or no (N) to indicate whether you want to install the GDM
development package. The GDM developer’s kit needs to be installed only if the site
will be developing X Window applications. If you answer yes (Y), you should see the
following message:
Installation of was successful.
More messages appear, followed by a prompt asking if a RAID controller is installed.
Adding ClearPath defaults to /etc/hosts
Adding ”fddi22am” to /etc/hosts.equiv
Changing the host name of the FDDI interface to fddiuxsr in
/etc/inet/rc.inet
Configuring dump disk and checking swap partitions ....
Setting up partitions on disk 1 ....
Is a raid controller installed? (Y/n)
8. Enter yes (Y) unless you are reinstalling software at a ClearPath release 1.0 site that
does not have a RAID controller—then you should enter no (N).
7848 4078–004 5–39

Installing UNIX on the Intel Node
5–40
More messages appear.
scsiformat –u /dev/rdsk/c0.0d1 desc.drv1_raid
/dev/rdsk/1s1 not mountable and not in use by kdm
– OK to use for dump disk.
Making dump disk on /dev/rdsk/1s1.
/dev/rdsk/1s1 will be configured as a dump disk partition.
This partition will be exclusively used for taking crash dumps.
Any existing data in this partition will be lost.
Do you wish to continue?
Yes or No [y,n,?,q] Thank you.
Configuring /dev/rdsk/1s1 as a dump disk.
Modifying sassign file.
done.
Creating device node for the dump disk.
done.
/dev/rdsk/1s1 configured as the dump disk partition.
The running kernel has been modified for this.
Rebuilding unix kernel to make this change permanent.
done.
The UNIX Operating System will now be rebuilt.
This will take some time. Please wait.
The UNIX Kernel has been rebuilt.
Checking Swap configuration
Setting up NFS ....
Creating mount directory ”/rmnt”
Changing ”initdefault” value from 2 to 3 in /etc/inittab
Changing ”initdefault” value . . . in /etc/conf/ef.d/init.base
Changing the value of VX_NINODE from 500 to 2000 in
/etc/conf/pack.d/vxfs/space.c
The UNIX Operating System will now be rebuilt.
This will take some time. Please wait.
Root for this system build is /
The UNIX Kernel has been rebuilt.
****************************************************
The system must be rebooted to load the new kernel.
****************************************************
Finished running the ClearPath tuning script.
Press return to shutdown and reboot.
7848 4078–004

Installing UNIX on the Intel Node
9. Press Enter to reboot the system. Reboot takes about 7 minutes.
After the reboot, proceed to Section 7 to
Install SPO server and LT501 X terminal software
Create UNIX Resource Manager (URM) agent files on the SPO server and copy them
to the UNIX node
See Section 10 for a description of how to install optional software packages on the
UNIX node.
7848 4078–004 5–41

Section 6
Installing SPO/HMP Console and
Related Software
Cautions
Except for yes (Y) or no (N) entries, all entries and responses to prompting
messages in this section are case sensitive. Type entries exactly as shown.
During the procedures in this section, be sure the Caps Lock key does not
become locked in the uppercase position while making entries. Use the Shift
key if you want to enter an uppercase password.
Note: If reinstalling SPO/HMP Console software (for example, when installing a
new level of software), follow the migration guidelines given in Appendix D.
The installation steps you take depend on whether or not SPO/HMP Console and related
software are preinstalled on the SPO server as follows:
If SPO/HMP Console and related software are preinstalled, take the steps in 6.2.
If SPO/HMP Console and related software are not preinstalled, do the following:
− Run the system configuration utility (SCU) if required (6.1).
− Install the UNIX operating system on the SPO server (6.3).
− Log on as the superuser (6.4).
− Install UNIX operating system patches (6.5).
− Install X terminal software (6.6).
− Install the multiport card driver (6.7).
− Install SPO/HMP Console software (6.8).
− Install and run a tuning script from the tuning scripts diskette (6.9).
− Copy the hosts file to the system consoles (6.10).
− Remotely install Autoaction Message System (AMS) databases on 2200 node
system consoles (6.11).
− Enable use of the X terminal (Section 7).
If the UNIX operating system is preinstalled, but not the SPO/HMP Console
software, skip installation of the UNIX operating system (6.3), but otherwise do all
of the procedures listed above (6.1, 6.4 through 6.11, and Section 7).
7848 4078–004 6–1

Installing SPO/HMP Console and Related Software
6–2
To determine whether the UNIX operating system and SPO/HMP Console software are
preinstalled, take the following steps:
1. Power on or reboot the SPO server (press the soft reset switch on the front panel).
If the UNIX operating system is installed, the console login prompt appears as
follows:
Console Login:
Otherwise, the system displays the following error message:
Non-System disk or disk error
Replace and Press any key when ready.
2. If the UNIX operating system is not present, skip the rest of this procedure—none of
the software is preinstalled. If the UNIX operating system is present, log on as
superuser (6.4).
3. Enter the following sequence of commands to verify that SPO/HMP Console
software is preinstalled:
cd /opt/SPO
ls
If the /opt/SPO directory is not present or is empty, the SPO/HMP Console software
is not preinstalled.
Caution
The standard UNIX factory default partitions established by Unisys are incorrect
for running SPO/HMP Console software. If the site is providing a SPO server, they
must repartition that server to ensure that the slices are the same as defined
in 6.3.
6.1. Running the System Configuration Utility
(SCU)
If the site has installed an optional circuit card or changed the SPO server hardware
configuration for any reason, you must run the System Configuration Utility (SCU) to
reconfigure the SPO server. If new devices were added, gather diskettes containing
driver software before running SCU. SCU prompts for the diskettes during installation
procedures. Refer to the SMP5400 Series System Configuration Utility User’s Guide
for detailed instructions.
7848 4078–004

Installing SPO/HMP Console and Related Software
You also may need to run SCU if an Ethernet error message appears when installing the
UNIX operating system or when running the tuning script if UNIX is preinstalled. You
may be connected to the Ethernet controller using a connector other than the thick
cable Ethernet connection (10Base-5) assumed to be the default.
To reconfigure the controller for the type of connector being used, refer to
“Reconfiguring Your System” in the U6000 Series UNE6000-ETH Ethernet Controller
Installation Guide.
6.2. Steps to Take If Software Is Preinstalled
If the UNIX operating system and SPO/HMP Console software are preinstalled, you must
take the following steps:
1. Run the System Configuration Utility (SCU) if required (6.1).
2. Log on as the superuser (6.4).
3. Install and run the tuning script as described in this subsection.
4. Copy the hosts file to the system consoles (6.10).
5. Remotely install Autoaction Message System (AMS) databases on 2200 node system
consoles (6.11).
6. Enable use of the X terminal (Section 7).
Notes:
When you run the tuning script, you need a blank 3-1/2-inch floppy diskette (can
be either MS-DOS or UNIX operating system format) on which to copy the hosts
file.
If an Ethernet error message appears when the tuning script is run, you may be
using a connection to the Ethernet controller other than the thick cable connection
(10Base-5) assumed to be the default. To reconfigure the controller for the type of
connector being used, refer to “Reconfiguring Your System” in the U6000 Series
UNE6000-ETH Ethernet Controller Installation Guide.
The tuning scripts diskette contains a tuning script that you install and run to complete
installation and configuration of the UNIX operating system. To install and run that
script, take the following steps:
1. If you are not already logged on, log on as root (superuser) (see 6.4).
2. Insert the tuning scripts diskette into the disk drive and enter the following
command to install and execute the tuning script:
# pkgadd -d diskette1 cptune
7848 4078–004 6–3

Installing SPO/HMP Console and Related Software
6–4
Messages appear prompting you to enter commands to change directories and start
the tuning script:
ClearPath tuning and configuration script . . .
Please enter the following commands to complete the ClearPath tuning.
cd /var/sadm/pkg/cptune/install
sh CP_tune
Installation of (CPtune) was successful
3. As indicated in the message, enter the cd and sh commands as follows:
# cd /var/sadm/pkg/cptune/install
# sh CP_tune
4. Remove the tuning script diskette from the drive unit. A prompt asks whether the
operating system was installed by you or at the factory.
Using the CP_tune script on the SMP5400 (SPO_Server)
If you installed the UNIX OS, you have already
configured it. If the OS was installed at the
factory, you need to customize it for your site.
Did you install the UNIX OS? [Y/n]: N
Note: If you installed the UNIX operating system, use the procedure in 6.9. Do
not use this procedure.
5. Enter no (N) to indicate that you did not install the UNIX operating system (it was
preinstalled). The tuning script begins operation and a prompting message appears
asking for the time zone for the site.
Timezone Selection
––––––––––––––––––
1) Greenwich Meantime (GMT) 9) Alaskan, USA (AST)
2) Atlantic, Canada (AST) 10) Hawaiian, USA (HST)
3) Eastern, USA (EST) 11) Eastern European (EST)
4) Central, USA (CST) 12) Middle European (MET)
5) Mountain, USA (MST) 13) Western European (WET)
6) Pacific, USA (PST) 14) Indian (IST)
7) Yukon, Canada (YST) 15) New Zealand (NZST)
8) Bering, USA (BST) 16) Japanese (JST)
Please select by option number: [1]: x
6. Select the appropriate time zone. A prompt asks whether daylight saving time is
applicable to your time zone selection.
Is daylight saving time observed in your locale? [Y/n]:
7. Enter yes (Y) if you want to have daylight saving time support. Enter no (N) if you
do not wish to have that support. A prompt asks you to confirm that the date and
time are correct.
7848 4078–004

Installing SPO/HMP Console and Related Software
Setting System Date and Time
––––––––––––––––––––––––––––
Current date is Tue Mar 5 18:23:25 MST 1996.
Is this correct? [Y/n]:
8. Enter yes (Y) if the date and time are correct. Enter no (N) to enter a new date and
time. You are prompted to set and confirm a default password used by several
users.
Setting Default System Passwords
––––––––––––––––––––––––––––––––
The password you are about to enter will be used for the following users:
– root (superuser)
– install
– bin
– dtadm
– mlsadmin
– sysadm
– makefsys
– checkfsys
– mountfsys
– unmountfsys
– setup
– powerdown
IMPORTANT: After installation you should assign unique passwords to these
users. Use the System Administration (OAM) menus or the passwd(1) command.
New Password: unisys1234
Re-enter new password: unisys1234
9. Enter unisys1234 (the default installation password). The password does not
appear on the screen as you type it. The site later changes the password during site
customization (the new password must be at least eight characters in length and
include at least two alphabetic characters and one numeric or special character).
You are asked to reenter the password to confirm it.
After entry of the password, you are prompted to enter a name for the SPO server
and confirm the selection (see Table 2–1 for the name of the SPO server).
Setting System and Node Names
–––––––––––––––––––––––––––––
Please enter a System Name for this system. This will set
the ”node” name and the ”system” name. This name will be
used for uucp(1) and networking. This name cannot be ”unix”,
an empty string (””) or more than 8 characters in length.
Please enter the System Name: xxxxx
The System Name chosen was ”xxxxx”
Is this correct? [Y/n]: y
7848 4078–004 6–5

Installing SPO/HMP Console and Related Software
6–6
After pressing Enter, you are prompted to establish your networking configuration.
Host Network Configuration Selection
––––––––––––––––––––––––––––––––––––
Your system is equipped with a Local Area Network controller.
You can either configure the basic networking configuration
during this installation, or you can configure them after the
system has been completely installed.
Do you wish to configure the Local Area Networking now? [Y/n]: Y
10. Enter yes (Y). You are prompted to enter the internet protocol (IP) address that
identifies the SPO server to your external Ethernet production LAN. You are asked
to confirm the address entered.
Internet Protocol (IP) Address Selection
––––––––––––––––––––––––––––––––––––––––
Please enter your local system IP Address. The IP Address is the
address by which your system will be known on the Internet.
These addresses must be administered by a central authority on
your network. IP Addresses are written as four decimal integers,
separated by decimal points and no spaces (e.g. 128.10.2.70).
Your system IP Address is? : xxx.xxx.xxx.xxx
Your system IP Address has been set to xxx.xxx.xxx.xxx
Is this correct? [Y/n]: Y
Note: IP addresses must be administered by a central administrator at the site.
11. Enter the IP address from Table 2–1 that identifies the SPO server. You are
prompted to confirm or change the calculated Netmask value.
Internet Protocol Netmask Selection
–––––––––––––––––––––––––––––––––––
Your local system Netmask is set to : xxx.xxx.xxx.xxx
You can either use this value, calculated from your system
IP Address, or you can enter a new value if you use
subnet addressing and wish to overide it.
Please select a new Netmask value or press enter to use the
calculated default: [ xxx.xxx.xxx.xxx ]
12. Press Enter to accept the calculated network value, or change the value if necessary.
You are prompted to confirm that it is correct.
Your local system Netmask has been set to xxx.xxx.xxx.xxx
Is this correct? [Y/n]: y
7848 4078–004

Installing SPO/HMP Console and Related Software
13. Enter yes (Y) to confirm that the value is correct. You are asked whether you want
to establish a gateway service.
Default Gateway System Selection
––––––––––––––––––––––––––––––––
You can select a system to provide a Gateway service between
your local subnet and any backbone networks on your site.
This is sometimes the Internet Address of another computer acting
as a Gateway, or more often the Internet Address of a dedicated
standalone Router system.
Do you wish to provide an IP Address for a Gateway? [y/N]:
14. The default is no (N). If you enter yes (Y) you are prompted to enter and then
confirm the IP address for the gateway.
You then must identify a Domain Name Service (DNS) host if any.
Note: The term “Directory Name Services” used in the prompt for DNS host
information is incorrect.
Directory Name Services (DNS) Host Selection
––––––––––––––––––––––––––––––––––––––––––––
You can elect to use Directory Name Services (DNS) host or a
statically configured /etc/hosts file for resolving
system names to Internet Addresses. If you choose to use a DNS
host, then you will be prompted for the Internet Address of the
DNS server systems on your network. The DNS host chosen here is
the Primary DNS host. Further hosts can be configured in the
/etc/resolv.conf file after installation.
Do you wish to use a DNS host? [y/N]:
15. The default is no (N). If you enter yes (Y) you are prompted to enter and then
confirm the IP address for the DNS host. You then are prompted to enter a network
domain name to identify the local network.
Network Domain Name Selection
–––––––––––––––––––––––––––––
Please enter a Network Domain Name for this system. This will
be used by the Domain Name Services as a name suffix for
system names that do not include a period (.) character
in them.
This name will also be used to identify the local network
in the /etc/networks database file.
The name slc.unisys.com would be a suitable example of a valid
Domain Name.
Please enter the Domain Name: xxxxx
The Domain Name chosen was xxxxx
Is this correct? [Y/n]: Y
7848 4078–004 6–7

Installing SPO/HMP Console and Related Software
6–8
16. Enter the network domain name from Table 2–1. Following that entry, the tuning
script begins to create a hosts file to identify components the SPO server must
communicate with. The first prompt asks for the system name of the Windows NT
or UNIX node.
Make hosts file for SPO
–––––––––––––––––––––––
Please enter the System name of the U6000/SMP61000:
17. Enter the system name of the Windows NT or UNIX node from Table 2–1. You are
prompted to enter the IP address of that component.
Please enter the IP address of the U6000/SMP61000:
18. Enter the IP address of the Windows NT or UNIX node from Table 2–1. You are
prompted to enter the number of 2200 Series system consoles (SCF workstations)
you have.
For an IX4400 you may define up to 12 consoles.
For an IX4800 you may define up to 6 consoles.
How many 2200 Consoles do you have?
19. Enter the number of system consoles you have. You are prompted to enter the IP
address for each system console.
Please enter the IP address of the 1st 2200 Console:
Please enter the IP address of the 2nd 2200 Console:
Enter the address for each system console from Table 2–1. You are prompted to
enter information about your first X terminal.
20. Take the following steps to identify your X terminals (only one X terminal is
required):
a. After entering the last system console IP address, you are prompted to enter the
system name of the first X terminal.
Please enter the System name of the first X terminal:
b. Enter the system name of the first X terminal from Table 2–1.
You are prompted to enter the IP address.
Please enter the IP address of the first X terminal:
c. Enter the IP address of the first X terminal from Table 2–1.
You are asked whether you have another X terminal.
Do you have another X terminal?
7848 4078–004

Installing SPO/HMP Console and Related Software
d. Enter Y if you have another X terminal to identify. If you do not have another
X terminal to identify, enter N, and proceed to step 21. If you have another X
terminal to identify, enter Y and take these steps:
− You are prompted to enter the system name of the next X terminal. Enter
the system name from Table 2–1.
− You are prompted to enter the IP address of the next X terminal. Enter the
IP address from Table 2–1.
− You are asked whether or not you have another X terminal to identify. If you
have another X terminal, enter Y and repeat the above steps. If you do not,
enter N and proceed with step 21.
− Keep repeating the above steps until you can enter N and proceed with
step 21.
21. The entries you have made are listed and you are asked to confirm that they are
acceptable.
New lines for /etc/inet/hosts
–––––––––––––––––––––––––––––
These lines will be added to /etc/inet/hosts:
ip–address node–name CP_UNIX
ip–address cp_cons01
ip–address cp_cons02
.
.
ip–address node–name cp_xterm
Is this correct? [Y/n]: y
Note: The default host names from Table 2–1 are automatically supplied as aliases.
22. Enter yes (Y) if they are acceptable, or no (N) if you wish to reenter information.
Upon entering yes, the new information is added to the /etc/inet/hosts file.
You then are prompted to save the information on diskette for copying to the system
consoles.
Adding ip–address SMP61000node–name to /etc/inet/hosts
Adding ip–address cp_cons01 to /etc/inet/hosts
Adding ip–address cp_cons02 to /etc/inet/hosts
Adding ip–address xterm–node–name to /etc/inet/hosts
Adding SMP61000–node–name root to rhosts file.
Do you want to copy the hosts file to diskette for the 2200 consoles? Y
7848 4078–004 6–9

Installing SPO/HMP Console and Related Software
6–10
23. Enter yes (Y) to save the information on diskette. You are prompted to put a floppy
diskette into the drive unit. Insert the blank diskette you formatted earlier and press
Enter.
Put diskette into drive and press RETURN:
Updating /etc/inet/inetd.conf ...done
****************************************************
The system must be rebooted to load the new kernel.
****************************************************
Finished running the ClearPath tuning script.
Press return to shutdown and reboot.
When the script is done, you are prompted to shut down and reboot the SPO server.
24. Remove the diskette (which now contains the hosts file information) from the drive
unit, and press Enter to reboot the SPO server.
When the reboot is done, copy the hosts file saved on diskette to the 2200 node consoles
as described in 6.10.
7848 4078–004

Installing SPO/HMP Console and Related Software
6.3. Installing UNIX on the SPO Server
If you are required to install the UNIX operating system, enter the information shown in
Table 6–1 in response to disk slicing prompting messages (6.3).
Note: With UNIX installed on the Intel node, the multiport I/O board required to
make a direct serial connection between the SPO server and the UNIX node
must be jumpered for the default value (340H). If SPO/ESE is connected, the
multiport I/O board is not used (see 6.7).
Table 6–1. Boot Disk Configuration Values
Slice Size Type Blocksize Mount Point Comments
1 583 MB ufs 4 KB /
2 12 MB bfs (selected
automatically)
3 128 MB raw (selected
automatically)
Not
prompted
Not
prompted
/stand /stand accommodates
large UNIX kernels and a
backup kernel.
Not prompted
(/dev/swap by
default)
/dev/swap is sized to
twice the size of
configured memory
(128 MB).
4 200 MB ufs 4 KB /var A large /var file system
is created to hold
default SPO/HMP
Console data
directories.
5 200 MB ufs 4 KB /opt /opt takes 200 MB to
further offload root,
which should be
adequate for SPO/HMP
Console software and
documentation.
6 Remaining
space
ufs 4 KB /var/opt/spo/
SPO_Log
Having the logging
directory in a separate
partition allows full use
of the Log threshold
feature.
7848 4078–004 6–11

Installing SPO/HMP Console and Related Software
6–12
Take the following steps to install the UNIX operating system software on the SPO
server:
Notes:
Cautions
This procedure is a destructive installation procedure. Make sure you have
read and understand the procedure before proceeding.
During the procedure, be sure the CAPS LOCK key on the keyboard does not
become locked in the uppercase position while making entries. Use the SHIFT
key if you want to enter an uppercase password.
Switch the monitor concentrator to the SPO Server position before beginning
(see 3.1)
Ignore any error messages for invalid disk header that may appear before the
prompt to insert installation media.
Use default responses unless otherwise noted.
1. With the system powered off, insert the boot diskette into the drive unit.
2. Power the system on. Messages indicate that boot information is being loaded off
the diskette (takes about 10 minutes):
Note: Ignore the message for pressing to go to the SCSI select utility
and a following message about SCSI BIOS not installed.
UNISYS U6000 Series: SVR4/MP-HA boot loader ...
Booting the UNIX System ... uncompressing and loading kernel ...
You are prompted to insert the installation media:
NOTICE: Please insert the correct installation TAPE or CD-ROM ...
Install the tape or CD-ROM (labeled “U6000 Series UNIX System V Release 4.0
Software”) in the drive unit. An informative message then appears indicating that
the tape or CD-ROM is being selected.
Note: If you have more than one drive unit and the CD-ROM is not detected in
the current unit, move it to the other unit.
Selecting TAPE or CD-ROM installation ...
7848 4078–004

Installing SPO/HMP Console and Related Software
That message is followed by a prompt asking if you have a color monitor.
UNISYS SVR4/MP–HA Installation, Console Monitor Type Selection
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
_________________________________________
| | | | |
|_________|_______|__________|___________|
Do you see colors in the box drawn above? [Y/n]: Y
3. Enter yes (Y) to indicate that you see colors. You are prompted to confirm the entry.
You appear to have a “COLOR” monitor.
Is this correct? [Y/n] Y
4. Enter yes (Y) to confirm that you have a color monitor. A welcome message
appears.
WELCOME TO THE UNISYS U6000(tm) SERIES
––––––––––––––––––––––––––––––––––––––
This is the Installation and Maintenance Interface
for the UNISYS UNIX(tm) SVR4/MP–HA
(Multi–Processor / High Availability) O/S.
Press Control–C at any time to cancel
and restart the Operating System installation.
Copyright (C) 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996 UNISYS Corp.
Copyright (C) 1995 Novell Inc.
Copyright (C) 1990, 1991, 1992 UNIX System Laboratories, Inc.
Copyright (C) 1984, 1986, 1987, 1988, 1989 AT&T.
Copyright (C) 1987, 1988 Microsoft Corp.
All Rights Reserved.
Press RETURN to continue or ? for help:
Note: As indicated by the welcome message, you can press CTRL-C to abort the
boot at any time that media is not being loaded.
7848 4078–004 6–13

Installing SPO/HMP Console and Related Software
6–14
5. Press Enter, to continue. You are prompted to select a keyboard type and confirm
the selection.
Keyboard Type Selection
–––––––––––––––––––––––
1) American (English/ASCII) 10) Latin–American
2) Belgian 11) Norwegian
3) Canadian (English) 12) Portuguese
4) Canadian (French) 13) Spanish
5) Danish 14) Swedish
6) Dutch 15) Swiss (German)
7) French 16) Swiss (French)
8) German 17) United Kingdom
9) Italian
Please select by option number: [1]: x
You have selected a xxxxxx keyboard.
Note the selection of the wrong keyboard may result
in difficulty answering etc
Is this correct? [Y/n]
6. Enter the number of the keyboard type you wish to use. After selecting a keyboard
type, you are asked if you have run the system configuration utility (SCU) and
whether you want to terminate this installation procedure.
System Configuration and Preparation
––––––––––––––––––––––––––––––––––––
If you have not configured this system with the System
Configuration Utility (SCU), you should do so at this
time. This installation will not proceed correctly
unless the SCU utility has been run (and the system
suitably configured).
If this is a system with an existing software
installation, it should be fully backed–up and archived
before continuing with this installation.
Do you wish to terminate this installation? [y/N]: N
7. Enter no (N). The SCU already has been run for all cards installed at the factory.
You need to run SCU again only if you add a hardware feature or change the
hardware configuration.
A message appears asking whether this is a new installation or a system upgrade:
Installation and Maintenance Selection
––––––––––––––––––––––––––––––––––––––
1) New Installation (This will erase ALL disk contents!)
2) 1.2(.X) or 1.3(.X) System Upgrade
3) Help
Please select by option number: [1]: 1
7848 4078–004

Installing SPO/HMP Console and Related Software
8. Enter 1 to select New Installation. You are asked to identify the type of installation.
Installation Options Selection
––––––––––––––––––––––––––––––
1) Easy Installation
2) Configurable Installation
3) Help
4) Return to Main Menu
Please select by option number: [1]: 1
9. Enter 1 to select Easy Installation. You are prompted to enter the time zone for the
site.
Timezone Selection
––––––––––––––––––
1) Greenwich Meantime (GMT) 9) Alaskan, USA (AST)
2) Atlantic, Canada (AST) 10) Hawaiian, USA (HST)
3) Eastern, USA (EST) 11) Eastern European (EST)
4) Central, USA (CST) 12) Middle European (MET)
5) Mountain, USA (MST) 13) Western European (WET)
6) Pacific, USA (PST) 14) Indian (IST)
7) Yukon, Canada (YST) 15) New Zealand (NZST)
8) Bering, USA (BST) 16) Japanese (JST)
Please select by option number: [1]: x
10. Select the appropriate time zone. A prompt asks whether daylight saving time is
applicable to your time zone selection.
Is daylight saving time observed in your locale? [Y/n]:
Note: The daylight saving time prompt does not appear if Greenwich Meantime
is selected.
11. Enter yes (Y) if you want to have daylight saving time support. Enter no (N) if you
do not wish to have that support. A prompt asks you to confirm that the date and
time are correct.
Setting System Date and Time
––––––––––––––––––––––––––––
Current date is Tue Mar 5 18:23:25 MST 1996.
Is this correct? [Y/n]:
7848 4078–004 6–15

Installing SPO/HMP Console and Related Software
6–16
12. Enter yes (Y) if the date and time are correct. Enter no (N) to enter a new date and
time. You are prompted to set and confirm a default password that will be used by
several users.
Setting Default System Passwords
––––––––––––––––––––––––––––––––
The password you are about to enter will be used for the following users:
– root (superuser)
– install
– bin
– dtadm
– mlsadmin
– sysadm
– makefsys
– checkfsys
– mountfsys
– unmountfsys
– setup
– powerdown
IMPORTANT: After installation you should assign unique passwords to these
users. Use the System Administration (OAM) menus or the passwd(1) command.
New Password: unisys1234
Re-enter new password: unisys1234
13. Enter unisys1234 (the default installation password). The password does not
appear on the screen as you type it. The site later changes the password during site
customization (the new password must be at least eight-characters in length and
include at least two alphabetic characters and one numeric or special character).
You are asked to reenter the password to confirm it.
After entry of the password, you are prompted to enter a name for the SPO server
and confirm the selection.
Setting System and Node Names
–––––––––––––––––––––––––––––
Please enter a System Name for this system. This will set
the ”node” name and the ”system” name. This name will be
used for uucp(1) and networking. This name cannot be ”unix”,
an empty string (””) or more than 8 characters in length.
Please enter the System Name: xxxxx
The System Name chosen was ”xxxxx”
Is this correct? [Y/n]: y
7848 4078–004

Installing SPO/HMP Console and Related Software
14. Enter the SPO server name from Table 2–1, determined by your site, and confirm
that it is correct. You are prompted to configure enhanced reliability, availability,
and serviceability (RAS) features.
RAS Features Determination
––––––––––––––––––––––––––
The system can be configured to take advantage of many enhanced
Reliability, Availability and Serviceability features during
installation.
These features include Disk Mirroring, Spanning, Striping and
RAID5 operation, enhanced error logging and event handling and
media archiving.
If not configured at installation time, these features may be
configured at a later time.
Do you wish to configure the enhanced RAS features? [y/N]: N
15. Enter no (N). Do not configure the RAS features at this time. You are asked if you
want to manually configure the boot disk.
Disk Configuration Options
––––––––––––––––––––––––––
This installation can be performed using a default boot disk
partitioning scheme, such that the disk layout will be dependent
upon the boot disk size and type. Optionally the boot disk can
be manually configured for an optimal disk layout.
Do you wish to manually configure the system boot disk? [y/N]: Y
16. Enter yes (Y) (not the default) to manually configure the boot disk. You configure
disk drive 0 according to the required values given in Table 6–1. The system
suggests a configuration and asks whether you want to change the layout.
Notes:
Ignore disk partitioning recommendations provided by prompting messages.
See Table 6–1 for values to enter for each slice.
The partitioning assumes a 2.0-gigabyte (GB) disk was used.
Disk Layout Selection
–––––––––––––––––––––
This is disk drive #0 (Size: xxxxxMB, Type: UST32).
Currently, this disk will be partitioned according to the
following layout:
Slice # Size (MB) FS Type Block Size Mount Point
––––––– ––––––––– ––––––– –––––––––– –––––––––––
1 200 ufs 4k /
2 17 bfs –– /stand
3 65 –––– –– /dev/swap
4 439 ufs 4k /home
5 439 ufs 4k /home1
6 439 ufs 4k /home2
7 438 ufs 4k /home3
Do you want to change the layout of disk drive #0? [Y/n]: Y
7848 4078–004 6–17

Installing SPO/HMP Console and Related Software
6–18
17. Enter yes (Y). You are requested to enter the number of disk partitions (slices) to
make.
How many slices should be created on disk drive #0? [3-15]: 6
18. Enter 6 as the number of slices to make. Information about disk partitioning is
presented.
Note: The values displayed may be different from those shown. Ignore
recommendations displayed in prompts, you must enter values as
specified in Table 6–1.
Disk #0 Partition Sizing Information
––––––––––––––––––––––––––––––––––––
Slice #1 on the root disk must be at least 100MB. If the disk is
large enough 200MB is recommended for a full installation,
Slice #2 on the root disk is reserved for swap and must be at
least 12 MB. Recommended size for swap space is at least
the size of main memory.
Slice #3 on the root disk is reserved for the boot file system
and must be at least 8 MB.
Press Return to continue
Disk 0, 2037MB (of 2037MB) remaining.
Select the size (MB) for slice #1 (200 for “/”): 583
19. After pressing Enter to continue, enter 583 for the size of slice 1. You are prompted
to select the file system type:
Select file system type for slice #1.
1) UNIX Fast File System (ufs)
2) UNISYS Bitmapped System V File System (s5bm)
3) Standard AT&T System V File System (s5)
4) Veritas File System (vxfs)
5) No File System (raw)
6) Secondary Swap Area (swap)
Please select by option number: [1]: 1
20. Enter 1 to select the UNIX Fast File System (UFS). You are prompted to enter the
block size for the file system:
Select block size for file system type ufs on slice #1.
1) Block Size 4KB
2) Block Size 8KB
Please select by option number: [1]: 1
21. Enter 1 to select a block size of 4 KB. You then are prompted for information about
slice 2 and the remaining slices. Enter the information as described in Table 6–1.
7848 4078–004

Installing SPO/HMP Console and Related Software
Note: Slices 2 and 3 ask only for the slice size. Slices 4, 5, and 6 ask for slice
size, file system type, block size, and mount point (refer to Table 6–1).
A message appears confirming the disk layout and asking if you want to change it.
Disk Layout Selection
–––––––––––––––––––––
This is disk drive #0 (Size: xxxxxMB, Type: UST31).
Currently, this disk will be partitioned according to the
following layout:
Slice # Size (MB) FS Type Block Size Mount Point
––––––– ––––––––– ––––––– –––––––––– –––––––––––
1 583 ufs 4k /
2 12 bfs –– /stand
3 128 –– –– /dev/swap
4 200 ufs 4k /var
5 200 ufs 4k /opt
6 xxx ufs 4k /var/opt/spo/SPO_Log
Do you want to further change the layout of disk drive #0? [Y/n]: N
22. Enter no (N) to indicate that you do not want to change the layout. A message then
asks if you want to format the disk.
Caution
The disk drive was formatted at the factory. To prevent wasted time, do not
format the disk drive at this time.
Do you want to format disk drive #0? [y/N]: N
23. Enter no (N); the drive is already formatted. Next, you are asked whether you want
to install the Graphical Desktop Metaphor package (gdmusr).
Graphical Desktop Metaphor (GDM), X Server Configuration
––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Your system is equipped with a VGA capable (or better) graphics
controller.
You can automatically install gdmusr etc.
Do you wish to automatically install the gdmusr package? [Y/n]: Y
24. Enter yes (Y). A message describes the network driver configuration.
Configuration Of The Network Adapter Drivers
––––––––––––––––––––––––––––––––––––––––––––
Configuring the i596 Ethernet device driver for the
UN6000/UNE6000/PCC500-ETH 16/32-bit ISA/EISA Ethernet Controller(s).
Adapter 1 type: UNE6000-ETH
IRQ: n
Press RETURN to continue:
7848 4078–004 6–19

Installing SPO/HMP Console and Related Software
6–20
After pressing Enter, you are prompted to establish your networking configuration.
Host Network Configuration Selection
––––––––––––––––––––––––––––––––––––
Your system is equipped with a Local Area Network controller.
You can either configure the basic networking configuration
during this installation, or you can configure them after the
system has been completely installed.
Do you wish to configure the Local Area Networking now? [Y/n]: Y
25. Enter yes (Y). You are prompted to enter the internet protocol (IP) address that
identifies the SPO server to your external Ethernet production LAN. You are asked
to confirm the address entered.
Internet Protocol (IP) Address Selection
––––––––––––––––––––––––––––––––––––––––
Please enter your local system IP Address. The IP Address is the
address by which your system will be known on the Internet.
These addresses must be administered by a central authority on
your network. IP Addresses are written as four decimal integers,
separated by decimal points and no spaces (e.g. 128.10.2.70).
Your system IP Address is? : xxx.xxx.xxx.xxx
Your system IP Address has been set to xxx.xxx.xxx.xxx
Is this correct? [Y/n]: Y
Note: IP addresses must be administered by a central administrator at the site.
26. Enter the IP address from Table 2–1 that identifies the SPO server. You are
prompted to confirm or change the calculated Netmask value.
Internet Protocol Netmask Selection
–––––––––––––––––––––––––––––––––––
Your local system Netmask is set to : xxx.xxx.xxx.xxx
You can either use this value, calculated from your system
IP Address, or you can enter a new value if you use
subnet addressing and wish to overide it.
Please select a new Netmask value or press enter to use the
calculated default: [ xxx.xxx.xxx.xxx ]
27. Press Enter to accept the calculated network value, or change the value if necessary.
You are prompted to confirm that it is correct.
Your local system Netmask has been set to xxx.xxx.xxx.xxx
Is this correct? [Y/n]: y
7848 4078–004

Installing SPO/HMP Console and Related Software
28. Enter yes (Y) to confirm that the value is correct. You are asked whether you want
to establish a gateway service.
Default Gateway System Selection
––––––––––––––––––––––––––––––––
You can select a system to provide a Gateway service between
your local subnet and any backbone networks on your site.
This is sometimes the Internet Address of another computer acting
as a Gateway, or more often the Internet Address of a dedicated
standalone Router system.
Do you wish to provide an IP Address for a Gateway? [y/N]:
29. The default is no (N). If you enter yes (Y) you are prompted to enter and then
confirm the IP address for the gateway.
You then are prompted to enter a network domain name to identify the local
network.
Network Domain Name Selection
–––––––––––––––––––––––––––––
Please enter a Network Domain Name for this system. This will
be used by the Domain Name Services as a name suffix for
system names that do not include a period (.) character
in them.
This name will also be used to identify the local network
in the /etc/networks database file.
The name slc.unisys.com would be a suitable example of a valid
Domain Name.
Please enter the Domain Name: xxxxx
The Domain Name chosen was xxxxx
Is this correct? [Y/n]: Y
30. Enter the network domain name from Table 2–1 and confirm your choice. You then
must identify a Domain Name Service (DNS) host if any.
Note: The term “Directory Name Services” used in the prompt for DNS host
information is incorrect.
Directory Name Services (DNS) Host Selection
––––––––––––––––––––––––––––––––––––––––––––
You can elect to use Directory Name Services (DNS) host or a
statically configured /etc/hosts file for resolving
system names to Internet Addresses. If you choose to use a DNS
host, then you will be prompted for the Internet Address of the
DNS server systems on your network. The DNS host chosen here is
the Primary DNS host. Further hosts can be configured in the
/etc/resolv.conf file after installation.
Do you wish to use a DNS host? [y/N]:
7848 4078–004 6–21

Installing SPO/HMP Console and Related Software
6–22
31. The default is no (N). If you answer yes (Y), you are prompted to enter and then
confirm the IP address of the DNS host (from Table 2–1). Following that entry, the
networking values you entered are stored in the system.
You are now prompted whether to continue or start over. There is no default answer
to this question.
System Installation Confirmation
––––––––––––––––––––––––––––––––
The installation of the UNIX System V Release 4/MP Operating
System will now begin. It will take about an hour to complete.
A negative answer to this question will terminate the
installation procedure.
Do you want to proceed? [y/n]: Y
32. Enter yes (Y) to continue. The installation program now repartitions the disk and
installs the UNIX operating system in the configuration you have defined.
Notes:
The complete installation may take up to 1 hour, depending on your system
configuration. Messages appear during the installation that contain
information about the operating system release.
Messages resulting from operating system installation are captured in a log
file, (/var/sadm/install/logs/INSTPKG.log).
When installation is complete, the following message appears:
System Reboot
–––––––––––––
Please remove all CD–ROMs, tapes and diskettes from their
respective devices.
Press RETURN to reboot:
33. Remove the installation media and press Enter to reboot the system. The console
login prompt appears following the reboot.
Console Login:
34. Log on as superuser (6.4) and install operating system patches (6.5).
7848 4078–004

6.4. Logging On as the Superuser
Installing SPO/HMP Console and Related Software
Caution
To prevent unauthorized access to the SPO server following initial installation, the
site must change the default password (unisys1234) to a different password.
Several installation and configuration procedures require you to log on as root
(superuser). Do that as follows:
Notes:
If the root prompt (#) is showing, you already are logged on as superuser.
If the screen saver is running, press any key to stop it.
1. Upon power on or reboot of the SPO server, the console login prompt appears as
follows:
Console Login: mlsadmin
2. Enter mlsadmin in response. You are prompted to enter a password:
Password: unisys1234
3. Enter unisys1234 (the default installation password). The UNIX shell prompt ($)
appears as follows:
$
At this point, you can begin using the UNIX operating system. To complete
installation of the remaining SPO/HMP software, you must log in as superuser.
4. Enter the su command to log in as superuser. You are prompted to enter a
password:
Password: unisys1234
5. Enter unisys1234 (the same password you used for mlsadmin). The UNIX root
prompt (#) appears.
#
Once the UNIX root prompt (#) appears, you can install UNIX operating system
patches (6.5) and SPO/HMP Console related software (6.6 through 6.9).
7848 4078–004 6–23

Installing SPO/HMP Console and Related Software
6.5. Installing UNIX Operating System Patches
6–24
Take the following steps to install the UNIX operating system patches:
1. Insert the tape containing the UNIX operating system patches (labeled “SPO Server
OS 1.4 Patches”) in the drive unit.
2. If you are not already logged on, log on as root (superuser) (see 6.4).
3. Enter the following commands:
# mkdir -p patchdir
# cd patchdir
# cpio -icumvd < device
where:
patchdir is the name of the directory in which to install patches.
device is /dev/rmt0 if the tape drive is the first configured tape device;
otherwise, enter the correct device (or different device if installing patches from
a different media)
4. Reboot to single-user mode by entering the following command:
init s
Note: You also could change to the root directory, then enter the following
command to reboot: shutdown -is -g0 -y
The following message appears after the reboot:
Type Ctrl-d to proceed with normal startup,
(or give the root password for system maint)!
5. Type unisys1234 then press Enter to log on.
6. Enter the following commands to kill remaining processes, mount all file systems,
and change to the patch directory:
# killall
# mountall
# cd patchdir
7. Enter the following command to install the patches:
# ./install.sh
The following message appears:
Do you want to install patch xxxxxx (default: Y) [Y,n,?,q]
7848 4078–004

Installing SPO/HMP Console and Related Software
8. Enter yes (Y), then enter the following command to build the new kernel:
# /etc/conf/bin/idbuild
9. Change to the root directory and reboot by entering the following commands:
# cd ..
# shutdown -i6 -g0 -y
Note: You can also enter an init 6 command to reboot.
10. Remove the tape from the drive unit.
6.6. Installing X Terminal Software (Done at SPO
Server)
Take the following steps to install the LT501 X terminal software on the SPO server:
1. If you are not already logged on, log on as root (superuser) (see 6.4).
2. Put the LT501 X terminal software tape (labeled “LT500-SW”) in the tape drive and
enter the following commands:
# cd /tmp
# tar -xvf /dev/rmt/c0d0 install
A message similar to the following appears:
x install, 44351 bytes, 87 tape blocks
About 10 minutes elapse before the pound sign (#) prompt reappears.
Caution
Do not remove the tape media until the last step of this procedure (when the
“Installation of the software is completed” message appears). Information from
the tape is needed until that point.
7848 4078–004 6–25

Installing SPO/HMP Console and Related Software
6–26
3. Enter the following install command:
# ./install
You see a list of available packages, followed by a prompt:
Welcome to the Unisys X Terminal Installation Program
Portions of this tape are Copyright 1990, 1991, 1992, 1993, and 1994
by Link Technologies and Unisys
The following are available on this tape:
1) Server images.
2) A complete set of compiled X fonts. (9.3MB)
3) Sample configuration files. (70KB)
4) Utility binaries for DECstations (DEC Mips / Ultrix) (1.6MB)
5) Utility binaries for IBM RS–6000s (AIX 3.X) (1.3MB)
6) Utility binaries for Sun–4s (sparc / SunOS 4.X) (1.9MB)
7) Utility binaries for PCs running SCO UNIX/Open Desktop (880KB)
8) Host utility shell scripts. (70KB)
9) UNIX–style man pages for the utilities. (520KB)
10) Source code for the utilities. (790KB)
11) XDM support (Sun 3 & Sun 4 only) (710KB)
You may install any or all of these items. At the next prompt, type
in a list of the numbers corresponding to the ones you want to install,
separated by spaces. If you want everything, just press RETURN.
Which should I install? [all] 1 2 3 8 9 10
4. Enter the following numbers separated by spaces: 1 2 3 8 9 10. That installs the
following: server images (1), compiled X fonts (2), sample configuration file (3), host
utility shell scripts (8), man pages (9), and source code for utilities (10).
Messages appear asking which server to install.
The following X servers are available on this tape:
Small Servers without Dynamic Downloadable Clients (for 4Meg systems):
1) Small Monochrome, with built–in Window Manager (arxM) (2.6MB)
2) Small Monochrome, without built–in Window Mgr (arxM–NLC) (1.8MB)
3) Small Color, with built–in Window Manager (arxC) (2.8MB)
4) Small Color, without built–in Window Manager (arxC–NLC) (2MB)
X Servers with Dynamic Downloadable Clients (for >4Meg systems):
5) Monochrome, with Dynamic Down–loading of Local Clients (arxM–dy)(2MB)
6) Color, with Dynamic Down–loading of Local Clients (arxC–dy) (2.2MB)
7) Color, with ALL Local Clients & XIE support built–in (arxC–xie)
(6.2MB)
Automatically loaded with Dynamically Down–loading Servers:
Dynamic Binaries (dy–bin directory) (1.7MB)
Dynamic Libraries (dy–libs directory) (3.8MB)
Help Files (help directory) (20KB)
Local Client Config File (lc–config) (10KB)
You may choose any or all of these items. At the next prompt, type in a
list of the numbers corresponding to the ones you want to install,
separated by spaces. If you want all of them, just press RETURN.
Which servers should I install? [all] 7
7848 4078–004

Installing SPO/HMP Console and Related Software
5. Enter 6 to specify color with dynamic down-loading of local clients (arxC-dy).
Messages appear indicating destination directories.
Determining available disk space... done.
Checking destinations............done
These are the destinations for the selected items:
1) Server images. /tftpboot
2) A complete set of compiled X fonts. /usr/lib/X11/unisys
3) Sample configuration files. /usr/local/unisys
8) Host utility shell scripts. /usr/local/unisys
9) UNIX–style man pages for the utilities. /usr/local/unisys
10) Source code for the utilities. /usr/local/unisys
Continue i)nstallation or c)hange a destination? [i] i
6. Enter i (installation) to continue without changing the defaults. You are prompted
to identify the directory into which the X terminal software was copied.
I need the name of the tape device (or tar image file) that the X
installation tape is mounted on. This is the same device (file) you
used in the tar command that extracted this installation script.
IMPORTANT! Most systems have two versions of the tape device – one that
automatically rewinds the tape, and another that leaves the tape at the
end of the last file read. Since there is no standardized way of
rewinding a tape on UNIX systems, this script assumes that you are
supplying the scripts tape device automatic rewind device.
If you supply the no–rewind device, the script will fail to work.
For example, on Sun Sparc systems you should use the
device /dev/rst8, and NOT /dev/nrst8.
Here is a list of likely devices to use for various systems:
Unisys System V R 4 /dev/rmt/c0d0
Wyse UNIX v3.2 /dev/rct0
Wyse UNIX v4.0 /dev/rmt/c0s0
SUN Sparcstation /dev/rst8
DEC 3100 with Ultrix /dev/rmt0a
SCO Unix /dev/rct0
Which device should I use? [/dev/rmt/c0d0]
7. Press Enter to accept the default device used for Unisys System VR4
(/dev/rmt/c0d0).
Extracting files from /dev/rmt/c0d0. Please be patient.
(there is a delay of about 10 minutes here)
images loaded.
fonts loaded.
examples loaded.
util loaded.
man loaded.
src loaded.
Moving items to their destinations this will take approximately 3 minutes
more...done.
Cleaning up...
Installation of the software is completed.
7848 4078–004 6–27

Installing SPO/HMP Console and Related Software
6–28
8. Remove the tape from the drive unit.
Proceed with installation of the multiport card driver (6.7) if you have UNIX installed on
the Intel node. Otherwise, install the SPO/HMP Console software (6.8).
Note: See 11.3.1 for information about creating an X terminal configuration file.
6.7. Installing the Multiport Card Driver
If UNIX is installed on the Intel node, the UNIX node is directly connected to a serial
port in a multiport I/O board in the SPO server (see Figure 6–1) unless the Intel node will
be connected to an existing SPO/ESE system.
Figure 6–1. Possible Connections to the SPO/HMP Server
7848 4078–004

Installing SPO/HMP Console and Related Software
Note: Switch the monitor concentrator to the SPO server position.
Install the driver software for the multiport card using the following procedure:
1. If you are not already logged on, log on as root (superuser) (see 6.4).
2. Insert the diskette containing the EISA driver software (labeled “US6000-ACD”) into
the drive unit.
3. Enter the following pkgadd command:
# pkgadd -d diskette1 eqn
A prompt to insert the diskette appears:
Insert diskette into Floppy Drive 1.
Type [go] when ready,
or [q] to quit: go
4. Enter go. Several informational messages appear followed by a prompt to enable a
high baud rate selection.
Installation in progress. Do not remove the diskette.
(more messages appear here).
==================================================================
EQUINOX SYSTEMS INC.
SSP Driver Installation
Unisys UNIX System V/386 SVR4
Copyright (c) 1994 Equinox Systems Inc. All Rights Reserved
==================================================================
(messages appear asking if Equinox boards are preconfigured by the SCU)
Continue with this package installation? Y
5. Enter yes (Y) to continue. A message appears indicating that the Equinox card was
detected.
1 Equinox boards found. Continue w/installation? Y
6. Enter yes (Y) to continue. After a few minutes, a message appears asking whether
you want to enable the high baud rate selection.
The high baud rates are selected according to the following table:
.
nnnn nnnn
nnn nnnnn
Enable high baud rate selection? (y/n) y
7. Enter yes (Y). Another set of messages appears relating to installation of default
port monitors and service.
Install the default set of port monitors and services? (y/n) y
7848 4078–004 6–29

Installing SPO/HMP Console and Related Software
6–30
8. Enter yes (Y) to install the default set of port monitors and services. Driver
installation is complete as indicated by the following message:
Installation of was successful.
9. Remove the diskette from the drive unit.
Proceed with installation of the SPO/HMP Console software (6.8).
6.8. Installing the SPO/HMP Console Software
This procedure describes how to install both the SPO/HMP Console software and the
Electronic Documentation software on the SPO server at the same time with a single
pkgadd command. The procedure is as follows:
1. Log on as superuser as described in 6.4. The pound sign (#) prompt appears
indicating that you are the root user.
#
2. Put the SPO/HMP Console software tape (labeled “SP Operation”) in the tape drive
of the SPO server and enter the following pkgadd command:
# pkgadd –d ctape1 all
A prompt to insert the tape appears:
Insert a tape into SCSI Fixed Block Tape Drive 1.
Type [go] when ready,
or [q] to quit: go
3. Insert the tape in the drive unit and enter go. Several informative messages appear
followed by queries. Respond to each query by pressing Enter to accept the default.
Caution
Do not remove the tape from the drive unit until the final step of this procedure
when the pound sign (#) prompt reappears.
Installation in progress. Do not remove cartridge tape.
Processing package instance from
SPO/HMP Console x.xCP
Version x.xCP (SVR4)
Using /opt/SPO as the package base directory
(there is a 10 minute delay while tape is loading)
Copyright 1996, Unisys Corporation
All rights reserved
7848 4078–004

UNISYS PROPRIETARY
Installing SPO/HMP Console and Related Software
This program(s) including the information
contained herein, is confidential and proprietary
to Unisys Corporation, and shall not be used or
reproduced for any purpose, except with written
consent/license of Unisys Corporation.
Where would you like SPO installed?
Enter an absolute pathname (default: /opt/SPO) [?,q]
4. Press Enter to accept the default absolute path name. Messages relating to logging
appear.
Single Point Operations Console has the ability to save traffic logs
of messages from various sources. These logs are automatically
stored in mass storage files under the path you specify.
Logs may consume considerable space depending upon the number of
message sources and your site’s rate of message traffic. You can
manage your site’s logging policy via Log Administration in Single
Point Operations Console.
Use the script ’movelogdir’ if you wish to change the location of
the log directory at some future time.
Where would you like to store your Single Point Operations Console
logs?
Enter an absolute pathname (default: /var/opt/spo/SPO_Log) [?,q]
5. Press Enter to accept the default absolute path name for the console logs.
A message asks where you would like to store site-dependent data.
Single Point Operations stores site dependent data in a separate
directory from where SPO is installed. You will have the option
of saving your data in the separate directory at SPO Console removal.
The default directory for storing SPO Console configurations, SP–AMS
databases, AMS databases used by RIU, URM scripts, Status files,
and help text used by Single Point Operations Console is
/var/opt/spo.
Where would you like to keep site dependent data for Single
Point Operations Console?
Enter an absolute pathname (default: /var/opt/spo) [?,q]
6. Press Enter to accept the default directory to contain the site-dependent SPO
configuration and database information. The following default login information is
configured automatically for you:
Administrator login name—spadmin
Group name—spo
Operator name—spoper
7848 4078–004 6–31

Installing SPO/HMP Console and Related Software
6–32
This is indicated by the following messages:
Single Point Operations Console requires an administrator log-in name for
the ownership of the installation files. The login name will also be
used as the default user name for the Supervisor class in the Single
Point Configuration routine when creating new configurations.
Your Single Point Operations administrator log-in name is “spadmin”
Single Point Operations Console requires a group name for the
installation files. All users of Single Point Operations Console
must be members of this group.
Your Single Point Operations group name is “spo”
Your Single Point Operations operator name is “spoper”
CONFIRMATION OF SPO CONSOLE INSTALLATION SETUP
Install SPO Console in directory: /opt/SPO
Store SPO Console logs in: /var/opt/spo/SPO_Log
Store all data for SPO Console in: /var/opt/spo
SPO Console administrator login name: spadmin
SPO Console group system name: spo
List of SPO Console operator login name(s):
SPO Console operator login name: spoper
Enter ”Yes” to Confirm All Entries or ”No” to Reject Any Entry
Yes or No (default: y) [y,n,?,q] y
7. Enter yes (Y) to confirm that the entries are correct. Several installation messages
appear.
The spadmin login name was added to the system ...
New password: unisys1234
Re-enter new password: unisys1234
8. Enter unisys1234 (the default installation password) for the administrator. The
following messages appear:
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
Installing Single Point Operations Console x.xCP as
## Executing preinstall script.
Single Point Operations Console added port names and service numbers
to /etc/services. The old port names and service numbers from
/etc/services are saved in /etc/services.old before any
modifications by Single Point Operations Console installation.
## Installing part 1 of nn.
[ verifying class ]
Modifying /etc/inet/services
[ verifying class
## Executing postinstall script.
(there is about a 10 minute wait here)
7848 4078–004

Installing SPO/HMP Console and Related Software
The messages end with a prompt to enter a password for the operator.
The “spoper” log-in name was added to the
system. The home directory of “spoper” is /home/spoper
New password: unisys1234
Re-enter new password: unisys1234
9. Enter unisys1234 (the default installation password) for the operator. After the
password is entered, the following messages appear:
You can use the SPO Configuration Routine to specify
a secondary SPO server for redundancy.
Installation of was successful.
Processing package instance from
SPO Electronic Documentation/ESE x.x
Version x.x (SVR4)
Using as the package base directory.
A 5-minute wait occurs. Then a prompt asks where you want SPO Electronic
Documentation installed.
Where would you like SPO Electronic Documentation installed?
Enter an absolute pathname (default: /opt/SPO–DOC) [?,q]
10. Press the Enter key to use the default (/opt/SPO–DOC). The system displays the
following messages:
Install SPO Electronic Documentation into /opt/SPO-DOC?
Yes or No (default: y) [y,n,?,q] y
The online documentation version is SPO x.x release.
11. Enter yes (Y). The system displays the following messages:
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
Installing SPO/ESE Electronic Documentation x.x as
## Installing part 1 of 1.
[ verifying class ]
## Executing postinstall script.
Installation of was successful.
(a brief delay occurs here while the tape is being rewound)
#
12. When the pound sign (#) prompt reappears, remove the tape from the drive unit.
13. Install and run the tuning script (6.9).
Note: Information Services (IS) software allows interactive services with the 2200
node. Because of the complexity of the configuration process, do not install
that software at this time.
7848 4078–004 6–33

Installing SPO/HMP Console and Related Software
6.9. Installing and Running the Tuning Script
(Site-Installed UNIX)
6–34
Notes:
Perform this procedure only if you installed the UNIX operating system and
entered site-specific information as described in 6.3. If the UNIX operating
system was preinstalled, install and run the tuning script as described in 6.2.
When you run the tuning script, you need a blank 3-1/2-inch floppy diskette (can
be either MS DOS or UNIX operating system format) on which to copy the hosts
file.
If an Ethernet error message appears when the tuning script is run, you may be
using a connection to the Ethernet controller other than the thick cable connection
(10Base-5) assumed to be the default. To reconfigure the controller for the type of
connector being used, refer to “Reconfiguring Your System” in the U6000 Series
UNE6000-ETH Ethernet Controller Installation Guide.
The tuning scripts diskette contains a tuning script that you install and run to complete
installation and configuration of the UNIX operating system. To install and run that
script, take the following steps:
1. If you are not already logged on, log on as root (superuser) (see 6.4).
2. Insert the tuning scripts diskette into the disk drive and enter the following
command to install and execute the tuning script:
# pkgadd -d diskette1 cptune
A prompt to insert the diskette appears:
Insert xxxxx into xxxxx drive. Type [go] when ready, or [q] to quit:
3. Type go and press Enter.
Messages appear prompting you to enter commands to change directories and start
the tuning script:
ClearPath tuning and configuration script . . .
Please enter the following commands to complete the ClearPath tuning.
cd /var/sadm/pkg/cptune/install
sh CP_tune
Installation of (CPtune) was successful
4. As indicated in the message, enter the cd and sh commands as follows:
# cd /var/sadm/pkg/cptune/install
# sh CP_tune
5. Remove the tuning script diskette from the drive unit. A prompt asks whether the
operating system was installed by you or at the factory.
7848 4078–004

Installing SPO/HMP Console and Related Software
Using the CP_tune script on the SMP5400 (SPO_Server)
If you installed the UNIX OS, you have already
configured it. If the OS was installed at the
factory, you need to customize it for your site.
Did you install the UNIX OS? [Y/n]: Y
Note: If you did not install the UNIX operating system, use the procedure in 6.2.
Do not use this procedure.
6. Enter yes (Y) to indicate you installed the UNIX operating system. The tuning script
begins operation and starts by creating a hosts file to identify components the SPO
server must communicate with. The first prompt asks for the system name of the
Windows NT or UNIX node (see Table 2–1).
Make hosts file for SPO
–––––––––––––––––––––––
Please enter the System name of the U6000/SMP61000:
7. Enter the system name of the Windows NT or UNIX node from Table 2–1. You are
prompted to enter the IP address of that component.
Please enter the IP address of the U6000/SMP61000:
8. Enter the IP address of the Windows NT or UNIX node from Table 2–1. You are
prompted to enter the number of 2200 Series system consoles (SCF workstations)
you have.
For an IX4400 you may define up to 12 consoles.
For an IX4800 you may define up to 6 consoles.
How many 2200 Consoles do you have?
9. Enter the number of system consoles you have. You are prompted to enter the IP
address for each system console.
Please enter the IP address of the 1st 2200 Console:
Please enter the IP address of the 2nd 2200 Console:
Enter the address for each system console from Table 2–1. You are prompted to
enter information about your first X terminal.
10. Take the following steps to identify your X terminals (only one X terminal is
required):
a. After entering the last system console IP address, you are prompted to enter the
system name of the first X terminal.
Please enter the System name of the first X terminal:
7848 4078–004 6–35

Installing SPO/HMP Console and Related Software
6–36
b. Enter the system name of the first X terminal from Table 2–1.
You are prompted to enter the IP address.
Please enter the IP address of the first X terminal:
c. Enter the IP address of the first X terminal from Table 2–1.
You are asked whether you have another X terminal.
Do you have another X terminal?
d. Enter Y if you have another X terminal to identify. If you do not have another
X terminal to identify, enter N, and proceed to step 21. If you have another X
terminal to identify, enter Y and take these steps:
− You are prompted to enter the system name of the next X terminal. Enter
the system name from Table 2–1.
− You are prompted to enter the IP address of the next X terminal. Enter the
IP address from Table 2–1.
− You are asked whether or not you have another X terminal to identify. If you
have another X terminal, enter Y and repeat the above steps. If you do not,
enter N and proceed with step 21.
− Keep repeating the above steps until you can enter N and proceed with
step 21.
11. The entries you have made are listed and you are asked to confirm that they are
acceptable.
New lines for /etc/inet/hosts
–––––––––––––––––––––––––––––
These lines will be added to /etc/inet/hosts:
ip–address node–name CP_UNIX
ip–address cp_cons01
ip–address cp_cons02
ip–address node–name cp_xterm
Is this correct? [Y/n]: y
12. Enter yes (Y) if they are acceptable or no (N) if you wish to reenter information.
Upon entering yes, the new information is added to the /etc/inet/hosts file.
You then are prompted to save the information on diskette for copying to the system
consoles.
Adding ip–address SMP61000node–name to /etc/inet/hosts
Adding ip–address cp_cons01 to /etc/inet/hosts
Adding ip–address cp_cons02 to /etc/inet/hosts
Adding ip–address xterm–node–name to /etc/inet/hosts
Adding SMP61000–node–name root to rhosts file.
Do you want to copy the hosts file to diskette for the 2200 consoles? Y
7848 4078–004

Installing SPO/HMP Console and Related Software
13. Enter yes (Y) to save the information on diskette. You are prompted to put a floppy
diskette into the drive unit. Insert the blank diskette you formatted earlier and press
Enter.
Put diskette into drive and press RETURN:
Updating /etc/inet/inetd.conf ...done
****************************************************
The system must be rebooted to load the new kernel.
****************************************************
Finished running the ClearPath tuning script.
Press return to shutdown and reboot.
When the script is done, you are prompted to shut down and reboot the SPO server.
14. Remove the diskette (which now contains the hosts file information) from the drive
unit and press Enter to reboot the SPO server.
When the reboot is done, copy the hosts file saved on diskette to the 2200 node consoles
as described in 6.10.
7848 4078–004 6–37

Installing SPO/HMP Console and Related Software
6.10. Copying the Hosts File (Done at 2200 System
Consoles)
6–38
Before using SPO/HMP Console software, you must ensure that the hosts file saved to
diskette when you ran the tuning script (6.2 or 6.9) is copied to each system console.
The host file provides the system consoles with the network address (IP address) of the
SPO server, the X terminals, and other hosts on the network. The hosts file does not
provide the IP address of the router to which the console LAN might be connected.
You load the hosts file to each system console from diskette using the Single Point
Interface Utility accessed through the 2200 Series system console Utilities session
(Optional Features option) (see Figure 6–2). The consoles can be done in any order, but
the procedure must be done on every system console.
Figure 6–2. System Console F3 Utilities Session Menu
7848 4078–004

Take the following steps:
Installing SPO/HMP Console and Related Software
Note: Switch the monitor concentrator to the first system console position (see 3.1).
1. On the system console, press F3 to activate the Utilities menu (Figure 6–2).
2. Select Optional Features and press Enter. A list of utilities similar to the following
appears:
AMS Utility
ESR Utility
UTCUS Utility
USP Utility
USP APFG Utility
SP Interface Utility
3. Select SP Interface Utility and press Enter. An Execute box appears.
4. Press Enter. The Single Point Interface Utility Session window appears
(Figure 6–3).
5. Press Esc to get the menu bar and use the arrow keys to select the Hosts File menu
bar item. A list of options appears as follows:
Load
Save
Edit
6. Press Enter to select the Load option. A form appears for selecting the media
(see Figure 6–4).
7. Press Enter again to position the cursor in the diskette type field. Press an arrow
key to activate the following drop down list:
DOS–HD
DOS–DD
UNIX
8. Select the UNIX option and press Enter.
9. Tab to the Host Name field and enter the name of whichever system console you are
loading as follows:
cp_cons01 (first system console)
cp_cons02 (second system console)
cp_cons03 (third system console)
and so on, up to cp_cons12 (twelfth system console)
This name identifies the system console on the TCP/IP network (for example, so the
SPO server can communicate with it).
Note: The name specified can be different from the system console name used on
the SCF token ring LAN.
7848 4078–004 6–39

Installing SPO/HMP Console and Related Software
6–40
Figure 6–3. Single Point Interface Utility Session Window
Figure 6–4. Specify Load Diskette Menu
10. Tab to the other fields on the form and make entries as follows:
Select No in the Use hosts file subnetwork information if available?: field,
unless you are using subnet masking, in which case you should select Yes.
Select Yes in the Use hosts file router information if available?: field, unless
for some reason you do not wish to use the router, in which case you should
enter No.
11. Press Enter. When the Execute box appears, press Enter again. You are prompted
to insert the diskette.
Insert the diskette
Note: Be sure to insert the diskette in the system console diskette drive unit.
7848 4078–004

Installing SPO/HMP Console and Related Software
12. In the system console diskette drive unit, insert the hosts file diskette created when
you ran the tuning script. Press Enter. A window appears indicating that the system
is working and that you should wait. The following message appears:
Added old router information to the new hosts file.
New hosts file loaded. Press Enter to continue.
13. Press Enter to continue. If the SPO server, X terminal, and system consoles are not
all on the same LAN, you need to add router information to the hosts file as follows:
Note: Skip steps a. through h. and proceed to step 14 if your SPO server, X
terminal, and system consoles are all on the same LAN.
a. Press Esc to get the menu bar and select the Changes menu bar item
(Figure 6–3). A list of options appears as follows:
Initialize Work
Execute Changes
Report Changes
b. Select Initialize Work. Press Enter, then press Enter again to execute.
c. Press Esc to activate the menu bar, and select the Routers menu bar item
(Figure 6–3). A list of options appears as follows:
Add Router
Delete Router
Display Routers
d. Press Enter to select Add Router. The window shown in Figure 6–5 appears.
e. In the bottom portion of that window, enter the IP address and host name of the
router.
f. When done, press Enter. The Single Point Interface Utility window reappears.
g. Select the Changes menu bar item (Figure 6–3). A list of options appears as
follows:
Initialize Work
Execute Changes
Report Changes
h. Select Execute Changes to enable the changes to the hosts file, and press Enter
to execute.
Note: When the router is configured, you can use the SAVE option to save the
router and host information for later loading at other system consoles.
14. Enable the SP Interface by taking the following steps:
a. Press the F2 key to activate the Display Control menu.
b. Select SP Interface and press Enter.
c. Select Enable and press Enter again. Press Enter again to execute.
7848 4078–004 6–41

Installing SPO/HMP Console and Related Software
6–42
15. Remove the diskette from the drive unit.
Figure 6–5. Add Router Information Window
Caution
Do not reboot system consoles by using the manual reset button on the system
unit. To reboot a system console, use the Terminate option of the Utilities (F3)
menu.
16. Reboot the system console to enable the changes you have made. To reboot the
system console, take the following steps:
a. Press F3 to access the Utilities session.
b. Select the Terminate option. When the following message appears, press Enter
to reboot:
Safe to Power off
– or –
Hit Any Key to Reboot
c. After the system console reboots, check the device status for the SP interface as
follows:
1. Press the F2 key to activate the Display Control menu.
2. In the Device Status window the SP Interface field should be idle.
Repeat this procedure for each system console.
When done with a system console, you may copy and activate the Autoaction Message
System (AMS) database at that console (6.11). Alternatively, you may install the hosts
files first on all system consoles, then copy and activate the AMS databases.
7848 4078–004

Installing SPO/HMP Console and Related Software
6.11. Copying and Activating the AMS Database
(Done at 2200 System Consoles)
Note: If you are an experienced SPO user and already have a configured X terminal,
you may perform the procedures in this subsection from an X terminal to the
SPO server rather than using the SPO server console.
Autoaction Message System (AMS) provides a pattern-matching capability to recognize
and take automated actions for OS 2200 console messages. For SPO/HMP Console to
operate properly, you must
Remotely install the SPO/HMP AMS database (hmp-ix22) on each system console
(6.11.1)
Activate each system console’s AMS database using the AMS Utility session (6.11.2).
Change each system console’s startup sessions to Systems Operations (6.11.3)
6.11.1. Remotely Installing the AMS Database (Done at SPO
Server)
To remotely install the SPO/HMP AMS database (hmp-ix22) for each system console,
take the following steps:
Notes:
Before running the Remote Install Utility (RIU), you may wish to start the SPO
daemons (7.1) to ensure that installation of the AMS database is logged in the
Remote-Install log file. Information from that file may be needed if something
goes wrong during the installation.
Switch the monitor concentrator to the SPO server position before beginning.
1. Run the RIU by entering the following command for each system console:
/opt/SPO/riu hmp–ix22 console
where console is the name of the system console (for example, cp_cons01) to which
you are copying the database.
The following message indicates RIU has started:
riu 4.1 Fri Dec 20 13:49:47 CDT 1996
If the console has not yet been configured for remote install, this message
appears:
–Console “console” not installed using riuc.
Would you like to configure console now?
(Y to configure, N to skip this console): Y
7848 4078–004 6–43

Installing SPO/HMP Console and Related Software
6–44
and you must take the following steps:
a. In response to that message Enter Y. You are prompted to enter the system
type:
What system type is console “console” connected to?
1 = 1100/90, 2200/100, 2200/200, 2200/400, or 2200/600
2 = Any other 2200 system (e.g., 2200/500, 2200/900)
3 = don’t know (so cannot configure “console” now)
b. Enter 2 to specify the 2200 node. A message confirms that the system
console has been configured:
+Console “console” dynamically configured.
If the console has been configured for remote install, or after taking steps a
and b, RIU compares the SMART level on the console with the database level to
ensure that they are compatible. It then asks you to confirm the install or
update.
Getting SMART level from console ”console” ...
Interactive mode off.
Hash mark printing on (1024 bytes/hash mark).
#
SMART level, on console ”console”, is 5R2 and database ”hmp–ix22”
level is 6.
INSTALL or UPDATE hmp–ix22 on console?
( or Y to execute, # to quit riu): y
2. Enter yes (Y) to proceed. Messages appear indicating that the database is being
copied and installed.
Looking for hmp–ix22 on console ...
Interactive mode off.
Hash mark printing on (1024 bytes/hash mark).
/console/backup/ams/*.t: No such file or directory.
can’t find list of remote files, oops
/console/backup/ams/hmp–ix22.ams: No such file or directory.
INSTALLING hmp–ix22 on console ...
Interactive mode off.
Hash mark printing on (1024 bytes/hash mark).
#################################
+AMS database ”hmp–ix22” successful INITIAL INSTALL on console ”console”.
Note: If the database already exists on the console, riu asks whether you want to
overwrite it. Answer Y if this is replacing an older version that you do
not want to save. Answer N if you have modified an older version of
hmp-ix22 and want to save it. If you enter Y and later change your mind,
you can use rirestore to put back the previous version as described in the
Single Point Operations Console/Enterprise Server Edition Administration
and Configuration Guide.
Repeat that procedure for each of the 2200 Series system consoles.
7848 4078–004

Installing SPO/HMP Console and Related Software
6.11.2. Activating the SPO/HMP AMS Database (Done at System
Consoles)
To activate the hmp-ix22 AMS database, perform the following at each system console:
1. On the system console, press F3 to activate the Utilities menu (Figure 6–2).
2. Select Optional Features and press Enter. A list of utilities appears as follows:
AMS Utility
ESR Utility
UTCUS Utility
USP Utility
USP APFG Utility
SP Interface Utility
3. Select AMS Utility and press Enter. An Execute box appears.
4. Press Enter. The AMS Utility window appears.
5. At the command prompt enter the following command:
activate hmp–ix22
A response indicating that the database will be activated appears.
I0007: Database “hmp–ix22” will be activated.
6. At the command prompt enter exit to exit the AMS Utility session.
6.11.3. Changing the Start-up Session to Systems Operations
(Done at System Consoles)
The start-up session for each system console determines which session is displayed
when the replicated console is opened from the SPO/HMP Console. Change the start-up
session to the Systems Operations session for each system console with the following
steps:
1. On the system console, press F3 to activate the Utilities menu (Figure 6–2).
2. Select Configuration: Dynamic and press Enter. A list of change options appears.
3. Select both options and press Enter. Another list of options appears.
4. Select Display Current Values and press Enter. An Execute box appears.
5. Press Enter. The Dynamic Configuration window appears with the cursor on the
Console Control option.
6. Press Enter. Tab down to the Start-up Session option. A list of options appears.
7. Select the System Operations option.
8. Press Enter. System Operations is now displayed as the start-up session.
9. Press Enter. The cursor returns to the Dynamic Configuration menu.
7848 4078–004 6–45

Installing SPO/HMP Console and Related Software
6–46
10. Select Execute Changes and press Enter. An Execute box appears.
11. Press Enter. Wait for the Working, Please wait box to disappear.
12. Select Exit Configuration and press Enter. An Execute box appears.
13. Press Enter.
Switch the monitor concentrator to the SPO server position and proceed with
configuration of X terminal software (Section 7).
7848 4078–004

Section 7
Enabling Use of the X Terminal
Following installation of SPO/HMP Console software as described in Section 6, enable
monitoring (Windows NT), or monitoring and control (UNIX), using the LT501 X
terminal as follows:
Note: If software is preinstalled on the SPO server, skip steps 3 and 4. The
information configured in those steps is provided by the configuration file
/usr/X/lib/unisys/unisys-config which also is preinstalled (see 11.3.1).
1. Start the SPO daemons (7.1).
2. Configure each X terminal (7.2).
3. Enable SPO server communications and remote access to fonts (7.3).
4. Enable monitoring (Windows NT), or monitoring and control (UNIX) from the
X terminal or terminals as follows:
If Windows NT is installed on the Intel node, use the procedure in 7.4.
If UNIX is installed, use the procedure in 7.5.
5. Start normal SPO/HMP Console operations (7.6).
7.1. Starting and Stopping the SPO Daemons
Note: Switch the monitor concentrator to the SPO server position.
The SPO daemons are background processes on the SPO server that must be running for
the correct operation of SPO/HMP Console. To start the SPO daemons take the
following steps:
1. If you are not already logged on at the SPO server, log on as superuser (see 6.4).
2. Enter the following command to start the SPO daemons:
# /etc/init.d/spod start
Whenever the SPO server is rebooted, the SPO daemons restart automatically.
You may need to stop all daemons before starting them (for example, if one of the
daemons was inadvertently stopped). To stop the daemons, enter the following:
# /etc/init.d/spod stop
7848 4078–004 7–1

Enabling Use of the X Terminal
7.2. Configuring Each X Terminal
7–2
Cautions
Except for yes (Y) or no (N) entries, all entries and responses to prompting
messages in this section are case sensitive. Type entries exactly as shown in
samples.
During the procedure, be sure the Caps Lock key does not become locked in
the uppercase position while making entries. Use the Shift key if you want to
enter an uppercase password.
After starting the SPO daemons, power on each LT501 X terminal and configure each
terminal using the following procedure:
1. The message sequence at power-on depends on the state of the X terminal as
follows:
If the X terminal has not been configured previously, an angle bracket (>)
prompt appears:
>
If the X terminal has been configured previously, a message appears to which
you must respond within 5 seconds.
Press ENTER within 5 seconds to prevent network reboot.
Press Enter to prevent booting to the existing X terminal configuration.
In response, an angle bracket (>) prompt appears.
>
2. Enter the config command in response to the prompt as follows:
> config
You are prompted to select a keyboard language.
Language Codes:
0 = US English, 1 = Belgian, 2 = Danish, 3 = French,
4 = French Canadian, 5 = German, 6 = Italian, 7 = Latin American,
8 = Norwegian, 9 = Spanish, 10 = Swedish/Finnish, 11 = Swiss French,
12 = Swiss German, 13 = UK English
Keyboard Language [0]:
7848 4078–004

Enabling Use of the X Terminal
3. Enter the number of the keyboard language you wish to use. You are prompted to
enter the IP address of the LT501 X terminal.
Configure Ethernet
IP address [0.0.0.0]: xxx.xxx.xxx.xxx
Note: IP addresses must be administered by a central administrator at the site.
4. Enter the IP address from Table 2–1. You are prompted to enter the address mode.
IP address mode (auto, user) [auto]: user
5. Enter user as the IP address mode. You are prompted to enter the boot method.
Boot method (tftp, rom, mop) [tftp]: tftp
6. Enter tftp (the default) as the boot method. You are prompted to enter the IP
address of the SPO server (BOOTHOST).
Boot host 1 [BOOTHOST]: xxx.xxx.xxx.xxx
7. Enter the IP address from Table 2–1. You are prompted to enter the IP address for a
second host.
Boot host 2 []:
8. Press Enter to bypass the second host. You are prompted to enter the boot file
name.
Boot filename []: /tftpboot/images/arxC-dy
9. Enter /tftpboot/images/arxC-dy (the letter C in arxC-dy must be uppercase) as the
boot file name. Messages appear as the configuration is saved. The angle bracket
(>) prompt reappears.
Standalone configuration saved
Ethernet address is 00:00:00:00:00:00
Hardware Address = (00:00:00:00:00:00)
Commands:
boot [method] { ] serial [baudrate]
ping host [timeout [count]] telnet [host [port]]
netstats [s|i|r|c] config [full]
diagnostics reset [factory]
flashload flashinfo
monitorconfig
>
7848 4078–004 7–3

Enabling Use of the X Terminal
7–4
10. Proceed with step 11 if your X terminal is connected to the same LAN as the SPO
server; otherwise, if the X terminal is connected to a different LAN than the SPO
server, take the following steps to configure an IP address for the router:
a. Enter the config full command. You are prompted with some of the same
configuration messages that appeared earlier. For example, the first message
that appears is the keyboard language prompt.
Language Codes:
0 = US English, 1 = Belgian, 2 = Danish, 3 = French,
4 = French Canadian, 5 = German, 6 = Italian, 7 = Latin American,
8 = Norwegian, 9 = Spanish, 10 = Swedish/Finnish, 11 = Swiss French,
12 = Swiss German, 13 = UK English
Keyboard Language [0]: 0
b. Press Enter (select the default) for every message, until you get to the following
message:
Default router [0.0.0.0]: xxx.xxx.xxx.xxx
c. Enter the IP address of the router from Table 2–1. The next configuration
message appears.
d. Press Enter to select the default for all remaining messages. When done, the
angle bracket (>) prompt reappears.
11. Enter the boot command. A prompt now verifies the boot file name.
Boot tftp [192.61.246.14] /tftpboot/images/arxC-xie
12. Press Enter in response. Loading messages appear followed by a window that
states that several files cannot be found. These files are the remote configuration
files. Because this installation did not use remote configuration files, you can safely
ignore these messages. The screen also flashes as the X terminal boots.
Note: If the boot file cannot be found, then the X server software may not be
properly installed. Reinstall the X server software (6.6) or change the boot
file name (if other than arxC-xie) to match the one you choose during the
install.
13. The Control Panel window should now open on the screen. Press the Select key if it
is not open. Ignore the login window if it is open.
Take the steps described in 7.3 to enable communications between the SPO server and
the X terminal.
7848 4078–004

Enabling Use of the X Terminal
7.3. Enabling SPO Server Communications and
Remote Access to Fonts (Done at Each X
Terminal)
Note: If software is preinstalled on the SPO server, skip this subsection and proceed
with subsection 7.4.
This procedure should be done as the next step following configuration of each
X terminal (7.2). As indicated, a Control Panel window should be open following the
reboot. If the Control Panel window is not open, press the Select key.
To enable communications between the SPO server and the LT501 X terminal, you must
enable an X Display Manager Control Protocol (XDMCP) session at the X terminal. Take
the following steps to enable an XDMCP session:
1. In the Control Panel window select Setup and click Launch. A Setup window
containing icons appears.
2. Double click the Session Management icon. A Setup-Session Management window
appears.
3. In the Setup-Session Management window, use the arrow keys in the list box to
change the Autoconnection mode from LOCAL to XDMCP.
4. Select Apply and then OK to close the window.
5. In the Setup window, double click the Font Management icon. A Configure Font
Management window opens.
6. Ensure that Enable Remote Access box is checked. If it is not, click it.
7. In the Saved Font Path field, select the font path as follows:
a. Position the slider to the top of the slide.
b. Click the top element in the list.
c. Click Edit . . . Font Path Element. A Setup window opens.
d. In the Font Path Element field, backspace to erase the current element and
enter the following as the Font Path Element:
/opt/SPO/XP/fonts
e. Click Add Before, then click Dismiss.
At this point, /opt/SPO/XP/fonts is the first path in the font path list.
f. Click Apply and then OK. The window closes.
You can now enable monitoring for Windows NT (7.4) or monitoring and control for
UNIX (7.5).
7848 4078–004 7–5

Enabling Use of the X Terminal
7.4. Enabling Monitoring (for Windows NT)
7–6
If Windows NT is installed on the Intel node, SPO/HMP Console monitors the
Windows NT event logs and converts entries in those logs to SPO/HMP Console alarms.
To enable monitoring of the Windows NT node, and also the SPO server, from the LT501
X terminal, you must
Install UNIX Resource Monitor (URM) agent files on the SPO server so that
SPO/HMP Console can monitor the SPO server (7.4.1)
Configure the Windows NT FTP server service (7.4.2)
Transfer the Windows NT agent to the Intel node using the Single Point
Configuration routine (7.4.3)
Install the Windows NT agent (7.4.4)
7.4.1. Installing URM Files on the SPO Server
Note: Switch the monitor concentrator to the SPO server position.
You install URM files on the SPO server so that it can be monitored by SPO/HMP
Console. To install URM files, take the following steps:
1. If you are not already logged on at the X terminal, log on in the login window
(Figure 7–1) as the SPO administrator as follows:
a. Enter spadmin (the SPO administrator user-id).
b. Press Enter to advance to the password field.
c. Enter unisys1234 (the default installation password).
You are prompted to select a configuration to retrieve (Figure 7–2).
Notes:
Configuration names take the format CPIX_n_x.xCP where n represents the
number of 2200 node partitions and x.x represents the SPO/HMP Console
software release level. Because the URM is universal across all of the
configurations, you may select any of the supplied configurations to edit. The
configuration itself is not edited at this time.
Resize windows or move them using the mouse if you wish.
2. Select any one of the supplied configurations and click OK to edit (for example,
CPIX_NT_1_x.xCP). In a few moments, both a configuration routine main menu
(Figure 7–3) and a TopCluster window similar to Figure 7–7 appear.
7848 4078–004

Figure 7–1. X Terminal Login Window
Figure 7–2. Selecting a Configuration
Enabling Use of the X Terminal
Figure 7–3. Single Point Configuration Routine Main Menu
3. In the Configuration Routine main menu select Application, then select Maintain
Unix Agents from the list of options.
After a brief wait, the Maintain UNIX Agents window (Figure 7–4) and a UNIX
Resource Monitor Policies window appear. The Maintain UNIX Agents window
identifies the status of the agent by its alias (SPO_Server for the SPO server).
4. Click the hyphen (-) in the URM Policy column.
A dialog window appears.
5. Click URM Policy “default”, then select OK. The word default appears under URM
Policy for SPO_Server, and the word yes appears under URM Enabled? (Figure 7–4
shows how the window should look when done).
7848 4078–004 7–7

Enabling Use of the X Terminal
7–8
Figure 7–4. Maintain UNIX Agents Window (SPO Server Only)
6. In the Maintain UNIX Agents window menu select Execute, then select Install from
the options that appear.
A dialog window appears in which to identify systems on which to install agents.
7. Click SPO_Server.
SPO_Server appears in the lower half of the window.
8. Click OK to accept the entry.
In a few moments, a window appears with a message indicating that the UNIX agent
for SPO_Server has been installed successfully.
9. Click Continue to proceed. Verify that the URM agent on the SPO server is running
as follows:
a. At the X terminal, open a new X terminal window session by positioning the
cursor on the screen background, clicking on the right mouse button, selecting
New Window, and then releasing the mouse button.
b. In the new window, enter the following command:
$ ps –ef | grep urm.loop
The preceding step finds the main URM agent running if the right half of the listing
produced by the PS command indicates the following:
sh ./urm.loop
10. If the main URM agent is not running, log on as superuser (see 6.4) either at the X
terminal using the su command or at the SPO server, and enter the following
command:
# /opt/SPO-agent/spo_urm start
Then repeat Steps 9 and 10.
11. When done, close the window session opened in step 9a.
7848 4078–004

Enabling Use of the X Terminal
12. Once you verify that the URM agents are running, exit from the windows as follows:
a. In the Maintain UNIX Agents window, select the File option, then select Exit
from the list of options that appears.
b. In the Configuration Routine main menu, select the File option, then select Exit
from the list of options that appears.
The following prompt appears in a window:
c. Click OK.
Quit Single Point Configuration Routine
OK CANCEL
A Goodbye window appears.
d. Click Press to End Session.
e. Click OK to quit the session.
A login window appears.
For more information on UNIX Resource Monitor agents, refer to “Administering UNIX
Agents” in the Single Point Operations Console Administration and Configuration
Guide.
7.4.2. Configuring the FTP Server Service
Note: To perform this procedure you must access the Windows NT operator
interface. In the console hardware cabinet, switch the monitor concentrator to
the Windows NT node position to access the Windows NT interface. You
cannot access the Windows NT operator interface through the X terminal.
To copy and install Windows NT agents, you must temporarily reconfigure the Windows
NT FTP server service as follows:
1. If you are not currently logged on, power on or restart the Windows NT node and log
on as the Administrator (4.6).
2. Click Start.
A popup window appears.
3. Select Programs, Microsoft Internet Server (Common), then Internet Service
Manager.
This launches the Microsoft Internet Service Manager application. A window opens
listing Internet services (WWW, Gopher, and FTP).
7848 4078–004 7–9

Enabling Use of the X Terminal
7–10
4. Double click the name of the computer running the FTP service.
A tabbed FTP Service Properties screen opens.
5. Click the Service tab and configure it as follows:
a. Click the Allow only anonymous connections check box to clear it (ensure that
no check mark appears in the check box).
A warning dialog box appears asking if you wish to continue.
b. Click Yes.
6. Click the Directories tab and configure it as follows:
a. By default the directory D:\Inetpub\ftproot is listed. Select (highlight) that entry.
b. Click Edit Properties.
The directory properties sheet appears.
c. By default the default access for this directory is read only. Click the Write
check box to enable write access (ensure that a check mark appears in the
check box). That will allow the Windows NT agent software to be copied to the
Windows NT node.
d. Click Apply then OK on the directory properties sheet.
7. Exit from the Internet Service Manager application.
You now can transfer Windows NT agent software as described in 7.4.3. After
transferring that software, you should reverse the changes made in this subsection to
return FTP server service to its default condition or configure it to site requirements.
7.4.3. Transferring the Windows NT Agent
Note: Perform this procedure from the X terminal. This procedure assumes you
have logged in at the X terminal and selected a SPO configuration as
described in 7.4.1.
Take the following steps to transfer the Windows NT agent to the Windows NT node:
1. From the Single Point Configuration routine main menu (Figure 7–3), click
Application. A menu of possible applications appears.
2. Click the Maintain Windows NT Interface menu item, and then select Transfer
Software. A window for entering the host name of the Windows NT node appears
(Figure 7–5).
3. Enter the host name of the Windows NT node from Table 2–1 and click OK.
A window for entering the Windows NT administrator name appears (see
Figure 7–6).
7848 4078–004

Enabling Use of the X Terminal
Figure 7–5. Entering the Host Name for Transferring the Agent
Figure 7–6. Defining the Administrator for Installation of the Agent
4. Enter Administrator (the default installation administrator name) and click OK.
A window appears requesting you to enter a password.
5. Enter administrator (the default installation password). The agent software
transfer is initiated.
Note: If the agent software transfer fails, an explanation appears. The message is
logged in two log files (NTINSTALL and host-name, where host-name is the
host name of the Windows NT node) that you can view using the Log View
window from the Single Point Operations Console menu.
7848 4078–004 7–11

Enabling Use of the X Terminal
7.4.4. Installing the Windows NT Agent
7–12
After you transfer the Windows NT agent to the Windows NT node, follow this procedure
to install the agent:
Note: Switch the monitor concentrator to the Intel node position.
1. Log on to Windows NT if you are not already logged on.
2. In the Main application group, click the MS-DOS icon to open an MS-DOS emulator
window.
3. At the DOS prompt, use the cd command as follows to change to the installation
directory (if you are not already in that directory):
cd d:\InetPub\ftproot\temp
4. Enter the following command to start the installation program:
spinst
When the DOS prompt returns, the installation is complete.
5. Type exit and press Enter to return to Windows NT. Installation is now complete.
After successful installation, the Windows NT node icon (CP_NT) indicates an active
connection to the SPO server in a top cluster diagram (Figure 7–7).
7848 4078–004

Enabling Use of the X Terminal
Figure 7–7. SPO/HMP Console TopCluster Window (Single 2200 Partition)
7848 4078–004 7–13

Enabling Use of the X Terminal
7.5. Enabling Monitoring and Control (for UNIX)
7–14
If UNIX is installed on the Intel node, you must enable monitoring and control of the
UNIX node and the SPO server from the LT501 X terminal as follows:
Create URM agent files on the SPO server (7.5.1)
Copy and install the URM agent files to the UNIX node and redirect console output
by running a script at the UNIX node (7.5.2).
7.5.1. Creating URM Files
To create URM files on the SPO server, you must take the following steps at the LT501
X terminal:
1. If you are not already logged on at the X terminal, log on in the login window
(Figure 7–1) as the SPO administrator as follows:
a. Enter spadmin (the SPO administrator user-id)
b. Press Enter to advance to the password field.
c. Enter unisys1234 (the default installation password).
You are prompted to select a configuration to retrieve (Figure 7–2).
2. Select any one of the supplied configurations and click OK to edit (for example,
CPIX_1_x.xCP).
In a few moments, the configuration routine main menu (Figure 7–3) and a
TopCluster window similar to Figure 7–7 appear.
Notes:
Configuration names take the format CPIX_n_x.xCP where n represents the
number of 2200 node partitions and x.x represents the SPO/HMP Console
software release level.
Because the URM is universal across all of the configurations, you may select
any of the supplied configurations to edit. The configuration itself is not
edited at this time.
Resize windows or move them using the mouse if you wish.
3. In the Configuration Routine main menu select Application, then select Maintain
Unix Agents from the options that appear.
After a brief wait, the Maintain UNIX Agents window (Figure 7–8) and the UNIX
Resource Monitor Policies window (Figure 7–9) appear.
The Maintain UNIX Agents window identifies the status of each agent by its alias
(SPO_Server for the SPO server and CP_UNIX for the UNIX node).
7848 4078–004

Enabling Use of the X Terminal
4. Take the following steps to select the default URM policy and security scheme for
the UNIX node (called CP_UNIX in the Maintain UNIX Agents window):
a. For CP_UNIX, click the hyphen (-) in the URM Policy column.
A dialog window appears.
b. Click URM Policy “default”, then select OK. The word default appears under
URM Policy for CP_UNIX.
c. In the Security Scheme column for CP_UNIX, click Access Allowed.
A dialog window appears.
d. Select Manual Install, then click OK.
5. Repeat only steps 4a and 4b for the SPO server. Do not change Access Allowed
under Security Scheme for SPO_Server. Figure 7–8 shows how the window should
look when done.
Figure 7–8. Maintain UNIX Agents Window
Figure 7–9. URM Policies Window
7848 4078–004 7–15

Enabling Use of the X Terminal
7–16
6. Install agents as follows:
a. In the Maintain UNIX Agents window select Execute, then select Install from
the list of options.
A dialog window appears in which to identify systems on which to install agents.
b. Click CP_UNIX first and then SPO_Server next.
They appear in the lower half of the window.
c. Click OK to accept the entries.
In a few moments, a window appears with a message indicating that the agent
for CP_UNIX has been placed in the following directory on the SPO server:
/var/opt/spo/manual/CP_UNIX
7. Click Continue to proceed.
In a few moments, a window with a message appears indicating that the UNIX agent
for SPO_Server has been installed successfully.
8. Click Continue to proceed. Verify that the URM agent on the SPO server is running
as follows:
a. At the X terminal, open a new X terminal window session by positioning the
cursor on the screen background, clicking on the right mouse button, selecting
New Window, and then releasing the mouse button.
b. In the new window, enter the following command:
$ ps –ef | grep SPO–agent
9. Check the right half of the listing produced by that command to ensure that the
agents are running. This is indicated by the following processes being listed:
/opt/SPO-agent/urm.loop
/opt/SPO-agent/pulse.loop
10. If they are not running, log on as superuser (see 6.4) either at the X terminal using
the su command or at the SPO server, and enter the following command:
# /opt/SPO-agent/spo_urm start
Then repeat Steps 9 and 10.
11. When done, close the window session opened in step 9a.
7848 4078–004

Enabling Use of the X Terminal
12. Once you verify that the URM agents are running, exit from the windows as follows:
a. In the Maintain UNIX Agents window, select the File option, then select Exit
from the list of options that appears.
b. In the Configuration Routine main menu, select the File option, then select Exit
from the list of options that appears.
The following prompt appears in a window:
c. Click OK.
Quit Single Point Configuration Routine
OK CANCEL
A Goodbye window appears.
d. Click Press to End Session.
e. Click OK to quit the session.
A login window appears.
The URM agent files now are ready to be copied to the UNIX node and installed using
procedures described in 7.5.2.
7.5.2. Installing URM Agents and Redirecting Console Output
Notes:
SPO/ESE sites must be at release 4.0 or higher and installed in the default
location to use this procedure. The UNIX Resource Monitor was not included in
earlier releases. If you have an earlier release of SPO/ESE, you must upgrade.
If you have installed SPO/ESE in a location other than the default, refer to the
installation instructions that came with the release.
Before beginning, switch the monitor concentrator to the Intel node.
This procedure describes steps for
Copying the URM agent files from the SPO server to the UNIX node
Installing the agent files
Testing the serial port connection between the UNIX node and SPO server
Redirecting the console output from the UNIX node to the SPO server so that it can
be monitored by SPO/HMP Console
Because the connection test fails if a process is not monitoring the serial port while it is
being tested, the first few steps of the procedure open an X terminal console session to
monitor the UNIX node.
7848 4078–004 7–17

Enabling Use of the X Terminal
7–18
The steps to take are as follows:
1. If you are not already logged on at the X terminal, log on in the login window
(Figure 7–1) as the SPO operator as follows:
a. Enter spoper (the SPO operator user-id)
b. Press Enter to advance to the password field.
c. Enter unisys1234 (the default installation password).
You are prompted to select a configuration to retrieve (Figure 7–2).
2. Select the predefined configuration for your site: CPIX_1_x.xCP (single partition
with two consoles), CPIX_2_x.xCP (two partitions with two consoles), or
CPIX_4_x.xCP (four partitions with four consoles). Then click OK.
In a few moments, the SPO/HMP Console main menu (Figure 7–10) appears.
3. In the main menu click Displays then Cluster.
A TopCluster window (Figure 7–7) appears.
4. Within the TopCluster window, verify that the SPO_Server, CP_UNIX, and console
icons are green. Green icons indicate that the SPO server has a normal connection
to those units.
If the icons have not turned green within about 30 seconds, ensure that all SPO
daemons are running by stopping and restarting them as described in 7.1.
Note: The remaining steps of this procedure are done at the UNIX node.
5. At the UNIX node, if you are not already logged on, log on as root (superuser)
(see 6.4).
6. In response to the pound sign (#) prompt, enter the following command to install
and start the script that copies the URM agent files:
# sh /usr/lbin/CP_urm.inst
Messages appear and you are prompted to enter the IP address of the SPO server.
You must be root to execute this script.
This script installs the UNIX Resource Manager.
Please enter the SPO system IP Address.
IP Addresses are written as four decimal integers,
separated by decimal points and no spaces (e.g. 128.10.2.70).
The SPO IP Address is? : xxx.xxx.xxx.xxx
7848 4078–004

Enabling Use of the X Terminal
7. Enter the SPO server IP address from Table 2–1. A prompt asks for the SPO server
name.
Please enter the SPO system node name.
This is typically the name returned when the uname –n
command is entered on the SPO system.
The SPO system node name is? :
8. Enter the SPO server name from Table 2–1. Messages appear as the URM agent
software is copied and installed (this process could take a couple of minutes).
Adding the following line to /etc/hosts:
xxx.xxx.xxx.xxx xxxxx SPO_Server # SPO
Changing line in /etc/hosts from:
xxx.xxx.xxx.xxx xxxxxxx
to:
xxx.xxx.xxx.xxx xxxxxxx CP_UNIX # Alias needed by URM
Getting the URM files ....
rcp –pr SPO_Server:/var/opt/spo/manual/CP_UNIX /tmp
Installing UNIX Resource Monitor. Please wait...
Sending output to nohup.out
INSTALL on CP_UNIX completed successfully
Installation of UNIX Resource Monitor complete
Getting the console redirection script ....
rcp –pr rt25spo:/opt/SPO/U6000/scripts/build_serial_console /tmp/CP_UNIX
Redirecting the console output to the serial port.
NOTE: A reboot is needed to activate this console redirection.
The purpose of this script is to take the console from the VGA monitor
and keyboard and put it onto /dev/term/00.
This is accomplished by modifying your UNIX kernel. This requires a
rebuild of your UNIX kernel and a reboot of your system. Upon rebooting
your system, all the console traffic will be rerouted to the terminal
connected to the /dev/term/00 serial port. Your VGA device may then be
used as a terminal.
Console control can be returned to the VGA device by executing the
accompanying script, build_vga_console.
Because you are building a new kernel you must be root to run this script!
To continue press RETURN, to quit type Q ––>>
9. Press Enter to continue.
For the console switch to occur, you must have a serial terminal device
connected properly to serial port /dev/term/00 and turned on. I will
test that for you now. This will only take a few seconds after which
you may terminate this function, continue on with the kernel build or
reexecute the test after making adjustments in your connection.
7848 4078–004 7–19

Enabling Use of the X Terminal
7–20
For this test to succeed, you must have a terminal device connected
to serial port 00 with a direct 1–1 serial cable. This cable will most
likely have to convert from a 9–pin connector to a 25–pin connector.
The terminal device must also be turned on.
To start the test press RETURN, to quit this script, type Q ––>>
10. Press Enter to test the serial port connection between the UNIX node and the SPO
server.
If the test succeeds, the following messages appear and you can continue with the
procedure:
The test succeeded, the build function will now continue.
The UNIX Operating System will now be rebuilt.
This will take some time. Please wait.
Root for this system build is /
The UNIX Kernel has been rebuilt.
The kernel changes for the console redirection to serial device
/dev/term/00 have been completed.
For the changes to take affect, the system must be shutdown and rebooted.
If you would like I will do this now with a ”shutdown –i6”. This
will broadcast a warning message to those currently online and wait 1
minute before asking if you wish to continue. If you answer ”y”
the system will be shutdown and a reboot will be initiated.
If you want me to do the SHUTDOWN now, answer Y, otherwise press RETURN: y
If the test fails, a prompt appears giving you the following options:
Rerun the test
Quit
Continue
You should select the option to rerun the test after first attempting to resolve the
problem (for example check cable connections and check for proper display at the
X terminal).
Caution
If you choose the continue option after a test failure without correcting the problem
first, the reboot of the UNIX node will hang while attempting to redirect its output to
the SPO server.
7848 4078–004

Enabling Use of the X Terminal
If after a test failure you choose to quit the script, you must take the following steps
before running the script again:
Enter the following sequence of commands to
− Remove all files associated with the URM
− Remotely copy a script from the SPO Server and then execute the script to
setup the vga monitor as the console output
− Rebuild the kernel and shutdown the system
# cd /opt/SPO–agent
# ./remove
# cd /tmp
# mkdir CP_UNIX
# cd CP_UNIX
# rcp –pr SPO_Server:/opt/SPO/U6000/scripts/build_vga_console \
> /tmp/CP_UNIX
#./build_vga_console
After the reboot, try to reinstall the URM agents by repeating the entire
procedure beginning with step 1 at the start of this subsection.
11. Enter y to shutdown the system.
The following messages appear:
I am initiating the shutdown now via ”shutdown –i6”
You will be given the opportunity to abort this procedure by
”shutdown” in about 1 minute. If you choose to abort the shutdown
(and the reboot), remember you must initiate that yourself for the console
redirection changes to become effective!!
Shutdown started. Tue Oct 22 15:22:11 CDT 1996
Broadcast Message from root (console) on rt25acp0 Tue Oct 22 15:22:12
CDT...
THE SYSTEM IS BEING SHUT DOWN NOW ! ! !
Log off now or risk your files being damaged.
Do you want to continue? (y or n): y
12. Enter y to continue the shutdown.
Changing to init state 6 – please wait
#
#
INIT: New run level: 6
The system is coming down. Please wait.
System services are now being stopped.
Print services stopped.
Stopping process accounting
Stopping Environment Control & Monitoring
Security audit trail daemon stopped
Saved the old unix kernel
Compacting BFS filesystem
Compaction of BFS filesystem completed
Installed new unix kernel
Cleaning up ramdisk device nodes ...done.
The system is coming down. Please wait.
The system is being rebooted.
7848 4078–004 7–21

Enabling Use of the X Terminal
7–22
13. When the UNIX node reboots, the first part of the boot operation displays at the
monitor concentrator, then the console output is redirected to the SPO
X–terminal—you can observe that in the CP_UNIX session that was started.
The last boot messages to be seen at the monitor concentrator are :
Total Real Memory = xxxxxxxx
Total Available Memory = xxxxxxxx
NCRSCSI : cid=0 pci_bus=0 pci_slot=0 vec=15 scsi–id=7 type=single–ended
found
DC21140/ASANTE Ethernet unit 0 initialized
Once the URM agents are running, you can start normal X terminal operations.
Note: If the installation fails, messages are logged in log file spinst.log in the
current directory.
7.6. Starting Normal SPO X Terminal Operations
Caution
To prevent unauthorized access to the X terminal following initial installation, the
site must change the default password (unisys1234) to a different password.
Note: The SPO daemons must be running before you start SPO/HMP Console
(see 7.1).
Take the following steps to begin normal SPO/HMP Console operations at the X
terminal:
1. Log on to the LT501 X terminal as the operator. In the login window (see
Figure 7–1), enter spoper as the user-id and unisys1234 as the password.
2. Select a configuration for operations (Figure 7–2):
For Windows NT select one of the following, then click OK.
− CPIX_NT_1_x.xCP (single partition)
− CPIX_NT_2_x.xCP (two-partition)
− CPIX_NT_4_x.xCP (four-partition)
For UNIX select one of the following, then click OK.
− CPIX_1_x.xCP (single partition)
− CPIX_2_x.xCP (two-partition)
− CPIX_4_x.xCP (four-partition)
3. Start Single Point Status (7.6.2) then activate the Single Point Autoaction Message
System (SP-AMS) database (7.6.3).
7848 4078–004

7.6.1. Windows Displayed by SPO/HMP Console
Upon selecting a configuration, the following windows open:
Enabling Use of the X Terminal
The SPO/HMP Console main menu (Figure 7–10) includes an Alert icon that turns
red whenever an alert is raised against any component of the ClearPath IX server.
A TopCluster diagram (Figure 7–7) contains icons representing the SPO server, the
Windows NT or UNIX node, and each 2200 partition and console. The icons turn red
whenever an alert is raised against the corresponding component. You can click an
icon to open a console session.
An Alerts window describes each alert currently raised against the ClearPath IX
server. Click the text of any alert for more information about the alert.
Figure 7–10. SPO/HMP Console Main Menu
SPO/ESE documentation can be viewed online. When SPO/HMP Console is running,
click Help in the SPO/HMP Console main menu (Figure 7–10) then click Documents.
When SPO/HMP Console is not executing, run the script /opt/SPO/spo_doc_view.
7.6.2. Starting Single Point Status
Single Point Status enables you to monitor the status of software and hardware
components on the 2200 node. Single Point Status can be started from the SPO/HMP
Console main menu using the following steps:
1. In the SPO/HMP Console main menu (Figure 7–10) select Applications, then select
Status from the list of options.
A dialog window appears asking you to select the classification you want to use.
2. Select the unix2200mon classification and click OK.
In a few moments the Single Point Status window appears.
7848 4078–004 7–23

Enabling Use of the X Terminal
7.6.3. Activating the SP-AMS Database
7–24
Note: The SP-AMS database supplied with SPO/HMP Console software contains no
patterns related to the Windows NT node so that node cannot be monitored.
Single Point Autoaction Message System (SP-AMS) is part of the SPO/HMP Console
software. SP-AMS runs continuously in the background once Single Point Operations
has been installed, and automates and monitors system operations. The spastart
database is provided with the SPO/HMP Console software and can be activated using the
following steps:
1. In the SPO/HMP Console main menu select Control, then select Automation Control
from the list of options.
The Automation Control window appears.
2. In the Automation Control window select Change, then select Activate Database
from the list of options.
A dialog window appears asking you to select the Single Point AMS database to
activate.
3. Select the spastart database and click OK.
The Automation Control window title now shows the active database as spastart.
4. Close the Automation Control window.
7848 4078–004

s
Section 8
Installing the Basic OS 2200 IOE
Fast-load tapes have been created to speed up installation of the OS 2200 IOE on a
ClearPath IX server. This section describes how to install OS 2200 IOE software from
fast-load tape CPIX-OE1, which is the minimum set of 2200 node software required to
achieve hardware ready for use (RFU). Section 10 describes how to install remaining
OS 2200 IOE products and the contents of fast-load tape CPIX-OE2 and tape CPIX-UDS3,
which are not needed to achieve hardware RFU.
Fast-load tape CPIX-OE1 contains IOE products (see Table 8–1) that typically can be
installed without change at a site and which should not have to be reinstalled.
Installation of products from CPIX-OE1 prevents having to install products from
numerous package tapes. CPIX-OE1 is either a single tape or a two-tape set.
This section describes
1. Read-and-reply message format (8.1)
2. How to perform an initial boot (8.2)
3. How to install IOE products from fast-load tape CPIX-OE1 (8.3)
4. How to establish the contracted performance level for IX4600 and IX4800 servers
(8.4)
Upon completion of the procedures described in this section, you must verify that the
hardware is ready for use by testing the communications links (see Section 9).
Notes:
Once IOE products have been installed from fast-load tape CPIX-0E1, they need
not be reinstalled from a package tape unless the site wishes to customize the
installation for some reason. Appendix D provides procedures for selectively
installing products from fast-load tape CPIX-0E1 when migrating from ClearPath
release 1.0 to 2.0.
The runstream that installs products from fast-load tapes also registers the
products with SOLAR.
Table 8–1 lists products in alphabetical order, not in the order they are stored on
tape.
7848 4078–004 8–1

Installing the Basic OS 2200 IOE
8–2
Table 8–1. Tape CPIX-OE1 Fast-Load Tape Contents
Product Full Name
CML Common Mathematical Library
CMR Console Message Redisplay
CMS1100 Communications Management System 1100
COMUS COMUS
CULL Cross Reference Generator
DAP Dump Analysis Processor
DDP-PPC Distributed Data Processing Program-to-Program Communications
DEPCON DEPCON
DMPLIB DMPLIB
DPREP1100 DPREP1100
ED ED
ELMS Extended Language Message System
ELT Element Processor
FAS File Administration System
FURPUR File Utility Routines/Program Utility Routines
GSA 1100 General Syntax Analyzer
IACULL Interactive CULL (IACULL)
IPF 1100 Interactive Processing Facility
IRU Integrated Recovery Utility
LINK Linking System
LIST LIST Processor
LSS Universal Compiling System (UCS) Language Support System
MAP Processor Collector
MASM Meta-Assembler
MSCP Monitor Services Control Program
OADE-UNIX Open Application Development Environment for UNIX
continued
7848 4078–004

Installing the Basic OS 2200 IOE
Table 8–1. Tape CPIX-OE1 Fast-Load Tape Contents (cont.)
Product Full Name
OLTP-HAA TransIT Open/OLTP Heritage Application Access Administration
OLTP-MON2200 TransIT Open/OLTP Transaction Monitor
OLTP-TM2200 TransIT Open/OLTP Transaction Manager
PADS Programmer’s Advanced Debugging System
PCFP Program-Callable FURPUR
PCIOS Processor Common Input/Output System
PDP Procedure Definition Processor
PLUS PLUS
PMD Postmortem Dump
2200POSIX-1 Portable Operating System Interface
RDMSKEY Relational Data Management System product key
ROLRUNS Roll-Out/Roll-Back Runstream
RSS Remote System Support
SIMAN Site Management Complex
SLIB Service Library
SMART SMART
SOLAR Software Library Administrator
SORT Sort/Merge Utility
SSG Symbolic Stream Generator
SYSLIB System Service Routines Library
UC Universal Compiling System (UCS) C
UCSRTS Universal Compiling System Run Time System
UNIACCESS-ODBC UniAccess Open Database Connectivity (ODBC) Server
UPLS Universal Compiling System (UCS) PLUS
URTS Universal Compiling System (UCS) Runtime System
7848 4078–004 8–3

Installing the Basic OS 2200 IOE
8.1. Read-and-Reply Message Format
8–4
Replies to outstanding OS 2200 read-and-reply console messages must begin with the
read-and-reply message number followed by a space. The following example illustrates
a typical read-and-reply message and how you would respond.
Ø Enter Reel Number
Your reply would begin with the same message number and a space, followed by the
information being entered:
Ø CPOE1A
Note that the reel number entered is only six characters long. Some ClearPath IX tape
names are longer than six characters (for example, CPIX-OE1)—you can enter only six
characters in response to a prompt for a reel number.
8.2. Performing the Initial Boot
Caution
The initial boot with jump key 13 set destroys all files on fixed mass storage.
Do not perform an initial boot except when initially setting up the 2200 node.
Before you can install OS 2200 software products, you must perform an initial boot to
load and activate the Exec from the boot tape. The first steps you take to perform the
boot depend on the current state of the 2200 node as follows:
Steps to take if the partition you want to boot is not activated (8.2.1)
Steps to take if the partition you want to boot already is up and the Exec is running
(8.2.2)
Do the procedure in either 8.2.1 or 8.2.2 to prepare for the boot, then complete the boot
process as described in 8.2.3.
Note: Either the command line or the menu bar can be used to perform the steps
described. To toggle between the command line and menu bar, press the Esc
key.
7848 4078–004

Installing the Basic OS 2200 IOE
8.2.1. Initial Boot Steps if Boot Partition Is Not Activated
If you do not have an activated boot partition, take the following steps to activate one:
1. Press F5 to access the SCF System Control display session at the master system
console.
2. If the cursor is not on the command line, press the Esc key to bring the cursor to the
command line.
3. Type the following command and press Enter to activate the partition:
AP xxxx
where xxxx is the partition name to be used to boot the system.
4. Proceed to 8.2.3.
8.2.2. Initial Boot Steps if Partition Is Up and Exec Is Running
Caution
To prevent loss of data, do not use a halt partition (hp) command to stop the Exec.
Use the procedures and commands described in this subsection.
If the partition you wish to use is already activated and the Exec is running, take these
steps to halt the Exec and confirm that it is halted:
1. At an Exec logical console for the running partition, press F4 to display the System
Operations Session.
2. Enter the following keyin to set jump key 3 to inhibit autorecovery:
SJ 3
3. Enter the following keyin to halt the Exec:
$!
Wait for the partition to change from running to stopped.
4. Press F5 to display the System Control session. A list of activated partitions appears
in the upper right corner of the display.
5. Press the function key (for example, F7) identified in the display for the partition.
That shows the partition’s Control session.
6. Proceed to 8.2.3.
7848 4078–004 8–5

Installing the Basic OS 2200 IOE
8.2.3. Completing the Boot Procedure
8–6
After preparing the boot partition as described in 8.2.1 or 8.2.2, take the following steps
at the master console session to perform the initial boot:
1. Enter the following system control facility (SCF) command to set the boot type to
tape:
st tape
2. Set the tape drive name from which you will be booting with the following SCF
command:
std tape-device-name
where tape-device-name is the name of a tape device in the partition.
3. Enter the following command to specify the name of the Disk Resident System
(DRS) disk to which the Exec will be written:
sd diskname
where diskname is the name of the DRS disk device in the partition.
4. Clear all jump keys with the following keyin:
cj all
5. Set jump keys for library load (jump key 4) and initialization (jump key 13) as
follows:
sj 4,13
Whenever jump key 13 is set, a prompt appears with a field for specifying the
reinitialize option.
6. In the field that appears, set the reinitialize option by typing the following entry and
pressing Enter twice.
destroy files
7. Load the tape EXEC BOOT in the tape drive specified in step 2.
8. Start the partition by entering the following SCF command:
sp
The start partition command initializes the partition and performs an initial program
load of the partition.
7848 4078–004

Installing the Basic OS 2200 IOE
9. Press the F4 key to change to the System Operations session. The following
message is displayed:
n Modify config. then answer: DONE
10. Before continuing the boot process, determine the current state of peripheral
devices by entering appropriate facility status (fs) keyins. For example, check the
status of all mass storage devices with the following keyin:
fs,ms
11. Use the UP or DN keyin to set devices to the state you want for the partition.
12. When done, end modification of the configuration by entering the following:
n DONE
where n is the number of the Modify config message requiring a response.
In response to that message, the following message appears:
n are you sure you want JK 13 set? Answer Y or N
13. Enter Y to confirm that you want to perform an initial boot:
n Y
Messages appear indicating the number of fixed mass storage disks that are up. You
must bring down disks that should not be up.
Caution
Once you continue with the boot, you cannot bring down any fixed mass storage
devices without a reboot. Be sure the correct disks are up before proceeding.
14. Enter the following to continue with the boot:
n go
You are prompted to enter the master account number.
n ENTER MASTER ACCOUNT
15. Enter 0 (zero) as the master account number.
n 0
You are prompted to enter the security officer user-id.
n ENTER SECURITY OFFICER ID
7848 4078–004 8–7

Installing the Basic OS 2200 IOE
8–8
16. Enter security as the default security officer user-id as follows:
n security
17. Several messages are displayed (both read-only and read-and-reply), concluding
with the following message:
n SPECIFY METHOD TO OBTAIN SECURITY FILES--LOAD, INITIALIZE (L,I)
18. Enter I to initialize security files and press Enter. For example:
n I
Other messages appear. Initial boot is finished when the following message appears:
SYS FIN
Continue installation with the procedures in 8.3.
8.3. Installing Products from Fast-Load Tape
CPIX-OE1
Note: Although Interactive Processing Facility (IPF 1100) is installed from
fast-load tape CPIX-OE1, it cannot be used in full screen mode until Display
Processing System (DPS 2200) is installed. If the site needs to use IPF 1100
in full screen mode, DPS 2200 should be installed from either fast-load tape
CPIX-OE2 or package tape CPIX12 (see Section 10) after hardware RFU.
The IOE products on tape CPIX-OE1 (single reel or two-reel set) are installed in default
mode. Once OS 2200 is initialized (see 8.2), take the following steps to install these
products:
1. Enter the following command to start the installation runstream:
ST INSTALLIOE
You are prompted to enter the reel number for the reel or reels you are loading:
INSIOE START
n INSTALLIOE: Enter reel number
n CPOE1A/CPOE1B,TJ,HICL
2. Because the tape or tapes are unlabeled, you can enter any reel number. In this
example, CPIX-OE1 is on a two-reel set so you must enter two reel numbers
separated by a slash character. Other parameters assign the tape as a temporary file
and indicate that it is unlabeled (TJ) and indicate the tape device type (for example,
HICL or HIC51).
7848 4078–004

The runstream now
Installs SOLAR
Installing the Basic OS 2200 IOE
Installs IOE products from the CPIX-OE1 tape or tapes in an order so that
dependencies are met
Registers the products with SOLAR
The following messages appear:
LOAD CPOE1A T40A12 TAPE$ – 1 INSIOE
(LOAD CPOE1A )(ANY UNASSIGNED CT0899 )
n ANSWER WITH REEL NUMBER ON T40A12 E,REEL
n CPOE1A
3. Enter the reel number of the tape reel (the first reel if a two-reel set) to confirm that
the unlabeled tape reel you mounted is the one you intended to mount. If a two-reel
set, you then are prompted to confirm the second reel number.
LOAD CPOE1B T40A12 TAPE$ – 1 INSIOE
(LOAD CPOE1B )(ANY UNASSIGNED CT0899 )
n ANSWER WITH REEL NUMBER ON T40A12 E,REEL
n CPOE1B
4. If appropriate, enter the reel number of the second tape reel to confirm that the
unlabeled tape reel you mounted is the one you intended to mount.
Messages appear indicating that the installation has started.
Note: You can ignore the warning message that appears relating to installation
of an IPF component at this time. The Interactive Processing Facility
(IPF 1100) can be configured after installation. Configuration
instructions are in the IPF 1100 Administration Guide.
INSIOE*MSG: STARTING THE INSTALL OF THE CLEARPATH IOE PRODUCTS
INSIOE*A warning or error has occurred–see the diag file for details.
INSIOE*MSG: THE INSTALL OF THE CLEARPATH IOE PRODUCTS COMPLETED CORRECTLY
INSIOE*MSG: STARTING THE REGISTER OF THE CLEARPATH IOE TAPES
LOAD CPOE1A T40A12 TAPE$ – 1 INSIOE
(LOAD CPOE1A )(ANY UNASSIGNED CT0899 )
If CPIX-OE1 is on a two-reel set, you are prompted to mount the first tape a second
time to register the products with SOLAR.
n ANSWER WITH REEL NUMBER ON T40A12 E,REEL
n CPOE1A
INSIOE*MSG: THE REGISTER HAS BEEN COMPLETED CORRECTLY
INSIOE FIN
The INSOE FIN message indicates that the runstream has finished.
IX4600 or IX4800 sites now must establish the contracted System Controlled
Performance level as described in 8.4. All sites must verify that the hardware is ready
for use by performing the communication tests described in Section 9.
7848 4078–004 8–9

Installing the Basic OS 2200 IOE
8.4. Establishing the Performance Level
(IX4600 and IX4800)
8–10
For an IX4600 or IX4800 you should establish the System Controlled Performance (SCP)
contracted performance level as soon as possible after SOLAR is installed (refer to
Appendix B for an overview of SCP).
The 2200 node runs at 100 percent performance until SOLAR creates the SYS$*DATA$
file during installation. After that, until you register your contracted performance level,
it runs at the default performance level (11 percent) and a console message is issued
every 5 minute time and date interval stating that the system is running with the SCP
default performance value.
Using SOLAR, you must register the Exec key tape included in the system packaging
(labeled “System Controlled Performance Key Tape”). Optionally, a new or replacement
Exec key may be provided in a file for registering from disk.
The Exec key tape or file contains encrypted fields for the system serial number, model
number, number of IPs, performance level, and expiration date (optional). The Exec key
tape or file is valid only for the system with a cabinet serial number that matches the
Exec key serial number. Both the cabinet and Exec key tape have labels identifying the
Manufacturing Cabinet Number (MCN).
The process for registering the tape is as follows:
1. Start the runstream for registering the key tape by entering the following command:
ST SYS$LIB$*SOLAR.REGISTERPKG
Note: The ST REGISTERPKG command optionally can be used when staging
systems at the factory.
The following messages appear:
REGPKG START
n Register package from or DISK?
n
2. Press transmit to select the default location of the key tape. A prompt asks for entry
of the reel number from which the key is to be installed.
n Enter reel number
n SCPKEY,TJ,HICL
7848 4078–004

Installing the Basic OS 2200 IOE
3. Because the tape is unlabeled, enter any reel number. Also enter the parameters to
indicate that the tape is to be assigned as a temporary file, that it is unlabeled, and
that indicate the device type on which it is to be mounted (for example, HICL or
HIC51).
The following message is displayed:
n Enter reel number
n
4. Press transmit to select the default and mount the key tape in the specified drive.
Loading begins, and you are prompted to verify that the unlabeled tape you mounted
is the correct reel.
LOAD SCPKEY T40Z0 NORING PP$TAPE – 1 REGPKG
(LOAD SCPKEY )(ANY UNASSIGNED CT0899 )
n ANSWER WITH REEL NO ON T40Z0 E,REEL
n SCPKEY
The following messages appear indicating that the key tape is registered:
REGPKG FIN
Model Number - IX4802-2 Performance level - 100%
Note: The model number message does not appear if an Exec key tape or file
registration problem is encountered such as a registration number that
does not match a previous installation or a registration expiration date
that has passed.
You only need to register the Exec key tape or file once because the data is stored in the
SOLAR SYS$*DATA$ file for recovery boots and a backup copy is written by the Exec to
the disk-resident system (DRS) device. The SCP data recovery first tries the
SYS$*DATA$ file and alternately the DRS device. The DRS device SCP data is used if a
SYS$*DATA$ file does not exist or an Exec key tape was never registered. An initial
boot does not destroy the SCP data on the DRS device.
7848 4078–004 8–11

Section 9
Verifying Interconnect
Communications
Following installation of OS 2200 software from fast-load tape CPIX-OE1, you must
verify that the 2200 and Intel nodes can communicate via the internal interconnect.
Once you have tested interconnect communication, the ClearPath IX server is
considered hardware ready for use (RFU) (9.5).
The steps for verifying interconnect communications are:
1. Depending on communications controller model, install microcode as follows:
For servers with a Host LAN Controller-2, install microcode as described in 9.1.
For servers with a channel service I/O processor (CSIOP), install channel
adapter microcode as described in 9.2.
2. Install the CEC tape that contains the “ping” test for verifying communications (9.3).
3. Test interconnect communications to determine whether the hardware is ready for
use (9.4).
9.1. Installing HLC2 Microcode
A cartridge tape containing microcode is included in the HLC2-FMK package that comes
with the HLC2. To install the microcode, take the following steps:
1. Enter the following command at the 2200 node system console:
ST INSTALLPKG
2. A run (run-id INSPKG) starts and asks the following question:
Install from , DISK, or RSS?
3. Press Enter to use the tape default. You are prompted to enter the reel number.
n INSPKG*Enter reel number
n HLC2M,TJ,HICL
7848 4078–004 9–1

Verifying Interconnect Communications
9–2
4. Because the tape is unlabeled, you can enter any reel number. Also enter the
parameters to indicate that the tape is to be assigned as a temporary file, that it is
unlabeled, and to indicate the device type on which the tape is to be mounted (for
example, HICL or HIC51).
You are asked whether you want to install using default modes.
n Install default modes? /N
n N
5. Enter no (N) and press Enter. You are prompted to enter the product name.
n Enter product name, transmit if complete
n HLC2–MCODE
6. Enter the name HLC2-MCODE (found on the tape label) and press Enter. You are
prompted to enter the product level.
n Enter product level
n level
7. Enter level (where level is the product level identified on the tape label) and press
Enter. You are prompted for the product mode.
n Enter product mode
n FDDI
8. Enter FDDI as the product mode and press Enter. You are again prompted for the
product name.
n Enter product name, transmit if complete
n HLC2–MCODE
9. Enter the name HLC2-MCODE (found on the tape label) and press Enter. You are
prompted to enter the product level.
n Enter product level
n level
10. Enter level (where level is the product level identified on the tape label) and press
Enter. You are prompted for the product mode.
n Enter product mode
n ETHER
11. Enter ETHER as the product mode and press Enter. You are again prompted for the
product name.
n Enter product name, transmit if complete
7848 4078–004

Verifying Interconnect Communications
12. Press Enter (transmit) to indicate that you are done. Loading begins, and you are
prompted to verify that the unlabeled tape you mounted is the correct reel.
LOAD HLC2M T40Z0 NORING PP$TAPE – 1 INSPKK
(LOAD HLC2M )(ANY UNASSIGNED CT0899 )
n ANSWER WITH REEL NO ON T40Z0 E,REEL
n HLC2M
The following message indicates when the run is finished:
INSPKK FIN
When CMS 1100 is started, it detects the new microcode level and automatically loads
the microcode into the HLC2.
9.2. Installing Channel Adapter Microcode (CSIOP)
To enable CSIOP communications, you must install Ethernet and FDDI channel adapter
(CA) production mode microcode into the CAs.
To install the microcode from the FDDI/Ethernet CA-MCODE tape, take the following
steps:
1. Enter the following command at the 2200 node system console:
ST INSTALLPKG
2. A run (run-id INSPKG) starts and asks the following question:
Install from , DISK, or RSS?
3. Press Enter to use the tape default. You are prompted to enter the reel number.
n INSPKG*Enter reel number
n CACODE,TJ,HICL
4. Because the tape is unlabeled, you can enter any reel number. Also enter the
parameters to indicate that the tape is to be assigned as a temporary file, that it is
unlabeled, and to indicate the device type on which the tape is to be mounted (for
example, HICL or HIC51).
You are asked whether you want to install using default modes.
n Install default modes? /N
n N
5. Enter no (N) and press Enter. You are prompted to enter the product name.
n Enter product name, transmit if complete
n CA–MCODE
7848 4078–004 9–3

Verifying Interconnect Communications
9–4
6. Enter the name CA-MCODE (found on the tape label) and press Enter. You are
prompted to enter the product level.
n Enter product level
n level
7. Enter level (where level is the product level identified on the tape label) and press
Enter. You are prompted for the product mode.
n Enter product mode
n FDDI
8. Enter FDDI as the product mode and press Enter. You are again prompted for the
product name.
n Enter product name, transmit if complete
n CA–MCODE
9. Enter the name CA-MCODE (found on the tape label) and press Enter. You are
prompted to enter the product level.
n Enter product level
n level
10. Enter level (where level is the product level identified on the tape label) and press
Enter. You are prompted for the product mode.
n Enter product mode
n ETHER
11. Enter ETHER as the product mode and press Enter. You are again prompted for the
product name.
n Enter product name, transmit if complete
12. Press Enter (transmit) to indicate that you are done. Loading begins, and you are
prompted to verify that the unlabeled tape you mounted is the correct reel.
LOAD CACODE T40Z0 NORING PP$TAPE – 1 INSPKK
(LOAD CACODE )(ANY UNASSIGNED CT0899 )
n ANSWER WITH REEL NO ON T40Z0 E,REEL
n CACODE
The following console message indicates when the run is finished.
INSPKG FIN
When CMS 1100 is started, it detects the new microcode level and automatically loads
the microcode into the CA.
7848 4078–004

9.3. Installing the CEC Tape
Verifying Interconnect Communications
The CEC tape provided with the plateau includes a test (PING-RUN) that you can run to
verify communications at the 2200 node. The CEC tape you have depends on the model
being installed as follows:
Model IX4400—CEC500 tape (minimum level of 1R8)
Model IX4600 or IX4800—CC3000 tape (minimum level of 1R1)
Note: Examples shown in this subsection illustrate use of the CEC500 tape.
1. Enter the following command at the system console:
ST INSTALLPKG
2. A run (run-id INSPKG) starts and the following messages appear:
INSPKG START
n Install from , DISK, or RSS?
3. Press Enter to use the tape default. You are prompted to enter the reel number.
n INSPKG*Enter reel number
n CEC500,TJ,HICL
4. Because the tape is unlabeled, you can enter any reel number (for example, CEC500)
and parameters to indicate that the tape is to be assigned as a temporary file (T),
that it is unlabeled (J), and to indicate the device type on which the tape is to be
mounted (for example, HICL or HIC51).
Following that entry, you are asked whether you want to install using default modes.
n Install default modes? /N
n
5. Press Enter to install using the default modes. You are prompted to verify that the
unlabeled tape you mounted is the correct reel.
LOAD CEC500 T40Z0 NORING PP$TAPE – 1 REGPKG
(LOAD CEC500) (ANY UNASSIGNED CT0899)
n ANSWER WITH REEL NO ON T40Z0 E,REEL
n CEC500
The tape is installed when the following message appears:
INSPKG FIN
Note: At this time the Diagnostic Software Peripheral Equipment Routines
(DSPER) tape also should be installed as described in the DSPER Definition
Reference Manual.
7848 4078–004 9–5

Verifying Interconnect Communications
9.4. Testing Interconnect Communications
9–6
The interconnect communications test uses the CMS 1100-based verification run
(PING-RUN) that was previously installed from the CEC tape.
To run the interconnect test, take the following steps:
1. Access an OS 2200 console session at either the SPO X terminal or at the monitor
concentrator.
2. Enter the following console keyin to start the interconnect test:
ST PING-RUN
Messages similar to the following appear to indicate that CMS 1100 has access to the
LAN:
CONFIGURATION ERRORS(0) WARNINGS(0)
LAN FDDIVI FDDI HLC IS USING MICROCODE LEVEL 006.52
LAN FDDIVI MAC ADDRESS = 02E6D3070058
3. At the Intel node, log on as follows:
If running UNIX, log on as superuser at a UNIX console session, if not already
logged on (5.6).
If running Windows NT, log on as administrator, if not already logged on(4.6),
and start an MS-DOS session.
4. Type the following command, then press Enter:
ping fddi22sr
The following message should appear in response:
fddi22sr is alive
The connection is not operational if the following message appears:
no answer from fddi22sr
9.5. Hardware Ready for Use (RFU)
Once the interconnect communication test has been performed as described in 9.4, the
ClearPath IX server is considered hardware ready for use (RFU). The site can now
Customize the CMS 1100 configuration to meet their needs as described in 2.6
Test TCP/IP communications and install remaining IOE products and optional
products from package tapes as described in Section 10.
7848 4078–004

Section 10
Installing the Remaining IOE
Following hardware RFU, the CSE turns the ClearPath IX server over to the site. Site
personnel must install the remaining IOE software as described in this section, then
customize the site to their requirements as described in Section 11.
The following remaining IOE software products must be installed:
Open Programming Environment (OPE) and SysAdmin (10.1)
PathMate (10.2)
Other products on fast-load tapes CPIX-OE2 and CPIX-UDS3 (10.3).
Unisys Repository Manager (UREP) Workstation (10.4)
Open Application Development Environment (OADE) for Windows (10.5)
TeamQuest Online (10.6)
Sites with UNIX installed on the Intel node also may install
− Enterprise Backup and Restore (EBRS) (10.7)
− Remaining UNIX IOE products (10.8)
10.1. Installing OPE and SysAdmin
OPE and SysAdmin are part of the standard IOE software package. OPE is installed on
the 2200 node, and provides the UNIX environment and basic open services needed by
SysAdmin.
SOLAR installation of the OPE tape provides both the OPE and SysAdmin products.
Each of those products requires its own installation and setup procedures as described
in the following documents:
Open Programming Environment (OPE) Configuration Guide
SysAdmin Administration Guide
The system administration procedures provided by SysAdmin require that the OPE
CERN Web Server be initialized following the documented setup procedures.
To use the Network File System (NFS) features provided by OPE, the site must update
the /etc/hosts file of OPE as follows:
The 2200 node must be given the alias name “localhost.”
7848 4078–004 10–1

Installing the Remaining IOE
10–2
The 2200 node host name must match the name displayed by the OPE uname-n
command.
The internet address for “localhost” must match the internet address in the
CMS 1100 configuration file.
Entries must be added for any remote systems that will be accessed as NFS clients.
After updating the /etc/hosts file, normal NFS administrative tasks can be performed.
10.2. Installing PathMate Software
Note: Before installing PathMate software, you must install Dynatext
documentation files from CD-ROM. For instructions, refer to the jewel case
insert in the CD-ROM labeled “ClearPath HMP IX Series Product Information
CD-ROM.”
Caution
To use the configuration tools of PathMate, the site must install a CMS 1100
configuration on the 2200 node that matches the site’s communications network
and that includes at least one TCP/IP path to the 2200 node.
After installing OPE and SysAdmin (10.1), the site can install PathMate software and
online documentation from the PathMate for ClearPath HMP IX Series with UNIX
CD-ROM (7848 4441).
Follow the instructions in the jewel case insert booklet. If the jewel case insert booklet
is not available—or for instructions on installing the Win32S subsystem if
needed—access the README file on the CD-ROM.
PathMate software is installed in a program group, as shown in Figure 10–1. Use the
PathMate object to execute PathMate and learn about its configuration aides and
solutions for business problems.
Except for the Readme and Uninstall objects, do not execute the other objects in the
group until you are familiar with them from the PathMate documentation.
The PathMate object opens the PathMate documentation, which is a conventional
WinHelp application. The contents include introductory information, overviews for
categories of solutions, and detailed procedures and processes. See the jewel case
insert booklet for more information.
See 11.1 for an overview of PathMate.
7848 4078–004

Installing the Remaining IOE
Figure 10–1. PathMate Program Group in Windows 95 Environment
10.3. Installing Default UDS Application Group 3
from Fast-Load Tapes
Fast-load tape CPIX-OE2 and fast-load tape CPIX-UDS3 are provided to allow you to
rapidly install a default UDS application group 3. Contents of those tapes are as follows:
Tape CPIX-OE2 (see Table 10–1)—Products TIPUTIL, MCB, and DPS that you may
or may not need to reconfigure to your particular needs. To reconfigure these
products, you must install and build them from the package tapes.
Tape CPIX-UDS3 (see Table 10–2)—UDS products in absolute format. UDS
products must be built and installed from the package tapes to customize the UDS
installation or to configure additional applications.
Table 10–1. Tape CPIX-OE2 Fast-Load Tape Contents
Product Full Name
DPS 2200 Display Processing System 2200
MCB Message Control Bank
TIPUTIL Transaction Processing Utilities
7848 4078–004 10–3

Installing the Remaining IOE
10–4
Table 10–2. Tape CPIX-UDS3 Fast-Load Tape Contents
Product Full Name
DMSSUB Data Management System (DMS 2200) subsystem
RRDMSSUB Relational Data Management System (RDMS 2200) subsystem
SFS 2200 Shared File System
UDS Control Universal Data System (UDS) Control
UREPSUB Unisys Repository Manager subsystem
This subsection describes how to
1. Install TIPUTIL, MCB, and DPS from fast-load tape CPIX-OE2 (10.3.1)
2. Set up the TIP environment (10.3.2)
3. Set up application group 3 (10.3.3)
4. Install UDS application 3 from fast-load tape CPIX-UDS3 (10.3.4)
10.3.1. Installing TIPUTIL, MCB, and DPS from Fast-Load
Tape CPIX-OE2
Note: The runstream used to install TIPUTIL, MCB, and DPS (INSTALLPKG) is a
generic runstream used to install products from tape. This same runstream
can be used to install optional products from package tapes.
The tape CPIX-OE2 contains products (TIPUTIL, MCB, and DPS) that may or may not
need to be configured to your particular needs. Use the INSTALLPKG runstream to
install those products in default mode as follows:
1. Enter the following command to start the installation runstream:
ST INSTALLPKG
You are prompted to select the installation source.
INSPKG START
n–INSPKG*Install from , DISK, or RSS?
2. Enter the default to select TAPE as the source. You are prompted to enter the reel
number.
n–INSPKG*Enter reel number
7848 4078–004

Installing the Remaining IOE
3. Because the tape is unlabeled, you can enter any reel number. Also enter the
parameters to indicate that the tape is to be assigned as a temporary file, that it is
unlabeled, and that it is mounted on device type HICL. For example:
n CPOE2,TJ,HICL
In response, you are asked whether the installation is in default mode.
0–INSPKG*Install default modes? /N
4. Enter yes (Y), the default, to choose default mode and mount the tape in the tape
drive. Informative messages appear as products are loaded from the tape.
LOAD CPOE2 T40A12 NORING PP$TAPE – 1 INSPKG
(LOAD CPOE2 )(ANY UNASSIGNED CT0899 )
INSPKG FIN
The INSPKG FIN message indicates that the runstream has finished. Proceed with
setting up the TIP environment as described in the next subsection.
10.3.2. Setting Up the TIP Environment
Immediately after installing TIPUTIL, MCB, and DPS from fast-load tape CPIX-OE2,
take the following steps to set up the TIP environment prior to bringing up application
group 3:
1. Enter the following command:
TIP UP
Messages appear indicating that TIP automatic recovery is up. This begins recording
of TIP activities.
*TIP* ARF$00 - TIP AUTOMATIC RECOVERY IS UP
.
.
2. Enter the following command to start the runstream that initializes TIP for use:
ST TIPINIT
This runstream does the following:
Creates SUPUR file 1000
Does the VALBLD of VALTAB 9 for the application group 3 error notification
program (ENP)
Copies the absolute for the MCB3 example ENP into the SUPUR file
7848 4078–004 10–5

Installing the Remaining IOE
10–6
The following messages appear:
TIPINT START
TIPINT*MSG: CREATE VALTAB ENTRIES
RECOVERY OFF TIPINT
SCHEDULE OFF TIPINT
STICKING ON TIPINT
RECOVERY ON TIPINT
*TIP* VINDEX BANK LOADED – TIP SCHEDULING ON
USER KONS INITIALIZED
TIPINT*MSG: CAT/TREG/RES TIP SUPUR FILE 1000
TIPINT FIN
The TIPINT FIN message indicates that the runstream has finished. Proceed with
setting up application group 3 as described in the next subsection.
10.3.3. Setting Up Application Group 3
To set up application group 3 so that the UDS tape can be installed, take the following
steps:
1. Application group 3 must be up to start this procedure. Take the following steps to
check its state:
a. Enter the following command:
AP 3 FS
The following message should be returned to indicate that IRU short recovery is
pending (“PND”) and is in the “INIT” recovery state:
APP 3 RCV 0% IRU:PND REC: INIT
b. If a message indicates that application group 3 is not in the correct recovery
state, enter the following commands:
AP 3 DN
AP 3 UP INIT
2. Enter the following command to start the runstream to set up application group 3:
ST AP3SETUP
This runstream does the following to perform an IRU short recovery of application
group 3 (required to set up the application group):
Creates rollback page file to TIP file 301
Adds the MCBSETUP3 runstream
Sets up the IRU history file for application group 3
Adds the IRU3 runstream to short recover application group 3
7848 4078–004

Messages appear and you are prompted to open an audit trail.
Installing the Remaining IOE
Note: The common bank error messages appear as a result of UDS products not
yet being installed when IRU short recovers application group 3 during
the initial set up. Application group 3 must be up and short recovered
when UDS is initially installed (11.2).
SETUP3 START
SETUP3*MSG: CREATE ROLLBACK PAGE FILE FOR APP3
SETUP3*MCB File Setup 8R1A 8R1A (A3)
SETUP3*(940914 1100:56) 1996 May 30 Thu 1103:14
SETUP3*MCB IRU Setup 8R1A 8R1A (A3)
SETUP3*(940914 1101:16) 1996 May 30 Thu 1103:15
SETUP3*MSG: CREATE IRU HISTORY FOR APP 3
SETUP3*MSG: PERFORMING A SHORT RECOVERY OF UDSSRC
Common bank error 9 . –0–>
–0–> common bank ” UNDETERMINED ” with bdi 400665 –0–>
–0–> referenced by run–id ” SETUP3 ” is not installed.
Common bank error 9. bdi 400665 not found –0–>
–0–> in omnibus element BANK–BDI$
–0–> in file SYS$*LIB$(1) .
SETUP3*App 3 Init of MCB complete
APP 3 ROLLBACK INITIALIZATION STARTED
APP 3 ROLLBACK INITIALIZATION COMPLETE
SETUP3**WARNING* 5807 App 3 UDS is not configured
SETUP3*App 3 AOR phase not required
0–EXEC 8 REQUIRES AUDIT TRAIL: 3 ANS. OP, E, OR DN
3. Open an audit trail by making the following entry:
0 OP
More messages appear. The SETUP3 FIN message indicates that the runstream has
finished.
AT 3 ACI$03(1) *FILE ASSIGNED* 1103:18
AT 3 L1 FIX(1,1) *OPEN* 1103:19
AT 3 L1 BLK 1 TBSN 0 1103:19
AT 3 OP
APP 3 RESTARTED
SETUP3*App 3 short recovery complete
AT 3 S1 FIX(2,2) *SPARE* 1103:19
SETUP3 FIN
After the SETUP3 FIN message appears, proceed with installing UDS application group 3
as described in the next subsection.
7848 4078–004 10–7

Installing the Remaining IOE
10.3.4. Installing UDS Application Group 3 from Fast-Load Tape
CPIX-UDS3
10–8
After application 3 has been set up, you can take the following steps to install the default
UDS application group 3 from fast-load tape CPIX-UDS3:
1. Enter the following command to start MCB:
ST MCB3
MCB initialization messages appear as follows:
MCB3 START
MCB3 *MCB 8R1A 8R1A (A3)
MCB3 *(940914 1058:42) 1996 May 30 Thu 1103:37
MCB3 *MCB INITIALIZATION COMPLETE 96/05/30 1103:40
2. Enter the following command to start the runstream that installs UDS application
group 3:
ST INSTALLAPP3
That runstream installs and registers the following products from the CPIX-UDS3
tape.
Database Management System (DMS 2200)
Relational Data Management System (RDMS 2200)
Shared File System (SFS 2200)
Universal Data System Control (UDSC)
Unisys Repository Manager (UREP)
Messages appear and you are prompted to enter a reel number:
INAP3 START
n–INAP3 *INSTALLAPP3: Enter reel number
3. Because the tape is unlabeled, you can enter any reel number. Also enter the
parameters to indicate that the tape is to be assigned as a temporary file, that it is
unlabeled, and that it is mounted on device type HICL. For example:
n CPOA3,TJ,HICL
Several message are displayed as follows:
LOAD CPOA3 T40A13 TAPE$ – 1 INAP3
(LOAD CPOA3 )(ANY UNASSIGNED CT0899 )
INAP3*MSG: STARTING THE INSTALL OF THE UDS PRODUCTS FOR APP3
INAP3*MSG: INSTALLING UDSC
INAP3 *
INAP3 *UDSC install processing could not assign the ADT–FILE.
INAP3 *It is assumed that the SYS–FILE for this application
INAP3 *group does not exist. UDSC will not attempt to free
7848 4078–004

INAP3 *the SYS–FILE from the UDS domain.
INAP3 *
INAP3 *
Installing the Remaining IOE
INAP3 **INFO* UDSC
INAP3 *File UDS$$SRC*ADT–FILE has been initialized by this
INAP3 *Solar PRODLD of the UDSC default application.
INAP3 *
INAP3 *
INAP3 **INFO* UDSC
INAP3 *File UDS$$SRC*SYS–FILE has been initialized by this
INAP3 *Solar PRODLD of the UDSC default application.
INAP3 *
INAP3 *
INAP3 **INFO* UDSC
INAP3 *The following files have been cataloged during this
INAP3 *Solar PRODLD of the UDSC default application.
INAP3 *
INAP3 * STD#UDS$$SRC*ADT–FILE
INAP3 * UDS$$SRC*SYS–FILE
INAP3*MSG: THE INSTALLATION OF UDSC APP3 COMPLETED CORRECTLY
INAP3*MSG: INSTALLING RDMS
INAP3*MSG: THE INSTALLATION OF RDMS APP3 COMPLETED CORRECTLY
INAP3*MSG: INSTALLING DMS
INAP3*MSG: THE INSTALLATION OF DMS APP3 COMPLETED CORRECTLY
INAP3*MSG: INSTALLING UREP
INAP3 MAX TIME
INAP3 *IRU history file – UDSSRC*IRU$HF – has been initialized
INAP3 MAX PAGES
INAP3 MAX TIME
INAP3*MSG: THE INSTALLATION OF UREP APP3 COMPLETED CORRECTLY
INAP3*MSG: INSTALLING SFS
INAP3*MSG: THE INSTALLATION OF SFS APP3 COMPLETED CORRECTLY
INAP3*MSG: STARTING THE REGISTER OF THE UDS APP3 TAPE
INAP3*MSG: THE REGISTER OF THE UDS APP3 PACKAGE COMPLETED CORRECTLY
INAP3 FIN
The INAP3 FIN message indicates that the runstream has finished.
7848 4078–004 10–9

Installing the Remaining IOE
10.4. Installing UREP Workstation
10–10
UREP Workstation is installed according to procedures described in the UREP-WS End
Use Guide.
10.5. Installing OADE
OADE is installed according to procedures described in the Open Application
Development Environment (OADE) for Windows User Guide.
10.6. Installing TeamQuest Online
TeamQuest Online can be installed from the package tape (see 11.2) using procedures
described in the TeamQuest Baseline and TeamQuest Online Administration and End
Use Reference Manual. Optionally, TeamQuest Baseline can be installed from the
package tape if authorized for the site.
10.7. Installing EBRS (UNIX on Intel Node Only)
EBRS software consists of host (2200 node), server (UNIX node), and workstation
(Windows workstation) modules. Each module requires its own installation procedures
as described in the following documents:
2200 node—Enterprise Backup and Restore Host Installation Guide
UNIX node—Enterprise Backup and Restore UNIX Server Installation and
Operations Guide for Windows
Windows workstation—Enterprise Backup and Restore DOS/Windows Installation
and Operations Guide
See Enterprise Backup and Restore Capabilities Overview for introductory information
about EBRS.
7848 4078–004

Installing the Remaining IOE
10.8. Installing Remaining UNIX IOE Products
The following UNIX IOE products remain to be installed after hardware RFU:
Unisys UNIX Internet Package (UUIP)
Web Transaction Enabler (WebTX)
Install those products according to procedures in 10.8.1 and 10.8.2. Installation of
optional UNIX products is described in Section 11.
10.8.1. Installing UUIP
Install UUIP following hardware RFU according to instructions in the Web Servers User’s
Guide.
10.8.2. Installing WebTX
The WebTX User’s Guide is an online help system that can be viewed with any Web
browser. That document cannot be used until a Web server is installed to view it as
described in the SysAdmin Administration Guide.
After installing the Web servers, install WebTX according to the following procedure:
1. Put the cartridge tape containing WebTX (labeled “Web Transaction Enabler for
SVR4 UNIX”) in the drive unit.
2. If you are not already logged on, log on to the UNIX node as root (superuser)
(see 6.4).
3. Type the following command and press Enter:
pkgadd WebTx –d /dev/rmt/tape_device_name
where tape_device_name is the name of the tape device you are using
(for example, c0s0)
Files are copied from the installation media into the directory /opt/WebTx.
7848 4078–004 10–11

Section 11
Site Customization
After installing the remaining IOE (Section 10), the site must
Use PathMate to configure other software (11.1).
Install optional OS 2200 software from package tapes (11.2).
Customize SPO/HMP Console configurations with site-specific names (11.3).
Test TCP/IP communications (11.4).
Install remaining UNIX optional software products (if applicable) (11.5).
In addition, other steps not described in this guide can be taken. For example, the
default OS 2200 Exec configuration was designed to provide an acceptable level of
functionality. Sites could tune or regenerate the Exec using procedures described in the
Exec Installation and Configuration Guide.
11.1. Using PathMate
Once PathMate has been installed and an appopriate CMS 1100 configuration established
(10.2), sites can use PathMate to customize the installation to meet their requirements.
PathMate solutions are organized by categories. For each category, an overview topic
identifies business problems and offers a solution for each problem.
One of the first uses of PathMate is to help configure the following software for the site:
CMS 1100
TransIT Open/OLTP (OLTP–TM2200)
Open Programming Environment (OPE)
DEPCON 2200
DEPCON PC
UniAccess ODBC
7848 4078–004 11–1

Site Customization
11–2
For other business problems, PathMate provides assistance ranging from totally
automated services to step-by-step instructions. Capabilities include
Intrinsic capabilities—Fully automated solutions are provided. An example is basic
print management for ClearPath IX servers.
Tools—Single-purpose applications are provided to help manage integrated
technologies. For example, a configuration utility creates basic configurations to get
ClearPath IX server software up and running.
Templates—Overall structures are provided that sites can customize. An example is
the sample Excel macro for accepting OS 2200 application output.
Demonstrations—These provide ideas or techniques that can be used to develop a
similar solution. An example is creating a distributed transaction between the UNIX
and OS 2200 environments.
How to—Instructions, explanations, and background information are centralized
and summarized for several tasks. References to product documentation are
provided if more detailed information is needed. An example is the process for
designing OLTP applications.
The introductory overview describes the kinds of problems and solutions in each
category. The overview for each category describes the problems and solutions in more
detail and links directly to the appropriate process or procedure.
Because PathMate is self-documenting, the best way to use it is to install it as described
in Section 10 and explore its capabilities.
11.2. Installing Optional OS 2200 Software from the
Package Tapes
Table 11–1 lists the products available on keyed package tapes. The installation status of
each product on the package tape is identified in Table 11–1 in the Fast Load? column as
follows:
Check mark ()—Indicates the product has already been installed from fast-load
tape CPIX-OE1 in preparation for hardware RFU. The product does not need to be
reinstalled unless you wish to customize it in some way.
CPIX-OE2—Indicates that the product may already have been installed from
fast-load tape CPIX-OE2 (see 10.3).
CPIX-UDS3—indicates that the product may have been installed from fast-load tape
CPIX-UDS3 (see 10.3).
Asterisk (*)—Indicates TeamQuest Online is a remaining OS 2200 IOE product that
can be installed from package tape.
Note: Products are listed in alphabetical order, not in the order they are stored on
tape.
7848 4078–004

Cautions
Site Customization
Products marked by a check mark () in Table 11–1 have already been
installed. Do not reinstall unless you are customizing the installation.
When reinstalling products, do not attempt to install them in package tape
numerical order. Products must be installed in an order described in the
OS 2200 System Base Software Planning and Migration Overview.
Install optional products according to procedures described in the following documents:
Software Products Installation Guide
System Base Software Planning and Migration Overview.
Individual product documentation (for example, the UDS Planning and Migration
Overview).
Because keys are needed to install products from the package tapes, you must register
the key tape (labeled “KEYTAPE”) as described in 11.2.1 before attempting to install a
product from the package tape. An example showing installation of an optional product
(ASCII COBOL) is shown in 11.2.2.
Table 11–1. Package Tape Contents
Tape Name Product Full Name Fast Load?
CPIX01 COMUS COMUS
FURPUR File Utility Routines/Program Utility
Routines
PCFP Program-Callable FURPUR
SOLAR Software Library Administrator
CPIX02 CML Common Mathematical Library
ED ED
ELT Element Processor
LIST LIST Processor
MAP Processor Collector
MASM Meta-Assembler
PDP Procedure Definition Processor
RSS Remote System Support
7848 4078–004 11–3
continued

Site Customization
11–4
Table 11–1. Package Tape Contents (cont.)
Tape Name Product
Full Name
Fast Load?
SLIB Service Library
SSG Symbolic Stream Generator
SYSLIB System Service Routines Library
UCSRTS Universal Compiling System Run Time
System
URTS Universal Compiling System (UCS)
Runtime System
CPIX03 ELMS Extended Language Message System
LINK Linking System
CPIX04 CMR Console Message Redisplay
CMS1100 Communications Management System
1100
DAP Dump Analysis Processor
DPREP1100 DPREP1100
FAS File Administration System
MSCP Monitor Services Control Program
PMD Postmortem Dump
ROLRUNS Roll-Out/Roll-Back Runstream
CPIX05 CKRS Checkpoint/Restart
CULL Cross Reference Generator
DMPLIB DMPLIB
IACULL Interactive CULL
LA Log Analyzer
MSAR Mass Storage Analysis Relocation
Processor
MSManager Mass Storage Manager
OSAM Online System Activity Monitor
PADS Programmer’s Advanced Debugging
System
continued
7848 4078–004

Table 11–1. Package Tape Contents (cont.)
Site Customization
Tape Name Product
Full Name
Fast Load?
ROBOHST2 RoboHost 22
SA Utilities Site Administration Utilities
SIMAN Site Management Complex
CPIX06 LSS Universal Compiling System (UCS)
Language Support System
CPIX07 FLIT Fault Location by Interpretive Testing
PAR Performance Analysis Routines
PLUS PLUS
UC Universal Compiling System (UCS) C
CPIX08 UCOB Universal Compiling System (UCS) COBOL
Compiler
UFTN Universal Compiling System (UCS)
FORTRAN
UPLS Universal Compiling System (UCS) PLUS
CPIX09 ACOB ASCII COBOL Compiler
Expipe Expipe
FTN ASCII FORTRAN Compiler
PCIOS Processor Common Input/Output System
2200POSIX-1 Portable Operating System Interface
2200POSIX-2 Portable Operating System Interface
SMART SMART
SORT Sort/Merge Utility
CPIX10 cpFTP Cooperative Processing File Transfer
Protocol
DDP-FJT Distributed Data Processing File and Job
Transfer
DDP-PPC Distributed Data Processing
Program-to-Program Communications
IPF 1100 Interactive Processing Facility
7848 4078–004 11–5
continued

Site Customization
11–6
Table 11–1. Package Tape Contents (cont.)
Tape Name Product
Full Name
Fast Load?
CPIX11 DFP Define File Processor
GSA 1100 General Syntax Analyzer
IMS 1100 Information Management System
PERCON PERCON Control
PERCONE PERCON E
PERCON7 PERCON 7
RBFTE Remote Batch File Transfer/Extended
program
SOLAR/E Software Library Administrator Extended
TPAS Transaction Performance Auditing System
CPIX12 DPS 2200 Display Processing System 2200 CPIX-OE2
IRU Integrated Recovery Utility
IRU-RM Integrated Recovery Utility (IRU) Recovery
Manager
UDS Control Universal Data System (UDS) Control CPIX-UDS3
CPIX13 DMS 2200 Data Management System CPIX-UDS3
DMS-DYN-AC Data Management System (DMS 2200)
dynamic access control feature
DMSKEY Data Management System (DMS 2200)
product key
RDMS 2200 Relational Data Management System CPIX-UDS3
RDMSENCRYPT RDMS 2200 Encryption
RDMSFASTSRCH RDMS 2200 Fast Search
RDMSKEY RDMS 2200 product key
RDMSUTIL RDMS 2200 Utilities
CPIX14 DDSMG DDS Migration Processor
FDP/ADP File Definition Processor/Application
Processor
QLP 2200 Query Language Processor
continued
7848 4078–004

Table 11–1. Package Tape Contents (cont.)
Site Customization
Tape Name Product
Full Name
Fast Load?
SFS 2200 Shared File System CPIX-UDS3
UREP Unisys Repository Manager CPIX-UDS3
UREPKEY Unisys Repository Manager (UREP)
product key
CPIX15 OSI-FTAM Open Systems Interconnection File
Transfer, Access, and Management
OSI-MHS Open Systems Interconnection Message
Handling System
UOSS Unattended Operations Support Software
CPIX16 OADE-UNIX Open Application Development
Environment for UNIX
SNAPPC System Network Architecture (SNA)
Program-to-Program Communications
SNARJE System Network Architecture (SNA)
Remote Job Entry
TAS Transmission Control Protocol/Internet
Protocol (TCP/IP) Application Services
TQ-BASELINE TeamQuest Baseline
TQ-ONLINE TeamQuest On line *
TQ-PMLOG TeamQuest PMLog
TQ-PROBES TeamQuest Probes
UADA Universal Compiling System (UCS) ADA
UADARTS Universal Compiling System (UCS) ADA
(UADA) Runtime System
CPIX-SPF ARC Automatic Recovery of Components
AT_MSAUDIT Mass Storage Audit Feature
CADIS Cache/Disk Interface Software
CARTIS Cartridge Tape Interface Software
CARTAPELIB Cartridge Tape Library Software
FBCADIS Fixed Block Cache/Disk Interface
Software
7848 4078–004 11–7
continued

Site Customization
11–8
Table 11–1. Package Tape Contents (cont.)
Tape Name Product
Full Name
Fast Load?
FBCIS Fixed Block Compatible Interface
Software
MHFS Multi-Host File Sharing
PAEXEC Partitioned Applications executive portion
PASSGEN-TRAN Password Generator transformation
algorithm
RLPCON Record Lock Processor configuration
utility
SCSITIS Small Computer System Interface (SCSI)
Software
SECOPT1 Security Option 1
SECOPT2 Security Option 2
SECOPT3 Security Option 3
SINCH Unisys Interconnect Channel Handler
SIPIPM Software Instrumentation Package Internal
Performance Monitor
SPAIR Software Product Application Initialization
and Recovery
TAVR Tape Automatic Volume Recognition
UDUPLEX Unit Duplexing
XPCEXEC Virtual Storage Manager
XTCEXEC Extended Transaction Capacity (XTC)
software
CPIX-TRN01 MCB Message Control Bank CPIX-OE2
TIPUTIL Transaction Processing Utilities CPIX-OE2
7848 4078–004

11.2.1. Registering the OS 2200 Product Key Tape
Site Customization
Registering the product key tape is required to install optional products from package
tape. To register the product key tape, take the following steps:
1. Start the runstream for registering the key tape by entering the following command:
ST REGISTERPKG
The following message appears:
n Register package from or DISK?
n
2. Press transmit to select the default location of the key tape. A prompt asks for entry
of the reel number from which the key is to be installed.
n Enter reel number
n CPKEY,TJ,HICL
3. Because the tape is unlabeled, enter any reel number. Also enter the parameters to
indicate that the tape is to be assigned as a temporary file, that it is unlabeled, and
that it is mounted on device type HICL.
The following message is displayed:
n Enter reel number
n
4. Press transmit to select the default and mount the key tape in the specified drive.
Loading begins, and you are prompted to verify that the unlabeled tape you mounted
is the correct reel.
LOAD CPKEY T40Z0 NORING PP$TAPE – 1 REGPKG
(LOAD CPKEY )(ANY UNASSIGNED CT0899 )
n ANSWER WITH REEL NO ON T40Z0 E,REEL
n CPKEY
The following message appears to indicate that the key tape is registered:
REGPKG FIN
7848 4078–004 11–9

Site Customization
11.2.2. Optional OS 2200 Product Installation
11–10
Once you have registered the key tape (11.2.1), you can install optional products or
product features from the package tapes. For information about product
interdependencies and installation procedures refer to the following documents:
Software Products Installation Guide
System Base Software Planning and Migration Overview.
Individual product documents (for example, the UDS Planning and Migration
Overview).
11.3. Customizing SPO/HMP Console and the
X Terminal Configuration
Following initial installation, the site may wish to modify the SPO/HMP Console default
configuration as follows:
Permanently change the X terminal configuration (11.3.1).
Modify the predefined SPO/HMP Console default configuration names to reflect
site-specific naming conventions.
As described in 2.6, if a site chooses host names other than the recommended names
used by the predefined SPO/HMP Console configurations, you must change the SPO
configurations following installation. The steps you take depend on whether or not the
new names were input as host names during the installation procedures.
If the changed host names were input during installation procedures, the only step you
must take is to reconfigure the host representations using the Single Point Configuration
Routine (11.3.4).
If, however, the changed host names were not input during installation procedures, you
must take the following steps:
1. Change the hosts files on the SPO server and, if applicable, the UNIX node (11.3.2).
2. Copy a new hosts file to each of the OS 2200 consoles (11.3.3).
3. Reconfigure the host representations using the Single Point Configuration Routine
(11.3.4).
4. Reinstall the Windows NT or URM agents on the Intel node so that the agents know
the new names (11.3.5).
7848 4078–004

Site Customization
11.3.1. Permanently Changing the X Terminal Configuration
If SPO/HMP Console and related software are preinstalled on the SPO server, a
configuration file /usr/X/lib/unisys/unisys-config also is preinstalled. Upon reboot the
contents of unisys-config take precedence over any configuration changes a user has
made at the X terminal. Example 11–1 shows the default contents of that file.
Following initial installation, sites can edit the contents of unisys-config if they wish to
permanently change the default X terminal configuration. Sites at which software was
not preinstalled can create that file as shown in Example 11–1 and use other X terminal
configuration options as described in the LT500 X Terminal Software Installation
Guide. At sites with preinstalled software, a full range of X terminal options is shown in
the template file /usr/X/lib/unisys/unisys-config.template.
! Unisys ClearPath SPO/HMP Console X Terminal Configuration Defaults
! This file should reside in /usr/X/lib/unisys/unisys–config for
! host–based LT501 configuration.
*.*.bootserverusing: tftp ! TFTP or ROM
*.*.boothostlist: BOOTHOST ! host, ...
*.*.bootfilename: /tftpboot/images/arxC–dy ! path to boot file
*.*.defaulttextfont: 6x13 ! 6x10, 6x13, 8x13, 9x15,
! 10x16, 12x17, or 12x20
*.*.fontpathlist: /opt/SPO/XP/fonts,\
LOCAL/,\
/usr/lib/X11/unisys/fonts/misc,\
/usr/lib/X11/unisys/fonts/75dpi,\
/usr/lib/X11/unisys/fonts/100dpi
*.*.remotefontaccess: enabled
*.*.defaultfonthost: BOOTHOST
*.*.defaultfontaccessprotocol: TFTP
*.*.autoconnectionmode: XDMCP ! Disabled, XDMCP,
! Telnet on Logout, or
! Telnet on Reboot
*.*.connectionhostlist: BOOTHOST ! host names/addresses
! or Disabled. (LOCAL CLIENT)
*.*.xdmcpcalloutmode: Direct ! Broadcast, Direct,
! or Indirect
*.*.keyclick: Off ! On or Off
*.*.autorepeat: Normal ! Off, Slow, Normal, or Fast
*.*.mouseaccelerationthreshold: 3 ! number of pixels
*.*.mouseacceleration: 4 ! multiplier
*.*.audiblebell: on ! On or Off
*.*.bellvolume: 100
*.*.keyboardlanguagemapping: US English ! US English, German, French,
! UK English, or Swedish/Finnish
*.*.keypadmode: Local NumLock ! Local NumLock,
! Numeric Unshifted,
! Numeric Shifted, or
! Numeric Only
*.*.prex11r4bugcompatibility: enabled ! Enabled or Disabled
*.*.defaultcolorvisualclass: PseudoColor ! PseudoColor, StaticColor,
! GrayScale, or StaticGray
! (color models only)
*.*.enablescreensaver: no ! Yes or No
*.*.screenmode: Virtual Desktop ! Normal, Virtual Desktop,
! or Alternate Screen
*.*.virtualdesktopsize: 2048x1024 ! 2048x1024 for Virtual Desktop
*.*.monitortype: 0 ! 0 for Unisys High Res 19 inch
! 1 for Unisys High Res 17 inch
Example 11–1. Default X Terminal Configuration File Contents
7848 4078–004 11–11

Site Customization
11.3.2. Editing the Hosts Files
11–12
You can edit the hosts file on the SPO server, and the UNIX node (if applicable), as
follows:
1. If not already logged on, log on as superuser (see 6.4).
2. Using an editor (for example, vi), open the /etc/hosts file.
3. Determine whether the names of the ClearPath IX server components are correct as
follows:
SPO server—Determine whether the names of the SPO server, Intel node
(Windows NT or UNIX node as applicable), 2200 node consoles, and X terminal
are correct (Example 11–2).
UNIX node—Determine whether the names of the SPO server and UNIX node
are correct (Example 11–4).
4. If the names are not correct, add the desired names as aliases to the current names
(Example 11–3 and Example 11–5). The names for the UNIX node and SPO server
should be the same as their UNIX system names (uname). The uname can be
determined by entering the following command for each component:
uname –n
For the 2200 node system consoles, the site’s preferred name should be used as the
name in the SPO server host file, otherwise SPO/HMP will not be able to bring up the
replicated display of the X terminal.
lan-address lan-node-name alias1... ..aliasn # comment
xxx.xxx.xxx.xxx Intelnode-name CP_NT CP_UNIX if a UNIX node
xxx.xxx.xxx.xxx sposerver-name SPO_Server
xxx.xxx.xxx.xxx cp_cons01
xxx.xxx.xxx.xxx cp_cons02
xxx.xxx.xxx.xxx xterm-name cp_xterm
Example 11–2. SPO Server Hosts File Format before Editing
lan-address lan-node-name alias1... ..aliasn # comment
xxx.xxx.xxx.xxx Intelnode-name new-alias CP_NT CP_UNIX if a UNIX node
xxx.xxx.xxx.xxx sposerver-name new-alias SPO_Server
xxx.xxx.xxx.xxx new-name cp_cons01
xxx.xxx.xxx.xxx new-name cp_cons02
xxx.xxx.xxx.xxx xterm-name cp_xterm
Example 11–3. SPO Server Hosts File Format after Editing
7848 4078–004

lan-address lan-node-name alias1.. ...aliasn # comment
xxx.xxx.xxx.xxx Intelnode–name CP_UNIX
xxx.xxx.xxx.xxx sposerver–name SPO_Server
Example 11–4. UNIX Node Hosts File Format before Editing
lan-address lan-node-name alias1.. ...aliasn # comment
xxx.xxx.xxx.xxx Intelnode-name new-alias CP_UNIX
xxx.xxx.xxx.xxx sposerver-name new-alias SPO_Server
Example 11–5. UNIX Node Hosts File Format after Editing
Site Customization
11.3.3. Copying the New Hosts File to the System Consoles
The newly edited hosts file on the SPO server should be copied to diskette and then
loaded at each of the 2200 node system consoles.
Copying the New Hosts File to Diskette
To copy the hosts file to diskette, take the following steps:
1. If not already logged on at the SPO server, log on as superuser (6.4).
2. Place a diskette into the drive unit of the SPO server and enter the following
commands to copy the hosts file to diskette:
Loading the New Hosts File
cd /etc/inet
tar cvf /dev/rdsk/f03ht ./hosts
To load the new hosts file on each 2200 node system console, take the following steps:
1. On the system console, press F3.
The Utilities Session menu appears (Figure 6–2).
2. Select Optional Features, then press Enter.
A list of utilities appears as follows:
AMS Utility
USP Utility
USP APFG Utility
SP Interface Utility
7848 4078–004 11–13

Site Customization
11–14
3. Select SP Interface Utility, then press Enter.
An execute box appears.
4. Press Enter.
The Single Point Interface Utility window appears.
5. Select the Hosts File menu bar item, then press Enter.
A list of options appears as follows:
Load
Save
Exit
6. Select Load, then press Enter.
7. Press the up or down arrow keys to get the following drop down list:
DOS–HD
DOS–DD
UNIX
8. Use the arrow keys to select the UNIX option, then press Enter.
9. Tab to the Host Name field, enter the site-defined name of the console you are
loading.
The Execute box appears.
10. Again press Enter.
You are prompted to insert the diskette.
11. Insert the diskette with the hosts file on it, then press Enter.
A window appears indicating that the system is working and that you should wait.
When the system completes loading the hosts file, it returns to the Single Point
Interface Utility window.
12. If you do not have a router, skip this step. If you have a router, add router
information as follows:
a. Select the Routers menu bar item.
A list of options appears as follows:
Add Router
Delete Router
Display Routers
b. Select Add Router, then press Enter.
An Add Router window appears.
7848 4078–004

Site Customization
c. Enter information in that window as follows:
− In the top portion enter the IP address and host name that defines the
destination of messages to be routed through the router. That destination
can be either a network or a host.
− In the bottom portion, enter the IP address and host name of the router.
13. When done, press Enter.
The Single Point Interface Utility window reappears.
14. Select the Changes menu bar item.
A list of options appears as follows:
Initialize Work
Execute Changes
Report Changes
15. Select Execute Changes to enable the changes to the hosts file.
16. Select Exit to exit from the Single Point Interface utility.
Repeat this procedure for each system console.
11.3.4. Reconfiguring the Host Representations
The most complete method of changing the host and console representations is to first
delete the predefined host or console, then add a new host or console using a
site-defined name. The following procedure describes the steps to take:
1. Create a new configuration as follows:
a. Log on to the X terminal as spadmin to start the Single Point configuration
routine.
You are prompted to select a configuration to edit.
b. Select the configuration to edit (for example, CPIX_NT_2_x.xCP or
CPIX_2_x.xCP), then select OK.
In a few moments the TopCluster window and the Configure SPO/HMP Console
main menu window appear.
c. Click File in the main menu and select the Save Configuration As option.
You are prompted to enter the name of the new configuration.
d. Enter a name for the new configuration you are creating, then click OK.
After a few moments the new configuration is created and the main menu title
reflects that you are now editing your new configuration (the Single Point
Configuration routine automatically switches to the new configuration).
7848 4078–004 11–15

Site Customization
11–16
e. In the TopCluster window menu click Edit, then select the Icon Placement
option.
This opens the Edit Icon Placement window. Move the window to keep it
accessible without overlapping the TopCluster window.
2. Customize the Intel node representation (Windows NT or UNIX node) as follows:
a. In the TopCluster window menu click Delete, then select the Windows NT or
UNIX Systems option as applicable.
In a few moments, a window appears listing the Windows NT or UNIX systems
that are currently configured.
b. Select CP_NT (Windows NT) or CP_UNIX (UNIX) system, as applicable, and
click OK.
The system is now removed from the configuration.
c. In the TopCluster window menu click Add, then select the Windows NT or UNIX
Systems option.
In a few moments a window for entering the new system representation
appears.
d. Enter the site-defined name of the Intel node and select OK.
The node is added to the TopCluster diagram.
If UNIX is installed on the Intel node, a window also appears requesting the
system’s network connection name.
e. Skip this step if Windows NT is installed on the Intel node. Take the following
steps if UNIX is installed:
− Click on the Unknown button if the Intel node is directly connected to the
SPO server. If the connection is through a Network Access Server (NAS),
enter the NAS network name that is listed in the /etc/hosts file.
A window requesting the /etc/services name for the system appears.
− Enter CP_UNIX , then select OK. This entry was already made in the
/etc/services file for the direct connection to the UNIX node to port 1 of the
Equinox multiport board. If the system is connected through a NAS, you
need to enter the service entry for the port assigned on the NAS.
f. To place the Intel node icon where you want it, click once on the icon, then click
once on the position in the TopCluster window where you would like it. X and Y
coordinates can be further adjusted by entering coordinates for the node
through the Edit Icon Placement window (the original coordinates for the node
were X=200 and Y=600).
7848 4078–004

Site Customization
3. Customize the SPO server representation (SPO_Server) as follows:
a. In the TopCluster window menu click Delete, then select the UNIX Systems
option.
In a few moments, a window listing the UNIX systems that are currently
configured appears.
b. Select the SPO_Server system and click on OK.
The SPO_Server system is now removed from the configuration.
c. In the TopCluster window menu click Add, then select the UNIX Systems option.
In a few moments a window for entering the new system appears.
d. Enter the site-defined name of the SPO server and select OK.
The system is added to the TopCluster diagram.
A window requesting the system’s network connection name appears.
e. Enter spo_telnet and select OK (this entry was already made in the
/etc/services file by the SPO/HMP Console installation routine).
f. To place the SPO server icon where you want it, click once on the icon, then
click once on the position in the TopCluster window where you would like it.
X and Y coordinates can be further adjusted by entering coordinates for the SPO
server through the Edit Icon Placement window (the original SPO server icon
was located at X=800 and Y=600).
4. The SPO server has a timeout feature used to determine the time interval between
the receipt of console message traffic before a timeout alert is generated. This
feature is not needed for monitoring nodes in a ClearPath IX server configuration.
Disable this feature as follows:
a. In the TopCluster window menu click Edit, then select the UNIX Systems
option.
In a few moments the Edit UNIX Systems window appears.
b. Click the value in the Timeout Period column for the new Intel node name.
A window appears for you to enter the new timeout value.
c. Change the timeout value to 0 (this disables the timeout feature), then click
Enter or OK.
d. Repeat this process for the new SPO server name and then close the Edit UNIX
Systems window.
7848 4078–004 11–17

Site Customization
11–18
5. Customize the 2200 node partitions and 2200 node console representations as
follows:
a. In the TopCluster window menu click Delete, then select the OS 2200 Systems
option.
In a few moments a window listing the currently configured 2200 node
partitions.
b. Select the 2200 partition, then click OK.
The 2200 partition is now removed from the configuration.
c. In the TopCluster window menu click Add, then select the OS 2200 Systems
option.
In a few moments a window for entering the new system appears.
d. Enter the site-defined name of the 2200 node partition, then select OK.
The node is added to the TopCluster diagram (note that the system does not
have a console icon connected at this time).
e. To place the 2200 node icon where you want it, click once on the icon, then click
once on the position in the TopCluster window where you would like it. X and Y
coordinates can be further adjusted by entering coordinates for the SPO server
through the Edit Icon Placement window (the original 2200 node icons were
located at X=300,700 and Y=150).
f. In the TopCluster window menu click Delete, then select the OS 2200 Consoles
option.
In a few moments a window listing the currently configured 2200 node system
consoles appears.
g. Select the OS 2200 console, then click OK.
The system console is removed from the configuration.
h. In the TopCluster window menu click Add, then select the OS 2200 Consoles
option.
In a few moments a window for entering the new console appears.
i. Enter the site-defined name of the OS 2200 console, then select OK.
The console is added to the TopCluster diagram. A window asks you to identify
the 2200 partition to which the console should be connected.
j. Click the name of the new 2200 partition, then select OK.
The console now shows a connection to the new 2200 partition.
7848 4078–004

Site Customization
k. To place the console icon where you want it, click once on the icon, then click
once on the position in the TopCluster window where you would like it. X and Y
coordinates can be further adjusted by entering coordinates for the SPO server
through the Edit Icon Placement window (the original 2200 console icons were
located at X=300,700 and Y=350).
l. Repeat these procedures for each of the OS 2200 systems and consoles you wish
to customize.
6. Save and Verify the new configuration changes as follows:
a. In the Configure SPO/HMP Console main menu click File, then select the Save
Configuration option.
A window asks if you want to perform configuration verification.
b. Click Yes.
After a few moments a window appears stating that no errors were found.
If errors are detected, two windows appear, one describing the errors and the
other asking if you wish to save the configuration anyway. Follow the
instructions given in the results window to fix the errors.
You now must reinstall the Windows NT or URM agents, as applicable, as described in
the following subsections.
11.3.5. Reinstalling the Agent Software
After modifying host representations, you must reinstall the agent software to allow the
agents to interact with the new site-defined representation names.
If Windows NT is installed on the Intel node, you must reinstall Windows NT agents
using the procedures in 7.4.
If UNIX is installed on the Intel node, you must reinstall URM agents as follows:
1. In the Single Point Configuration Routine main menu click Application, then select
the Maintain UNIX Agents option.
Two windows with tables appear—a Maintain UNIX Agents window and a URM
policies window.
2. In the Maintain UNIX Agents window menu, click Execute, then select Remove.
A dialog box appears asking you to select the systems on which you want to remove
agents.
7848 4078–004 11–19

Site Customization
11–20
3. Select the CP_UNIX and SPO_Server systems.
In a few moments, a dialog box appears informing you that the UNIX agent for
system CP_UNIX has been removed and that you must execute
/opt/SPO–agent/remove on the CP_UNIX system.
4. Click OK.
In a few moments, a dialog box appears informing you that the UNIX agent for
system SPO_Server has been removed successfully.
5. Click OK.
6. Sign on to the UNIX node as root (see 5.6).
7. Enter the following commands:
cd /opt/SPO–agent
./remove
The URM agent is now removed.
8. Go back to the Single Point Configuration Routine main menu on the X terminal
(see step 1).
9. In the Maintain UNIX Agents table, click the hyphen (-) under URM Policy for the
new UNIX node name.
A dialog box appears.
10. Under URM Policy, double click default.
11. Under Security Scheme, click Access Allowed for the new UNIX node name.
A dialog box appears.
12. Under Security Scheme, double click Manual Install.
13. In the Maintain UNIX Agents table, click the hyphen (-) under URM Policy for the
new SPO server name.
A dialog box appears.
14. Under URM policy, double click default.
15. In the Maintain UNIX Agents window menu bar click Execute, then select Install.
A dialog box appears asking you to select the systems on which you want to install
agents.
16. Select the new UNIX node name and the new SPO server name.
In a few moments, a dialog box appears informing you that the UNIX agent
for the new UNIX node name has been placed into directory
/var/opt/spo/manual/new-Intelnode-name on the SPO server.
7848 4078–004

17. Click OK.
Site Customization
In a few moments, a dialog box appears informing you that the UNIX agent for the
new SPO server name has been installed successfully.
18. Click OK.
19. Check to see that the URM agent is running as follows:
a. Enter the following command on the SPO server:
ps –ef | grep SPO-agent
b. Check the response output for /opt/SPO–agent/urm.loop and
/opt/SPO–agent/pulse.loop.
If the URM agent is not running, su to root (enter the su command to become
superuser) and enter the following command:
/opt/SPO-agent start.
20. Sign on to the UNIX node as root and enter the following commands:
rcp –pr spo-server-name:/var/opt/spo/data/manual/new-Intelnode-name /tmp
where spo-server-name is the network name of the SPO server
cd /tmp/new–Intelnode–name
./install
21. Again, check to see that the URM agent is running by entering the following
command:
ps –ef | grep SPO-agent
a. Check the response output for /opt/SPO–agent/urm.loop and
/opt/SPO–agent/pulse.loop.
b. If the URM agent is not running, enter the following command:
/opt/SPO-agent start.
22. In the Maintain UNIX Agents window menu bar click Execute, then select Exit.
23. Exit the configuration routine as follows:
a. From the Configure SPO/HMP Console main menu window click File, then
select the Exit Configuration Routine option. A window appears to verify that
you wish to quit.
b. Click OK.
7848 4078–004 11–21

Site Customization
11.4. Testing TCP/IP Communications
11–22
Once the site customizes their CMS 1100 configuration(see 2.6), they can test TCP/IP
communications as follows:
1. Access an OS 2200 console session at either the SPO X terminal or at the monitor
concentrator.
2. Start the customized CMS 1100 configuration. CMS 1100 should indicate that the
Ethernet interface has been initialized, and is up and active.
3. At the Intel node, log on as follows:
If running UNIX, log on as superuser at a UNIX console session, if not already
logged on (5.6).
If running Windows NT, log on as administrator, if not already logged on (4.6),
and start an MS-DOS session.
4. Type the following command, then press Enter:
ping xxx.xxx.xxx.xxx
where xxx.xxx.xxx.xxx is the IP address of the 2200 node. Alternatively, you
could enter hostname instead of the IP address, where hostname is the
internet system name assigned to the 2200 node.
The following message should appear in response:
xxx.xxx.xxx.xxx is alive
where xxx.xxx.xxx.xxx is the IP address of the 2200 node.
The connection is not operational if the following message appears:
no answer from xxx.xxx.xxx.xxx
7848 4078–004

11.5. Installing Optional UNIX Products
Site Customization
After using the tuning script to install basic UNIX IOE packages on the Intel node (see
Section 5), sites can install optional UNIX application packages. In general, optional
UNIX application packages are installed using the following procedure:
1. If you are not already logged on, log on as root (superuser) (see 5.6).
2. Load the application package release medium (CD-ROM or tape) in the appropriate
drive unit.
3. At the UNIX shell prompt enter a pkgadd command appropriate to the media. For
example, when installing from diskette you would enter the following command:
# pkgadd -d /dev/rdsk/f03ht
Answer any prompts that appear on the screen. Refer to the individual product
documentation for specific instructions.
4. After the last package has been installed, reboot the UNIX node.
7848 4078–004 11–23

Appendix A
Communication Settings Specific to
ClearPath
This appendix describes ClearPath-specific communication settings including
Internal FDDI LAN IP addresses used by ClearPath IX server components
(Table A–1). These addresses cannot be used by customer sites.
TSAM configuration values (Table A–2).
Default contents of the hosts file (/etc/hosts) (Example A–1).
Caution
PathMate configuration assistants define the values in Table A–1 by default.
ClearPath does not function properly if those values are not used.
Table A–1. IP Addresses and Host Names Used by the Internal FDDI LAN
FDDI IP
Address Product
FDDI Host
Name
192.168.57.3 Windows NT node (if applicable) fddintsr
192.168.57.4 UNIX node (if applicable) fddiuxsr
192.168.57.5 2200 node (OS 2200 demand/common) fddi22sr
192.168.57.6 Open Programming Environment (OPE) (OS 2200)
IP Address
fddi22am
192.168.57.7 MAPPER fddi22mr
7848 4078–004 A–1

Communication Settings Specific to ClearPath
A–2
Product
Table A–2. TSAM Configuration Assignments
TSAM
Process
Name TSAM Password
DEPCON V$DEP DEPCON DEPCON
MAPPER TSAMID PASSWORD
Open Programming
Environment (2200)
IP Address
AMTSAA SCRAMBLED-EGGS-WITH-
HASH-BROWNSA
TM 2200 IP Address V$TM2 TM2200
UniAccess (2200) IP Address UACP UA
InfoAccess (2200) IP Address IASOCK IA
Oracle Transparent Gateway ORALSN ORA
TSAM
T-Selector
Example A–1 shows the default contents of the UNIX node and OPE UNIX hosts file
(/etc/hosts). See 4.7 for the contents of the Windows NT node hosts file.
# begin ClearPath IX /etc/hosts defaults
# The following host numbers and names are reserved for ClearPath
# private internal LAN. The IP network number 192.168.57.xx is
# from the block of IP network numbers that the Internet Assigned
# Numbers Authority (IANA) has reserved for private internets.
# See RFC# 1918 for details.
#
# WARNING!
#
# Do not change these values. Your ClearPath system will not
# function properly if these values are modified or removed.
#
# One or more alias names may be added for any entry.
192.168.57.3 fddintsr # Reserved
192.168.57.4 fddiuxsr # Reserved for UNIX node
192.168.57.5 fddi22sr # Reserved for shared 2200
192.168.57.6 fddi22am # Reserved for OPE
192.168.57.7 fddi22mr # Reserved for Mapper
# Put your site specific information after the next line.
# end ClearPath IX /etc/hosts defaults
Example A–1. Default UNIX Node and OPE UNIX Hosts File
7848 4078–004

Appendix B
Enabling System Controlled
Performance
If you have an IX4600 or IX4800 ClearPath IX server you should establish the System
Controlled Performance (SCP) contracted performance level as soon as possible while
installing 2200 node IOE software. Until your contracted performance level is
registered, the node runs at the default performance level (11 percent), and a console
message is issued every 5 minutes stating the system is running with the SCP default
performance value.
SCP software limits the availability of IP cycles depending on the performance level
specified for the model number. A unique SOLAR Exec key tape is created for each 2200
node by system serial number. The Exec key tape contains encoded SCP information for
each specific model’s serial number and must be registered as part of the SOLAR
installation process by the person with the SSCONFIGMGR security privilege.
SOLAR level 2R5 or higher must be installed before the first Exec key tape registration.
The Exec key tape (unlabeled) is included in the node packaging and must be
safeguarded for disaster recovery. If the Exec key tape is bad, there are multiple copies
(10) of the first file. If an alternate file can be read from the key tape, copy the file to a
new unlabeled tape for registration.
B.1. Initial Installation
When the Exec is initially booted, the 2200 node operates, after SYS FIN, at the 100
percent performance level until a SYS$*DATA$ file exists. After SYS$*DATA$ is
established by SOLAR, the system performance is set to the default level (11 percent)
and the Exec issues a read-and-reply console message every 5 minute time and date
interval until the SOLAR Exec key tape is registered.
The first SOLAR Exec key tape registration registers any valid Exec key tape, including
one with an incorrect node serial number. A subsequent Exec key tape registration will
fail if the Exec key tape system serial number does not match the previously registered
system serial number with the following SOLAR error message:
*ERROR* PKREG 47190:
A key for product name, level level, and style style-id containing the
key identifier id1 cannot be registered. A key for the same name, level, and
style-id is already registered with the key identifier id2. The keys conflict.
7848 4078–004 B–1

Enabling System Controlled Performance
B–2
After the Exec key tape is registered, if the Exec key tape serial number does not match
the Partition Data Bank (PDB) system serial number, a read-and-reply console message
is reported every 5 minutes and the node is set to operate at the default performance
level. SOLAR re-registration of the correct Exec key tape will resolve the problem. If an
Exec key tape with an incorrect serial number is registered, there are two methods to
resolve the problem:
If your node has: Do the following:
No previous product keys
installed
1. Delete the KEYTABLE$ element in SYS$*DATA$
@DELETE,O SYS$*DATA$.KEYTABLE$
2. Start the SOLAR registration process over from the beginning.
Product keys installed 1. Copy the KEYTABLE$ element from the previous SYS$*DATA$
file cycle to the current cycle.
@COPY,O SYS$*DATA$(-1).KEYTABLE$,SYS$*DATA$.
2. Reregister the correct Exec key tape.
Note: Beginning with SB7, SOLAR will include a key purging utility to purge the
Exec key tape information before reregistering the correct Exec key tape.
The SCP information is SOLAR registered into the SYS$*DATA$.KEYTABLE$ element in
encrypted form, read by the Exec from the KEYTABLE$ element to the SCP resident
data cells, and copied to the disk-resident system (DRS) device protected area for
alternative system recovery use. The Exec logs the model number and performance
level in the system log and in a console message.
B.2. Normal Operation
The model and performance rating are made available by SIP and the system log to
Performance Analysis Routines (PAR), Online System Activity Monitor (OSAM), and
other performance monitoring software. The Exec logs the model number and
performance level in the system log on each boot and system performance change.
The MODELNUM keyin is provided to verify the model number and performance level
registered by the Exec key tape. The model number and performance level are also
displayed on the system console, after SYS FIN on each boot, after every system
performance change, and after each SCP compliance error message.
7848 4078–004

B.3. Model Upgrade
Enabling System Controlled Performance
When you order a performance upgrade, a new Exec key tape is provided. When the
upgrade involves no hardware, you can register the new Exec key tape without
rebooting. It is recommended that SIP be turned off during Exec key tape registration.
If there is a mismatch with the Exec key tape, an error is reported and the node
continues operation at whatever performance rating was in effect. When the upgrade
also involves hardware, you should register the new Exec key tape first, install the new
IPs, and reboot the node. If the number of IPs that are up or reserved is greater than the
number allowed by the current registered Exec key tape, the correct Exec key tape was
not registered. An error is reported and any additional IPs above the contracted number
of IPs are brought down (IPs in reserved state are brought down first) until the correct
SOLAR Exec key tape is registered. The node continues to operate at the previous
performance level.
B.4. Recovery Boots
For all 2200 node reboots, the SCP information is retrieved from the SYS$*DATA$ file
and is copied to the DRS device so the latest SCP information is always on the DRS
device for alternative recovery. If retrieval from SYS$*DATA$ fails, the DRS device SCP
information is used when the Exec key tape was previously registered. An I-Boot does
not destroy the SCP data on the DRS device. If a DRS device without SCP information is
used, or the retrieval from the DRS device fails, the default SCP performance level is
used until the Exec key tape is registered.
B.5. MODELNUM Keyin
An unsecured MODELNUM unsolicited keyin is provided to verify the correct model
number and performance level have been SOLAR-registered with the Exec key tape.
When you enter the MODELNUM keyin, the following information is displayed:
Model Number - nnnnnnnnnnnn Performance level - xxx%
where:
nnnnnnnnnnnn
is the model number (for example, IX4802-2) when the Exec key tape is SOLAR
registered. The default model number is UNKNOWN.
xxx
is the contracted SCP level percentage when the Exec key tape is registered. The
default percent is 11 percent. xxx is 100 percent of the contracted performance for
this system. If this value is less than 100 percent, the difference represents the
performance reserve available for system growth. The reserve is available with a
new contracted performance level.
7848 4078–004 B–3

Enabling System Controlled Performance
B–4
If you enter a MODELNUM keyin on a node without SCP, the following message appears:
MODELNUM keyin is not supported on this system.
B.6. Messages
The Exec checks the SCP settings every 5 minute time and date interval after SYS FIN
for compliance. If not compliant, the following messages are redisplayed (the message
suppression level is 0 for each message):
The Exec checks for a valid SCP KEYTABLE$ element. If not found, the following
read-and-reply console message will be issued to the SYSMSG response console:
The System Controlled Performance KEYTABLE$ element does not
exist or is not readable. The system is running at the default
performance level or the values recovered from the DRS device.
n Please SOLAR register the Exec key tape - Answer Go
n GO
Model number – UNKNOWN Performance level – 11%
The following message is displayed on the console at boot time following SYS FIN,
after Exec key tape registration, and after any Exec key tape discrepancy message
for all SCP systems:
Model Number - nnnnnnnnnnnn Performance level - xxx%
where:
nnnnnnnnnnnn
is the model number (for example, IX4802-2) when the Exec key tape is SOLAR
registered. The default model number is UNKNOWN.
xxx
is the contracted SCP level percentage when the Exec key tape is registered.
The default percent is 11 percent. xxx is 100 percent of the contracted
performance for this system. If this value is less than 100 percent, the difference
represents the performance reserve available for system growth. The reserve is
available with a new contracted performance level.
If the Exec key tape serial number does not match the PDB system serial number,
the following read-and-reply console message is issued to the SYSMSG response
console and the node operates at the lowest performance level:
The Exec key tape does not match the system serial number.
The system is running at the default performance level.
n Please SOLAR register the correct Exec key tape - Answer Go
n GO
Model number – IX4802-2 Performance level – 11%
7848 4078–004

Enabling System Controlled Performance
If the Exec detects the node is running with more up or reserved IPs than the
current Exec key tape indicates, the model has been upgraded but the new Exec key
tape was not registered. The following read-and-reply console message is issued to
the SYSMSG response console and the additional IPs are brought down:
The number of IPs present is greater than the number allowed
by the current registered Exec key tape. All IPs above the
registered number are being downed. The Exec key tape that
contains the contracted number of IPs, and the System Controlled
Performance level must be registered.
n Please SOLAR register the correct Exec key tape - Answer GO
DN of IP3 requested by fault recovery was received.
n+1 System performance may be degraded. Press the Enter Key.
IP3 DN
n+1
n GO
Model number – IX4802-2 Performance level – 100%
The IPs that were brought down can be brought up after the correct Exec key tape is
SOLAR registered.
If the current date is within 14 days of a registered Exec key tape or file specified
expiration date, a read-and-reply console message is issued once the first and
twelfth hour of each day.
The System Controlled Performance Exec key expires after YYYY–MM–DD.
The expiring Exec key tape will no longer SOLAR register after this date.
Unless a new Exec key tape is registered before this date, the system
will run at the default performance level.
n Notify the site administrator of the expiring Exec key tape – Answer GO
n GO
Model Number – IX4802–2 Performance level – 100%
If the registered Exec key tape or file specified expiration date is beyond the current
date, a read-and-reply console message is issued atfter midnight and the
performance level is dropped to the default.
The System Controlled Performance Exec key expiration date has passed.
The system is now running at the default performance level.
The old Exec key tape can no longer be SOLAR registered.
n Please SOLAR register a new Exec key tape – Answer GO
n GO
Model Number – IX4802–2 Performance level – 11%
7848 4078–004 B–5

Appendix C
SPO/HMP IX Interface License Key
Registration
The ClearPath IX server includes SPO/HMP Console software (component style name
SMS 154-CPS). The license entitles your site to use SPO/HMP Console software to
operate a stand-alone ClearPath IX server or alternatively to manage one ClearPath IX
server from one or more SPO Enterprise Server Edition (SPO/ESE) servers.
License keys are not used within a stand-alone SPO/HMP Console server. However, the
feature that allows SPO/ESE to control a ClearPath IX server is enabled by a license key.
That feature is known as the SPO/HMP IX Interface.
When the license key is installed on the SPO/ESE server, an increment in SPO Console
functionality is provided as follows:
The ANSI X3.64 connectivity attributes are enabled for monitoring the SPO server.
If Windows NT is installed on the Intel node
− The Windows NT connectivity attributes are enabled for monitoring the
Windows NT node.
− The 2200Mon Status classification is enabled for running the HMP preconfigured
Status display.
If UNIX is installed on the Intel node
− The ANSI X3.64 connectivity attributes are enabled for monitoring the UNIX
node.
− The Unix2200Mon Status classification is enabled for running the HMP
preconfigured Status display.
Each ClearPath IX server delivery includes a temporary key (see C.3) that enables you to
immediately configure and manage the ClearPath IX server from a SPO/ESE system.
You should obtain a permanent key as soon as possible (see C.1).
7848 4078–004 C–1

SPO/HMP IX Interface License Key Registration
C.1. How to Obtain a Permanent Key
C–2
Take the following steps to obtain a permanent key:
1. Complete the permanent key request portion of the registration form in C.3. The
form is used to identify your ClearPath IX server order number(s) plus the SPO/ESE
server-id value(s) used for permanent keying.
2. Send the form to Unisys Software Publications and Manufacturing Division (SPMD).
3. Upon receipt of the key request, SPMD generates a permanent key and returns it to
you on standard permanent key shipment forms (43059784 and 43059785).
4. Upon receiving the permanent key, install the new keys on the designated server or
servers.
Permanent keys for the SPO/HMP IX Interface reflect the total number of ClearPath IX
servers that you have registered to be managed by SPO/ESE. Normally, this is one per
ClearPath IX server purchased. The resultant key includes the accumulated total as the
license count value.
C.2. Upgrades to SPO/ESE
To upgrade from standard SPO/HMP Console software to SPO/ESE, you must purchase
package style SMS 6000–CPS. That package consists of two components: SPO Console
(SPO 155–SPO) and Status (SMS 6000–STA). In this case, the registration of license keys
begins with receipt of the software order in SPMD. Initial delivery of temporary keys
and subsequent delivery and registration of permanent keys are performed through the
normal SPO key registration process which is documented in the SPO Console
Configuration and Administration Guide.
In order to manage the ClearPath IX servers from SPO Console, however, you must now
install the temporary key provided in C.3 and follow the instructions for requesting a
permanent key for the SPO/HMP IX Interface. If you have more than one ClearPath IX
server, the order number for each must be indicated on the request. If you have more
than one SPO server, the server-id for each must be indicated on the request.
C.3. SPO/HMP IX Interface License Key
Registration Form
The following form provides the universal temporary key for SPO/HMP IX Interface.
Use this form as instructed in C.1 to request a permanent key.
7848 4078–004

SPO/HMP IX Interface License Key Registration
7848 4078–004 C–3

Appendix D
Migrating from ClearPath Release 1.0
to 2.0
This appendix describes how existing ClearPath release 1.0 sites can migrate to
ClearPath release 2.0 to use the new capabilities of release 2.0. It describes
New and changed products for ClearPath release 2.0 (D.1)
Installing OS 2200 products from fast-load tape CPIX-OE1 (D.2)
Updating the UNIX node (if UNIX is installed on the Intel node) (D.3)
Installing SPO/HMP Console level 4.1 (D.4)
All sites must install the new level of PathMate (level 2.0). PathMate is provided on
CD-ROM as part of the IOE. See 10.2 for installation instructions.
Most new and changed OS 2200 products for ClearPath release 2.0 are on fast-load tape
CPIX-OE1 and can be installed as described in D.2.
Instructions for installing products not on the fast-load tape are as follows:
Cooperative Processing File Transfer Protocol (cpFTP)—See the Cooperative
Processing File Transfer Protocol (cpFTP) User’s Guide.
DEPCON—See the DEPCON Application Configuration and Operations Guide
(also see PathMate help).
Enterprise Backup and Restore (EBR2200)—See 10.7.
Windows NT IOE products—Open/OLTP Pathway—See the Open/OLTP Pathway
Installation and Operations Guide.
7848 4078–004 D–1

Migrating from ClearPath Release 1.0 to 2.0
D.1. New and Changed Software for Release 2.0
D–2
Table D–1 lists the new software products for ClearPath release 2.0.
Table D–1. New Products for ClearPath Release 2.0
Cooperative Processing File Transfer Protocol (cpFTP)
Enterprise Backup and Restore (EBR2200)
Product Level IOE
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MAPPER–NT
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Open/OLTP Pathway (OLTP–PATHWAY) for Windows NT
TransIT 500 (TRANSIT–500) for Windows NT
ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TransIT Mail Exchange (TRANSIT–MAIL) for Windows NT
1R1
2R3
5.3.1
ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Web Transaction Server (WEBTS)
ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Web Transaction Enabler for Windows NT ÁÁÁÁÁÁ
(WEBTX–NT) ÁÁÁÁ
1.0 No
Web Transaction Enabler for UNIX (WEBTX–UNIX)
ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Table D–2 lists the changed software products for CPIX2.0, the SB6 Delta 2 based
version of ClearPath release 2.0.
Table D–2. Changed Products for CPIX-2.0 (SB6D2 Based Release)
Product
Communications Management System 1100
(CMS1100)*
Product
Level
3R2
8.0
2.0
1R1
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DEPCON
Dump Analysis Processor (DAP)*
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
DMPLIB*
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
EXEC*
1.0
Intel/
2200
No
Yes
No
Yes
No
No
No
No
IOE
8R3 2200 ÁÁÁÁÁ
Yes
ÁÁÁÁÁ
ÁÁÁÁÁ
3R1 2200 ÁÁÁÁÁ
Yes
10R3A 2200
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
* This product is at a higher level than the same product in SB6 Delta 2
Yes
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
6R1C 2200 Yes
45R1C 2200
Yes
ÁÁÁÁÁ
ÁÁÁÁÁ
continued
ÁÁÁÁÁ
ÁÁÁÁÁ
7848 4078–004

Migrating from ClearPath Release 1.0 to 2.0
Table D–2. Changed Products for CPIX-2.0 (SB6D2 Based Release) (cont.)
File Administration System (FAS)
Product Intel/
Product Level 2200 IOE
Fault Location by Interpretive Testing (FLIT)*
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
MAPPER*
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁ
6R1A 2200 Yes
10R3A 2200 ÁÁÁÁ
No
38R2B 2200
ÁÁÁÁ
ÁÁÁÁ
Open/OLTP Pathway (OLTP–PATHWAY) for UNIX 3R2 Intel (UNIX) Yes
Open Programming Environment (OPE)
Open Programming Environment Transaction
Processing (OPE–TP)
3R5 2200
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
7848 4078–004 D–3
No
Yes
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
5R1B 2200 No
ÁÁÁÁ
ÁÁÁÁ
Oracle Transparent Gateway ÁÁÁÁÁ
(ORA–TG) 3.1 ÁÁÁÁ
2200 No
Open Systems Interconnection Message Handling
System (OSI–MHS)*
Open Systems Interconnection Transaction
Processing (OSI–TP)
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
5R1 2200 ÁÁÁÁ No
ÁÁÁÁ
2.0.1 Intel (UNIX) ÁÁÁÁ No
PathMate 2.0 Intel Yes
ÁÁÁÁ
ÁÁÁÁ
SP-Operation 4.1CP Intel Yes
Transaction Processing Utilities (TIPUTIL)*
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁ
45R1C 2200 Yes
TransIT Mail Exchange (TRANSIT–MAIL) for UNIX 2.0 Intel (UNIX) No
TransIT Open/OLTP Heritage Application Access
(OLTP–HAA)
3R2 2200
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TransIT Open/OLTP Transaction Manager
(OLTP–TM2200)
3R2 2200
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TransIT Open/OLTP Two-Phase Commit (OLTP–2PC)
3R2 2200
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Yes
ÁÁÁÁ
ÁÁÁÁ
Yes
ÁÁÁÁ
ÁÁÁÁ
No
ÁÁÁÁ
ÁÁÁÁ
TransIT 500 (TRANSIT–500) for UNIX 8.0 Intel (UNIX) No
Unisys Repository Manager (UREP)*
4R2 2200
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
No
ÁÁÁÁ
ÁÁÁÁ
Universal Data System Control ÁÁÁÁÁ
(UDSC)* 7R1D ÁÁÁÁ
2200 Yes
* This product is at a higher level than the same product in SB6 Delta 2
ÁÁÁÁ
ÁÁÁÁ

Migrating from ClearPath Release 1.0 to 2.0
D–4
Table D–3 lists the changed software products for CPIX2.0-SB5, the SB5R4 Delta 2 based
version of ClearPath release 2.0.
Table D–3. Changed Products for CPIX2.0-SB5
(SB5R4D2 Based Release)
Product
Communications Management System 1100
(CMS1100)*
Product
Level
8R3 2200
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Intel/
2200
IOE
Yes
ÁÁÁÁÁ
ÁÁÁÁÁ
DEPCON 3R1 2200 Yes
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
Dump Analysis Processor ÁÁÁÁÁ
(DAP)* 10R3A ÁÁÁÁÁ
2200 Yes
DMPLIB*
EXEC*
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Fault Location by Interpretive Testing (FLIT)*
MAPPER*
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Open Application Development Environment for
Windows (OADE-WIN)
3R1M 2200 ÁÁÁÁÁ Yes
44R4C 2200
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Yes
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
10R3A 2200 No
38R2B 2200 ÁÁÁÁÁ
No
1R3 Intel Yes
ÁÁÁÁÁ
ÁÁÁÁÁ
Open/OLTP Pathway (OLTP–PATHWAY) for UNIX 3R2 Intel (UNIX) Yes
Open Programming Environment (OPE)
Open Programming Environment Transaction
Processing (OPE–TP)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Oracle Transparent Gateway (ORA–TG)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Open Systems Interconnection Message Handling
System (OSI–MHS)*
ÁÁÁÁÁ
3R5 2200 Yes
5R1B 2200
3.1 2200
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Open Systems Interconnection Transaction
Processing (OSI–TP)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Open Systems Interconnection Transaction
Processing (OSI–TP)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
No
ÁÁÁÁÁ
ÁÁÁÁÁ
No
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
5R1 2200 No
ÁÁÁÁÁ
ÁÁÁÁÁ
2.0.1 (UNIX)ÁÁÁÁÁ
Intel No
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
3R2 2200 No
ÁÁÁÁÁ
ÁÁÁÁÁ
PathMate 2.0 Intel Yes
SP-Operation 4.1CP Intel Yes
Transaction Processing Utilities (TIPUTIL)*
44R4C 2200
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
* This product is at a higher level than the same product in SB5R4 Delta 2
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
Yes
ÁÁÁÁÁ
ÁÁÁÁÁ
continued
ÁÁÁÁÁ
7848 4078–004

Migrating from ClearPath Release 1.0 to 2.0
Table D–3. Changed Products for CPIX2.0-SB5
(SB5R4D2 Based Release) (cont.)
Product Intel/
Product Level 2200 IOE
TransIT Mail Exchange (TRANSIT–MAIL) for UNIX 2.0 Intel (UNIX) No
TransIT Open/OLTP Heritage Application Access
(OLTP–HAA)
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
TransIT Open/OLTP Transaction Manager
(OLTP–TM2200)
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
3R2 2200 ÁÁÁÁ Yes
ÁÁÁÁ
ÁÁÁÁ
3R2 2200 ÁÁÁÁ Yes
ÁÁÁÁ
ÁÁÁÁ
TransIT Open/OLTP Two-Phase Commit (OLTP–2PC) ÁÁÁÁÁ
3R2 2200 ÁÁÁÁ No
TransIT 500 (TRANSIT–500) for UNIX 8.0 Intel (UNIX) No
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁ
Unisys Repository Manager ÁÁÁÁÁ
(UREP)* 3R5 ÁÁÁÁ
2200 No
Universal Data System Control (UDSC)*
* This product is at a higher level than the same product in SB5R4 Delta 2
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
6R4B 2200 ÁÁÁÁ
Yes
ÁÁÁÁ
ÁÁÁÁ
7848 4078–004 D–5

Migrating from ClearPath Release 1.0 to 2.0
D.2. Installing OS 2200 Products from Fast-Load
Tape CPIX-OE1
D–6
All new and changed OS 2200 products for ClearPath release 2.0 are on fast-load tape
CPIX-OE1 (either a single tape or a two-tape set) that contains the IOE products (see
Table 8–1). To install the entire contents of that tape, refer to the procedure in 8.3. If
you wish to preserve current information, however, and selectively install new or
changed products from CPIX-OE1 when migrating, take the following steps:
1. Start the SOLAR processor by entering the following command:
@SOLAR
The SOLAR Main Menu appears.
2. Tab to Software Package Registration: Register, then press Enter.
The Package Information screen appears as shown in Figure D–1.
Figure D–1. Package Information Screen
7848 4078–004

3. In that screen enter the following information:
Migrating from ClearPath Release 1.0 to 2.0
Reel-ids—Because the tape or tapes are unlabeled, you can enter any reel
number. For example if CPIX-OE1 is on a two-reel set, enter two reel numbers
separated by a slash character (for example, CPOE1A/CPOE1B).
Assign options—Enter TJ to indicate that the tape should be assigned as a
temporary file and is unlabeled.
Device type—Enter the tape device type (for example, HICL or HIC51)
4. Press F5 to commit the information entered.
The Runstream Information screen appears as shown in Figure D–2.
5. Change the information in that screen as needed (refer to the SOLAR End Use
Reference Manual for detailed information). If you want to start the runstream now,
move the cursor to the Do you wish to start (@START) the runstream now? field,
then change N to Y and press F5.
The CPIX-OE1 package is registered with SOLAR.
Figure D–2. Runstream Information Screen
7848 4078–004 D–7

Migrating from ClearPath Release 1.0 to 2.0
D–8
6. When the run finishes, tab to Software Installation: Registered Packages, then press
Enter.
A list of registered packages appears in a screen similar to Figure D–3.
7. In that screen, tab to CPIX-OE1 with the correct level, then press F8 to view the
products contained on the CPIX-OE1 tape.
A list of products appears in a screen similar to Figure D–4.
8. Tab to the product you want to install and place a non-blank character in the
selection field to mark it for selection.
9. When done, press F5 to commit the selection or selections.
The products are installed from the CPIX-OE1 tape.
10. When done, press F2 to exit SOLAR.
Figure D–3. Registered Package Menu
7848 4078–004

Migrating from ClearPath Release 1.0 to 2.0
Figure D–4. Product Selection Screen
D.3. Updating the UNIX Node (UNIX on Intel Node)
Caution
This procedure reformats logical drive unit 1 of the UNIX node. Before proceeding,
prevent loss of data by backing up the drive unit using procedures in Section 9 of
the UNIX System V Release 4.0, System Administrator’s Guide, Volume 1.
This procedure is necessary only if the site wishes to upgrade without reinstalling the
UNIX node software.
Take the following steps to upgrade the UNIX node to ClearPath release 2.0 software:
1. If you are not already logged on, log on as root (superuser) (see 5.6).
2. Enter the following command to remove the old tuning script:
pkgrm cptune (or cd /var/sadm/pkg, rm –r cptune)
3. Insert the diskette containing the new tuning script (labeled “CPTUNE 2.0”) into the
drive unit, then enter the following command to add the new tuning script from
diskette:
pkgadd –d diskette1 cptune
7848 4078–004 D–9

Migrating from ClearPath Release 1.0 to 2.0
D–10
4. Enter the following command to copy the configuration file for Distributed
Transaction Processing (DTP) On-line Transaction Processing (DTP-OLTP) to the
/usr/lbin directory:
cp /var/sadm/pkg/cptune/install/dtpconfig /usr/lbin
5. If you have not done so already, back up logical drive unit 1 of the UNIX node
according to procedures in Section 9 of the UNIX System V Release 4.0, System
Administrator’s Guide, Volume 1.
6. Reformat logical drive unit 1 using one of the following methods:
If drive 1 has no data on it, enter the following command to reformat the drive:
scsiformat –u /dev/rdsk/c0.0d1 /var/sadm/pkg/cptune/install/desc.drv1_3slc
If drive 1 needs to be partitioned with other directories for data, take the following
steps:
a. Enter the diskadd command as follows:
diskadd
b. Enter the number of partitions (minimum 4).
c. Partition 1 must be 2 GB and must remain as raw disk space for swap space.
d. Partitions 2 and 3 must be 5 MB each and must remain as raw disk space.
e. The remainder of the disk may be partitioned as necessary.
7. If you had data on logical drive 1, restore it to directories that were created on
drive 1 using the restore procedures in Section 10 of the UNIX System V Release 4.0,
System Administrator’s Guide, Volume 1.
8. Insert the OLTP-PATHWAY installation tape into the drive unit and enter the
following command to install it:
pkgadd –d ctape1 pathway
9. Copy new tuning parameters by entering the following command:
cp /var/sadm/pkg/cptune/install/kern.61000 /etc/conf/cf.d/stune
10. Rebuild the UNIX kernel by entering this command:
idbuild
11. Enter the following command to reboot:
shutdown –y –g0 –i6
7848 4078–004

Migrating from ClearPath Release 1.0 to 2.0
D.4. Migrating SPO/HMP Console Software
This subsection describes
Use of login names during the upgrade (D.4.1)
Installation scenarios to use (D.4.2)
How to change the logging directory (D.4.3)
Detailed migration guidelines are provided in the Single Point Operations
Console/Enterprise Server Edition Installation Guide.
D.4.1. Use of Login Names
When you install a SPO/HMP Console software upgrade do the following:
1. Specify the same administrator login name and group name in the new release as in
the previous release. The administrator login name is the owner name for all
SPO/HMP Console software files.
2. Specify the same operator login names in the new release as in the previous release.
This causes the scripts that start the software to be updated with the new
installation directory location and changes to the scripts.
Advantages of this approach are:
You can use the same administrator login name, group name, and operator login
names that you are currently using.
You do not have to add a new administrator to your system nor modify the old
administrator login name because of a new group name.
You do not have to modify the old operator login names because of a new group
name.
D.4.2. Installation Scenarios
Scenario 1
You can use various methods to upgrade your SPO/HMP Console software as described
in the following subsections.
1. Use the pkgrm command to remove all versions of SPO/HMP Console software and
corresponding features from your system. If a question about feature removal
appears during the removal process, select the default answer “n” to not remove the
site–dependent data directory (sp_data_directory).
2. Specify the same installation directory for the new level of software as for the
previous release (sp_installation_directory).
7848 4078–004 D–11

Migrating from ClearPath Release 1.0 to 2.0
Scenario 2
Scenario 3
D–12
3. Specify the same site-dependent data directory for the new level of software as for
the previous release (sp_data_directory).
Advantages of this approach are
Your site-dependent data is saved and reused by the new level of software. You may
have to execute SPOCU to use your old configuration data with the new level.
Disk space on your system is conserved by using the same installation directory as
in the previous release.
A disadvantage of using this scenario is that you cannot return to the previous level,
unless you manually save the data used with the previous level before installing the new
level.
1. Install the new level of SPO/HMP Console software in new directory locations.
2. Specify a new installation directory for the new level of software that is different
from the previous release (sp_installation_directory).
3. Specify a new site-dependent data directory for the new level of software that is
different from the previous release (sp_data_directory).
Advantages of this approach are
Your previous site-dependent data is reusable by the new level of software because
the new release copies your previous site-dependent data to the new
site-dependent-data directory. You may have to execute SPOCU to use your old
configuration data with the new level.
You can execute your previous level and the new level completely independent of
each other.
You can use the previous level as a backup, but be sure that you use the correct level
of daemons.
A disadvantage of using this scenario is that it requires additional disk space.
1. Use the pkgrm command to remove all versions of SPO/HMP Console software and
corresponding features from your system. If a question about feature removal
appears during the removal process, select the default answer “n” to not remove the
site-dependent data directory (sp_data_directory).
2. Specify a new installation directory for the new level that is different from the
previous release (sp_installation_directory).
3. Specify the same site-dependent data directory for the new level as for the previous
release (sp_data_directory).
7848 4078–004

Advantages of this approach are:
Migrating from ClearPath Release 1.0 to 2.0
Your site-dependent data is saved and reused by the new level of software. You may
have to execute SPOCU to use your old configuration data with the new level.
Disk space on your system is reallocated by using a new installation directory that is
different from the previous release, possibly in a new file system.
D.4.3. Changing the Logging Directory
For the initial installation of SPO/HMP Console software, the default logging directory is
/var/opt/spo/SPO_Log. The files in a previously used logging directory are not changed
or deleted during installation.
To change the logging directory after you have installed SPO/HMP Console software, do
the following:
1. Terminate the daemons (see Section 4 of the Single Point Operations
Console/Enterprise Server Edition Installation Guide).
2. In a terminal window, execute the movelogdir script in the sp_installation_directory.
The sp_installation_directory is where SPO/HMP Console software is installed.
3. If you used Log Administration from SPO Console to configure log message sources
before, you have two options:
You can save both the existing log configuration and the log files. Do this by
copying the entire contents of the old logging directory into a new logging
directory.
You can save the existing logging configuration, but not the log files. Do this by
copying only the splstatus file from the old logging directory into the new
logging directory. SPO/HMP Console software uses the old logging
configuration information and automatically updates the number of files saved
for each message source.
Make sure that you do not change the permissions on the files that you move.
Also, make sure that the owner and the group name match the owner and group
name used during installation of the SPO/HMP Console software software.
4. Restart the daemons, either automatically by rebooting, or manually (see Section 4
of the Single Point Operations Console/Enterprise Server Edition Installation
Guide).
7848 4078–004 D–13

Appendix E
Request for Comments (RFC) 1918
Network Working Group Y. Rekhter
Request for Comments: 1918 Cisco Systems
Obsoletes: 1627, 1597 B. Moskowitz
BCP: 5 Chrysler Corp.
Category: Best Current Practice D. Karrenberg
RIPE NCC
G. J. de Groot
RIPE NCC
E. Lear
Silicon Graphics, Inc.
Status of this Memo
Address Allocation for Private Internets
February 1996
This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements. Distribution of this memo is unlimited.
1. Introduction
For the purposes of this document, an enterprise is an entity
autonomously operating a network using TCP/IP and in particular
determining the addressing plan and address assignments within that
network.
This document describes address allocation for private internets.
The allocation permits full network layer connectivity among all hosts
inside an enterprise as well as among all public hosts of different
enterprises. The cost of using private internet address space is the
potentially costly effort to renumber hosts and networks between
public and private.
2. Motivation
With the proliferation of TCP/IP technology worldwide, including
outside the Internet itself, an increasing number of non–connected
enterprises use this technology and its addressing capabilities for
sole intra–enterprise communications, without any intention to ever
directly connect to other enterprises or the Internet itself.
The Internet has grown beyond anyone’s expectations. Sustained
exponential growth continues to introduce new challenges. One
challenge is a concern within the community that globally unique
address space will be exhausted. A separate and far more pressing
concern is that the amount of routing overhead will grow beyond the
Rekhter, et al Best Current Practice [Page 1]
7848 4078–004 E–1

Request for Comments (RFC) 1918
E–2
RFC 1918 Address Allocation for Private Internets February 1996
capabilities of Internet Service Providers. Efforts are in progress
within the community to find long term solutions to both of these
problems. Meanwhile it is necessary to revisit address allocation
procedures, and their impact on the Internet routing system.
To contain growth of routing overhead, an Internet Provider obtains a
block of address space from an address registry, and then assigns to
its customers addresses from within that block based on each customer
requirement. The result of this process is that routes to many
customers will be aggregated together, and will appear to other
providers as a single route [RFC1518], [RFC1519]. In order for route
aggregation to be effective, Internet providers encourage customers
joining their network to use the provider’s block, and thus renumber
their computers. Such encouragement may become a requirement in the
future.
With the current size of the Internet and its growth rate it is no
longer realistic to assume that by virtue of acquiring globally
unique IP addresses out of an Internet registry an organization that
acquires such addresses would have Internet–wide IP connectivity once
the organization gets connected to the Internet. To the contrary, it
is quite likely that when the organization would connect to the
Internet to achieve Internet–wide IP connectivity the organization
would need to change IP addresses (renumber) all of its public hosts
(hosts that require Internet–wide IP connectivity), regardless of
whether the addresses used by the organization initially were
globally unique or not.
It has been typical to assign globally unique addresses to all hosts
that use TCP/IP. In order to extend the life of the IPv4 address
space, address registries are requiring more justification than ever
before, making it harder for organizations to acquire additional
address space [RFC1466].
Hosts within enterprises that use IP can be partitioned into three
categories:
Category 1: hosts that do not require access to hosts in other
enterprises or the Internet at large; hosts within
this category may use IP addresses that are
unambiguous within an enterprise, but may be
ambiguous between enterprises.
Category 2: hosts that need access to a limited set of outside
services (e.g., E–mail, FTP, netnews, remote login)
which can be handled by mediating gateways (e.g.,
application layer gateways). For many hosts in this
category an unrestricted external access (provided
Rekhter, et al Best Current Practice [Page 2]
7848 4078–004

Request for Comments (RFC) 1918
RFC 1918 Address Allocation for Private Internets February 1996
via IP connectivity) may be unnecessary and even
undesirable for privacy/security reasons. Just like
hosts within the first category, such hosts may use
IP addresses that are unambiguous within an
enterprise, but may be ambiguous between
enterprises.
Category 3: hosts that need network layer access outside the
enterprise (provided via IP connectivity); hosts in
the last category require IP addresses that are
globally unambiguous.
We will refer to the hosts in the first and second categories as
”private”. We will refer to the hosts in the third category as
”public”.
Many applications require connectivity only within one enterprise and
do not need external (outside the enterprise) connectivity for the
majority of internal hosts. In larger enterprises it is often easy to
identify a substantial number of hosts using TCP/IP that do not need
network layer connectivity outside the enterprise.
Some examples, where external connectivity might not be required,
are:
– A large airport which has its arrival/departure displays
individually addressable via TCP/IP. It is very unlikely
that these displays need to be directly accessible from
other networks.
– Large organizations like banks and retail chains are
switching to TCP/IP for their internal communication. Large
numbers of local workstations like cash registers, money
machines, and equipment at clerical positions rarely need
to have such connectivity.
– For security reasons, many enterprises use application
layer gateways to connect their internal network to the
Internet. The internal network usually does not have
direct access to the Internet, thus only one or more
gateways are visible from the Internet. In this case, the
internal network can use non–unique IP network numbers.
– Interfaces of routers on an internal network usually do not
need to be directly accessible from outside the enterprise.
Rekhter, et al Best Current Practice [Page 3]
7848 4078–004 E–3

Request for Comments (RFC) 1918
E–4
RFC 1918 Address Allocation for Private Internets February 1996
3. Private Address Space
The Internet Assigned Numbers Authority (IANA) has reserved the
following three blocks of the IP address space for private internets:
10.0.0.0 – 10.255.255.255 (10/8 prefix)
172.16.0.0 – 172.31.255.255 (172.16/12 prefix)
192.168.0.0 – 192.168.255.255 (192.168/16 prefix)
We will refer to the first block as “24–bit block”, the second as
“20–bit block”, and to the third as “16–bit” block. Note that (in
pre–CIDR notation) the first block is nothing but a single class A
network number, while the second block is a set of 16 contiguous
class B network numbers, and third block is a set of 256 contiguous
class C network numbers.
An enterprise that decides to use IP addresses out of the address
space defined in this document can do so without any coordination
with IANA or an Internet registry. The address space can thus be used
by many enterprises. Addresses within this private address space will
only be unique within the enterprise, or the set of enterprises which
choose to cooperate over this space so they may communicate with each
other in their own private internet.
As before, any enterprise that needs globally unique address space is
required to obtain such addresses from an Internet registry. An
enterprise that requests IP addresses for its external connectivity
will never be assigned addresses from the blocks defined above.
In order to use private address space, an enterprise needs to
determine which hosts do not need to have network layer connectivity
outside the enterprise in the foreseeable future and thus could be
classified as private. Such hosts will use the private address space
defined above. Private hosts can communicate with all other hosts
inside the enterprise, both public and private. However, they cannot
have IP connectivity to any host outside of the enterprise. While not
having external (outside of the enterprise) IP connectivity private
hosts can still have access to external services via mediating
gateways (e.g., application layer gateways).
All other hosts will be public and will use globally unique address
space assigned by an Internet Registry. Public hosts can communicate
with other hosts inside the enterprise both public and private and
can have IP connectivity to public hosts outside the enterprise.
Public hosts do not have connectivity to private hosts of other
enterprises.
Rekhter, et al Best Current Practice [Page 4]
7848 4078–004

Request for Comments (RFC) 1918
RFC 1918 Address Allocation for Private Internets February 1996
Moving a host from private to public or vice versa involves a change
of IP address, changes to the appropriate DNS entries, and changes to
configuration files on other hosts that reference the host by IP
address.
Because private addresses have no global meaning, routing information
about private networks shall not be propagated on inter–enterprise
links, and packets with private source or destination addresses
should not be forwarded across such links. Routers in networks not
using private address space, especially those of Internet service
providers, are expected to be configured to reject (filter out)
routing information about private networks. If such a router receives
such information the rejection shall not be treated as a routing
protocol error.
Indirect references to such addresses should be contained within the
enterprise. Prominent examples of such references are DNS Resource
Records and other information referring to internal private
addresses. In particular, Internet service providers should take
measures to prevent such leakage.
4. Advantages and Disadvantages of Using Private Address Space
The obvious advantage of using private address space for the Internet
at large is to conserve the globally unique address space by not
using it where global uniqueness is not required.
Enterprises themselves also enjoy a number of benefits from their
usage of private address space: They gain a lot of flexibility in
network design by having more address space at their disposal than
they could obtain from the globally unique pool. This enables
operationally and administratively convenient addressing schemes as
well as easier growth paths.
For a variety of reasons the Internet has already encountered
situations where an enterprise that has not been connected to the
Internet had used IP address space for its hosts without getting this
space assigned from the IANA. In some cases this address space had
been already assigned to other enterprises. If such an enterprise
would later connects to the Internet, this could potentially create
very serious problems, as IP routing cannot provide correct
operations in presence of ambiguous addressing. Although in principle
Internet Service Providers should guard against such mistakes through
the use of route filters, this does not always happen in practice.
Using private address space provides a safe choice for such
enterprises, avoiding clashes once outside connectivity is needed.
Rekhter, et al Best Current Practice [Page 5]
7848 4078–004 E–5

Request for Comments (RFC) 1918
E–6
RFC 1918 Address Allocation for Private Internets February 1996
A major drawback to the use of private address space is that it may
actually reduce an enterprise’s flexibility to access the Internet.
Once one commits to using a private address, one is committing to
renumber part or all of an enterprise, should one decide to provide
IP connectivity between that part (or all of the enterprise) and the
Internet. Usually the cost of renumbering can be measured by
counting the number of hosts that have to transition from private to
public. As was discussed earlier, however, even if a network uses
globally unique addresses, it may still have to renumber in order to
acquire Internet–wide IP connectivity.
Another drawback to the use of private address space is that it may
require renumbering when merging several private internets into a
single private internet. If we review the examples we list in Section
2, we note that companies tend to merge. If such companies prior to
the merge maintained their uncoordinated internets using private
address space, then if after the merge these private internets would
be combined into a single private internet, some addresses within the
combined private internet may not be unique. As a result, hosts with
these addresses would need to be renumbered.
The cost of renumbering may well be mitigated by development and
deployment of tools that facilitate renumbering (e.g. Dynamic Host
Configuration Protocol (DHCP)). When deciding whether to use private
addresses, we recommend to inquire computer and software vendors
about availability of such tools. A separate IETF effort (PIER
Working Group) is pursuing full documentation of the requirements and
procedures for renumbering.
5. Operational Considerations
One possible strategy is to design the private part of the network
first and use private address space for all internal links. Then plan
public subnets at the locations needed and design the external
connectivity.
This design does not need to be fixed permanently. If a group of one
or more hosts requires to change their status (from private to public
or vice versa) later, this can be accomplished by renumbering only
the hosts involved, and changing physical connectivity, if needed. In
locations where such changes can be foreseen (machine rooms, etc.),
it is advisable to configure separate physical media for public and
private subnets to facilitate such changes. In order to avoid major
network disruptions, it is advisable to group hosts with similar
connectivity needs on their own subnets.
Rekhter, et al Best Current Practice [Page 6]
7848 4078–004

Request for Comments (RFC) 1918
RFC 1918 Address Allocation for Private Internets February 1996
If a suitable subnetting scheme can be designed and is supported by
the equipment concerned, it is advisable to use the 24–bit block
(class A network) of private address space and make an addressing
plan with a good growth path. If subnetting is a problem, the 16–bit
block (class C networks), or the 20–bit block (class B networks) of
private address space can be used.
One might be tempted to have both public and private addresses on the
same physical medium. While this is possible, there are pitfalls to
such a design (note that the pitfalls have nothing to do with the use
of private addresses, but are due to the presence of multiple IP
subnets on a common Data Link subnetwork). We advise caution when
proceeding in this area.
It is strongly recommended that routers which connect enterprises to
external networks are set up with appropriate packet and routing
filters at both ends of the link in order to prevent packet and
routing information leakage. An enterprise should also filter any
private networks from inbound routing information in order to protect
itself from ambiguous routing situations which can occur if routes to
the private address space point outside the enterprise.
It is possible for two sites, who both coordinate their private
address space, to communicate with each other over a public network.
To do so they must use some method of encapsulation at their borders
to a public network, thus keeping their private addresses private.
If two (or more) organizations follow the address allocation
specified in this document and then later wish to establish IP
connectivity with each other, then there is a risk that address
uniqueness would be violated. To minimize the risk it is strongly
recommended that an organization using private IP addresses choose
randomly from the reserved pool of private addresses, when allocating
sub–blocks for its internal allocation.
If an enterprise uses the private address space, or a mix of private
and public address spaces, then DNS clients outside of the enterprise
should not see addresses in the private address space used by the
enterprise, since these addresses would be ambiguous. One way to
ensure this is to run two authority servers for each DNS zone
containing both publically and privately addressed hosts. One server
would be visible from the public address space and would contain only
the subset of the enterprise’s addresses which were reachable using
public addresses. The other server would be reachable only from the
private network and would contain the full set of data, including the
private addresses and whatever public addresses are reachable the
private network. In order to ensure consistency, both servers should
be configured from the same data of which the publically visible zone
Rekhter, et al Best Current Practice [Page 7]
7848 4078–004 E–7

Request for Comments (RFC) 1918
E–8
RFC 1918 Address Allocation for Private Internets February 1996
only contains a filtered version. There is certain degree of
additional complexity associated with providing these capabilities.
6. Security Considerations
Security issues are not addressed in this memo.
7. Conclusion
With the described scheme many large enterprises will need only a
relatively small block of addresses from the globally unique IP
address space. The Internet at large benefits through conservation of
globally unique address space which will effectively lengthen the
lifetime of the IP address space. The enterprises benefit from the
increased flexibility provided by a relatively large private address
space. However, use of private addressing requires that an
organization renumber part or all of its enterprise network, as its
connectivity requirements change over time.
8. Acknowledgments
We would like to thank Tony Bates (MCI), Jordan Becker (ANS), Hans–
Werner Braun (SDSC), Ross Callon (BayNetworks), John Curran (BBN
Planet), Vince Fuller (BBN Planet), Tony Li (cisco Systems), Anne
Lord (RIPE NCC), Milo Medin (NSI), Marten Terpstra (BayNetworks),
Geza Turchanyi (RIPE NCC), Christophe Wolfhugel (Pasteur Institute),
Andy Linton (connect.com.au), Brian Carpenter (CERN), Randy Bush
(PSG), Erik Fair (Apple Computer), Dave Crocker (Brandenburg
Consulting), Tom Kessler (SGI), Dave Piscitello (Core Competence),
Matt Crawford (FNAL), Michael Patton (BBN), and Paul Vixie (Internet
Software Consortium) for their review and constructive comments.
9. References
[RFC1466] Gerich, E., ”Guidelines for Management of IP Address
Space”, RFC 1466, Merit Network, Inc., May 1993.
[RFC1518] Rekhter, Y., and T. Li, ”An Architecture for IP Address
Allocation with CIDR”, RFC 1518, September 1993.
[RFC1519] Fuller, V., Li, T., Yu, J., and K. Varadhan, ”Classless
Inter–Domain Routing (CIDR): an Address Assignment and
Aggregation Strategy”, RFC 1519, September 1993.
Rekhter, et al Best Current Practice [Page 8]
7848 4078–004

Request for Comments (RFC) 1918
RFC 1918 Address Allocation for Private Internets February 1996
10. Authors’ Addresses
Yakov Rekhter
Cisco systems
170 West Tasman Drive
San Jose, CA, USA
Phone: +1 914 528 0090
Fax: +1 408 526–4952
EMail: yakov@cisco.com
Robert G Moskowitz
Chrysler Corporation
CIMS: 424–73–00
25999 Lawrence Ave
Center Line, MI 48015
Phone: +1 810 758 8212
Fax: +1 810 758 8173
EMail: rgm3@is.chrysler.com
Daniel Karrenberg
RIPE Network Coordination Centre
Kruislaan 409
1098 SJ Amsterdam, the Netherlands
Phone: +31 20 592 5065
Fax: +31 20 592 5090
EMail: Daniel.Karrenberg@ripe.net
Geert Jan de Groot
RIPE Network Coordination Centre
Kruislaan 409
1098 SJ Amsterdam, the Netherlands
Phone: +31 20 592 5065
Fax: +31 20 592 5090
EMail: GeertJan.deGroot@ripe.net
Eliot Lear
Mail Stop 15–730
Silicon Graphics, Inc.
2011 N. Shoreline Blvd.
Mountain View, CA 94043–1389
Phone: +1 415 960 1980
Fax: +1 415 961 9584
EMail: lear@sgi.com
Rekhter, et al Best Current Practice [Page 9]
7848 4078–004 E–9

Appendix F
Configuring the FDDI Interconnect
The SCMS database and operations database (ODB) are provided prebuilt from the
factory. If you need to recreate them at the site for some reason, you must configure
FDDI connections as described in this appendix.
Cautions
Naming conventions used in the SCMS procedures must be followed for
PathMate to operate correctly.
Modification of the SCMS configuration requires a stop of all partitions to allow
reloading of the SCMS generated ODB files. Use procedures described in the
ClearPath HMP IX Series Operations Guide to deactivate active partitions.
F.1. Configuring the 2200 FDDI Connection
To configure the FDDI connection at the 2200 node you must reboot the master system
console in SDF online mode and use the SCMS software to
Define the logical system configuration
Generate ODB files that you can load into the SCF workstation and use to reboot the
2200 node
Note: The Site Configuration Management System (SCMS) Administration Guide
Volume 1, Reference Information describes detailed procedures for using the
SCMS software.
A critical aspect of setting up the logical system configuration is configuring the FDDI
channel that connects the 2200 node and the Intel node. This section describes how to
change the SCMS system definition to include an FDDI channel if it has not already been
configured.
The type of system you have determines how the FDDI channel is connected as follows:
IX4400 server—The FDDI connection is provided by a Host LAN Controller-2
(HLC-2) or an FDDI channel card.
IX4600 or IX4800 server—The FDDI connection is provided by an FDDI channel
card.
This following subsections describe how to configure each type of server.
7848 4078–004 F–1

Configuring the FDDI Interconnect
F.1.1. IX4400 Server Component Configuration (HLC2)
F–2
ClearPath HMP IX4400 servers contain the following hardware components that you
must configure using SCMS:
Processing complex cabinet 0 (PCC0) contains a dedicated input/output processor
(IOP).
That IOP connects to block multiplexer channels (BMC) in a BMC rack in PCC0.
A Host LAN Controller-2 (HLC-2) connects to a BMC channel.
The HLC-2 contains an FDDI channel card that connects to an EISA FDDI card in
the Intel node.
The HLC-2 contains an Ethernet feature, if needed, to make a TCP/IP connection to
a site’s production LAN.
Note: A TCP/IP Ethernet connection to the site’s production LAN is required. If a
connection does not already exist, the connection can be made through the
HLR2-EDF Ethernet feature.
Configure those components as follows:
1. Power on or reboot the SCF workstation (master system console) in SDF online
mode.
2. Using SCMS, add a 4.5-MB-per-second block multiplexer channel input/output
processor module (IOPM-BMC-4.5) to the processor complex cabinet (PCC)
configuration. Select that module from the PCC feature screen as follows:
7848 4078–004

Configuring the FDDI Interconnect
3. Configure the HLC-2 to match the hardware configuration as follows:
a. Add an HLC-2 unit to inventory and assign it whatever name is appropriate for
the site.
b. Add the FDDI feature to location 00 (the A position) in the HLC-2. Make sure
the feature component name is FDDIVI.
Note: The name FDDIVI is required for later use by automated
configuration tools.
c. Exit from the inventory add procedure.
d. Modify inventory to add the Ethernet feature to the HLC-2 in location 01 (the B
position).
e. Exit to the main menu of SCMS.
f. Use System_include to include the HLC-2 in the system configuration.
4. Make Host LAN Controller-2 (HLC-2) connections by selecting the Subsystem option
from the System_Connect menu. Then select the HLC-2 to which to make the FDDI
connection. This screen appears as follows:
7848 4078–004 F–3

Configuring the FDDI Interconnect
F–4
5. In that screen, define the channels to which the HLC-2 is connected and specify the
contents of the HLC-2 cabinet as shown in the following screen:
6. Modify the HLC-2 subsystem media access control (MAC) address and channel
address configuration parameters as appropriate as shown in the following screen.
The MAC address can be read from the HLC-2 maintenance panel menu.
7. Verify/lock the system and partitions, create and mark the partitions, and send the
ODB to a floppy disk or tape, whichever is preferred.
8. Reboot the SCF in offline mode and load the new ODB.
9. Reboot the SCF in online mode, then reboot the 2200 node.
7848 4078–004

F.1.2. IX4600 or IX4800 Component Configuration
Configuring the FDDI Interconnect
IX4600 or IX4800 servers need the following hardware components configured in SCMS
system inventory:
A Power Domain (PWRD) with at least one CSIOP for the required FDDI and
Ethernet connections. The CSIOP is identified by Feature Name IOPM–CS under
PWRD.
Connect the FDDI/Ethernet channel adapters to Bus0 of physical IOP0 in Power
Domain 0.
An FDDI control unit (CS–FDDI) to provide the 2200 connection to the FDDI port in
the UNIX node. This control unit must be named FDDIVI for proper OS 2200
identification. With that name, SCMS automatically names the devices as HLVI01
(address=1 type=output) and HLVI02 (address=2 type=input). Do not change those
names. No parameter changes are needed in System_Connect/Subsystem.
An Ethernet control unit (CS–ETH) to provide the 2200 connection to the site’s
production LAN. There is no special naming for this control unit and no parameter
changes are needed in System_Connect/Subsystem.
F.2. Configuring the UNIX Node FDDI Connection
The UNIX node FDDI connection is configured when the tuning script is run during
procedures described in Section 5.
7848 4078–004 F–5

Glossary
A
ACID properties
A term coined by Andreas Reuter to summarize the properties that online transaction
processing (OLTP) systems must demonstrate in order to be useful. ACID stands for
atomicity, which means a transaction is an indivisible unit of work (all actions succeed
or fail); consistency, which means a transaction must either leave the system in a new,
correct state or return the system to its initial state; isolation, which means a transaction
is not affected by other transactions that may be executing concurrently; and durability,
which means that, once the changes are committed, the results of a transaction are
permanent, even if system failures occur.
alias
AMS
See network alias.
See Autoaction Message System.
AMS database
The patterns and associated actions used by the Autoaction Message System that allow
it to automatically recognize and respond to OS 2200 console messages.
asynchronous transfer mode (ATM)
An emerging standard for high-speed, cell-switching network services. The ATM
standard defines an access method that can be used for both local and wide area
networking. ATM is intended to provide a common, efficient service for communication
of data, nvoice, video, and images.
ATM
See asynchronous transfer mode.
Autoaction Message System (AMS)
A component of SMART (residing on OS 2200 system consoles) that provides automatic
message recognition and corresponding actions to enable the system to run without an
operator.
7848 4078–004 Glossary–1

Glossary
B
backup domain controller (BDC)
One or more computers that maintain a replicated copy of the security and user account
database for a Windows NT domain. A backup domain controller can authenticate user
logons for a domain. A backup domain controller also can be promoted to function as
the primary domain controller.
basic input/output system (BIOS)
Instructions stored on read-only memory that provide the lowest level interface to
peripheral devices. The BIOS performs an autostart routine that tests for peripheral
devices on startup. After preparing pointers (interrupt vectors) to allow access to its
routines by device drivers and application programs, the BIOS loads the operating
system and passes control to it.
BDC
BIOS
C
CERN
CGI
Glossary–2
See backup domain controller.
See basic input/output system.
Abbreviation for Conseil Européen pour la Recherche Nucléaire (European Laboratory
for Particle Physics), the origin of the World Wide Web. CERN is where much of the
original Web software was developed, including the first Web server and Web browser
software.
See common gateway interface.
channel service I/O processor (CSIOP)
A processor that handles input/output operations between instruction processors and
channels in the 2200 Series component of ClearPath IX4800 servers.
CIT
See ClearPath Installation and Tuning (CIT) diskette.
classification
A defined set of component classes that can be monitored simultaneously by Status. A
classification is independent of a particular SPO Console configuration.
ClearPath Installation and Tuning (CIT) diskette
A diskette containing a UNIX shell script. When installed and run, the script
automatically determines the hardware configuration of the UNIX node; it repartitions
and sets up the UNIX operating system accordingly.
7848 4078–004

client
CMOS
Glossary
Typically, a desktop personal computer that communicates with other PCs, a server, or a
host computer.
See complementary metal-oxide semiconductor.
common gateway interface (CGI)
(1) A standard that defines the mechanism by which Web server software communicates
with executable programs on the Web server. This enables the Web server software to
call executables to help fulfill requests. (2) A standard that defines the use of
environment variables set by a server program before it transfers data to an executable
program. The environment variables are available to both the server program and the
executable program and govern how data is transferred between the programs.
complementary metal-oxide semiconductor (CMOS)
A semiconductor device made up of two metal-oxide semiconductor transistors (each a
different type), integrated on a single silicon chip. Such devices run at very high speeds
and have extremely low power requirements. The Intel and custom processors in
ClearPath IX servers use CMOS technology.
component class
A group of similar components, such as hosts, instruction processors, or processes
monitored by single point status. All components within a class have the same
attributes.
component group
A collection of components that a site has decided to represent as a single icon in the
status diagram of Single Point Status. Components in a component group are selected
based on the name of the component, the class of the component, and the host on which
the component resides.
configuration
A definition of the host systems that SPO/HMP Console monitors and controls. The
definition also specifies the means of connection for each system.
CSIOP
D
daemon
See channel service I/O processor.
A background process, often perpetual, that performs a system-wide public function.
Daemons run on the Single Point Operations (SPO) server in the background and
perform various services, including the management of all network activity pertaining to
SPO/HMP Console. The daemons must be running in order to run SPO/HMP Console.
datagram
The basic unit of information passed across an internet. A datagram contains a source
and a destination, as well as the data packet.
7848 4078–004 Glossary–3

Glossary
directory service agent (DSA)
The server component defined in the X.500 standard for global directories. The DSA
executes requests from directory user agents (DUA) to read and update the directory
entries on the global directory server.
directory user agent (DUA)
The client component defined in the X.500 standard for global directories. An
application on a client workstation uses a local DUA to read and update the directory
entries on a global directory server.
distributed transaction processing (DTP)
A type of online transaction processing (OLTP) in which transactions are distributed
across multiple databases and systems instead of being executed against one database
on one system. X/Open has defined a widely accepted DTP reference model that defines
the relationship between OLTP applications, resource managers (such as database
management systems), transaction managers (which control the execution of
transactions), and communications resource managers (which control communications
between distributed applications). TransIT Open/OLTP and BEA Tuxedo software are
two examples of software products that comply with the X/Open DTP model.
DLL
DNS
domain
Glossary–4
See dynamic link library.
See domain name system.
A logical grouping of Windows NT network servers and other computers that share
common security and user account information. Users have only one account in the
domain, thus simplifying sign-on and administration. Users log on to the domain, not to
individual servers in the domain.
domain controller
A Windows NT server that maintains a database of security and user account
information for a Windows NT domain. See also primary domain controller (PDC) and
backup domain controller (BDC).
domain name
See fully qualified domain name.
domain name system (DNS)
(Also domain name server) The mechanism that implements a hierarchical naming
scheme known as domain names for TCP/IP networks. A domain name consists of a
sequence of subnames separated by periods that identify successive levels in directory
structure. This system maps host names to IP addresses.
DSA
DTP
See directory service agent.
See distributed transaction processing.
7848 4078–004

DUA
See directory user agent.
Glossary
dynamic link library (DLL)
An executable routine that is stored as a separate file and loaded into memory only
when called by a program. DLLs are used for common functions that are needed by
more than one program. DLLs are used in the Windows and OS/2 operating systems.
E
EDI
See electronic data interchange.
electronic data interchange (EDI)
The ability to transmit business documents, such as purchase orders and invoices,
electronically over a network. The goal is to streamline conventional ordering and
billing processes by eliminating the need for paper forms and mail delivery. To be able
to implement EDI, users must agree on standards for formatting and exchanging
information. See also X.400.
Ethernet
F
FDDI
A widely implemented type of local area network (LAN) in which devices are connected
to a single network cable in a bus configuration. Any device can transmit as long as no
other devices are transmitting. In the event of a collision, an algorithm ensures that the
two devices do not transmit again at the same time. Ethernet, developed by the Xerox
Palo Alto Research Center in 1976, is the basis for the IEEE 802.3 standard for LANS
with carrier sense multiple access with collision detection (CSMA/CD).
See fiber distributed data interchange.
fiber distributed data interchange (FDDI)
A type of local area network (LAN) in which devices are connected to two concentric
fiber-optic rings. Because it uses fiber optic cable, FDDI supports higher transmission
speeds than other LAN technologies, such as Ethernet and token ring. The FDDI
standard was developed by the American National Standards Institute (ANSI).
file transfer protocol (FTP)
A program that lets you transfer data between two computers on a network.
fourth-generation language (4GL)
Programming environments that streamline the application development process by
allowing programmers to focus more on the results desired and less on the specific
programming techniques required to process the data. LINC and MAPPER are examples
of fourth-generation languages.
FQDN
See fully qualified domain name.
7848 4078–004 Glossary–5

Glossary
FTP
Glossary–6
See file transfer protocol.
fully qualified domain name (FQDN)
The full internet name of a system consisting of its local host name and its internet
domain name. For example, venera is a host name and venera.isi.edu is an FQDN.
G
group
H
A UNIX file ownership mechanism that allows files or user-ids to be grouped for the
purpose of granting file access permissions (for example, read, write, or execute). That
allows the granting or taking away of permission to access a set of files or commands by
simply adding or removing a user-id or file to or from the group. See also component
group.
heterogeneous multiprocessing (HMP)
A Unisys computing paradigm in which multiple dissimilar processors (for example,
Intel and custom CMOS processors) and operating system kernels (for example, UNIX
and OS 2200) execute as a single server.
HMP
hosts file
HTML
HTTP
See heterogeneous multiprocessing.
The TCP/IP network configuration file (typically in the directory /etc on a UNIX system)
that identifies the network addresses (IP addresses) of other hosts on the network.
See hypertext markup language.
See hypertext transfer protocol.
hypertext markup language (HTML)
The primary language used to define documents accessed over the WWW. As a markup
language, HTML uses tags to identify how the text is used (for example, a first-level
heading, paragraph, or list), as opposed to how the text should be presented. This leaves
it up to the Web browsers to determine how to present the text (for example, font, type
size, indention, and justification). HTML also allows authors to define hypertext links
between locations in the same document and between documents and multimedia
objects.
hypertext transfer protocol (HTTP)
The primary protocol for transferring data over the WWW. HTTP uses a simple
algorithm that makes fast response times possible compared to earlier protocols, such
as FTP.
7848 4078–004

Glossary
integrated operating environment (IOE)
The foundation software bundled with ClearPath HMP Series servers. The IOE includes
operating systems, a database manager, online transaction processing (OLTP) software,
integrated administration and operations software, integrated printing software, and
application development software.
Intel node
The portion of the ClearPath IX server on which the Windows NT operating environment
or the native UNIX operating environment executes.
internal LAN
The internal fiber distributed interface (FDDI) link that connects the 2200 Series
component to the SMP61000 component in the ClearPath IX server. This is a private
network with internet protocol (IP) addresses assigned from a block of addresses
reserved for private internets by the Internet Assigned Numbers Authority (IANA).
internet protocol
The protocol suite that defines the IP datagram as the unit of information passed across
an internet and is the basis for the packet delivery service. IP includes the Internet
Control Message Protocol (ICMP) control and error message protocol. The complete
communications protocol suite is referred to as TCP/IP because TCP and IP are the two
most fundamental protocols in the protocol suite.
intranet
IOE
IP
A private, enterprise-wide network that uses TCP/IP and WWW technologies.
See integrated operating environment.
See TCP/IP.
IP address
The 32-bit address assigned to hosts in a TCP/IP internet. An IP address identifies the
network to which a host is attached, as well as a specific host on that network. The IP
address usually is represented in dotted decimal notation (for example,
xxx.xxx.xxx.xxx) with each part (xxx) being a decimal number from 0 to 255
(represented by 8 bits).
L
local area network (LAN)
A data communications network that enables computers, terminals, and other data
processing resources, typically at one location, to communicate with each other.
logging
See Single Point Logging.
LT501 X terminal
See X terminal.
7848 4078–004 Glossary–7

Glossary
M
MAPI
Glossary–8
See Messaging Application Program Interface.
master configuration table (MCT)
A table built at system generation to reflect the system configuration. The MCT is an
Exec file that primarily contains system configuration information. Audit control and
Transaction Processing (TIP) use the MCT for recovery information. The MCT is
recreated on tape recovery boots.
master system console
The single system console that supports an Exec logical console for one partition and
that has full system control facility (SCF) control capabilities including partitioning,
initializing, booting, and maintaining.
MCT
See master configuration table.
message store
The software component of an X.400 mail system that accepts messages from message
transfer agents (MTA) and stores them until they are retrieved by remote user agents
(RUA).
message transfer agent (MTA)
The software component of an X.400 mail system that cooperates with other MTAs to
perform store-and-forward message delivery.
Messaging Application Program Interface (MAPI)
A Windows dynamic-link library (DLL) that provides Windows applications with access
to e-mail, message store, and address book services through a set of API calls. The
service provider can be any MAPI-compliant messaging software, such as Microsoft
Mail.
middleware
Software required to support interactions between clients and servers. Examples of
middleware are TCP/IP software, NetWare, remote procedure call (RPC) software, Open
Database Connectivity (ODBC) drivers, and client software for accessing distributed
transaction processing (DTP) applications.
Mosaic
mount
MTA
A Web browser program developed at the National Center for Supercomputing
Application (NCSA). As the first Web browser program with a graphical user interface,
Mosaic helped popularize the World Wide Web.
To integrate the local directory structure of a physical disk partition into the overall
UNIX directory hierarchy.
See message transfer agent.
7848 4078–004

N
NAS
See network access server.
Glossary
Netscape Navigator
A popular Web browser program developed by Netscape Communications Corporation.
NetWare
A popular network operating system (NOS) that enables client systems to share files and
resources (such as printers) on servers.
network access server
A hardware component that connects one or more serial devices to a LAN.
network alias
An alias, or equivalent name, for a network host name in the hosts file.
Network File System (NFS)
Client/server middleware that provides client workstations with access to files on a
server over a network. The files appear to clients much like local files. NFS was
originally written by Sun Microsystems for its UNIX workstations, but it has since been
implemented on a range of systems, from PCs to enterprise servers.
network segment
A part of an Ethernet network on which all message traffic is common to all nodes.
Specifically, a message broadcast from one node is received by all other nodes on the
segment, typically because the segment is a continuous conductor.
NFS
O
ODB
ODBC
OLTP
See Network File System.
See operations database.
See Open Database Connectivity.
See online transaction processing.
online transaction processing (OLTP)
A high-performance type of application characterized by a service request from a user
immediately followed by an action and response from a server system. A complete
request-response cycle is called a transaction. OLTP systems must meet certain criteria,
called ACID properties (atomicity, consistency, isolation, and durability), to maintain the
integrity of the data and ensure that transactions are executed correctly.
7848 4078–004 Glossary–9

Glossary
Open Database Connectivity (ODBC)
A Microsoft call level interface for Structured Query Language (SQL) that has become a
de facto standard. ODBC is an extended version of the call level interface defined by the
SQL Access Group (SAG), a consortium of database vendors. ODBC middleware
enables Windows database clients to interoperate with a variety of server databases that
would otherwise be incompatible.
Open/OLTP Pathway
A TransIT Open/OLTP middleware component that provides applications in the Intel
(UNIX or Windows NT) environment of a ClearPath IX server with a gateway to the
Open/OLTP Transaction Manager in the OS 2200 environment. This allows UNIX or
Windows NT applications to execute transactions against OS 2200 databases.
operations database (ODB)
A database populated with information unloaded from the Site Configuration
Management System (SCMS) database. The ODB contains configuration information
needed by the OS 2200 Exec to operate 2200 Series component hardware.
P
parity
Glossary–10
An extra bit added to a group of bits (for example, a byte or a word) to reveal errors in
data storage or transmission.
partition databank (PDB)
A data structure passed by the System Control Facility (SCF) to the Exec that contains
all the necessary information for the Exec to operate the hardware in the partition. The
PDB is used to build the I/O, tape translator, and other sections of the master
configuration table (MCT). The partition databank is created by the SCMS partitioning
function.
PathMate
The online integration assistant for effectively using ClearPath IX servers and creating
solutions for business problems. PathMate contains a Windows Help application that
explains and runs the other built-in components including a package of tools, working
prototype solutions, procedures, and product configuration aids.
PDB
PDC
PERL
See partition databank.
See primary domain controller.
Abbreviation for Practical Extraction and Report Language. A scripting language that
makes it easy to perform string-manipulation and parsing tasks. Common gateway
interface (CGI) scripts are often written in PERL.
7848 4078–004

Glossary
primary domain controller (PDC)
The computer running Windows NT server that directly receives and tracks changes to
the security and user account database for a Windows NT domain. Both primary and
backup domain controllers can authenticate user logons. A backup domain controller
can be promoted to function as the PDC.
protocol
A set of rules or standards describing methods to achieve compatible transmission and
receipt of data (for example, message packets) over a network.
protocol port
The abstraction that transport protocols use to distinguish between multiple
destinations within a host computer. TCP/IP protocols identify ports using small
positive integers. Usually, the operating system allows an application program to specify
which ports it wants to use. Some ports are used for standard services (for example,
electronic mail).
R
redundant array of independent disks (RAID)
(Originally, redundant array of inexpensive disks, or devices.) Multiple disk units
combined into a single logical device designed to increase data integrity and availability
by means of redundant copies of disk contents. Organization of the disks is defined by
six RAID levels—two of which (levels 1 and 5) are fault tolerant. In level 1 (disk
mirroring) disks are duplicated 100 percent on another disk for redundancy. In level 5
(striping with parity) free space across multiple disks is combined into one logical
volume and data is spread in a fixed order across those disks (striping). Parity data
saved with the striped data allows information to be recreated if a disk should fail.
remote procedure call (RPC)
A mechanism that enables processes on client systems to execute procedures stored on
remote systems. On the client side, the RPC software encapsulates the parameters for a
procedure call in a message and then sends the message to a server. The server unpacks
the parameters, calls the procedure, and then sends a response to the client.
remote user agent (RUA)
The client software of an X.400 mail system that provides remote users with access to a
message store.
router
RPC
RUA
A hardware device used to transfer packets of data from one logical network to another,
in the TCP/IP protocol.
See remote procedure call.
See remote user agent.
7848 4078–004 Glossary–11

Glossary
S
SCF
SCMS
SCU
SDF
shell
Glossary–12
See system control facility.
See Site Configuration Management System.
See System Configuration utility.
See site data facility.
The command interpreter that passes commands to the UNIX operating system. The
most common UNIX shells are the c shell and the Bourne shell.
shell script
A collection of commands stored in a file that can be executed as input to the shell
(similar to batch file commands in MS-DOS).
simple network management protocol (SNMP)
A Transmission Control Protocol/Internet Protocol (TCP/IP) that provides basic network
management in TCP/IP-based networks, which typically include hardware and software
from a variety of vendors. See also SNMP agent.
Single Point Autoaction Message System (SP-AMS)
A program that runs on the SPO server and provides automatic message recognition and
corresponding actions while monitoring ANSI X3.64-compliant (UNIX) host systems and
A Series host systems. Contrast with Autoaction Message System.
Single Point Logging
A SPO Console capability that enables a user to store, in log files at a central location, an
electronic history of messages from selectable message sources (managed host systems,
SPO Console, and external applications).
Single Point Status
A capability of Single Point Operations that lets a user monitor the status of hardware
and software components across multiple host systems. See also Status feature.
Site Configuration Management System (SCMS)
Software that runs on a site data facility (SDF) PC that is part of the System Control
Facility (SCF). SCMS is used to configure system and partition definitions of hardware
at a site. Information from the SCMS database includes an operations database (ODB)
and a partition databank (PDB). The ODB and PDB give the Exec the information
needed to operate the system hardware. The PDB is used to build several areas of the
master configuration table (MCT).
site data facility (SDF)
The personal computer hosting SCMS in the System Control Facility (SCF).
7848 4078–004

SNMP
See simple network management protocol.
Glossary
SNMP agent
A software component on a network node that collects information and performs
network management functions on behalf of authorized SNMP managers.
Communications management system (CMS) 1100 includes SNMP agent software, which
allows OS 2200 hosts to respond to requests for managed information by SNMP network
managers.
socket
SP-AMS
A software abstraction that provides the interface between application programs and
communications software.
See Single Point Autoaction Message System.
SP-AMS database
The patterns and associated actions used by the Single Point Autoaction Message
System that allows it to automatically recognize messages from UNIX and A Series host
systems and respond to these messages.
SPO Console
A software application that enables a user to monitor and control multiple host systems
from a single workstation.
SPO Console/Enterprise Server Edition (ESE)
The full-featured version of SPO Console capable of monitoring and controlling OS 2200,
A Series, UNIX, and Windows NT systems.
SPO/HMP Console
A restricted version of SPO Console, specifically adapted to monitor and control a single
ClearPath IX server.
SPO server
The UNIX hardware platform on which SPO Console runs.
SQL
See structured query language.
static page
A document object in the form of a file. The file can contain any type of data, such as
text, graphic images, video, or audio. It is not an executable program file.
Status feature
A feature of SPO Console/ESE that allows a site to define additional classifications for
use by Single Point Status and that allows new classes and attributes to be defined in
classifications provided with SPO Console.
7848 4078–004 Glossary–13

Glossary
Structured Query Language (SQL)
A specialized language for defining, retrieving, changing, and maintaining data in
databases. End users can use SQL to perform ad hoc, interactive queries. Programmers
can include SQL statements in applications written with high-level languages, such as C,
C++, and COBOL.
superuser
A privileged account with unrestricted access to all commands and all files regardless of
permissions. The user name of this account is root.
System Configuration Utility (SCU)
A software utility used to configure U 6000 Series systems that support Extended
Industry Standard Architecture expansion boards.
system console
A general term applying to any System Control Facility (SCF) workstation. System
consoles are used for system operations (Exec logical console) and system control
(partitioning, initializing, booting, and maintaining).
system control facility (SCF)
A set of workstations, connected in a local area network, that provides an operator
interface to a ClearPath IX server. The SCF provides system operator console and
system control functions through a minimum of two workstations. System configuration
functions are provided through the workstation on which the site configuration
management system (SCMS) runs (referred to as the Site Data Facility, or SDF).
T
TCP/IP
Glossary–14
Transmission Control Protocol/Internet Protocol, a set of communication rules that
specifies how data is transferred among computers on the Internet.
third-generation language (3GL)
High-level programming languages such as C, COBOL, and FORTRAN. 3GLs hide much
of the complexity of machine processing from programmers, allowing them to focus
more on the problem to be solved. Programs written in 3GLs are more
machine-independent than programs written in assembly (second-generation) languages.
token ring
A type of local area network (LAN) in which devices are connected to a network cable in
a ring configuration. Before devices can transmit, they must possess a logical token,
which is passed from device to device in sequence around the ring. When a device has
something to transmit, it labels the token as busy until the transmission is complete.
When the transmission is complete, the token is labeled not busy and the token is again
passed around the ring. The IEEE 802.5 standard defines a token ring type of network.
tuning script
An initialization program (supplied by Unisys), written in Bourne shell script, that is run
to initialize kernel parameters and partition disks and install software on the UNIX node
and SPO server of a ClearPath IX server.
7848 4078–004

Tuxedo
U
UDP
Glossary
A software product that is based on the X/Open model for distributed transaction
processing (DTP). Tuxedo was developed by AT&T, sold to Novell, and is currently
owned by BEA Systems. Tuxedo and other X/Open compliant DTP software (including
the Unisys product TransIT Open/OLTP) allows organizations to develop applications
that execute transactions across multiple systems and database types.
See user datagram protocol.
UNIX Resource Monitor (URM)
A capability of SPO Console that allows an operator to monitor file systems, CPU usage,
critical processes, long-running processes, and users on UNIX host systems. This feature
includes the UnixMon and Unix2200Mon classifications run on Single Point Status, and
URM agents run on the managed UNIX host systems.
UNIX SVR4
UNIX System V Release 4, a version of the UNIX operating system that combines
features of Berkeley Software Distribution (BSD) UNIX and earlier releases of UNIX
System V. UNIX System V was developed by UNIX System Laboratories, originally a part
of AT&T and later purchased by Novell.
UnixWare
A popular version of the UNIX operating system based on UNIX System V Release 4.2.
Santa Cruz Operation (SCO) purchased UnixWare from Novell.
unmount
To remove the local directory structure of a physical disk partition from the overall
UNIX directory hierarchy.
URM agent
A program of the Event Server API that sends event reports from a managed UNIX
system to Single Point Status running on the SPO server.
URM policy
Parameters set by the Single Point administrator that control the execution of the URM
agent on each managed UNIX system, in terms of which information to collect and how
often.
user datagram protocol (UDP)
The TCP/IP standard transport level protocol that enables an application program on
one machine to send a datagram to an application program on another machine. UDP
uses the internet protocol (IP) to send the datagram. The datagram includes a port
number enabling the sender to distinguish between multiple destinations (application
programs) on another machine.
7848 4078–004 Glossary–15

Glossary
W
Web browser
Client software for viewing documents on the World Wide Web and navigating
hyperlinks to other documents. Used with a ClearPath IX server to access the Single
View administration software on the Web.
Windows Open Services Architecture (WOSA)
A Microsoft software architecture intended to integrate Windows workstations with
back-end services on a broad range of vendors’ systems. WOSA consists of a set of
application program interfaces (API) that enable Windows client applications to access
data independent of the type of network, the software providing the services, and the
type of server system. Two examples of WOSA components are Open Database
Connectivity (ODBC) and Messaging Application Program Interface (MAPI).
World Wide Web (WWW)
A world-wide network (a subset of the Internet) that is populated by hyperlinked
documents. Web browsers such as Mosaic and Netscape hide much of the complexity of
the WWW and allow users to view multimedia documents and easily jump from one
document to another and from one Web site to another. Also referred to as the Web.
WOSA
WWW
X
X.400
X.500
X/Open
Glossary–16
See Windows Open Services Architecture.
See World Wide Web.
A standard for electronic mail developed by the International Organization for
Standardization (ISO). Products implementing the X.400 standard provide a mail
backbone across which users can send e-mail, faxes, images, and EDI documents. See
also message store, message transfer agent (MTA), and remote user agent (RUA).
A standard for global directory services developed by the International Organization for
Standardization (ISO). The X.500 standard defines protocols and interfaces that enable
client applications to read and update directory databases on global directory servers.
See also directory service agent (DSA) and directory user agent (DUA).
An international nonprofit consortium dedicated to the advancement of open systems.
Its primary activities include defining standards and branding products to ensure
interoperability between the products of different vendors.
X terminal
A terminal that provides X Window Access for Single Point Operations. For SPO/HMP
Console, an LT501 X terminal provides this capability.
7848 4078–004

X Window Access
A UNIX based GUI window environment that enables a user to perform various
functions in multiple windows on a single display screen.
3GL
4GL
See third-generation language.
See fourth-generation language.
Glossary
7848 4078–004 Glossary–17

Bibliography
ClearPath HMP IX Model 4400 Preinstallation Planning Templates (7842 6079).
Unisys Corporation.
ClearPath HMP IX Model 4600/4800 Preinstallation Planning Templates (7842 6087).
Unisys Corporation.
ClearPath HMP IX Model 4400 Installation and Service Reference (7842 6053).
Unisys Corporation.
ClearPath HMP IX Model 4600/4800 Installation and Service Reference (7842 5980).
Unisys Corporation.
ClearPath HMP IX Series Open Programming Environment (OPE) Configuration
Guide (7831 1032). Unisys Corporation.
ClearPath HMP IX Series Single View Administration Guide (7848 4086). Unisys
Corporation.
ClearPath HMP IX Series Conceptual Overview (7848 4052). Unisys Corporation.
ClearPath HMP IX Series Getting Started (7848 4060). Unisys Corporation.
ClearPath HMP IX Series Open/OLTP Pathway Installation and Operations Guide
(7848 4409). Unisys Corporation.
ClearPath HMP IX Series Operations Guide (7848 4094). Unisys Corporation.
ClearPath HMP IX Series Web Services Programming Guide (7848 4458). Unisys
Corporation.
ClearPath HMP IX Systems Configuration Guide (7847 5746). Unisys Corporation.
ClearPath HMP IX4400 Server Configuration Guide (7848 4334). Unisys Corporation.
ClearPath HMP IX4800 Server Configuration Guide (7847 5746). Unisys Corporation.
ClearPath HMP IX4800 Server Peripheral Subsystems Configuration Guide
(7847 5704). Unisys Corporation.
ClearPath SMP61000 Series System Configuration Utility User’s Guide (4619 7901).
Unisys Corporation.
7848 4078–004 Bibliography–1

Bibliography
Bibliography–2
ClearPath 2200/3000 Series System Control Facility (SCF) Operations Guide
(7844 8560). Unisys Corporation.
ClearPath 2200/3000 Series System Control Facility (SCF) Operations Guide
(7844 8560). Unisys Corporation.
DEPCON Application Configuration and Operations Guide (7833 3960). Unisys
Corporation.
IPF 1100 Administration Guide (7833 3754). Unisys Corporation.
Microsoft Windows NT Server Version 4.0 Concepts and Planning (69940).
Microsoft Corporation.
Open Systems Terminals LT500 X Terminal Software Installation Guide (4621 5372).
Unisys Corporation.
Open Systems Terminals LT500 X Terminal Software User’s Guide (4621 5380).
Unisys Corporation.
OS 1100 SX 1100 Network File System (NFS) Administrator’s Guide (7833 2392).
Unisys Corporation.
OS 2200 Communications Management System (CMS 1100) Configuration Reference
Manual (7830 9853). Unisys Corporation.
OS 2200 Communications Management System (CMS 1100) Installation and
Configuration Guide (7830 9846). Unisys Corporation.
OS 2200 Enterprise Backup and Restore Capabilities Overview (3495 3059). Unisys
Corporation.
OS 2200 Enterprise Backup and Restore DOS/Windows Installation and Operations
Guide (3495 3091). Unisys Corporation.
OS 2200 Enterprise Backup and Restore Host Installation Guide (3495 3067). Unisys
Corporation.
OS 2200 Enterprise Backup and Restore UNIX Server Installation and Operations
Guide for Windows (3498 1308). Unisys Corporation.
OS 2200 Exec System Software Installation and Configuration Guide (7830 7915).
Unisys Corporation.
OS 2200 Open Application Development Environment (OADE) for Windows User
Guide (7848 3989). Unisys Corporation.
OS 2200 Software Library Administrator (SOLAR) End Use Reference Manual
(7831 0604). Unisys Corporation.
OS 2200 Software Products Installation Guide (7831 0612). Unisys Corporation.
7848 4078–004

Bibliography
OS 2200 System Base Software Planning and Migration Overview (7831 0349). Unisys
Corporation.
OS 2200 TeamQuest Baseline and TeamQuest Online Administration and End Use
Reference Manual (7830 7717). TeamQuest Corporation.
Personal Workstation 2 (PW2) Unisys Repository Workstation (UREP-WS) End Use
Guide (7830 8103). Unisys Corporation.
Single Point Operations Console/Enterprise Server Edition Installation Guide
(7833 4075). Unisys Corporation.
SMP5400 Series System Configuration Utility User’s Guide (7441 4731).
Unisys Corporation.
Unisys Volume Manager Installation Guide (4358 5322). Unisys Corporation.
UNIX System V Release 4.0 Software Installation Guide (7442 0373).
Unisys Corporation.
UNIX System V Release 4.0 System Administrator’s Guide (7436 1742).
Unisys Corporation.
UNIX System V Release 4.0 User’s Guide (3914 9398). Unisys Corporation.
U6000 Series UNE6000-ETH Ethernet Controller Installation Guide (7441 2842).
Unisys Corporation.
2200 Series Site Configuration Management System (SCMS) Administration Guide
Volume 1, Reference Information (7832 8861). Unisys Corporation.
2200 Series Site Configuration Management System (SCMS) Administration Guide
Volume 2, Tutorial (7833 2434). Unisys Corporation.
2200/XPA System Migration Guide (7830 9697). Unisys Corporation.
2200/500 System System Control Facility (SCF) Operations Guide (7833 3622).
Unisys Corporation.
7848 4078–004 Bibliography–3

Index
A
account number, master, 8–7
address, X terminal,
addresses
7–3
configuring in CMS1100, 2–11
default, A–1
private internets, E–1
selecting TCP/IP, 2–8
administration, SysAdmin, browser requirement, 2–3
application group, installing,
applications
10–6
DEPCON, 11–1
OLTP-TM2200, 11–1
Open Programming Environment (OPE), 11–1
UniAccess ODBC,
ASCII compilers
11–1
COBOL (ACOB) package tape location, 11–5
FORTRAN (FTN) package tape location, 11–5
AT_MSAUDIT (See Mass Storage Audit Feature)
B
boot
file name, 7–3
procedure, 2200 component, 8–4
C
cabling, instructions (reference), 1–7
Cartridge Tape Interface Software (CARTIS), package
tape location, 11–7
Cautions, partition requirements,
cautions
6–11
address use, 2–8
changing communication parameters,
changing default password
A–1
SPO server, 6–23
UNIX node, 5–34
Windows NT, 4–30
X terminal, 7–22
internal IP addresses, 1–6
IPF 1100 full screen mode, 8–8
not to format SPO server drive, 6–19
partition requirements, 5–2, 5–26
PathMate configuration requirement, 10–2
SPO server defaults, 6–2
UNIX initial installation only, 5–20
UNIX installation, 6–12
uppercase letters, 5–20, 6–1, 6–12, 7–2
using reset to reboot consoles, 6–42
channel service I/O processor (CSIOP)
configuring in SCMS, F–5
installing microcode,
checklists
9–3
CSE installation, 2–23
fast-load tape products, 11–2
site installation, 2–13
site planning,
CMS 1100
2–1
configuration issues, 2–11
fast-load tape location, 8–2
package tape location, 11–4
Collector (MAP processor)
fast-load tape location, 8–2
package tape location, 11–3
Common Mathematical Library (CML)
fast-load tape location, 8–2
package tape location,
communications
11–3
default parameters, A–1
establishing, XDMCP session, 7–5
planning network addresses, 2–6
verifying, FDDI,
communications test
9–6
FDDI hardware connection, 1–8
verifying interconnect,
COMUS
9–6
fast-load tape location, 8–2
package tape location, 11–3
configuration, submitting information,
configuring
2–2
CMS 1100, 11–1
DEPCON, 11–1
7848 4078–004 Index–1

Index
Ethernet adapter, 4–25
FTP service for SPO, 7–9
monitor concentrator, 3–1
OLTP-TM2200, 11–1
Open Programming Environment (OPE), 11–1
Simple Network Management Protocol (SNMP)
Service, 4–24
Simple TCP/IP Service, 4–24
SPO, 2–6, 11–10
UniAccess ODBC, 11–1
WINS, 4–7, 4–24
X terminal, 7–2, 11–10
Console Message Redisplay (CMR)
fast-load tape location, 8–2
package tape location, 11–4
control, enabling from SPO, 7–1
Cooperative Processing File Transfer Protocol (cpFTP)
installation instructions, D–1
package tape location, 11–5
Cross Reference Generator (CULL)
fast-load tape location, 8–2
package tape location, 11–4
CSE (See customer service engineer (CSE))
CSIOP (See channel service I/O processor (CSIOP))
customer service engineer (CSE)
checklist, 2–23
installation overview, 1–4
D
daemons
starting, 7–1
starting before running RIU, 6–43
Data Management System (DMS 2200)
dynamic access control feature, package tape
location, 11–6
installation, 10–8
package tape location, 11–6
subsystem (DMSUB), fast-load tape location, 10–4
date and time, configuring,
daylight saving time
4–28
configuring, 4–27
entry, 5–5, 5–23, 6–4, 6–15
DDS Migration Processor (DDSMG), package tape
location, 11–6
default
password, 5–5
caution about changing, 6–23
passwords, 2–13
Define File Processor (DFP), package tape
location, 11–6
Index–2
DEPCON
configuring, 11–1
fast-load tape location, 8–2
print queues, 2–5
workstation requirements, 2–4
DEPERR print queue, 2–5
Diagnostic Software Peripheral Equipment Routines
(DSPER), installation, 9–5
directory, default (WINNT), 4–21
disk, emergency repair, 4–28
disk partitions, SPO server, 6–11
Display Processing System (DPS 2200)
fast-load tape location, 10–3
installing, 10–4
package tape location, 11–6
Distributed Data Processing File and Job Transfer
(DDP-FJT), package tape location, 11–5
Distributed Data Processing Program-to-Program
Communications (DDP-PPC)
fast-load tape location, 8–2
package tape location,
DMPLIB
11–5
fast-load tape location, 8–2
package tape location,
DPREP1100
11–4
fast-load tape location, 8–2
package tape location, 11–4
drivers, multiport card, 6–28
DSPER (See Diagnostic Software Peripheral Equipment
Routines (DSPER))
Dump Analysis Processor (DAP)
fast-load tape location, 8–2
package tape location, 11–4
dump disk partition, 5–3
E
EBRS (See Enterprise Backup and Restore (EBRS))
ED
fast-load tape location, 8–2
package tape location,
Element Processor (ELT)
11–3
fast–load tape location, 8–2
package tape location, 11–3
EMAIL print queue, 2–5
emergency repair disk, creating, 4–28
Enterprise Backup and Restore (EBRS)
installation caution, 2–3
installing, 10–10
site license number, 2–3
workstation requirement, 2–3
7848 4078–004

Ethernet adapter
configuring, 4–25
configuring in SCMS, F–5
Exec, configuration parameters, 11–1
Expipe, package tape location, 11–5
Extended Language Message System (ELMS)
fast-load tape location, 8–2
package tape location, 11–4
Extended Transaction Capacity software (XTCEXEC),
package tape location, 11–8
F
fast-load tape
CPIX-OE1, 8–2
CPIX-OE2, 10–3
CPIX-UDS3, 10–4
fast-load tapes
installing from, 8–8
note about reinstalling, 8–1
Fault Location by Interpretive Testing (FLIT), package
tape location, 11–5
FDDI (See fiber distributed data interface (FDDI))
fiber distributed data interface (FDDI)
configuring in SCMS, F–1
driver installation (EISA), 1–8, 5–32
hardware test, 1–8
File Administration System (FAS)
fast-load tape location, 8–2
package tape location, 11–4
File Definition Processor/Application Processor
(FDP/ADP), package tape location, 11–6
file name, boot, 7–3
file transfer protocol (FTP), configuring for SPO, 7–9
File Utility Routines/Program Utility Routines (FURPUR)
fast-load tape location, 8–2
package tape location, 11–3
files, X terminal configuration, 11–11
fonts, accessing, 7–5
FTP (See file transfer protocol (FTP))
G
General Syntax Analyzer (GSA 1100)
fast-load tape location, 8–2
package tape location, 11–6
Graphical Desktop Metaphor (GDM)
installing, 5–28
installing (SPO server), 6–19
installing the developer’s kit, 5–32
Index
7848 4078–004 Index–3
H
hardware
migration issues, 2–4
planning installation, 2–1
ready for use (RFU), 9–1, 9–6
Host LAN Controller-2, configuring in CMS 1100, 2–11
Host LAN Controller-2, installing microcode,
host names
9–1
changing, 11–10
recommended,
hosts file
2–6
creating on the system console, 6–38
loading on system consoles, 11–13
UNIX node, A–2
I
IIS (See Microsoft Internet Information Server (IIS))
Information Management System (IMS 1100), package
tape location,
installation
11–6
CSE performed procedures, 1–4
default passwords, 2–13
overview, 1–4
SPO server, determining if preinstalled, 6–2
Windows NT, determining if preinstalled,
installing
4–1
AMS database, 6–43
DPS, 10–4
EBRS, 10–10
FDDI drivers, 1–8, 5–32
Graphical Desktop Metaphor (GDM), 5–28
developer’s kit, 5–32
SPO server, 6–19
MCB, 10–4
network drivers, 5–28, 6–19
OADE-UNIX, 10–10
Open Programming Environment (OPE), 10–1
Open/OLTP Pathway, 1–8, 4–35, 5–32, D–1
optional OS 2200 products, 11–10
OS 2200, 8–8
PathMate, 10–2
RAS features, Unisys Volume Manager (UVM),
simple network management protocol (SNMP)
5–3
agent, 1–8
SNMP agent, 5–32
SPO/HMP console software, 6–30
SysAdmin, 10–1
TeamQuest products, 10–10
TIP, 10–5

Index
UDS application group 3, 10–3
Unisys UNIX Internet Package (UUIP), 10–11
Unisys Volume Manager (UVM),
UNIX
1–8
SPO server, 6–12
UNIX node software, 5–20
UREP Workstation (UREP-WS), 10–10
Veritas VxFS file system, 1–8, 5–32
Volume Manager, 5–32
Web Transaction Enabler (WebTX), 10–11
Windows NT, Intel node, 4–15
Windows NT agent, 7–10
Integrated Recovery Utility (IRU)
fast-load tape location, 8–2
package tape location, 11–6
Recovery Manager (IRU-RM), package tape
location, 11–6
Intel node
copying URM files, 7–17
enabling control from SPO, 7–1
installing, Windows NT,
Interactive CULL (IACULL)
4–15
fast-load tape location, 8–2
package tape location, 11–4
Interactive Processing Facility (IPF 1100)
fast-load tape location, 8–2
full screen mode caution, 8–8
package tape location, 11–5
Internet Explorer, 2–3
Internet support,
IP addresses
2–23
default, A–1
X terminal, 7–3
K
key tapes, registering, 8–10, 11–9, 11–10
L
license
EBRS, 2–3
Windows NT, 2–14
Linking System (LINK)
fast-load tape location, 8–2
Index–4
package tape location,
LIST processor
11–4
fast-load tape location, 8–2
package tape location, 11–3
Log Analyzer (LA), package tape location,
log files
11–4
Transaction log, 5–3
X Open Application Program Interface log
(XAPLOG), 5–3
logging on
SPO server, 6–23
UNIX node, 5–34
LT501 X terminal (See X terminal)
M
Mass Storage Analysis Relocation Processor (MSAR),
package tape location, 11–4
Mass Storage Audit Feature (AT_MSAUDIT), package
tape location, 11–7
Mass Storage Manager (MSManager), package tape
location, 11–4
master account number, 8–7
Message Control Bank (MCB)
fast-load tape location, 10–3
installing, 10–4
package tape location, 11–8
messages, read-and-reply,
Meta-Assembler (MASM)
8–4
fast-load tape location, 8–2
package tape location,
microcode
11–3
CSIOP installation,
installing HLC2, 9–1
9–3
Microsoft Internet Information Server (IIS)
selecting for installation, 4–23
setting properties, 4–27
migration, considerations,
monitor concentrator
2–4
configuring, 3–1
operation, 3–2
Monitor Services Control Program (MSCP)
fast-load tape location, 8–2
package tape location,
multiport I/O card
11–4
connections, 6–28
jumpering, 6–11
7848 4078–004

N
Netscape Navigator,
network
2–3
address guidelines, E–1
driver installation,
network addresses
6–19
planning, 2–6
selecting, 2–8
network driver, installation, 5–28
Network File System (NFS), using,
networking
10–1
guidelines, E–1
sites without a network, 2–6
NFS (See Network File System (NFS))
O
ODB (See operations database (ODB))
ODBC (See UniAccess Open Database Connectivity
(ODBC))
Online System Activity Monitor (OSAM), package tape
location, 11–4
Open Application Development Environment for UNIX
(OADE-UNIX)
fast-load tape location, 8–2
installing, 10–10
package tape location, 11–7
Open Programming Environment (OPE)
configuring, 11–1
installing, 10–1
IP address and host name, A–1
Open Systems Interconnection Directory Services (OSI)
File Transfer, Access, and Management (OSI-FTAM),
package tape location, 11–7
Message Handling System (OSI-MHS), package tape
location, 11–7
Open/OLTP (See TransIT Open/OLTP)
Open/OLTP Pathway
installation, 1–8
installing, 4–35, 5–32, D–1
operations database (ODB)
loading, 1–7
reloading, F–1
optional packages, Intel node, 10–11
OS 2200
applicable software levels, 2–4
installing, 8–8
optional product installation, 11–10
overview, installation, 1–4
Index
7848 4078–004 Index–5
P
partition requirements, UNIX node,
partitions
5–2
SPO server, 6–11
UNIX node (disk 0),
passwords
5–1
caution about changing, 4–30, 5–34, 6–23, 7–22
default, 6–23
default installation, 2–13
patches, installing UNIX,
PathMate
6–24
configuration requirement, 10–2
description of, 11–1
installing, 10–2
when to use, 1–10
PERCON, package tape location, 11–6
Performance Analysis Routines (PAR), package tape
location, 11–5
performance level, establishing, 8–10, B–1
personal computers (PCs), site requirements,
ping test (See communications tests)
planning
2–2
network addresses, 2–6
site preparation, 2–1
site-supplied workstations,
PLUS
2–2
fast-load tape location, 8–3
package tape location, 11–5
Portable Operating System Interface (POSIX)
fast-load tape location, 8–3
package tape location,
Postmortem Dump (PMD)
11–5
fast-load tape location, 8–3
package tape location, 11–4
print queues, DEPCON, 2–5
Procedure Definition Processor (PDP)
fast-load tape location, 8–3
package tape location, 11–3
Processor Common Input/Output System (PCIOS)
fast-load tape location, 8–3
package tape location,
product key
11–5
DMS 2200, 11–6
Relational Data Management System (RDMS
2200), 8–3, 11–6
Unisys Repository Manager (UREP), 11–7
products, packaging, 11–2
Program-Callable FURPUR (PCFP)
fast-load tape location, 8–3
package tape location, 11–3

Index
Programmers Advanced Debugging System (PADS)
fast-load tape location, 8–3
package tape location, 11–4
Q
Query Language Processor (QLP 2200), package tape
location, 11–6
R
read-and-reply message format, 8–4
ready for use (RFU), hardware, 9–1, 9–6
redundant array of independent disks (RAID)
configuring for UNIX, 5–13
configuring for Windows NT,
registration number
4–2
EBRS, 2–3
Windows NT, 2–14
Relational Data Management System (RDMS 2200)
fast-load tape location, 10–4
installation, 10–8
package tape location, 11–6
product key (RDMSKEY)
fast-load tape location, 8–3
package tape location, 11–6
Reliability, Availability, and Serviceability (RAS), feature
installation, 5–3
Remote Install Utility (RIU), remote AMS database
installation, 6–43
Remote System Support (RSS)
fast-load tape location, 8–3
package tape location, 11–3
Request for Comments (RFC) 1918,
requirements
E–1
DEPCON workstation, 2–4
hardware and software, 2–2
site-supplied workstations, 2–2
Web browser, 2–3
RFC (See Request for Comments (RFC))
RoboHost 22, package tape location, 11–5
Roll-out/Roll-back Runstream (ROLRUNS)
fast-load tape location, 8–3
package tape location, 11–4
routers, identifying, 6–41
Index–6
S
SCMS (See Site Configuration Management System
(SCMS))
scripts
tuning, SPO server, 6–3, 6–34
URM installation,
security
7–17
options installation, 11–8
security officer user-id, 8–7
serial interface, driver installation,
Service Library (SLIB)
6–28
fast-load tape location, 8–3
package tape location, 11–4
Shared File System (SFS 2200)
fast-load tape location, 10–4
installation, 10–8
package tape location, 11–7
Simple Network Management Protocol (SNMP) agent,
installing, 5–32
simple network management protocol (SNMP) agent,
installing, 1–8
Simple Network Management Protocol (SNMP) Service,
configuring, 4–24
Simple TCP/IP Service, 4–24
SINCH (See Unisys Interconnect Channel Handler)
Single Point Interface Utility,
Single Point Operations (SPO)
AMS database
6–39, 6–45
activating, 7–24
installing, 6–43
block diagram, 6–28
changing the predefined configurations, 11–10
console software installation, 6–30
daemons, 7–1
default configuration, 7–22
enabling monitoring and control, 7–1
Enterprise Server Edition (SPO/ESE) use, 2–5
font access, 7–5
hardware, jumpering, 6–11
help, 7–23
hosts file copying to system consoles, 6–38
installing UNIX, 6–12
installing Windows NT agent, 7–10
main menu, 7–23
normal operations, 7–22
SPO/ESE connections, 6–28
URM files, creating, 7–6, 7–14
7848 4078–004

single point status, 7–23
Site Administration Utilities (SA Utilities), package tape
location, 11–5
Site Configuration Management System (SCMS)
configuring the FDDI connection, F–1
naming conventions, F–1
submitting information, 2–2
Site Management Complex (SIMAN)
fast-load tape location, 8–3
package tape location, 11–5
site planning, checklist, 2–1
Small Computer System Interface (SCSI) software
(SCSITIS), package tape location, 11–8
SMART, fast-load tape location, 8–3
SMART software, package tape location, 11–5
SNMP service (See Simple Network Management
Protocol (SNMP) service)
Software Instrumentation Package Internal Performance
Monitor (SPIPM), package tape
location, 11–8
Software Library Administrator (SOLAR)
fast-load tape location, 8–3
package tape location, 11–3
Software Library Administrator Extended (SOLAR/E),
package tape location, 11–6
Software Product Application Initialization and Recovery
(SPAIR), package tape location,
Sort/Merge (SORT) utility
11–8
fast-load tape location, 8–3
package tape location, 11–5
SPO (See Single Point Operations (SPO))
SPO server
caution about defaults, 6–2
enabling communications,
installing URM files
7–5
for UNIX, 7–14
for Windows NT, 7–6
start-up session, system console, 6–45
status classification, Unix2200Mon, 7–23, C–1
SUMMIT, requirement to run, 1–7
Symbolic Stream Generator (SSG)
fast-load tape location, 8–3
package tape location, 11–4
SYS FIN message,
SysAdmin
8–8
product installation, 10–1
WEB browser requirement, 2–3
system configuration utility (SCU),
system consoles
4–2
AMS database installation, 6–43
hosts file installation, 6–38
loading the hosts file, 11–13
monitor concentrator use, 3–1
Index
procedures, changing start-up session, 6–45
Utility Session menu, 6–38
System Controlled Performance (SCP), enabling,
B–1
8–10,
system generation, print queue requirement, 2–5
system name, SPO server, 6–5, 6–16
System Network Architecture (SNA)
Program-to-Program Communications (SNAPPC),
package tape location, 11–7
Remote Job Entry (SNARJE), package tape
location, 11–7
System Service Routines Library (SYSLIB)
fast-load tape location, 8–3
package tape location, 11–4
7848 4078–004 Index–7
T
Tape Automatic Volume Recognition (TAVR), package
tape location, 11–8
tapes
key tape, registering, 11–10
product package, 11–2
TCP/IP Service, configuring,
Teamquest
4–24
Baseline, package tape location, 11–7
Online, package tape location, 11–7
PMLog, package tape location, 11–7
product installation, 10–10
Technical Information Bulleting (TIB)
Internet access to support, 2–23
SCMS information, 2–2
time, configuring,
time zone
4–28
configuring, 4–27
entry,
TIP
5–23, 6–15
installing TIPUTIL, 10–4
setting up, 10–5
transaction log (TLOG) partition, 5–3
Transaction Performance Auditing System (TPAS),
package tape location, 11–6
Transaction Processing Utilities (TIPUTIL)
fast-load tape location, 10–3
package tape location,
TransIT Open/OLTP
11–8
configuring, 11–1
Heritage Application Access Administration
(OLTP–HAA), fast-load tape location, 8–3
Transaction Manager (OLTP–TM2200), fast-load tape
location, 8–3
Transaction Monitor (OLTP–MON2200), fast-load
tape location, 8–3

Index
Trivial File Transfer Protocol (TFTP), boot method,
tuning scripts
7–3
SPO server,
UNIX node
6–3, 6–34
factory-installed UNIX, 5–4
site-installed UNIX, 5–35
U
UDS application group 3, installing, 10–3
Unattended Operations Support Software (UOSS),
package tape location, 11–7
UniAccess ODBC, configuring, 11–1
UniAccess Open Database Connectivity (ODBC),
fast-load tape location, 8–3
Unisys Interconnect Channel Handler (SINCH), package
tape location, 11–8
Unisys Repository (UREP), workstation (UREP-WS),
installing, 10–10
Unisys Repository Manager (UREP)
installation, 10–8
product key, absolute mode location,
subsystem (UREPSUB), fast-load tape
11–7
location, 10–4
Unisys UNIX Internet Package (UUIP),
installing, 10–11
Unisys Volume Manager (UVM)
installation, 1–8
RAS feature installation, 5–3
unisys-config file, 11–11
Unit Duplexing, package tape location,
Universal Compiling System (UCS)
11–8
ADA (UADA), package tape location, 11–7
ADA Runtime System (UADARTS), package tape
location, 11–7
C (UC), absolute mode location, 8–3, 11–5
COBOL Compiler (UCOB), package tape
location, 11–5
FORTRAN (UFTN), package tape location, 11–5
Language Support System (LSS), absolute mode
location, 8–2, 11–5
PLUS
absolute mode location, 8–3
package tape location, 11–5
Run Time System (UCSRTS), absolute mode
location, 8–3, 11–4
Runtime System (URTS), absolute mode
location, 8–3, 11–4
Universal Data System Control (UDS Control)
fast-load tape location, 10–4
Index–8
installation, 10–8
package tape location,
UNIX node
11–6
enabling communication with SPO, 7–14
installing UNIX, 5–20
logging on,
tuning script
5–34
factory-installed UNIX, 5–4
site-installed UNIX,
UNIX operating system
5–35
enabling monitoring by SPO,
installing
7–14
SPO server, 6–12
UNIX node software, 5–20
installing patches (See X terminal)
Intel node, optional packages, 10–11
partitions (SPO server), 6–11
SPO server, determining if preinstalled,
UNIX Resource Monitor (URM)
6–2
copying, 7–17
creating, 7–14
installing files, 7–6
Unix2200Mon status classification, 7–23, C–1
Utilities Session menu, 6–38
UUIP (See Unisys UNIX Internet Package (UUIP))
UVM (See Unisys Volume Manager (UVM))
V
verifying, communications, 9–1
Veritas VxFS File System, installing, 1–8, 5–32
Virtual Storage Manager (XPCEXEC), package tape
location, 11–8
Volume Manager, installing, 5–32
W
Web, browser requirement, 2–3
Web Transaction Enabler (WebTX), installing, 10–11
WebTX (See Web Transaction Enabler (WebTX))
WINDOC print queue, 2–5
Windows Internet Name Service (WINS),
configuring,
Windows NT
4–7, 4–24
changing the password, 4–30
registration number, 2–14
Windows NT node, enabling communication with
SPO, 7–6
7848 4078–004

Windows NT operating system
determining if preinstalled, 4–1
enabling monitoring by SPO, 7–6
installing, Intel node, 4–15
product installation, 4–35
WINNT directory, 4–21
WINS (See Windows Internet Name Service (WINS))
workstations, site requirements, 2–2
X
X Display Manager Control Protocol (XDMCP),
session, 7–5
X Open Application Program Interface log (XAPLOG),
log file, 5–3
X terminal
configuration file, 11–11
configuring, 7–2, 11–11
installing software, 6–25
IP address, 7–3
XPCEXEC. See Virtual Storage Manager
XTCEXEC. See Extended Transaction Capacity
installing software, 6–25
IP address, 7–3
XPCEXEC (See Virtual Storage Manager)
XTCEXEC (See Extended Transaction Capacity)
Index
7848 4078–004 Index–9

Help Us To Help You
Unisys Corporation is interested in your comments and suggestions regarding this document. We
will use them to improve the quality of your product information. You can return this form in the
mail or by fax: (612) 635-7523 or 635-7990. Please check type of suggestion:
Addition Deletion Revision Error
Publication title
Document number
Comments:
Name
Title
Address
City
Company
Date
State ZIP code
Telephone number
( )

Tape
Fold here
Cut along dotted line
Do Not Staple
Please Fold and Fasten
BUSINESS REPLY MAIL
FIRST CLASS MAIL PERMIT NO. 1145 ST. PAUL, MN 55164
POSTAGE WILL BE PAID BY ADDRESSEE
PI Response Card
Unisys Corporation
PO Box 64942
St. Paul, MN 55164–9544
Tape