v7000 software installation and activation guide -...

V7000

Software Installation and

Activation Guide DPS

7000/XTA

NO

VASC

ALE

7000

Hardware: DPS7000/XTA

REFERENCE77 A2 88US 03

DPS7000/XTANOVASCALE 7000

V7000Software Installation and Activation

Guide

Hardware: DPS7000/XTA

March 2006

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

REFERENCE77 A2 88US 03

The following copyright notice protects this book under Copyright laws which prohibit such actions as, but notlimited to, copying, distributing, modifying, and making derivative works.

Copyright Bull SAS 2006

Printed in France

Suggestions and criticisms concerning the form, content, and presentation of thisbook are invited. A form is provided at the end of this book for this purpose.

To order additional copies of this book or other Bull Technical Publications, youare invited to use the Ordering Form also provided at the end of this book.

Trademarks and Acknowledgements

We acknowledge the right of proprietors of trademarks mentioned in this book.

Intel® and Itanium® are registered trademarks of Intel Corporation.

Windows® and Microsoft® software are registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark in the United States of America and other countries licensed exclusively throughthe Open Group.

Linux® is a registered trademark of Linus Torvalds.

The information in this document is subject to change without notice. Bull will not be liable for errors containedherein, or for incidental or consequential damages in connection with the use of this material.

77 A2 88US iii

Preface

This guide describes the installation and activation of V7000 software.

It contains all the information required to install and activate V7000 software to operate a GCOS7 system on an Intel® platform.

The other DPS 7000/XTA machine guides are listed in the present guide. Chapter 1 Introduction gives an overview of the DPS 7000/XTA

machine and of the installation of V7000 software on an Intel Architecture (IA) platform under Microsoft® Windows™.

Chapter 2 Installing a version describes how to install a version of the V7000 software.

Chapter 3 Activating an installed version describes how to select a version of the V7000 software before starting a GCOS7 system.

Chapter 4 Installing the remote administration tools describes how to install the remote administration tools.

Chapter 5 Uninstalling the software describes how to uninstall the V7000 software and the remote administration tools.

Chapter 6 Troubleshooting explains how to solve the main problems encountered during the installation of version of the V7000 software.

APPENDIX A Starting a minimum GCOS7 system

GLOSSARY

INDEX

Scope and Objectives

Structure

V7000 Software Installation and Activation Guide

iv 77 A2 88US

V7000 Operator’s Guide.......................................................................... 47 A2 74US V7000 Software Installation and Activation Guide ................................. 77 A2 88US V7000 Evolution Guide ........................................................................... 47 A2 76US GCOS7-V7-V9 System Installation Configuration ................................. 47 A2 23US and Updating Guide GCOS7-V7-V9 Operator's Guide ............................................................ 47 A2 53US V7000 Configuration and Maintenance Guide ....................................... 77 A2 77US Interop7 User's Guide.............................................................................. 47 A2 91US

Bibliography

77 A2 88US v

Table of Contents

1. Introduction 1.1 The DPS 7000/XTA and Novascale 7000 machines...................................................... 1-2

1.1.1 Architecture........................................................................................................ 1-2 1.1.2 GCOS7 – V7000 relationship on a DPS 7000/XTA or Novascale 7000

machine ............................................................................................................. 1-4 1.1.3 Starting the DPS 7000/XTA or Novascale 7000 machines ............................... 1-5

1.2 Installing a DPS 7000/XTA or Novascale 7000 platforms .............................................. 1-6 1.2.1 V7000 installation .............................................................................................. 1-6 1.2.2 V7000 software versions ................................................................................... 1-7 1.2.3 V7000 installation CD-Rom ............................................................................... 1-7 1.2.4 Installation requirements ................................................................................... 1-8

2. Installing a version 2.1 How to install a version of V7000 ................................................................................... 2-2 2.2 First installation ............................................................................................................... 2-3

2.2.1 Setup ................................................................................................................. 2-3 2.2.1.1 Preliminary checks ............................................................................ 2-3 2.2.1.2 Dialogue with the Administrator ........................................................ 2-4 2.2.1.3 Copying files...................................................................................... 2-7 2.2.1.4 Setting security levels ....................................................................... 2-7 2.2.1.5 Updating the Windows™ registry...................................................... 2-8 2.2.1.6 Start Menu......................................................................................... 2-8 2.2.1.7 Finishing Setup.................................................................................. 2-9

2.2.2 Anomalies encountered during Setup ............................................................. 2-10 2.3 Installing a new version of V7000 ................................................................................. 2-11

2.3.1 Installing a new version ................................................................................... 2-11 2.3.1.1 Setup ............................................................................................... 2-11 2.3.1.2 Anomalies encountered during Setup............................................. 2-11

2.3.2 Re-installing an existing version ...................................................................... 2-11 2.4 Installing a correction .................................................................................................... 2-12


vi 77 A2 88US

2.5 Errors that may interrupt Setup..................................................................................... 2-13 2.5.1 V7000 Setup error messages.......................................................................... 2-13 2.5.2 InstallShield error messages ........................................................................... 2-14 2.5.3 Windows™ error messages ............................................................................ 2-14

3. Activating an installed version 3.1 How to activate a version................................................................................................ 3-2 3.2 What does the Version Manager do? ............................................................................. 3-3 3.3 How to use the Version Manager ................................................................................... 3-4

3.3.1 Selecting a version ............................................................................................ 3-4 3.3.2 Activation process.............................................................................................. 3-7 3.3.3 Errors encountered during the version activation process .............................. 3-11

4. Installing the remote administration tools 4.1 How to install remote administration tools ...................................................................... 4-1 4.2 Setup............................................................................................................................... 4-2 4.3 Launching the remote administration tools ..................................................................... 4-5 4.4 How to install remote administration tools correction ..................................................... 4-5 4.5 Anomalies encountered during Setup............................................................................. 4-6 4.6 Old Firewall configuration ............................................................................................... 4-7

4.6.1 Adding RPC Port ............................................................................................... 4-9 4.6.2 Adding ClientConsole.exe and mmc.exe Programs........................................ 4-10

4.7 New Firewall configuration............................................................................................ 4-11

5. Uninstalling the software 5.1 What can be uninstalled?................................................................................................ 5-2 5.2 How to uninstall the software .......................................................................................... 5-2 5.3 Uninstall of V7000 server................................................................................................ 5-3 5.4 Uninstall of V7000 Remote Administration Tools ........................................................... 5-6 Anomalies encountered during Uninstall .................................................................................. 5-7 5.5 Finishing Uninstall ........................................................................................................... 5-7

6. Troubleshooting 6.1 Problems encountered during Setup / Uninstall ............................................................. 6-1 6.2 Problems encountered when activating a version .......................................................... 6-3

77 A2 88US vii

A. Starting a minimum GCOS7 System

Glossary

Index


viii 77 A2 88US

Table of Graphics

