 *4D     *4E  *2D   	Acorn Software, Inc.	         	Acorn Software, Inc.                                   1	         1            ,  		                                        1  	                        I  1	Acorn Software, Inc.	                             Branches User Guide        :  Branches User Guide	Acorn Software, Inc.	               1            M  Branches User Guide 	Acorn Software, Inc.	                                 1                         I  1	Acorn Software, Inc.	                             Branches User Guide          Branches User Guide	Acorn Software, Inc.                                                                                         1             5  Branches User Guide	Acorn Software, Inc.	          1                         I  1	Acorn Software, Inc.	                             Branches User Guide        7  Branches User Guide 	Acorn Software, Inc.	           1             7  Branches User Guide	Acorn Software, Inc.	            1                         I  1	Acorn Software, Inc.	                             Branches User Guide        9  Branches User Guide 	Acorn Software, Inc.	             1             7  Branches User Guide 	Acorn Software, Inc.	           1                         I  1	Acorn Software, Inc.	                             Branches User Guide        9  Branches User Guide 	Acorn Software, Inc.	             1             1  Branches User Guide	Acorn Software, Inc.	 	    1                         I  1	Acorn Software, Inc.	                             Branches User Guide        9  Branches User Guide 	Acorn Software, Inc.	             1             3  Branches User Guide	Acorn Software, Inc.	   	    1                         I  1	Acorn Software, Inc.	                             Branches User Guide        9  Branches User Guide 	Acorn Software, Inc.	             1             3  Branches User Guide	Acorn Software, Inc.	   	    1                         I  1	Acorn Software, Inc.	                             Branches User Guide        9  Branches User Guide 	Acorn Software, Inc.	             1             8  Branches User Guide	Acorn Software, Inc.	             1                        I  1	Acorn Software, Inc.	                             Branches User Guide        9  Branches User Guide 	Acorn Software, Inc.	             1             8  Branches User Guide	Acorn Software, Inc.	             1                        I  1	Acorn Software, Inc.	                             Branches User Guide        U  Branches User Guide 	Acorn Software, Inc.                            	             1             7  Branches User Guide	Acorn Software, Inc.	            1                         I  1	Acorn Software, Inc.	                             Branches User Guide        U  Branches User Guide 	Acorn Software, Inc.                            	             1             7  Branches User Guide	Acorn Software, Inc.	            1                   I  1	Acorn Software, Inc.	                             Branches User Guide        U  Branches User Guide 	Acorn Software, Inc.                            	             1             3  Branches  User Guide	               	            1           *2E  *4D      Branchestm   User Guide                                               *4E  *2D                   *2E  *2I  *4D     *4E  *2E  *4D   Acorn Software, Inc.  *4E  *2D '  Software Solutions for Storage Systems 
  Marlboro, MA  *2E  *2I  *4D   storage in a nutshell  Hudson, MA  *4E  *2E  *4D                                   *4E  *2D     *2E  *4D   Document Version:	2.2-3 *4E  *2D 2  Revision Information:	This manual supersedes all %  	previous versions of documentation.   Software Version:	2.7A  *2E  *2I  *4D V  Revision Information:	This manual supersedes all 	previous versions of documentation. *4E  *3D   Software Version:	2.8 *3E  *3I  *4D   Software Version:	2.8-1 *4E  *3E  *2E  *4D 7  Operating System and Version:	VMS version 5.4 or later        *4E  *2D ,  Copyright  1992-1995, Acorn Software, Inc. *2E  *2I  *4D ,  Copyright  1992-1996, Acorn Software, Inc. *4E  *2E  *4D   All rights reserved *4E  *2D   .F  Information in this document is subject to change without notice and G  does not constitute a commitment on the part of Acorn Software, Inc.   J  The software described herein is provided subject to a license agreement G  and the descriptions may include proprietary information belonging to  C  Acorn Software, Inc.  No part of this manual may be reproduced in  D  whole or in part by any means, including electronic means, without G  specific written permission from Acorn Software, Inc. or as part of a  C  specified permission contained within a specific software license  G  agreement.  The associated software may not be redistributed, copied,  I  or reproduced in any form except for specified user backup as described  #  in the software license agreement. C  Branches, VIRTUALBranches, the Acorn Software logo and Squash are  $  trademarks of Acorn Software, Inc. E  All other trademarks or registered trademarks are the properties of     their respective manufacturers. *2E  *2I  *4D        / Information in this document is subject to change without notice and does not constitute a commitment on the part of Acorn Software, Inc.  The software described herein is provided subject to a license agreement and the descriptions may include pro /prietary information belonging to Acorn Software, Inc.  No part of this manual may be reproduced in whole or in part by any means, including electronic means, without specific written permission from Acorn Software, Inc. or as part of a specified pe -rmission contained within a specific software license agreement.  The associated software may not be redistributed, copied, or reproduced in any form except for specified user backup as described in the software license agreement. y  Branches, VIRTUALBranches, the Acorn Software logo, HSManager, MODISK and Squash are trademarks of Acorn Software, Inc.  d  All other trademarks or registered trademarks are the properties of their respective manufacturers. *4E  *2E  *4D                                 Printed on recyclable paper.      Table of Contents *4E  *2D 
  Preface	v     Chapter 1, Introduction	1  Features	1   System Prerequisites	2   Branches Supported Devices	2    ,  Chapter 2, Introduction to Data Libraries	5  Introduction	5   Concepts and definitions	5 $  Using Branches and Data Libraries	61  Creating and initializing your inventory table	6 ,  Importing media into your inventory table	6  Examples	7    +  Chapter 3, Installing and Using Branches	9    Where and how to get Branches	94  Connect the data library hardware  to the system	10!  VAXStation 3100 Configuration	10 '  Digital 3000-300L AXP Configuration	11 2  Setting up your system for installing Branches	12  Set System Parameters	12 #  Installing Branches (VMSINSTAL)	13 #  Example of Typical Installation	13   Configuring Branches	15=  Example of Configuring Branches to support an Exabyte 210	18   Starting Branches	19   Licensing Branches	19  Set Startup Sequence	20  Using Branches	21  Updating Branches	21    *  Chapter 4, Branches System Information	23  System Startup	23  System Shutdown	23 &  System Variables and Logical Names	23      Chapter 5, Branches Commands	25  Branches Dismount	26   Branches Export	27   Branches Import	28   Branches Initialize	29   Branches License	30  Branches Load	31   Branches Mount	32  DCL Mount/SYS$MOUNT	33   Branches Set Drive	34  Branches Set Position	35   Branches Set Slot	36   Branches Set Trace	37  Branches Show Contents	38  Branches Show Version	39   Branches Shutdown	40   Branches Tune	41   Branches Unload	42    .  Chapter 6, Third Party Product Integration	43  Using Branches and Backup	43   Sequential Disk Saves	43   Sequential Disk Restores	43  Multi-volumeTape Saves	44  Multi-volume Tape Restores	45  Using Branches and Qfile	45  Using Branches and TapeSys	45   Using Branches and Hierarchy	45  Using Branches and SLS	46   Using Branches and HyperTape	46   -  Chapter 7, Application and Hardware Notes	47   OpenVMS/AXP	47   OpenVMS/AXP 6.1	47 /  Writing programs to integrate with Branches	47   IDE Model  Library Systems	48*  IDE Model 7100 Personal Library System	48%  Kodak Model  560E Library Systems	49 !  NKK Model 556 Library Systems	49   Olympus Deltis OLS-10	49    QualStar Q7 DLT Tape Library	49!  Other Hardware Configurations	50 #  CMD Technology SCSI Controllers	50   Tape Data Libraries	50   Optical Data Libraries	51   >  Chapter 8, Branches Error Messages and Recovery Techniques	53   )  Branches License and Key Request Form	59 <  Example of a blank key request form for the node, QUICK.	59+  Example of a completed key request form	61 -  Send the completed form via the Internet.	62 7  Send the completed form via  a FAX or postal system	62    !  Acorn Software Problem Report	63   Contact us by Internet	64,  Contact us by the carrier of your choice	64   &  Appendix A, The Configuration File	659  Definitions of entries in Branches Configuration File	65  *2E  *2I  *4D 	  Preface	   Chapter 1, Introduction	 
  Features	  System Prerequisites	  Branches Supported Devices	+  Chapter 2, Introduction to Data Libraries	   Introduction	  Concepts and definitions	#  Using Branches and Data Libraries	 0  Creating and initializing your inventory table	+  Importing media into your inventory table	 
  Examples	*  Chapter 3, Installing and Using Branches	   Where and how to get Branches;	2  Connect the data library hardware  to the system	   VAXStation 3100 Configuration;	&  Digital 3000-300L AXP Configuration;	0  Setting up your system for installing Branches	  Set System Parameters	 !  Installing Branches (VMSINSTAL)	 !  Example of Typical Installation	   Configuring Branches	;  Example of Configuring Branches to support an Exabyte 210	   Starting Branches	   Licensing Branches	  Set Startup Sequence	  Using Branches	  Updating Branches	 (  Chapter 4, Branches System Information	  System Startup	  System Shutdown	 $  System Variables and Logical Names	  Chapter 5, Branches Commands	  Branches Dismount	   Branches Export	r  Branches Import	   Branches Initialize	e  Branches License	  Branches Load	r  Branches Mount	  DCL Mount/SYS$MOUNT	   Branches Set Drive	  Branches Set Position	   Branches Set Slot	   Branches Set Trace	  Branches Show Contents	  Branches Show Version	f  Branches Shutdown	   Branches Tune	   Branches Unload	e  Chapter 6 Trouble Shooting	  Problems Getting Started	   Problems After Getting Started	  Advanced Trouble Shooting	 #  Running Branches AXP 2000 systems	   Inventory table corruption	  Hardware Problems	 -  Chapter 6, Third Party Product Integration;	S  Using Branches and Backup	   Sequential Disk Saves;	  Sequential Disk Restores	  Multi-volumeTape Saves	  Multi-volume Tape Restores	 *4E  *3Da  Using Branches and BACPLUS	 *3Ec *3I  *4D   Using Branches and SYSWARE	 *4E  *3EA *4DS  Using Branches and TapeSys	  Using Branches and Hierarchy	  Using Branches and SLS	  Using Branches and HyperTape	+  Chapter 8, Application and Hardware Notes	G:  AXP 150 processors with Adaptec AHA1742 SCSI Controllers	
  OpenVMS/AXP	1  OpenVMS/AXP 6.1	c-  Writing programs to integrate with Branches	i  IDE Model  Library Systems	(  IDE Model 7100 Personal Library System	#  Kodak Model  560E Library Systems	e  NKK Model 556 Library Systems	   Olympus Deltis OLS-10	   QualStar Q7 DLT Tape Library	+  Spectralogic 4000 and 6000 Data Libraries	 
  Exabyte 10e	c  Other Hardware Configurations	n"  CMD Technology SCSI Controllers;	  Tape Data Libraries;	  Optical Data Libraries;	 [  Chapter 9, Branches Error Messages                                and Recovery Techniques	e'  Branches License and Key Request Form	i:  Example of a blank key request form for the node, QUICK.	)  Example of a completed key request form		C  Send the completed form to us at Acorn Software via the Internet.	 M  Send the completed form to us at Acorn Software via  a FAX or postal system	r  Acorn Software Problem Report	   Contact us by Internet	*  Contact us by the carrier of your choice	$  Appendix A, The Configuration File	7  Definitions of entries in Branches Configuration File	e  Customer Service Policy	a *4E  *2EG *4D	  r *4Et *2D   Customer Service Policy	69  *2E  *4Da  e  s *4Ei *2Do
  .c1.Preface;c *2E  *2I  *4D   Preface *4E  *2E  *4D     *4Eo *2DfM  March 1995   --  Welcome to Acorn Softwares Branches documentation.  We at eK  Acorn are happy to add you to our group of users world wide who enjoy the  2  advantages of data library management software.   *2Ec *2I  *4D   November 1995   --  Welcome to Acorn Software's Branches documentation.  We at Acorn are happy to add you to our group of users world wide who enjoy the advantages of data library management software.    *4E  *2E  *4D :  In this preface, you will find the following information:.  	what information our documentation contains!  	who this manual is written fore  	what conventions we usedc  Documentation set contentse *4E. *2D R  Our documentation set consists of one book with two distinct sections:  the user S  guide and the release notes.  The user guide contains information on installation  M  and use; the release notes contains information specific to each release of    Branches.  L  Although we will keep you  informed on new product features by reoccurring Q  mailings, you are welcome to take a copy of our documentation at any time  from sJ  the Internet.  These documents and all other Acorn Software products are 4  accessible via FTP, Gopher, and the World Wide Web:4  	ftp://ftp.acornsw.com/uucp_public/acorn.branches/  	gopher://gopher.acornsw.com/n  	http://www.acornsw.com/ *2Ee *2I: *4D  / Our documentation set consists of one book with two distinct sections:  the user guide and the release notes.  The user guide contains information on installation and use; the release notes contains information specific to each release of Branches. -  4 / Although we will keep you  informed on new product features by reoccurring mailings, you are welcome to take a copy of our documentation at any time  from the Internet.  These documents and all other Acorn Software products are accessible via FTP,   -Gopher, and the World Wide Web:e  	ftp://ftp.acornsw.com/uucp_public/acorn.branches/ftp://ftp.acornsw.com/uucp_public/acorn.branches/b;  	gopher://gopher.acornsw.com/gopher://gopher.acornsw.com/d1  	http://www.acornsw.com/http://www.acornsw.com/f *4E, *2E  *4Da	  Audiencem *4E  *2DeC  We have written our documents with the experienced VAX/VMS system cI  manager and application developer in mind; if you are that reader, skip  O  Chapters 1, and 2, and go on to Chapter 3, Installing and Using Branches.  We eN  have relied upon your knowledge and experience as well as your access to the !  complete VMS documentation set.  N  If you are new to a data library management system,  we have written Chapter L  2, Introduction to Data Libraries with you in mind.  Your comments on this J  chapter, and in fact, the entire book are always welcome.  In Chapter 3, N  Installing and Using Branches. we have included several sections of examples H  in the installation chapter as an introduction that may prove useful.  P  If you are an application developer, be sure to see Chapter 4, Branches System K  Information, Chapter 6, Branches and Backup,  and Chapter 7,  Application o  and Hardware Notes.  M  Should you experience problems, our error messages chapter contains helpful  N  information for resolution of problems or difficulties.  If you have further N  questions, we will be happy to address them.  Feel free to contact us on the   Internet at info@acornsw.com. *2Es *2Ii *4Dt / We have written our documents with the experienced VAX/VMS system manager and application developer in mind; if you are that reader, skip Chapters 1, and 2, and go on to Chapter 3, Installing and Using Branches.  We have relied upon your knowledge N -and experience as well as your access to the complete VMS documentation set.  / If you are new to a data library management system,  we have written Chapter 2, Introduction to Data Libraries with you in mind.  Your comments on this chapter, and in fact, the entire book are always welcome.  In Chapter 3, Installing and Using Br~ -anches. we have included several sections of examples in the installation chapter as an introduction that may prove useful.    If you are an application developer, be sure to see Chapter 4, Branches System Information, Chapter 6, Branches and Backup,  and Chapter 7,  Application and Hardware Notes.  e / Should you experience problems, our error messages chapter contains helpful information for resolution of problems or difficulties.  If you have further questions, we will be happy to address them.  Feel free to contact us on the Internet at info@a -cornsw.com. *4Eg *2Ec *4D2  Conventions-  Our documentation follows these conventions:)  Character		Convention *4Et *2DiM  italics		indicates optional items that you substitute the specific names or n'  			numbers in Branches or DCL commands N  courier, roman	indicates Branches or DCL commands and any examples of either /  			Branches licensing or program documentationoL  shaded note	indicates that we ask you to pay  very strict attention to the +  			information contained in the gray area.a  	 *2EB *2Ie *4Dm8  italics			indicates optional items that you substitute /  				the specific names or numbers in Branches c  				or DCL commands<  courier, roman		indicates Branches or DCL commands and any .  				examples of either Branches licensing or   				program documentation5  shaded note		indicates that we ask you to pay  very  *  				strict attention to the 	information    				contained in the gray area.<  double underline	indicates a hot spot in the HTML versions   			of the documentation.S *4E4 *2ES *4Dt     k *4Eo *2D3  .c. Chapter 1, Introduction;MM  This chapter describes Branches, the Acorn Software data library management  S  and robotic control software for both optical disk jukeboxes and tape stackers in cN  an OpenVMS environment.  Also, in this chapter you will find the particulars L  of our system requirements as well as the devices that Branches supports.  D  Branches provides OpenVMS VAX, MicroVAX, SCSI-based VAXstation and N  VAXServer computers transparent access to data libraries locally or within a I  cluster.  There are no modifications to OpenVMS software needed thereby rN  eliminating the installation of new device drivers or patches on your system.N  Branches, which was written for storage-intensive applications like imaging, L  multimedia and large data base systems, also provides support for the more P  typical and reoccurring operations like file migration, archiving and backup.  L  For instance, with Branches and your own backup procedure, you can achieve O  lights-out backup.  Or, you can use Branches to access and manipulate data in  F  diverse database management systems like Rdb/VMS, Rdb/ELN, DBMS, DSM   and Oracle.  P  Branches supports an extensive array of data libraries from optical disks that C  are either rewritable, WORM, multifunction or CDROM and tape data cP  libraries that are based on DLT, 4 mm, 8 mm, or 3480 technologies.  Please see 0  the table of supported devices in this chapter.  .c1.Features;P  Branches software automates the management of data libraries:  the contents of L  optical disk, magnetic tape and CDROM libraries can be searched, accessed, O  shared and managed with robotic control that is transparent to you.  Branches C  provides these features:d *2E  *2Ie *4De  Chapter 1, Introduction / This chapter describes Branches, the Acorn Software data library management and robotic control software for both optical disk jukeboxes and tape stackers in an OpenVMS environment.  Also, in this chapter you will find the particulars of our system? - requirements as well as the devices that Branches supports.  g / Branches provides OpenVMS VAX, MicroVAX, SCSI-based VAXstation and VAXServer computers transparent access to data libraries locally or within a cluster.  There are no modifications to OpenVMS software needed thereby eliminating the installation of . -new device drivers or patches on your system. / Branches, which was written for storage-intensive applications like imaging, multimedia and large data base systems, also provides support for the more typical and reoccurring operations like file migration, archiving and backup.  For instance, wit -h Branches and your own backup procedure, you can achieve lights-out backup.  Or, you can use Branches to access and manipulate data in diverse database management systems like Rdb/VMS, Rdb/ELN, DBMS, DSM and Oracle.  c / Branches supports an extensive array of data libraries from optical disks that are either rewritable, WORM, multifunction or CDROM and tape data libraries that are based on DLT, 4 mm, 8 mm, or 3480 technologies.  Please see the table of supported d -evices in this chapter.	  FeaturesB / Branches software automates the management of data libraries:  the contents of optical disk, magnetic tape and CDROM libraries can be searched, accessed, shared and managed with robotic control that is transparent to you.  Branches provides these f	 -eatures:	 *4Ee *2EA *4D P  	integrates tapes, optical disks and CDROM with VMS file systems transparentlyH  	installs automatically and easily (VMSINSTAL in less than 30 minutes)@  	assured upward compatibility with software for larger devicesL  	supports multiple data libraries connected to single system or VMSClusterD  	automatic failover for non-stop usage of Branches in VMSClusters.N  	eliminates operator intervention and error in locating and mounting volumesH  	improves data processing efficiency and lowers cost of data storage. 2  	full integration with all OpenVMS applications.N  	performs drive substitution as necessary to fully utilize library hardware.;  	supports bar code readers for all libraries having them.m  	Alpha ready.o *4Ee *2DtN  With Branches, you can add an entry-level library device to your VMS system, O  use your existing software to support these libraries, and upgrade later to a aJ  larger device with no additional software adaptation.  All with a simple -  upgrade to your original license from Acorn.oJ  Use your knowledge of DCL commands and OpenVMS system services to access T  data libraries either locally or on a cluster.  All you need to know is the volume P  name in order to mount and dismount that volume; the software and the robotics "  take the place of the operator.    .c1.System Prerequisites;N  Branches has certain system prerequisites that appear below.  If your system J  does not conform to these requirements, you may experience unpredictable R  results.  We urge you to conform to these requirements for  best performance and S  results.  If your business requirements define other systems, we will be happy to oQ  work with you on those specific models and their use of Branches.  Here are the t  requirements:;  	Operating system 			VMS version 5.4 or later, excluding r'  					versions of OpenVMS/AXP prior to    					V1.5.n+  	Operator's terminal			for OPCOM messagesn *2Ec *2It *4Do / With Branches, you can add an entry-level library device to your VMS system, use your existing software to support these libraries, and upgrade later to a larger device with no additional software adaptation.  All with a simple upgrade to your orig -inal license from Acorn.  / Use your knowledge of DCL commands and OpenVMS system services to access data libraries either locally or on a cluster.  All you need to know is the volume name in order to mount and dismount that volume; the software and the robotics take the plac -e of the operator.  c  System Prerequisitesp / Branches has certain system prerequisites that appear below.  If your system does not conform to these requirements, you may experience unpredictable results.  We urge you to conform to these requirements for  best performance and results.  If your - business requirements define other systems, we will be happy to work with you on those specific models and their use of Branches.  Here are the requirements:i:  	Operating system 		VMS version 5.4 or later, excluding &  				versions of OpenVMS/AXP prior to 
  				V1.5.*  	Operator's terminal		for OPCOM messages *4Ea *2E  *4Dp9  	SYSGEN parameters, DISMOUMSG, GBLPAGES and GBLSECTIONS_ *4Ec *2Dn$  					set prior to starting Branches1  	FTDriver 				must be loaded if DECwindows is 	c%  					running; if DECwindows is not 	t%  					running, then must be started 	c  					manually6  	SCSI interface				CMD Technologies controller with *  					SCSI pass through enabled or VAX or    					AXP with embedded SCSI bus*  	Disk space				100000 blocks to install. *2Et *2I, *4D2#  				set prior to starting Branchesa  	FTDriver 			must be loaded if DECwindows is 					running; if DECwindows is not 					running, then must be started 					manuallyY  	SCSI interface		CMD Technologies controller with 				SCSI pass through enabled or VAX 2#  				or  AXP with embedded SCSI bus )  	Disk space			100000 blocks to install.t *4En *2Ef *4Dt  Exclusions and exceptions *4E. *2DCA  Some optical disk drives may Acorn Softwares MODISK to provide l:  compatibility with the Digital-supplied SCSI disk driver.   .c1.Branches Supported Devices;J  Branches currently supports many different off-the-shelf SCSI-based data P  libraries from companies such as EXABYTE, IDE,  Kodak, Diverse Logistics Inc., 5  Hewlett-Packard and Digital Equipment Corporation.  oH  Optical libraries support includes Rewritable, WORM, Multifunction and L  CDROM; tape libraries support includes 4 mm, 8 mm, DLT and 3480 technology. *2Eh *2It *4Drz  Some optical disk drives may Acorn Software's MODISK to provide compatibility with the Digital-supplied SCSI disk driver.  Branches Supported DevicesS  Branches currently supports many different off-the-shelf SCSI-based data libraries from companies such as EXABYTE, IDE,  Kodak, Diverse Logistics Inc., Hewlett-Packard and Digital Equipment Corporation.     Optical libraries support includes Rewritable, WORM, Multifunction and CDROM; tape libraries support includes 4 mm, 8 mm, DLT and 3480 technology.r *4Ei *2E  *4DL$  Table of Branches Supported Devices *4En *2D P  Use the following chart to note all Branches-supported devices and their model S  numbers.  If you do not see a device that you are interested in knowing about its aN  support, contact Acorn Software at info@acornsw.com, or by FAX, or telephone. *2Ed *2Ip *4De  Use the following chart to note all Branches-supported devices and their model numbers.  If you do not see a device that you are interested in knowing about its support, contact Acorn Software at info@acornsw.com, or by FAX, or telephone.n *4Er *2Es *4Di  	  Branches Supported Devicesq  t  	Optical Disks	Capacities  			Model 	Drives		Cartridgesc  				Nu.	Capacityt *4En *2D   		Digital	10	2	1.2 GB		16   		Digital	20	 2	1.2 GB		32 i  		Digital	60	4	1.2 GB		88   		Digital	100	4	1.2 GB		144 %  		Hewlett-Packard 	10	2	650 MB		16 s'  		Hewlett-Packard 	10LC	1	650 MB		16 r&  		Hewlett-Packard.	20	 2	1.2 GB		32 (  		Hewlett-Packard 	20LT	1	1.2 GB 		16 &  		Hewlett-Packard 	20T	2	1.2 GB		16 &  		Hewlett-Packard 	40T	2	1.2 GB		32 %  		Hewlett-Packard.	60	4	650 MB		88 a&  		Hewlett-Packard.	100	4	650 MB		144'  		Hewlett-Packard.	120T	4	1.2 GB		88 t(  		Hewlett-Packard.	200T	4	1.2 GB		144  *2E	 *2Ic *4Do]  		http://www.storage.digital.com/swrks/catalog/sup_html/pr-opt.htm Digital	10	2	1.2 GB		16 C^  		http://www.storage.digital.com/swrks/catalog/sup_html/pr-opt.htm Digital	20	 2	1.2 GB		32 ]  		http://www.storage.digital.com/swrks/catalog/sup_html/pr-opt.htm Digital	60	4	1.2 GB		88 o^  		http://www.storage.digital.com/swrks/catalog/sup_html/pr-opt.htm Digital	100	4	1.2 GB		144T  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard 	10	2	650 MB		16 V  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard 	10LC	1	650 MB		16 U  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard.	20	 2	1.2 GB		32 wW  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard 	20LT	1	1.2 GB 		16 oU  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard 	20T	2	1.2 GB		16 sU  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard 	40T	2	1.2 GB		32 bT  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard.	60	4	650 MB		88 U  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard.	100	4	650 MB		144yV  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard.	120T	4	1.2 GB		88 W  		http://www.dmo.hp.com/storage/optical/main.htmlHewlett-Packard.	200T	4	1.2 GB		144 n *4Eg *2Ea *4D   		IDE 	LG5TSD	1	1.2 GB		5   		IDE 	7100 PLS	1	1.2 GB		10 c  		IDE 	9000	2	1.2 GB		20 i  		Kodak 	560E	5	1.2 GB		61  		NKK	556	2	650MB		56r(  		Olympus 	Deltis OLS-10	1	1.2 GB		10      	CDROM	Capacities  			Model 	Drive		Max. CDs  				Nu.	Capacityn  		Pioneer	1804x	1 	650 MB		18d *4Es *2Ia *4Dt   		Pioneer	5004x	4 	650 MB		500 *4ES *2Ea *4Da  .  	Magnetic Tapes	Capacitiese  			Model 	Drives		Max.  Tapes  				Nu.	Capacitya *4Ea *2Dt  		ADIC	Autoc.	2	4 mm 		1 *2Eo *2IC *4DaA  		http://www.adic.com/products/1200.htmlADIC	Autoc.	2	4 mm 		128 *4Eh *2Ei *4DP  		Cipher	L7A	2	DLT		7  *4Er *2De#  		Conners	Arc/Pyt 4590	1	4 mm		4; *2Ea *2I  *4Da#  		Conner's	Arc/Pyt 4590	1	4 mm		4ih  		http://www.storage.digital.com/swrks/catalog/inf_html/info_brf/ec_f2629.htmDigital 	DLT2000	1	DLT		7h  		http://www.storage.digital.com/swrks/catalog/inf_html/info_brf/ec_f2629.htmDigital 	DLT2700	1	DLT		7h  		http://www.storage.digital.com/swrks/catalog/inf_html/info_brf/ec_f2629.htmDigital 	DLT4000	1	DLT		7h  		http://www.storage.digital.com/swrks/catalog/inf_html/info_brf/ec_f2629.htmDigital 	DLT4700	1	DLT		7 *4ES *2Er *4Dt  		Digital 	THZ27	1	DLT		7w *4Ei *2De  		Digital 	TL820	3	DLT		180e  		Digital 	TZ85x	1	DLT		7i *2Eh *2Ia *4D e  		http://www.storage.digital.com/swrks/catalog/inf_html/info_prd/t_5tb.htmDigital 	TL820	3	DLT		180t  		Digital	TZ85x	1	DLT		7 *4Ee *2Ea *4Dr  		Digital 	TZ86x	1	DLT		7  *4Ed *2Dt  		EXABYTE	EXB10i	1	8 mm		10   		EXABYTE	EXB10e	1	8 mm		10a  		EXABYTE	EXB60	4	8 mm		60  		EXABYTE	EXB120	4	8 mm		116  		EXABYTE	EXB210	2	8 mm		10t  		EXABYTE	EXB218	2	4 mm		16k  		EXABYTE	EXB440	4	8 mm		40   		EXABYTE	EXB480	4	8 mm		80s *2Eo *2Ir *4Dme  		http://www.storage.digital.com/swrks/catalog/inf_html/info_prd/t_dlt50.htmDigital 	TZ87x	1	DLT		7hU  		http://www.Exabyte.COM:80/Products/Ready_to_Install.htmlEXABYTE	EXB10i	1	8 mm		10nU  		http://www.Exabyte.COM:80/Products/Ready_to_Install.htmlEXABYTE	EXB10e	1	8 mm		10 T  		http://www.Exabyte.COM:80/Products/Ready_to_Install.htmlEXABYTE	EXB60	4	8 mm		60V  		http://www.Exabyte.COM:80/Products/Ready_to_Install.htmlEXABYTE	EXB120	4	8 mm		116U  		http://www.Exabyte.COM:80/Products/Ready_to_Install.htmlEXABYTE	EXB210	2	8 mm		10eU  		http://www.Exabyte.COM:80/Products/Ready_to_Install.htmlEXABYTE	EXB218	2	4 mm		16wU  		http://www.Exabyte.COM:80/Products/Ready_to_Install.htmlEXABYTE	EXB440	4	8 mm		40 U  		http://www.Exabyte.COM:80/Products/Ready_to_Install.htmlEXABYTE	EXB480	4	8 mm		80t *4Eh *2E  *4Dp)  		Diverse Logistics 	DRDAT08,	1	4 mm		8e(  		Diverse Logistics 	LIBRA 8	1	4 mm		8*  		Diverse Logistics 	LIBRA 16	1	4 mm		16 *4Ee *2Da$  		Odetics 	ACL5480	3	3480/3490	180 *2Ea *2I( *4DSK  		http://www.odetics.com/atl/atlhmpg.htmlOdetics 	ACL5480	3	3480/3490	180o *4Eg *2Ev *4D   		QualStar 	Q7	2	DLT		28 *4Ee *2Dn%  		Spectra Logic	STL-6000	2	8 mm		20%  		Spectra Logic	STL-8000	2	8 mm		40o *2En *2Ii *4DCL  		http://www.spectra.wali.com/lib_top.htmSpectra Logic	STL-4000	4	4 mm		60L  		http://www.spectra.wali.com/lib_top.htmSpectra Logic	STL-6000	2	8 mm		20L  		http://www.spectra.wali.com/lib_top.htmSpectra Logic	STL-8000	2	8 mm		40L  		http://www.spectra.wali.com/lib_top.htmSpectra Logic	STL-9000	4	8 mm		60  e *4Ee *2Er *4Dl  a  s  v *4Eh *2D .  .c.Chapter 2, Introduction to Data Libraries;  .c1.Introduction;P  This chapter discusses the basics of data library concepts and definitions and J  how they are used with Branches.  Immediately following the concepts and R  definitions section is a step-by-step illustration and two examples: one with an N  optical library and  mailbox and one with a tape stacker and magazine.  Both L  examples presume that Branches has already been installed on your system.  F  We included these examples as a way to add to your knowledge of data   libraries with Branches.hJ  If you are already familiar with data libraries, please skip to the next   chapter, Installing Branches.  .c1. Concepts and definitions; K  Data libraries are made of hardware and software; they are similar to the sK  library that you may have in your company or town.  There are volumes (of rQ  media containing data), which are stored on shelves (in this case, in a mailbox  N  or magazine) and identified by a specific number or term (here, we have slot H  numbers). Volumes are accessed and read by you.  And, in this analogy, I  Branches is the librarian that guides you to the right book or volume.  'Q  Here is a short tour of a data library as if it were the public library in your    town:Q  	the door or the entrance to the library is, in a data library, a mailbox or a lH  magazine.  Both mailbox and magazine provide the ability to import and K  export the media that contains your data.  The difference between them is nO  --  a mailbox can pass only one piece of media at a time; a magazine can pass t(  more than one piece of media at a time.M  	the library staff, in this analogy, is made up of robots , which move the vM  media.  You can also think of the drives , which read and write data on the sK  media, as part of the staff, since without the m, books and volumes would e  not be shelved.  A  Data libraries can be implemented in many ways, including their cK  addressing schemes.  A robot and a drive may each have one address.  Some mK  libraries take one SCSI ID for each drive and one SCSI ID for each robot, wN  other libraries take a single SCSI ID, but each drive takes one logical unit H  number (LUN).  For example, a tape data library with one drive and one G  magazine has a total of two SCSI IDs or one SCSI ID and two SCSI LUNs.OQ  	the books are the media , either tape or optical cartridge.  They contain the MQ  data and can be read from, and in the case of data library, can be written on.   L  But, in a data library, media can be one or more volumes. -- tapes are one 5  volume; optical cartridges are one or two volumes.  	R  	the card catalog of a public library corresponds to a data library inventory.  8  All the media combined is the data library inventory.  J  In the public library card catalog, you can find a information on a book )  whether or not it is not on the shelf.  	E  However, in a data library, the inventory references only the media 	M  currently inside the data library.  Any media outside of the library cannot eI  be accessed or used.  The inventory table maintains information about a  M  volume:  its position and/or slot and label.  For easy identification, each tK  volume has a position .  A slot and a position is identical only when the  I  media has one volume.  Each volume can have a label  , which may or may SL  not be unique.  For example, scratch tapes can all be labeled SCRTCH (tape P  labels can contain 6 characters; disk labels can contain up to 12 characters). (  .c1. Using Branches and Data Libraries;M  There are six basic steps for using Branches with data libraries.  They are sK  presented in the following section in the order you should perform them.  s4  .c2.Creating and initializing your inventory table; *2Eh *2It *4Dr*  Chapter 2, Introduction to Data Libraries
  Introductionp / This chapter discusses the basics of data library concepts and definitions and how they are used with Branches.  Immediately following the concepts and definitions section is a step-by-step illustration and two examples: one with an optical library - and  mailbox and one with a tape stacker and magazine.  Both examples presume that Branches has already been installed on your system.  We included these examples as a way to add to your knowledge of data libraries with Branches.ng  If you are already familiar with data libraries, please skip to the next chapter, Installing Branches.h  Concepts and definitionso / Data libraries are made of hardware and software; they are similar to the library that you may have in your company or town.  There are volumes (of media containing data), which are stored on shelves (in this case, in a mailbox or magazine) and ide -ntified by a specific number or term (here, we have slot numbers). Volumes are accessed and read by you.  And, in this analogy, Branches is the librarian that guides you to the right book or volume.  iV  Here is a short tour of a data library as if it were the public library in your town: / 	the door or the entrance to the library is, in a data library, a mailbox or a magazine.  Both mailbox and magazine provide the ability to import and export the media that contains your data.  The difference between them is --  a mailbox can pass _ -only one piece of media at a time; a magazine can pass more than one piece of media at a time.l  	the library staff, in this analogy, is made up of robots , which move the media.  You can also think of the drives , which read and write data on the media, as part of the staff, since without the m, books and volumes would not be shelved.   / Data libraries can be implemented in many ways, including their addressing schemes.  A robot and a drive may each have one address.  Some libraries take one SCSI ID for each drive and one SCSI ID for each robot, other libraries take a single SCSI I -D, but each drive takes one logical unit number (LUN).  For example, a tape data library with one drive and one magazine has a total of two SCSI IDs or one SCSI ID and two SCSI LUNs.  / 	the books are the media , either tape or optical cartridge.  They contain the data and can be read from, and in the case of data library, can be written on.  But, in a data library, media can be one or more volumes. -- tapes are one volume; optic( -al cartridges are one or two volumes.    	the card catalog of a public library corresponds to a data library inventory.  All the media combined is the data library inventory.  Br  In the public library card catalog, you can find a information on a book whether or not it is not on the shelf.   / However, in a data library, the inventory references only the media currently inside the data library.  Any media outside of the library cannot be accessed or used.  The inventory table maintains information about a volume:  its position and/or slo /t and label.  For easy identification, each volume has a position .  A slot and a position is identical only when the media has one volume.  Each volume can have a label  , which may or may not be unique.  For example, scratch tapes can all be label` -ed SCRTCH (tape labels can contain 6 characters; disk labels can contain up to 12 characters). #   Using Branches and Data Librariesn  There are six basic steps for using Branches with data libraries.  They are presented in the following section in the order you should perform them.  ./  Creating and initializing your inventory table4 *4E2 *2E4 *4D	L  First step:	  create and initialize your inventory table, then populate it. *4E  *2DaO  The Branches startup procedure creates an inventory table with no entries the cK  very first time that you run Branches.  If, at any time, you need another w9  inventory table, use the command, Initialize/Database.  2 *2ED *2Il *4D2  The Branches startup procedure creates an inventory table with no entries the very first time that you run Branches.  If, at any time, you need another inventory table, use the command, Initialize/Database.  4 *4E	 *2E7 *4DS^  NOTE:  The inventory table must  be created before any other Branches commands are issued.    *4ET *2D1N  After you have created the inventory table and your data library already has J  tapes or disks inserted, use the command, Branches Initialize/Verify, to 2  populate the inventory table with volume labels. /  .c2.Importing media into your inventory table;X *2E	 *2Ie *4Dm  After you have created the inventory table and your data library already has tapes or disks inserted, use the command, Branches Initialize/Verify, to populate the inventory table with volume labels. *  Importing media into your inventory table *4Es *2Ec *4Dg   Second step:  import all media. *4ET *2D1O  All media must be imported into your data library to list it in the inventory 1F  table.  Branches can then track the media within your data library.  R  Although it is handy to label all media, it is not required.  Branches can label J  your media for you when the media is imported.  To import your media and ,  make it ready for use by Branches, use the  *2Et *2Iw *4Da  All media must be imported into your data library to list it in the inventory table.  Branches can then track the media within your data library.    Although it is handy to label all media, it is not required.  Branches can label your media for you when the media is imported.  To import your media and make it ready for use by Branches, use the  *4E	 *2Es *4DiD  	Branches Import command to import media into the inventory table. *4Ei *2D O  If you use the Import/Initialize command, you destroy all data on the media.   Q  All systems routinely use scratch media; including data libraries.  Whether the 0O  media is labeled or not, it can be used as scratch media.  To import media as    scratch, use them *2E *2I	 *4Dr / If you use the Import/Initialize command, you destroy all data on the media.  All systems routinely use scratch media; including data libraries.  Whether the media is labeled or not, it can be used as scratch media.  To import media as scratch, use - thec *4E8 *2E	 *4D	#  	Branches Import/Scratch command.iI  .c2 .Before reading and writing your data to a volume, mount the volume;v0  Third step:  read and write data to the volume. *4Er *2D K  Before you can read or write to a volume, it must be in the drive and the tM  operating system must know about it.  To make the volume ready for use, use gF  	either the SYS$MOUNT system service, the Branches Mount command or   the DCL Mount command.hQ  Branches picks the requested media from its slot, then positions it so that the  3  volume is available, and places it in the drive.  s *2Ed *2Io *4Ds  Before you can read or write to a volume, it must be in the drive and the operating system must know about it.  To make the volume ready for use, use i *4El *4Ds\  	either the SYS$MOUNT system service, the Branches Mount command or the DCL Mount command.  Branches picks the requested media from its slot, then positions it so that the volume is available, and places it in the drive.  l *4E( *2E  *4Da%  .c2 .Loading and unloading a volume;s *4Es *2DtS  Fourth step:  if your data processing requires that a volume be placed in a drive h)  without mounting it, you can do so with a *2Ee *2I  *4Db{  Fourth step:  if your data processing requires that a volume be placed in a drive without mounting it, you can do so with t *4Ef *2Et *4Dr  	Branches Load command.c *4Ea *2D J  You can remove any unmounted media from a drive with the Branches Unload 	  command.l *2Er *2I  *4DzR  You can remove any unmounted media from a drive with the Branches Unload command. *4Et *2Ea *4Do6  .c2 .After reading and writing your data to a volume; *4En *2D I  Fifth step:  after you are finished with the volume, the media must  be e+  dismounted.  To finish the operation, use  F  	either the SYS$DISMOU system service, Branches Dismount command or   the DCL Dismount command   P  Branches removes the media from the drive, orients it properly, and returns it '  to the slot from which it was removed.h *2E. *2ID *4Dis  Fifth step:  after you are finished with the volume, the media must  be dismounted.  To finish the operation, use n`  	either the SYS$DISMOU system service, Branches Dismount command or the DCL Dismount command  v  Branches removes the media from the drive, orients it properly, and returns it to the slot from which it was removed. *4Ea *2Et *4D 1  .c2 .Removing the disk or tape from the library;D  r *4ES *2DDQ  Sixth step (optional):  remove your tapes or disks from the inventory table and .U  place them in external storage, if your data processing  requires.  To do this, use b  the e *2E  *2IB *4Dn  Sixth step (optional):  remove your tapes or disks from the inventory table and place them in external storage, if your data processing  requires.  To do this, use the s *4E  *2Ed *4Di  	Branches Export command.m *4Ec *2De  .c1.Examples;M  These examples presume that you have completed a successful installation of tM  Branches, that you have media in the data library and that you are somewhat  0  versed, but have no in-depth knowledge of VMS. S  If, after a quick scan of the bulleted items below, you are not familiar with one  G  or more of them, you may require more knowledge to be successful with vH  Branches; please consult with your system manager and/or your hardware 1  vendor documentation for tips on how to proceed.  *2Ee *2Il *4D 	  Examples   These examples presume that you have completed a successful installation of Branches, that you have media in the data library and that you are somewhat versed, but have no in-depth knowledge of VMS.  / If, after a quick scan of the bulleted items below, you are not familiar with one or more of them, you may require more knowledge to be successful with Branches; please consult with your system manager and/or your hardware vendor documentation for  -tips on how to proceed. *4El *2E2 *4D2=  .c2 .Example with optical disk data library and one mailbox;t *4E  *2DsI  This example shows BRANCHES working with an optical  disk  data library hM  which has one  mailbox.  Please see the chapter, Branches Commands, for the i%  details on each command shown below.i *2Ed *2Ie *4De  This example shows BRANCHES working with an optical  disk  data library which has one  mailbox.  Please see the chapter, Branches Commands, for the details on each command shown below.  *4El *2E  *4D   BRANCHES INITIALIZE/DATABASE	>  Initializes the inventory table for the default data library.  BRANCHES INITIALIZE/LIBRARY	e/  Initializes the data library hardware for use.n'  BRANCHES IMPORT/INITIALIZE SIDE1,SIDE2  *4Er *2D \  Requests that an optical disk be placed in the mailbox, imports that disk from the mailbox _  into the data library and then, initializes both sides with the labels , SIDE1 and SIDE2, and  -  records these labels in the inventory table.m *2Er *2I  *4D,  Requests that an optical disk be placed in the mailbox, imports that disk from the mailbox into the data library and then, initializes both sides with the labels , SIDE1 and SIDE2, and records these labels in the inventory table. *4Eo *2Ew *4D   MOUNT/SYSTEM $1$DUA21 SIDE2	hW  Places the volume, SIDE2, into the drive,  $1$DUA21, mounts it for system wide access.i  DISMOUNT $1$DUA21	o *4Ed *2DrY  Dismounts the volume in drive $1$DUA21 and returns the disk to its original slot in its    original orientation. *2E  *2Ie *4Dan  Dismounts the volume in drive $1$DUA21 and returns the disk to its original slot in its original orientation. *4E  *2Ec *4De  BRANCHES EXPORT SIDE2 *4En *2Dt^  Removes the volume labels, SIDE1 and SIDE2,  from the inventory table and places the disk in )  the mailbox for removal by the operator.  *2El *2Ii *4Dn  Removes the volume labels, SIDE1 and SIDE2,  from the inventory table and places the disk in the mailbox for removal by the operator. *4ES *2Ef *4Dc8  .c2 .Example with a tape data library and one magazine; *4Es *2D I  This example shows BRANCHES working with a tape  data library  with one eQ  magazine.    The slots are numbered starting at 0 for ease of use.  A tape data rN  library with a magazine containing 10 tapes has slots numbered from 0 to 9.  0  Some Branches commands require a slot number.   *2Ed *2I, *4Di / This example shows BRANCHES working with a tape  data library  with one magazine.    The slots are numbered starting at 0 for ease of use.  A tape data library with a magazine containing 10 tapes has slots numbered from 0 to 9.  Some Branches comma -nds require a slot number.  d *4Eh *2Ea *4Da  BRANCHES INITIALIZE/DATABASE	6  Initializes inventory table for default data library.  BRANCHES INITIALIZE/LIBRARY	 +  Initializes data library hardware for use.h  BRANCHES LOAD/MAGAZINE	 *4E  *2D [  Requests that the magazine, already loaded with tapes and placed within the data library, eL  be made available for use.  BRANCHES will not import the media in magazine. *2Es *2It *4Dl  Requests that the magazine, already loaded with tapes and placed within the data library, be made available for use.  BRANCHES will not import the media in magazine. *4Ea *2Em *4Dt)  BRANCHES IMPORT/INITIALIZE/SLOT=3 MONDAY  *4Ee *2DlZ  Initializes tape in the 4th slot of the magazine.  And assigns label, MONDAY, to volume, $  recording label in inventory table. *2En *2Ie *4De}  Initializes tape in the 4th slot of the magazine.  And assigns label, MONDAY, to volume, recording label in inventory table.e *4E  *2E  *4DC  MOUNT QUICK$MKA0 MONDAY	uK  Places volume labeled, MONDAY,  into the drive, QUICK$MKA0, and mounts it.u  DISMOUNT QUICK$MKA0	 J  Dismounts volume in drive, QUICK$MKA0, and returns tape to original slot.  BRANCHES EXPORT/POSITION=3	 *4Er *2DsU  Removes label, MONDAY, in 4th position of data library from inventory table.  Media sQ  remains in the magazine, but BRANCHES has no knowledge of it. BRANCHES does not c\  restrict use of /POSITION or /SLOT qualifiers.  For data libraries with no mailbox, it may *  require that those qualifiers be present. *2E  *2Ih *4Dm / Removes label, MONDAY, in 4th position of data library from inventory table.  Media remains in the magazine, but BRANCHES has no knowledge of it. BRANCHES does not restrict use of /POSITION or /SLOT qualifiers.  For data libraries with no mailbox, 1 -it may require that those qualifiers be present.f *4E  *2Ep *4D     *4Et *2Da-  .c.Chapter 3, Installing and Using Branches;iP  This chapter contains information on installing Branches with an example of an Q  installation on a VAXstation 3100-based system of an Exabyte 210, a 2 drive, 10  J  cartridge 8mm tape subsystem and the appropriate way to install the same M  subsystem on an Digital 3000-300L AXP.  The subsections appear in the order pN  that you will follow in installing Branches.  We have formatted this chapter K  with additional white space for your convenience in writing notes and any aI  information that may assist you in a speedy and successful installation.iJ  Installing the data library hardware and the BRANCHES software is a four-  stage process:o *2Eu *2Ii *4D )  Chapter 3, Installing and Using Branchesh / This chapter contains information on installing Branches with an example of an installation on a VAXstation 3100-based system of an Exabyte 210, a 2 drive, 10 cartridge 8mm tape subsystem and the appropriate way to install the same subsystem on an  /Digital 3000-300L AXP.  The subsections appear in the order that you will follow in installing Branches.  We have formatted this chapter with additional white space for your convenience in writing notes and any information that may assist you in a s# -peedy and successful installation.eX  Installing the data library hardware and the BRANCHES software is a four-stage process: *4E  *2Ea *4Da3  	Connect the data library hardware to your systemp  	prepare your system!  	run the installation procedurey  	configure Branches. *4Ec *2Dd#  .c1.Where and how to get Branches; N  Branches is shipped to you on a TK50 tape or the medium of your choice.  You J  should have this file:  BRNCHUUVVV.A.  Branches is also available on the I  Internet via anonymous FTP from acornsw.com in UUCP_PUBLIC:[BRANCHES].  dJ  To obtain the files from the Internet via FTP, please follow these steps: *2ET *2Is *4D   Where and how to get Branches;. / Branches is shipped to you on a TK50 tape or the medium of your choice.  You should have this file:  BRNCHUUVVV.A.  Branches is also available on the Internet via anonymous FTP from acornsw.com in UUCP_PUBLIC:[BRANCHES].  To obtain the files from t0 -he Internet via FTP, please follow these steps: *4Er *2Es *4D,  ftp ftp.acornsw.com  user anonymousm  password: your email addressn   cd uucp_public:[acorn.branches]  binaryo,  get *.zip	! for all savesets in a ZIP file."  get unzip.exe	! OpenVMS/VAX UNZIP&  get unzip.exe-axp	! OpenVMS/AXP UNZIP"  mget brnch*.%	! For all savesets.  exit    &  You may also get Branches via Gopher:  	gopher://gopher.acornsw.com/  or the World Wid Web:  	http://www.acornsw.com/s *4E, *2D O  If you are updating your Branches software, please see the following section, (I  Updating your Branches software, for the differences between an initial t  installation and an update.G  Included on the TK50 tape or in the directory noted above is Branches a,  documentation in Microsoft Word 5.0 format:J  	BRNCH.DOC is the Macbinary copy of the file.  This may be moved to any <  Macintosh and converted into a Microsoft Word 5.0 document.P  	BRNCH.RTF is the rich text format version of BRNCH.DOC.  This may be read by A  any version of Microsoft Word that supports importing RTF files.rN  You can print as many copies of this documentation as you want provided that 6  no changes of any kind are made in the documentation.  v6  .c1.Connect the data library hardware  to the system;#  .c2.VAXStation 3100 Configuration;e *2Es *2Ie *4Do  If you are updating your Branches software, please see the following section, Updating your Branches software, for the differences between an initial installation and an update.r  Included on the TK50 tape or in the directory noted above is Branches documentation in Microsoft Word 5.0 format:  	BRNCH.DOC is the Macbinary copy of the file.  This may be moved to any Macintosh and converted into a Microsoft Word 5.0 document.,  	BRNCH.RTF is the rich text format version of BRNCH.DOC.  This may be read by any version of Microsoft Word that supports importing RTF files.  You can print as many copies of this documentation as you want provided that no changes of any kind are made in the documentation.t  a1  Connect the data library hardware  to the systemt  VAXStation 3100 Configuration;a *4Er *2Ei *4Dr(  This requires you to do several things: *4E  *2DeK  Step 1	Determine the SCSI addresses to be used by your data library.  You tL  will have to determine which SCSI addresses are available on your system.    For this example, we selected:s *2E  *2Id *4Di  Step 1	Determine the SCSI addresses to be used by your data library.  You will have to determine which SCSI addresses are available on your system.  For this example, we selected: *4Ea *2Ed *4D '  SCSI ID 0:	Robot for the Exabyte  210.i(  SCSI ID 1:	Drive 0 for the Exabyte 210.(  SCSI ID 2:	Drive 1 for the Exabyte 210.0  Step 2	Connect the data library to your system. *4E  *2DrP  Unless your system specifically allows hot swapping of SCSI devices, it is a O  good idea to shut your system down before connecting the SCSI devices to your dQ  SCSI bus.  If you do shut down your system, take a few minutes after physically  S  connecting your data library to make sure that all the SCSI devices are, in fact,  O  visible to the system.  This example assumes that you are connecting to the B u  bus of your VAXStation 3100.b *2E  *2Ir *4D  / Unless your system specifically allows "hot swapping" of SCSI devices, it is a good idea to shut your system down before connecting the SCSI devices to your SCSI bus.  If you do shut down your system, take a few minutes after physically connecting  -your data library to make sure that all the SCSI devices are, in fact, visible to the system.  This example assumes that you are connecting to the B bus of your VAXStation 3100. *4Eh *2Em *4D,  Step 3	Configure the devices. *4Es *2DbK  OpenVMS/VAX Autoconfigure automatically configures the tape drives in the lI  Exabyte 210 as MUB100 and MUB200 and will not mistake robot devices for hR  other types of devices, so nothing special need be done other than configure the J  robot itself.  The robot is configured by entering SYSGEN and connecting   GKDRIVER to the robot:N *2EI *2IB *4De / OpenVMS/VAX Autoconfigure automatically configures the tape drives in the Exabyte 210 as MUB100 and MUB200 and will not mistake robot devices for other types of devices, so nothing special need be done other than configure the robot itself.  The roK -bot is configured by entering SYSGEN and connecting GKDRIVER to the robot:v *4Ey *2Ee *4D2
  $ MCR SYSGEN   SYSGEN> AUTOCONFIGURE ALL  SYSGEN> AUTOCONFIGURE ALL  SYSGEN> AUTOCONFIGURE ALL.  SYSGEN> CONNECT GKB0:/NOADAPT/DRIVER=GKDRIVER
  SYSGEN> EXITw    *4Ea *2D,N  It is necessary to enter the autoconfigure 3 time in order to guarantee that I  Autoconfigure correctly configures MUB100 and MUB200.  If you shut your rJ  system down to install the hardware, the 3 autoconfigure commands may be 	  omitted.D *2En *2Ie *4Dm  It is necessary to enter the autoconfigure 3 time in order to guarantee that Autoconfigure correctly configures MUB100 and MUB200.  If you shut your system down to install the hardware, the 3 autoconfigure commands may be omitted.2 *4E4 *2EB *4DE  X  Step 4	Edit SYCONFIG.COMmM  To guarantee that the robot is configured appropriately when the VAXStation hG  3100 is rebooted, add the following lines to SYS$MANAGER:SYCONFIG.COM: 
  $ MCR SYSGENl  $ DECKs&  CONNECT GKB0:/NOADAPT/DRIVER=GKDRIVER  EXITd  $ EOD    *4Ei *2D S  If you are running in a cluster environment, you are strongly advised to create a aJ  system specific copy of SYCONFIG.COM before editing.  To create a system &  specific copy of SYCONFIG.COM, simply *2Ez *2I  *4D   If you are running in a cluster environment, you are strongly advised to create a system specific copy of SYCONFIG.COM before editing.  To create a system specific copy of SYCONFIG.COM, simply  *4E  *2E  *4D -  $ COPY SYS$MANAGER:SYCONFIG.COM SYS$MANAGER:p *4Et *2Dr)  .c2.Digital 3000-300L AXP Configuration;mH  Hardware configuration for an AXP differs in detail from configuring a 5  VAXStation 3100.  The overall steps remain the same.mK  Step 1	Determine the SCSI addresses to be used by your data library.  You  L  will have to determine which SCSI addresses are available on your system.    For this example, we selected:I *2El *2Id *4Di%  Digital 3000-300L AXP Configuration;D|  Hardware configuration for an AXP differs in detail from configuring a VAXStation 3100.  The overall steps remain the same.  Step 1	Determine the SCSI addresses to be used by your data library.  You will have to determine which SCSI addresses are available on your system.  For this example, we selected: *4Ea *2Eb *4Dr'  SCSI ID 0:	Robot for the Exabyte  210. (  SCSI ID 1:	Drive 0 for the Exabyte 210.(  SCSI ID 2:	Drive 1 for the Exabyte 210.  Step 2	Edit SYCONFIG.COMe *4Es *2DfP  To guarantee that the robot is configured appropriately when the 3000-300L  is ?  rebooted, add the following lines to SYS$MANAGER:SYCONFIG.COM:f *2Em *2In *4Dn  To guarantee that the robot is configured appropriately when the 3000-300L  is rebooted, add the following lines to SYS$MANAGER:SYCONFIG.COM: *4EY *2Et *4D 
  $ MCR SYSMANA  $ DECKu.  IO CONNECT GKA0:/NOADAPT/DRIVER=SYS$GKDRIVER (  IO AUTOCONFIGURE /DISABLE=(MKA0:,DKA0:)  EXITg  $ EOD    *4EC *2DXS  If you are running in a cluster environment, you are strongly advised to create a  J  system specific copy of SYCONFIG.COM before editing.  To create a system &  specific copy of SYCONFIG.COM, simply *2Er *2Is *4D/  If you are running in a cluster environment, you are strongly advised to create a system specific copy of SYCONFIG.COM before editing.  To create a system specific copy of SYCONFIG.COM, simplyf *4En *2Er *4Dl-  $ COPY SYS$MANAGER:SYCONFIG.COM SYS$MANAGER:    0  Step 3	Connect the data library to your system. *4EP *2DOM  Shut your system down before connecting the SCSI devices to your SCSI bus.  hO  Take a few minutes after physically connecting your data library to make sure ,N  that all the SCSI devices are, in fact, visible to the system.  This example @  assumes that you are connecting to the A bus of your 3000-300L. *2Eb *2Is *4D  / Shut your system down before connecting the SCSI devices to your SCSI bus.  Take a few minutes after physically connecting your data library to make sure that all the SCSI devices are, in fact, visible to the system.  This example assumes that you / -are connecting to the A bus of your 3000-300L.f *4Eu *2Ev *4Dc  Step 3	Reboot the 3000-300L *4Er *2DnG  When SYCONFIG.COM is executed during system startup, the robot device nH  (GKA0:) is configured manually and MUA100 and MUA200 are configured as )  part of the IO AUTOCONFIGURE processing.t *2Eg *2IU *4DB  When SYCONFIG.COM is executed during system startup, the robot device (GKA0:) is configured manually and MUA100 and MUA200 are configured as part of the IO AUTOCONFIGURE processing. *4E  *2Es *4Dn  h *4Er *2Dt4  .c1.Setting up your system for installing Branches;J  The software installation for Branches is identical independent of which %  processor is being used, VAX or AXP.tI  You will need to make just one change to your OpenVMS system before you e*  install Branches:  set system parameters.  .c2.Set System Parameters;n *2Ea *2Ie *4Ds/  Setting up your system for installing BranchesSn  The software installation for Branches is identical independent of which processor is being used, VAX or AXP.r  You will need to make just one change to your OpenVMS system before you install Branches:  set system parameters.  Set System Parameters *4Ei *2Et *4D   aC  If the SYSGEN parameter, DISMOUMSG is not set, follow these steps:e?  Step 1	In the file, SYS$SYSTEM:MODPARAMS.DAT, enter this line:i  DISMOUMSG=1 *4Em *2DnO  Branches requires 80 global pages to install.  If your system doesnt have at F2  least 80 free global pages, add the following to   SYS$SYSTEM:MODPARAMS.DAT: *2E  *2Ih *4D   Branches requires 80 global pages to install.  If your system doesn't have at least 80 free global pages, add the following to SYS$SYSTEM:MODPARAMS.DAT:y *4EF *2Eo *4Dr  ADD_GBLPAGES=80 *4E[ *2DHQ  Branches requires 4 global sections to install.  If your system doesnt have at  4  least 4 free global sections, add the following to   SYS$SYSTEM:MODPARAMS.DAT: *2En *2I  *4Dp  Branches requires 4 global sections to install.  If your system doesn't have at least 4 free global sections, add the following to SYS$SYSTEM:MODPARAMS.DAT:e *4Ec *2E! *4Da  ADD_GBLSECTIONS=4  Step 2	Run AUTOGEN:*  $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS  s *4E/ *2D O  If your system has been up and running less than 48 hours, add the parameter, yC  NOFEEDBACK, to the command above.  AUTOGEN will run to completion.  *2EB *2Ie *4Dt  If your system has been up and running less than 48 hours, add the parameter, NOFEEDBACK, to the command above.  AUTOGEN will run to completion.s *4Ed *2En *4Dn5  $ @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS NOFEEDBACKb  r *4Ey *2DhG  Neither GBLPAGES nor GBLSECTIONS are dynamic parameters.  If you must sQ  add additional global pages and/or sections to your system then you must reboot  E  your system after running AUTOGEN.  To do so automatically, replace r8  SETPARAMS with REBOOT in the above examples of AUTOGEN.K  Step 3	If you had to add global pages and/or sections to your system, you h6  had to AUTOGEN and reboot.  You may skip this step.  G  If you did not reboot your system, set new values for DISMOUMSG using 4	  SYSGEN.   *2Ep *2Ig *4D  / Neither GBLPAGES nor GBLSECTIONS are dynamic parameters.  If you must add additional global pages and/or sections to your system then you must reboot your system after running AUTOGEN.  To do so automatically, replace SETPARAMS with REBOOT in the a -bove examples of AUTOGEN.  Step 3	If you had to add global pages and/or sections to your system, you had to AUTOGEN and reboot.  You may skip this step.   If you did not reboot your system, set new values for DISMOUMSG using SYSGEN.   *4Eo *2EM *4Do
  $ MCR SYSGENp  SYSGEN> USE ACTIVEi  SYSGEN> SET DISMOUMSG 1  SYSGEN> WRITE ACTIVEe
  SYSGEN> EXITw *4Er *2Dd%  .c1.Installing Branches (VMSINSTAL);n *2Ed *2In *4Dn   Installing Branches (VMSINSTAL) *4Ea *2Eo *4Ds  e *4EV *2DtK  The installation program for Branches is a VMSINSTAL kit.  If you are not tG  familiar with VMSINSTAL, see the VMS System Manager's Guide  for more u
  information. D  The files are contained in the BACKUP save set named BRNCHUUUVV.A, &  where UUU VV is the version number.  R  Do the installation from the system manager's account.  If you aren't the system F  manager, get the system manager to perform this installation for you. *2Eo *2Ir *4De  The installation program for Branches is a VMSINSTAL kit.  If you are not familiar with VMSINSTAL, see the VMS System Manager's Guide  for more information.oi  The files are contained in the BACKUP save set named BRNCHUUUVV.A, where UUU VV is the version number.  f  Do the installation from the system manager's account.  If you aren't the system manager, get the system manager to perform this installation for you.y *4E  *2Ed *4DoH  In this example we used a TK50 tape cartridge with only Branches on it.  Follow these steps:%  Step 1	Log in as the system manager.   Username: SYSTEMt  Password: mE  Step 2	Insert the tape or optical disk in the drive. We used a TK50. %  Step 3	Enter this VMSINSTAL command: %  @SYS$UPDATE:VMSINSTAL product deviceg  f(  product: the exact file name (BRNCHxxx)M  device: the system name of the drive that you inserted the disk or tape into K  We used this command to install Branches v 2.1 from the TK50 device, MUA0: '  $ @SYS$UPDATE:VMSINSTAL BRNCH021 MUA0:S *4Ei *2DrF  Step 4	As VMSINSTAL transfers files, respond to the questions on the M  screen.  See the next chapter, Branches System Information, which describes gL  file names and logical names to make any changes while installing Branches.%  .c2.Example of Typical Installation;2Q  The following example is a typical installation.  If there is no response shown e*  to a prompt, the default has been chosen:  a  o *2Er *2I  *4Db  Step 4	As VMSINSTAL transfers files, respond to the questions on the screen.  See the next chapter, Branches System Information, which describes file names and logical names to make any changes while installing Branches.0   Example of Typical Installationz  The following example is a typical installation.  If there is no response shown to a prompt, the default has been chosen: *4Eb *2Ee *4DS?          VAX/VMS Software Product Installation Procedure V5.5-2$  R *4EE *2DS  E *2ET *4DI  It is 28-MAR-1995 at 06:15.  A0  Enter a question mark (?) at any time for help.  :?  %VMSINSTAL-W-ACTIVE, The following processes are still active:n          DECW$WM_1          MUNROE           MUNROE_SM1a          MUNROE_SM2i          DECW$TE_1          _TWA2:M          _TWA3:u          _TWA4:           _TWA5:h          BATCH-NNTP_73          _TWA6:m          NEWSSKIM_277n          NEWSSKIM_LOCKED          NEWSMGR_1          _VTA4:e          _VTA3:a)  * Do you want to continue anyway [NO]? ys?  * Are you satisfied with the backup of your system disk [YES]?h  w  ,*  The following products will be processed:   
    BRNCH V2.6E  X  S6          Beginning installation of BRNCH V2.6 at 06:15  o7  %VMSINSTAL-I-RESTORE, Restoring product save set A ...bB  * Do you want to purge files replaced by this installation [YES]?  SG  * Enter root directory for BRANCHES directories [$1$DIA2:[BRANCHES.]]:   4M  * Enter file name for BRANCHES configuration file [BRNCH-CONFIGURATION.DAT]:d   D  * Can this system send to and receive mail from the Internet [N]? y  a.  The Internet address for BRANCHES Support is:  y          support@acornsw.com  uF  Enter the OpenVMSMail address necessary to reach support@acornsw.com.   I  * OpenVMSMail address is [support@acornsw.com]: mx%"support@acornsw.com"c   $  No further questions will be asked.    *4EC *2DYB  %VMSINSTAL-I-SYSDIR, This product creates system disk directory    BRNCH_ROOT:[SYSTEM].m *2Er *2I  *4DgV  %VMSINSTAL-I-SYSDIR, This product creates system disk directory  BRNCH_ROOT:[SYSTEM]. *4Es *2Ei *4D 5  %CREATE-I-EXISTS, BRNCH_ROOT:[SYSTEM] already exists  *4Eu *2DaB  %VMSINSTAL-I-SYSDIR, This product creates system disk directory    BRNCH_ROOT:[SCRATCH]. *2EF *2Ii *4DmW  %VMSINSTAL-I-SYSDIR, This product creates system disk directory  BRNCH_ROOT:[SCRATCH].o *4Er *2E  *4Dn6  %CREATE-I-EXISTS, BRNCH_ROOT:[SCRATCH] already exists *4Eh *2DrB  %VMSINSTAL-I-SYSDIR, This product creates system disk directory  $  BRNCH_ROOT:[SCRATCH.DOCUMENTATION]. *2Ee *2Ie *4Dne  %VMSINSTAL-I-SYSDIR, This product creates system disk directory  BRNCH_ROOT:[SCRATCH.DOCUMENTATION].  *4E  *2E	 *4D D  %CREATE-I-EXISTS, BRNCH_ROOT:[SCRATCH.DOCUMENTATION] already exists *4E2 *2DvB  %VMSINSTAL-I-SYSDIR, This product creates system disk directory  '  SYS$COMMON:[SYSHLP.EXAMPLES.BRANCHES].a *2Er *2Iy *4D h  %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$COMMON:[SYSHLP.EXAMPLES.BRANCHES]. *4Er *2E  *4DtG  %CREATE-I-EXISTS, SYS$COMMON:[SYSHLP.EXAMPLES.BRANCHES] already exists  *4Eo *2DnB  %VMSINSTAL-I-SYSDIR, This product creates system disk directory  +  SYS$COMMON:[SYSHLP.EXAMPLES.BRANCHES.SLS].R *2EG *2IE *4DIl  %VMSINSTAL-I-SYSDIR, This product creates system disk directory  SYS$COMMON:[SYSHLP.EXAMPLES.BRANCHES.SLS]. *4Et *2E  *4DtK  %CREATE-I-EXISTS, SYS$COMMON:[SYSHLP.EXAMPLES.BRANCHES.SLS] already existsiK  %BRNCH-I-DELIVER, Delivering BRNCH-STARTUP.COM to SYS$COMMON:[SYS$STARTUP]s@  %BRNCH-I-DELIVER, Delivering BRNCH-STARTUP.COM to BRNCH_SYSTEM:B  %BRNCH-I-DELIVER, Delivering BRNCH-SYSTARTUP.COM to BRNCH_SYSTEM:H  %BRNCH-I-DELIVER, Delivering BRNCH-INVENTORY-TABLE.FDL to BRNCH_SYSTEM:K  %BRNCH-I-DELIVER, Delivering BRNCH-CONFIGURATION.TEMPLATE to BRNCH_SYSTEM:n<  %BRNCH-I-DELIVER, Delivering VMS_SHARE.COM to BRNCH_SYSTEM:8  %BRNCH-I-DELIVER, Delivering DOALL.COM to BRNCH_SYSTEM:G  %BRNCH-I-DELIVER, Delivering BRNCH-PROBLEM-REPORT.COM to BRNCH_SYSTEM:rL  %BRNCH-I-DELIVER, Delivering BRNCH-PROBLEM-REPORT.TEMPLATE to BRNCH_SYSTEM:H  %BRNCH-I-DELIVER, Delivering BRNCH-SYSHUTDWN.COM to SYS$COMMON:[SYSMGR]?  %BRNCH-I-DELIVER, Delivering BRNCH.DOC to BRNCH_DOCUMENTATION:e?  %BRNCH-I-DELIVER, Delivering BRNCH.RTF to BRNCH_DOCUMENTATION:rG  %BRNCH-I-DELIVER, Delivering RELEASE-NOTES.DOC to BRNCH_DOCUMENTATION:eG  %BRNCH-I-DELIVER, Delivering RELEASE-NOTES.RTF to BRNCH_DOCUMENTATION: 8  %BRNCH-I-DELIVER, Delivering BRNCH.KRF to BRNCH_SYSTEM:N  %BRNCH-I-DELIVER, Delivering BRNCH-CONFIGURATION-UTILITY.COM to BRNCH_SYSTEM: *4Ed *2D /  %BRNCH-I-DELIVER, Delivering TAPESTART.COM to o*  SYS$COMMON:[SYSHLP.EXAMPLES.BRANCHES.SLS] *2Eg *2Ia *4DpX  %BRNCH-I-DELIVER, Delivering TAPESTART.COM to SYS$COMMON:[SYSHLP.EXAMPLES.BRANCHES.SLS] *4En *2Et *4Da7  %VMSINSTAL-I-RESTORE, Restoring product save set B ... ;  %BRNCH-I-LINK, Linking OpenVMS VAX specific executables...U!  %BRNCH-I-LINK, Linking BRNCH.EXEh/  %BRNCH-I-LINK, Linking BRNCH-OPCOM-CATCHER.EXEt:  %PATCH-I-NOGBL, some or all global symbols not accessible5  %PATCH-I-NOLCL, image does not contain local symbolss *4EA *2DAL  %PATCH-I-OVERLAY, $1$DIA2:[SYS10.SYSUPD.BRNCH026]BRNCH-OPCOM-CATCHER.EXE;1   being overwritten *2Ee *2It *4Dr]  %PATCH-I-OVERLAY, $1$DIA2:[SYS10.SYSUPD.BRNCH026]BRNCH-OPCOM-CATCHER.EXE;1 being overwritteng *4Ec *2E  *4Ds%  %BRNCH-I-LINK, Linking BRNCH-SET.EXEe.  %BRNCH-I-LINK, Linking BRNCH-SHOWCONTENTS.EXE*  %BRNCH-I-LINK, Linking BRNCH-LOCATION.EXE$  %BRNCH-I-LINK, Linking BRNCHMSG.EXE *4Ey *2DsL  %LINK-W-USRTFR, image $1$DIA2:[SYS10.SYSUPD.BRNCH026]BRNCHMSG.EXE;1 has no   user transfer address *2Et *2II *4DSa  %LINK-W-USRTFR, image $1$DIA2:[SYS10.SYSUPD.BRNCH026]BRNCHMSG.EXE;1 has no user transfer addressi *4ES *2EG *4D4   %BRNCH-I-LINK, Linking MFTU.EXE6  %BRNCH-I-LINK, Linking BRNCH-SYSTEM-DEPENDENT-VAX.EXE8  %BRNCH-I-DELIVER, Delivering BRNCH.EXE to BRNCH_SYSTEM:F  %BRNCH-I-DELIVER, Delivering BRNCH-OPCOM-CATCHER.EXE to BRNCH_SYSTEM:<  %BRNCH-I-DELIVER, Delivering BRNCH-SET.EXE to BRNCH_SYSTEM:E  %BRNCH-I-DELIVER, Delivering BRNCH-SHOWCONTENTS.EXE to BRNCH_SYSTEM:2E  %BRNCH-I-DELIVER, Delivering BRNCH-SHOWLOCATION.EXE to BRNCH_SYSTEM:t;  %BRNCH-I-DELIVER, Delivering BRNCHMSG.EXE to BRNCH_SYSTEM:f7  %BRNCH-I-DELIVER, Delivering MFTU.EXE to BRNCH_SYSTEM:O:  %BRNCH-I-DELIVER, Delivering MFTUCMD.CLD to BRNCH_SYSTEM:M  %BRNCH-I-DELIVER, Delivering BRNCH-SYSTEM-DEPENDENT-VAX.EXE to BRNCH_SYSTEM:n  aB  To complete the installation of Branches you must modify the file)  SYS$MANAGER:SYSTARTUP_V5.COM to contain:@  $)          $ @SYS$STARTUP:BRNCH-STARTUP.COM/  2E  and SYS$MANAGER:SYLOGIN.COM must be modified to define the DCL MOUNT   command as:  F!          $ MOUNT :== MOUNT/ASSISTO   D  Make sure to remove or comment out all other definitions of the DCL*  MOUNT command in SYS$MANAGER:SYLOGIN.COM.  e=  You must also install the new SYS$SHARE:DCLTABLES.EXE on allp?  nodes in your cluster.  This may be accomplished using SYSMAN:A  S          $ MC SYSMAN(          SYSMAN> SET ENVIRONMENT/CLUSTER=          SYSMAN> DO INSTALL REPLACE SYS$SHARE:DCLTABLES.EXE -p)          _SYSMAN> /OPEN/HEADER_RES/SHAREDu          SYSMAN> EXITy  mO  %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...T   6          Installation of BRNCH V2.6 completed at 06:39  l  l*          VMSINSTAL procedure done at 06:39 *4Ed *2DU  E  n  .c1.Configuring Branches;H  After you have completed the VMSINSTAL, the next step is to create the G  Branches configuration file, BRNCH-CONFIGURATION.DAT.  If you entered S;  a file name different from BRNCH-CONFIGURATION.DAT during aP  installation, you have changed the name of the configuration file, that is the   file that you will edit.c *2E  *2Ic *4DP  Configuring Branchese / After you have completed the VMSINSTAL, the next step is to create the Branches configuration file, BRNCH-CONFIGURATION.DAT.  If you entered a file name different from BRNCH-CONFIGURATION.DAT during installation, you have changed the name of the co7 -nfiguration file, that is the file that you will edit.T *4EO *2E1 *4DS6  But, first, define the logical names; use the command(  @SYS$STARTUP:BRNCH-STARTUP.COM LOGICALS *4En *2DsP  Once this is completed, the logicals are defined exactly as they appear in the L  following examples.  You are now prepared to run the configuration utility: *2EL *2I  *4DM  Once this is completed, the logicals are defined exactly as they appear in the following examples.  You are now prepared to run the configuration utility:e *4E  *2Eh *4Dt  a.  @BRNCH_SYSTEM:BRNCH-CONFIGURATION-UTILITY.COM *4Et *2DsM  Branches now comes with a utility to make the creation of configuraton file  P  entries easier.  The Configuration File Utility is used to create entries.  To Q  remove entries, your favorite text editor, e.g., TPU, EDT, etc., should be used.fK  CFU asks a series of questions, when all questions have been answered, it AQ  displays the configuration entry to be added to the configuration file and asks gN  for confirmation.  Upon confirmation the entry is added to the configuration W  file.  If the configuration file does not exist one is created by CFU.  The questions rO  and their answers follow.  You may exit the Configuration File Utility at any t  time by using ^Z or ^Y. *2Et *2Is *4D:  Branches now comes with a utility to make the creation of configuraton file entries easier.  The Configuration File Utility is used to create entries.  To remove entries, your favorite text editor, e.g., TPU, EDT, etc., should be used. / CFU asks a series of questions, when all questions have been answered, it displays the configuration entry to be added to the configuration file and asks for confirmation.  Upon confirmation the entry is added to the configuration file.  If the con -figuration file does not exist one is created by CFU.  The questions and their answers follow.  You may exit the Configuration File Utility at any time by using ^Z or ^Y.i *4En *2Ea *4D2(  Do you have a tape data library? (y/n)   aC  If you have an optical disk library, answer no to this question.    *4Ec *2D:R  A list of the supported data libraries of the appropriate type (tape or optical)   are then displayed. *2Et *2Ix *4Dpe  A list of the supported data libraries of the appropriate type (tape or optical) are then displayed.e *4Ea *2E  *4Dh4  Select from the above by number (return for more):   a *4Ei *2DyT  If your data library appears in the list, enter the number next to it.  If it does 9  not, then use the return key to see more data libraries.  *2El *2In *4De  If your data library appears in the list, enter the number next to it.  If it does not, then use the return key to see more data libraries. *4E- *2EE *4D "  Select from the above by number:     *4E  *2DCN  There are no more data libraries to display after this screen.  If your data O  library has not appeared contact Acorn Software Technical Support for further    help. *2EH *2I_ *4D   There are no more data libraries to display after this screen.  If your data library has not appeared contact Acorn Software Technical Support for further help.s *4EA *2Eu *4Ds  1. CMD BI (CBI)  2. CMD Q-Bus (CQD)k  3. CMD DSSI (CDI)  4. CMD HAWK DSSIt  5. Digital SCSI   :  How are you connecting your data library to your system?   B"  Select from the above by number:   E *4E, *2DoP  The list is all the ways that Branches supports connecting data libraries to a K  VAX or AXP.  Select the appropriate one by entering the number associated :O  with it.  If your interface board does not appear on this list, contact Acorn F3  Software Technical Support for further assistance.r *2Ee *2I  *4Dt / The list is all the ways that Branches supports connecting data libraries to a VAX or AXP.  Select the appropriate one by entering the number associated with it.  If your interface board does not appear on this list, contact Acorn Software Technica" -l Support for further assistance. *4Eb *2Ee *4D /  What node(s) control the data library robot?" c  t"  Node name (return to terminate):   : *4EE *2D N  For each node capable of sending commands to the robot enter the node name.  N  For each node name entered, a server will be started on that node.  Only one M  server will actually issue commands to the robot.  All other servers act as eQ  failover servers in the event that the master node crashes.  If no node name is  O  entered a server will be started on each node upon which the Branches startup 4  command procedure is run. *2E: *2IT *4Dl / For each node capable of sending commands to the robot enter the node name.  For each node name entered, a server will be started on that node.  Only one server will actually issue commands to the robot.  All other servers act as failover servers i -n the event that the master node crashes.  If no node name is entered a server will be started on each node upon which the Branches startup command procedure is run. *4ES *2EO *4DSM  Do any of the above nodes(s) have more than one data library attached? (y/n)c  t *4Es *2DiM  If you have more than one data library connected to any of the nodes in the EP  above list (or any node on the cluster if you entered no node name) answer yes. *2EA *2IY *4D   If you have more than one data library connected to any of the nodes in the above list (or any node on the cluster if you entered no node name) answer yes. *4Ek *2Ec *4D '  Enter your name for the data library: .  4 *4E2 *2D4N  If you answered yes to the previous question, you must enter a name for your K  data library.  This name will be used in all Branches commands required a sJ  library name parameter or a /LIBRARY qualifier.  The name may be up to 7 P  characters long, must begin with an alphabetic character, and must be unique.  K  If you are not sure which names are in use, check your configuration file.r *2ER *2IO *4DR / If you answered yes to the previous question, you must enter a name for your data library.  This name will be used in all Branches commands required a library name parameter or a /LIBRARY qualifier.  The name may be up to 7 characters long, must be -gin with an alphabetic character, and must be unique.  If you are not sure which names are in use, check your configuration file. *4E- *2EE *4Dl&  Which VMS device controls the robot?     *4EC *2DEM  Specify which VMS devices is used to send SCSI commands to the robot.  This rT  device need not exist but if it does not you will be asked for confirmation to use   the specified device. *2EI *2I  *4DC  Specify which VMS devices is used to send SCSI commands to the robot.  This device need not exist but if it does not you will be asked for confirmation to use the specified device.. *4Eo *2ES *4DM@  Enter unit number of the DU device representing the robot: (0)   E *4El *2DnM  In the event that you are using a CMD board such as the CDQ, the robot will  M  appear as a disk device, e.g., $1$DUA3:.  You will need to provide the unit nW  number of the device, in this case 3, in response to this question.  0 is the default K  value if you make no answer.X *2E% *2I- *4DB / In the event that you are using a CMD board such as the CDQ, the robot will appear as a disk device, e.g., $1$DUA3:.  You will need to provide the unit number of the device, in this case 3, in response to this question.  0 is the default value if y -ou make no answer.N *4E] *2E- *4D-'  Number of drives in the data library? 2   9  Enter the number of drives present in your data library.K  Drive name 0: H  Drive name 1:  ...  - *4E  *2DnL  For each drive in the data library, enter the VMS device name.  The device G  need not exist, but you will be asked for confirmation if it does not.u *2Er *2Ir *4De  For each drive in the data library, enter the VMS device name.  The device need not exist, but you will be asked for confirmation if it does not. *4EK *2Ek *4DF'  Base priority for Branches server? (4)T  D *4EE *2DXQ  Specifies the base process priority of the Branches server.  The default is 4.  DL  The valid ranges is between 1 and 15.  Use a higher number if you want the '  Branches server to be more responsive.C *2EE *2I, *4Dv  Specifies the base process priority of the Branches server.  The default is 4.  The valid ranges is between 1 and 15.  Use a higher number if you want the Branches server to be more responsive. *4ED *2Er *4DF&  Capture debugging information? (y/n)   , *4Ev *2D N  If you wish to capture debugging information (a good idea when you are first *  bringing up your data library) reply yes. *2Ee *2Ia *4Dow  If you wish to capture debugging information (a good idea when you are first bringing up your data library) reply yes.R *4EO *2E2 *4Dd  DEFINE            libraryName"  TYPE              dataLibraryType  NODE              nodeNameM%  CONTROL           robotControlDevicet5  DRIVE             numberOfDrives,(drive0,drive1,...)L  TRANSPORT         interconnectY   PRIORITY		serverProcessPriority!  TRACE             debuggingStateE     Is this correct? (y/n)     *4E  *2DeP  At this point the configuration file entry is complete.  The entry, as it will R  appear in the configuration file, is displayed.  If you wish to add the entry to $  the configuration file, answer yes.?  .c2.Example of Configuring Branches to support an Exabyte 210;  *2Ee *2Id *4Dh  At this point the configuration file entry is complete.  The entry, as it will appear in the configuration file, is displayed.  If you wish to add the entry to the configuration file, answer yes.:  Example of Configuring Branches to support an Exabyte 210 *4EB *2Ee *4Df,  $ @brnch_system:brnch-configuration-utility$  Branches Configuration Utility V1.1;  Copyright Acorn Software, Inc., 1994, all rights reserved.   n)  Do you have a tape data library? (y/n) yt     1. ADIC 4mm DatStacker   2. Conner's Python4  3. Digital THZ27a  4. Digital TL820   5. Dilog DBS0  6. Dilog Libra 8e  7. Dilog Libra 16  8. Exabyte 10ef  9. Exabyte 10iR  10. Exabyte 60.  11. Exabyte 120  12. Exabyte 210  e6  Select from the above by number (return for more): 12  v9  How are you connecting your data library to your system?e  l  1. CMD BI (CBI)  2. CMD Q-Bus (CQD)S  3. CMD DSSI (CDI)  4. CMD HAWK DSSI;  5. Digital SCSI  Y#  Select from the above by number: 5   n-  What node(s) control the data library robot?r'  Node name (return to terminate): quick !  Node name (return to terminate):r  rO  Do any of the above nodes(s) have more than one data library attached? (y/n) yt  l-  Enter your name for the data library: exb210h  o*  Which VMS device controls the robot? gka0  t(  Number of drives in the data library? 2     Drive name 0: mka100H  Drive name 1: mka200C   '  Base priority for Branches server? (4)i  y'  Capture debugging information? (y/n) ye     Your configuration entry is:t     DEFINE          EXB210r  TYPE            EX210  NODE            QUICK  CONTROL         _QUICK$GKA0: 2  DRIVE           2,(_QUICK$MKA100:,_QUICK$MKA200:)  TRANSPORT       GKA  PRIORITY        4  TRACE           OPCOM,SCSIr  o  Is this correct? (y/n) yc *4Eu *2Dn  .c1.Starting Branches;n *2Et *2I  *4Dc  Starting Branches *4Ea *2Et *4D )  Start Branches by entering this command:n(  	Execute SYS$STARTUP:BRNCH-STARTUP.COM *4Ee *2DtL  If the Branches system startup command procedure is invoked by your system L  startup command procedure, then Branches will restart when you reboot your   system.I  The Branches system startup command procedure may be used to define the tA  Branches system wide logical names without starting any servers:r *2Er *2Ie *4Di  If the Branches system startup command procedure is invoked by your system startup command procedure, then Branches will restart when you reboot your system.  The Branches system startup command procedure may be used to define the Branches system wide logical names without starting any servers:g *4Eo *2Ee *4D    *  	@SYS$STARTUP:BRNCH-STARTUP.COM LOGICALS   J  Servers may be started without either database or library initialization:  b+  	@SYS$STARTUP:BRNCH-STARTUP.COM STARTONLY   e=  Specific servers may be also be started on the current node:l  a *4En *2Dn0  	@SYS$STARTUP:BRNCH-STARTUP.COM  libraryName  .c1.Licensing Branches;H  When Branches is started, it automatically installs a 30 day temporary O  license.  During this period you may freely operate Branches.  Once this time rA  period expires Branches will no longer respond to user requests.aK  During the last 7 days of a temporary license, Branches sends mail to the eH  SYSTEM account warning that the Branches temporary license is about to P  expire.  The body of the mail message contains a key request form for the node   running the Branches server.tO  You must acquire a license key from Acorn Software to continue using Branches i  beyond this time period.  SP  Branches must be licensed on each node on which a data library server is to be O  run.  In practice this means that a license must be installed on each node to  %  which a data library is connected.  rG  Use the Branches License/OUTPUT[=SYS$OUTPUT:] command to generate the sG  license or key request form.  The output of that commandappears below o3  complete and ready to send back to Acorn Software.A *2Eu *2Is *4D 0  	@SYS$STARTUP:BRNCH-STARTUP.COM "" libraryName  Licensing BranchesS  When Branches is started, it automatically installs a 45 day temporary license.  During this period you may freely operate Branches.  Once this time period expires Branches will no longer respond to user requests. / During the last 7 days of a temporary license, Branches sends mail to the SYSTEM account warning that the Branches temporary license is about to expire.  The body of the mail message contains a key request form for the node running the Branches ser -ver.hi  You must acquire a license key from Acorn Software to continue using Branches beyond this time period.  e  Branches must be licensed on each node on which a data library server is to be run.  In practice this means that a license must be installed on each node to which a data library is connected.    Use the Branches License/OUTPUT[=SYS$OUTPUT:] command to generate the license or key request form.  The output of that commandappears below complete and ready to send back to Acorn Software.e *4Es *2E  *4Db$  Example of Branches License/Output $  $ BRANCH LICENSE/OUTPUT=LICENSE.TXT     $ TYPE LICENSE.TXTv&  Key Request Form:       BRANCHES V2.60  Date:                   27-MAR-1995 20:36:07.74  sC  To obtain your Software Key, send this form containing your SystemnK  Identification Code (below) to Acorn Software, Inc., or contact your Acorn P  Software service or sales representative.  If you are outside of North America,P  contact your local Branches distributor or send your System Identification CodeO  directly to Acorn Software to obtain a Software Key which will enable full usee  of BRANCHES V2.6.   %                  Acorn Software, Inc.s                  267 Cox St."                  Hudson, Ma. 01749  m:                  Phone:  508-568-1618    Fax: 508-562-11334                  E-Mail: LICENSE-REQUEST@ACORNSW.COM  nJ  Please complete this software key request form by providing the followingK  information before sending this form to Acorn Software, Inc. or your localdH  Branches distributor.  Only key request forms that have been filled out  completely can be processed.    C          Company:        Data Library Specialists_________________  C          Address:        946 Massachusetts Avenue_________________ tC                          Cambridge, MA. 02139_____________________ eC                          _________________________________________ lC                          _________________________________________ eC          Country:        USA______________________________________ gC          Phone:          (617) 491-7474___________________________  C          Fax:            (617) 491-7475___________________________ eC          Contact Person: D. Dewey_________________________________  C          Title:          V.P., Marketing__________________________ i  lB          Data Library Manufacturer:      Exabyte------------------B          Data Library Model:             210----------------------   N  The following is a list of System Identification Codes for some or all of theM  VAXes in your VAXcluster.  To include the System Identification Codes (SICs)oM  for additional VAXes in your VAXcluster, log in to those VAXes and issue theS   )          BRANCHES LICENSE/OUTPUT=filenamed  t  command for Branches.  oD  SIC:    BRN2-4WVLB7-E3CNXX-XGFXB5---3CG4W4-WD4MT5-DGT0K6    (QUICK)  2 *4E4 *2DS  .c1.Set Startup Sequence; *2Et *2Id *4D   Set Startup Sequence  *4Ed *2E  *4Dn  eU  For automatic startup, modify the system startup procedures to include this command:.!  $ @SYS$STARTUP:BRNCH-STARTUP.COMb  o *4E  *2DvQ  If you have the Digital-supplied SCSI driver, you must use SYSGEN to create the aO  appropriate GK device.  For example, to create a GK device that provides SCSI DN  pass through to SCSI unit 0 on the external SCSI bus of a MicroVAX 3100, add E  these commands to your startup file, SYS$MANAGER:SYSTARTUP_V5.COM,  e#  before  running BRNCH-STARTUP.COM.t *2Ee *2Ia *4D  / If you have the Digital-supplied SCSI driver, you must use SYSGEN to create the appropriate GK device.  For example, to create a GK device that provides SCSI pass through to SCSI unit 0 on the external SCSI bus of a MicroVAX 3100, add these commandZ -s to your startup file, SYS$MANAGER:SYSTARTUP_V5.COM,  before  running BRNCH-STARTUP.COM. *4E  *2Eu *4Da
  $ MCR SYSGENi  CONNECT GKB0: /NOADAPTER:  . *4E- *2D Q  For further information on configuring generic SCSI devices, see the I/O User's    Reference: Part II.@  The next step is to modify the system login command procedure, C  SYS$MANAGER:SYLOGIN.COM so that Branches can respond to DCL Mount  Q  requests.  In the Digital supplied version of this file, the line, $ MOU*NT :==  !  MOUNT/NOASSIST, edit it to read:r *2Ec *2Ie *4D d  For further information on configuring generic SCSI devices, see the I/O User's Reference: Part II.  The next step is to modify the system login command procedure, SYS$MANAGER:SYLOGIN.COM so that Branches can respond to DCL Mount requests.  In the Digital supplied version of this file, the line, $ MOU*NT :== MOUNT/NOASSIST, edit it to read: *4En *2Ed *4D   $ MOU*NT :== MOUNT/ASSIST   0  Branches can now respond to DCL MOUNT requests. *4E  *2D   .c1.Using Branches;M  For specifics on commands, please see the next chapter, Branches commands.   N  But, here in the broadest of strokes, are the first steps in using  Branches: *2E2 *2I4 *4DI  Using Branchest  For specifics on commands, please see the next chapter, Branches commands.  But, here in the broadest of strokes, are the first steps in using  Branches: *4E  *2E  *4Dt  bS  1.  Create the inventory table first --  before  any Branches commands are issued.E  $ Branches Initialize/Databasee  r"  2.  Initialize the data library.   $ Branches Initialize/Library  rK  3.  Populate the inventory table with volume labels, if media are present.   $ Branches Initialize/Verifyc  i-  4.  Import media to place it in inventory.     $ Branches Import  e1  5.  Read or write data to a volume in a drive.  a  $ Mount DCL command orn  $ Branches Mount DCL command. *4Ea *2Do  .c1. Updating Branches P  If you are updating your installation of Branches with a new version, stop all ,  Branches library servers with this command: *2E  *2Io *4Dr  Updating Branches{  If you are updating your installation of Branches with a new version, stop all Branches library servers with this command:a *4E2 *2E4 *4D2  $ Branches SHUTDOWN/ALL  n *4En *2DaO  After you have entered this command, install the upgrade as described before, cH  and run Branches system startup procedure again.  If you are upgrading K  Branches, the default values of the answers to the questions asked during  9  installation will be those of your current installation.  *2E  *2I  *4D8 / After you have entered this command, install the upgrade as described before, and run Branches system startup procedure again.  If you are upgrading Branches, the default values of the answers to the questions asked during installation will be thos  -e of your current installation. *4ES *2E5 *4Di    *4E  *2DS+  .c.Chapter 4, Branches System Information; K  This chapter describes startup and shutdown activities and defines system u  variables that Branches uses.  .c1.System Startup;Q  The system startup procedure processes the Branches configuration file, defines r;  the Branches logical names and starts the library servers.c  .c1.System Shutdown;kP  Makes sure the cartridges in the drives have been dismounted and are safely in ,  their slots before the system is shut down.(  .c1.System Variables and Logical Names;S  This section lists logical names, identifiers, system directories, and file names 1I  used by Branches.  All logical names are defined by the Branches system $  startup procedure.  *2E( *2IK *4D0'  Chapter 4, Branches System Information h  This chapter describes startup and shutdown activities and defines system variables that Branches uses.  System Startupt  The system startup procedure processes the Branches configuration file, defines the Branches logical names and starts the library servers.e  System Shutdown{  Makes sure the cartridges in the drives have been dismounted and are safely in their slots before the system is shut down.e#  System Variables and Logical Namesa  This section lists logical names, identifiers, system directories, and file names used by Branches.  All logical names are defined by the Branches system startup procedure.e *4Er *2Eo *4D   Logical Names *4Eb *2Dr7  BRNCH_CONFIGURATION	The file of library configuration t
  information.b0  BRNCH_DOCUMENTATION	The directory for Branches   documentation.y3  BRNCH_LIBGXX_SHR	The file of the GNU C++ run time a	  library. ,  BRNCH_ROOT	The root directory for Branches    system and scratch directories.3  BRNCH_SCRATCH	The directory for all files created d  and used by Branches.2  BRNCH_SUPPORT	A logical name for the destination    of a mail message for software %  support.  This logical name is only e&  defined if your site is connected to #  the Internet and the installation c$  procedure is informed of this fact.1  BRNCH_SYSTEM	An identifier that allows the data  &  library server access to the control   device for the datalibrary.6  BRNCH-SYSTEM-DEPENDENT	An operating system dependent   sharable library. *2E  *2In *4D C  BRNCH_CONFIGURATION	The file of library configuration information.S>  BRNCH_DOCUMENTATION	The directory for Branches documentation.;  BRNCH_LIBGXX_SHR	The file of the GNU C++ run time library.eK  BRNCH_ROOT	The root directory for Branches system and scratch directories. H  BRNCH_SCRATCH	The directory for all files created and used by Branches.  BRNCH_SUPPORT	A logical name for the destination of a mail message for software support.  This logical name is only defined if your site is connected to the Internet and the installation procedure is informed of this fact.eq  BRNCH_SYSTEM	An identifier that allows the data library server access to the control device for the datalibrary.tG  BRNCH-SYSTEM-DEPENDENT	An operating system dependent sharable library.t *4EA *2Eu *4Ds  Identifiers *4ER *2DR2  BRNCH_CONTROL	An identifier that allows Branches   access to the control device. *2Ea *2Il *4DtO  BRNCH_CONTROL	An identifier that allows Branches access to the control device.h *4EO *2Eh *4Dm  System Directoriesc+  BRNCH_DOCUMENTATION	See discussion above.  %  BRNCH_SCRATCH	See discussion above.  $  BRNCH_SYSTEM	See discussion above.   M   System Files *4E  *2Dr9  libraryName-OUTPUT.LOG	If tracing is enabled, the trace h"  output for the named library (in   BRNCH_SCRATCH:). <  libraryName-ERROR.LOG	If a library error occurs, the error "  information (for that library).    Tracing is forced on for the !  duration of error recovery; all s$  commands and responses used during   error recovery appear in   libraryName-OUTPUT.LOG. *2Es *2It *4Dnk  libraryName-OUTPUT.LOG	If tracing is enabled, the trace output for the named library (in BRNCH_SCRATCH:). c  libraryName-ERROR.LOG	If a library error occurs, the error information (for that library).  Tracing is forced on for the duration of error recovery; all commands and responses used during error recovery appear in libraryName-OUTPUT.LOG.  *4E$ *2E  *4DS  libraryName.INVENTORY-TABLE	  *4EC *2D2$  	The file of inventory information   for the named data library. *2E  *2Ia *4Dy?  	The file of inventory information for the named data library.e *4Et *2Er *4Dt6  BRNCH_CONFIGURATION:	The Branches configuration file.  l *4Ep *2Dt!  .c.Chapter 5, Branches Commands; N  With the Branches commands noted in this chapter, you can access and use the M  contents of your data library.   Branches commands provide an interface for bL  controlling your data library devices. This is a quick summary of Branches 
  commands: *2E2 *2Ix *4D   Chapter 5, Branches Commands7  With the Branches commands noted in this chapter, you can access and use the contents of your data library.   Branches commands provide an interface for controlling your data library devices. This is a quick summary of Branches commands: *4Eo *2Ef *4D,  c  Function	Branches Command,  Dismount the tape or disk	BRANCHES DISMOUNT4  Display the current version number	BRANCHES VERSION2  Export the tape, disk or magazine	BRANCHES EXPORT2  Import the tape, disk or magazine	BRANCHES IMPORT9  Initialize the data library hardware	BRANCHES INITIALIZE .  Load the magazine, tape or disk	BRANCHES LOAD4  Manage the license key information	BRANCHES LICENSE.  Mount the tape, disk, or CDROM	BRANCHES MOUNT3  Mount the tape, disk, or CDROM	DCL Mount/SYS$MOUNT '  Set state within Branches	BRANCHES SET_2  Show the contents of a data library	BRANCHES SHOW3  Shutdown the data library server	BRANCHES SHUTDOWN(0  Tune an account for use by BACKUP	BRANCHES TUNE  Unload a drive	BRANCHES UNLOAD_  _ *4E_ *2D_L  The following pages list each command in alphabetical order.  Each command   appears on a separate page. *2Eu *2Ir *4D g  The following pages list each command in alphabetical order.  Each command appears on a separate page.e *4Eo *2Ei *4Di  o *4Et *2De  .c1.Branches Dismount;e *2El *2It *4DV  Branches Dismount *4E  *2Ec *4Dt  S *4E  *2DiN  Closes a device mounted in a library and cancels the logical name associated Q  with it.  For full details of the interpretation of the command qualifiers, see d1  the VMS DCL Dictionary discussion of DISMOUNT.  X *2E3 *2I- *4D5  Closes a device mounted in a library and cancels the logical name associated with it.  For full details of the interpretation of the command qualifiers, see the VMS DCL Dictionary discussion of DISMOUNT.   *4E. *2E@ *4DT  This command requires: '  	the GRPNAM (group logical name) and s *4Ee *2DIH  	SYSNAM (system logical name) privileges to dismount group and system   volumes as well as TMPMBX.c *2Et *2Ii *4DCb  	SYSNAM (system logical name) privileges to dismount group and system volumes as well as TMPMBX. *4Ey *2Et *4D %  Format	Branches DISMOUNT device-name   Qualifiers	NotesN *4EA *2DCA  /ABORT	Specifies that the volume is to be dismounted regardless v  of who mounted it.E *2Ec *2I  *4DpS  /ABORT	Specifies that the volume is to be dismounted regardless of who mounted it.u *4E  *2Eu *4D *  /CLUSTER	Dismounts a volume cluster-wide.   /OVERRIDE=CHECKS	To be supplied *4Ef *2DS8  /UNIT	Dismounts only the volume of a volume set on the   specified drive.  *2E  *2IR *4DEH  /UNIT	Dismounts only the volume of a volume set on the specified drive. *4Ef *2En *4De?  /[NO]UNLOAD	Unloads the device on which the volume is mounted.e  x *4Ep *2Do  .c1.Branches Export;n *2Ea *2Io *4De  Branches Export *4EN *2Es *4Dt  a *4E  *2DeK  Exports a volume from a library.  For libraries with mailboxes, the media eJ  associated with the volume will be placed in the mailbox and the mailbox L  opened.  The media may then be removed.  For libraries with magazines, the K  media associated with the volume is placed in the magazine.  The magazine m  may then be removed later.  O  This command requires:c  	OPER and TMPMBX privileges.M  In all cases, the volume and all other volumes associated with the media is O"  removed from the inventory table. *2E  *2IM *4D  / Exports a volume from a library.  For libraries with mailboxes, the media associated with the volume will be placed in the mailbox and the mailbox opened.  The media may then be removed.  For libraries with magazines, the media associated with the M -volume is placed in the magazine.  The magazine may then be removed later.  l  This command requires:,  	OPER and TMPMBX privileges.n  In all cases, the volume and all other volumes associated with the media is removed from the inventory table. *4Ea *2Ei *4D-%  Format	Branches EXPORT [volume-name]u  Qualifiers	Notesn *4Ei *2Dt<  /MAGAZINE	For libraries that have magazines, the /MAGAZINE <  qualifier is used to allow the user to remove the magazine 4  from the library.  If /MAGAZINE is omitted, volume-2  name is required.  /MAGAZINE only has effect for ,  libraries having magazines.  /MAGAZINE and "  /POSITION are mutually exclusive. *2E  *2I$ *4Dt / /MAGAZINE	For libraries that have magazines, the /MAGAZINE qualifier is used to allow the user to remove the magazine from the library.  If /MAGAZINE is omitted, volume-name is required.  /MAGAZINE only has effect for libraries having magazines.  // -MAGAZINE and /POSITION are mutually exclusive.h *4Et *2Ee *4DsM  /LIBRARY[=DEFAULT]	The data library from which the volume is to be exported.$ *4Ec *2DHH  /POSITION=number	The position of the volume to be exported.  /POSITION 8  and /MAGAZINE are mutually exclusive.  If the position ;  being exported is on media with more than one side, e.g., ,=  magneto-optical, all positions associated with the exported g   position will also be exported.  u  u  .c1.Branches Import;2 *2E2 *2I4 *4D  / /POSITION=number	The position of the volume to be exported.  /POSITION and /MAGAZINE are mutually exclusive.  If the position being exported is on media with more than one side, e.g., magneto-optical, all positions associated with the exported posi -tion will also be exported.  4     Branches Import *4E2 *2E. *4Dp    *4Ea *2D Q  Imports media into a library.  For data libraries with mailboxes, the specified eL  media will be placed in the mailbox and then imported.  For data libraries 7  with magazines, the media is placed in the magazine.  n *2E, *2In *4D   Imports media into a library.  For data libraries with mailboxes, the specified media will be placed in the mailbox and then imported.  For data libraries with magazines, the media is placed in the magazine.   *4E1 *2Ee *4Di  This command requires:   	OPER and TMPMBX privileges. *4Ee *2DeF  Media imported using the /SCRATCH qualifier remains as SCRATCH media O  until it has been placed in a device in response to a Branches LOAD, Branches 4'  MOUNT, DCL MOUNT or SYS$MOUNT request.o *2ET *2Ih *4D   Media imported using the /SCRATCH qualifier remains as SCRATCH media until it has been placed in a device in response to a Branches LOAD, Branches MOUNT, DCL MOUNT or SYS$MOUNT request. *4Ee *2Ec *4Do8  Format	Branches IMPORT [volumelabel[, volumelabel ...]]  Qualifiers	Notesh *4Et *2DsI  /INITIALIZE	Import media into a library and initialize all volumes with e:  the associated media with their specific labels.  If not ;  enough labels are provided, media with multiple sides are c7  initialized with the name volumelabelA, volumelabelB, e4  etc.  The /INITIALIZE and /MAGAZINE qualifiers are   mutually exclusive.C  /MAGAZINE	Accept a magazine of media into a library and, for each c<  piece of media present, read the label on each side of the 6  media and place the media into the library inventory 5  database.  The /INITIALIZE and /MAGAZINE qualifiers R  are mutually exclusive. *2Ec *2I  *4De / /INITIALIZE	Import media into a library and initialize all volumes with the associated media with their specific labels.  If not enough labels are provided, media with multiple sides are initialized with the name volumelabelA, volumelabelB, etc.  T@ -he /INITIALIZE and /MAGAZINE qualifiers are mutually exclusive. / /MAGAZINE	Accept a magazine of media into a library and, for each piece of media present, read the label on each side of the media and place the media into the library inventory database.  The /INITIALIZE and /MAGAZINE qualifiers are mutually exclu -sive. *4EN *2Ef *4DfJ  /LIBRARY[=DEFAULT]	The data library to which the media is to be imported.?  /SCRATCH	The imported media is to be considered scratch media.+ *4E  *2DlI  /SLOT=number	All media must, at some time, be initialized.  In the case r;  of libraries with magazines, the /SLOT qualifier allows a d=  specific media in the magazine to be initialized and placed e8  into the library inventory database.  Slots are always =  numbered from 0.  0 is the first slot in the magazine.  The e8  /SLOT and /MAGAZINE qualifier are mutually exclusive.  9  The /SLOT qualifier may be used at any time to reimport a@  or reinitialize media that are already within a data library.  >  If the specified slot does not have media in it and the data 8  library has a mailbox, then Branches will request that 6  media be placed into the mailbox for processing into   inventory.v  .  2     .c1.Branches Initialize;A  dM  Performs initialization of components of the Branches library subsystem and    the library hardware.  This command requires:s  	OPER and TMPMBX privileges.M  When a new inventory data base is created and the data library has media in lM  it, the new inventory data base will have those slots marked as full with a tM  volume name of "++++++++++++".  Thus, Branches cannot attempt to use either  N  drives or slots which already contain media.  To fully recover the inventory E  table database, you must issue a Branches INITIALIZE/VERIFY command.  *2En *2Is *4Dr / /SLOT=number	All media must, at some time, be initialized.  In the case of libraries with magazines, the /SLOT qualifier allows a specific media in the magazine to be initialized and placed into the library inventory database.  Slots are always num /bered from 0.  0 is the first slot in the magazine.  The /SLOT and /MAGAZINE qualifier are mutually exclusive.  The /SLOT qualifier may be used at any time to reimport or reinitialize media that are already within a data library.  If the specified s -lot does not have media in it and the data library has a mailbox, then Branches will request that media be placed into the mailbox for processing into inventory.  I  A  N  Branches Initialize  ib  Performs initialization of components of the Branches library subsystem and the library hardware.  This command requires:s  	OPER and TMPMBX privileges. / When a new inventory data base is created and the data library has media in it, the new inventory data base will have those slots marked as full with a volume name of "++++++++++++".  Thus, Branches cannot attempt to use either drives or slots whic~ -h already contain media.  To fully recover the inventory table database, you must issue a Branches INITIALIZE/VERIFY command. *4Er *2Ei *4DT   '  Format	Branches INITIALIZE libraryname  *4E  *2D i  Parameters	The name of the library for which the initialize operation is to be performed.   If omitted, r  the default library is used.E *2E  *2Ia *4Di  Parameters	The name of the library for which the initialize operation is to be performed.   If omitted, the default library is used.I *4E  *2Ea *4D   Qualifierse *4Ei *2DA@  /DATABASE	The inventory data base for the specified library is +  constructed. The /DATABASE, /LIBRARY, and T:  /VERIFY qualifiers are mutually exclusive.  The database >  created correctly records the state of slots and drives.  If =  drives have media in them, the drive will be marked as full N/  and will not be available for use by Branches.PE  /LIBRARY	The library hardware is initialized for use.  No media may f5  be mounted in the library and the library inventory  4  database must exist.  The /DATABASE, /LIBRARY, and +  /VERIFY qualifiers are mutually exclusive.aJ  /USAGE=BACKUP	Verify the labels of all media flagged as processed by the 6  OpenVMS BACKUP utility.  This qualifier must be used   in conjunction with /VERIFY.u>  /VERIFY	The inventory database is constructed by reading the :  volume labels of the media in the library.  No media may 5  be mounted on drives in the library and the library a0  inventory database must exist.  The /DATABASE, /  /LIBRARY, and /VERIFY qualifiers are mutually  
  exclusive.  d *2E  *2Ir *4D  / /DATABASE	The inventory data base for the specified library is constructed. The /DATABASE, /LIBRARY, and /VERIFY qualifiers are mutually exclusive.  The database created correctly records the state of slots and drives.  If drives have media in themR -, the drive will be marked as full and will not be available for use by Branches.  /LIBRARY	The library hardware is initialized for use.  No media may be mounted in the library and the library inventory database must exist.  The /DATABASE, /LIBRARY, and /VERIFY qualifiers are mutually exclusive.  /USAGE=BACKUP	Verify the labels of all media flagged as processed by the OpenVMS BACKUP utility.  This qualifier must be used in conjunction with /VERIFY.e / /VERIFY	The inventory database is constructed by reading the volume labels of the media in the library.  No media may be mounted on drives in the library and the library inventory database must exist.  The /DATABASE, /LIBRARY, and /VERIFY qualifier -s are mutually exclusive.   *4Eh *2Eu *4D D  NOTE:  For tapes, this command may take up to 3 minutes per tape.  K  NOTE:  The database must be created before the library can be initialized.c     o *4E  *2D   .c1.Branches License; *2E  *2I  *4D   Branches Licensee *4Ep *2Ea *4Dm  r *4El *2DyP  Produces a license and key request form for Branches.  Please see the section, M  Branches Key Request and License Form, for an example of the output of this .	  command.r *2Ei *2Ig *4Ds  Produces a license and key request form for Branches.  Please see the section, Branches Key Request and License Form, for an example of the output of this command. *4Ee *2EI *4D 1  The command, Branches License/Install, requires:w  	SYSPRV privilege.C  Each node that runs a Branches server must be licensed seperately.e  o  Format	Branches LICENSE   	Branches LICENSE/INSTALL [key]  Qualifiers	Notese *4E  *2DaR  /OUTPUT[=SYS$OUTPUT:]	The file to contain the key request form.  The key request *  form is written to SYS$OUTPUT by default.G  /INSTALL 	Installs a license.  Branches must be licensed on each node m8  on which it will run and for each data library on each :  node.  Key parameter, provided by Acorn, must be entered.     o  t  .c1.Branches Load;r  vI  Loads a device with the volume.   Load/Position loads the volume from a lL  position in the data library into a drive.    Load/Scratch loads a SCRATCH E  volume into a drive.  Any available SCRATCH volume will be loaded.  o *2Ee *2Iz *4D {  /OUTPUT[=SYS$OUTPUT:]	The file to contain the key request form.  The key request form is written to SYS$OUTPUT by default.a  /INSTALL 	Installs a license.  Branches must be licensed on each node on which it will run and for each data library on each node.  Key parameter, provided by Acorn, must be entered.e  e  g  n  Branches Load     Loads a device with the volume.   Load/Position loads the volume from a position in the data library into a drive.    Load/Scratch loads a SCRATCH volume into a drive.  Any available SCRATCH volume will be loaded.   *4E  *2E  *4Do  This command requires:   	OPER and TMPMBX privileges.  o.  Format	Branches LOAD device-name [volumename]  Qualifiers	Notese *4Ea *2Dx<  /MAGAZINE	Loads a magazine of media into a library without   importing any of the media. *2Eo *2Ic *4DlW  /MAGAZINE	Loads a magazine of media into a library without importing any of the media.1 *4Ec *2Em *4D2N  /LIBRARY[=DEFAULT]	The data library into which the magazine is to be loaded. F  /POSITION=position	The position from which the volume is to be taken.=  /SCRATCH	Loads any SCRATCH volume into the device specified.p  a *4El *2Dt  .c1.Branches Mount; *2Ep *2I  *4D   Branches Mounte *4Er *2E  *4D   B *4Ee *2DoQ  Mounts the media in a library onto a drive in a library.  Only those qualifiers aO  relevant to disks are supported.  For a full discussion of the meaning of the e5  various qualifiers see the VMS Mount Utility Manual.m *2Ei *2Ic *4D   Mounts the media in a library onto a drive in a library.  Only those qualifiers relevant to disks are supported.  For a full discussion of the meaning of the various qualifiers see the VMS Mount Utility Manual.e *4Es *2Ee *4Dt  This command requires:e *4Ei *2Di@  	GRPNAM (group logical name) and SYSNAM (system logical name) 1  privileges to mount group and system volumes ands *2EC *2I  *4D p  	GRPNAM (group logical name) and SYSNAM (system logical name) privileges to mount group and system volumes and *4Ee *2E  *4D   	TMPMBX privileges.r    *4E  *2DSF  Branches MOUNT provides a subset of the functionality of the VMS DCL <  MOUNT command.  For maximum flexibility use Branches MOUNT. *2E  *2IO *4De  Branches MOUNT provides a subset of the functionality of the VMS DCL MOUNT command.  For maximum flexibility use Branches MOUNT.p *4Ee *2En *4Dl>  Format	Branches MOUNT device-name volume-label [logical-name]  Qualifiers	Notes  *4Es *2D ?  /BIND	Creates a volume set of one or more volumes or adds one c+  or more volumes to an existing volume set.lC  /CLUSTER	Specifies that  after the volume is successfully mounted m8  on the local node, or if it is already mounted /SYSTEM <  on the local node, it is to be mounted on every other node   in the existing VMScluster.F  /EXTENSION	Specifies the number of blocks by which disk files are to 9  be extended on the volume unless otherwise specified by l*  an individual command or program request.B  /FOREIGN	Indicates that the volume is not in the standard format !  used by the VMS operating system.@  /GROUP	Makes the volume available to other users with the same 5  group number in their UICs as the user entering the e  Mount command.I *2E  *2IM *4DNi  /BIND	Creates a volume set of one or more volumes or adds one or more volumes to an existing volume set.i  /CLUSTER	Specifies that  after the volume is successfully mounted on the local node, or if it is already mounted /SYSTEM on the local node, it is to be mounted on every other node in the existing VMScluster.  /EXTENSION	Specifies the number of blocks by which disk files are to be extended on the volume unless otherwise specified by an individual command or program request. b  /FOREIGN	Indicates that the volume is not in the standard format used by the VMS operating system  /GROUP	Makes the volume available to other users with the same group number in their UICs as the user entering the Mount command. *4Ey *2En *4De'  /[NO]SHARE	Makes the volume shareable.a *4E  *2DeD  /SYSTEM	Makes the volume public, that is available to all users of 8  the system, as long as the UIC-based volume protection   allows them access.@  /[NO]UNLOAD	Controls whether or not the disk or tape volume or 5  volumes specified in the Mount command are unloaded x  when they are dismounted.  a     .c1.  DCL Mount/SYS$MOUNT;l   J  This section is not a full discussion of the OpenVMS Mount DCL command.  L  Rather it discusses the integration between Branches and the OpenVMS Mount 
  services.E  Under normal usage when an OpenVMS user issues a DCL Mount command, eS  Branches examines the mount request and, if the request is for a device in a data iK  library managed by Branches, Branches will move the requested volume into  K  the specified device.  If the requested volume isnt in the data library,  '  Branches will abort the mount request.mE  OpenVMS allows a user to issue a MOUNT/FOREIGN request that doesnt  N  have a volume label.  If Branches receives such a request Branches will load   the device with scratch media.i *2E  *2Ie *4D   /SYSTEM	Makes the volume public, that is available to all users of the system, as long as the UIC-based volume protection allows them access.  /[NO]UNLOAD	Controls whether or not the disk or tape volume or volumes specified in the Mount command are unloaded when they are dismounted.e  T  /  DCL Mount/SYS$MOUNT  d  This section is not a full discussion of the OpenVMS Mount DCL command.  Rather it discusses the integration between Branches and the OpenVMS Mount services. / Under normal usage when an OpenVMS user issues a DCL Mount command, Branches examines the mount request and, if the request is for a device in a data library managed by Branches, Branches will move the requested volume into the specified device.  IY -f the requested volume isn't in the data library, Branches will abort the mount request.   OpenVMS allows a user to issue a MOUNT/FOREIGN request that doesn't have a volume label.  If Branches receives such a request Branches will load the device with scratch media. *4Eu *2Et *4Dr(  Format	MOUNT device-name [volume-label]  Qualifiers	Notese *4E  *2DtB  /FOREIGN	Indicates that the volume is not in the standard format !  used by the VMS operating system	 *2Eh *2II *4DZb  /FOREIGN	Indicates that the volume is not in the standard format used by the VMS operating system *4Eb *2Ef *4D.  I  m *4E, *2Dt  .c1.Branches Set Drive; *2E2 *2I2 *4D4  Branches Set Drivea *4E  *2Ei *4D    ;  Modifies information about the drives managed by Branches.e&  Format	Branches SET DRIVE device-name  Qualifiers	NotesiJ  /[NO]LABEL[=label]	Specifes the label, if any, of the media in the drive.M  /LIBRARY[=DEFAULT]	Specifies the library whose contents are to be displayed.u *4Ey *2DuP  /[NO]LINKAGE=[position]	Specifies the position which should contain the volume   when unloaded, if any.  *2E  *2Ir *4Dif  /[NO]LINKAGE=[position]	Specifies the position which should contain the volume when unloaded, if any. *4En *2Ei *4Do-  /STATE=state	Specifies one of the following:a%  	DISABLED	The drive cannont be used.s$  	FULL		The drive contains a volume.  	EMPTY	The drive is empty     u *4Ee *2Di  .c1.Branches Set Position;h *2Ee *2I  *4De  Branches Set Position *4Eh *2EO *4DS  C<  Modifies information about the volumes managed by Branches.-  Format	Branches SET POSITION position-numbers  Qualifiers	Notesd>  /[NO]LABEL[=label]	Specifes the label, if any, of the volume.M  /LIBRARY[=DEFAULT]	Specifies the library whose contents are to be displayed.s  /[NO]LINKAGE=[device-name] 4  	Specifies the drive containing the volume, if any.-  /STATE=state	Specifies one of the following: '  	FULL		The position contains a volume.r  	MOUNTED	The volume is mounted,@  /[NO]USAGE[=usage]	Specifies the usage, if any, of this volume:  	BACKUP	Mounted by BACKUP  	SCRATCH	Scratch volume.d  e    *4Ei *2Da  .c1.Branches Set Slot;d *2Ew *2Ie *4De  Branches Set Slot *4E  *2Ea *4Do  s:  Modifies information about the media managed by Branches.%  Format	Branches SET SLOT slot-numbert  Qualifiers	NoteslM  /LIBRARY[=DEFAULT]	Specifies the library whose contents are to be displayed.l-  /STATE=state	Specifies one of the following:V$  	DISABLED	The slot cannont be used.   	FULL		The slot contains media.  	EMPTY	The slot is emptyuB  /[NO]VID[=string]	Specifies the volume id, if any, of this media.  a  i *4Es *2De  .c1.Branches Set Trace; *2Eo *2I  *4D   Branches Set Tracee *4Ea *2Em *4Dd    *4Es *2DhP  Enables or disables the tracing of commands and other internal information for D  a library server.  Use this command as a service and debugging aid.N  Log files are written to BRNCH_SCRATCH.  Error logs have a file extension of 3  ERR and trace logs have a file extension of LOG.  e *2Ei *2Id *4D   Enables or disables the tracing of commands and other internal information for a library server.  Use this command as a service and debugging aid.   Log files are written to BRNCH_SCRATCH.  Error logs have a file extension of ERR and trace logs have a file extension of LOG.   *4Er *2Ei *4Dg  4%  Format	Branches SET TRACE [ON ! OFF] ?  Parameters	on|off  Specifies that tracing is either ON or OFF.a  Qualifiers	Notesr!  /DISABLE=(ALL, QIO, OPCOM, SCSI)o *4E. *2De2  	Disable ALL tracing, or any combination of QIO,   OPCOM, or SCSI tracing. *2Eg *2IE *4DoI  	Disable ALL tracing, or any combination of QIO, OPCOM, or SCSI tracing.r *4Es *2EN *4D	   /ENABLE=(ALL, QIO, OPCOM, SCSI) *4Ei *2Do1  	Enable ALL tracing, or any combination of QIO, o  OPCOM, or SCSI tracing.N  /LIBRARY[=DEFAULT]	Specifies the name of the library whose server is to have   the trace state manipulated.s *2El *2Ie *4DeH  	Enable ALL tracing, or any combination of QIO, OPCOM, or SCSI tracing.j  /LIBRARY[=DEFAULT]	Specifies the name of the library whose server is to have the trace state manipulated. *4Eh *2Ev *4D.  L(  BRANCHES SET TRACE ON is equivalent to:  t'  BRANCHES SET TRACE/ENABLE=(OPCOM,SCSI)L  /  a *4Eo *2D   .c1.Branches Show Contents; *2Ey *2Il *4DS  Branches Show Contentsd *4Eo *2Ee *4Dz  4I  Displays information on the contents of the objects managed by Branches.e  Format	Branches SHOW CONTENTS  Qualifiers	Notesa7  /ALL	All entries in the inventory table are displayed.e *4Ee *2DoB  /COLUMNS=n	Specifies the number of columns for listing contents; ,  either 1, 2, or 3.  The default value is 3. *2Ee *2I  *4DBm  /COLUMNS=n	Specifies the number of columns for listing contents; either 1, 2, or 3.  The default value is 3.  *4Er *2Eo *4Di@  /DRIVE	The state of drives in the inventory table is displayed.<  /FULL	All information in the inventory table is displayed.. *4Em *2De@  /[NO]HEADER	Identifies the data library (with SHOW CONTENTS).  2  Suppressed by /NOHEADER.  The default is /HEADER.S  /MEDIA[=wildcard-name]	Specifies a wild card pattern to be matched with all media o;  names in library inventory.  If wildcard name is omitted, f  the default is '*'. *2Eu *2Io *4D q  /[NO]HEADER	Identifies the data library (with SHOW CONTENTS).  Suppressed by /NOHEADER.  The default is /HEADER.   /MEDIA[=wildcard-name]	Specifies a wild card pattern to be matched with all media names in library inventory.  If wildcard name is omitted, the default is '*'. *4E  *2E; *4DpM  /LIBRARY[=DEFAULT]	Specifies the library whose contents are to be displayed.e *4En *2DbH  /OUTPUT[=filename]	Specifies the file to which the information will be >  written.  If the output file name is omitted, the default is   SYS$OUTPUT.B  /POSITION	Specifies that the volume's physical position is to be   displayed.nC  /SLOT	Specifies that the volume's physical slot location is to be  4  displayed.  For some media there are more than one 0  volume per slot, i.e., optical disk cartridges. *2El *2Ia *4De  /OUTPUT[=filename]	Specifies the file to which the information will be written.  If the output file name is omitted, the default is SYS$OUTPUT.L  /POSITION	Specifies that the volume's physical position is to be displayed.  /SLOT	Specifies that the volume's physical slot location is to be displayed.  For some media there are more than one volume per slot, i.e., optical disk cartridges.a *4Ee *2Et *4Dn-  /VIDS	The bar code information is displayed.r  x0  The Show Contents command displays these codes: *4E  *2DcQ  B	The disk volume was used by BACKUP during a multi-volume sequential disk save  X  operation.  The label displayed may be invalid; to determine the proper label, use the :  Branches Import command on the slot containing the media. *2E  *2ID *4Dt  B	The disk volume was used by BACKUP during a multi-volume sequential disk save operation.  The label displayed may be invalid; to determine the proper label, use the Branches Import command on the slot containing the media.  *4Eh *2Ea *4De  M	The volume is mounted.eQ  U	The volume is unavailable; one of the other surfaces has already been mounted.l"  S	The volume is a SCRATCH volume.B  If no additional information is shown, the volume may be mounted.  l  m *4Eo *2Dg  .c1.Branches Show Version;aH  Displays the current version number of Branches.  When you call us for P  Technical Support, this is one of the first questions that will need an answer !  What version are you using?.  e *2Ee *2It *4D   Branches Show Version  M  Displays the current version number of Branches.  When you call us for Technical Support, this is one of the first questions that will need an answer "What version are you using?".    *4Eo *2Eo *4Dr  Format	Branches SHOW VERSIONE  n  e *4El *2D,  .c1.Branches Shutdown;v *2Et *2Io *4D   Branches Shutdown *4E  *2EE *4D	  c *4E  *2DuP  Stops the Branches library server for a given library.  If the library name is 3  omitted, the DEFAULT library server is terminated.e *2E  *2IE *4Dn  Stops the Branches library server for a given library.  If the library name is omitted, the DEFAULT library server is terminated. *4E  *2Et *4Dm'  Format	Branches SHUTDOWN [libraryName]e  r    *4Eo *2Do  .c1.Branches Tune;4 *2E/ *2IH *4Da  Branches Tune *4Eb *2E  *4D   e *4EY *2DMN  Sets the account quotas for the current account for best use by VMS BACKUP.  G  Use this command whenever AUTOGEN is run and the values of the SYSGEN CD  parameters WSMAX or CHANNELCNT are changed; the account(s) running   BACKUP should be TUNEd. *2Ed *2I  *4D   Sets the account quotas for the current account for best use by VMS BACKUP.  Use this command whenever AUTOGEN is run and the values of the SYSGEN parameters WSMAX or CHANNELCNT are changed; the account(s) running BACKUP should be TUNEd. *4Es *2Eh *4D   n  Format	Branches TUNEo     m *4Ee *2Da  .c1.Branches Unload;t *2Ee *2Id *4Dt  Branches Unload *4Ei *2E  *4Da   "  Unloads a volume from a drive.     w%  Format	Branches UNLOAD [device-name]t  Qualifiersd *4E. *2DtM  /LIBRARY[=DEFAULT]	Specifies the name of the library whose drives are to be t
  unloaded.  e/  .c.Chapter 6, Third Party Product Integration;s  .c1.Using Branches and Backup;lR  All Backup operations that request media for writing record the correct label of   the media.   .c2.Sequential Disk Saves;kP  Before starting your BACKUP procedures, initialize all disks to be used with a V  cluster factor of 1.  You may experience unpredictable results if you do not do so.  K  Issue your backup command.  We strongly recommend that when you backup to  J  disk, e.g., /IMAGE or backups to sequential disks, use the /NOINITIALIZE H  qualifier (since Branches does not know you are performing a backup).    eO  When the disk is full, BACKUP notifies Branches that a new volume is needed.  lO  Branches selects a scratch volume from the inventory table, removes the disk, nJ  replaces it in the storage bay, places the volume in the drive and tells O  BACKUP to continue.  If a scratch volume is not available, Branches stops the fO  backup.  Unload the volume in the drive (Branches Unload) because Branches is qL  not notified when BACKUP terminates.  Although this is not required, it is   strongly recommended. *2Eh *2Ic *4D V  /LIBRARY[=DEFAULT]	Specifies the name of the library whose drives are to be unloaded.  	  Chapter 6	Trouble Shootinge  Problems Getting Started  / So, you did everything we told you to do, you saw the hardware when you were at the console prompt, you used the configuration utility to specify your configuration file enty, all your devices were seen by OpenVMS, you ran the startup command proce0 -dure and your reward for all this great effort:  	the server doesn't come up. w  You will recognize this because one or both of the following happen when you run the system startup command procedure:e"  	A BRNCH-E-NOSERVER error occursf  	Processes of the form BRNCH-librarayName do not appear when you do a SHOW SYSTEM at the DCL prompt.&  The first thing to do is don't panic! / The second thing to do is to verify that your configuration table enty for your library is accurate.  Common mistakes, especially if you created your configuration table entry manually instead of using the Configuration File Utility (BRNCH_ SYSTEM:( -BRNCH -CONFIGURATION-UTILITY.COM) are :s  	Embedded spaces in configuration entry lines other than the white space between the keywords and the parameters. A  	The configuration entry lines must have no leading whitespace.   	The drives specified in the DRIVE configuration entry do not exist, are not online, or OpenVMS will not return a full device name for them.  	The control device specified in the CONTROL configuration entry does not exist, is not online, or OpenVMS will not return a full device name for it.a / If you find one of these errors, correct it and run the Branches startup command procedure.  If you are using a CMD Technologies controller, you may not have properly configured the controller.  The Cobra and CDI 4xxx series do not require any spec /fic configuration to enable SCSI pass through.  To the best of our knowledge, all other controllers do require some form of controller specific configuration to enable SCSI pass through.  CMD Technologies calls SCSI pass through SCSI Format Online.  / Check your controller documentation for the specific mechanism used to enable SCSI Format Online.  Then verify that the controller is, indeed, properly configured.  Also, call CMD Technologies technical support and verify that the firmware in the c /ontroller is the latest and greatest (not necessary for controllers purchased from Acorn Software).  This step is especially important if you are using an older CMD Technologies controller, e.g., CQD series, purchased prior to 1994.  If the firmware - requires upgrading, you should do this as a matter of course.  CMD Technologies will be glad to do it for you (for a fee) or to send you the necessary ROMs to install (for a smaller fee).h / OK, the controller is properly configured and up to date, the configuration enty is correct, all the necessary devices are present, and OpenVMS returns full device names for all of them.  You may have not configured your data library properly.  Che /ck the Applications Notes chapter, below, for details on how to configure your specific hardware.  If we haven't included details for your data library it is because, to the best of our knowledge, it does not require any specific configuration for c -ompatibility with Branches.  Make sure to check the release notes that may have come with yourBranches kit.  Any details on new hardware support are included there and not here, pending the next major documentation revision cycle.a / The third thing to do is to look in the Branches log file (BRNCH_SCRATCH:libraryName-OUTPUT.LOG and BRNCH_SCRATCH:libraryName-ERROR.LOG) for more information.  The Branches log file contains the various tracing  requested by the user and process teI -rmination information.  You did remember to turn tracing on, didn't you?, / In any event, either print or edit the file and see what happened down towards the end of the file.  One of the most common problems is a corrupt inventory table (BRNCH-E-CORRUPTIT) error.  This means that, for some reason, Branches either created  /a corrupt inventory table or the inventory table became corrupt on its own, possibly due to a system crash or a bug in RMS both of which we have seen.  The simplest solution for this is to delete the inventory table (BRNCH_SCRATCH:libraryName.INVENT -ORY_TABLE) and restart the server using the system startup command procedure (SYS$STARTUP:BRNCH-STARTUP.COM).  See the section on Starting Branches, above. / If you are trying to use an old CMD Technologies controller (purchased prior to 1993) you may see an access violation in the log file just after a SCSI Mode Sense Request.  Are you sure you checked the firmware revision to make sure you have the la -test and greatest in that board?  We have only seen this specific problem with relatively early version of the SCSI Format Online feature.  The latest releases of all CMD firmware (as of this writing) are known to work properly.  / If you see specific SCSI errors in your log file there is frequently a lot of information available in the data library manufacturer's documentation that you received with your data library.  If it is not there, contact the manufacturer's technical / support to see what the SCSI error is, you may have a problem with your data library.  We wish that we could provide you with a detailed explaination of the errors for each data library we support, but this manual would be several hundred pages lon` -g if we did and always out of date since we don't write the data library documentation as well.  Once you have determined that none of the above are the case, you probably have stumbled across one of our undocumented "features".  Further, that feature probably shouldn't be there.  You will need to contact Acorn Software.j  Since you're having problems getting started, we will need to see the following information (physically):  	the configuration file with the entry for the specific data library marked.  This file is pointed to by the logical name BRNCH_CONFIGURATION:U  	the entire contents of the output log file (BRNCH_SCRATCH:libraryName-OUTPUT.LOG).i  	the type of controller you are using (if this is a CMD Technologies controller, please make sure you know the firmware revision number)5  	the version of OpenVMS upon which you are running.o  	the output of a SHOW DEVICE/FULL for each relavent device in the configuration file entry for the data library, i.e., all drives in the DRIVE line and the device in the CONTROL line.TG  	the scsi id's for all the drives and the robot in your data library. 2  	the type of data library you are trying to use.?  Collect all of this information and send it to Acorn Software: (  by electronic mail: support@acornsw.com  by fax: (508) 568-1133s9  by physical mail: 267 Cox Street, Hudson, Ma. 01749, USAhS  along with a cover letter detailing your problem and how to contact you in return.e  Then, and only then, call our support line and let us know that the information we need to help you is on the way.  Technical support at Acorn Sofware may be reached at:  	(508) 568-1618 x5m:  Someone from Acorn will be in touch within 1 working day.  We know this is a lot of information to gather, but you will be doing it one way or another, so you might as well do it up front.  We'll be able to help you faster that way.  Problems After Getting Started   These generally fall into three distinct catagories, licensing, Branches  dieing because of hardware errors, and Branches  dieing because of software errors and configuration problems.h  Configuration problems tend to show up as Branches  working, but when you attempt to mount the devices, you see errors of the form:  Volume not software enabled  4 / This is generally due to an incorrect setting of the LOAD-TIMEOUT in the configuration file for your library.  Acorn Software selects reasonable values for the amount of time drives take to load, but drive specifications change without notificationR -.   Contact Acorn Software for the correct value for your LOAD-TIMEOUT parameter. / In all other cases, you will need to look in the output log (BRNCH_SCRATCH:libraryName-OUTPUT.LOG) to sort out what's happening.  If there is a licensing problem, you should see a license error message (BRNCH-E-NOLICENSE), perhaps with some explana -tory text.  If you have not applied for, received, and installed your permanent license key, you had better do so in a hurry.  See the details on licensing Branches elsewhere in this document.r / Acorn Software does not use Digital's LMF for licensing our products.  As a consequence, our licenses are sensitive to things like the ethernet address, processor type, SCS node name, SCS node number, clustering state, and several others.   If you  /have changed any major piece of hardware in your system or made the transition from non-clustered to clustered or clustered to non-clustered you will have to get a new license for your copy of Branches.  See the details on licensing Branches  elsewh -ere in this document. / Occasionally, and we are still trying to track down why, the license system simply stops working for a product.  Frequently you can fix this by simply reinstalling the key for the product.  You did keep the key form we sent to you, didn't you?  If  -this fails to work, we will need to know a great deal about your system so that we can examine the licensing algorithms in the context of your specific installation.i  If none of the above work, you will have to contact Acorn Software.  We will need the following details: }  	the entire contents of the output log file (BRNCH_SCRATCH:libraryName-OUTPUT.LOG and BRNCH_SCRATCH:libraryName-ERROR.LOG).h8  Collect this information and send it to Acorn Software:(  by electronic mail: support@acornsw.com  by fax: (508) 568-1133r9  by physical mail: 267 Cox Street, Hudson, Ma. 01749, USAaS  along with a cover letter detailing your problem and how to contact you in return.m  Then, and only then, call our support line and let us know that the information we need to help you is on the way.  Technical support at Acorn Sofware may be reached at:  	(508) 568-1618 x5 :  Someone from Acorn will be in touch within 1 working day. / Hardware errors are somewhat more difficult to deal with.  We have not dealt with the generic problem of robotics failure particularly well in Branches.  We continue to refine our techniques, but there comes a time when the hardware is so broken (b2 -y our lights) that we cannot continue to operate. / If you have SCSI tracing on, your output log will be of use to Acorn Software in further studying the failure modes of the various data libraries supported by Branches.  It will also be of use to your data library hardware support personnel.  Pleas# -e send it to us as detailed above.e / Software errors occasionally get past our testing regimen.  When unexplainable crashes of Branches occur, they leave process dumps (BRNCH.DMP) in directory from which Branches was started.  This and other information needs to be sent to Acorn SoftwX -are as per the instructions below in the chapter dealing with Software Problem Reports.  Advanced Trouble Shooting"  Running Branches AXP 2000 systems  There appear to be a number of AXP 2000 system options which don't interoperate with the Digital supplied GKDRIVER.  Without a properly working GKDRIVER, Branches cannot function.  The symptoms of this are as follows:|  	The startup command procedure runs to completion but the Branches server never gets to the point of really being started.  	The log for the library held in BRNCH_SCRATCH: have, near the bottom, the log for a single SCSI command, usually a test unit ready, and nothing else.A  	No error information of any kind is recorded in the log files. i  As near as we can tell, the SCSI command to the robot we use goes into the GKDRIVER but never comes out.hv  You should report this problem to Digital and request that they contact us to work toward a solution to this problem.l  We do not know if there is as solution from Digital, but we cannot provide one for this particular problem.  Inventory table corruptionr / Occasionally, and the causes are unknown, the inventory table may become corrupt.  You can recognize this by looking in the log files when you try to start Branches and it fails to work and there is text near the bottom of the log file indicating tF -hat Branches found some form of inconsistency in the inventory table.  If this happens, the only way to repair the problem is to shutdown Branches (if it hasn't already crashed), delete the inventory table for the library, restart Branches, and repopulate the inventory table.  Hardware Problems / Should hardware errors occur, information necessary to your hardware vendor is captured in the Branches log files (BRNCH_SCRATCH:libraryName-OUTPUT.LOG and BRNCH_SCRATCH:libraryName-ERROR.LOG).  This information appears in the log files following a - "Request Sense" SCSI command.r  Wed Nov 15 17:56:54 1995:+  SCSI Command = Request Sense (03 (00, 03)),'  SCSI Command body = 00, 00, 00, 0e, 00n  p  SCSI Sense Data#          Valid = 0, Error Code = 70a          Segment Number = 005          FileMk = 0, EOM = 0, ILI = 0, Sense Key = 06a!          Information = 0000, 0000c$          Additional Sense Length = 82          Command Specific Information = 0000, 0000#          Additional Sense Code = 29d-          Additional Sense Code Qualifier = 00i%          Sense Key Specific Valid = 0   e / The information reported is defined in the ANSI SCSI specification.  If you do not have a copy of this specification you may contact your library hardware vendor for the details associated with your specific error.  A version of a draft of the http /://abekas.com:8080/SCSI2/SCSI-2 Specification (Draft X3T9.2 Rev 10L) is available over the world wide web.  The key pieces of information that will need to be communicated with your library hardware vendor are the http://abekas.com:8080/SCSI2/SCSI2- /08.html#tab69Sense Key, http://abekas.com:8080/SCSI2/SCSI2-08.html#tab71Additional Sense Code and http://abekas.com:8080/SCSI2/SCSI2-08.html#tab71Additional Sense Code Qualifiers.  Do not contact Acorn Software directly.  If your library hardware ve\ -ndor has any specific questions concerning the operation of Branches, have them contact us.  w,  Chapter 7, Third Party Product Integration;  Using Branches and Backup\  All Backup operations that request media for writing record the correct label of the media.  Sequential Disk Saves;   Before starting your BACKUP procedures, initialize all disks to be used with a cluster factor of 1.  You may experience unpredictable results if you do not do so.  e  Issue your backup command.  We strongly recommend that when you backup to disk, e.g., /IMAGE or backups to sequential disks, use the /NOINITIALIZE qualifier (since Branches does not know you are performing a backup).       / When the disk is full, BACKUP notifies Branches that a new volume is needed.  Branches selects a scratch volume from the inventory table, removes the disk, replaces it in the storage bay, places the volume in the drive and tells BACKUP to continue. -  If a scratch volume is not available, Branches stops the backup.  Unload the volume in the drive (Branches Unload) because Branches is not notified when BACKUP terminates.  Although this is not required, it is strongly recommended. *4E  *2Ee *4D !  Example of sequential disk savesr  MOUNT/FOREIGN drive label8  Mount the first volume in the sequential disk save set. *4Eo *2Dt4  BACKUP/NOINITIALIZE filelist drive:[000000]saveset-  name/SAVESET/qualifiers *2Ep *2Il *4DgK  BACKUP/NOINITIALIZE filelist drive:[000000]saveset-name/SAVESET/qualifierse *4Eo *2Ew *4D   Issue the backup command.  DISMOUNT drive	6  Dismount the drive to free it for further use by VMS.  Branches UNLOAD drive	r *4E  *2DeO  Replace the volume in the library.  This is unnecessary if only one volume is w  used in the backup operation.  .c2.Sequential Disk Restores;O  Branches provides a way to interact with BACKUP during restores.  --  use the tD  Branches UNLOAD and LOAD commands. Because BACKUP does not specify L  the required volume label Branches cannot automate the removal and loading   of volumes during restores.   yG  When BACKUP requires another volume, issue an UNLOAD command to empty  L  the drive, a LOAD command to place the next volume in the drive, and a DCL L  REPLY command to tell BACKUP that the next volume in the save set has been M  made available.   You must unload the final volume in the save set with the f  Branches UNLOAD command.a *2Ei *2In *4DDl  Replace the volume in the library.  This is unnecessary if only one volume is used in the backup operation.  Sequential Disk Restoresd / Branches provides a way to interact with BACKUP during restores.  --  use the Branches UNLOAD and LOAD commands. Because BACKUP does not specify the required volume label Branches cannot automate the removal and loading of volumes during restores.  -  d / When BACKUP requires another volume, issue an UNLOAD command to empty the drive, a LOAD command to place the next volume in the drive, and a DCL REPLY command to tell BACKUP that the next volume in the save set has been made available.   You must uI -nload the final volume in the save set with the Branches UNLOAD command.s *4Et *2En *4Dt$  Example of sequential disk restores  MOUNT/FOREIGN drive label	m8  Mount the first volume in the sequential disk save set. *4Et *2Da2  BACKUP drive:[000000]saveset-name/SAVESET output 
  /qualifiers	r *2Es *2I  *4Do>  BACKUP drive:[000000]saveset-name/SAVESET output /qualifiers	 *4En *2E  *4Dg  Issue the backup command.  Branches UNLOAD drive	s *4EC *2DuO  Replace the volume in the library.  This is unnecessary if only one volume is n  used in the backup operation. *2Ef *2I  *4Dml  Replace the volume in the library.  This is unnecessary if only one volume is used in the backup operation. *4En *2E  *4Do  Branches LOAD drive volume	 *4E  *2DnQ  Load the next volume in the save set in the drive.  Any of the various Branches a  LOAD commands may be used.  *2Ea *2Io *4Dfk  Load the next volume in the save set in the drive.  Any of the various Branches LOAD commands may be used.t *4Et *2Eo *4DN  DISMOUNT drive	6  Dismount the drive to free it for further use by VMS.  Branches UNLOAD drive	y  Empty the drive.e *4Er *2De  .c2.Multi-volumeTape Saves;Q  Branches tape save operations are simpler than the disk saves.  In the simplest tK  case, you issue a BACKUP command with the /LABEL qualifier specifying the eO  volume upon which to start saving data.  The starting volume does not need to oG  be mounted.  Branches mounts the volume in response to BACKUP's mount c	  request.eK  During output processing of a multi-volume save set, if BACKUP requests a CO  volume that is not available in inventory Branches aborts the mount request.   Q  BACKUP ignores the abort and requests the mount again.  A loop results.  To get  M  around this potential problem, make sure that all members of a multi-volume yJ  save set are present in inventory before beginning any multi-volume save   operations.=  If you have specified the BACKUP command with the /NOREWIND tI  qualifier,  you must populate the data library with appropriately named iM  volumes for any overflow.  BACKUP does not initialize tape volumes when the rM  /NOREWIND qualifier is used.  Branches attempts to mount a labelled scratch  N  volume in response to a request from BACKUP for a new volume.  This causes a J  BACKUP  error because the tape labels do not match.  Branches aborts the   BACKUP operation.I  If you have specified the  BACKUP operation with the /REWIND qualifier, nS  you can specify the set of volumes to use via the /LABEL qualifier or omit them.  rJ  Branches attempts to mount either the named volume or a labelled scratch L  volume if the named volume doesn't exist in inventory.  BACKUP initializes 2  the tape and continues with the BACKUP operation. *2Eo *2It *4Do  Multi-volumeTape Saves  / Branches tape save operations are simpler than the disk saves.  In the simplest case, you issue a BACKUP command with the /LABEL qualifier specifying the volume upon which to start saving data.  The starting volume does not need to be mounted.  Bra? -nches mounts the volume in response to BACKUP's mount request.r / During output processing of a multi-volume save set, if BACKUP requests a volume that is not available in inventory Branches aborts the mount request.  BACKUP ignores the abort and requests the mount again.  A loop results.  To get around this pote -ntial problem, make sure that all members of a multi-volume save set are present in inventory before beginning any multi-volume save operations.e / If you have specified the BACKUP command with the /NOREWIND qualifier,  you must populate the data library with appropriately named volumes for any overflow.  BACKUP does not initialize tape volumes when the /NOREWIND qualifier is used.  Branches a -ttempts to mount a labelled scratch volume in response to a request from BACKUP for a new volume.  This causes a BACKUP  error because the tape labels do not match.  Branches aborts the BACKUP operation. / If you have specified the  BACKUP operation with the /REWIND qualifier, you can specify the set of volumes to use via the /LABEL qualifier or omit them.  Branches attempts to mount either the named volume or a labelled scratch volume if the named vh -olume doesn't exist in inventory.  BACKUP initializes the tape and continues with the BACKUP operation. *4Ed *2Ee *4Dr#  Example of multi-volume tape savesr  MOUNT/FOREIGN drive label	f *4El *2DnQ  Mount the first volume in the sequential disk save set.  This may be omitted if ,%  the /LABEL BACKUP qualifier is used.a *2E  *2Iu *4Deu  Mount the first volume in the sequential disk save set.  This may be omitted if the /LABEL BACKUP qualifier is used.e *4E  *2En *4Dt9  BACKUP/LABEL=label filelist drive:saveset-name/SAVESET -h
  /qualifiers	e *4Et *2DrQ  Issue the backup command.  These are not the only qualifiers that may be used.   H  The effect of the BACKUP command on Branches varies depending upon the   particular combination. *2Eu *2Ir *4D.  Issue the backup command.  These are not the only qualifiers that may be used.  The effect of the BACKUP command on Branches varies depending upon the particular combination.t *4E  *2E  *4Dh  DISMOUNT drive	 *4E  *2DhN  Dismount the drive to return the last volume of the multi-volume save set to 5  inventory and free the drive for further use by VMS.h   .c2.Multi-volume Tape Restores;L  Branches restores work in much the same way as tape saves.  Use the /LABEL S  qualifier if the label of the volume being processed is not the default  (derived l  from the save set name).hJ  During input processing of a multi-volume save set, if BACKUP requests a O  volume that is not available in inventory Branches aborts the mount request.  CQ  BACKUP ignores the abort and requests the mount again.  A loop results.  To get iM  around this potential problem, make sure that all members of a multi-volume nM  save set are present in inventory before beginning any multi-volume restore    operations.  .c1.Using Branches and Qfile;  This section under development    .c1.Using Branches and TapeSys;   This section under development.M  Branches has been made compatible with TapeSys.  This allows data libraries mN  to be supported without intervention of the JB product provided with TapeSys M  and to be generally useful for a wide variety of other OpenVMS applications  .  above and beyond those inherent with TapeSys."  .c1.Using Branches and Hierarchy;   This section under development.P  Conformance testing has demonstrated that Branches can be used to control data ;  libraries used as inswap and outswap devices by Hierarchy.   .c1.Using Branches and SLS;L  Branches now directly supports integration with Digitals SLS.  AUTOSELECT U  is fully support.  If Branches is to be used to select scratch volumes for SLS, the wL  SLS database and Branches inventory table must be kept synchronized, i.e., J  volumes that can be selected by SLS must be imported into an appropriate J  library with the appropriate volume labels.  A sample TAPESTART.COM that 8  allows integration of SLS with Branches is provided in: *2Ey *2Iw *4De  Dismount the drive to return the last volume of the multi-volume save set to inventory and free the drive for further use by VMS.  Multi-volume Tape Restores   Branches restores work in much the same way as tape saves.  Use the /LABEL qualifier if the label of the volume being processed is not the default  (derived from the save set name). / During input processing of a multi-volume save set, if BACKUP requests a volume that is not available in inventory Branches aborts the mount request.  BACKUP ignores the abort and requests the mount again.  A loop results.  To get around this poten -tial problem, make sure that all members of a multi-volume save set are present in inventory before beginning any multi-volume restore operations.w *4Em *3Dn  Using Branches and BACPLUSr / Branches if fully compatible with BACPLUS version 3.2 and up.  Simply install Branches and BACPLUS and define your backup policies and strategies.  Branches will keep BACPLUS supplied with tapes for handling your lights out backup and hands off fil -e restores. *3Ea *3Ir *4Ds  Using Branches and SYSWAREt  Branches is fully compatible with SYSWARE version 3.2 and up.  Branches is not compatible with earlier versions of SYSWARE (aka BAC/Plus).  You must upgrade to SYSWARE version 3.2 or later to obtain Branches compatibility.  C / To use Branches and SYSWARE, simply install both products, acquire the necessary keys to run SYSWARE from Professional Software, Inc., and define your backup policies and strategies.  Branches will keep SYSWARE supplied with tapes for handling your0 - lights out backup and hands off file restores.  Recovery of lost files, directories, or entire disks is a matter of a few keystrokes and due to the integration between Branches and SYSWARE require no operator involvement unless the necessary tape is not in the library.  In this event, you must use the Branches IMPORT command to put the necessary tape in the library and make it known to Branches prior to making the SYSWARE restore request. / There is one known incompatibility between SYSWARE and Branches.  You cannot utilize Branches to initialize tapes using the PREINIT.COM command procedure produced by SYSWARE.  You must initialize tapes manually using the Branches IMPORT/INITIALIZE k -command.  This is problem is being addressed and will be fixed in a later version of Branches and SYSWARE.N *4Ec *3Ed *4D2  Using Branches and TapeSysv   This section under development. / Branches has been made compatible with TapeSys.  This allows data libraries to be supported without intervention of the JB product provided with TapeSys and to be generally useful for a wide variety of other OpenVMS applications above and beyond th -ose inherent with TapeSys.t  Using Branches and Hierarchyf   This section under development.  Conformance testing has demonstrated that Branches can be used to control data libraries used as inswap and outswap devices by Hierarchy.  Using Branches and SLSe / Branches now directly supports integration with Digital's SLS.  AUTOSELECT is fully support.  If Branches is to be used to select scratch volumes for SLS, the SLS database and Branches inventory table must be kept synchronized, i.e., volumes that c -an be selected by SLS must be imported into an appropriate library with the appropriate volume labels.  A sample TAPESTART.COM that allows integration of SLS with Branches is provided in: *4Eo *2E  *4Di8  	SYS$COMMON:[SYSHLP.EXAMPLES.BRANCHES.SLS]TAPESTART.COM *4E  *2DDG  The settings of SLS variables that are required by Branches are fully s  documented there."  .c1.Using Branches and HyperTape; *2E  *2I  *4D X  The settings of SLS variables that are required by Branches are fully documented there.  Using Branches and HyperTape  *4E  *2E  *4Dc   This section under development. *4Ea *2D H  HyperTape has been made compatible with Branches.  This allows archive I  management for Unix, IBM MVS, Macintosh, and a variety of other systems.e *2E  *2In *4Dd  HyperTape has been made compatible with Branches.  This allows archive management for Unix, IBM MVS, Macintosh, and a variety of other systems. *4EM *2EB *4De  N *4Ed *2Dy.  .c.Chapter 7, Application and Hardware Notes;L  This chapter details for the application developer and system manager some <  unusual aspects of Branches software.  Those libraries are: *2EA *2Iu *4De*  Chapter 8, Application and Hardware Notes  This chapter details for the application developer and system manager some unusual aspects of Branches software.  Those libraries are:e *4E  *2En *4Dp  	Cipher MiniLibrary   	Digital THZ27 *4EC *2Ie *4Ds  	Exabyte 10e *4E  *2Ev *4Dl-  	All Hewlett-Packard Optical Disk Librariest  	IDE Models 7100 and 9000r
  	Kodak 560Et
  	NKK 556  	Olympus Deltis OLS-10  	QualStar Q7 DLT Tape Libraryl *4Ea *2DrF  Additionally, we have noted here hardware configuration and specific D  information that we found helpful to know in testing with Branches.  .c1.OpenVMS/AXP;UG  The volume name is omitted from Dismount notification messages.  As a iN  consequence, Branches leaves media in drives until a request for media other J  than that in the drive is received.  This behavior is caused by a bug in =  OpenVMS and will disappear when the bug in OpenVMS is fixed.r  .c1.OpenVMS/AXP 6.1;aK  Digital introduced a feature into OpenVMS/AXP 6.1.  It can take up to 5 aQ  minutes for Mount to notice that a drive does not contain media.  This directly oQ  affects the speed with which Branches can respond to mount requests.  This is a v4  bug in OpenVMS and cannot be addressed by Branches.1  .c1.Writing programs to integrate with Branches;eN  Branches utilizes a little known feature of OpenVMS which allows an operator P  to place a requested volume in a drive other than the requested drive and then N  substitute the drive selected by the operator for the one requested by the P  program.  All programs should therefore be prepared for the drive specified in K  their mount request to be different from the one upon which the requested e  volume is actually mounted.J  This is accommodated by always specifying that a logical name be defined Q  upon completion of the mount request which will translate to the drive actually  M  containing the media.  The program (DCL or otherwise) must use that logical sM  name for all operations refering to the physical drive containing the media.oL  In the event that this is not possible, drive substitution may be disabled ;  through use of the DRIVE-SUBSTITUTION configuration entry.pM  Many programs frequently assume that they are the only programs utilizing a fO  specific drive.  Further, they assume that once a volume is placed in a drive  1  that that volume will remain there for all time.wQ  This is never the case with Branches.  Volumes remain in drives only as long as tO  the drives are mounted or allocated.  Once a volume has been dismounted it is AM  placed back into inventory and is no longer in the drive.  Programs must be pO  written to accommodate this behavior, that of a smart and aggressive operator r5  whose job it is to keep hardware maximally utilized.B   .c1.IDE Model  Library Systems;,  .c1.IDE Model 7100 Personal Library System;R  When the operator aborts an import cartridge request in this library, the server Q  detects the abort but cannot clear the pending import in the library hardware.   P  To clear the hardware condition, turn the power to the library off and then on.L  When a cartridge is exported from the library, the hardware move operation L  does not complete until the media is removed from the mailbox.  Only after E  media has been removed will the server respond to Branches commands.AO  This library uses the mailbox slot to store the 10th cartridge in inventory.  iH  Branches attempts to distribute wear evenly across the contents of the N  inventory and will place a cartridge in the 10th slot.  This may result in a N  situation in which you cannot import or export your media from the library.    The work around is. *2Es *2Ie *4Du+  	Spectralogic 4000 and 6000 Tape Librarys   Additionally, we have noted here hardware configuration and specific information that we found helpful to know in testing with Branches.O9  AXP 150 processors with Adaptec AHA1742 SCSI Controllersa  It appears that the Adaptec AHA1742 and the Digital GKDRIVER do not support SCSI LUNs other than 0.  This makes use of all libraries using these LUNs unusable.  OpenVMS/AXP / The volume name is omitted from Dismount notification messages.  As a consequence, Branches leaves media in drives until a request for media other than that in the drive is received.  This behavior is caused by a bug in OpenVMS and will disappear w! -hen the bug in OpenVMS is fixed.e  OpenVMS/AXP 6.1 / Digital introduced a "feature" into OpenVMS/AXP 6.1.  It can take up to 5 minutes for Mount to notice that a drive does not contain media.  This directly affects the speed with which Branches can respond to mount requests.  This is a bug in OpenVMS& - and cannot be addressed by Branches.,  Writing programs to integrate with Branches / Branches utilizes a little known feature of OpenVMS which allows an operator to place a requested volume in a drive other than the requested drive and then "substitute" the drive selected by the operator for the one requested by the program.  All p -rograms should therefore be prepared for the drive specified in their mount request to be different from the one upon which the requested volume is actually mounted. / This is accommodated by always specifying that a logical name be defined upon completion of the mount request which will translate to the drive actually containing the media.  The program (DCL or otherwise) must use that logical name for all operat: -ions refering to the physical drive containing the media.  In the event that this is not possible, drive substitution may be disabled through use of the DRIVE-SUBSTITUTION configuration entry.  Many programs frequently assume that they are the only programs utilizing a specific drive.  Further, they assume that once a volume is placed in a drive that that volume will remain there for all time.  / This is never the case with Branches.  Volumes remain in drives only as long as the drives are mounted or allocated.  Once a volume has been dismounted it is placed back into inventory and is no longer in the drive.  Programs must be written to accu -ommodate this behavior, that of a smart and aggressive operator whose job it is to keep hardware maximally utilized.l  IDE Model  Library Systemss'  IDE Model 7100 Personal Library Systemn  When the operator aborts an import cartridge request in this library, the server detects the abort but cannot clear the pending import in the library hardware.  To clear the hardware condition, turn the power to the library off and then on.g  When a cartridge is exported from the library, the hardware move operation does not complete until the media is removed from the mailbox.  Only after media has been removed will the server respond to Branches commands.a / This library uses the mailbox slot to store the 10th cartridge in inventory.  Branches attempts to distribute wear evenly across the contents of the inventory and will place a cartridge in the 10th slot.  This may result in a situation in which youJ - cannot import or export your media from the library.  The work around is *4Er *2Eo *4DAA  1.  export the cartridge in the 10th slot (positions 18 and 19) u0  2.  import or export the desired cartridge, and4  3.  import the cartridge formerly in the 10th slot.P  In this library, there are two configuration items that must be set.  They are:  	CHANGER EJECT and  	ANSI ST SCSI2 *4Eh *2DnJ  CHANGER EJECT must be set to Y.  See the IDE Model 7100 Personal Library D  System Technical Reference Manual for instructions on changing the   configuration.gJ  ANSI ST SCSI2 must be set to Y.  See the IDE Model 7100 Personal Library D  System Technical Reference Manual for instructions on changing the   configuration.OK  If you are connecting your IDE 7100 data library to a VAX or AXP using an cJ  embedded SCSI bus, you must be aware that the Branches Import and Export I  commands are considered by the data library to be part of a single SCSI iJ  command.  This means that you must adjust the SCSI-TIMEOUT configuration J  line to the maximum time the data library will wait for cartridges to be M  inserted (Branches Import) or removed (Branches Export).  Remember too that nP  until a cartridge is either placed in the mailbox (Branches Import) or removed G  from the mailbox (Branches Export) no other Branches commands will be S	  honored.l  sR  An implication of this hardware design is that there is no way to abort either a J  Branches Import or Export operation.  If you must abort either, then the   following is done:y *2Eh *2Ie *4Dr  CHANGER EJECT must be set to Y.  See the IDE Model 7100 Personal Library System Technical Reference Manual for instructions on changing the configuration.r  ANSI ST SCSI2 must be set to Y.  See the IDE Model 7100 Personal Library System Technical Reference Manual for instructions on changing the configuration.. / If you are connecting your IDE 7100 data library to a VAX or AXP using an embedded SCSI bus, you must be aware that the Branches Import and Export commands are considered by the data library to be part of a single SCSI command.  This means that you / must adjust the SCSI-TIMEOUT configuration line to the maximum time the data library will wait for cartridges to be inserted (Branches Import) or removed (Branches Export).  Remember too that until a cartridge is either placed in the mailbox (Brancf -hes Import) or removed from the mailbox (Branches Export) no other Branches commands will be honored.     An implication of this hardware design is that there is no way to abort either a Branches Import or Export operation.  If you must abort either, then the following is done:  *4E  *2E  *4Dr8  1. Abort the Branches EXPORT or IMPORT command with ^Y. *4Ev *2DmO  2. From a fuly priviledge account, use SHOW SYSTEM to identify the server for 2H  the IDE 7100.  Its process name will be of the form BRNCH-libraryName ?  where libraryName is taken from the BRNCH_CONFIGURATION: file.  *2E  *2Im *4D4  2. From a fully privileged account, use SHOW SYSTEM to identify the server for the IDE 7100.  Its' process name will be of the form BRNCH-libraryName where libraryName is taken from the BRNCH_CONFIGURATION: file.r *4E2 *2E2 *4D45  3. Use STOP/ID=processID to stop the server process.h$  4. Cycle power on the IDE 7100 box.K  5. Restart the Branches server using the system startup command procedure.b *4Es *2De'  .c1.Kodak Model  560E Library Systems; L  Is supported only in NKK emulation mode.  You must place your 560E in this Q  mode prior to attempting to start Branches.  See your library documentation for 0	  details.5#  .c1.NKK Model 556 Library Systems;SF  There is a signigicant restriction in the Branches IMPORT and EXPORT P  commands due to the design of the NKK 556 firmware.  Specifically, there is no K  way to abort either operation once they have been begun.  The only way to mE  recover from an unintentional IMPORT or EXPORT command is to do the    following:e *2Ei *2Ie *4D "  Kodak Model  560E Library Systems  Is supported only in NKK emulation mode.  You must place your 560E in this mode prior to attempting to start Branches.  See your library documentation for details.  NKK Model 556 Library Systems / There is a signigicant restriction in the Branches IMPORT and EXPORT commands due to the design of the NKK 556 firmware.  Specifically, there is no way to abort either operation once they have been begun.  The only way to recover from an unintentio5 -nal IMPORT or EXPORT command is to do the following:e *4El *2Ea *4Dl  n/  1. Abort the EXPORT or IMPORT command with ^Y.  *4El *2D O  2. From a fuly priviledge account, use SHOW SYSTEM to identify the server for eK  the N-556.  Its process name will be of the form BRNCH-libraryName where  9  libraryName is taken from the BRNCH_CONFIGURATION: file.e *2Ed *2I  *4Dr  2. From a fuly priviledge account, use SHOW SYSTEM to identify the server for the N-556.  Its' process name will be of the form BRNCH-libraryName where libraryName is taken from the BRNCH_CONFIGURATION: file.u *4Eh *2Ei *4Da5  3. Use STOP/ID=processID to stop the server process. !  4. Cycle power on the N-556 box. K  5. Restart the Branches server using the system startup command procedure.o *4Ei *2De  .c1.Olympus Deltis OLS-10;tT  This library is functionally equivalent to the IDE 7100, see above for details for 6  configuring the IDE 7100 for Branches compatibility. "  .c1.QualStar Q7 DLT Tape Library;K  This library is supported only in Quad7 mode.  See your documentation for m.  details on configuring the Q7 for Quad7 mode.#  .c1.Other Hardware Configurations;s%  .c2.CMD Technology SCSI Controllers; Q  Branches relies on the SCSI pass through features of the CMD SCSI controllers.  oP  The documentation provided by CMD Technologies for their controllers refers to Q  this feature as SCSI Format OnLine.  If your installation is using a CMD SCSI aN  controller check your documentation to determine if anything, and what, must &  be done to enable SCSI Format OnLine. *2EI *2Id *4D0  Olympus Deltis OLS-10  This library is functionally equivalent to the IDE 7100, see above for details for configuring the IDE 7100 for Branches compatibility. o  QualStar Q7 DLT Tape Library x  This library is supported only in Quad7 mode.  See your documentation for details on configuring the Q7 for Quad7 mode.*  Spectralogic 4000 and 6000 Data Libraries  Make sure that the import/export door is open prior to issuing the first import command.  After that, the door will remain in the correct state.i  In order for the bar code information to be correctly maintained by Branches, the bar code reader must be enabled and automatic bar code reading must also be enabled.l  Exabyte 10e  The Exabyte 10e as shipped from the factory is in sequential mode.  Branches will not operate until the library has been configured to be in random mode.  Make this change following the instructions in the documentation provided by Exabyte.h  Other Hardware Configurations!  CMD Technology SCSI Controllers;e / Branches relies on the SCSI pass through features of the CMD SCSI controllers.  The documentation provided by CMD Technologies for their controllers refers to this feature as "SCSI Format OnLine".  If your installation is using a CMD SCSI controllej -r check your documentation to determine if anything, and what, must be done to enable SCSI Format OnLine. *4Ea *2E  *4Ds  CQD Q-Bus to SCSI Controllers *4Em *2DoD  A jumper must be inserted to enable SCSI Format OnLine for the CQD E  controllers.  Check your documentation to determine which jumper is e*  appropriate for your specific controller.F  There appears to be a bug in the CMD Technology CQD controllers that R  occasionally prevents a Mount request from successfully completing.  If you have L  problems with Mount completing and Acorn Software support can come up with L  no other reason, you may have to disable the ability of the CQD to support M  SCSI Disconnect for the tape devices during SCSI command processing.  Acorn rK  Software has only seen this problem with tape data libraries, but CMD has eG  noted that this problem may occur with optical data libraries as well.ye  Note: Turning off SCSI Disconnect will prevent any other SCSI device on that bus from using the bus eQ  until operations are complete.  This may have a serious performance impact.  If .N  you must turn SCSI Disconnect off, you may want to make the library and its *  I/O devices the only devices on that bus. *2Es *2It *4D   A jumper must be inserted to enable SCSI Format OnLine for the CQD controllers.  Check your documentation to determine which jumper is appropriate for your specific controller.  / There appears to be a bug in the CMD Technology CQD controllers that occasionally prevents a Mount request from successfully completing.  If you have problems with Mount completing and Acorn Software support can come up with no other reason, you ma /y have to disable the ability of the CQD to support SCSI Disconnect for the tape devices during SCSI command processing.  Acorn Software has only seen this problem with tape data libraries, but CMD has noted that this problem may occur with optical  -data libraries as well. / Note: 	Turning off SCSI Disconnect will prevent any other SCSI device on that bus from using the bus until operations are complete.  This may have a serious performance impact.  If you must turn SCSI Disconnect off, you may want to make the library4 - and its' I/O devices the only devices on that bus. *4Ei *2E, *4Ds  CBI BI to SCSI Controllersa *4Ec *2DtN  The on board configuration utility must be used to enable SCSI Format OnLine O  for the CBI controllers.  Check your documentation to determine how to enable t1  SCSI Format OnLine for your specific controller.m *2E  *2I  *4De  The on board configuration utility must be used to enable SCSI Format OnLine for the CBI controllers.  Check your documentation to determine how to enable SCSI Format OnLine for your specific controller. *4Et *2Ed *4Db1  CDI, Cobra, Hawk and Trident DSSI/CI Controllersy *4Ew *2DlN  These CMD Technology controllers have pass through built in at the factory.  N  However, versions of the firmware for these controllers prior to revison X50 L  may not work fully.  Check your controller firmware to make sure that your *  version is at least this level or higher.  .c2.Tape Data Libraries;aI  When connecting a tape data library to an OpenVMS system using a CMD TM rQ  (tape and disk) controller, e.g., CQD223-TM, configure the data library so that 4N  the autochanger SCSI address is in the range 0..3 and the tape drive(s) have N  SCSI addresses in the range 4..7.  If this is not possible, consult your CMD 5  manual for instructions on controller configuration.  *2Eo *2I1 *4Dr / These CMD Technology controllers have pass through built in at the factory.  However, versions of the firmware for these controllers prior to revison X50 may not work fully.  Check your controller firmware to make sure that your version is at least - this level or higher.d  Tape Data Libraries;y / When connecting a tape data library to an OpenVMS system using a CMD TM (tape and disk) controller, e.g., CQD223-TM, configure the data library so that the autochanger SCSI address is in the range 0..3 and the tape drive(s) have SCSI addresses in to -he range 4..7.  If this is not possible, consult your CMD manual for instructions on controller configuration.B *4Ee *2Eo *4Do  Cipher MiniLibrary L7A-42X  *4E  *2DrL  The Cipher MiniLibrary L7A-42X is implemented as two LUNs, 0 is the drive, H  1 is the autochanger.  This requires special initialization of the CMD N  controller.  Specifically, two of the devices provided by the CMD controller @  must be dedicated to the same SCSI ID, but to different LUNs.  K  For example, using a CMD Technologies CQD Q-Bus to SCSI controller and if TM  the SCSI ID of the L7A-42Xis 4, one MU device must support SCSI ID 4, LUN 0 cN  and one DU device must support SCSI ID 4, LUN 1.  The DU device thus created 4  will be used by Branches to control the robotics.  M  See the documentation that came with your controller for further details on x  configuring SCSI IDs and LUNs.h *2Ea *2Ia *4D  / The Cipher MiniLibrary L7A-42X is implemented as two LUNs, 0 is the drive, 1 is the autochanger.  This requires special initialization of the CMD controller.  Specifically, two of the devices provided by the CMD controller must be dedicated to the ' -same SCSI ID, but to different LUNs.  a / For example, using a CMD Technologies CQD Q-Bus to SCSI controller and if the SCSI ID of the L7A-42Xis 4, one MU device must support SCSI ID 4, LUN 0 and one DU device must support SCSI ID 4, LUN 1.  The DU device thus created will be used by Branc -hes to control the robotics.  gk  See the documentation that came with your controller for further details on configuring SCSI IDs and LUNs.a *4E  *2El *4Da  Connors Python  *4E  *2DeO  The Python is implemented as two LUNs, 0 is the drive, 1 is the autochanger.  CS  This requires special initialization of the CMD controller.  Specifically, two of  J  the devices provided by the CMD controller must be dedicated to the same "  SCSI ID, but to different LUNs.  N  For example, if the SCSI ID of the LD4 is 4, one MU device must support SCSI M  ID 4, LUN 0 and one DU device must support SCSI ID 4, LUN 1.  The DU device IA  thus created will be used by Branches to control the robotics.  .M  See the documentation that came with your controller for further details on    configuring SCSI IDs and LUNs.E *2Ea *2Is *4D  / The Python is implemented as two LUNs, 0 is the drive, 1 is the autochanger.  This requires special initialization of the CMD controller.  Specifically, two of the devices provided by the CMD controller must be dedicated to the same SCSI ID, but to - different LUNs.  a  For example, if the SCSI ID of the LD4 is 4, one MU device must support SCSI ID 4, LUN 0 and one DU device must support SCSI ID 4, LUN 1.  The DU device thus created will be used by Branches to control the robotics.  k  See the documentation that came with your controller for further details on configuring SCSI IDs and LUNs.y *4EK *2El *4D   Digital THZ27 *4E  *2D5H  The Digital THZ27 is implemented as two LUNs, 0 is the drive, 1 is the L  autochanger.  This requires special initialization of the CMD controller.  I  Specifically, two of the devices provided by the CMD controller must be s8  dedicated to the same SCSI ID, but to different LUNs.  N  For example, if the SCSI ID of the LD4 is 4, one MU device must support SCSI M  ID 4, LUN 0 and one DU device must support SCSI ID 4, LUN 1.  The DU device lT  thus created will be used by Branches to control the robotics.  In addition, there O  appears to be a bug in the CMD controllers that occasionally prevents a Mount NK  request from successfully completing.  To avoid this problem, disable the aM  ability for the devices supporting the Digital THZ27 to disconnect from the mH  SCSI bus during command processing.  Acorn Software has only seen this K  problem with tape data libraries, but CMD has noted that this problem may y,  occur with optical data libraries as well  6  See the documentation that came with your controller. *2E  *2Ir *4De / The Digital THZ27 is implemented as two LUNs, 0 is the drive, 1 is the autochanger.  This requires special initialization of the CMD controller.  Specifically, two of the devices provided by the CMD controller must be dedicated to the same SCSI ID, - but to different LUNs.   / For example, if the SCSI ID of the THZ27 is 4, one MU device must support SCSI ID 4, LUN 0 and one DU device must support SCSI ID 4, LUN 1.  The DU device thus created will be used by Branches to control the robotics.  In addition, there appears to / be a bug in the CMD controllers that occasionally prevents a Mount request from successfully completing.  To avoid this problem, disable the ability for the devices supporting the Digital THZ27 to disconnect from the SCSI bus during command process -ing.  Acorn Software has only seen this problem with tape data libraries, but CMD has noted that this problem may occur with optical data libraries as well  G  See the documentation that came with your controller for more details.  *4E  *2Ee *4D   DILOG LIBRA DATstacker1 *4Er *2DcO  For CMD controllers, the SCSI IDs for the drive and the autochanger must have o  DISCONNECT turned off.  r *2Em *2Ii *4Drg  For CMD controllers, the SCSI IDs for the drive and the autochanger must have DISCONNECT turned off.  a *4E  *2Et *4DrC  See the CMD manual provided with your controller for more details., *4Ed *2Di  .c2.Optical Data Libraries; *2EI *2Ie *4D   Optical Data Libraries; *4Ec *2Et *4Di'  Hewlett Packard Optical Disk Librariesm  CONF 32 *4Ea *2DtO  Must be set to ON in order for  Branches to function with HP ODLs  See the HP  @  user manual for instructions on changing the ODL configuration. *2Ea *2It *4De  Must be set to ON in order for  Branches to function with HP ODLs  See the HP user manual for instructions on changing the ODL configuration. *4Er *2E  *4Dg'  IDE Model 7100 Personal Library Systems  Changer Eject *4E  *2DeM  Must be set to Y.  See the IDE Model 7100 Personal Library System Technical vA  Reference Manual for instructions on changing the configuration.r *2E" *2IF *4D   Must be set to Y.  See the IDE Model 7100 Personal Library System Technical Reference Manual for instructions on changing the configuration.n *4ES *2Eo *4DO  ANSI ST SCSI2 *4E4 *2DCM  Must be set to Y.  See the IDE Model 7100 Personal Library System Technical SB  Reference Manual  for instructions on changing the configuration. *2Eo *2Ir *4Dw  Must be set to Y.  See the IDE Model 7100 Personal Library System Technical Reference Manual  for instructions on changing the configuration. *4Er *2Es *4Du(  IDE Model 9000 Corporate Library System *4Eu *2D K  Due to the way in which IDE designed the IDE Model 9000 Corporate Library  P  System, it is not possible to support it on any system which ejects cartridges N  automatically on DISMOUNT.  This restricts Branches support of this model to F  those systems using a CMD Technologies SCSI controller or SCEA board. *2En *2It *4Dh / Due to the way in which IDE designed the IDE Model 9000 Corporate Library System, it is not possible to support it on any system which ejects cartridges automatically on DISMOUNT.  This restricts Branches support of this model to those systems usin4 -g a CMD Technologies SCSI controller or SCEA board. *4Eb *2Ea *4Ds  Changer Eject *4Eo *2DeM  Must be set to Y.  See the IDE Model 7100 Personal Library System Technical  A  Reference Manual for instructions on changing the configuration.  *2Em *2Ih *4Du  Must be set to Y.  See the IDE Model 7100 Personal Library System Technical Reference Manual for instructions on changing the configuration.s *4Eu *2Eq *4Df+  CMD Controller or SCEA board Configurationb *4Ew *2DoP  To prevent the premature unloading of the cartridge from the drive, the Eject E  on Unload for the host controller must be set to N using the CMD fN  Technologies on board configuration utility.  See the documentation provided '  with your controller for more details.b  CF  .c.Chapter 8, Branches Error Messages                                  and Recovery Techniques;oQ  This chapter contains Branches error messages and some recovery techniques.  If sK  you have further difficulty, do not hesitate to contact us for support at  G  support@acornsw.com or (508) 568-1618 x16 or by fax at (508) 562-1133.  *2Et *2IO *4Dc / To prevent the premature unloading of the cartridge from the drive, the "Eject on Unload" for the host controller must be set to "N" using the CMD Technologies on board configuration utility.  See the documentation provided with your controller for - more details.O  nZ  Chapter 9, Branches Error Messages                                and Recovery Techniques  This chapter contains Branches error messages and some recovery techniques.  If you have further difficulty, do not hesitate to contact us for support at support@acornsw.com or (508) 568-1618 x16 or by fax at (508) 562-1133.o *4Ey *2Ew *4Dl#  Error messages in alphabetic orderaF  CANTINITDB      Cannot initialize database for library "libraryName".H  The inventory database cannot be initialized for the specified library.@  CLOSEMAILBOX  Empty and close mailbox for library "libraryName" *4El *2DtJ  This OPCOM message is presented to the CENTRAL operator in response to a O  Branches EXPORT request.  Branches will process no more requests for the data gP  library until the mailbox door is closed.  The export operation may be aborted #  using the REPLY/ABORT DCL command.v *2Eh *2I  *4D  / This OPCOM message is presented to the CENTRAL operator in response to a Branches EXPORT request.  Branches will process no more requests for the data library until the mailbox door is closed.  The export operation may be aborted using the REPLY/AB -ORT DCL command.c *4El *2Ep *4Dt1  CORRUPTIT  Inventory table filename is corruptedo *4Ef *2DrO  The specified inventory table has become corrupted.  This should not happen.  aT  If it does, report the problem, along with a copy of the inventory table, to Acorn 
  Software. *2E  *2Io *4D   The specified inventory table has become corrupted.  This should not happen.  If it does, report the problem, along with a copy of the inventory table, to Acorn Software.s *4Eo *2Es *4D   ERROR  Error: string  *4En *2DtK  This is a result of an internal error in Branches.  Report the problem as -%  described earlier to Acorn Software.r *2E- *2Is *4Deo  This is a result of an internal error in Branches.  Report the problem as described earlier to Acorn Software.c *4El *2E  *4DfI  INSERTCARTRIDGE  Insert cartridge into mailbox for library "libraryName"t *4E  *2DaJ  This OPCOM message is presented to the CENTRAL operator in response to a O  Branches IMPORT request.  Branches will process no more requests for the data eP  library until the mailbox door is closed.  The import operation may be aborted #  using the REPLY/ABORT DCL command.w *2Ee *2I  *4Da / This OPCOM message is presented to the CENTRAL operator in response to a Branches IMPORT request.  Branches will process no more requests for the data library until the mailbox door is closed.  The import operation may be aborted using the REPLY/AB -ORT DCL command.r *4Ee *2Ec *4Dn   INTLOGERR  Internal Logic Error:  Report this problem as discussed above to Acorn Software.@  INVCONTROL  Line lineNumber: Invalid control device: deviceName *4E  *2D F  The configuration file entry for the data library contains a CONTROL L  statement with an invalid device name.  Correct the configuration file and   restart Branches. *2Ep *2IS *4DD  The configuration file entry for the data library contains a CONTROL statement with an invalid device name.  Correct the configuration file and restart Branches. *4E  *2En *4Di9  INVDRIVENAME  Line lineNumber: Invalid drive name: drive  *4E  *2D S  The specified drive does not exist on the system.  Correct the configuration file i  and restart Branches. *2Et *2If *4DCh  The specified drive does not exist on the system.  Correct the configuration file and restart Branches. *4Em *2ES *4DD5  INVDRIVES  Line lineNumber: Invalid DRIVE statement.D *4Eh *2D N  The configuration file entry for the data library contains a badly formatted G  DRIVE statement.  Correct the configuration file and restart Branches.n *2Et *2It *4Dh  The configuration file entry for the data library contains a badly formatted DRIVE statement.  Correct the configuration file and restart Branches. *4Ey *2Ei *4Dl=  INVLIBNAME  Line lineNumber: Invalid library name specified.s *4Ei *2DpO  The configuration file entry for the data library contains a DEFINE statement vP  with an invalid data library name.  Correct the configuration file and restart 
  Branches. *2Er *2Ip *4Df  The configuration file entry for the data library contains a DEFINE statement with an invalid data library name.  Correct the configuration file and restart Branches.a *4E  *2En *4Dt6  INVLIBTYPE  Line lineNumber: Library type is invalid. *4En *2DeM  The configuration file entry for the data library contains a TYPE statement gP  with an invalid data library type.  Correct the configuration file and restart 
  Branches. *2Ea *2Ia *4D   The configuration file entry for the data library contains a TYPE statement with an invalid data library type.  Correct the configuration file and restart Branches.  *4Eu *2Ed *4De>  INVLOADTIMEOUT  Line lineNumber: Invalid Load Timeout: string *4Ec *2DtH  The load timeout must be a decimal number.  The specified value in the Q  configuration file is bad.  Correct the configuration file and restart Branches.s *2E  *2Ii *4Dh  The load timeout must be a decimal number.  The specified value in the configuration file is bad.  Correct the configuration file and restart Branches. *4Et *2E  *4Di@  INVPOSITION  Line lineNumber: Invalid position number: position *4Em *2DSI  The value specified in the last Branches command containing a /POSITION lK  qualifier was invalid.  Make sure you specify a valid position number and r!  reissue the command that failed.l *2ES *2Ie *4Dm  The value specified in the last Branches command containing a /POSITION qualifier was invalid.  Make sure you specify a valid position number and reissue the command that failed.o *4Et *2ED *4Dr>  INVSCSITIMEOUT  Line lineNumber: Invalid SCSI Timeout: string *4Ee *2DtI  This SCSI timeout must be a decimal number.  The specified value in the lN  configuration file is not valid.  Correct the configuration file and restart 
  Branches. *2Ee *2I  *4Dr  This SCSI timeout must be a decimal number.  The specified value in the configuration file is not valid.  Correct the configuration file and restart Branches.r *4Et *2Es *4Dl#  INVSLOT  Invalid slot number: slots *4Ey *2DlO  The value specified in the last Branches command containing a /SLOT qualifier  I  was invalid.  Make sure you specify a valid slot number and reissue the    command that failed.y *2E  *2Ip *4Dm  The value specified in the last Branches command containing a /SLOT qualifier was invalid.  Make sure you specify a valid slot number and reissue the command that failed.e *4Ei *2E  *4D A  INVUNLOADTIMEOU  Line lineNumber: Invalid Unload Timeout: stringe *4Eh *2DIJ  The unload timeout must be a decimal number.  The specified value in the Q  configuration file is bad.  Correct the configuration file and restart Branches.c *2Er *2I  *4DD  The unload timeout must be a decimal number.  The specified value in the configuration file is bad.  Correct the configuration file and restart Branches. *4E  *2E  *4D 4  INVXPORT Line lineNumber: Invalid transport: string *4Ed *2DcN  The specified transport type is invalid.  Correct the configuration file and   restart Branches. *2ED *2Ie *4D _  The specified transport type is invalid.  Correct the configuration file and restart Branches.e *4Et *2Ei *4De1  LIBDEFAULT  Too many default library definitionsP *4E  *2DlJ  The configuration file entry for the data library contains more than one N  DEFINE statement without a name field.  There may be only one such statement Q  in the configuration file.  Correct the configuration file and restart Branches.  *2En *2It *4Do  The configuration file entry for the data library contains more than one DEFINE statement without a name field.  There may be only one such statement in the configuration file.  Correct the configuration file and restart Branches.  *4E  *2E  *4Dt,  MISSINGARG  <One or more arguments missing>C  MOUNTEDDRIVES  One or more drives mounted in library "libraryName" C  MOVEMENTFAILURE  Moving volumeName to drive deviceName has failed.  *4E  *2DPK  The last mount or Branches MOUNT command failed to move the volume to the nR  drive.  Generally this is a result of physically rearranging the contents of the N  data library without restructuring the inventory data base for the library.  @  Reconstruct the data library inventory data base with Branches 2  INITIALIZE/VERIFY and reissue the failed command. *2E  *2Ii *4Dr / The last mount or Branches MOUNT command failed to move the volume to the drive.  Generally this is a result of physically rearranging the contents of the data library without restructuring the inventory data base for the library.  Reconstruct the a -data library inventory data base with Branches INITIALIZE/VERIFY and reissue the failed command.l *4Eh *2Ey *4D B  NOCONFIGURATION  <No configuration is available in library "!AS">:  NOCONTROL  Line lineNumber: CONTROL statement is missing. *4E  *2DoH  The configuration file entry for the data library is missing a CONTROL A  statement.  Correct the configuration file and restart Branches.s *2E  *2Ie *4D   The configuration file entry for the data library is missing a CONTROL statement.  Correct the configuration file and restart Branches. *4Er *2E  *4DE$  NODISMOUNT  Dismount of !AS failed.A  During an import operation, a SYS$DISMOU system service failed. t8  NODRIVE  No drive is available in library "libraryName" *4E *2DiK  A Branches command could not be satisfied because there were no available aN  drives.  Dismount one or more drives and reissue the failed Branches command. *2E  *2I  *4Dg  A Branches command could not be satisfied because there were no available drives.  Dismount one or more drives and reissue the failed Branches command. *4Eu *2E  *4Dc5  NOHWSUPPORT	<No hardware support for this function.>s)  NOLICENSE  This product is not licensed.  *4Ex *2D5G  The license for Branches has expired.  Only Branches SHUTDOWN will be  T  executed.  Fill out a key request form at the back of this book and send it or fax 4  it to Acorn Software for a license.  Contact us at: *2Eu *2Iy *4De  The license for Branches has expired.  Only Branches SHUTDOWN will be executed.  Fill out a key request form at the back of this book and send it or fax it to Acorn Software for a license.  Contact us at:e *4Es *2Es *4De  			267 Cox St..  			Hudson, Ma. 01749i  			508-568-1618 (voice)  			508-562-1133 (fax) *4Es *2Dt  			info@acornsw.com *2E6 *2I6 *4Dy  			support@acornsw.com  *4E  *2E  *4D ;  NOMAILBOX  No mailbox available for library "libraryName".  *4Ea *2DdM  An operation requiring a mailbox was request for the specified data library e  which has no mailbox. *2E  *2IE *4DOb  An operation requiring a mailbox was request for the specified data library which has no mailbox. *4E  *2EA *4Dr%  NOMAGAZINE	<No magazine in library.>T)  NOOUTPUTFILE  <Output file open failed.>q%  NORECOVERY  No recovery is possible.e *4Eb *2DoG  Branches has failed to recover from a detected error condition.  More T2  information on the error is present in the file, C  BRNCH_SCRATCHlibraryname-ERROR.LOG.  Report this problem to Acorn O
  Software. *2Ec *2Ii *4Do  Branches has failed to recover from a detected error condition.  More information on the error is present in the file, BRNCH_SCRATCHlibraryname-ERROR.LOG.  Report this problem to Acorn Software.l *4Ee *2Ei *4Dr-  NOSCRATCHAV  No scratch volume is available.b *4Es *2Dm>  No scratch volume is available for mounting in response to a 8  MOUNT/FOREIGN or MOUNT/OVERRIDE=IDENTIFICATION with no O  volume name.  Add a scratch volume to the data library and reissue the failed r	  command.s *2El *2I  *4Dn  No scratch volume is available for mounting in response to a MOUNT/FOREIGN or MOUNT/OVERRIDE=IDENTIFICATION with no volume name.  Add a scratch volume to the data library and reissue the failed command.R *4E  *2Er *4D 1  NOSERVER Server for data library is not running.  *4E  *2D S  The server is not started or has stopped before executing the operation requested eK  by the user.  Restart the server and reissue the command.  If the problem d@  persists, report the problem to Acorn Software product support. *2Es *2Is *4De  The server is not started or has stopped before executing the operation requested by the user.  Restart the server and reissue the command.  If the problem persists, report the problem to Acorn Software product support. *4EY *2ET *4Dc@  NOTCLOSED  <Mailbox is not closed in library "!AS">/FAO_COUNT=13  NOTDEFINE  Line lineNumber: Not a define statementrD  The first line of the configuration file is not a DEFINE statement.Q  NOTEJECTED  Volume not ejected from one or more drives in library "libraryName".L *4E  *2DDJ  A Branches INITIALIZE operation was attempted while media was present in P  the drives.  Dismount or unload the media in the drives and reissue the failed 	  command.o *2Ei *2Ie *4Da  A Branches INITIALIZE operation was attempted while media was present in the drives.  Dismount or unload the media in the drives and reissue the failed command.  *4Es *2EB *4De)  NOTHOMED  Library libraryName not homed.l *4Er *2D P  The library failed to home during initialization.  This may indicate some sort L  of hardware problem.  Check your hardware and reissue the operation.  More C  details on the specific error can be found in BRNCH_SCRATCH:BRNCH-i  ERROR.LOG.e *2E  *2I  *4De  The library failed to home during initialization.  This may indicate some sort of hardware problem.  Check your hardware and reissue the operation.  More details on the specific error can be found in BRNCH_SCRATCH:BRNCH-ERROR.LOG.m *4EI *2Ed *4DE.  NOTIMPLEMENTED  operation is not implemented.A  The requested operation is not implemented for the data library.a<  NOTINLIB  Volume volumeName is not in library "libraryName" *4Et *2DtJ  The volume requested in the last Branches operation doesnt exist in the N  library.  Add the required volume to the data library and reissue the failed 	  command.i *2El *2IV *4DM  The volume requested in the last Branches operation doesn't exist in the library.  Add the required volume to the data library and reissue the failed command.l *4Et *2Er *4DaK  NOTINROTOR  Volume volumeName is not in any rotor in library "libraryName"f *4Ee *2DiN  In attempting error recover for a Kodak 560 Optical Data Library, the volume O  was not in the rotor where Branches expected it to be.  Report the problem to 4  Acorn Software. *2ET *2IL *4Di  In attempting error recover for a Kodak 560 Optical Data Library, the volume was not in the rotor where Branches expected it to be.  Report the problem to Acorn Software.t *4En *2Ea *4Df7  NOTINVENTORIED  Library inventoryName not inventoried.i *4Ei *2DlP  The library failed to inventory during initialization.  This may indicate some L  sort of hardware problem.  Check your hardware and reissue the operation.  H  More details on the specific error can be found in BRNCH_SCRATCH:BRNCH-  ERROR.LOG.a *2Ee *2Iu *4D   The library failed to inventory during initialization.  This may indicate some sort of hardware problem.  Check your hardware and reissue the operation.  More details on the specific error can be found in BRNCH_SCRATCH:BRNCH-ERROR.LOG. *4E  *2E  *4Dc)  NOTOCCUPIED  <The drive isn't occupied.>e/  NOTYPE  Line lineNumber: Library type missing.e *4Ev *2DpQ  The configuration file entry for the data library is missing a TYPE statement.  m5  Correct the configuration file and restart Branches.M *2Eu *2Iu *4Di  The configuration file entry for the data library is missing a TYPE statement.  Correct the configuration file and restart Branches.n *4Et *2Eg *4DON  REMOVECARTRIDGE	<Remove cartridge from mailbox for library "!AS">/FAO_COUNT=19  SCSI  SCSI Error: Sense Key = !ZL, ASC = !ZL, ASCQ = !ZLC *4EE *2DL6  A SCSI error occurred.  More details can be found in   BRNCH_SCRATCH:BRNCH-ERROR.LOG *2El *2Ie *4DhS  A SCSI error occurred.  More details can be found in BRNCH_SCRATCH:BRNCH-ERROR.LOGi *4El *2E  *4Dr5  SLOTMISSING  Required slot number was not specified.s *4Ea *2DmG  Data libraries with magazines require /SLOT qualifiers for all IMPORT CF  operations.  Reissue the Branches command with the appropriate /SLOT   qualifier.a *2El *2Im *4Ds  Data libraries with magazines require /SLOT qualifiers for all IMPORT operations.  Reissue the Branches command with the appropriate /SLOT qualifier. *4Ea *2Ei *4Dt  UNKKEYWORD  Unknown keyword.2 *4E2 *2D4M  The configuration file entry for the data library contains a statement that iK  contained an unknown keyword.  Correct the configuration file and restart m
  Branches. *2Ee *2Ii *4D   The configuration file entry for the data library contains a statement that contained an unknown keyword.  Correct the configuration file and restart Branches. *4En *2Ea *4Df    *4Ed *2Dr*  .c.Branches License and Key Request Form;N  This chapter contains examples on how to acquire a license for Branches.  We Q  have made every effort to make it easy for you so there is a blank license form r=  that you can fax back to us. or contact us on the Internet  I>  .c1.Example of a blank key request form for the node, QUICK.; *2Es *2Il *4DC&  Branches License and Key Request Form  This chapter contains examples on how to acquire a license for Branches.  We have made every effort to make it easy for you so there is a blank license form that you can fax back to us. or contact us on the Internet  9  Example of a blank key request form for the node, QUICK.t *4En *2ED *4D   t(  Unauthorized use is strictly forbidden!  Username: MUNROEm  Password:    fK  Log into any account on the system to which the data library is connected. $  $ BRANCH LICENSE/OUTPUT=LICENSE.TXT   ,  Create a license request form for the node.&  Key Request Form:       BRANCHES V2.60  Date:                   27-MAR-1995 20:36:07.74  oC  To obtain your Software Key, send this form containing your System K  Identification Code (below) to Acorn Software, Inc., or contact your Acorn P  Software service or sales representative.  If you are outside of North America,P  contact your local Branches distributor or send your System Identification CodeO  directly to Acorn Software to obtain a Software Key which will enable full use   of BRANCHES V2.6.  n%                  Acorn Software, Inc.i                  267 Cox St."                  Hudson, Ma. 01749  n:                  Phone:  508-568-1618    Fax: 508-562-11334                  E-Mail: LICENSE-REQUEST@ACORNSW.COM   J  Please complete this software key request form by providing the followingK  information before sending this form to Acorn Software, Inc. or your localcH  Branches distributor.  Only key request forms that have been filled out  completely can be processed.h   C          Company:        _________________________________________  C          Address:        _________________________________________  C                          _________________________________________ mC                          _________________________________________ lC                          _________________________________________ eC          Country:        _________________________________________ TC          Phone:          _________________________________________  C          Fax:            _________________________________________ rC          Contact Person: _________________________________________  C          Title:          _________________________________________ i  vB          Data Library Manufacturer:      -------------------------B          Data Library Model:             -------------------------  uN  The following is a list of System Identification Codes for some or all of theM  VAXes in your VAXcluster.  To include the System Identification Codes (SICs)iM  for additional VAXes in your VAXcluster, log in to those VAXes and issue theu  2)          BRANCHES LICENSE/OUTPUT=filename      command for Branches.  ED  SIC:    BRN2-4WVLB7-E3CNXX-XGFXB5---3CG4W4-WD4MT5-DGT0K6    (QUICK)  a  $ EDIT LICENSE.TXTc    *4EO *2Dl`  Using your favorite editor, complete the key request form.  Please see the next section for an (  example of a complete key request form. *2E: *2Iu *4Dy  Using your favorite editor, complete the key request form.  Please see the next section for an example of a complete key request form.  *4Ea *2En *4Do  a *4Et *2Dr-  .c1.Example of a completed key request form;s *2Es *2Ie *4D	(  Example of a completed key request form *4E6 *2E8 *4Dc     	  $ TYPE LICENSE.TXT4&  Key Request Form:       BRANCHES V2.60  Date:                   27-MAR-1995 20:36:07.74   C  To obtain your Software Key, send this form containing your System2K  Identification Code (below) to Acorn Software, Inc., or contact your AcornaP  Software service or sales representative.  If you are outside of North America,P  contact your local Branches distributor or send your System Identification CodeO  directly to Acorn Software to obtain a Software Key which will enable full use.  of BRANCHES V2.6.  o%                  Acorn Software, Inc.e                  267 Cox St."                  Hudson, Ma. 01749  f:                  Phone:  508-568-1618    Fax: 508-562-11334                  E-Mail: LICENSE-REQUEST@ACORNSW.COM   J  Please complete this software key request form by providing the followingK  information before sending this form to Acorn Software, Inc. or your localCH  Branches distributor.  Only key request forms that have been filled out  completely can be processed.   sC          Company:        Data Library Specialists_________________ aC          Address:        946 Massachusetts Avenue_________________ IC                          Cambridge, MA. 02139_____________________ tC                          _________________________________________  C                          _________________________________________ GC          Country:        USA______________________________________ hC          Phone:          (617) 491-7474___________________________ 2C          Fax:            (617) 491-7475___________________________ 2C          Contact Person: D. Dewey_________________________________ eC          Title:          V.P., Marketing__________________________    mB          Data Library Manufacturer:      Exabyte------------------B          Data Library Model:             210----------------------  aN  The following is a list of System Identification Codes for some or all of theM  VAXes in your VAXcluster.  To include the System Identification Codes (SICs)oM  for additional VAXes in your VAXcluster, log in to those VAXes and issue thes  i)          BRANCHES LICENSE/OUTPUT=filenamei  l  command for Branches.  tD  SIC:    BRN2-4WVLB7-E3CNXX-XGFXB5---3CG4W4-WD4MT5-DGT0K6    (QUICK)  n    *4EJ *2D G  .c1.Send the completed form to us at Acorn Software via the Internet.;4    *2E  *2Ia *4D B  Send the completed form to us at Acorn Software via the Internet. *4Ee *2Ei *4Dt    *4Ed *2Dm\  The quickest way to send key request forms is by electronic mail on the Internet.  Here is   where to send it: *2Ed *2Ie *4Dam  The quickest way to send key request forms is by electronic mail on the Internet.  Here is where to send it:  *4E  *2E  *4DO  LICENSE-REQUEST@ACORNSW.COM  d *4E4 *2D2Q  .c1.Send the completed form to us at Acorn Software via  a FAX or postal system;  *2E  *2Ia *4DoL  Send the completed form to us at Acorn Software via  a FAX or postal system *4Ef *2Er *4Dn    *4E  *2DNX  If you do not have access to the Internet, fax the completed key request form to Acorn 
  Software at:h *2Ey *2Ic *4Dod  If you do not have access to the Internet, fax the completed key request form to Acorn Software at: *4Ee *2Ec *4D   1 (508) 562-1133TK  Or, send the completed via the postal system or your carrier of choice to:l  Acorn Software, Inc.d  267 Cox St.  Hudson, MA 01749  USA  a  b *4Ea *2DT#  .c.Acorn Software Problem Report ;bN  To report a problem, assemble the information that will allow us to diagnose P  the problem, then contact us with this information, either by the Internet, by   telephone or Fax. *2E  *2Ia *4D   Acorn Software Problem Report u  To report a problem, assemble the information that will allow us to diagnose the problem, then contact us with this information, either by the Internet, by telephone or Fax. *4Em *2Eu *4De  Helpful Information5  First, assemble the information we need to help you:r *4Ec *2Df@  Step 1  Use BRNCH_SYSTEM:BRNCH-PROBLEM-REPORT.TEMPLATE as your ?  basis for the software problem report and create a file named  J  BRNCH-PROBLEM-REPORT.TXT.  Describe the problem in as much detail as you "  can.  In addition, please note   C  	If you were able to duplicate the circumstances that caused the p	  problem.c *2Eo *2Ie *4D4  Step 1  Use BRNCH_SYSTEM:BRNCH-PROBLEM-REPORT.TEMPLATE as your basis for the software problem report and create a file named BRNCH-PROBLEM-REPORT.TXT.  Describe the problem in as much detail as you can.  In addition, please note   K  	If you were able to duplicate the circumstances that caused the problem.: *4E- *2ER *4DG'  	The location of the file, SYSUAF.DAT >  	The definition of the SYSUAF logical name, if it is defined *4Ea *2DeD  	The privileges (specifics) of the account from which you started H  Branches.  We need the details since not all accounts such as a system -  managers account have the same privileges. o *2Ee *2I  *4DP  	The privileges (specifics) of the account from which you started Branches.  We need the details since not all accounts such as a system manager's account have the same privileges. r *4Es *2E2 *4D2-  	The version number of Branches and of VMS.  *4El *2DyR  Step 2  If the problem involves a crash, locate the process dump.  When Branches Q  crashes, it leaves a process dump on your system device.  The location can vary SL  according to where the default directory is when the BRNCH-STARTUP command J  procedure starts.  Check the date of the process dump with the DIRECTORY F  command to identify the one that might have been part of the problem. *2E  *2Ie *4Dd / Step 2  If the problem involves a crash, locate the process dump.  When Branches crashes, it leaves a process dump on your system device.  The location can vary according to where the default directory is when the BRNCH-STARTUP command procedure st -arts.  Check the date of the process dump with the DIRECTORY command to identify the one that might have been part of the problem.e *4E  *2Er *4Ds/  Step 3  Make a backup save set of these files:4  BRNCH-PROBLEM-REPORT.TXT   BRNCH-OPCOM-CATCHER.DMP%  BRNCH_SYSTEM:BRNCH-OPCOM-CATCHER.EXE   BRNCH_SCRATCH:BRNCH-OUTPUT.LOGm  BRNCH_SCRATCH:BRNCH-ERROR.LOG  SYS$SYSTEM:ANALIMDMP.EXEf *4Et *2DiR  Step 4  If you are connected to the Internet, send us the backup set via mail or K  anonymous FTP.  Here are the commands that will send us the files we need.c *2E  *2Ig *4Do  Step 4  If you are connected to the Internet, send us the backup set via mail or anonymous FTP.  Here are the commands that will send us the files we need. *4Ee *2Eo *4Dn  FTP FTP.ACORNSW.COM  USER INCOMING  BINARYe
  PUT filenamet  EXIT  *4En *2DeR  If you are not connected to the Internet, copy the backup save set to one of the   following media:  *2Es *2Im *4Dtb  If you are not connected to the Internet, copy the backup save set to one of the following media: *4Ee *2Eh *4D   TK50 Cartridge  *4Er *2Ds  TK70 Cartridgev	  4 mm DATt *2Ee *2Ia *4Dr
   4 mm DAT *4Ea *2Ek *4Dn0  5 1/4" Sony optical disk cartridge (ISO format)
  8 mm tape *4E  *2Da  .c1.Contact us by Internet;Q  This the fastest way to get to us without a doubt.  During the installation for dG  Branches, the BRNCH_SUPPORT parameter gets set as the default support sI  address.  Please use the Branches utility command just for that purpose:C *2ET *2I  *4De  Contact us by Internetm  This the fastest way to get to us without a doubt.  During the installation for Branches, the BRNCH_SUPPORT parameter gets set as the default support address.  Please use the Branches utility command just for that purpose:e *4E. *2Ec *4DtA  $ @BRNCH_SYSTEM:BRNCH-PROBLEM-REPORT.COM backupSaveSet [support]e  t *4Eo *2DtH  backupSaveSet  is the fully qualified file name of the backup save set :  containing the problem report and diagnostic information.H  support is the email address that will reach support@acornsw.com.  The 5  installation parameter BRNCH_SUPPORT is the default.x.  .c1.Contact us by the carrier of your choice;N  If you are not on the Internet, send the us backup save set on the specified A  medium (noted in previous section) with a brief cover letter to:k *2Eq *2If *4Dy  backupSaveSet  is the fully qualified file name of the backup save set containing the problem report and diagnostic information.y|  support is the email address that will reach support@acornsw.com.  The installation parameter BRNCH_SUPPORT is the default. *4E_ *4D_)  Contact us by the carrier of your choice_  If you are not on the Internet, send the us backup save set on the specified medium (noted in previous section) with a brief cover letter to: *4E_ *2E_ *4D_  Acorn Software, Inc.   267 Cox St.  Hudson, Ma. 01749  USA1  attn: Customer Services, Software Problem Report_ *4E_ *2D_J  If you need operational support and you have a customer services support ;  contract, please call or FAX a software problem report to:_ *2E_ *2I_ *4D_  If you need operational support and you have a customer services support contract, please call or FAX a software problem report to: *4E_ *2E_ *4Di  VOICE:	1 (508) 568-1618  FAX	1 (508) 562-1133- *4E- *2D-Q  Our business hours are 8:00 am to 5:00 PM EST (GMT -5:00).  We will call you or  "  send you email within 24 hours.   *2Ef *2Io *4Der  Our business hours are 8:00 am to 5:00 PM EST (GMT -5:00).  We will call you or send you email within 24 hours.   *4E  *2E  *4Du  A *4Et *2Do'  .c.Appendix A, The Configuration File; L  Under rare circumstances, you will have to manually edit the configuration Q  file.  If you are not running Branches, you must first define the logical names S  used by Branches: *2EU *2Iy *4Da  The Configuration Fileh  Under rare circumstances, you will have to manually edit the configuration file.  If you are not running Branches, you must first define the logical names used by Branches:m *4Ee *2Ee *4D (  @SYS$STARTUP:BRNCH-STARTUP.COM LOGICALS *4Ee *2D P  Once this is completed, the logicals are defined exactly as they appear in the   following examples.  5  You are now prepared to edit the configuration file  E  (BRNCH_CONFIGURATION:).  The text editor of your choice may be used.2R  The format of the configuration file is simple.  Lines begin with a keyword that Q  cannot be contracted, with parameters and a carriage return, CR.  Lines may not oJ  have leading blanks.  Entries begin with a DEFINE keyword and end with a N  null line (a line with no characters except the ending CR) or the end of the N  configuration file.  Each entry defines a library to be served, its physical P  characteristics, the physical characteristics of the linkage to the robot, the Q  location of the library inventory database, etc.  Branches allows more than one ,5  data library per OpenVMS or OpenVMSCluster system.    *2E  *2I6 *4D3e  Once this is completed, the logicals are defined exactly as they appear in the following examples.  fy  You are now prepared to edit the configuration file (BRNCH_CONFIGURATION:).  The text editor of your choice may be used.t / The format of the configuration file is simple.  Lines begin with a keyword that cannot be contracted, with parameters and a carriage return, CR.  Lines may not have leading blanks.  Entries begin with a DEFINE keyword and end with a null line (a l /ine with no characters except the ending CR) or the end of the configuration file.  Each entry defines a library to be served, its physical characteristics, the physical characteristics of the linkage to the robot, the location of the library inventg -ory database, etc.  Branches allows more than one data library per OpenVMS or OpenVMSCluster system.    *4E) *2E7 *4D_)  NOTE:  This file must be world readable.t *4Eo *2D ;  .c1.Definitions of entries in Branches Configuration File; U  The following sections describe each line of the configuration file.  If you prefer rH  example configuration files, please skip to the next section, Examples. *2E- *2I- *4D-  -  The following sections describe each line of the configuration file.  If you prefer example configuration files, please skip to the next section, Examples. *4EI *2E  *4Da#  Control robot_dev [,devpara[,...]]o *4Et *2DsQ  This required line identifies and defines the device which performs the robotic d$  motions to the data library device. *2EC *2IG *4D-t  This required line identifies and defines the device which performs the robotic motions to the data library device. *4E. *2E  *4D   robot_dev must be a   *4Ee *2DoR  	a SCSI pass-through device from a CMD Technologies SCSI controller (DUc254: or 
  DIcnnn:) or o *2E  *2Ie *4D ^  	a SCSI pass-through device from a CMD Technologies SCSI controller (DUc254: or DIcnnn:) or  *4Ei *2E  *4DoV  	a device from a Digital-supplied SCSI driver (GKbu0l) without the option of devpar. *4E4 *2D2L  If the device is a SCSI pass-through device from a CMD Technologies CQD or M  CBI SCSI controller, the optional devpara is the OpenVMS unit number of the  N  disk device representing the robot, e.g., if the robot is seen as DUA3:, the   devpara would be 3. *2E2 *2II *4D   If the device is a SCSI pass-through device from a CMD Technologies CQD or CBI SCSI controller, the optional devpara is the OpenVMS unit number of the disk device representing the robot, e.g., if the robot is seen as DUA3:, the devpara would be 3. *4E  *2Es *4Dh  Define data_library *4Es *2D P  This required line defines the name of the data library.  The name can contain Q  up to 8 alphanumeric characters.  Be specific and characterize the data library pF  according to its use or origin or another easily recognizable name.  N  To use the default, type Define.  The default name is DEFAULT and requires a L  blank parameter for data_library.  Do not enter "DEFAULT" as a parameter.  J  There can be only one default data library per VMS or VAX Cluster system. *2Et *2Io *4D   This required line defines the name of the data library.  The name can contain up to 8 alphanumeric characters.  Be specific and characterize the data library according to its use or origin or another easily recognizable name.  L  To use the default, type Define.  The default name is DEFAULT and requires a blank parameter for data_library.  Do not enter "DEFAULT" as a parameter.  There can be only one default data library per VMS or VAX Cluster system. *4Eu *2Ec *4Da$  Drive n, (datname [, datname ...])  *4E4 *2DeM  This required line defines how many drives (the number of the data transfer aM  devices) and their names (the VMS device name of each data transfer device) h4  in the data library.  The parentheses are required. *2Ee *2I  *4D  This required line defines how many drives (the number of the data transfer devices) and their names (the VMS device name of each data transfer device) in the data library.  The parentheses are required. *4E  *2Ee *4DiZ  NOTE:  The device names must be specified in the physical address order of the library.   *4Eo *2D H  Depending on your VMS device names, the actual device order may not be   related to the device names.  e *2Es *2Ii *4Dff  Depending on your VMS device names, the actual device order may not be related to the device names.   *4En *2Es *4Du  DRIVE-SUBSTITUTION ne *4Er *2DsK  This optional line allows you to disable or enable the drive substitution eK  behavior of Branches.  Some 3rd party archiving packages, notably TapeSys  L  from Software Partners 32, do not fully support all OpenVMS capabilities.  O  Specifically they are not well behavied when faced with drive substitution in nL  response to a mount request.  Should you be in the unfortunate position of S  possesing one of these packages, it is possible to disable the drive substitution    feature of Branches.  oP  A value of 0 for this configuration entry will disable drive substitution.  By '  default drive substitution is enabled.e *2Et *2Ia *4Dy / This optional line allows you to disable or enable the drive substitution behavior of Branches.  Some 3rd party archiving packages, notably TapeSys from Software Partners 32, do not fully support all OpenVMS capabilities.  Specifically they are not - well behavied when faced with drive substitution in response to a mount request.  Should you be in the unfortunate position of possesing one of these packages, it is possible to disable the drive substitution feature of Branches.  2v  A value of 0 for this configuration entry will disable drive substitution.  By default drive substitution is enabled. *4Es *2E  *4Ds     INVENTORY filenamec *4E  *2DgO  This optional line specifies the name of the inventory database.  The default  0  is:  BRNCH_SCRATCH:data_library.INVENTORY_TABLEL  data_library is the parameter on the DEFINE line for the current entry.  A M  unique inventory data base must be defined for each library.  The directory cL  with the inventory database(s) must allow world access for read operations. *2E2 *2I2 *4D4~  This optional line specifies the name of the inventory database.  The default is:  BRNCH_SCRATCH:data_library.INVENTORY_TABLE  data_library is the parameter on the DEFINE line for the current entry.  A unique inventory data base must be defined for each library.  The directory with the inventory database(s) must allow world access for read operations.o *4Et *2Ew *4Dt  LOAD-TIMEOUT n  *4En *2DaN  This optional entry notes the number of seconds it takes for media to become R  available for I/O after it is in the drive.  Branches sets reasonable values for   the LOAD-TIMEOUT. a *2E  *2It *4Dm  This optional entry notes the number of seconds it takes for media to become available for I/O after it is in the drive.  Branches sets reasonable values for the LOAD-TIMEOUT. r *4Es *2Ei *4DmX  NOTE:  Do NOT use this entry unless told to do so by a Branches support representative.  NODE node_name[,node_name]  *4E  *2D P  This optional line names the node connected to the data library and from which E  it receives commands.  node_name must be the SCS name; there are no i  exceptions to this rule.  pN  When the node line is omitted, Branches starts a library server on each node -  where the Branches startup procedure runs.   O  When running multiple Branches library servers for the same library, you must mP  provide a list of nodes upon which the servers are to start.  When the servers Q  start, they bid to become a master server.  Only the master server operates the gO  robot in response to mount and dismount requests and Branches commands.  When hK  the node running the master server crashes or is shut down, the remaining iQ  servers go through the bidding process again to determine a new master server.   N  Once this process is complete, the new master takes over responding to mount -  and dismount requests and Branches commands.t *2E4 *2I2 *4D4  This optional line names the node connected to the data library and from which it receives commands.  node_name must be the SCS name; there are no exceptions to this rule.  z  When the node line is omitted, Branches starts a library server on each node where the Branches startup procedure runs.   / When running multiple Branches library servers for the same library, you must provide a list of nodes upon which the servers are to start.  When the servers start, they bid to become a master server.  Only the master server operates the robot in re /sponse to mount and dismount requests and Branches commands.  When the node running the master server crashes or is shut down, the remaining servers go through the bidding process again to determine a new master server.  Once this process is complet^ -e, the new master takes over responding to mount and dismount requests and Branches commands. *4Eo *2Ef *4D A  To successfully operate cluster failover for Branches, you must:nH  	have the device names of the drives identical throughout the cluster. *4Er *2DiU  	have the device name of the robot identical on each system running a server which n*  could potentially become a master server.S  	have installed a Branches license on each node which could potentially become a A  master server.O *2Eh *2I  *4De~  	have the device name of the robot identical on each system running a server which could potentially become a master server.a  	have installed a Branches license on each node which could potentially become a master server.f *4Ec *2Eu *4Dn  SCSI-TIMEOUT n  *4E  *2D O  This optional entry notes the number of seconds it takes for the longest SCSI n  command to complete.  hL  This is useful for systems with embedded SCSI busses using the GKDRIVER to %  control the data library robotics.  t *2Ee *2I  *4Dre  This optional entry notes the number of seconds it takes for the longest SCSI command to complete.  ap  This is useful for systems with embedded SCSI busses using the GKDRIVER to control the data library robotics.   *4E, *2E  *4DcX  NOTE:  Do NOT use this entry unless told to do so by a Branches support representative.  TRACE state *4Eh *2D T  This optional line specifies the initial state of the tracing as if a Branches SET R  TRACE command had been executed.  Set state to 0 if tracing is to be off or to a R  comma seperated list containing one or more of the following if tracing is to be   on: *2EL *2Ib *4Dw  This optional line specifies the initial state of the tracing as if a Branches SET TRACE command had been executed.  Set state to 0 if tracing is to be off or to a comma seperated list containing one or more of the following if tracing is to be on:  *4Eg *2Eo *4De  	ALL  	Trace everything.r  o  	OPCOM  	Trace all OPCOM messages.s  h  	QIO&  	Trace all QIO activity to the robot.  b  	SCSIo(  	Trace all SCSI commands and responses.%  The default value is 0, tracing off.d  TRANSPORT transportType *4EV *2DsN  This optional entry specifies the command transport to be used by Branches.  .  transportType may be one of CMD, GKA, or DSA. *2Ef *2It *4Di{  This optional entry specifies the command transport to be used by Branches.  transportType may be one of CMD, GKA, or DSA.l *4Es *2Eo *4DnW  NOTE: Do NOT use this entry unless told to do so by a Branches support representative.o  TYPE device *4E  *2D R  This required line defines the type of data library.  These are the device codes   that are valid: *2EC *2Il *4Dta  This required line defines the type of data library.  These are the device codes that are valid:f *4Et *2Eb *4Dd  1804X	Pioneer 1804x CDROM+  ACL5480	Odetics ACL 5480 3480/3490 Libraryl  ADIC	ADIC Autochanger1  EX10E	Exabyte 10e 8 mm cartridge handling system 1  EX10I	Exabyte 10i 8 mm cartridge handling systemd  EX60	Exabyte EXB60   EX120	Exabyte EXB120r  EX210	Exabyte EXB210T  EX218	Exabyte EXB218l  EX440	Exabyte EXB440n  EX480	Exabyte EXB4804  HP10C	Hewlett-Packard 10C ODL   HP10LC	Hewlett-Packard 10LC ODL  HP20T	Hewlett-Packard 20T ODL   HP20LT	Hewlett-Packard 20LT ODL  HP20C	Hewlett-Packard 20 ODLe  HP40T	Hewlett-Packard 40T ODL  HP60C	Hewlett-Packard 20 ODLe  HP100C	Hewlett-Packard 100 ODLe   HP120T	Hewlett-Packard 120T ODL   HP200T	Hewlett-Packard 200T ODL  IDE	IDE HyperShuttle /  IDE7100	IDE Model 7100 Personal Library Systemh0  IDE9000	IDE Model 9000 Corporate Library System  K560	Kodak 560 ODL.  K560E	Kodak 560E ODL "  L7A42X	Cipher MiniLibrary L7A-42X*  LIBRA	Diverse Logistics LIBRA8 or LIBRA16%  LD43200	WangDAT  LD4 3200 DATStackere*  NKK556	NKK Model 556 Optical Data Library1  OLS10	Olympus Deltis OLS-10 Optical Data LibraryU"  PYTHON	Connor Archive/Python 4590  Q7		QualStar Q7 DLT Library)  RW504	Digital RW504 Optical Data Library )  RW510	Digital RW510 Optical Data Library )  RW514	Digital RW514 Optical Data Library )  RW516	Digital RW516 Optical Data Librarya4  SA100	DBSO or DRDAT08 Diverse Loigistics DATstacker *4Eo *2Ib *4Dm  STL4000	STL-4000 Tape Library *4Ee *2Ee *4Du  STL6000	STL-6000 Tape Library  STL8000	STL-8000 Tape Library *4E. *2In *4Dt  STL9000	STL-9000 Tape Library *4Ee *2Eb *4Dy(  TL820	Digital TL820 Magnum Tape Library  THZ27	Digital THZ27  TZ867	Digital TZ867  d  UNLOAD-TIMEOUT na *4E  *2DaN  This optional entry notes the number of seconds it takes for media to become N  available to the robot after a SYS$DISMOU system service has been executed.  9  Branches sets reasonable values for the UNLOAD-TIMEOUT.   *2Ed *2It *4D   This optional entry notes the number of seconds it takes for media to become available to the robot after a SYS$DISMOU system service has been executed.  Branches sets reasonable values for the UNLOAD-TIMEOUT. [ *4En *2E. *4D X  NOTE:  Do NOT use this entry unless told to do so by a Branches support representative.  d *4Es *2D c  Acorn Software                                                                                    s  .c1.Customer Service Policy;4R  March 1994  -- We are pleased to have you join our community of Branches users.  L  We are committed to the best possible software solution for storage system S  requirements and the best possible support for you.  Occasionally difficulties in nR  installation or operation of our software occurs.  We are ready to assist you in P  the diagnosis and recovery from errors.  Our technical support is available by N  telephone and Internet.  We are open for business during the usual hours EST   (USA).aP  As with all our customers, we will make every effort to resolve your technical L  difficulties or help you diagnose them to the level that you then can seek /  information from the source of the difficulty.eR  On a regular basis, we issue new versions of our documentation, both printed and Q  on-line help as well as our software.  The newest versions are available on the    Internet or at your request.  bG  We value you as our customer, especially your ideas and comments.  We tK  welcome your calls and letters with suggestions on how we can improve our lP  product, our documentation or our technical support.  Working together we make >  a better product.  And, we thank you for purchasing Branches.  e *2Et *2Io *4Dez  Acorn Software                                                                                    Customer Service Policy / March 1994  -- We are pleased to have you join our community of Branches users.  We are committed to the best possible software solution for storage system requirements and the best possible support for you.  Occasionally difficulties in installati -on or operation of our software occurs.  We are ready to assist you in the diagnosis and recovery from errors.  Our technical support is available by telephone and Internet.  We are open for business during the usual hours EST (USA).  As with all our customers, we will make every effort to resolve your technical difficulties or help you diagnose them to the level that you then can seek information from the source of the difficulty.Y  On a regular basis, we issue new versions of our documentation, both printed and on-line help as well as our software.  The newest versions are available on the Internet or at your request.   / We value you as our customer, especially your ideas and comments.  We welcome your calls and letters with suggestions on how we can improve our product, our documentation or our technical support.  Working together we make a better product.  And, w% -e thank you for purchasing Branches.t  a  m     d  	Acorn Software, Inc.	      e  	Acorn Software, Inc.  t  s  )  s  l     l  c  s  r  a   	r  o  o        w  4   -  		                                         	t  n  s  e  m     s  n  iI   	Acorn Software, Inc.	                             Branches User Guide    n  s:  Branches User Guide	Acorn Software, Inc.	                     m  T   M  Branches User Guide 	Acorn Software, Inc.	                                  l  o  /  f     i  n  e  iI   	Acorn Software, Inc.	                             Branches User Guide 4     T  Branches User Guide	Acorn Software, Inc.                                                                                             i  l  n  a5  Branches User Guide	Acorn Software, Inc.	           c        e  s  m  d     eI   	Acorn Software, Inc.	                             Branches User Guide W      7  Branches User Guide 	Acorn Software, Inc.	               h  d     e7  Branches User Guide	Acorn Software, Inc.	                t  e  a  e  i  r  e  rI   	Acorn Software, Inc.	                             Branches User Guide    v   9  Branches User Guide 	Acorn Software, Inc.	              e  m  e  e  r7  Branches User Guide 	Acorn Software, Inc.	            n  t  o        m  t  q  tI   	Acorn Software, Inc.	                             Branches User Guide e  r   9  Branches User Guide 	Acorn Software, Inc.	                 c     i  o3  Branches User Guide	Acorn Software, Inc.	   	     s     p  e  h  e  a  r  kI   	Acorn Software, Inc.	                             Branches User Guide t  2   9  Branches User Guide 	Acorn Software, Inc.	                    a  b  y3  Branches User Guide	Acorn Software, Inc.	   	        t  S  n  ;  e  a  n  xI   	Acorn Software, Inc.	                             Branches User Guide    r   9  Branches User Guide 	Acorn Software, Inc.	              n        n  n8  Branches User Guide	Acorn Software, Inc.	                y  m     v     i  o  oI   	Acorn Software, Inc.	                             Branches User Guide t  e  e9  Branches User Guide 	Acorn Software, Inc.	              t        o   8  Branches User Guide	Acorn Software, Inc.	                h  o  r  i  t  m  e  eI   	Acorn Software, Inc.	                             Branches User Guide p  e  aU  Branches User Guide 	Acorn Software, Inc.                            	              r  k  o     p7  Branches User Guide	Acorn Software, Inc.	             d     o  2        T  u  sI   	Acorn Software, Inc.	                             Branches User Guide e  m  oU  Branches User Guide 	Acorn Software, Inc.                            	              t  r  t  e  c7  Branches User Guide	Acorn Software, Inc.	             i  y  c     a  r  rI   	Acorn Software, Inc.	                             Branches User Guide a     oU  Branches User Guide 	Acorn Software, Inc.                            	              c  o  a  s  e$  Branches  User Guide		              *4Eb *2E  *4Dt  s  e *4E *4I   This file is obsolete.n *4E 