XPC-L System Installation, Configuration, and Migration Guide

ClearPath Enterprise Servers 

Extended Processing Complex- Locking (XPC-L) 

System 

Installation, Configuration, and Migration Guide 

XPC-L Release 2.2 and Higher 

November 2009 6885 3522–003 

unisys 

imagine it. done.

NO WARRANTIES OF ANY NATURE ARE EXTENDED BY THIS DOCUMENT. Any product or related information 

described herein is 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 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, 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. 

Notice to U.S. Government End Users: This is commercial computer software or hardware documentation developed at 

private expense. Use, reproduction, or disclosure by the Government is subject to the terms of Unisys standard 

commercial license for the products, and where applicable, the restricted/limited rights provisions of the contract data 

rights clauses. 

FCC Statement 

The statement below is included in this document to comply with a Federal Communications Commission (FCC) 

regulation. The FCC is an agency of the United States government; thus, the statement below applies to computing 

equipment installed in the United States of America. Unisys is taking appropriate steps to be in compliance with FCC 

regulations and similar regulations of other countries. 

WARNING: This equipment has been tested and found to comply with the limits for a Class A device, pursuant to Part 

15 of FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the 

equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency 

energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio 

communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case 

users will be required to correct the interference at their own expense. 

Canadian Regulatory Statement 

This class A apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. 

Cet appareil de la classe A respecte toutes les exigences du Règlement sur le matériel brouilleur du Canada. 

Unisys and ClearPath are registered trademarks of Unisys Corporation in the United States and other countries. 

All other brands and products referenced in this document are acknowledged to be the trademarks or registered 

trademarks of their respective holders.

Contents 

Section 1. Introduction 

Section 2. Installation 

1.1. Documentation Updates .......................................................... 1–1 

1.2. Overview of an XPC-L System................................................. 1–2 

1.2.1. Hardware Components ................................................... 1–6 

1.2.2. Connections between Components ............................... 1–7 

1.2.3. Software Components .................................................... 1–9 

1.3. Notation Conventions ............................................................ 1–10 

2.1. Hardware Installation ............................................................... 2–1 

2.1.1. Installing XPC-L Control Workstation Hardware ............. 2–4 

2.1.2. Installing XPC-L Server Hardware ................................... 2–4 

2.1.3. Installing Host Hardware ................................................. 2–5 

2.1.4. Installing VI Cables .......................................................... 2–6 

2.1.5. Installing Ethernet Cables and Hubs ............................. 2–10 

2.2. Software Installation .............................................................. 2–13 

2.2.1. Installing Platform Software .......................................... 2–13 

2.2.1.1. Installing Platform Software on the XPC-L 

Control Workstations ....................................... 2–13 

2.2.1.2. Creating Partitions on the XPC-L Servers ............. 2–16 

2.2.1.3. Installing Platform Software on the XPC-L 

Servers ............................................................. 2–17 

2.2.1.4. Installing Platform Software on the 

OS 2200 Hosts ................................................. 2–24 

2.2.2. Preparing to Install XPC-L Software .............................. 2–25 

2.2.2.1. Modifying the Hosts File ...................................... 2–26 

2.2.2.2. Creating a Configuration File ................................ 2–28 

2.2.2.3. Creating User Names and Updating Local 

Security Policies ............................................... 2–28 

2.2.2.4. Creating Shared Folders ....................................... 2–31 

2.2.3. Installing XPC-L Control Workstation Software ............ 2–32 

2.2.3.1. Installing the XPC-L Control Software .................. 2–32 

2.2.3.2. Identifying the Location of the 

Configuration File ............................................. 2–33 

2.2.4. Installing XPC-L Server Software .................................. 2–35 

2.2.5. Installing XPC-L Host Software ..................................... 2–38 

2.2.5.1. Installing Exec Features ........................................ 2–38 

2.2.5.2. Operations Sentinel Message Text ...................... 2–38 

6885 3522–003 iii

Contents 

Section 3. Configuration 

Section 4. Migration 

3.1. Configuring XPC-L Control ........................................................ 3–1 

3.2. Configuring XPC-L Servers ....................................................... 3–2 

3.3. Configuring Hosts ..................................................................... 3–2 

3.3.1. Using SCMS for Dorado Series Host 

Configuration ............................................................... 3–3 

3.3.2. Site Configuration Management System II ...................... 3–4 

3.4. Configuration File ...................................................................... 3–5 

3.4.1. Configuration File Syntax ................................................. 3–6 

3.4.2. Sample Configuration ..................................................... 3–10 

3.4.3. Generating a Configuration File ..................................... 3–27 

4.1. Conceptual Differences ............................................................ 4–1 

4.2. Crossbooting ............................................................................. 4–4 

4.2.1. Discontinuing Use of XPC File Caching ........................... 4–5 

4.2.1.1. Overview ................................................................. 4–5 

4.2.1.2. Determining the Caching Information of a 

File....................................................................... 4–6 

4.2.1.3. Removing Data from the XPC ................................. 4–7 

4.2.1.4. Removing the XPC Identifier from the MFD ........... 4–8 

4.2.2. Adding XPC-L to the OS 2200 Environment .................... 4–9 

4.2.2.1. Migrating Without Duplexing ................................ 4–10 

4.2.2.2. Migrating to XPC-L with Shared Unit 

Duplexing .......................................................... 4–10 

4.3. Clearing the XPC ..................................................................... 4–12 

4.4. New Console Messages ........................................................ 4–13 

4.5. Changed Console Messages .................................................. 4–15 

4.6. Keyin Changes ........................................................................ 4–16 

4.6.1. Unsupported Keyins ....................................................... 4–16 

4.6.2. Changed Keyins ............................................................. 4–17 

4.6.3. New Keyins .................................................................... 4–21 

4.7. Initialization ............................................................................. 4–22 

4.8. EXERRS .................................................................................. 4–22 

Section 5. Changing Hardware and Software Components 

5.1. Changing Hardware .................................................................. 5–1 

5.1.1. Changing XPC-L Control Workstation Hardware ............. 5–1 

5.1.2. Changing XPC-L Server Hardware ................................... 5–2 

5.1.2.1. Replacing an Existing VI Card .................................. 5–3 

5.1.2.2. Adding a New VI Card ............................................. 5–6 

5.1.3. Changing XPC-L Host Hardware ...................................... 5–6 

5.1.4. Changing the XPC-L Control Workstation LAN 

Ethernet Switch ........................................................... 5–7 

5.2. Changing Software ................................................................... 5–7 

5.2.1. Changing with a Complete Shutdown of the 

System ......................................................................... 5–7 

5.2.2. Changing XPC-L Platform Software ................................. 5–8 

iv 6885 3522–003

Contents 

5.2.3. Changing Platform Software on the XPC-L 

Control Workstations [Dell OptiPlex 960] ................... 5–9 

5.2.3.1. Reinstalling Windows XP SP3 and Setting 

Up the XPC-L Control Workstation [Dell 

OptiPlex 960] ...................................................... 5–9 

5.2.3.2. Reinstalling Device Drivers ................................... 5–16 

5.2.3.3. Removing Unnecessary Windows 

Components, Executables, and Services ......... 5–18 

5.2.3.4. Enabling Multi CPU Core Mode ........................... 5–20 


Control Workstations [Dell OptiPlex 745 and 

Dell OptiPlex 755] ..................................................... 5–20 

5.2.4.1. Reinstalling Windows XP and Setting Up 

the XPC-L Control Workstation Dell 

[OptiPlex 745 and Dell OptiPlex 755] ............... 5–21 




5.2.4.4. Enabling Multi CPU Core Mode ........................... 5–31 


Control Workstations [Dell GX270 and GX280] ........ 5–32 

5.2.5.1. Reinstalling Windows XP and Setting Up 

the XPC-L Control Workstation [Dell 

GX270 and GX280] ........................................... 5–32 




5.2.5.4. Verifying and Enabling CPU Hyper- 

Threading .......................................................... 5–42 


Servers ...................................................................... 5–43 

5.2.7. Changing XPC-L Control Workstation Software ............ 5–44 

5.2.8. Changing XPC-L Server Software ................................. 5–45 

5.2.9. Changing XPC-L Host Software .................................... 5–47 

5.2.9.1. Loading a New Version of XIIP Microcode ........... 5–48 

Section 6. Deinstallation 

6.1. Overview .................................................................................. 6–1 

6.2. Removing XPCEXEC Software ................................................ 6–2 

6.3. Removing XPC-L Server Software ........................................... 6–3 

6.4. Removing XPC-L Control Workstation Software ..................... 6–3 

Section 7. Maintenance for XPC-L Systems 

7.1. Maintaining XPC-L Servers ...................................................... 7–1 

7.2. Maintaining XPC-L Workstations ............................................. 7–2 

7.3. Maintaining XPC-L Service Processors .................................... 7–3 

6885 3522–003 v

Contents 

Appendix A. Setting Windows User Names and Local Security 

Policies 

A.1. Creating a New User Name ..................................................... A–1 

A.2. Setting User Rights Assignments ........................................... A–2 

A.3. Setting Security Options .......................................................... A–2 

Appendix B. Example XPC-L Server PCI Locations Charts and 

Worksheets 

Appendix C. Reinstallation of Windows 2003 on XPC-L Servers 

Glossary ............................................................................................. 1 

Index ............................................................................................. 1 

vi 6885 3522–003

Figures 

1–1. System Level Database Locking Provided by the XPC-L ................................... 1–3 

1–2. Configuration for Partitioned Applications ......................................................... 1–5 

1–3. Configuration for XTC ......................................................................................... 1–6 

1–4. XPC-L System Interconnections ........................................................................ 1–8 

2–1. Major Hardware Components ............................................................................ 2–3 

2–2. Fiber-Optic Cable Connectors .......................................................................... 2–10 

2–3. XPC-L Control Window: Select Server Pane .................................................... 2–34 

3–1. Sample Configuration ....................................................................................... 3–11 

3–2. Sample Configuration—Degraded ................................................................... 3–24 

6885 3522–003 vii

Figures 

viii 6885 3522–003

Tables 

2–1. Intel Cabling Connections .................................................................................. 2–5 

2–2. VI Cabling for Dorado 300 Series Servers .......................................................... 2–6 

2–3. VI Cabling for Dorado 200 Series Servers .......................................................... 2–8 

2–4. Ethernet Cabling for Dorado 300 Series Servers ............................................. 2–11 

2–5. Ethernet Cabling for Dorado 200 Series Servers ............................................. 2–12 

3–1. Determining PciBridgeNumber ........................................................................ 3–30 

B–1. Dorado 300 Series Servers: Primary or Secondary XPC-L Server (Back 

View, Left 2/3) ............................................................................................... B–2 

B–2. Dorado 300 Series Servers: Primary XPC-L Server (Back View, Right 

1/3—Expanded) ............................................................................................. B–3 

B–3. Dorado 300 Series Servers: Secondary XPC-L Server (Back View, Right 

1/3—Expanded) ............................................................................................. B–4 

B–4. Dorado 200 Series Servers: Primary XPC-L Server (Front View) ....................... B–5 

B–5. Dorado 200 Series Servers: Primary XPC-L Server (Back View) ........................ B–6 

B–6. Dorado 200 Series Servers: Secondary XPC-L Server (Front View) .................. B–7 

B–7. Dorado 200 Series Servers: Secondary XPC-L Server (Back View) ................... B–8 

B–8. Worksheet: XPC-L System Information ............................................................. B–9 

B–9. Worksheet: XPC-L System User Name/Password Information ......................... B–9 

B–10. Worksheet: XPC-L License Code ....................................................................... B–9 

6885 3522–003 ix

Tables 

x 6885 3522–003

Examples 

2–1. Example Hosts File .......................................................................................... 2–27 

5–1. Online Loading of XIIP Microcode—Console Output ...................................... 5–53 

5–2. Offline Loading of XIIP Microcode—Console Output ...................................... 5–56 

5–2 Offline Loading of XIIP Microcode—Console Output (continued) ................... 5–57 

5–3. Running XSTRESS—Console Output............................................................... 5–59 




6885 3522–003 xi

Examples 

xii 6885 3522–003

Section 1 

Introduction 

Extended Processing Complex-Locking (XPC-L) system provides an external lock engine 

that is used to coordinate access to files and databases that are simultaneously 

accessed from multiple hosts. This document describes the procedures to install and 

configure XPC-L and explains changes to be made for migrating to the XPC-L from its 

predecessor. 

This section provides an overview of the XPC-L system and describes the notation 

conventions used in this manual. 

1.1. Documentation Updates 

This document contains all the information that was available at the time of publication. 

Technical changes identified after release of this document are included in problem list 

entry (PLE) 18693046. To obtain a copy of the PLE, contact your Unisys representative or 

access the current PLE from the Unisys Product Support Web site: 

http://www.support.unisys.com/all/ple/18693046 

Note: If you are not logged into the Product Support site, you will be asked to do so. 

PLE 18709112 identifies changes made to various levels of OS 2200 after they were 

released to provide support for the XPC-L. 

6885 3522–003 1–1

Introduction 

1.2. Overview of an XPC-L System 

The XPC-L system is a central electronics complex (CEC) component that is optionally 

added to a Dorado Series server. Such systems are referred to as 2200 XP systems. 

An XPC-L system uses a Dorado Series server Intel based platform to provide the 

following categories of functions: 

• External locking manager 

• Operating system interhost messaging 

• Shared Unit Duplexing synchronization 

OS 2200, which runs on Dorado Series servers, contains optional feature code to use the 

functions of the XPC-L. The features, XPC-L and Multi-Host File Sharing (MHFS), 

Partitioned Applications (PA) and Extended Transaction Capacity (XTC) are described later 

in this section. 

It is not necessary to make program or transaction changes while migrating from an 

Extended Processing Complex (XPC) to an XPC-L. Refer to Section 4, “Migration“ for 

details on the migration process. 


The external lock manager is primarily used for database locking. Database locking 

(Figure 1–1) supports a synchronized lock manager for use in multiple host systems. 

This is the function that the OS 2200 uses to enable a single application to execute 

simultaneously on multiple Dorado Series servers while accessing a common 

database. Separate locking interfaces and support are provided for use by Exec/TIP 

FCSS and the Universal Data System (UDS). It provides capabilities to lock and 

unlock various database structures (such as pages). This capability is referred to in 

some documentation as RLP locking. 

The external lock manager can also be used by the MHFS feature to manage locks 

associated with the coordination and control of shared files. 

1–2 6885 3522–003

Figure 1–1. System Level Database Locking Provided by the XPC-L 


Introduction 

Operating system interhost messaging supports communications among hosts in a 

multiple host environment. The mechanism provides a low volume interface using 

small packets of message data for the transfer of information in processes such as 

host and file status communication. 


XPC-L 

Locks for Application Group n 

Host Host Host 

Application 

Group n 

Application 

Group n 

Data for 

Application 

Group n 

Shared Unit Duplexing synchronization provides a record of the I/Os in progress to 

duplexed shared devices. All hosts in the MHFS environment have access to the 

synchronization tables so that any surviving host can synchronize the data in 

duplexed shared files if another host in the MHFS environment should stop. 

XPC-L and Multi-Host File Sharing (MHFS) 

Application 

Group n 

The XPC-L enhances the MHFS feature and two software feature groupings that build on 

the MHFS feature. 

The MHFS feature is a separately orderable and separately installed software feature of 

OS 2200. MHFS provides the OS 2200 coordination and control required to allow 

multiple hosts to simultaneously access data residing in a set of shared mass storage 

devices (referred to as the shared device group). There is only one shared device group 

in an MHFS environment. 

6885 3522–003 1–3

Introduction 

The hosts in the MHFS environment communicate with each other to coordinate actions 

taken related to the shared devices, such as 

• Setting and clearing locks that protect shared files from simultaneous updates 

• Changes in the configuration of devices in the shared device group 

• Recovery information 

• Operational information, including messages or unsolicited keyins directed to other 

hosts 

• Host status 

The MHFS feature supports the following methods of communication among hosts in 

the MHFS environment: 

• The preferred MHFS interhost communication method is with the XPC-L. In this 

configuration, the XPC-L system manages the locks for all hosts and passes MHFS 

coordination and control information among hosts. 

• The alternate MHFS interhost communication method is with a network 

configuration. In a network MHFS configuration, an Ethernet LAN links all the hosts 

in the MHFS environment together. In a network MHFS configuration, lock 

information, as well as MHFS coordination and control information, is passed 

through the network to all hosts in the MHFS environment. 

• Another alternative MHFS interhost communication method is with the XPC. In this 

configuration, the XPC manages the locks for all hosts and passes MHFS 

coordination and control information among hosts. 

Unisys has two software feature groupings that build on the MHFS feature to extend the 

capabilities of the operating system: Partitioned Applications (PA) and Extended 

Transaction Capacity (XTC). 

1–4 6885 3522–003

XPC-L and Partitioned Applications (PA) 

Introduction 

The PA feature grouping allows two hosts in an MHFS environment to provide backup 

for each other. Each host runs its own set of Transaction Processing (TIP) or Universal 

Data System (UDS) application groups. The files in support of those application groups 

reside in the shared device group, but these cannot be accessed by more than one host 

at a time. 

The two hosts maintain communications with each other (called “heartbeat“) through 

the MHFS interhost communication mechanism. If a host fails, the surviving host 

automatically recovers and begins processing the application groups for the failed host. 

Using the MHFS feature to make the production files of each host accessible by both 

hosts is key to this feature. 

Figure 1–2 shows the configuration in a Partitioned Applications environment. For more 

information on the Partitioned Applications feature grouping, refer to the Partitioned 

Applications Conceptual Overview and the Partitioned Applications Planning, Installation, 

and Operations Guide. 


Host A Host B 

Application Application 

Local 

Databases 

Local 

Disks 

Shared 

Databases 

Shared 

Disks 

Figure 1–2. Configuration for Partitioned Applications 

XPC-L and Extended Transaction Capacity (XTC) 

Local 

Databases 

Local 

Disks 

The XTC feature grouping enables several hosts in the MHFS environment to 

simultaneously execute transactions against the same TIP or UDS application group. The 

data files for the application group reside on the shared device group; this means that all 

hosts in the MHFS environment have access to them. The XPC-L system provides the 

locking mechanism that is required to allow multiple hosts to update shared databases. 

Figure 1–3 shows the configuration in an XTC environment with two hosts. For more 

information on the XTC feature grouping, refer to the Extended Transaction Capacity 

Planning, Migration, and Operations Guide. 

6885 3522–003 1–5

Introduction 

Figure 1–3. Configuration for XTC 

You can have either the Partitioned Applications feature grouping or the XTC feature 

grouping installed on your system, but not both. 

1.2.1. Hardware Components 

Multiple hosts connect to a redundant XPC-L system. The redundant XPC-L system 

consists of 

• A primary XPC-L Server platform 

• A secondary XPC-L Server platform 

• An active XPC-L Control Workstation 


Record Lock 

Logic 

Host A Host B 

Local 

Databases 

Local 

Disks 

• One or more backup XPC-L Control Workstations 

• Connections between the various entities 

Application 

Shared 

Databases 

Shared 

Disks 

Local 

Databases 

Local 

Disks 

The primary and secondary platforms provide redundancy; they are used in a 

master/slave mode of operation. The role of master is initially assigned to the primary 

platform, but can change under software control while the system is in operation. The 

master XPC-L server is the server that actively provides the database locking and 

interhost messaging functions. The slave XPC-L server provides backup if the master 

XPC-L server encounters an error condition. 

1–6 6885 3522–003

• Host platforms can be Dorado Series servers (or later). 

Introduction 

• Each XPC-L platform is an Intel cellular multiprocessing (CMP) platform. Redundancy 

is provided by using a second server and connecting it to the first. While the XPC-L 

servers are Dorado Series server platforms, their service processors do not perform 

any XPC-L functions. The service processor is used only for general CMP 

configuration and control functions. Refer to the ClearPath Plus Server Dorado 300 

Series Preinstallation and Planning Guide (Dorado 300 Series servers) or the 

ClearPath Plus Servers for OS 2200 Preinstallation Planning Guide (Dorado 200 

Series servers) for an overview of the Dorado Series server and the functions that 

the service processor provides. 

• The XPC-L Control Workstation platform is an Intel based computer. XPC-L Control is 

the primary operator interface to the XPC-L. Redundancy is provided by using more 

than one such workstation and networking both to the XPC-L servers with redundant 

LANs. 

1.2.2. Connections between Components 

Each host is connected to the primary and secondary XPC-L servers by a Virtual Interface 

(VI) channel (Figure 1–4). A VI channel consists of a pair of PCI cards connected by a fiber 

optic cable. One PCI card resides in an XPC-L server and the other in a host IOP. The 

host IOP with a VI channel PCI card installed is called an XIOP. 

The primary and secondary XPC-L servers connect to each other using VI channels 

(Figure 1–4). The active and backup XPC-L Control Workstations connect to each other 

through a private Ethernet network. The primary and secondary XPC-L servers also 

connect to this private Ethernet network for communication with the XPC-L Control 

Workstations. 

6885 3522–003 1–7

Introduction 

Request/status 

packet routing paths 

for 'reversed' 

configuration 

(slave on left, 

master on right) 

VI 

= VI Interface Channel 

Host A 

(2200) 

PCIOP PCIOP PCIOP PCIOP 

VI VI VI VI 

XPC 

Master 

CMP 

Primary XPC-L 

Platform 

- 

(Intel Node) 

Primary/Secondary 

Crossover Paths 


Synchronization Paths 

Host D 

Secondary XPC-L 

Platform 

(Intel Node) 

Figure 1–4. XPC-L System Interconnections 

Request/status 

packet routing paths 

for configuration 

shown — routed by 

software 

Each host has paths to both the primary and secondary XPC-L and all paths can be used 

to send commands to XPC-L system. The server functioning as the master executes all 

XPC-L commands. Therefore, commands received by the slave must be sent to the 

master for execution. The crossover paths move command requests from the slave to 

the master and, at the completion of command execution, return status to the requester 

through the path connected to the slave. 

While the master server processes the commands, the slave XPC-L server monitors the 

operations of the master server. The slave server monitors the synchronization paths for 

audit requests, performs the data updates as directed by the master, and sends 

completion status when the data updates have been completed. 

In addition to providing the paths to be used to maintain data structure coherency, the 

synchronization paths are also used for general master/slave control functions—including 

memory size arbitration when the XPC-L system is started. 

1–8 6885 3522–003 

(2200) 

PCIOP PCIOP PCIOP PCIOP 

VI VI VI VI 

VI VI VI VI VI VI VI VI 

Active 

XPC-L Control 

Workstation 

VI 

VI 

VI 

VI 

VI VI 

VI VI 

VI VI 

VI 

VI 

VI 

VI 

VI 

VI 

Backup 


Control 

Workstation 


Direct Connect paths 

- 

Private LAN 


System

1.2.3. Software Components 

Introduction 

The hosts, XPC-L servers, and XPC-L Control Workstations run the following required or 

optional software: 

• OS 2200 host platforms run OS 2200/Exec software with the XPCEXEC feature. The 

XPCEXEC feature is a separately installed package for the Exec which must be 

ordered along with the XPC-L hardware. The following software components can 

use the XPC-L: 

− Multi-Host File Sharing (MHFS) 

− Partitioned Applications (PA) 

− Extended Transaction Capacity (XTC) 

• XPC-L Server platforms run Windows 2003, Enterprise Edition, and the XPC-L 

locking manager software. 

• XPC-L Control Workstation platforms run Windows XP Professional and the XPC-L 

Control software. 

The XPC-L Server software and the XPC-L Control software (including both versions of 

Microsoft Windows) are part of the XPC-L firmware release. Refer to the XPC-L System 

Firmware 2.2 Customer Reference Manual for more information. 

6885 3522–003 1–9

Introduction 

1.3. Notation Conventions 

This manual uses the following typographical conventions for command formats, 

examples, and procedural discussions: 

Code 

User 

Commands and other characters that you must type in to activate 

the command are shown in this monospaced font, with variable 

information also being italicized. Information displayed by the 

system is also shown in this monospaced font, with variable 

information being italicized. 

Commands and other characters that you type in are shown in 

this monospaced font, with variable information also being 

italicized. 

interface References to specific menu items, icons, options, and most 

other user interface elements are shown in bold text (italicization 

is only to match the rest of the paragraph containing the term). 

Ctrl+Break A plus sign separates the labels of two or more keys to be 

pressed at the same time. 

[ ] 

{ } 

| 

Brackets indicate optional parameters or fields. 

Braces indicate two or more required parameters or fields from 

which you must choose one. 

A vertical line indicates a choice between two or more 

parameters, for example: 

parameter | parameter 

Note: Braces, brackets, and vertical lines are not part of the command syntax; do not 

type them in. Unless otherwise indicated, use blank spaces (one or more) to separate 

fields when you enter input. 

1–10 6885 3522–003

Section 2 

Installation 

Software installation procedures vary, depending on the type of XPC-L system you 

ordered (see “2.1 Hardware Installation“). The installation information in this section 

consists primarily of references to existing documents and provides only those 

procedures that are unique to the XPC-L system. 

If you are unfamiliar with using an Intel node of a Dorado Series server, refer to any of 

the following documents for additional information: 

• ClearPath Plus Server Dorado 300 Series Install & Config Gd, Vol 5 Set Up OS 2200 

& Intel Part for Dorado 300 Series servers 

• ClearPath Plus Server Dorado Series Install & Config Guide, Vol 5: Set Up OS 2200 & 

Intel Part for Dorado 100 Series servers and Dorado 200 Series servers 

2.1. Hardware Installation 

Figure 2–1 shows the major hardware components comprising an XPC-L system. 

The XPC-L system uses one or more Unisys Dorado Series servers running the Windows 

2003, Enterprise Edition operating system. The following are the available options when 

ordering an XPC-L system: 

• An XPC-L system that includes a Dorado Series server. 

Note: If you ordered an XPC-L system which included a Dorado Series server, all 

required platform hardware would have already been installed. 

• An XPC-L system that does not include a cabinet for the Dorado Series server and 

where you use an existing Dorado Series server to house a single XPC-L server. 

6885 3522–003 2–1


If you ordered the above XPC-L system, refer to the following documents for the 

hardware platform installation procedure: 





2–2 6885 3522–003

E 

T 

H 

1 

E 

T 

H 

2 

Host A 

Primary 


P-C01 

P-C02 

P-C03 

P-C04 

P-S01 

P-S02 

Active 


Control 

Backup 


Control 

Figure 2–1. Major Hardware Components 

Host B 

Secondary 



PCIOP1-3 PCIOP1-4 PCIOP1-2 PCIOP1-1 


P-DC04 P-DC03 P-DC02 P-DC01 


PCIOP3-1 PCIOP3-2 

Host C 

PCIOP3-4 

PCIOP3-3 

HUB1 

P-S03 

P-S04 

P-C05 

P-C06 

P-C07 

P-C08 

LAN1 LAN2 

6885 3522–003 2–3 

S-C01 

S-C02 

S-C03 

S-C04 

S-S01 

S-S02 

S-S03 

S-S04 

S-C05 

S-C06 

S-C07 

S-C08 

HUB2 

LAN1 LAN2 

S-DC01 S-DC02 S-DC03 S-DC04 



Host D 

PCIOP4-1 

PCIOP4-2 

E 

T 

H 

1 

E 

T 

H 

2


2.1.1. Installing XPC-L Control Workstation Hardware 

The XPC-L Control Workstation hardware is a workstation supplied by Unisys with the 

appropriate hardware for supporting the operation of the XPC-L system. Unless 

otherwise directed by Unisys, do not change or modify any hardware on the XPC-L 

Control Workstation. Also, do not upgrade your XPC-L Control Workstation unless it is 

required to do so in the XPC-L Firmware 2.2 Customer Reference Manual or in the 

Technical Information Bulletin for an XPC-L system. Procedures for any required platform 

hardware updates are described in the documentation accompanying the XPC-L system 

firmware release. 

Documentation for installing the XPC-L Control Workstation is provided in the packaging 

from Dell. Connect the keyboard and monitor to the PC as documented. 

2.1.2. Installing XPC-L Server Hardware 

The XPC-L system hardware can be delivered by Unisys in two types. The system could 

include cabinetry with the Intel node installed in a Dorado Series server. Else, it could be 

shipped to your site as a stand-alone component, without the cabinet (except for 

Dorado 300 Series servers, which always include cabinetry). Initial installation depends 

on the type ordered and accordingly begins with one of the following two documentation 

sets: 

If the ordered XPC-L server style is 

• Installed as the Intel node of a Dorado 300 Series server, refer to the ClearPath Plus 

Server Dorado 300 Series Install & Config Gd Volumes 1 (Installing and Connecting 

Hardware), 2 (Setting Up Service Processors), 4 (Testing Hardware), 5 (Setting Up 

OS 2200 and Intel Partitions), and 6 (Completing Installation Tasks) for hardware 

installation procedures. Your system will arrive with the Intel partition connected to 

port 5 of the Monitor concentrator. 

2–4 6885 3522–003

Table 2–1. Intel Cabling Connections 

From To 


Name Port/Jack Name Port/Jack 

Intel Partition 1 Monitor 

Intel Partition 1 Keyboard 

Intel Partition 1 Mouse 

KVM9001301-CNV CAT5 Monitor 

Concentrator 

Monitor 

Concentrator 

Monitor 

Keyboard 

Mouse 

Back of the LCD tray 

on the left side (from 

the rear of the 

cabinet) 

Note: The Port/Jack column shows either port numbers or the labels of the jacks as they 

appear on the equipment. The following list provides additional information about the jacks: 

• CAT5 — Ethernet cable jack 

• Keyboard — PS/2 keyboard connector 

• Monitor — video connector 

• Mouse — PS/2 connector 

• Installed as the Intel node of a Dorado 200 Series host, refer to the ClearPath Plus 

Server Dorado Series Install & Config Guide, Vol 5: Set Up OS 2200 & Intel Part for 

hardware installation procedures. 

• Delivered as a stand-alone component, refer to the document Enterprise Servers 

Hardware Installation Guide hardware installation procedures. (This does not apply to 

Dorado 300 Series servers; they are not delivered as stand-alone components.) 

Follow the procedures in the appropriate hardware installation guide for insertion of new 

PCI connected devices to install the VI cards in the XPC-L server. 

2.1.3. Installing Host Hardware 

For the installation of your Dorado Series host, refer to the following documents: 





The only hardware components in a host unique to an XPC-L system are the VI cards and 

the PCIOP (the XIOP). 

6885 3522–003 2–5 

5


For information on adding or replacing PCIOPs, refer to the following documents: 

• For connecting PCIOP cables 

− ClearPath Plus Server Dorado 300 Series Install & Config Gd, Vol 1 Installing & 

Connecting H/W for Dorado 300 Series servers 

− ClearPath Plus Server Dorado Series Install & Config Guide for CSR, Vol 3 

Installing & Connecting H/W for Dorado 100 Series servers and Dorado 200 

Series servers 

Note: Volume 3: Installing and Connecting Hardware is available only to Unisys 

representatives. 

• For PCIOP PCA/VI card installation 

− Dorado Series Fault Isolation and Servicing Guide (Dorado 100 Series servers 

and Dorado 200 Series servers) 

− Dorado 300 Series Installation and Configuration Guide for Customer Service 

Representatives Volume 1: Installing and Connecting Hardware (Dorado 300 

Series servers) 

2.1.4. Installing VI Cables 

A number of VI cables are supplied with your XPC-L system. Refer to Figure 2–1 and the 

appropriate part of the worksheet (see Table B–1 through Table B–7) supplied with your 

XPC-L system. Compare the locations of the VI cards in the PCI slots of your server to 

determine the overall VI card interconnections that are required. Refer to Table 2–2 

(Dorado 300 Series servers) or Table 2–3 (Dorado 200 Series servers) to cable your 

system; the factory might have already connected some of the cables. 

Table 2–2. VI Cabling for Dorado 300 Series Servers 

From... To... 

Name Location Name Location 

Primary XPC-L Server, 

DC01 Host A Path 1 


C01 Host A Path 1 


S01 Path 1 


DC03 Host B Path 1 


C03 Host B Path 1 



Cell 0, Bus 3 Host A, PCIOP1-1 Customer Unique 

Cell 0, Bus 4 Secondary XPC-L Server, 



S01 Path 1 

Cell 0, Bus 4 

Cell 0, Bus 5 

Cell 0, Bus 6 Host B, PCIOP2-1 Customer Unique 



Cell 0, Bus 7 


2–6 6885 3522–003


From... To... 






S02 Path 2 






DC05 Host C Path 1 


C05 Host C Path 1 


S03 Path 3 


DC07 Host D Path 1 


C07 Host D Path 1 






S04 Path 4 





Secondary XPC-L Server, 











S02 Path 2 

Cell 1, Bus 4 

Cell 1, Bus 5 




Cell 1, Bus 7 

Cell 2, Bus 3 Host C, PCIOP3-1 Customer Unique 




S03 Path 3 

Cell 2, Bus 4 

Cell 2, Bus 5 

Cell 2, Bus 6 Host D, PCIOP4-1 Customer Unique 



Cell 2, Bus 7 





S04 Path 4 

Cell 3, Bus 4 

Cell 3, Bus 5 




Cell 3, Bus 7 





6885 3522–003 2–7



From... To... 















From... To... 
























Pod 0 

DIB-0-1-0 

Pod 0 

DIB-0-1-1 

Pod 0 

DIB-0-1-2 

Pod 0 

DIB-0-1-3 

Pod 0 

DIB-1-1-0 

Pod 0 

DIB-1-1-1 

Pod 0 

DIB-1-1-2 

Pod 0 

DIB-1-1-3 

Pod 2 

DIB-0-1-0 

Pod 2 

DIB-0-1-1 

Pod 2 

DIB-0-1-2 

Host C, PCIOP3-1 Customer 

Unique 

Host A, PCIOP1-1 Customer 

Unique 

Host D, PCIOP4-1 Customer 

Unique 

Host B, PCIOP2-1 Customer 

Unique 


Unique 


Unique 


Unique 


Unique 







Pod 2 

DIB-0-1-0 

Pod 2 

DIB-0-1-1 

Pod 2 

DIB-0-1-2 

2–8 6885 3522–003


From... To... 






S01 Path 1 


S03 Path 3 










S02 Path 2 


S04 Path 4 

















Pod 2 

DIB-0-1-3 

Pod 2 

DIB-0-2-1 

Pod 2 

DIB-0-2-3 

Pod 2 

DIB-1-1-0 

Pod 2 

DIB-1-1-1 

Pod 2 

DIB-1-1-2 

Pod 2 

DIB-1-1-3 

Pod 2 

DIB-1-2-1 

Pod 2 

DIB-1-2-3 

Pod 0 

DIB-0-1-0 

Pod 0 

DIB-0-1-1 

Pod 0 

DIB-0-1-2 

Pod 0 

DIB-0-1-3 

Pod 0 

DIB-1-1-0 

Pod 0 

DIB-1-1-1 

Pod 0 

DIB-1-1-2 

Pod 0 

DIB-1-1-3 




S01 Path 1 


S03 Path 3 










S02 Path 2 


S04 Path 4 

Pod 2 

DIB-0-1-3 

Pod 2 

DIB-0-2-1 

Pod 2 

DIB-0-2-3 

Pod 2 

DIB-1-1-0 

Pod 2 

DIB-1-1-1 

Pod 2 

DIB-1-1-2 

Pod 2 

DIB-1-1-3 

Pod 2 

DIB-1-2-1 

Pod 2 

DIB-1-2-3 


Unique 


Unique 


Unique 


Unique 


Unique 


Unique 


Unique 


Unique 

6885 3522–003 2–9


Figure 2–2 shows how to connect an individual VI cable to a VI card. The connectors are 

keyed to prevent misalignment or inversion. When inserting the cable, an audible click 

should be heard from the connector when it snaps into place. 

Figure 2–2. Fiber-Optic Cable Connectors 

After connecting a cable to a VI card, use the appropriate label supplied with your XPC-L 

system to indicate what this end of the cable connects to (for example, Host A, Path 1). 

Apply the label to the cable such that it is visible without disconnecting the cable. 