Figure 1-1 DPS 7000/XTA Machine Block Diagram ........................................................... 1-3 Figure 1-2 Non-authorized User Window............................................................................ 1-9 Figure 2-1 InstallShield Wizard Initialization Window ......................................................... 2-2 Figure 2-2 Preliminary Check Wait Message...................................................................... 2-3 Figure 2-3 Home Page........................................................................................................ 2-4 Figure 2-4 Setup Type Window .......................................................................................... 2-5 Figure 2-5 Setup Path Window ........................................................................................... 2-6 Figure 2-6 Setup Status Window ........................................................................................ 2-7 Figure 2-7 Wait Message: Setting V7000 Security Levels.................................................. 2-7 Figure 2-8 Wait Message: Registry Initialization................................................................. 2-8 Figure 2-9 Wait Message: Creating the Start Menu ........................................................... 2-8 Figure 2-10 Finish Setup Window......................................................................................... 2-9 Figure 2-11 Setup Abort Window (Serious Error) ............................................................... 2-13 Figure 3-1 Version Manager User Warning Message ........................................................ 3-2 Figure 3-2 Version Manager Access Forbidden Message.................................................. 3-2 Figure 3-3 Version Manager Home Page ........................................................................... 3-4 Figure 3-4 Selecting a Version............................................................................................ 3-6 Figure 3-5 Active Version Re-activation Dialogue Box ....................................................... 3-7 Figure 3-6 DianeNet Driver Re-install Warning Message................................................... 3-7 Figure 3-7 Complete Version Activation Process (V0.12) .................................................. 3-8 Figure 3-8 Dynamic Correction Activation Process ............................................................ 3-9 Figure 3-9 V7000 System Control Console Startup.......................................................... 3-10 Figure 3-10 V7000 Start Menu............................................................................................ 3-10 Figure 3-11 Error Message: GCOS7 Running .................................................................... 3-11 Figure 4-1 Remote Administration Tools Setup Type Selection ......................................... 4-2 Figure 4-2 Remote Administration Tools Setup Path Selection.......................................... 4-3 Figure 4-3 Message asking the Security Policies modifications ......................................... 4-4 Figure 4-4 Remote Administration Tools Start Menu.......................................................... 4-5 Figure 4-5 Firewall Main Window........................................................................................ 4-7 Figure 4-6 Firewall default defined permissions. ................................................................ 4-8 Figure 4-7 Adding RPC Port. .............................................................................................. 4-9 Figure 4-8 Adding ClientConsole.exe Program. ............................................................... 4-10 Figure 4-9 Firewall configuration for V7000 usage. .......................................................... 4-11 Figure 5-1 V7000 Uninstall Warning Message ................................................................... 5-3 Figure 5-2 Remote Administration Tools Uninstall Warning Message ............................... 5-3 Figure 5-3 Uninstall Confirm Box ........................................................................................ 5-3

Figures

77 A2 88US ix

Figure 5-4 Active Version Uninstall Confirm Box................................................................ 5-4 Figure 5-5 V7000 Uninstall Status Window: Uninstalling Files ........................................... 5-5 Figure 5-6 V7000 Environment Cleanup Confirm Box........................................................ 5-5 Figure 5-7 Uninstall Process Finish Window ...................................................................... 5-6


x 77 A2 88US

77 A2 88US 1-1

1. Introduction

The DPS 7000/XTA (IA32 Platforms) and Novascale 7000 (IA64 Platforms) machines are a new generation of DPS 7000 designed to run on a BULL Intel® Architecture (IA) platform, administered by the Windows 2000™ (et seq.) operating system, referred to in the present document by the generic term Windows™.

The DPS 7000/XTA and Novascale 7000 machines comprise a hardware part (IA Server or Bull Novascale) and a software part called V7000.

The V7000 software, which comprises a functional engine and graphic administration tools, is used to activate the GCOS7 operating system under Windows™. It is installed as a standard Windows™ application from a CD-Rom created by InstallShield.

The install program (Setup) installs either the complete V7000 software (functional engine and administration tools, excluding the GCOS7 system disk) on the Server or just the administration tools on a remote Server or Station.

An installation CD-Rom is distributed for each new complete V7000 version or for each new correction version.

From V4, the CD-Rom delivery contains both IA32 and IA64 V7000 Versions.

IMPORTANT: GCOS7 system installation, configuration and updating is not described in the present manual (Cf. GCOS7-V7-V9 System Installation, Configuration and Updating Guide - 47A2 23US).

