Hardware & Software Configuration Manual

Dealing 2000-2 Central System

Hardware & Software ConfigurationManual

Synopsis: This document provides information on system hardware andfirmware configuration. Information is also provided on theinstallation, functionality, and use of the Dealing 2000-2 SoftwareManagement Utility.

Status: DRAFT

Approvals: See Software Release Notes

Version: 02.01-00

Date: 1 December 1997

Document ID: TD-CCXX-CIXX-002

Filename: HW_SW.DOC

Technical Publications Group

PROPRIETARY INFORMATION OF REUTERS

This document contains information proprietary to Reuters America Inc, and may not be reproduced, disclosed, or usedin whole or in part without the written permission of Reuters America Inc.

Hardware & Software Configuration Manual Proprietary

i

Table of Contents

1. INTRODUCTION.................................................................................................................... 1

1.1 Overview.................................................................................................................................................. 1

1.2 Purpose ................................................................................................................................................... 1

1.3 Related Documents ................................................................................................................................ 1

1.4 Revision History ..................................................................................................................................... 2

2. CLUSTER CONFIGURATION .................................................................................................. 3

2.1 General .................................................................................................................................................... 3

2.1.1 Hardware Specifications ........................................................................................................................... 3

2.2 Central System AlphaServer 8400....................................................................................................... 10

2.3 Operations Control System AlphaServer 4000 .................................................................................. 11

2.4 Storage Devices and Controllers ........................................................................................................ 11

2.4.1 HSJ and Disk Configuration.................................................................................................................... 11

2.4.2 Storage Works Layout ............................................................................................................................. 13

2.5 Rebooting after Initial Installation....................................................................................................... 17

3. DECSERVER CONFIGURATION ........................................................................................... 19

3.1 DECserver Overview ............................................................................................................................ 19

3.2 GTC-L DECserver Configuration......................................................................................................... 19

3.2.1 DECserver Port Assignments ................................................................................................................. 19

3.2.2 Configuring the DECServer 90M Port .................................................................................................... 20

3.2.3 List Port Commands ................................................................................................................................ 21

3.2.4 Setting DECServer Server Name ............................................................................................................ 26

3.3 GTC-G DECserver Configuration ........................................................................................................ 26

3.3.1 DECserver Port Assignments ................................................................................................................. 26

Proprietary Dealing 2000-2 Central System

ii

3.3.2 Configuring the DECServer 90M Port.....................................................................................................27

3.3.3 List Port Commands.................................................................................................................................28

3.3.4 Setting DECServer Server Name.............................................................................................................33

3.4 T-Desk DECserver Configuration ........................................................................................................33

3.4.1 DECserver Port Assignments..................................................................................................................33

3.4.2 Configuring the DECServer 700 Port ......................................................................................................33

3.4.3 List Port Commands.................................................................................................................................35

3.4.4 Setting DECServer Server Name.............................................................................................................37

4. SOFTWARE MANAGEMENT UTILITY .....................................................................................39

4.1 Installation .............................................................................................................................................39

4.1.1 General39

4.1.2 Installation Procedure ..............................................................................................................................39

4.2 Operation ...............................................................................................................................................40

4.2.1 General40

4.3 Menu Descriptions ................................................................................................................................40

4.3.1 Main Menu .................................................................................................................................................40

4.3.2 Load Release Submenu ...........................................................................................................................41

4.3.3 Activate Release Submenu......................................................................................................................42

4.3.4 Rollback Release Display.........................................................................................................................42

4.3.5 Delete Release Submenu .........................................................................................................................43

4.3.6 Show Current Versions Display ..............................................................................................................43

4.3.7 Install Third-Party Display .......................................................................................................................44

4.3.8 Show/Modify Configuration.....................................................................................................................44

4.4 Starting the SMU ...................................................................................................................................44

4.5 Load 45

4.6 Activate Host .........................................................................................................................................47

4.6.1 Activate Host Environment Software......................................................................................................48

4.6.2 Activate Application .................................................................................................................................52

4.7 Rollback .................................................................................................................................................54

4.8 Delete......................................................................................................................................................55

4.9 Show Current Versions ........................................................................................................................56

4.10 Install Third-Party Software ...............................................................................................................56


iii

4.11 Show/Modify Configuration............................................................................................................... 57

Proprietary Dealing 2000-2 Central System

iv

List of FiguresFIGURE 1: GTC-L CENTRAL SITE OVERVIEW........................................................................................................... 5FIGURE 2: GTC-G CENTRAL SITE OVERVIEW .......................................................................................................... 6FIGURE 3: GTC-L DECHUB BACKPLANE LAYOUT .................................................................................................. 7FIGURE 4: GTC-G DECHUB BACKPLANE LAYOUT.................................................................................................. 8FIGURE 5: TDESK ROOM LAYOUT .............................................................................................................................. 9FIGURE 6: D2000-2 CENTRAL SITE DISK CONFIGURATION ................................................................................ 14FIGURE 7: STORAGE WORKS HSJ000/HSJ001 SHELF LAYOUT............................................................................. 15FIGURE 8: SMU MAIN MENU ...................................................................................................................................... 41FIGURE 9: SMU LOAD RELEASE SUBMENU............................................................................................................ 41FIGURE 10: SMU HOST OPTIONS SUBMENU........................................................................................................... 42FIGURE 11: SMU ACTIVATE RELEASE SUBMENU................................................................................................. 42FIGURE 12: SMU ROLLBACK RELEASE DISPLAY .................................................................................................. 43FIGURE 13: SMU DELETE RELEASE SUBMENU...................................................................................................... 43FIGURE 14: SHOW CURRENT VERSIONS DISPLAY................................................................................................ 43FIGURE 15: SMU SHOW/MODIFY CONFIGURATION SUBMENU ......................................................................... 44FIGURE 16: HOST VERSIONED DIRECTORY STRUCTURE (TYPICAL) ............................................................... 46

List of Tables

TABLE 1: PHYSICAL DISKS AS SHADOW SETS/LOGICAL NAMES ..................................................................... 12TABLE 2: SWITCH SETTINGS FOR HSJ000 AND HSJ001 CONTROLLERS........................................................... 13TABLE 3: DISK SWITCH SETTINGS ........................................................................................................................... 17TABLE 4: TZ88 (T140) SWITCH SETTINGS ............................................................................................................... 17TABLE 5: GTC-L CENTRAL SITE HOST DECSERVER 1 PORT ASSIGNMENTS (HUB A/SLOT 1) (HUB B/SLOT

1 IS THE BACKUP.)................................................................................................................................................ 19TABLE 6: GTC-L CENTRAL SITE HOST DECSERVER 2 PORT ASSIGNMENTS (HUB A/SLOT 2) (HUB B/SLOT

2 IS THE BACKUP.)................................................................................................................................................ 20TABLE 7: GTC-G CENTRAL SITE HOST DECSERVER 1 PORT ASSIGNMENTS (HUB A/SLOT 1) (HUB B/SLOT

1 IS THE BACKUP.)................................................................................................................................................ 26TABLE 8: GTC-G CENTRAL SITE HOST DECSERVER 2 PORT ASSIGNMENTS (HUB A/SLOT 2) (HUB B/SLOT

2 IS THE BACKUP.)................................................................................................................................................ 27TABLE 9: T-DESK DECSERVER HPFS05, 06, 07, 08 PORT ASSIGNMENTS.......................................................... 33TABLE 10: NODE INSTALLATION PARAMETERS.................................................................................................... 48TABLE 11: DISK INSTALLATION PARAMETERS ..................................................................................................... 50TABLE 12: PORT INSTALLATION PARAMETERS ................................................................................................... 50TABLE 13: SERVER INSTALLATION PARAMETERS ............................................................................................... 50


v


Version: 02.01-0 Introduction •••• 1

1. Introduction

1.1 OverviewThis manual covers the following topics:

• Cluster configuration information, including console settings for the AlphaServer 8400s, DECserver portconfigurations, and configuration of the HSJ50 storage controllers.

• Installation, functionality, and use of the Dealing 2000-2 Software Management Utility (SMU).

Note that the SMU ONLY installs applications relating to the D2000-2 Central Systems. It does NOTinclude installation routines for components of the Reuters Transaction Network (RTN), such as the NRM orNDCS, which also reside at the D2000-2 Central Site. RTN components are installed independently usingseparate installation methods.

1.2 PurposeThis manual contains information on the required hardware and firmware configurations for the DECserver,AlphaServer 8400, and HSJ50 controllers. This hardware and firmware must be properly configured beforethe SMU and other software can be installed. Additional information on hardware and firmware installationand configuration is found in the Dealing 2000-2 Central System Cutover/Fallback Procedures Manual.

This manual contains information necessary to install D2000-2 Central Systems software applicationsrequired for proper operation of the Reuters Dealing 2000-2 Automated Matching System. Additionalinformation on installing the third-party software is contained in the appropriate software release notes.

1.3 Related Documents• Dealing 2000-2 Central System Cutover/Fallback Procedures

• Dealing 2000-2 Central System Operational Procedures Manual

• Dealing 2000-2 DEChub Procedures Manual

• Dealing 2000-2 Central System Installation Release Note

• DECserver 250 Hardware Installation Manual

• DECserver Management Guide

• DEC VAX 8400 Console Reference Manual

• Guide to DECnet-VAX Networking, DEC Order No. AA-LA47A-TE

• Guide to Setting Up a VMS System, DEC Order No. AA-LA25A-TE

• CLI Reference Manual: HSJ50, HSD50, and HSZ50 Array Controllers – HSOF Version 5.0

• AlphaServer 4000 Installation Guide

Proprietary Hardware & Software Configuration Manual

Introduction •••• 2 1 December 1997

• AlphaServer 8400 Owners Manual

• VMS License Management Utility Manual, DEC Order No. AA-LA33B-TE