2.1.5. Installing Ethernet Cables and Hubs 

A number of Ethernet cables are supplied along with your XPC-L system. One or more 

Ethernet hubs might be also be included. Refer to Figure 2–1 and the appropriate part of 

the worksheet (see Table B–1 through Table B–7) supplied with your XPC-L system to 

determine the overall Ethernet card and hub interconnections that are required. Refer to 

Table 2–4 (Dorado 300 Series servers) or Table 2–5 (Dorado 200 Series servers) to cable 

your system; the factory might have already connected some of the cables. 

The Ethernet equipment provided with your XPC-L system is standard Ethernet 

hardware (refer to the appropriate Dorado Series manuals if you are unfamiliar with 

Ethernet equipment). Set up the connections between the Ethernet cards and hubs as 

indicated. After connecting a cable to an Ethernet card or hub, use the appropriate label 

supplied with your XPC-L system to indicate what this end of the cable connects to (for 

example, XPC-L Control Workstation 1, LAN 1). Apply the label to the cable such that it is 

visible without disconnecting the cable. 

In a redundant configuration, it is important to connect things properly. The Ethernet 1 

connections from each XPC-L server must connect to HUB1. Similarly, the Ethernet 2 

connections from each XPC-L server must connect to HUB2. If you are using Dorado 300 

Series servers, the Ethernet 1 connection is on cell 0 (LAN 0) and the Ethernet2 

connection is on cell 1 (LAN 4). The LAN1 connections from each XPC-L Control 

Workstation must connect to HUB1. The LAN2 connections from each XPC-L Control 

Workstation must connect to HUB2. 

The Ethernet hubs supplied with your XPC-L system must not be confused with or 

connected to any other Dorado Series server networking equipment (for example, 

Dorado Series server maintenance processor LAN). The maintenance processor LAN 

must be configured as a separate Ethernet network. 

2–10 6885 3522–003


The Ethernet card designated as part of the maintenance system can be used with the 

Dorado Series server maintenance processor LAN for things such as support for Call 

Home. The XPC-L Ethernet cards are separate and distinct from the Ethernet card used 

for maintenance. 

The Ethernet managed switch (NG700-SWX) used for the XPC-L Control Workstation 

interconnect is the same as that used in the XPC-L (Dorado 300 Series servers) for 

hardware control. However, when used for XPC-L Control Workstation interconnect, the 

switch is used as a simple switch rather than as a managed switch. All management 

programming is removed from the switch by forcing a factory reset: momentarily press 

the Factory Reset button located on the back of the unit, then cycle the AC power 

switch to OFF and then to ON again. 

Table 2–4. Ethernet Cabling for Dorado 300 Series Servers 

From... To... 


Hub 1 Port 1 Primary XPC-L Server 

(Ethernet 1) 

Hub 1 Port 2 Secondary XPC-L Server 

(Ethernet 1) 

Hub 1 Port 3 Active XPC-L Control PC 

(LAN 1) 

Hub 1 Port 4 Backup XPC-L Control PC 

(LAN 1) 


(Ethernet 2) 


(Ethernet 2) 


(LAN 2) 

Hub 2 Port 4 Backup XPC-L Control PC 

(LAN 2) 

Primary Server 

Control LAN 0 

Secondary 

Server Control 

LAN 0 

Port 15 Maintenance LAN 0 

Primary Server 

Port 15 Maintenance LAN 0 

Secondary Server 

Cell 0, Left Server LAN Port 


On-board Ethernet 




Add-In Card Ethernet 


Cell 0, right hand LAN port 

Cell 0, right hand LAN port 

6885 3522–003 2–11


Table 2–5. Ethernet Cabling for Dorado 200 Series Servers 

From... To... 



(Ethernet 1) 


(Ethernet 1) 


(LAN 1) 

Hub 1 Port 4 Backup XPC-L Control 

PC 

(LAN 1) 


(Ethernet 2) 


(Ethernet 2) 


(LAN 2) 

Hub 2 Port 4 Backup XPC-L Control 

PC 

(LAN 2) 

Primary 

Service 

Processor 

Maintenance 

LAN 

Secondary 

Service 

Processor 

Maintenance 

LAN 

Any open 

port 

Any open 

port 

Primary XPC-L Server 

(Maintenance Ethernet) 

Secondary XPC-L Server 

(Maintenance Ethernet) 

POD 0, DIB 0, 

SubDIB 2, Slot 3 

POD 0, DIB 0, 




POD 0, DIB 1, 


POD 0, DIB 1, 




POD 0, DIB 1, 


POD 0, DIB 1, 


2–12 6885 3522–003

2.2. Software Installation 

Software installation consists of two parts: 

• Installation of platform software 

• Installation of XPC-L software 

2.2.1. Installing Platform Software 


Before beginning the XPC-L software installation, you need to have installed the hosts, 

servers, and workstations that would comprise your XPC-L system. Doing these includes 

connecting them together and booting them. 

Installation of the hardware and default software is covered in the documentation 

specific to the host, server, and workstation. All default Windows software must be 

available on the XPC-L Control Workstations and similarly all default Dorado Series server 

software on the XPC-L servers. 

2.2.1.1. Installing Platform Software on the XPC-L Control 

Workstations 

All default Windows software is required on the XPC-L Control Workstations. 

The XPC-L Control Workstation supplied with your XPC-L system has Windows XP 

Professional already loaded. This subsection describes how to complete the installation 

of the operating system and also how to configure the workstation for local use. Perform 

these procedures for the active XPC-L Control Workstation and for any backup XPC-L 

Control Workstation supplied with your XPC-L system. 

Installing Windows XP 

Perform the following steps to complete installation of the operating system and to enter 

the user names and passwords for this workstation. 

Note: A customer representative must accept software license agreements; a Unisys 

service representative cannot perform these functions. 

1. Turn on the workstation. The system boots and the Windows XP Setup Wizard 

appears. 

2. Click Next. 

The End User Software License Agreement window appears. 

3. Request the customer's representative to perform the following steps to accept the 

End User License Agreements (EULA): 

a. Read the license agreements, scrolling as necessary. 

b. Select the I accept the agreement check box for each EULA and then click 

Next. 

The Regional and Language Options dialog box appears. 

6885 3522–003 2–13



The Personalize Your Software dialog box appears. 

5. Type in your name and the name of your company or organization and click Next. 

A dialog box appears in which you enter the product key for Windows XP operating 

system. 

6. Type in the product key and click Next. 

Note: For the OptiPlex 755 and 960 workstations, you may have to use an XP 

product key from one of the service processors or any PC that has an XP product 

key. Please refer to “Windows XP Activation“ of this section for an explanation of 

this procedure. 

7. Use the XPC-L System Information part of the worksheet provided with your system 

(see Table B–8 for an example of this table) to respond to the resulting What’s 

your computer name? message. 

• Type the Computer Name from the appropriate row of the XPC-L System 

Information part of the worksheet provided with your system into the Name 

box. 

• Type a password of your choice into the Password box. 

• Set the Date, Time, and Time Zone boxes appropriately. 

• Click Next. 

The Network Settings dialog box appears. 

8. Select the Typical option and click Next. 

The Workgroup or Computer Domain dialog box appears. 

9. Select the No option (this selects Workgroup) and click Next. 

The system performs the final set up tasks, and displays Completing the Window XP 

Setup Wizard. 

10. Click FINISH. 

The system reboots. 

Setting up Network Configurations 

Perform the following steps to configure and set up the network configurations. The 

workstation has two Ethernet ports installed. 

The onboard Ethernet port is LAN2 when looking at the Microsoft Network Connections 

window and must be configured with the Network IP address 1 shown in Table B–8. The 

port provided by the PCI Ethernet card is simply LAN when looking at the Microsoft 

Network Connections window and must be configured with the Network IP address 2 

shown in Table B–8. 

2–14 6885 3522–003

1. On the Start menu, point to settings and click Control Panel. 

2. Double-click the Network and Internet connections category. 


The Network and Internet connections window appears. There are two parts to this 

window; the top part has the caption Pick a task and the lower part has the 

caption or pick a Control Panel Icon with labeled icons below it. 

3. On the lower part of the window, click Network Connections. The Network 

Connections window appears. 

4. Right-click the appropriate Local Area Connection icon and click Properties. 

The Local Area Connection Properties window appears. 

5. Click Internet Protocol (TCP/IP) to highlight it. 

6. Click Properties. 

The Internet Protocol (TCP/IP) Properties dialog box appears. 

7. Click Use the following IP address and fill in the boxes as follows: 

a. Type the IP address for this workstation. Also write it into the appropriate row 

and column of the XPC-L System Information part of the worksheet provided 

with your system (see Table B–8 for an example of this table). 

b. Type the appropriate Subnet mask. 

c. Leave the boxes Default gateway, DNS server, and Alternate DNS 

server blank. 

d. Click OK to close the Internet Protocol (TCP/IP) Properties window. 

8. Click Close to close the Local Area Connection Properties window. 

9. Repeat steps 4 through 8 for the other network card (the other Local Area 

Connection icon). 

10. Close Control Panel. 

Windows XP Activation 

The Dell OptiPlex 755 and 960 workstations that are shipped as Control Workstations for 

the XPC-L have Windows XP SP2 installed. These workstations are setup at the Unisys 

factory for use as XPC-L Control Workstations. The most recently shipped OptiPlex 755 

and 960 workstations have a software option to downgrade from Windows Vista 

Business Bonus-Windows XP Professional. 

After you downgrade to Windows XP, you will no longer be able to activate the XP 

software over the Internet. When prompted to activate, call the activation support 

number and speak to the customer service representative who will help you activate the 

Windows XP software. 

Before you call the activation support number, ensure that you have the Windows XP CD 

and the XP product key from one of your existing workstations or service processors. 

You might be asked for the product key to activate the XPC-L workstation. 

6885 3522–003 2–15


2.2.1.2. Creating Partitions on the XPC-L Servers 

The XPC-L software runs in a hardware partition with a specific configuration. Perform 

the following steps on each server to create and configure an XPC-L partition. 

Note: If you ordered an XPC-L system that included a cabinet for the Dorado Series 

server, the hardware partition profiles would have already been installed. 

Dorado 300 Series Servers 

Using Server Sentinel, install PartitionX (where X is the partition number, 0 through 9). 

For instructions on creating and configuring partitions, refer to the Server Sentinel User's 

Guide and Task Help. 

Activate the partitions and enable each of the PCI buses needed for your system. Refer 

to the worksheet supplied with your system (Appendix B, “Example XPC-L Server PCI 

Locations Charts and Worksheets“ contains a sample of this worksheet). 

Note: Due to an existing Windows problem, PCI bus 1 must be up in all cells before 

booting the server. 

Dorado 200 Series Servers 

Perform the following steps and use the partition profiles provided on the XPC-L 

Firmware CD. 

1. Insert the XPC-L Firmware CD (which contains the XPC-L installation application) into 

the CD-ROM drive of the Service Processor of the Dorado Series server being used 

as the XPC-L server and cancel the installation program that starts automatically. 

2. Refer to the appropriate part of the worksheet (see Table B–1 through Table B–7) 

supplied with your XPC-L system; compare the locations of the VI cards in the PCI 

slots of your server to determine whether the XPC-L partition is in pod 0/ , 2 (lower 

profile) or in pod 1, 3 (upper profile). 

3. Copy the /PartitionProfiles directory from the CD to the C:\ drive on the Dorado 

Series server Service Processor and install the appropriate profile (XPCLLower.ptn or 

XPCLUpper.ptn) to the /PartitionProfiles directory. Repeat this for each Service 

Processor (master and slave). 

4. Use Server Sentinel to activate the partition XPCLLower for each of your XPC-L 

servers. Enable each of the DIBs and SubDIBs needed for you system. Refer to the 

appropriate part of the worksheet (see Table B–1 through Table B–7) supplied with 

your XPC-L system and compare the locations of the cards in the PCI slots of your 

server. 

2–16 6885 3522–003

Notes: 

This applies to Dorado 200 Series servers only. 


• You must use the appropriate partition profile provided on the release media. These 

profiles work for all installations. Contact Unisys if you think that the delivered files 

will not work with your installation.. Do not attempt to create or use partition profiles 

other than those delivered. 

• The partition profiles provided on the release media configure all possible PCI buses 

and bridges. During initialization, the system displays an error message for each 

component not found. Verify that each component identified as not being found 

really does not exist at your installation. 

Refer to the appropriate Server Sentinel documentation for specific information about 

creating partitions on the XPC-L servers. 

2.2.1.3. Installing Platform Software on the XPC-L Servers 

All default Dorado Series server software is required on the XPC-L servers. 

The XPC-L system uses one or more Dorado Series servers running the Windows 2003, 

Enterprise Edition, operating system. You have the following general options when 

ordering an XPC-L system: 

• An XPC-L system that includes a Dorado Series server with cabinet. 

• An XPC-L system that does not include a cabinet for the Dorado Series server, 

where you will use an existing Dorado Series server to house one XPC-L server. 

XPC-L Server with Cabinet 

If you ordered an XPC-L system which included a Dorado Series server with cabinet, 

most of the software would have already been installed. Perform the following steps to 

install the rest of the server platform software. 

Note: The mouse is disabled; Use the tab key to move through the available fields and 

buttons. 

1. Start the XPC-L Partition from Server Sentinel. 

The system boots and the Windows Setup Wizard appears. 

2. Press the tab key to go to Next and press Enter. 

6885 3522–003 2–17


3. When the End User Software License Agreement appears, request a representative 

of the customer to perform the following steps to accept the End User License 

Agreements (EULA): 

a. Read the license agreements, using the Page Up and Page Down keys to 

scroll as necessary. 

b. Click I accept the agreement for each EULA and then press the tab key to 

select Next and press Enter. 


Note: A customer representative must accept software license agreements; a 

Unisys service representative cannot perform these functions. 

4. Press Enter. 

The Personalize Your Software dialog box appears. 

5. Type your name and the name of your company or organization, then select Next 

using the tab key and press Enter. 

The Licensing Modes dialog box appears. 


7. Use the XPC-L System Information part of the worksheet provided with your system 

(see Table B–8 for an example of this table) to respond to the resulting computer 

name and password display. 

− Type the name written in the appropriate row under the Computer Name column 

of the worksheet into the Name box. 

− Type a password of your choice in the Password box. 

8. Set the Date, Time, and Time Zone fields appropriately. 

9. Select Next using the tab key and press Enter. 

The Network Settings dialog box appears. 

10. Select the Typical option, then select Next using the tab key and press Enter. 

The Workgroup or Computer Domain dialog box appears. 

11. Select the No option to select Workgroup. 

12. Select Next using the tab key and press Enter. 

13. Select FINISH using the tab key and press Enter. 

The system reboots. 

14. After the XPC-L server reboots, log on as administrator so you can configure the 

maintenance LAN IP address for Call Home. 


2–18 6885 3522–003



The Network and Internet connections window appears. This window consists of 

two parts; the top part has the caption Pick a task and the lower part has the 

caption or pick a Control Panel icon with labeled icons below it. 



18. Click Start, point to Settings and select Network Connections. 

19. Right-click the LAN connection labeled LAN2 and select Properties. 




22. Type the IP address for the appropriate XPC-L server and XPC-L platform referring to 

Table B–8. 

23. Type the appropriate subnet mask. 

24. Leave the boxes Default gateway, DNS server, and Alternate DNS server 

blank. 

25. Click OK to close the Internet Protocol (TCP/IP) Properties window. 



XPC-L Server without Cabinet 

If you ordered an XPC-L system which does not include a cabinet for the Dorado Series 

server, where you will use an existing Dorado Series server to house one XPC-L Server, 

refer to the appropriate documents in the following list for the hardware platform 

installation procedure. Note that you must refer to the information specific to Windows 

2003, Enterprise Edition, as well as the information appropriate for your Dorado Series 

server. 


& Intel Part for Dorado 300 Series servers or ClearPath Plus Server Dorado Series 

Install & Config Guide, Vol 5: Set Up OS 2200 & Intel Part for Dorado 100 Series 

servers and Dorado 200 Series servers 

• Windows 2003, Enterprise Edition (32-Bit Version) Information Notice 

6885 3522–003 2–19


While installing the platform software, ensure that all the subDIBs (Dorado 200 Series 

servers) or PCI buses (Dorado 300 Series servers) with VI cards are down in the partition 

during the installation procedures. You must also use the IP addresses and host names 

identified on the worksheets provided with the system (see Table B–8 and Table B–9 for 

examples of these worksheets). Following the completion of the platform software 

installation procedures in the preceding reference documents, perform the following 

steps: 

1. Refer to “Increasing the Size of the Windows Nonpaged Pool” later in this 

subsection for instructions on how to increase the size of the nonpaged pool in 

Windows. 

2. Shut down Windows. 

3. Bring up the subDIBs containing the VI cards. 

4. Start the partition. 

5. Refer to “Installing VI Card Driver Software” later in this subsection for instructions 

on how to install the software driver for the VI cards in the Intel partition of an 

existing Dorado Series server. 

6. After the XPC-L server reboots, log on as administrator in order to configure the 

Maintenance LAN IP address for Call Home. 



The Network and Internet connections window appears. There are two parts to this 

window; the top part has the caption Pick a task and the lower part has the 

caption or pick a Control Panel Icon with labeled icons below it. 



10. From the Start menu, choose Settings, and then select Network Connections. 

11. Right-click the LAN connection labeled LAN2 and select Properties. 




14. Type the IP address for the appropriate XPC-L server and XPC-L platform from 

Table B–8. 

15. Type the appropriate Subnet mask. 

16. Leave the boxes Default gateway, DNS server, and Alternate DNS server 

blank. 




2–20 6885 3522–003

Increasing the Size of the Windows Nonpaged Pool 


If you ordered an XPC-L system that included a cabinet, all of the required platform 

software is already installed, including the modification to increase the size of the 

nonpaged pool in Windows. 

If you ordered an XPC-L system that did not include a cabinet for the Dorado Series 

server, where you will use an existing Dorado Series server to house one XPC-L server, 

perform the following steps: 

1. Ensure that Windows has booted on the XPC-L server. 

2. Log on as an administrator. 

3. Insert the XPC-L Firmware CD into the CD-ROM drive of the Intel partition of the 

Dorado Series server. 

You might receive the installation setup dialog box for XPC-L Control after inserting 

the CD. Do not install XPC-L Control onto the server. 

4. Navigate to CD-ROM_drive_letter:/Server Registry Changes/ and double-click 

System Pages.reg. 

A message appears in the Registry Editor asking you to confirm if you wanted to add 

the information to the registry. 

5. Click Yes. 

A message appears in the Registry Editor stating that the information has been 

successfully entered into the registry. 

6. Click OK. 

7. Remove the XPC-L Firmware CD from the CD-ROM drive of the Intel partition of the 

Dorado Series server and reboot the server to make these changes effective. 

6885 3522–003 2–21


Installing VI Card Driver Software 

If you ordered an XPC-L system that included a cabinet, all of the required platform 

software is already installed, including VI card driver software. 

If you ordered an XPC-L system that did not include a cabinet, where you will use an 

existing Dorado Series server to house one XPC-L server, perform the following steps: 

1. With all necessary hardware components installed and enabled, power on and boot 

the Intel partition of the Dorado Series server. 


The hardware message displays the message Can Windows connect to Windows 

update search for software? 

3. Click No, not at this time. Then click Next. 

A Found new hardware window appears. 

4. Leave Install Automatically selected, but do not click Next. 

5. Insert the XPC-L Firmware CD into the CD-ROM drive of the Intel partition of the 


You might see the installation setup dialog box for XPC-L Control after inserting the 

CD. If you do, click Cancel; do not install XPC-L Control onto the server. 

A message in the Hardware Installation window states that this adapter did not pass 

Windows Logo testing. 

6. Click Continue Anyway. 

The VI card software driver is installed. 

7. Click Finish. 


8. Ensure that Install Automatically is selected and click Next. 

9. Repeat steps 6 through 8 for each VI card until the software driver is installed for all 

cards. 

10. Remove the XPC-L Firmware CD from the CD-ROM drive of the Intel partition of the 


2–22 6885 3522–003


Perform the following steps to change the network settings for each of the VI cards: 

1. On the Start menu, point to Settings and click Control Panel. 

2. Double-click Network Connections. 

A Network Connections window appears. 

3. Right-click one of the VI cards and select Properties. 

A Local Area Connection Properties window appears. 

4. Clear each of the check boxes listed under This connection uses the 

following items. 

5. Select the Show icon in notification area when connected check box. 

6. Clear Notify me when this connection has limited or no connectivity 

check box. 

7. Click OK. 

8. Repeat steps 3 through 7 for each VI card. 

9. Close the Network Connections window. 

10. Reboot the server. 

Caution 

1. You must change the network settings for each VI card. Failure to do so 

could result in unpredictable behavior. 

2. Do not perform these network setting changes for non-VI cards such as 

the Ethernet cards in the system. 

6885 3522–003 2–23


2.2.1.4. Installing Platform Software on the OS 2200 Hosts 

All default OS 2200 software is required to be installed on the OS 2200 hosts. Refer to 

OS 2200 software installation documentation for installation procedures. After loading 

default OS 2200 software, you have to load PCIOP microcode that contains drivers for 

the VI cards. 

There are two ways of installing microcode files on XPC-L XIIPs; both use the MCLOAD 

utility. One method is to load the microcode files directly from the released tape; the 

other method is to load the files from a cataloged file on to the system. 

New platform microcode for XIIPs is released on a tape containing two files. The first file 

contains information about the definition files and their origin in program file format. The 

second file contains the microcode that will be transferred to the XIIP by the MCLOAD 

utility in a data file in COPYG format. 

The first mechanism for loading the platform software on the host is to use MCLOAD in the 

IOPUTIL runstream to load from tape. The MCLOAD utility uses PCFP to position the tape to 

the specified file and loads the microcode from that file to a scratch file before 

transferring it to the XIIP. This process requires loading a tape for each XIIP that is 

reloaded. 

The second mechanism uses a demand runstream to copy the second file of the 

platform microcode release tape onto a cataloged file and then reference it with runs of 

the IOPUTIL utility. The procedure for doing this is to enter the following commands from 

a demand run or to construct a runstream to be started from the operator console that 

includes these commands: 

@ASG,TJ PLATFORM.,T,[reel] . Assign the unlabeled Platform Release tape. 

@MOVE PLATFORM.,1 . Skip to second file on the Platform Release tape 

@ASG,C MCODE-XIIP,F///1000 . Catalog a large enough file for microcode to load 

@COPY,G PLATFORM.,MCODE-XIIP. . Copy the platform microcode to mass storage 

@CHG,R MCODE-XIIP. . For safety make the file Read-Only 

@FREE PLATFORM. 

The IOPUTIL can now be used to load microcode to all XIIPs in the configuration without 

the need to mount tapes. Note that the microcode file on mass storage is not cataloged 

as public and is made “read-only“ for safety. As usual for site management files, the 

normal site security methods must be used to ensure that the IOPUTIL runstream runs 

with access privileges that allow it to read the MCODE-XIIP file. 

2–24 6885 3522–003

2.2.2. Preparing to Install XPC-L Software 


Extended Processing Complex-Locking (XPC-L) software installation consists of the 

following three parts: 

• Installation and configuration of the XPC-L Control software on the XPC-L Control 

Workstations 

• Installation and configuration of the XPC-L lock manager software on the XPC-L 

servers 

• Installation and configuration of OS 2200 Exec features on or Dorado Series servers 

XPC-L lock manager software installation is initiated from the XPC-L Control software. 

Exec features are installed using the standard SOLAR installation process to create an 

Exec boot tape. The Site Configuration Management System (SCMS) used to create the 

system definition for the OS2200 system is also used to include the XPC-L in the host 

configuration. 

It does not matter whether you install the XPC-L Control software or configure the 

OS 2200 Exec to use XPC-L first. However, you must start the XPC-L Control software 

before the Exec can access the XPC-L. 

The following is an overview of XPC-L software installation: 

1. Prepare to install software. 

• Modify the default hosts file on each XPC-L Control Workstation and XPC-L 

server. 

• Create a configuration file (ASCII) and store it on each XPC-L Control 

Workstation. 

• Create user accounts and update security settings on the XPC-L Control 

Workstations and on the XPC-L servers. 

• Create shared folders on the XPC-L servers. 

2. Install software required by the XPC-L product on the XPC-L Control Workstations. 

3. Install software required by the XPC-L product on the XPC-L servers. 

4. Install software required by the XPC-L product on the hosts. 

6885 3522–003 2–25


2.2.2.1. Modifying the Hosts File 

Perform the following steps to modify the default hosts file on each XPC-L server and 

each XPC-L Control Workstation. 


server, the hosts file would have already been modified. The hosts file is also modified 

appropriately on each XPC-L Control Workstation. 

1. Copy the default hosts file appropriate for your server type from the root of the 

installation CD-ROM to a diskette. For example, 

− For Dorado 300 systems, copy z:\Dorado 300\hosts to a:\hosts. 

− For Dorado 200 systems, copy z:\hosts to a:\hosts. 

2. Log on to the active XPC-L Control Workstation as an administrator and use 

Windows Notepad to open the following file: 

C:\Windows\system32\drivers\etc\hosts 

The default file contains comments explaining the format of the entries it contains. 

3. Log on to the backup XPC-L Control Workstation (if the backup XPC-L Control 

Workstation exists in your configuration) as an administrator and copy the hosts file 

from the diskette to the following location, replacing the existing file: 


4. Log on to the primary XPC-L server as an administrator and copy the hosts file from 

the diskette to the following location, replacing the existing file: 


5. Modify the hosts file for the XPC-L Server Maintenance LAN for your appropriate 

Platform. Also add this IP address to the hosts file of the Service Processor. 

6. Log on to the secondary XPC-L server (if the secondary XPC-L server exists in your 

configuration) as an administrator and copy the hosts file from the diskette to the 

following location, replacing the existing file: 


7. Modify the hosts file for the XPC-L server maintenance LAN for your appropriate 

platform. Also add this IP address to the hosts file of the Service Processor. 

2–26 6885 3522–003


---------------------------------------------------------------------------- 

# Copyright (c) 1993-1999 Microsoft Corp. 

# 

# This is a sample HOSTS file used by Microsoft TCP/IP for Windows. 

# 

# This file contains the mappings of IP addresses to host names. Each 

# entry should be kept on an individual line. The IP address should 

# be placed in the first column followed by the corresponding host name. 

# The IP address and the host name should be separated by at least one 

# space. 

# 

# Additionally, comments (such as these) may be inserted on individual 

# lines or following the machine name denoted by a '#' symbol. 

# 

# For example: 

# 

# 102.54.94.97 rhino.acme.com # source server 

# 38.25.63.10 x.acme.com # x client host 

# 

127.0.0.1 localhost 

192.168.225.1 P-XPC-L # primary xpc-l server (Eth 1) 

192.168.225.2 S-XPC-L # secondary xpc-l server (Eth 1) 

192.168.225.3 Active-XPC-Ctl # active xpc-l control pc (Eth 1) 

192.168.225.4 Backup-XPC-Ctl # backup xpc-l control pc (Eth 1) 

# 

192.168.226.1 P-XPC-L # primary xpc-l server (Eth 2) 

192.168.226.2 S-XPC-L # secondary xpc-l server (Eth 2) 

192.168.226.3 Active-XPC-Ctl # active xpc-l control pc (Eth 2) 

192.168.226.4 Backup-XPC-Ctl # backup xpc-l control pc (Eth 2) 

# Call Home for the XPC-L Servers requires a seperate lan connection to the 

Service 

# Processors Maintenance lan. You need to modify this host file for the 

ES7000 platform 

# that you are using. You also need to add the IP addresses to the Service 

Processor 

# HOSTS file. 

#172.26.3.20 P-XPC-L # primary xpc-l server maintenance lan 

(ES7000/one) 

#172.26.3.21 S-XPC-L # secondary xpc-l server maintenance lan 

(ES7000/one) 

#192.168.222.4 P-XPC-L # primary xpc-l server maintenance lan 

(ES7000/550) 

#192.168.222.5 S-XPC-L # secondary xpc-l server maintenance lan 

(ES7000/550) 

Example 2–1. Example Hosts File 

6885 3522–003 2–27


2.2.2.2. Creating a Configuration File 

If you ordered an XPC-L system that included a cabinet, a configuration file matching the 

ordered system is included. This file is the ConfigFile.txt on C: of the XPC-L Control 

Workstations. If you want to modify the file, refer to “3.4 Configuration File.“ 

If you ordered an XPC-L system that did not include a cabinet, because you plan to use 

an existing Dorado Series server to house one XPC-L server, use the appropriate part of 

the worksheet (see Table B–1 through Table B–7) supplied with your XPC-L system as 

input for creating a configuration file. Appendix B, “Example XPC-L Server PCI Locations 

Charts and Worksheets“ contains a sample of this chart. Two default ConfigFile.txt 

files are included with the XPC-L Firmware CD. The ConfigFile.txt file for the Dorado 

200 Platform is available at the root directory and the ConfigFile.txt file for the Dorado 

300 Platform in the Dorado 300 folder. 

Use an ASCII text editor and information available in the worksheet to create an XPC-L 

Configuration file (required for the installation steps in “Identifying the Location of the 

configuration file“) that describes the connections between the XPC-L servers and the 

hosts. Store the XPC-L configuration on the XPC-L Control Workstation that will initially 

be the active XPC-L Control Workstation (“Identifying the Location of the Configuration 

File“ solicits the location of the file). Also, maintain a copy of the configuration file on any 

backup XPC-L Control Workstation. Subsection “3.4.1 Configuration File Syntax“ defines 

the configuration file parameters in detail. 

2.2.2.3. Creating User Names and Updating Local Security Policies 


server, the user names would have already been created and the local security policies 

would have already been updated. 

Create two local user names (Windows users) on each XPC-L server and on each XPC-L 

Control Workstation: 

• The user name under which XPC-L Control runs. This username will be a member of 

the Administrators group and must be identical on the XPC-L servers and on all 

XPC-L Control Workstations. 

• The user name for the XPC-L Server service. This username will be a member of the 

Administrators group and must be identical on the XPC-L servers and on all XPC-L 

Control Workstations. 

2–28 6885 3522–003

Define user rights for each XPC-L Server service running on each XPC-L server. 


• XPC-L Control: User Rights Assignment—who can access the XPC-L Control 

Workstation over the LAN (Access this computer from the network: Either 

select Everyone or add the user name under which the XPC-L Server service runs). 

• XPC-L Server: User Rights Assignment—what privileges the XPC-L Control 

Workstation will have when accessing the XPC-L server (Access this computer 

from the network) and what privileges the XPC-L server service will have on the 

XPC-L server (Log on as a service and Lock pages in memory). 

• XPC-L Control: Security Options—increases the XPC-L server's access privilege from 

the default of “Guest“ when it logs onto the XPC-L workstation. 

XPC-L Control Workstations 

The following steps are already performed for each XPC-L Control Workstation; the 

following information is given to show how the user names and user rights on the XPC-L 

Control Workstations correlate to those on the XPC-L servers. 

Use the User Name/Password Information part of the worksheet (see Table B–9) while 

performing the following steps: 

1. Add the defined user name under which XPC-L Control will run to the Windows 

Administrators group (refer to “A.1 Creating a New User Name“). 

2. Add the defined user name under which the XPC-L Server service will run to the 

Windows Administrators group (refer to “A.1 Creating a New User Name“). 

3. Set the user rights assignment Access this computer from the network to 

include Everyone or the user name under which XPC-L Server service runs (refer to 

“A.2 Setting User Rights Assignments“). 

Note: You may not want to set Access this computer from the network to 

Everyone for security reasons—specifying individual user names that are allowed 

to access the XPC-L Control Workstation provides greater security. 

4. Change the security option Network Access: sharing and security model 

for local accounts from Guest only—local users authenticate as Guest 

to Classic—local users authenticate as themselves (refer to “A.3 Setting 

Security Options“). 

5. Reboot the workstation to make the user rights changes effective. 

6885 3522–003 2–29


XPC-L Servers 

Log on to each XPC-L server as an administrator and perform the following steps: 

1. Create a user name for the XPC-L Server service (refer to “A.1 Creating a New User 

Name“). Add this user name to the Windows Administrators group. This name 

is used by Windows as a local log on, so it must be set up on the servers without a 

domain specification. After it is entered, the user name should appear preceded by 

servername\ and not domainname\ when displayed in the Administrators group. 

2. Set the XPC-L Server service user name (or a group of which it is a member) to have 

the user rights assignments of Log on as service and Lock pages in memory 

(refer to “A.2 Setting User Rights Assignments“). 

3. Create a user name under which XPC-L Control will run (refer to “A.1 Creating a 

New User Name“). Add this user name to the Windows Administrators group 

on this server. 

4. Set the user rights assignment Access this computer from the network to 

Everyone or to the user name under which XPC-L Control runs (refer to “A.2 

Setting User Rights Assignments“). 

Note: You may not want to set Access this computer from the network to 

Everyone for security reasons specifying individual user names that are allowed to 

access the XPC-L Control Workstation provides greater security. 

5. Reboot the server to make the user rights changes effective. 

2–30 6885 3522–003

2.2.2.4. Creating Shared Folders 


Note: In an XPC-L system that includes a cabinet for the Dorado Series server, the 

shared folders would have already been created. 

A shared folder XPC-L SHARE is used on each XPC-L server for various XPC-L files, 

including the following: 

• Executable files 

• DLLs 

• Log files 

• Dump files 

Log onto each XPC-L server as an administrator and create the shared folder in the C: 

root directory as follows: 

1. Launch Windows Explorer. 

2. Select New on the File menu to create a folder. Name the folder XPC-L SHARE. 

3. Right-click the XPC-L SHARE folder and click Properties. 

The XPC-L SHARE Properties dialog box appears 

4. Click Sharing tab. 

5. Select the Share this folder check box and type XPC-L SHARE in the Share 

name box. 

6. Click Permissions. 

7. Select the Full Control, Change, and Read check boxes. Click Apply, and then 

click OK. 

8. Click Apply, and then click OK to complete the creation of the shared folder. 

Notes: 

• The XPC-L SHARE folder will already exist if the server has been previously 

prepared for use as an XPC-L server. 

• If you map the XPC-L Share folder on either XPC-L server or XPC-L Control 

Workstation, it must be mapped with the same user name as the one used for 

running XPC-L Control. 

6885 3522–003 2–31


2.2.3. Installing XPC-L Control Workstation Software 

To install the XPC-L Control software, you must be logged on to the XPC-L Control 

Workstation as an administrator. The XPC-L Control software runs as a Windows 

application. Use the XPC-L Control Workstation software to install XPC-L server software 

on the XPC-L platforms. 

When you install the software on each XPC-L Control Workstation, ensure that no other 

XPC-L Control Workstation has the XPC-L control application software running on it. This 

is because having more than one active XPC-L Control Workstation at a time causes 

problems. 

2.2.3.1. Installing the XPC-L Control Software 

Note: The XPC-L Control software has already been installed on each XPC-L Control 

Workstation. The following information is provided for use in the case where you need to 

reinstall the software. 

The XPC-L Firmware CD contains the installation application, the XPC-L Control software, 

the XPC-L service executable file, and associated libraries. The installation program is an 

InstallShield script. It gives you options to create a shortcut icon on the desktop and to 

set automatic start of XPC-L Control when you boot the active XPC-L Control 

Workstation. At the end of the installation process, the installation program gives you the 

option of starting the XPC-L Control software. 

1. Load the CD into the CD drive of the XPC-L Control Workstation. 

The installation application should begin the installation process. If the installation 

application does not load immediately on Windows Explorer, double-click setup.exe 

in the root directory of the CD. 

The Install Shield Wizard dialog box appears. 


The installation program prompts you to set the location of the XPC-L Control 

program going to be installed. 

3. Click Next to install the software on the default destination folder. 

The default folder is C:\Program Files\Unisys\XPC-L Control\. 

4. Click YES in response to the dialog box about creating a desktop icon. 

5. Click NO in response to the dialog box about setting automatic restart of program. 

