_____________________________________________________ ALL-IN-1 Services for DECwindows Installation and Set-up Guide AA-PBBLA-TE Software Version: ALL-IN-1 Services Version 1.0 digital equipment corporation maynard, massachusetts _____________________________________________________ January, 1991 AA-PBBLA-TE The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that 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. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. © Digital Equipment Corporation 1991. All Rights Reserved. Printed in U.S.A. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: ALL-IN-1 LN03 VAX FMS CDA LN03 PLUS VAXmate DDIF MicroVAX VAXstation DEC MicroVMS VAX VTX DECdecision Rdb/VMS VMS DECnetocument wVAXprepared usiVT VAX DOCUMENT, Version 1.2. DECwindows VAXcluster WPS-PLUS DECwrite VAX DOCUMENT DIGITAL PostScript [R] is a registered trademark of Adobe Systems, Inc. ________________________________________________________________ Contents Preface.................................................. vii 1 Preparing to Install ALL-IN-1 Services 1.1 Required Hardware............................... 1-2 1.2 Required Software............................... 1-2 1.3 Optional Software............................... 1-3 1.4 Order of Installation........................... 1-3 1.5 Full and Additional Language Installations...... 1-3 1.6 Contents of Your Kit............................ 1-4 1.7 Required Disk Space............................. 1-4 1.8 Installation Time............................... 1-5 1.9 Setting Up Your Environment for ALL-IN-1 Services........................................ 1-6 1.10 Handling Conflicts with Customization Management...................................... 1-6 1.11 Registering Your License........................ 1-7 1.12 Setting the JTQUOTA............................. 1-7 1.13 Verifying Your ALL-IN-1 Environment............. 1-8 1.14 Handling Installation Errors.................... 1-8 1.15 Backing Up Disks................................ 1-9 iii 2 Installing ALL-IN-1 Services 3 Preparing ALL-IN-1 Services for Operation 3.1 Modifying Your ALL-IN-1 Site Startup File....... 3-1 3.2 Starting Up Images in a VAXcluster.............. 3-2 3.3 Preparing Workstations for Remote Display....... 3-2 3.4 Setting Required Parameters and Quotas.......... 3-4 3.4.1 Setting User Account Quotas .................. 3-4 3.4.2 Setting SYSGEN Parameters .................... 3-6 3.5 Running the ALL-IN-1 Services Startup File...... 3-9 3.6 Resolving Conflicts with Customizations......... 3-9 3.6.1 Resolving Conflicts with OA$MAIN.EXE ......... 3-10 3.6.2 Resolving Conflicts with Customization Management................................... 3-11 3.7 Run the MICA$POSTINSTALL_DRV Command Procedure....................................... 3-12 3.8 Adding the ALL-IN-1 Services Form Library to User Profiles................................... 3-13 3.9 Converting Menus to Windows..................... 3-13 3.10 Verifying the Installation...................... 3-15 3.10.1 Running the IVP .............................. 3-16 3.10.2 Verifying That ALL-IN-1 Services Is Ready to Use.......................................... 3-17 A Sample Installation of ALL-IN-1 Services B Sample Installation of an Additional Language of ALL-IN-1 Services iv C Forms Provided with ALL-IN-1 Services D Files and Logicals Installed on Your System D.1 Logicals Added to the System Table.............. D-1 D.2 ALL-IN-1 Logicals Added to Each Language Table........................................... D-3 D.3 Files Placed on the System Disk................. D-4 D.4 Files Placed in the ALL-IN-1 Directory.......... D-4 D.5 ALL-IN-1 Files Modified......................... D-4 D.6 Files Placed in the ALL-IN-1 Services Directory....................................... D-5 E PUB Log Files F Log of MICA$POSTINSTALL_DRV Index Tables 1-1 Required Disk Space............................. 1-5 3-1 Required Quotas for ALL-IN-1 User Accounts...... 3-5 3-2 Required SYSGEN Parameters...................... 3-7 v ________________________________________________________________ Preface Purpose This guide describes how to install ALL-IN-1 Services for DECwindows (ALL-IN-1 Services), Version 1.0. Intended Audience Use this guide if you are installing ALL-IN-1 Services. You should have experience using VMSINSTAL to install software on VAX/VMS processors. To do the post-installation tasks, you should have system management experience with ALL-IN-1 and VMS. Organization This manual contains the following chapters: _ Chapter 1, "Preparing to Install ALL-IN-1 Services," describes requirements you must meet and tasks you must do before you install ALL-IN-1 Services. vii _ Chapter 2, "Installing ALL-IN-1 Services," takes you through the ALL-IN-1 Services installation procedure step-by-step. _ Chapter 3, "Preparing ALL-IN-1 Services for Operation," explains the post-installation tasks you must do before users can access and work with ALL-IN-1 Services. This manual also contains the following appendixes: _ Appendix A, "Sample Installation of ALL-IN-1 Services," shows a sample installation session of a full kit, which installs language-independent and language-dependent files. _ Appendix B, "Sample Installation of an Additional Language of ALL-IN-1 Services," shows a sample installation session for an additional language. For example, you can install an English version on ALL-IN-1 Services and later install German as an additional language. This installation installs only the language-dependent files. _ Appendix C, "Forms Provided with ALL-IN-1 Services," lists the forms in the ALL-IN-1 Services form libraries. _ Appendix D, "Files and Logicals Installed on Your System," lists the logicals and file names that the ALL-IN-1 Services installation procedure adds to and modifies on your system. _ Appendix E, "PUB Log Files," shows a partial log for the PUB command procedure, which is explained in Section 3.9. _ Appendix F, "Log of MICA$POSTINSTALL_DRV," shows a sample log for the MICA$POSTINSTAL_DRV command procedure, which is explained in Chapter 3. viii Related Documents For more information on ALL-IN-1 Services, see the following manuals: ALL-IN-1 Services for DECwindows User's Guide ALL-IN-1 Services for DECwindows Customization Guide For more information on installing ALL-IN-1, see the following manuals: ALL-IN-1 Management Guide ALL-IN-1 Administration Guide ALL-IN-1 Installation Guide For more information on installing software on VAX/VMS, see the following manuals: VAX/VMS System Manager's Reference Manual VMS License Utility Manual Introduction to VMS System Management Guide to Setting Up a VMS System VMS Authorize Utility Manual Guide to DECnet-VAX Networking For more information on installing DECwrite, see the DECwrite Installation Guide for VMS. Conventions This guide uses the following conventions: _____________________________________________________________ Conventions______Meaning_____________________________________ CTRL/X Indicates that you press the control key and then another key (in this case, the X key.) ix _____________________________________________________________ Conventions______Meaning_____________________________________ Square brackets Indicate default answers to questions ([ ]) displayed during installation. Italics Indicate variable information in commands or installation questions. Enter Indicates that you type information and _________________press_RETURN._______________________________ x 1 ________________________________________________________________ Preparing to Install ALL-IN-1 Services This chapter discusses the following requirements and issues you should address or be aware of before installing ALL-IN-1 Services for DECwindows (ALL-IN-1 Services), Version 1.0: _ Required hardware _ Required software _ Optional software _ Order of installation _ Full and additional language installations _ Contents of your kit _ Required disk space _ Installation time _ Setting up your environment for ALL-IN-1 Services _ Handling conflicts with Customization Management This chapter also explains how to do the following tasks, which you must do before installing ALL-IN-1 Services: _ Registering your license _ Setting the JTQUOTA Preparing to Install ALL-IN-1 Services 1-1 _ Verifying your ALL-IN-1 environment _ Handling installation errors _ Backing up your disks 1.1 Required Hardware To run ALL-IN-1 Services, you must have the following hardware: _ A VAX system capable of running ALL-IN-1 and DECwindows. _ A supported display device-see the System Support Addendum (SSA) to the Software Product Description (SPD) for an up- to-date list of supported hardware that you can use with ALL-IN-1 Services. 1.2 Required Software You must install the following software before you install ALL-IN-1 Services. You must install it on the same system that you plan to install ALL-IN-1 Services on. _ VMS V5.3 or VMS 5.4 with DECwindows V2.0 installed. DECwindows V2.0 is part of the VMS 5.3 kit, but you install it separately. When you install DECwindows, you have the option of installing several components. Make sure you install the following components: _ VMS DECwindows Compute Server _ VMS DECwindows Device Support _ VMS DECwindows Programming Support _ CDA Converter Library V1.0 or V1.1 and all CDA patches _ ALL-IN-1 V2.4 See the System Support Addendum (SSA) to the Software Product Description (SPD) for an up-to-date list of the software that ALL-IN-1 Services has been tested with. 1-2 Preparing to Install ALL-IN-1 Services 1.3 Optional Software DECwrite V1.1 is optional software for ALL-IN-1 Services. If you install DECwrite, users can use it from Word and Document Processing in ALL-IN-1 Services and file their documents in their ALL-IN-1 File Cabinet. For information on installing DECwrite, see the DECwrite Installation Guide for VMS. Note If you plan to install DECwrite for use with ALL-IN-1 Services, you must install it on the same system that you install ALL-IN-1 Services on. 1.4 Order of Installation Install the software in the following order: 1 VMS V5.3 or VMS V5.4 with DECwindows V2.0 components installed (see Section 1.2) 2 CDA Converter Library V1.0 or V1.1 and all CDA patches 3 ALL-IN-1 V2.4 4 ALL-IN-1 Services V1.0 Note If you install DECwrite, you can install it before or after installing ALL-IN-1 Services. 1.5 Full and Additional Language Installations You can install ALL-IN-1 Services in the following ways: _ A full kit installation-installs savesets for a specific language as well as savesets that contain code that is independent of the language you install. _ An additional language installation-installs only language-dependent savesets for a language that you want to add to the system. You should install an additional language only after you have installed a full kit. Preparing to Install ALL-IN-1 Services 1-3 1.6 Contents of Your Kit The ALL-IN-1 Services kit contains the following savesets: _____________________________________________________________ File_Name__________________Contents__________________________ ASD010.A the language-independent installation procedure ASD010.B the language-independent files ASDLlanguage[1]010.A the additional language installa- tion procedure ASDLlanguage[1]010.B the language-dependent files ASDLlanguage[1]010.C the language-dependent files ASDLlanguage[1]010.D the language-dependent files _____________________________________________________________ [1]language refers to the language of the kit you are installing.__________________________________________________ 1.7 Required Disk Space Installing ALL-IN-1 Services requires the following total amounts of disk space: _ For a full kit: 37900 blocks during the installation and 14000 after the installation _ For an additional language: 29600 blocks during the installation and 12130 after the installation Table 1-1 shows this the disk space divided up among three disks. You can use fewer disks, but you still need the same total amount of free blocks. 1-4 Preparing to Install ALL-IN-1 Services Table 1-1 Required Disk Space ________________________________________________________________ Disk _____________Number_of_Blocks_____________ During ______________________Installation_____After_Installation_______ For_a_Full_Kit:_________________________________________________ System disk 14050 300 ALL-IN-1 Services 3350 3350 (target) disk ALL-IN-1 disk[1] 20500 10350 ________________________________________________________________ For_an_Additional_Language[2]:__________________________________ System disk 13900 30 ALL-IN-1 Services 2250 2250 (target) disk ALL-IN-1 disk[1] 13450 9850 ________________________________________________________________ [1]The space on the ALL-IN-1 disk refers only to the space that ALL-IN-1 Services uses. It does not include the space that ALL-IN-1 uses. [2]An additional language assumes that you have already installed the full kit and are now installing only the language- dependent files for a specific language. ________________________________________________________________ 1.8 Installation Time The installation can take from 30 minutes to an hour, depending on the type of VAX/VMS system you are using. Note This is the time to install ALL-IN-1 Services. The post- installation tasks can approximately 8 hours to complete, but much of this can be done in batch mode. Preparing to Install ALL-IN-1 Services 1-5 1.9 Setting Up Your Environment for ALL-IN-1 Services You can set up your environment for ALL-IN-1 Services in the following ways: _ On a single machine-you can do this for stand-alone workstations or for users who set host to a different machine and set display to their workstations. In either case, you are running ALL-IN-1 Services using the power and disk space of the machine that you installed ALL-IN-1 Services on. _ In a VAXcluster - you can install ALL-IN-1 Services on one machine and start up the image on each user's workstation. In this case, you are using the disk space of the machine that you installed ALL-IN-1 Services on and the power of the workstation to run ALL-IN-1 Services. How you choose to set up your environment depends on the power and memory of the machines you are working with. 1.10 Handling Conflicts with Customization Management You can customize ALL-IN-1 Services files using ALL-IN-1 Customization Management. To allow this, VMSINSTAL updates Customization Management to support these files. It adds records to Customization Management data files, changes base elements in the Digital area, and adds new elements in the site area. Additionally, it checks for conflicts among files that you customized using Customization Management. The following are the ALL-IN-1 Services files that you can customize using Customization Management: _ Files that reside in the ALL-IN-1 Services or ALL-IN-1 directories _ Files that have a file type of .BLP, .COM, .FRM, and .SCP VMSINSTAL checks to see if you customized any of these files using Customization Management. If you have and there are conflicts, VMSINSTAL places information about the conflicts in MICA$BUILD_SHARE:MICA$CM_CONFLICT.TXT. You must resolve these conflicts after installing ALL-IN-1 Services. See Section 3.6 for information on doing so. See Appendix C and Appendix D for names of all files and forms that ALL-IN-1 Services adds and changes. 1-6 Preparing to Install ALL-IN-1 Services 1.11 Registering Your License Your kit includes a Product Authorization Key (PAK). This is a paper certificate that contains data you use to register your license. Note The installation for ALL-IN-1 Services fails if you do not register your PAK. To register your PAK, use the VMS License Management Facility (LMF) as follows: 1 Log in to the system manager's account, SYSTEM. 2 At the DCL prompt, enter the following: @SYS$UPDATE:VMSLICENSE.COM This procedure prompts you for information. Respond to the prompts with data from your PAK. For more information on using LMF, see the VMS License Management Utility Manual. 1.12 Setting the JTQUOTA The account that you are using for the installation must have a JTQUOTA of at least 10000. To confirm and, if necessary, change the JTQUOTA, use the VMS Authorize Utility (AUTHORIZE), as follows: 1 Set your default directory to SYS$SYSTEM. 2 Enter the following command at the DCL prompt: RUN AUTHORIZE 3 Enter the following command at the UAF> prompt: SHOW account_name For account_name, substitute the name of the account from which you are running VMSINSTAL. 4 To change the quota, enter the following at the UAF> prompt: MODIFY account_name /JTQUOTA=10000 For account_name, substitute name of the account from which you are running VMSINSTAL. Preparing to Install ALL-IN-1 Services 1-7 5 To exit from the utility, enter EXIT at the UAF> prompt: 6 For the quotas to take effect, log out of the account and log in again. For more information on this task, see the VAX/VMS System Manager's Reference Manual. 1.13 Verifying Your ALL-IN-1 Environment ALL-IN-1 must be installed and running on your system before you install ALL-IN-1 Services. To verify this, check to see if the following logicals are defined: _ OA$BUILD _ OA$LIB _ OA$DO To make sure the logicals have been defined, enter the following commands at the DCL prompt: SHOW LOGICAL OA$LIB SHOW LOGICAL OA$BUILD SHOW LOGICAL OA$DO If the logicals do not exist, run the startup procedure by entering the following command at the DCL prompt: @SYS$STARTUP:A1V24START.COM device:[directory.DATA_SHARE] For device and directory, substitute the device and directory for the A1CONFIG.DAT file. Check for the logical definitions again by entering the SHOW LOGICAL commands as explained in this section. 1.14 Handling Installation Errors If you receive any unexpected error messages during the installation or the installation fails, do the following: 1 Check to see if you have responded to the prompts correctly. 2 If you have made a mistake and have been re-prompted, enter the correct information. 1-8 Preparing to Install ALL-IN-1 Services 3 If that fails, you should create a log file of the installation by entering the following at the DCL prompt: SET HOST/LOG=log_name node_name For log_name, enter a name for the log file that you want to be created. For node_name, enter the node that you are installing ALL-IN-1 Services on. 4 Restart the installation. 5 If you receive the same error or the installation fails at the same point, contact your Customer Support Center. 1.15 Backing Up Disks You should back up your system, ALL-IN-1, and ALL-IN-1 Services disks before installing software. If you do not and your system fails during installation, it can corrupt your disks. Preparing to Install ALL-IN-1 Services 1-9 2 ________________________________________________________________ Installing ALL-IN-1 Services This chapter explains how to install ALL-IN-1 Services using VMSINSTAL. Use it to install either of the following: _ A full kit-installs all files for ALL-IN-1 Services. _ An additional language of ALL-IN-1 Services- installs only the language-dependent files. For example, after installing the full kit using English, you can install German as an additional language. In this case, VMSINSTAL only installs the language-dependent savesets. You should install an additional language only after you have installed a full kit. During the installation procedure, VMSINSTAL asks you which type of installation you want to perform. See Appendix A for a sample installation of the full kit. See Appendix B for a sample installation of an additional language. To stop the installation procedure at any time, press CTRL/Y. When you press CTRL/Y, the installation procedure deletes all files it has created up to that point and then exits. If you want to restart the installation procedure after pressing CTRL/Y, you must restart VMSINSTAL. Note VMSINSTAL uses the initials ASD and MICA to refer to ALL-IN-1 Services. To install ALL-IN-1 Services, do the following: 1 Make sure no one on the system is using ALL-IN-1. 2 Log into the SYSTEM account. This account gives you the privileges you need to run VMSINSTAL. Installing ALL-IN-1 Services 2-1 3 If necessary, mount the tape containing the ALL-IN-1 Services software on a tape drive. 4 Set your default disk and directory to SYS$UPDATE by entering the following command at the DCL prompt: SET DEF SYS$UPDATE: 5 Enter one of the following commands at the DCL prompt: _ If you want to access the release notes during the installation, enter the following command: @VMSINSTAL ASD010 software_media OPTIONS N During the installation, VMSINSTAL prompts you to display or print the release notes. _ If you do not want to see the release notes during the installation, enter the following command: @VMSINSTAL ASD010 software_media For software_media, substitute the location of the ALL-IN-1 Services savesets. This can be a tape device or a disk device and location. You can substitute a VMS logical name for the device name. VMSINSTAL then asks you a series of questions. These questions prompt you for information required to complete the installation. The remainder of this chapter shows the questions and your options for responding to them. You can enter a ? at any time to get online help. Note Square brackets ( [] ) show default answers to the questions. To enter the default answer for a specific question, press RETURN. 6 VMSINSTAL displays the following if your DECnet network is up and running or if there is other system activity: * Do you want to continue anyway [NO]? Do one of the following: _ Press RETURN to stop the installation. Do this if you are concerned about the presence of network activity. _ Enter YES to continue the installation. 2-2 Installing ALL-IN-1 Services 7 VMSINSTAL displays the following: * Are you satisfied with the backup of your system disk [YES]? Do one of the following: _ Press RETURN if you are satisfied with your the backup of your system disk. _ Enter NO to stop the installation. You can then back up your disk and restart the installation. (If you have not backed up your disk and the system fails, it can corrupt your disk.) 8 If you specified "OPTIONS N" when invoking VMSINSTAL, VMSINSTAL displays the following options: Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: Enter an option. 9 If you specified "OPTIONS N" when invoking VMSINSTAL, VMSINSTAL displays the following: * Do you want to continue the installation [NO]? Do one of the following: _ Enter YES if you want to continue the installation. _ Press RETURN if you want to exit the installation and review the release notes. 10 VMSINSTAL displays the following: * Enter the language code for this kit [ENGLISH]: Do one of the following: _ Press RETURN to accept the default as the language of the kit you are installing. Installing ALL-IN-1 Services 2-3 _ Enter the language for the kit you are installing. In the language saveset name, ASDLlanguage010.B, language is a valid language name to enter. For example, if the saveset name is ASDLGERMAN010.B, enter GERMAN. Note VMSINSTAL displays the message, Checking LMF for product registration. If you did not register your license with LMF as explained in Chapter 1, the installation fails and you must do so before you can restart the installation. 11 VMSINSTAL displays the following: ALL-IN-1 Services for DECwindows Installation Options ===================================================== 1) Install ALL-IN-1 Services for DECwindows 2) Install an Additional Language of ALL-IN-1 Services for DECwindows * Enter an option listed above [1]: Do one of the following: _ If you are installing the full kit for ALL-IN-1 Services, enter 1. _ If you have already installed the full kit and are only installing an additional language, enter 2. 12 VMSINSTAL displays the following: * Are you satisfied with the backup of your ALL-IN-1 files [YES]? Do one of the following: _ If the disk is already backed up, press RETURN. _ If the disk is not backed up, enter N. VMSINSTAL stops, allowing you to back up the disk. You can then restart the installation. (If you have not backed up your disk and the system fails, it can corrupt your disk.) 13 VMSINSTAL displays the following: * Where do you want to load the files [device:[ASD]]: For device, you see one of the following: _ If ALL-IN-1 Services has never been installed, you see the device that ALL-IN-1 is installed on. 2-4 Installing ALL-IN-1 Services _ If ALL-IN-1 Services has been installed previously, you see the device that ALL-IN-1 Services was installed on previously. Do one of the following: _ To load the files into the default directory, press RETURN. _ To load the files on another device and directory, enter that device and directory and press RETURN. 14 VMSINSTAL displays the following: * What UIC should own the files for ALL-IN-1 Services [[ggg,mmm]]: For ggg,mmm, you see the UIC (User Identification Code) for the ALL-IN-1 files (usually the ALL-IN-1 system manager). Do one of the following: _ To use the default UIC, press RETURN. _ To use a different UIC, enter it using the format [ggg,mmm], where ggg stands for a valid group and mmm stands for a valid member within the group. 15 VMSINSTAL displays the following: Note VMSINSTAL does not display this prompt if you are installing an additional language only. *Enter the queue name for the MICA$BATCH queue [MICA$BATCH_QUEUE]: ALL-IN-1 Services requires a batch queue with the following quotas: _ JOB_LIMIT = 1 _ WSEXTENT = 5000 _ WSQUOTA = 3000 Do one of the following: _ To use the default queue name, press RETURN. VMSINSTAL creates a queue called MICA$BATCH_QUEUE and sets the quotas for it. _ To use a different queue, enter the queue name and press RETURN. Installing ALL-IN-1 Services 2-5 VMSINSTAL checks for the queue and does one of the following: _ Informs you if the queue does not exist and asks you if you want to create it (if you say yes, VMSINSTAL creates the queue and sets the quotas correctly for you) _ Lets you continue if the queue exists and the parameters are correct _ Informs you if the quotas are too low and prompts you for another queue 16 VMSINSTAL displays the following: * Do you want to purge files replaced by this installation [YES]? _ To purge temporary files that each installation of ALL-IN-1 Services creates, or to purge files from previous installations of ALL-IN-1 Services, press RETURN. _ If you want to keep temporary files or files from previous versions, enter NO. You may wish to do this, for example, if you want to keep your versions of files that ALL-IN-1 Services modifies. See Appendix D for a list of modified files. VMSINSTAL now displays a message indicating that it has asked all questions and that the installation is continuing. It begins displaying informational messages that report on the progress of the installation. When the installation is complete, VMSINSTAL displays the following: Installation of ASD V1.0 completed at time time is the current time. You can now log out of the privileged account by entering the following at the DCL prompt: LOGOUT The following message appears: SYSTEM logged out at time 2-6 Installing ALL-IN-1 Services time is the current time. Note VMSINSTAL deletes or changes entries in the process symbol tables during the installation. Therefore, if you are going to continue using the system manager's account and you want to restore these symbols, you should log out and log in again. You have completed the installation. (To verify that the installation completed successfully, you can perform the Installation Verification Procedure (IVP) explained in Section 3.10.) Proceed with the post-installation tasks explained in Chapter 3. Installing ALL-IN-1 Services 2-7 3 ________________________________________________________________ Preparing ALL-IN-1 Services for Operation This section explains how to do the following post- installation tasks: _ Modify your ALL-IN-1 site startup file _ Start up images in a VAXcluster _ Prepare workstations for remote display _ Set required parameters and quotas _ Run the ALL-IN-1 Services startup file _ Restore customizations _ Run the MICA$POSTINSTALL_DRV command procedure _ Add the ALL-IN-1 Services form library to user profiles _ Convert menus to windows _ Verify the installation 3.1 Modifying Your ALL-IN-1 Site Startup File You need to modify your ALL-IN-1 site startup file to do the following: _ Allow ALL-IN-1 Services to start up after ALL-IN-1 when the system reboots. _ Install the CDA sharable images. If these images are not installed, users cannot work with CDA documents. To do so, do the following: 1 Access the system account. Preparing ALL-IN-1 Services for Operation 3-1 2 Edit the file OA$SITE_BUILD_SHARE:A1V24_SITE_START.COM. (If this file does not exit, create it.) 3 Add the following commands to the file: @SYS$STARTUP:MICA$STARTUP.COM @OA$LIB:OA$CDA_STARTUP.COM 3.2 Starting Up Images in a VAXcluster If the nodes in your VAXcluster each have site-specific startup files, follow the startup procedure explained in Section 3.1 for each node that starts up the ALL-IN-1 Services image. See Section 1.9 for more information about running ALL-IN-1 Services in a VAXcluster environment. Note You need to make sure that the ALL-IN-1 Services startup command, @SYS$STARTUP:MICA$STARTUP.COM, shown in Section 3.1, is in each site-specific startup file. 3.3 Preparing Workstations for Remote Display If ALL-IN-1 Services is running remotely (that is, it is installed and running on a machine different from your users' workstations), these users must set host to that machine and set display to their workstations. For users to do this, you need to make sure that the host machine and the remote machines know each other's address. To make sure the host machine knows the address of the remote machine, do the following: 1 Access a privileged account on the host machine. 2 Enter the following command at the DCL prompt: MC NCP 3 Enter the following command at the NCP> prompt: SHOW KNOWN NODES This shows you the node names that the host machine knows the addresses of. 4 Do one of the following: _ If the remote node name appears in the list, enter EXIT at the NCP> prompt and go to Step 5. The host machine already knows the remote node's address. 3-2 Preparing ALL-IN-1 Services for Operation _ If the remote node name does not appear in the list, enter EXIT at the NCP> prompt and do the following: a From a privileged account on the remote machine, enter MC NCP at the DCL prompt. b Enter the following at the NCP> prompt: SHOW EXEC This shows you the address of the remote node. The information you see is similar to the following example: Node Volatile Summary as of 25-MAY-1990 08:53:50 Executor node = 33.196 (HORSES) State = on Identification = DECnet-VAX V5.3-1, VMS V5.3-1 The number next to the Executor node field is the node's address. Make note of the number (in this case, 33.196) and the name (in this case, HORSES) for the next steps. Then, enter EXIT at the NCP> prompt. c Access a privileged account on the host machine and enter the following at the DCL prompt: MC NCP d Enter the following command at the NCP> prompt: SET NODE remote_node_address NAME remote_node_name. For remote_node_address, substitute the number from Step b., next to the Executor node field (for example, 33.196). For remote_node_name, substitute the node name next to the number (for example, HORSES). e Enter the following command at the NCP> prompt: DEFINE NODE remote_node_address NAME remote_node_name. For remote_node_address, substitute the number from Step b., next to the Executor node field (for example, 33.196). For remote_node_name, substitute the node name next to the number (for example, HORSES). Preparing ALL-IN-1 Services for Operation 3-3 f To verify that the host machine now knows the remote machine's address, enter the following at the NCP> prompt: SHOW NODE remote_node_name For remote_node_name, substitute the name of the remote node. g Enter EXIT at the NCP> prompt. This returns you to the DCL prompt. 5 Repeat the steps in this section for the remote machine. To run remotely, it must know the address of the host machine. 3.4 Setting Required Parameters and Quotas This section lists the quotas and parameters that you need to set for ALL-IN-1 Services to run. Set the quotas and parameters for the following cases: _ User account quotas for each ALL-IN-1 Services user _ SYSGEN parameters for every system that you are running the ALL-IN-1 Services startup file from. 3.4.1 Setting User Account Quotas User account quotas are stored in the file SYSUAF.DAT. Use the VMS Authorize Utility (AUTHORIZE) to verify and change user account quotas to at least those listed in Table 3-1. 3-4 Preparing ALL-IN-1 Services for Operation Table 3-1 Required Quotas for ALL-IN-1 User Accounts _____________________________________________________________ Quotas________________Value__________________________________ PRCLM 10 FILLM 120 BIOLM 130 DIOLM 130 ASTLM 160 ENQLM 350 BYTLM 100000 JTQUOTA 20000 WSQUO 1500 WSEXTENT 5000 PGFLQUO_______________50000__________________________________ To change user account quotas, do the following: 1 Access the system account. 2 Set your default directory to SYS$SYSTEM. 3 Enter the following command at the DCL prompt: RUN AUTHORIZE 4 Enter the following command at the UAF> prompt: SHOW account_name For account_name, substitute the name of the account that you are checking quotas for. 5 To change a quota, enter the following the UAF> prompt: MODIFY account_name /quota_name=quota_number Preparing ALL-IN-1 Services for Operation 3-5 For account_name, substitute the name of the account whose quota you are changing. For quota_name, substitute the quota you are changing. For quota_number, substitute the new number you are changing the quota to. The following example shows what to enter if you are changing the ROBERTSON account's FILLM quota to 120: MODIFY ROBERTSON /FILLM=120 6 To exit from the utility, enter EXIT at the UAF> prompt. 7 If you have changed quotas for the account that you are logged in to, log out of the system and log back in. This allows the quotas to take effect. For more information on modifying account quotas, see the VMS Authorize Utility Manual. 3.4.2 Setting SYSGEN Parameters Make sure you set the SYSGEN parameters listed in Table 3-2 for each individual workstation that you run the ALL-IN-1 Services startup file from. ALL-IN-1 Services cannot run if you do not set these parameters. (For multi-user systems, you may need to increase these quotas.) 3-6 Preparing ALL-IN-1 Services for Operation Table 3-2 Required SYSGEN Parameters _____________________________________________________________ Parameter________Value_______________________________________ SYSMWCNT 1027 WSMAX 5000 NPAGEDYN 1841664[1] PAGEDYN 713728 NPAGEVIR 5867520 VIRTUALPAGECNT 57152 LOCKIDTBL 689 LOCKIDTBL_ 65535 MAX[2] MAXBUF[2] 5000 MAXPROCESSCNT Current value + (8 * number of ALL-IN-1 Services users) BALSETCNT Current value + (8 * number of ALL-IN-1 Services users) _____________________________________________________________ [1]If you are setting this parameter for an individual workstation running ALL-IN-1 Services, you can set this parameter to 1000000 to save memory. [2]These parameters are dynamic. You do not need to reboot after changing dynamic parameters. However, all other parameters in this table are non-dynamic. You must reboot after changing non-dynamic parameters. _____________________________________________________________ Note You must reboot the system and the individual workstations if you change non-dynamic SYSGEN parameters. To see the current values that the parameters are set to, do the following: 1 Access the system account. Preparing ALL-IN-1 Services for Operation 3-7 2 At the DCL prompt, enter the following: MCR SYSGEN 3 At the SYSGEN> prompt, enter the following: SHOW parameter_name For parameter_name, substitute a parameter listed in Table 3-2. 4 To return to DCL, enter EXIT at the SYSGEN> prompt. Change the parameters by going through the following steps: 1 Access the system account. 2 Edit the file SYS$SYSTEM:MODPARAMS.DAT. 3 Enter a new parameter or change an existing one by entering it in the following format: MIN_parameter_name = value For parameter_name, enter the parameter. For value, enter the value from Table 3-2 that corresponds with the parameter. This ensures that the parameter is set to at least the value that you have entered. For example, for SYSMWCNT, you should enter the following: MIN_SYSMWCNT = 1027 4 Exit from the file when you have finished making changes. Set the new parameters by doing one of the following: _ If you changed only dynamic system parameters, do the following: 1 Run the AUTOGEN utility by entering the following command at the DCL prompt: @SYS$UPDATE:AUTOGEN SAVPARAMS SETPARAMS FEEDBACK This sets the parameters. 2 Run the SYSGEN utility by entering following at the DCL prompt: @SYS$SYSTEM:SYSGEN 3-8 Preparing ALL-IN-1 Services for Operation 3 At the SYSGEN prompt, enter the following command: USE CURRENT 4 At the SYSGEN prompt, enter the following command: WRITE CURRENT This writes the changes to the current system. You do not need to reboot the system. _ If you changed non-dynamic parameters, you need to reboot the system for the parameters to take effect. To set the parameters and reboot the system, enter the following at the DCL prompt: @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT AUTOGEN sets the parameters and automatically reboots the system. For more information on this task, see the VAX/VMS System Manager's Reference Manual. 3.5 Running the ALL-IN-1 Services Startup File You must run the ALL-IN-1 Services startup file on the node on which you are starting ALL-IN-1 Services. This defines the logicals for ALL-IN-1 Services. Note Make sure you start ALL-IN-1 before running this startup file and that you do this task before doing any of the remaining post-installation tasks. To run the startup file, do the following: 1 Access the system account. 2 Enter the following command at the DCL prompt: @SYS$STARTUP:MICA$STARTUP.COM 3.6 Resolving Conflicts with Customizations This section explains how to resolve conflicts among ALL-IN-1 Services files and your existing files. It provides information on the following: _ Resolving OA$MAIN.EXE conflicts Preparing ALL-IN-1 Services for Operation 3-9 _ Resolving conflicts found with files customized through ALL-IN-1 Customization Management You may have additional conflicts to resolve. To find out, look at the forms and files listed in Appendix C and Appendix D. If you have customized versions of any of these, you must merge your customizations with those that ALL-IN-1 Services provides. See the ALL-IN-1 Management Guide for more information on how to resolve these conflicts. 3.6.1 Resolving Conflicts with OA$MAIN.EXE ALL-IN-1 Services provides its own versions of the following files and places them in OA$SITE_BUILD_SHARE: _ OASDF.BLI _ OASDF.OBJ _ OAGBL.BLI _ OAGBL.OBJ If you had customized versions of these files in OA$SITE_BUILD_SHARE, VMSINSTAL renamed them, appending "_OLD" to the file name (for example, OASDF_OLD.BLI). VMSINSTAL then inserts the new OAGBL.OBJ and OASDF.OBJ into OA$BUILD_SHARE:OALIBR.OLB and places a copy of the new OAGBL.OBJ and OASDF.OBJ into OA$SITE_BUILD_SHARE. To merge your customized files with the files that ALL-IN-1 Services supplies, do the following: 1 Access the ALL-IN-1 manager account. 2 Manually merge your customized files with the ALL-IN-1 Services files. 3 Compile the OAGBL.BLI and OASDF.BLI files. Note You need a VAX BLISS compiler to compile these files. 4 Insert the compiled versions into OA$BUILD_SHARE:OALIBR.OLB. 5 Relink ALL-IN-1. For information on relinking ALL-IN-1, see the ALL-IN-1 Management Guide. 3-10 Preparing ALL-IN-1 Services for Operation 3.6.2 Resolving Conflicts with Customization Management As explained in Section 1.10, VMSINSTAL updates Customization Management to support the ALL-IN-1 Services files. Additionally, it checks for conflicts among any of these files that you customized using Customization Management. If VMSINSTAL finds conflicts, it places information about them in the file MICA$BUILD_SHARE:MICA$CM_CONFLICT.TXT. VMSINSTAL also displays messages during the installation telling you there are conflicts. Note If you do not have any conflicts, you can skip this section. You should not have conflicts, for example, if you are installing ALL-IN-1 Services for the first time. This section explains how to resolve conflicts for the following: _ New files for ALL-IN-1 Services _ Existing files for ALL-IN-1 _ Existing base elements of Customization Management _ New site area files for Customization Management To resolve conflicts for any of these files, do the following: 1 Access the ALL-IN-1 manager account. 2 Read the following file: MICA$BUILD_SHARE:MICA$CM_CONFLICT.TXT For each conflict, you see the following information: _ Element-the element name, such as COMTP or CM_CTX _ Element Type-the type of element, such as COM, SCP, or DO _ Language-the language area for the element, such as, MICA_SHARE _ Filename-the filename of the element, such as COMTP.COM, or MICA$PUB.COM _ Disk Location-the name of the file delivered with the ALL-IN-1 Services kit _ Live Disk Location-the name of your customized file Preparing ALL-IN-1 Services for Operation 3-11 3 Compare the file in the Disk Location and Live Disk Location. 4 Merge the differences into the file in the Live Disk Location field. For example, for conflicts with ALL-IN-1 Services files, you could see the following information: Element: MICA$PUB Element Type: COM Language: MICA_SHARE Filename: MICA$PUB.COM Disk Location: MICA$LIB_SHARE:MICA$PUB.COM Live Disk Location: MICA$SITE_LIB_SHARE:MICA$PUB.COM In this case, merge the differences between MICA$LIB_ SHARE:MICA$PUB.COM and MICA$SITE_LIB_SHARE:MICA$PUB.COM into MICA$SITE_LIB_SHARE:MICA$PUB.COM. 3.7 Run the MICA$POSTINSTALL_DRV Command Procedure This section explains how to run the command procedure MICA$POSTINSTALL_DRV. This command procedure completes the following tasks for you: _ Relinking ALL-IN-1 _ Running and installing a new ALL-IN-1 command _ Recompiling ALL-IN-1 TXLs (text libraries) _ Adding code for viewer windows _ Adding a command for DECwrite to ALL-IN-1 _ Precompiling form libraries This procedure takes approximately 30 minutes, depending on your system. As it completes each step, it displays a prompt asking you whether you want to continue. Additionally, after relinking ALL-IN-1, it asks you if you want to move and install images. Press RETURN to accept the default answer to each of these prompts. To run the command procedure, do the following: 1 Make sure no one on your system is using ALL-IN-1. 2 Access the system account. 3-12 Preparing ALL-IN-1 Services for Operation 3 Enter the following command at the DCL prompt: @MICA$BUILD_SHARE:MICA$POSTINSTALL_DRV installation_type language - ALL-IN-1_user_name ALL-IN-1_password For variable information, substitute the following: _ installation_type-enter one of the following: _ If you installed the full kit, enter 1 _ If you installed an additional language, enter 0 _ language-enter the language of ALL-IN-1 Services that you specified in the installation procedure. _ ALL-IN-1_user_name-if you want the command procedure to run ALL-IN-1 from an ALL-IN-1 account that is different from the account associated with your current VMS account, enter the ALL-IN-1 user name for that account. (This parameter is optional.) _ ALL-IN-1_password- if you entered an ALL-IN-1 user name and it has a password associated with it, enter the password. (This parameter is optional.) See Appendix F for a log of the command procedure 3.8 Adding the ALL-IN-1 Services Form Library to User Profiles Users cannot access ALL-IN-1 Services until you add the ALL-IN-1 Services form library to their ALL-IN-1 profiles. To add it, access the ALL-IN-1 manager account and enter MICALIB in the Form Libr field of each user's ALL-IN-1 profile. See the ALL-IN-1 Management Guide for further information on working with user profiles. 3.9 Converting Menus to Windows Run the command procedure explained in this section to convert menus in the following form libraries to windows: _ OAFORM.FLB _ SITEOAFORM.FLB Preparing ALL-IN-1 Services for Operation 3-13 The command procedure runs the PUB (Platform User Interface Builder), which is the tool that converts the menu forms in these form libraries to windows. The PUB converts menus into two different styles of windows, push-button and pull-down menus. Users have the choice of using the style they prefer. On a stand-alone VAXstation 3100, running the procedure takes approximately 4 hours. You need 4466 blocks of free disk space to run the PUB procedure. Note Users can be logged into their ALL-IN-1 accounts while you run this command procedure. You can also use ALL-IN-1 from the same account that you run this procedure from. To do so, access ALL-IN-1 using the command ALLIN1/REENTER. If you have additional form libraries that you want to convert to windows, see the ALL-IN-1 Services for DECwindows Customization Guide. To see how to choose a style and work with it, see the ALL-IN-1 Services for DECwindows User's Guide. To run the PUB procedure, do the following: 1 Make sure you have run the command procedure that is explained in Section 3.7. 2 Log into an account that has the following: _ Access to an ALL-IN-1 account that has the APP privilege _ User quotas listed in Table 3-1 _ The form library MICALIB - see Section 3.8 for instructions on how to add the form library to the account's user profile. _ The VMS privileges SYSPRV, PRMGBL, and SYSGBL 3 Set your default directory to MICA$LIB_SHARE. 4 To convert the form libraries to windows, enter one of the following commands at the DCL prompt: _ If you have an ALL-IN-1 password, enter the following: @MICA$PUB_LIB "ALL-IN-1_user_name password" language 3-14 Preparing ALL-IN-1 Services for Operation For ALL-IN-1_user_name substitute your user name. For password, substitute your password. For language, enter the language for the form libraries you are converting. This can be the same language as the language installed on your system. If you are working in a multiple language environment, it can be a different language. _ If you do not have an ALL-IN-1 password, enter the following: @MICA$PUB_LIB ALL-IN-1_user_name language For ALL-IN-1_user_name, substitute your user name. For language, enter the language for the form libraries you are converting. This can be the same language as the language installed on your system. If you are working in a multiple language environment, it can be a different language. This submits 4 jobs to the batch queue that you specified during the installation procedure. You receive notification that the batch job has finished when the final job completes. Remember that the whole procedure runs for approximately 4 hours (depending on your system). The batch job starts a subprocess that does the work. Note If the PUB fails and the subprocess does not show any activity, check the system's page files. You may need to increase them. See your system manager if you do not know how to do this. This procedure also creates several log files. See Appendix E for their names, purpose, and locations. 3.10 Verifying the Installation This section explains how to do the following: _ Run the IVP (Installation Verification Procedure)-do this to verify that VMSINSTAL placed all files in the correct directories. _ Verify that ALL-IN-1 Services is ready for operation- do this to ensure that you can access and use ALL-IN-1 Services. Preparing ALL-IN-1 Services for Operation 3-15 3.10.1 Running the IVP The IVP (Installation Verification Procedure) ensures that all files are in the correct directories. To run the IVP, go through the following steps: Note Make sure you have already run the ALL-IN-1 Services startup file, as explained in Section 3.5. The IVP fails if you have not completed this task. 1 Access the system account. 2 Set your default disk and directory to SYS$TEST by entering the following at the DCL prompt: SET DEF SYS$TEST 3 Start the IVP by entering the following at the DCL prompt: @MICA$IVP.COM installation_type device:[directory] language Enter the following for the variable parameters: _ For installation_type, enter one of the following: _ F - if you installed a full kit _ A - if you installed an additional language _ For device:[directory], enter the device and directory for the ALL-IN-1 Services files. Make sure you enter the same location that you entered when you installed ALL-IN-1 Services. _ For language, enter the language that you installed. Make sure you enter the same language that you entered when you installed ALL-IN-1 Services. You must enter a value for each parameter. If you do not, the IVP prompts you for the values. As the IVP begins, you see the following message: Beginning the ALL-IN-1 Services for DECwindows V1.0 Installation Verification Procedure When the IVP finishes, it places a log file called MICA$IVP.LOG in SYS$TEST. This file contains any errors. If the IVP completes successfully, you see the following message: 3-16 Preparing ALL-IN-1 Services for Operation ALL-IN-1 Services for DECwindows V1.0 Installation Verification Procedure Completed Successfully 3.10.2 Verifying That ALL-IN-1 Services Is Ready to Use To verify that you have installed ALL-IN-1 Services correctly and that it is ready to use, go through the following steps: 1 Make sure you are on a workstation and have logged into DECwindows. 2 If you are accessing ALL-IN-1 Services from a remote node, add the node that ALL-IN-1 Services is installed on to your workstation security, as follows: a From the Customize pull-down menu on the Session Manager window, choose the Security... option. b In the Node field, enter the node on which ALL-IN-1 Services is installed. c In the Username field, enter your user name. d Click on the OK button. 3 Open a DECterm window. 4 If ALL-IN-1 Services is installed on a different node than your workstation node, set host to the node where it is installed. 5 If ALL-IN-1 Services is installed on a different node and you are displaying it on your node, enter the following at the DCL prompt: SET DISPLAY/CREATE/NODE=node_name For node_name, substitute your node name. 6 At the DCL prompt, enter the following: ALLIN1/INTERFACE=DECWINDOWS ALL-IN-1 Services appears. 7 Make sure the following items appear: _ The information window-appears in the upper left corner of your workstation and contains your name, title, and date. _ Your main menu-contains the same options you see when you access ALL-IN-1, but is a window with push-button options. Preparing ALL-IN-1 Services for Operation 3-17 _ In the Icon Box, the Document, Mail, and Calendar Viewers-at this point, clicking on any of these icons expands it to an empty window. _ In the Icon box, the ALL-IN-1 Services icon-clicking on this icon shrinks and expands the ALL-IN-1 Services application to and from the icon. 8 Click on the WP button, and make sure the Word and Document Processing window opens. 9 To make sure that you can access DECwrite (if it is installed on your system), click on the C button. When the Creating New Document form appears, answer Y to the Use DECwrite prompt. DECwrite's New Attributes form appears. Note Note that if you have the APP privilege in your user profile in ALL-IN-1 and if forms that you converted are currently in the development area, you will see these forms in FMS format when you access ALL-IN-1 Services. To see the windowed format, either remove the APP privilege from your user profile or move the forms back to the site area if they are ready to be moved. See the ALL-IN-1 Services for DECwindows User's Guide for more information on accessing and using ALL-IN-1 Services. 3-18 Preparing ALL-IN-1 Services for Operation A ________________________________________________________________ Sample Installation of ALL-IN-1 Services This appendix contains a sample installation of the full kit for ALL-IN-1 Services. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. $ SET DEF SYS$UPDATE $ @VMSINSTAL ASD010 SYS$:[PRODUCTS.ASD] VAX/VMS Software Product Installation Procedure V5.3-1 It is 1-NOV-1990 at 10:30. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: MRLOGGER DECW$WM_1 DECW$TE_1 _TWA6: * Do you want to continue anyway [NO]? Y * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: ASD V1.0 Beginning installation of ASD V1.0 at 10:33 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. Checking VMS Operating System version ... Sample Installation of ALL-IN-1 Services A-1 Checking prerequisite software ... Checking DECwindows Checking DECwindows UIL Compiler Checking ALL-IN-1 Checking CDA Converter Library Checking RUNOFF Determining ALL-IN-1 information required for this installation ... * Enter the language code for this kit [ENGLISH]: ENGLISH Restoring the LANGUAGE Code Saveset(s) ... Restoring saveset ASDLENGLISH010.B ... %VMSINSTAL-I-RESTORE, Restoring product save set B ... Saveset ASDLENGLISH010.B restored Checking LMF for product registration ... ALL-IN-1 Services for DECwindows Installation Options ===================================================== 1) Install ALL-IN-1 Services for DECwindows 2) Install an Additional Language of ALL-IN-1 Services for DECwindows * Enter an option listed above [1]: 1 * Are you satisfied with the backup of your ALL-IN-1 files [YES]? * Where do you want to load the files [DKA200:[ASD]]: DEV$:[ASD] * What UIC should own the files for ALL-IN-1 Services [ [100,10] ]: A batch queue with the following characteristics is required by this software. JOB_LIMIT = 1 WSEXTENT = 5000 WSQUOTA = 3000 This queue is used by the ALL-IN-1 Services for DECwindows software any time the PUB option is selected to run in batch. The logical name MICA$BATCH will be used by the software to reference this queue. * Enter the queue name for the MICA$BATCH queue [MICA$BATCH_QUEUE]: * Queue MICA$BATCH_QUEUE does not exist. Do you want to create it [YES]? * Do you want to purge files replaced by this installation [YES]? A-2 Sample Installation of ALL-IN-1 Services All questions regarding the installation have now been asked. The installation will continue from 30 minutes to 1 hour. Checking Disk Space Requirements ... Checking for pre-existing files modified during this installation ... Checking system parameters ... Performing ALL-IN-1 Customization Management Conflict Checking ... ALL-IN-1 will be invoked several times during this phase of the installation to determine if any Customization Management Conflicts will occur during the installation. SYSTEM finished using ALL-IN-1 at 01-Nov-1990 10:36 SYSTEM finished using ALL-IN-1 at 01-Nov-1990 10:37 SYSTEM finished using ALL-IN-1 at 01-Nov-1990 10:38 SYSTEM finished using ALL-IN-1 at 01-Nov-1990 10:38 SYSTEM finished using ALL-IN-1 at 01-Nov-1990 10:38 SYSTEM finished using ALL-IN-1 at 01-Nov-1990 10:38 Restoring the BASE Code Saveset(s) ... Restoring saveset ASD010.B ... %VMSINSTAL-I-RESTORE, Restoring product save set B ... Saveset ASD010.B restored Restoring the LANGUAGE Code Saveset(s) ... Restoring saveset ASDLENGLISH010.C ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... Saveset ASDLENGLISH010.C restored Restoring saveset ASDLENGLISH010.D ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... Saveset ASDLENGLISH010.D restored Processing Directories ... Processing OAGBL ... Processing OASDF ... Updating OALIBR.OLB ... Processing ALL-IN-1 Sitelink Command File ... Initializing ALL-IN-1 Services Batch Queue Updating ALL-IN-1 Help Files ... Sample Installation of ALL-IN-1 Services A-3 Processing Startup Files ... The ALL-IN-1 Services for DECwindows startup files will be placed in SYS$STARTUP. You will need to modify the ALL-IN-1 SITE startup file, OA$SITE_BUILD_SHARE:A1V24_SITE_START.COM, to execute the ALL-IN-1 Services for DECwindows startup command procedure. Refer to the Post-Installation Chapter in the Installation Guide for a description of the modifications required to start ALL-IN-1 Services for DECwindows at system startup. Processing FileView Files ... Preparing to process files in 2 table files Preparing to move files listed in table file 1 Preparing to move files listed in table file 2 %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Setting File Protections ... Setting ACL's ... Purging Files Moved ... An Installation Verification Procedure for this product has been placed in SYS$TEST. Please be sure to execute this IVP as instructed in the post installation chapter of the Installation Guide. Installation of ASD V1.0 completed at 10:50 VMSINSTAL procedure done at 10:51 $ A-4 Sample Installation of ALL-IN-1 Services B ________________________________________________________________ Sample Installation of an Additional Language of ALL-IN-1 Services This appendix contains a sample installation of an additional language for ALL-IN-1 Services. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. $ SET DEF SYS$UPDATE $ @VMSINSTAL ASD010 SYS$:[PRODUCTS.ASD] VAX/VMS Software Product Installation Procedure V5.3-1 It is 1-NOV-1990 at 12:09. Enter a question mark (?) at any time for help. %VMSINSTAL-W-ACTIVE, The following processes are still active: MRLOGGER DECW$WM_1 DECW$TE_1 * Do you want to continue anyway [NO]? Y * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: ASD V1.0 Beginning installation of ASD V1.0 at 12:10 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. Checking VMS Operating System version ... Sample Installation of an Additional Language of ALL-IN-1 Services B-1 Checking prerequisite software ... Checking DECwindows Checking DECwindows UIL Compiler Checking ALL-IN-1 Checking CDA Converter Library Checking RUNOFF Determining ALL-IN-1 information required for this installation ... * Enter the language code for this kit [ENGLISH]: GERMAN Restoring the LANGUAGE Code Saveset(s) ... Restoring saveset ASDLGERMAN010.B ... %VMSINSTAL-I-RESTORE, Restoring product save set B ... Saveset ASDLGERMAN010.B restored Checking LMF for product registration ... ALL-IN-1 Services for DECwindows Installation Options ===================================================== 1) Install ALL-IN-1 Services for DECwindows 2) Install an Additional Language of ALL-IN-1 Services for DECwindows * Enter an option listed above [1]: 2 * Are you satisfied with the backup of your ALL-IN-1 files [YES]? * Where do you want to load the files [DKA300:[ASD]]: * What UIC should own the files for ALL-IN-1 Services [ [100,10] ]: * Do you want to purge files replaced by this installation [YES]? All questions regarding the installation have now been asked. The installation will continue from 30 minutes to 1 hour. Checking Disk Space Requirements ... Checking for pre-existing files modified during this installation ... Checking system parameters ... Performing ALL-IN-1 Customization Management Conflict Checking ... ALL-IN-1 will be invoked several times during this phase of the installation to determine if any Customization Management Conflicts will occur during the installation. SYSTEM finished using ALL-IN-1 at 01-Nov-1990 12:12 SYSTEM finished using ALL-IN-1 at 01-Nov-1990 12:12 B-2 Sample Installation of an Additional Language of ALL-IN-1 Services SYSTEM finished using ALL-IN-1 at 01-Nov-1990 12:13 Restoring the LANGUAGE Code Saveset(s) ... Restoring saveset ASDLGERMAN010.C ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... Saveset ASDLGERMAN010.C restored Restoring saveset ASDLGERMAN010.D ... %VMSINSTAL-I-RESTORE, Restoring product save set D ... Saveset ASDLGERMAN010.D restored Processing Directories ... Updating ALL-IN-1 Help Files ... Processing Startup Files ... Processing FileView Files ... Preparing to process files in 1 table files Preparing to move files listed in table file 1 %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Setting File Protections ... Setting ACL's ... Purging Files Moved ... An Installation Verification Procedure for this product has been placed in SYS$TEST. Please be sure to execute this IVP as instructed in the post installation chapter of the Installation Guide. Installation of ASD V1.0 completed at 12:17 VMSINSTAL procedure done at 12:18 $ Sample Installation of an Additional Language of ALL-IN-1 Services B-3 C ________________________________________________________________ Forms Provided with ALL-IN-1 Services The following lists the forms in the MICA.FLB form library: EM$INDEX$MENU EM$INDEX$MENU1 EM$INDEX$MENU2 EM$INDEX$MENU3 EM$INDEX$MENU4 EM$INDEX$OPTIONS EMC MICA$DOCDS2 MICA$DOCDSC MICA$MAGIC MICA$PROFIL_ARG MICA$TMEV_O5 MICA$TMSTG_O4 MICA$TMS_PAGE4 MICA$TMXT_PAGE2 MICA_MESSAGES MORE$SCROLL$KEYS$INDEX OLD_PUB PUB PUB_ARG PUB_BATCH_ARG PUB_ENTRY PUB_STYLE_ARG PUB_STYLE_MENU TMEG TMEP TMET TMEVINDEX TMS Forms Provided with ALL-IN-1 Services C-1 TMSEV_OPTIONS1 TMSEV_OPTIONS2 TMSEV_OPTIONS3 TMSEV_OPTIONS4 TMSTG_OPTIONS1 TMSTG_OPTIONS2 TMSTG_OPTIONS3 TMS_MORE TMS_MORE_PAGE2 TMS_MORE_PAGE3 TMTG TMTINDEX TMXT TMXT_MORE US WP$INDEX WP C-2 Forms Provided with ALL-IN-1 Services D ________________________________________________________________ Files and Logicals Installed on Your System The ALL-IN-1 Services installation procedure installs or moves files and adds or modifies logicals. This appendix lists these files and logicals. D.1 Logicals Added to the System Table MICA$BLP_SHARE device:[directory.BLP_SHARE] MICA$BUILD_SHARE device:[directory.SOURCES_SHARE] MICA$DATA_SHARE device:[directory.DATA_SHARE] MICA$DO_SHARE device:[directory.DO_SHARE] MICA$LIB_SHARE device:[directory.LIB_SHARE] MICA$SCP_SHARE device:[directory.SCP_SHARE] MICA$SITE_BLP_SHARE device:[directory.SITE.BLP_ SHARE] MICA$SITE_BUILD_SHARE device:[directory.SITE.SOURCES_ SHARE] MICA$SITE_DATA_SHARE device:[directory.SITE.DATA_ SHARE] MICA$SITE_DEV_SHARE device:[directory.SITE.DEV_ SHARE] MICA$SITE_DO_SHARE device:[directory.SITE.DO_SHARE] MICA$SITE_LIB_SHARE device:[directory.SITE.LIB_ SHARE] MICA$SITE_SCP_SHARE device:[directory.SITE.SCP_ SHARE] MICA$DUMP_AREA device:[directory.DUMP_AREA] Files and Logicals Installed on Your System D-1 MICA$BLP_language device:[directory.BLP_language] MICA$DATA_language device:[directory.DATA_language] MICA$DO_language device:[directory.DO_language] MICA$LIB_language device:[directory.LIB_language] MICA$SCP_language device:[directory.SCP_language] MICA$SITE_BLP_language device:[directory.SITE.BLP_ language] MICA$SITE_DATA_language device:[directory.SITE.DATA_ language] MICA$SITE_DEV_language device:[directory.SITE.DEV_ language] MICA$SITE_DO_language device:[directory.SITE.DO_ language] MICA$SITE_LIB_language device:[directory.SITE.LIB_ language] MICA$SITE_SCP_language device:[directory.SITE.SCP_ language] MICA$BLP_LLV device:[directory.BLP_language] MICA$DATA_LLV device:[directory.DATA_language] MICA$DO_LLV device:[directory.DO_language] MICA$LIB_LLV device:[directory.LIB_language] MICA$SCP_LLV device:[directory.SCP_language] MICA$SITE_BLP_LLV device:[directory.SITE.BLP_ language] MICA$SITE_BUILD_LLV device:[directory.SITE.SOURCES_ language] MICA$SITE_DATA_LLV device:[directory.SITE.DATA_ language] MICA$SITE_DEV_LLV device:[directory.SITE.DEV_ language] MICA$SITE_DO_LLV device:[directory.SITE.DO_ language] MICA$SITE_LIB_LLV device:[directory.SITE.LIB_ language] MICA$SITE_SCP_LLV device:[directory.SITE.SCP_ language] MICA$BATCH queue_name MICA$UI_IMAGE MICA$LIB:MICA$UI_DRIVER.EXE MICALIB MICA$LIB:MICA.FLB SMICALIB MICA$LIB:SITEMICA.FLB OA$SITE_DEV_MICA_language device:[directory.SITE.DEV_ language] OA$SITE_DEV_MICA_SHARE device:[directory.SITE.DEV_ SHARE] D-2 Files and Logicals Installed on Your System Logical Search Lists MICA$BLP MICA$SITE_BLP_LLV, MICA$SITE_BLP_SHARE, MICA$BLP_LLV, MICA$BLP_SHARE MICA$BUILD MICA$SITE_BUILD_LLV, MICA$SITE_BUILD_SHARE, MICA$BUILD_SHARE MICA$DATA MICA$SITE_DATA_LLV, MICA$SITE_DATA_SHARE, MICA$DATA_LLV, MICA$DATA_SHARE MICA$DO MICA$SITE_DO_LLV, MICA$SITE_DO_SHARE, MICA$DO_LLV, MICA$DO_SHARE MICA$LIB MICA$SITE_LIB_LLV, MICA$SITE_LIB_SHARE, MICA$LIB_LLV, MICA$LIB_SHARE MICA$SCP MICA$SITE_SCP_LLV, MICA$SITE_SCP_SHARE, MICA$SCP_LLV, MICA$SCP_SHARE D.2 ALL-IN-1 Logicals Added to Each Language Table MICA$BLP_LLV device:[directory.BLP_language] MICA$DATA_LLV device:[directory.DATA_language] MICA$DO_LLV device:[directory.DO_language] MICA$LIB_LLV device:[directory.LIB_language] MICA$SCP_LLV device:[directory.SCP_language] MICA$SITE_BLP_LLV device:[directory.SITE.BLP_language] MICA$SITE_BUILD_LLV device:[directory.SITE.SOURCES_ language] MICA$SITE_DATA_LLV device:[directory.SITE.DATA_language] MICA$SITE_DEV_LLV device:[directory.SITE.DEV_language] MICA$SITE_DO_LLV device:[directory.SITE.DO_language] MICA$SITE_LIB_LLV device:[directory.SITE.LIB_language] MICA$SITE_SCP_LLV device:[directory.SITE.SCP_language] Files and Logicals Installed on Your System D-3 D.3 Files Placed on the System Disk SYS$COMMON:[SYS$STARTUP]MICA$INSTALLED_LANGUAGES.DAT SYS$COMMON:[SYS$STARTUP]MICA$STARTUP.COM SYS$COMMON:[SYSEXE]MICA$START.EXE SYS$COMMON:[SYSHLP]MICA010.RELEASE_NOTES SYS$COMMON:[VUE$LIBRARY.USER]MICA$ALL-IN-1$VUE.COM SYS$COMMON:[VUE$LIBRARY.USER]MICA$PROFILE.VUE$DAT SYS$COMMON:[SYSTEST]MICA$IVP.COM SYS$COMMON:[SYSTEST]MICA$IVP.LOG D.4 Files Placed in the ALL-IN-1 Directory OA$BUILD_SHARE:MICA$OA.OLB OA$SITE_LIB_SHARE:CM_POST_COMPILE_A1TXL.COM OA$SITE_LIB_SHARE:CM_POST_COMPILE_CMTXL.COM OA$SITE_LIB_SHARE:CM_PRE_COMPILE_A1TXL.COM OA$SITE_LIB_SHARE:CM_PRE_COMPILE_CMTXL.COM D.5 ALL-IN-1 Files Modified OA$BUILD_SHARE:OALIBR.OLB OA$BUILD_SHARE:SITELINK24.COM OA$DATA_SHARE:CM_FORM_LIBS.DAT OA$DATA_SHARE:CM_LANGUAGES.DAT OA$DATA_SHARE:CM_SDC_ELEMENTS.DAT OA$DATA_SHARE:CM_SITEHIST.DAT OA$DATA_SHARE:CM_SITELOG.DAT OA$SITE_BUILD_SHARE:OAGBL.BLI OA$SITE_BUILD_SHARE:OAGBL.OBJ OA$SITE_BUILD_SHARE:OASDF.BLI OA$SITE_BUILD_SHARE:OASDF.OBJ OA$SITE_LIB_LLV:HLPSOURCE.HLB OA$SITE_LIB_LLV:OAHELP.HLB OA$SITE_LIB_SHARE:COMTP.COM OA$SITE_LIB_SHARE:CM_FORMCREAT.COM OA$SITE_LIB_SHARE:CM_FORMUPDAT.COM OA$SITE_LIB_SHARE:CM_CDS.SCP OA$SITE_LIB_SHARE:CM_CTX.SCP D-4 Files and Logicals Installed on Your System OA$LIB_SHARE:CM_MOVE_TO_LIVE.SCP D.6 Files Placed in the ALL-IN-1 Services Directory device:[directory.BLP_SHARE]MICA$ERROR.BLP device:[directory.DO_SHARE]MICA$DECWRITE.SCP device:[directory.DO_SHARE]MICA$DECWRITE_EXIT.SCP device:[directory.DO_SHARE]MICA$DOCCREATE.SCP device:[directory.DO_SHARE]MICA$VIEWER_SETERR.SCP device:[directory.DO_SHARE]MICA$VIEWER_START.SCP device:[directory.DO_SHARE]MICA$VIEWER_VIEW_EM.SCP device:[directory.DO_SHARE]MICA$VIEWER_VIEW_FC.SCP device:[directory.DO_SHARE]MICA$VIEWER_VIEW_TM.SCP device:[directory.DO_SHARE]MICA$VIEWER_VIEW_UNREAD.SCP device:[directory.DO_SHARE]MICA$VIEWER_VIEW_VMS.SCP device:[directory.DO_SHARE]MICA$VIEWER_VIEW_WP.SCP device:[directory.LIB_SHARE]MICA$A1.CLD device:[directory.LIB_SHARE]MICA$CLOSE.EXE device:[directory.LIB_SHARE]MICA$DB$DEFINITIONS.COM device:[directory.LIB_SHARE]MICA$DB.EXE device:[directory.LIB_SHARE]MICA$DECTERM.EXE device:[directory.LIB_SHARE]MICA$DIALOGUE_ENV.TXT device:[directory.LIB_SHARE]MICA$DIALOGUE_START.TXT device:[directory.LIB_SHARE]MICA$DWDB.EXE device:[directory.LIB_SHARE]MICA$FORM_REPLACE.COM device:[directory.LIB_SHARE]MICA$FORM_TEMPLATE.UIL device:[directory.LIB_SHARE]MICA$LIB_TEMPLATE.UIL device:[directory.LIB_SHARE]MICA$OAINI.SCP device:[directory.LIB_SHARE]MICA$OPEN.EXE device:[directory.LIB_SHARE]MICA$POST_COMPILE_A1TXL.COM device:[directory.LIB_SHARE]MICA$POST_COMPILE_CMTXL.COM device:[directory.LIB_SHARE]MICA$PRE_COMPILE_A1TXL.COM device:[directory.LIB_SHARE]MICA$PRE_COMPILE_CMTXL.COM device:[directory.LIB_SHARE]MICA$PUB.COM device:[directory.LIB_SHARE]MICA$PUB.MICA$PUB_OPTION device:[directory.LIB_SHARE]MICA$PUB.SCP device:[directory.LIB_SHARE]MICA$PUBB.SCP device:[directory.LIB_SHARE]MICA$PUBC.SCP device:[directory.LIB_SHARE]MICA$PUB_AUTHORIZE.SCP device:[directory.LIB_SHARE]MICA$PUB_CLEANUP.COM device:[directory.LIB_SHARE]MICA$PUB_LIB.COM device:[directory.LIB_SHARE]MICA$PUB_SETUP.SCP device:[directory.LIB_SHARE]MICA$PULLDOWN.MICA$PUB_OPTION Files and Logicals Installed on Your System D-5 device:[directory.LIB_SHARE]MICA$PULLDOWN_LIB.UIL device:[directory.LIB_SHARE]MICA$PULLDOWN_TEMPLATE.UIL device:[directory.LIB_SHARE]MICA$STARTDB.COM device:[directory.LIB_SHARE]MICA$UI_DRIVER.EXE device:[directory.LIB_SHARE]MICA$VIEWER.EXE device:[directory.LIB_SHARE]MICA$VIEWER_MESSAGES.EXE device:[directory.LIB_SHARE]MICA$VIEWER_START.COM device:[directory.SOURCES_SHARE]CM_CDS.SCP device:[directory.SOURCES_SHARE]CM_CTX.SCP device:[directory.SOURCES_SHARE]CM_MOVE_TO_LIVE.SCP device:[directory.SOURCES_SHARE]CM_POST_COMPILE_A1TXL.COM device:[directory.SOURCES_SHARE]CM_POST_COMPILE_CMTXL.COM device:[directory.SOURCES_SHARE]CM_PRE_COMPILE_A1TXL.COM device:[directory.SOURCES_SHARE]CM_PRE_COMPILE_CMTXL.COM device:[directory.SOURCES_SHARE]COMTP.COM device:[directory.SOURCES_SHARE]MICA$DCLTABLES.COM device:[directory.SOURCES_SHARE]MICA$FORMAT_EDIT.COM device:[directory.SOURCES_SHARE]MICA$POSTINSTALL_DRV.COM device:[directory.SOURCES_SHARE]MICA$UPDATE_OAINI.COM device:[directory.SOURCES_SHARE]CM_FORMCREAT.COM device:[directory.SOURCES_SHARE]CM_FORMUPDAT.COM device:[directory.SOURCES_SHARE]MICA$A1RELINK.COM device:[directory.SOURCES_SHARE]MICA$COMPILE_FLCS.COM device:[directory.SOURCES_SHARE]MICA$COMPILE_TXLS.COM device:[directory.DATA_language]MICA$PUB_STYLES.DAT device:[directory.DATA_language]MICA$VIEWER_DEFAULTS.DAT device:[directory.DATA_language]MICA_MESSAGES.DAT device:[directory.LIB_language]A1_SERV.HLB device:[directory.LIB_language]MICA$DECTERM.UID device:[directory.LIB_language]MICA$DECTERM_POPUP.UID device:[directory.LIB_language]MICA$DECTERM_POPUP.UIL device:[directory.LIB_language]MICA$PUB_RULES.MICA$PUB_ OPTION device:[directory.LIB_language]MICA$SYS_RULES.MICA$PUB_ OPTION device:[directory.LIB_language]MICA$TRANSLATE.UIL device:[directory.LIB_language]MICA$UI_DRIVER.UID device:[directory.LIB_language]MICA$VIEWER.UID device:[directory.LIB_language]MICA.FLB device:[directory.LIB_language]MICA.UID_PULL device:[directory.LIB_language]MICA.UID_PUSH device:[directory.LIB_language]PUB_STYLE_PRINT.BLP device:[directory.SITE.DEV_language]DEVELOP.FLB D-6 Files and Logicals Installed on Your System device:[directory.SITE.LIB_language]SITEMICA.FLB ALL-IN-1 Services Images Installed on the System The following images are installed on the system and place in the ALL-IN-1 Services directory: MICA$LIB_SHARE:MICA$CLOSE.EXE MICA$LIB_SHARE:MICA$DB.EXE MICA$LIB_SHARE:MICA$DECTERM.EXE MICA$LIB_SHARE:MICA$DWDB.EXE MICA$LIB_SHARE:MICA$OPEN.EXE MICA$LIB_SHARE:MICA$UI_DRIVER.EXE MICA$LIB_SHARE:MICA$VIEWER.EXE MICA$LIB_SHARE:MICA$VIEWER_MESSAGES.EXE SYS$SYSTEM:MICA$START.EXE Files and Logicals Installed on Your System D-7 E ________________________________________________________________ PUB Log Files The PUB creates the following log files and places all but MICA$PUB.LOG in your ALL-IN-1 directory. It places MICA$PUB.LOG in your SYS$LOGIN directory. Note In each of the following log files, library represents the form library you ran through the PUB. _ MICA$library_OUT.LOG-the PUB redirects SYS$OUTPUT to this file. It contains any error messages. It also has informational messages about temporary files that the PUB has deleted during the cleanup phase. _ MICA$library_PUB.LOG-lists each form that the PUB processed. It also contains information about forms that the PUB did not convert to windows. _ MICA$library_UID.LOG-contains all of the output that the UIL compiler created as it processed the library.uil file. Also contains UIL errors, if there are any. _ MICA$PUB.LOG-is the log of the batch job that the PUB submitted. It includes the names of the files passed to the PUB, and the informational and error messages that occurred while the PUB processing took place. The following is an example of the information you see in the MICA$PUB.LOG file. Note that it displays the following error message: Error occurred while form MICA$DOCDS2 was current PUB Log Files E-1 If your log file contains similar messages, you can ignore them. They do not cause any problems. $ ! MICA$PUB.COM V1.0-621 $! Write sys$output "Init:'mica_init'" $ set ver $ if "" .nes. "" then $ p = F$setprv("SYSPRV") $ IF .NOT. $STATUS THEN GOTO PRIV_EXIT $ ! Run the PUB in Batch $ DEFINE/NOLOG PUB$LIBRARY MICA$LIB:MICA.FLB $ DEFINE/NOLOG PUB$STYLE PULL-DOWN $ ! P4 = 'P4 $ DEFINE/NOLOG PUB$DOLIBRARY Y $ DEFINE/NOLOG PUB$DOFORM Y $ DEFINE/NOLOG PUB$DOUIL Y $ DEFINE/NOLOG PUB$DODELETE Y $ US = P5 $ USER = "" $ PASS = "" $ LANG = "" $ IF P5 .EQS. "" THEN GOTO SKIP_USER $ US = F$EDIT(F$EDIT(P5,"TRIM"),"COMPRESS") $ SP = F$LOCATE(" ",US) $ IF SP .GE. F$LENGTH(US) THEN GOTO SKIP_PASS $ SKIP_PASS: $ USER = "/USER=MANAGER" $ SKIP_USER: $ IF P1 .NES. "" $ ENDIF $ ALLIN1/USER=MANAGER/REENTER/SCRIPT=MICA$lib:mica$pubc E-2 PUB Log Files FORM Main Menu Working . . . EMC EMC1 EMC2 FC1 Error occurred while form MICA$DOCDS2 was current MICA$TMXT_PAGE2 PUB PUB_STYLE_MENU TMMENU TMS TMS_MORE TMS_MORE_PAGE2 TMS_MORE_PAGE3 TMXT TMXT_MORE US WP WPCONT1 Precompiling DKB200:[MICA.LIB_ENGLISH]MICA.FLB . . . PUB LIB MICA.lis Mica$MICA.UIL MICA$LIB:MICA$PULLDOWN_LIB.UIL MICA$LIB:MICA$PULLDOWN.MICA$PUB_OPTION $ UIL/LIST=MICA$MICA_UID.LOG Mica$MICA.UIL/output=DKB200:[MICA.LIB_ENGLISH]- MICA.UID_PULL PUB processing complete. MANAGER finished using ALL-IN-1 at 15-Aug-1990 05:27pm $ EXIT PUB Log Files E-3 F ________________________________________________________________ Log of MICA$POSTINSTALL_DRV The following is a sample log of the procedure that is explained in Section 3.7: $ @MICA$BUILD_SHARE:MICA$POSTINSTALL_DRV 1 --------------------------------------------------------------------------- Executing MICA$POSTINSTALL_DRV.COM Interactively --------------------------------------------------------------------------- This command procedure is used to perform the following Post Installation Steps. 1 Link, Move, and Install the ALL-IN-1 Main Image 2 Redefine the ALL-IN-1 Command 3 Edit OAINI.SCP 4 Recompile A1TXL 5 Add DECwrite to the Format Master 6 Precompile Form Libraries * Do you want to continue? (Y/N) [Y] --------------------------------------------------------------------------- Starting Step 1: LINK, MOVE, AND INSTALL THE ALL-IN-1 MAIN IMAGE --------------------------------------------------------------------------- This step will execute OA$BUILD_SHARE:A1LNKDRV.COM to relink the ALL_IN-1 Main image. After the link, the Main image will be copied from OA$BUILD_SHARE to OA$LIB_SHARE and installed. Relinking the Main image. Log of MICA$POSTINSTALL_DRV F-1 %A1 -I-SAVED_ANS_1, Default answers are being taken from saved answers file %A1 -I-SAVED_ANS_2, which was created on 1-NOV-1990 09:13:12.66 %A1 -I-DTRNOLINK, DATATRIEVE will not be linked with ALL-IN-1 %A1 -I-WPSLINK, The WPS-PLUS editor will be linked with ALL-IN-1 %A1 -I-ACMSNOLINK, ACMS will not be linked with ALL-IN-1 %A1 -I-MLLINK, ALL-IN-1 will be linked as a multi-language system %A1 -I-DATEFORMAT, Date format DD-MMM-YYYY and MM/DD/YY (1) has been selected %A1 -I-NODDS, DDS support will not be included in the link %DCL-I-SUPERSEDE, previous value of VMI$KWD has been superseded Linking the OA$LLVENGLISH.EXE Building shared image modules Shared image modules built Starting execution of DKA200:[ALLIN1.SOURCES]SITELINK24.COM;36 Linking the OA$MAIN image Linking the Background Formatter Linking the TM Server Linking the OA$SUBMIT image Linking the MAILCOUNT image Remember to move the OA$LLVlanguage image to SYS$SHARE and re-install the image prior to attempting to run ALL-IN-1. Remember to move the OA$MAIN image to OA$LIB_SHARE and re-install the image prior to attempting to run ALL-IN-1. The ALL-IN-1 relink has completed. You can have this procedure move and install the new Main image or you can wait and perform this function after the procedure has completed. * Do you want to move and install the new Main image? (Y/N) [Y]: Moving the relinked Main image to OA$LIB_SHARE. Installing the relinked Main image. Step 1 Completed * Do you want to continue with the next step? (Y/N) [Y] --------------------------------------------------------------------------- Starting Step 2: REDEFINE THE ALL-IN-1 COMMAND --------------------------------------------------------------------------- This step will modify the system DCL table. This modification will allow ALL-IN-1 Services for DECwindows to be invoked when the $ALLIN1 command is entered. F-2 Log of MICA$POSTINSTALL_DRV ********************************************************************* * N O T E * ********************************************************************* * * * If you upgrade to a later version of ALL-IN-1 and reinstall the * * ALL-IN-1 command, or install other software that redefines the * * command, you lose the ALL-IN-1 Services for DECwindows command. * * In these cases, redefine the command again by entering the * * the following at DCL prompt: * * * * $ SET PROC/PRIV=(SYSPRV,CMKRNL) * * $ @MICA$BUILD_SHARE:MICA$DCLTABLES.COM * * * ********************************************************************* Modifing SYS$COMMON:[SYSLIB]DCLTABLES.EXE. Setting ownership and protections. Installing new version of DCLTABLES.EXE. Step 2 Completed * Do you want to continue with the next step? (Y/N) [Y] --------------------------------------------------------------------------- Starting Step 3: EDIT OAINI.SCP --------------------------------------------------------------------------- This step will modify OA$LIB:OAINI.SCP to contain the line .FZ DO MICA$LIB:MICA$OAINI If this file doesn't previously exist on your system, it will be created and placed in OA$SITE_LIB_SHARE. ALL-IN-1 does not currently have an OAINI file. One will be created for you... Moving OAINI.SCP into the ALL-IN-1 area... Step 3 Completed * Do you want to continue with the next step? (Y/N) [Y] --------------------------------------------------------------------------- Starting Step 4: RECOMPILE A1TXL Text Library --------------------------------------------------------------------------- This step will compile and install the A1TXL Text Library. Removing A1 TXL... Compiling A1 TXL... Log of MICA$POSTINSTALL_DRV F-3 TXL> BLP AIBRIEF TXL> BLP MICA$ERROR TXL> BLP PRINTER_TYPESB TXL> BLP SA_PROFILEB . . . TXL> SCRIPT GENERAL_JS_ERROR TXL> SCRIPT CM_MEASURE TXL> SCRIPT EDITORAPP TXL> SCRIPT TMEDIT TXL> total bytes in elements = 267749 Installing A1 TXL... Step 4 Completed * Do you want to continue with the next step? (Y/N) [Y] --------------------------------------------------------------------------- Starting Step 5: ADD DECwrite TO THE FORMAT MASTER --------------------------------------------------------------------------- This step will add a DECwrite command to the DDIF and DOTS records in the Format Master. DDIF FORMAT updated with MICA$DECwrite edit DOTS FORMAT updated with MICA$DECwrite edit Step 5 Completed * Do you want to continue with the next step? (Y/N) [Y] --------------------------------------------------------------------------- Starting Step 6: PRECOMPILING FORM LIBRARIES --------------------------------------------------------------------------- This step will precompile and install form libraries. <<< PROCESSING MICA (Language: ENGLISH) >>> Removing MICA Compiling MICA Installing MICA <<< PROCESSING MEMRES (Language: ENGLISH) >>> Removing MEMRES Compiling MEMRES Installing MEMRES F-4 Log of MICA$POSTINSTALL_DRV <<< PROCESSING SITEMEMRES (Language: ENGLISH) >>> Removing SITEMEMRES Compiling SITEMEMRES Installing SITEMEMRES Step 6 Completed --------------------------------------------------------------------------- MICA$POSTINSTALL_DRV.COM PROCEDURE EXITING --------------------------------------------------------------------------- 6 out of the 6 Steps processed completed successfully. $ Log of MICA$POSTINSTALL_DRV F-5 ___________________________________________________________ Index A Converting, menus to Accessing ALL-IN-1 Services windows, 3-13 to 3-15 , 3-17 to 3-18 Customizations, resolving ALL-IN-1 conflicts, 1-6, 3-10 to logicals, 1-8 3-12 relinking, 3-12 D ALLIN1/INTERFACE=DECWINDOWS DECwrite , 3-17 installing, 1-3 ALL-IN-1 Services optional software, 1-3 starting, 3-17 to 3-18 Disk space, 1-4 to 1-5 B F Backing up disks, 1-9 Form libraries Batch, monitoring the job, adding, 3-13 3-15 precompiling, 3-12 C H CDA images, installing, 3-2 Hardware, required, 1-2 Conflicts, handling, 1-6 Index-1 I MICA$IVP.COM, 3-16 Images, starting up in a MICA$library_OUT.LOG, E-1 VAXcluster, 3-2 MICA$library_PUB.LOG, E-1 Installing MICA$library_UID.LOG, E-1 additional language, 1-3, MICA$POSTINSTALL_DRV, 3-12 2-1 to 2-7 to 3-13 CDA images, 3-2 log, F-1 full installation, 2-1 MICA$PUB.LOG, E-1 to 2-7 MICA$PUB_LIB, 3-13 to 3-15 full kit, 1-3 MICALIB, 3-13 in a VAXcluster, 1-6 N on a single machine, 1-6 Node names, for VAXclusters optional software, 1-3 , 3-2 required disk space, 1-4 to 1-5 O required hardware, 1-2 required software, 1-2, OA$MAIN.EXE, 3-9 1-3 OA$SITE_BUILD_SHARE, 3-10 time, 1-5 OAFORM, converting to IVP, running, 3-16 to 3-17 windows, 3-14 K OAFORM.FLB, 3-13 OAGBL.BLI, 3-10 Kit, contents, 1-4 OAGBL.OBJ, 3-10 OASDF.BLI, 3-10 L OASDF.OBJ, 3-10 Licenses, registering, 1-7 P LMF, registering your PAK, Parameters, SYSGEN, 3-6 to 1-7 3-9 Log files PUB MICA$POSTINSTALL_DRV, F-1 command procedure, 3-14 PUB, E-1 Platform User Interface Logicals, ALL-IN-1, 1-8 Builder, 3-14 M Pull-down menus, 3-14 MICA$BATCH_QUEUE, 2-5, 3-15 Push-button menus, 3-14 Index-2 Q SYSGEN parameters, 3-6 to Quotas 3-9 for user accounts, 3-4 U to 3-6 User account quotas, 3-4 JTQUOTA, 1-7 to 3-6 R User profiles, editing, Recompiling TXLs, 3-12 3-13 Release notes, displaying, V 2-3 VAXcluster Remote display, making node machine node names, 3-2 addresses known, 3-2 to starting up images, 3-2 3-4 ways of installing, 1-6 Running Verifying the installation, ALL-IN-1 Services startup 3-17 to 3-18 file, 3-9 PUB command procedure, 3-13 to 3-15 S Savesets in kit, 1-4 Setting display, making node addresses known, 3-2 to 3-4 SITEOAFORM, converting to windows, 3-14 SITEOAFORM.FLB, 3-13 Software optional, 1-3 order to install, 1-3 required, 1-2 Startup commands, 3-1 to 3-2, 3-9 SYS$STARTUP:MICA$STARTUP.COM , 3-2, 3-9 Index-3