Quantum AMU 3.12 User Manual

AML Management Unit

Reference Guide

Version 3.12

Document Number: 6-00440-02

The information contained in this document is subject to change without notice.

This document contains proprietary information which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without prior written consent of ADIC.

ADIC shall not be liable for errors contained herein or for incidental or consequential damages (including lost profits) in connection with the furnishing, performance or use of this material whether based on warranty, contract, or other legal theory.

All trademarks are the property of their respective owners.

All rights reserved. No part of this document may be copied or reproduced in any form or by any means, without prior written permission of ADIC Europe, ZAC des Basses Auges, 1, rue Alfred de Vigny, 78112 - Fourqueux, FRANCE.

ADIC Europe assumes no responsibility for any errors that may appear in this document, and retains the right to make changes to these specifications and descriptions at any time, without notice.

This publication may describe designs for which patents are pending, or have been granted. By publishing this information, ADIC Europe conveys no license under any patent or any other right.

ADIC Europe makes no representation or warranty with respect to the contents of this document and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Further, ADIC Europe reserves the right to revise or change this publication without obligation on the part of ADIC Europe to notify any person or organization of such revision of change.

Every effort has been made to acknowledge trademarks and their owners. Trademarked names are used solely for identification or exemplary purposes, any omission is unintentional.

ADIC is a registered trademark and ADIC Europe is a trademark of Advanced Digital Information Corporation.

ADIC USA ADIC Europe ADIC Germany Beteiligungs GmbH, KG Tel.: +1-303-705-3900 ZAC des Basses Auges Eschenstrasse 3 Fax: +1-303-792-2465 1, rue Alfred de Vigny D-89558 Boehmenkirch, Germany ATAC: 1-800-827-3822 78112 Fourqueux, FranceTel:+00.800.9999.3822 www.adic.com Tel.: +33.1.3087.5300

Fax: +33.1.3087.5301

Document number: 6-00440-02

Published: 22 Jul 2003 Printed in the USA

ADIC CORPORATE • 11431 WILLOWS ROAD, NE • REDMOND, WASHINGTON, USA • 1-800-336-1233

ADIC • 8560 UPLAND DRIVE • ENGLEWOOD, COLORADO, USA • 1-800-827-3822

ADIC • 10 BROWN ROAD • ITHACA, NEW YORK, USA • 1-607-241-4800

AMU

Contents

Introduction

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Explanation of Symbols and Conventions . . . . . . . . . . . . . . . . . . . . . . . 1-1

Associated Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Customer Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Technical Assistance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Contacting Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Description

AMU Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Command Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Dismount Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Supported drives and required DCI unit hardware . . . . . . . . . . . . . 2-2

Clean Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Import/Export Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Host-Controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

AMU-Controlled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Foreign Mount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Archive Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Data Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

DUAL AMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Database Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Log Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Disaster Recovery Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Host Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

AMU as Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Selection and Number of Connections . . . . . . . . . . . . . . . . . . . . . . 2-8

Connecting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Access Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Access to AMU Operating Console . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Database Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

AMU Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Functions of Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Service Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

AMU System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Operating Console

Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Design of the Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

System menu field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Selecting a Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Altering a Window´s Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Moving a Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Closing a Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Overview of Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Menu Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Menu Edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Menu View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Menu Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Manual Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Insert Clean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Eject Clean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Clean Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Menu Admin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Process Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

Clean Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Scratch Pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

Create Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

Update Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

Edit Volser Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28

Menu Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

Command String Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

AMU

iv 6-00440-02

AMU

Command "Mount...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

Command "Keep...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

Command "Move...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

Command "Inventory...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

Command "Close Unit...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

Command "Unload Unit...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

Command "Status...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

Command "Purge...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

Command "Homing...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

Command "Put...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

Command "Get...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40

Command "Look...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41

Command "Turn...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42

Command "Insert Clean...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

Command "Eject Clean...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

Command "Clean Drive...” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

Command "Switch” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

Menu Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44

Command "Teach single command” . . . . . . . . . . . . . . . . . . . . . . . 3-44

Command "Teach MTCGDialog” . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