6. At the end of installation, select I would like to launch XPC L Control check 

box if you would like to launch XPC-L Control immediately. 


2–32 6885 3522–003

The State File 


The state file contains the software license code, XPC-L Control Workstation names, the 

server names of the default and current master platforms, and the state (“up“ or 

“down“) of interfaces. The state file is an ASCII text file XPC-L Control.ini. This file is 

located in C:\ when XPC-L Control is first run and is retrieved from there on subsequent 

runs. 

XPC-L Control displays a warning box on the XPC-L Control Workstation reminding you 

that only one XPC-L Control Workstation can be active on the XPC-L private LAN at a 

time. Stop the XPC-L Control software on any other XPC-L Control Workstations before 

clicking Yes on this warning box. 

2.2.3.2. Identifying the Location of the Configuration File 

The XPC-L configuration file is an ASCII text file that describes the VI card configuration 

of the primary and secondary XPC-L servers. You created this configuration file using 

steps in “2.2.2.2 Creating a Configuration File.“ 

The master XPC-L server validates the configuration data during initialization. The 

configuration data provides information about the XPC-L platforms in the configuration 

(the first one identified in the file is the primary XPC-L server), and various parameters 

that identify the hardware that connects the components of the XPC-L system. 

Subsection “3.4.1 Configuration File Syntax“ defines the configuration file parameters in 

greater detail. 

Upon executing XPC-L Control on a given workstation, XPC-L Control displays a message 

box indicating that a configuration file must be opened. This happens when it detects 

that XPC-L configuration data is not available in the State File, indicating that a 

configuration file must be opened. Click OK. 

XPC-L Control then displays its log in window and the main window. The menu items 

Action and Tools become available after a configuration file is opened. 

Click Open Config File on the File menu to browse to and open the XPC-L 

configuration file. 

At this point, XPC-L Control attempts to connect to the primary and secondary XPC-L 

Servers to determine the current status of the servers. 

If one or both of the servers are not currently booted, there will be a considerable delay 

(a couple of minutes) as Windows searches the entire network for the servers. 

Eventually, the status is displayed in a Select Server pane as “Server not found“ (see 

Figure 2–3). 

6885 3522–003 2–33


Figure 2–3. XPC-L Control Window: Select Server Pane 

XPC-L Control retains the currently opened configuration data in the XPC-L Control State 

file until you choose to load a new configuration file. The server names from that 

configuration data are displayed as the server names for the primary and secondary 

XPC-L servers at the top of the main window and are used by XPC-L Control to 

communicate with the servers. Subsection “3.4.1 Configuration File Syntax“ describes 

the configuration file in detail. 

If you will be installing XPC-L Control software on another XPC-L Control Workstation, 

exit from this copy of the software; only one copy must be running at a time within the 

XPC-L private LAN during installation. 

2–34 6885 3522–003

2.2.4. Installing XPC-L Server Software 


Note: If you ordered an XPC-L system which included a cabinet for the Dorado Series 

server, the XPC-L server software would have already been installed. 

Use the XPC-L Control software to install XPC-L Server software on the XPC-L servers. 

Note: A prerequisite for installation of the XPC-L Server software is that a directory 

must exist on the XPC-L platform whose shared name is XPC-L Share (see “2.2.1 

Installing Platform Software“). 

1. Run XPC-L Control on the XPC-L Control Workstation and click Install XPC-L 

Software on the Tools menu. 

Note: Upon initial execution of the XPC-L Control software, the Action and Tools 

menu selections are inactive until a configuration file is opened. Click Open Config 

File on the File menu and point it to the configuration file created in “Creating a 

Configuration File.“ 

2. Make sure the XPC-L servers are booted. 

If either entry under Servers in the main window displays “Server not found“ as its 

status, then either the server is not booted or the name of the server in the 

configuration file is incorrect. You can continue to the next step, once the Select 

Server display has been updated with “Service not found“ (the software has not 

been installed yet) or “Stopped“ (the software is being reinstalled, thus the service 

is stopped). 

6885 3522–003 2–35


3. Install the XPC-L executable and DLLs on the XPC-L servers: 

Select each server in turn by clicking the server name in the Select Server pane. 

Click Tools, and then click Install XPC-L Software to install the XPC-L Server 

service on the selected server. 

a. The License Code dialog box appears, soliciting the license code for the 

specific combination of configured XPC-L servers. The license code is available 

on a worksheet provided by Unisys; Appendix B, “Example XPC-L Server PCI 

Locations Charts and Worksheets“ shows example worksheets. 

The dialog box validates the format of the license code. The license code is 

further verified during the XPC-L initialization process following a start XPC-L 

command. If the verification check fails, the XPC-L will not initialize correctly and 

you will have to reinstall the software. 

b. If XPC-L Control finds that the service is already installed on the selected server, 

it skips the solicitation of a user name and password. 

If the XPC-L service was not previously installed, the User name window 

appears. Enter the user name and password that was set up for the XPC-L 

service on the selected server and on the XPC-L Control Workstation (see 

“2.2.2 Preparing to Install XPC-L Software“). Click OK. 

XPC-L Control then copies the XPC-L executable and DLLs to the XPC-L Share 

folder on that server and automatically creates the XPC-L service on that server. 

You can observe the results in the Log window. 

Once this step has been successfully completed, the state of the service in the 

Select Server pane is updated with Stopped. 

Repeat step 3 for the secondary server after selecting it by clicking its name in the 

Select Server pane (Figure 2–3). 

2–36 6885 3522–003


4. You have now completed installing the XPC-L Server software on the active XPC-L 

Control Workstation. Unisys recommends that you copy the most current 

configuration and XPC-L Control.ini files to backup media so that they can be 

loaded before starting XPC-L Control on a newly installed XPC-L Control Workstation 

and on any backup XPC-L Control Workstations you have. 

Perform the following steps to create a backup of these files: 

a. Insert writeable media into the DVD drive on the currently active XPC-L Control 

Workstation. 

b. Close any window that pops up upon inserting the blank media into the drive. 

c. Open an instance of Windows Explorer. 

d. The XPC-L Control.ini file (also referred to as the state file) is located in 

C:\XPC-L Control.ini. 

e. Copy C:\XPC-L Control.ini to the backup media. 

f. Copy the XPC-L configuration file (the default file name is ConfigFile.txt) from 

its location to the backup media. 

g. With the DVD drive highlighted, click Write these Files to CD on the File 

menu in the upper left corner of Windows Explorer. 

h. Remove the media, label it “XPC-L Control.ini (‘State file’) & Configuration file 

backup,“ and put the date on it. 

i. Insert the media back into the DVD and verify the files are present. 

j. Remove the media and store it for safe keeping. 

k. Close Windows Explorer. 

5. Now you need to install the XPC-L server software from all of your backup XPC-L 

Control Workstations so the XPC-L Control.ini file on the backup workstation has 

all the required information (such as the License code) in it. You also want to make 

sure you have the current configuration file that was saved in step 4 copied to all of 

the backup XPC-L Control Workstations. 

a. On the active XPC-L Control Workstation click Exit on the File menu to close 

out the active XPC-L Control Workstation. 

b. Start XPC-L Control on the backup XPC-L Control Workstation. 

An XPC-L Control alert message says that the XPC-L servers were being 

controlled by the other workstation and that you need to load a configuration file. 

c. Click OK. 

d. In XPC-L Control, click Open Config File on the File menu, browse to the 

config.txt file for this system, and click Open. 

e. Repeat Step 3 for any other backup XPC-L Control Workstations. 

6885 3522–003 2–37


2.2.5. Installing XPC-L Host Software 

This section describes 

• Installing required Exec features 

• Modifying Operations Sentinel message text for the site 

2.2.5.1. Installing Exec Features 

The XPCEXEC separately installed Exec feature is required and is ordered separately. 

Use standard SOLAR installation procedures to install XPCEXEC. Then perform a system 

generation (this creates a NEWMASTER tape, a boot tape, and an updated source 

symbolics file). 

You will also have ordered one additional Exec feature or feature grouping: 

• Multi-Host File Sharing (MHFS) 

• Partitioned Applications (PA) 

• Extended Transaction Capacity (XTC) 

That feature or feature grouping is installed at the same time as the XPCEXEC feature. 

Refer to the following documents for more information: 

• 2200 XP Systems PMOG 

• Exec Software Installation and Configuration Guide, 12.0 

• Extended Transaction Capacity Planning, Migration and Operations Guide 

• Partitioned Applications Planning, Installation, and Operations Guide 

• OS 2200 Software Products Installation Guide 

• Multi-Host File Sharing (MHFS) Planning, Installation, and Operations Guide 

Subsection “3.3.1 Using SCMS for Dorado Series Host Configuration“ describes how to 

use SCMS to configure hosts to use the XPC-L. 

2.2.5.2. Operations Sentinel Message Text 

Operations Sentinel is an optional separately packaged feature. If you have Operations 

Sentinel on your hosts, this section describes how to modify and how to print the 

Operations Sentinel message text. 

2–38 6885 3522–003


Several read and reply messages related to the XPC-L inform the operator that a 

potentially serious situation exists. Some of these messages are displayed during a 

recovery boot and deal with a mismatch between the expected configuration and the 

actual configuration. The mismatch can be due to hardware reasons such as loss of the 

last available path to the XPC-L, inadvertently taking down the last path to the XPC-L, or 

operational errors such as using the wrong partition profile (or operations database, ODB, 

depending on your platform). During normal operation of the system, these messages 

report serious situations with an XPC-L server or XPC-L Control Workstation. 

To assist the operator, Operations Sentinel includes a sample Autoaction Message 

System (AMS) database for the XPC-L messages in this category. When AMS 

recognizes one of these messages, the resulting actions append a highlighted message 

to the read and reply message that is displayed on the host console. The appended 

message advises the operator to go to the Operations Sentinel console for more detailed 

information. The automated actions also generate an Operations Sentinel alert. 

The operator can display the detailed information in the Operations Sentinel Console 

Alert Details pane. 

Operations Sentinel Message Text Format 

All of the Operations Sentinel messages related to the XPC-L have the same format. 

Each message consists of six parts: 

• FILE 

The number (name) of the text file that contains this message. This field also 

contains other control information. Each message in the AMS database related to 

the XPC-L has a unique Operations Sentinel text file associated with it. This is the file 

name to use if you modify the contents of the Operations Sentinel text file. 

• MESSAGE 

This is the Exec console message that generated the Operations Sentinel alert. The 

message is preceded by a line in parentheses that contains the label of the message 

as it is found within the Exec source code. 

• CONTACT 

This contains the name of the person that the operator should contact if this 

message is displayed. This field is initially set to Systems Analyst or Customer 

Service Engineer. You can change this field to contain information that is more 

meaningful for your site. 

• DESCRIPTION 

This explains the source and effect of the XPC-L exception condition. This field is 

intended to serve as an easily understandable explanation of the background of the 

XPC-L exception, as well as an overview of the effect. 

6885 3522–003 2–39


• ACTION 

This provides specific actions the operator can take to resolve the XPC-L exception. 

In general, the host console message that generated this alert must not be 

answered directly by an operator without first contacting the individual indicated in 

the CONTACT field. 

More than one action might be provided for consideration. The correct action 

depends on your site's activities, requirements, or on other matters. You can modify 

the actions listed, add more actions, or entirely replace the actions with your own 

actions. 

• GLOSSARY 

This defines any technical terms that may be displayed in the host console message 

that generated this alert. 

Modifying Operations Sentinel Message Text 

As part of the XP system planning process, review the text of the Operations Sentinel 

messages related to the XPC-L and consider filling in the CONTACT field. It may be 

necessary to add to or modify the ACTION field if there are unique procedures for your 

site. 

The message files are ASCII text files that can be found in the XP C directory under the 

help text directory for Operations Sentinel. By default, the help text directory is defined 

as sp_data_directory/help/locale, where sp_data_directory is the Operations 

Sentinel data directory and locale is determined from the LANG environment variable; 

locale is C by default. For example, /var/opt/spo/help/C/XPC is the location of the 

message files when the default location for the Operations Sentinel data directory is 

selected during Operations Sentinel installation. 

Printing Operations Sentinel Message Text 

The ACTION field can be lengthy. You might want to consider having a printed copy of all 

of the text files related to the XPC-L available for use by the operator. Using a printed 

copy might be easier than scrolling through several screens of details. To print a copy of 

one or more of the message files, use lp [-d dest] file (dest is the print queue and 

file is the XPC-L message file). Consult the UNIX man pages or your local UNIX 

specialist if you have trouble printing. 

You can also print the Alert Details window from Operations Sentinel Console. 

2–40 6885 3522–003

Section 3 

Configuration 

The XPC-L product can be operated in one of two modes, either redundant mode (which 

requires two XPC-L servers) or non-redundant mode (which uses a single XPC-L server). 

In redundant mode, one server is designated at run time to assume the role of master 

and the other server is designated as the “slave.“ In the non-redundant mode, the single 

server assumes the role of the master XPC-L. The assignment of these roles is provided 

by XPC-L Control when the XPC-L servers request a copy of the configuration file from 

XPC-L Control. 

This section describes how to configure: 

• XPC-L Control Workstation hardware (see “3.1 Configuring XPC-L Control“) 

• XPC-L Server hardware (see “3.2 Configuring XPC-L Servers“) 

• Hosts to recognize the XPC-L hardware (see “3.3 Configuring Hosts“) 

A configuration file describes the connections and relationships among the XPC-L 

Control Workstations, XPC-L servers, and hosts. Figure 1–4 shows an overview of the 

XPC-L system components and connections. Subsection “3.4 Configuration File“ 

describes the configuration file. 

3.1. Configuring XPC-L Control 

The XPC-L Control Workstation configures and controls the XPC-L servers. It is an Intel 

based workstation running Windows XP Professional. The XPC-L Control Workstation is 

connected to the XPC-L servers through a private Ethernet network. Unisys provides the 

XPC-L Control Workstation, including it with the XPC-L hardware. The Unisys 

manufacturing facility does not preconfigure the XPC-L Control Workstation for the site 

(Ethernet addresses and so on). Preconfiguration is performed during initial setup. 

6885 3522–003 3–1


3.2. Configuring XPC-L Servers 

Use the XPC-L Control Workstation to configure and control the XPC-L servers, and not 

the Service Processor console connected to the XPC-L servers. The Service Processor 

console is the interface for Dorado Series server hardware functions in the XPC-L 

servers. 

While configuration of XPC-L servers involves selecting the server that is to function as 

the “master,“ such initial configuration of the XPC-L servers is not necessary. 

The first XPC-L server specified in the XPC-L Control State file is assumed to be the 

primary server and is automatically started as the “master,“ followed by the secondary 

platform starting as the “slave.“ 

3.3. Configuring Hosts 

Use SCMS to configure the hosts for use with the XPC-L product. 

In SCMS, define each connection to a VI card as an XIIP. Remember the following rules 

regarding VI card configuration: 

• The PDB has information about connection between the VI channel and the XPC-L 

server. 

• The VI channel must be registered in the PDB. 

• The VI channel module has only one upward configurable interface to an SCIOP. 

• The VI channel is configured as a standard channel I/O processor (SCIOP) channel of 

a PCIOP-K (in Dorado 100 Series servers or Dorado 200 Series servers) or PCIOP-D 

(in Dorado 300 Series servers), or PCIOP-E (in Dorado 700 Series servers) module. 

• The equipment mnemonic of the VI channel is VICHN. 

• The equipment class of the VI channel is 3 (channel module). 

• Each VI channel module has a downward interface to an XPC L server. 

Note: SCMS II is available to create partition profiles for Dorado Series servers. Check 

with your Unisys representative for more information. 

The following table compares the names and mnemonics used by SCMS and by 

SCMS II. Note that mnemonics are defined by the Exec and are the same for SCMS and 

SCMS II. 

SCMS Name SCMS Mnemonic SCMS II Name SCMS II Mnemonic 

IOPMYR SCIOP XIOP SCIOP 

CH-VI VICHN VICHN VICHN 

IOPM-XIIP XIIP DATA-MOVER XIIP 

3–2 6885 3522–003

Configuration Restrictions 

Restrictions are as follows: 


• DataMovers and VI channel modules can be simultaneously configured, but cannot 

be simultaneously included in the partition profile. (DataMovers are components 

used with XPC systems.) 

• Each PCIOP can have only one VI channel module. 

• The maximum number of direct connect host VI channels is 64. 

• The maximum number of direct connect host VI channels on an XPC-L server is 16. 

3.3.1. Using SCMS for Dorado Series Host Configuration 

Adding New IOP Channels for an XPC-L to an Existing OS 2200 System 

Partition Profile (or Operations Database) 

1. Start with a copied and unlocked system. 

2. In SCMS, go to Inventory/Modify/Comprehensive page, find the power domain 

(PWRD) in which you will be adding or changing the IOPs and press Enter. 

3. Select Features and remove any existing IOPM-XIIP (XPC I/O Interface Processor). 

4. If necessary, remove any IOP that is not needed or is being changed to the new IOP 

style for the XPC-L. 

5. Add one or more IOPMYRs (Standard Channel I/O); place the new IOP in the 

appropriate slot of the PWRD. 

6. Accept the default hardware revision level. Unless your Unisys service 

representative differs, you can leave serial number, location, and position 

blank. 

7. Accept the default of 1 CH-VI feature. 

Adding XPC-L to an OS 2200 System That Does Not Currently Have an 


1. Go to Inventory/Include/Comprehensive page. Select XPC (Extended 

Processing Complex) at the bottom of the list. 

2. Enter 1 when prompted to enter the number of XPCs. 

3. Change the name given for the XPC if you want to use something different, but use 

the same name across all hosts. 

6885 3522–003 3–3


Connecting the New IOPs and XPC-L 

1. Go to System/Connect/XPC. 

2. Place your first new IOP in the PWRD box by pressing F2 to select the CH-VI IOP 

channel (there must be no XIIP channels). 

3. If there will be more than one CH-VI IOP, tab to the next position in the PWRD box 

and enter the next IOP channel name. 

4. Press F12 when done. 

5. Update the description in System/Manage/Modify. 

When satisfied with the additions or changes to Inventory and System/Connect, 

continue by selecting System/Prepare/Verify and check for errors. Continue and 

complete the usual procedure followed to create a new partition profile (or Operations 

Database, depending on your platform) tape or diskette. 

Example references: 

• XIP4 - Standard Channel I/O (SCIOP) 

• X4CM00 - NON-BRIDGE Channel Module (CM-NONBRIDGE-S) 

• X4CH00 - Virtual Interface Channel (CH-VI) 

3.3.2. Site Configuration Management System II 

For ClearPath Plus servers, you use the SCMS II software tool in a Windows 

environment to define configurations. However, you must define each OS 2200 partition 

separately. Hence, it is not necessary to update the entire system configuration at once. 

There are also features to help you migrate from previous OS 2200 servers to ClearPath 

Plus servers. For information about installing and using SCMS II, refer to the ClearPath 

Plus Server Dorado 200, 300, 700 or 4000 Series Hardware Platform Definition 

Reference Manual. 

For more information on SCMS II refer to the Overview presentation available with the 

SCMS II Release CD/DVD. To start the presentation, execute SCMS_II_Overview.exe, 

available in the root directory of the CD/DVD. 

Note: If you use Microsoft Windows XP Service Pack 2, you might have a problem 

viewing the presentation. On selecting a topic from the Overview menu, a blank screen 

appears on Internet Explorer with a security warning at the top. This is because Internet 

Explorer considers ActiveX controls to be a potential security risk. The SCMS II Overview 

presentation is controlled by an ActiveX control. You can proceed with the SCMS II 

Overview by clicking Yes on the security warning message. 

3–4 6885 3522–003

3.4. Configuration File 


A configuration file (see “3.4.1 Configuration File Syntax“) defines the XPC-L 

configuration for the XPC-L servers, specifies the names of the XPC-L servers, which 

XPC-L server is the primary server, the connections between the servers, and so on. A 

sample configuration file is provided on the XPC-L firmware release media for both the 

Dorado 200 Series XPC-L servers and the Dorado 300 Series XPC-L servers. Refer to the 

XPC-L Server PCI Locations chart supplied with your XPC-L system as input for creating 

a configuration file. (Appendix B, “Example XPC-L Server PCI Locations Charts and 

Worksheets“ contains a sample of the chart.) 

Two default Config.txt files are included with the XPC-L Firmware CD. The Config.txt file 

for the Dorado 200 Platform is available at the root directory and the Config.txt file for 

the Dorado 300 Platform in the Dorado 300 folder. 

The configuration file contains the basic information necessary to describe the various 

connections between the XPC-L servers and connections between each XPC-L server 

and the hosts, and to verify that the two platforms have compatible connections. 

Remaining information is retrieved from the Windows system registry of the primary 

XPC-L server. 

For a redundant XPC-L configuration, there are two separate sections in a common file, 

each labeled with the Windows computer name of one of the XPC-L server platforms. 

The configuration file may contain information for components not yet installed. The 

XPC-L server verifies nonexistent components as being correct but marks them offline. 

This allows for the future addition of connections between the XPC-L servers or hosts 

without requiring a complete shutdown of the XPC-L server. For example: 

• Adding a preconfigured VI card on an XPC-L server 

• Adding a preconfigured VI card on a 2200 host such that the new VI card connects to 

an existing VI card on an XPC-L server 

Generally, you can make the following changes between an XPC-L server and host 

components in the supported XPC-L system, without having to restart the system 

completely: 

• Replace a VI card on an XPC-L server 

• Replace a VI card on an OS 2200 host 

• Swap an entire PCIOP on an OS2200 host 

• Replace an entire XPC-L server (while in the down state) or various major 

components such as a processor or IO module. The new XPC-L server must have 

the same connections as its predecessor, including the changes listed in all the 

preceding bullets. A new license code is required to account for the new XPC-L 

server. 

6885 3522–003 3–5


The configuration file syntax contains a string of data for each VI card; the format is 

keyword based. Each string has an end sentinel (a semicolon) to allow the string of data 

associated with one VI card to be placed on multiple text lines. See “3.4.2 Sample 

Configuration“ for a sample configuration file. 

Three functional categories of VI cards are installed in an XPC-L system: 

• Direct-Connect (Host) path — direct path from this VI card to a host based VI card. 

• Synchronization (Sync) path — direct path from this VI card to the peer XPC-L, 

independent of which is the master and which is the slave. 

• Crossover (Cross-Over) path — the second leg of an indirect path from a host to one 

of the XPC-L platforms; the second leg passes through the other XPC-L server. 

Note: The term “host“ always refers to one of the OS2200 platforms being served by 

the XPC-L product. Each XPC-L server has a Windows computer name, such as XPC1, 

which is used as a “node name“ in the VI configuration. You can access this information 

in this way: On the Start menu, point to Control Panel, select System, select the 

Network Identification tab, and then click the Full computer name field. 

In a non-redundant configuration, there are only host connected VI cards. In a redundant 

configuration, every host connected VI card may be associated with a crossover VI card. 

In the case in which only a single XPC-L Server is initially implemented but a second 

XPC-L Server is planned for, build a redundant configuration containing paths to the 

nonexistent XPC-L server. At startup time, the master XPC-L server detects that the 

slave does not yet exist and ignores the paths to the nonexistent XPC-L server. No errors 

are generated and no operator input is solicited. 

3.4.1. Configuration File Syntax 

The configuration file is an ASCII text file; you create it with a text editor such as 

Notepad. A sample configuration file is included with the XPC-L firmware; see “3.4.2 

Sample Configuration“ for a description of a configuration file very similar to the sample 

configuration file included with the XPC-L firmware. 

The configuration file must begin with three specific entries: 

• a Version entry containing an integer value that identifies the version of the file 

syntax 

• a RevisionNumber entry containing an integer value that identifies the revision 

number of the file 

• a ConfigurationName entry that is an arbitrary string to identify the instance of a 

configuration 

The next entry is a SystemName field that identifies an XPC-L server. 

The first XPC-L server defined in the configuration file is referred to as the “primary 

XPC-L Server.“ There may be up to 24 VI card entries following the SystemName. 

3–6 6885 3522–003


If there is a second XPC-L server, its SystemName comes next, followed by up to another 

24 VI card entries. The second XPC-L server in a file is referred to as the “secondary 

XPC-L Server.“ Note that the “primary“ and “secondary“ terms are static and do not 

convey the dynamic operational properties of master/slave for these systems. 

File entry syntax format: 

Version = n; 

RevisionNumber = n 

ConfigurationName = ccccc; 

SystemName = sssss; 

Type = ttttt, UserName = uuuuu, AssociatedUserName = aaaaa, 

PCIBridgeNumber = p, BusNumber = n, DeviceNumber = m, 

NetworkAddress = xx:xx:xx:xx:xx:xx, XIIPNumber = yy, 

PeerNodeName = ddddd, PeerUserName = eeeee, 

Description = iiiii; 

$ 

where: 

Version 

This is an integer value defined by Unisys that identifies the current version of the 

syntax for the configuration entries. This value must equal 1. 

RevisionNumber 

This is a number that indicates the current revision of the configuration file. Initially, 

this value must be set to 1. If the configuration file is updated because of a VI card 

change, the value in this field is automatically incremented by one. 

ConfigurationName 

This is an arbitrary string (excluding “,“,“;“ and “$“) to identify this instance of a 

configuration file. Its maximum length is 255 characters. 

SystemName 

This is the Windows computer name (or node name) of the XPC-L server, retrieved 

from the registry. This field can take up to 255 characters, and must not include a 

colon. 

Note: You can access this information as follows: On the Start menu, point to 

Control Panel, select System, select the Network Identification tab, and 

then click the Full computer name field. 

Type 

This indicates function of the path defined by this entry (and its peer). Values are 

Host, Sync, Cross-Over. 

6885 3522–003 3–7


UserName 

This is the user supplied name of the VI card that was specified when the VI card 

was installed. This field can take a maximum of 16 characters. (P-DC01 in 

Figure 3–1is an example of UserName.) 

AssociatedUserName 

This is the other leg of an indirect path to one of the XPC-L platforms. 

If the file entry is type = Host, then AssociatedUserName is the local endpoint of a 

crossover path. 

If the file entry is type = Cross-Over, then this is the local endpoint of a host 

connected path (see Figure 3–2). If there is no associated path, this field may still be 

included in the entry, but set it to the NULL string. For Sync paths, this field must 

not be included in the entry, as the association concept does not apply to them. The 

maximum length is 16 characters. 

PCIBridgeNumber 

This is the PCI bridge position that holds this VI card. The valid range of values is 0 

through 7. 

BusNumber 

This is the PCI bus position on the bridge that holds this VI card. 

Dorado 200 Series servers: The valid range of values is 1 through 3. 


DeviceNumber 

This is the position of this VI card on the PCI bus. 


Dorado 300 Series servers: The valid value is 1. 

NetworkAddress 

This is the unique media access control (MAC) address of this VI card, assigned by 

the manufacturer. An address has six segments separated by colons; each segment 

is an integer in the range of 0/ –FF. 

3–8 6885 3522–003

XIIPNumber 


Each host type entry must include this field and define a unique (within the file) 

integer value. Each VI card directly connected to a host is seen by the host software 

as an XIIP. All other VI card entries must not include a XIIPNumber field. The values 

used for paths in the primary platform are 0/ through 15. The values used for paths in 

the secondary platform are 24 through 39. Values 16 through 23 and 40 through 47 

are reserved for internal use only. 

PeerNodeName 

This is the Windows computer name of the other platform containing the VI card 

paired with this VI card. This field and can take up to 16 characters and must not 

include a colon. 

PeerUserName 

This is the UserName of the other platform VI card connected to this VI card. (This is 

important only for crossover paths and sync paths, where this name must match the 

name used for its peer on the other XPC-L platform.) For host paths, any name may 

be used. This field and can take up to 16 characters and must not include a colon. 

Description 

$ 

This is an optional, free format comment field to describe this VI card entry. It must 

be enclosed within quotes. Maximum length is 255 characters. 

Notes: 

This symbol indicates the end of the configuration file. 

• All the VI card names (UserName, AssociatedUserName, and PeerUserName) must be 

unique across the entire system. 

• Each VI card entry contains a variable number of fields, from a minimum of eight 

fields to a maximum of 11. The XIIPNumber field and the AssociatedUserName field 

are not always required. The Description field is never required. 

• The Version, RevisionNumber, ConfigurationName, and SystemName entries must have 

one field each. 

• All values are case insensitive. 

• UserName values are alphanumeric, from 1 to 16 characters long, and may include the 

hyphen and underscore characters. 

• An entry can contain unlimited white space and use multiple lines. 

• Each entry must end with a semicolon. 

• Each field within an entry ends with a comma, except the last. 

6885 3522–003 3–9


3.4.2. Sample Configuration 

Sample configuration files for the configuration shown in Figure 3–1 (which are valid for 

Dorado 300 Series servers and Dorado 200 Series servers) follow the figure. 

3–10 6885 3522–003

Host A 

Primary 


P-C01 

P-C03 

P-C04 

Active 


Control 

Backup 


Control 

Figure 3–1. Sample Configuration 

Host B 

Secondary 








Host C 

PCIOP3-4 

PCIOP3-3 

P-C02 

P-S01 

P-S02 

P-S03 

P-S04 

P-C05 

P-C06 

P-C07 

P-C08 

6885 3522–003 3–11 

S-C01 

S-C02 

S-C03 

S-C04 

S-S01 

S-S02 

S-S03 

S-S04 

S-C05 

S-C06 

S-C07 

S-C08 




Host D 

PCIOP4-1 

PCIOP4-2


Dorado 200 Series Server Sample Configuration File 

Version = 1; 

RevisionNumber = 1; 

ConfigurationName = 4-Host; 

SystemName = P-XPC-L; 

Description = "Pod 0, DIB 0, SubDIB 1, Slot 1 - Connects to Host A, 

PCIOP1-1", 

Type = Host, UserName = P-DC01, AssociatedUserName = P-C01, 

PciBridgeNumber = 0, BusNumber = 1, DeviceNumber = 2, 

NetworkAddress = 00:00:00:00:00:00, XIIPNumber = 0, 

PeerNodeName = HostA, PeerUserName = PCIOP1-1; 


PCIOP1-2", 





Description = "Pod 0, DIB 0, SubDIB 1, Slot 3 - Connects to Host B, 

PCIOP2-1", 




PeerNodeName = HostB, PeerUserName = PCIOP2-1; 


PCIOP2-2", 





Description = "Pod 0, DIB 0, SubDIB 1, Slot 0 - Connects to Host C, 

PCIOP3-1", 




PeerNodeName = HostC, PeerUserName = PCIOP3-1; 

3–12 6885 3522–003




PCIOP3-2", 





Description = "Pod 0, DIB 0, SubDIB 1, Slot 2 - Connects to Host D, 

PCIOP4-1", 




PeerNodeName = HostD, PeerUserName = PCIOP4-1; 


PCIOP4-2", 





Description = "Pod 2, DIB 0, SubDIB 1, Slot 1 - Connects to S-C01", 

Type = Cross-Over, UserName = P-C01, AssociatedUserName = P-DC01, 


NetworkAddress = 00:00:00:00:00:00, 

PeerNodeName = S-XPC-L, PeerUserName = S-C01; 
















6885 3522–003 3–13























Description = "Pod 2, DIB 0, SubDIB 2, Slot 1 - Connects to S-S01", 

Type = Sync, UserName = P-S01, 



PeerNodeName = S-XPC-L, PeerUserName = S-S01; 
















3–14 6885 3522–003


SystemName = S-XPC-L; 



PCIOP1-3", 

Type = Host, UserName = S-DC01, AssociatedUserName = S-C01, 





PCIOP1-4", 






PCIOP2-3", 






PCIOP2-4", 






PCIOP3-3", 






PCIOP3-4", 





6885 3522–003 3–15




PCIOP4-3", 






PCIOP4-4", 





Description = "Pod 2, DIB 0, SubDIB 1, Slot 1 - Connects to P-C01", 

Type = Cross-Over, UserName = S-C01, AssociatedUserName = S-DC01, 



PeerNodeName = P-XPC-L, PeerUserName = P-C01; 





















3–16 6885 3522–003


















Description = "Pod 2, DIB 0, SubDIB 2, Slot 1 - Connects to P-S01", 

Type = Sync, UserName = S-S01, 



PeerNodeName = P-XPC-L, PeerUserName = P-S01; 
















$ 

6885 3522–003 3–17


Notes: 

• The $ sign is an end sentinel that terminates the file search for more entries. The 

end-of-file indicator inserted by the text processor used to build the file also 

terminates the search. 

• The UserNames used in this example are designed to suggest the function of the 

card, such as DC for direct connect to a host and CO for crossover. Otherwise, there 

are no constraints other than length on the UserNames and AssociatedUserNames. 

Figure 3–2 represents the XPC-L Control function as a single workstation, whereas 

there can be an active and a backup XPC-L Control Workstation. 

The configuration file is read very early in the master and slave main initialization routine, 

and an internal configuration table is built. Each VI card in the XPC-L platforms is 

represented by a separate entry in the file. 

Crossover path entries are tied to host connected entries by a two-way linkage using the 

AssociatedUserName field. As illustrated in Figure 3–2 and its configuration file, not all 

host type VI cards are required to have an associated crossover path (DC3) and not all 

crossover type VI cards are required to have an associated host path (C06). Note this 

degrades throughput and could compromise redundancy. 


Version = 1; 


ConfigurationName = 4-Host; 

SystemName = P-XPC-L; 

Description = "Cell 0, Bus 3 - Connects to Host A, PCIOP1-1", 










Description = "Cell 0, Bus 6 - Connects to Host B, PCIOP2-1", 





3–18 6885 3522–003








Description = "Cell 2, Bus 3 - Connects to Host C, PCIOP3-1", 










Description = "Cell 2, Bus 6 - Connects to Host D, PCIOP4-1", 










Description = "Cell 0, Bus 4 - Connects to S-C01", 















6885 3522–003 3–19




























Description = "Cell 0, Bus 5 - Connects to S-S01", 















3–20 6885 3522–003







SystemName = S-XPC-L; 
































6885 3522–003 3–21













Description = "Cell 0, Bus 4 - Connects to P-C01", 






























3–22 6885 3522–003













Description = "Cell 0, Bus 5 - Connects to P-S01", 



















PerNodeName = P-XPC-L, PeerUserName = P-S04; 

$ 

6885 3522–003 3–23


Figure 3–2 shows a sample configuration where not all VI cards have associated peers or 

connections. Such a configuration works with degraded performance and compromised 

redundancy. A sample configuration file for a Dorado 200 Series server follows the 

figure. 

DC1 

Host 1 

Figure 3–2. Sample Configuration—Degraded 

Host 2 

DC2 DC3 DC4 DC5 

CO1 

CO2 

XPC-L 1 XPC-L 2 


3–24 6885 3522–003 

CO4 

CO5 

CO3 CO6 

S1 

S2

Dorado 200 Series Server Configuration File (Degraded) 

Version = 1; 


ConfigurationName = Example-06-09-04; 

SystemName = XPC1; 

Type = Host, UserName = DC1, AssociatedUserName = CO3, 

PCIBridgeNumber = 0, BusNumber = 1, DeviceNumber = 1, 

NetworkAddress = 00:90:FA:00:3A:15, XIIPNumber = 1, 

PeerNodeName = Host1, PeerUserName = H1-1, 

Description = "Special cable used for this path."; 



NetworkAddress = 00:90:FA:00:3A:22, XIIPNumber = 2, 

PeerNodeName = Host1, PeerUserName = H1-2; 

Type = Host, UserName = DC3, AssociatedUserName = "", 


NetworkAddress = 00:90:FA:00:3C:2F, XIIPNumber = 3, 

PeerNodeName = Host2, PeerUserName = H2-1, 

Description = "Testing non-association case here"; 

Type = Cross-Over, UserName = CO1, AssociatedUserName = "", 


NetworkAddress = 00:90:FA:00:5A:07, 

PeerNodeName = XPC2, PeerUserName = CO4; 

Type = Cross-Over, UserName = CO2, AssociatedUserName = DC2, 


NetworkAddress = 00:90:FA:00:39:3E, 