• VMS VAXcluster Manual, DEC Order No. AA-LA27B-TE

• VMS Version 6.2 Upgrade and Installation Manual

1.4 Revision HistoryVersion 02.01-00 1 December 1997 Revisions to support Geneva

contingency.

Version 01.02-00 6 August 1997 Redlines incorporated from SystemIntegration Testing (SIT) as of8/6/97. Added the DECServer90M port configuration procedure;set HSJ maximum_hosts = 6.

Version 01.00-00 18 July 1997 This is a new manual, replacing theSoftware Management UtilityManual. It incorporates hardware,firmware, and softwareconfiguration information. Thischange was needed to incorporateHost move and related changes.The D2000-2 Central SystemsEnvironment Parametersdocument was also incorporatedinto this manual.


Version: 02.01-0 Cluster Configuration •••• 3

2. Cluster Configuration

2.1 GeneralThe procedures in this chapter are provided to ensure that the proper hardware platform and softwareenvironment exist for the successful installation and operation of the D2000-2 Central Systems. Theseprocedures are usually performed either during initial site installation or as part of a major hardware and/orsoftware upgrade.

Refer to the Dealing 2000-2 Central System Cutover/Fallback Procedures Manual for additional informationon installing hardware and software.

Note: The procedures outlined in this chapter should ONLY be performed as specified in applicable Dealing2000-2 Central Systems Software Release Notes or at the direction of Reuters Development.

This chapter covers:

• Console settings for the AlphaServer 8400.

• Boot procedures for the AlphaServer 4000s.

• Configuration of the HSJ50 controllers.

• DECserver port configurations.

2.1.1 Hardware SpecificationsThe hardware configuration required to support the D2000-2 Central Systems is shown in Figure 1 throughFigure 5 on the following three pages.

2.1.1.1 Four AlphaServersThe Dealing 2000-2 Central System is configured with four DEC AlphaServers in an Open VMSclusterconfiguration. The nodes are connected via the Central System Cluster Interconnect (CI), and the RTNEthernet, and are attached to a star coupler as shown in Figure 1.

The AlphaServers include:

• Two AlphaServer 8400s (Host Nodes) running OpenVMS 6.2-1H3 and configured with 1GB of memory.One node runs the live host application and SYBASE Dataserver, and the other runs as a warm standbythat can be used in the event of an application or node failure. Dual Cluster Interconnect (CI) controllersoffer load balancing and redundancy in the event of a controller failure.

• Two AlphaServer 4000s that act as an Operational Control System (OCS), providing a nearly lights-outfacility.


Cluster Configuration •••• 4 1 December 1997

2.1.1.2 Storage DevicesStorage is provided by Digital Storageworks components, connected by a pair of dual-redundant HSJ storagecontrollers. The controllers are also connected to the star coupler as shown in Figure 1.

2.1.1.3 LAN ControlTwo DEChub 900 MultiChassis hubs are used to control multiple local area networks (LANs). The DEChubsare configured to be fully application, system, and hardware redundant so that any one of the modules can beremoved with no effect to the D2000-2 service. Refer to the Dealing 2000-2 DEChub Procedures Manual fora complete description of the functionality and design. Figure 5 shows the DEChub layout. Figure 5 showsthe TDesk layout at 90 Davids Drive in Hauppauge, beginning from the Retix bridge from both the GTC-Land the GTC-G.



8400

CIXCDDEMNA

16 PortStar

Coupler

4100CIPCADE500

4100CIPCADE500

All Cables FDDIDUAL ATTACHED

DAS - BN24B

DRAWN BYJeff Weissman

D2000-2 Rev 2.3D2 DTC Central Site Configuration,

With Contingency, No DSSFILENAME

D2 DTC CENTRAL SITE NO DSS.VSDDATE

17-NOV-1997

Docklands Controller AreaDocklands Computer Room

CIXCD

DETPM-AA

CSFEVAXstation

GEMSHP PC

AUI

DETPM-AA

T-DESKVAXstation

AUI

DETPM-AA

IMFVAXstation

AUI

CabletronSEHI-22

DETPM-AA

OSFEVAXstation

AUI

DETPM-AA

NDCSVAXstation

AUI

Emergency T-Desk

HSJ50HSJ50DiscFarm

(24 RZ29)

10BaseFL

DETPM-AA

UTP

UTP

DEMNADETPM

-AA

UTP

8400

CIXCDDEMNA

CIXCD

DEMNA

DETPM-AA

DETPM-AA

UTP

UTP

UTP

10BaseFL

CI Node: 0

CI Node: 1

CI Node:3

CI Node:2

CI Node:7

CI Node:6

CI Node:4

CI Node:5

2x128KBTo 90DD

T-DESK LAN

DEChub 900

DECserver 90M

PORTswitch 900TP

PORTswitch 900FPDECswitch 900EF

DECswitch 900EF

RETIXBridge

AUI

DECserver 90M

DEChub 900

DECserver 90M

PORTswitch 900TP

PORTswitch 900FP

DECswitch 900EF

DECswitch 900EF

RETIXBridge

AUI

DECserver 90M

DECserver Ports1) VT Terminal2) Error Port3) Security Port4) Automation Port5) xGPS Feed6) xGPS Feed7) VT Terminal8) VT Terminal

DETPM-AA

DETPM-AA

clearVISNPC

UTP:BN24F

DECnis 600

W601

W622HS NYGenevaUKI/RCESingapore

W622HSW622HSW622HS

W601

UTP

Future Installation

DETPM-AA

DETPM-AA

AUI

AUI

DETPM-AAUTP

DETPM-AAUTP

NRM FEVAXstation

NDCSVAXstation

GEMSHP PC

NT NRMHP PC

UTP

UTP

AUI

AUI

CabletronSEHI-22

DECnis 600

W601

W622HSNYGeneva

UKI/RCESingapore

W622HSW622HSW622HS

W601

UTP

Future Installation

DETPM-AA

DETPM-AA

AUI

AUI

DETPM-AA UTP

DETPM-AA UTP

NRM FEVAXstation

NDCSVAXstation

GEMSHP PC

NT NRMHP PC

UTP

UTP

AUI

AUI

CabletronSEHI-22

Central System Monitoringand Control LAN

DETPM-AAUTP

OSFEVAXstation

CabletronSEHI-22

Cisco2514

DETPM-AA

ToOMN Mgt.

LAN

Cisco2514

DETPM-AA

AUIAUI

1

NULL

1

NULL


DETPM-AAUTP

OSFEVAXstation

CabletronSEHI-22

26

ComputerInterconnectSystem

DETPM-AA

NRMMV3100 M80

VT510

AUI

NFR

RETIX

RETIX

RETIX

RETIX

NY

Geneva

UKI

Singapore

DETPM-AA

AUI

DETPM-AA

AUI

DETPM-AA

AUIDETPM-AA

AUI

RETIX RCEDETPM-AA

AUI

ComputerInterconnectSystem

DETPM-AA

NRMMV3100 M80

VT510

AUI

NFR

RETIX

RETIX

RETIX

RETIX

NY

Geneva

UKI

Singapore

DETPM-AA

AUI

DETPM-AA

AUI

DETPM-AA

AUI DETPM-AA

AUI

RETIXRCE DETPM-AA

AUI

26 2525

3

4

5

7

6

88

6

7

5

4

3

99 87654319

25

EPIM-F2

EPIM-F2

Cabletron SEHI-24

87654319

26

26 EPIM-F2

EPIM-F2

Cabletron SEHI-24

24

RETIXBridge

RETIXBridge

2

2

ULS2x1.544MbTo GenevaDEChubs

24

25 "A"

"B"

Figure 1: GTC-L Central Site Overview


Cluster Configuration •••• 61 December 1997

8400

CIXCDDEMNA

16 PortStar

Coupler

4100CIPCADE500

4100CIPCADE500

All Cables FDDIDUAL ATTACHED

DAS - BN24B

CIXCD

HSJ50HSJ50DiscFarm

(24 RZ29)

10BaseFL

DETPM-AA

UTP

UTP

DEMNADETPM

-AA

UTP

8400

CIXCDDEMNA

CIXCD

DEMNA

DETPM-AA

DETPM-AA

UTP

UTP

UTP

10BaseFL

CI Node: 0

CI Node: 1

CI Node:3

CI Node:2

CI Node:7

CI Node:6

CI Node:4

CI Node:5

2x128KBTo 90DD

T-DESK LAN

DEChub 900

DECserver 90M

PORTswitch 900TP

PORTswitch 900FPDECswitch 900EF

DECswitch 900EF

RETIXBridge

AUI

DECserver 90M

DEChub 900

DECserver 90M

PORTswitch 900TP

PORTswitch 900FP

DECswitch 900EF

DECswitch 900EF

RETIXBridge

AUI

DECserver 90M

DECserver Ports1) VT Terminal2) Error Port3) Security Port4) Automation Port5) xGPS Feed6) xGPS Feed7) VT Terminal8) VT Terminal

DETPM-AA

DETPM-AA

clearVISNPC

UTP:BN24F

DECnis 600

W601W601

UTP DETPM-AA

DETPM-AA

AUI

AUI

DECnis 600

W601W601

UTPDETPM-AA

DETPM-AA

AUI

AUI


DETPM-AAUTP

OSFEVAXstation

CabletronSEHI-22

Cisco2514

DETPM-AA

ToOMN Mgt.

LAN

Cisco2514

DETPM-AA

AUIAUI


DETPM-AAUTP

OSFEVAXstation

CabletronSEHI-22

NFRNFR

2x128KBTo GTC-LSEHI-24

RETIXBridge

AUIRETIXBridge

AUI DETPM-AA

DETPM-AA

Alternateconfiguration for

Normal Mode, andContingency Mode.An Ethernet switchmay be installed at

this point

Alternateconfiguration for

Normal Mode, andContingency Mode.An Ethernet switchmay be installed at

