 *2D      Acorn Software, Inc.            Acorn Software, Inc.                              1           		  1                 1                           ;  1	Acorn Software, Inc.	            Branches  Release Notes          2  Branches Release Notes	Acorn Software, Inc.	    1               <  Branches Release Notes	Acorn Software, Inc.        	      1                     K  Branches Release Notes	Acorn Software, Inc.	                             1       .  Branches Release Notes	Acorn Software, Inc.	1            3  Branches  Release Notes	Acorn Software, Inc.	    1                   ;  1	Acorn Software, Inc.	             Branches Release Notes       M  Branches  Release Notes	Acorn Software, Inc.                            	  1             3  Branches  Release Notes	Acorn Software, Inc.	    1       6  1	               	             Branches Release Notes      -  Branches Release Notes	               	    1        *2E  *7D                    Branchestm   Release Notes *7E  *3D   Version 2.7 *3E  *3I  *4D   Version 2.8-1 *4E  *3E  *7D                                                  *7E  *2D                   *2E  *2I  *7D     *7E  *2E  *7D   Acorn Software, Inc. 
  Acton, MA                               *7E  *2D     *2E  *7D   Document Version:	2.3-3 *7E  *2D 4  Revision Information:	This manual replaces version   	2.3-2. *2E  *2I  *7D ;  Revision Information:	This manual replaces version 	2.3-2.  *7E  *2E  *3D   Software Version:	2.7 *3E  *3I  *4D   Software Version:	2.8-1 *4E  *4I  *5D   Software Version:	2.8-2 *5E  *5I  *7D   Software Version:	2.8-3 *7E  *5E  *4E  *3E  *7D 7  Operating System and Version:	VMS version 5.4 or later        *7E  *3D ,  Copyright  1992-1995, Acorn Software, Inc. *3E  *3I  *7D ,  Copyright  1992-1996, Acorn Software, Inc. *7E  *3E  *7D   All rights reserved *7E  *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.   @  The software described herein is provided subject to a license 8  agreement and the descriptions may include proprietary @  information belonging to Acorn Software, Inc.  No part of this <  manual may be reproduced in whole or in part by any means, A  including electronic means, without specific written permission  @  from Acorn Software, Inc. or as part of a specified permission >  contained within a specific software license agreement.  The E  associated software may not be redistributed, copied, or reproduced  B  in any form except for specified user backup as described in the   software license agreement.6  VAX, VMS, VAXStation, and VAX Cluster are registered .  trademarks of Digital Equipment Corporation.  *2E  *2I  *7D  / 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. c  VAX, VMS, VAXStation, and VAX Cluster are registered trademarks of Digital Equipment Corporation.   *7E  *2E  *7D .  SCEA is a trademark of CMD Technologies, Inc. *7E  *2D ?  Branches, the Acorn Software logo, "The data library software  =  vendor of choice" and "A leader in data library  management  2  software" are trademarks of Acorn Software, Inc.  *2E  *2I  *3D   Branches, the Acorn Software logo, "The data library software vendor of choice" and "A leader in data library  management software" are trademarks of Acorn Software, Inc.  *3E  *3I  *4D   Branches, VirtualBranches, HSManager, Squash, MODISK, the Acorn Software logo, "The data library software vendor of choice" and "A leader in data library  management software" are trademarks of Acorn Software, Inc.  *4E  *4I  *7D  / Branches, VirtualBranches, VirtualBranches for OpenVMS, VirtualBranches for Windows/NT, HSManager, Squash, MODISK, the Acorn Software logo, "The data library software vendor of choice" and "A leader in data library  management software" are tradema -rks of Acorn Software, Inc.   *7E  *4E  *3E  *2E  *7D /  EXABYTE is a trademark of Exabyte Corporation.  *7E  *2D 7  LIBRA DATStacker is a trademark of Diverse Logistics,    Incorporated.B  All other trademarks or registered trademarks are the properties #  of their respective manufacturers.  *2E  *2I  *7D D  LIBRA DATStacker is a trademark of Diverse Logistics, Incorporated.d  All other trademarks or registered trademarks are the properties of their respective manufacturers. *7E  *2E  *7D                           Printed on recycled paper.      Table of Contents *7E  *3D   Preface	iii0  What information our documentation contains	iii#  Who this manual is written for	iii 3  What conventions we used in these release notes	iv      Branches Release Notes	1    (  Branches License and Key Request Form	3      Acorn Software Problem Report	7  Helpful Information	7  Contact us by Internet	8 +  Contact us by the carrier of your choice	8      Customer Service Policy	9 *3E  *3I  *7D 	  Preface	 -  What information our documentation contains	    Who this manual is written for	1  What conventions we used in these release notes	   Branches Release Notes	#  Changes from version 2.8 to 2.8-1	 !  Changes from version 2.7 to 2.8	 !  Changes from version 2.6 to 2.7	 '  Branches License and Key Request Form	   Acorn Software Problem Report	   Customer Service Policy	  *7E  *3E  *7D        *7E  *2D   .c.Preface; *2E  *2I  *7D   Preface *7E  *2E  *7D     *7E  *2D H  March 1995 --  Welcome to Acorn Softwares Branches documentation.  We J  at Acorn are happy to add you to our group of users world wide who enjoy 6  the advantages of data library management software.   *2E  *2I  *4D   March 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  *4I  *7D   May 1996 --  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.   *7E  *4E  *2E  *7D :  In this preface, you will find the following information: *7E  *6D .  	what information our documentation contains!  	who this manual is written for   	what conventions we used  *6E  *6I  *7D .  	what information our documentation contains!  	who this manual is written for   	what conventions we used  *7E  *6E  *2D 1  .c1.What information our documentation contains; I  Our documentation set consists of three items:  the user guide, related  I  release notes and on-line help.  The user guide contains information on  J  installation and use; these release notes are kept as current as printed J  matter can be.  The on-line help is meant to jog your memory of specific J  details of operation and serves as the  most up-to-date documentation.   K  Although we will keep you  informed on new product features by reoccurent  L  mailings, you are welcome to take a copy of our documentation at any time  M  from the Internet.  The Internet address to obtain these documents from is:    docserv@dmc.com.   $  .c1.Who this manual is written for;C  We have written our documents with the experienced VAX/VMS system  F  manager and application developer in mind.  We have relied upon your E  knowledge and experience as well as your access to the complete VMS    documentation set.   M  If you are taking the first steps with a data library management system, we  K  have included several sections of examples in the installation chapter of  M  the user guide.  Should you experience problems, our error messages section  N  contains helpful information for resolution of problems or difficulties.  If M  you have further questions, we will be happy to address them.  Feel free to  0  contact us on the internet at info@acornsw.com.      5  .c1.What conventions we used in these release notes;  *2E  *2I  *7D ,  What information our documentation contains / Our documentation set consists of three items:  the user guide, related release notes and on-line help.  The user guide contains information on installation and use; these release notes are kept as current as printed matter can be.  The on-line helt -p is meant to jog your memory of specific details of operation and serves as the  most up-to-date documentation.     Although we will keep you  informed on new product features by reoccurent mailings, you are welcome to take a copy of our documentation at any time  from the Internet.  The Internet address to obtain these documents from is: docserv@dmc.com.    Who this manual is written for   We have written our documents with the experienced VAX/VMS system manager and application developer in mind.  We have relied upon your knowledge and experience as well as your access to the complete VMS documentation set.   / If you are taking the first steps with a data library management system, we have included several sections of examples in the installation chapter of the user guide.  Should you experience problems, our error messages section contains helpful infor -mation 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@acornsw.com.       0  What conventions we used in these release notes *7E  *2E  *7D -  Our documentation follows these conventions:   Character		Convention *7E  *2D M  italics		indicates optional items that you substitute the specific names or  '  			numbers in Branches or DCL commands N  courier, roman	indicates Branches or DCL commands and any examples of either /  			Branches licensing or program documentationsH  shaded note	indicates that we ask you to pay  very strict attention to /  			the information contained in the gray area.   t  e  .c.Branches Release Notes; K  This chapter presents, in order of their occurrence, the changes from the  L  previous versions of Branches to the current version of Branches.  We have H  included these items in the user guide and  we have them here for your   quick reference.       n  f*  .c.Branches License and Key Request Form;K  This chapter contains examples on how to acquire a license for Branches.   G  We have made every effort to make it easy for you so there is a blank IJ  license form that you can fax back to us. or contact us on the Internet   *2E  *2Ia *7D s  italics		indicates optional items that you substitute the specific names or 			numbers in Branches or DCL commands |  courier, roman	indicates Branches or DCL commands and any examples of either 			Branches licensing or program documentationv  shaded note	indicates that we ask you to pay  very strict attention to 			the information contained in the gray area.        Branches Release Notes   This chapter presents, in order of their occurrence, the changes from the previous versions of Branches to the current version of Branches.  We have included these items in the user guide and  we have them here for your quick reference.o *7E7 *3I  *4I  *5I  *6If *7D $  Changes from version 2.8-4 to 2.8-5  Sysware SupportA  Branches now support the PREINIT processing provided by Sysware.3$  Changes from version 2.8-3 to 2.8-4  Sysware Support$  Branches now fully supports Sysware *7E *6E- *7D $  Changes from version 2.8-2 to 2.8-3  New Device Support91  Branches now supports the following new devices:g   Pioneer DRM-1004X CDROM Changer  	device type: P1004Xs *7Ee *5E  *7De$  Changes from version 2.8-2 to 2.8-2,  Renaming Volumes as a side effect of BACKUP  A long standing feature of Branches, renaming volumes in the inventory table when overwritten by Backup, proved to be very timing dependent.  This has been fixed and should no longer be a problem.  *7En *4Ea *7Dr"  Changes from version 2.8 to 2.8-1  SYSWARE 3.2 Compatibility  Branches now provides explicit support for Professional Software's backup scheduler, archive management and file location package.  Support is provided for SYSWARE V3.2 and up.  Earlier versions of BACPLUS are not compatible.  The sole known point of incompatiblity is in interface between SYSWARE and Branches when the SYSWARE user wishes to use the tape library to initialize tapes.  This cannot be done at this time.g  Professional Software, Inc. and Acorn Software are working to resolve this incompatibility in a future release of Branches and SYSWARE.   Changes from version 2.7 to 2.8  New Device Supports1  Branches now supports the following new devices:i2  SpectraLogic 4000 4mm and 9000 8mm tape libraries  	device type: STL4000, STL9000  *7Eo *3Ef *7D,   Changes from version 2.6 to 2.7  New Device Supporte1  Branches now supports the following new devices:s  Breece Hill Q7 DLT libraryr  	device type: Q7S7  Digital and Quantum DLT2000, DLT2700, DLT4000, DLT4700t4  	 devices types:  DLT200, DLT2700, DLT4000, DLT4700  DEC C++ supportT  Was introduced.  The Branches images are now compiled and linked instead of VESTed.  Mixed Architecture Supporthj  You may install Branches for both Alpha and VAX processors using the same root directory in your cluster.  License Remindero  Branches now correctly reminds you of the status of you evaluation license.  Mail messages to that effect are sent to the SYSTEM account.  a   &  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   *7Er *2Ee *7De9  Example of a blank key request form for the node, QUICK.,K  Log into any account on the system to which the data library is connected.t$  $ BRANCH LICENSE/OUTPUT=LICENSE.TXT  ",  Create a license request form for the node.  $ TYPE LICENSE.TXTo  S&  Key Request Form:       BRANCHES V2.60  Date:                   27-MAR-1995 20:36:07.74  iC  To obtain your Software Key, send this form containing your SystemfK  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 usel  of BRANCHES V2.6.  g%                  Acorn Software, Inc.                   267 Cox St."                  Hudson, Ma. 01749  c:                  Phone:  508-568-1618    Fax: 508-562-11334                  E-Mail: LICENSE-REQUEST@ACORNSW.COM  tJ  Please complete this software key request form by providing the followingK  information before sending this form to Acorn Software, Inc. or your local H  Branches distributor.  Only key request forms that have been filled out  completely can be processed.W   C          Company:        _________________________________________  C          Address:        _________________________________________ fC                          _________________________________________ eC                          _________________________________________ vC                          _________________________________________ uC          Country:        _________________________________________ iC          Phone:          _________________________________________ gC          Fax:            _________________________________________ CC          Contact Person: _________________________________________ oC          Title:          _________________________________________ 7   B          Data Library Manufacturer:      -------------------------B          Data Library Model:             -------------------------  nN  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)tM  for additional VAXes in your VAXcluster, log in to those VAXes and issue then  s)          BRANCHES LICENSE/OUTPUT=filenamed  o  command for Branches.  lD  SIC:    BRN2-4WVLB7-E3CNXX-XGFXB5---3CG4W4-WD4MT5-DGT0K6    (QUICK)  4  $ EDIT LICENSE.TXT1    *7Ee *2D ]  Using your favorite editor, complete the key request form.  Please see the next section for s+  an example of a complete key request form.t *2Er *2Ia *7De  Using your favorite editor, complete the key request form.  Please see the next section for an example of a complete key request form.o *7Et *2E  *7Di   (  Example of a completed key request form(  Unauthorized use is strictly forbidden!  Username: MUNROE   Password: t   R  Log into any account to which the data library is connected and fill in the form.   $  $ BRANCH LICENSE/OUTPUT=LICENSE.TXT  t  $ TYPE LICENSE.TXTd&  Key Request Form:       BRANCHES V2.60  Date:                   27-MAR-1995 20:36:07.74  iC  To obtain your Software Key, send this form containing your System K  Identification Code (below) to Acorn Software, Inc., or contact your AcorneP  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 usea  of BRANCHES V2.6.  i%                  Acorn Software, Inc.T                  267 Cox St."                  Hudson, Ma. 01749  c:                  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 localaH  Branches distributor.  Only key request forms that have been filled out  completely can be processed.d  sC          Company:        Data Library Specialists_________________ eC          Address:        946 Massachusetts Avenue_________________  C                          Cambridge, MA. 02139_____________________ lC                          _________________________________________ tC                          _________________________________________ .C          Country:        USA______________________________________  C          Phone:          (617) 491-7474___________________________ uC          Fax:            (617) 491-7475___________________________ sC          Contact Person: D. Dewey_________________________________ tC          Title:          V.P., Marketing__________________________ m  eB          Data Library Manufacturer:      Exabyte------------------B          Data Library Model:             210----------------------  nN  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)mM  for additional VAXes in your VAXcluster, log in to those VAXes and issue the@  .)          BRANCHES LICENSE/OUTPUT=filenameW  a  command for Branches.  tD  SIC:    BRN2-4WVLB7-E3CNXX-XGFXB5---3CG4W4-WD4MT5-DGT0K6    (QUICK)  d  WB  Send the completed form to us at Acorn Software via the Internet. *7Eo *2Dc[  The quickest way to sendkey request forms is by electronic mail on the Internet.  Here is a  how to do it: *2Ee *2Iu *7Deh  The quickest way to sendkey request forms is by electronic mail on the Internet.  Here is how to do it: *7Ee *2Em *7De6  $ MAIL LICENSE.TXT MX%"LICENSE-REQUEST@ACORNSW.COM" -  	/SUBJECT="License Request"   L  Send the completed form to us at Acorn Software via  a FAX or postal system *7E  *2D X  If you do not have access to the Internet, fax the completed key request form to Acorn 
  Software: *2E7 *2IO *7Dca  If you do not have access to the Internet, fax the completed key request form to Acorn Software:i *7Ei *2Et *7Do  1 (508) 562-1133eK  Or, send the completed via the postal system or your carrier of choice to:n  Acorn Software, Inc.   267 Cox St.  Hudson, MA 01749  USA  	  n *7El *2Di#  .c.Acorn Software Problem Report ; L  To report a problem, you must first put together the information that will J  allow us to diagnose the problem, then contact us with this information, -  either by the Internet, by telephone or Fax.r  .c1.Helpful Information;  *2Ee *2I  *7Do  Acorn Software Problem Report s  To report a problem, you must first put together the information that will allow us to diagnose the problem, then contact us with this information, either by the Internet, by telephone or Fax.t  Helpful Information *7Eu *2E  *7Ds5  First, assemble the information we need to help you:i *7Ey *2Dy;  Step 1  Use BRNCH_SYSTEM:BRNCH-PROBLEM-REPORT.TEMPLATE as  D  your basis for the software problem report and create a file named F  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 e	  problem.e *2Ee *2I  *7Do  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    *7E  *6DtK  	If you were able to duplicate the circumstances that caused the problem.  *6Ed *2Ee *6De'  	The location of the file, SYSUAF.DATr>  	The definition of the SYSUAF logical name, if it is defined *6Ea *2DfD  	The privileges (specifics) of the account from which you started A  Branches.  We need the details since not all accounts such as a .4  system managers account have the same privileges.  *2Es *2Ia *6D7  	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.   *6E  *2E  *6D -  	The version number of Branches and of VMS.  *6Ee *6Ia *7D K  	If you were able to duplicate the circumstances that caused the problem.h'  	The location of the file, SYSUAF.DATk>  	The definition of the SYSUAF logical name, if it is defined  	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. a-  	The version number of Branches and of VMS.a *7Ep *6Ee *2DpI  Step 2  If the problem involves a crash, locate the process dump.  When nQ  Branches crashes, it leaves a process dump on your system device.  The location W?  can vary according to where the default directory is when the rH  BRNCH-STARTUP command procedure starts.  Check the date of the process E  dump with the DIRECTORY command to identify the one that might have t  been part of the problem. *2Ea *2I  *7DY / 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.l *7EQ *2Em *7D0/  Step 3  Make a backup save set of these files:   BRNCH-PROBLEM-REPORT.TXTD  BRNCH-OPCOM-CATCHER.DMP%  BRNCH_SYSTEM:BRNCH-OPCOM-CATCHER.EXEr  BRNCH_SCRATCH:BRNCH-OUTPUT.LOG   BRNCH_SCRATCH:BRNCH-ERROR.LOG  SYS$SYSTEM:ANALIMDMP.EXEB *7Ee *2D R  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.t *2Ei *2I. *7Dl  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. *7Es *2E  *7Dh  FTP ACORNSW.COM  USER INCOMING  BINARYa
  PUT filenameh  EXITa *7Ek *2DnR  If you are not connected to the Internet, copy the backup save set to one of the   following media:l *2Ee *2Iu *7Dob  If you are not connected to the Internet, copy the backup save set to one of the following media: *7E$ *2EC *7DE  TK50 CartridgeE  TK70 Cartridge 	  4 mm DATe0  5 1/4" Sony optical disk cartridge (ISO format)
  8 mm tape *7Er *2D   .c1.Contact us by Internet;M  This the fastest way to get to us without a doubt.  During the installation iC  for Branches, the BRNCH_SUPPORT parameter gets set as the default  I  support address.  Please use the Branches utility command just for that t	  purpose:y:  		$ @BRNCH_SYSTEM:BRNCH-PROBLEM-REPORT.COM backupSaveSet 
  [support] *2E  *2Iy *7Dy  Contact us by Internet   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: C  		$ @BRNCH_SYSTEM:BRNCH-PROBLEM-REPORT.COM backupSaveSet [support]M *7EL *2EE *7DE  A *7EW *2D H  backupSaveSet  is the fully qualified file name of the backup save set :  containing the problem report and diagnostic information.J  support is the email address that will reach support@acorn.dmc.com.  The 5  installation parameter BRNCH_SUPPORT is the default. .  .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:_ *2E_ *2I_ *7D   backupSaveSet  is the fully qualified file name of the backup save set containing the problem report and diagnostic information._~  support is the email address that will reach support@acorn.dmc.com.  The installation parameter BRNCH_SUPPORT is the default.)  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: *7E_ *2E_ *7D_  Acorn Software, Inc.   267 Cox St.  Hudson, Ma. 01749  USA1  attn: Customer Services, Software Problem Report  *7E: *2D J  If you need operational support and you have a customer services support ;  contract, please call or FAX a software problem report to:l *2E. *2Ii *7De  If you need operational support and you have a customer services support contract, please call or FAX a software problem report to: *7EC *2EI *7D/  VOICE:	1 (508) 568-1618 x16  FAX	1 (508) 562-1133C *7EB *2DWJ  Our business hours are 8:00 am to 5:00 PM EST (GMT -5:00).  We will call !  you/email you within 24-hours.  o  ec  Acorn Software                                                                                       .c1.Customer Service Policy; H  July 1993 -- We are pleased to have you join our community of Branches M  users.  We are committed to the best possible technical support for you and  K  your data library software requirements.  Our software is the best in the rQ  business, but occasionally difficulties in installation or operation occur.  We iK  stand ready to assist you in the diagnosis and recovery from errors.  Our /L  technical support is available by telephone and Internet.  We are open for +  business during the usual hours EST (USA).2F  As with all our customers, we will make every effort to resolve your M  technical difficulties or help you diagnose them to the level that you then y8  can seek information from the source of the difficulty.N  On a regular basis, we issue new versions of our documentation, both printed N  and on-line help as well as our software.  The newest versions are available N  on the Internet or at your request.  If you want to check what is the latest K  new feature, please check the on-line help.  That is where we have placed ,N  a summary of the latest new features.  In the on-line help is also a section L  called,  tips and techniques, which contains answers to the questions that   we hear frequently from you.iM  We will advise you of these newest versions both by Internet and reoccurent c  mailings.      *2Ec *2Ii *7Duj  Our business hours are 8:00 am to 5:00 PM EST (GMT -5:00).  We will call you/email you within 24-hours.     z  Acorn Software                                                                                    Customer Service Policy / July 1993 -- We are pleased to have you join our community of Branches users.  We are committed to the best possible technical support for you and your data library software requirements.  Our software is the best in the business, but occasionally  -difficulties in installation or operation occur.  We stand 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).e  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.e / 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.  If you want to check what is the latest new feature, plea -se check the on-line help.  That is where we have placed a summary of the latest new features.  In the on-line help is also a section called,  tips and techniques, which contains answers to the questions that we hear frequently from you.X  We will advise you of these newest versions both by Internet and reoccurent mailings.    2     u  7  Acorn Software, Inc.o  n  y  q  Acorn Software, Inc.o     l        e  t  H     h     o  :  7  		     7     M     E        "  E  -  U  @  R  .  ";   	Acorn Software, Inc.	            Branches  Release Notesm     a  c2  Branches Release Notes	Acorn Software, Inc.	       I  o  o  t  v<  Branches Release Notes	Acorn Software, Inc.        	         c     S  w  :  2   K  Branches Release Notes	Acorn Software, Inc.	                                 u   .  Branches Release Notes	Acorn Software, Inc.	   )  2  3   3  Branches  Release Notes	Acorn Software, Inc.	        r     c  c  o   ;   	Acorn Software, Inc.	             Branches Release Notes       M  Branches  Release Notes	Acorn Software, Inc.                            	   t  r  p  t  t3  Branches  Release Notes	Acorn Software, Inc.	           b'   		             Branches Release Notesn     t  Branches Release Notes		      *7EF *2E  *7DH  f  I *7Ea *7I  *8De / 