NetworkAddress = 00:90:FA:00:72:01, 


Type = Sync, UserName = S1, 


NetworkAddress = 00:90:FA:00:5E:11, 

PeerNodeName = XPC2, PeerUserName = S2; 


6885 3522–003 3–25


SystemName = XPC2; 



NetworkAddress = 00:90:FA:00:22:44, XIIPNumber = 24, 




NetworkAddress = 00:90:FA:00:CA:41, XIIPNumber = 25, 










Type = Cross-Over, UserName = CO6, AssociatedUserName = "", 


NetworkAddress = 00:90:FA:00:2D:67, 




NetworkAddress = 00:90:FA:00:19:0D, 


$ 



NetworkAddress = 00:90:FA:00:19:0D, 


$ 

3–26 6885 3522–003

3.4.3. Generating a Configuration File 


This section describes the general procedure for creating a configuration file for use with 

the XPC-L at your site. The following information must be available before beginning with 

this step: 

• ClearPath Plus Server Dorado 300 Series Technical Overview (Dorado 300 Series 

servers) or ClearPath Plus Server Dorado Series Technical Overview (Dorado 200 

Series servers) 

• The names of all the PCIOPs and corresponding VI channels (XIIPs) for each host 

connected to the XPC-L 

• The MAC addresses and their corresponding PCI bus locations for each VI card in the 

XPC-L servers 

• An online version of either a previous configuration file or the sample configuration 

file (appropriate for your XPC-L Server hardware) provided with the XPC-L release 

media 

If you are creating a configuration file for the first time, carefully read the information in 

“3.4 Configuration File“ and “3.4.1 Configuration File Syntax.“ A diagram showing the 

hosts, XPC-L servers, and which VI cards are connected to each other could prove a 

useful reference. You also need to possess a working knowledge of how to use a 

Windows text editor (such as Notepad). 

A safe way initially, is to begin with a known good configuration file, modifying it with the 

changes appropriate for your specific XPC-L configuration. To create a configuration file 

from scratch, perform the following steps. Skip these if you are only making minor 

changes to an existing configuration file (for example, adding an additional host path). 

1. Copy the sample configuration file from the root of the installation CD-ROM into a 

new file. For example, 

copy z:\Dorado 300\ConfigFile.txt to c:\ConfigFile.txt 

Do not directly modify the starting configuration file- you might need to start over if 

you make an error. 

2. Open the new configuration file in a Windows text editor. 

If you do not plan to add additional hosts in the future, go to step 3. Otherwise, go to 

step 5. 

3. Remove the host and crossover path entries for any hosts that do not exist (refer to 

“3.4.1 Configuration File Syntax“ for how to identify which entries are for host and 

crossover paths). Note that the number of hosts you have connected to the XPC-L 

may eliminate the need to make any changes. 

If you do not plan to add additional XIIPs to the hosts in the future, go to step 4. 

Otherwise, go to step 5. 

6885 3522–003 3–27


3. Remove the host and crossover path entries for any paths (XIIPs) that do not exist 

for the hosts that are connected to the XPC-L. Note that the number of XIIPs each 

host has may eliminate the need to make any changes. 

If you do not plan to add additional synchronization paths in the future, go to step 5. 

Otherwise, go to step 6. 

4. Remove any synchronization path entries for any sync paths that do not exist 

between the master and slave XPC-L servers (refer to “3.4.1 Configuration File 

Syntax“ for information on how to identify which entries are for sync paths). Note 

that the number of sync paths used may eliminate the need to make any changes. 

5. Change the existing ConfigurationName value to a value appropriate for your site 

(this is an optional, but recommended step). 

6. Change all occurrences of the primary XPC-L Server SystemName value from the name 

it currently is to the SystemName value for your primary XPC-L server (refer to “3.4.1 

Configuration File Syntax“ for information on how to identify the XPC-L server name 

). This name is not just any character string; it must match the Windows computer 

name for the primary XPC-L server. 

Note: You can access this information as follows: On the Start menu, point to 

Control Panel, select System, select the Network Identification tab, and 

then click the Full computer name field. 

7. If you are not using a redundant XPC-L configuration (that is, an XPC-L with both a 

primary and secondary servers) and do not plan to do so in the future, perform step 

9; otherwise, skip step 9 and proceed directly to step 10. 

8. Remove (delete) all information in the configuration file associated with the 

secondary XPC-L server. Continue with step 11. 

9. Change all occurrences of the secondary XPC-L server SystemName value from the 

name it currently has to the SystemName value of your secondary XPC-L server (refer 

to “3.4.1 Configuration File Syntax“ for information on how to identify what the 

XPC-L server name). Note that this name is not just any character string; it must 

match the Windows computer name for the secondary XPC-L server. 

10. Update the Description value for each host, crossover, and sync path entry so it 

reflects the location and connection information for your site (this is an optional, but 

recommended step). 

11. Update the PciBridgeNumber, BusNumber, and DeviceNumber values for each host, 

crossover, and sync path entry so it reflects the VI card location for your site (see 

Table 3–1). Refer to the Dorado 300 Series Technical Overview (Dorado 300 Series) 

or Dorado Series Technical Overview (Dorado 200 Series servers) document for how 

to identify where the VI cards are located in your XPC-L Servers. Alternatively, if you 

have a basic working knowledge of the major components in a Dorado Series server, 

refer to the PCI bus information that follows at the end of this section. Note that the 

hardware PCI card locations you have in the XPC-L Servers can eliminate the need to 

make any changes. 

12. Update each NetworkAddress value from the value it currently is to the 

NetworkAddress value associated with the VI cards in your servers. Each VI card 

must be labeled with its unique MAC address. 

3–28 6885 3522–003

13. Save the updated configuration file to the place where it will be used during 

installation (refer to Section 2.2.2, “Preparing to Install XPC-L Software“). 

This completes the required steps necessary to generate your configuration file. 

Additional optional configuration file changes follow: 


• UserName values can be changed. Note that this may require changes to 

AssociatedUserName for host and crossover path entries. It may also require 

changes for PeerUserName for sync path entries. 

• XIIPNumber values can be changed for host path entries. 

• PeerNodeName values can be changed for host path entries. 

• PeerUserName values can be changed. Note that this may require changes to 

UserName for host and crossover path entries. 

The following is a summary of Dorado Series server PCI card locations and how to 

translate them to PciBridgeNumber, BusNumber, and DeviceNumber values: 

Dorado Series 200 Servers 

The hardware location of each individual PCI card in a Dorado 200 Series server is 

determined by the Pod, DIB, SubDIB, and slot within the SubDIB in which the card is 

placed. A way to keep track of this information is to place it in the Description for each 

entry in the configuration file (for example, using PodNumber, DIBNumber, SubDIBNumber, 

and SlotNumber). 

The following restrictions must be considered: 

• PodNumber must be 0/ , 1, 2, or 3. 

• DIBNumber must be 0/ or 1. 

• SubDIBNumber must be 1, 2, or 3 (note that VI cards will always reside in either 

SubDIB 1 or 2). 

• SlotNumber must be 0/ , 1, 2, or 3. 

6885 3522–003 3–29


To determine the PciBridgeNumber for an individual entry in the configuration file, use the 

PodNumber and DIBNumber, and then locate the corresponding PciBridgeNumber from 

Table 3–1: 

Table 3–1. Determining PciBridgeNumber 

PodNumber DIBNumber PciBridgeNumber 

0/ 0/ 0/ 

0/ 1 1 

1 0/ 2 

1 1 3 

2 0/ 4 

2 1 5 

3 0/ 6 

3 1 7 

The BusNumber for an individual entry in the configuration file is the SubDIBNumber. 

The DeviceNumber for an individual entry in the configuration file is the SlotNumber plus 

1. 

Example 

A VI card located in Pod 2, DIB 1, SubDIB 1, and Slot 3 has a PciBridgeNumber value of 5, 

BusNumber value of 1, and DeviceNumber value of 4. 

Dorado Series 300 Servers 

The hardware location of each individual PCI card in a Dorado 300 Series server is 

determined by the cell and the PCI bus in which the card is placed. A way to keep track 

of this information is to place it in the Description for each entry in the configuration file 

(for example, using CellNumber and PCIbusNumber). 

The following restrictions must be considered: 

• CellNumber must be 0/ , 1, 2, or 3. 

• PCIbusNumber must be 3, 4, 5, 6, or 7. 

The PciBridgeNumber for an individual entry in the configuration file is the CellNumber. 

The BusNumber for an individual entry in the configuration file is the PCI bus number. 

The DeviceNumber for an individual entry in the configuration file is always 1. 

3–30 6885 3522–003

Example 


A VI card located in Cell 1, PCI bus 4 has a PciBridgeNumber value of 1, BusNumber value 

of 4, and DeviceNumber value of 1. 

6885 3522–003 3–31


3–32 6885 3522–003

Section 4 

Migration 

This section describes migration issues involved while moving from an XPC environment 

to an XPC-L environment. 

4.1. Conceptual Differences 

From a hardware perspective, the XPC-L system replaces the XPC system. The OS 2200 

Exec supports usage of either an XPC-L or an XPC system, but not both at the same 

time. 

From a functional perspective, the XPC-L system replaces the record locking function of 

the XPC system with a faster, more robust, and higher volume lock manager. The need 

for a replacement for the system level file caching function of the XPC has been 

eliminated by a combination of today’s high speed and higher bandwidth I/O channels. In 

the case where I/O channels alone do not provide I/O performance equivalent to the 

XPC, the optional “Exec I/O command queuing“ feature provides additional operating 

system modification to enhance I/O performance. 

Within the operating system, the XPC-L system (as with the XPC) continues to be used 

to store some shared system level data (for example, Unit Duplexing synchronization 

tables for shared mass storage). 

6885 3522–003 4–1


The following is a list of specific differences between the XPC and XPC-L systems: 

• File caching is automatically disabled. The following XPC caching related 

configuration variables are ignored when using the XPC-L system: 

FILE_CACHING_DEFAULT FCACHEDFLT 

SHARED_FILE_CACHING_DEFAULT SHRDFCDFLT 

CACHE_LOCAL_FIXED_MFD MFDONXPCSTD 

CACHE_SHARED_FIXED_MFD MFDONXPCSHR 

FILE_CACHE_SECURITY_FILES XCACHESECFIL 

XPC_PERIODIC_DESTAGE_LOCAL XPDLOCAL 

XPC_PERIODIC_DESTAGE_SHARED XPDSHARED 

XPC_DESTAGE_LOCAL_START XPDCLSTRT 

XPC_DESTAGE_SHARED_START XPDSHRDSTRT 

XPC_DESTAGE_LOCAL_INTERVAL XPDLCLINTV 

XPC_DESTAGE_SHARED_INTERVAL XPDSHRDINTV 

XPC_PERIODIC_DESTAGE_ON_BOOT PRDDSTBOOT 

XPC_DESTAGE_MAX_IO XPDMAXIO 

AUDIT_TRAIL_ATTRIBUTE_FOR_XR 

• The XPC-L system supports interhost messaging and database locking in a manner 

compatible with that of the XPC system. 

− Extended I/O processors (XIIP)/DataMovers are no longer supported. The logic 

provided by them is now provided by the PCIOP (a PCIOP-K, PCIOP-D, or a 

PCIOP-E) and associated virtual interface (VI) channel in the host. 

− Host Interface Adapters (HIA) are no longer supported. The logic provided by an 

HIA is provided by the network card implementing the Virtual Interface (VI) 

channel between the host and the XPC-L system. 

• The interface between the host and the XPC-L server is seen as an XIIP by SCMS 

and in the PDB. As already mentioned, the XIIP is composed of a PCIOP (named 

XIPnn) and a VI channel (named XnnCnn). 

4–2 6885 3522–003


• The Exec keyins for controlling an XIIP now control the interface between the host 

and the XPC-L, although the keyins still refer to the interface as an XIIP. As already 

mentioned, the XIIP is composed of a PCIOP (named XIPnn) and a VI channel 

(named XnnCnn). 

• A personal computer called XPC-L Control Workstation controls the interface 

between the host and the XPC-L system, as well as other XPC-L functions. 

Note: The XPC-L Control Workstation cannot DN a 2200 host IOP. 

• The XPC system has a special SCF console, whereas the XPC-L system has the 

XPC-L Control Workstation and the CMP Service Processor interfaces. 

• The XPC-L Control Workstation is used to configure and manage the XPC-L service. 

• The XPC-L system never contains the only valid copy of user data. As a result, the 

XPC-L does not provide a feature equivalent to the DataSave Disk feature of the 

XPC. 

6885 3522–003 4–3


4.2. Crossbooting 

The XPC-L system is designed to be functionally compatible with the predecessor 

external locking engines, the RLP and XPC systems. From a programming perspective, it 

is functionally equivalent to the predecessor systems. There is no need for programs, 

associated runstreams, and Exec Control Language statements to be modified in any 

way when the XPC-L is introduced. 

The XPC supported file caching, referred to as Virtual Storage Management (VSM) and 

Multiple Independent Hosts (MIH), as well as Distributed Systems Management (DSM) 

capabilities, where DSM encompasses file caching as also data locking and inter-system 

communications capabilities. The XPC-L provides fully compatible support of the DSM 

locking and intersystem communications capabilities offered in the XPC. 

The major result of migration to the XPC-L is the lack of file caching capabilities. Before 

the XPC-L system can be put into use, all aspects of the predecessor XPC file caching 

functionality must be removed from the existing system. This means that in systems 

with an XPC, all cached data must be destaged. A new PDB must be created with the 

new XPC-L system configured and the old XPC system removed from the configuration. 

This section documents the migration process from an XPC system, using the 

Distributed Systems Manager (DSM) environment, to the XPC-L system. The complexity 

of the migration depends on how the XPC system is being used. When the XPC system 

is being used for both record locking and system level file caching, file caching must be 

stopped and all remnants of its use removed from the system. This is accomplished by 

removing data from the cache and by removing the XPC identifier from the MFD (Refer 

to “4.2.1 Discontinuing Use of XPC File Caching“). After these tasks are completed, the 

XPC-L can be added to the 2200 host environment (Refer to “4.2.2 Adding XPC-L to the 

OS 2200 Environment“). 

XPC environments using Virtual Storage Manager (VSM) or Multiple Independent Hosts 

(MIH) only provide system level file caching of local mass storage. As a result, migration 

to XPC-L in these environments is not meaningful since XPC-L does not provide file 

caching for any mass storage. If you are moving from a single host environment to a 

multi-host environment and have an XPC system in use in the single host environment, 

remove the XPC from the environment following the procedures in the 2200 XP Systems 

PMOG. Then install and configure the XPC-L as a new device as described in Section 2, 

“Installation“ and Section 3, “Configuration.“ 

4–4 6885 3522–003

4.2.1. Discontinuing Use of XPC File Caching 


The following migration steps remove all aspects of system level file caching for both 

local and shared files from the system. Discontinuing use of XPC file caching requires 

advance planning and involves two major steps. 

1. Remove data from the XPC system. 

If the system is migrated to the XPC-L environment without destaging XPC cached 

data and the file recovery or initialization process detects a disk that was globally 

cached, it displays messages to prevent the loss of cached data in the same manner 

as when the XPC is initialized. 

2. Remove the XPC identifier from the MFD. 

The MFD directory items contain an XPC identifier that is unique to each XPC. This 

identifier must be removed from the directory items for each cached file to avoid any 

fallback or future recovery problems. 

In the following sections, there are references to both, the XPC and the XPC-L. Your 

PDB will have only one XPC configured. Thus, the xpc_name in the example console 

messages is the same XPC name for the XPC and the XPC-L. The XPC-L must be in an 

initialized state before beginning with this procedure. 

4.2.1.1. Overview 

Caution 

Performing steps incorrectly or skipping steps could result in a loss of data. 

Files in the shared and local MFDs contain an XPC identifier and the caching specification 

for each file. The XPC identifier describes whether a file has ever been cached in the 

XPC. This value is either zero or an internal XPC serial number. A nonzero value indicates 

that data for this file potentially resides in the XPC system. The DN,XCACHE xpc_name 

keyin and the DN xpc_name keyin do not remove the XPC identifier from the MFD main 

item extension for files that are cached in the XPC. You must perform a file recovery and 

long pack registration to remove this information. 

The caching specification for a cataloged file is set by several mechanisms. A cataloged 

file is initially set to use the system default. The file may be changed from SYS_DEFAULT 

to DO_CACHE, DO_NOT_CACHE, or XRP with the FURPUR CHG,F command, the FREIPS UPDIR 

command, or a user program using the FILECACHE$ call interface. 

Note: XRF is an XPC resident file; XRP is a FURPUR and FREIPS option that sets a 

file’s XPC caching specification to make it a permanent XRF. 

6885 3522–003 4–5


You can alternate between the two procedures described in “4.2.1.3 Removing Data 

from the XPC“ and “4.2.1.4 Removing the XPC Identifier from the MFD“ by breaking 

down the steps within. For example, you can handle the local files from one host, then 

the local files for another host, and then the shared files. You can also change the 

caching specifications for files in steps and continue to use the XPC for caching data. For 

example, files rarely used can be changed to DO_NOT_CACHE and critical files can be 

changed before the migration to the XPC-L. 

Both procedures must be completed before performing the procedure described in 

“4.2.2 Adding XPC-L to the OS 2200 Environment.“ 

4.2.1.2. Determining the Caching Information of a File 

You can determine which files have the XPC identifier in the MFD by using the following 

FAS select criteria commands. These files may potentially have data in the XPC system. 

For the local directory on a given host: 

@fas,lem 

list criteria= [xpc_cached=yes] ; end; 

For the shared directory: 

@fas,lem 

set directory_name:=shared; 

list criteria= [xpc_cached= yes] ; end; 

The FREIPS MAP command with no file specification can be used to provide a list of 

TIP/Exec files. 

You can determine which files have a file caching specification of DO_CACHE or XRP (for 

XRP, specify xpc_user_spec=xrp) by using the following FAS select criteria commands. 

You may want to change the caching specification for these files to SYS DEFAULT or 

DO_NOT_CACHE. 

For the local directory on a given host: 

@fas,lem 

list criteria= [xpc_user_spec=do_cache]; end; 

For the shared directory: 

@fas,lem 

set directory_name:=shared; 

list criteria= [xpc_user_spec=do_cache]; end; 

4–6 6885 3522–003

4.2.1.3. Removing Data from the XPC 

The data can be removed from the XPC system by any of the following methods. 

Removing Data for All Files 


Use the DN,XCACHE keyin to remove data from the XPC. This method removes all data 

from the XPC and no additional steps are required to remove data. This keyin must 

always be performed before removing the XPC identifier from the MFD (see “4.2.1.4. 

Removing the XPC Identifier from the MFD“). 

Note: Use the following two methods, if you want to incrementally remove data from 

the XPC for specific files. However, the above method must be used before the 

completion of the “Removing the XPC identifier from the MFD” step. 

Removing Data for All Files Using the System Default Caching 

Specification 

For local and shared files with a caching specification of SYS_DEFAULT, data is removed 

from the XPC system by changing the Exec system default caching specification to 

FALSE (which means “do not cache“) for each directory. For local caching, the 

configuration parameter is FCACHDEFAULT, and for shared caching, the configuration 

parameter is SHRDFCDFLT. Both configuration parameters must be changed on all hosts. 

The change becomes effective the next time an I/O is performed to the file or when the 

file is initially assigned. This method has the advantage of making it unnecessary to 

change individual file caching specifications. The disadvantage is requiring either an I/O 

against each file or dropping of the assign count to zero and then reassigning the file. 

Removing Data for a Specific File 

Files that are XPC cached can have one of three caching specifications associated with 

the file: DO_CACHE, XRP, or SYS_DEFAULT. You can immediately remove data from the XPC 

system for a file by changing its caching specification to DO_NOT_CACHE. 

This method has the advantage of handling all types of files (TIP, Exec, UDS, local and 

shared, fixed and removable, and so on) without requiring a forced I/O to each file. 

However, the disadvantage is that you need to locate all XPC cached files cataloged in 

the system. This method is recommended for sites that do not cache files by default and 

that have a known set of cataloged files. 

You may use the FURPUR CHG,F command, the FREIPS UPDIR command, or a user 

program using the FILECACHE$ call interface to perform this operation on each file. 

6885 3522–003 4–7


4.2.1.4. Removing the XPC Identifier from the MFD 

If XPC caching is not down, the XPC identifier in the MFD indicates that there might still 

be data in the XPC for the file. Removal of the XPC identifier as performed in this section 

will also result in the data being removed from the XPC system for the file. 

The XPC identifier can be removed from the MFD by the following methods, described 

in the following paragraphs: 

• Removing the XPC Identifier for a specific file 

• Removing the XPC Identifier from a file by performing a Recovery Boot 

• Removing the XPC Identifier from files by performing an I/O to the file 

You can use any of those methods for fixed files. 

For removable pack files, the system determines the type of pack registration needed 

(short or long) during recovery. The system always chooses the minimum needed to 

recover the files. Thus the method using a recovery boot is unlikely to clear the XPC 

identifier in the removable pack directory. The XPC identifier for removable pack files 

should be cleared using the method for a specific file or by performing an I/O to the file. 

Removing the XPC Identifier for a Specific File 

For files with a caching specification of DO_CACHE, XRP, or SYS_DEFAULT, the XPC identifier 

in the MFD for the file can immediately be cleared by changing the file’s caching 

specification to DO_NOT_CACHE. 

This method has the advantage of handling all types of files (TIP, Exec, UDS, 

local/shared, fixed/removable, and so on) without requiring a forced I/O to each file. It 

has the disadvantage of requiring you to locate all XPC cached files cataloged in the 

system. This method is recommended for sites that do not cache files by default and 

that have a known set of cataloged files. 

You can use the FURPUR CHG, F command, the FREIPS UPDIR command, or a user 

program using the FILECACHE$ call interface to perform this operation on each file. 

Removing the XPC Identifier from a File by Performing a Recovery Boot 

Issue a DN,XCACHE keyin. When caching is disabled, perform a recovery boot. For shared 

files, all hosts must be taken down. Then one host can perform the shared recovery. 

This will remove the XPC identifier in the MFD from files with a caching specification of 

DO_CACHE, XRP, or SYSTEM_DEFAULT. 

4–8 6885 3522–003


Removing the XPC Identifier from Files by Performing an I/O to the File 

If a file has a file caching specification of SYS_DEFAULT and the Exec system default is set 

to TRUE (which means “do not cache“), you can clear the XPC identifier for a file by 

changing the system default to FALSE (which means “do not cache“). The change 

becomes effective the next time an I/O is performed to the file, the next time the file’s 

directory is recovered, or the next time the file’s removable disk pack is registered with a 

long pack registration. This method has the advantage of making it unnecessary to 

change individual file caching specifications. It has the disadvantage of requiring an I/O 

against each file or rebooting the system (a shared directory recovery, not a 

reemployment). 

This method is recommended for sites that cache files by default. 

Change the Exec system default caching specification to FALSE (which means do not 

cache) for each directory. The configuration parameter for local caching is FCACHDEFAULT 

and for shared caching, SHRDFCDFLT. Both configuration parameters must be changed on 

all hosts. 

If XPC caching is enabled, assign each file that is using the caching specification of 

SYS_DEFAULT and then perform one I/O to the file. TIP/Exec files can be left assigned to 

TIP and you can issue the FREIPS PRINT command to perform one I/O to each of these 

files. The I/O process determines that the file must be taken out of file caching and 

clears the XPC identifier from the MFD directory items for the file. 

If XPC caching is disabled, then assign and free each file that is using the caching 

specification of SYS_DEFAULT. The assign process determines that the file must be taken 

out of file caching and makes the update to the directory items for the file. 

Since it is normally not practical to "TPFREE" and "TPASG" TIP/Exec files when application 

programs are accessing database files, an alternative method is available. XPC caching 

can be temporarily enabled with an UP,XCACHE keyin, which causes the XPC identifiers to 

be cleared for all TIP/Exec files. XPC caching can then be returned to a disabled state 

with a DN,XCACHE keyin. 

4.2.2. Adding XPC-L to the OS 2200 Environment 

All steps in “4.2.1 Discontinuing Use of XPC File Caching“ must have been completed 

before this is done. 

OS 2200 does not support simultaneous configuration and use of XPC and XPC-L. From 

a hardware perspective, both an XPC system and an XPC-L system can be connected to 

an OS 2200 host. This allows for migration preparation and for moving to and from an 

XPC-L in a test environment. 

From an operating system perspective, only one type of XPC can be configured at a 

time. As part of the migration to XPC-L, a partition definition must be created that 

removes the XPC and adds the XPC-L. 

When you have completed all steps for discontinuing use of XPC file caching, installed 

and connected the XPC-L system, and created a partition definition that configures the 

XPC-L, then you are ready to starting using the XPC-L system. 

6885 3522–003 4–9


The procedure that you use to begin use of the XPC-L system depends on whether you 

are using the Unit Duplexing feature of the OS 2200 Exec to duplex any of your shared 

mass storage devices. If none of your shared mass storage devices are duplexed, then 

use “4.2.2.1 Migrating Without Duplexing.“ If you have duplexed shared mass storage 

devices and it is acceptable for the duplex associations to be terminated as part of the 

migration process, then use “4.2.2.1 Migrating Without Duplexing.“ In all other cases, 

use “4.2.2.2 Migrating to XPC-L with Shared Unit Duplexing.“ 

4.2.2.1. Migrating Without Duplexing 

At this point, all steps required to prepare for the introduction of the XPC-L into the 

OS 2200 environment have been completed. None of the shared mass storage devices 

are duplexed, or if they are, it is acceptable for the duplex associations to be terminated 

as part of the migration process. Perform the following steps to begin use of the XPC-L 

system: 

1. Perform an orderly shutdown of all OS 2200 hosts. 

2. Reboot each system using the PDB that has the XPC-L defined. At MODIFY 

CONFIG, enter the keyin: UP,MHM xpc_name, where xpc_name is the XPC-L system. 

The following messages are displayed: 

The HOST ID for this HOST is host-id 

xpc_name UP MHM 

Here, host-id is the host-id from the PDB and xpc_name is the XPC-L system. 

It is not necessary to perform an MH,RC keyin during migration. 

4.2.2.2. Migrating to XPC-L with Shared Unit Duplexing 

When any shared mass storage device is duplexed using the Unit Duplexing (UDUPLEX) 

Exec feature, the Exec maintains I/O synchronization tables for those devices. The 

shared unit duplex synchronization tables reside in the XPC and provide a record of I/Os 

in progress to duplexed shared devices. The synchronization tables are used during a 

recovery from any host stop to synchronize I/O that was in progress at the time of the 

stop. 

The process of migrating from XPC to XPC-L requires that all hosts be stopped, the 

configuration be switched from using the XPC to using the XPC-L, and then all hosts be 

rebooted. If shared unit duplex synchronization tables existed in the XPC at the time all 

hosts were stopped, they cannot be accessed during the recovery boot with the XPC-L 

in the configuration. 

This results in the shared unit duplex associations being broken when the first host 

reenters MHFS. Shared unit duplex associations can be restored by performing UD 

keyins, but I/O performance may be degraded while the duplex images are restored. 

The following paragraphs describe a procedure that avoids breaking shared unit duplex 

associations during the migration process. 

4–10 6885 3522–003


Stop all hosts but one and bring MHFS down gracefully on the one remaining host. 

Bringing MHFS down gracefully means only one host is up in MHFS, all shared files have 

been freed, and all shared I/Os have been completed. When the first host recover boots 

with the XPC-L, shared unit duplex associations do not need to be broken because there 

are no active synchronization entries to recover. The following procedure provides the 

method to retain shared unit duplex associations. 

1. Bring down file caching on all hosts. 

2. Take all hosts down but one. 

3. Perform an MH,DN keyin on the remaining host after “Modify Config.“ You might 

need to prevent shared files from being assigned by placing audit trails in a deferred 

state and/or leaving the TIP messages outstanding. 

If you have audit trail files on shared mass storage, reboot with jump key 1 set. At 

Modify Config, perform an AT ALL NR keyin to put all configured audit trails in a 

deferred state. 

To prevent TIP files being assigned on shared mass storage, reboot with jump key 7 

and leave the TIP messages outstanding or answer No to TIP. 

This host automatically processes its own as well as the other hosts’ unit duplex 

synchronization tables. When the MH,DN keyin is performed, the MH,DN processing 

ensures that all shared files are freed and all shared activities are completed before 

the host MHFS status is put in a down state. This means that a point has been 

reached where there are no shared I/O’s outstanding. A “graceful down“ indicator is 

written to the shared system device. 

The following message is displayed when file sharing has been taken down: 

mh,dn 

1 SHARED FILE(S) ASSIGNED BY EXEC / COMMON SECTION(S) 

0 - MH,DN - SHARED ENVIRONMENT TO BE UNAVAILABLE? - YN 

0 y 

HOST A SYSTEM-ID system_id DN SESSION nnn 

4. Migrate from the XPC to the XPC-L. This is initiated by stopping the host that did the 

MH,DN keyin in step 3, switching to the new PDB for all hosts in the MHFS 

environment, and rebooting each host. 

To avoid problems, ensure your shared device status conditions (for example, UP, 

DN, SU, and RV) are correct in your new PDB. 

6885 3522–003 4–11


5. At Modify Config, use the MH,UP keyin to bring up MHFS on the first host booting 

with the XPC-L. (This does not need to be the last surviving host from step 2.) During 

the shared recovery by the first host, the shared unit duplex synchronization tables 

are acquired and initialized. Because a graceful MHFS down was performed and 

flagged in the shared DRS, shared unit duplex associations are not broken. 

Note: If an MH,IN keyin or an MH,RC keyin is performed, the shared unit duplex 

associations will be broken. This is because software is unable to determine whether 

the shared system device was switched and the validity of the graceful down flag 

indicator cannot be determined. 

The following new console message is displayed during mass storage recovery: 

The shared unit duplex synchronization table is initialized and 

shared unit duplex associations are maintained. 

6. Bring up the remaining hosts. 

Note: The preceding procedure can also be performed before initializing the XPC or 

XPC-L to prevent termination of the duplex associations during the initialization process. 

4.3. Clearing the XPC 

The migration to XPC-L includes the destaging of all data in the XPC system and the 

termination of all paths to the XPC system. 

1. Once all hosts are stopped, perform a Halt Partition (HP) at the XPC SCF. 

2. The next time the XPC is used, perform a Start Partition (SP) at the XPC SCF. 

This procedure causes the XPC to be initialized. If you fall back to the XPC from the 

XPC-L, the shared unit duplex synchronization tables that are in the XPC-L system are 

lost (unless the procedure in “Migrating to XPC-L with Shared Unit Duplexing“ under 

“4.2.2 Adding XPC-L to the OS 2200 Environment“ is followed). If the XPC was not 

initialized, the XPC shared unit duplex synchronization tables would be recovered and 

data corruption would occur because the active synchronization entries in the XPC-L 

would not be recovered and the unit duplexed pairs will no longer be identical. 

4–12 6885 3522–003

4.4. New Console Messages 


Console messages referring to the XPC that apply to the XPC-L product have not been 

changed. References to XPC should be interpreted as applying to the XPC-L and 

references to an XIIP should be interpreted as applying to the VI channel. 

The following paragraphs describe new messages for the XPC-L product. 

Loss of XPC-L Control 

When the XPC-L Control facility is lost, the host is notified and displays the following 

message: 

Critical interrupt received from xpc_name RA = maintenance required, 

Reason = XPC Control Unavailable. An internal fault has resulted in a loss 

of resiliency within xpc_name. 

0 - Answer GO to acknowledge the need for urgent maintenance. 

This message could appear for a variety of reasons. Verify that the workstation currently 

designated as the active XPC-L Control Workstation is still operational. Initiate the 

actions to switch to the backup XPC-L Control Workstation if the workstation is not 

operational. 

If the workstation currently designated as the active XPC-L Control Workstation is 

operational, verify that XPC-L Control is still running on the workstation. If XPC-L Control 

is not running, then initiate the actions to start up XPC-L Control on the workstation. 

If the workstation is operational and XPC-L Control is running, then verify again the state 

of each server by selecting the opposite server and then reselecting the original server. 

The state of each server should be either “Running as Master“ or “Running as Slave.“ 

If the state of a server cannot be determined, there is probably a network problem 

between the workstation currently designated as the active XPC-L Control Workstation 

and the servers. Initiate the actions to switch to the backup XPC-L Control Workstation. 

If the state of each server cannot be determined by the backup XPC-L Control 

Workstation, the network problem is probably not isolated to an individual workstation or 

server. Initiate the actions to restore the network to an operational condition. 

Loss of XPC-L Redundancy 

When the slave XPC-L server is lost, the host is notified and displays the following 

message: 


Reason = hardware redundancy lost. An internal fault has resulted in a loss 

of redundancy within xpc_name. Notify the Customer Engineer. 


6885 3522–003 4–13


This message normally appears when either the slave has encountered a problem or 

there are no synchronization paths operational between the master and slave. Initiate the 

actions through XPC-L Control to start the slave. 

If this fails to establish redundancy, look in the XPC-L Control log window to see if there 

is a log entry indicating that there was a problem on a synchronization path. If there is an 

indication of a problem with a synchronization path, initiate the actions to up additional 

synchronization paths and retry the actions to start the slave. 

If this fails to establish redundancy, initiate the actions to restore the synchronization 

paths to an operational condition. 

If in the original attempt to start the slave, the state of the slave server is “Unknown“ or 

“Server not found,“ then there is a problem with the server. Initiate the actions to 

restore the server to an operational condition. 

Loss of XPC-L Synchronization Path 

When the XPC-L Servers lose a synchronization path, the host is notified and displays 

the following message: 


Reason = Synchronization Path lost. An internal fault has resulted in a 

loss of resiliency within xpc_name. Notify the Customer Engineer. 


This message normally appears when an XPC-L Server synchronization path has 

encountered a problem and the host receives this message for each synchronization 

path lost. 

The XPC-L system has a maximum of four synchronization paths. When it loses the last 

synchronization path, the host gets the Exec message indicating loss of XPC-L 

redundancy. If this happens, refer to “Loss of XPC-L Redundancy“ and initiate the 

actions through XPC-L Control to bring up the failing synchronization paths. 

If this fails to establish the synchronization paths, look in the XPC-L Control log window 

to see if there is a log entry indicating where the problem was. Then refer to 

“4.1.6.2 Synchronization or Crossover path“ of Section 4, “Troubleshooting“ of the 

ClearPath Enterprise Servers Extended Processing Complex-Locking (XPC-L) System 

Operations Guide to resolve the problem. 

XIIP Configuration Error 

If the system has configured both types of host interfaces (XIIP and VI channel), the boot 

process displays the following message and stops the system: 

Two types of XIIPs are configured in PDB. 

Reload of correct PDB is required. 

Go back into SCMS and fix the configuration so only one type of XIIP (a VI) is configured 

(see Section 3.3, “Configuring Hosts“). 

4–14 6885 3522–003

Disabling the Last Path to XPC-L 


If a DN IOP results in no path being available to the XPC-L server, the following type and 

reply message is displayed: 

DN OF IOP_name will disable this host's last path to XPC_name 

Continue to DN, enter DISABLE, else CANCEL 

If you answer the message with DISABLE, the Exec continues bringing down of the IOP. 

Otherwise, the Exec aborts processing of the DN IOP keyin. 

If the host is active in MHFS, the DN IOP keyin of the last path is rejected and instead of 

the preceding message, the following message is displayed. The path is not disabled. 

DN of IOP_name requested by the operator was rejected 

because MHFS is up and XPC_name is MHM. 

IOP_name UP 

Shared Unit Duplex Associations Maintained 

The following message is displayed during the migration procedure described in “4.2.2.2 

Migrating to XPC-L with Shared Unit Duplexing“: 

The shared unit duplex synchronization table is initialized and 

shared unit duplex associations are maintained. 

This console message indicates that the shared unit duplex synchronization tables have 

been allocated and the shared unit duplex associations have been recovered. 

4.5. Changed Console Messages 

The following paragraphs describe console messages that were changed for the XPC-L 

product. 

FS,XPC 