this point

DRAWN BYJeff Weissman

D2000-2 Rev 1.0D2 GTC-G Central Site Configuration,

With Contingency, No DSSFILENAME

D2 GENEVA CENTRAL SITE NO DSS.VSD

DATE19-NOV-1997

Figure 2: GTC-G Central Site Overview



Figure 3: GTC-L DEChub Backplane Layout

ThinWire:D2 FE LAN

Ethernet 1:T-Desk WAN LAN

Ethernet 3:OCS LAN

Ethernet 5:RTN Bridge LAN

Ethernet 6:RTN NRM &FE LAN

DECserver 90M

Retix Bridge toHTC T-Desk LAN

HOST

RETIX Bridge toNY PCS

RETIX Bridge toSNG PCS

RETIX Bridge toRCE PCS

RETIX Bridgeto GEV PCS

NRM NT GEMS NDCS

RETIX Bridge toUKI PCS

NRM FE NT NRM

NFR SNIFFER

DEC

switc

h 90

0EF

RTN

Net

wor

kD

ECsw

itch

900E

FH

AL N

etw

ork

601

DECnis

DRAWN BYLATHAM

D2000-2 Rev 2.1

D2 London DEChub Backplane Layout

FILENAMED2 LONDON DECHUB BACKPLANE.VSDDATE

20-NOV-1997

OCS CISCO to OMNMgt. LAN

LAT Only

Legend:= in DEChub

= Fibre

= Twisted Pair

Cabletron Hubswitched to herein disaster mode.

DECserver 90M

Ethernet 2:Cent. Sys. Monitor LAN

OSFE Emer. T-Desk

Ethernet 4:HOST LAN

601

D7

D3To USA

T-Desk LAN

D5

C1

Cabletron Hub toGeneva

Geneva

C4 C2 C3 C5

TO OMN Mgt. LAN

A3A2A1

A7 A8 B1 B2 B3 B4 B5 B6

C7 C8 D1

Slot 4

Slot 3


Cluster Configuration •••• 81 December 1997

Figure 4: GTC-G DEChub Backplane Layout

ThinWire:D2 FE LAN

Ethernet 1:T-Desk WAN LAN

Ethernet 3:OCS LAN

Ethernet 5:RTN Bridge LAN

Ethernet 6:RTN NRM &FE LAN

DECserver 90M

Retix Bridge toHTC T-Desk LAN

HOST

NFR SNIFFER

DEC

switc

h 90

0EF

RTN

Net

wor

kD

ECsw

itch

900E

FH

AL N

etw

ork

601

DECnis

DRAWN BYJEFF LATHAM

D2000-2 Rev 1.0

D2 DEChub Backplane Layout

FILENAMED2 GENEVA DECHUB BACKPLANE.VSD

DATE19-NOV-1997

OCS CISCO to OMNMgt. LAN

LAT Only

Legend:= in DEChub

= Fibre

= Twisted Pair

Cabletron Hubswitched to herein disaster mode.

DECserver 90M

Ethernet 2:Cent. Sys. Monitor LAN

OSFE

Ethernet 4:HOST LAN

601

D7

D3To USA

T-Desk LAN

D5

C1

Cabletron Hub toLondon

London

C4 C2 C3 C5

TO OMN Mgt. LAN

A3A2A1

B4 B5 B6

C8 D1

Slot 4

Slot 3



Figure 5: TDesk Room Layout

DRAWN BYLATHAM

D2000-2 Rev 1.0

D2 Hauppauge Site With DSS

FILENAMED2 HAUP WITH DSS.VSD

DATE19-NOV-1997

FN100-8TX

PDC DSS_A(live)

MR9T-E

OPS ADMWKSTN

EPIM-CBRIM-E6

ESXMIM-F2 EPIM-T

DECbrouter 90ToHPSN

FN100-8TX

BDCDSS_A(stdby)

MR9T-E

OPS ADMWKSTN

EPIM-CBRIM-E6

ESXMIM-F2EPIM-T

DECbrouter 90

DEREN

DEMPR

1 2 3 4

RETIX RETIX RETIX RETIX

1

C

A

B

C

A

B

B

A

C

A

B

C

2

3

4

C

A B

C

A B

C

BA

C

A B

Chan 1 Chan 2 Chan 1 Chan 2

London2 x 128kb

Geneva2 x 128kb

T-Desk LAN

DEMPR DELNI DEMPRDELNI

Ganged Switches:SLP Live Selector

A=LondonB=Geneva

Ganged Switches:Retix SelectorA= Retix "A"B= Retix "B"

Cabletron MMACCabletron MMAC

Cisco 2514

DEFLM-AA

Cisco 2514

DEFLM-AA

DECserver 700 DECserver 700

VT420VT420

R/O NDCSVAXstation

BOJ IMFVAXstation

T-DESKVAXstation

LA75

LA75

DECserver 700DECserver 700

VT420

SLPTerminal

VT420

Devel.Terminal

OSFEVAXstation

BOJ IMFVAXstation

CSFEVAXstation

LA75

LA75

90 DavidsT-Desk Room

SLPTerminal

Devel.Terminal

DSS T-DESKWorkstation

LASERPRINTER

CabletronMR9T-E

DSS T-DESKWorkstation

LASERPRINTER

CabletronMR9T-E

ToHPSN

90 DavidsComputer Room


Cluster Configuration •••• 10

2.2 Central System AlphaServer 8400Proper console settings must be established on the AlphaServer 8400 at each of the two Host nodes (live andstandby). Use the following procedure:

1. At the console, turn key to the Enable position.

2. Set terminal width to 132 characters.

3. At the console prompt, enter the following commands:>>>set bootdef_dev dua320.1.0.2.0,dua320.0.0.2.0,dua420.1.0.2.0,dua420.0.0.2.0

>>>set boot_osflags 0,0 (for Host A)

Or

>>>set boot_osflags 1,0 (for Host B)

>>>set auto_action HALT

>>>set boot_reset ON

>>>set mode adv

>>>create -nv STAB (ignore error message)

>>>set STAB DKA> fl,0,0

>>>set cpu 0

>>>set cpu_enabled ff

>>>set cpu_primary ff

>>>set d_harderr halt

>>>set d_report summary

>>>set d_softerr continue

>>>set enable_audit ON

>>>set interleave default

>>>set language 36



2.3 Operations Control System AlphaServer 4000Two AlphaServer 4000s act as an Operational Control System (OCS). The two AlphaServer 4000s are nodeson the CI, providing for automated system management functions. This section details information specific tothe OCS AlphaServer 4000s.

Set the terminal width to 132 characters.

At the console prompt, enter the following commands to configure the AlphaServer consoles:POO>>>set bootdef_devdua320.1.0.5.0,dua320.0.0.5.0,dua420.1.0.5.0,dua420.0.0.5.0

POO>>>set boot_osflags 2,0 (for OCS C)

OrPOO>>>set boot_osflags 3,0 (for OCS D)

POO>>>set auto_action HALT

POO>>>set boot_reset ON

POO>>>set enable_audit ON

Note: After configuring the consoles, make sure the HALT button is OUT. The HALT button is locatedon the front of the AlphaServer 4000, on the right side. It is the middle button. The HALT button shouldnot be depressed and the green light should be off.

2.4 Storage Devices and ControllersThe D2000-2 Central System configuration includes a set of SCSI disk drives contained in a Storage Workscabinet. Two HSJ50 controllers provide automatic failover and load balancing capability.

2.4.1 HSJ and Disk ConfigurationThe HSJ50 controllers provide performance and backup capability for the Host application disks and for themaintenance and administrative disks. The HSJ is configured with 128 MB of write-back cache, which isenabled only for the Database, Journal, and Transaction Log disks. Each HSJ is configured to support dual-data-link operations over the CI, utilizing both A and B CI paths.

D2000-2 disks are defined as logical volumes. The logical volumes are made up of the two-member Host-based shadow sets shown in Table 1. Each two-member shadow set contains two SCSI disk drives, whereeach disk is the same type with a minimum of 4.3 GB of disk storage.

In order to load balance the I/O for each HSJ controllers in the dual-redundant set, each disk drive has apreferred path. Automatic load balancing occurs when the failed HSJ is brought back into the set. In the event


Cluster Configuration •••• 12

of a controller failure, the other controller in the set will service all disks. Automatic load balancing willoccur when the failed HSJ is restarted.

Disk Description Virtual Drive Volume Label Logical Name PhysicalDeviceNames

System DSA1 SYSTEM SYS_SYSTEM 320,420

Database DSA2 DATABASE SYS_DATABASE 110,210

Journal DSA3 JOURNAL SYS_JOURNAL 300,400

Statistics DSA4 STATS SYS_STATS 500,600

Transaction Log DSA5 XACT SYS_XACT 310,410

PageSwap DSA6 PAGESWAP SYS_PAGESWAP 100,200

Database Dump1 DSA7 DBDMP1 SYS_DBDMP1 530,630

Database Dump2 DSA8 DBDMP2 SYS_DBDMP2 540,640

Staging Disk DSA9 STAGE SYS_STAGE 510,610

Staging Disk1 DSA10 STAGE1 SYS_STAGE1 520,620

Table 1: Physical Disks as Shadow Sets/Logical Names

2.4.1.1 HSJ000 and HSJ001 Switch settingsThe following table shows configuration settings for the HSJ controllers -- HSJ000 and HSJ001.

Switch HSJ Values

CACHE_FLUSH_TIMER DEFAULT (10 seconds)

CACHE_POLICY A (default)

CACHE_UPS NOCACHE_UPS (default)

CI_ARBITRATION SYNCHRONOUS (default)

CI_4K_PACKET_CAPABILITY CI_4K_PACKET_CAPABILITY

DUAL_REDUNDANCY OTHER_CONTROLLER



Switch HSJ Values