VIRTUAL Branchestm
Release Notes













storage in a nutshell
Acorn Software, Inc.
Hudson, MA

 










Document Version:	1.0
Revision Information:	This manual supersedes all 	previous versions of 	documentation.
Software Version:	2.2-4 /
Operating System and Version:	OpenVMS VAX version 5.5 or 	later
	OpenVMS AXP version 6.0 or 	later


Copyright  1994-1996, Acorn Software, Inc.
All rights reserved
Information in this document is subject to change without notice and does not const -itute a commitm / ent on the part of Acorn Software, Inc.  The software described herein is provided subject to a license agreement and the descriptions may include proprietary information belonging to Acorn Software, Inc.  No part of this manual may be reproduced i /n whole or in part by any means, including electronic means, without specific written permission from Acorn Software, Inc. or as part of a specified permission contained within a specific software license agreement.  The associated software may not  -be redistribute / d, copied, or reproduced in any form except for specified user backup as described in the software license agreement.

VIRTUALBranches, VIRTUALBranches for OpenVMS, VIRTUALBranches/VMS, VIRTUALBranches for Windows/NT, VIRTUALBranches/NT, the Acorn  /Software logo, "The data library software vendor of choice" and "A leader in data library  management software" are trademarks of Acorn Software, Inc. 