The following messages are examples of the changed messages displayed for the 

FS,XPC keyin: 

XPCT82 UP MHM 

HOST A active I04C00 I15C00 

HOST B inactive 

HOST C inactive 

HOST D inactive 

FS,XCACHE 

The following message is an example of the changed messages displayed for the 

FS,XCACHE keyin: 

xpc_name UP MHM - THE XPC DOES NOT SUPPORT CACHING 

6885 3522–003 4–15


Downing All XIIPs at MODIFY CONFIG 

The following messages are examples of the changed messages displayed as a result of 

downing all XIIPs connected to an XPC-L system at MODIFY CONFIG: 

DN of xiip-name will disable this host's last path to xpc_name. 

This host's usage of the XPC's functional capabilities will be disabled. 

1-Proceeding with DN disables XPC functions, enter DISABLE, else CANCEL: 

No messages are displayed during file recovery. 

Exec Internal Fault Processing 

The following is an example of an Exec internal fault processing error message: 

Critical interrupt received from xpc_name 

RA = down XPC for repair, Reason = hardware redundancy lost 

Check XPC-L Control for error information. 

0-Answer GO to acknowledge error at xpc_name 

This message could appear for a variety of reasons. The RA and Reason provide the 

recommended action and the reason. 

Check XPC-L Control for additional error information and verify the state of each server 

by selecting the opposite server and then reselecting the original server. The state of 

each server should be either “Running as Master“ or “Running as Slave.“ Also check 

the XPC-L Control log window to see if there is a log entry indicating that there was a 

problem. 

File Control and UD Processing When a System Is Stopped 

While performing cataloged file recovery on a system with an XPC-L, the Exec is unable 

to update or initialize internal XPC-L data files. An Exerr-0155 is taken after this message 

is displayed. 

Possible hardware problems with the XPC. 

May need to down xpc_name to reboot the system. 

4.6. Keyin Changes 

Keyins relative to XPC caching are not processed because caching is not available on the 

XPC-L; they result in the display of existing console messages which indicate caching is 

disabled. 

4.6.1. Unsupported Keyins 

XPCDUMP Keyin 

The XPCDUMP keyin is not supported in the XPC-L environment. The XPCDUMP keyin is 

rejected with the console message: 

XPCDUMP keyin is not supported on this type of XPC 

4–16 6885 3522–003

Use XPC-L Control’s Take Dump menu option to take a dump instead. 

4.6.2. Changed Keyins 

UP and DN Keyins 


The IOP and channel module connected to the XPC-L are partitioned as a single entity. 

An UP keyin partitions the IOP and channel module to UP available. A DN keyin partitions 

the IOP to DN and the channel module to DN not available. 

Note: SCMS defaults to the following names for the XPC-L: 

• An IOP connected to the XPC-L is identified as the XIIP and defaults to a name of the 

form XIPnn, where nn is a number or unique identifier. 

• A channel module connected to the XPC-L defaults to a name of the form XnnCnn, 

where nn is a number or unique identifier. 

Any attempt to up a channel module connected to the XPC-L is rejected with one of the 

following messages: 

If the IOP (XIPnn) connected to the channel module (XnnCnn) is currently up: 

UP keyin already performed for XnnCnn. 

If the IOP (XIPnn) connected to the channel module (XnnCnn) is currently down: 

UP of XnnCnn not performed - no path available. 

Any attempt to DN a channel module connected to the XPC-L (XnnCnn) is rejected with 

the following message: 

Require DN XIPnn to complete the request. 

UP/DN of an IOP connected to the XPC-L (XIPnn): 

UP XIPnn 

This partitions the XIPnn and the XnnCnn connected to the XPC-L to UP. 

DN XIPnn 

This partitions the XIPnn to DN and the XnnCnn connected to the XPC-L to DN/NA. 

UP XPC_name 

If the XPC_name is an XPC-L, this changes the partition status of the XPC_name to UP in 

MHM mode. 

DN XPC_name 

This changes the partition status of the XPC_name to DN. 

6885 3522–003 4–17


FS Keyins 

All FS keyins relating to the XPC-L and the IOP connected to the XPC-L (XIPnn) are as 

follows. 


This displays XPC status, mode, and all XIIP interfaces. 

At MODIFY CONFIG: 


XPC_name UP 

After SYS FIN: 


XPC_name UP MHM 

HOST A active XIPnn_a XIPnn_b 

HOST B inactive 

HOST C active XIPnn_c XIPnn_d 

HOST D inactive 

FS,IOP 

This displays all IOP names and status, including IOPs connected to the XPC-L. 

FS,IOP 

IOP00 UP , IOP01 DN , IOP02 UP 

XIP03 UP , IOP04 UP , IOP05 DN 

IOP11 DN , IOP12 UP , XIP13 UP 

IOP14 DN , IOP15 UP 

4–18 6885 3522–003

FS,CM 


This displays all channel module (CM) names and status, including any channel modules 

connected to the XPC-L. 

FS,CM 

I00C00 UP , I00C01 DN NA , I00C02 DN NA 


I00C06 DN NA , I00C07 DN NA , I00C14 DN NA 




I02C02 UP , X03C00 UP , I04C00 UP 



I12C00 UP , I12C01 UP , X13C00 UP 


I15C00 UP , I15C01 UP , I15C02 DN 

FS,XIIP 

These display all IOP names connected to the XPC-L. 

FS,XIIP 

XIPnn_a UP XIPnn_b UP 

FS,ALL XPC_name 

These display XPC_name and XIPnn and status. 

FS,ALL XPC_name 

XPC_name UP 

XIPnn_a UP XIPnn_b UP 

6885 3522–003 4–19


FS,ALL IPx 

These display name and status of all connected IOPs, channel modules (CM), and control 

units (CU), including IOPs (XIPnn) and channel modules (XnnCnn) connected to the 

XPC-L. 

fs,all ip0 

IP0 UP ACTIVE 

IOP00 UP , IOP01 DN , IOP02 UP 

IOP03 UP , XIP04 UP , IOP10 DN 

IOP11 DN , IOP12 UP , IOP13 UP 

IOP14 DN , XIP15 UP , I00C00 UP 

I00C01 DN NA , I00C02 DN NA , I00C03 UP 





I02C00 DN NA , I02C10 UP , I02C12 DN NA 



X04C00 UP , I10C00 DN NA , I10C01 DN NA 





I12C00 DN NA , I12C10 UP , I12C12 DN NA 



I14C00 DN NA , X15C00 UP , 51JA DN NA 

60AA S UP , HLC2A DN NA , T40SA UP 

F58BE UP , 51JA DN NA , F58BB UP 

E1 DN NA , F58BF UP , F0 DN NA 

X15C00 UP 

FS,ALL CM_name 

When the channel module (CM) is not connected to the XPC-L, this keyin displays the 

names and status of all control units connected to the channel module. When the 

CM_name is connected to the XPC-L, the keyin is rejected with the following message: 

FS KEYIN - (ALL) OPTION INVALID FOR XIPnn, INPUT IGNORED. 

FS,ALL IOP_name 

When the IOP_name is not connected to the XPC-L, this keyin displays the names and 

statuses of all channel modules and control units connected to the IOP_name. When the 

IOP_name is connected to the XPC-L, the keyin is rejected with the following message: 

FS KEYIN - (ALL) OPTION INVALID FOR XIPnn, INPUT IGNORED. 

4–20 6885 3522–003

FS,ALL XIIP_name 


The FS,ALL XIIP_name keyin is rejected with the same message used for the XPC. For 

example: 

FS,ALL XIIP45 

FS KEYIN - (ALL) OPTION INVALID FOR XIIP45, INPUT IGNORED. 

4.6.3. New Keyins 

The MAINT keyin moves an XIIP from the DN partition state into an UP partition state 

which supports microcode loading or dumping of the XIIP microcode. The MAINT keyin 

supports only XIIP partitioning; it is not defined for SCIOP partitioning. The format of the 

keyin is 

MAINT xiip_name 

where the xiip_name is the PCIOP which required microcode loading or dumping. 

When the MAINT xiip_name keyin completes, the status reported on the system console 

is: UP MT. An FS keyin shows the XIIP in the UP MT state. 

For example: 

FS XIP44 

XIP44 UP MT 

FS,XIIP 

XIP44 UP MT, XIP45 UP 

If the MAINT xiip_name keyin is entered when the XIIP is not in the DN partition state, the 

following message is displayed: 

"xiip_name must be DN when the MAINT keyin is entered." 

If a MAINT request is entered for a non-XIIP component, the following message is 

displayed: 

"MAINT keyin invalid for logical name component_name, input ignored." 

6885 3522–003 4–21


If a MAINT keyin is entered for a PCIOP which is already in the MAINT partition state, the 


"MAINT keyin already performed for xiip_name." 

An FS keyin of the XIIP performed after IOP load has started provides an indicator on the 

FS display that a microcode load is currently in progress. 

UP or DN keyins are not allowed to affect an XPC-L component while the IOP load is in 

progress and a message display will indicate this. 

When the microcode load or dump operation is completed, the XIIP must be downed to 

remove the XIIP from the MAINT partition state. An UP of the XIIP moves the XIIP back 

into the partition for system use. 

If the system stops when the XIIP is in MAINT mode, the XIIP remains in MAINT mode 

when the partition is rebooted. If the XIIP state is moved from UP to DN by the operator at 

the System Control Facility while the system is stopped, the MAINT mode is cleared 

when the partition is rebooted. 

4.7. Initialization 

If the system has two types of XPC host interfaces (XIIP and VI channel) configured, the 

boot process displays the following message and stops the system (see “4.4. New 

Console Messages“): 

4.8. EXERRS 

Two types of XIIPs are configured in PDB. 

Reload of correct PDB is required. 

The system stops with EXERR-133 if more than one VI channel is connected to a PCIOP. 

This is a new cause for an EXERR-133. 

4–22 6885 3522–003

Section 5 

Changing Hardware and Software 

Components 

This section provides procedures for adding, updating, upgrading, replacing, and deleting 

XPC-L hardware and software components. 

5.1. Changing Hardware 

This section provides guidelines and procedure for changing hardware components in an 

XPC-L system. Information is provided separately for the 

• XPC-L Control Workstation 

• XPC-L Server 

• XPC-L Host 

• XPC-L Control Workstation LAN Ethernet Switch (Ng700-SWX) for Dorado 300 

Series servers 

5.1.1. Changing XPC-L Control Workstation Hardware 

The XPC-L Control Workstation Control Workstation hardware is a workstation supplied 

by Unisys with the appropriate hardware for supporting the operation of the XPC-L 

system. Unless otherwise directed by Unisys, do not change or modify any hardware on 

the XPC-L Control Workstation. Do not upgrade your XPC-L Control Workstation unless 

specifically asked to do so in the XPC-L System Firmware 2.2 Customer Reference 

Manual or in the Technical Information Bulletin for an XPC-L system. Any required 

platform hardware update procedures are described within the accompanying 

documentation of the XPC-L system plateau release. 

Should a component within the workstation fail, it may render the workstation incapable 

of supporting the XPC-L system. After ordering a replacement workstation, refer to 

Section 2.1.1, “Installing XPC-L Control Workstation Hardware“ to install the replaced 

workstation. 

Ensure that the latest XPC-L Control.ini file (also called the state file) and configuration 

file (the default file name is ConfigFile.txt) are loaded on the replacement XPC-L 

Control Workstation. 

6885 3522–003 5–1

Changing Hardware and Software Components 

To load these files from previously created backup media, perform the following steps: 

1. Using the replacement XPC-L Control Workstation, insert the backup media with the 

current XPC-L Control.ini file (the state file) and configuration files into the DVD drive. 

a. Verify that the desired files reside on the media. 

b. Close the pop up window that displays the files currently on the DVD or CD. 

2. Open Windows Explorer. 

3. Copy the XPC-L Control.ini file (the state file) from the DVD to C:\XPC-L 

Control.ini. 

4. Copy the XPC-L configuration file from the DVD to its location on the C: drive. 

5. Remove the backup media from the DVD drive. 

At this point, the replacement XPC-L Control Workstation has the correct license code 

and is available to be used as the active XPC-L Control Workstation. 

5.1.2. Changing XPC-L Server Hardware 

The XPC-L Server hardware is an Intel node of either a Dorado 200 Series server or a 

Dorado 300 Series server supplied by Unisys with the appropriate hardware for 

supporting the operation of the XPC-L system. With the exception of adding additional VI 

cards, do not change or modify any hardware on the XPC-L server unless directed to do 

so by Unisys. Also, do not upgrade your XPC-L Server hardware unless directed in the 

XPC-L Firmware 2.0 Customer Reference Manual or the Technical Information Bulletin 

for an XPC-L system. Any platform hardware update procedures that are required are 

described within the accompanying documentation the XPC-L system firmware release. 

Should a component within the server fail (for example, a Dorado 200 Series server 

subDIB, a Dorado 300 Series server internal I/O module, a memory unit, and so on) it 

may render the server incapable of supporting the XPC-L system. After ordering the 

appropriate replacement hardware, refer to the following documents for procedures to 

reinstall the replaced hardware. 

If the XPC-L server type you ordered is 

• Installed as the Intel node of a Dorado Series server, refer to the ClearPath Plus 

Server Dorado 300 Series Install & Config Gd, Vol 5 Set Up OS 2200 & Intel Part 

(Dorado 300 Series servers) or ClearPath Plus Server Dorado Series Install & Config 

Guide, Vol 5: Set Up OS 2200 & Intel Part (Dorado 200 Series servers) for hardware 

reinstallation procedures. 

• Delivered as a standalone unit (does not apply to Dorado 300 Series servers), refer to 

the Enterprise Servers Hardware Installation Guide for hardware reinstallation 

procedures. 

Follow installation of any VI cards (for either replacing an existing card or adding a new 

card) on the XPC-L server the procedures documented in the appropriate hardware 

installation guide for insertion of new PCI connected devices. 

5–2 6885 3522–003


Refer to “5.1.2.1 Replacing an Existing VI Card“ and “5.1.2.2 Adding a New VI Card“ 

first for the entire procedure for replacing or for adding a VI card. Replacing the actual 

hardware card is only one of the steps in this procedure. 

5.1.2.1. Replacing an Existing VI Card 

This section describes how to replace a VI card in an XPC-L server. 

Notes: 

• You must stop the XPC-L service on the server containing the card that will be 

replaced. 

• If you purchased a redundant XPC-L system, the OS 2200 hosts can remain running 

during the replacement of the additional VI card. 

• If you purchased a non-redundant XPC-L system (that is, you have only a primary 

XPC-L server), you must stop all OS 2200 hosts connected to the XPC-L and 

terminate the XPC-L before replacing a VI card. 

• The XPC-L service on the server on which you are replacing the VI card must be 

running to place the direct connect host path, crossover path, or synchronization 

path offline. If the XPC-L service on this server is already indicated as being Stopped 

before beginning this procedure and the card to be replaced is a direct connect host 

path, crossover path, or synchronization path that is not already OFFLINE, use the 

XPC-L workstation to start the slave before beginning the card replacement 

procedure: Click Start Slave on the Action menu. 

• The VI card connectors are keyed to prevent misalignment or inversion and when 

inserting it, an audible click should be heard from the connector when it snaps in 

place. 

The following procedure for replacing a VI card is for a redundant XPC-L system and it 

assumes that the OS 2200 hosts remain running throughout the procedure. 

1. Use the host console to bring down all of the XIIPs that have direct connect paths to 

the server in which the VI card will be replaced. 

2. If the device to be replaced is a host path, go to the XPC-L Control Workstation and 

click the server that contains the host path. Then, in the Select Device pane, 

highlight the host path and click Offline. 

3. If the server in which the card is to be replaced is indicated as Running as 

Master, click Switch Master/Slave on the Action menu. 

4. If the device to be replaced is a synchronization or crossover path, click the server 

designated as Running as Master and highlight the peer device of the device 

being replaced. 

5. If the device is not already marked OFFLINE, click Offline. 

6885 3522–003 5–3


6. Click Terminate Slave on the Action menu. 

An EXEC console message appears on each OS 2200 host indicating that there has 

been a loss of redundancy in the XPC-L system. 

Note: This message does not appear in the case of XPC-L Firmware 2.2. 

7. Select the server in which the card is to be replaced. It should be the one indicated 

as Stopped. 

8. Highlight the device to be replaced. 

9. Double-click the device. 

A Properties window appears with information about the VI card. The network 

address of the card is displayed. 

10. Type the new network address over the old one and then click Apply. 

Note: The network address of the card is contained on a label affixed to the card. It 

is of the form xx:xx:xx:xx:xx:xx, where each x is a single hexadecimal digit. 

11. Perform a “Windows shutdown“ of the server in which the card is to be replaced. 

Caution 

1. Perform shutdown operation on the correct server. 

2. Do not perform the shutdown operation on the server that XPC-L Control 

indicates is Running as Master. 

3. Note the active PCI-Bridge and PCI-Bus before stopping. 

5–4 6885 3522–003


12. Perform the following steps for the particular server series in use: 

a. Dorado 300 Series server: Use the Service Processor console to bring down the 

appropriate PCI bus containing the card to be replaced. 

Dorado 200 Series server: Use the Service Processor console to bring down the 

appropriate subDIB and DIB containing the card to be replaced. 

b. Disconnect the cable from the card that is to be replaced. 

c. Dorado 300 Series server: Pull out the internal I/O module and replace the PCI 

card. 

Dorado 200 Series server: Pull out the subDIB and replace the PCI card. 

d. Dorado 300 Series server: Reinsert the internal I/O module. 

Dorado 200 Series server: Reinsert the subDIB. 

e. Reconnect the cable to the newly replaced card. 

f. Dorado 300 Series server: Bring up the PCI bus that was brought down in step 

12a. 

Dorado 200 Series server: Bring up the subDIB and DIB that was brought down 

in step 12a. 

g. Restart the server. 

h. Dorado 300 Series server: When the Windows boot on the XPC-L server is 

complete and you see all the connections for the VI cards, verify that the 

appropriate PCI bus is active. 

Dorado 200 Series server: When the Windows boot on the XPC-L server is 

complete and you see all the connections for the VI cards, verify that all 

appropriate subDIB and DIBs are active. 

13. On the XPC-L Control Workstation, select the server designated as Stopped. Click 

Start Slave on the Action menu. 

14. Select the server designated as Server Not Found. This causes a probe of the 

server and the server should now be designated as Stopped. 

15. If the device that was replaced is a host path, go to step 17. 

16. Select the server designated as Running as Master and highlight the peer device 

of the device that was replaced (this is the device that was selected to be placed 

offline in step 4). Click Up. XPC-L Control should now display the state of the device 

as Down. 

17. Click Start Slave on the Action menu. 

18. If the device that was replaced was a host path, select the appropriate server, 

highlight the device that was replaced, and click Up. 

19. Use the host console to up the XIIPs that were brought down in step 1. 

20. If you performed the Switch Master/Slave action in step 3, you may optionally 

perform this action again to return the master to the server that was originally the 

master before the card replacement. 

6885 3522–003 5–5


21. Click Save Config File on the File menu and save the configuration file to a 

removable media; provide a name for the new configuration file. 

22. If the XPC-L system you purchased contains a backup XPC-L Control Workstation, 

use the removable media from step 21 and Windows Explorer on the backup XPC-L 

Control Workstation to copy the updated configuration file to the backup XPC-L 

Control Workstation. 

23. Update the XPC-L Server PCI Locations Chart supplied with your XPC-L system (see 

Appendix B) to reflect the changed network address. 

5.1.2.2. Adding a New VI Card 

This section describes how to add a VI card to an XPC-L server. 

Stop the XPC-L service on the server containing the card that will be added. If you 

purchased a non-redundant XPC-L system (that is, you only have a primary XPC-L Server) 

stop all OS 2200 hosts connected to the XPC-L and terminate the XPC-L before adding a 

VI card. If you purchased a redundant XPC-L system, the OS 2200 hosts can remain 

running during the card addition. The procedure for adding a new VI card is identical to 

the procedure for replacing a VI card (see “5.1.2.1 Replacing an Existing VI Card“), 

except there is no existing VI card (the PCI bus slot is open); the device will already be 

marked OFFLINE by XPC-L Control because of this. 

If the configuration file your XPC-L system is currently running with has a VI card for this 

device location included in the configuration (that is, there is an entry for a VI card, but a 

VI card was not installed in this slot), the procedure will work. If there is no entry in the 

configuration file for the device to be added, the entire XPC-L system must be stopped 

before the VI card can be added. In this case, the configuration file is manually updated 

with a text editor to include the new VI card and the new configuration file is given as 

input before starting up the XPC-L system. 

5.1.3. Changing XPC-L Host Hardware 

The only hardware in a host that is unique to an XPC-L system are the VI cards and the 

PCIOP, which are a single Field Replaceable Unit (FRU). 

For replacement of the connectors to the VI Channels, follow the instructions in Section 

2.1.3, “Installing Host Hardware.“ 

For information about PCIOP PCA removal and replacement and for the troubleshooting 

and replacement of standard components within your Dorado Series server, refer to the 

following documents: 

• ClearPath Plus Server Dorado Series Fault Isolation and Servicing Guide (Dorado 100 

Series servers and Dorado 200 Series servers) 

• Dorado 300 Series Fault Isolation and Servicing Guide (Dorado 300 Series servers) 

• Dorado 700 Server Fault Isolation and Servicing Guide (Dorado 700 Series servers) 

• Dorado 4000 Server Fault Isolation and Servicing Guide (Dorado 4000 Series servers) 

5–6 6885 3522–003


5.1.4. Changing the XPC-L Control Workstation LAN Ethernet 

Switch 

The Ethernet managed switch (NG700-SWX) used for the XPC-L Control Workstation 

interconnect is the same as that used in the XPC-L (Dorado 300 Series servers) for 

hardware control. However, when used for XPC-L Control Workstation interconnect, the 

switch is used as a simple switch rather than as a managed switch. All management 

programming is removed from the switch by forcing a factory reset: Momentarily press 

Factory Reset located on the back of the unit, then cycle the AC power switch to OFF 

and then to ON again. 

5.2. Changing Software 

This section describes how to change one or more of the software components that 

make up an XPC-L system. You must determine if a complete shutdown of the XPC-L 

system is required to be able to change one or more of the components. Consult the 

XPC-L Firmware 2.2 Customer Reference Manual and Technical Information Bulletin for 

the plateau you are intending to move to for this information. 

Installing all of the software components from the new plateau is a simpler and less 

error prone procedure than changing an individual software component while the other 

software components remain operating. A complete shutdown of the XPC-L system 

requires all hosts connected to the XPC-L system to be down. If this is undesirable, you 

can change the software components individually (if the newly installed software is 

compatible with the current XPC-L software that remains running). However, you may 

have to perform a complete shutdown if your upgrade results in incompatible code levels 

while attempting to change software components individually. 

5.2.1. Changing with a Complete Shutdown of the System 

Use the following procedure if you choose to perform the software upgrade change by 

completely shutting down the XPC-L system. You might have to use this procedure if 

your upgrade results in incompatible code levels while attempting to change software 

components individually. 

1. Shut down the entire XPC-L system, referring to the XPC-L Operations Guide.. 

2. Remove the currently installed XPC-L Server software from the primary and 

secondary servers (see Section 6.3, “Removing XPC-L Server Software“). 

3. Remove the currently installed XPC-L Control software from the active and backup 

workstations (see Section 6.4, “Removing XPC-L Control Workstation Software“). 

4. Install the new XPC-L Control software using the procedures in Section 2.2.3, 

“Installing XPC-L Control Workstation Control Software.“ 

5. Install the new XPC-L Server software using the procedures in Section 2.2.4, 

“Installing XPC-L Server Software.“ 

6. Install the new version of XIIP (PCIOP) microcode using the procedures in “5.2.9.1 

Loading a New Version of XIIP Microcode.“ 

6885 3522–003 5–7


5.2.2. Changing XPC-L Platform Software 

The XPC-L platform software consists of Windows 2003, Enterprise Edition, on the 

XPC-L servers and Windows XP on the XPC-L Control Workstations. Microsoft releases 

patches, service packs, and new releases of its operating system and associated 

software on an ongoing basis. Do not change or modify any Windows software on the 

XPC-L servers or XPC-L Control Workstations unless otherwise directed by Unisys. 

Unisys also announces and makes available updates to its Dorado Series platform 

software for general use for those customers running the Windows operating system. 

Do not upgrade your XPC-L system platform unless it is specifically called for in the XPC- 

L Firmware 2.0 Customer Reference Manual or the Technical Information Bulletin for an 

XPC-L platform. Any required platform software upgrade procedures are described in 

each XPC-L firmware release. This includes information on whether the code levels are 

compatible for changing components individually or whether the entire system should be 

shut down and upgraded all at once. 

Windows XP Activation 

The Dell OptiPlex 755 and 960 workstations that are shipped as Control Workstations for 

the XPC-L come with Windows XP SP2 installed. These Workstations are setup at the 

Unisys factory for use as the XPC-L Control Workstations. The most recently shipped 

OptiPlex 755 and 960 workstations have the software option for downgrading Windows 

Vista Business Bonus-Windows XP Professional. 

You will no longer be able to activate on-line over the Internet. When prompted to 

activate, call the activation support line and explain your circumstances to the Microsoft 

customer service representative. Once it is determined that you have a valid Vista 

Business License, the customer service representative will help you activate your XP 

software. 

When calling the customer service representative, keep ready an XP CD and its product 

key from one of your existing workstations or service processors. This is because the 

customer service representative might ask you to use this product key to activate your 

XPC-L Workstation. 

5–8 6885 3522–003


5.2.3. Changing Platform Software on the XPC-L Control 

Workstations [Dell OptiPlex 960] 

This section describes how to: 

• Reinstall Windows XP onto an XPC-L Control Workstation 

• Reinstall device drivers onto an XPC-L Control Workstation 

• Reconfigure the XPC-L Control Workstation 

5.2.3.1. Reinstalling Windows XP SP3 and Setting Up the XPC-L 

Control Workstation [Dell OptiPlex 960] 

The following procedure reinstalls everything except the device drivers. Reinstallation of 

the device drivers is described in “5.2.3.2 Reinstalling Device Drivers.“ You will also 

need to remove certain Windows components and enable Multi CPU Core mode for the 

processor. These procedures are described in “5.2.3.3 Removing Unnecessary Windows 

Components, Executables, and Services“ and “5.2.3.4 Enabling Multi CPU Core Mode.“ 

1. Disconnect any mapped network drives on all XPC-L servers. 

2. Copy any data that has to be saved off the local disk (for example, control logs, 

configuration files, host files, and so on). 

3. Insert the reinstallation (recovery) CD-ROM and reboot the XPC-L Control 

Workstation. The message Boot from CD appears. 

Note: If you do not see the message Boot from CD, press F2 to access the 

BIOS and change the boot configuration to boot from CD first instead of from the 

hard drive first. Then reboot the XPC-L Control Workstation. 

4. Press Enter to boot from CD. 

The Windows Setup window appears and then the Welcome to Setup selection 

window appears. 

5. Press Enter to select the menu item To set up Windows XP now. 

The Windows XP Licensing Agreement window appears. 

6. Press F8 to accept the terms of the license agreement. The window showing the 

current partitions appears. 

a. To install a fresh copy of Windows XP without repairing, press ESC. 

b. Select the C: partition with the current size of 76,254 MB. 

c. Press D to delete the selected partition. 

d. Press Enter to delete. 

e. Press L. 

6885 3522–003 5–9


7. Create the new partition using the following steps: 

a. Select the unpartitioned space of 76,254 MB. 

b. Press C to select the current partition size of 76,254 MB. 

c. Press Enter. 

d. Select C: Partition 2 [New Raw] 76254MB. 

e. Press Enter. 

f. Select Format the partition using NTFS file system and press Enter. 

The drive is formatted. After the drive has been formatted, Windows XP begins 

to install. The PC reboots when installation is complete. 

The Regional and Language Options dialog box is displayed. 

8. Click Next. Type your name and organization in the registration window that 

appears. Type the name and organization values established by your site 

administrator, then click Next. 

9. Type the computer name and password from Table B–8 into the appropriate boxes 

and click Next. 

10. Set the correct date and time for your location. Click Next. 

Windows installation continues for a few minutes. A progress window lets you know 

the installation process is continuing. The message "To improve the appearance of 

visual elements, Windows will automatically adjust your screen resolution" 

appears. 

11. Click OK on the Display settings message box. 

After Windows completes its adjustments, it asks if you can view the display. 

12. Click OK. 

The Welcome window appears. 

13. Click Next to continue. 

The Help Protect your PC window appears showing the following two options: 

− Help Protect my PC by turning on Automatic updates now. 

− Not right now. 

14. Select Not right now (because your PC will be on a private network) and click 

Next. 

The Who will use this computer window appears. 

15. Type the user name from Table B–9 (or one that has been assigned by your site) in 

the Administrator box and click Next. 


The Logon window appears. 

5–10 6885 3522–003


17. Log on to the Administrator account and perform the procedures provided in the 

following sections: 

− “5.2.3.2 Reinstalling Device Drivers“ 

− “5.2.3.3 Removing Unnecessary Windows Components, Executables, and 

Services“ 

− “ 5.2.3.4 Enabling Multi CPU Core Mode“ 

18. Continue setting up the user accounts by performing the following steps: 

a. On the Start menu, point to Settings and click Control Panel. 

b. Double-click User Accounts. 

The User Accounts window appears. 

c. Select Change the way users log on or off. 

The Select logon and logoff options dialog box appears. 

d. Clear the Use the welcome screen option, and then click Apply Options. 

You are returned to the User Accounts window. 

e. Click Create a new account. Type the XPC-L Control user name (or a user of 

your choice) referring to the appropriate row of the XPC-L System User 

Name/Password Information Worksheet provided with your system (see Table 

B–9 for an example of this table). 

f. Click Change an account and select the user name you defined in step 18e. 

g. Click Create password. 

Enter the password (or a password of your choice) for this user name referring 

to the appropriate row of the XPC-L System User Name/Password Information 

Worksheet provided with your system (see Table B–9 for an example of this 

table). 

The Files and folders dialog box appears. 

h. Click Create password. 

i. Click No and close the User Accounts window. 

j. Repeat steps 18f through 18i for the XPC-L Service user name and password. 

6885 3522–003 5–11


19. Perform the following steps to configure and set up the network configurations. The 

workstation has two Ethernet cards installed. Note these cards might not be 

identical. 

a. On the Start menu, point to Settings and then click Control Panel. 

b. Double-click the Network and Internet connections category. 

The Network and Internet connections window appears. 

c. Click Network Connections on the lower part of the window. 

The Network Connections window appears. 

d. Right click the appropriate Local Area Connection icon and click 

Properties. 


e. Click Internet Protocol (TCP/IP) to highlight it and then click Properties. 


f. Click Use the following IP address and fill in the fields as follows: 

1. Type the IP address for this XPC-L Control Workstation. Also write into the 

appropriate row and column of the XPC-L System Information part of the 

worksheet provided with your system (see Table B–8 for an example of this 

table). Use Network IP Address 1 for LAN 2 and Network IP Address 2 for 

LAN. 

2. Type the appropriate subnet mask in the Subnet mask box. 

3. Leave the Default gateway, DNS server, and Alternate DNS server 

boxes blank. 


g. Click Close to close the Local Area Connection Properties window. 

h. Repeat steps 19d through 19g for the other network card (click the other Local 

Area Connection icon). 

i. Close Control Panel. 

5–12 6885 3522–003


20. Install the Roxio Creator Dell Edition software using the following steps: 

a. Insert the Roxio Creator 9.0 DE CD. The Roxio setup wizard appears 

b. Click Next Next. Next The End User License agreement appears. 

c. Read the license agreement. Click I accept the terms and then click Next. 

Customer Information screen appears. 

d. Fill in the name, organization, and serial number if not already filled. Then click 

Next. The choose setup type window appears. 

e. Select Custom and then click Next to install Roxio in the default location. The 

Feature window appears. 

f. Uncheck the following features: 

ο Roxio Creator Audio 

ο Roxio Express Labeler 3 

ο Roxio Drag to Disc 

g. Click Next and click Install. The installation continues and will take a few 

minutes to finish. 

h. When the installation is done click Finish. Click Yes to the restart message and 

reboot your computer. Remove the Roxio CD. 

i. Log back on as an administrator. Click Start, point to Settings and open 

Control Panel. Double-click Add/Remove programs. Then remove this 

program: Sonic CinePlayer Decoder-Pack. 

6885 3522–003 5–13


21. Install the Microsoft .NET framework and .NET framework SP1 from the XPC-L 

Firmware CD-ROM by performing the following steps: 

a. Insert the XPC-L Firmware Level CD into the CD drive of the XPC-L Control 

Workstation. The installation application detects if the proper version of .NET 

Framework is installed. 

ο If the proper version is installed, you will not receive any messages related 

to the installation of .NET Framework. In this case, cancel the XPC-L Control 

installation (this step will be performed later). 

ο If you receive an End User License Agreement (EULA) window about .NET 

Framework 1.1 setup, proceed to step 21b. 

ο If you receive a window asking if you want to install Microsoft .NET 

Framework Service Pack 1, proceed to step 21e. 

b. Request a customer representative to perform the following steps to accept the 

EULA. A Unisys service representative is not authorized to perform this step. 

1. Read the license agreement, scrolling as necessary. 

2. Click I agree to accept the EULA. 

c. Click Install. 

Status windows display the progress of the .NET Framework installation. 

d. Click Cancel to stop the XPC-L Control installation (this step is performed later). 

Click OK to continue with the Microsoft .NET Framework Service Pack 1 

installation. 

e. Read through the End User License Agreement for .NET Framework SP1 and 

then click I accept. 

f. A message box appears indicating that all applications should be closed before 

performing the installation. 

g. Close all applications except the XPC-L Control installation application, and then 

click Ignore to proceed with the installation. 

Status windows display the progress of the .NET Framework SP1 installation 

until the final window indicates that the installation was completed successfully. 

h. Click OK. 

A message box appears prompting you to restart the system for the 

configuration changes to take effect. 

i. Click Yes to restart your computer. 

Note: Your computer will not reboot if it requires installation of the hot fix 

described in step 22. 

5–14 6885 3522–003


22. Install the Microsoft .NET framework 1.1 hot fix (KB896665) from the XPC-L 

Firmware CD-ROM by performing the following steps: 

a. Insert the XPC-L Firmware Level CD into the CD drive of the XPC-L Control 

Workstation. The installation application checks to see if the hot fix is installed. 

ο If the hot fix is installed, you do receive any messages related to the 

installation of the hot fix. In this case, cancel the XPC-L Control installation 

(this step will be performed later). 

ο If you receive a window asking if you want to install Microsoft .NET 

Framework 1.1 hot fix (KB896665), proceed to step 22b. 

b. Click OK to continue with the Microsoft .NET Framework hot fix (KB896665) 

installation. 

c. Read through the End User License Agreement for the hot fix. Click I accept. 


until the final window indicates successful completion of installation. 

d. Click OK. 

The system displays the XPC-L Control Workstation installation window. 

e. Click Cancel to not proceed with the XPC-L Control installation (this step will be 

performed later). 

f. Reboot the computer. 

23. To finish setting up your XPC-L Control Workstation, refer to Section 2.2.2, 

“Preparing to Install XPC-L Software.“ 

6885 3522–003 5–15


5.2.3.2. Reinstalling Device Drivers 

Perform the following steps to reinstall the video, audio, and network drivers: 

1. Insert the Dell Driver and Utilities Resource CD-ROM that came with your system 

into the CD drive. 

2. Click Cancel to avoid installing from the CD-ROM. 

3. Restart the PC. The Startup dialog box appears. 

4. Click Boot from CD-ROM. 

5. Click 1 Run the 32 bit diagnostics. 


7. Click 1. 


9. Click Test System. 

10. Click Express Test. 

11. When Express Test completes successfully, click OK and then close the dialog box. 

This causes the system to reboot. 

12. On the Startup dialog box, remove the CD-ROM from the drive and click Boot 

from hard drive. 

13. Insert the Dell Driver and Utilities Resource CD-ROM into the CD drive. 

