  
 HSManager
 User Guide               Acorn Software, Inc.   storage in a nutshell 
 Hudson, MA                          Document Version:	version 1.0 F Revision Information:	This manual supersedes all 	previous versions of documentation. Software Version:	version 1.0-2 > Operating System and Version:	OpenVMS VAX version 5.5 or later! 	OpenVMS AXP version 6.1 or later   + Copyright  1995-1996, Acorn Software, Inc.  All rights reserved M Information in this document is subject to change without notice and does not I constitute a commitment on the part of Acorn Software, Inc.  The software C described herein is provided subject to a license agreement and the M descriptions may include proprietary information belonging to Acorn Software, I Inc.  No part of this manual may be reproduced in whole or in part by any K means, including electronic means, without specific written permission from L Acorn Software, Inc. or as part of a specified permission contained within aH specific software license agreement.  The associated software may not beJ redistributed, copied, or reproduced in any form except for specified user6 backup as described in the software license agreement.  I Branches, VIRTUALBranches, Squash, MODisk and HSManager are trademarks of  Acorn Software, Inc.  I All other trademarks or registered trademarks are the properties of their  respective manufacturers.      Contents PREFACE	 CHAPTER 1 INTRODUCTION	 	 Features	  System Prerequisites	  CHAPTER 2 INSTALLING HSMANAGER	  Where and how to get HSManager	 ! Installing HSManager (VMSINSTAL)	   Example of Typical Installation	 Configuring HSManager	+ Creating an HSManager server configuration	 $ Deleting an HSManager Configuration	# Editing an HSManager Configuration	  Starting an HSManager Server	  Stopping an HSManager Server	 + In swapping files from an HSManager Server	 & Site wide space and policy management	 Starting HSManager	  Licensing HSManager	 Using HSManager	' CHAPTER 3 HSMANAGER SYSTEM INFORMATION	  System Startup	  System Shutdown	# System Variables and Logical Names	  CHAPTER 4 HSMANAGER COMMANDS	  HSMANAGER/SET/PROCESS=EXEMPT	  HSMANAGER/INSTALL	 HSMANAGER/LICENSE	 HSMANAGER/VERSION	 HSMANAGER/SHUTDOWN	  HSMSOFTLINK	
 HSMMOVEFILES	 
 HSMMAKESPACE	  CHAPTER 5 TROUBLE SHOOTING	  CHAPTER 6 APPLICATION NOTES	 ANALYZE/DISK/REPAIR	< APPENDIX A HSMANAGER ERROR MESSAGES AND RECOVERY TECHNIQUES		 RMS$_FUL	  APPENDIX B LICENSING HSMANAGER	 8 Example of a blank key request form for the node, HULK.	( Example of a completed key request form	0 Send the completed form to us at Acorn Software	 SOFTWARE PROBLEM REPORT	 Contact us by Internet	 ) Contact us by the carrier of your choice	  CUSTOMER SERVICE POLICY	     	PrefaceK October 1995  --  Welcome to Acorn Software's HSManager  documentation.  We L at Acorn are happy to add you to our group of users world wide who enjoy theN advantages of optical data library management and robotics control software.     In this preface, you will find: - 	what information our documentation contains   	who this manual is written for 	what conventions we used 	Help! from Acorn# Documentation Contents and Audience L Our  documentation consists of this user guide.  We have written it with theJ experienced OpenVMS VAX or AXP system manager and application developer inG mind. We have relied upon your knowledge and experience as well as your ; access to the complete operating system documentation set.  , Our documentation follows these conventions:J italics	indicates optional items that you substitute the specific names or numbers in commands   B courier, roman	indicates commands, HSManager licensing and program
 documentation   9 	shaded note	indicates that we ask you to pay very strict 8 attention to the information contained in the gray area.  = double underline	indicates that the text is a hot spot in the 4 http://www.acornsw.com/HTML  version of  the manual.  H shaded text	indicates that the material discussed will be implemented in a later version of HSManager.    Acorn Help!   K When you need help with storage, look to us first!  On the Internet, by fax  or by phone.  8 For an evaluation copy of our software and documentation  5 HSManager  is available on the Internet via anonymous @ ftp://ftp.acornsw.com/acorn/hsmanagerFTP from ftp.acornsw.com inI UUCP_PUBLIC:[ACORN.HSMANAGER].  To obtain the files from the Internet via  FTP, please follow these steps:    ftp ftp.acornsw.com  user anonymous password: your email address  cd uucp_public:[acorn.hsmanager] binary, get *.zip	! for all save sets in a ZIP file.! get unzip.exe	! OpenVMS/VAX UNZIP % get unzip.exe-axp	! OpenVMS/AXP UNZIP   mget hsm*.%	! For all save sets. exit  - You may also get VIRTUALBranches  via Gopher: 9 	gopher://gopher.acornsw.com/gopher://gopher.acornsw.com/  or the World Wide Web:/ 	http://www.acornsw.com/http://www.acornsw.com/ K You will receive your software and documentation as quickly as the Internet  transports it.   Or, call us at   508-568-1618 (voice) 508-562-1133 (fax)  M For the most current technical information on our software and device support G Contact us at mailto:info@acornsw.cominfo@acornsw.com.  We will respond + quickly (during the usual business hours).    I For technical support and information about installing or using any ofour ) products Please send a mail message to:    support@acornsw.com  support@acornsw.com   K  We will respond quickly (during the usual business hours).  If you prefer,  call us at:    1-508-568-1618 x5 (voice)  1-508-562-1133 (fax)L We will answer your questions or return your call no later than the close of the next business day.  ) For a license key for any of our products 9 Please fill out a key request form and send or fax it to:  267 Cox St.  Hudson, MA 01749 508-562-1133 (fax)E mailto:license-request@acornsw.comlicense-request@acornsw.com (email) . We will send your license key within 24 hours.M For sales and marketing information:  software solutions for storage problems ? Please fill out our customer survey form on the world wide web: V http://www.acornsw.com/customer-survey.htmlhttp://www.acornsw.com/customer-survey.html   Or, if  send a mail message to: ' mailto:info@acornsw.cominfo@acornsw.com J We will respond quickly (during the usual business hours).  If you prefer, call us:   508-568-1618 (voice) 508-562-1133 (fax)L We will return your call or fax no later than the close of the next business day.     Chapter 1	IntroductionI This chapter describes HSManager, the Acorn Software hierarchical storage   management package in an OpenVMSF ftp://ftp.digital.com/pub/Digital/info/infosheet/EC-F4723-93.txtVAX orJ http://www.digital.com/info/infosheet/EC-F3084-10.txt.htmlAXP environment.: Also, in this chapter you will find system requirements.    L Some of the ongoing problems faced by system managers and administrators is:M How do I manage my storage effectively and efficiently for my application(s)? L How can I safely archive data and keep track of it without having to spend a3 lot of time cataloguing data, managing tapes, etc.?   = How can I get files back that have been accidentally deleted? ( HSManager is the answer to that problem.L By allowing the system manager to define a "storage hierarchy" in which dataK is free to move from device to device depending upon the frequency and type H of access to that data the system manager can, effectively, forget aboutH managing storage, doing backups, etc.  She need only examine the overallH storage capacity from time to time and as necessary retire data to trulyK off-line storage, add additional near line storage (tape, mageneto-optical, K or CD-ROM data libraries), add additional compressed storage (Squash disks, B ZIP  or ZOO archives), additional high speed rotating mass storageL (Winchester disks) or if speed is of essence  solid state data devices (ESE,H RAM disks, or equivalent) as budget and application performance require.  L By using HSManager these resource are automatically used to their maximum toJ hold data that is most appropriate to the applications at the moment.  TheK system manager need never worry about where the data is located.  HSManagera6 guarantees that it will be in the "appropriate" place.  L HSManager works by extending the OpenVMS I/O system to have transparent fileK migration between devices.  Devices can be disks, compressed archives, tapee4 data libraries, magneto optical data libraries, etc.  M Files are migrated in a hierarchical fashion from "expensive/fast" storage to9L "inexpensive/slow" storage under the control of a simple policy specified byF the system manager.  Should this storage policy be too simple a model,I HSManager is completely compatible with all 3rd party, rule based storager management packages.  J Any number of devices of any type can participate in the hierarchy and anyK number of distinct migration policies can be implemented depending upon the M requirements of the system manager, the applications upon the system, and ther) amount and type of storage on the system..  E Version 1.0-2 and earlier of HSManager are restricted to disk to diskrI hierarchies, e.g., VIRTUALBranches managed data libraries, virtual disks,pG disks, Squash compressing disks, etc.  Any disk device may participate.i  E Applications accessing data on disks managed by HSManager run withoutsJ modifications.  As far as applications (and users) are concerned, the dataG of interest is on the disk being accessed.  Depending upon the style ofcJ HSManager shelving chosen there may be an occasional delay while space for* the data is allocated and the data copied.   HSManager achieves this by: = 	Automatically shelving as managed devices run out of space.m% 	In swapping data as it is accessed.nL In the simplest cases, out and in swapping require copying of data.  ClearlyK this can be a time consuming operation, so HSManager allows out swapping ofeJ files by command so that batch procedures can be run as appropriate by theF system manager to guarantee that sufficient free space is available on5 managed disks prior to the beginning of "prime" time.S  I Even this has substantial performance implications, so HSManager adds twoa- unique features to the OpenVMS I/O subsystem:O   	Read only soft links 	Read/Write soft links/L Soft links are functionally equivalent to links available under UNIX and mayD exist across devices, i.e., between files on the same disk, files onH different disks, or from files to other types of storage containers (ZIP archives, tapes, etc.)  K When HSManager detects a read only access to data with a form of soft link,kL then the data is accessed in place.  No copying of the data is done prior to allowing the I/O to proceed.  M Read/Write soft links extend this capability further by allowing write accesscC to occur on the out swap device rather than in swapping the data.  P  K Read/Write soft links must be used carefully since data will, over time and L depending upon access patterns, migrate toward the "least expensive/slowest"G devices.  Since the purpose of Read/Write soft links is to avoid any insK swapping activity, this may result in your data moving to devices which mayn1 be inappropriate if the access patterns change.     E Fortunately, the system manager may force nswapping of data under alldJ circumstances in the event that data pointed to with read/write soft links needs to be in swapped.   L Soft links may be created by HSManager during its normal shelving activities (if so configured) or manually.r  J Note:	If soft links of either kind are used both the source and the targetL device must be under the control of HSManager.  The data linked to must be aI disk file.  Data may not be converted into a compressed archive (except a B Squash disk) or placed on a tape and then accessed by a soft link.   Features The features of HSManager are:0 	Menu driven, full screen management interface.5 	Complete user control over which files are shelved.r@ 	Distributed management interface for remote system management.G 	Automatic movement of data within a user defined hierarchy of storagem devices.  G 	Distinct out swapping styles configurable to your access patterns andp needs.  6 	Read or Read/Write Soft links that can span devices.4 	Simple, user definable, space management policies., 	Users modifiable space management modules.< 	Manual as well as automatic management of in/out swapping.7 	Manual as well as automatic management of soft links.P/ 	Managed disks never runs out of file headers.rE 	Direct support of "container" archives, e.g., backup save sets, ZIPs archives, etc.  @ 	Migration of data to non-file structured devices, e.g., tapes.L System Prerequisites HSManager  has certain system prerequisites that appearM below.  If your system does not conform to these requirements, HSManager willaH not install.    Here are the requirements:  	OpenVMS VAX version 5.5 or= later OpenVMS AXP version 6.1 or later 	20000 blocks must bed available for install.   Chapter 2	Installing HSManagerM This chapter contains information on installing and configuring HSManager and K examples of both.  The subsections appear in the order that you will follow)H in installing HSManager.  We have formatted this chapter with additionalJ white space for your convenience in writing notes and any information that7 may assist you in a speedy and successful installation.o  5 Installing HSManager software is a two-stage process:s  	run the installation procedure, 	configure  one or  more HSManager servers. Where and how to get HSManagerG HSManager is shipped to you on a TK50 tape.  The label on the tape willaE detail the contents.  HSManager is also available on the Internet via F anonymous ftp://ftp.acornsw.com/acorn/hsmanagerFTP from acornsw.com inI UUCP_PUBLIC:[ACORN.HSMANAGER].  To obtain the files from the Internet viaf FTP, please follow these steps:n   ftp ftp.acornsw.como user anonymous  cd uucp_public:[acorn.hsmanager] binary, get *.zip	! for all save sets in a ZIP file.! get unzip.exe	! OpenVMS/VAX UNZIPe% get unzip.exe-axp	! OpenVMS/AXP UNZIP   mget hsm*.%	! For all save sets. exit   You may also get HSManager via? gopher://dmc.com/11gopher_root1%3a%5bacorn.hsmanager%5dGopher:	w gopher://gopher.acornsw.com/  - or the http://www.acornsw.com/World Wide Web:  	http://www.acornsw.com/G Included on the TK50 tape and in the directory noted above is HSManagerl documentation:  E 	ftp://ftp.acornsw.com/acorn/hsmanager/hsmanager.docHSMANAGER.DOC is0G the MacBinary copy of the file.  This may be moved to any Macintosh and M converted into a http://www.microsoft.com/SalesInfo/mspword.htmMicrosoft WordH
 5.1 document.c  E 	ftp://ftp.acornsw.com/acorn/hsmanager/hsmanager.rtfHSMANAGER.RTF is:G the rich text format version of HSMANAGER.DOC.  This may be read by any/J version of http://www.microsoft.com/SalesInfo/mspword.htmMicrosoft Word or7 other word processor that supports importing RTF files.o  E 	ftp://ftp.acornsw.com/acorn/hsmanager/hsmanager.txtHSMANAGER.TXT is:G the text format version of HSMANAGER.DOC.  This may be read by any texto- editor but will not be formatted as prettily.t   	K ftp://ftp.acornsw.com/acorn/hsmanager/release-notes.docRELEASE-NOTES.DOC is G the MacBinary copy of the file.  This may be moved to any Macintosh and M converted into a http://www.microsoft.com/SalesInfo/mspword.htmMicrosoft Wordi
 5.1 document.i   	K ftp://ftp.acornsw.com/acorn/hsmanager/release-notes.rtfRELEASE-NOTES.RTF iseK the rich text format version of RELEASE-NOTES.DOC.  This may be read by any J version of http://www.microsoft.com/SalesInfo/mspword.htmMicrosoft Word or7 other word processor that supports importing RTF files.e   	K ftp://ftp.acornsw.com/acorn/hsmanager/release-notes.txtRELEASE-NOTES.TXT iseK the text format version of RELEASE-NOTES.DOC.  This may be read by any texto- editor but will not be formatted as prettily.d  L You can print as many copies of this documentation as you want provided thatL no changes of any kind are made in the documentation.  These as well as HTML copies of the most recenteB http://www.acornsw.com/acorn/manuals/HSManager/index.htmlHSManager@ documentation are available at all time from the World Wide Web.  K Installing HSManager(VMSINSTAL) The installation program for HSManager is aaJ VMSINSTAL kit.  If you are not familiar with VMSINSTAL, see the VMS SystemM Manager's Guide  for more information.  The files are contained in the BACKUPnL save set named HSMUUUVVV where UUUVV V is the optional update identificationM and the version number.  Do the installation from the system manager's login.tH If you aren't the system manager, get the system manager to perform thisD installation for you.  In this example we used a TK50 tape with onlyK HSManager on it.  Follow these steps:  Step 1	Log in as the system manager.eH Username: SYSTEM Password:  Step 2	Insert the tape in the drive. We usedL a TK50.  Step 3	Enter this VMSINSTAL command:  @SYS$UPDATE:VMSINSTAL product device  ( product: the exact file name (HSMuuuvvv)E device: the system name of the drive that you inserted the tape into.nJ We used this command to install HSManager V1.0 from the TK50 device, MKB0:$ $ @SYS$UPDATE:VMSINSTAL HSM010 MKB0:L Step 4	As VMSINSTAL transfers files, respond to the questions on the screen.M See the next chapter, #hsmanager internalsHSManager System Information, whichiL describes file names and logical names if you need to make any changes while installing HSManager.a   Example of Typical InstallationsI The following example is a typical installation.  If there is no response / shown to a prompt, the default has been chosen:e  $ $ @sys$update:vmsinstal hsm010 mkb0:  >         VAX/VMS Software Product Installation Procedure V5.5-2   It is 15-OCT-1995 at 09:05.   / Enter a question mark (?) at any time for help.a  > %VMSINSTAL-W-ACTIVE, The following processes are still active:         _VTA19:l         DECW$TE_1i         _TWA2:         MUNROE         _VTA14:s         _VTA15:n         _TWA5:         DECW$WM_1w         MUNROE_SM1         MUNROE_SM2         NEWSSKIM_730( * Do you want to continue anyway [NO]? y> * Are you satisfied with the backup of your system disk [YES]?  ) The following products will be processed:e  
   HSM V1.0  3         Beginning installation of HSM V1.0 at 09:05M  6 %VMSINSTAL-I-RESTORE, Restoring product save set A ...A * Do you want to purge files replaced by this installation [YES]?n  O * Enter root directory for HSM directories [SYS$SYSDEVICE:[HSM.]]: user4:[hsm.]d  C * Can this system send to and receive mail from the Internet [N]? y,  ( The Internet address for HSM Support is:           support@acornsw.come  A Enter the VMSMail address necessary to reach support@acornsw.com.   H * OpenVMSMail address is [support@acornsw.com]: mx%"support@acornsw.com"  # No further questions will be asked.r  4 %HSM-I-DELIVER, Delivering CSWING.HLB to HSM_SYSTEM:2 %HSM-I-DELIVER, Delivering FILE.HLB to HSM_SYSTEM:2 %HSM-I-DELIVER, Delivering FIND.HLB to HSM_SYSTEM:4 %HSM-I-DELIVER, Delivering FORCEX.HLB to HSM_SYSTEM:@ %HSM-I-DELIVER, Delivering HSAUTHMAINT.DOC to HSM_DOCUMENTATION:= %HSM-I-DELIVER, Delivering HSDRIVER.DOC to HSM_DOCUMENTATION:s: %HSM-I-DELIVER, Delivering HSHSM.DOC to HSM_DOCUMENTATION:> %HSM-I-DELIVER, Delivering HSMUSERMAN.PS to HSM_DOCUMENTATION:? %HSM-I-DELIVER, Delivering HSMUSERMAN.TXT to HSM_DOCUMENTATION:l3 %HSM-I-DELIVER, Delivering ZMENU.CLD to HSM_SYSTEM:e4 %HSM-I-DELIVER, Delivering FORCEX.CLD to HSM_SYSTEM:3 %HSM-I-DELIVER, Delivering HSDMN.CLD to HSM_SYSTEM: 6 %HSM-I-DELIVER, Delivering HSEXEDEL.CLD to HSM_SYSTEM:6 %HSM-I-DELIVER, Delivering HSEXEMPT.CLD to HSM_SYSTEM:6 %HSM-I-DELIVER, Delivering HSFILDEL.COM to HSM_SYSTEM:8 %HSM-I-DELIVER, Delivering HSFILEMARK.COM to HSM_SYSTEM:: %HSM-I-DELIVER, Delivering HSFILRSTMDIR.COM to HSM_SYSTEM:: %HSM-I-DELIVER, Delivering HSFILRSTMDSK.COM to HSM_SYSTEM:: %HSM-I-DELIVER, Delivering HSFILSAVMDIR.COM to HSM_SYSTEM:: %HSM-I-DELIVER, Delivering HSFILSAVMDSK.COM to HSM_SYSTEM:4 %HSM-I-DELIVER, Delivering HSLINK.COM to HSM_SYSTEM:6 %HSM-I-DELIVER, Delivering HSMAKSPC.COM to HSM_SYSTEM:: %HSM-I-DELIVER, Delivering HSMOVE_FILES.COM to HSM_SYSTEM:6 %HSM-I-DELIVER, Delivering HSRPTSPC.COM to HSM_SYSTEM:< %HSM-I-DELIVER, Delivering HSSPACE_TAILOR.COM to HSM_SYSTEM:9 %HSM-I-DELIVER, Delivering HS_SEL_MOVE.COM to HSM_SYSTEM:eG %HSM-I-DELIVER, Delivering HSM-CONFIGURATION-UTILITY.COM to HSM_SYSTEM:c: %HSM-I-DELIVER, Delivering HSM-SOFTLINK.COM to HSM_SYSTEM:7 %HSM-I-DELIVER, Delivering HSM-LOGIN.COM to HSM_SYSTEM:oF %HSM-I-DELIVER, Delivering HSM-STARTUP.COM to SYS$COMMON:[SYS$STARTUP]9 %HSM-I-DELIVER, Delivering HSM-STARTUP.COM to HSM_SYSTEM:s; %HSM-I-DELIVER, Delivering HSM-SYSTARTUP.COM to HSM_SYSTEM: @ %HSM-I-DELIVER, Delivering HSM-STARTUP-DAEMON.COM to HSM_SYSTEM:4 %HSM-I-DELIVER, Delivering FILDEL.COM to HSM_SYSTEM:4 %HSM-I-DELIVER, Delivering MAKSPC.COM to HSM_SYSTEM:6 %VMSINSTAL-I-RESTORE, Restoring product save set B ...$ %HSM-I-LINKING, Linking HS Driver...P %LINK-W-USRTFR, image $1$DUA11:[SYS10.SYSUPD.HSM010]HSDRIVER.EXE;1 has no user t ransfer addressk! %HSM-I-LINKING, Linking Daemon... > %HSM-I-LINKING, Linking Authorization Maintenance Interface...0 %HSM-I-LINKING, Linking Exempt List Interface...5 %HSM-I-LINKING, Linking Space Management Interface...t4 %HSM-I-DELIVER, Delivering CSWING.EXE to HSM_SYSTEM:2 %HSM-I-DELIVER, Delivering FILE.EXE to HSM_SYSTEM:2 %HSM-I-DELIVER, Delivering FIND.EXE to HSM_SYSTEM:4 %HSM-I-DELIVER, Delivering FORCEX.EXE to HSM_SYSTEM:3 %HSM-I-DELIVER, Delivering UNZIP.EXE to HSM_SYSTEM:a1 %HSM-I-DELIVER, Delivering ZIP.EXE to HSM_SYSTEM:u3 %HSM-I-DELIVER, Delivering ZMENU.EXE to HSM_SYSTEM:r: %HSM-I-DELIVER, Delivering ZMENU_SCROLL.EXE to HSM_SYSTEM:3 %HSM-I-DELIVER, Delivering HSDMN.EXE to HSM_SYSTEM:c9 %HSM-I-DELIVER, Delivering HSAUTHMAINT.EXE to HSM_SYSTEM: 6 %HSM-I-DELIVER, Delivering HSEXEMPT.EXE to HSM_SYSTEM:6 %HSM-I-DELIVER, Delivering HSSAVSPC.EXE to HSM_SYSTEM:6 %HSM-I-DELIVER, Delivering HSDRIVER.EXE to HSM_SYSTEM:  A To complete the installation of the Hierarchical Storage Manager,[
 you must run:]  /         $ @SYS$STARTUP:HSM-STARTUP.COM LOGICALSl3         $ @HSM_SYSTEM:HSM-CONFIGURATION-UTILITY.COM-  ( to complete the setup of the HSM server.  F You must also modify the file SYS$MANAGER:SYSTARTUP_V5.COM to contain:  &         $ @SYS$STARTUP:HSM-STARTUP.COM   In addition:  K         $ IF F$TRNLNM("HSM_SYSTEM") .NES. "" THEN @HSM_SYSTEM:HSM-LOGIN.COMw  H must be added to your SYLOGIN.COM file to define symbols needed for HSM.    Put documentation pointers here!  N %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...  3         Installation of HSM V1.0 completed at 09:13n  )         VMSINSTAL procedure done at 09:13/   Configuring HSManageroE After you have completed the VMSINSTAL, the next step is to configures4 HSManager using the HSManager configuration utility.  ) @HSM_SYSTEM:HSM-CONFIGURATION-UTILITY.COMnL The HSManager  configuration utility provides a menu driven interface to theK management features of HSManager.  Once all appropriate questions have beenrM answered, the configuration utility creates a configuration file for a single K HSManager server.  More information on the way HSManager works can be foundaJ in "#hsmanager internalsHSManager System Information".  This configurationK file contains data contained in DCL variables and is processed, indirectly,d6 by SYS$STARTUP:HSM-STARTUP.COM when your system boots.  E This section contains a screen by screen description of the HSManager: configuration utility.  J It is also possible to configure HSManager using the world wide web.  ThisJ allows distributed site management from any computer supporting TCP/IP andM having a WWW browser.  If you are already running a web site then this may bep a good option for you.  I If you are not already running a web site then stick with the menu drivenSK interface as the security issues of the web are significant.  You will havea? to run a web server on each system or cluster to be so managed.a  H HSManager must be run on each node accessing data on managed disks.  ForL clusters, this means the each node must be licensed and running HSManager toG guarantee reliable access to shelved or linked to data.  Acorn SoftwaredH provides cluster and site wide licenses for customers running in such an environment.  * Creating an HSManager server configuration  B Note:	This section is documented as if the user interface had beenH redesigned already.  V1.0 will ship with the screens as shown here.  TheI screens will be updated as soon as the user interface is redesigned.  TheUF information presented is identical in any event, it is just located in "illogical" places.   K After installing HSManager the next thing to do is to configure one or morem1 servers.  Run the configuration command procedureh@ (HSM_SYSTEM:HSM-CONFIGURATION-UTILITY.COM) to begin the process.J Configuration consists of first creating a configuration for a new server,M then (if necessary) setting specific space policy for the new server.  If theVI existing site wide space policy is appropriate, then the step setting thea space policy can be omitted.  J Note:	If you are running a defragmentation package, you must let HSManagerB know about it.  If you don't, every time the files are touched forC defragmentation purposes you will incur an in swap or a potentiallye# disastrous file access redirection.r  J The exempt application list is limited to 32 entries and must consist of aL fully specified file name of the form: device:[directory]file.type.  VersionK numbers, concealed logicals as device names and wild cards are not allowed.w  L Configuring a server consists of setting a variety of parameters.  These areG divided, loosely into three types (unfortunately, not very well in this:2 version of HSManager, this will change over time).  G The first type of parameter deals with the execution environment of the * server.  Examples of these parameters are:   	Process priority' 	Directory containing executable image % 	Directory containing database files  	Shelving directory6 	Base unit number for the HSManager intercept driversJ Defaults are provided for all of these and, in general, these defaults areI sufficient for you to begin running HSManager without any changes on youru part.m  H If you choose to change these parameters, be assured that changing theseE parameters change the execution environment only for the server beingS+ configured and not for the site as a whole.y  L In general it is not necessary to restart a server for the new parameters to3 take effect.  Any exceptions to this will be noted.e  M The parameter most likely to be of interest to you is the shelving directory.,  K The shelving directory may be entered in a number of forms.  The first, and G most obvious, is simply a device and directory on any disk or disk likepK device, including bound volume sets.  Disk like devices include such thingsr: as virtual devices provided by VirtualBranches or Squash  9 Note:	This is the only model supported by HSManager V1.0.L  G Others include a list of disk or disk like devices that are not a boundIM volume set.  There can be substantial performance benefits to this particularTM style of shelf since bound volume sets require updating of data structures onMM more than one member of the set resulting a substantially more I/O.  However,HK you pay for the privilege since the largest file that can be stored using a L list of volumes is that of the volume with the most free space.  The largestI file that can be stored using a bound volume set is the free space on theE bound volume set.   L And last, but not least, are tape devices.  Files placed on tape devices areH fully integrated with Branches for truly lights out operation for thoseM customers with tape data libraries.  HSManager also supports stand alone tapeH8 devices.  The exact operational characteristics are TBD.  L HSManager requires an intercept driver for each managed disk device.  If youL are running more than one HSManager server (not required) you must specify aL different starting unit number for each server.  Failing to do so can result; in a fair amount of confusion and potentially loss of data.K    J The second group of parameters deals with the environment to be managed by" the server.  These parameters are:  1 	The list of disks to be managed by this server.S% 	The shelving "style" of the server.DI A single HSManager server can manage an "unlimited" number of disks.  TheiM only issue is one of performance.  Performance becomes an issue when you haveML large amounts of in and out swap activity.  If you find this happening, thenM you may need to change shelving styles (from shelve to read/only soft link or]M from read/only soft link to read/write soft link) or add additional HSManagereM servers.  Another possible solution is to purchase additional or larger disksTM and then reconfigure.  Remember, while HSManager makes your disks look biggerEG than they are, eventually you will run out of room, so it pays to startS planning for that eventuality.  I There are three distinct styles of shelving supported by  HSManager.  The[H first is "Copy Shelving" or simply "Shelving".  When copy shelve managedM storage runs out of room, files are copied to the shelf (out swapped) and the G original data truncated.  Any access (other than by those images on theNF exempt list) results in an in swap (copying from the shelf back to theJ original space) of the file.  This style of management is most appropriateK for data that is, essentially, being managed for archival purposes and wille "never" get read.H  I The second style is "read/only soft links".  HSManager provides a genericVJ mechanism for providing links from on file to another.  These operate in aM manner similar to soft links available under UNIX and can be used outside theHM context of HSManager.  Links can cross device boundaries, but must be betweenH disk or disk like devices.    H When read/only soft link managed storage runs out of room, files are outM swapped and the original data truncated.  After the data is moved a read/onlyoJ soft link is created between the original and the shelved files.  Any readI only access to the shelved data will result in the data being transferred K directly from the shelf without requiring an in swap operation.  Any access H that would update the data on the shelf results in an in swap operation.K This style of management is most appropriate for data that is "read mostly" J and is updated in bursts, for example at the end of the month, quarter, orL year.  Both the data source and the data destination must be under HSManagerF control although only the source of data need be managed by HSManager.  K The third style is "read/write soft links".   Like HSManager read/only soft1G links, read/write soft links are generic, usable outside the context ofo- HSManager, and can cross device boundaries.  t  L When read/write soft link managed storage runs out of room, files are copiedH to the shelf and the original data truncated.  After the data is moved aK read/write soft link is created between the original and the shelved files.eF Any access to the shelved data read OR write results in the data beingI transferred from or to the shelf without requiring any in swap operation. J Using read/write soft links, once data is shelved it remains on the shelf.L Mechanisms are provide to convert read/write soft links to read/only or copy< shelving styles to allow data to be in swapped if necessary.  E This style of management is most appropriate for situations where the K performance of the shelf and the original data store are, for all practicalfB purposes, identical or declared to be so by the system management.    G Source disks are selected either by moving within the menu and enteringpL return when the appropriate item is highlighted.  Selection of disks by name# is not available in HSManager V1.0.o  + Source disks have a number of restrictions:g 	They must be mounted" 	They must not be mounted foreignG 	They must not have a copy of OpenVMS on them (detected by looking forw! device:[000000]VMS$COMMON.DIR;1).   E If you selected one of the soft link styles of management all devicesnI specified in shelf list will be automatically controlled by the HSManagernF configuration utility although they will not be under space management control.  L Shelf areas themselves can be managed by an HSManager server thus allowing aL hierarchy of storage to be defined.  You may use a single server or multipleM servers depending upon the performance requirements of your installation.  InyM general a single HSManager server should be sufficient for most applications.   A If the site wide default space policy is not to your liking or isnG inappropriate for this particular collection of managed device, you may L specify a server specific space policy.  The initial values for the server's2 space policy are copied from the site wide policy.  M The parameters control how space is automatically freed when the HSMMAKESPACEoG command is executed.  If you are running HSManager in automatic storagenM management mode (the HSManager server decides which, if any, files to shelve)sM we recommend that this command be run periodically (nightly or weekly) duringcK non-prime time.  Alternatively, you may manually move files to the shelf byt using the HSMMOVEFILE command.  K Space policy parameters may not be set or manipulated until disks have beenu	 selected.   , Files are eligible for shelving if they are:! 	larger than the small file sizep" 	smaller than the jumbo file size9 	the creation date is older than "now" less the file agef9 	the revision date is older than "now" less the file agel; 	the expiration date is older than "now" less the file age  	is non-contiguousr 	is not a directory filee< 	can be processed by backup (NOBACKUP attribute is not set)8 	can be moved by movefile (NOMOVE attribute is not set). 	can be out swapped  (NOSHELVABLE is not set) 	is not an ISAM file   	does not have stored semanticsC 	whose [directory]name.type;version contains none of the specifiedy exclusion strings.   Whew.u  E Within this group of files, files are shelved in the following order:y* 	files between the medium and large sizes) 	files between the large and jumbo sizes * 	files between the small and medium sizesK For OpenVMS 5.5 users, the NOSHELVABLE file attribute is unavailable.  This E robs them of the user control over shelving that is necessary to manynI customers.  HSManager solves this in two ways.  First, the truncated file J length on the source disks once a file has been out swapped is 0, thus theH file will never be considered for shelving (it's too small).  Second, byL allowing the space policy to be set to manual.  This restricts the selectionH of space to those files already in the HSManager database as having beenM shelved.  This feature is also available for later versions of OpenVMS but iseF unnecessary due to the availability of the NOSHELVABLE file attribute.  I At this point you have completed the configuration of your server and mayyM write the configuration file.  If you have made any mistakes, just repeat theaG menu entry to update the information.  When you are satisfied, save the  configuration information.  J The name of an HSManager server is the name of the first device managed byL that server.  If you look in HSM_SCRATCH you can easily tell all the relatedK information collected by the HSManager configuration utility by looking for ( identical device names in the file name.  $ Deleting an HSManager  Configuration  D All good things must come to an end and the lifetime of an HSManager configuration is no exception.  J You will be presented with a list of server configurations.  Simply select7 one (or more) and then the delete selections menu item.e  # Editing an HSManager  Configurationr4 Will be implemented in a later version of HSManager. Starting an HSManager  Servers  I Now that you've gone to all this work you should start your server.  This I must be done from a fully privileged account, so if you aren't running invC one, use #hsm-startupSYS$STARTUP:HSM-STARTUP.COM (discussed below).d  J You will be presented with a list of server configurations.  Simply select6 one (or more) and then the start selections menu item.   Stopping an HSManager  Serverh  I Should you need to shut down a running HSManager server, it can easily be % done using the configuration utility.   L You will be presented with a list of running servers.  Simply select one (orM more) and then the stop selections menu item.  This can also be done directlyi% using the HSMANAGER/SHUTDOWN command.r  * In swapping files from an HSManager ServerI Occasionally it may be necessary to get all files off of a shelf and backoH onto the target disks.  One example of such a time is when you intend toJ reconfigure the disk subsystem or remove a disk from HSManager management.I If you fail to in swap all data then your source disk will, in effect, berL missing all data in the shelf.  It is the system manager's responsibility toG guarantee that sufficient space exists on the source disk to allow  alla shelved files to be in swapped.v  K Two pieces of information are necessary.  The first is the HSManager servereI managing the disk of interest.  For the in swap operation to succeed, them server must be running.o  K The second is list of disks managed by the selected server whose data is ton be in swapped.  J One of the properties of HSManager managed disks is that they appear to beK bigger than they actually are.  The in swap operation will not be attempted L unless there is sufficient room on the source disk to hold all the data.  IfK this is not the case, the system manager will have to remove some data froma+ the selected disks and retry the operation.e  % Site wide space and policy managemento  H The form and function of the site wide space policy is identical to thatM discussed earlier for the server specific space policy.  See that section foro* details on the meaning of the site policy.  I To see the effect of the chosen site policy use the report function.  For I large disks with many files this can be somewhat time consuming.  A small M screen report is given breaking down the space recoverable by the chosen siteh policy.   L To apply the space policy use the make space available function.  10% of theB size of the disk will be freed.  This is equivalent to running the3 HSMMAKESPACE command with the following parameters:   ? HSMMAKESPACE deviceName 'F$GETDVI("deviceName","MAXBLOCKS")/10't   Starting HSManagerL hsm-startupYou can start HSManager using the HSManager configuration utility or by entering this command:   $ @SYS$STARTUP:HSM-STARTUP.COM  J To guarantee that HSManager starts when your system reboots, add the above1 command to your system startup command procedure.t  I You may use the HSManager startup command procedure to define the logical/; name environment of HSManager without starting any servers:   ' $ @SYS$STARTUP:HSM-STARTUP.COM LOGICALS   = You may also use create load all HSManager intercept devices: * $ @SYS$STARTUP:HSM-STARTUP.COM DEVICE_ONLY  + A specific HSManager server may be started: * $ @SYS$STARTUP:HSM-STARTUP.COM "" fileName  G Where filename is the name of the configuration file for the particulari HSManager server.a     Licensing HSManagermG When HSManager is started, it automatically installs a 45 day temporaryiI license.  During this period you may freely operate HSManager.  Once thiseL time period expires HSManager will no longer respond to user requests.  OnceM a week during the temporary license period and once a day for the last 7 daysoK of the temporary license period, HSManager sends mail to the SYSTEM accountiM warning that the HSManager temporary license is about to expire.  The body of E the mail message contains a key request form for the node running theoM HSManager server.  You must run HSManager on each node which will access datahM managed by HSManager.  This means that you will have to acquire a license fore each system in your cluster.  D You must acquire a license key from Acorn Software to continue using# HSManager beyond this time period. o  @ To get your license key from Acorn Software, follow these steps:+ Step 1.  Do a HSMANAGER/LICENSE=license.txte? Step 2.  Edit license.txt to fill in the requested information.oF Step 3.  Mail, email, or fax it back to your HSManager dealer or Acorn Software, Inc.    9 The email address for processing your license request is:b> 	mailto:license-request@acornsw.comlicense-request@acornsw.comA If you prefer, complete a key request form and send or fax it to:v   		Acorn Software, Inc.
 		267 Cox St.e 		Hudson, Ma. 01749a 		508-568-1618 x5 (voice)e 		508-562-1133 (fax)  B Step 4.  You will receive your license information within 24 hoursD Step 5.  Install the license with the HSMANAGER/INSTALL=key command.K HSManager must be licensed on each node accessing data managed by HSManager  on any node.    F Note: 	It is the policy of Acorn Software to not grant extension keys.M Specific exceptions to this rule are made on a case by case basis.  To get anAJ extension key, you must provide documentation of your time requirements toM finish evaluation.  Upon receipt and analysis of this document Acorn Softwareh" will grant a single extension key.   Using HSManagerlH From the perspective of the user, using HSManager is just like using theL existing disk devices on their OpenVMS system.  All disk operations continueK to work unchanged.  There may occasionally be some perceivable delays whiledM HSManager performs any necessary in swap and/or out swap operations but thesee# delays are the only thing they see.   9 hsmanager internalsChapter 3	HSManager System Informationg System StartupK Starting HSManager consists of running the HSManager system startup commandrG procedure.  The startup process itself consists of the following steps:y  F 1.	Search HSM_SCRATCH: for all files named HSM-*.CONFIGURATION.  These; files contain configuration data for each HSManager server.e  H 2.	For each HSManager server configuration file found load the HS deviceB driver as necessary for all disks managed by the HSManager server.  = 3.	Link all disks managed by the HSManager server back to theiL configuration file.  This is crucial to the successful operation of the restI of the HSManager server command procedures since this is the way they alliK test for the disk to HSManager server relationship.  The logical names thatE0 link disks to configuration file are of the formF HSM_fullDeviceName_CONFIGURATION,  e.g., HSM__FRA1_CONFIGURATION.  TheF translation of the logical names is the file name of the configuration0 information for the associated HSManager server.  H 4.	Run HSM_SYSTEM:HSM-STARTUP-DAEMON.COM as a detached process.  This isK the startup of the HSManager server itself.  The server startup connects HSc8 devices to "real" disk devices which turns them on-line.  E 5.	Once the HSManager server is started, the remainder of the managede" disks (if any) are also connected.  * This process as a whole is run by issuing: $ @SYS$STARTUP:HSM-STARTUP.COM  J To guarantee that HSManager starts when your system reboots, add the above1 command to your system startup command procedure.i  I You may use the HSManager startup command procedure to define the logical ; name environment of HSManager without starting any servers:o  ' $ @SYS$STARTUP:HSM-STARTUP.COM LOGICALSr  = You may also use create load all HSManager intercept devices:u* $ @SYS$STARTUP:HSM-STARTUP.COM DEVICE_ONLY  + A specific HSManager server may be started:i* $ @SYS$STARTUP:HSM-STARTUP.COM "" fileName  G Where fileName is the name of the configuration file for the particular  HSManager server.    System Shutdown L hsm-shutdownSimply run HSM_SYSTEM:HSM-SHUTDOWN.COM and all running HSManagerM servers will be shut down.  To shut down a single HSManager server use either I the HSMANAGER/SHUTDOWN command or the shutdown server functions availablel& through the HSM-CONFIGURATION-UTILITY.  " System Variables and Logical NamesK This section lists logical names, identifiers, system directories, and filetH names used by HSManager.  All logical names are defined by the HSManager system startup procedure.T  
 Logical NamesMF HSM_DEBUG	Define if you wish to see the detailed operations of all HSM command procedures.e  F HSM_DATABASE	The directory containing the files that provide the extraF semantic information for HSManager and the files managed by HSManager.  M HSM_DELETE_SAVE	The default shelving directory for all HSManager servers.  It F may not be more that 3 levels deep as the automatic shelving directory+ structure uses an additional 5 directories.   / HSM_DOCUMENTATION	The directory containing the T   machine readable HSManager documentation.K HSM_MAKE_SPACE	The command procedure responsible for automatically clearinge space on managed devices.e  D HSM_RESTORE_FILE	The command procedure responsible for taking a file. from a shelf and placing it on active storage.  @ HSM_ROOT	The root directory for the HSManager system and scratch directories.  F HSM_SAVE_FILE	The command procedure responsible for taking a file from) active storage and placing it on a shelf.c  D HSM_SCRATCH	The directory to be used to contain all files created by
 HSManager.  G HSM_SPAWN2	Primarily used for debugging.  It causes a sub process to beaM spawned each time an out swap operation is necessary.  This can be convenientrI since the output log then appears in the HSM_SCRATCH:HSM-server.LOG file.e  D HSM_SUPPORT	A logical name used as the destination address of a mailM message for HSManager software support.  This logical name is only defined ifhH your site is connected to the Internet and the installation procedure is informed of this fact.  A HSM_SYSTEM	The directory that contains system related portions of 
 HSManager.    HSM_fullDeviceName_CONFIGURATIONK Points to the configuration information for the HSManager server in control G of the device.  Used to determine if there is a server for this device.c   Chapter 4	HSManager CommandsM With the HSManager commands noted in this chapter, you can access contents ofpG your and control the server data library. HSManager commands provide antM interface for controlling some aspects of HSManager. The principle management G interface is provided by the HSM-CONFIGURATION-UTILITY and is discussed 6 above.  This is a quick summary of HSManager commands:   Function	HSManager Command6 Exempt a process from HSManager.	HSMANAGER/SET/PROCESS) Install the license key	HSMANAGER/INSTALLc( Get a key request form	HSMANAGER/LICENSE4 Display the current version number	HSMANAGER/VERSION( Create a read/write softlink	HSMSOFTLINK+ Move selected files to shelves	HSMMOVEFILESr# Apply the space policy	HSMMAKESPACEg1 Shutdown an HSManager server		 HSMANAGER/SHUTDOWN J The following pages list each command in alphabetical order.  Each command appears on a separate page.p     HSMANAGER/SET/PROCESS   I Exempt a process from HSManager control.  Used to control if Backup readseI data from softlinks and shelves or ignores them.  By default, backup willML read shelved data.  Use this command to prevent shelved data from from beingG read.  Requires SYSPRV and that both ends of the softlink be managed bynK HSManager.  In this version of HSManager you may not link either from or toh a directory.  I Note: 	This interface is only for versions of OpenVMS prior to 6.0.  When L running OpenVMS 6.0 or higer, you must use the Digital supplied DCL command:   	SET PROCESS/NOAUTO_UNSHELVE   to get the same effect.f7 Format	HSManager/SET/PROCESS=[NO]EXEMPT HSManagerDevice 
 QualifiersA /PROCESS	EXEMPT implies that the process is exempt from HSManagerpG processing.  Softlinks will not be honored and inswap requests will notyL occur.  NOEXEMPT implies that the process is no longer exempt from HSManagerF processing.  Note that this is "sticky" and is in effect from the time< /PROCESS=EXEMPT is issued until /PROCESS=NOEXEMPT is issued.   HSMANAGER/INSTALLY    Install a license for HSManager.& Format	HSManager/INSTALL=licenseString Qualifiers	NotesJ /INSTALL key	Installs a license.  HSManager  must be licensed on each node< on which it will run and for each data library on each node.   HSMANAGER/LICENSEe  O Gets a key request form for sending to Acorn Software or your HSManager dealer.s# Format	HSManager/LICENSE[=fileName]E Qualifiers	NotesI /LICENSE[=SYS$OUTPUT:]	The file to contain the key request form.  The keyM1 request form is written to SYS$OUTPUT by default.    HSMANAGER/VERSIONn  F Displays the current version number of HSManager. When you call us forG Technical Support, this is one of the first questions that will need anc' answer "What version are you using?".  x   Format	HSManager/VERSION   HSMANAGER/SHUTDOWN  ) Shuts down a specific HSManager server.  i$ Format	HSManager/SHUTDOWN serverNameJ The server name is one of the server names defined when you configured the HSManager servers.   HSMSOFTLINKT  ) Creates or removes a read/write softlink.o" Format	HSMSOFTLINK fromFile toFileL Create a read/write softlink from one file to another.  The files must exist prior to invoking HSMSOFTLINK.   Format	HSMSOFTLINK removeFiled6 Remove a read/write softlink from one file to another.  
  HSMMOVEFILESo  D Allows the system manager to manually cause the selected files to beJ outswapped, depending upon the type of HSManager behavior defined.  SimpleI shelving will cause data to be copied to the shelf.  Read/only soft linksaG will cause the data to be copied to the shelf and a read/only soft link.+ connected between the source and the shelf.n  I Read/write soft links will cause the data to be copied to the shelf and af@ read/write soft link connected between the source and the shelf.  - Format	HSMMOVEVILES wildCardFileSpecification    HSMMAKESPACE  H Makes a requested amount of space on the specified disk.  The associatedL HSManager logical name environment must be defined, but the HSManager server/ associated with the device need not be running.   / Format	HSMMAKESPACE deviceName [numberOfBlocks]NP If the number of blocks is omitted, 10% of the size of the device will be freed.   Chapter 5	Trouble Shooting   Chapter 6	Application NotestD This chapter deals with known application integration issues betweenA HSManager and other components of OpenVMS as supplied by Digital,kK applications, and layered products.  This list contains all the information F available to us at the time of writing.  This list will be expanded as, further information becomes available to us.   ANALYZE/DISK/REPAIReG Note:	The information contained in this section is crucial.  Failure toSH read and understand this will lead to extremely confusing situations andL could, potentially, corrupt your source disk.  We actually haven't seen thisJ happen in our testing, but we have  certainly not seen all possible cases.  ? If soft links are in use on a device and it is necessary to runr/ ANALYZE/DISK/REPAIR on that device then either:   6 	The process must be exempt from HSManager processing9 (HSMANAGER/SET/PROCESS=EXEMPT or, version 6.0 and up, SET  PROCESS/NOAUTO_UNSHELVE) ora  : 	the HSManager server for that device must be turned off.K Soft links work by "redirecting" file header accesses in specific ways that L result in file number and header information for the file on the shelf beingK returned.  This information may or may not make sense within the context of  the source device.  G The effect may be as simple as a few error messages about the files notAI existing (if the file header information does not make sense) to the filedK data being corrupted (if it does).  It is not possible to lose shelved datasM under these circumstances, but it may take a while to recover the appropriatee state of the shelved data.    ; Appendix A	HSManager Error Messages and Recovery TechniquesSF RMS$_FUL	This error can occur when an in swap operation indicates thatJ there wasn't enough room on the source device.  This may occur during whatL appear to be read operations, e.g., DIFFERENCES.  There are two solutions toL this problem.  (1) delete enough space on the device to allow the in swap toJ succeed.  (2) Assign a read only softlink to the file.  You'll have to pawM through the shelf for the device to find the two files.  Eventually this willtM have to have enough room made if you ever want to write the file.  (3) Assign I a read/write softlink to the file and leave it on the shelf indefinately.    Appendix B	Licensing HSManagerI These are examples of how to acquire a license for HSManager.  We want todM make it easy for you:  Generate a blank license form using HSMANAGER/LICENSE.oL Using you favorite text editor fill it out.  Then you can fax back to us, orM send it to us on the Internet via mailto:license-request@acornsw.comemail, orS! mail it back via physical mail.  i  8 Example of a blank key request form for the node, HULK.;  J Log into any account on the system to which the data library is connected.+ Create a license request form for the node.T   $ HSMANAGER/LICENSE=LICENSE.TXTr $ TYPE LICENSE.TXT    e  a  p Key Request Form:	HSM T1.0 Date:			 5-NOV-1995 20:35:01.20o  hB To obtain your Software Key, send this form containing your SystemJ Identification Code (below) to Acorn Software, Inc., or contact your AcornO Software service or sales representative.  If you are outside of North America,rK contact your local HSManager distributor or send your System Identification O Code directly to Acorn Software to obtain a Software Key which will enable fullaK use of HSM T1.0.  Note that your customer number is required.  Your licenser* request will not be processed without it.   $                 Acorn Software, Inc.                 267 Cox St.t!                 Hudson, Ma. 01749   y:                 Phone:  508-568-1618 x5 Fax: 508-562-1133 4                 E-Mail: LICENSE-REQUEST@ACORNSW.COM   I Please complete this software key request form by providing the following.J information before sending this form to Acorn Software, Inc. or your localH HSManager distributor.  Only key request forms that have been filled out completely can be processed.    B         Company:        _________________________________________ B         Customer Number:_________________________________________ B         Address:        _________________________________________ B                         _________________________________________ B                         _________________________________________ B                         _________________________________________ B         Country:        _________________________________________   PB         Phone:          _________________________________________ B         Fax:            _________________________________________ B         E-Mail:         _________________________________________   eB         Contact Person: _________________________________________ B         Title:          _________________________________________   M The following is a list of System Identification Codes for some or all of theaL VAXes in your VAXcluster.  To include the System Identification Codes (SICs)N for additional VAXes in your VAXcluster, log in to those VAXes and issue the     	HSMANAGER/LICENSE=filenamee   command for HSManager. c  a@ SIC:	HSM1-R37B34-NDKV66-6101PK---PD3MRM-RTM1Y2-E3C252    (HULK)   d   $ EDIT LICENSE.TXT  J Using your favorite editor, complete the key request form.  Please see the; next section for an example of a complete key request form.c  ' Example of a completed key request form6K Log into any account to which the data library is connected and fill in theC form.n   $ HSMANAGER/LICENSE=LICENSE.TXT    $ TYPE LICENSE.TXT       m Key Request Form:	HSM T1.0 Date:			 5-NOV-1995 20:35:01.20e   B To obtain your Software Key, send this form containing your SystemJ Identification Code (below) to Acorn Software, Inc., or contact your AcornO Software service or sales representative.  If you are outside of North America,sK contact your local HSManager distributor or send your System IdentificationEO Code directly to Acorn Software to obtain a Software Key which will enable full K use of HSM T1.0.  Note that your customer number is required.  Your licenseN* request will not be processed without it.   $                 Acorn Software, Inc.                 267 Cox St.c!                 Hudson, Ma. 01749A  E:                 Phone:  508-568-1618 x5 Fax: 508-562-1133 4                 E-Mail: LICENSE-REQUEST@ACORNSW.COM   I Please complete this software key request form by providing the followingaJ information before sending this form to Acorn Software, Inc. or your localH HSManager distributor.  Only key request forms that have been filled out completely can be processed.    B         Company:        _________________________________________ B         Customer Number:_________________________________________ B         Address:        _________________________________________ B                         _________________________________________ B                         _________________________________________ B                         _________________________________________ B         Country:        _________________________________________   nB         Phone:          _________________________________________ B         Fax:            _________________________________________ B         E-Mail:         _________________________________________   eB         Contact Person: _________________________________________ B         Title:          _________________________________________   M The following is a list of System Identification Codes for some or all of the L VAXes in your VAXcluster.  To include the System Identification Codes (SICs)N for additional VAXes in your VAXcluster, log in to those VAXes and issue the     	HSMANAGER/LICENSE=filenames   command for HSManager. t  s@ SIC:	HSM1-R37B34-NDKV66-6101PK---PD3MRM-RTM1Y2-E3C252    (HULK)    / Send the completed form to us at Acorn Softwarep   Via the internet to:= mailto:license-request@acornsw.comlicense-request@acornsw.comd   Via fax, our fax number is:r 1 (508) 562-1133   Via mail, our addrress is: Acorn Software, Inc. 267 Cox St.e Hudson, MA 01749 USA    # Appendix C	Software Problem Report tC To report a problem with HSManager, you must first put together the L information that will allow us to diagnose the problem, then contact us with> this information, either by the Internet, by telephone or Fax.   Helpful InformationkH The most critical information is the log file for your HSManager server.G Other pieces of information will be added to this list as time goes on.    Contact us by InternetM This the fastest way to get to us.  During the installation for HSManager the J mailto:support@acornsw.comHSM_SUPPORT logical name gets set as the default support email address.    ( Contact us by the carrier of your choiceI If you are not on the Internet, send us the log file with a brief letter:w Acorn Software, Inc. 267 Cox St.i Hudson, Ma. 01749f USAk attn: Software Problem Report K If you need operational support and you have a maintenance contract, pleaseh) call or FAX a Software Problem Report to:c   VOICE:	1 (508) 568-1618 x5 FAX	1 (508) 562-1133H Our business hours are 8:00 am to 5:00 PM EST (GMT -5:00).  We will call  you/email you within 24-hours.     Acorn Software Customer Service PolicyrJ October 1995 -- We are pleased to have you join our community of HSManagerK users.  We are committed to the best possible software product and the besttE possible support for you and your data library software requirements.yF Occasionally difficulties in installation or operation of our softwareH occurs.  We stand ready to assist you in the diagnosis and recovery fromK errors.  Our technical support is available by telephone, Internet and fax.s: We are open for business during the usual hours EST (USA).  D As with all our customers, we will make every effort to resolve yourJ technical difficulties or help you diagnose them to the level that you can3 seek information from the source of the difficulty.o  M We value you as our customer, especially your ideas and comments.  We welcome.J your calls and letters with suggestions on how we can improve our product,G our documentation or our technical support.  Working together we make aa< better product.  And, we thank you for purchasing HSManager.         	h 	Acorn Software, Inc.	