All other trademarks or registered trademarks are the properties of their respective manufacture -rs.





Printe / d on recyclable paper.

VIRTUALBranchestm, version  2.2-4
What conventions we used in these release notes
Our documentation follows these conventions:
Character		Convention
italics		indicates optional items that you substitute the specific 
			name /s or numbers in Branches or DCL commands
courier, roman	indicates Branches or DCL commands and any examples of 
			either  Branches licensing or program documentation
	shaded note	indicates that we ask you to pay  very strict attention 
			to the in -formation conta / ined in the gray area.
double underline	indicates that the text is a hot spot in the http://www.acornsw.com/HTML  version of 
			the manual.
shaded text	indicates that the material discussed will be
			implemented in a later version of VIRTUALBranc /hes .


VirtualBranches Release Notes
This chapter presents, in order of their occurrence, the changes from the previous versions of VIRTUAL Branches to the current version of VIRTUAL Branches.  We will include these items in the user guide and  we  -have them here  / for your quick reference.
Changes from 2.2-3 to 2.2-4
New Device Support

VIRTUALBranches now supports the HP FX series of MO Jukeboses.
	DeviceTypes: HP40FX, HP80FX, and HP160FX
Media not software enabled and Pioneer 6xx series changers

If your h /ost computer is fast enough you may experience intermittent failures accessing data on CDROMs in Pioneer 6xx series changers.  As near as we can tell this is because the 6xx series drive responds immediately to an IO$_PACKACK despite the fact that t -he media in the /  drive may not have been swapped out or new media inserted.
The solutione to this problem is to enable the LOAD-TIMEOUT configuration line for P6xx boxes.
If you are experiencing this problem, add the following line to your configuration table entr /y:
	LOAD-TIMEOUT	1