14. Click OK to install from the CD-ROM. Then click Next. 

15. Click Install, and then click Finish. 

The Welcome dialog box appears. 

16. Click Next. The system searches for hardware. 

Perform the following steps to reinstall audio drivers: 

1. Click Audio Drivers. 

2. Click Extract and follow the instructions to reinstall the driver. 

3. Click Continue. 

4. Click OK. 

5. Click Yes. 

6. Click OK. 


8. Click NO, I will start my computer later. 

9. Click Finish and then click Return. 

5–16 6885 3522–003

Perform the following steps to reinstall network drivers: 


1. Select the NIC driver (the Broadcom 57xx Gigabit) to reinstall the network driver. 


3. Click Return when the reinstallation of the network driver finishes. 

4. Select the NIC driver (Intel 825xx Gigabit) to reinstall the network driver. 


6. Click Return when the reinstallation of the network drivers finishes. 

Perform the following steps to reinstall video drivers: 

1. Click Video Driver to reinstall the video driver. 


3. Click No, I will start my computer later. 

4. Click Return when the reinstallation of the video driver finishes. 

5. Click Controller Drivers/ Intel Chip Set Software. 


7. When the InstallShield Wizard Complete dialog box appears, remove the Dell 

Drivers and Utilities CD-ROM from the drive. 

Note: If you do not see the InstallShield Wizard, close the OptiPlex Resource CD 

window. 

8. Click Finish and reboot the computer. 

9. Adjust the window properties as needed. Right-click Desktop icon and click 

Properties. 

The Display Properties window appears. 

10. Select the Settings tab and, under Screen resolution, change the resolution to 

1024x768 pixels. 

11. Return to step 17 in “5.2.3.1 Reinstalling Windows XP SP3 and Setting Up the XPC-L 

Control Workstation [Dell OptiPlex 960].“ 

6885 3522–003 5–17


5.2.3.3. Removing Unnecessary Windows Components, Executables, 

and Services 

Perform the following steps to remove unnecessary Windows components and 

executables: 


2. Switch to Classic mode on the Control Panel using the following steps: 

a. Click Start, point to Settings, and then click Control Panel. 

b. Double-click Folder Options. 

c. On the General tab under Tasks, click Use Windows classic folders. Click 

OK. 

3. Double-click Add or Remove Programs. 

4. Click Add/Remove Windows Components. 

5. Ensure that the following check boxes are cleared: 

− Internet Explorer 

− MSN Explorer 

− Outlook Express 

− Update Root Certificates 

− Windows Media Player 

− Windows Messenger 


Status windows display the progress of the removal of Windows components. 

7. Click Finish when you receive a message indicating that you have successfully 

completed the Windows component operation. 

Note: You might see a message box during the process of removing of Windows 

components indicating that there is Windows failure related to MSN Explorer. Click 

OK if you see this message box. 

8. Close the Windows Components window. 

9. If any of the following programs are listed, click each of them and remove it: 

− Google desktop 

− Google toolbar 

− Power DVD 517 

− Dell resource CD 

5–18 6885 3522–003

10. Close the Add or Remove Programs window. 


Perform the following steps to disable unnecessary Windows services: 

1. On Control Panel, double-click Administrative Tools. 

2. Double-click Services. 

3. If the Security Center service exists, select it and perform the following steps. 

Otherwise, proceed to step 4. 

a. If the Security Center service does not have a status of Started, proceed 

to step 3c. 

b. Right-click the service and click Stop. Wait for the service to stop. 

c. If the service has a Startup Type of Disabled, proceed to step 4. 

d. Right-click the service and click Properties. 

e. Select Disabled from the Startup Type list. 

f. Click OK. 

4. Repeat steps 3a through 3f for each of the following services: 

− Windows Firewall 

− Fast User Switching Compatibility 

− Spkrmon 

− Application Layer Gateway 

5. Close the Services window. 

6. Close the Administrative Tools window. 

7. Reboot the workstation. 



6885 3522–003 5–19


5.2.3.4. Enabling Multi CPU Core Mode 

Multi CPU Core must be enabled on XPC-L Control Workstations. Perform the following 

steps to enable Multi- CPU Core: 

1. Reboot the workstation and enter the BIOS setup by pressing the F2 key early in the 

reboot process. The appropriate time to press F2 is when you see DELL in large 

letters on the screen and the F2 setup option displayed in the upper right corner of 

the screen. 

The BIOS Settings screen appears. 

2. Click Performance Group in the left column of the display to select it. 

3. Expand Performance Group and click Multi Core Support. 

4. Ensure Enable Multi Core Support is checked. If it is not already selected, 

select it and then go to step 5. If it is selected, go to step 6. 

5. Click Apply. 

6. Click Exit. 

The workstation reboots with Multi CPU Core enabled. 




Workstations [Dell OptiPlex 745 and Dell OptiPlex 755] 

This section describes how to: 




5–20 6885 3522–003


5.2.4.1. Reinstalling Windows XP and Setting Up the XPC-L Control 

Workstation Dell [OptiPlex 745 and Dell OptiPlex 755] 


the device drivers is described in “5.2.4.2 Reinstalling Device Drivers.“ You will also 

need to remove certain Windows components and enable Multi CPU Core mode for the 

processor. These procedures are described in “5.2.4.3 Removing Unnecessary Windows 

Components, Executables, and Services“ and “5.2.4.4 Enabling Multi CPU Core Mode.“ 




3. Insert the reinstallation (recovery) CD-ROM and reboot the XPC-L Control 

Workstation. The message Boot from CD appears. 

Note: If you do not see the message Boot from CD, press F2 to access the 

BIOS and change the boot configuration to boot from CD first instead of from the 

hard drive first. Then reboot the XPC-L Control Workstation. 

4. Press Enter to boot from CD. 

The Windows Setup window appears and then the Welcome to Setup selection 

window appears. 

5. Press Enter to select the menu item To set up Windows XP now. 

The Windows XP Licensing Agreement window appears. 

6. Press F8 to accept the terms of the license agreement. The window showing the 

current partitions appears. 

a. Press ESC to install a fresh copy of Windows XP without repairing. 

b. Select the C: partition with the current size of 76,254 MB. 

c. Press D to delete the selected partition. 

d. Press Enter to delete. 

e. Press L. 


a. Select the unpartitioned space of 76,254 MB. 

b. Press C to select the current partition size of 76,254 MB. 

c. Press Enter. 

d. Select C: Partition 2 [New Raw] 76254MB. 

e. Press Enter. 

f. Select Format the partition using NTFS file system and press Enter. 


to install. The PC reboots when installation is complete. 

The Regional and Language Options dialog box is displayed. Click Next. 

6885 3522–003 5–21


8. Type your name and organization in the registration window that appears. Type the 

name and organization values established by your site administrator, then click 

Next. 

9. Type the computer name and password from Table B–8 into the appropriate boxes 

and click Next. 


Windows installation continues for a few minutes. A progress window lets you 

know the installation process is continuing. The message "To improve the 

appearance of visual elements, Windows will automatically adjust your 

screen resolution" appears. 

11. Click OK on the Display settings message box. 

After Windows completes its adjustments, it asks if you can view the display. 

12. Click OK. 

The Welcome window appears. 


The Help Protect your PC window appears showing the following two options: 

− Help Protect my PC by turning on Automatic updates now. 

− Not right now. 

14. Select Not right now (because your PC will be on a private network) and click 

Next. The Who will use this computer window appears. 

15. Type the user name from Table B–9 (or one that has been assigned by your site) in 

the Administrator box and click Next. 


The Logon window appears. 

17. Log on to the Administrator account and perform the procedures provided in the 

following sections of “5.2.4 Changing Platform Software on the XPC-L Control 

Workstations [Dell OptiPlex 745 and Dell OptiPlex 755].“ 

− “5.2.4.2 Reinstalling Device Drivers“ 

− “5.2.4.3 Removing Unnecessary Windows Components, Executables, and 

Services“ 

− “ 5.2.4.4 Enabling Multi CPU Core Mode“ 

5–22 6885 3522–003









You are returned to the User Accounts window. 





f. Click Change an account and select the user name you defined in step 18e. 





table). 


h. Click No and close the User Accounts window. 

i. Repeat steps 18f through 18h for the XPC-L Service user name and password. 

6885 3522–003 5–23


19. Perform the following steps to configure and set up the network configurations. The 

workstation has two Ethernet cards installed. Note these cards might not be 

identical. 

a. On the Start menu, point to Settings and then click Control Panel. 

b. Double-click the Network and Internet connections category. The 

Network and Internet connections window appears. This window has two parts: 

the top part has the caption Pick a task and the lower part has the caption or 

pick a Control Panel Icon with labeled icons below it. 

c. Click Network Connections on the lower part of the window. 

The Network Connections window appears. 

d. Right click the appropriate Local Area Connection icon and click 

Properties. 


e. Click Internet Protocol (TCP/IP) to highlight it and then click Properties. 


f. Click Use the following IP address and fill in the fields as follows: 

1. Type the IP address for this XPC-L Control Workstation. Also write into the 

appropriate row and column of the XPC-L System Information part of the 

worksheet provided with your system (see Table B–8 for an example of 

this table). Use Network IP Address 1 for LAN 2 and Network IP Address 2 

for LAN. 

2. Type the appropriate subnet mask in the Subnet mask box. 

3. Leave the Default gateway, DNS server, and Alternate DNS server 

boxes blank. 


g. Click Close to close the Local Area Connection Properties window. 

h. Repeat steps 19d through 19g for the other network card (click the other Local 

Area Connection icon). 

i. Close Control Panel. 

20. Install the Roxio Creator Dell Edition software. 

5–24 6885 3522–003


21. Install the Microsoft .NET framework and .NET framework SP1 from the XPC-L 

Firmware CD-ROM using the following steps: 

a. Insert the XPC-L Firmware CD into the CD drive of the XPC-L Control 

Workstation. The installation application checks to see if the proper version of 

.NET Framework is installed. 

− If the proper version is installed, you will not receive any messages related 

to the installation of .NET Framework. In this case, cancel the XPC-L Control 

installation (this step will be performed later). 

− If you receive an End User License Agreement (EULA) window about .NET 

Framework 1.1 setup, proceed to step 21b. 

− If you receive a window asking if you want to install Microsoft .NET 

Framework Service Pack 1, proceed to step 21e. 

b. Request a customer representative to perform the following steps to accept the 

EULA. A Unisys service representative is not authorized to perform this step. 

1. Read the license agreement scrolling through as necessary. 

2. Click I agree to accept the EULA. 

c. Click Install. 


d. Click Cancel to stop the XPC-L Control installation (this step is performed later). 

Proceed to step 21e to install Microsoft .NET Framework Service Pack 1. 

e. Click OK to continue with the Microsoft .NET Framework Service Pack 1 

installation. 

f. Read through the End User License Agreement for .NET Framework SP1 and 

then click I accept. 

A message box appears indicating that all applications should be closed before 


g. Close all applications except the XPC-L Control installation application, and then 

click Ignore to proceed with the installation. 



h. Click OK. 

A message box appears prompting you to restart the system for the 

configuration changes to take effect. 

i. Click Yes to restart your computer. 

Note: Your computer will not reboot if it requires installation of the hot fix 

described in step 22. 

6885 3522–003 5–25


22. Install the Microsoft .NET framework 1.1 hot fix (KB896665) from the XPC-L 

Firmware CD-ROM using the following steps: 

a. Insert the XPC-L Firmware CD into the CD drive of the XPC-L Control 

Workstation. The installation application checks to see if the hot fix is installed. 

− If the hot fix is installed, you do receive any messages related to the 

installation of the hot fix. In this case, cancel the XPC-L Control installation 


− If you receive a window asking if you want to install Microsoft .NET 

Framework 1.1 hot fix (KB896665), proceed to step 23b. 

b. Click OK to continue with the Microsoft .NET Framework hot fix (KB896665) 

installation. 

c. Read through the End User License Agreement for the hot fix. Click I accept. 



d. Click OK. 


e. Click Cancel to not proceed with the XPC-L Control installation (this step will be 

performed later). 

f. Reboot the computer. 

23. To finish setting up your XPC-L Control Workstation, refer to Section 2.2.2, 

“Preparing to Install XPC-L Software.“ 

5–26 6885 3522–003




1. Insert the Dell Resource CD-ROM that came with your system into the CD drive. 


3. Restart the PC. The Startup dialog appears. 


5. Click 1 Run the 32 bit diagnostics. 


7. Click 1. 


9. Click Test System. 


11. When Express Test completes successfully, click OK and then close the dialog box. 


12. On the Startup dialog box, remove the CD-ROM from the drive and click Boot 

from hard drive. 

13. Insert the Dell Resource CD-ROM into the CD drive. 

14. Click OK to install from the CD-ROM. 

15. Click Install, and then click Finish. 

The Welcome dialog box appears. 

16. Click Next. The system searches for hardware. 

Perform the following steps to reinstall audio drivers: 

1. Click Audio Drivers. 



4. Click OK. 

5. Click Yes. 

6. Click OK. 


8. Click NO, I will start my computer later. 

9. Click Finish and then click Return. 

6885 3522–003 5–27


Perform the following steps to reinstall network drivers: 

1. Select the NIC driver (the Broadcom 57xx Gigabit) to reinstall the network driver. 


3. Click Return when the reinstallation of the network driver finishes. 

For the OptiPlex 755, go to step 1 of video driver reinstallation. For the OptiPlex 745, 

go to step 4 of video driver reinstallation. 

4. Select the NIC driver (Intel 825xx Gigabit) to reinstall the network driver. 


6. Click Return when the reinstallation of the network drivers finishes. 

Perform the following steps to reinstall video drivers: 

1. Click Video Driver to reinstall the video driver. 


3. Click No, I will start my computer later. 

4. Click Return when the reinstallation of the video driver finishes. 

5. Click Controller Drivers. 


7. When the InstallShield Wizard Complete dialog box appears, remove the 

Resource CD-ROM from the drive. 

Note: If you do not see the InstallShield Wizard, close the OptiPlex Resource CD 

window. 

8. Click Finish and reboot the computer. 

9. Adjust the window properties as needed. Right-click Desktop icon and click 

Properties. 




11. Return to step 17 in “5.2.4.1 Reinstalling Windows XP and Setting Up the XPC-L 

Control Workstation [OptiPlex 745 and Dell OptiPlex 755].“ 

5–28 6885 3522–003





executables: 


2. Switch to Classic mode on the Control Panel using the following steps: 



c. On the General tab under Tasks, click Use Windows classic folders. Click 

OK. 



5. Ensure that the following check boxes are cleared: 








Status windows display the progress of the removal of Windows components. 

7. Click Finish when you receive a message indicating that you have successfully 

completed the Windows component operation. 

Note: You might see a message box during the process of removing of Windows 

components indicating that there is Windows failure related to MSN Explorer. Click 

OK if you see this message box. 


6885 3522–003 5–29


9. If any of the following programs are listed, click each of them and remove it: 

− Google desktop 

− Google toolbar 

− Power DVD 517 

− Dell resource CD 

− Express Labeler 

− Roxio Creator Audio 

− Roxio Creator BDAV Plug-ins 

− Roxio Drag to Disc 

− J2SE Runtime Environmental 5.0 Update 6 

− Search Assist 

− URL Assist 







a. If the Security Center service does not have a status of Started, proceed 

to step 3c. 




e. Select Disabled from the Startup Type list. 

f. Click OK. 

5–30 6885 3522–003



− Windows Firewall 

− Fast User Switching Compatibility 

− Spkrmon 

− Application Layer Gateway 






5.2.4.4. Enabling Multi CPU Core Mode 

Multi CPU Core must be enabled on XPC-L Control Workstations. Perform the following 

steps to enable Multi- CPU Core: 




the screen. 

The BIOS Settings window appears. 

2. Use the up or down arrow keys to highlight Performance Group on the left 

column of the window. 

3. Press Enter to view the fields in the Performance Group. 

4. Use the up or down arrow keys to highlight the Multi CPU Core field in the group. 

5. Press Enter to modify the workstation’s Multi CPU Core behavior. 

6. Use the left or right arrow keys to change the setting to On (On should be 

highlighted). 

7. Press Enter to complete the Multi CPU Core modification change. 

8. Press Esc to initiate the BIOS setup exit. 

9. Use the left or right arrow keys to select Save/Exit to save your changes and exit 

setup. 


The workstation reboots with Multi CPU Core enabled. 



6885 3522–003 5–31



Workstations [Dell GX270 and GX280] 

This section describes how to 




5.2.5.1. Reinstalling Windows XP and Setting Up the XPC-L Control 

Workstation [Dell GX270 and GX280] 


the device drivers is described in “5.2.5.2 Reinstalling Device Drivers.“ 

You must also remove certain Windows components and verify Hyper-Thread mode for 

the processor. These procedures are described in “5.2.5.3 Removing Unnecessary 

Windows Components, Executables, and Services“ and “5.2.5.4 Verifying and Enabling 

CPU Hyper-Threading.“ 




3. Insert the restorable (recovery) CD-ROM and reboot the XPC-L Control Workstation. 

The message Boot from CD appears. 

4. Press Enter to continue. 

The Windows Setup window appears and then the Welcome to Setup window 

appears. 

5. Press Enter to select To set up Windows XP now, press Enter. 

The Windows XP Licensing Agreement window appears on the window. 

6. Press F8 to accept the terms of the license. 

The window showing the current partition appears and should show something 

similar to C: Partition 1 NTFS 38139 MB. 

Note: If you had Windows XP installed previously, press ESC to continue. 

7. Delete the current partition using the following steps: 

a. Press D to delete the selected partition. 

b. Press Enter to delete. 

c. Press L. 

5–32 6885 3522–003



a. Press C to select the current partition size of 38139 MB 

b. Press Enter. 

c. Select Format the partition using NTFS file system and press Enter. 


to install. 


9. Click Customize to enter your regional and language preferences. 


On the next window displayed, select your language and location choices and then 

click OK. 

11. Click Next. Type the values for the name and organization established by your site 

administrator into the registration window. 

12. Type the user name and password from Table B–9 and click Next. 


The Network Settings window appears for the added network interface card. 

14. Select typical and then click Next. 

Note: The NIC card installed is described as either a Netgear FA312 Fast Ethernet 

Adapter or a Broadcom NetXtreme 57XX Gigabit Controller. 

The Workgroup or Computer Domain window appears. 

15. Click No this computer is not on a network. Enter the workgroup name 

WORKGROUP and click Next. 

The following message appears: 

To improve the appearance of visual elements, Windows will automatically 

adjust your screen resolution 

16. Click OK in response to the Monitor settings message. 

17. When the Windows XP welcome screen appears, click Next. 

Windows then asks you to check your Internet capability. 

18. Click Skip. 

19. Click No in response to the message that asks you if you are ready to register online 

with Microsoft. 

20. Click Next. Set up the users by entering the user names referring Table B–9. 

21. Click Finish. The Logon window appears. 

6885 3522–003 5–33


22. Perform the procedures as given in the following sections: 

• “5.2.5.2 Reinstalling Device Drivers,“ to reinstall the device drivers. 

• “5.2.5.3 Removing Unnecessary Windows Components, Executables, and 

Services,“ to remove unnecessary Windows components. 

• “5.2.5.4 Verifying and Enabling CPU Hyper-Threading,“ to verify Hyper-Thread 

mode. 








You are taken back to the User Accounts window. 





f. Click Change an account and select the user name you defined in step 12. 





table). 


h. Click No and close the User Accounts window. 

i. Repeat steps 23b through 23h for the XPC-L Service user name and password. 

5–34 6885 3522–003


Configuring and Setting Up Network Configurations 

Perform the following steps to configure and set up the network configurations. The 

workstation has two Ethernet cards installed. Note these cards might not be identical. 

1. On the Start menu, point to Settings, and then click Control Panel. 

2. Select the Network and Internet connections category. 

The Network and Internet connections window appears. This window has two parts; 

the top part has the caption Pick a task and the lower part has the caption or pick a 

Control Panel Icon with labeled icons below it. 

3. From the lower part of the window, select Network Connections. The Network 


4. Right-click the appropriate Local Area Connection icon and click Properties. 





7. Click Use the following IP address and fill in the fields as follows: 

a. Type the IP address for this workstation. Also write it into the appropriate row 

and column of the XPC L System Information part of the Worksheet provided 

with your system (see Table B–8 for an example of this table). Use Network IP 

address 1 for LAN 2 and use Network IP address 2 for LAN. 

b. Type the appropriate subnet mask into the Subnet mask box. 

c. Leave the fields Default gateway, DNS server, and Alternate DNS 

server blank. 

d. Click OK to close the Internet Protocol (TCP/IP) Properties window. 


9. Repeat steps 4 through 8 for the other network card (click the other Local Area 

Connection icon). 


Now, install the Sonic Record Now 7.1 Deluxe software and begin with the following 

procedure. 

6885 3522–003 5–35


Installing Microsoft .NET framework and .NET framework SP1 

Perform the following steps to install the Microsoft .NET framework and .NET 

framework SP1 from the XPC-L Firmware CD-ROM: 

1. Insert the XPC-L Firmware CD into the CD drive of the XPC-L Control Workstation. 

The installation application checks to see if the proper version of .NET Framework is 

installed. 

• If the proper version is installed, you do not receive any messages related to the 

installation of .NET Framework. In this case, cancel the XPC-L Control installation 


• If you receive an End User License Agreement (EULA) window about .NET 

Framework 1.1 setup, proceed to step 2. 

• If you receive a window asking if you want to install Microsoft .NET Framework 

Service Pack 1, proceed to step 5. 

2. Request a representative of the customer to perform the following steps to accept 

the EULA (A Unisys service representative is not authorized to perform this step): 

a. Read the license agreement, scrolling as necessary. 

b. Click I agree to accept the EULA. 

3. Click Install. 


4. Click Cancel to avoid installing XPC-L Control now (this step will be performed 

later). Proceed to step 5 to install Microsoft .NET Framework Service Pack 1. 

5. Click OK to continue with the Microsoft .NET Framework Service Pack 1 installation. 

6. Read through the End User License Agreement for .NET Framework SP1 and then 

click I accept. 

A message box appears indicating that all applications should be closed before 


7. Close all applications except the XPC-L Control installation application and then click 

Ignore to proceed with the installation. 

Status windows display the progress of the .NET Framework SP1 installation until 

the final window that indicates successful completion of the installation. 

8. Click OK. 

You see a message box about the need to restart your system for the configuration 

changes to take effect. 

9. Click Yes to restart your computer. 

5–36 6885 3522–003


Installing the Microsoft .NET framework 1.1 hot fix (KB896665) 

Perform the following steps to install the Microsoft .NET framework 1.1 hot fix 

(KB896665) from the XPC-L Firmware CD-ROM: 

1. Insert the XPC-L Firmware CD into the CD drive of the XPC-L Control Workstation. 

The installation application detects if the hot fix is installed. 

• If the hot fix is installed, you do not receive any messages related to the 

installation of the hot fix. In this case, cancel the XPC-L Control installation (this 

step will be performed later). 

• If you receive a window asking if you want to install Microsoft .NET Framework 

1.1 hot fix (KB896665), proceed to step 2. 

2. Click OK to continue with the Microsoft .NET Framework hot fix (KB896665) 

installation. 

3. Read through the End User License Agreement for the hot fix and then click I 

accept. 

Status windows display the progress of the .NET Framework SP1 installation until 

the final window that indicates that the installation was completed successfully. 

4. Click OK. 


5. Click Cancel to avoid installing XPC-L Control now (this step is performed later). 

6. To finish setting up your XPC-L Control Workstation, go to Section 2.2.2, “Preparing 

to Install XPC-L Software.“ 

6885 3522–003 5–37




1. Insert the latest Dell Resource CD-ROM into the drive. 


3. Restart the PC. 

The Startup dialog box appears. 


5. Select 1 Run the 32-bit diagnostics and press Enter. 


The Service tag dialog box appears. 


When Express Test completes successfully, click OK and close the dialog box. 


8. When the Startup dialog box appears, remove the CD-ROM from the drive and 

click Boot from hard drive. 

9. Reinsert the Dell Resource CD-ROM into the drive. Click OK to install from the 

CD-ROM. 

10. Click Next, and then click Finish. 

The Welcome dialog appears. 


The system searches for hardware. 

12. Reinstall the audio driver using the following steps: 

a. Click Audio Driver. 

b. Click Extract and follow the instructions to reinstall the driver. 

c. Click Continue. 

d. Click OK. 

e. Click Yes. 

f. Click OK. 

g. Click Next. 

h. Click NO, I will start my computer later. 

13. Reinstall the network driver using the following steps: 

a. Select the NIC driver (the Broadcom NetXtreme). 


c. Click Return when the reinstallation of the network driver finishes. 

5–38 6885 3522–003

14. Reinstall the video driver using the following steps: 

a. Click Video Driver to reinstall the video driver. 



15. Click YES, I want to restart my computer. 


17. After the computer has restarted, launch the Dell Resource CD-ROM. 

18. Reinstall the controller drivers using the following steps: 

a. Click Controller Drivers. 

b. Click Extract and follow the instructions to reinstall the drivers. 

19. When the InstallShield Wizard Complete dialog box appears, remove the 

Resource CD-ROM from the drive and turn off the computer (you have to disconnect 

power to reboot the computer). 

20. Turn on the computer to reboot it. 

21. Adjust properties of the window as needed. Right-click Desktop and click 

Properties. 





Control Workstation [Dell GX270 and GX280].“ 

6885 3522–003 5–39





executables: 


2. Switch to Classic mode on Control Panel using the following steps: 



c. On the General tab, under Tasks, click Use Windows classic folders. 

Click OK. 



5. Ensure the following check boxes are cleared: 








You can observe the progress of the removal of Windows components on the status 

windows. 

7. Click Finish when you receive a message indicating that the Windows component 

operation is successfully completed. 

Note: You may receive a message box during the process of removing of Windows 

components indicating that there is a Windows failure related to MSN Explorer. If 

you do see this message box, click OK. 



5–40 6885 3522–003







a. If the Security Center service does not have a status of Started, proceed to 

step 3c. 




e. Click the down arrow on Startup Type and select Disabled. 

f. Click OK. 


• Windows Firewall 

• Fast User Switching Compatibility 

• spkrmon 

• Application Layer Gateway 





Control Workstation [Dell GX270 and GX280].“ 

6885 3522–003 5–41


5.2.5.4. Verifying and Enabling CPU Hyper-Threading 

CPU hyper-threading must be enabled on XPC-L Control Workstations. 

Checking CPU Hyper-Threading State 

Perform the following steps to verify that CPU hyper-threading is enabled: 

1. Right-click the taskbar on an empty area and click Windows Task Manager. 

2. Select the Performance tab. 

3. On the View menu in the Windows Task Manager window, point to CPU 

History, and then click One Graph Per CPU. 

4. If there are two CPU Usage History graphs, hyper-threading is enabled on the 

workstation and no further action is required. Proceed to Step 5. 

If there is a single CPU Usage History graph displayed, hyper-threading is disabled on 

this workstation. Perform the steps to enable CPU hyper-threading. 

5. Close Windows Task Manager. 

Enabling CPU Hyper-Threading on Dell GX280 

Perform the following steps to enable CPU hyper-threading on a Dell GX280 workstation: 

1. Reboot the workstation and enter the BIOS setup by pressing F2 early in the reboot 

process. The appropriate time to press F2 is when you see DELL in large letters on 

the screen and the F2 setup option displayed in the upper right corner of the screen. 


2. Use the up and down arrow keys to highlight Performance Group in the left 

column of the window. 

3. Press Enter to view the fields in the Performance Group. 

4. Use the up and down arrow keys to highlight the Hyper-Threading field in the 

group. 

5. Press Enter to modify the workstation’s hyper-threading behavior. 

6. Use the left or right arrow keys to change the setting to On (On should be 

highlighted). 

7. Press Enter to complete the hyper-threading modification change. 

8. Press Esc to initiate the BIOS setup exit. 

9. Use the left or right arrow keys to select Save/Exit to save your changes and exit 

setup. 

10. Press Enter; the workstation reboots with CPU hyper-threading enabled. 

5–42 6885 3522–003

Enabling CPU Hyper-Threading on Dell GX270 


Perform the following steps to enable CPU hyper-threading on a Dell GX270 workstation: 




the screen. 


2. Use the up and down arrow keys to highlight CPU Information. 

3. Press Enter to view the fields in CPU Information. 

4. Use the up and down arrow keys to highlight the Hyper-Threading field. 

5. Press the space bar to modify the workstation’s hyper-threading behavior; change 

the setting to Enabled. 

6. Press Esc to complete the hyper-threading modification change. 

7. Press Esc to exit the BIOS setup. 

8. Use the left or right arrow keys to select Save Changes and Exit to save your 

changes and exit setup. 

9. Press Enter; the workstation reboots with CPU hyper-threading enabled. 

5.2.6. Changing Platform Software on the XPC-L Servers 

Refer to the following documents to reinstall Windows: 

• For an XPC-L server, refer to “2.2.1.2 Creating Partitions on the XPC-L Servers“ for 

the appropriate reference documents and procedures. 

• For the Dorado 200 Series servers, refer to ES7000 Model 550 and 560 32-Bit 

Environment Firmware and Server Sentinel Software Reinstallation Guide for 

procedures to reload Windows 2003, Enterprise Edition SP1. 

• For the Dorado 300 Series servers, refer to Appendix C, “Reinstallation of Windows 

2003 on XPC-L Servers“ for procedures to reload Windows 2003, Enterprise Edition 

SP2. 

Note: The only time you would usually need to reinstall Windows is when there is a 

problem with the system boot hard drive. 

6885 3522–003 5–43


5.2.7. Changing XPC-L Control Workstation Software 

This subsection describes how to update the XPC-L Control software on one or both 

XPC-L Control Workstations. You have to stop the XPC-L Control application on the 

workstation being updated. You do not have to stop the XPC-L services. The OS 2200 

hosts can remain running during the update procedure. The following procedure for 

updating XPC-L Control software on a workstation is for a system with both an active 

and a backup XPC-L Control Workstation and it assumes that the OS 2200 hosts remain 

running throughout the procedure. 

Before beginning the update procedure, perform the following steps: 

• Verify the current code versions that are running on the active and backup 

workstations. Click About on the Help menu on each XPC-L Control Workstation. 

• Keep ready the media for the currently installed plateaus, as well as the media for 

the plateau about to be installed. 

• Read the XPC-L System Firmware 2.2 Customer Reference Manual and Technical 

Information Bulletin for the new plateau to ascertain that it is compatible with the 

currently installed plateau. 

1. Refer to Section 6.4, “Removing XPC-L Control Workstation software“ and uninstall 

the current XPC-L Control software from the backup XPC-L Control Workstation. 

2. Refer to “2.2.3.1 Installing the XPC-L Control Software“ and install the new XPC-L 

Control software on the backup XPC-L Control Workstation. However, do not click 

the I would like to launch XPC-L Control check box. 

Note: This installs the XPC-L Control software on the XPC-L Control Workstation as 

well as copying the XPC-L service software to the XPC-L Control Workstation. 

However, the procedure in "Installing the XPC-L Control Software" does not install 

the XPC-L service software. 

3. Terminate XPC-L Control on the active XPC-L Control Workstation. 

This action results in an Exec console message on each OS 2200 host indicating that 

there has been a loss of resiliency in the XPC-L. 

Note: Do not delay in performing step 4 after completing step 3. Until an active 

XPC-L Control is running, a failure of either the master or slave service would result 

in all OS 2200 hosts going down. 

5–44 6885 3522–003


4. Start the XPC-L Control software on the backup XPC-L Control Workstation. This 

means the backup XPC-L Control Workstation has now become the active XPC-L 

Control Workstation and is now running the newly installed code. 

If the start fails to complete, you might receive an alert box indicating that the newly 

installed software is not compatible with the XPC-L service software. In this 

situation, you have to terminate XPC-L Control on the workstation. If the code levels 

are not compatible, drop back to the previously installed plateau, by starting XPC-L 

Control on the workstation that was the active XPC-L Control Workstation before you 

began the update procedure. Similarly, drop back to the previously installed plateau 

on the backup XPC-L Control Workstation. This can be done by performing steps 1 

and 2 with the original plateau media. 

Then shut down the entire system and perform the procedure described in “5.2.1 

Changing with a Complete Shutdown of the System.“ 

5. Verify that the new active XPC-L Control Workstation sees one XPC-L server as 

“Running as Master“ and the other XPC-L server as “Running as Slave.“ Also check 

the Log window to be certain there are no unusual messages that might indicate a 

problem. 

You now have two different code versions running on the active and backup XPC-L 

Control Workstations. You can continue to run this way for some time, but Unisys 

recommends that you upgrade the other workstation to the new plateau as soon as 

possible. The procedure is identical to that described above, but is to be performed on 

the other workstation. 

5.2.8. Changing XPC-L Server Software 

This subsection describes how to update the XPC-L software on one or both XPC-L 

servers. Stop the XPC-L service on the server being updated. If you purchased a 

non-redundant XPC-L system (that is, you only have a primary XPC-L server), stop all 

OS 2200 hosts connected to the XPC-L server and terminate the XPC-L server before 

beginning the update procedure. If you purchased a redundant XPC-L system, the 

OS 2200 hosts can remain running during the update procedure (assuming you are 

installing a compatible XPC-L software level). The following procedure for updating 

XPC-L software on a server is for a redundant XPC-L system and it assumes that the 

OS 2200 hosts remain running throughout the procedure. 

Note: This procedure only needs to be used if one is not documented in the XPC-L 

Customer Reference Manual or by your Unisys Support Personnel. 

6885 3522–003 5–45


Before beginning the update procedure, perform the following steps: 

• Verify the current code versions that are running on the primary and secondary 

servers. Click About on the Help menu on each XPC-L Control Workstation. 

• Keep ready media for the currently installed plateaus, as well as the media for the 

plateau about to be installed. 

• Read the XPC-L System Firmware 2.0 Customer Reference Manual and Technical 

Information Bulletin for the new plateau to be certain it is compatible with the 

currently installed plateau. 

• Keep ready the XPC-L Service user name, password, and license code for your 

system (see Table B–9 and Table B–10). 

1. Use the host console to bring down the XIIPs that have direct connect paths to the 

XPC-L server in which the software will be updated. 

2. If the XPC-L server on which the software will be updated is indicated as “Running 

as Master,“ click Switch Master/Slave on the Action menu. 

3. Click Terminate Slave on the Action menu. 

This action results in an Exec console message on each OS 2200 host indicating that 

there has been a loss of redundancy in the XPC-L. 

Note: This message does not appear in the case of XPC-L Firmware 2.2. 

4. Select the XPC-L server on which the software is to be updated. It should be the one 

indicated as Stopped. 

5. Click Uninstall XPC-L Software on the Tools menu. This action results in an 

alert box saying this action will cause the XPC-L service to be unusable. 


This action results in the service state being set to Service not found. 

7. Insert the XPC-L Firmware CD-ROM into the CD drive of the XPC-L Control 

Workstation. 

You might receive the uninstall setup window for XPC-L Control after inserting the 

CD. Click Cancel; do not uninstall XPC-L Control. 

8. Using Windows Explorer, copy all the files from the appropriate folder of the plateau 

about to be installed to the XPC-L Control Workstation folder. 

• If the software update is being performed on the primary XPC-L server, copy 

from the CD folder Program Files\Unisys\XPC-L Control\XPC-L-P to the XPC-L 

Control Workstation directory C:\Program Files\Unisys\XPC-L 

Control\XPC-L-P. 

• If the software update is being performed on the secondary XPC-L server, copy 

from the CD folder Program Files\Unisys\XPC-L Control\XPC-L-S to the XPC-L 

Control Workstation directory C:\Program Files\Unisys\XPC-L 

Control\XPC-L-S. 

This step overwrites the previously installed files in the folder. A message asks if you 

want to write over these files; click Yes for all. Then click each confirm file 

replace message that is displayed. 

5–46 6885 3522–003


9. Remove the XPC-L Firmware CD-ROM from the CD drive of the XPC-L Control 

Workstation. 