Interop7 is to be installed AFTER V7000 has been installed (Cf. Interop7 User's Guide - 47 A2 91US).

The figures presented in the present document are only examples and may vary according to the V7000 versions used (e.g. versions V0.10, V0.10.1, V0.11, V0.12, V0.13, V0.13.1).

13

3


1-2 77 A2 88US

1.1 The DPS 7000/XTA and Novascale 7000 machines

IMPORTANT: In the present document, V7000 designates the V7000 software and the DPS 7000/XTA machine or Novascale 7000 designates the Server and the software.

The DPS 7000/XTA or Novascale 7000 machines offer all the characteristics of standard DPS 7000 mainframe computers (reliability, robustness, security) for GCOS7.

The visibility and availability of GCOS7 client applications remain identical. The only adaptation required is the prior migration of GCOS7 data for accessibility under Windows™ (Cf. V7000 Evolution Guide - 47 A2 76US).

GCOS7 environment management remains identical.

1.1.1 Architecture

The DPS 7000/XTA machine (Figure 1-1) comprises the following components:

• An Intel® multi-processor platform,

• The Windows™ operating system, Large System version, centered on reliability, robustness and security,

• The V7000 software (functional engine and administration tools),

• A minimum GCOS7 TS9866 system identical to that running on standard DPS 7000 machines,

• GCOS7 applications and data (Batch, TDS, IOF),

• Native or reconnected (inherited from a standard DPS 7000 and repopulated with migrated data) Server devices,

• Interop7 gateways between Windows™ and GCOS7.

• An external communications system.

13

3

Introduction

77 A2 88US 1-3

GCOS7 applications

GCOS7 system

BULL Intel® Architecture platform: DPS 7000/XTA

WINDOWSV7000: GCOS7

VIRTUAL MACHINE

INTEROP7GATEWAYS

Iso DSA network TCP IP network

V7000 Operators&

Bull Support

LocalAdministration

Tools

V7000 Operators&

Bull Support

RemoteAdministration

Tools

Figure 1-1 DPS 7000/XTA Machine Block Diagram

NOTE: The architecture for Novascale 7000 is the same.

V7000 is a standard Windows™ application. It manages its own resources and minimizes interaction with the operating system. Input / Output management and administration are based on Windows™.

V7000 comprises a functional engine (GCOS7 Virtual Machine, Figure 1-1), specific administration tools (System Administration Manager or SAM) and manages external ISO/DSA communications.

V7000 is a safe application. The software can only be used to administer a GCOS7 operating system by privileged users, via either local or remote administration tools (Figure 1-1).

Remote administration tools can be installed on a remote Windows™ Server or Station from the V7000 installation CD-Rom.

V7000 supports a standard GCOS7 system, from TS9866. The V7000 environment is identical to that of a standard DPS 7000.


1-4 77 A2 88US

GCOS7 technical status updating and management are also identical, via the GIUF tool.

Certain standard DPS 7000 disk devices can be reconnected to the V7000 machine and repopulated with previously saved GCOS7 data and applications (Cf. V7000 Evolution Guide - 77 A2 76US).

Apart from back-up and restore processes, data does not need to be modified or adapted to the new environment.

GCOS7 volumes are based on Server NTFS files (NT File System) and are only accessed by GCOS7 applications (exclusive secure access).

External communications take place via one or several telecommunications cards, managed by a specific driver.

IMPORTANT: Windows™ manages DPS 7000/XTA or Novascale 7000 hardware and devices. The V7000 install program only manages specific V7000 drivers. The V7000 install program does not manage independent Windows™ and hardware drivers.

The addition of new devices (disks, cartridge drives, telecommunication adapters, etc…) and the installation of associated drivers fall under platform management.

1.1.2 GCOS7 – V7000 relationship on a DPS 7000/XTA or Novascale 7000 machine

GCOS7 is a BULL proprietary operating system, characterized by a technical status. The standard DPS 7000 GCOS7 technical status is used for DPS 7000/XTA and Novascale 7000 machines.

GCOS7 technical status evolutions are independent of the V7000 version used.

The GCOS7 operating system is configured (hardware) and administered by V7000.

13

3

Introduction

77 A2 88US 1-5

1.1.3 Starting the DPS 7000/XTA or Novascale 7000 machines

GCOS7 operation on an installed Server (excluding system disk and data disk migration) is carried out in seven stages.

The first four stages are described in the present guide. (Cf. Annex A).

1. Installation of a version of V7000. A version of V7000 can be installed even if one or several other versions are already installed on the Server (Cf. Chapter 2). Each version is fully independent, with a complete installation of all the products, no common files.

2. Creation of a privileged user belonging to the V7000BullServices and Administrators groups.

3. Connection of the privileged user, who proceeds with stage 4.

4. Selection and activation of a version of V7000 (one or several versions may be installed) by the privileged user with the Version Manager tool. (Cf. Chapter 3).

5. Preparation of the GCOS7 hardware configuration with the Configuration Editor tool before V7000 is started for the first time. This configuration phase is independent of the GCOS7 configuration phase.

6. Creation of a GCOS7 V7000 operator belonging to the V7000Operators group.

7. Starting GCOS7 with its own specific parameters. The GCOS7 V7000 operator starts GCOS7 with the System Control tool.

Stage 5 is described in documents:

V7000 Operator’s Guide (47 A2 74US), V7000 Configuration and Maintenance Guide (77 A2 77US).

Stages 6 and 7 are described in document:

GCOS7-V7-V9 Operator's Guide (47 A2 53US).

IMPORTANT: V7000 is NEVER started at the end of the install process. The selected version is started with the Version Manager tool.

13

3


1-6 77 A2 88US

1.2 Installing a DPS 7000/XTA or Novascale 7000 platforms

A DPS 7000/XTA or Novascale 7000 platform is installed in two stages:

• hardware configuration of the Server,

• installation of V7000.

Server installation and migration of data to the new operating context are described in documents:

V7000 Operator’s Guide (47 A2 74US), V7000 Evolution Guide (77 A2 76US).

The installation of V7000 software is described in the present document.

The DPS 7000/XTA machine is delivered pre-installed and pre-configured by BULL in compliance with the customer’s requirements in terms of Server capacity (power, disks, telecommunication adapters, etc…) and the commercial model chosen.

The delivered GCOS7 configuration is the customer’s required configuration or a standard minimum configuration delivered ready for use.

The pre-installation carried out by BULL allows rapid machine configuration and operation.

IMPORTANT: 1. The use of the install program (Setup) is mandatory for the installation of

V7000. No manual operations are to intervene during Setup.

2. Setup is not locked by a Setup key. Access control checks take place when V7000 is launched. The installed version cannot manage GCOS7 operation without a valid key.

3. Interop7 is not installed with V7000. Interop7 is installed by another Setup (Cf. Interop7 User's Guide (47 A2 91US). It is mandatory to install V7000 before Interop7.

4. V7000 can start without Interop7 being installed or started.

1.2.1 V7000 installation

V7000 is installed via the install program (Setup) on the V7000 installation CD-Rom.

13

3

Introduction

77 A2 88US 1-7

1.2.2 V7000 software versions

Each version of V7000 is given an identifier (Version Id): VX.Y[.Z], according to the BULL distribution rate. New versions of the software correspond to functional evolutions or to the supply of corrections.

VX.Y corresponds to a complete, independent version of V7000.

VX.Y.Z corresponds to a correction for the VX.Y version of V7000, which includes all the corrections issued since the distribution of the preceding version. Therefore, a VX.Y.Z correction includes all the corrections issued in the VX.Y.Z-1, VX.Y.Z-2, … and VX.Y.1 versions.

NOTE: On DPS 7000/XTA or Novascale 7000 machines, the GCOS 7 banner FW field indicates the V7000 version format (Dxyyzz), where:

1. Main release number

2. Version technical status

3. Correction index (blank if no technical status correction).

1.2.3 V7000 installation CD-Rom

A V7000 VX.Y installation CD-Rom contains V7000 software, i.e. a set of files (executable, data, configuration, … files),

V7000 documentation is delivered on the V7000 documentation CD-Rom.

From V4 versions, softwares for XTA and Novascale 7000 Platforms are delivered on the same CD-Rom. Control of Intel Architecture is done by setup program.

Thus IA32 version cannot be installed on Novascale 7000 and IA64 Version cannot be installed on XTA Platforms.

IMPORTANT: Interop7 documentation (Cf. Interop7 User's Guide - 47 A2 91US) is delivered on the Interop7 installation CD-Rom.

13

3


1-8 77 A2 88US

1.2.4 Installation requirements

The V7000 Setup requires a dedicated Server. Only Server administrators can perform setup.

NOTE: When the DPS 7000/XTA or Novascale 7000 Platform belongs to a domain, install of V7000 Version must be performed by a local administrator of the machine and known in the domain.

NOTE: V7000 functional engine can only be installed on English Windows Server. Remote Administration Tools can be installed on any language of Windows Station.

Setup takes charge of certain commands required for software installation. The following conditions are to be complied with:

• The host machine is to be a Windows™ Server for the installation of a complete version of V7000 or a Station / Server for the installation of the remote administration tools.

• At least 15 Mb free disk space is to be available on one of the valid Server volumes for the installation of a complete version of V7000 and at least 3 Mb is to be available for the installation of the remote administration tools.

• The user installing V7000 must belong to the machine Administrators group. If this is not the case, the following window is displayed (Figure 1-2).

Introduction

77 A2 88US 1-9

NEVER checkthis box otherwisethe system maycrash.

Figure 1-2 Non-authorized User Window

The user must stop the install process (Cancel) and reconnect under the name of a user belonging to the Administrators group.

IMPORTANT : 4. V7000 can be installed by remote control via Terminal Service, provided

that the CD-Rom is installed on the target machine.

5. To install a new version of V7000, it is not necessary to stop a version of V7000 managing a GCOS7 operating system, nor is it necessary to shut down Interop7 if installed and active.

13

3


1-10 77 A2 88US

❑

77 A2 88US 2-1

2. Installing a version

IMPORTANT: The install process (Setup) described in the present chapter is for guidance only. V7000 is delivered pre-installed and pre-configured by BULL, in compliance with the customer’s requirements.

The figures presented in this document are only examples and may vary according to the versions used (e.g. versions V0.10, V0.10.1, V0.11, V0.12, V0.13, V0.13.1).

A version of V7000 may be installed even if one or several other versions have already been installed on the Server. Each version is fully independent, with a complete installation of all the products. There are no common files and it is not necessary to successively install all the versions distributed by BULL.

Each correction includes all the corrections for the corresponding complete version.

The V7000 Setup copies files to directories and creates a registry tree (complete version), dependent on the version identifier.

Partitioning allows several, fully independent versions to be installed and provides operational versatility. When a given version fails, another version can be used.

When V7000 is installed for the first time, the V7000 environment is secured and two Windows™ user groups are created (V7000BullServices and V7000Operators).

V7000 installation is quick (a few minutes only).

When a version has been installed successfully, a description of the said version is displayed in the Add/Remove Programs tab in the Windows™ Control Panel.

The next stage consists in starting the installed version (Cf. Chapter 3).

13

3


2-2 77 A2 88US

2.1 How to install a version of V7000

The install process is carried out by a Server Administrator from the V7000 installation CD-Rom. The install process is Setup-driven. Setup requests information via dialogue boxes.

Setup is launched from the Add/Remove Programs tab in the Server Control Panel. The Setup.Exe file is found on the CD-Rom by the Windows™ Search Wizard.

The InstallShield Wizard initialization window is displayed at the beginning of Setup (Figure 2-1).

Figure 2-1 InstallShield Wizard Initialization Window

The Setup window is then displayed.

Each dialogue box (except the Home Page) provides three options:

• Next: continues Setup,

• Back: returns to the previous dialogue box,

• Cancel: stops Setup.

IMPORTANT: The install process is traced in the <rootdir>\Trace\V7000 Installation and Activation.log file, shared with the Version Manager (Cf. Chapter 3).

Rootdir means root directory of V7000 environment location, fixed by Manufacturing process.

13

3

Installing a version

77 A2 88US 2-3

2.2 First installation

The first V7000 install process initializes the V7000 management structures, creates the privileged user groups (V7000Operators and V7000BullServices) and secures the components.

2.2.1 Setup

A preliminary check and dialogue phase takes place before files are copied. Setup then sets security levels, records the components, creates the Start Menu and ends with the last registry update.

2.2.1.1 Preliminary checks

Preliminary checks are made with regard to available disk space, user rights and host machine features. If the required conditions are not satisfied, Setup is not launched. During the preliminary check phase, a Wait Message is displayed (Figure 2-2).

Figure 2-2 Preliminary Check Wait Message

When the required conditions are satisfied, the Wait Message disappears and the Setup Home Page opens.


2-4 77 A2 88US

2.2.1.2 Dialogue with the Administrator

Dialogue with the Administrator begins with the Home Page shown in Figure 2-3.

Figure 2-3 Home Page


• Cancel: stops Setup. The Setup type is then requested (Figure 2-4):

• Full V7000 Server (default value):

Installation of the complete machine:

− functional engine,

− telecommunications,

− local administration tools.

• Remote V7000 Administration Tools:

Installation of the remote administration tools, only. (Cf. Chapter 4).


77 A2 88US 2-5

Figure 2-4 Setup Type Window

Once the Setup type has been selected:


• Cancel: stops Setup,

• Back: returns to the Home Page.

The last dialogue box requests the Setup path (Figure 2-5), which establishes the future file tree root directory.

The default path displayed is compliant with the Windows™ standard. The directory proposed is created by concatenating the system disk "Program Files" root, the supplier’s name and the application name. In the example given in Figure 2-5:

- C:\Program Files\ System disk Program Files root

- Bull\ Supplier’s name

- V7000 Application name


2-6 77 A2 88US

When V7000 is installed for the first time, the Setup path can be changed via the Browse button. Once confirmed, this Setup path is used for all future software installations and corresponds to the actual <rootdir> Setup path. If the path selected does not end with V7000, V7000 will be added.

IMPORTANT: The <rootdir> directory may not exist. In this case, it will be created.

Figure 2-5 Setup Path Window


• Cancel: stops Setup,

• Back: returns to the Setup Type window.

NOTE: The default Destination Folder for Novascale 7000 Platforms is “C:\Program Files (x86)”.

13

3


77 A2 88US 2-7

2.2.1.3 Copying files

V7000 files are copied to directories identified by concatenating the version to the Setup folder selected by the Administrator. Each version has its own Windows™ system files, which are only installed if required.

The following window is displayed when files are being copied (Figure 2-6).

Figure 2-6 Setup Status Window

2.2.1.4 Setting security levels

Access rights are positioned in the V7000 file and registry trees. The following Wait Message is displayed during this phase (Figure 2-7).

Figure 2-7 Wait Message: Setting V7000 Security Levels


2-8 77 A2 88US

2.2.1.5 Updating the Windows™ registry

The Windows™ registry is used to write V7000 version management and operating environment data.

The part of the registry used by V7000 is structured per version. Therefore, each new install process does not alter the keys of a previous version.

Each version registry is only used by the version concerned.

During this phase the following Wait Message is displayed (Figure 2-8).

Figure 2-8 Wait Message: Registry Initialization

2.2.1.6 Start Menu

The V7000 Start Menu created when V7000 is installed for the first time is rudimentary.

The only shortcut is via the Version Activation tool:

Start Menu\V7000\Bull Services\Version Manager During this phase, the following Wait Message is displayed (Figure 2-9).

Figure 2-9 Wait Message: Creating the Start Menu

The Start Menu is constructed by the Version Manager (Cf. Chapter 3).


77 A2 88US 2-9

2.2.1.7 Finishing Setup

The following window (Figure 2-10) is displayed when Setup is finished. This window prompts to launch the Version Manager or to consult the corresponding Readme file.

Figure 2-10 Finish Setup Window

When V7000 is installed for the first time, the user is not prompted to launch the Version Manager (box not checked), as he does not yet belong to the V7000BullServices user group (Cf. Chapter 3).

When future versions are installed, the Version Manager box is checked (default option).

The Readme file outlines functional evolutions and describes the precautions to be taken before launching the version. The Readme file is in the <rootdir>\<VersionId>\Component directory.

At this stage, it is no longer possible to return to the previous window (Back) or to stop (Cancel) Setup. It is only possible to end Setup (Finish).

Once Setup is finished, the version installed can be selected with the Version Manager (Cf. Chapter 3).


2-10 77 A2 88US

2.2.2 Anomalies encountered during Setup

When Setup fails, the environment is returned to pre-Setup status. The version is not displayed under the Add/Remove Programs tab and is not detected by the Version Manager.

Once the problems encountered have been corrected, Setup must be restarted.

Cf. § 2.5 and / or Chapter 6 of the present document.


77 A2 88US 2-11

2.3 Installing a new version of V7000

InstallShield differentiates between the installation of a new version and the re-installation of an existing version.

2.3.1 Installing a new version

A new version is installed with the V7000 CD-Rom containing the Setup for the new version.

The new version uses its own directories and registry keys, dependent on its identifier, based on the Setup path confirmed when V7000 was installed for the first time.

2.3.1.1 Setup

The Setup for a new version of the software is comparable to the Setup used when installing the software for the first time. However, the dialogue box requesting the Setup path (Cf. Figure 2-5) is not displayed – the Setup path is definitively confirmed when the software is installed for the first time.

Once installed, the new version can be activated by the Version Manager Tool.

2.3.1.2 Anomalies encountered during Setup

Cf. § 2.5 and / or Chapter 6 of the present document.

2.3.2 Re-installing an existing version

Re-installing an existing version is a special process.

To re-install a given version, it must first be uninstalled, either via the Add/Remove Programs tab or by re-launching Setup (Cf. Chapter 5).


2-12 77 A2 88US

2.4 Installing a correction

A version of V7000 (VX.Y type VersionId) may require corrections, distributed in the form of corrections (VX.Y.Z VersionId).

A correction can only be installed on a compatible version of the software (identical VX.Y radical). The existence and integrity of the complete version are checked before the correction is installed.

The Setup for a correction is comparable to the Setup used when installing a complete version. The correction is located with the other versions already installed.

Once installed, the correction can be activated by the Version Manager tool.


77 A2 88US 2-13

2.5 Errors that may interrupt Setup

Setup may be interrupted by supported errors reported to the Administrator via information boxes (Cf. Chapter 6).

However, the InstallShield engine driving the Setup process and Windows™ may also encounter errors during Setup and generate special messages.

2.5.1 V7000 Setup error messages

Errors and messages are generated when Setup detects anomalies. These errors correspond to inconsistencies in V7000 management structures or insufficient rights and resources.

Certain errors do not affect Setup and are only Warnings.

Certain errors are serious and generate the following Abort Window:

Figure 2-11 Setup Abort Window (Serious Error)

Setup error messages are displayed in a Message Window.

The Setup trace file (V7000 Installation and Activation.log file) may allow the identification of errors.


2-14 77 A2 88US

2.5.2 InstallShield error messages

InstallShield directly reports two types of error messages:

• error messages concerning resource access conflicts,

• unexpected error messages, not supported by Setup.

These messages are to be reported to the BULL Support Center if Setup is still not successful once the appropriate corrective measures have been implemented.

2.5.3 Windows™ error messages

These messages reflect exceptional unfavorable conditions for Setup.

These messages are to be reported to the BULL Support Center if Setup is still not successful once the appropriate corrective measures have been implemented.

77 A2 88US 3-1

3. Activating an installed version

A single version of V7000 can be activated on a DPS 7000/XTA or Novascale 7000 machines at a given time by a user belonging to the Administrators and V7000BullServices groups, via the Version Manager too l.

The first version installed can be activated or the activated version can be changed with the Version Manager tool.

When a version of the V7000 software is activated, all its components run and work together correctly, under the supervision of the System Control and V7000 Administration services.

A version is launched when a GCOS7 operating system is actually being managed (Cf. V7000 Operator's Guide - 47 A2 74US).

IMPORTANT: The Version Manager tool used is ALWAYS that of the last complete version of V7000 installed.

The figures presented in this document are only examples and may vary according to the versions used (e.g. versions V0.10, V0.10.1, V0.11, V0.12, V0.13, V0.13.1).

13

3


3-2 77 A2 88US

3.1 How to activate a version

The Version Manager can be activated via the Bull Services\Version Manager shortcut in the V7000 Start Menu. The tool is dedicated to Bull Support and the following warning message is displayed:

Figure 3-1 Version Manager User Warning Message

The user must belong to the V7000BullServices and Administrators groups. If not the following message is displayed:

Figure 3-2 Version Manager Access Forbidden Message

The Version Manager decides whether or not to shut down GCOS7 and V7000 before proceeding to activate the selected version and informs the user.

When the complete version of the software is changed, the following actions are carried out:

• GCOS7 and V7000 are to be shut down by the Operator,

• the local and remote administration tools are to be shut down by their users,

• V7000 services and some Windows services are to be shut down by the tool.

Activating an installed version

77 A2 88US 3-3

IMPORTANT: Do not forget to close the Windows™ tools that may be using V7000 resources (Explorer, EventViewer, My Computer → Manage window due to V7000 Management snap-in, etc).

The Version Manager is capable of shutting down and starting Interop7, Opensave or Windows specific Services, if one or more of them are active, when a V7000 version is changed.

When a correction is activated, GCOS7 and V7000 are to be shut down if the functional engine or system management tools are affected. In this case, the user is informed by an error message.

However, when the correction only concerns Input / Output controllers, activation is dynamic and GCOS7 and V7000 do not need to be shut down. The correction is taken into account after performing the GCOS7 commands:

MDHW … OUT MDHW … IN.

3.2 What does the Version Manager do?

The Version Manager transfers files, manages Services (under Windows™), manages a telecommunications driver, installs graphic tools and updates registry data.

It re-generates the activated version Start Menu and launches V7000 Services. At the end of the process, it prompts the System Control Console (SYC) launch option if the user also belongs to the V7000Operators group.

13

3


3-4 77 A2 88US

3.3 How to use the Version Manager

The Version Manager is a simple graphic tool, consisting in a main window and error or information windows.

3.3.1 Selecting a version

Figure 3-3 Version Manager Home Page

The Version Manager Home Page comprises the following windows and buttons.

Liste of Complete Installed versions

Messages Window

Active button: launches the Activation Process

Start System Control button: not accessible

Quit button: quits the Activation Process


77 A2 88US 3-5

Home Page windows:

• a Message Window displaying activation process data. Contents are copied in the V7000 <rootdir>1\Trace\V7000 Installation and Activation.log file at the end of the process,

• an Information Window displaying the list of complete versions installed. A version may be selected with the mouse before launching the activation process.

Home Page buttons:

• a Quit button, accessible to quit the Version Manager before or after the activation process. The Quit button cannot interrupt the activation process,

• an Active button, accessible when a version is selected. The Active button launches the version activation process, even when the selected version is already active,

• a Start System Control button (Start Syc Figure 3-3), not accessible until the selected version activation process is finished. Once the activation process is finished, the Start System Control button becomes accessible if the user belongs to the V7000Operators group.

The Active and Start System Control buttons operate alternately. When one is accessible, the other is not accessible – if the user belongs to the V7000Operators group.

Before the selection and activation of a version, the Message Window displays current V7000 status. During the activation process, the Message Window displays activation status data.

V7000 working environment integrity is indicated by the line V7000 Working Space is consistent. The active version shown in Figure 3-3 is version V0.12. Active version services are launched whereas Interop7 administration services. At this level, non-installed and non-launched services are not differentiated.

Windows WinMgmt service and OpenSave Backup Agent for GCOS7 if installed are also managed for V7000 activation need. In Figure 3-3, Windows WinMgmt service is launched and Opensave Agents not installed.

The line V7000 Version Manager V0.13.1 is ready indicates which version of the Version Manager tool is being used. Here a correction for version V0.13.0 is being used. The Version Manager is capable of managing all the versions installed.

The following lines concern the internal checks carried out on the selected version (file, registry data consistency). These lines are displayed for each version selected, prior to launching the activation process.

1 Rootdir is C:\Program Files\Bull\V7000 for DPS 7000 XTA Platforms (IA32 Architecture), and C:\Program Files (x86)\Bull\V7000 for Novascale 7000 Platforms (IA64 Architecture).


3-6 77 A2 88US

The following options are open:

• continue with an active version (V0.13.1) by pressing Quit,

• select and activate a different version (V0.12) by pressing Active,

• return to the standard complete version (V0.13) by pressing Active.

If V0.13 is selected, the top of the Dialogue Box changes.

Figure 3-4 Selecting a Version

When a version with one or more corrections is selected, a volatile list containing the corrections installed is displayed.

The following options are open:

• select a correction with the mouse,

• inhibit the selection of a correction by selecting NONE to return to the standard complete version (V0.13),

• select a new complete version (V0.12 in Figure 3-1).

When V0.12 is selected, the list of corrections is no longer displayed as a correction is not associated with this version.

The activation process begins once the Active button has been clicked and the messages generated are copied to the V7000 <rootdir>\Trace\V7000 Installation and Activation.log file.


77 A2 88US 3-7

IMPORTANT: 1. When installing the software for the first time, the installed version alone

can be activated.

2. A correction can be selected directly, i.e. without previously activating the associated complete version or a previous correction.

3. The active version may be selected and re-activated. The following Dialogue Box is opened (Figure 3-5).

Figure 3-5 Active Version Re-activation Dialogue Box

• Yes: restarts a complete activation process (this option may be useful when activation of the first version installed fails),

• No: allows the selection of a new version.

3.3.2 Activation process

The activation process decides whether or not GCOS7 and the active version are to be shut down. If the active DianeNet Driver is different from the one selected, a Warning Message is sent to the Administrator (Figure 3-4), reminding him to intervene on the telecommunications cards when the activation process is finished (Cf. V7000 Configuration and Maintenance Guide - 77 A2 77US)).

Figure 3-6 DianeNet Driver Re-install Warning Message

Activation also creates specific Start Menu of the version, increases EventLog size if needed, manages Dr Watson properties and Firewall configuration.

For Activation process errors, see paragraph 3.3.3 .

13

3


3-8 77 A2 88US

Figure 3-7 shows the end of the activation process for version V0.12.

Figure 3-7 Complete Version Activation Process (V0.12)

The Active button is no longer accessible since the activation process is finished.

If the user also belongs to the V7000Operators group, the Start System Control button becomes accessible, allowing the user to launch the System Control Window (Figure 3-9). Otherwise, the user is to press Quit to end the process.


77 A2 88US 3-9

The activation process for a correction affecting the operating system nucleus is comparable to the complete version activation process. However, the activation process for a dynamic correction, only affecting Input / Output controllers, is simplified (Figure 3-8).

Figure 3-8 Dynamic Correction Activation Process

The actions to be performed are limited to updating internal data, without shutting down the Services.


3-10 77 A2 88US

The Start System Control button is not accessible. It is not applicable in the case of a dynamic correction.

Figure 3-9 V7000 System Control Console Startup

For further information, Cf. V7000 Operator's Guide - 47 A2 74US.

When the activation process is finished, the specific version Start Menu is created (Figure 3-10).

Figure 3-10 V7000 Start Menu

The V7000Operators tools are positioned directly under the V7000 root directory, whereas the Bull Services sub-menu groups the maintenance tools reserved for Bull Support personnel.


77 A2 88US 3-11

IMPORTANT: Interop7 administration tools are inserted in the V7000 Start Menu when Interop7 is installed and are maintained when versions are changed.

3.3.3 Errors encountered during the version activation process

When an error is detected, a message indicating the origin of the error is displayed. The activation process is stopped when the error window is closed.

Furthermore, the detected error is underlined in the last line of the Version Manager Home Page (Figure 3-11).

Error Message

V7000 is running

Figure 3-11 Error Message: GCOS7 Running

Errors causing the termination of the Version Manager may be due to:

13

3


3-12 77 A2 88US

• inconsistencies detected in the version being activated or in the complete version when a correction is being activated,

• the impossibility to install the telecommunications driver (DianeNet),

• the impossibility to register components (Services, Dlls, Snap-ins, …),

• the impossibility to transfer files (used files, therefore irreplaceable) – administration tools open, EventViewer open, …

NOTE: Some errors are recoverable. In this case, the user is prompted to retry current operation after errors corrections (Figure 3-12).

Figure 3-12 Retry on error

Click on Cancel aborts the activation process.


77 A2 88US 3-13

IMPORTANT: The activation process trace file is saved in the V7000 Setup file (<rootdir>\Trace \V7000 Installation and Activation.log file).

Cf. Chapter 6 (§ 6.2) for further information.

13

3


3-14 77 A2 88US

❑

77 A2 88US 4-1

4. Installing the remote administration tools

The remote administration tools are used to for V7000 network management and administration via dialogues with the System Administrator Manager (SAM) located on the DPS 7000/XTA machine (Cf. V7000 Operator’s Guide – 47 A2 74US).

The remote administration tools can be installed on a Windows™ Station or Server (non DPS 7000/XTA) from the V7000 CD-Rom by selecting the Remote V7000 Administration Tools option in the Setup Type dialogue box.

The remote administration tools are not installed in directories identified by the VersionId and are not managed with a Version Manager type tool.

A single Main version of the remote administration tools may therefore be installed at any given time. The remote administration tools are compatible (upward and downward) with the version of V7000 Server ones. Nevertheless a correction version can be installed on a main one.

When the software is installed for the first time, the V7000Operators and V7000BullServices groups are created to allow user access to specific tools.

NOTE: The figures presented in this document are only examples and may vary according to the V7000 versions used (e.g. versions V0.10, V0.10.1, V0.11, V0.12, V0.13, V0.13.1).

4.1 How to install remote administration tools

Remote administration tools can be installed from the V7000 CD-Rom.

IMPORTANT: It is mandatory to uninstall the current version, after closing all active tools, before installing a new main version, except for a correction one.

13

3


4-2 77 A2 88US

4.2 Setup

Select Remote V7000 Administration Tools to install the remote administration tools (Figure 4-1).

Setup is comparable to that of a complete version of V7000 software. Setup copies files, creates registry keys, a Start Menu and user groups, registers the components and sets security levels.

Figure 4-1 Remote Administration Tools Setup Type Selection

Installing the remote administration tools

77 A2 88US 4-3

The Setup path selected when the software is installed for the first time (Figure 4-2) is confirmed and the path is used for all future install processes.

Figure 4-2 Remote Administration Tools Setup Path Selection

The main phases are underlined by Wait Messages comparable to those displayed during complete V7000 software installation.

IMPORTANT: On a XP Windows or Windows 2003 Server, the message shown in Figure 4-3 is intended for the System Administrator in order to modify security policies for SYC and VOS clients.

13

3


4-4 77 A2 88US

Figure 4-3 Message asking the Security Policies modifications

On XP Station, the Administrator must

- From Start Menu, choose Settings then Control Panel.

- Double-click on Administrative Tools then on Local Sheet

- Choose Security Policy

- In Local Policies, select "Security Options"

- Set Network option "Let everyone permissions apply anonymous users" enable

On Windows 2003 Server, the Administrator must

- From Start Menu, choose Settings then Administrative Tools.

- Click on Local Security Policy Tools then choose Local Policies

- Select "Security Options"

- Set Network option "Let everyone permissions apply anonymous users" enable

IMPORTANT : In case of Windows XP Service Pack 2, native Windows Firewall must be configured (see § 4.6) .

13

3


77 A2 88US 4-5

4.3 Launching the remote administration tools

The required tool is launched from the V7000 Start Menu by the appropriate user (Figure 4-4).

For further information, Cf. V7000 Operator's Guide - 47 A2 74US) and V7000 Configuration and Maintenance Guide - 77 A2 77US).

Figure 4-4 Remote Administration Tools Start Menu

NOTE: Interop7 is integrated in the Start Menu, if installed.

4.4 How to install remote administration tools correction

A correction can be installed on a main version using correction Setup program.

If the correction level must be changed, uninstall current correction version then main version one (See chapter 5).

Restart the system (MANDATORY).

Install first Main version then the right correction version.

13

3


4-6 77 A2 88US

4.5 Anomalies encountered during Setup

Problems, comparable to those encountered when installing complete V7000 software, may be encountered when installing the remote administration tools.

Cf. paragraph 2.5 and Chapter 6.


77 A2 88US 4-7

4.6 Old Firewall configuration

On a remote station with Windows XP Service Pack 2 (and V7000 version lower than V4), native Windows Firewall is started in a standard way and must be kept alive to insure high level of security.

So, it must be manually configured to allow incoming communications between local V7000 Remote Administration Tools (client components) and a remote V7000 Platform (server components).

With V7000 V4 versions, a new tool automatically configures the firewall for V7000 needs (cf paragraph 4.7).

Configuration of Firewall is made by the administrator of the station and consists to a set of permissions. A permission (or Exception) is defined through a specific Port or an executable.

Launch Firewall configuration from Control panel Menu, then click on Windows Firewall icon .

Verify that Firewall is started (On) and that Don’t allow exception option is not selected (Figure 4-5).

Figure 4-5 Firewall Main Window


4-8 77 A2 88US

The Exception tab shows four default defined permissions (Figure 4-6).

Figure 4-6 Firewall default defined permissions.

V7000 Remote Administration Tool use needs three new defined exceptions:

- one for RPC port (Figure 4-7),

- one for ClientConsole.exe executable (Figure 4-8),

- one for mmc.exe system file.


77 A2 88US 4-9

4.6.1 Adding RPC Port

Click Add Port option (Figure 4-6).

Give RPC for Name of the exception, and 135 for Port number. TCP must be checked, then click OK (Figure 4-7).

Figure 4-7 Adding RPC Port.


4-10 77 A2 88US

4.6.2 Adding ClientConsole.exe and mmc.exe Programs

Click Add Program option (Figure 4-6).

When the Add Program window is opened, click on Browse button.

Look for ClientConsole.exe location (C:\Program Files\Bull\V7000\Component) then Open this program (Figure 4-8).

Figure 4-8 Adding ClientConsole.exe Program.

Same as above for mmc.exe file. Browse for C:\Windows\System32\mmc.exe then click Open.


77 A2 88US 4-11

The Firewall configuration is now (Figure 4-9):

Figure 4-9 Firewall configuration for V7000 usage.

Quit the Firewall configuration.

Now launch V7000 Remote Administration Tools (System Control V7000 Operation Supervisor), then choose connect to Another Computer option as described before.

4.7 New Firewall configuration

Firewall Configurator Tool is provided in V4 V7000 Versions to avoid manual configuration.


4-12 77 A2 88US

Firewall configuration for V7000 needs is made with a new V7000 tool and will be taken in account when windows firewall is started.

During V7000 Setup, Firewall Configurator tool is launched in silent mode in order to configure the Windows firewall. This configuration is Mandatory for V7000 Remote Administration Tools use when Windows firewall is running.

Firewall Configurator tool is installed by Setup program and a new shortcut (Firewall Configuration) is added in V7000 Start menu (Figure 4-10).

Figure 4-10 V7000 Start Menu from V4 Versions.

For further information, Cf. V7000 Configuration and Maintenance Guide - 77 A2 77US).

77 A2 88US 5-1

5. Uninstalling the software

A version of the V7000 software can be uninstalled via the Add/Remove Programs tab in the Windows™ Control Panel or by restarting Setup.

Uninstall is symmetrical to Setup and is based on a log file created during Setup by InstallShield. This log file lists all the actions to be removed.

Uninstall only removes the components of the version concerned. The uninstall process does not affect the objects used by V7000, e.g. groups, application working directories, the version configuration directory.

When the last existing version is uninstalled, remove of V7000 environment is proposed.

The remote administration tools uninstall process does not destroy the V7000 environment – unless requested.

IMPORTANT: The figures presented in this document are only examples and may vary according to the V7000 versions used (e.g. versions V0.10, V0.10.1, V0.11, V0.12, V0.13, V0.13.1).

13

3


5-2 77 A2 88US

5.1 What can be uninstalled?

The following software components, identified by a V7000 VX.Y[.Z] type identifier under the Add/Remove Programs tab in the Control Panel, can be uninstalled:

• a complete version of V7000,

• a V7000 correction,

• the remote administration tools.

IMPORTANT: A complete version can only be uninstalled once the last corresponding correction has been uninstalled.

The uninstall process (except the uninstall process for the last existing version) is traced in the Installation and Activation.log in the <rootdir>\Trace directory.

5.2 How to uninstall the software

An obsolete or inactive version can only be uninstalled by a System Administrator via the Windows™ Control Panel

CAUTION: It is mandatory to use the Add/Remove Programs tab in the Windows™ Control Panel or to restart Setup.

In no event may a version be uninstalled manually, e.g. by removing the root directory.

The server does not have to be rebooted when an inactive version is uninstalled.

13

3

Uninstalling the software

77 A2 88US 5-3

5.3 Uninstall of V7000 server

The uninstall process is identical for a complete and correction versions.

Uninstall begins by launching the InstallShield Wizard (Figure 2-1). A Warning Message recalls the type of platform concerned by the uninstall process: Full V7000 Server (Figure 5-1) or remote administration tools (Figure 5-2).

Figure 5-1 V7000 Uninstall Warning Message

Figure 5-2 Remote Administration Tools Uninstall Warning Message

• No: stops the uninstall process and an Abort Window is displayed. The V7000 environment is not affected,

• Yes: launches the uninstall process. The uninstall process is irreversible. A Confirm Box is displayed (Figure 5-3).

Figure 5-3 Uninstall Confirm Box


5-4 77 A2 88US

• Cancel: stops the uninstall process,

• OK: continues the uninstall process.

IMPORTANT: When the version selected is active and started (Active Services), a Confirm Box is displayed (Figure 5-4).

Figure 5-4 Active Version Uninstall Confirm Box

• No: stops the uninstall process and an Abort Window is displayed. The Services are not stopped, the version remains started and the V7000 environment is not affected.

• Yes: stops the Services (including Interop7, if present) and continues the uninstall process.

If the version is only active (no services started), a similar Confirm Box is displayed.

An Uninstall Status Window is displayed during the uninstall process (Figure 5-5).

A similar Status Window is displayed when uninstalling a complete version, a correction or the remote administration tools

This phase only takes a few seconds.

13

3


77 A2 88US 5-5

Figure 5-5 V7000 Uninstall Status Window: Uninstalling Files

When the last existing complete version of V7000 or the remote administration tools are to be uninstalled, a Confirm Box is displayed (Figure 5-6).

Figure 5-6 V7000 Environment Cleanup Confirm Box

If Yes is clicked, the whole V7000 environment is cleaned and the User will be prompted to reboot.

If No is clicked, the V7000 environment is left as it is.


5-6 77 A2 88US

The process ends with a standard Finish Window (Figure 5-7).

Figure 5-7 Uninstall Process Finish Window

5.4 Uninstall of V7000 Remote Administration Tools

Uninstall of Remote Administration Tools Main version is similar to V7000 server (See paragraph 5.3).

IMPORTANT: A reboot is required at the end of process if you want to install another version.

If a Correction version is installed, first uninstall Correction Version then the Main one.

Reboot only once after Main version uninstall.

13

3


77 A2 88US 5-7

Anomalies encountered during Uninstall

CAUTION: In general, Uninstall fails due to inconsistencies in the resources used by V7000 tools or Windows™, or because connections are still active. When Uninstall fails, an Abort Window, similar to that shown in Figure 2-11, is displayed.

Uninstall is to be restarted once all the components have been shut down and tools closed.

Uninstall may end with a Reboot Prompt to clean the freed files. The server may be rebooted later.

Uninstall may be stopped by InstallShield or Windows™, in which case specific error messages are displayed.

In all events, Uninstall is to be restarted once the problems encountered have been corrected.

5.5 Finishing Uninstall

Once Uninstall is finished, the description of the version is no longer displayed under the Add/Remove Programs tab in the Control Panel and cannot be viewed with the Version Manager tool.


5-8 77 A2 88US

❑

77 A2 88US 6-1

6. Troubleshooting

Errors may be encountered during the Setup and Uninstall processes (symmetrical processes), or when a version is activated.

These errors are traced in the Installation and Activation.log, shared by the installation and activation processes, located in the <rootdir>\Trace directory.

6.1 Problems encountered during Setup / Uninstall

The most common problems encountered during Setup concern the user, Server capacity, or internal V7000 environment inconsistencies:

• insufficient user rights,

• insufficient Server capacity (disk space, …),

• InstallShield resources not loaded,

• access to a resource impossible at a given time (e.g.: CD-Rom),

• internal inconsistencies in V7000 management structures, preventing the correct installation of a version,

• installation of a correction not permitted because the corresponding complete version is either absent or inconsistent (incorrect installation, loss or corruption of components),

• …

The most common problems encountered during the Uninstall process concern accessibility to the components to be deleted or unregistered (files open during Uninstall).


6-2 77 A2 88US

Solutions:

• in the event of a problem with access rights, connect the user with the rights required,

• in the event of a problem with resources, correct the Server (disk space, memory, CD-Rom, …),

• check that no version with the same index is already started (with the Windows™ Service Control Manager), then restart Setup / Uninstall,

• uninstall the version responsible for the problem via the Control Panel and reinstall,

• check that corrections are compatible with the complete versions of V7000 software,

• free V7000 resources. Check that components are not used by Windows™ tools. Should this be the case, close these tools:

− EventViewer message dlls open,

− directories or files accessed by a Windows™ Explorer,

− files opened by V7000 mmc consoles (V7000 System Control, …) or by Windows™. Check with the Windows™ Task Manager,

− unseen Terminal Service connections occupying resources. Check with the V7000\Operation Supervisor or with the Windows™ Task Manager (then close).

• as a last resort, restart the Server if requested by InstallShield. If problems are not solved, contact the Bull Support Center with the data collected by the Bull Collector tool.

Troubleshooting

77 A2 88US 6-3

6.2 Problems encountered when activating a version

The activation of a version is recorded in the Installation and Activation.log file in the <rootdir>\ Trace directory, which logs a trace of any errors encountered.

Main problems concern user rights and access to resources (files) when activating a version.

V7000 files may be used by the machine or by Windows™.

Solutions:

• check that GCOS7 is not running. If GCOS7 is running, close GCOS7 applications, execute TSYS then TS. Finally, close the System Control console,

• close the local administration tools. The V7000\Operation Supervisor tool visualizes and identifies connected users,

• close the EventViewer and the Computer Management window,

• check that mmc.exe processes (in relation with V7000 mmc consoles) are not running with the Task Manager. These processes may hold certain V7000 mmc console files. Terminate with the Task Manager,

− check that no users are connected via Terminal Service. Check with the V7000\Operation Supervisor or with the Windows™ Task Manager (then close).

• as a last resort, restart the Server if the problems encountered concern the V7000 Driver and Services.

If problems are not solved, contact the Bull Support Center with the data collected by the Bull Collector tool.


6-4 77 A2 88US

❑

77 A2 88US A-1

A. Starting a minimum GCOS7 System

This appendix briefly outlines how to start a minimum GCOS7 disk system on a DPS 7000/XTA machine for the first time. However, please refer to the V7000 Operator's Guide (77 A2 74US) and V7000 Configuration and Maintenance Guide (77 A2 77US) for further information.

• Installation of Windows™ on the platform,

• Installation of V7000 from the CD-Rom by an Administrator group user,

• Creation of a privileged user in the V7000BullServices and Administrators groups and connection of the privileged user to the Server,

• Activation of the installed version with Version Manager (tools accessible) by the privileged user,

• Acquisition of the platform identifier with the Platform Identifier tool and transmission of the identifier to the Bull Support Center for calculation of the hardware key,

• Installation of hardware key supplied by Bull by the privileged user with the Key Installer tool,

• Creation of the machine configuration by the privileged user with the Configuration Editor tool according to the customer’s key. Actual configuration may be “lower” than the maximum configuration defined by the key,

• Installation of a minimum GCOS7 TS9866 system disk from the GCOS7 technical status image supplied on the CD-Rom for the DPS 7000/XTA machine,

• Adaptation of the GCOS7 system disk by the privileged user via the Disk Manager tool,

• Checking and activating the configuration with the Configuration Editor tool,

• Creation of a V7000 Operators group user and connection of the user to the Server,

• Starting the System Control by the V7000 Operator from the V7000 Start Menu, followed by the GCOS7 system INIT command (right-click on V7000 (Local/S0)),

• Opening an LN02 console, requested with INIT, via the Operation Supervisor tool,


A-2 77 A2 88US

• Starting the GCOS7 system with the RESTORE command under IL01 Options in the LN02 console,

• Connection of the standard GCOS7 operator and system configuration before restarting the real GCOS7 configuration,

• Where applicable, installation of Interop7, first on GCOS7 then on Windows, from the appropriate installation media.

Once these operations have been completed, the following can be installed independently:

• a new version of GCOS7 by GIUF,

• a new DPS 7000/XTA machine dedicated version of Interop7 by ISI7,

• a new version of V7000.

77 A2 88US g-1

Glossary

D

DLL Dynamic Link Library

Functional extensions used by an executable file.

DPS 7000/XTA New generation of Extended Twin Architecture DPS 7000 machines.

Designates the new range of platforms supporting the GCOS7 operating system managed by V7000.

G

GCOS7 General Comprehensive Operating System 7

BULL propriety operating system running either on a standard DPS 7000 machine or on a DPS 7000/XTA machine.

I

IA (Intel® Architecture)

Designates Intel® Processor Architecture around which the DPS 7000/XTA machine is designed. Pentium™ processors belong to the IA32 family (32-bit architecture). Itanium™ will be the first processor in the IA64 family (64-bit architecture).

InstallShield

Install program creation and packaging tool for Windows™ applications.

Interop7 Interoperability between GCOS7 and the open world.


g-2 77 A2 88US

Set of communication gateways between GCOS7 applications and open world applications (Unix™, Windows™, …).

M

MMC Microsoft® Management Console

Graphic environment or window defining a console grouping a set of tools or Snap-ins. An MMC can be local to the host machine or activated via the network.

N

NTFS New Technology File System

Secure Windows™ NT file system (access rights management).

O

OpenSave Backup Agent for GCOS7 GCOS7 backup agent of OpenSave solution to save/restore GCOS7 files in open world

R

RootDir Installed version file tree root.

Default access path based on the concatenation of the system disk identifier, "Program Files", the supplier’s name, the product name. In practice, the file tree root is that selected by the user plus V7000, if V7000 is not indicated in the selected file tree root.

S

SAM System Administration Manager

Generic term designating V7000 graphic Administration and Configuration tools.

Setup InstallShield install program. Setup performs all the operations required to install an application on a machine. It starts by simply launching the setup.exe executable file on the CD-Rom.

Snap-in A recorded DLL integrated in an MMC.

Glossary

77 A2 88US g-3

V

V7000 BULL software operating on a DPS 7000/XTA machine. V7000 is a Windows™ application that creates the environment required to run GCOS7 and its applications.

VersionId Version Identifier (VX.Y type for a complete version, VX.Y.Z type for a correction).

W

WINDOWS 2000 New generation Microsoft® NT operating system.

This term designates the new Microsoft® NT secure operating system.

WIZARD Graphic assistant guiding the user through an installation process.


g-4 77 A2 88US

77 A2 88US i-1

Index

A access control 1-6 access rights 2-7 activated version 3-1 Active 3-5 active version 5-4 Add/Remove Programs 5-1 administration tools 1-8 Administrator 2-4 Administrators 1-8 anomalies 2-10, 2-11, 2-13, 4-6

C CD-Rom 1-1, 1-6, 4-1 compatibility 4-1 complete installation 2-1 components 2-3, 4-2 configuration directory 5-1 Control Panel 5-1 copying files 2-3, 2-7 corrections 1-7, 2-12

D description 5-7 dialogue 2-3 DianeNet 3-7 disk devices 1-4 dlls 6-2 DPS 7000/XTA 1-1, 1-2 Dynamic Link Library g-1

E error 3-11 error messages 2-13 EventViewer 6-2 Extended Twin Architecture g-1

F finishing Setup 2-9 first Setup 2-3, 3-7 free disk space 1-8 freed files 5-7 Full V7000 Server 2-4 functional engine 2-4 functional evolutions 2-9 future installations 4-3

G gateways 1-2 GCOS7 1-1, 1-2, 6-3 GCOS7 client applications 1-2 GCOS7 data 1-2 GCOS7 operation 1-5 GCOS7 Operator 3-2 GCOS7 technical status 1-4 GCOS7 TS 9866 1-2 GIUF 1-4


i-2 77 A2 88US

H hardware configuration 1-5 Home Page 2-3 host machine 1-8

I IA Server 1-1 identifier 1-7 incorrect installation 6-1 install process 2-2 install program 1-6 installation 1-5, 2-11 Installation and Activation.log 5-2, 6-1, 6-3 InstallShield 1-1 Interop7 1-1, 1-7, 3-3, 3-11, 5-4

L local administration tools 2-4

M mainframe computers 1-2 maintenance tools 3-10 migration of data 1-6 mmc consoles 6-2 multiprocessors 1-2

N NTFS 1-4

O obsolete version 5-2 operating system 1-2 operating system nucleus 3-9

P partitioning 2-1 preliminary check 2-3 privileged user 1-5

Q Quit 3-5

R Readme 2-9 reboot 5-7 registry 2-8 registry keys 4-2 re-installing 2-11 remote administration tools 1-3, 2-4, 4-1 resources 2-13, 6-2 rights 2-13

S SAM 1-3, 4-1 security 2-3, 4-2 server 5-2 Server capacity 6-1 Server installation 1-6 Setup 1-1, 1-6, 1-8, 2-2, 4-2 Setup path 2-6, 4-3 Setup trace 2-13 Setup Type 4-1 Snap-ins g-2 specific tools 4-1 Start Menu 2-3, 2-8, 3-2, 3-3, 4-2 status 3-5 supported errors 2-13 System Control 3-8 System Control Services 3-1

T telecommunications 1-4, 2-4 Terminal Service 1-9, 6-2

Erreur ! Style non défini.

77 A2 88US i-3

U unexpected error messages 2-14 uninstall 2-11, 4-1, 5-1, 5-7 update 2-3 user 6-1, 6-2, 6-3 user groups 2-1, 4-2

V V7000 1-1, 1-3 V7000 Administration Server 3-1 V7000 Bull Services 4-1 V7000 Operators 4-1 V7000 root directory 3-10 V7000 software 1-1, 1-2 valid key 1-6 version compatibility 6-2 Version Manager 1-5, 2-9, 3-3 VersionId 4-1

W Wait Message 2-3 Wizard 5-3 working directories 5-1


i-4 77 A2 88US

Technical publication remarks form

Title : DPS7000/XTA NOVASCALE 7000 V7000 Software Installation and ActivationGuide

Reference Nº : 77 A2 88US 03 Date: March 2006

ERRORS IN PUBLICATION

SUGGESTIONS FOR IMPROVEMENT TO PUBLICATION

Your comments will be promptly investigated by qualified technical personnel and action will be taken as required.If you require a written reply, please include your complete mailing address below.

NAME : Date :

COMPANY :

ADDRESS :

Please give this technical publication remarks form to your BULL representative or mail to:

Bull - Documentation Dept.

1 Rue de ProvenceBP 20838432 ECHIROLLES [email protected]

Technical publications ordering form

To order additional publications, please fill in a copy of this form and send it via mail to:

BULL CEDOC357 AVENUE PATTONB.P.2084549008 ANGERS CEDEX 01FRANCE

Phone: +33 (0) 2 41 73 72 66FAX: +33 (0) 2 41 73 70 66E-Mail: [email protected]

CEDOC Reference # Designation Qty

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

_ _ _ _ _ _ _ _ _ [ _ _ ]

[ _ _ ] : The latest revision will be provided if no revision number is given.

NAME: Date:

COMPANY:

ADDRESS:

PHONE: FAX:

E-MAIL:

For Bull Subsidiaries:

Identification:

For Bull Affiliated Customers:

Customer Code:

For Bull Internal Customers:

Budgetary Section:

For Others: Please ask your Bull representative.

BULL CEDOC

357 AVENUE PATTON

B.P.20845

49008 ANGERS CEDEX 01

FRANCE

77 A2 88US 03REFERENCE

v7000 software installation and activation guide -...

Documents