and try again.  If you continue to see the failures, increment the value of the LOAD-TIMEOUT line until the problem goes away.
SHOW STATE MODE

A new parameter has been added to the SHOW STATE DCL command. 
This is used to determi -ne if the node  / upon which the DCL command is issued is the master node for a specified library.
BRNCH-VIRTUAL-SYSHUTDWN.COM

A system shutdown procedure has been added that dismounts all JB device mounted on your node.
If your node is acting as a master node for  /a library the associated JB devices will be dismount cluster wide.
Add the following reference to your system wide shutdown command procedure:
	@BRNCH_VIRTUAL_SYSTEM:BRNCH-VIRTUAL-SYSHUTDWN
Changes from 2.2-2 to 2.2-3
VIRTUALBranches didn't dump sig -nals properly.
 / 
It does now.
Additional ldebugging code was installed.

VIRTUALBranches didn't wait for the server when mounting volumes.

It does
What conventions we used in these release notes	
Changes from	
Changes from	
Changes from	
Changes from	
Changes fro /m	
Changes from	
Changes from	
Changes from 1.2-1 to 2.0	
 now.
Changes from 2.2-1 to 2.2-2
VIRTUALBranches didn't abort when any error during startup occurred.

It does now.
Export for Virtual Disks didn't delete the virtual disk container file.