10. Click Install XPC-L Software on the Tools menu. Refer to Section 2.2.4, 

“Installing XPC-L Server Software“ for the various dialog boxes that appear during 

the installation of the XPC-L Server software. 

Note that at this time you will be installing the service only on this particular server, 

not onto both servers. 

Following the installation of the XPC-L software on the XPC-L server, the service 

state for the XPC-L server should now be Stopped. 

11. Click Start Slave on the Action menu. 

If the start operation fails to complete (that is, the service on the XPC-L server is not 

indicated as “Running as Slave“), check the Log window for a message indicating 

that the newly installed service is not compatible with the master XPC-L service. If 

the code levels are not compatible, you should drop back to the plateau that was 

previously installed on the slave. This can be done by performing steps 7 through 12 

with the original plateau media. 

The Start Slave command takes a few seconds to complete execution. You need 

to wait for the “Chargeup completed-redundant mode ENABLED” in the XPC-L 

Control log and for the server to say “Slave running as Slave.” 

Then shutdown the entire system and perform the procedure described in “5.2.1 

Changing with a Complete Shutdown of the System.“ 

12. Use the host console to bring up the XIIPs that were brought down in step 1. 

13. Click Switch Master/Slave on the Action menu. This results in the newly 

installed software being run under the master. The slave will run the software that 

was previously installed on its XPC-L server. 

You now have two different code versions running on the primary and secondary 

XPC-L servers. You can continue to run this way for some time, but Unisys 

recommends that you upgrade the other server to the new plateau as soon as 

possible. The procedure is identical to that described above, but is to be performed 

on the other XPC-L server. 

14. If the XPC-L system you purchased contains a backup XPC-L Control Workstation, 

perform steps 7 through 9 on the backup XPC-L Control Workstation to ensure that it 

has the same updates as the active XPC-L Control Workstation. 

5.2.9. Changing XPC-L Host Software 

There are two stages in the modification of the XPC-L host software: 

• Loading new XIIP microcode on the OS 2200 host system and installing it on the 

XIIPs in the configuration (see “5.2.9.1 Loading a New Version of XIIP Microcode“). 

• Modifying Operations Sentinel handling of any messages documented as changed 

from earlier releases as noted in “2.2.5.2 Operations Sentinel Message Text.“ 

6885 3522–003 5–47


5.2.9.1. Loading a New Version of XIIP Microcode 

XIIP microcode (in both the PCIOP-K and the PCIOP-D) is loaded during software 

installation. This subsection describes how XIIP microcode can be updated in an offline 

or online environment. 

Loading of XIIP microcode is performed as a plateau upgrade or as an emergency fix. 

This function allows the dynamic replacement of XIIP and VI channel microcode; it does 

not require the Exec be halted to load the microcode in an offline environment. 

A redundant path to affected devices must be available. You can perform the microcode 

load process while the XIIP is performing another activity; however, all activities on the 

XIIP must be stopped at the point where the flash memory is written. This operation 

takes two to three minutes, during which time no other I/O operation can be processed. 

A completion UPI interrupt is delivered by the IOP on successful burning of the flash 

memory. At this point, the reset of the device results in loading the new microcode for 

use. 

Online Loading of XIIP Microcode 

Online loading of XIIP microcode allows you to load the microcode while the Exec is 

running. 

You can invoke the loading of XIIP microcode by running the IOPUTIL utility from batch 

mode or from demand mode. 

Example 5-1 is an example of the console output seen during online loading of XIIP 

microcode. 

When more than one XIIP is available, the XIIP can be in the up partition state when you 

start the process of loading new XIIP microcode; otherwise, it must be in the down 

partition state. 

The MAINT operator keyin moves the XIIP from the down partition state into the UP/maint 

partition state explicitly for loading or dumping the XIIP. This keyin is valid only for the 

XIIP component. When the XIIP is in the UP/maint state, the Exec does not use the XIIP, 

but it is available for microcode to be loaded or for dumps of the XIIP to be taken. After 

the microcode load or dump is completed, the XIIP must be moved to the down partition 

state before it is allowed to be moved into the up partition state for active use. 

If the system stops when the XIIP is in MAINT mode, the XIIP remains in MAINT mode 

when the partition is rebooted. If the XIIP state is moved from UP to DOWN by the 

operator at the System Control Facility while the system is stopped, the MAINT mode is 

cleared when the partition is rebooted. 

Issue the following keyin for the target XIIP to check the current level of its microcode: 

IT iopinq,xiip_name 

5–48 6885 3522–003

The following is an example of the resultant output: 


COMPONENT XIP05 MICROCODE: 03.36.00 HARDWARE: 78-RLP 

Perform the following steps to load new XIIP microcode: 

1. Issue the DN keyin to the XIIP for which you want to load new XIIP microcode. 

DN xiip_name 

where the xiip_name is the XIIP which requires microcode loading or dumping. 

2. Issue the MAINT keyin to move the XIIP from the down state into the UP/maint 

partition state. 

MAINT xiip_name 

Notes: 

• When the MAINT xiip_name keyin completes, the status reported on the system 

console is UP MT. An FS keyin shows the XIIP in the UP MT state. 

For example: 

FS XIP44 

XIP44 UP MT 

FS,XIIP 

XIP44 UP MT, XIP45 UP 

• If the MAINT xiip_name keyin is entered when the XIIP is not in the down partition 

state, the following message is displayed: 

"xiip_name must be DN when the MAINT keyin is entered." 

• If a MAINT request is entered for a non-XIIP component, the following message 

is displayed: 

"MAINT keyin invalid for logical name component_name, input ignored." 

• If a MAINT keyin is entered for an XIIP already in the MAINT partition state, the 


"MAINT keyin already performed for xiip_name." 

• An FS keyin of the XIIP performed after IOP load has started provides an 

indicator on the FS display that a microcode load is currently in progress. 

• UP or DN keyins affecting an XPC-L component while the IOP load is in progress 

are not allowed and a message will indicate this. 

3. Run the IOPUTIL utility. 

6885 3522–003 5–49


Batch Mode 

To invoke the loading of XIIP microcode in batch mode, type the following on an 

OS 2200 console: 

ST IOPUTIL[,,,acct/userid] 

Note: You must have the SSADHMCODE privilege to load XIIP microcode this 

way. 

The IOPUTIL utility runs with default options of I and S. Console messages request 

input. Only information required to be input and any error or necessary informational 

messages are displayed on the console. A debug file, IOPUTL*OUTPUT, is kept that 

contains all collected debug information. Each time the IOPUTIL run is started, the 

debug file is overwritten. 

The IOPUTIL utility requests the name of the component to load. After this, you have 

a choice of specifying either a microcode file already located in mass storage or a 

microcode file located on tape. 

Additional questions are asked based on the specific location of the source 

microcode file to gain the information required to load microcode onto an XIIP. Only 

the file name of the microcode file is required if a mass storage file is being used: 

Enter the Component Name to Load: 

IOP01 

Load micro-code from Tape or File? |F: 

F 

Enter the file name of the micro-code to load: 

TEST*MCODE. 

Otherwise, the information required to retrieve the microcode file includes the tape 

ID of the tape containing the microcode, the tape assign options for the specified 

tape id, the device type to load the specified tape, and the file number of the 

microcode file on the specified tape. For example: 

Enter the Component Name to Load: 

IOP01 

Load micro-code from Tape or File? |F: 

T 

Enter the Tape ID that contains the micro-code to load: 

18400C 

Enter the tape assign options |TF: 

TF 

Enter the tape device type : 

HICL 

Enter the File Number on the tape containing 

the Micro-Code to load. 

2 

Note: The first file on a tape would be 1. 

5–50 6885 3522–003


File Micro-Code version = 02.18.00 

Inquiry completed Successfully 

Inquiry Micro-Code version = 02.21.00. 

Continue with the Micro-Code Load process? Y|? 

Y 

Setup completed Successfully 

File Transfer completed Successfully 

Flash completed Successfully 

Reset completed Successfully 

Release completed Successfully 

Note: File Micro-Code version indicates the version of the code currently 

installed and Inquiry Micro-Code version indicates the version of the code being 

installed. 

Console messages convey only required output, as shown in the preceding example. 

The Debug output is written to a debug file. 

The following debugging options are available for the IOPUTIL utility: 

A 

D 

I 

This option performs the steps of the microcode load process one at a time with 

a query between each. This option allows a step-by-step activity. If this option is 

not specified, the entire process is completed without interaction with the 

administrator. 

This option displays the options available and the instructions on how to start the 

utility in demand mode. 

This is the default option and performs the inquiry request for the specified 

component. If this option is not included, the inquiry step is skipped and 

processing starts with the component setup step after the microcode has been 

retrieved. 

Demand Mode 

In demand mode, any option can be specified on the call line. The MCLOAD 

processor resides in the released SYS$*LIB$ file. 

To invoke the loading of XIIP microcode from a demand session, type the following 

on an OS 2200 console: 

@SYS$*LIB$.MCLOAD,options 

The input is queried from the screen and all output is displayed there as well. The 

debug file is not created in this mode of operation. 

6885 3522–003 5–51


Options 

The following debugging options are available for the MCLOAD processor: 

A 

D 

F 

I 

L 

S 

This option performs the steps of the microcode load process one at a time 

displaying a query between each. It thus allows for a step-by-step activity. If this 

option is not specified, the entire process is completed without interaction with 

the administrator. 

This option displays the options available and the instructions on how to start the 

utility in Demand mode. 

This option displays debug information regarding the microcode file only. 

This is a default option and performs the inquiry request for the specified 

component. If this option is not included, the inquiry step is skipped and 

processing starts with the component setup step after the microcode has been 

retrieved. 

This option displays full debug listings. This includes all debug statements for 

any action taken. 

This is a default option and displays short debug listings. This displays only highly 

relevant information, including status of each step completed during processing. 

4. Issue the DN keyin to the XIIP for which you just loaded new XIIP microcode. 

DN xiip_name 

where xiip_name is the XIIP that requires microcode loading or dumping. 

5. Issue the UP keyin to the XIIP for which you just loaded new XIIP microcode to move 

the XIIP back into the partition for system use. 

UP xiip_name 

5–52 6885 3522–003


EXEC IOPUTIL to load U-code on the PCIOPK for XPCL. 

fs,xpc 

XPCL1A UP MHM 

HOST A active XIP04 XIP05 XIP14 XIP15 

HOST B active XIP23 XIP25 XIP22 XIP24 

it iopinq,xip05 




st ioputil,,,0/security 

1-ENTER C.L. FOR : .IOPUTIL 

1 

1 

IOPUTL START 

1-IOPUTL*Enter the Component Name to Load: 

2-ANSWER WITH REEL NO ON T73A1 E,REEL 

dn xip04 

maint xip04 

XIP04 DN 

XIP04 UP MT 

1 xip04 

1 

1-IOPUTL*Load micro-code from Tape or File? |F: 

1 

1 

1-IOPUTL*Enter the Tape ID that contains the micro-code to load: 

1 PCI643 

1 

1-IOPUTL*Enter the tape assign options |TF: 

2 PCI643 

2 

1 

1 

1-IOPUTL*Enter the tape device type : 

1 

1 

IOPUTL*Enter the File Number on the tape containing 

IOPUTL*the Micro-Code to load. 

1-IOPUTL* (ie. The first file on a tape would be 1.) 

Example 5–1. Online Loading of XIIP Microcode—Console Output 

6885 3522–003 5–53


1 2 

1 

T73A1 IS SELECTED PCI643 MCTAPE - 1 IOPUTL 

IOPUTL*Micro-Code File Type is (2). 

IOPUTL*File Micro-Code version = 03.36.00 

IOPUTL*Inquiry completed successfully. 

IOPUTL*Inquiry Micro-Code version (XIP04 ) = 03.35.00 

1-IOPUTL*Continue with the Micro-Code Load process? Y|? 

1 y 

1 

IOPUTL*Setup completed successfully. 

IOPUTL*File Transfer completed successfully. 

IOPUTL*Flash request started; maximum delay 4 minutes 0 seconds. 

fs,xpc 


HOST A active XIP05 XIP14 XIP15 


IOPUTL*Flash completed successfully. 

dn xip04 

DN of XIP04 not allowed while Load-Microcode operation is active. 

XIP04 UP MT 

IOPUTL*Reset completed successfully. 

IOPUTL*Release completed successfully. 

IOPUTL*Micro-code load program complete for component XIP04 

IOPUTL FIN 

dn xip04 

XIP04 DN 

up xip04 

XIP04 UP 



fs,xpc 


HOST A active XIP04 XIP05 XIP14 XIP15 


Example 5–1. Online Loading of XIIP Microcode—Console Output 

(continued) 

5–54 6885 3522–003

Offline Loading of XIIP Microcode 


Offline loading of XIIP microcode allows you to load the microcode before booting the 

Exec. 

Example 5-2 is an example of the console output seen during offline loading of XIIP 

microcode. 

Issue the following command to check the current level of microcode for all XIIPs in the 

system: 

SIOREV 

The following is an example of the resultant output: 

XIP05 FIRMWARE: 03.36.00 HARDWARE: 78-RLP 



You invoke the offline loading of XIIP microcode from SUMMIT using these steps: 

1. Booting with Summit requires the XPC-L be in a Test Partition and not in a 

Production Partition. Click Start XPC-L in Test Partition on the Tools menu. 

2. Boot SUMMIT from the appropriate CC7000, CC7200, CC7400 or CC8000 tape for 

your system. 

3. Load the DSPER tape, then enter one of the following to run the appropriate epts 

command: 

Dorado 200 Series server: Xqt aaa epts 

Dorado 300, 700, 4000 Series server: Xqt,a aaa epts 

Note: The minimum level of DSPER for this level is 9R4Q2. 

4. Respond to the input prompts with IOULOD path (where path is the IOP name). 

5. Respond appropriately to the prompts that follow (mount tape, and so on). 

A window shows the microcode level to be loaded and the current level installed. 

6. Respond C to continue and load the new code. 

7. WAIT messages are displayed while the code is burning. 

The operation is complete when you see the Unit Released message. You can now run 

XSTRESS to test the microcode or reboot and run the system. 

Note: For this release there is one version of XSTRESS for the Dorado 200,300,700 

(1R24T1) and another for the Dorado 4000 (1R25-14). 

6885 3522–003 5–55


summit 

EXE ****************************************************************** 

* Revision - 13R5L Build date - 11/01/04 * 

------------------ XIIPs Available ------------------ 

Name UPI number Control table IOP type State 

XIP04 404 000005010100 SIO-RLP3 UP 

XIP05 405 000005030100 SIO-RLP3 UP 

XIP14 414 000005140100 SIO-RLP3 UP 

XIP15 415 000005160100 SIO-RLP3 UP 

--- End List --- 

xqt iou epts 

>XQT IOU EPTS 13:02:39 

EXE IOU Loaded, PAR = 4,00136,001025 (000012120025) Date = 11/01/04 

Name: EPTS Version: 110104 PCT = 000005270000 

IOU USE X HELP CALL FOR THE SRL UNAME CALL LINE FEATURE 13:03:03 

IOU X = TYPE AND READ PROMPT 13:03:03 

IOU PATH SELECTION FROM AVAILABLE PATHS IS NOW SUPPORTED 13:03:03 

0-IOU*EPTS: MORE? 13:03:04 

0 ioulod xip15 

>0 IOULOD XIP15 13:03:14 

0 

0-IOU*EPTS: MORE? 13:03:14 

IOU IOULOD XIP15 REV 3R1.030903 TEST START 13:03:15 

1-IOU*XIP15 ENTER UNIT NAME OF DEVICE CONTAINING MICROCODE TAPE 13:03:15 

1 t73a1 

>1 T73A1 13:03:32 

1 

IOU ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13:03:38 

IOU MICROCODE TAPE LEVELS -- 13:03:38 

IOU MICROCODE ID 78 13:03:39 

IOU MICROCODE REVISION LEVEL 03.36.00 13:03:39 

IOU BYTE TRANSFER COUNT 03428740 13:03:39 

IOU ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13:03:40 

IOU PCIOP-K4RLP3 03.35.00 13:03:40 

IOU ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 13:03:40 

IOU IOP FIRMWARE WILL BE UPDATED WITH REV LEVELS FROM TAPE 13:03:40 

1-IOU*XIP15 (C)ONTINUE DLL OR (T)ERMINATE. C,T 13:03:40 

Example 5–2. Offline Loading of XIIP Microcode—Console Output 

5–56 6885 3522–003


1 c 

>1 C 13:04:05 

1 

IOU MICROCODE TRANSFER TO IOP COMPLETED - MICROCODE BURN ISSUED PLEASE 

IOU PLEASE WAIT - MAX BURN TIME = 240 SECONDS 13:04:11 

IOU XIP15 MICROCODE BURN COMPLETED. 13:06:45 

IOU IOULOD T 2 XIP15 PATH 00/00/00/ 0/00 13:06:45 

IOU TEST COMPLETE : 13:06:46 

IOU 13:06:46 

IOU TOTAL PASSES OF TEST = 1 13:06:46 

TOTAL I/O OPERATIONS = 7 

TOTAL TEST I/O TIME = 0 HOURS 0 MINUTES 0 SECONDS 

INITIAL TIME TO TEST = 99 HOURS 0 MINUTES 0 SECONDS 

TIME FOR LAST I/O = 0 MILLISECONDS 

AVERAGE TIME/FUNCTION = 0 MILLISECONDS 

READ BYTES XFERED = 0 

WRITE BYTES XFERED = 3428740 

I/O TRANSFER RATE = 0 I/OS PER SECOND 

IOU XIP15/0 DEVICE ERRORS ENCOUNTERED 13:06:47 

0 RECOVERABLE STATUS ERRORS 

0 NON-RECOVERABLE STATUS ERRORS 

0 I/O TIME OUT STATUS ERRORS 

0 VERIFY ERRORS 

IOU IOP RESET ISSUED - PLEASE WAIT 13:06:48 

IOU IOULOD XIP15 UNIT RELEASED 13:07:05 

Example 5–2 Offline Loading of XIIP Microcode—Console Output (continued) 

6885 3522–003 5–57


Testing XIIP Microcode with XSTRESS 

The XSTRESS program is normally run only to verify hardware or configuration changes 

before using the XPC-L system in a production environment. 

To run XSTRESS, click Start XPC-L in Test Partition on the Tools menu to start the 

services for the XPC-L servers. 

After loading the XSTRESS jobs to run, xqt aaa runs the job. 

Before executing an instance of XSTRESS the status timer also needs to be disabled in 

XSTRESS. The following is an example of the keyins to load, disable status timer, and 

execute XSTRESS: 

LOD aaa XSTRESS 

SPEC aaa 

STMRY0 TER 

XQT aaa 

Example 5-3 is an example of the console output you see while running XSTRESS. The 

stmry0 ter you see in Example 5-3 disables the status timer; this is performed for each 

of the jobs loaded. 

5–58 6885 3522–003


>LOD AAA,BBB,CCC,DDD XSTRESS 10:11:35 

EXE AAA Loaded, PAR = 4,00125,100054 (000050170054) Date = 02/03/03 

Name: XSTRESS Version: 1R19T212 PCT = 000045700000 

EXE BBB Loaded, PAR = 4,00125,100054 (000050770054) Date = 02/03/03 


EXE CCC Loaded, PAR = 4,00125,100054 (000051300054) Date = 02/03/03 


EXE DDD Loaded, PAR = 4,00125,100054 (000051610054) Date = 02/03/03 


spec aaa 

>SPEC AAA 10:11:48 

EXE AAA ACTIVATED PAR=4,00125,100044 (000050170044) 10:11:48 

AAA 10:11:48 

XPC Stress Test REV 1R19T212 

Enter Directive (or Help) 

stmry0 ter 

Enter Directive (or Help) STMR - Status Timer 

Status timer is currently Enabled 

Change (Y or N) ? Yes 

Enter new status timer value (0 = DISABLE, OCTAL 1-77) 0 

Status timer is now Disabled 

Enter Directive (or Help) TER - Terminate Parameterization 

EXE AAA TERMINATED PAR=4,00116,010241 (000045640241) VIA ER SPEND$ . 

spec bbb 

>SPEC BBB 10:11:58 

EXE BBB ACTIVATED PAR=4,00125,100044 (000050770044) 10:11:58 

BBB 10:11:58 



stmry0 ter 







EXE BBB TERMINATED PAR=4,00116,010241 (000050310241) VIA ER SPEND$ . 

spec ccc 

>SPEC CCC 10:12:05 

EXE CCC ACTIVATED PAR=4,00125,100044 (000051300044) 10:12:05 

CCC 10:12:05 



Example 5–3. Running XSTRESS—Console Output 

6885 3522–003 5–59


stmry0 ter 







EXE CCC TERMINATED PAR=4,00116,010241 (000051120241) VIA ER SPEND$ 

spec ddd 

>SPEC DDD 

EXE DDD ACTIVATED PAR=4,00125,100044 (000051610044) 

DDD 10:12:10 



stmry0 ter 







EXE DDD TERMINATED PAR=4,00116,010241 (000051430241) VIA ER SPEND$ 

xqt all 

>XQT ALL 10:12:49 

EXE AAA ACTIVATED PAR=4,00125,100054 (000050170054) 10:12:49 

AAA 10:12:50 

Starting XPC Stress Test REV 1R19T212 

Host Processor Type: 2200/8010 

EXE BBB ACTIVATED PAR=4,00125,100054 (000050770054) 10:12:51 

BBB 10:12:51 



EXE CCC ACTIVATED PAR=4,00125,100054 (000051300054) 10:12:52 

AAA 10:12:52 

File size is now 000312 

Minimum file size always 

Nailed file space is ENABLED for RLP3 

RLP3 Default Setup Complete 

Data Mover UPI 404 Initialized As Host ID 11 

EXE DDD ACTIVATED PAR=4,00125,100054 (000051610054) 10:12:54 

CCC 10:12:55 




5–60 6885 3522–003


BBB 10:12:56 






DDD 10:12:58 



AAA Expanding dynamic banks 10:12:59 

CCC 10:12:59 






BBB Expanding dynamic banks 10:13:02 

DDD 10:13:02 

Data Mover Failed To Initialize 

AAA Initializing dynamic banks 10:13:03 

EXE DDD DACT$ ERROR PAR=4,00115,000255 (000051360255) VIA ER EXIT$ . 

EVENT ASA = 001400 

LAST ASP (IP01) PAR= 400115000255 DES-REG= 000030000000 

IKR= 010014200005 QT= 377777777777 

F0= 105400130016 ISW0= 000000000011 

ISW1= 000000000000 ISW2= 000000000000 

CCC Expanding dynamic banks 10:13:05 

BBB Initializing dynamic banks 10:13:05 

AAA Starting host interface 10:13:06 

BBB Starting host interface 10:13:06 

CCC Initializing dynamic banks 10:13:07 

AAA Host interface is active 10:13:07 

BBB Host interface is active 10:13:07 

CCC Starting host interface 10:13:07 

AAA INFO:Performance Monitor Enabled 10:13:08 

BBB INFO:Performance Monitor Enabled 10:13:08 

CCC Host interface is active 10:13:08 

AAA Initialization complete 10:13:09 

BBB Initialization complete 10:13:09 

AAA 10:13:10 


6885 3522–003 5–61


PERFORMANCE MONITOR CONFIGURATION: 

Number of NVSMs = 1 

Number of HIAs = 2 

Number of IXPs = 6 

NVS Size (MW) = 320 

BBB INFO:Perf Monitor Already Active On Interface 12 10:13:12 

CCC Initialization complete 10:13:12 

AAA 10:13:12 

Message Session Established For Host ID 11 

BBB 10:13:13 



CCC 10:13:14 




AAA 10:13:16 



BBB 10:13:17 


AAA INFO:Nail Space Full 10:13:21 

CCC INFO:Nail Space Full 10:13:22 

BBB INFO:Nail Space Full 10:13:22 



BBB INFO:Nail Space Full 10:13:24 




5–62 6885 3522–003

Section 6 

Deinstallation 

This section describes how to remove the XPC-L Control and XPC-L Server software. 

6.1. Overview 

The following are the general steps for deinstalling XPC-L software: 

1. Migrate concurrent applications to local applications (“idle“ all applications, perform a 

short recovery on all hosts). Refer to the Extended Transaction Capacity Planning, 

Migration, and Operations Guide for specific instructions for migrating concurrent 

applications to local applications. 

2. If your environment will not be using file sharing, refer to the Multi-Host File Sharing 

(MHFS) Planning, Installation, and Operations Guide for instructions for removing 

MHFS. Then continue with step 3. 

If your environment will be using the network communication method of file sharing, 

continue with step 3. 

2. Stop the hosts, XPC-L servers, and XPC-L Control Workstations. 

3. Remove the XPC-L software from the hosts (see Section 6.2, “Removing XPCEXEC 

Software“), XPC-L Servers (see Section 6.3, “Removing XPC-L Server Software“), 

and XPC-L Control Workstations (see Section 6.4, “Removing XPC-L Control 

Workstation Software“). 

6885 3522–003 6–1


6.2. Removing XPCEXEC Software 

The following procedure describes how to remove the XPCEXEC feature (see “Installing 

Exec Features“ under Section 2.2.5, “Installing XPC-L Host Software“) and how to 

remove the XPC-L product from the host configuration for the cases of continuing to use 

MHFS and not continuing to use MHFS. 

1. Use the DEINSTALL statement to deinstall the XPCEXEC feature. 

DEINSTALL XPCEXEC FEATURE 

Note: This requires at least a Master Configuration Table (MCT) generation. For 

other information about deinstalling features and building system tapes refer the 

Exec Installation and Configuration Guide. 

2. The deinstallation of the XPC-L product depends upon the intended usage of MHFS 

following the deinstallation of the XPC-L product. 

• If the system will continue to use MHFS after the XPC-L is removed, then the 

MHFS interhost communication mechanism must be switched from an XPC-L 

configuration to a network configuration. To accomplish this, perform the 

following steps: 

a. Stop all hosts at the same time. 

b. Reboot all hosts to a system with the XPCEXEC feature deinstalled. The 

network configuration that will be used by MHFS must be available during 

the reboot. 

• If the system will discontinue use of MHFS and remove the XPC-L at the same 

time, then the deinstallation process can be done one host at a time. To 

accomplish this 

a. Take down MHFS on the host that will be rebooted. 

b. Reboot the host to a system with the XPCEXEC, MHFS, and XTC features 

deinstalled. Refer the Exec Installation and Configuration Guide for other 

information about deinstalling features and building system tapes. 

Refer to the Multi-Host File Sharing (MHFS) Planning, Installation, and Operations Guide 

for detailed information about the MHFS environment and for additional background and 

procedures to use when switching from an XPC-L interhost communication configuration 

to a network interhost communication configuration. 

6–2 6885 3522–003

6.3. Removing XPC-L Server Software 


To remove the XPC-L Server software from the XPC-L Control Workstation, click 

Uninstall XPC-L Software on the Tools menu. This removes the XPC-L Server 

software from the selected XPC-L server. 

To remove the XPC-L Server software from both XPC-L servers, repeat the procedure for 

the second XPC-L server. 

6.4. Removing XPC-L Control Workstation 

Software 

Removing the XPC-L Control software can be initiated on any workstation that has the 

XPC-L Control software installed. 

You can remove XPC-L Control Workstation software in the following ways: 

• By double-clicking the Add/Remove Programs icon in the Windows Control 

Panel. After locating the XPC-L product in the list of products, click 

Change/Remove to initiate the maintenance application and display the Confirm 

Uninstall window. 

• By using the XPC-L Control Workstation installation software CD. 

a. Execute the setup.exe file on the installation CD by loading the CD to evoke the 

autorun.inf file or by double-clicking the setup.exe file from Windows Explorer. 

When setup runs, it displays a Confirm Uninstall window. 

b. Click OK to remove the XPC-L Control software. 

The Maintenance Complete window is displayed when the uninstallation is 

complete. 

c. Click Finish to continue. 

Remove deletes the installed files, the registry entries, and any icons or 

shortcuts that were installed. 

Note: Remove does not delete the XPC-L configuration file, the state file, any 

dumps, or any logs. 

6885 3522–003 6–3


6–4 6885 3522–003

Section 7 

Maintenance for XPC-L Systems 

This section provides instructions for periodically removing old files from the XPC-L 

Servers, XPC-L Workstations and Service Processors. 

7.1. Maintaining XPC-L Servers 

The XPC-L Windows servers do not require periodic reboot to optimize hard disk space. 

Maintenance can be done at the customer's discretion and, or every three to six months 

and should be done during normal preventative maintenance, when the system usage is 

minimal. Once this has been done, your disks will not become fragmented unless 

multiple dumps and log files are generated over time. You should always run the Analyze 

function for disk defragmentation before running the Disk Defragmenter utility. 

You can do the following for maintenance: 

• Deleting old XPC-L dump files 

• Deleting old log files 

Deleting Old XPC-L Dump Files 

Old XPC-L dump files on the XPC-L Servers would be present in the XPC-L Share 

directory of the primary and secondary XPC-L Servers. The following example shows a 

folder with two zip files which is the result of taking a manual dump. 

Example of a dump folder and associated files to be deleted: 

DUMP P-080422133733 

Dump P-080422133733.zip 

XPC-L Log.zip 

The following example shows only a zip file which is the result of an automatic dump 

being taken due to a server failure. 

Example of a dump folder to be deleted: 

DUMP P-080421760323.zip 

6885 3522–003 7–1


Deleting Old Log Files 

You can also remove any old log files present on the XPC-L Servers. While removal is 

possible, it is recommended that you retrieve the file from the server using active XPC-L 

Control Workstation for copying on to DVD media for future reference. This file also 

exists in the XPC-L Share directory of the primary and secondary servers. 

An example of the old log file is XPC-L LOG080221030230.txt. 

The current log file is named XPC-L LOG.txt which cannot be deleted. 

Once you have removed all the files from your server, ensure that the server is “Running 

as Slave.“ If it is not running as the slave, perform a “Switch Master/Slave“ operation 

from the active XPC-L control PC. You can now run the Disk Defragmenter utility. 

7.2. Maintaining XPC-L Workstations 

Another possible maintenance activity is to clean up the old log files and dump files on 

the XPC-L Control Workstation. If you have both an active and a backup control 

workstation perform maintenance on the backup Control Workstation first. Once 

maintenance on the backup control workstation is completed, start XPC-L control on it 

and take control away from the active XPC-L Control Workstation. You can now perform 

maintenance on the other Workstation. This way you also check the functionality of your 

backup XPC-L Control Workstation occasionally. 

The XPC-L dump files that can be removed are in the root directory or in a folder that 

was defined by the customer. 

Example of a file to be deleted: DUMP P-080421760323.zip. 

You can also remove any old XPC-L log files that have been copied to the XPC-L Control 

Workstations. 

Example of an old log file: XPC-L LOG080221030230.txt. 

You can also remove any of the old XPC-L control log files. While these can be removed 

it is good practice to keep these on DVD media for future reference. These files are 

located in the root directory or in a pre- defined folder. 

Example of an old XPC-L control log file: XPC Control Log 08042221330330.txt. 

You can also remove any XPC-L Control Mini-dump files. These files are in the directory 

c:/XPCControl MiniDump. 

7–2 6885 3522–003

Example of a dump folder and associated files to be deleted: 

Dump C-080423040331 

DUMP C-080423040331.zip 

XPCControl.zip 

You can now run the Disk Defragmenter utility. 


7.3. Maintaining XPC-L Service Processors 

Refer to the following documents for maintenance procedures. 

• For the Service Processors on a Dorado 200 based system, follow the Maintenance 

procedures in the Plateau 2.2 Definition Reference Manual (7862 6447). 

• For the Service Processors on a Dorado 300 based system, follow the Maintenance 

procedures in the Hardware Platform Definition Reference Manual Firmware 1.4 

(3850 7828). 

6885 3522–003 7–3


7–4 6885 3522–003

Appendix A 

Setting Windows User Names and 

Local Security Policies 

A.1. Creating a New User Name 

To create a new user name, perform the following steps: 

1. On Control Panel, double-click Administrative Tools, and then double-click 

Computer Management. 

2. Under Local Users and Groups, click Users. 

3. Click Action. 

4. Click New User on the Action menu. 

5. Type the desired values in the User name and Password boxes (Full name and 

Description are optional). 

The password must be longer than six characters. 

6. Clear the User must change password at next logon check box and click 

Password never expires. 





9. Click Create. 

10. Click Close. 

To add the new user name to the Administrators group, perform the following steps: 

1. Under Local Users and Groups, click Groups. 

2. Double-click Administrators. 

3. Click Add. 

4. Type the user name defined in the above step 5 and click OK. 

5. Click Apply, and then click OK. 

6885 3522–003 A–1

Setting Windows User Names and Local Security Policies 

A.2. Setting User Rights Assignments 

To check or set a user rights assignment, perform the following steps: 

1. On Control Panel, double-click Administrative Tools, and then double-click Local 

Security Policy. 

2. Under Local Policies, click User Rights Assignment. 

3. Double-click the desired rights in the right pane. 

4. Click Add User or Group. 

5. Type the user name and click OK. 


7. Repeat steps 1 through 6 to check or set each desired right. 

Note: Reboot the server to make any changes effective. 

A.3. Setting Security Options 

To check or set a security option, perform the following steps: 

1. On Control Panel, double-click Administrative Tools, and then double-click Local 

Security Policy. 

2. Under Local Policies, click Security Options. 

3. Double-click the desired security option and update the setting. 


Note: Reboot the server to make any changes effective. 

A–2 6885 3522–003

Appendix B 

Example XPC-L Server PCI Locations 

Charts and Worksheets 

Manufacturing determines the slots in which VI cards and network cards should be in 

the XPC-L servers. The cards should be installed in these slots only, and the VI cards 

should be used only for the indicated function (direct connect host, crossover, and 

synchronization paths). 

While the VI card placement in the XPC-L server must remain as documented in this 

appendix, XPC-L master/slave configurations that have only one interface between each 

XPC-L server and each host may alter the host destination of a direct connect path. For 

example, secondary server direct connect path 01 (S-DC01) interfacing to host B instead 

of host A. For fully redundant XPC-L configurations with two interfaces between each 

host and each server, we strongly recommend that you follow the host interface scheme 

documented in this appendix. 

For Dorado 300 Series servers, Table B–1 shows the placement of the VI cards and 

network cards in the XPC-L server when looking from the back (left part of the server). 

Table B–2 and Table B–3 show the placement of the cards in the XPC-L server when 

looking from the back (right part of the server). This chart also identifies the MAC 

addresses of the network cards. 

For Dorado 200 Series servers, Table B–4 and Table B–6 show the placement of the VI 

cards and network cards in the XPC-L server when looking from the front. Table B–5 and 

Table B–7 shows the placement of the cards in the XPC-L server when looking from the 

back. This chart also identifies the MAC addresses of the network cards. 

Manufacturing also provides a worksheet (Table B–8, Table B–9, and Table B–10) to help 

you create user names and security settings. The worksheet also contains the license 

code for your XPC-L system. 

6885 3522–003 B–1

Example XPC-L Server PCI Locations Charts and Worksheets 

C 

E 

L 

L 

3 

C 

E 

L 

L 

2 

C 

E 

L 

L 

1 

C 

E 

L 

L 

0 

Table B–1. Dorado 300 Series Servers: Primary or Secondary XPC-L Server 

(Back View, Left 2/3) 

Ethernet 

(not used) 

Ethernet 

(not used) 

Ethernet 2 

Ethernet 1 

Ethernet 

(not used) 

Ethernet 

(not used) 

Maintenance 

LAN (optional) 

Maintenance 

LAN 0 

B–2 6885 3522–003

C 

E 

L 

L 

3 

C 

E 

L 

L 

2 

C 

E 

L 

L 

1 

C 

E 

L 

L 

0 

DC06 

Path 2 


Table B–2. Dorado 300 Series Servers: Primary XPC-L Server 

(Back View, Right 1/3—Expanded) 

PCI Bus 3 PCI Bus 4 PCI Bus 5 PCI Bus 6 PCI Bus 7 

Host C 

DC05 

Path 1 

Host C 

DC02 