HOST_FUNCTION N/A

ID ci_port_#

MAX_NODES 8

MAXIMUM_HOSTS 6

MSCP_ALLOCATION_CLASS 1

VALID CI NODE 0 or 1

PATH PATH_A (PATH A is ON)

PATH_B (PATH B is ON)

PREFERRED_ID N/A

PROMPT HSJci_port_#>

For example, HSJ000>

SCS_NODENAME HSJci_port#

For example, HSJ001

TERMINAL_PARITY

NO_TERMINAL_PARITY

NO_TERMINAL_PARITY (default)

TERMINAL_SPEED 9600 (default)

TIME DD-MMM-YYY: HH:MM:SS

TMSCP_ALLOCATION_CLASS 1

TRANSFER_RATE_REQUESTED N/A

Table 2: Switch Settings for HSJ000 and HSJ001 Controllers

2.4.2 Storage Works LayoutAll Central System disk drives are located in a ten-shelf Storage Works cabinet. One shelf contains both HSJcontrollers. Six shelves contain the Storage devices. Figure 6 on Page 14 shows the relationship of theStorage Works cabinet to the star coupler at the Central Site.



Figure 6: D2000-2 Central Site Disk Configuration

DRAWN BYJEFF WEISSMAN

D2000-2 Rev 1.1

D2 DTC Central Site Disc Configuration

FILENAMED2 DTC DISC LAYOUT.VSD

DATE29-OCT-1997

16 PortStar

Coupler

4100CIPCADE500

DETPM-AA

DETPM-AA

CI Node:3

CI Node:2

CI Node:7

DEChub 900

DECserver 90MPORTswitch 900TP

PORTswitch 900FP

DECswitch 900EF

DECswitch 900EF

DECserver 90M

8400

CIXCDDEMNA

CIXCD

DEMNA

4100CIPCADE500

DETPM-AA

DETPM-AA

CI Node:4

CI Node:5

CI Node:6

DEChub 900

DECserver 90MPORTswitch 900TP

PORTswitch 900FP

DECswitch 900EF

DECswitch 900EF

DECserver 90M

8400

CIXCDDEMNA

CIXCD

DEMNA

HSJ50

SW8XP

StorageWorks Cabinet

HSJ50

SW8XP

29

29

29

29

29

29

29

29

29

29

29

29

29

2929

29

29

29

29

29

29

29

29

29P P

P P

P P

P P

P P

P P

TZ88N

B

B

CI Node:0

CI Node:1



Each Storage Works cabinet shelf is divided into 8 slots, numbered 0 to 7, where slot 0 has the highestpriority. The last two slots on each shelf (slot 6 and slot 7) contain redundant power supplies for the shelf,and the first 6 slots of each shelf are available for SCSI disk drives. Refer to Figure 7 for the Storage Worksshelf layout.

Shelves 1, 3, and 5 in the cabinet contain the first member of each shadow set of disks, with a preferred pathto the first HSJ. Shelves 2, 4, and 6 contain the second member of each shadow set and have a preferred pathto the second HSJ.

Slot 7 Slot 6 Slot 5 Slot 4 Slot 3 Slot 2 Slot 1 Slot 0

Shelf 1 Power supply Power supply Cachebattery

TZ887 TAPE Drive *Database Disk PageSwapDisk

Shelf 2 Power supply Power supply Cachebattery

*Database Disk PageSwapDisk

Shelf 3 Power supply Power supply Spare TransportDisk

System *XACT *Journal

Shelf 4 Power supply Power supply Spare TransportDisk

System *XACT *Journal

Shelf 5 Power supply Power supply DBDump 2

DBDump 1

Staging 1Disk

Staging Disk StatisticsDisk

Shelf 6 Power supply Power supply DBDump 2

DBDump 1

Staging 1Disk

Staging Disk StatisticsDisk

* Writeback cache enabled

Figure 7: Storage Works HSJ000/HSJ001 Shelf Layout

2.4.2.1 Disk Switch SettingsThe disks controlled by the HSJs require switch settings to determine such parameters as which controller isthe preferred path, whether disk caching is enabled, etc.

Table 3 shows switch settings for each of the 24 disks. Table 4 shows settings for the tape drives. Devicesare named following this convention:

Device Type + Storage Shelf + Slot Position + 0 for HSJ Device

For example: 420 is a device on second slot of fourth shelf, served by HSJ.

(Refer to Table 1 on Page 12 for additional identifying information.)



Switch Settings

VolumeLabel

DeviceName

MAXIMUM_CACHED_TRANSFER

PREFERRED_PATH/ READ_CACHE

NOREAD/CACHE

RUN/NO_RUN

WRITE_PROTECT/NOWRITE_ PROTECT

WRITEBACK_CACHE/NOWRITEBACK_CACHE

PAGESWAP

D100

32 OTHER_CONTROLLER

READ_CACHE RUN NOWRITE_PROTECT NOWRITEBACK_CACHE

DATABASE

D110

32 OTHER_CONTROLLER

READ_CACHE RUN NOWRITE_PROTECT NOWRITEBACK_CACHE

PAGESWAP

D200

32 THIS CONTROLLER NO_READ_CACHE

RUN NOWRITE_PROTECT NOWRITEBACK_CACHE

DATABASE

D210

32 THIS CONTROLLER READ_CACHE RUN NOWRITE_PROTECT WRITEBACK_CACHE

JOURNAL

D300

32 OTHER_CONTROLLER

READ_CACHE RUN NOWRITE_PROTECT WRITEBACK_CACHE

XACT

D310

32 OTHER_CONTROLLER

READ_CACHE RUN NOWRITE_PROTECT WRITEBACK_CACHE

SYSTEM

D320

32 OTHER_CONTROLLER

NOREAD_CACHE


TRANSPORTDISK

D330

32 OTHER_CONTROLLER

NOREAD_CACHE


SPARE

D340

32 OTHER_CONTROLLER

NOREAD_CACHE


JOURNAL

D400


XACT

D410


SYSTEM

D420

32 THIS CONTROLLER NOREAD_CACHE


TRANSPORTDISK

D430



SPARE

D440



STATS

D500

32 OTHER_CONTROLLER

NOREAD_CACHE


STAGE

D510

32 OTHER_CONTROLLER

NOREAD_CACHE




Switch Settings

VolumeLabel

DeviceName

MAXIMUM_CACHED_TRANSFER

PREFERRED_PATH/ READ_CACHE

NOREAD/CACHE

RUN/NO_RUN

WRITE_PROTECT/NOWRITE_ PROTECT

WRITEBACK_CACHE/NOWRITEBACK_CACHE

STAGE1

D520

32 OTHER_CONTROLLER

NOREAD_CACHE


DB DUMP1

D530

32 OTHER_CONTROLLER

NOREAD_CACHE


DB DUMP2

D540

32 OTHER_CONTROLLER

NOREAD_CACHE


STATS

D600



STAGE

D610



STAGE1

D620



DB DUMP1

D630



DB DUMP2

D640



Table 3: Disk Switch Settings

2.4.2.2 Tape Switch Settings

Switch HSJ Values

DEFAULT_FORMAT TZ88_COMPRESSION (CLI_SELECTED)

PREFERRED_PATH

NO_PREFERRED_PATH

NO_PREFERRED_PATH

Table 4: TZ88 (T140) Switch Settings

2.5 Rebooting after Initial InstallationWhen performing a first-time installation, it is important that AFTER ALL SOFTWARE has been installed, areboot of ALL CLUSTER NODES be performed. This is to ensure that all systems are functioning correctly.This should be done by first shutting down the cluster nodes (RDTSA, RDTSB, RDTSC and RDTSD) andthen rebooting them in the opposite order (RDTSD, RDTSC, RDTSB, RDTSA).


Version: 02.01-0 DECserver Configuration •••• 19

3. DECserver Configuration

3.1 DECserver OverviewThe Dealing 2000-2 Central System uses the following DECservers:

• Two DECservers at the Central Site, provide:

- Local access within the GTC:

- Global time synchronization feed for each node in the Central System.

- Security serial feed to either a hard-copy printer device or monitoring application.

- Error log serial feed to either a hard-copy printer device or monitoring application.

• Each of these DECservers has a standby or spare DECserver associated with it, for a total of fourDECservers at the Central Site.

• Two DECservers at Hauppauge provide T-Desk terminal connections and development remote accessconnectivity. Again, each of these DECservers at Hauppauge has a standby or spare.

3.2 GTC-L DECserver Configuration

3.2.1 DECserver Port AssignmentsDECserver port configuration must be performed as part of the initial hardware configuration. However,DECservers cannot be configured until DECserver software has been loaded. Configurations forDECserver ports are shown in Table 5 and Table 6.

Port Description

PORT 1 Terminal (Controllers)PORT 2 Error Port (Host A) (Not Wired)PORT 3 Security Port (OCS C) (to RCC

or OCM)PORT 4 Automation Port (OCS C) (Not

Wired)PORT 5 Time Sync (Host A) (GPS)PORT 6 Time Sync (OCS C) (GPS)PORT 7 Terminal (Local Use)PORT 8 Terminal (Local Use)

Table 5: GTC-L Central Site Host DECserver 1 Port Assignments (Hub A/Slot 1)(Hub B/Slot 1 is the backup.)


DECserver Configuration •••• 20 1 December 1997

Port Description

PORT 1 Terminal (Emergency T-Desk)PORT 2 Error Port (Host B) (Not

Wired)PORT 3 Security Port (OCS D) (to

RCC or OCM)PORT 4 Automation Port (OCS D) (Not

Wired)PORT 5 Time Sync (HOST B) (GPS)PORT 6 Time Sync (OCS D) (GPS)PORT 7 Terminal (Local Use)PORT 8 Terminal (Local Use)

Table 6: GTC-L Central Site Host DECserver 2 Port Assignments (Hub A/Slot 2)(Hub B/Slot 2 is the backup.)