I -t does now.
/SL / OT=number qualifier works for BRANCHES/VIRTUAL IMPORT command.

Branches/Virtual Import

Imports media into a library.  For data libraries with mailboxes, the specified media must be placed in the mailbox and then VIRTUALBranches will place the med /ia in the right spot.
This command requires:
	OPER and TMPMBX privileges.
Format	Branches/Virtual IMPORT 
Qualifiers	Notes
/LIBRARY[=DEFAULT]	The data library to which the media is to be imported.
/SLOT=number	The slot into which the physical media - is to be place / d.
/SYMBOL	When specified, IMPORT defines local DCL symbols of the form: BRNCH_VIRTUAL_JB_DEVICEn (n starts at 0) for each JB device brought online as a consequence of the import.  If global symbols are required, you must promote the provided symbo /ls to global context.

Changes from 2.2 to 2.2-1
License expiration wasn't stopping VIRTUALBranches

It does now.
SE-RANGE configuration line now works on all libraries

The SE-RANGE now controls the enabling of JB devices.  If you specify an SE-RAN -GE, only those  / JB devices within that range are turned online, even if the hardware claims that media are present.
New Device Support

VIRTUALBranches now support the Pioneer DRM-1004X CDROM changer.
	DeviceType: P1004X
Multiple treading of Mount At Boot option.
 /
VIRTUALBranches will now use all drives simultaneously when mounting devices at boot time.  The BRANCHES/VIRTUAL SHOW CONTENTS/COMMAND=filename command has been modified to generate the necessary code for this.
Virtual disk demonstartions wouldn't  -load properly o / n AXP

The wrong device driver name was being used. 
Disk Arbitration was not working

Part of the driver interface restructuring that occurred in 2.2 had the effect of disabling the dwell time used by the disk arbitration.  This has been fixed.
Ch /anges from 2.1 to 2.2
New JBDRIVER

There has been some moderate work on the JBDRIVER in this version of VIRTUALBranches.  This has been done as part of the preperatory work for further simplification of the driver and better integration between the - VAX, AXP Step1 / , and AXP Step 2 versions.  Unfortunately, this means that this release of requires that you reboot your system after installing VIRTUALBranches.
5004X Export

Its not pretty, but we have figured out how to get the 5004X to export media.  The proce /dure is as follows:
	BRANCHES/VIRTUAL EXPORT
At which point, all activity stops until the export is completed.
	Open the door of the 5004X.
	Remove the exported CDROM from the transporter.
	Close the door.
This completes the export operation.
Th -e export operat / ion may not be aborted.
Running VIRTUALBranches with missing or broken drives

Once a drive goes out of service you must shut down VIRTUALBranches and modify the configuration entry for the library in question in order to take a drive out of servic /e.  In the DRIVES line, replace the OpenVMS device name of the drive to be taken out of service with the keyword "DISABLED".  Then restart VIRTUALBranches.
BRANCHES/VIRTUAL SHUTDOWN/ABORT libraryName

Under normal circumstances, VIRTUALBranches requ -ires all device / s managed by the server to be dismounted prior to being able to shutdown the server.  Under some circumstances it may not be desirable or possible to do so.  The /ABORT qualifier bypasses the check for mounted devices and will immediately shutdown  /the server.
Note:	Use of this featur may result in a loss of data and the possible creation of unusable media.  It should only be used under emergency situations where it is imperative to shut your system down immediately or if you have been instruc -ted to use this /  feature by Acorn Software technical support.
BRANCHES/VIRTUAL IMPORT/SYMBOL

When /SYMBOL is specified, IMPORT defines local DCL symbols of the form: BRNCH_VIRTUAL_JB_DEVICEn (n starts at 0) for each JB device brought online as a consequence of th /e import.  If global symbols are required, you must promote the provided symbols to global context.

For example, if you were importing a cartridge into a MO jukebox and it wound up in slot 7, two symbols would be defined:

	BRNCH_VIRTUAL_JB_DEVICE0 - = "JBA16:"
	BR / NCH_VIRTUAL_JB_DEVICE1 = "JBA17:"

This can be used to automate population of the inventory table.

6nnX support

VIRTUALBranches now requires that the underlying physical devices of the Pioneer DRM-6nnX be present and online in order for the JB de /vices corresponding to the underlying DK devices to be turned online.
Changes from 2.0-2 to 2.1
Access Violation

There was a memory leak in the OPCOM message processing that, under severe load, resulted in an eventual access violation.  Typically,  -this required a / n OPCOM message every 10 seconds for 3 days to hit.
Changes from 2.0-1 to 2.0-2
LSBNOTVALID

There was a case we missed when we put in the code that ignored the occasional lock mastering problem on startup.  This release fixes that problem.
Changes / from 2.0 to 2.0-1;
5004X IMPORT

We have figured out how to do an IMPORT operation acceptably for the 5004X.  The procedure is as follows:
	BRANCHES/VIRTUAL IMPORT
At which point, all activity stops until the import is completed.
	Open the door o -f the 5004X.
	 / Place the CDROM to be imported into the transporter in the proper orientation.
	Close the door.
This completes the import operation.
If you have issued an import command in error, you may abort the import operation by opening the door of the 5004X / for 5 seconds and then closing it.
The user interface on this will change in later versions of VIRTUALBranches .
Changes from 1.2-1 to 2.0
Disk Arbitration and scheduling

Has been completely redesigned.  As a consequence VirtualBranches is substan -tially more rob / ust in the face of hardware errors.  In addition, is is now possible to set individual dwell times per JB device and it is possible to set "priorities" on JB devices allowing preemptive scheduling of swapping.  For details, see the BRANCHES/VIRTUAL / SET command in the user manual.
System crashes cause Invalid Lock Value Block errors