Path 2 

Host A 

DC01 

Path 1 

Host A 

C06 

Path 2 

Host C 

C05 

Path 1 

Host C 

C02 

Path 2 

Host A 

C01 

Path 1 

Host A 

S04 

Path 4 

S03 

Path 3 

S02 

Path 2 

S01 

Path 1 

DC08 

Path 2 

Host D 

DC07 

Path 1 

Host D 

DC04 

Path 2 

Host B 

DC03 

Path 1 

Host B 

6885 3522–003 B–3 

C08 

Path 2 

Host D 

C07 

Path 1 

Host D 

C04 

Path 2 

Host B 

C03 

Path 1 

Host B


C 

E 

L 

L 

3 

C 

E 

L 

L 

2 

C 

E 

L 

L 

1 

C 

E 

L 

L 

0 

DC06 

Path 4 

Table B–3. Dorado 300 Series Servers: Secondary XPC-L Server 

(Back View, Right 1/3—Expanded) 

PCI Bus 3 PCI Bus 4 PCI Bus 5 PCI Bus 6 PCI Bus 7 

Host C 

DC05 

Path 3 

Host C 

DC02 

Path 4 

Host A 

DC01 

Path 3 

Host A 

C06 

Path 4 

Host C 

C05 

Path 3 

Host C 

C02 

Path 4 

Host A 

C01 

Path 3 

Host A 

S04 

Path 4 

S03 

Path 3 

S02 

Path 2 

S01 

Path 1 

DC08 

Path 4 

Host D 

DC07 

Path 3 

Host D 

DC04 

Path 4 

Host B 

DC03 

Path 3 

Host B 

B–4 6885 3522–003 

C08 

Path 4 

Host D 

C07 

Path 3 

Host D 

C04 

Path 4 

Host B 

C03 

Path 3 

Host B

S 

u 

b 

D 

I 

B 

1 

S 

u 

b 

D 

I 

B 

2 

S 

u 

b 

D 

I 

B 

3 


Table B–4. Dorado 200 Series Servers: Primary XPC-L Server (Front View) 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

Intel Subpod 1 

(not used) 


(4 IPs) 

DOMAIN 0 DOMAIN 1 (not used) 

POD 0 POD 1 (not used) 

MSU 2 (4GB) MSU 3 

(not used) 


(not used) 


(not used) 

DIB 1 DIB 0 DIB 1 (not used) DIB 0 (not used) 

DC06 (direct connect) 

Path 2 

Host C 


Path 2 

Host A 


Path 2 

Host D 


Path 2 

Host B 

Ethernet 

(maintenance) 


Path 1 

Host C 


Path 1 

Host A 


Path 1 

Host D 


Path 1 

Host B 

(not used) (not used) 




(not used) SCSI (not used) (not used) 

(not used) (not used) (not used) 

(not used) (not used) (not used) (not used) 

Ethernet 2 Ethernet 1 (not used) (not used) 

(not used) Floppy (not used) (not used) 

(not used) CMP PCI Board (not used) (not used) 


(not used) Uni Screen (not used) (not used) 

6885 3522–003 B–5


S 

u 

b 

D 

I 

B 

1 

S 

u 

b 

D 

I 

B 

2 

S 

u 

b 

D 

I 

B 

3 

Table B–5. Dorado 200 Series Servers: Primary XPC-L Server (Back View) 

DOMAIN 1 (not used) DOMAIN 0 


(not used) 


(not used) 

POD 3 (not used) POD 2 

MSU 1 

(not used) 

MSU 0 

(not used) 


(not used) 


(not used) 

DIB 1 (not used) DIB 0 (not used) DIB 1 DIB 0 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

(not used) (not used) C06 (crossover) 

Path 2 

Host C 


Path 2 

Host A 


Path 2 

Host D 


Path 2 

Host B 

C05 (crossover) 

Path 1 

Host C 


Path 1 

Host A 


Path 1 

Host D 


Path 1 

Host B 


(not used) (not used) S02 (synchronization) 

Path 2 

S01 (synchronization) 

Path 1 



Path 4 


Path 3 





B–6 6885 3522–003

S 

u 

b 

D 

I 

B 

1 

S 

u 

b 

D 

I 

B 

2 

S 

u 

b 

D 

I 

B 

3 


Table B–6. Dorado 200 Series Servers: Secondary XPC-L Server (Front View) 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 


(not used) 


(4 IPs) 

DOMAIN 0 DOMAIN 1 (not used) 

POD 0 POD 1 (not used) 

MSU 2 (4GB) MSU 3 

(not used) 


(not used) 


(not used) 

DIB 1 DIB 0 DIB 1 (not used) DIB 0 (not used) 


Path 4 

Host C 


Path 4 

Host A 


Path 4 

Host D 


Path 4 

Host B 

Ethernet 

(maintenance) 


Path 3 

Host C 


Path 3 

Host A 


Path 3 

Host D 


Path 3 

Host B 





(not used) SCSI (not used) (not used) 

(not used) (not used) (not used) 


Ethernet 2 Ethernet 1 (not used) (not used) 

(not used) Floppy (not used) (not used) 

(not used) CMP PCI Board (not used) (not used) 


(not used) Uni Screen (not used) (not used) 

6885 3522–003 B–7


S 

u 

b 

D 

I 

B 

1 

S 

u 

b 

D 

I 

B 

2 

S 

u 

b 

D 

I 

B 

3 

Table B–7. Dorado 200 Series Servers: Secondary XPC-L Server (Back View) 

DOMAIN 1 (not used) DOMAIN 0 


(not used) 


(not used) 

POD 3 (not used) POD 2 

MSU 1 

(not used) 

MSU 0 

(not used) 


(not used) 


(not used) 

DIB 1 (not used) DIB 0 (not used) DIB 1 DIB 0 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 

Slot 

0 

Slot 

1 

Slot 

2 

Slot 

3 


Path 4 

Host C 


Path 4 

Host A 


Path 4 

Host D 


Path 4 

Host B 


Path 3 

Host C 


Path 3 

Host A 


Path 3 

Host D 


Path 3 

Host B 



Path 2 


Path 1 



Path 4 


Path 3 





B–8 6885 3522–003


Table B–8. Worksheet: XPC-L System Information 

Component Computer Name Network IP Address 1 Network IP Address 2 

XPC-L Primary 

Server 


Secondary 

Server 


Workstation 

(active) 


Workstation 

(backup) 


Server 

Maintenance 

LAN 


Secondary 

Server 

Maintenance 

LAN 

P-XPC-L 192.168.225.1 192.168.226.1 

S-XPC-L 192.168.225.2 192.168.226.2 

Active-XPC-Ctl 192.168.225.3 192.168.226.3 

Backup-XPC-Ctl 192.168.225.4 192.168.226.4 

(not applicable) Dorado 200 Series servers: 

192.168.222.4 

Dorado 300 Series servers: 

172.26.3.20 

(not applicable) Dorado 200 Series servers: 

192.168.222.5 

Dorado 300 Series servers: 

172.26.3.21 

(not applicable) 

(not applicable) 

Table B–9. Worksheet: XPC-L System User Name/Password Information 

Component User Name Password 


Service 

XPC-L Secondary 

Service 


(active) 


(backup) 

XPC-L XPC-L 

XPC-L XPC-L 

XPC-Ctl XPC-L-Ctl 

XPC-Ctl XPC-L-Ctl 

Table B–10. Worksheet: XPC-L License Code 

6885 3522–003 B–9


B–10 6885 3522–003

Appendix C 

Reinstallation of Windows 2003 on 

XPC-L Servers 

This appendix provides the procedure for a full reinstallation of Windows 2003, 

Enterprise Edition SP2 on the Dorado 300 Series XPC-L servers. This procedure 

describes the steps to reinstall the Windows operating system, the Server Sentinel 

components, Call Home, and configuring the server for use in the XPC-L server 

environment. The process takes approximately one and a half hour for each server. To 

ensure continuous operation of the XPC-L system, perform this procedure on one XPC-L 

server at a time. For more information on this procedure, refer to the following 

documents: 

• ES7000/one Firmware and Server Sentinel Software Reinstallation Guide for Itanium 

2 Processors , which relates to ES7000/ one Version 2.1 and higher 

• XPC-L System Installation, Configuration, and Migration Guide of XPC-L Release 2.0 

• XPC-L Firmware 2.0 Customer Reference Manual of XPC-L Release 2.0 

• ClearPath Plus Server Dorado 300 Series Install & Config Gd, Vol 2 Set Up Service 

Processors 

• Call Home TIB 10151261 

6885 3522–003 C–1

Reinstallation of Windows 2003 on XPC-L Servers 

Perform the following steps to reinstall Windows 2003 on XPC-L servers. 

Note: The XPC-L service must be stopped on the server before beginning this 

procedure. 

1. If the XPC-L Windows server is still operational, copy any DUMP files and LOG files 

that you might want to save before reinstalling the Windows operating system. 

2. Ensure you have the following media available: 

− Dorado 300 Windows IA32 Easy Install, Partition Drivers CD (3847 5620-003) 

− Windows 2003, Enterprise Edition CDs and also the SP2 CD if it is not integrated 

in your version of Windows 2003 Enterprise Edition 

− Server Sentinel Products CD (38475893-003) 

− The Windows Product Key 

− Current XPC-L Firmware CD 

3. Ensure you have the following information of the XPC-L server : 

− Computer name and password 

− HOSTS file 

− XPC-L service username and password 

− XPC-L control username and password 

− License code for the XPC-L system 

4. Reconfigure the Windows Partition in Server Sentinel so that you have the minimum 

necessary components. During the initial reinstallation of Windows, only the 

following components must be up while the others must be down. 

− Processors, IP0,0-3; IP0,8-11 

− Mem0 

− CPB0 

− PCI Bus 0,0-2; 1,1-2 

5. Insert the Dorado 300 Easy Install Partition Drivers CD in the CD-ROM drive. 

6. The XPC-L Server uses two drives that are “RAIDED“; the next step is to configure 

these drives. Power up or restart the partition from Server Sentinel. 

C–2 6885 3522–003


7. Switch on Windows. Watch for the LSI SAS BIOS display window and press 

CTRL + C to call the LSI Configuration Utility. Perform the following steps to 

configure the RAID Array: 

a. Select the first SAS adapter on the list and press Enter. 

The Adapter Properties window appears. 

b. Ensure that the Boot Support value is set to [Enabled BIOS & OS]. 

Select RAID Properties and press Enter. If the RAID array is already created 

proceed to step 7c. Else, proceed to step 7g. 

c. Select Manage Array and press Enter. 

d. Select Delete Array and press Enter. 

e. Type Y to delete array and exit to adapter properties. 

f. Select RAID properties and press Enter. 

The Select New Array Type window appears. 

g. On the Select New Array Type window, select Create IM Volume and 

press Enter. 

The Create New Array Type window appears. The disk drives available on the 

partition cell are listed here. 

h. For the first drive listed, select No under RAID Disk, and press the spacebar. 

i. Type D to overwrite the existing data and create a new IM array. 

On the Create New Array window, the RAID disk value of the selected disk 

drive changes to Yes. 

j. For the second drive listed, select No under RAID Disk and press the spacebar 

to change value to Yes. 

k. If a third disk exists in your configuration, select No under Hot Spr for that disk 

and press the spacebar to change the value to Yes. 

l. Type C to view the Create and save New Array's options dialog box. 

m. Select Save, exit this menu and press Enter. 

The Adapter properties window is displayed. 

n. To exit the LSI Logic MPT Setup Utility, press ESC twice, select Exit the 

Configuration Utility and Reboot, and press Enter. 

The partition reboots. 

8. When the system reboots, the Windows Splash window appears prompting you to 

press any key to boot from the CD-ROM. The Server Sentinel Easy Install interface 

appears after several minutes. 

Note: If you have not pressed a key to boot from the CD-ROM, then stop and start 

the partition to boot from the CD-ROM. 

6885 3522–003 C–3


9. Click Configure Boot Disk. 

a. Select Use Windows 2003 Partitioning and click OK on the message. 

b. Click Create Partition. 

A Create Partition message appears which informs you that all data will be lost. 

c. Click OK. 

Partition creation will proceed and messages will be displayed in the partitioning 

window. 

d. When the disk partitioning is complete click Format Partition. 

A Format Partition message appears telling you all the data will be lost. 

e. Click OK. 

f. When the Primary partition format is complete you will have two partitions. 

Volume 0 is the DVD-ROM and Volume 1 is the NTFS partition. 

10. Exit the Configuration Boot Disk Utility and Click on Server Sentinel 

Easy Install. 

The Easy Install Wizard appears. 

C–4 6885 3522–003



a. Click Next to use the default C partition. It must be configured as NTFS and 

approximately of size 66GB, unless your system has a different size hard drive. 

b. Select NO for Manually configure partition and click Next. 

c. Select the appropriate operating system you are installing and click Next. 

d. Enter the name, organization, and the time zone you are in. Click Next. 

e. Enter the Windows Product Key and click Next. 

f. Accept the default password or enter the site specific password and click Next. 

g. Select the licensing mode per server and click Next. 

h. Enter the computer name and make sure Workgroup is selected. Use the 

default name “WORKGROUP“ or enter the site specific name. Click Next. 

i. Ensure Yes is selected for the Network setup. Click Next. 

j. Enter the IP address and Subnet mask and click Next. 

k. Accept the Community Name Public for the SNMP service and click Next. 

l. Enter the SNMP service's contact name and location. Accept the default 

services selected (Application, Internet, and End to End). Click Next to continue. 

m. The installation summary appears if all entered information is correct. Click 

Finish to begin the Windows installation. 

The installation files will now be copied. 

n. If you are installing Windows 2003, Enterprise Edition R2, a window appears 

prompting you to insert CD 2 of the two CDs to install the R2 components. Clear 

the check box so that you do not save the R2 files and click Skip. 

A warning message appears about skipping the R2 components. 

Note: For the XPC-L servers we do not install these components. 

o. Click Yes. Insert CD 1 of the two CDs of Windows 2003, Enterprise Edition. If 

the CD does not start automatically, click browse to start the setup file. 

p. Select I accept for the License agreement and click Continue. 

The installation proceeds without requiring any intervention and will take about 

60 minutes to complete. At the end of the installation, you will able to log on to 

the system with the system administrator's credentials. 

12. Log on as administrator. The Windows setup window appears with the message 

that Windows setup is incomplete and that you need to install the new components 

from CD2. Click Cancel. The Windows setup window reappears, click OK. The 

Windows Server Post-Setup Updates window appears. 

13. As your system is part of a private network, do not configure the update capabilities 

for Windows. Click Finish, and then click Yes on the updated warning message. 

The Manage Your Server window appears. 

14. .Your system does not configure any of these components. Select Don’t display 

the page at logon and close this window. 

6885 3522–003 C–5


15. Install the partition drivers using the following steps: 

a. Log on to the system as the administrator if not already logged on. 

b. Insert the Partition Easy Install, Drivers, and HAL Media CD into the Partition 

CD/DVD drive. 

This action launches the Installation Assistant. 

Note: If the autorun option is not set, use Windows Explorer to navigate to the 

following location and double-click the setup.exe file: :\setup.exe. 

If the Internet Explorer Enhanced Security dialog box appears, select In the 

future, do not show this message again and click OK. 

c. Click the partition drivers. 

The Supplemental Driver Utility is installed. A scan is performed to determine 

whether updated drivers are available from the CD-ROM. The Supplemental 

Driver Utility is then displayed, enabling you to update your drivers. 

d. Ensure that you install drivers that are appropriate for your environment. If the 

installed drivers are of the same level as the available drivers, the most up to 

date drivers are installed and no drivers are selected for installation. Click Exit 

and proceed to step 15e. 

If drivers are selected, click Install. An installation progress bar is displayed. 

Each selected driver is installed. After the drivers are updated, click Exit. 

Note: If prompted, load the vendor driver utilities selected by the Supplemental 

Driver Utility 

e. Click Finished. 

f. Click Yes to restart the system if prompted to do so. 

g. Remove the Partition Easy Install, Drivers, and HAL Media CD from the partition 

CD/DVD drive. 

16. Configure Maintenance LAN for Call Home by performing the following steps: 

a. If not already logged on, log on as the administrator. 

b. Open the network connections. You can do this by right-clicking and opening the 

network connection from the network icon. Alternatively, point to Control 

Panel on the Start menu and select Network connections. 

c. Go to the LAN2 connection, right-click and select properties. This should be 

Cell 0 right hand connection. You can verify this by unplugging and plugging the 

cable. On the General tab, select Internet Protocol and properties. Click 

Use the following IP address and enter the appropriate IP address for 

the Server. Refer to the HOSTS file for your system for this IP address. Also 

enter the Subnet mask address 255.255.0.0. Click OK and close the 

connection window. 

C–6 6885 3522–003


17. Configure the Ethernet 2 LAN connection by performing the following steps: 

a. Go to the LAN connection and right click, then select properties. This should 

be the Cell 1 left hand connection. You can verify this by unplugging and 

plugging the cable. 

b. On the General tab, select Internet Protocol and properties. Click Use 

the following IP address and enter the appropriate Ethernet 2 IP address for 

the server. Refer to the HOSTS file for your system to get the IP address. Also 

enter the Subnet mask address 255.255.255.0. Click OK and close the 

connection window. 

18. Change the Windows nonpaged pool size by performing the following steps: 

a. Log on as an administrator. 

b. Insert the XPC-L Firmware CD into the CD-ROM drive of the Intel partition of the 


You might see the installation setup box for XPC-L Control. Click Cancel. 

c. Navigate to CD-ROM_drive_letter:/Server Registry Changes/ and double-click 

System Pages.reg. 

A message appears in the registry editor asking you whether you are sure you 

want to add the information to the registry. 

d. Click Yes. 

A message appears in the registry editor stating that the information has been 

successfully entered into the registry. 

e. Click OK. 

f. Remove the XPC-L Firmware CD from the CD-ROM drive of the Intel partition of 

the server and reboot the server to make these changes effective. 

6885 3522–003 C–7


19. Install the VI driver software by performing the following steps: 

a. Shut down the Windows server and go to Server Sentinel and “up“ all the PCI 

buses for the Myrinet cards that are installed in your system. 

Note: PCI Bus 1 must be up in all the cells. 

b. Boot the system and log on as Administrator. 

The Welcome to the Found New hardware wizard window appears, with the 

message Can Windows connect to Windows update search for 

software? 

c. Click No, not this time. Then click Next. 

d. Leave Install Automatically selected, but do not click Next. 

e. Insert the XPC-L Firmware CD into the CD-ROM drive of the Intel partition 

server. 

You might receive the installation setup dialog box for XPC-L Control after 

inserting the CD. If you do, click Cancel; do not install XPC-L Control onto the 

server. 

A message in the Hardware Installation window states that the adapter has not 

passed Windows Logo testing. 

f. Click Continue Anyway. 

The VI card software driver is installed. 

g. Click Finish. 


h. Repeat steps 19c through 19g for every VI card until the software driver is 

installed for all cards. 

i. Remove the XPC-L Firmware CD from the CD-ROM drive of the Intel partition 

server. 

C–8 6885 3522–003


20. Perform the following steps to change the network settings for each of the VI cards: 


b. Double-click Network Connections. 

A Network Connections window appears. 

c. Right-click one of the VI cards (Myricom Myrinet Adapter) and click Properties. 

A Local Area Connection Properties window appears. 

d. Clear each of the check boxes listed under This connection uses the 

following items. 

e. Select the Show icon in notification area when connected check box. 

f. Clear the Notify me when this connection has limited or no 

connectivity check box. 

g. Click OK. 

h. Repeat steps 20c through 20g for each VI card. 

i. Close the Network Connections window. 

j. Reboot the server. 

Caution 

a. Change the network settings for each VI card. Failure to do so could 

result in unpredictable behavior. 

b. Do not perform these network setting changes for non-VI cards (such as 

the Ethernet cards) in the system. 

21. Copy the HOSTS file. 

a. Log on to the XPC-L server as an administrator and copy the HOSTS file for your 

system to the following location, replacing the existing file: 


b. Modify the HOSTS file for the XPC-L server maintenance LAN for your appropriate 

XPC-L server. Also add this IP address to the HOSTS file of the service processor. 

6885 3522–003 C–9


22. Create user names and update local security policies by performing the following 

steps: 

a. Log on to the XPC-L server as an administrator to create the XPC-L Service User 

name for your system. 

b. On Control Panel, double-click Administrative Tools, and then doubleclick 

Computer Management. 

c. Under Local Users and Groups, click Users. 

d. Click Action. 

e. Click New User on the Action menu. 

f. Type the required user name and password (Full name and Description are 

optional). 

The password must be greater than six characters. 

g. Clear the User must change password at next logon check box and click 


h. Click Create. 

i. Click Close. 

j. Add the new user name to the Administrators group 

k. Under Local Users and Groups, click Groups. 

l. Double-click Administrators. 

m. Click Add. 

n. Type the user name defined in step 22f and click OK. 

o. Click Apply, and then click OK. 

p. Now repeat steps 22c through 22o to create the XPC-L Control user name. 

q. Set the XPC-L Server service user name (or a group of which it is a member) to 

have the user rights assignments of Log on as service and Lock pages in 

memory. 

r. On Control Panel, double-click Administrative Tools, and then doubleclick 

Local Security Policy. 

s. Under Local Policies, click User Rights Assignment. 

t. Double-click Log on as service in the right pane. 

u. Click Add User or Group. 

v. Type the user name and click OK. 

w. Click Apply, and then click OK. 

x. Repeat steps 22t through 22w for Lock pages in memory rights. 

y. Reboot the server to make changes effective, before continuing to the next 

step. 

C–10 6885 3522–003


23. Create the shared folder by performing the following steps. Log onto the XPC-L 

server as an administrator and create this folder in the C: root directory as follows: 

a. Launch Windows Explorer. 

b. Click New on the File menu to create a folder. Name the folder “XPC-L 

SHARE.“ 

c. Right-click the XPC-L SHARE folder and select Properties. 

The XPC-L SHARE Properties dialog box appears. 

d. On the Sharing tab, select the Share this folder check box and type XPC-L 

SHARE in the Share name box. 

e. On the Permissions tab, select the Full Control, Change, and Read check 

boxes. Click Apply, and then click OK. 

f. Click Apply, and then click OK to complete the creation of the shared folder. 

6885 3522–003 C–11


24. Using the Active XPC-L Control Workstation, install XPC-L Server software. 

a. Ensure that the XPC-L Server is booted. 

In the main window under Servers, if the server status is Server not found, 

then either the server is not booted or the name of the server in the 

configuration file is incorrect. After the Select Server display is updated with 

Service not found (the software has not been installed yet) or Stopped (the 

software is being reinstalled, therefore the service is stopped), you can continue 

with the next step. 

b. Install the XPC-L executable and DLLs on the XPC-L server. 

c. On the Select Server pane, click the server name to select it. Click Tools and 

then click Install XPC-L Software to install the XPC-L Server service on the 

selected server. 

The License Code dialog box appears, soliciting the license code for the specific 

combination of configured XPC-L servers. The license code is available on the 

worksheet provided by Unisys. The dialog box validates the format of the license 

code. The license code is further verified during the XPC-L initialization process 

following a start XPC-L command. If the verification check fails, the XPC-L will 

not initialize correctly and you must reinstall the software. If XPC-L Control finds 

that the service is already installed on the selected server, it skips the solicitation 

of a user name and password. If the XPC-L service was not previously installed, 

the User Name window appears. 

d. Enter the user name and password that was set up for the XPC-L service on the 

selected server and on the XPC-L Control Workstation. Click OK. 

e. XPC-L Control then copies the XPC-L executable and DLLs to the XPC-L Share 

folder on that server and automatically creates the XPC-L service on that server. 

You can view the results on the Log window. Once this step is successfully 

completed, the state of the service on the Select Server pane is updated with 

Stopped. 

You have now completed installing the XPC-L Server software. 

The XPC-L server is now ready for use and can be started. 

If you wish to use Call Home for your system, perform step 25 before using your 

server with your XPC-L System. 

25. To set up and test Call Home for Dorado 300 Series XPC-L servers refer to the XPC-L 

Firmware 2.0 Customer Reference Manual and the Technical Bulletin 10128684. 

C–12 6885 3522–003

Glossary 

D 

Distributed Systems Manager (DSM) 

A hardware and software environment that extends data acceleration capabilities into 

multihost file sharing environments. DSM software uses the XPC hardware unit to 

provide caching of shared mass storage files and improved interhost messaging and 

locking functions in various multi host configurations. See also Extended Processing 

Complex (XPC). 

DLL 

E 

Abbreviation for dynamic link library. 

Extended Processing Complex (XPC) 

An optional central electronics complex (CEC) component that extends the processing 

capabilities of a Dorado Series server. It provides data acceleration for individual and 

multiple hosts, and data locking and interhost communication capabilities for multi host 

processing environments. Extended processing capabilities are realized through the 

combination of XPC hardware and host-resident features, such as XPCEXEC for data 

acceleration, MHFS for multi host file sharing, and XTC for multi host concurrent 

application processing. See also Distributed Systems Manager (DSM). 

The next generation replacement for the XPC is the XPC-L. 

Extended Processing Complex-Locking (XPC-L) 

A central electronics complex (CEC) component that is optionally added to a Dorado 

Series server. XPC-L provides an external lock engine that is used to coordinate access 

to files and databases that are simultaneously accessed from multiple hosts. It provides 

the following categories of functions: 

M 

MIH 




XPC-L is the next generation replacement for the XPC. 

Abbreviation for Multiple Independent Hosts. 

6885 3522–003 Glossary–1

Glossary 

R 

record lock processor (RLP) 

The capability provided by the XPC-L that enables a single application to execute 

simultaneously on multiple Dorado Series servers while accessing a common database 

(an XTC environment). This capability is also referred to as the external lock manager. 

S 

SCP 

V 

VI 

VSM 

X 


Initially, the RLP was a processor connected to all hosts in an XTC environment. The RLP 

is no longer supported, but the capability it initially provided continues to be provided by 

the XPC and XPC-L. 

Acronym for Service Control Program. 

Abbreviation for virtual interface. 

Abbreviation for Virtual Storage Manager. 

See Extended Processing Complex. 

XPC I/O Interface Processor (XIIP) 

An IOP connected to the XPC-L. 

XPC Resident File (XRF) 

A file with the XRP file caching specification. XPC resident files are not subject to the 

caching algorithm and are destaged only under specific conditions. 


See Extended Processing Complex-Locking. 


The software that runs on an XPC-L Control Workstation to control and provide the 

primary user interface to the XPC-L Servers. 

XPC-L platform 

The hardware comprising an XPC-L Server. 

Glossary–2 6885 3522–003

XPC-L Server 

The physical entity that performs the record-level locking functions. 

Glossary 

Multiple hosts connect to redundant XPC-L platforms, which are controlled by redundant 

XPC-L Control Workstations. The redundant XPC-L systems operate in a master/slave 

software configuration; the platform that is the master is referred to as the primary 

server and the platform that is the slave is referred to as the secondary server. The 

primary/secondary configuration may consist of two independent hardware platforms or 

multiple pods within the same hardware platform. 

XPC-L service 

The software that runs on an XPC-L Server. 

XPC-L system 

The group of XPC-L Control Workstations and XPC-L Servers that provide the Extended 

Processing Complex-Locking (XPC-L) function. 

XRF 

XRP 

See XPC Resident File. 

A FURPUR and FREIPS option that sets a file’s XPC caching specification to make it a 

permanent XPC Resident File. 

6885 3522–003 Glossary–3

Glossary 

Glossary–4 6885 3522–003

Index 

A 

add a new VI card, 5-6 

administrator 

create shared folder, 2-31 

install XPC-L control, 2-32 

XPC-L Control Workstation 

modify hosts file, 2-26 

XPC-L Control Workstation, modify hosts 

file, 2-26 


add user names, 2-30 


administrators group, A-1 

create XPC-L Control user name, 2-28 

create XPC-L Server user name, 2-28 


add server user name, 2-29 

add XPC-L Control user name, 2-29 


add XPC-L Control user name, 2-30 

add XPC-L Server user name, 2-30 

C 

caching, eliminated, 4-1 

configuration file 

creating, 3-6, 3-27 

identify location, 2-33 

purpose, 3-5 

sample, 3-10, 3-24 

syntax, 3-7 

configuring 

hosts, 3-2 

XPC-L Control Workstation, 3-1 

XPC-L Server, 3-2 

console messages 

changed, 4-15 

new, 4-13 

CPU hyper-threading, enable, 5-42, 5-43 

crossover path 

purpose, 1-8 

VI card function, 3-6 

6885 3522–003 Index–1 

D 

database locking, 1-2 

DataMover 

mutually exclusive with VI channel, 4-22 

not supported, 3-3, 4-2 

direct-connect path, VI card function, 3-6 

DLL, 2-31, 2-36 

DN XIPnn keyin, 4-17 

DN XPC_name keyin, 4-17 

document notations, 1-10 

E 

EXERR-0133, 4-22 

Extended I/O processors, See XIIP 

Extended Transaction Capacity 

defined, 1-5 

installing, 2-38 

external lock manager, defined, 1-2 

F 

feature grouping 

Extended Transaction Capacity, 1-5 

Partitioned Applications, 1-5 

feature, MHFS, 1-3 

FS,ALL CM_name keyin, 4-20 

FS,ALL IOP_name keyin, 4-20 

FS,ALL IPx keyin, 4-20 

FS,ALL XIIP_name keyin, 4-21 

FS,ALL XPC_name keyin, 4-19 

FS,CM keyin, 4-19 

FS,IOP keyin, 4-18 

FS,XCACHE keyin

Index 

changed console message, 4-15 

FS,XIIP keyin, 4-19 

FS,XPC keyin, 4-18 

H 

Host Interface Adapter (HIA), not 

supported, 4-2 

host platform 

hardware, 1-7 

software, 1-9 

host software 


removing, 6-2 

host, configuring, 3-2 

hosts file, modifying, 2-26 

hyper-threading 

enable, 5-20, 5-31, 5-42, 5-43 

I 

I/O command queuing, 4-1 

increase nonpaged pool, 2-21 

interhost messaging, 1-3 

IOPUTIL, 5-50 

K 

k, 5-21 

keyins 

DN XIPnn, 4-17 

DN XPC_name, 4-17 

FS,ALL CM_name, 4-20 

FS,ALL IOP_name, 4-20 

FS,ALL IPx, 4-20 

FS,ALL XIIP_name, 4-21 

FS,ALL XPC_name, 4-19 

FS,CM, 4-19 

FS,IOP, 4-18 

FS,XCACHE, 4-15 

FS,XIIP, 4-19 

FS,XPC, 4-15, 4-18 

MAINT, 4-21 

UP XIPnn, 4-17 

UP XPC_name, 4-17 

XPCDUMP, 4-16 

Index–2 6885 3522–003 

L 

license code, 2-33, 2-36 

load PCIOP microcode, 5-48 

batch mode, 5-50 

demand mode, 5-51 

offline, 5-55 

online, 5-48 

locale, 2-40 

lock manager, 4-1 

M 

m, 2-1 

MAINT keyin, 4-21 

master server, 1-6, 3-1 

MHFS, See Multi-Host File Sharing 

migration 

changed console messages, 4-15 

conceptual and major functional 

differences, 4-1 

DataMover not supported, 4-2 

HIA not supported, 4-2 

interhost database locking, 4-2 

interhost messaging, 4-2 

new console messages, 4-13 

with shared unit duplexing, 4-10 

XIIP keyins, 4-3 

XIIP not supported, 4-2 

modes 

nonredundant mode, 3-1 

redundant mode, 3-1 


Multi-Host File Sharing (MHFS) 

defined, 1-3 


interhost communication 

alternate method, 1-4 

preferred method, 1-4 

XPC method, 1-4 

removing with XPC-L, 6-2 

without XPC-L, 6-2 

N 

n, 3-7 

nonpaged pool, increase, 2-21 

nonredundant mode, 3-1 

notation conventions, 1-10

O 

Operations Sentinel message text 

format, 2-39 

modifying, 2-40 

printing, 2-40 

purpose, 2-39 

ordering options, 2-1 

P 

PA, See Partitioned Applications 

partition, 2-17 

partition profile names, 2-16 

Partitioned Applications (PA), 1-5 

defined, 1-5 


PCIOP microcode 

load new version, 5-48 

batch mode, 5-50 

demand mode, 5-51 

offline, 5-55 

online, 5-48 

primary server platform, 1-6 

R 

R, 5-32 

record locking function, 4-1 

redundant mode, 3-1 

reinstall Windows drivers, XPC-L Control 

Workstation, 5-16, 5-27, 5-38 

reinstall Windows XP, XPC-L Control Wor XE 

"k" kstation, 5-21 

reinstall Windows XP, XPC-L Control 

Workstation, 5-9 

reinstall Windows XP, XPC-L Control 

Workstation, 5-32 

replace a VI card, 5-3 

S 

SCIOP, 3-2 

SCMS II, 3-2 

SCMS, define VI cards, 3-2 

secondary server platform, 1-6 

server 

identifying primary, 2-33 

Index 

interface, 4-2 

server names, 2-33 

servers, 1-7, 1-9 

configuring, 3-2 

controlling, 3-1 

installing software, 2-35 

master, 1-8 

slave, 1-8 

Service Processor console, not to configure 


shared unit duplex, 4-10 

shutdown to upgrade software, 5-7 

slave server, 1-6, 3-1 

software upgrade, with shutdown, 5-7 

sp_data_directory/help/locale, 2-40 

state file, 2-33 

synchronization path 

purpose, 1-8 

VI card function, 3-6 

6885 3522–003 Index–3 

T 

TIP, 1-2, 1-5 

U 

UDS, 1-2 

Unit Duplexing synchronization, 1-3 

Universal Data System (UDS), 1-5 

UP XIPnn keyin, 4-17 

UP XPC_name keyin, 4-17 

upgrade hardware 


XPC-L host, 5-6 


upgrade platform software 

XPC-L Control Workstation, 5-9, 5-20, 5-32 

upgrade software 

with shutdown, 5-7 


XPC-L host, 5-47 


user name, 2-28, 2-29, 2-30, A-1 

user rights, 2-29, 2-30, A-2 

V 

VI card 

add new, 5-6

Index 

driver software, 2-22 

functional categories, 3-6 

one per PCIOP, 4-22 

placement, B-1 

replace, 5-3 

seen as XIIP, 3-2, 3-9 

VI channel, 1-7 

messages, 4-13 

mutually exclusive with DataMover, 4-22 

virtual interface channel, See VI channel 

X 

XIIP 

messages, 4-13 

not supported, 4-2 

VI card seen as, 3-9, 4-2 

xiip_name, 4-22 

XPCDUMP keyin, 4-16 

XPCEXEC 


removing, 6-2 


deinstalling, 6-2 

functions, 1-2 

hardware, 1-6 

master, defined, 1-6 

nonredundant mode, 3-1, 3-6 

platform 

hardware, 1-7 

software, 1-9 

primary, defined, 1-6 

redundant mode, 3-1, 3-6 

secondary, defined, 1-6 

slave, defined, 1-6 

system, 1-6 

system, defined, 1-2 


changing hardware, 5-1 

changing platform software, 5-9, 5-20, 5-32 



reinstall Windows drivers, 5-38 

reinstall Windows drivers, 5-16, 5-27 

reinstall Windows XP, 5-9, 5-21, 5-32 

removing software, 6-3 

software, 1-9 

upgrade software, 5-44 

user name, 2-29 

user rights assignment, 2-29, 2-30 

XPC-L host 







license code, 2-36 

partition, 2-17 

removing software, 6-3 

service 


user rights, 2-30 

shared folder, 2-31 



XPCLLower.ptn profile, 2-16 

XPCLUpper.ptn profile, 2-16 

XSTRESS, 5-58 

XTC, See Extended Transaction Capacity 

Index–4 6885 3522–003

© 2009 Unisys Corporation. 

All rights reserved. 

*68853522-003* 

6885 3522–003

XPC-L System Installation, Configuration, and Migration Guide

Create successful ePaper yourself

Delete template?

Save as template?