3.2.2 Configuring the DECServer 90M PortUse the following procedures to configure each DECServer 90M. There are 4 DECServers (2 for DEChub A

and 2 for DEChub B) and each DECServer has 8 ports.

1. Connect your video terminal to Slot 1 on the 90M on DEChub A, terminal Port 1.

2. Set VT characteristics to the following:

9600 baud

8 bits, no parity

XON/XOFF flow control

3. Press RETURN.

4. At the Enter username> prompt, type any name. This will display the Local> prompt.

5. At the Local> prompt, enter:

Local> set privilege

This will display the Password> prompt.

6. At the Password> prompt, enter:

Password> system

This will display the Local> prompt.


Local> change server name lnfs01



8. At the Local> prompt, to verify the server name, enter:

Local> list server


Local> change port 2,3,4,5,6 access remote break disabled type ansi

Local> change port 5,6 broadcast disabled flow control disabled speed 4800

NOTE: Ports 1, 7, 8 are “terminal ports” which use the factory default settings.

10. Change the terminal port names as follows:Local> change port 1 name port_1

Local> change port 2 name port_2







11. To verify terminal ports, enter:Local> list port 1

Type this command for each of the 8 ports. The results of this command are displayed at the end of this

procedure. Note: If a port does not match the enable characteristics display, use the Change command

to enable or disable characteristics for each port. Then list the port again to verify terminal ports.


Local> logout

The message displays: Local> Logged out port 1 on server LNFS01

13. Repeat the above procedure, starting with Step 1, for each of the following DECServer 90Ms:

For DEChub A 90M, Slot 2 ⇒ Use DECServer name lnfs02

For DEChub B 90M, Slot 1 ⇒ Use DECServer name lnfs03

For DEChub B 90M, Slot 2 ⇒ Use DECServer name lnfs04

3.2.3 List Port CommandsFollowing are the results of the list port commands for lnfs01 (DEChub A 90M, Slot 1, Ports 1-8).



Local> list port 1

Port 1: Server: LNFS01

Character Size: 8 Input Speed: 9600

Flow Control: XON Output Speed: 9600

Parity: None Signal Control: Disabled

Stop Bits: Dynamic

Access: Local Local Switch: None

Backwards Switch: None Name: PORT_1

Break: Local Session Limit: 4

Forwards Switch: None Type: Ansi

Default Protocol: LAT Default Menu: None

Dialer Script: None

Preferred Service: None

Authorized Groups: 0

Enabled Characteristics:

Broadcast, Input Flow Control, Output Flow Control

Local> list port 2





Stop Bits: Dynamic

Access: Remote Local Switch: None


Break: Disabled Session Limit: 1



Dialer Script: None







Local> list port 3





Stop Bits: Dynamic






Dialer Script: None





Local> list port 4





Stop Bits: Dynamic






Dialer Script: None



Enabled Characteristics:Broadcast, Input Flow Control, Output Flow Control



Local> list port 5



Flow Control: None Output Speed: 4800


Stop Bits: Dynamic






Dialer Script: None




Local> list port 6





Stop Bits: Dynamic






Dialer Script: None






Local> list port 7





Stop Bits: Dynamic






Dialer Script: None




Autobaud, Autoprompt, Broadcast, Failover, Input Flow Control, Lock, Loss Notification, MessageCodes, Output Flow Control, Verification

Local> list port 8





Stop Bits: Dynamic






Dialer Script: None



Enabled Characteristics: Autobaud, Autoprompt, Broadcast, Failover, Input Flow Control, Lock,Loss Notification, Message Codes, Output Flow Control, Verification



3.2.4 Setting DECServer Server NameThe DECserver server name must be set. Perform the following steps to set the server name for each of theservers.

1. Log into the DECserver and enter the following:SET PRIV password

where:password is the password obtained from the person who set up SERVER.

2. Enter the following commands to set the server name.SET SERVER NAME LNFS01

DEFINE SERVER NAME LNFS01

(Names of other servers to be used in these commands are: LNFS02, LNFS03 and LNFS04.)

3. Reboot the DECserver by entering the following command:INIT DELAY 0

4. Log out of the DECserver.

3.3 GTC-G DECserver Configuration

3.3.1 DECserver Port AssignmentsDECserver port configuration must be performed as part of the initial hardware configuration. However,DECservers cannot be configured until DECserver software has been loaded. Configurations forDECserver ports are shown in Table 7 and Table 8.

Port Description

PORT 1 Terminal (Controllers)PORT 2 Error Port (Host A) (Not Wired)PORT 3 Security Port (OCS C) (to RCC

or OCM)PORT 4 Automation Port (OCS C) (Not

Wired)PORT 5 Time Sync (Host A) (GPS)PORT 6 Time Sync (OCS C) (GPS)PORT 7 Terminal (Local Use)PORT 8 Terminal (Local Use)

Table 7: GTC-G Central Site Host DECserver 1 Port Assignments (Hub A/Slot 1)(Hub B/Slot 1 is the backup.)



Port Description

PORT 1 TERMINALPORT 2 Error Port (Host B) (Not

Wired)PORT 3 Security Port (OCS D) (to

RCC or OCM)PORT 4 Automation Port (OCS D) (Not

Wired)PORT 5 Time Sync (HOST B) (GPS)PORT 6 Time Sync (OCS D) (GPS)PORT 7 Terminal (Local Use)PORT 8 Terminal (Local Use)

Table 8: GTC-G Central Site Host DECserver 2 Port Assignments (Hub A/Slot 2)(Hub B/Slot 2 is the backup.)

3.3.2 Configuring the DECServer 90M PortUse the following procedures to configure each DECServer 90M. There are 4 DECServers (2 for DEChub A

and 2 for DEChub B) and each DECServer has 8 ports.

1. Connect your video terminal to Slot 1 on the 90M on DEChub A, terminal Port 1.


9600 baud

8 bits, no parity


3. Press RETURN.






Password> system



Local> change server name GTFS01




Local> list server


Local> change port 2,3,4,5,6 access remote break disabled type ansi

Local> change port 5,6 broadcast disabled flow control disabled speed 4800

NOTE: Ports 1, 7, 8 are “terminal ports” which use the factory default settings.














Local> logout

The message displays: Local> Logged out port 1 on server GTFS01

13. Repeat the above procedure, starting with Step 1, for each of the following DECServer 90Ms:

For DEChub A 90M, Slot 2 ⇒ Use DECServer name GTFS02

For DEChub B 90M, Slot 1 ⇒ Use DECServer name GTFS03

For DEChub B 90M, Slot 2 ⇒ Use DECServer name GTFS04

3.3.3 List Port CommandsFollowing are the results of the list port commands for GTFS01 (DEChub A 90M, Slot 1, Ports 1-8).



Local> list port 1

Port 1: Server: GTFS01




Stop Bits: Dynamic






Dialer Script: None





Local> list port 2





Stop Bits: Dynamic






Dialer Script: None







Local> list port 3





Stop Bits: Dynamic






Dialer Script: None





Local> list port 4





Stop Bits: Dynamic






Dialer Script: None



Enabled Characteristics:Broadcast, Input Flow Control, Output Flow Control



Local> list port 5





Stop Bits: Dynamic






Dialer Script: None




Local> list port 6





Stop Bits: Dynamic






Dialer Script: None






Local> list port 7





Stop Bits: Dynamic






Dialer Script: None




Autobaud, Autoprompt, Broadcast, Failover, Input Flow Control, Lock, Loss Notification, MessageCodes, Output Flow Control, Verification

Local> list port 8





Stop Bits: Dynamic






Dialer Script: None



Enabled Characteristics: Autobaud, Autoprompt, Broadcast, Failover, Input Flow Control, Lock,Loss Notification, Message Codes, Output Flow Control, Verification






2. Enter the following commands to set the server name.SET SERVER NAME GTFS01

DEFINE SERVER NAME GTFS01

(Names of other servers to be used in these commands are: GTFS02, GTFS03, and GTFS04.)



3.4 T-Desk DECserver Configuration

3.4.1 DECserver Port AssignmentsDECserver port configuration must be performed as part of the initial hardware configuration. However,DECservers cannot be configured until DECserver software has been loaded. Configurations forDECserver ports are shown in - Table 9.

Port Description

PORT 1 TerminalPORT 2 TerminalPORT 3 TerminalPORT 4PORT 5PORT 6PORT 7PORT 8

Table 9: T-Desk DECserver HPFS05, 06, 07, 08 Port Assignments

3.4.2 Configuring the DECServer 700 PortUse the following procedures to configure each DECServer 700. There are 4 DECServers and each

DECServer has 8 ports.



1. Connect your video terminal to Slot 1 on the DECServer 700, terminal Port 1.


9600 baud

8 bits, no parity


3. Press RETURN.






Password> system



Local> change server name HPFS05


Local> list server









Local> logout

The message displays: Local> Logged out port 1 on server HPFS05



12. Repeat the above procedure, starting with Step 1, for each of the following DECServer 700s:

For DEC Server 700 ⇒ Use DECServer name hpfs06



3.4.3 List Port CommandsFollowing are the results of the list port commands for HPFS05 (DECServer 700, Ports 1-3).

Local> list port 1

Port 1: Server: HPFS05




Stop Bits: Dynamic






Dialer Script: None







Local> list port 2





Stop Bits: Dynamic






Dialer Script: None





Local> list port 3





Stop Bits: Dynamic






Dialer Script: None










2. Enter the following commands to set the server name.SET SERVER NAME HPFS05

DEFINE SERVER NAME HPFS05

(Names of other servers to be used in these commands are: HPFS06, HPFS07, and HPFS08.)




Version: 02.01-0 Software Management Utility •••• 39

4. Software Management Utility

4.1 Installation

