Quantum AMU 3.10 User Manual
REFERENCE GUIDE
AMU 3.10
AML
MANAGEMENT
UNIT
Order No.DOC E00 024-B
Copyright Notice
© Copyright ADIC 2002
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 within this document are the property of their respective owners.
Copyright Notice (Europe)
© Copyright ADIC Europe 2002
All rig hts reserved. No part of th is document may be copied or repro duced in any form or by any mea ns,
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 and ADIC Europe are trademarks of Advanced Digital Information Corporation.
ADIC ADIC Europe ADIC Germany Beteiligungs GmbH, KG
Tel.: +1 303-705-3900 ZAC des Basses Auges Eschenstraße 3
Fax: +1-303-792-2465 1, rue Alfred de Vigny D-89558 Böhmenkirch, Germany
ATAC: 1-800-827-3822 78112 Fourqueux, France Tel:+00.800.9999.3822
www.adic.com Tel.: +33.1.3087.5300
Fax: +33.1.3087.5301
Published: Jan, 2002
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-266-4000
Table of Content
1 Introduction
1.1 Contents ............................................................................... 1-1
1.2 Target Audience ................................................................... 1-1
1.3 Further Documentation ......................................................... 1-2
1.4 Explanation of Symbols and Notes ....................................... 1-2
1.5 Technical Support ................................................................. 1-3
1.6 Product Observation ............................................................. 1-4
2 Overview of AMU
1.2.1 Structure of the Manual .............................................. 1-1
2.1 Tasks of AMU ....................................................................... 2-3
2.1.1 Command Management ............................................. 2-3
2.1.2 Dismount Management ............................................... 2-3
2.1.3 Clean Management .................................................... 2-4
2.1.4 Import/Export Management ........................................ 2-5
2.1.5 Database .................................................................... 2-6
2.1.6 Data Safety ................................................................. 2-8
2.1.7 Log Function ............................................................. 2-10
2.1.8 Disaster Recovery Support ....................................... 2-10
2.1.9 Host Connections ..................................................... 2-11
2.1.10 Access Rights ......................................................... 2-14
2.2 AMU Processes .................................................................. 2-15
2.3 AMU System Requirements ............................................... 2-17
2.3.1 Hardware .................................................................. 2-17
2.3.2 Software .................................................................... 2-17
2.3.3 Compatibility ............................................................. 2-18
3 For Your Safety
102 DOC E00 024-B Reference Guide Page iii
Table of Content
3.1 Hazard Alert Messages ........................................................ 3-2
3.2 Further Symbols ................................................................... 3-3
3.3 Scope of Application ............................................................. 3-4
4 Operating Console
4.1 Application ............................................................................ 4-1
4.1.1 Design of the Menu Bar ............................................. 4-2
4.1.2 Selecting a Command ................................................ 4-3
4.1.3 Altering a Window´s Size ........................................... 4-4
4.1.4 Moving a Window ....................................................... 4-4
4.1.5 Closing a Window ....................................................... 4-4
4.2 Overview of Menus ............................................................... 4-5
4.3 Menu Shutdown .................................................................... 4-6
4.4 Menu Edit ............................................................................. 4-8
4.5 Menu View ............................................................................ 4-9
4.5.1 Archive ........................................................................ 4-9
4.5.2 Trace ........................................................................ 4-14
4.5.3 Log ........................................................................... 4-17
4.6 Menu Operations ................................................................ 4-20
4.6.1 Login/Logoff (Operator) ............................................ 4-20
4.6.2 Manual Operation ..................................................... 4-21
4.6.3 Disaster Recovery .................................................... 4-24
4.6.4 Insert Clean .............................................................. 4-25
4.6.5 Eject Clean ............................................................... 4-26
4.6.6 Clean Drive .............................................................. 4-27
4.7 Menu Admin ....................................................................... 4-28
4.7.1 Login (Administrator) ................................................ 4-28
4.7.2 Configuration ............................................................ 4-29
4.7.3 Process Configuration .............................................. 4-30
4.7.4 Clean Pool ................................................................ 4-35
4.7.5 Scratch Pool ............................................................. 4-38
Page iv Reference Guide 102 DOC E00 024-B
Table of Content
4.8 Menu Commands ............................................................... 4-42
4.7.6 Create Archive .......................................................... 4-40
4.7.7 Update Devices ........................................................ 4-40
4.7.8 Edit Volser Ranges ................................................... 4-41
4.7.9 Restore ..................................................................... 4-41
4.8.1 Login (Supervisor) .................................................... 4-43
4.8.2 Command String Conventions ................................. 4-45
4.8.3 Command “Mount...” ................................................ 4-46
4.8.4 Command “Keep...” .................................................. 4-47
4.8.5 Command “Move...” .................................................. 4-48
4.8.6 Command “Inventory...” ............................................ 4-50
4.8.7 Command “Close Unit...” .......................................... 4-52
4.8.8 Command “Unload Unit...” ........................................ 4-53
4.8.9 Command “Status...” ................................................ 4-54
4.8.10 Command “Purge...” ............................................... 4-56
4.8.11 Command “Homing...” ............................................ 4-57
4.8.12 Command “Put...” ................................................... 4-58
4.8.13 Command “Get...” ................................................... 4-59
4.8.14 Command “Look...” ................................................. 4-60
4.8.15 Command “Turn...” ................................................. 4-61
4.8.16 Command “Insert Clean...” ..................................... 4-62
4.8.17 Command “Eject Clean...” ...................................... 4-63
4.8.18 Command “Clean Drive...” ...................................... 4-64
4.8.19 Command “Switch” ................................................. 4-65
4.9 Menu Service ...................................................................... 4-66
4.9.1 Login (Supervisor) .................................................... 4-66
4.9.2 Command “Teach singlecommand” ......................... 4-67
4.9.3 Command “Teach MTCGDialog” .............................. 4-69
4.9.4 Dual-AMU Service: File Transfer .............................. 4-71
4.9.5 Dual-AMU Service: Activate this AMU ...................... 4-73
4.9.6 Continuous Send ...................................................... 4-74
4.9.7 Start Testmode ......................................................... 4-77
102 DOC E00 024-B Reference Guide Page v
Table of Content
4.9.8 Stop Alerter .............................................................. 4-78
4.9.9 Rho File Manager ..................................................... 4-78
4.10 Menu Window ..................................................................... 4-79
4.11 Menu Help .......................................................................... 4-80
5 Configuration
5.1 Window “Graphical Configuration” ........................................ 5-1
5.1.1 The Configuration Procedure ..................................... 5-4
5.1.2 Configuration Windows of Components ..................... 5-6
5.2 Configuration Of Volser Numbering .................................... 5-51
5.2.1 Terms ....................................................................... 5-51
5.2.2 Overview ................................................................... 5-51
5.2.3 Window Edit Volser Ranges ..................................... 5-52
5.2.4 Inserting a new volser range .................................... 5-55
5.2.5 Changing an existing volser range ........................... 5-55
5.2.6 Defining a dynamic range ........................................ 5-56
5.2.7 Changing individual archive catalog entries ............. 5-56
5.3 Configuration of the Drive Control Interface ....................... 5-57
5.4 Configuration of Drive Cleaning .......................................... 5-60
5.5 Configuration of Scratch Pools ........................................... 5-61
5.6 Configuration of AMU Log .................................................. 5-62
5.7 Configuration of AMU Start ................................................. 5-63
5.7.1 AMUSTART.CMD .................................................... 5-65
5.8 Symbols on the Operating Console .................................... 5-66
5.9 Archiving Function of the Operating System OS/2 ............. 5-68
5.10 Logic Coordinates ............................................................... 5-69
5.10.1 ABBA/1 Coordinates ............................................... 5-69
5.10.2 Comparison of AMU and ABBA/1 Coordinates ...... 5-69
5.10.3 Structure ................................................................. 5-70
5.10.4 Archive Coordinates ............................................... 5-72
5.10.5 Special Coordinates ............................................... 5-73
Page vi Reference Guide 102 DOC E00 024-B
Table of Content
6 Utilities
6.1 Rho File Manager ................................................................. 6-1
6.2 “JUSTUTIL.EXE” ................................................................ 6-17
6.3 PMMaint .............................................................................. 6-22
6.4 Starting PMMaint ................................................................ 6-22
5.10.6 Status of Coordinates ............................................. 5-76
5.10.7 Coordinates for Scalar 1000 ................................... 5-77
6.1.1 Starting the Rho File Manager ................................... 6-2
6.1.2 Menu File .................................................................... 6-3
6.1.3 Menu Connection ....................................................... 6-4
6.4.1 Menu File .................................................................. 6-23
6.4.2 Menu Installation ....................................................... 6-27
6.4.3 Menu Teach .............................................................. 6-42
6.4.4 Menu Service ............................................................ 6-55
6.5 SCSIUtil .............................................................................. 6-67
6.5.1 Start SCSIUTIL ......................................................... 6-67
6.5.2 Scalar 1000 SCSI Diagnostic Window ..................... 6-69
6.5.3 Menu Commands ..................................................... 6-71
6.6 LOG2ASC ........................................................................... 6-77
6.7 SHOWINI ............................................................................ 6-78
6.8 PATINI ................................................................................ 6-82
7 Procedures
7.1 Switching the AMU Computer On ......................................... 7-1
7.2 Starting the AMU Operating Console ................................... 7-2
7.3 Terminating the AMU Operating Console ............................. 7-3
7.3.1 Switching the AMU Computer Off ............................... 7-3
7.4 Remote Power ON/OFF ....................................................... 7-5
102 DOC E00 024-B Reference Guide Page vii
Table of Content
7.5 Switching Over between the Dual-AMU Computers ............. 7-6
7.5.1 Switch (Switch-Normal) .............................................. 7-6
7.5.2 Switch-Force ............................................................... 7-6
7.6 Disaster Recovery Support ................................................... 7-8
7.6.1 Precondition ................................................................ 7-8
7.6.2 Preparing the Disaster Recovery Support .................. 7-8
7.6.3 Ejection Procedure for Disaster Recovery .................. 7-9
7.7 Installing the AML Management Software .......................... 7-10
8 Useful System Functions
8.1 Useful OS/2 Commands ....................................................... 8-1
8.1.1 Mode Command ......................................................... 8-1
8.1.2 Pstat Command ......................................................... 8-2
8.1.3 Syslevel Command .................................................... 8-3
8.1.4 Restoring the OS/2 System ........................................ 8-4
8.1.5 Saving Files ................................................................ 8-5
8.1.6 Compressing Files ..................................................... 8-6
8.1.7 Decompressing Files .................................................. 8-6
8.2 TCP/IP Commands ............................................................... 8-7
8.2.1 “ping” Command ......................................................... 8-7
8.2.2 Netstat Command ...................................................... 8-8
8.2.3 rpcinfo Command ..................................................... 8-10
8.3 Database Manager DB/2 .................................................... 8-11
8.3.1 Database Destroyed - What to do? .......................... 8-11
8.3.2 Backup of Database ................................................. 8-15
8.3.3 Restoring the Database ............................................ 8-16
8.3.4 Exporting Tables from the Database ........................ 8-17
8.3.5 Query Database ....................................................... 8-18
8.3.6 Assignment of Volsers to Compartments ................. 8-19
Page viii Reference Guide 102 DOC E00 024-B
Table of Content
9Messages
9.1 General Information .............................................................. 9-1
9.2 Error Codes (ABBA/1 Format) .............................................. 9-2
9.3 Messages in AML/2 Format (AMU) ...................................... 9-5
9.3.1 Robot Control System Errors ...................................... 9-5
9.3.2 Logic Errors of the Application Program .................. 9-22
9.3.3 Handling Errors ........................................................ 9-23
9.3.4 Barcode and Teaching Errors .................................. 9-26
9.3.5 Hardware Errorss ..................................................... 9-28
9.3.6 Robot Status Messages ............................................ 9-28
9.3.7 Message Storage Tower .......................................... 9-30
9.3.8 I/O Unit Messages .................................................... 9-33
9.3.9 Automatic Data Switch Messages ............................ 9-36
9.3.10 AMU Information and Error Messages ................... 9-37
10 Appendix
10.1 Terms Used ........................................................................ 10-1
10.2 Trace Levels ....................................................................... 10-4
10.3 Media Types ....................................................................... 10-8
10.4 Component Types ............................................................ 10-10
10.4.1 Drives .................................................................... 10-10
10.4.2 I/O Unit .................................................................. 10-12
10.4.3 Host Computers .................................................... 10-13
10.4.4 Storage Units ........................................................ 10-13
10.4.5 Robots .................................................................. 10-14
10.4.6 AMU ...................................................................... 10-14
10.4.7 Control Units ......................................................... 10-14
10.5 Important Configuration Files ............................................ 10-15
102 DOC E00 024-B Reference Guide Page ix
11 Index
Table of Content
Page x Reference Guide 102 DOC E00 024-B
Introduction
1 Introduction
1.1 Contents
This manual contains information and instructions required to set up and operate
the AML Management Unit (AMU).
1.2 Target Audience
The manual is designed for system administrators; service technicians and users
operating the AMU. Familiarity with the operating system OS/2 is assumed.
1.2.1 Structure of the Manual
The manual contains the following chapters:
Chapter 1
Chapter 2
Chapter 3
Chapter 4
Chapter 5
Chapter 6
Introduction Information concerning use of the manual as well as safety instructions
Overview of AMU Description of the functions of the
AML Management Unit
For Your safety Information concerning safe operation of AMU
Operating Console Explanation of functions of the
AMU operating console (CON)
Configuration Explanation of the configuration features for AMU (AMU and OS/2)
Utilities Utility programmes for diagnosis and installation of AML Systems
102 DOC E00 024-B Reference Guide Page 1 - 1
Further Documentation
Chapter 7
Procedures Description of important procedures
(start, software update etc.)
Chapter 8
Useful System Functions Information on OS/2 operating system, database manager and TCP/IP functions in connection with AMU
Chapter 9
Appendix
Messages Log messages of AMU
glossary, trace levels, media and device types
1.3 Further Documentation
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
1.4 Explanation of Symbols and Notes
The following symbols and notes call attention to important information.
A detailed explanation of these symbols is found in QVW.
<1>+<2> press keys simultaneously
italic headline, e.g. chapter 3, Safety
filename, e.g. amuconf.ini
variable, e.g.client_name
Chicago
bold special term, e. g. Scratch-Pool
courier
term appearing on the operating console of AMU
line or term appearing in an input window
- programme message
- command
- parameter or file
Page 1 - 2 Reference Guide 102
DOC E00 024-B
Technical Support
[courier]
Param1 | Param2
(dism)
☞
optional parameter
alternative parameter
abbreviated command
cross reference
1.5 Technical Support
If you cannot solve a problem with the aid of this document or if you are interested in a recommendation regarding training, please contact your contract
partner or the ADIC Technical Assistance Center (ATAC).
ADIC Germany Beteiligungs GmbH, KG ADIC
Eschenstrasse 3 8560 Upland Drive
89558 Boehmenkirch Parker, CO 80134
Germany U.S.A.
We would be pleased to help you further.
Telefax: +49 (0) 6196-59 08 69
Email: techsup@adic.com
Telephone: 1 800 827 3822 North America
+49 6142 992364 Germany
00800 9999 3822 (the rest of the world)
102 DOC E00 024-B Reference Guide Page 1 - 3
1.6 Product Observation
We are obliged by law to monitor our products even after delivery to the customer.Therefore please communicate every point of interest.
• modified set-up data
• experience with the product
• repetitive faults
• difficulties with this manual
Product Observation
ADIC Germany Beteiligungs GmbH, KG ADIC
Eschenstrasse 3 8560 Upland Drive
89558 Boehmenkirch Englewood, CO 80112
Germany U.S.A.
Telefax: +49 (0) 6196-59 08 69
Email: techsup@adic.com
Telephone: 1 800 827 3822 North America
+49 6142 992364 Germany
00800 9999 3822 (the rest of the world)
Page 1 - 4 Reference Guide 102
DOC E00 024-B
Overview of AMU
2 Overview of AMU
AMU
DAS Clients
TCP/IP
Distributed AML Server
DAS
Mainframe
AML System
AML Management Unit
AMU
OS/2
Fig. 2-1: AMU in a Multi-Host Environment
102 DOC E00 024-B Reference Guide Page 2 - 1
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 programmes are running
- AML Management Software (AMU) and
- 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
•AML/E
•AML/J
• Scalar 1000
Information
In den following chapters the AML Management Unit (AMU) described.
Information on DAS is found in following manuals:
• DAS Administration Guide
• DAS Interfacing Guide
Page 2 - 2 Reference Guide 102
DOC E00 024-B
Tasks of AMU
2.1 Tasks of AMU
2.1.1 Command Management
AMU accepts commands incoming via various interfaces:
• host interfaces
• graphic operating console on AMU processor (☞ Page 4-1)
The commands are either processed immediately and acknowledged (e.g. database
querries) or entered on a command queue according to priority. The software can
enter up to 50 commands on the command queue. All important events related to
these commands are recorded in a log file.
With AMU 3.00 can be mounted also not "Foreign Cartridges" from the I/O unit.
But the user make sure, that this compartment are still empty for the Keep
(Dismount)
2.1.2 Dismount Management
Dismounting includes:
• the unload command to the drive
• the process inside the drive preparing the unloading (e. g. rewinding on 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 take up a differing amount of time depending on the type of
drive. With the aid of the Dismount Manager these procedures can be adapted to
the different drive types, and be controlled even if there are time differences for
dismounting by the robots.(☞ “Drive” on page 5 - 22)
For DLT-Low-Profile-drives operation is precondition the Drive Control Interface
(DCI). This direct drive interface to the AMU prevent not necessary dismount
actions and a drive controlled cleaning.
102 DOC E00 024-B Reference Guide Page 2 - 3
2.1.3 Clean Management
In an AML some drives may require cleaning. The following modes are
differentiated:
• drive is cyclically cleansed manually
• drive is cyclically cleansed automatically using a cleaning medium
• drive is cleansed manually as needed
• drive is cleansed automatically as needed
To determine the cleaning mode required for your drive turn 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.
Tasks of AMU
Information
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
preferrably.
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 cleanpool.
The cleanpool is the amount of cleaning media of a certain type, and each medium
in the cleanpool has a barcode label. Parameters required are assigned the
cleanpool, such as maximum number of uses of the medium and minimum number
of cleaning media required.
The cleanpool is filled by special insert commands for cleaning media. The
application receives a message when the number of available cleaning media drops
below the minium 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.
DLT-LowProfile drives sends the clean request via DCI to the AMU, so that the
Clean Manager clean the drive only in the right situation.
Page 2 - 4 Reference Guide 102
DOC E00 024-B
Tasks of AMU
2.1.4 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 with stopping the robot (I/O unit/D -HICAP AML/J)
and according to the type of host connection for import and export:
• host-controlled
• AMU-controlled
Host-Controlled
The operator request the I/O unit by pressing a push-button and thereby makes it
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
The operator request the I/O unit by pressing a push-button and thereby makes it
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.
102 DOC E00 024-B Reference Guide Page 2 - 5
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 therein do not require a barcode label
for identification. The assignment is made via the compartments and virtual volsers
(e.g.*FR001).
2.1.5 Database
The information on compartments in the archive and the media in the archive is
save in a relational database. Such information includes
• serial number of the medium represented by a barcode (VOLSER),
• kind of coordinate (CTYPE), e.g., can a cleaning or data medium be stored on
this coordinate,
• qualities of the coordinate (CATTR),
- is it occupied or empty,
- has the Volser just been mounted on a drive,
• 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.e. scratch (VTYPE),
• number of uses of the medium/drive for drive cleaning (COUNTER).
Tasks of AMU
The AML database consists of three tables:
• COORDINATES (compartments in the archive),
• SCOORDINATES (drives and I/O unit) and
• POOL (scratch and cleaning media).
The database is automatically accessed with every host command.
Page 2 - 6 Reference Guide 102
DOC E00 024-B
Tasks of AMU
Archive Organization
The table COORDINATES can be configurated for various applications:
• Hierarchical Archive Organization
Volser are assigned to coordinates in rising order. To allow for this, ranges
(Volser ranges) are defined when the database is set up, and the data records are
preassigned to these.
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 Vosers in the archive change frequently).
If a Volser as yet unknown to the system is to be 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).
102 DOC E00 024-B Reference Guide Page 2 - 7
2.1.6 Data Safety
The AMU plays a key roll in the connection of host systems and robot system.
An AMU failure leads to a standstill of the entire robot system.
Dual AMU
Tasks of AMU
Host 1 Host 4Host 3Host 2
RTE
AMU
AMU A AMU B
ADS
Robot Control System
Fig. 2-2: Functional Principle Dual AMU
Host 5
RTE
AMU
Dual AMUs are two identical computers for control of ADIC archives (AML/2 and
AML/E). The AMU computers are connected to the control units of the archives by
means of Automatic Data Switch (ADS) via an RS232C connection.
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.
Page 2 - 8 Reference Guide 102
DOC E00 024-B
Tasks of 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
(☞
You can switch the database backup function on or off with an entry in the
configuration file AMUCONF.INI (☞ “Process Configuration” from page 4-30).
Process Configuration
Database Backup
or
).
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 harddisk in the AMU PC,
• via the IBM-LAN-Requester to a LAN server (accessory). This would also
provide protection from possible disk crashes.
Information
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.
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
entirity (complete backup). Additionally, all current changes are protocolled in
separate files (journal files).
102 DOC E00 024-B Reference Guide Page 2 - 9
Tasks of AMU
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. To do that the following is required
• backup file,
• corresponding journal file and
on the AMU operating console in menu
(
☞Page 4-41).
During the restoration, the backup and journal files are checked for integrity.
2.1.7 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.
Information
Log files up to version 2.40J are saved in binary format and must be converted
for reading. You can detect this on the 3 letters LOG in the filename for
binary, instead of LO for the ASCII-File.
Service
the command
Restore
2.1.8 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
(☞ “Ejection Procedure for Disaster Recovery” from page 7-9).
Page 2 - 10 Reference Guide 102
DOC E00 024-B
Tasks of AMU
2.1.9 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.
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 can be extracted from
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, Ethernet and 3270Connection).
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
102 DOC E00 024-B Reference Guide Page 2 - 11
Tasks of AMU
Limitations
In an environment with several hosts the following limitations apply
• 1 coaxial connection (EXCP / LU 2) per AMU,
• 1 Token Ring connection with n x LU 6.2- and 1 coaxial connection in parallel,
• simultaneous connection of HACC/MVS and HACC/VM:
- HACC/MVS via LU 6.2,
- HACC/VM via EXCP/LU 2,
• always additionally possible is: TCP/IP via Ethernet,
• always additionally possible is: AML via RS-232-C.
Connecting Options
The following chart provides an overview of the various connecting options.
Page 2 - 12 Reference Guide 102
DOC E00 024-B
Tasks of AMU
Vo l S e r v
DAS
Clients
VA X
BS2000
Tande m
Tandem
AS/400
OS/400
HACC/MVS
VMS
Trob-
HACC/
HACC/
Guardian
Guardia
Restore
Backup/
DAS
MAN
(SINIX)
ROBAR
n
Kernel
NonStop-
HACC/
SNA
(VTAM)
OS/400
CHANNELCHANNEL
(V24)
RS-232-C
3745
LAN
Ring, ISDN)
(Ethernet, Token
LAN-Adapter
AML TCP/IP
RS-232-C
(In-
X.25
X.25
SDLC
house)
Modem
X.25
(64K)
Modem
(19200K)
ISDN
Modem
SDLC
AMU
LU 6.2
Ring
Toke n
NPSI
Modem
X.25
ISDN
Modem
NCP
SDLC
Modem
TR
NTRI
TR
3174/3274
REMOTE
Ring
Tok en
TR-Adapter
LU 2
SNA
(VTAM)
3174/3274
Koax
(LU 2)
HACC/MVS
HACC/VM/VSE
Non-SNA
102 DOC E00 024-B Reference Guide Page 2 - 13
3174/3274
Koax
(EXCP)
OS/2, CM/2, DB 2/2
EHLLAPI
3270 Connection
2.1.10 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:
Tasks of AMU
supervisor
system technician with full access right to the
system,
administrator
system administrator and task preparation have
access to configuration of the system,
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”.
Page 2 - 14 Reference Guide 102
DOC E00 024-B
AMU Processes
2.2 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.
DIM
CLM
BUD
DB 2/2
HOC
KrnL
ARC
ART
CFG-Server
KnP
RTE
CON
RFM
PMMaint
ARCBACK
AMUCONF
AMUCONST
Logs
Traces
DB Backup
Fig. 2-3: AMU Processes
102 DOC E00 024-B Reference Guide Page 2 - 15
Functions of Processes
AMU Processes
Abbrevia-
tion
Arc Archive manages and protocols (journaling) archive catalog; SQL
ArcBack Archive-Backup short-term, writes backup file
ART Alerter wirtes logs and traces
BUD Backup Daemon background process for control of data transfer between dual
Clm Clean Manager monitors cleaning of drives
Con AMU Operator
Dim Dismount Manager monitors drive cleaning
Hoc Host and other
KRN-L (Kernel-logical central logic, converts host commands to control commands
KNP Kernel-physical processing for robot (compute coordinates)
RTE Router set up routing table,
Name Explanation
database
AMUs
operator surface for application, installation and maintenance
Console
process controlling the communication to all external systems
Communication
(e.g. HACC/MVS, robot control unit of AML/2)
passes on host commands from passive AMU computer to
active AMU computer and back
Service Programs
Abbrevia-
tion
INI2CONF AMUINI Converter converts AMUINI.IN file in AMU version 2.00 to
JustUtil JustUtility editor for teach point files for AML/2 and AML/E
Log2Asc Log to ASCII converts binary coded log file from AMU version 2.4 and
PmMaint PMAC
patini patini allows to edit binary configuration files
RFM Rho File manager file transer to rho control when Kernel, HOC and ARC (incl.
showini showini displays binary-coded configuration file in ASCII format
Page 2 - 16 Reference Guide 102
Name Explanation
AMUCONF.INI
earlier to ASCII file
microcode download and diagnosys program for AML/J control
Maintenance
unit (PMAC)
DB 2/2) have been stopped
DOC E00 024-B
Loading...