DUAL-AMU Service: File Transfer . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

DUAL-AMU Service: Activate this AMU . . . . . . . . . . . . . . . . . . . . 3-50

Continuous Send . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

Start Testmode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

Stop Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

Rho File Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

Menu Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

Configuration

Window "Graphical Configuration” . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

The Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Configuring a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Deleting a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Defining connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Saving the configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Configuration Windows of Components . . . . . . . . . . . . . . . . . . . . . . . 4-4

Host Computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Contents v

AMU

Command Look . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

AMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Robot System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Scanner (barcode reading system, for AML/J only) . . . . . . . . . . . . . 4-10

ADS (Automatic Data Switch) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Configuration of an AML System with DUAL AMU and Automatic Data Switch 4-11

Meaning of the file LOCAL.AMU . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Drive Folder (Drive Container) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

IBM 3590 drive parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

IBM LTO drive parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

DLT/SDLT drive parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

Sony AIT Drive Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

Storage Tower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

I/O Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Linear shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28

Problem box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30

Configuration Window for AMU Communication . . . . . . . . . . . . . . . 4-31

Interface Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32

RS232 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

I2 APPC (LU 6.2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34

TCP/IP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36

I7 Internal PMAC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37

I8 RS232 Scanner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38

I9 RS232 Interface (SOTEC Multiport) . . . . . . . . . . . . . . . . . . . . . 4-39

IB Serial PMAC Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40

ID CAN-Interface (DCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42

Configuration Of Volser Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

Window Edit Volser Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44

Inserting a new Volser range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45

Changing an existing Volser range . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46

Defining a dynamic range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46

Changing individual archive catalog entries . . . . . . . . . . . . . . . . . . . 4-46

Configuration of the Drive Control Interface . . . . . . . . . . . . . . . . . . . . 4-47

Configuration of Drive Cleaning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49

vi 6-00440-02

AMU

Configuration of Scratch Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50

Configuration of AMU Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50

Configuration of AMU Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51

AMUSTART.CMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52

Symbols on the Operating Console . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53

Archiving Function of the OS/2 Operating System . . . . . . . . . . . . . . . 4-54

Logic Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55

ABBA/1 Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55

Comparison of AMU and ABBA/1 Coordinates . . . . . . . . . . . . . . . . 4-55

Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55

Storage segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56

Linear shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56

Archive Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57

Special Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57

I/O units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57

Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58

Problem box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59

Status of Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60

Utilities

Rho File Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Starting the Rho File Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

During operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

After booting the control system . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Menu File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Menu Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

JUSTUTIL.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Start "JUSTUTIL.EXE” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Activate changes in the list of teach points . . . . . . . . . . . . . . . . . . . . 5-14

PMMaint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Starting PMMaint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Starting from OS/2 desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Starting from OS/2 command line . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Menu File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Start/Stop PMac Progs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Query PMac status... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Download File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Contents vii

Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Menu Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Motor Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Initial Teach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

PMac Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

Barcode Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

Gripper test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27

Menu Teach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

Teach Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

Setup new Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30

PMAC PVAR DIalog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32

Adjust Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33

Menu Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35

Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36

Global status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37

Handling units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39

Motor status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

AMU

LOG2ASC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

Structure of Log-Filename: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

SHOWINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46

Range in the file AMUCONF.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47

Ranges in file AMUCONST.INI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48

PATINI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49

Procedures

Switching the AMU Computer On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Starting the AMU Operating Console . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Terminating the AMU Operating Console . . . . . . . . . . . . . . . . . . . . . . . 6-2

Switching the AMU Computer Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

System Shutdown OS/2 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Remote Power ON/OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Switching Over between the DUAL-AMU Computers . . . . . . . . . . . . . . 6-3

Switch (Switch-Normal) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

Switch-Force . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Preconditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

viii 6-00440-02

AMU

Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Disaster Recovery Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Precondition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Preparing the Disaster Recovery Support . . . . . . . . . . . . . . . . . . . . . 6-5

Create a file listing the media to be ejected . . . . . . . . . . . . . . . . . . . 6-5

Structure of the file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Example: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Ejection Procedure for Disaster Recovery . . . . . . . . . . . . . . . . . . . . . 6-5

Installing the AML Management Software . . . . . . . . . . . . . . . . . . . . . . 6-6

Useful System Functions

Useful OS/2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Mode Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Pstat Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Syslevel Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Restoring the OS/2 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Saving Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Compressing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Decompressing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

TCP/IP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

"ping” Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Netstat Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

rpcinfo Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Database Manager DB/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Database Destroyed - What to do? . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Special SQL error message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Backup of Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11

Restoring the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

Contents ix

Exporting Tables from the Database . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Query Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

Example 1 (drive engagement of all drives) . . . . . . . . . . . . . . . . . 7-14

Example 2 (on which drive is Volser 000815?) . . . . . . . . . . . . . . . 7-14

Example 3 (are there several entries for Volser 000815?) . . . . . . 7-14

Assignment of Volsers to Compartments . . . . . . . . . . . . . . . . . . . . . 7-14

Messages

Error Codes (ABBA/1 Format) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Messages in AML/2 Format (AMU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Robot Control System Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Logic Errors of the Application Program . . . . . . . . . . . . . . . . . . . . . . 8-17

Handling Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

Barcode and Teaching Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20

Hardware Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21

Robot Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22

Message Storage Tower . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22

I/O Unit Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24

Automatic Data Switch Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26

AMU Information and Error Messages . . . . . . . . . . . . . . . . . . . . . . . 8-27

AMU

Appendix

Terms Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Trace Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

HOC-Trace (Communication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

CON-Trace (Operating Console) . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

KRN-Trace (Central Logic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

ART-Trace (Log- and Trace Functions) . . . . . . . . . . . . . . . . . . . . . . . A-4

ARC-Trace (Archive Catalog Management) . . . . . . . . . . . . . . . . . . . . A-4

BUD-Trace (Data Transfer to DUAL-AMU) . . . . . . . . . . . . . . . . . . . . A-5

DAS trace (diagnosis for DAS/2 Version 1.3) . . . . . . . . . . . . . . . . . . . A-5

DCM trace (Dismount and Clean Manager) . . . . . . . . . . . . . . . . . . . . A-5

Media Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Component Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

I/O Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11

Host Computers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

Storage Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

AML/J Linear Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

x 6-00440-02

AMU

Robots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

AMU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Control Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Important Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Index

Contents xi

AMU

xii 6-00440-02

AMU

Introduction

This manual contains information and instructions required to set up and operate the AML Management Unit (AMU).

Intended Audience

This guide is intended for use by system programmers and administrators working with the AMU software. Familiarity with the operating system OS/2 is assumed.

Organization

This publication contains the following chapters:

Chapter 1

Chapter 2 Description - Description of the functions of the AML Management Unit

Chapter 3

Chapter 4

Chapter 5 Utilities - Utility programs for diagnosis and installation of AML Systems

Chapter 6 Procedures - Description of important procedures (start, software update, etc.)

Chapter 7

Chapter 8 Messages - Log messages of AMU.

Appendix A Appendix - Glossary, trace level, media and device types.

Index

Introduction - Information concerning use of the manual as well as safety instructions.

Operating Console - Explanation of functions of the AMU operating console (CON)

Configuration - Explanation of the configuration features for AMU (AMU and OS/2)

Useful System Functions - Information on OS/2 operating system, database manager and TCP/IP functions in connection with AMU.

Explanation of Symbols and Conventions

The following symbols and highlighted passages note important information:

Symbol Damage to... Signal Word Definition Consequence

Person WARNING:

Material CAUTION:

NOTE:

Intended Audience 1-1

Imminent hazardous electrical situation

Potential damaging situation

Indicates important information that helps make better use of the system

Death or serious injury

Possible damage to the product, data, or environment

No hazardous or damaging consequences

The following is a list of formatting conventions used throughout this document:

• headline, for example, Chapter 2, Description

Italics

Helvetica term appearing on the operating console of AMU

Bold • Special Term, for example, Utilities

• filename, e.g. amuconf.ini

• variable, e.g. client_name

line or term appearing in an input window

AMU

Courier

[Courier] optional parameter

Param1 | Param2 alternative parameter (dism) abbreviated command

• program message

• command

• parameter or file

Associated Documents

This manual contains references to following documents:

DOC E00 003 AMU Installation Guide

DOC E00 018 AMU Problem Determination Manual

DOC E00 014 AML-Controller User Guide

DOC F00 018 HACC/DAS Administration Guide

Customer Assistance

Advanced Digital Information Corporation (ADIC) provides the following types of customer assistance for the AMU.

Technical Assistance

Telephone and e-mail support, as well as training for the AMU, is available through ADIC.

Contacting Support

Depending on how the technical support is purchased, telephone support is provided either through your reseller or directly through ADIC.

The ADIC Technical Assistance Center (ATAC) provides world-wide service and support.

In the USA 800.827.3822

World-wide free call 00.800.9999.3822

In the Germany 49.07332.83458

Phone number 0033-(0) 130875300

Fax number 0033-(0) 130875301

Send email to support@adic.com

1-2 6-00440-02

AMU

Description

Figure 2-1 AMU in a Multi-Host Environment

The AMU:

• is the main processor of the AML Mixed-Media Library (for each AML one AMU is required),

• is the central interface of the unmanned AML system,

• conducts the configuration service for hardware related AML functions,

• can be connected to several hosts,

• manages a database (SQL database DB/2 for OS/2) for;

• assignment of volsers to compartments,

• cleaning media,

• groups for rewritable media (scratch pools),

• is the hardware on which the following programs are running;

• AML Management Software (AMU),

• Distributed AML Server (DAS) (optional for connection of Distributed AML Clients),

• can be connected to a second AML to enhance the failure safety (DUAL AMU).

With the appropriate configuration, AMU can control various kinematics:

•AML/2

2-1

•AML/E

•AML/J

AMU

NOTE:

The AML Management Unit (AMU) is described in the following chapters. The information on DAS can be found in the following manuals:

• DAS Administration Guide

• DAS Interfacing Guide

AMU Tasks

The following section describes the various AMU tasks.

Command Management

AMU accepts commands from various interfaces:

• host interfaces

• graphic operating console on AMU processor (Refer to Operating Console on page 3-1)

The commands are either processed immediately and acknowledged (e.g. database queries) or entered on a command queue according to priority. The software can enter up to 240 commands on the command queue. All important events related to these commands are recorded in a log file.

AMU 3.12 accepts "foreign” cartridges from the I/O unit. You must, however, keep this compartment empty for the dismount procedure.

Dismount Management

Dismounting includes:

• the unload command to the drive

• the process inside the drive preparing the unloading (e.g. rewinding tape drives)

• the dismounting (medium is moved to dismounting position)

• the robot command to move the medium from the drive to a new position (e.g. home position)

These procedures can take different amounts of time depending on the drive type. With the aid of the Dismount Manager these procedures can be adapted to the different drive types, and can be controlled even if there are time differences for dismounting. (Refer to Drive on page 4-15)

AMU supports Drive Control Interface (DCI) for some types of drives.By means of this interface, the AMU can get drive status, send unload commands and handle clean request from drive.

Supported drives and required DCI unit hardware

The following drives are supported in current release of the AMU software.

2-2 6-00440-02

AMU

Drive DCI hardware version Notes

Quantum DLT ver. 4 or above

Quantum SDLT ver. 4 or above

IBM LTO ver. 4 or above

IMB LTO 2 FC ver. 4 or above

IBM 3590 ver. 4 or above

SONY AIT-1 ver. 4 or above

SONY AIT-2 ver. 4 or above

SONY AIT-3 ver. 4 or above

Require a special connection cable (part no. 407000529)

Clean Management

In an AML some drives may require cleaning. The following modes are differentiated:

• drive is cyclically cleaned manually

• drive is cyclically cleaned automatically using a cleaning medium

• drive is cleaned manually as needed

• drive is cleaned automatically as needed

To determine the cleaning mode required for your drive refer to the drive´s documentation or ask the drive´s manufacturer.

Clean Management supports cyclical automatic cleaning and automatic cleaning as needed. Cyclical cleaning is based on a count of the mount procedures.

NOTE:

The cleaning cycle for the drive in the archive is individually adjusted for each drive. When cleaning is required, the Clean Manager selects a cleaning medium from the clean pool.

The clean pool is the amount of cleaning media of a certain type, and each medium in the clean pool has a barcode label. Required parameters are assigned by means of the clean pool, such as maximum number of uses and minimum number of cleaning media required.

The clean pool is filled by special insert commands for cleaning media. The application receives a message when the number of available cleaning media drops below the minimum amount. The eject command for cleaning media is used to eject exhausted cleaning media.

In addition to this cyclical cleaning the application also offers a command for immediate cleaning of a drive.

DCI-connected drives send the clean request via DCI interface to the AMU (except for the IBM 3590 drive, which does not support this). Thus Clean Manager cleans the drive only in the correct procedure.

AMU Tasks 2-3

If your application should support cleaning of drives as needed or cleaning based on the read and write procedures of the drive, use this version.

AMU

Import/Export Management

In AML systems, ranges and units are defined for import and export of media. AMU differentiates these according to the type of I/O unit:

• import and export without stopping the robot

• import and export while stopping the robot (I/O unit/D -HICAP AML/J);

As well as according to the type of host connection for import and export:

• host-controlled

• AMU-controlled.

Host-Controlled

When the operator presses a push-button to request the I/O unit, it then becomes unavailable for the system (I/O unit cannot be used by the robot while operator is active).

After release by the system, the operator opens the I/O unit and removes the media from the I/O unit as well as puts other media into the I/O unit.

When the I/O unit has been closed, it is automatically made available to the system.

Robot activities designed to check the changes made, are started by commands send by the HOST software (HACC/MVS).

AMU-Controlled

When the operator presses a push-button to request the I/O unit, it then becomes unavailable for the system (I/O unit cannot be used by the robot while operator is active).

After release by the system, the operator opens the I/O unit and removes the media from the I/O unit as well as puts other media into the I/O unit.

When the I/O unit has been closed it is automatically made available to the system. AMU starts checking the open ranges. Movement of media (filing in a storage area) is triggered by a host command.

Foreign Mount

In the I/O unit a range for direct mount can be reserved (without insertion into archive shelves or towers). The media stored there do not require a barcode label for identification. The assignment is made via the compartments and virtual volsers (e. g.*FR001).

Database

The information on compartments in the archive and the media in the archive is saved in a relational database. Such information includes:

• serial number of the medium represented by a barcode (VOLSER)

• kind of coordinate (CTYPE), e.g., whether a cleaning or data medium can be stored on this coordinate

• qualities of the coordinate (CATTR)

• is it occupied or empty

• has the Volser just been mounted on a drive

2-4 6-00440-02

AMU

• how often has it been used (USECOUNT)

• which robots have access right (COWNER)

• type of media that can be stored on this coordinate (MEDIA)

• backup status in case a DUAL-AMU is used (BUDSTATE)

• time of the last change (TIMESTMP)

• status of the medium, e.g. scratch (VTYPE)

• number of uses of the medium/drive for drive cleaning (COUNTER).

The AML database consists of three tables:

• COORDINATES (compartments in the archive)

• SCOORDINATES (drives and I/O unit)

• POOL (scratch media, cleaning media and data for Media Identifier convertion).

The database is automatically accessed with every host command.

Archive Organization

The table COORDINATES can be configured for various applications:

• Hierarchical Archive Organization Volser are assigned to coordinates in increasing order. To allow for this, ranges (Volser ranges) are defined when the database is set up, and the data records are preassigned. A Volser can be stored in the system only if it is within a Volser range and therefore has a home coordinate (home position). Identification is made automatically with the aid of the barcode label on the storage medium.

• Dynamic Archive Organization no fixed assignment of coordinates and Volsers upon setup of the database. Volser are filed in random order in the archive (this type of organization is recommended if the Volsers in the archive change frequently). If a Volser as yet unknown to the system is inserted, it is automatically inserted at the first vacant compartment in the dynamic range. This compartment remains the home position of the Volser until it is ejected from the system with the "Eject Total” option.

• Dynamic Archive Organization with HACC/MVS The host software HACC/MVS runs its own archive.When a new Volser is inserted into the system, the target coordinate (new home position) is assigned by HACC/MVS. This system also differentiates temporary and total ejection.

In one archive several organization principles may be used in combination (e.g. 1st range dynamic, 2nd range hierarchical).

Data Safety

The AMU plays a key roll in the connection between host systems and the robot system. An AMU failure leads to a standstill of the entire robot system.

DUAL AMU

DUAL AMUs are two identical computers for control of ADIC archives (AML/2, AML/E, AML/J with serial PMAC). The AMU computers are connected to the control units of the archives by means of Automatic Data Switch (ADS) via an RS232C connection.

AMU Tasks 2-5

AMU

The ADS is a remote-controlled switch creating the connection between AMU PC and control components. If one AMU fails, a command shifts the switch and processing is resumed by the second AMU.

The two AMU computers are linked by an RS232 interface or a LAN. This connection is used to

• synchronize the databases

• transfer commands (routing function)

• transfer configuration data (command controlled).

For the host systems the DUAL AMU is a single system (not two separate computers). The information on which of the two AMU computers is currently holding the connection to the robot control unit, is irrelevant for the function. Both AMU computers can receive host commands.

The commands are automatically sent to the active AMU and the robot control unit.

Figure 2-2 Functional Principle DUAL AMU

If the AMU (AML Management Unit) fails, the router (RTE) continues to run. In the example (shown in Figure 2-2) there is no change in Host-AMU-communication when AMU fails on AMU A. Only the ADS is switched by the switch command and the router of AMU A sends the host commands to the AMU of AMU B. If AMU A fails entirely, the router is likewise no longer available. In this situation the host-AMU-communication must be changed. Since host 3 in the above example is not connected to AMU B, it would not be able to control the AML system if AMU A fails entirely.

Database Backup

Independent of the DUAL AMU, a constant, current backup of the database can be created: the database backup (Refer to Process Configuration on page 3-19).

You can switch the database backup function on or off with an entry in the configuration file AMUCONF.INI (Refer to Process Configuration on page 3-19).

By means of an entry in the configuration file you can determine where backup and journal files will be saved.

You can write these files

• to a second physical hard disk in the AMU PC

• via the IBM-LAN-Requester to a LAN server (accessory). This would also provide protection from possible disk crashes

2-6 6-00440-02

AMU

NOTE:

The database backup starts once per day: when AMU is idling ("Idle Time”) at a programmable time.

The backup runs as an independent task in the background, that is, while the system operates. All data records in the database are written to an ASCII file in their entirety (complete backup). Additionally, all current changes are protocolled in separate files (journal files).

Since the database backup is created outside the database system, it will remain available for restoration even if the database manager fails.

You can completely restore a database. You must have the following

• backup file

• corresponding journal file

on the AMU operating console in menu Service the command Restore (Refer to Restore on page

3-28). During the restoration, the backup and journal files are checked for integrity.

If a LAN server is used, the function of the network must be guaranteed. A functional defect in the connection to the LAN server can cause a failure of AMU.

Also, after interruption of the connection to a LAN server (e.g. after shutdown of the LAN server) manual intervention for sign-on to the LAN server is required.

Log Function

The activities of the archive software on the AMU computer (AMU, DAS) are recorded in the AMU log.

For each day (beginning at 0.00 hours) a new log file is opened. The log file is written into a defined

directory (preset to: C:\AMU\LOGS-TRC). If the available storage capacity drops below a defined

value (preset to 40 MB), the oldest log files are deleted.

The log files are saved in ASCII format and can be read with any ASCII viewer.

Disaster Recovery Support

After a failure of the entire data processing center (host and disk storage), some media are immediately required from the archive, to be able to continue operating with a spare data processing center (Disaster Recovery). Since the host and therefore the software for control of the AML system is not longer available in this case, the export is controlled by AMU. Refer to Ejection Procedure for Disaster Recovery on page 6-5.

Host Connections

Host connection is made either

• directly by AMU (mainframes)

• or by DAS (Distributed AML Clients).

AMU as Server

In environments with several hosts, AMU operates as a server. It takes over the entire coordination, since several host computers can access the AML system in parallel.

AMU Tasks 2-7

AMU

To enhance fail safety of the system, two AMU computers can be connected to one AML system (DUAL AMU).

The corresponding host software components communicate with AMU via various connections.

Selection and Number of Connections

The connection types available for the respective host type are described in the table below and the diagram in this chapter.

The number of possible parallel host connections to AMU is limited only by the AMU hardware. If the version does not provide what is required, select the next higher hardware version.

The AMU hardware currently employed can be used for systems with up to three physically differing host connections (e.g. Token Ring, and Ethernet Connection).

Host Host Software

IBM - MVS HACC/MVS

IBM - VM/VSE HACC/VM/VSE

Siemens BS2000 ROBAR (BS2000)

IBM - AS400 LMS (M&T Consults)

Tandem TwinATL

UNIX HACC/DAS

DEC HACC/Open VMS

Limitations

In an environment with several hosts the following limitations apply

• one Token Ring connection with n x LU 6.2-connections in parallel

• simultaneous connection of HACC/MVS and HACC/VM:

• HACC/MVS via LU 6.2

• HACC/VM via LU 6.2

• as an option: TCP/IP via Ethernet

• as an option: AML via RS-232-C.

Connecting Options

The following chart provides an overview of the various connecting options.

2-8 6-00440-02

AMU

Figure 2-3 AMU Connecting Options

Access Rights

Access rights to the functions of the AMU software are assigned to different levels.

Access to AMU Operating Console

Three user groups are differentiated:

• supervisor - system technician with full access rights to the system

• administrator - system administrator and task preparation has access to system configuration

• operator - system operator, user of the system, without access to configuration.

Database Access

Authorization for database access is automatically made with the user identification "AMUADMIN.”

AMU Tasks 2-9

AMU

AMU Processes

The software consists of individual programs (processes) running in parallel (multi-tasking). Each process accomplishes a specific task. Additionally, there are various service utilities.

Figure 2-4 AMU Processes

Functions of Processes

The following table lists all functions and processes of AMU.

Abbreviation Name Explanation

Arc Archive

ArcBack Archive-Backup short-term, writes backup file

ART Alerter writes logs and traces

BUD Backup Daemon

Clm Clean Manager monitors cleaning of drives

Con

Dim Dismount Manager monitors drive cleaning

Hoc

2-10 6-00440-02

AMU Operator Console

Host and other Communication

manages and protocols (journaling) archive catalog; SQL database

background process for control of data transfer between DUAL AMUs

operator interface for application, installation and maintenance

process controlling the communication to all external systems (e.g. HACC/MVS, robot control unit of AML/2)

AMU

Abbreviation Name Explanation

KRN-L Kernel-logical

KNP Kernel-physical processing for robot (compute coordinates)

RTE Router

central logic, converts host commands to control commands

set up routing table, passes host commands from passive AMU computer to active AMU computer and back

Service Programs

The following table lists all AMU service programs.

Abbreviation Name Explanation

INI2CONF AMUINI Converter

JustUtil JustUtility

Log2Asc Log to ASCII

PmMaint PMAC Maintenance

converts AMUINI.IN file in AMU version 2.00 to AMUCONF.INI

editor for teach point files for AML/2, AML/J, and AML/E

converts binary coded log file from AMU version

2.4 and earlier to ASCII file

microcode download and diagnosis program for AML/J control unit (PMAC)

patini patini allows editing of binary configuration files

RFM Rho File manager

showini showini

file transfer to rho control when Kernel, HOC and ARC (incl. DB 2/2) have been stopped

displays binary-coded configuration file in ASCII format

AMU Processes 2-11

AMU System Requirements

This section describes the AMU system requirements.

Hardware

Hardware Required level

Processor min. Intel Pentium 350 MHz

AMU

Memory

Hard disk min. one hard disk with 850 MB free space (2 hard disks recommended)

Graphic adapter min. XGA, 1024 x 768

Input device keyboard and mouse / trackball

min. 64 MB RAM (128 MB recommended, required for systems with two or more hosts)

Software

Software Required level

Operating system

Database manager

Communication

OS/2 4.0 with fixpack 15, MPTS 6.0 and TCP/IP 4.31

IBM DATABASE 7.01

TCP/IP 4.31

Compatibility

This AMU version requires the following host and control software versions:

Software Version Comments

AML/2 control unit

AML/E control unit

AML/J control unit 2.40D or higher

DAS 3.12

ROBAR V2.5 or higher V3.02 recommended

HACC/OS400 V2.2 or higher

HACC/MVS 3.0 PTF ZY30015

TwinATL S0308D20 or higher

HACC/VM 1.4.2

2-12 6-00440-02

2.20D or higher Standard gripper

2.30D or higher Parallel gripper

2.20D or higher Standard gripper

2.30C or higher Parallel gripper

older version does not support the DUAL- and CLEAN function

AMU

Operating Console

System operation is identical whether you input commands at the operating console of the AMU or at the host. Each has the same access priority to the system.

CAUTION:

NOTE:

Especially when using the commands Put, Get, Look, and Teach, be sure to prevent conflicts with host commands. If in doubt, restart the AMU after using any of these commands.

After any change of the configuration, you must restart the AMU (AMU and DAS).

Input at the AMU must be restricted to the following situations:

• host communication failure

• robot failure (manual update of the archive catalog after manual interventions (Refer to Operator Guide)

• during installation

• during maintenance

All non-executable commands or options are displayed with a shadow.

3-1

Application

Design and application conforms to the SAA standard.

It it operated with

• the keyboard

• the mouse

Further information can be found in the OS/2 manuals.

Design of the Menu Bar

Figure 3-1 AMU Menu Bar

AMU

NOTE:

The following functions are the same in all windows:

Button Function

Cancel Cancels the current function and closes the window.

Help Opens online help.

In the active window the title bar background is dark; in inactive windows the title bar´s background is light.

System menu field

Figure 3-2 System Menu Field of AMU

Selecting a Command

With the mouse

3-2 6-00440-02

AMU

1. Move the mouse pointer to the desired menu in the menu bar.

2. Click on the menu; the menu opens.

3. Click on the command in the menu; the command window opens.

With the keyboard

1. Press the <ALT> key and the underlined letter in the menu bar. The menu opens.

2. Now press the underlined letter in the menu to select the command.

With a command code

1. If a key or a combination of keys is specified following the command you can directly select the command with it.

Altering a Window´s Size

Resizeable windows have a frame all around (e.g. Trace window).

1. Move the mouse to any corner of the active window. The mouse pointer changes into a double arrow.

2. Press the mouse button and pull the window to the desired size while keeping the mouse button pressed.

Moving a Window

1. Move the mouse pointer onto the title bar.

2. Move the window while keeping the mouse button pressed.

Closing a Window

1. Close the window by a double click on the system menu field.

Application 3-3

Overview of Menus

All commands of the AMU operating console are explained here:

Figure 3-3 Overview of Menus of AMU

AMU

NOTE:

When DUAL AMU is used, only the command Switch can be processed by the passive AMU (even the command View Archive Catalog Management is not allowed for the passive AMU). Enter all commands at the active AMU.

Menu Shutdown

Figure 3-4 Menu "Shutdown”

3-4 6-00440-02

+ 244 hidden pages