4.1.1 GeneralThis chapter details the procedure for installing the SMU. The SMU must be installed before it can be usedto install D2000-2 Central Systems Applications. The installer should be familiar with VMS and DCLcommands and utilities before proceeding.

Installation of the SMU is required, on the one of the OCS AlphaServer 4000 nodes, after every new releaseof the utility or as otherwise directed by Reuters Development.

Note: The SMU should be run from a host node (RDTSA, RDTSB). The SMU can be installed on either of theOCS nodes.

4.1.2 Installation ProcedureThis installation should only be performed when specifically called for in the Dealing 2000-2 Central SystemInstallation Release Note. The following steps detail the procedure necessary to install the SMU. Thesesteps should be followed in the order presented to ensure successful installation.

1. Load the SMU release tape onto the selected tape device and place the device online.

2. At the console, log into a privileged account.

3. Set the default directory by entering the following DCL command:$ SET DEFAULT SYS$SYSDEVICE:[000000]

4. Mount the tape using the following DCL command:

$ MOUNT/FOREIGN tape_dev:

where: tape_dev is the name of the selected tape device (e.g., $1$MUA0).

5. Enter the following DCL command to copy the SMU saveset to disk:$ BACKUP/LOG/NEW_VER tape_dev:D2_INS_ver.BCK SYS$SYSDEVICE:[000000]

where: tape_dev is the name of the selected tape device (e.g., $1$MUA0),andver is the six digit version number, without spaces or otherpunctuation, as stated in the Dealing 2000-2 Central System

Installation Release Note.


Software Management Utility •••• 40 1 December 1997

6. Enter the following to dismount the tape:

$ DISMOUNT tape_dev:

where: tape_dev is the name of the selected tape device (e.g., $1$MUA0).

7. Enter the following command to invoke the INSTALL_D2_INSTALL.COM command procedure. Thisprocedure will create the proper directory structure, unwind the saveset, and define the necessary logicalsand symbols.$ @INSTALL_D2_INSTALL

8. A series of Informational and Success messages will be displayed. Upon successful completion of theinstallation, a message so stating will also be displayed.

9. Log out of the privileged account.

4.2 Operation

4.2.1 GeneralSeven major functions are provided by the Software Management Utility: LOAD, ACTIVATE, ROLLBACK,DELETE, SHOW CURRENT VERSION, INSTALL THIRD-PARTY, and SHOW/MODIFYCONFIGURATION. This section describes the interface used to accomplish these tasks.

Installations of new software are accomplished in two phases: LOAD and ACTIVATE. When a release tapeis received, the first step is to load the release software onto the system. At any time thereafter, the installerwill use the ACTIVATE function to complete the transition to the new version.

ROLLBACK permits the installer to return to the previous configuration.

Once an installation has been deemed successful, the DELETE version function can be used to removeobsolete software from the system, thereby freeing-up system resources. To prevent the inadvertent removalof essential release versions, neither the current nor previous release versions can be deleted.

SHOW CURRENT VERSION is used check all versions currently on a target system.

Third party software products are loaded and activated using the INSTALL THIRD-PARTY function.

The SHOW/MODIFY CONFIGURATION function may be used, at any time, to either view or change anyHost or Operations Control System configuration parameters.

4.3 Menu DescriptionsEach of the following sections will describe the functionality available from each of the menus. Theoperation and use of each menu is described beginning with Load on page 45 .

4.3.1 Main MenuThe SMU Main menu is the starting point for all utility operations. This menu is displayed whenever theSMU is invoked. Refer to Figure 8 below.



1 - LOAD RELEASE...2 - ACTIVATE RELEASE...3 - ROLLBACK RELEASE...4 - DELETE RELEASE...5 - SHOW CURRENT VERSIONS6 - INSTALL THIRD-PARTY7 - SHOW/MODIFY CONFIGURATION...X - EXIT

CHOICE ? > _

SOFTWARE MANAGEMENT UTILITY

Version: 02.01-00

Figure 8: SMU Main Menu

4.3.2 Load Release SubmenuThe Load Release submenu is depicted below in Figure 9. This submenu is the starting point for all LOADoperations.

1 - HOST...X - EXIT

CHOICE ? > _

LOAD RELEASE

Figure 9: SMU Load Release Submenu

4.3.2.1 Options Submenu

When HOST has been selected from the Load Release submenu, the Host Options submenu will bedisplayed as shown in Figure 10.



1 - ENVIRONMENT2 - APPLICATIONX - EXIT

CHOICE ? > _

HOST OPTIONS

Figure 10: SMU Host Options Submenu

4.3.3 Activate Release SubmenuThe Activate Release submenu offers a list of all software releases which have been loaded onto the system.A typical Activate Release submenu is shown below in Figure 11. This list is used by the installer to selectthe desired software release to be activated. The order in which releases appear on the submenu is the orderin which they were loaded.

1 - HOSENV_020000 (LOADED on 20-JAN-1992 13:12:42.49)2 - HOST_050400 (LOADED on 24-JAN-1992 15:17:07.46)X - EXIT

Choose an installation to activate > 2

You have chosen HOST_050400 to be activated

Please confirm (Y/N)

ACTIVATE RELEASE

Figure 11: SMU Activate Release Submenu

4.3.4 Rollback Release DisplayThe Rollback Release submenu permits the installer to return the system to a previous configuration. Thelast created Activation group (described in the Activate Host on Page 47) is presented to the installer for thepurposes of selecting a rollback configuration. The installer will be given the choice to rollback either all ornone of the releases in the group. A sample display is shown below in Figure 12.



Subsystem HOST_050100 will rollback to HOST_050500Subsystem HOSENV_011000 will rollback to HOSENV_010600

Do you wish to rollback ALL of the above releases (Y/N)? n

Figure 12: SMU Rollback Release Display

4.3.5 Delete Release SubmenuThe Delete Release submenu is displayed whenever DELETE is chosen from the SMU Main menu. Thisselection permits the installer to remove obsolete software release versions from the system. This menu isshown below in Figure 13.

1 - HOST...X - EXIT

CHOICE ? > _

DELETE RELEASE

Figure 13: SMU Delete Release Submenu

4.3.6 Show Current Versions DisplayThis function permits the installer to check all versions currently on a target system. No submenu ispresented. However, a display similar to Figure 14 will appear below the Main menu.

Current versions are:

HOSENV Version 011000HOST Version 050400

Press RETURN to continue...

Figure 14: Show Current Versions Display



4.3.7 Install Third-Party DisplayThe Install Third-Party submenu is used to install third-party software. Although this installation process isautomated, it does require some manual intervention. The user will be prompted to:

• Ensure that a full image backup of the Central System Host exists.

• Enter the third-party installation product name.

• Enter the version number of the product which is contained in the Dealing 2000-2 Central System Environment Release Notes.

A series of Informational messages will be displayed throughout the installation. Refer to the appropriateThird-Party Installation Manual for a complete description of all Informational messages. Upon completionof the installation, the SMU will return to the Main menu.

4.3.8 Show/Modify ConfigurationThe Show/Modify Configuration submenu (Figure 15) permits the user to view parameters in a specificgroup (e.g., NODES) and/or modify any of these parameters.

1 - NODES2 - DISKS3 - PORTS4 - SERVERS==========================X - RETURN TO MAIN MENU

CHOICE ? > _

CONFIGURATION

Figure 15: SMU Show/Modify Configuration Submenu

4.4 Starting the SMUThe SMU stores some of its control files in a common area regardless of the system on which it is operating.Therefore, only one SMU may be operating at any given time. Should an attempt be made to start a secondSMU, a warning message will be displayed showing the node on which the SMU is operating.

Note: The SMU can be run only on an OCS node (RDTSC, RDTSD). It cannot be used on a Host node(RDTSA, RDTSB).

Note: If for any reason the SMU must be terminated while an operation is in progress, enter CTRL-Y. Thiswill cause the SMU to perform an orderly termination. This may take some time depending on how far the



operation had proceeded prior to the termination request. Take no further action until prompted to do so.

A log file will be created in the RDTS_STATE directory to aid the installer in the event of an unsuccessfuloperation. The file name is based on the function which was being performed (i.e.,function_subsystem_version.LOG). For example, if the Host Environment, Version 01.00-00, were beingactivated, the filename ACTIVATE_HOSENV_010000.LOG would be assigned to the log file. As eachMenu/Submenu item is executed by the SMU, a new log file would be opened using this naming convention.

Use the following procedure to start the SMU:

1. At the appropriate console, log into an System Administrator account.

Note: If an System Administrator account has not yet been created, log into a SYSTEMaccount and proceed to step 3.

2. Select the Exit to DCL menu item.

3. Ensure that the console printer is on (if so equipped) and has a serviceableprinter ribbon and sufficient paper to log the entire installation procedure.

4. Then press CTRL-F2 so that all screen prompts and messages will be logged tothe printer.

5. Enter the following command at the DCL prompt to invoke the SMU:$ @RDTS_UPDATE:D2_INSTALL

This will result in the display of the SMU Main Menu (Figure 8). Prior to proceeding, refer to MenuDescriptions on page 40 if unfamiliar with this menu.

4.5 LoadThis function first creates the necessary versioned directory structure to hold the release. Due to the presenceon the target system of more than one version of release software, the need to segmenting these releases isrequired. The versioned directory structure provides this segmentation and is depicted in Figure 16. Aseparate directory exists for each release type and version. For example, hosenv_010200 contains HostEnvironment release version 1.02.

The LOAD function also unwinds a release saveset and loads the release software into the appropriatedirectories on the target system. Release loading is the first step in the installation process.



RDTS$SYS

log

pwd

state

update

exe

dem

sql

mgr

roll

exe

dem

sql

mgr

roll

sysmgr

roll

sysmgr

roll

host_010000 host_010200 hosenv_010000 hosenv_010200

Figure 16: Host Versioned Directory Structure (typical)