VirtualBranches ignores Invalid Lock Value Block errors during server startup allowing a crash of the lock master in cluster environments.
Pioneer DRM-5004X suppo -rt

The Pioneer /  DRM-5004X is now fully supported.  We have added a new configuration line entry:

SE-RANGE		n-m

to allow users to control the range of slots available to the DRM-5004X hardware.  This allows users to tailor the "size" of the DRM-5004X to avoid th -e excessively long initialization time imposed by Pioneer's hardware design.  n and m are slot numbers.  To restrict access to the first magazine in a Pioneer DRM-5004X, set the SE-RANGE to:

SE-RANGE		0-99



		   



 *8Eo *7En *8IV *11D                T  Branchestmo  Release Notes  A  a  e  T  h  c     S  w     o  T  d     r     t  Acorn Software, Inc.a  Hudson, MAi  a  l  a     a  e  s  w  "  e  Document Version:	2.3-3 *11E *11D;  Revision Information:	This manual replaces version 	2.3-2.i *11E *9D   Software Version:	2.8-7 *9E
 *9In *10D  Software Version:	2.10A *10E *10I *11D  Software Version:	2.10t *11E *10E *9Eh *11D7  Operating System and Version:	VMS version 5.4 or laterC  a  r,  Copyright  1992-1997, Acorn Software, Inc.  All rights reserved / 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..c  VAX, VMS, VAXStation, and VAX Cluster are registered trademarks of Digital Equipment Corporation. e.  SCEA is a trademark of CMD Technologies, Inc. / Branches, VirtualBranches, VirtualBranches for OpenVMS, VirtualBranches for Windows/NT, HSManager, Squash, MODISK, the Acorn Software logo, "The data library software vendor of choice" and "A leader in data library  management software" are tradema -rks of Acorn Software, Inc.  /  EXABYTE is a trademark of Exabyte Corporation. D  LIBRA DATStacker is a trademark of Diverse Logistics, Incorporated.d  All other trademarks or registered trademarks are the properties of their respective manufacturers.  
     u  n  o  i  r  e  Printed on recycled paper.U  o  Table of Contents	  Preface	.-  What information our documentation contains	f   Who this manual is written for	1  What conventions we used in these release notes	f  Branches Release Notes	#  Changes from version 2.8 to 2.8-1	O!  Changes from version 2.7 to 2.8	o!  Changes from version 2.6 to 2.7	a'  Branches License and Key Request Form	L  Acorn Software Problem Report	i  Customer Service Policy	w  h  e  Preface  i  January 1997 --  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.  :  In this preface, you will find the following information:.  	what information our documentation contains!  	who this manual is written forn  	what conventions we usedI,  What information our documentation contains / Our documentation set consists of three items:  the user guide, related release notes and on-line help.  The user guide contains information on installation and use; these release notes are kept as current as printed matter can be.  The on-line helt -p is meant to jog your memory of specific details of operation and serves as the  most up-to-date documentation.    *11E *9D   Although we will keep you  informed on new product features by reoccurent mailings, you are welcome to take a copy of our documentation at any time  from the Internet.  The Internet address to obtain these documents from is: docserv@dmc.com.   *9EV *9IL *11D / Although we will keep you  informed on new product features by reoccurent mailings, you are welcome to take a copy of our documentation at any time  from the Internet.  This, and all other Acorn documentation, is available from our website at http: -//www.acornsw.com/.   *11E *9Ee *11D  Who this manual is written forR  We have written our documents with the experienced VAX/VMS system manager and application developer in mind.  We have relied upon your knowledge and experience as well as your access to the complete VMS documentation set.   *11E *9DE / If you are taking the first steps with a data library management system, we have included several sections of examples in the installation chapter of the user guide.  Should you experience problems, our error messages section contains helpful infor -mation 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@acornsw.com.c *9Et *9Ih *11D / If you are taking the first steps with a data library management system, we have included several sections of examples in the installation chapter of the user guide.  Should you experience problems, our error messages section contains helpful infor -mation 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@acornsw.com.i *11E *9Ed *11D  s  t0  What conventions we used in these release notes-  Our documentation follows these conventions:i  Character		Conventions  italics		indicates optional items that you substitute the specific names or 			numbers in Branches or DCL commandsh|  courier, roman	indicates Branches or DCL commands and any examples of either 			Branches licensing or program documentationv  shaded note	indicates that we ask you to pay  very strict attention to 			the information contained in the gray area.  f  e  Branches Release Notesa  This chapter presents, in order of their occurrence, the changes from the previous versions of Branches to the current version of Branches.  We have included these items in the user guide and  we have them here for your quick reference.o *11E *9Ie *10D"  Changes from version 2.9 to 2.10A *10E *10I *11D!  Changes from version 2.9 to 2.10n *11E *10E *11D  New Device Supporti1  Branches now supports the following new devices:  *11E *10D=  Storage Technologies 9710, 9714, and 9740 Tape Data Librarysh*  	device types: STK9710, STK9714, STK9740  *10E *10I *11DC  Storage Technologies 9710, 9714, 9730, and 9740 Tape Data Librarysr3  	device types: STK9710, STK9714, STK9730, STK9740 n *11E *10E *11D  Breece Hill Q2 DLT library   	device type: Q2   SCSI Interface Redesign  The low level interface to SCSI has been redesigned pending ports to other platforms and to encourage reuse of the code within our own products.e  SHOW CONTENTS+  Was showing everything as a BACKUP volume.y  Miscellaneous Tracing  Has been fully implemented, allowing our support folks to find out most, if not all, of whats going on inside Branches at your site..$  Changes from version 2.8-8 to 2.8-9  Branches Show Contentst  oI  Displays information on the contents of the objects managed by Branches.i  Format	Branches SHOW CONTENTS  Qualifiers	Notess7  /ALL	All entries in the inventory table are displayed.am  /COLUMNS=n	Specifies the number of columns for listing contents; either 1, 2, or 3.  The default value is 3.s@  /DRIVE	The state of drives in the inventory table is displayed.<  /FULL	All information in the inventory table is displayed..q  /[NO]HEADER	Identifies the data library (with SHOW CONTENTS).  Suppressed by /NOHEADER.  The default is /HEADER.I  /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 '*'.M  /LIBRARY[=DEFAULT]	Specifies the library whose contents are to be displayed.b  /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.l-  /VIDS	The bar code information is displayed.o  .0  The Show Contents command displays these codes:  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.
  M	The volume is mounted. Q  U	The volume is unavailable; one of the other surfaces has already been mounted.u"  S	The volume is a SCRATCH volume.B  If no additional information is shown, the volume may be mounted.2  Unload all drives correctly parses library names. / The parsing of library names for the UNLOAD all drives was incorrectly parsing the name as a TPA$_STRING.  Libraries with non-alphanumeric characters in their names, e.g., "$" or "_", would fail to parse and the Branches system startup command procE -edure would hang attempting to unload all the drives in the library.tD  ACL 4/52 error recovery on source empty or destination full errors.  The ACL 4/52 specification requires that the error recovery when the Move Medium SCSI command gets an error indication that either the source of the move is empty or the destination of the move is full is to do the following:2  Attempt a Read Element Status and retry the move.`  If this fails, perform an Initialize Element Status, a Read Element Status, and retry the move.  This has been done, but if the move still fails at this point, the inventory table is out of synchronization with the state of the data library and Branches will fail at startup time with an Internal Logic Error.e  Should this happen, you should take steps to correct the inventory table manually or delete the inventory table, restart Branches, and manually populate the inventory table.$  Changes from version 2.8-7 to 2.8-8  New Device Support 0  Branches now supports the following new device:#  Odetics ACL 4/52 Tape Data Libraryw  	device type: ACL452a *11E *9Es *11D$  Changes from version 2.8-6 to 2.8-7 *11E *9Ds  Segate Python Product names *9E0 *9I  *11D  Seagate Python Product namesi *11E *9E  *11Ds  Keep changing.  This version of Branches simply extends the Python licensing to those versions we've seen to date.-$  Changes from version 2.8-5 to 2.8-6  New Device Support81  Branches now supports the following new devices:o'  Hewlett Packard FX series MO jukeboxes &  	device type: HP40FX, HP80FX, HP160FX  SysWare Supportz  Branches was not recognizing SysWare messages indicating that the wrong volume was in a tape drive.  This has been fixed. *11E *9Dl$  Changes from version 2.8-4 to 2.8-5  Sysware Support *9E8 *9I9 *11D,  Changes from version 2.8-4 to 2.8-5 Sysware *11E *9Ef *11DB  Branches now supports the PREINIT processing provided by Sysware. *11E *9Di$  Changes from version 2.8-3 to 2.8-4  Sysware Support *9Ea *9In *11D,  Changes from version 2.8-3 to 2.8-4 Sysware *11E *9Ej *11D$  Branches now fully supports Sysware *11E *9Dc$  Changes from version 2.8-2 to 2.8-3 *9Ec *9Ie *11D)  Changes from version 2.8-2 to 2.8-3 New   *11E *9Eg *11D  New Device Supports1  Branches now supports the following new devices:o *11E *9Dw   Pioneer DRM-1004X CDROM Changer *9Ee *9Io *11D!  Pioneer DRM-1004X CD-ROM Changern *11E *9Ec *11D  	device type: P1004Xc *11E *9Dr$  Changes from version 2.8-2 to 2.8-2,  Renaming Volumes as a side effect of BACKUP *9En *9Ie *11D.  Changes from version 2.8-2 to 2.8-2 Renaming #  Volumes as a side effect of BACKUP, *11E *9Ec *11D  A long standing feature of Branches, renaming volumes in the inventory table when overwritten by Backup, proved to be very timing dependent.  This has been fixed and should no longer be a problem.  *11E *9Da"  Changes from version 2.8 to 2.8-1  SYSWARE 3.2 Compatibility  Branches now provides explicit support for Professional Software's backup scheduler, archive management and file location package.  Support is provided for SYSWARE V3.2 and up.  Earlier versions of BACPLUS are not compatible.  The sole known point of incompatiblity is in interface between SYSWARE and Branches when the SYSWARE user wishes to use the tape library to initialize tapes.  This cannot be done at this time.e  Professional Software, Inc. and Acorn Software are working to resolve this incompatibility in a future release of Branches and SYSWARE.   Changes from version 2.7 to 2.8 *9Et *9Io *11D/  Changes from version 2.8 to 2.8-1 SYSWARE 3.2 n  Compatibility  Branches now provides explicit support for Professional Software's backup scheduler, archive management and file location package.  Support is provided for SysWare V3.2 and up.  Earlier versions of BACPLUS are not compatible.  The sole known point of incompatibility is in interface between SysWare and Branches when the SYSWARE user wishes to use the tape library to initialize tapes.  This cannot be done at this time.  Professional Software, Inc. and Acorn Software are working to resolve this incompatibility in a future release of Branches and SysWare.%  Changes from version 2.7 to 2.8 New o *11E *9El *11D  New Device Supporto1  Branches now supports the following new devices:t2  SpectraLogic 4000 4mm and 9000 8mm tape libraries  	device type: STL4000, STL9000e   Changes from version 2.6 to 2.7 *11E *9Du  New Device Supporti *9E  *9Il *11D  New New Device Supporto *11E *9Et *11D1  Branches now supports the following new devices:p  Breece Hill Q7 DLT libraryo  	device type: Q7o7  Digital and Quantum DLT2000, DLT2700, DLT4000, DLT4700i4  	 devices types:  DLT200, DLT2700, DLT4000, DLT4700  DEC C++ supportT  Was introduced.  The Branches images are now compiled and linked instead of VESTed.  Mixed Architecture Support.j  You may install Branches for both Alpha and VAX processors using the same root directory in your cluster.  License Reminderf  Branches now correctly reminds you of the status of you evaluation license.  Mail messages to that effect are sent to the SYSTEM account.  ,  d&  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. K  Log into any account on the system to which the data library is connected.e$  $ BRANCH LICENSE/OUTPUT=LICENSE.TXT  r,  Create a license request form for the node.  $ TYPE LICENSE.TXTi  h&  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 System K  Identification Code (below) to Acorn Software, Inc., or contact your AcornmP  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 useg  of BRANCHES V2.6.  i%                  Acorn Software, Inc.o                  267 Cox St."                  Hudson, Ma. 01749  c:                  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 localrH  Branches distributor.  Only key request forms that have been filled out  completely can be processed.B  cC          Company:        _________________________________________ nC          Address:        _________________________________________ nC                          _________________________________________ tC                          _________________________________________ aC                          _________________________________________ rC          Country:        _________________________________________ nC          Phone:          _________________________________________ eC          Fax:            _________________________________________  C          Contact Person: _________________________________________ eC          Title:          _________________________________________     B          Data Library Manufacturer:      -------------------------B          Data Library Model:             -------------------------  SN  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) M  for additional VAXes in your VAXcluster, log in to those VAXes and issue thef   )          BRANCHES LICENSE/OUTPUT=filenameh  b  command for Branches.  sD  SIC:    BRN2-4WVLB7-E3CNXX-XGFXB5---3CG4W4-WD4MT5-DGT0K6    (QUICK)  d  $ EDIT LICENSE.TXTS  W  Using your favorite editor, complete the key request form.  Please see the next section for an example of a complete key request form.o   (  Example of a completed key request form(  Unauthorized use is strictly forbidden!  Username: MUNROEa  Password: n  tR  Log into any account to which the data library is connected and fill in the form.  r$  $ BRANCH LICENSE/OUTPUT=LICENSE.TXT  o  $ TYPE LICENSE.TXTe&  Key Request Form:       BRANCHES V2.60  Date:                   27-MAR-1995 20:36:07.74  tC  To obtain your Software Key, send this form containing your SystemhK  Identification Code (below) to Acorn Software, Inc., or contact your AcornnP  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 usei  of BRANCHES V2.6.  f%                  Acorn Software, Inc.i                  267 Cox St."                  Hudson, Ma. 01749  t:                  Phone:  508-568-1618    Fax: 508-562-11334                  E-Mail: LICENSE-REQUEST@ACORNSW.COM  eJ  Please complete this software key request form by providing the followingK  information before sending this form to Acorn Software, Inc. or your localuH  Branches distributor.  Only key request forms that have been filled out  completely can be processed.i  ,C          Company:        Data Library Specialists_________________ yC          Address:        946 Massachusetts Avenue_________________ sC                          Cambridge, MA. 02139_____________________ eC                          _________________________________________ pC                          _________________________________________ mC          Country:        USA______________________________________  C          Phone:          (617) 491-7474___________________________ SC          Fax:            (617) 491-7475___________________________ yC          Contact Person: D. Dewey_________________________________ hC          Title:          V.P., Marketing__________________________ p  iB          Data Library Manufacturer:      Exabyte------------------B          Data Library Model:             210----------------------  nN  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 thee  h)          BRANCHES LICENSE/OUTPUT=filenamed  t  command for Branches.  oD  SIC:    BRN2-4WVLB7-E3CNXX-XGFXB5---3CG4W4-WD4MT5-DGT0K6    (QUICK)  o  wB  Send the completed form to us at Acorn Software via the Internet. *11E *9Drh  The quickest way to sendkey request forms is by electronic mail on the Internet.  Here is how to do it: *9Ee *9Il *11Di  The quickest way to send key request forms is by electronic mail on the Internet.  Here is how to do it:e *11E *9E  *11D6  $ MAIL LICENSE.TXT MX%"LICENSE-REQUEST@ACORNSW.COM" -  	/SUBJECT="License Request"  oL  Send the completed form to us at Acorn Software via  a FAX or postal systema  If you do not have access to the Internet, fax the completed key request form to Acorn Software:   1 (508) 562-1133 K  Or, send the completed via the postal system or your carrier of choice to:   Acorn Software, Inc.   267 Cox St.  Hudson, MA 01749  USA  .     Acorn Software Problem Report h  To report a problem, you must first put together the information that will allow us to diagnose the problem, then contact us with this information, either by the Internet, by telephone or Fax.   Helpful Information5  First, assemble the information we need to help you:   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.8'  	The location of the file, SYSUAF.DATC>  	The definition of the SYSUAF logical name, if it is defined  	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. 8-  	The version number of Branches and of VMS.l / 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.s/  Step 3  Make a backup save set of these files:s  BRNCH-PROBLEM-REPORT.TXT9  BRNCH-OPCOM-CATCHER.DMP%  BRNCH_SYSTEM:BRNCH-OPCOM-CATCHER.EXEV  BRNCH_SCRATCH:BRNCH-OUTPUT.LOG,  BRNCH_SCRATCH:BRNCH-ERROR.LOG  SYS$SYSTEM:ANALIMDMP.EXEe  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.  FTP ACORNSW.COM  USER INCOMING  BINARY2
  PUT filename3  EXITab  If you are not connected to the Internet, copy the backup save set to one of the following media:  TK50 Cartridged  TK70 Cartridgec	  4 mm DATo0  5 1/4" Sony optical disk cartridge (ISO format)
  8 mm tape  Contact us by Internet.  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:.C  		$ @BRNCH_SYSTEM:BRNCH-PROBLEM-REPORT.COM backupSaveSet [support]f  r  backupSaveSet  is the fully qualified file name of the backup save set containing the problem report and diagnostic information.3 *11E *9Da~  support is the email address that will reach support@acorn.dmc.com.  The installation parameter BRNCH_SUPPORT is the default. *9Ep *9Ie *11D|  support is the email address that will reach support@acornsw.com.  The installation parameter BRNCH_SUPPORT is the default. *11E *9En *11D)  Contact us by the carrier of your choiceS  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:  Acorn Software, Inc.l  267 Cox St.  Hudson, Ma. 01749  USA1  attn: Customer Services, Software Problem Report   If you need operational support and you have a customer services support contract, please call or FAX a software problem report to: *11E *9D   VOICE:	1 (508) 568-1618 x16 *9E0 *9IT *11D  VOICE:	1 (508) 568-1618 x5o *11E *9E  *11D  FAX	1 (508) 562-11339j  Our business hours are 8:00 am to 5:00 PM EST (GMT -5:00).  We will call you/email you within 24-hours.     z  Acorn Software                                                                                    Customer Service Policy / July 1993 -- We are pleased to have you join our community of Branches users.  We are committed to the best possible technical support for you and your data library software requirements.  Our software is the best in the business, but occasionally  -difficulties in installation or operation occur.  We stand 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).e  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.t / 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.  If you want to check what is the latest new feature, plea -se check the on-line help.  That is where we have placed a summary of the latest new features.  In the on-line help is also a section called,  tips and techniques, which contains answers to the questions that we hear frequently from you.X  We will advise you of these newest versions both by Internet and reoccurent mailings.    a  y     a  Acorn Software, Inc.o  e  y     Acorn Software, Inc.o     r  l  o  o  S  w     o        t  e  		     w     b  f        o  R  H  V  .  i         ;   	Acorn Software, Inc.	            Branches  Release Notes          2  Branches Release Notes	Acorn Software, Inc.	       5  1     F   <  Branches Release Notes	Acorn Software, Inc.        	         M     P  s  o  e  tK  Branches Release Notes	Acorn Software, Inc.	                                 d   .  Branches Release Notes	Acorn Software, Inc.	   B  c     t3  Branches  Release Notes	Acorn Software, Inc.	     d  t  c  l  l  a  e;   	Acorn Software, Inc.	             Branches Release Notes_  _  _M  Branches  Release Notes	Acorn Software, Inc.                            	   _  _         3  Branches  Release Notes	Acorn Software, Inc.	     _  _   '   		             Branches Release Notes_  _  _  Branches Release Notes		            *11E *8E_ *11I  This file is obsolete._ *11E