MultiHelp® T020 Release Notes and Installation Guide This document contains current information concerning this release of MultiHelp as well as installation instructions. Revision/Update Information: This is a new document Proprietary Information, SIO Technologies Corporation [November 8, 1995] ________________________ April 1995 __________ Copyright ©1993 SIO Technologies Corporation The information in this document is proprietary to and embodies the confidential technology of SIO Technologies Corporation Possesion, use, duplication or dissemination of the information in this document is authorized only after written permission is obtained from SIO Technologies Corporation The information contained in this document is subject to change without notice and should not be construed as a commitment by SIO Technologies Corporation SIO Technologies Corporation assumes no responsibility for any errors which may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such license. MultiHelp® is a trademark of SIO Technologies Corporation All Rights Reserved. _______________________________________________________ Contents _________________________________________________ PREFACE v _______________________________________________________ CHAPTER 1 RELEASE NOTES 1-1 _________________________________________________ 1.1 PRODUCT LICENSE 1-1 _________________________________________________ 1.2 DOCUMENTATION AVAILABILITY 1-2 _________________________________________________ 1.3 NOTABLE CHANGES AND BUG FIXES IN THIS RELEASE 1-3 1.3.1 Email interface changes _______ 1-3 1.3.1.1 Literal and End Literal Email Directives, 1-3 1.3.1.2 LOOKUPS server accepts wildcard for work reports, 1-3 1.3.1.3 USER@NODE syntax allowed for DECnet addresses, 1-4 1.3.1.4 All notification methods used for ~UserId, 1-4 1.3.1.5 New arguments available to MULTIHELP$MAIL_INSTRUCTIONS, 1-4 1.3.1.6 MH_CLASS_MAIL logical name for requests entering the queue, 1-5 1.3.1.7 Email Send and Receive filtering, 1-5 1.3.1.7.1 Receive Filtering, 1-5 1.3.1.7.2 Send Filtering, 1-7 iii Contents 1.3.2 Command Line Interface changes _______________________ 1-7 1.3.2.1 ARCHIVE and RESTORE functionality, 1-8 1.3.2.1.1 ARCHIVE and RESTORE Qualifiers, 1-8 1.3.2.2 creating NEW request and updating EXISTING request CLI messages, 1-10 1.3.2.3 /UPDATED qualifier to be used with LOOKUP/BEFORE or /SINCE, 1-10 1.3.2.4 New KEY definition file pointers, 1-10 1.3.2.5 Fixed REQUEST command output not counting lines correctly, 1-11 1.3.2.6 New /INPUT=filename qualifier to REQUEST verb, 1-11 1.3.2.7 Logical name MH_SECTION changed to MULTIHELP$SECTION, 1-12 1.3.2.8 PROFILE ADD USER foo/CUSTOMER is now default, 1-12 1.3.2.9 Enhancement to /CURRENT with REQUEST and LOOKUP, 1-12 1.3.3 Graphical User Interface changes _______________________ 1-13 1.3.3.1 GUI customizations can now be SAVED, 1-13 1.3.3.2 Email notification errors generate X-popup, 1-13 1.3.3.3 Retirement of QLOG, 1-14 1.3.3.4 Outer arrows removed from main window scrollbar, 1-14 1.3.4 General changes _______________ 1-14 1.3.4.1 Date/Time recognition enhancement, 1-14 1.3.4.2 MULTIHELP$IGNORE_CURSORS logical name, 1-15 1.3.4.3 Supporting Non-UCX TCP/IP packages, 1-15 1.3.4.4 Automatic Paging, 1-18 1.3.4.5 Automatic Faxing, 1-19 iv Contents 1.3.4.6 Logicals affecting the RPC server processes, 1-20 _______________________________________________________ CHAPTER 2 KIT INSTALLATION 2-1 _________________________________________________ 2.1 PRE-INSTALLATION TASKS 2-1 2.1.1 System Resource Requirements __ 2-1 2.1.1.1 Remote Application Servers, 2-4 2.1.2 Disable MultiHelp system access ________________________ 2-4 2.1.3 Backup the MultiHelp database files _________________________ 2-5 _________________________________________________ 2.2 HARDWARE REQUIREMENTS 2-5 _________________________________________________ 2.3 SOFTWARE REQUIREMENTS 2-5 _________________________________________________ 2.4 INSTALLING MULTIHELP 2-6 2.4.1 Initiating the installation ___ 2-7 2.4.2 Performing the Installation ___ 2-7 _________________________________________________ 2.5 POST-INSTALLATION TASKS 2-18 2.5.1 Print documentation ___________ 2-19 2.5.2 Change PASSWORD of SYSTEM User Id ____________________________ 2-19 2.5.3 Enable System Access __________ 2-19 2.5.4 MultiHelp Quick Start Guide ___ 2-20 v Contents _______________________________________________________ APPENDIX A SAMPLE INSTALLATION A-1 _______________________________________________________ APPENDIX B IVP MAIL MESSAGES B-1 _______________________________________________________ APPENDIX C SAMPLE DEINSTALLATION C-1 _______________________________________________________ APPENDIX D INSTALLATION STATISTICS D-1 _______________________________________________________ APPENDIX E IN-DEPTH RESOURCE STATISTICS E-1 E.0.1 MultiHelp Resource Requirements __________________ E-1 E.0.1.1 OpenVMS AXP Resources Data, E-1 E.0.1.2 OpenVMS VAX Resources Data, E-5 _______________________________________________________ TABLES 2-1 Recommended SYSGEN Settings ___ 2-1 2-2 Recommended Minimum UAF Settings ______________________ 2-2 2-3 Global Pages/Sections Usage by MultiHelp _____________________ 2-2 2-4 OpenVMS AXP Resource Consumption by Interface ______ 2-3 2-5 OpenVMS VAX Resource Consumption by Interface ______ 2-3 2-6 Software Requirements _________ 2-6 E-1 OpenVMS AXP In-Depth Resource Consumption ___________________ E-1 vi Contents E-2 Recommended UAF and SYSGEN settings on OpenVMS AXP _______ E-3 E-3 Global Pages/Sections Usage ___ E-4 E-4 OpenVMS VAX In-Depth Resource Consumption ___________________ E-5 E-5 Recommended UAF and SYSGEN settings on OpenVMS VAX _______ E-6 E-6 Global Pages/Sections Usage ___ E-8 vii _______________________________________________________ Preface Intended Audience This document is intended for system managers who will install MultiHelp on a licensed system and for the MultiHelp Administrator responsible for communicating information about new features to end-users. Please read the release notes in Chapter 1 and the installation instructions in Chapter 2 before proceeding with the installation. v _______________________________________________________ 1 Release Notes __________________________________________________________________ 1.1 Product License A Product License is required to run the unrestricted version (T020) of MultiHelp. Without a license, you are free to run the MultiHelp- CLI version of MultiHelp as long as you like. The MultiHelp-CLI version gives you access to the fully functional MultiHelp command line interface (CLI). The product license or 30-day trial license can be obtained by one of three methods: 1 Visit our World Wide Web home page at http://www.sio.com/ where you can find product and pricing information. If your web browser has forms capabilities you may also use it to request a free 30-day trial license. 2 Sending electronic mail to multihelp@mhelp.sio.com if you have access to the INTERNET. o The first word in the subject should be LICENSE. o Provide the following information: - Hardware Address of the node which MultiHelp will be installed on. ($ MC NCP SHOW KNOW LINES CHAR) - Hardware Model of the node upon which MultiHelp will be installed. ($ WRITE SYS$OUTPUT F$GETSYI("HW_MODEL")) - Your company name - Your name 1-1 Release Notes - Your business phone number 3 Call SIO Technologies Corporation at (719)488-0581. __________________________________________________________________ 1.2 Documentation Availability Documentation will be provided on-line by the installation procedure in SYS$HELP: if requested during the installation. You will be given the opportunity to restore the documentation and either exit the installation at that time or continue on with the installation. The documentation provided is: o MULTIHELP$HDSR_UG.PS [Support Representative's Users Guide] (PostScript Format) o MULTIHELP$HDSR_UG.TXT [Support Representative's Users Guide] (Text Format) o MULTIHELP$CMND_REF.PS [CLI Command Reference Manual] (PostScript Format) o MULTIHELP$CMND_REF.TXT [CLI Command Reference Manual] (Text Format) o MULTIHELP$QUICKSTART.PS [Quick Start Guide] (PostScript Format) o MULTIHELP$QUICKSTART.TXT [Quick Start Guide] (Text Format) o MULTIHELP.RELEASE_NOTES [This document] (Text Format) o MULTIHELP_RELEASE_NOTES.PS [This document] (PostScript Format) 1-2 Release Notes __________________________________________________________________ 1.3 Notable changes and bug fixes in this release This section contains a brief description of the major changes in functionality, enhancements and new features included in this release. The items listed here may or may not be included in the standard documentation. ___________________________ 1.3.1 Email interface_changes_____ 1.3.1.1 Literal and End Literal Email Directives Two new Email directives have been added that allow you to send text in an Email request submission or update that may include Email directives that you do not wish to have interpreted by MultiHelp. These new directives can be thought of as forming a LITERAL-END_ LITERAL block that can be used to delimit a section of text. \2 is used to initiate a literal block and all text in the message found after this directive is passed into MultiHelp without interpreting any directives that may be found until a \3 directive is found and designates the end of the block. _____________________ 1.3.1.2 LOOKUPS server accepts wildcard for work reports A problem was fixed that forced you to enclose an asterisk passed to the \W directive inside quotes. \W * now works as expected. 1-3 Release Notes _____________________ 1.3.1.3 USER@NODE syntax allowed for DECnet addresses You may now specify the Email addresses for a recipient over DECnet using the syntax USER@DECnet- NODENAME (e.g. SMITH@ROYAL instead of ROYAL::SMITH). An address of this form is assumed to be a DECnet address unless a period (.) is also found embedded within the string (in which case it is assumed to be an Internet address). _____________________ 1.3.1.4 All notification methods used for ~UserId When a ~UserId is encountered in a CClist, in a CLASS notification logical name list, or any other place that MultiHelp performs notifications, the UserId will now receive notification using all methods listed in their PROFILE record. Previously only Email was sent. _____________________ 1.3.1.5 New arguments available to MULTIHELP$MAIL_INSTRUCTIONS Two new arguments have been added to the ReturnAnEmailAddressList argument list in MULTIHELP$EXAMPLES:MULTIHELP$MAIL_INSTRUCTIONS.C: o Boolean CLASS_CHANGED o Boolean REOPENED With this new information, user-supplied CALLBACK routines can generate whatever EMAIL address lists they want - perhaps by adding a new entry to the MAIL_ INSTRUCTIONS array, with different WR detail, etc. Please examine MULTIHELP$EXAMPLES:MULTIHELP$MAIL_ INSTRUCTIONS.C for more detail. No further changes will be made in the SIO-supplied code, however. 1-4 Release Notes _____________________ 1.3.1.6 MH_CLASS_MAIL logical name for requests entering the queue A new attribute has been added to the scheme of MH_ CLASS_MAIL logical names such that an individual, or group of individuals can be notified when a request of a particular class enters the queue. For example: $ DEFINE/SYSTEM MH_CLASS_MAIL_UNIX_QUEUED "TONGO::DAVE,~HATCH" will notify TONGO::DAVE by Email and the UserId HATCH at all of her notification types stored in her MultiHelp profile record whenever a request of class UNIX enters the queue. See SYS$STARTUP:MULTIHELP$SYSTARTUP.TEMPLATE for more detail. _____________________ 1.3.1.7 Email Send and Receive filtering There are times that you may wish to either prevent MultiHelp from attempting to process certain Email messages or prevent MultiHelp from sending Email to a particular address. An example of this might be Email coming from an automated Email attendant such as a Postmaster used by some Email systems. To this end, we have implemented an Email filtering mechanism for both when MultiHelp receives mail and when it sends mail. _____________________ 1.3.1.7.1 Receive Filtering A simple filter file can be created to be used by the MultiHelp EMAIL-Server when it receives mail. This file is read once during each startup of as EMAIL- Server process - that is to say, each time Email is received by MultiHelp or each time an updated request is processed for notifications. The format of the file will be multi-line, one line per action and the file must reside in MULTIHELP$DIR: and must have the filename: 1-5 Release Notes [prefix]$RECEIVE_FILTER.DAT Where [prefix] represents your site prefix. For example: MultiHelp$DIR:ABCD$RECEIVE_FILTER.DAT Each line will have the format of: [from] [to] [subj] [action] [parameter] Where: o [from] = wildcard pattern match on the FROM field o [to] = wildcard pattern match on the TO field o [sub] = wildcard pattern match on the SUBJECT field o [action] = action to be taken if all fields match o [parameter] = misc information for action For example: *postmast* * * S System In this case if a mail message comes from anywhere with "postmast" in its FROM field, we will perform action S[end] to user SYSTEM. Actions: o S = send to parameter list and do not process any further o N = normal processing, this is the default if no rule lines match o D = drop in bit bucket if rules match For example: (MultiHelp$DIR:[prefix]$RECEIVE_FILTER.DAT) *postmast* * * S system * * *failure* D * * * N 1-6 Release Notes Note that the strings are *case-sensitive*. Note also that both strings "*REQUESTS" and "MULTIHELP" must be used as the To: string, because I can send MAIL to MHMAIL$REQUESTS.EXE using either MULTIHELP or SIO%REQUESTS. The filter isn't foolproof, because a tricky person could forward someone else's MAIL to MULTIHELP or [prefix]%REQUESTS, and this filter would not detect it. _____________________ 1.3.1.7.2 Send Filtering MultiHelp can also scan all addresses to which it is about to send mail and explicitly eliminate individual addresses if you specifically filter them out. The send filter file is implemented in much the same way as the receive filter, but the format is more simple. The file MULTIHELP$DIR:[prefix]$SEND_ FILTER.DAT contains a list of EMAIL addresses, one per line, and/or multiples on the same, separated by a comma, with no intervening blanks or tabs, to whom MultiHelp is not allowed to send MAIL at any time. Period. This file cannot contain wildcards. For example: (MultiHelp$DIR:[prefix]$SEND_FILTER.DAT) TONGO::DAVE SMTP%"smith@jasmine.disney.com" JIM,JONES ___________________________ 1.3.2 Command Line Interface changes 1-7 Release Notes _____________________ 1.3.2.1 ARCHIVE and RESTORE functionality The ARCHIVE REQUEST command is used to archive specified service requests based on criteria supplied by qualifiers. It will archive the specified service requests along with all related work reports and labor records from the on-line database to an archive Database. The RESTORE REQUEST command is used to retrieve specified service requests based on criteria supplied by qualifiers. It will restore the specified service requests along with all related work reports and labor records from the archive database to the on-line database Database. _____________________ 1.3.2.1.1 ARCHIVE and RESTORE Qualifiers /BEFORE=date_time Do not archive or restore requests whose creation date-time is after the date-time specified. Enclose the date-time inside quotes if it contains blanks or special characters. /SINCE=date_time Do not archive or restore requests whose creation date-time is later than the date-time specified. Enclose the date-time inside quotes if it contains blanks or special characters. /CLOSED Do not archive or restore open requests. In other words, only service requests with a closed status. 1-8 Release Notes /ID=request_id Will archive or restore the service request with the specified request Id. /STATUS[="value[,value]"] Only archive or restore service requests whose status values are equal to one of the status values specified in the list. Enclose the list in double-quotes and separate multiple status names with commas. /LOG Will generate progress messages during the archive or restore. /DELETE During an archive command /DELETE will remove the service requests from the active on-line database after archiving the request to the archive database. During a restore command /DELETE will remove the service requests from the archive database after restoring the request to the active on-line database. /EXCLUSIVE Forces the archive or restore command to take out an exclusive lock against the database. During this time other users will not be able to access any service requests. 1-9 Release Notes /REPLACE Instructs the archive or restore command to replace an existing service request with service request being archived or restored. _____________________ 1.3.2.2 creating NEW request and updating EXISTING request CLI messages Two new informational messages have been added in the CLI interface to inform you that a request is either being CREATED or UPDATED and what the associated RequestId is. When a request is being updated, a message similar to the following will be displayed: %MULTIHELP-I-UPDATE, Updating EXISTING Service Request ID: MH19950410.2 When a request is being created, a message similar to the following will be displayed: %MULTIHELP-I-CREATE, Creating NEW Service Request ID: MH19950416.1 _____________________ 1.3.2.3 /UPDATED qualifier to be used with LOOKUP/BEFORE or /SINCE A new qualifier has been added to the LOOKUP verb in the CLI that alters the date that is examined when using the /BEFORE and /SINCE qualifiers. LOOKUP/UPDATE specifies that the /BEFORE and /SINCE qualifiers will base their search on the LAST UPDATE date for requests instead of on the CREATION date which is the default without the qualifier. _____________________ 1.3.2.4 New KEY definition file pointers The options for defining keys for the CLI interface have been greatly enhanced. Previously a single logical name, MULTIHELP$KEYS, could be defined to point to a file containing key definitions (DEFINE/KEY commands). 1-10 Release Notes There is now a second logical name, MULTIHELP$KEYS_ USER, that can be defined to point to a file that is read after the file pointed to by MULTIHELP$KEYS. The key definitions are combined and if any duplicate keys are defined, the last occurrence takes precedence. Additionally, either or both of the logical names can be defined as search-list logical names pointing to more than one file and the files will be processed in order. For example: $ DEFINE/SYSTEM MULTIHELP$KEYS MULTIHELP$DIR:MULTIHELP$SYSTEM.KEYS $ DEFINE MULTIHELP$KEYS_USER DISK1:[GRPA]GROUP.KEYS,SYS$LOGIN:MYKEYS.KEYS will result in the key definitions in the file MULTIHELP$DIR:MULTIHELP$SYSTEM.KEYS being read first, followed by DISK1:[GRPA]GROUP.KEYS and lastly by SYS$LOGIN:MYKEYS.KEYS. When one of the files is being read, an informational message is displayed including the files name. If there is an error opening one of the files, no message is displayed and the file is skipped. _____________________ 1.3.2.5 Fixed REQUEST command output not counting lines correctly A problem was fixed in which the output generated after creating or updating a REQUEST did not always count lines correctly and sometimes placed the MORE prompt in unexpected places. _____________________ 1.3.2.6 New /INPUT=filename qualifier to REQUEST verb A new qualifier has been added to the REQUEST verb that allows the inclusion of an external file into a work report. The /INPUT qualifier cannot be used with the /EDIT qualifier, so you must have already fully formatted the text with an external edit prior to including it into MultiHelp. You will still be prompted for the subject of a request or an update, but after entering it the work report will be entered with no further interaction. 1-11 Release Notes _____________________ 1.3.2.7 Logical name MH_SECTION changed to MULTIHELP$SECTION Previously, the logical name MH_SECTION was used to point to a custom TPU section file. This logical name has been changed to MULTIHELP$SECTION. _____________________ 1.3.2.8 PROFILE ADD USER foo/CUSTOMER is now default Previously, if a UserId was added to the system using the PROFILE ADD command and neither the /CUSTOMER or /NOCUSTOMER qualifiers were specified, the UserId was added as /NOCUSTOMER (as a Support Rep). Because of security concerns this default has been changed such that /CUSTOMER is the default. _____________________ 1.3.2.9 Enhancement to /CURRENT with REQUEST and LOOKUP The CLI REQUEST and LOOKUP verbs have been modified/enhanced in their handling of the RequestId pointed to by the /CURRENT qualifier. Previously, the "current" request that was accessed by LOOKUP/CURRENT or REQUEST/CURRENT was the last request explicitly specified in a LOOKUP/ID=request-id or REQUEST/ID=request-id command. In this release, the "current" request will also be set to be the first request returned by a LOOKUP command when either: o There is currently no "current" RequestId o The last request was just closed or attempted This way, a typical specialist will login, do a LOOKUP, work the /CURRENT call (the first one on the list), then close it, then do another LOOKUP, and work the new /CURRENT call, etc. If he does not close the /CURRENT call, then the LOOKUP does not change the request-id used by /CURRENT. 1-12 Release Notes ___________________________ 1.3.3 Graphical_User_Interface_changes 1.3.3.1 GUI customizations can now be SAVED A new menu item has been added to the MultiHelp GUI main screen called Options that allows you to save and restore customizations made in the GUI interface. When a SAVE operation is performed, your customized resources are saved into a file called MULTIHELP$userid.DAT where 'userid' is your MultiHelp logon userId. The UserId is included in the filename so that multiple users can share a VMS account to access MultiHelp (such as when starting MultiHelp using the MHGUI Email address). This file is placed in the directory DECW$USER_DEFAULTS (which is typically the SYS$LOGIN directory). You may also save and restore resources using a filename you specify. You may also manually edit the resource file to add resources that are not directly accessible through the GUI menus (window colors for example) and these resources will be retained even if you later use the Save option again later. _____________________ 1.3.3.2 Email notification errors generate X-popup Any error messages generated by Email notifications after creating or updating requests in the GUI now generate a popup error notification box highlighting the error encountered as well as placing the messages into the status pane at the bottom of the GUI main window. Previously these errors were only visible at the DCL command level from which MultiHelp was started. 1-13 Release Notes _____________________ 1.3.3.3 Retirement of QLOG The QLOG Email interface for MultiHelp is no longer supported as of this release as all of its functionality is now available by using the new WWW Browser interface available native-mode on most operating system platforms. The interface may continue to function properly, but no further support will be supplied for the application. _____________________ 1.3.3.4 Outer arrows removed from main window scrollbar Previously there was a pair of small arrows above and below the vertical scrollbar on the main lookup window. These have now been removed by placing the following resource in MULTIHELP.DAT: *mainSVN.DXmuseScrollButtons: False Customers assumed that these arrows would allow them to scroll quickly to the top or the bottom of the list, but they did not perform this function and have been removed to avoid confusion. You may quickly scroll to the top or the bottom of the list simply by clicking mouse-button-2 in the scrollbar trough at the position to which you wish to move. ___________________________ 1.3.4 General_changes_____________ 1.3.4.1 Date/Time recognition enhancement Date and Time recognition has been enhanced such that the following values are recognized anywhere date and time values can be entered into MultiHelp: o TODAY (today at midnight or 00:00 hours) o YESTERDAY (yesterday at midnight or 00:00 hours) o NOW (the current date and time) 1-14 Release Notes o TOMORROW (tomorrow's date at midnight or 00:00 hours) For example: MultiHelp> LOOKUP/UPDATE/CLOSED/SINCE=YESTERDAY will perform a lookup of all requests that are currently closed and have been updated anytime yesterday or today. _____________________ 1.3.4.2 MULTIHELP$IGNORE_CURSORS logical name Some versions of SQL/Rdb have a bug that requires that we CLOSE ALL CURSORS before opening a new one after a ROLLBACK operation. As a result, the default operation of MultiHelp is to do this extra work in the RPC processes after ROLLBACK operations. If you are confident that the version of Rdb you are running does not have this bug, you may define the logical name MULTIHELP$IGNORE_CURSORS to avoid this step and get slightly better performance. For example: $ DEFINE/SYSTEM MULTIHELP$IGNORE_CURSORS TRUE _____________________ 1.3.4.3 Supporting Non-UCX TCP/IP packages The VAX MultiHelp Y020 installation presumes that Digital's UCX V3.2 product is present on the system. MultiHelp only uses UCX in the MultiHelp$HTTPD.EXE image. It needs UCX for its implementation of the following TCP/IP socket routines: o accept o bind o gethostbyaddr o getpeername o htons o listen o recv 1-15 Release Notes o send o setsockopt o socket The MultiHelp installation checks for the presence of the logical name UCX$IPC. If it's present, it links MULTIHELP$HTTPD.EXE against that object (or shareable image) library .OLB file. If it's not present, then the installation links MULTIHELP$HTTPD.EXE against UCX's library called SYS$SHARE:UCX$IPC.OLB. If you do not have UCX installed, but do happen to have an implementation of the TCP/IP socket routines, then you can make your routines available to the MultiHelp installation, by creating an object (or shareable image) library .OLB file containing the names of at least the above socket routines. There are a number of variations on how this might be accomplished: 1 Your implementation provides an object library (or shareable image) .OLB file containing all the above names precisely as they're listed above (case-blind) ... Use it: $ define UCX$IPC SYS$SHARE:MYIMPLEMENTATION.OLB $ @SYS$UPDATE:VMSINSTAL MULTIHELP020 2 Your implementation provides a shareable image .EXE file containing all the above names precisely as they appear above (case-blind) ... Insert that shareable image into a shareable image library .OLB file: $ library/shareable_ image/create SYS$SHARE:MYIMPLEMENTATION.OLB - _$ SYS$SHARE:MYIMPLEMENTATION.EXE $ define UCX$IPC SYS$SHARE:MYIMPLEMENTATION.OLB $ @SYS$UPDATE:VMSINSTAL MULTIHELP020 1-16 Release Notes 3 Your implementation provides an object library .OLB file containing the above routines, but with names differ from what is listed above (e.g. they might have prefixes before the names) ... Build a vector module containing those straight names and insert it into a copy of your library: $ create MYIMPLEMENTATION_VECTOR.MAR .title MultiHelp$SOCKETS .entry accept, 0 callg ap, g^MINE$ACCEPT ret .entry bind, 0 callg ap, g^MINE$BIND ret ... .entry socket, 0 callg ap, g^MIND$SOCKET ret .end $ macro MYIMPLEMENTATION_VECTOR.MAR $ copy SYS$SHARE:MYIMPLEMENTATION.OLB - _$ SYS$COMMON:[SYSLIB]PRIVATEIMPLEMENTATION.OLB $ library/insert SYS$SHARE:PRIVATEIMPLEMENTATION.OLB - _$ MYIMPLEMENTATION_VECTOR.OBJ $ define UCX$IPC SYS$SHARE:PRIVATEIMPLEMENTATION.OLB $ @SYS$UPDATE:VMSINSTAL MULTIHELP020 4 Your implementation provides a shareable image library .OLB file containing the above routines, but the names differ from what is listed above (e.g. they might have prefixes before the names) ... Create a private vector shareable image .EXE file and insert it into your own private shareable image library .OLB file: $ create MYIMPLEMENTATION_ VECTOR.MAR .title MultiHelp$SOCKETS .entry accept, 0 callg ap, g^MINE$ACCEPT ret .entry bind, 0 callg ap, g^MINE$BIND ret ... .entry socket, 0 callg ap, g^MIND$SOCKET ret .end $ macro MYIMPLEMENTATION_VECTOR.MAR $ link/shareable_ image=SYS$COMMON:[SYSLIB]PRIVATEIMPLEMENTATION.EXE - _$ SYS$INPUT:/options MYIMPLEMENTATION_ VECTOR.OBJ SYS$SHARE:MYIMPLEMENTATION.OLB/library $ library/shareable_image/create - _$ SYS$COMMON:[SYSLIB]PRIVATEIMPLEMENTATION.OLB - _$ SYS$SHARE:PRIVATEIMPLEMENTATION.EXE $ define UCX$IPC SYS$SHARE:PRIVATEIMPLEMENTATION.OLB $ @SYS$UPDATE:VMSINSTAL MULTIHELP020 1-17 Release Notes 5 Your implementation provides only a shareable image .EXE file containing the above routines, and their names differ from what is listed above (e.g. they might have prefixes before the names) ... Create a private shareable image .EXE file and insert it into your own private shareable image library .OLB file: $ create MYIMPLEMENTATION_ VECTOR.MAR .title MultiHelp$SOCKETS .entry accept, 0 callg ap, g^MINE$ACCEPT ret .entry bind, 0 callg ap, g^MINE$BIND ret ... .entry socket, 0 callg ap, g^MIND$SOCKET ret .end $ macro MYIMPLEMENTATION_VECTOR.MAR $ link/shareable_ image=SYS$COMMON:[SYSLIB]PRIVATEIMPLEMENTATION.EXE - _$ SYS$INPUT:/options MYIMPLEMENTATION_VECTOR.OBJ SYS$SHARE:MYIMPLEMENTATION.EXE/shareable_image $ library/shareable_image/create - _$ SYS$COMMON:[SYSLIB]PRIVATEIMPLEMENTATION.OLB - _$ SYS$SHARE:PRIVATEIMPLEMENTATION.EXE $ define UCX$IPC SYS$SHARE:PRIVATEIMPLEMENTATION.OLB $ @SYS$UPDATE:VMSINSTAL MULTIHELP020 _____________________ 1.3.4.4 Automatic Paging The user-modifiable paging software supplied by MultiHelp uses the following logical names to determine how to access modems available for MultiHelp notification paging operations. They should have AT- compatible modems attached directly (for physical device names) or indirectly (for LAT service names). MultiHelp$PAGER_PORT DIALOUT ! LAT service for a set of ports MultiHelp$PAGER_PORT0 LTA2: ! Physical device name MultiHelp$PAGER_PORT1 $PORT3 ! Logical pointing to physical device MultiHelp$PAGER_PORT2 PORT4 ! LAT service for a single port These four different forms represent four different terminal/modem access methods. DIALOUT represents a LAT service which describes a set of physical terminal ports. LTA2: is a particular physical device, as is $PORT3, and PORT4 represents the LAT service name for a particular port. 1-18 Release Notes The paging software will walk through the list of logicals MultiHelp$PAGER_PORTn until it finds a terminal/modem port that is free. It will connect to that port, and deliver appropriate AT commands to dial the pager. The following define extra control for use in accessing pagers. MultiHelp$PAGER_DELAY "5" ! Delay 5 seconds between messages MultiHelp$PAGER_PREFIX "1" ! Prefix for dialing long-distance MultiHelp$PAGER_MESSAGE "1(800)555-1212" ! Phone number for your HelpDesk The PAGER_DELAY describes how long the software should wait after dialing the pager number (from the MultiHelp database) before sending the "message". The PAGER_PREFIX states what numbers must be dialed before the area code to get an outside long-distance connection (some sites might need "8", others might need "91", others might want other codes, such as "102880"). The PAGER_MESSAGE is the string of digits that appears on the window of the pager. By default, the digits of the RequestId appear. In the above example, the telephone number 1(800)555-1212 would appear in the pager window. _____________________ 1.3.4.5 Automatic Faxing The built-in user-modifiable FAXing software assumes that a FAX can be sent out using the VMSmail utility. The following logical names describe how MultiHelp is to access the FAX software. The following define the parameters for automatic FAXing: MultiHelp$FAX_XPORT "fxml%" ! VMSmail transport for sending out FAX MultiHelp$FAX_PREFIX "1" ! Prefix for dialing long-distance For example, if a customer's name is "Fred Flintstone", and his FAX number (in the MultiHelp database) is (800)555-1212, then, using the above 1-19 Release Notes logical name definitions, MultiHelp would generate the equivalent of the following VMSmail transaction: MAIL> send To: fxml%"Fred Flintstone^1(800)555-1212^" Notice the "fxml%" precedes the quoted name/number string, and the "1" precedes the FAX number. _____________________ 1.3.4.6 Logicals affecting the RPC server processes The following logicals control the behavior of the MultiHelp$RPCSRV process. This process handles all database requests for MultiHelp users. [prefix]$RPCSRV_MIN (default: 2) Controls the minimum number of RPCSRV processes that stay running if they are not being used by any MultiHelp users. [prefix]$PRCSRV_COUNT (default: 8) Controls the maximum number of RPCSRV process that are permitted to run at any time. More RPCSRV processes will generally equate to better MultiHelp database performance, but too many processes may waste precious virtual memory. 1-20 _______________________________________________________ 2 Kit Installation __________________________________________________________________ 2.1 Pre-Installation Tasks This sections describes tasks that should be performed prior to a MultiHelp upgrade. There are no special Pre-Installation tasks for a new installation other than making sure that you meet the software and hardware requirements. ___________________________ 2.1.1 System Resource Requirements This section outlines general resource requirements including recommended UAF and SYSGEN settings as well as process resource consumption. See Appendix E, In-Depth Resource Statistics for a more detailed breakdown of these numbers. Table 2-1 gives recommended settings for certain SYSGEN parameters. Table_2-1__Recommended_SYSGEN_Settings_________________ Parameter__________OpenVMS_AXP____OpenVMS_VAX__________ VIRTUALPAGECNT >= 66464 >= 30875 pages pagelets WSMAX >= 32000 >= 16823 pages ___________________pagelets____________________________ Table 2-2 gives recommended minimum settings for certain UAF quotas. 2-1 Kit Installation Table_2-2__Recommended_Minimum_UAF_Settings____________ Quota__________Value___________________________________ PGFLQUOTA 21000 ENQLM 5000 TQELM 1000 BIOLM 50 DIOLM 50 BYTLM 1000000 FILLM 50 ASTLM__________1000____________________________________ Table 2-3 gives the required GBLPAGES and GBLSECTIONS for MultiHelp. Table_2-3__Global_Pages/Sections_Usage_by_MultiHelp____ Platform___________GBLPAGES_____GBLSECTIONS____________ OpenVMS AXP 4817 25 OpenVMS_VAX________2436_________22_____________________ Table 2-4 lists resource consumption for the OpenVMS AXP platform while table 2-5 lists them for the OpenVMS VAX platform. Each table lists the resource consumption based on the interface being used. 2-2 Kit Installation Table 2-4 OpenVMS AXP Resource Consumption by ___________Interface___________________________________ Email Graphical Command In- User In- Line In- ter- Resource____________________terface____terface___face__ Memory usage (typical, 1176 827 968 per user) CPU (typical, per 2.847 1.377 5.845 transaction) seconds seconds sec- onds I/O (typical, per 1044 444 I/Os 1353 transcation) I/Os I/Os _______________________________________________________ A typical transaction consists of reviewing a service request and three of its work reports and then updating the request. _______________________________________________________ Table 2-5 OpenVMS VAX Resource Consumption by ___________Interface___________________________________ Email Graphical Command In- User In- Line In- ter- Resource____________________terface____terface___face__ Memory usage (typical, 11777 6702 7034 per user) CPU (typical, per 14.61 4.259 28.91 transaction) seconds seconds sec- onds I/O (typical, per 1122 369 I/Os 1990 transcation) I/Os I/Os _______________________________________________________ A typical transaction consists of reviewing a service request and three of its work reports and then updating the request. _______________________________________________________ 2-3 Kit Installation _____________________ 2.1.1.1 Remote Application Servers When MultiHelp is installed on remote nodes for the purpose of spreading the resource load, the resource requirements will be offloaded to the remote node. But when MultiHelp is run in this manner from a remote installation, a RDBSERVER process is created on the MultiHelp database node in order to service the data requests. This RDBSERVER process is created under the account RDB$REMOTE on the MultiHelp database node. You can control the amount of memory these RDBSERVER processes consume on the database node by modify the UAF record for this account. A recommended setting for WSEXTENT is 2048. A lower setting may be required due to memory resources on the database node, in which case you should lower it and perform tests as to acceptable performance. NOTE: The RDB$REMOTE account will be bypassed by RDB if the user has a network proxy on the database node. In this case, it will use the account designated by the proxy record. This creates a problem, because you cannot control all RDBSERVER resource consumption by modifying the RDB$REMOTE account. This is the case when a user can use their local proxy account which may have higher resource settings. ___________________________ 2.1.2 Disable MultiHelp system access Access to the MultiHelp system must be disabled in order to prevent access conflicts while performing the upgrade and insure a complete backup of the MultiHelp database. This is done by entering MultiHelp with a User Id with Administrative privilege and entering the command: SYSTEM STATUS/NOSYSTEM_ACCESS. For example: $ multihelp/user=SYSTEM/password=MANAGER system status/nosystem_access System access must be enabled after the upgrade is complete. See Section 2.5.3, Enable System Access. 2-4 Kit Installation ___________________________ 2.1.3 Backup the MultiHelp database files If you are performing an upgrade to an existing MultiHelp X8.0 installation, it is imperative that you obtain a backup of your existing MultiHelp database before performing the upgrade. A system outage during the upgrade process could make the MultiHelp database unusable. You must use the RMU utility to backup your database. Do not use the BACKUP utility. Backup to another disk drive: $ RMU/Backup/OnLine/Log/NoQuiet MultiHelp$DB $1$DUA17:[temp]MultiHelp080.RBF Backup to a tape drive: $ RMU/Backup/OnLine/Log/NoQuiet MultiHelp$DB MUA0:MultiHelp080.RBF __________________________________________________________________ 2.2 Hardware Requirements The hardware requirements are: o OpenVMS VAX or AXP System o Disk Space of approximately 35,000 blocks for the disk device that will hold the database files depending on the options chosen during installation. o Disk Space of approximately 6000 blocks for the system disk __________________________________________________________________ 2.3 Software Requirements The software requirements depend on the options you choose during installation. The installation procedure prompts you for the following: 2-5 Kit Installation This product contains two different installation options: 1) Install the full product which includes the database files. This must be installed at least once in your environment. 2) Install only the application server interface, which does not include the database files. In this case, MultiHelp runs locally but accesses the database information remotely, which was installed using option 1. Which do you want to install on this system: 1) Full product installation (including database files) 2) Application server only (without database files) * Which [1]: Table 2-6, Software Requirements, lists the minimum versions of software required depening on the selection chosen. Table_2-6__Software_Requirements_______________________ Product_____________________Selection__________________ OpenVMS AXP V1.5 Either OpenVMS VAX V5.5 Either DEC Rdb V4.2A Either OpenVMS DECwindows Motif 2 V1.2___________________________________________________ __________________________________________________________________ 2.4 Installing MultiHelp This sections describes how to initiate the installation and how to answer the questions asked of you during the installation. For an example of a sample installation see, Appendix A, Sample Installation. 2-6 Kit Installation ___________________________ 2.4.1 Initiating the installation MultiHelp is installed using the standard VMS installation procedure, SYS$UPDATE:VMSINSTAL.COM. For example, to start the installation of MultiHelp when the product distribution resides on a tape that is loaded on device MUA0:, enter the following command: $ @SYS$UPDATE:VMSINSTAL MULTIHELP020 MUA0: To start the installation when the product kit files reside on disk, issue the following command: $ @SYS$UPDATE:VMSINSTAL MULTIHELP020 ddcu:[directory] Replace ddcu:[directory] with the device and directory name of where the kit files reside (e.g. $1$DUA17:[MHKIT]). To simply extract the Installation Guide and Release Notes, use the Options N specifier, for example: $ @SYS$UPDATE:VMSINSTAL MULTIHELP020 MUA0: OPTIONS N ___________________________ 2.4.2 Performing the Installation The following section explains the installation dialog, the questions asked of you during the installation, and how to answer them. Some of the questions will not be asked during your particular installation or upgrade. This is due in part to how you answer previous questions asked of you. 1 Do you want this procedure to restore the documentation [N] 2-7 Kit Installation MultiHelp documentation is shipped along with the kit in PostScript and text format. At this time you have the option of whether to have the documentation loaded into SYS$HELP: by this procedure or to do it manually at a later time. If you answer YES to unloading the documentation now, you will be given the opportunity to unload the documentation and exit the installation. To unload the documentation manually simply restore the .B saveset using the BACKUP utility: $ backup MULTIHELP020.B/save_set SYS$HELP: * Do you want this procedure to restore the documentation [YES]? Answer YES if you want all of the documentation moved to SYS$HELP by this procedure. If you choose NO, then follow the instructions for restoring the documentation at a later time. If you answer YES then you will be prompted with the following question: * Do you want to continue with the installation [NO]? Answer YES if you want to continue with the installation. Take the default if you would prefer to have time to print the documentation and review before continuing with the installation. 2 Install Option This product contains two different installation options: 1) Install the full product which includes the database files. This must be installed at least once in your environment. 2) Install only the application server interface, which does not include the database files. In this case, MultiHelp runs locally but accesses the database information remotely, which was installed using option 1. Which do you want to install on this system: 1) Full product installation (including database files) 2) Application server only (without database files) * Which [1]: 2-8 Kit Installation For most installations you will choose option 1, Full product installation. You would choose option 2, Application server only if you want to install the MultiHelp user interface on a system that will access the MultiHelp database that resides on another node in the (DECnet) network. 3 Check required product versions The installation checks to insure that you have the required versions of OpenVMS, DEC Rdb, and OpenVMS DECwindows Motif installed on the system. If you do not have one of the products or do not have the required version the installation will fail. 4 Check for TP_SERVER process MultiHelp an its use of DEC Rdb require that the process TP_SERVER be running on your system. The installation checks for this process and if it is not found, the following message is displayed and the installation fails: Rdb requires that the TP_SERVER process be running. It is not currently running on this system. It is sometimes disabled by defining the logical name SYS$DECDTM_INHIBIT during system startup (e.g. SYLOGICALS.COM). The IVP will not run correctly without this process. If a journal file does not exist then one may need to be created with the following command: $ mcr LMCP create logfile SYS$JOURNAL:SYSTEM$.LM$JOURNAL You can start the TP_SERVER process by deassigning the logical name SYS$DECDTM_INHIBIT, then executing the following command: $ @SYS$STARTUP:DECDTM$STARTUP.COM If you receive this message, follow the instructions provided and then start the installation again. 5 Do you want to purge files replaced by this installation [YES]? 2-9 Kit Installation Answer YES to this question if you want previous versions of MultiHelp files purged at the end of the installation. You should normally answer YES . 6 Do you want to run the IVP after the installation [YES]? Answer YES to this question if you want the installation to run a procedure after the product is installed that verifies that the installation worked and that MultiHelp is functional. If you don't answer yes, you can still execute the IVP at any time after the installation by entering the following command: $ @SYS$TEST:MULTIHELP$IVP.COM userid password site_prefix Where: - userid is a privileged MultiHelp userid - password is the password of the userid given above - site_prefix is the site prefix given to your installation by SIO Technologies Corp. For an example of the mail messages sent during the IVP, see Appendix B, IVP Mail Messages. 7 Upgrade or New Installation Option Is this a 1. New Installation of MultiHelp 2. Upgrade of a previous version of MultiHelp 3. Re-Installation of MultiHelp (Previous Database Left Intact) * Which [1]: Answer with 1 if this is a new installation of MultiHelp. Answer with 2 if this is an upgrade of a previous version of MultiHelp. Answer with 3 if you are re-installing the same version of the MultiHelp software and don't want a new empty database created. 2-10 Kit Installation 8 Do you have your MultiHelp license [N]?" You may use a subset of the MultiHelp functionality without a license from SIO Technologies Corporation. To enable the full MultiHelp feature set, including: o DECwindows Motif interface o Fully-customizable Xmosaic interface o Full-function EMAIL interface o Ad-hoc report-generator interface o Automatic time/event-driven call escalation o Significant performance improvements you must purchase a license. If you have a MultiHelp license, you may enter it now. This will enable the full MultiHelp functionality. If not, you can add the license at any future time, with the LICENSE ADD command. * Do you have your MultiHelp license [NO]? Answer YES if you have your license information from SIO Technologies Corporation. If not, you will receive the following output and the installation will be aborted. To purchase a MultiHelp license, please contact SIO Technologies at (800)951-3424, or Sales@sio.com. Have ready the following information: Target node NI hardware address [$ mcr NCP show known lines characteristics] Target node hardware model number [$ write SYS$OUTPUT f$getsyi("HW_MODEL")] 9 Checksum: At this time you should enter the checksum given to you by SIO Technologies Corporation. This will be an 8 digit alphnumeric number. 10 Expiration Date: Enter the expiration date given to you exactly as given by SIO Technologies Corporation. 11 Site Prefix: 2-11 Kit Installation Enter the site prefix given to you by SIO Technologies Corporation. 12 Concurrent Users: Enter the value for concurrent users given to you by SIO Technologies Corporation. 13 Have you completed a backup [N]? Before you upgrade MultiHelp to the latest version, you should perform an RMU backup of your database. Use the command: $ rmu/backup/online/log/noquiet MultiHelp$DB - _$ device:[dir]MultiHelp_X080.RBF You can use a disk device if you have enough space or initialize a tape, mount the tape /FOREIGN and backup to the tape. NOTE: The space required by the RMU backup file is much smaller than that occupied by the on-line database. Refer to the DEC Rdb RMU Reference Manual for assistance. * Have you performed a Backup [N]? If you answer NO to this question, the installation will abort and allow you to perform a backup of your database. You will only be asked this question if this is an upgrade as opposed to a new installation of MultiHelp. 14 Database Option 2-12 Kit Installation You have the option of installing an abbreviated version of the database if you are short on disk space. It is recommended that you install the full version requiring 34,000 blocks of disk space if you have the space and will probably use that much space. Else you may install a database with an initial allocation of only 11,000 blocks. You also have the option of installing a Demo Database which is for the express purpose of demoing MultiHelp. This requires 11,000 blocks in disk space. Which do you want? 1. Fully allocated database (34,000 blocks) 2. Abbreviated database (11,000 blocks) 3. Demo database (11,000 blocks) * Which [1]: If you are installing MultiHelp for production purposes you must choose option 1. Otherwise, if you are installing MultiHelp for evaluation or demonstration purposes, then choose option 2 or 3. Option 3 provides a database already populated with demonstration data. NOTE: The demonstration database provided with T020 does not contain any demonstration data already pre-loaded. 15 * Select a Device: 2-13 Kit Installation This procedure requires a device and directory for the database files to reside. When choosing the device, if possible, pick a device which is not a system disk and one that does not contain a pagefile or swapfile as well. This is to reduce the I/O contention for the device that will hold the database files. A top level directory will be created on this device named [MULTIHELP]. * Select a device: DKA300: You need to select a device which will hold the MultiHelp database files. This device must have at least 35,000 free blocks on it to perform the install, and should have about 100,000 free blocks on it to allow for growth of the database over time. This is if you chose the full installation option. Try to choose a device that is not already very heavily loaded with I/O. A disk containing a system pagefile or swapfile would not be a good candidate for example. Placing the database on a lightly loaded disk will assure optimal performance of the application. The installation also insures that there is sufficient free disk space on the disk that you have specified to build the database. If there is not, the installation prompts for another device. If you enter an invalid device name, the procedure prompts you for another. 16 Select a Node and Device: If you have chosen to install only the Application Server portion of the installation you will now be prompted for the location of the MultiHelp database: 2-14 Kit Installation You have chosen not to install the Server portion of the product on this node. This means that the Server portion has been or will be installed on another node on your network. You must now supply the node name and device name where the database does (will) reside. When prompted, please respond in the following format: nodename::device: * Select a Node and Device: Enter the network path to the MultiHelp database directory. For example: MHELP::$1$DUS17: 17 MULTIHELP and MH Verb conflicts This installation updates DCLTABLES.EXE to add the following verbs: MULTIHELP MH OpenVMS requires that all DCL command verbs be unique to within the first four characters. If you have another verb, such as MULTINET, which shares the same first four characters as either MULITHELP or MH, then your previous verbs will be overwritten, possibly disabling those previous layered-products. If you answer yes to the first question, then the MULTIHELP verb will not be installed. If you answer yes to the second question, then the MH verb will not be installed. * Do you have a verb which would conflict with MULTIHELP [NO]? * Do you have a verb which would conflict with MH [NO]? Answer YES if MULTIHELP or MH would not be unique verbs on your system. Only consider the first 4 characters. For instance, if you already have the product, and therefore the verb, MULTINET on your system, continuing to install MultiHelp will disable the MULTINET verb. You should answer N in this case. 2-15 Kit Installation 18 Enter a valid UIC [220,220]: This installation creates a MultiHelp account for local interactive access to MultiHelp for users without accounts on this system. This will be a captive account with access only to the MultiHelp verb. You need to select a unique UIC for this account. This procedure will check to see if the chosen UIC is in use and report back who is using it if it is in use. It will also give you a chance to change your selection if it is in use. The account will not have a password, but access to the MultiHelp applic- ation is protected via application authorization. * Enter a valid UIC [220,220]: This installation creates a MultiHelp account. In order to create this account you must select a valid UIC for for it to use. A default UIC of [220,200] is offered and can be chosen simply by pressing RETURN. It is recommended you choose a UIC that is not currently in use. 19 Enter username to forward to SIO%REQUESTS: You will now be prompted for unique usernames to be associated with each of the MultiHelp EMAIL-Server destinations. Each username you specify will be assigned to a particular EMAIL-Server functionality-base. For instance, you may wish to assign the username MULTIHELP to the REQUESTS functionality-base. This allows your users to send EMAIL directly to the username MULTIHELP on your system to generate or update a request for service, or MHSOLUTIONS for the SOLUTIONS functionality-base, permitting your users to send MAIL directory to MHSOLUTIONS for a KnowledgeBase query. For each username you specify, an account will be created in the system authorization file. This username must be unique on your system. If you do not wish to associate a username with a particular destination, then simply hit . EMAIL users must then use the SIO%DESTINATION syntax to invoke that functionality. MultiHelp can have several different usernames for email addresses that perform specific functions related to MultiHelp. 2-16 Kit Installation For example, the email server which will assume all incoming correspondance is related to a solution query, prefix%SOLUTIONS, can be given the username EXPERT, or SOLUTIONS, etc. These forwarding addresses are required for most types of TCP/IP email. MultiHelp is a good default for site_ prefix%REQUESTS. If you are unsure for the others, you might merely prepend the site prefix to the destination such as: ABCDSOLUTIONS Where ABCD is the site prefix and SOLUTIONS is a MultiHelp destination. 20 Use SYSMAN [YES]? The installation places a DCL command procedure into the directory SYS$STARTUP called MULTIHELP$STARTUP that must be executed each time the system is rebooted in order to start the MultiHelp application. By default, an entry is made in the SYSMAN startup database for this procedure and as a result the application is started automatically during each system boot with no further intervention required by the system manager. You are given the option to bypass the use of the SYSMAN database entry if you choose. If you choose not to use SYSMAN, then you must invoke the MultiHelp startup procedure manually in your site-specific startup command file with the command: @SYS$STARTUP:MULTIHELP$STARTUP ddcu: site-prefix where ddcu: is the name of the disk that holds your MultiHelp database, and site-prefix is the lite prefix contained in your MultiHelp license. The site-specific startup command file is 2-17 Kit Installation SYS$MANAGER:SYSTARTUP_V5.COM on OpenVMS VAX systems prior to OpenVMS VAX V6.0 and SYS$MANAGER:SYSTARTUP_ VMS.COM on OpenVMS VAX systems running OpenVMS VAX V6.0 or higher and on all OpenVMS AXP systems. 21 DCLTABLES.EXE The installation makes a copy of DCLTABLES.EXE prior to making any modifications to it so that should any problem occur, the old version can quickly be restored. The following instructions are provided during the installation. Simply carry out these instructions after the installation should any problem occur. A copy of SYS$COMMON:[SYSLIB]DCLTABLES.EXE will be made before any modifications are made to it. The copy will have the following file specification: SYS$COMMON:[SYSLIB]DCLTABLES.EXE_BEFORE_MH You may delete this file after you are sure that no problems occurred during the installation. If problems did occur and you need to retain your old DCLTABLES all that is necessary is to rename it back to DCLTABLES.EXE and issue the following command: $ install replace SYS$SHARE:DCLTABLES.EXE 22 %MULTIHELP-I-KickBack, All questions have been answered All interaction with the installation procedure is completed. At this point the installation will complete with no further intervention. __________________________________________________________________ 2.5 Post-Installation Tasks This section describes recommended tasks to be performed after the installation has completed. 2-18 Kit Installation ___________________________ 2.5.1 Print documentation It is recommended that you print copies of the new documentation included with this release. MultiHelp documentation can be found in SYS$HELP:. See Section 1.2, Documentation Availability, for more information. ___________________________ 2.5.2 Change PASSWORD of SYSTEM User Id A new installation comes with a privileged MultiHelp account already setup. The UserId is "SYSTEM" and the Password is "MANAGER". It is recommended that immediately following a new installation the password on this User Id be changed to prevent unauthorized access to the application. To change the password, use the following command: $ multihelp/user=SYSTEM/pass=MANAGER - _$ profile modify user SYSTEM /password={new-value} ___________________________ 2.5.3 Enable System Access Access to the MultiHelp system must be enabled in order to allow non-privileged users to access MultiHelp after an upgrade. If this is a new installation this step is not required. This is done by entering MultiHelp with a User Id with Administrative privilege and entering the command: SYSTEM STATUS /SYSTEM_ACCESS. For example: $ multihelp/USER=system/PASSWORD=manager - _$ system status /system_access 2-19 Kit Installation ___________________________ 2.5.4 MultiHelp Quick Start Guide A new manual is being shipped with this release. The purpose of the guide is to navigate the first time user of MultiHelp or organization evaluating the product through the functionality and breadth of MultiHelp via a set of exercises and demonstrations. Each exercise is design to build on the previous one. Therefore, it is important that you start at the beginning and proceed through to the end without jumping around. The guide has been shipped with this installation and can be found in SYS$HELP or in Save Set B of the MultiHelp kit if you chose not to have the documentation downloaded by the installation. See Section 1.2, Documentation Availability for more information on accessing this new guide. 2-20 _______________________________________________________ A Sample Installation $ $ @SYS$UPDATE:VMSINSTAL MULTIHELP020 DKA400:[MULTIHELP020.KIT] OpenVMS AXP Software Product Installation Procedure V6.1 It is 19-APR-1995 at 09:17. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: DECW$SERVER_0 UCX$FTPD DECW$MWM DECW$TE_037A * Do you want to continue anyway [NO]? YES * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: MULTIHELP V2.0 Beginning installation of MULTIHELP V2.0 at 09:17 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I- RELMOVED, Product's release notes have been moved to SYS$HELP. * Do you want to purge files replaced by this installation [YES]? MultiHelp documentation is shipped along with the kit in PostScript and text format. At this time you have the option of whether to have the documentation loaded into SYS$HELP: by this procedure or to do it manually at a later time. If you answer YES to unloading the documentation now, you will be given the opportunity to unload the documentation and exit the installation. A-1 Sample Installation To unload the documentation manually simply restore the .B saveset using the BACKUP utility: $ backup MULTIHELP020.B/save_set SYS$HELP: * Do you want this procedure to restore the documentation [YES]? * Do you want to continue with the installation [NO]? YES This product contains two different installation options: 1) Install the full product which includes the database files. This must be installed at least once in your environment. 2) Install only the application server interface, which does not include the database files. In this case, MultiHelp runs locally but accesses the database information remotely, which was installed using option 1. Which do you want to install on this system: 1) Full product installation (including database files) 2) Application server only (without database files) * Which [1]: This installation requires the following software products depending on the installation options you have chosen: OpenVMS AXP V1.5 or OpenVMS VAX V5.5 (UI or Server) OpenVMS DECwindows Motif V1.0 (UI Only) DEC Rdb V4.2A (UI or Server) If DECwindows Motif is not present on your system, then the Motif interface will not be built. %MULTIHELP-I-VERSIONS, Checking required product versions This installation contains an installation verification procedure (IVP). This procedure can be run automatically at the end of the installation or can be run manually at any time after the installation by entering the following command: $ @SYS$TEST:MultiHelp$IVP.COM * Do you want to run the IVP after the installation [YES]? Is this a A-2 Sample Installation 1. New Installation of MultiHelp 2. Upgrade of a previous version of MultiHelp 3. Re- Installation of MultiHelp (Previous Database Left Intact) * Which [1]: You may use a subset of the MultiHelp functionality without a license from SIO Technologies Corporation. To enable the full MultiHelp feature set, including: o DECwindows Motif interface o Fully-customizable Xmosaic interface o Full-function EMAIL interface o Ad-hoc report-generator interface o Automatic time/event-driven call escalation o Significant performance improvements you must purchase a license. If you have a MultiHelp license, you may enter it now. This will enable the full MultiHelp functionality. If not, you can add the license at any future time, with the LICENSE ADD command. * Do you have your MultiHelp license [NO]? YES * Checksum: 40440351 * Is this correct <40440351> [YES]? * Expiration Date: 31-DEC-1999 * Is this correct <31-DEC-1999> [YES]? * Concurrent Users [-1]: * Is this correct <-1> [YES]? * Site Prefix: SIO * Is this correct [YES]? %MULTIHELP-I-DBTYPE, Choose the type of database You have the option of installing an abbreviated version of the database if you are short on disk space. It is recommended that you install the full version requiring 34,000 blocks of disk space if you have the space and will probably use that much space. Else you may install a database with an initial allocation of only 11,000 blocks. A-3 Sample Installation You also have the option of installing a Demo Database which is for the express purpose of demoing MultiHelp. This requires 11,000 blocks in disk space. Which do you want? 1. Fully allocated database (34,000 blocks) 2. Abbreviated database (11,000 blocks) 3. Demo database (11,000 blocks) * Which [1]: This procedure requires a device and directory for the database files to reside. When choosing the device, if possible, pick a device which is not a system disk and one that does not contain a pagefile or swapfile as well. This is to reduce the I/O contention for the device that will hold the database files. A top level directory will be created on this device named [MULTIHELP]. * Select a device: DKA300: This installation updates DCLTABLES.EXE to add the following verbs: MULTIHELP MH OpenVMS requires that all DCL command verbs be unique to within the first four characters. If you have another verb, such as MULTINET, which shares the same first four characters as either MULITHELP or MH, then your previous verbs will be overwritten, possibly disabling those previous layered-products. If you answer yes to the first question, then the MULTIHELP verb will not be installed. If you answer yes to the second question, then the MH verb will not be installed. * Do you have a verb which would conflict with MULTIHELP [NO]? * Do you have a verb which would conflict with MH [NO]? %MULTIHELP-I-INTERACT, Interactive MultiHelp account A-4 Sample Installation This installation creates a MultiHelp account for local interactive access to MultiHelp for users without accounts on this system. This will be a captive account with access only to the MultiHelp verb. You need to select a unique UIC for this account. This procedure will check to see if the chosen UIC is in use and report back who is using it if it is in use. It will also give you a chance to change your selection if it is in use. The account will not have a password, but access to the MultiHelp applic- ation is protected via application authorization. * Enter a valid UIC [[220,220]]: * Is [220,220] correct [YES]? %MULTIHELP-I- EMAILFORWARDING, Choose forwarding addresses for the EMAIL-Server You will now be prompted for unique usernames to be associated with each of the MultiHelp EMAIL- Server destinations. Each username you specify will be assigned to a particular EMAIL-Server functionality-base. For instance, you may wish to assign the username MULTIHELP to the REQUESTS functionality- base. This allows your users to send EMAIL directly to the username MULTIHELP on your system to generate or update a request for service, or MHSOLUTIONS for the SOLUTIONS functionality- base, permitting your users to send MAIL directory to MHSOLUTIONS for a KnowledgeBase query. For each username you specify, an account will be created in the system authorization file. This username must be unique on your system. If you do not wish to associate a username with a particular destination, then simply hit . EMAIL users must then use the SIO%DESTINATION syntax to invoke that functionality. * Enter a username which will forward to SIO%REQUESTS [MULTIHELP]: MULTIHELP * Enter a username which will forward to SIO%LOOKUPS [MHLOOKUPS]: MHLOOKUPS * Enter a username which will forward to SIO%SOLUTIONS [MHSOLUTIONS]: MHSOLUTIONS * Enter a username which will forward to SIO%COMMANDS [MHCOMMANDS]: MHCOMMANDS * Enter a username which will forward to SIO%GUI [MHGUI]: MHGUI A-5 Sample Installation By default this installation inserts the MultiHelp$STARTUP.COM procedure into SYSMAN (in the LPBETA phase in SPAWN mode). If you choose not to have this done, then you must execute the procedure from your system- specific startup file SYS$MANAGER:SYSTARTUP_ V5.COM or SYSTARTUP_VMS.COM, depending on your version of OpenVMS with the command: $ @SYS$STARTUP:MultiHelp$STARTUP _MHELP$DKA300: SIO If in a VMScluster environment, make sure that this procedure is executed on all nodes in the cluster. * Use SYSMAN [YES]? A new installation comes with a MultiHelp privileged account already registered. Its UserId is "SYSTEM" and its Password is "MANAGER". It is recommended that immediately following the installation the password on this MultiHelp account be changed to prevent unauthorized access to the application. To change the password, use the following command: $ multihelp/user=SYSTEM/pass=MANAGER - _$ profile modify user SYSTEM /password= %MULTIHELP-I-KICKBACK, All questions have been answered at 09:21 -MULTIHELP-I- KICKBACK, The installation will now proceed unattended -MULTIHELP-I- KICKBACK, Plan for 15 minutes on a VAXstation 3100/30 %VMSINSTAL-I-RESTORE, Restoring product save set B ... %MULTIHELP-I-DOC, MULTIHELP$ADMIN_GD.PS will be moved to SYS$HELP %MULTIHELP-I-DOC, MULTIHELP$CMND_REF.PS will be moved to SYS$HELP %MULTIHELP-I-DOC, MULTIHELP$HDSR_UG.PS will be moved to SYS$HELP %MULTIHELP-I- DOC, MULTIHELP$QUICKSTART.PS will be moved to SYS$HELP %MULTIHELP-I-DOC, MULTIHELP$RELEASE_ NOTES.PS will be moved to SYS$HELP %MULTIHELP-I-DOC, MULTIHELP$ADMIN_ GD.TXT will be moved to SYS$HELP %MULTIHELP-I-DOC, MULTIHELP$CMND_ A-6 Sample Installation REF.TXT will be moved to SYS$HELP %MULTIHELP-I-DOC, MULTIHELP$HDSR_UG.TXT will be moved to SYS$HELP %MULTIHELP-I- DOC, MULTIHELP$QUICKSTART.TXT will be moved to SYS$HELP %MULTIHELP-I-DOC, MULTIHELP$RELEASE_ NOTES.TXT will be moved to SYS$HELP %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... A copy of SYS$COMMON:[SYSLIB]DCLTABLES.EXE will be made before any modifications are made to it. The copy will have the following file specification: SYS$COMMON:[SYSLIB]DCLTABLES.EXE_BEFORE_MH You may delete this file after you are sure that no problems occurred during the installation. If problems did occur and you need to retain your old DCLTABLES all that is necessary is to rename it back to DCLTABLES.EXE and issue the following command: $ install replace SYS$SHARE:DCLTABLES.EXE %MULTIHELP-I-BUILDDB, Building database %VMSINSTAL- I-SYSDIR, This product creates system disk directory _ MHELP$DKA300:[MULTIHELP]. %CREATE-I-EXISTS, _MHELP$DKA300:[MULTIHELP] already exists %VMSINSTAL-I-RESTORE, Restoring product save set F ... %RMU-I- LOGCONVRT, database root converted to current structure level %RMU-S-CVTDBSUC, database _MHELP$DKA300:[MULTIHELP]MULTIHELP.RDB;1 successfully converted from version V4.2 to V5.1 %RMU-I-CVTCOMSUC, CONVERT committed for _ MHELP$DKA300:[MULTIHELP]MULTIHELP.RDB;1 to version V5.1 %VMSINSTAL-I-RESTORE, Restoring product save set H ... %RMU-I- LOGCONVRT, database root converted to current structure level %RMU-S-CVTDBSUC, database _MHELP$DKA300:[MULTIHELP]MULTIHELP_ ARCHIVE.RDB;1 successfully converted from version V4.2 to V5.1 %RMU-I-CVTCOMSUC, CONVERT committed for _ A-7 Sample Installation MHELP$DKA300:[MULTIHELP]MULTIHELP_ARCHIVE.RDB;1 to version V5.1 %MULTIHELP-I-DBBUILT, Database build complete %MULTIHELP-I-LINKING, Linking MultiHelp images -MULTIHELP-I-LINKING, Ignore any DATMISMCH messages %MULTIHELP-I-LINKING, Link complete %MULTIHELP-I-HTML, Creating MHML library %VMSINSTAL- I-SYSDIR, This product creates system disk directory _ MHELP$DKA300:[MULTIHELP.MHML]. %VMSINSTAL-I-RESTORE, Restoring product save set I ... %MULTIHELP-I-HELPLIB, Providing on-line help %MULTIHELP-I-HELPLIB, On-line help provided This installation places a DCL procedure in SYS$UPDATE: that will De-Install MultiHelp - SYS$UPDATE:MultiHelp$DEINSTALL.COM. %MULTIHELP-I- EXAMPLES, Providing example files to MultiHelp$EXAMPLES This procedure supplies the sources for the QuickLog Application. The application runs on the following platforms: UNIX, Ultrix, OpenVMS VAX, OpenVMS AXP The application is automatically built on the installation node/cluster. Instructions for building, customizing, and executing the application on other platforms are included in the Release Notes and the sources for the application. The files provided are: SYS$SYSROOT:[SYSHLP.EXAMPLES.MultiHelp]QLog.C SYS$SYSROOT:[SYSHLP.EXAMPLES.MultiHelp]QLog.UIL SYS$SYSROOT:[SYSHLP.EXAMPLES.MultiHelp]QLog.Dat %VMSINSTAL-I- ACCOUNT, This installation creates an ACCOUNT named MULTIHELP. %UAF-I-ADDMSG, user record successfully added %UAF-I-RDBADDMSGU, identifier MULTIHELP value [000220,000220] added to rights database %VMSINSTAL-I- A-8 Sample Installation ACCOUNT, This installation updates an ACCOUNT named MULTIHELP. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- ACCOUNT, This installation updates an ACCOUNT named MULTIHELP. %UAF-I-MDFYMSG, user record(s) updated %VMSINSTAL-I- MOVEFILES, Files will now be moved to their target directories... %MULTIHELP-I-POSTINSTALL, Performing post-installation tasks %MULTIHELP-I-INSTALL, Installing new version of DCLTABLES.EXE %MULTIHELP-I- STARTUP, This procedure adds MultiHelp$STARTUP.COM to SYSMAN %MULTIHELP-I-IGNORE, Ignore any STRTUPNOREM messages %VMSINSTAL-I-STRTUPNOREM, File not found in startup database -VMSINSTAL-I-STRTUPNOREM, REMOVE not done %MULTIHELP-I-SETPROT, Setting protections on DB files %MULTIHELP-I-STARTUP, Executing MultiHelp$STARTUP.COM -MULTIHELP-I-STARTUP, P1 = _MHELP$DKA300: -MULTIHELP-I-STARTUP, P2 = SIO %MULTIHELP-I-LICENSE_ADD, Adding MultiHelp license MultiHelp[R] Version Y020, SIO Technologies Corp., 1993-1995 © %MULTIHELP-I-DBATTACH, attaching to database -- one moment please %MULTIHELP-E-LICENSE_MISSING, no such license Welcome to the fully functional command line interface to MultiHelp. There are many more features available to improve the capabilities of your HelpDesk for licensed users. For more information, please type HELP SIO at the prompt below. %MULTIHELP-I-LICENSE_ADDED, license succesfully added %MULTIHELP-I-POSTCOMPLETE, Post-installation phase complete ************************************ Beginning execution of MultiHelp IVP ************************************ Testing existance of Logicals Testing Command Line Interface MultiHelp[R] Version Y020, SIO Technologies Corp., 1993-1995 © %MULTIHELP-I-DBATTACH, attaching to database -- one moment please A-9 Sample Installation System Parameters System Status: Up REQUEST access via EMail: Yes SOLUTION access via EMail: Yes P Review Solution Bulletin Report Admin W User Id Access Access Access Access Priv Customer SIO OWN Q-- -- -- NoAdmin SYSTEM ALL QAM VM GS *ADMIN* MultiHelp[R] -+-+-+-+-+- List of Requests for Service -+-+-+-+-+- Testing EMAIL-Server interface New mail on node MHELP from MHELP::SYSTEM New mail on node MHELP from SIO%COMMANDS New mail on node MHELP from MHELP::SYSTEM New mail on node MHELP from MULTIHELP **************************************** IVP for MultiHelp completed successfully Check your returned mail to verify that the EMAIL-Server responded appropriately **************************************** Installation of MULTIHELP V2.0 completed at 10:47 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]MULTIHELP020.VMI_ DATA VMSINSTAL procedure done at 10:48 $ A-10 _______________________________________________________ B IVP Mail Messages $ $ @SYSTEST:MULTIHELP$IVP.COM SYSTEM MANAGER SIO ************************************ Beginning execution of MultiHelp IVP ************************************ Testing existance of Logicals Testing Command Line Interface MultiHelp[R] Version Y020, SIO Technologies Corp., 1993-1995 © %MULTIHELP-I-DBATTACH, attaching to database -- one moment please System Parameters System Status: Up REQUEST access via EMail: Yes SOLUTION access via EMail: Yes P Review Solution Bulletin Report Admin W User Id Access Access Access Access Priv Customer SIO OWN Q-- -- -- NoAdmin SYSTEM ALL QAM VM GS *ADMIN* MultiHelp[R] -+-+-+-+-+- List of Requests for Service -+-+-+-+-+- Testing EMAIL-Server interface New mail on node MHELP from MHELP::SYSTEM New mail on node MHELP from SIO%COMMANDS New mail on node MHELP from MHELP::SYSTEM New mail on node MHELP from MULTIHELP B-1 IVP Mail Messages **************************************** IVP for MultiHelp completed successfully Check your returned mail to verify that the EMAIL-Server responded appropriately **************************************** $ mail You have 4 new messages. MAIL> read/new #1 19-APR- 1995 10:47:34.15 NEWMAIL From: HELPMT::MAGE To: SIO%COMMANDS CC: MAGE Subj: !MultiHelp IVP Command Test \U SYSTEM \P MANAGER SEVERITY SHOW PRIORITY SHOW SYSTEM STATUS MAIL> next #2 19-APR- 1995 10:47:43.43 NEWMAIL From: SIO%COMMANDS To: MAGE CC: Subj: \! MultiHelp[R] -+-+- EMAIL-Server LogFile Echo -+-+- \! ******* MultiHelp[R] received this text: ******* \! MultiHelp/Email="MAGE"/UserId=SYSTEM/Password=MANAGER \! MultiHelp[R] Version Y020, SIO Technologies Corp., 1993- 1995 © \! %MULTIHELP-I-DBATTACH, attaching to database -- B-2 IVP Mail Messages one moment please \! \! !MultiHelp IVP Command Test \! SEVERITY SHOW \! \! Default Escalation \! Name Value Due Date Delta Description \! \! HIGH 75 000:04:00 000:00:30 Critical Impact to Customer \! MED 50 001:00:00 000:02:00 Moderate Impact to Customer \! LOW 25 007:00:00 001:00:00 Low Impact to Customer \! \! PRIORITY SHOW \! \! Name Value Description \! \! P1 90 High Priority \! P2 70 Level 2 Priority \! P3 50 Level 3 Priority \! P4 30 Level 4 Priority \! P5 10 Low Priority \! \! SYSTEM STATUS \! \! System Parameters \! \! System Status: Up \! REQUEST access via EMail: Yes \! SOLUTION access via EMail: Yes \! MAIL> next #3 19-APR- 1995 10:47:43.85 NEWMAIL From: HELPMT::MAGE To: SIO%REQUESTS CC: MAGE Subj: MultiHelp IVP Problem Test \U SYSTEM \P MANAGER Testing the Problem interface B-3 IVP Mail Messages MAIL> next #4 19-APR- 1995 10:48:27.68 NEWMAIL From: MULTIHELP To: MAGE CC: Subj: \I SIO19950419.1 MultiHelp IVP Problem Test \! MultiHelp[R] -+-+- Service Request Id: SIO19950419.1 \* Your message has been entered into the MultiHelp system. \* REPLY to this message to add another Work Report to this Request for Service. \* FORWARD this message to your LOOKUPS destination for more detail about this \* Request for Service. Forward this message to your SOLUTIONS destination \* in order to have the text of any solution titles appearing after the Request \* returned to you. Delete any titles that you do not want returned. SIO19950419.1 ! Logged: <1995-04-19:10:47> Due: <1995-04- 26:10:47> Class: <> Severity: Priority: Status: Subject: MAIL> exit $ B-4 _______________________________________________________ C Sample DeInstallation $ @SYS$UPDATE:MULTIHELP$DEINSTALL.COM ************************************************************ MultiHelp De-Installation Procedure Are you sure that you want to DeInstall MultiHelp [N]: Y Removing MultiHelp Images... Removing SYS$SYSTEM:MULTIHELP$MAIN.EXE... Removing SYS$SYSTEM:MULTIHELP$DWUI.EXE... Removing DECW$SYSTEM_DEFAULTS:MULTIHELP$DWUI.UID... Removing SYS$SHARE:MHMAIL$REQUESTS.EXE... Removing SYS$SHARE:MHMAIL$COMMANDS.EXE... Removing SYS$SHARE:MHMAIL$GUI.EXE... Removing SYS$SHARE:MHMAIL$LOOKUPS.EXE... Removing SYS$SHARE:MHMAIL$SOLUTIONS.EXE... Removing SYS$SHARE:MULTIHELP$TABLES.EXE... Removing SYS$SHARE:MULTIHELP$SHAREP.EXE... Removing SYS$SHARE:MULTIHELP$MULTIHELP.EXE... Removing SYS$SHARE:MULTIHELP$SHARE.EXE... Removing SYS$SYSTEM:MULTIHELP$RPCSRV.EXE... Removing SYS$SHARE:MULTIHELP$RPCSHR.EXE... Removing SYS$SHARE:MULTIHELP$FAX_INSTRUCTIONS.EXE... Removing SYS$SHARE:MULTIHELP$MAIL_INSTRUCTIONS.EXE... Removing SYS$SHARE:MULTIHELP$PHONE_INSTRUCTIONS.EXE... Removing SYS$SHARE:MULTIHELP$PAGER_INSTRUCTIONS.EXE... Removing SYS$SHARE:MULTIHELP$XPOPUP_INSTRUCTIONS.EXE... Removing SYS$SHARE:MULTIHELP$GENERIC_INSTRUCTIONS.EXE... Removing SYS$MESSAGE:MULTIHELP$MESSAGES.EXE... Removing SYS$SYSTEM:QLOG.EXE... Removing DECW$SYSTEM_DEFAULTS:QLOG.UID... Removing SYS$SYSTEM:MULTIHELP$ESCALATIONS.EXE... Removing SYS$HELP:MULTIHELP$MAIN.UIL... Removing DECW$SYSTEM_DEFAULTS:MULTIHELP.DAT... C-1 Sample DeInstallation Removing SYS$STARTUP:MULTIHELP$BACKUP.COM... Removing SYS$SYSTEM:MULTIHELP$HTTPD.EXE... Removing SYS$STARTUP:MULTIHELP$HTTPD_DETACH.COM... Removing SYS$STARTUP:MULTIHELP$HTTPD_RUN.COM... Removing SYS$STARTUP:MULTIHELP$HTTPD_SUBMIT.COM... Removing MultiHelp Help Libraries... Removing SYS$HELP:MULTIHELP$MAIN.HLB... Removing SYS$HELP:MULTIHELP$DWUI.HLB... Removing IVP... Removing SYS$TEST:MULTIHELP$IVP.COM... Removing Example Files... Removing SYS$SYSROOT:[SYSHLP.EXAMPLES]MULTIHELP.DIR;... Removing Release Notes and Documentation from Sys$Help... Removing DCL verb... Removing Startup Procedures... Removing SYS$STARTUP:MULTIHELP$STARTUP.COM... Removing SYS$STARTUP:MULTIHELP$SYSTARTUP.COM... Removing SYS$STARTUP:MULTIHELP$SYSTARTUP.TEMPLATE... Removing SYS$STARTUP:MHMAIL$SYSTARTUP.COM... Removing MultiHelp Account... Stopping Escalation server...SIO$ESCALATION (2020D35B) ********************************************************************* Removing the Database files deletes all data stored in them forever. This includes all MHML files in sub- directories under MultiHelp$DIR: Do you want the database files removed as well? [N]: Y ********************************************************************* Removing Database Files and the directory... $ C-2 _______________________________________________________ D Installation Statistics Initial Free Blocks: 317226 Minimum Free Blocks: 208968 Maximum Free Blocks: 317226 Final Free Blocks: 236031 Peak Utilization: 108258 (Initial-Minimum) Net Utilization: 81195 (Initial-Final) FILES ADDED HELPMT$DKA300:[MULTIHELP]HASH_INDICES.RDA;1 196 HELPMT$DKA300:[MULTIHELP]HASH_INDICES.SNP;1 202 HELPMT$DKA300:[MULTIHELP]HASH_INDICES_ARCHIVE.RDA;1 68 HELPMT$DKA300:[MULTIHELP]HASH_INDICES_ARCHIVE.SNP;1 22 HELPMT$DKA300:[MULTIHELP]HELPMATE.DIR;1 1 HELPMT$DKA300:[MULTIHELP]MHMAIL$SERVER.LOG;2 10 HELPMT$DKA300:[MULTIHELP]MHMAIL$SERVER.LOG;1 14 HELPMT$DKA300:[MULTIHELP]MHML.DIR;1 4 HELPMT$DKA300:[MULTIHELP]MH_ARCHIVE.RBF;1 2583 HELPMT$DKA300:[MULTIHELP]MULTIHELP$CAPTIVE.COM;1 HELPMT$DKA300:[MULTIHELP]MULTIHELP$LABOR_ACCOUNTING.RDA;1 132 HELPMT$DKA300:[MULTIHELP]MULTIHELP$LABOR_ACCOUNTING.SNP;1 22 HELPMT$DKA300:[MULTIHELP]MULTIHELP$LABOR_ACCOUNTING_ARCHIVE.RDA;1 68 HELPMT$DKA300:[MULTIHELP]MULTIHELP$LABOR_ACCOUNTING_ARCHIVE.SNP;1 4 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS.RDA;1 516 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS.SNP;1 D-1 Installation Statistics 42 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_ARCHIVE.RDA;1 516 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_ARCHIVE.SNP;1 6 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_PS.RDA;1 336 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_PS.SNP;1 88 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_PS_ARCHIVE.RDA;1 80 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_PS_ARCHIVE.SNP;1 16 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_WR.RDA;1 1952 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_WR.SNP;1 816 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_WR_ARCHIVE.RDA;1 224 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEMS_WR_ARCHIVE.SNP;1 96 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEM_QUEUE.RDA;1 324 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEM_QUEUE.SNP;1 22 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEM_QUEUE_ARCHIVE.RDA;1 68 HELPMT$DKA300:[MULTIHELP]MULTIHELP$PROBLEM_QUEUE_ARCHIVE.SNP;1 4 HELPMT$DKA300:[MULTIHELP]MULTIHELP$SOLUTIONS.RDA;1 1860 HELPMT$DKA300:[MULTIHELP]MULTIHELP$SOLUTIONS.SNP;1 102 HELPMT$DKA300:[MULTIHELP]MULTIHELP$SOLUTIONS_ARCHIVE.RDA;1 2116 HELPMT$DKA300:[MULTIHELP]MULTIHELP$SOLUTIONS_ARCHIVE.SNP;1 HELPMT$DKA300:[MULTIHELP]MULTIHELP$SOLUTION_ARTICLES.RDA;1 3264 HELPMT$DKA300:[MULTIHELP]MULTIHELP$SOLUTION_ARTICLES.SNP;1 352 D-2 Installation Statistics HELPMT$DKA300:[MULTIHELP]MULTIHELP$SOLUTION_ARTICLES_ ARCHIVE.RDA;1 384 HELPMT$DKA300:[MULTIHELP]MULTIHELP$SOLUTION_ARTICLES_ ARCHIVE.SNP;1 64 HELPMT$DKA300:[MULTIHELP]MULTIHELP.RDA;1 23050 HELPMT$DKA300:[MULTIHELP]MULTIHELP.RDB;1 150 HELPMT$DKA300:[MULTIHELP]MULTIHELP.SNP;1 4842 HELPMT$DKA300:[MULTIHELP]MULTIHELP_ARCHIVE.RDA;1 17608 HELPMT$DKA300:[MULTIHELP]MULTIHELP_ARCHIVE.RDB;1 150 HELPMT$DKA300:[MULTIHELP]MULTIHELP_ARCHIVE.SNP;1 836 HELPMT$DKA300:[MULTIHELP]SIO$HTTPD_DETACH.LOG;1 9 HELPMT$DKA300:[MULTIHELP]SIO$HTTPD_RUN.LOG;1 9 HELPMT$DKA300:[MULTIHELP]SIO$HTTPD_TRANS.LOG;1 0 HELPMT$DKA300:[MULTIHELP.MHML]CLASS.COM;1 2 HELPMT$DKA300:[MULTIHELP.MHML]CURRENT_PROBLEMS.HTML;1 2 HELPMT$DKA300:[MULTIHELP.MHML]EXAMPLE_FUNCTIONS.HTML;1 4 HELPMT$DKA300:[MULTIHELP.MHML]EXAMPLE_MAIN.HTML;1 3 HELPMT$DKA300:[MULTIHELP.MHML]EXTRACT_FULL_OUTPUT.HTML;1 6 HELPMT$DKA300:[MULTIHELP.MHML]EXTRACT_SIMPLE.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]EXTRACT_SIMPLE_OUTPUT.HTML;1 2 HELPMT$DKA300:[MULTIHELP.MHML]EXTRACT_SIMPLE_WR_OUTPUT.HTML;1 2 HELPMT$DKA300:[MULTIHELP.MHML]HOW_TO_CONTACT_SIO.GIF;1 2 HELPMT$DKA300:[MULTIHELP.MHML]LOOKUP2.HTML;1 1 HELPMT$DKA300:[MULTIHELP.MHML]LOOKUP_FULL.HTML;1 5 HELPMT$DKA300:[MULTIHELP.MHML]LOOKUP_FULL_OUTPUT.HTML;1 5 HELPMT$DKA300:[MULTIHELP.MHML]LOOKUP_MEDIUM.HTML;1 D-3 Installation Statistics 2 HELPMT$DKA300:[MULTIHELP.MHML]LOOKUP_SIMPLE.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]LOOKUP_SIMPLE_OUTPUT.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]MHML.HTML;1 16 HELPMT$DKA300:[MULTIHELP.MHML]MHSERVER.HTML;1 13 HELPMT$DKA300:[MULTIHELP.MHML]ONE_LOGO.GIF;1 1 HELPMT$DKA300:[MULTIHELP.MHML]ONE_LOGO_SMALL.GIF;1 HELPMT$DKA300:[MULTIHELP.MHML]QUERY_FULL.HTML;1 5 HELPMT$DKA300:[MULTIHELP.MHML]QUERY_FULL_OUTPUT.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]REQUEST_ACKNOWLEDGE.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]REQUEST_FULL.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]REQUEST_FULL_OUTPUT.HTML;1 1 HELPMT$DKA300:[MULTIHELP.MHML]REQUEST_UPDATE_SIMPLE.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]SEVERITY.COM;1 2 HELPMT$DKA300:[MULTIHELP.MHML]SIO_LOGO.GIF;1 3 HELPMT$DKA300:[MULTIHELP.MHML]SIO_LOOKUP.HTML;1 6 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_EXTRACT_LIST.HTML;1 4 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_LOGON.HTML;1 3 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_LOOKUP.HTML;1 5 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_MAIN.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_QUERY.HTML;1 5 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_QUERY_ADVANCED.HTML;1 8 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_REQUEST.HTML;1 5 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_REQUEST_ D-4 Installation Statistics ACKNOWLEDGEMENT.HTML;1 2 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_REQUEST_LIST.HTML;1 3 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_REQUEST_UPDATE.HTML;1 3 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_SOLUTION.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_SOLUTION_COMMENT.HTML;1 2 HELPMT$DKA300:[MULTIHELP.MHML]SIO_SUPPORT_SOLUTION_LIST.HTML;1 3 HELPMT$DKA300:[MULTIHELP.MHML]SOLUTION_FULL.HTML;1 HELPMT$DKA300:[MULTIHELP.MHML]SOLUTION_FULL_OUTPUT.HTML;1 3 HELPMT$DKA300:[MULTIHELP.MHML]SOLVE_IT_ONCE.GIF;1 1 HELPMT$DKA300:[MULTIHELP.MHML]TEXT_AREA.HTML;1 1 HELPMT$DKA300:[MULTIHELP.MHML]WELCOME.HTML;1 2 HELPMT$DKA300:[RDM$RUJ]MULTIHELP$0098F2E56E87F890.RUJ;1 102 HELPMT$DKA300:[RDM$RUJ]MULTIHELP$0098F2E573C169E0.RUJ;1 102 HELPMT$DKA300:[SYS0.SYSCOMMON.DECW$DEFAULTS.USER]MULTIHELP$DWUI.UID;1 736 HELPMT$DKA300:[SYS0.SYSCOMMON.DECW$DEFAULTS.USER]MULTIHELP.DAT;1 35 HELPMT$DKA300:[SYS0.SYSCOMMON.DECW$DEFAULTS.USER]QLOG.DAT;2 HELPMT$DKA300:[SYS0.SYSCOMMON.DECW$DEFAULTS.USER]QLOG.UID;1 72 HELPMT$DKA300:[SYS0.SYSCOMMON.SYS$STARTUP]MHMAIL$SYSTARTUP.COM;1 1 HELPMT$DKA300:[SYS0.SYSCOMMON.SYS$STARTUP]MULTIHELP$BACKUP.COM;1 18 HELPMT$DKA300:[SYS0.SYSCOMMON.SYS$STARTUP]MULTIHELP$HTTPD_ DETACH.COM;1 1 HELPMT$DKA300:[SYS0.SYSCOMMON.SYS$STARTUP]MULTIHELP$HTTPD_ RUN.COM;1 2 HELPMT$DKA300:[SYS0.SYSCOMMON.SYS$STARTUP]MULTIHELP$HTTPD_ D-5 Installation Statistics SUBMIT.COM;1 1 HELPMT$DKA300:[SYS0.SYSCOMMON.SYS$STARTUP]MULTIHELP$STARTUP.COM;1 HELPMT$DKA300:[SYS0.SYSCOMMON.SYS$STARTUP]MULTIHELP$SYSTARTUP.COM;1 19 HELPMT$DKA300:[SYS0.SYSCOMMON.SYS$STARTUP]MULTIHELP$SYSTARTUP.TEMPLATE;1 19 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSEXE]MULTIHELP$DWUI.EXE;1 794 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSEXE]MULTIHELP$ESCALATIONS.EXE;1 9 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSEXE]MULTIHELP$HTTPD.EXE;1 70 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSEXE]MULTIHELP$MAIN.EXE;1 118 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSEXE]MULTIHELP$RPCSRV.EXE;1 258 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSEXE]QLOG.EXE;1 69 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$ADMIN_GD.PS;1 5428 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$ADMIN_GD.TXT;1 803 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$CMND_REF.PS;1 1540 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$CMND_REF.TXT;1 774 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$DWUI.HLB;1 400 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$HDSR_UG.PS;1 9840 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$HDSR_UG.TXT;1 1255 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$MAIN.HLB;1 501 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$MAIN.UIL;1 8 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$QUICKSTART.PS;1 3853 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$QUICKSTART.TXT;1 192 D-6 Installation Statistics HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$RELEASE_NOTES.PS;1 393 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP$RELEASE_ NOTES.TXT;1 203 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSHLP]MULTIHELP020.RELEASE_NOTES;1 203 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]DCLTABLES.EXE;281 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]DCLTABLES.EXE_BEFORE_MH;40 765 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MHMAIL$COMMANDS.EXE;1 107 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MHMAIL$GUI.EXE;1 107 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MHMAIL$LOOKUPS.EXE;1 133 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MHMAIL$REQUESTS.EXE;1 266 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MHMAIL$SOLUTIONS.EXE;1 126 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$FAX_ INSTRUCTIONS.EXE;1 18 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$GENERIC_ INSTRUCTIONS.EXE;1 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$MAIL_ INSTRUCTIONS.EXE;1 21 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$MULTIHELP.EXE;1 1992 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$PAGER_ INSTRUCTIONS.EXE;1 19 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$PHONE_ D-7 Installation Statistics INSTRUCTIONS.EXE;1 10 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$RPCSHR.EXE;1 1021 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$SHARE.EXE;1 2953 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$SHAREP.EXE;1 16 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$TABLES.EXE;1 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSLIB]MULTIHELP$XPOPUP_ INSTRUCTIONS.EXE;1 10 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSMSG]MULTIHELP$MESSAGES.EXE;1 28 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSTEST]MULTIHELP$IVP.COM;1 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSUPD]MULTIHELP$DEINSTALL.COM;13 16 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSUPD]MULTIHELP020.ANL;2 2 HELPMT$DKA300:[SYS0.SYSCOMMON.SYSUPD]MULTIHELP020.VMI_DATA;24 2 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]CHANGE_BAR.TPU;1 3 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]FIRST_SOLUTION.MH;1 2 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MHREQGUI.COM;1 4 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MH_VIEWS.SQL;1 84 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP$FAX_ INSTRUCTIONS.C;1 19 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP$GENERIC_ INSTRUCTIONS.C;1 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP$MAIL_ INSTRUCTIONS.C;1 40 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP$MESSAGES.H;1 277 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP$NOTIFICATION_ D-8 Installation Statistics INSTRUCTIONS.H;1 30 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP$PAGER_ INSTRUCTIONS.C;1 24 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP$PHONE_ INSTRUCTIONS.C;1 7 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP$PROFILE.COM;1 12 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP$XPOPUP_ INSTRUCTIONS.C;1 7 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]MULTIHELP.LSE;1 17 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]QLOG.C;1 101 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]QLOG.DAT;1 5 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]QLOG.UIL;1 72 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]QS_CLASS.MH;1 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]REQUESTS_ADD.MH;1 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]RPT_PRB_WR_ LABOR.SQL;1 8 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]SOLUTIONS_ADD.MH;1 7 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]TEXT_ PAGING.EXAMPLE;1 78 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]TPAGE_ SUBSYSTEM.EXAMPLE;1 151 HELPMT$DKA300:[SYS0.SYSHLP.EXAMPLES.MULTIHELP]XSUPPORT.;1 5 HELPMT$DKA300:[SYS0.SYSUPD]MULTIHELP$DEINSTALL.COM;1 14 D-9 _______________________________________________________ E In-Depth Resource Statistics ___________________________ E.0.1 MultiHelp Resource Requirements This sections gives resource requirements and recommended UAF settings for use with MultiHelp. It is broken down into two segments, one for the OpenVMS AXP platform and one for the OpenVMS VAX platform. _____________________ E.0.1.1 OpenVMS AXP Resources Data The statistics found in Table E-1, provide in-depth resource utilization statistics gathered on an OpenVMS AXP system. Table_E-1__OpenVMS_AXP_In-Depth_Resource_Consumption___ Email GUI CLI Server Statistic___________________Usage______Usage_____Usage_ Virtual size of process 4154 3650 71770 pagelets NULL pages 1207 1202 Non-NULL P1 pages 181 181 GPTX pages 641 815 STX pages 49 38 Readonly pages 1628 1561 Writeable pages 1319 887 Heap pages 701 351 Peak working set 1666 1230 PGFIL pages 6 5 _______________________________________________________ All values are in pages unless otherwise stated. E-1 In-Depth Resource Statistics Table E-1 (Cont.) OpenVMS AXP In-Depth Resource ___________________Consumption_________________________ Email GUI CLI Server Statistic___________________Usage______Usage_____Usage_ TRANS pages 344 182 VALID modified pages 826 640 Typical modified pages 1176 827 VALID clean pages 824 584 Typical page usage 2000 1411 1637 Pagefile usage <= 96 <= 80 <= blocks blocks 128 blocks _______________________________________________________ Resource_Demands_______________________________________ Global memory 690 853 1003 Process pages (typical, 2000 1411 1637 per user) Memory usage (typical, 1176 827 968 per user) CPU (typical, per 2.847 1.377 5.845 transaction) seconds seconds sec- onds I/O (typical, per 1044 444 I/Os 1353 transcation)________________I/Os_________________I/Os__ The data found in Table E-2, gives recommended UAF settings for MultiHelp users on OpenVMS AXP. E-2 In-Depth Resource Statistics Table E-2 Recommended UAF and SYSGEN settings on ___________OpenVMS_AXP_________________________________ Quota_______________________GUI________CLI_______Email_ VIRTUALPAGECNT 66464 58400 PGFLQUOTA 21104 14192 81920 ENQLM 5000 5000 5000 TQELM 1000 1000 1000 BIOLM 50 50 50 DIOLM 50 50 50 BYTLM 1000000 1000000 1000000 FILLM 50 50 50 ASTLM 1000 1000 1000 _______________________________________________________ No pagefaults occur and no pagefile usage is required (on a properly tuned system) when the following settings_are_observed._________________________________ WSMAX >= 32000 >= 22576 WSEXTENT >= 32000 >= 22576 24576* _______________________________________________________ If these values are too high for a particular installation, then they can be reduced. If they are reduced drastically, then the following typical demand can be expected on the pagefile (or modified page- list)_per_user.________________________________________ _______________________________________________________ Are values are in pagelets unless otherwise stated. (*) The /WSEXTENT value for the EMAIL-Server is arbitrary, because the code is a single path. No page is re-used more than a few times. This recommentation is based upon the fact that the MULTIHELP account can also be used interactively for access to the CLI. E-3 In-Depth Resource Statistics Table E-2 (Cont.) Recommended UAF and SYSGEN settings ___________________on_OpenVMS_AXP______________________ Quota_______________________GUI________CLI_______Email_ If these values are too high for a particular installation, then they can be reduced. If they are reduced drastically, then the following typical demand can be expected on the pagefile (or modified page- list)_per_user.________________________________________ Maximum typical pagefile <= 18816 <= 13232 <= usage blocks blocks 14928 _________________________________________________blocks TUNING NOTE: Higher working sets will give the appearnce of better graphical performance at the cost of less users per CPU. The contents of Table E-3 indicate the Global Pages/Sections usage for the images that comprise MultiHelp on OpenVMS AXP. Table_E-3__Global_Pages/Sections_Usage_________________ Image_Name______________________GBLPAGES_GBLSECTIONS___ SYS$SYSTEM:MULTIHELP$MAIN.EXE 918 2 SYS$SYSTEM:MULTIHELP$DWUI.EXE 1272 2 SYS$SYSTEM:MULTIHELP$ESCALATIONS323E 2 SYS$SHARE:MULTIHELP$SHARE.EXE 1658 2 SYS$SHARE:MULTIHELP$SHAREP.EXE 5 1 SYS$SHARE:MULTIHELP$TABLES.EXE 2 1 SYS$SHARE:MHMAIL$COMMANDS.EXE 125 3 SYS$SHARE:MHMAIL$GUI.EXE 125 3 SYS$SHARE:MHMAIL$LOOKUPS.EXE 130 3 SYS$SHARE:MHMAIL$REQUESTS.EXE 130 3 SYS$SHARE:MHMAIL$SOLUTIONS.EXE 129 3 E-4 In-Depth Resource Statistics Table_E-3_(Cont.)__Global_Pages/Sections_Usage_________ Image_Name______________________GBLPAGES_GBLSECTIONS___ _______________________________________________________ TOTAL:__________________________4817_____25____________ _____________________ E.0.1.2 OpenVMS VAX Resources Data The statistics found in Table E-4, provide in-depth resource utilization statistics gathered on an OpenVMS VAX system. Table_E-4__OpenVMS_VAX_In-Depth_Resource_Consumption___ Email GUI CLI Server Statistic___________________Usage______Usage_____Usage_ Virtual size of process 30875 23279 27270 pagelets NULL pages 142 142 Non-NULL P1 pages 2408 2408 GPTX pages 7452 8479 STX pages 1377 1108 Readonly pages 12251 11195 Writeable pages 18482 12084 Heap pages 11222 6003 Peak working set 14432 8437 PGFIL pages 31 35 TRANS pages 2439 1240 VALID modified pages 9307 5427 Typical modified pages 11777 6702 VALID clean pages 5046 3025 _______________________________________________________ All values are in pages unless otherwise stated. E-5 In-Depth Resource Statistics Table E-4 (Cont.) OpenVMS VAX In-Depth Resource ___________________Consumption_________________________ Email GUI CLI Server Statistic___________________Usage______Usage_____Usage_ Typical page usage 16823 9727 10343 Pagefile usage <= 31 <= 35 <= 39 blocks blocks blocks _______________________________________________________ Resource_Demands_______________________________________ Global memory 8829 9587 11434 Process pages (typical, 16823 9727 10343 per user) Memory usage (typical, 11777 6702 7034 per user) CPU (typical, per 14.61 4.259 28.91 transaction) seconds seconds sec- onds I/O (typical, per 1122 369 I/Os 1990 transcation)________________I/Os_________________I/Os__ The data found in Table E-5, gives recommended UAF settings for MultiHelp users on OpenVMS VAX. Table E-5 Recommended UAF and SYSGEN settings on ___________OpenVMS_VAX_________________________________ Quota_______________________GUI________CLI_______Email_ VIRTUALPAGECNT 30875 23279 _______________________________________________________ Are values are in pagelets unless otherwise stated. (*) The /WSEXTENT value for the EMAIL-Server is arbitrary, because the code is a single path. No page is re-used more than a few times. This recommentation is based upon the fact that the MULTIHELP account can also be used interactively for access to the CLI. E-6 In-Depth Resource Statistics Table E-5 (Cont.) Recommended UAF and SYSGEN settings ___________________on_OpenVMS_VAX______________________ Quota_______________________GUI________CLI_______Email_ PGFLQUOTA 18482 12084 81920 ENQLM 5000 5000 5000 TQELM 1000 1000 1000 BIOLM 50 50 50 DIOLM 50 50 50 BYTLM 1000000 1000000 1000000 FILLM 50 50 50 ASTLM 1000 1000 1000 _______________________________________________________ No pagefaults occur and no pagefile usage is required (on a properly tuned system) when the following settings_are_observed._________________________________ WSMAX >= 16823 >= 9727 WSEXTENT >= 16823 >= 9727 24576* _______________________________________________________ If these values are too high for a particular installation, then they can be reduced. If they are reduced drastically, then the following typical demand can be expected on the pagefile (or modified page- list)_per_user.________________________________________ Maximum typical pagefile <= 11777 <= 6702 <= usage blocks blocks 19638 _________________________________________________blocks TUNING NOTE: Higher working sets will give the appearnce of better graphical performance at the cost of less users per CPU. E-7 In-Depth Resource Statistics The contents of Table E-6 indicate the Global Pages/Sections usage for the images that comprise MultiHelp on OpenVMS VAX. Table_E-6__Global_Pages/Sections_Usage_________________ Image_Name______________________GBLPAGES_GBLSECTIONS___ SYS$SYSTEM:MULTIHELP$MAIN.EXE 549 3 SYS$SYSTEM:MULTIHELP$DWUI.EXE 742 3 SYS$SYSTEM:MULTIHELP$ESCALATIONS173E 2 SYS$SHARE:MULTIHELP$SHARE.EXE 572 1 SYS$SHARE:MULTIHELP$SHAREP.EXE 5 2 SYS$SHARE:MULTIHELP$TABLES.EXE 2 1 SYS$SHARE:MHMAIL$COMMANDS.EXE 77 2 SYS$SHARE:MHMAIL$GUI.EXE 77 2 SYS$SHARE:MHMAIL$LOOKUPS.EXE 80 2 SYS$SHARE:MHMAIL$REQUESTS.EXE 80 2 SYS$SHARE:MHMAIL$SOLUTIONS.EXE 79 2 _______________________________________________________ TOTAL:__________________________2436_____22____________ E-8