The only information required to load any software is the release type, version number and the name of thedevice containing the saveset. You will also be prompted as to whether or not you are satisfied with thebackup of your system. Since all LOADs are functionally identical, with the only exception being the releasetype and version, only one sample (Host Application version 010200) is presented below. To load otherrelease types/versions, simply substitute accordingly as specified in the applicable release notes.

1. Load the tape containing the release software onto the selected tape device (e.g.,$1$MUA0) and place the device online.

2. From the SMU Main menu select LOAD RELEASE. This will start the mirrorprocess and open the temporary log file.

3. The first prompt to appear will be the following "backup" prompt:Are you satisfied with the Backup of your system (Y/N) ? [N] :

If you have NOT recently performed a full image backup of the Central System Host,it is recommended that one be performed at this time. Enter Y if you are satisfiedand proceed with the next step. Otherwise, enter N to cancel the LOAD and exitthe SMU.

1. The LOAD RELEASE submenu (Figure 9) will now be displayed. Select theappropriate item from the submenu, in this case HOST.

2. The HOST OPTIONS submenu (Figure 10) will now be displayed. Select theappropriate item from the submenu, in this case APPLICATION.

3. The following "version number" prompt will now be displayed:Enter HOST APPLICATION version number as per release note

Enter version number (999999) or EXIT :

Enter the appropriate six-digit version number as specified in the release note andproceed with the next step. Otherwise, enter EXIT to cancel the LOAD.



1. The following prompt will appear requesting the device containing the releasesoftware (i.e., the selected tape device from step 1, above).

Enter Device Name containing the saveset or EXIT [$1$MUA0:] :

The brackets ([]) are used to indicate the default device, which in this case is$1$MUA0:. Press RETURN to accept the default or enter the appropriate devicename and proceed with the next step. Otherwise, enter EXIT to cancel theLOAD.

1. A series of messages will be displayed on the screen as the SMU performs itstask. At the conclusion of these messages will be a display similar to thefollowing:

Load of HOST_010200 complete at 13-MAR-1992 02:58:51.46

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

END OF LOAD UTILITY - COMPLETE

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

Press RETURN to continue....

1. At this point press RETURN to continue. The following will now be displayed:

LOG FILE CLOSED AT 13-MAR-1992 02:58:56.85LOG located in RDTS_STATE:LOAD_HOST_010200.LOGMIRROR process is terminating ...

The Log filename is: RDTS_STATE:LOAD_HOST_ version.LOG

where: version = the version number as entered from the release notes

The SMU will now redisplay the Main menu.

4.6 Activate HostOnce a release has been loaded into the appropriate directories on the system, it is ready for activation. Thiscan be performed at any time subsequent to the release loading and is the final step required to complete theinstallation of a release.

Note:: Host releases may not be activated while the Host application or dataservers are running.

A release that has been activated either begins or is added to an activation group, which consists of allsoftware activated over a three-day period. This period is determined by the time and date of activation ofthe first member of a group. For example, assume that on March 31 the Host Environment and Applicationwere activated. On April 2 the Third Party software was activated. These software releases comprise anactivation group. Any software activated after April 2 would begin a new activation group.

The function of the activation group is further explained in the Rollback on page 54.

The following sections detail the procedures necessary to activate a Host release. Specific instructions aregiven for the Host Environment and Application.



4.6.1 Activate Host Environment Software4.6.1.1 ParametersThe information contained in Table 10 through Table 13 is needed for the Environment activation procedure.

Node Description GTC-LConfiguration

GTC-GConfiguration

Host Cluster Alias Alias NameAlias Address

RDTS11.150

RDTS11.150

OCS Cluster Alias OCS Alias NameOCS Alias Address

LD2OCS11.163

GT2OCS11.166

First RDTS Host Node ‘0’ NameNode ‘0’ Address

RDTSA11.151

RDTSA11.151

Second RDTS Host Node ‘1’ NameNode ‘1’ Address

RDTSB11.152

RDTSB11.152

First RDTS OCS Node ‘2’ NameNode ‘2’ Address

RDTSC11.161

GTTSC11.164

Second RDTS OCS Node ‘3’ NameNode ‘3’ Address

RDTSD11.162

GTTSD11.165

ALT OCS ClusterAlias

ALT OCS NodeALT OCS Address

GT2OCS11.166

LD2OCS11.163

ALT OCS Node 1 ALT OCS Node 1ALT OCS Address 1

GTTSC11.164

RDTSC11.161

ALT OCS Node 2 ALT OCS Node 2ALT OCS Address 2

GTTSD11.165

RDTSD11.162

Table 10: Node Installation Parameters



Unit/Device Description Default

System Shadow Set Disk Virtual DeviceDisk 1 Physical DeviceDisk 2 Physical Device

DSA1$1$DUA320$1$DUA420

Page Swap Shadow Set Disk Virtual DeviceDisk 1 Physical DeviceDisk 2 Physical Device


Journal Disk (Sybase)Shadow Set

Disk Virtual DeviceDisk 1 Physical DeviceDisk 2 Physical Device


DB Disk (Sybase)Shadow Set



Statistic DiskShadow Set



XACT Shadow Set Disk Virtual DeviceDisk 1 Physical DeviceDisk 2 Physical Device


DBDMP1Shadow Set



DBDMP2Shadow Set





Unit/Device Description Default

Staging Shadow Set Disk Virtual DeviceDisk 1 Physical DeviceDisk 2 Physical Device


Staging 1 Shadow Set Disk Virtual DeviceDisk 1 Physical DeviceDisk 2 Physical Device

DSA10$1$DUA520$1$DUA620

Table 11: Disk Installation Parameters

Unit/Device Description Port GTC-LServer

GTC-GServer

Security Feed RDTSARDTSB

PORT_3PORT_3

LNFS01LNFS02

GTFS01GTFS02

Error Feed RDTSARDTSB

PORT_2PORT_2

LNFS01LNFS02

GTFS01GTFS02

Time Sync Port A RDTSA PORT_5 LNFS01 GTFS01

Time Sync Port B RDTSB PORT_5 LNFS02 GTFS02

Time Sync Port C RDTSC PORT_6 LNFS01 GTFS01

Time Sync Port D RDTSD PORT_6 LNFS02 GTFS02

Automation_PTR_Port RDTSC

RDTSD

PORT_4PORT_4

LNFS01LNFS02

GTFS01GTFS02

Table 12: Port Installation Parameters

Unit/Device Description GTC-L Default GTC-G Default

90M Node NameNode AddressEthernet HW AddressType

LNFS0111.31XX-XX-XX-XX-XX-XX*

NONE

GTFS0111.36XX-XX-XX-XX-XX-XX*

NONE

90M Node NameNode AddressEthernet HW AddressType

HPFS0211.32XX-XX-XX-XX-XX-XX*

NONE

GTFS0211.37XX-XX-XX-XX-XX-XX*

NONE

* XX-XX-XX-XX-XX-XX is obtained from sticker on the rear of the DECserver.

Table 13: Server Installation Parameters



4.6.1.2 ProcedureActivate Host Environment software as follows:

1. From the SMU Main menu select ACTIVATE RELEASE. This will start themirror process and open the temporary log file.


If you have NOT recently performed a full image backup of the Central System Host,it is recommended that one be performed at this time. Enter Y if you are satisfiedand proceed with the next step. Otherwise, enter N to cancel the ACTIVATEand exit the SMU.

1. At this point you will be prompted as to which Host environment release youwish to activate. Refer to Figure 10 for a typical ACTIVATE RELEASEsubmenu. Enter the appropriate selection number.

2. The SMU will now display the selected release type and version number andrequest confirmation:

You have chosen HOSENV_010200 to activate


If this is the release to be activated, enter Y and proceed with the following step.Otherwise, enter N to cancel the ACTIVATE and exit the SMU.

1. The initial default configuration data appears in Table 10 through Table 13. Aseach group is displayed, the following prompt will appear requesting verificationof the parameters:

Are the above values correct (Yes,No,Quit)? =

This information should not be changed unless specifically directed by the SystemManager or Reuters Development. However, customization for a particular sitemay be required. If modification is required, enter N at the prompt. The SMUthen prompts the installer for new input for each parameter. If no change to aparameter is required, press RETURN to select the default (displayed) parameter.When the SMU has cycled through all the parameters, the complete updated setof installation parameters will be displayed followed by a verification prompt.Enter the appropriate response.

Following the display of the Installation Parameters, a series of Success andInformational messages will be displayed. If an error message appears, proceedto step 1. Otherwise, proceed to step 1.

1. All nodes defined in the parameters (Table 10 through Table 13) must beidentified as cluster members. If a node is not a cluster member, an errormessage will appear identifying the node name. Perform the following steps:

2. Reboot the node if it is not currently running.

3. Verify that the node was added to the cluster. If it was not, enter the followingcommand at the DCL prompt:

$ @RDTS_SYSMGR:CREATE_HOST_ROOTS



Upon completion, activate the SMU and proceed from step 1.

1. A series of messages will be displayed followed by the completion messagebelow:

Activate of HOSENV_010200 complete at 13-MAR-199202:58:51.46

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

END OF ACTIVATE UTILITY - COMPLETE

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

Press RETURN to continue....

1. Press RETURN to continue. A message similar to the following will now bedisplayed:

LOG FILE CLOSED AT 13-MAR-1992 02:58:56.85LOG located in RDTS_STATE:ACTIVATE_HOSENV_version.LOGMIRROR process is terminating ...

The Log filename is: RDTS_STATE:ACTIVATE_HOSENV_version.LOG


This concludes the Host Environment Activation procedure. The SMU will indicate that the system isrebooting.

4.6.2 Activate ApplicationThis section covers activation of a previously loaded Central System Host Application software release. Ifthis is an initial activation or if a new RDTS database will be created, the Security Officer/Site Administratormust be available and have the password list for the following Sybase Accounts:

• ADMIN_SOFTWARE

• ARCHIVE_SYSTEM

• DATA_MAINTENANCE

• ENV

• HOST

• TDESK_PROD

• VIEW_ONLY

When the activation procedure prompts the installer to enter the new Sybase passwords for these accounts,the Security Officer/Site Administrator MUST enter the passwords. This will ensure that password securityis maintained during the activation.

Activate Host Application software as follows:

1. From the SMU Main menu select ACTIVATE RELEASE. This will start themirror process and open the temporary log file.

2. The first prompt to appear will be the following "backup" prompt:



Are you satisfied with the Backup of your system (Y/N) ? [N] :

If you have NOT performed a full image backup of the Central System Host, it isrecommended that one be performed at this time. Enter Y if you are satisfied andproceed with the next Step. Otherwise, enter N to cancel the ACTIVATE andexit the SMU.

1. The ACTIVATE RELEASE submenu will now be displayed (Figure 11). Enterthe appropriate release selection number.

2. The SMU will now display the selected release and version number and requestconfirmation:

You have chosen HOST_010200 to activate


1. If this is the release to be activated, enter Y and proceed with the following Step.Otherwise, enter N to cancel the ACTIVATE and exit the SMU.

2. If the Sybase Database already exists, proceed to step 1, otherwise, continuebelow.

3. If there is no Sybase Database on the Host the SMU will automatically create it.This process may take more than 3 hours to complete. After creation of thedatabase, the SMU will prompt the installer to enter new passwords for thefollowing Sybase accounts:

- sa

- rdts_sa

- rdts

- admin_software

- probe

1. The Site Administrator should now enter the appropriate passwords as prompted.

2. A series of messages will be displayed followed by the completion messagebelow:

Activate of HOST_010200 complete at 13-MAR-199202:58:51.46

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

END OF ACTIVATE UTILITY - COMPLETE

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


1. Press RETURN to continue. A message similar to the following will now bedisplayed:

LOG FILE CLOSED AT 13-MAR-1992 02:58:56.85LOG located in RDTS_STATE:ACTIVATE_HOST_010200.LOGMIRROR process is terminating ...

The Log file is: RDTS_STATE: ACTIVATE_HOST_version.LOG




It is recommended that a full weekly backup of the Central System Disks now be performed by the CentralSystem Operator.

4.7 RollbackThis function is provided to reduce the risk associated with a new software release. If a release proves to beunsatisfactory, upon receipt of proper authorization, the system can be returned to a prior operational state.This can be done effectively and in a timely manner by using the ROLLBACK function.

Note: Host releases may not be rolled back while the Host Application or dataservers are running. FrontEnd releases may be activated regardless of Host status. Dataservers must be shut down.

It is important to note that after ten days have elapsed since activation, rollback is no longer possible withoutproper authorization. Follow normal problem escalation procedures to perform a rollback beyond this timelimit. Additionally, a rollback will consist of any software release(s) contained in an activation group. Onlyentire activation groups may be rolled-back. Refer to Activate Host on page 47 for a description of anactivation group.

Once ROLLBACK RELEASE has been selected from the SMU Main menu, the Rollback Release submenu(Figure 12) will be displayed. You will be prompted as to whether or not to rollback ALL releases. This isthe only choice available, so respond accordingly. As the ROLLBACK function is basically the same (withthe one exception being the Host Environment) on all systems, only one sample is shown below.

1. From the SMU Main menu select ROLLBACK RELEASE. This will start themirror process and open the temporary log file.


If you have NOT performed a full image backup of the target System, it isrecommended that one be performed at this time. Enter Y if you are satisfied andproceed with the next step. Otherwise, enter N to cancel the ROLLBACK andexit the SMU.

1. A series of messages will be displayed as configuration and control files arecopied. When done a list of all releases, similar to the following, in the latestactivation group will be displayed.

Subsystem HOST_050400 will rollback to NONESubsystem HOSENV_XXXXXX will rollback toHOSENV_010600.

1. You will then be prompted for confirmation as to whether or not to rollback allof the above releases. This is a choice of ALL or NONE.

Do you wish to rollback ALL of the above releases (Y/N)?

A response of N will terminate the SMU with a user cancel status. Otherwise, therollback will be performed and a series of messages will be displayed as theoperation continues.

1. Once complete, a message similar to the following will be displayed:



----------------------------------------------------END of ROLLBACK UTILITY - COMPLETE----------------------------------------------------

LOG FILE CLOSED AT 30-MAR-1992 17:07:27.32

As with other log files, the rollback logs are located in RDTS_STATE: directory.Any rollback log filename will have the word ROLLBACK plus the date andtime the rollback was performed. This will be similar to the format shownbelow:

ROLLBACK_30_MAR_1992_17_05_11.LOG;1


4.8 DeleteThis facilitates the complete removal of software deemed obsolete from the system. In practice this wouldinclude software more than two releases prior to the software currently operating. Therefore, a maximum ofthree release versions of an application may be on the system at any given time.

The only release-specific information required to delete any software is the release type and version number.Also, you will be prompted as to whether or not you are satisfied with the backup of your system. Since allDELETEs function identically, with the only exception being the release type and version, only one sample(Host Application version 010200) is presented below. To delete other release types/versions, simplysubstitute accordingly as specified in the applicable release notes.

1. From the SMU Main menu select DELETE RELEASE. This will start themirror process and open the temporary log file.


If you have NOT performed a full image backup of the Central System Host, it isrecommended that one be performed at this time. Enter Y if you are satisfied andproceed with the next step. Otherwise, enter N to cancel the LOAD and exit theSMU.

1. The DELETE RELEASE submenu (Figure 13) will now be displayed. Selectthe appropriate item from the submenu, in this case HOST.

2. The HOST OPTIONS submenu (Figure 10) will now be displayed. Select theappropriate item from the submenu, in this case APPLICATION.

3. The following "version number" prompt will now be displayed:ENTER version of HOST to delete = 010200

Enter the appropriate six-digit version number as specified in the release notes andproceed with the next Step. Otherwise, enter EXIT to cancel the DELETE.

1. A series of messages will be displayed on the screen as the SMU performs itstask. At the conclusion of these messages will be a display similar to thefollowing:

Delete of HOST_010200 complete at 13-MAR-1992 02:58:51.46

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



END OF DELETE UTILITY - COMPLETE

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


1. At this point press RETURN to continue. The following will now be displayed:

LOG FILE CLOSED AT 13-MAR-1992 02:58:56.85LOG located inRDTS_STATE:DELETE_HOST_APPLICATION_010200.LOGMIRROR process is terminating ...

The Log file is: RDTS_STATE:DELETE_HOST_APPLICATION_version.LOG



4.9 Show Current VersionsThis function is used whenever necessary to display all software and third-party software versions currentlyrunning on a target system. The target system is the system from which the SMU is invoked. Selecting thisoption will present a list of this information similar to the one below:Current versions are:

HOSENV Version 020000HOST Version 050400XGPS Version 010000 Vendor Version 2.0 (example versionnumber)DROPSAFE Version 010000 Vendor Version 1.0 (example versionnumber)


Pressing RETURN at this point will return to the Main menu. No log file is created during this operation.

4.10 Install Third-Party SoftwareFollowing is a list of third party software to be installed with the SMU.

• XGPS

XGPS is the time synchronization package.

• Dropsafe

Dropsafe is the third-party software used for the encryption of sensitive data.

Following are general procedures for using this function. For specific instructions, refer to the release notesfor complete instructions.

1. From the SMU Main menu select INSTALL THIRD-PARTY. This willimmediately start the process.

2. The following "backup" prompt will appear:Are you satisfied with the Backup of your system (Y/N) ?

[N] :



If you have NOT performed a full image backup of the Central System Host, it isrecommended that one be performed at this time. Enter Y if you are satisfied andproceed with the next step. Otherwise, enter N to cancel the installation and exitthe SMU.

1. To begin the installation process, press RETURN at the following prompt:

Hit any Key to continue.

1. The following prompt will be displayed:Enter PRODUCT name =

Enter the product name.

1. The following prompt will display.Enter product version number as per release note

Enter version number (999999) or EXIT .

Enter the appropriate version number at the following prompt:

1. After the version number has been entered, the following prompt will bedisplayed:

Enter Device Name containing the saveset or EXIT[SYS$SYSDEVICE:[000000]:]:

A series of Informational messages will be displayed regarding the unwinding of theBackup saveset and the placing of files in appropriate directories.

1. A series of Informational messages will be displayed regarding the installation ofthe third-party software.

4.11 Show/Modify ConfigurationThis allows the user to both view and modify all Host and Operations configuration parameters at any giventime during an SMU session.

1. Select SHOW/MODIFY CONFIGURATION from the SMU Main menu.


If you have NOT recently performed a full image backup of the system, it isrecommended that one be performed at this time. Enter Y if you are satisfied andproceed with the next Step. Otherwise, enter N to cancel the procedure and exitthe SMU.

1. The CONFIGURATION submenu will now be displayed (Figure 15). Select theappropriate menu option for the desired configuration information.

2. The initial default configuration data appears in Table 10 through Table 13.Verify the parameters each time the following prompt is displayed:

Are the above values correct (Yes,No,Quit)? =

This information should not be changed unless specifically directed by the SystemManager or Reuters Development. However, customization for a particular site



may be required. If modification is required, enter N at the prompt. The SMUthen prompts the installer for new input for each parameter. If no change to aparameter is required, press RETURN to select the default (displayed)parameter. When the SMU has cycled through all the parameters, the completeupdated set of installation parameters will be displayed followed by averification prompt. Enter the appropriate response. Entering Y will processany changed parameters, while Q will ignore all changes. Both will redisplay theCONFIGURATION submenu.

1. At this point the user can either choose another menu option, or select X toreturn to the Main menu.