DECmessageQ_________________________________________ Installation Guide for VMS Order Number: AA-PF43A-TE March 1991 This guide contains instructions for installing DECmessageQ on the VMS operating system. Revision/Update Information: This is a new document. Operating System and Version: VMS Version 5.3 Software Version: DECmessageQ Version 1.0 ________________________ March 1991 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 only be used or copied in accordance with the terms of such license. No responsibility is assumed for the use or reliability of software on equipment 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. This document was prepared using VAX DOCUMENT, Version 1.2 _________________________________________________________________ Preface This document explains how to install DECmessageQ Version 1.0 on a VAX computer running the VMS operating system. You will also need this document should you receive any maintenance updates or need to reinstall DECmessageQ for any other reason. DECmessageQ is installed using VMSINSTAL, a command procedure that executes the installation. The installation procedure is described step by step. The dialogue, for the most part, is self-explanatory. The system prompts you to enter information. Intended Audience The DECmessageQ Installation Guide for VMS is intended for the system manager or whoever installs and maintains DECmessageQ. Structure of This Document This guide is divided into the following chapters: o Chapter 1, Preparing to Install DECmessageQ , describes the installation procedure requirements and prerequisites for installing DECmessageQ. o Chapter 2, At the SYSGEN> prompt, enter the SHOW command to display the value of a system parameter. The values displayed should equal or exceed the value of each system parameter listed in Table 1-2. The following example displays the value for the GBLPAGFIL system parameter: SYSGEN> SHOW GBLPAGFIL After checking the parameters with the SHOW command, enter the EXIT command at the SYSGEN> prompt to return to DCL level. Preparing to Install DECmessageQ 1-3 Preparing to Install DECmessageQ 1.2 Installation Procedure Requirements 1.2.2.2 Calculating the Values for GBLPAGES and GBLSECTIONS To install and run DECmessageQ, you must have sufficient free global pages and global sections. You must first find out how many free global pages and sections you have on your system. Then use AUTOGEN if you need to increase the GLBPAGES and GBLSECTIONS system parameters. Another way to obtain SYSGEN parameters is to use the DCL WRITE command with the F$GETSYI lexical function to find the number of free global pages and global sections. The following example shows how to get this information at your terminal (the default for SYS$OUTPUT): $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLPAGES") 15848 $ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS") 24 If the values displayed by the system are greater than the values in Table 1-2, you do not need to increase the values for these parameters. If the value of free global pages or global sections is less than the value in Table 1-2, you must increase the system parameter setting. Section 1.2.2.3 describes the procedures for increasing these values using AUTOGEN. 1.2.2.3 Changing System Parameter Values with AUTOGEN Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually. To change system parameters with AUTOGEN, edit the following file: SYS$SYSTEM:MODPARAMS.DAT Use an editor to access the file. To change a parameter value listed in this file, delete the current value associated with that parameter and enter the new value. To modify incremental parameters such as GBLPAGES and GBLSECTS, use ADD_. The following example increases the global page setting by 2000: ADD_GBLPAGES = 2000 When you set the page file quota, do not use a value that exceeds the amount of page file space available on the system. After you make all your changes, exit from the editor and execute the AUTOGEN procedure to recalculate your system parameters. Enter the following command at the DCL prompt: $ @SYS$UPDATE:AUTOGEN GETDATA REBOOT 1-4 Preparing to Install DECmessageQ Preparing to Install DECmessageQ 1.2 Installation Procedure Requirements When you specify REBOOT, AUTOGEN performs an automatic system shutdown and then reboots the system. Any users logged in to the system are immediately disconnected during the shutdown. The automatic reboot puts the new parameter values into effect. The AUTOGEN Utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For more information about using AUTOGEN, see the VMS System Management Subkit. Preparing to Install DECmessageQ 1-5 Preparing to Install DECmessageQ 1.2 Installation Procedure Requirements 1.2.3 Process Account Quotas DECmessageQ requires that the BYTLM quota be set to 18,000 or higher. User account quotas are stored in the file SYSUAF.DAT. Use the VMS Authorize Utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM and then run AUTHORIZE: $ SET DEFAULT SYS$SYSTEM $ RUN AUTHORIZE UAF> At the UAF> prompt, enter the SHOW command with an account name to check a particular account. For example: UAF> SHOW SMITH To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account and then exits from the utility: UAF> MODIFY SMITH /BYTLM=18,000 UAF> EXIT After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in again for the new quotas to take effect. For more information on modifying account quotas, see the description of the Authorize Utility in the VMS System Management Subkit. 1.2.4 VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Whether you have set your default device and directory to SYS$UPDATE o Whether you are logged in to a privileged account o Whether you have adequate quotas for installation o Whether DECnet is running o Whether any users are logged in to the system If VMSINSTAL detects any problems during the installation, it notifies you and asks if you want to continue the installation. In some instances, you can enter YES to continue. To stop the installation process and correct the situation, enter NO or press Return. Then correct the problem and restart the installation. 1-6 Preparing to Install DECmessageQ Preparing to Install DECmessageQ 1.2 Installation Procedure Requirements 1.2.5 Backing Up Your System Disk At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you do a system disk backup before installing any software. Use the backup procedures that are established at your site. For details on performing a system disk backup, see the section on the Backup Utility in the VMS System Management Subkit. Preparing to Install DECmessageQ 1-7 2 _________________________________________________________________ Installing DECmessageQ This chapter explains how to install DECmessageQ. Section 2.1 contains a step-by-step description of the installation procedure. 2.1 The Installation Procedure The DECmessageQ installation procedure consists of a series of questions and informational messages. See Appendix A for a sample installation. To abort 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 exits. You can then start the installation again. 1. Invoke VMSINSTAL. @SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N To start the installation, invoke the VMSINSTAL command procedure from a privileged account, such as the SYSTEM account. VMSINSTAL is in the SYS$UPDATE directory. The following list defines the elements of the VMSINSTAL command procedure: saveset-name The installation name for the component. For DECmessageQ, use the following installation name: DMQ010 device-name The name of the device on which you plan to mount the media. For example, MTA0: is the device name for a tape drive. It is not necessary to use the console drive for this installation. However, if you do use the console drive, you should replace any media you removed once the installation is complete. OPTIONS N An optional parameter that indicates you want to see the question on release notes. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. You should review the release notes before proceeding with the installation in case they contain additional information about the installation. If you are restarting the installation and have already Installing DECmessageQ 2-1 Installing DECmessageQ 2.1 The Installation Procedure reviewed the release notes, you do not need to specify OPTIONS N. Note that there are several other options you can select when you invoke VMSINSTAL. o Auto_answer option (A): Initially creates a file that contains your answers to VMSINSTAL questions and prompts. You can then use the option (and the answer file) to save time during a reinstallation (typically after upgrading your system). o Get save set option (G): Lets you store product save sets temporarily on a magnetic tape or in a disk directory. o File log option (L): Logs all activity to the terminal during installation. See the VMS documentation on software installation in the VMS System Management Subkit for detailed information on these options. If you specify more than one option, separate the options with commas (OPTIONS A,N). The following example invokes VMSINSTAL to install DECmessageQ from tape drive MTA0: and shows the system response. This example uses the OPTIONS N release notes parameter. $ @SYS$UPDATE:VMSINSTAL DMQ010 MTA0: OPTIONS N VAX/VMS Software Product Installation Procedure V5.3 It is 15-FEB-1991 at 16:01. Enter a question mark (?) at any time for help. If you do not supply either the product name or the device name, VMSINSTAL prompts you for this information later in the installation procedure. 2. Confirm system backup. * Are you satisfied with the backup of your system disk [YES]? VMSINSTAL asks if you are satisfied with your system backup. You should always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press Return. Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. 3. Mount the media. 2-2 Installing DECmessageQ Installing DECmessageQ 2.1 The Installation Procedure Please mount the first volume of the set on MTA0:. * Are you ready? YES %MOUNT-I-MOUNTED, DECmessageQ MOUNTED ON _$$MTA0: (NODE 1) The following products will be processed: DMQ V1.0 Beginning installation of DMQ V1.0 at 16:03 %VMSINSTAL-I-RESTORE, Restoring product saveset A... You should now mount the first distribution volume on the device you specified when you invoked VMSINSTAL. The device name appears in the line preceding the question. VMSINSTAL then asks you if you are ready to continue with the installation. If you respond YES to indicate that you are ready, VMSINSTAL displays a message that the media containing DECmessageQ has been mounted on the specified device and that the installation has begun. If you entered the wrong device name when you invoked VMSINSTAL and need to restart the installation, enter NO in response to the "Are you ready?" question. To abort the installation for other reasons, press Ctrl/Y. 4. Select a release notes option. Release notes included with this kit are always copied to SYS$HELP. 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]: If you specified OPTIONS N when you invoked VMSINSTAL, you are now asked to choose one of the four options for reviewing the release notes. If you select option 1, VMSINSTAL displays the release notes immediately on the console terminal. You can terminate the display at any time by pressing Ctrl/C. If you select option 2, VMSINSTAL prompts you for the name of the print queue that you want to use: * Queue name [SYS$PRINT]: You can press Return to send the file to the default output print device or you can enter another queue name. If you select option 3, VMSINSTAL displays the release notes immediately on the console terminal and then prompts you for a queue name for the printed version. Installing DECmessageQ 2-3 Installing DECmessageQ 2.1 The Installation Procedure Select option 4 if you have already reviewed the release notes and are restarting the installation. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: YES %VMSINSTAL-I-RELMOVED, The product's release notes have been successfully moved to SYS$HELP. To continue the installation, enter YES. Otherwise, press Return. In either case, the release notes are copied to a file in the SYS$HELP directory: SYS$HELP:DMQ$V10.RELEASE_NOTES ________________________ Note ________________________ The name of the release notes file installed by VMSINSTAL consists of the current product name and version number. ______________________________________________________ 5. Choose development or run-time kit. * Would you like to install the DECmessageQ for VMS development kit [NO]? You have the option of choosing the run-time only kit. If you want to install the development kit, you must have a Product Authorization Key registered and loaded. If you install the development kit, you will also be asked if you want to install the base DECmessageQ kit and the DECmessageQ demo programs. ________________________ Note ________________________ To install the demo programs, you must have installed a base kit on your system. ______________________________________________________ 6. Respond to license registration queries. Product: DMQ-DEV-V Producer: DEC Version: Release Date: 21-JAN-1991 * Does this product have an authorization key registered and loaded? The installation procedure displays license information about your product and then asks if you have registered and loaded your Product Authorization Key (PAK). If you have not registered and loaded your PAK, you must answer NO to this question. You have to register and load your PAK to successfully complete the installation. If you have not done so, you should stop the installation, register and load your PAK, and then restart the installation. 2-4 Installing DECmessageQ Installing DECmessageQ 2.1 The Installation Procedure 7. Enter the device where DECmessageQ will reside. * Enter the DEVICE where DMQ will reside [SYS$SYSDEVICE]: The default device is SYS$SYSDEVICE, but you can install DECmessageQ on any disk. If you are installing the DECmessageQ development kit, you are asked if you want to install the base kit and demo programs after you specify the device where DECmessageQ will reside. 8. Choose the Installation Verification Procedure (IVP) option. * Do you want to run the IVP after the installation [YES]? The installation procedure now asks if you want to run the IVP. The IVP for DECmessageQ checks to be sure that the installation is successful. It is recommended that you run the IVP. After DECmessageQ is installed, you can run the IVP independently to verify that the software is available on your system. You might need to run the IVP after a system failure to make sure that users can access DECmessageQ (see Section 3.1). 9. Purge files. * Do you want to purge files replaced by this installation [YES]? You have the option to purge files from previous versions of DECmessageQ that are superseded by this installation. Purging is recommended; however, if you need to keep files from the previous version, enter NO in response to the question. Installing DECmessageQ 2-5 Installing DECmessageQ 2.1 The Installation Procedure 10.Read informational messages. At this point, the installation procedure displays a number of informational messages that report on the progress of the installation. There are no further questions. If the installation procedure has been successful up to this point, VMSINSTAL moves the new or modified files to their target directories, updates help files, and updates DCL tables, if necessary. If you chose to have files purged, that work is done now. The following messages are displayed: %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... 11.Observe the Installation Verification Procedure (IVP). If you chose to run the IVP, VMSINSTAL runs it now. When the IVP runs successfully, you see the following display: %DMQ-S-SUCCESS, DECmessageQ for VMS IVP successfully completed. 12.End the installation procedure. Installation of DMQ V1.0 completed at 17:35 VMSINSTAL procedure done at 17:35 The previous messages indicate that the entire installation procedure is complete. You can now log out of the privileged account: $ LOGOUT SYSTEM logged out at 15-FEB-1991 17:35:46.53 Note that 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. 2.2 Error Recovery If errors occur during the installation itself or when the Installation Verification Procedure (IVP) is running, VMSINSTAL displays failure messages. If the installation fails, you see the following message: %VMSINSTAL-E-INSFAIL, The installation of DECmessageQ V1.0 has failed. If the IVP fails, you see these messages: The DECmessageQ V1.0 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for DECmessageQ V1.0 has failed. 2-6 Installing DECmessageQ Installing DECmessageQ 2.2 Error Recovery Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect. o A prerequisite software version is incorrect. o Quotas necessary for successful installation are insufficient. o System parameter values for successful installation are insufficient. o The product license has not been registered and loaded. For descriptions of the error messages generated by these conditions, see the VMS documentation on system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, you should take the appropriate action as described in the message. For information on installation requirements, see Chapter 1. Installing DECmessageQ 2-7 3 _________________________________________________________________ After Installing DECmessageQ The following tasks take place after installing DECmessageQ: o Running the Installation Verification Procedure separately o Editing the system startup and shutdown files o Making the product usable on a VAXcluster o Setting user account quotas and privileges o Reporting problems 3.1 Running the Installation Verification Procedure Separately You usually run the Installation Verification Procedure (IVP) during installation. If you want to run the IVP separately to ensure the integrity of installed files should system problems occur, execute the following command procedure: $ @[DMQ$V10.EXE]DMQ$IVP Example 3-1 shows an example of the IVP. Example 3-1 Installation Verification Procedure (continued on next page) After Installing DECmessageQ 3-1 After Installing DECmessageQ 3.1 Running the Installation Verification Procedure Separately Example 3-1 (Cont.) Installation Verification Procedure %DMQ-I-SETUP, Setting up DECmessageQ IVP environment %DMQ-I-SETUP, Clearing DECmessageQ logicals from process logical name table... %DMQ-I-SETUP, Creating IVP group 0000_00001 in directory SYS$SYSDEVICE:[DMQ$V10.USER.0000_00001] %CREATE-I-CREATED, SYS$SYSDEVICE:[DMQ$V10.USER.0000_00001] created %CREATE-I-CREATED, SYS$SYSDEVICE:[DMQ$V10.LOG.0000_00001] created %CREATE-I-CREATED, SYS$SYSDEVICE:[DMQ$V10.MRS.0000_00001] created %DMQ-I-COPYFILE, Copying DMQ$BOOT.COM %DMQ-I-COPYFILE, Copying DMQ$INIT.TXT %DMQ-I-COPYFILE, Copying DMQ$TYPCLS.TXT %DMQ-I-COPYFILE, Copying HIDDEN_DATA_TYPES.PAS %DMQ-I-COPYFILE, Copying PAIENTBLI.TXT %DMQ-I-COPYFILE, Copying PAIENTPAS.TXT %DMQ-I-COPYFILE, Copying PAIGRPBLI.TXT %DMQ-I-COPYFILE, Copying PAIGRPPAS.TXT %DMQ-I-COPYFILE, Copying PAIPRCBLI.TXT %DMQ-I-COPYFILE, Copying PAIPRCPAS.TXT %DMQ-I-COPYFILE, Copying PAISTSBLI.TXT %DMQ-I-COPYFILE, Copying PAISTSDBLI.TXT %DMQ-I-COPYFILE, Copying PAISTSDPAS.TXT %DMQ-I-COPYFILE, Copying PAISTSPAS.TXT %DMQ-I-COPYFILE, Copying PAISYMBLI.TXT %DMQ-I-COPYFILE, Copying PAISYMPAS.TXT %DMQ-I-COPYFILE, Copying PAITYPBLI.TXT %DMQ-I-COPYFILE, Copying PAITYPPAS.TXT %DMQ-I-COPYFILE, Copying PAMS_ADA_ENTRY_POINT_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_GROUP_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_PROCESS_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_RETURN_STATUS_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_RETURN_STATUS_DEF_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_SYMBOL_DEF_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_TYPE_CLASS_.ADA %DMQ-I-COPYFILE, Copying PSSBUILD.MLB %DMQ-I-COPYFILE, Copying PSSSYNTAX.MAR %DMQ-I-COPYFILE, Copying PSSSYNTAX.OBJ %DMQ-I-COPYFILE, Copying SYCUSTOMIZE.COM %DMQ-I-COPYFILE, Copying DMQ.TLB %DMQ-I-COPYFILE, Copying DMQ.MLB ...Linking DMQ$PSSRTL0000_00001 (DMQ$PSSRTL) ---------------------------------------------------------------------- Please verify the following: DMQ$INIT.TXT - if Cross-Group messaging has been enabled then this group must have an entry for itself with the DECnet node name matching this node. To complete the group creation DMQ$STARTUP needs to be run in order to create the DECmessageQ LNM table and names. ---------------------------------------------------------------------- (continued on next page) 3-2 After Installing DECmessageQ After Installing DECmessageQ 3.1 Running the Installation Verification Procedure Separately Example 3-1 (Cont.) Installation Verification Procedure %DMQ-I-SETUP, Defining necessary logical names... %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 %DMQ-I-SETUP, Starting IVP group... DMQ$STARTUP.COM - 15-FEB-1991 17:06:06.03 Bus: 0000 Group: 00001 Disk: SYS$SYSDEVICE: Start Servers: Y DMQ Version: DMQ$V10 User Area: DMQ$DISK:[DMQ$V10.USER.0000_00001] Log Area: DMQ$DISK:[DMQ$V10.LOG.0000_00001] PSS file: DMQ$USER:DMQ$PSSRTL0000_00001.EXE %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 DMQ$FORCEX: Forcing image termination on process "DMQ_C_000000001" %SYSTEM-W-NONEXPR, nonexistent process ...Installing DMQ$MSGSHR ...Installing DMQ$EXECRTL ...Installing DMQ$PSSRTL ...Installing DMQ$ENTRYRTL ...Creating DMQ$BOOT_DATA_FILE ...Starting DMQ_C_000000001 (DMQ$COM_SERVER) %RUN-S-PROC_ID, identification of created process is 2020005E %DMQ_xxxx_xxxxx-COM_SERVER-I-DMQ$COM_SERVER (V1.0-02A) starting at 15-FEB-1991 17:06:41 %DMQ_xxxx_xxxxx-COM_SERVER-I-Checking product "DMQ-DEV-V" for DEV type license %DMQ_xxxx_xxxxx-COM_SERVER-I-Created MCS and LLS containing 419 pages. %DMQ_0000_00001-COM_SERVER-I-Begin initial configuration database load %DMQ_xxxx_xxxxx-DMQ_LOADER-I-DECmessageQ System Loader starting... %DMQ_0000_00001-DMQ_LOADER-I-Parsing PROFILE Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing X-Group Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Skipping Buffer Pool Configuration Section %DMQ_0000_00001-DMQ_LOADER-I-Parsing Queue Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing SBS Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing MRS Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing Group Name Table %DMQ_0000_00001-COM_SERVER-I-Created 200 entry Group Name Table containing 32 pages %DMQ_0000_00001-DMQ_LOADER-I-DECmessageQ load successfully completed %DMQ_0000_00001-COM_SERVER-I-Created 1 multi-reader queue %DMQ_0000_00001-COM_SERVER-I-Automatic reset of counters at 15-FEB-1991 17:06:57 %DMQ_0000_00001-COM_SERVER-I-Group 1 (ONE) Initialized ...Starting DMQ_S_000000001 (DMQ$SBS_SERVER) %RUN-S-PROC_ID, identification of created process is 2020005F ...Starting DMQ_M_000000001 (DMQ$MRS_SERVER) %RUN-S-PROC_ID, identification of created process is 20200060 %DMQ_0000_00001-SBS_SERVER-I-SBS_SERVER(DMQ V1.0-00) Booted %DMQ_0000_00001-SBS_SERVER-I-SBS_SERVER(DMQ V1.0-00) Initialized (continued on next page) After Installing DECmessageQ 3-3 After Installing DECmessageQ 3.1 Running the Installation Verification Procedure Separately Example 3-1 (Cont.) Installation Verification Procedure %DMQ-I-COMSTART, DECmessageQ COM Server DMQ_C_0000_00001 successfully started DECmessageQ Installation Verification Program. To override default of temporary process numbers use the logicals DMQ$DCL_NUMBER and DMQ$DCLS_NUMBER. ok - STARTING VALIDATION OF DECmessageQ ROUTINES Test declare process. %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:24.82 %DMQ_0000_00001-MRS_SERVER-I-MRS DMQ V1.0-00 starting %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:26.37 %DMQ_0000_00001-MRS_SERVER-I-Space alloted for 15 queues, 100 messages %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:26.43 %DMQ_0000_00001-MRS_SERVER-I-DQF size:0 bytes, chunks:0, chunk_size:2500 bytes %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:26.50 %DMQ_0000_00001-MRS_SERVER-I-Max SAF files:100, SAF file size:10000 bytes %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:27.64 %DMQ_0000_00001-MRS_SERVER-I-MRS DMQ V1.0-00 initialized Declared self as 1.200. Test declare synch process. Synch declared self as 201. Test allocating a message buffer. Test send message. Test receive message wait. Test free message just received. Test disconnecting from PAMS. Test re-declaring to PAMS. Declared self as 1.202. Test re-declaring synch to PAMS. Synch declared self as 203. Test set timer. Test waiting for the timer just set. ok - SET TIMER ...waiting 5 seconds Test receiving the timer message. Test canceling the timer. Test setting synch. Test sending and receiving synch messages. Test canceling synch. Test pass-along of receive buffers. Test pass-along of UCB buffers. Test for both normal and synch receive buffers. Test synch queue buffer flushing. ok - NORMAL PAMS CALLS HAVE EXECUTED PROPERLY (continued on next page) 3-4 After Installing DECmessageQ After Installing DECmessageQ 3.1 Running the Installation Verification Procedure Separately Example 3-1 (Cont.) Installation Verification Procedure ok - STARTING TEST OF PROPER ERROR CONDITION CODE PRODUCTION Test declare process 2X. Test allocate buffer 2X. Test send message 2X. Test receive message wait timeout. Test free message 2X. Test send message with bad priority. Test send message with bad delivery number. ok - ERROR PRODUCING PAMS CALLS HAVE EXECUTED PROPERLY %DMQ-I-COMSTOP, Preparing to stop DECmessageQ COM Server DMQ_C_0000_00001 %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 DMQ$FORCEX: Forcing image termination on process "DMQ_C_000000001" %DMQ_0000_00001-I-FORCEX, Process # 98 "MRS_SERVER " PID (20200060) forced to exit. %DMQ_0000_00001-I-FORCEX, Process # 99 "SBS_SERVER " PID (2020005F) forced to exit. DMQ$FORCEX: Process "DMQ_C_000000001" image terminated. %DMQ-I-RTLREM, Removed DMQ$MSGSHR %DMQ-I-RTLREM, Removed DMQ$EXECRTL %DMQ-I-RTLREM, Removed DMQ$PSSRTL %DMQ-I-RTLREM, Removed DMQ$ENTRYRTL %DMQ-I-CLNUP, Cleaning up %DMQ-I-CLNUP, Removing subdirectory SYS$SYSDEVICE:[DMQ$V10.USER.0000_00001] %DMQ-I-CLNUP, Removing subdirectory SYS$SYSDEVICE:[DMQ$V10.LOG.0000_00001] %DMQ-I-CLNUP, Removing subdirectory SYS$SYSDEVICE:[DMQ$V10.MRS.0000_00001] %DMQ-I-CLNUP, Clearing logical name table DMQ$LNM_ Removing logical DMQ$BOOT_DATA_FILE from table DMQ$LNM_TBL Removing logical DMQ$BUS_GROUP from table DMQ$LNM_TBL Removing logical DMQ$DEMO from table DMQ$LNM_TBL Removing logical DMQ$DOC from table DMQ$LNM_TBL Removing logical DMQ$ENTRYRTL from table DMQ$LNM_TBL Removing logical DMQ$MSGSHR from table DMQ$LNM_TBL Removing logical DMQ$EXAMPLES from table DMQ$LNM_TBL Removing logical DMQ$EXE from table DMQ$LNM_TBL Removing logical DMQ$EXECRTL from table DMQ$LNM_TBL Removing logical DMQ$INIT_FILE from table DMQ$LNM_TBL Removing logical DMQ$LIB from table DMQ$LNM_TBL Removing logical DMQ$LOG from table DMQ$LNM_TBL Removing logical DMQ$PSSRTL from table DMQ$LNM_TBL Removing logical DMQ$USER from table DMQ$LNM_TBL Removing logical DMQ$VERSION from table DMQ$LNM_TBL %DMQ-S-SUCCESS, DECmessageQ for VMS IVP successfully completed. 3.2 Editing the System Files After DECmessageQ is installed, the DECmessageQ configuration manager may want to add automatic startup and shutdown files to the SYSTARTUP and SYSHUTDOWN command files. See the DECmessageQ Management and Configuration Guide for VMS for information on editing the DECmessageQ startup and shutdown files. After Installing DECmessageQ 3-5 After Installing DECmessageQ 3.3 VAXcluster Considerations 3.3 VAXcluster Considerations To use DECmessageQ on a VAXcluster, you must load the license for DECmessageQ on each node in the cluster. For a development kit enter the following at the system prompt: $ License Load DMQ-DEV-V For a run-time only kit enter the following at the system prompt: $ License Load DMQ-RTO-V ________________________ Note ________________________ The License Load command will fail if the license has not been registered on the cluster (see Section 1.1). ______________________________________________________ 3.4 User Account Requirements To work with DECmessageQ, user accounts on your system require no special privileges or quotas. The configuration manager does require certain privileges (see the DECmessageQ Management and Configuration Guide for VMS). 3.5 Determining and Reporting Problems If you encounter a problem while using DECmessageQ, report it to Digital. Depending on the nature of the problem and the type of support you have, you can take one of the following actions: o Call Digital if your software contract or warranty agreement entitles you to telephone support. o Submit a Software Performance Report (SPR). o Fill out and submit a Reader's Comments form if the problem has to do with the DECmessageQ documentation. There are Reader's Comments forms at the back of each manual. Use the form from the manual in which you found the error. Include the section and page number. Review the Software Product Description (SPD) and Warranty Addendum for an explanation of warranty. If you encounter a problem during the warranty period, report the problem as indicated above or follow alternate instructions provided by Digital for reporting SPD nonconformance problems. 3-6 After Installing DECmessageQ A _________________________________________________________________ Sample Installation This appendix contains a sample installation of DECmessageQ. This sample was run on a system that had no previous version of DECmessageQ installed. Depending on which layered products you have on your system, you might see additional messages and questions when you perform your installation. The sample installation assumes that DECnet has been shut down, that no users are logged in to your system, and that OPTIONS N is specified to print the release notes. The Installation Verification Procedure (IVP) runs at the end of the installation. A.1 Full Development Kit This section contains a sample installation for the DECmessageQ full development kit. $ @SYS$UPDATE:VMSINSTAL VAX/VMS Software Product Installation Procedure V5.4-1 It is 15-FEB-1991 at 16:10. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? * Where will the distribution volumes be mounted: MUAO: Enter the products to be processed from the first distribution volume set. * Products: DMQ010 * Enter installation options you wish to use (none): N The following products will be processed: DMQ V1.0 Beginning installation of DMQ V1.0 at 16:11 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 Sample Installation A-1 Sample Installation A.1 Full Development Kit 4. None of the above * Select option : 4 * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. * Would you like to install the DECmessageQ for VMS development kit [NO]: YES Product: DMQ-DEV-V Producer: DEC Version: Release Date: 21-JAN-1991 * Does this product have an authorization key registered and loaded? YES * Enter the DEVICE where DMQ will reside [SYS$SYSDEVICE]: ==================================================================== The DECmessageQ for VMS installation is divided into two parts: 1 Base kit) 2 Demo programs directory ) ==================================================================== * Install base DECmessageQ kit [YES]? * Install DECmessageQ demo programs [YES]? * Do you want to run the IVP after the installation [YES]? * Do you want to purge files replaced by this installation [YES]? =================================================================== All questions regarding the installation of DECmessageQ for VMS have now been asked. The installation will continue for approximately 1-2 hours, depending on load, CPU type and kit media. =================================================================== %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %DMQ-I-LINKALL, Link all DMQ images .... %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 ...Linking DMQ$EXECRTLV10 (DMQ$EXECRTL) ...Linking DMQ$PSSRTL (DMQ$PSSRTL) ...Linking DMQ$ENTRYRTLV10 (DMQ$ENTRYRTL) ...Linking DMQ$MSGSHRV10 (DMQ$MSGSHR) ...Linking DMQ$COM_SERVER ...Linking DMQ$LOADER ...Linking DMQ$SBS_SERVER ...Linking DMQ$MRS_SERVER ...Linking DMQ$CHECK_LICENSE ...Linking DMQ$FORCEX ...Linking DMQ$LLS_VERIFY ...Linking DMQ$LOOP ...Linking DMQ$MONITOR ...Linking DMQ$TEST A-2 Sample Installation Sample Installation A.1 Full Development Kit ...Linking DMQ$MRQ_TEST ...Linking DMQ$IVP ...Linking DMQ$SBS_EXAMPLE ...Linking DMQ$PSSVFY ...Linking DMQ$QFLUSH ...Linking DMQ$DSPBLK ...Linking DMQ$DNSLOAD ...Linking DMQ$DQF_UTIL ...Linking DMQ$DUMP_GNT ...Linking DMQ$LIST_PROCS ...Linking DMQ$TEST_LOCATE ...Linking DMQ$QMENU ...Linking DMQ$VALID ...Linking DMQ$SRC ...Linking DMQ$SINK ...Linking DMQ$JTEST ...Linking DMQ$DQF_CONTROL ...Linking DMQ$QTRANSFER DEMO_BUILD - Build the DECmessageQ Demonstration Software. Linking image DEMO_ARCHIVE Linking image DEMO_IO_SERVER Linking image DEMO_CLIENT Linking image DEMO_MONITOR Linking image DEMO_FULL_MONITOR Linking image CHECK_FOR_DMQ %DEMO_BUILD-I-DONE, DECmessageQ demonstration software built. %VMSINSTAL-I-SYSDIR, This product creates system disk directory SYS$SYSDEVICE:[DMQ$V10]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.EXE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.USER]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.USER.TEMPLATE]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.DOC]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.MRS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.LOG]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.LIB]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.EXAMPLES]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.EXAMPLES.MRS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.EXAMPLES.SBS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.DEMO]. %VMSINSTAL-I-SYSDIR, This product creates system disk directory DMQ$DISK:[DMQ$V10.DEMO.VMS]. ===================================================================== The DECmessageQ for VMS Installation has completed successfully. Before programs can access DECmessageQ for VMS a privileged user must configure a DECmessageQ group with SYS$SYSDEVICE:[DMQ$V10.EXE]- DMQ$CREATE_GROUP.COM. Then SYS$SYSDEVICE:[DMQ$V10.EXE]DMQ$STARTUP.COM must be called in the site specific startup procedure for each DECmessageQ group to create the DECmessageQ logical name tables and to optionally start the DECmessageQ servers. Please see the "DECmessageQ for VMS Management and Configuration Guide" for details. Sample Installation A-3 Sample Installation A.1 Full Development Kit Once the DECmessageQ Servers are up a (non-privileged) user program can gain access to the DECmessageQ group through the logicals defined in the DECmessageQ logical name tables. It needs to execute SYS$SYSDEVICE:[DMQ$V10.EXE]DMQ$SET_LNM_TABLE.COM to find the appropriate logical name table. See the "DECmessageQ Programmers Guide" for details. The Installation Verification Procedure DMQ$IVP.COM has been placed in SYS$SYSDEVICE:[DMQ$V10.EXE]. An extra copy of the Release Notes DMQ010.RELEASE_NOTES has been placed in SYS$SYSDEVICE:[DMQ$V10.DOC]. ===================================================================== %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... DECmessageQ V1.0 IVP started at 15-FEB-1991 17:01 %DMQ-I-SETUP, Setting up DECmessageQ IVP environment %DMQ-I-SETUP, Clearing DECmessageQ logicals from process logical name table... %DMQ-I-SETUP, Creating IVP group 0000_00001 in directory SYS$SYSDEVICE:[DMQ$V10.USER.0000_00001] %CREATE-I-CREATED, SYS$SYSDEVICE:[DMQ$V10.USER.0000_00001] created %CREATE-I-CREATED, SYS$SYSDEVICE:[DMQ$V10.LOG.0000_00001] created %CREATE-I-CREATED, SYS$SYSDEVICE:[DMQ$V10.MRS.0000_00001] created %DMQ-I-COPYFILE, Copying DMQ$BOOT.COM %DMQ-I-COPYFILE, Copying DMQ$INIT.TXT %DMQ-I-COPYFILE, Copying DMQ$TYPCLS.TXT %DMQ-I-COPYFILE, Copying HIDDEN_DATA_TYPES.PAS %DMQ-I-COPYFILE, Copying PAIENTBLI.TXT %DMQ-I-COPYFILE, Copying PAIENTPAS.TXT %DMQ-I-COPYFILE, Copying PAIGRPBLI.TXT %DMQ-I-COPYFILE, Copying PAIGRPPAS.TXT %DMQ-I-COPYFILE, Copying PAIPRCBLI.TXT %DMQ-I-COPYFILE, Copying PAIPRCPAS.TXT %DMQ-I-COPYFILE, Copying PAISTSBLI.TXT %DMQ-I-COPYFILE, Copying PAISTSDBLI.TXT %DMQ-I-COPYFILE, Copying PAISTSDPAS.TXT %DMQ-I-COPYFILE, Copying PAISTSPAS.TXT %DMQ-I-COPYFILE, Copying PAISYMBLI.TXT %DMQ-I-COPYFILE, Copying PAISYMPAS.TXT %DMQ-I-COPYFILE, Copying PAITYPBLI.TXT %DMQ-I-COPYFILE, Copying PAITYPPAS.TXT %DMQ-I-COPYFILE, Copying PAMS_ADA_ENTRY_POINT_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_GROUP_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_PROCESS_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_RETURN_STATUS_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_RETURN_STATUS_DEF_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_SYMBOL_DEF_.ADA %DMQ-I-COPYFILE, Copying PAMS_ADA_TYPE_CLASS_.ADA %DMQ-I-COPYFILE, Copying PSSBUILD.MLB %DMQ-I-COPYFILE, Copying PSSSYNTAX.MAR %DMQ-I-COPYFILE, Copying PSSSYNTAX.OBJ %DMQ-I-COPYFILE, Copying SYCUSTOMIZE.COM %DMQ-I-COPYFILE, Copying DMQ.TLB %DMQ-I-COPYFILE, Copying DMQ.MLB ...Linking DMQ$PSSRTL0000_00001 (DMQ$PSSRTL) A-4 Sample Installation Sample Installation A.1 Full Development Kit ---------------------------------------------------------------------- Please verify the following: DMQ$INIT.TXT - if Cross-Group messaging has been enabled then this group must have an entry for itself with the DECnet node name matching this node. To complete the group creation DMQ$STARTUP needs to be run in order to create the DECmessageQ LNM table and names. ---------------------------------------------------------------------- %DMQ-I-SETUP, Defining necessary logical names... %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 %DMQ-I-SETUP, Starting IVP group... DMQ$STARTUP.COM - 15-FEB-1991 17:06:06.03 Bus: 0000 Group: 00001 Disk: SYS$SYSDEVICE: Start Servers: Y DMQ Version: DMQ$V10 User Area: DMQ$DISK:[DMQ$V10.USER.0000_00001] Log Area: DMQ$DISK:[DMQ$V10.LOG.0000_00001] PSS file: DMQ$USER:DMQ$PSSRTL0000_00001.EXE %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 DMQ$FORCEX: Forcing image termination on process "DMQ_C_000000001" %SYSTEM-W-NONEXPR, nonexistent process ...Installing DMQ$MSGSHR ...Installing DMQ$EXECRTL ...Installing DMQ$PSSRTL ...Installing DMQ$ENTRYRTL ...Creating DMQ$BOOT_DATA_FILE ...Starting DMQ_C_000000001 (DMQ$COM_SERVER) %RUN-S-PROC_ID, identification of created process is 2020005E %DMQ_xxxx_xxxxx-COM_SERVER-I-DMQ$COM_SERVER (V1.0-02A) starting at 15-FEB-1991 17:06:41 %DMQ_xxxx_xxxxx-COM_SERVER-I-Checking product "DMQ-DEV-V" for DEV type license Sample Installation A-5 Sample Installation A.1 Full Development Kit %DMQ_xxxx_xxxxx-COM_SERVER-I-Created MCS and LLS containing 419 pages. %DMQ_0000_00001-COM_SERVER-I-Begin initial configuration database load %DMQ_xxxx_xxxxx-DMQ_LOADER-I-DECmessageQ System Loader starting... %DMQ_0000_00001-DMQ_LOADER-I-Parsing PROFILE Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing X-Group Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Skipping Buffer Pool Configuration Section %DMQ_0000_00001-DMQ_LOADER-I-Parsing Queue Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing SBS Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing MRS Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing Group Name Table %DMQ_0000_00001-COM_SERVER-I-Created 200 entry Group Name Table containing 32 pages %DMQ_0000_00001-DMQ_LOADER-I-DECmessageQ load successfully completed %DMQ_0000_00001-COM_SERVER-I-Created 1 multi-reader queue %DMQ_0000_00001-COM_SERVER-I-Automatic reset of counters at 15-FEB-1991 17:06:57 %DMQ_0000_00001-COM_SERVER-I-Group 1 (ONE) Initialized ...Starting DMQ_S_000000001 (DMQ$SBS_SERVER) %RUN-S-PROC_ID, identification of created process is 2020005F ...Starting DMQ_M_000000001 (DMQ$MRS_SERVER) %RUN-S-PROC_ID, identification of created process is 20200060 %DMQ_0000_00001-SBS_SERVER-I-SBS_SERVER(DMQ V1.0-00) Booted %DMQ_0000_00001-SBS_SERVER-I-SBS_SERVER(DMQ V1.0-00) Initialized %DMQ-I-COMSTART, DECmessageQ COM Server DMQ_C_0000_00001 successfully started DECmessageQ Installation Verification Program. To override default of temporary process numbers use the logicals DMQ$DCL_NUMBER and DMQ$DCLS_NUMBER. ok - STARTING VALIDATION OF DECmessageQ ROUTINES Test declare process. %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:24.82 %DMQ_0000_00001-MRS_SERVER-I-MRS DMQ V1.0-00 starting %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:26.37 %DMQ_0000_00001-MRS_SERVER-I-Space alloted for 15 queues, 100 messages %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:26.43 %DMQ_0000_00001-MRS_SERVER-I-DQF size:0 bytes, chunks:0, chunk_size:2500 bytes %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:26.50 %DMQ_0000_00001-MRS_SERVER-I-Max SAF files:100, SAF file size:10000 bytes %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 17:07:27.64 %DMQ_0000_00001-MRS_SERVER-I-MRS DMQ V1.0-00 initialized Declared self as 1.200. Test declare synch process. Synch declared self as 201. Test allocating a message buffer. A-6 Sample Installation Sample Installation A.1 Full Development Kit Test send message. Test receive message wait. Test free message just received. Test disconnecting from PAMS. Test re-declaring to PAMS. Declared self as 1.202. Test re-declaring synch to PAMS. Synch declared self as 203. Test set timer. Test waiting for the timer just set. ok - SET TIMER ...waiting 5 seconds Test receiving the timer message. Test canceling the timer. Test setting synch. Test sending and receiving synch messages. Test canceling synch. Test pass-along of receive buffers. Test pass-along of UCB buffers. Test for both normal and synch receive buffers. Test synch queue buffer flushing. ok - NORMAL PAMS CALLS HAVE EXECUTED PROPERLY ok - STARTING TEST OF PROPER ERROR CONDITION CODE PRODUCTION Test declare process 2X. Test allocate buffer 2X. Test send message 2X. Test receive message wait timeout. Test free message 2X. Test send message with bad priority. Test send message with bad delivery number. ok - ERROR PRODUCING PAMS CALLS HAVE EXECUTED PROPERLY %DMQ-I-COMSTOP, Preparing to stop DECmessageQ COM Server DMQ_C_0000_00001 %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 DMQ$FORCEX: Forcing image termination on process "DMQ_C_000000001" %DMQ_0000_00001-I-FORCEX, Process # 98 "MRS_SERVER " PID (20200060) forced to exit. %DMQ_0000_00001-I-FORCEX, Process # 99 "SBS_SERVER " PID (2020005F) forced to exit. DMQ$FORCEX: Process "DMQ_C_000000001" image terminated. %DMQ-I-RTLREM, Removed DMQ$MSGSHR %DMQ-I-RTLREM, Removed DMQ$EXECRTL %DMQ-I-RTLREM, Removed DMQ$PSSRTL %DMQ-I-RTLREM, Removed DMQ$ENTRYRTL %DMQ-I-CLNUP, Cleaning up %DMQ-I-CLNUP, Removing subdirectory SYS$SYSDEVICE:[DMQ$V10.USER.0000_00001] %DMQ-I-CLNUP, Removing subdirectory SYS$SYSDEVICE:[DMQ$V10.LOG.0000_00001] %DMQ-I-CLNUP, Removing subdirectory SYS$SYSDEVICE:[DMQ$V10.MRS.0000_00001] %DMQ-I-CLNUP, Clearing logical name table DMQ$LNM_ Removing logical DMQ$BOOT_DATA_FILE from table DMQ$LNM_TBL Removing logical DMQ$BUS_GROUP from table DMQ$LNM_TBL Removing logical DMQ$DEMO from table DMQ$LNM_TBL Removing logical DMQ$DOC from table DMQ$LNM_TBL Removing logical DMQ$ENTRYRTL from table DMQ$LNM_TBL Removing logical DMQ$MSGSHR from table DMQ$LNM_TBL Removing logical DMQ$EXAMPLES from table DMQ$LNM_TBL Sample Installation A-7 Sample Installation A.1 Full Development Kit Removing logical DMQ$EXE from table DMQ$LNM_TBL Removing logical DMQ$EXECRTL from table DMQ$LNM_TBL Removing logical DMQ$INIT_FILE from table DMQ$LNM_TBL Removing logical DMQ$LIB from table DMQ$LNM_TBL Removing logical DMQ$LOG from table DMQ$LNM_TBL Removing logical DMQ$PSSRTL from table DMQ$LNM_TBL Removing logical DMQ$USER from table DMQ$LNM_TBL Removing logical DMQ$VERSION from table DMQ$LNM_TBL %DMQ-S-SUCCESS, DECmessageQ for VMS IVP successfully completed. DECmessageQ V1.0 IVP completed at 15-FEB-1991 17:07 Installation of DMQ V1.0 completed at 17:08 A-8 Sample Installation Sample Installation A.2 Run-Time Kit A.2 Run-Time Kit This section contains a sample installation for the DECmessageQ run-time only kit. $ @VMSINSTAL DMQ010 MUA0: VAX/VMS Software Product Installation Procedure V5.3 It is 15-FEB-1991 at 11:33. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? The following products will be processed: DMQ V1.0 Beginning installation of DMQ V1.0 at 11:33 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option : 4 * Do you want to continue the installation [NO]? YES %VMSINSTAL-I-RELMOVED , The product's release notes have been successfully moved to SYS$HELP. * Would you like to install the DECmessageQ for VMS development kit [NO]: * Would you like to install the DECmessageQ for VMS runtime only kit [YES]? Product: DMQ-RTO-V Producer: DEC Version: Release Date: 21-JAN-1991 * Does this product have an authorization key registered and loaded? Yes Sample Installation A-9 Sample Installation A.2 Run-Time Kit * Enter the DEVICE where DMQ will reside [SYS$SYSDEVICE]: * Do you want to run the IVP after the installation [YES]? * Do you want to purge files replaced by this installation [YES]? =================================================================== All questions regarding the installation of DECmessageQ for VMS have now been asked. The installation will continue for approximately 1-2 hours, depending on load, CPU type and kit media. =================================================================== %VMSINSTAL-I-RESTORE, Restoring product save set B ... %DMQ-I-LINKALL, Link all DMQ images .... %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 ...Linking DMQ$EXECRTLV10 (DMQ$EXECRTL) ...Linking DMQ$PSSRTL (DMQ$PSSRTL) ...Linking DMQ$ENTRYRTLV10 (DMQ$ENTRYRTL) ...Linking DMQ$MSGSHRV10 (DMQ$MSGSHR) ...Linking DMQ$COM_SERVER ...Linking DMQ$LOADER ...Linking DMQ$SBS_SERVER ...Linking DMQ$MRS_SERVER ...Linking DMQ$CHECK_LICENSE ...Linking DMQ$FORCEX ...Linking DMQ$LLS_VERIFY ...Linking DMQ$LOOP ...Linking DMQ$MONITOR ...Linking DMQ$TEST ...Linking DMQ$MRQ_TEST ...Linking DMQ$IVP ...Linking DMQ$SBS_EXAMPLE ...Linking DMQ$PSSVFY ...Linking DMQ$QFLUSH ...Linking DMQ$DSPBLK ...Linking DMQ$DNSLOAD ...Linking DMQ$DQF_UTIL ...Linking DMQ$DUMP_GNT ...Linking DMQ$LIST_PROCS ...Linking DMQ$TEST_LOCATE ...Linking DMQ$QMENU ...Linking DMQ$VALID ...Linking DMQ$SRC ...Linking DMQ$SINK ...Linking DMQ$JTEST ...Linking DMQ$DQF_CONTROL ...Linking DMQ$QTRANSFER ===================================================================== The DECmessageQ for VMS Installation has completed successfully. Before programs can access DECmessageQ for VMS a privileged user must configure a DECmessageQ group with FLASH$DUA0:[DMQ$V10.EXE]- DMQ$CREATE_GROUP.COM. Then FLASH$DUA0:[DMQ$V10.EXE]DMQ$STARTUP.COM must be called in the site specific startup procedure for each A-10 Sample Installation Sample Installation A.2 Run-Time Kit DECmessageQ group to create the DECmessageQ logical name tables and to optionally start the DECmessageQ servers. Please see the DECmessageQ Management and Configuration Guide for VMS for details. Once the DECmessageQ Servers are up a (non-privileged) user program can gain access to the DECmessageQ group through the logicals defined in the DECmessageQ logical name tables. It needs to execute FLASH$DUA0:[DMQ$V10.EXE]DMQ$SET_LNM_TABLE.COM to find the appropriate logical name table. See the DECmessageQ Programmer's Guide for details. The Installation Verification Procedure DMQ$IVP.COM has been placed in FLASH$DUA0:[DMQ$V10.EXE]. An extra copy of the Release Notes DMQ010.RELEASE_NOTES has been placed in FLASH$DUA0:[DMQ$V10.DOC] ===================================================================== %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... DECmessageQ V1.0 IVP started at 15-FEB-1991 11:43 %DMQ-I-SETUP, Setting up DECmessageQ IVP environment %DMQ-I-SETUP, Clearing DECmessageQ logicals from process logical name table... %DMQ-I-CLNUP, Removing subdirectory FLASH$DUA0:[DMQ$V10.USER.0000_00001] %DMQ-I-SETUP, Creating IVP group 0000_00001 in directory FLASH$DUA0:[DMQ$V10.USER.0000_00001] %CREATE-I-CREATED, FLASH$DUA0:[DMQ$V10.USER.0000_00001] created %DMQ-I-COPYFILE, Copying DMQ$BOOT.COM %DMQ-I-COPYFILE, Copying DMQ$INIT.TXT %DMQ-I-COPYFILE, Copying SYCUSTOMIZE.COM %DMQ-I-PSSCRE, Created FLASH$DUA0:[DMQ$V10.USER.0000_00001]DMQ$PSSRTL0000_00001.EXE; ---------------------------------------------------------------------- Please verify the following: DMQ$INIT.TXT - if Cross-Group messaging has been enabled then this group must have an entry for itself with the DECnet node name matching this node. To complete the group creation DMQ$STARTUP needs to be run in order to create the DECmessageQ LNM table and names. ---------------------------------------------------------------------- %DMQ-I-SETUP, Defining necessary logical names... %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 %DMQ-I-SETUP, Starting IVP group... DMQ$STARTUP.COM - 15-FEB-1991 11:52:09.61 Bus: 0000 Group: 00001 Sample Installation A-11 Sample Installation A.2 Run-Time Kit Disk: FLASH$DUA0: Start Servers: Y DMQ Version: DMQ$V10 User Area: DMQ$DISK:[DMQ$V10.USER.0000_00001] Log Area: DMQ$DISK:[DMQ$V10.LOG.0000_00001] PSS file: DMQ$USER:DMQ$PSSRTL0000_00001.EXE %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 DMQ$FORCEX: Forcing image termination on process "DMQ_C_000000001" %SYSTEM-W-NONEXPR, nonexistent process ...Installing DMQ$MSGSHR ...Installing DMQ$EXECRTL ...Installing DMQ$PSSRTL ...Installing DMQ$ENTRYRTL ...Creating DMQ$BOOT_DATA_FILE ...Starting DMQ_C_000000001 (DMQ$COM_SERVER) %RUN-S-PROC_ID, identification of created process is 21A000B4 %DMQ_xxxx_xxxxx-COM_SERVER-I-DMQ$COM_SERVER (V1.0-02A) starting at 15-FEB-1991 11:53:17 %DMQ_xxxx_xxxxx-COM_SERVER-I-Checking product "DMQ-RTO-V" for RTO type license %DMQ_xxxx_xxxxx-COM_SERVER-I-Created MCS and LLS containing 419 pages. %DMQ_0000_00001-COM_SERVER-I-Begin initial configuration database load %DMQ_xxxx_xxxxx-DMQ_LOADER-I-DECmessageQ System Loader starting... %DMQ_0000_00001-DMQ_LOADER-I-Parsing PROFILE Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing X-Group Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Skipping Buffer Pool Configuration Section %DMQ_0000_00001-DMQ_LOADER-I-Parsing Queue Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing SBS Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing MRS Configuration Table %DMQ_0000_00001-DMQ_LOADER-I-Parsing Group Name Table %DMQ_0000_00001-COM_SERVER-I-Created 200 entry Group Name Table containing 32 pages %DMQ_0000_00001-DMQ_LOADER-I-DECmessageQ load successfully completed %DMQ_0000_00001-COM_SERVER-I-Created 1 multi-reader queue %DMQ_0000_00001-COM_SERVER-I-Automatic reset of counters at 15-FEB-1991 11:53:47 %DMQ_0000_00001-COM_SERVER-I-Group 1 (ONE) Initialized ...Starting DMQ_S_000000001 (DMQ$SBS_SERVER) %RUN-S-PROC_ID, identification of created process is 21A000B6 ...Starting DMQ_M_000000001 (DMQ$MRS_SERVER) %DMQ_0000_00001-SBS_SERVER-I-SBS_SERVER(DMQ V1.0-00) Booted %DMQ_0000_00001-SBS_SERVER-I-SBS_SERVER(DMQ V1.0-00) Initialized %RUN-S-PROC_ID, identification of created process is 21A000B7 %DMQ-I-COMSTART, DECmessageQ COM Server DMQ_C_0000_00001 successfully started %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 11:55:00.56 A-12 Sample Installation Sample Installation A.2 Run-Time Kit %DMQ_0000_00001-MRS_SERVER-I-MRS DMQ V1.0-00 starting %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 11:55:03.71 %DMQ_0000_00001-MRS_SERVER-I-Space alloted for 15 queues, 100 messages %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 11:55:03.99 %DMQ_0000_00001-MRS_SERVER-I-DQF size:0 bytes, chunks:0, chunk_size:2500 bytes %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 11:55:04.11 %DMQ_0000_00001-MRS_SERVER-I-Max SAF files:100, SAF file size:10000 bytes %DMQ_0000_00001-MRS_SERVER-I-15-FEB-1991 11:55:05.93 %DMQ_0000_00001-MRS_SERVER-I-MRS DMQ V1.0-00 initialized DECmessageQ Installation Verification Program. To override default of temporary process numbers use the logicals DMQ$DCL_NUMBER and DMQ$DCLS_NUMBER. ok - STARTING VALIDATION OF DECmessageQ ROUTINES Test declare process. Test declare synch process. Synch declared self as 201. Test allocating a message buffer. Test send message. Test receive message wait. Test free message just received. Test disconnecting from PAMS. Test re-declaring to PAMS. Declared self as 1.202. Test re-declaring synch to PAMS. Synch declared self as 203. Test set timer. Test waiting for the timer just set. ok - SET TIMER ...waiting 5 seconds Test receiving the timer message. Test canceling the timer. Test setting synch. Test sending and receiving synch messages. Test canceling synch. Test pass-along of receive buffers. Test pass-along of UCB buffers. Test for both normal and synch receive buffers. Test synch queue buffer flushing. ok - NORMAL PAMS CALLS HAVE EXECUTED PROPERLY ok - STARTING TEST OF PROPER ERROR CONDITION CODE PRODUCTION Test declare process 2X. Test allocate buffer 2X. Test send message 2X. Test receive message wait timeout. Test free message 2X. Test send message with bad priority. Sample Installation A-13 Sample Installation A.2 Run-Time Kit Test send message with bad delivery number. ok - ERROR PRODUCING PAMS CALLS HAVE EXECUTED PROPERLY %DMQ-I-COMSTOP, Preparing to stop DECmessageQ COM Server DMQ_C_0000_00001 %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 DMQ$FORCEX: Forcing image termination on process "DMQ_C_000000001" DMQ$FORCEX: Process "DMQ_C_000000001" image terminated. %DMQ_0000_00001-I-FORCEX, Process # 98 "MRS_SERVER " PID (21A000C4) forced to exit. %DMQ_0000_00001-I-FORCEX, Process # 99 "SBS_SERVER " PID (21A000C3) forced to exit. %DMQ-I-RTLREM, Removed DMQ$MSGSHR %DMQ-I-RTLREM, Removed DMQ$EXECRTL %DMQ-I-RTLREM, Removed DMQ$PSSRTL %DMQ-I-RTLREM, Removed DMQ$ENTRYRTL %DMQ-I-CLNUP, Cleaning up %DMQ-I-CLNUP, Removing subdirectory FLASH$DUA0:[DMQ$V10.USER.0000_00001] %DMQ-I-CLNUP, Removing subdirectory FLASH$DUA0:[DMQ$V10.LOG.0000_00001] %DMQ-I-CLNUP, Removing subdirectory FLASH$DUA0:[DMQ$V10.MRS.0000_00001] %DMQ-I-CLNUP, Clearing logical name table DMQ$LNM_ Removing logical DMQ$BOOT_DATA_FILE from table DMQ$LNM_TBL Removing logical DMQ$BUS_GROUP from table DMQ$LNM_TBL Removing logical DMQ$DEMO from table DMQ$LNM_TBL Removing logical DMQ$DOC from table DMQ$LNM_TBL Removing logical DMQ$ENTRYRTL from table DMQ$LNM_TBL Removing logical DMQ$MSGSHR from table DMQ$LNM_TBL Removing logical DMQ$EXAMPLES from table DMQ$LNM_TBL Removing logical DMQ$EXE from table DMQ$LNM_TBL Removing logical DMQ$EXECRTL from table DMQ$LNM_TBL Removing logical DMQ$INIT_FILE from table DMQ$LNM_TBL Removing logical DMQ$LIB from table DMQ$LNM_TBL Removing logical DMQ$LOG from table DMQ$LNM_TBL Removing logical DMQ$PSSRTL from table DMQ$LNM_TBL Removing logical DMQ$USER from table DMQ$LNM_TBL Removing logical DMQ$VERSION from table DMQ$LNM_TBL %DMQ-S-SUCCESS, DECmessageQ for VMS IVP successfully completed. DECmessageQ V1.0 IVP completed at 15-FEB-1991 11:56 Installation of DMQ V1.0 completed at 11:57 VMSINSTAL procedure done at 12:46 A-14 Sample Installation B _________________________________________________________________ DECmessageQ Files and Logical Names Installed on Your System The DECmessageQ installation procedure installs a number of files on your system and defines some logical names. Section B.1 lists the files installed. Section B.2 lists the logical names that are added to the system logical name table. B.1 File Names This section contains the names of all files created on your system when DECmessageQ is installed. B.1.1 Development Base Kit Files Table B-1 lists the base kit files that are added during the installation of the development kit. Table_B-1_Development_Base_Kit_Files_______________________ File_Name____________________Location______________________ DQF_CONTROL.C DMQ$DISK:[DMQ$V10.EXAMPLES.MRS] JTEST.C DMQ$DISK:[DMQ$V10.EXAMPLES.MRS] SINK.C DMQ$DISK:[DMQ$V10.EXAMPLES.MRS] SINK.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES.MRS] SRC.C DMQ$DISK:[DMQ$V10.EXAMPLES.MRS] SRC.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES.MRS] VALID.C DMQ$DISK:[DMQ$V10.EXAMPLES.MRS] AVAILMSGDEF.H DMQ$DISK:[DMQ$V10.EXAMPLES.SBS] AVAIL_EXAMPLE.C DMQ$DISK:[DMQ$V10.EXAMPLES.SBS] BRDCST_EXAMPLE.C DMQ$DISK:[DMQ$V10.EXAMPLES.SBS] SBSMSGDEF.H DMQ$DISK:[DMQ$V10.EXAMPLES.SBS] SBS_EXAMPLE.C DMQ$DISK:[DMQ$V10.EXAMPLES.SBS] (continued on next page) DECmessageQ Files and Logical Names Installed on Your System B-1 DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ SBS_EXAMPLE.LNK DMQ$DISK:[DMQ$V10.EXAMPLES.SBS] BUILD_MBX_UCB.COM DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] CNTRLC.C DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] CNTRLC.LIS DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] CNTRLC.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] MBX.C DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] MBX.LIS DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] MBX.LNK DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] MBXRCV.C DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] MBXRCV.LIS DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] MBXSND.C DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] MBXSND.LIS DMQ$DISK:[DMQ$V10.EXAMPLES.UCBS] BUILD_PAMS_TASK_ DMQ$DISK:[DMQ$V10.EXAMPLES] EXAMPLES.COM BUILD_PASCAL_PEN_FILE.COM DMQ$DISK:[DMQ$V10.EXAMPLES] COBOL_RECEIVER.COB DMQ$DISK:[DMQ$V10.EXAMPLES] COBOL_RECEIVER.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES] COBOL_SENDER.COB DMQ$DISK:[DMQ$V10.EXAMPLES] COBOL_SENDER.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES] DMQ$MRQ_TEST.C DMQ$DISK:[DMQ$V10.EXAMPLES] DMQ$QMENU.C DMQ$DISK:[DMQ$V10.EXAMPLES] ECHO.PSS DMQ$DISK:[DMQ$V10.EXAMPLES] GETMSG_AST.C DMQ$DISK:[DMQ$V10.EXAMPLES] GETMSG_EF.C DMQ$DISK:[DMQ$V10.EXAMPLES] (continued on next page) B-2 DECmessageQ Files and Logical Names Installed on Your System DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ PAMPRTERR.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES] PAMPRTERR.PLI DMQ$DISK:[DMQ$V10.EXAMPLES] PAMPRTMSG.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES] PAMPRTMSG.PLI DMQ$DISK:[DMQ$V10.EXAMPLES] PAMPRTSTS.C DMQ$DISK:[DMQ$V10.EXAMPLES] PAMPRTSTS.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES] PAMS.LIS DMQ$DISK:[DMQ$V10.EXAMPLES] PAMS.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES] PAMS.PAS DMQ$DISK:[DMQ$V10.EXAMPLES] PAMS.PEN DMQ$DISK:[DMQ$V10.EXAMPLES] PAMSAMPLE.FOR DMQ$DISK:[DMQ$V10.EXAMPLES] PAMSAMPLE.PLI DMQ$DISK:[DMQ$V10.EXAMPLES] PAMSAMPLE_C.C DMQ$DISK:[DMQ$V10.EXAMPLES] PAMSAMPLE_C.LNK DMQ$DISK:[DMQ$V10.EXAMPLES] PAMSSLEEP.C DMQ$DISK:[DMQ$V10.EXAMPLES] PAMS_TASK_PKG.ADA DMQ$DISK:[DMQ$V10.EXAMPLES] PAMS_TASK_PKG_.ADA DMQ$DISK:[DMQ$V10.EXAMPLES] PAMS_TASK_SENDER.ADA DMQ$DISK:[DMQ$V10.EXAMPLES] PAMS_TASK_TESTER.ADA DMQ$DISK:[DMQ$V10.EXAMPLES] PUT_WF_REPLY.C DMQ$DISK:[DMQ$V10.EXAMPLES] SENDER.C DMQ$DISK:[DMQ$V10.EXAMPLES] SENDER.PSS DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE.C DMQ$DISK:[DMQ$V10.EXAMPLES] (continued on next page) DECmessageQ Files and Logical Names Installed on Your System B-3 DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ SIMPLE_BUILD.COM DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE_CLIENT.ADA DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE_CLIENT.C DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE_CLIENT.FOR DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE_CLIENT.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE_RUN_SERVER.COM DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE_SERVER.ADA DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE_SERVER.C DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE_SERVER.FOR DMQ$DISK:[DMQ$V10.EXAMPLES] SIMPLE_SERVER.OBJ DMQ$DISK:[DMQ$V10.EXAMPLES] TTAST.C DMQ$DISK:[DMQ$V10.EXAMPLES] WATCHDOG.C DMQ$DISK:[DMQ$V10.EXAMPLES] DMQ$BOOT.COM DMQ$DISK:[DMQ$V10.USER.TEMPLATE] DMQ$INIT.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] DMQ$PSSRTL.MAP DMQ$DISK:[DMQ$V10.USER.TEMPLATE] DMQ$TYPCLS.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] HIDDEN_DATA_TYPES.PAS DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAIENTBLI.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAIENTPAS.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAIGRPBLI.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAIGRPPAS.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAIPRCBLI.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAIPRCPAS.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] (continued on next page) B-4 DECmessageQ Files and Logical Names Installed on Your System DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ PAISTSBLI.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAISTSDBLI.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAISTSDPAS.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAISTSPAS.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAISYMBLI.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAISYMPAS.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAITYPBLI.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAITYPPAS.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAMS_ADA_ENTRY_POINT_.ADA DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAMS_ADA_GROUP_.ADA DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAMS_ADA_PROCESS_.ADA DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAMS_ADA_RETURN_STATUS_.ADA DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAMS_ADA_RETURN_STATUS_DEF_ DMQ$DISK:[DMQ$V10.USER.TEMPLATE] .ADA PAMS_ADA_SYMBOL_DEF_.ADA DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PAMS_ADA_TYPE_CLASS_.ADA DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PSSBUILD.MLB DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PSSSYNTAX.MAR DMQ$DISK:[DMQ$V10.USER.TEMPLATE] PSSSYNTAX.OBJ DMQ$DISK:[DMQ$V10.USER.TEMPLATE] SYCUSTOMIZE.COM DMQ$DISK:[DMQ$V10.USER.TEMPLATE] DMQ$CHECK_LICENSE.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$CHECK_LICENSE.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$COM_SERVER.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$COM_SERVER.MAP DMQ$DISK:[DMQ$V10.EXE] (continued on next page) DECmessageQ Files and Logical Names Installed on Your System B-5 DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ DMQ$COM_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$COPY_LNM_TABLE.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$CREATE_GROUP.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$CUSTOMIZE.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$DEASSIGN.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$DETACH_PROCESS.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$DNSLOAD.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$DNSLOAD.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$DQF_CONTROL.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$DQF_CONTROL.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$DQF_UTIL.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$DQF_UTIL.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$DSPBLK.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$DSPBLK.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$DUMP_GNT.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$DUMP_GNT.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$ENTRYRTL.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$ENTRYRTL.OPT DMQ$DISK:[DMQ$V10.EXE] DMQ$ENTRYRTLV10.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$ETHTEST.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$EXECRTL.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$EXECRTLV10.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$FORCEX.COM DMQ$DISK:[DMQ$V10.EXE] (continued on next page) B-6 DECmessageQ Files and Logical Names Installed on Your System DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ DMQ$FORCEX.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$FORCEX.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$FULLTEST.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$IVP.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$IVP.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$IVP.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$JTEST.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$JTEST.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$LIST_PROCS.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$LIST_PROCS.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$LLS_VERIFY.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$LLS_VERIFY.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$LOADER.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$LOADER.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$LOOP.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$LOOP.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$MACWRITE.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$MENU.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$MONITOR.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$MONITOR.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$MRQ_TEST.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$MRQ_TEST.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$MRS_SERVER.LNK DMQ$DISK:[DMQ$V10.EXE] (continued on next page) DECmessageQ Files and Logical Names Installed on Your System B-7 DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ DMQ$MRS_SERVER.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$MRS_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$MSGSHR.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$MSGSHR.OBJ DMQ$DISK:[DMQ$V10.EXE] DMQ$MSGTBLBLD.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$PEXIT.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$PRCTBLBLD.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$PROCESS_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$PSSBUILD.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$PSSRTL.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$PSSVFY.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$PSSVFY.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$PSSVFYD.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$QFLUSH.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$QFLUSH.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$QMENU.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$QMENU.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$QTRANSFER.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$QTRANSFER.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$QTRANSFER_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$SBS_EXAMPLE.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$SBS_EXAMPLE.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$SBS_SERVER.LNK DMQ$DISK:[DMQ$V10.EXE] (continued on next page) B-8 DECmessageQ Files and Logical Names Installed on Your System DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ DMQ$SBS_SERVER.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$SBS_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$SET_LNM_TABLE.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$SHUTDOWN.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$SINK.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$SINK.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$SRC.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$SRC.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$STARTUP.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$TEST.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$TEST.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$TEST_LOCATE.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$TEST_LOCATE.MAP DMQ$DISK:[DMQ$V10.EXE] DMQ$VALID.LNK DMQ$DISK:[DMQ$V10.EXE] DMQ$VALID.MAP DMQ$DISK:[DMQ$V10.EXE] LINK.COM DMQ$DISK:[DMQ$V10.EXE] LINKALL.COM DMQ$DISK:[DMQ$V10.EXE] PAMPRTMSG_STUB.OBJ DMQ$DISK:[DMQ$V10.EXE] DMQ$IVP.TLB DMQ$DISK:[DMQ$V10.LIB] DMQ$OLB.OPT DMQ$DISK:[DMQ$V10.LIB] DMQ.MLB DMQ$DISK:[DMQ$V10.LIB] DMQ.OPT DMQ$DISK:[DMQ$V10.LIB] DMQ.TLB DMQ$DISK:[DMQ$V10.LIB] (continued on next page) DECmessageQ Files and Logical Names Installed on Your System B-9 DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ DNS.OLB DMQ$DISK:[DMQ$V10.LIB] ETH_UCB.OLB DMQ$DISK:[DMQ$V10.LIB] EXEC.OLB DMQ$DISK:[DMQ$V10.LIB] MRS.OLB DMQ$DISK:[DMQ$V10.LIB] MSG.OLB DMQ$DISK:[DMQ$V10.LIB] PSS.OLB DMQ$DISK:[DMQ$V10.LIB] PSS_STUBS.OLB DMQ$DISK:[DMQ$V10.LIB] SBS.OLB DMQ$DISK:[DMQ$V10.LIB] UCB.OLB DMQ$DISK:[DMQ$V10.LIB] DMQ010.RELEASE_NOTES SYS$HELP DMQ010.RELEASE_NOTES DMQ$DISK:[DMQ$V10.DOC] DMQ_UCB_PROG_GUIDE.LINE DMQ$DISK:[DMQ$V10.DOC] DMQ$CHECK_LICENSE.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$COM_SERVER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DNSLOAD.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DQF_CONTROL.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DQF_UTIL.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DSPBLK.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DUMP_GNT.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$ENTRYRTLV10.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$EXECRTLV10.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$FORCEX.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$IVP.EXE DMQ$DISK:[DMQ$V10.EXE] (continued on next page) B-10 DECmessageQ Files and Logical Names Installed on Your System DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-1_(Cont.)_Development_Base_Kit_Files_______________ File_Name____________________Location______________________ DMQ$JTEST.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$LIST_PROCS.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$LLS_VERIFY.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$LOADER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$LOOP.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$MONITOR.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$MRQ_TEST.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$MRS_SERVER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$MSGSHRV10.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$PSSVFY.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$QFLUSH.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$QMENU.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$QTRANSFER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$SBS_EXAMPLE.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$SBS_SERVER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$SINK.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$SRC.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$TEST.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$TEST_LOCATE.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$VALID.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$PSSRTL.EXE_______________DMQ$DISK:[DMQ$V10.USER.TEMPLATE] DECmessageQ Files and Logical Names Installed on Your System B-11 DECmessageQ Files and Logical Names Installed on Your System B.1 File Names B.1.2 Development Kit Demo Files Table B-2 lists the demo files that are added during the installation of the development kit. Table_B-2_Development_Demo_Kit_Files_______________________ File_Name___________________Location_______________________ CHECK_FOR_DMQ.C DMQ$DISK:[DMQ$V10.DEMO.VMS] CHECK_FOR_DMQ.LIS DMQ$DISK:[DMQ$V10.DEMO.VMS] CHKDQF.COM DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_ARCHIVE.C DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_BUILD.COM DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_CLIENT.C DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_CLIENT.LIS DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_DEFS.H DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_FULL_MONITOR.C DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_FULL_MONITOR.H DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_FULL_MONITOR.LIS DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_IO_SERVER.C DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_IO_SERVER.LIS DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_LIBRARY.OBJ DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_LIBRARY.OLB DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_MONITOR.C DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_MONITOR.LIS DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_ROUTER.C DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_START.COM DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_SUBS.C DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_SUBS.LIS DMQ$DISK:[DMQ$V10.DEMO.VMS] POLICY_FILE.DAT DMQ$DISK:[DMQ$V10.DEMO.VMS] (continued on next page) B-12 DECmessageQ Files and Logical Names Installed on Your System DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-2_(Cont.)_Development_Demo_Kit_Files_______________ File_Name___________________Location_______________________ POLICY_FILE.FDL DMQ$DISK:[DMQ$V10.DEMO.VMS] TEST_GET.C DMQ$DISK:[DMQ$V10.DEMO.VMS] TEST_PUT.C DMQ$DISK:[DMQ$V10.DEMO.VMS] CHECK_FOR_DMQ.EXE DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_CLIENT.EXE DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_FULL_MONITOR.EXE DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_IO_SERVER.EXE DMQ$DISK:[DMQ$V10.DEMO.VMS] DEMO_MONITOR.EXE____________DMQ$DISK:[DMQ$V10.DEMO.VMS]____ DECmessageQ Files and Logical Names Installed on Your System B-13 DECmessageQ Files and Logical Names Installed on Your System B.1 File Names B.1.3 Run-time Kit Files Table B-3 lists the files that are added during the installation of the run-time kit. Table_B-3_Run-time_Kit_Files_______________________________ File_Name___________________Location_______________________ DMQ010.RELEASE_NOTES SYS$HELP DMQ$BOOT.COM DMQ$DISK:[DMQ$V10.USER.TEMPLATE] SYCUSTOMIZE.COM DMQ$DISK:[DMQ$V10.USER.TEMPLATE] DMQ$INIT.TXT DMQ$DISK:[DMQ$V10.USER.TEMPLATE] DMQ$COM_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$COPY_LNM_TABLE.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$CREATE_GROUP.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$CUSTOMIZE.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$DEASSIGN.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$DETACH_PROCESS.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$FORCEX.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$FULLTEST.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$IVP.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$MENU.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$MRS_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$PROCESS_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$QTRANSFER_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$SBS_START.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$SET_LNM_TABLE.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$SHUTDOWN.COM DMQ$DISK:[DMQ$V10.EXE] DMQ$STARTUP.COM DMQ$DISK:[DMQ$V10.EXE] DMQ010.RELEASE_NOTES DMQ$DISK:[DMQ$V10.DOC] (continued on next page) B-14 DECmessageQ Files and Logical Names Installed on Your System DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-3_(Cont.)_Run-time_Kit_Files_______________________ File_Name___________________Location_______________________ DMQ_UCB_PROG_GUIDE.LINE DMQ$DISK:[DMQ$V10.DOC] DMQ$IVP.TLB DMQ$DISK:[DMQ$V10.LIB] DMQ$CHECK_LICENSE.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$COM_SERVER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DNSLOAD.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DQF_CONTROL.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DQF_UTIL.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DSPBLK.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$DUMP_GNT.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$ENTRYRTLV10.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$EXECRTLV10.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$FORCEX.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$IVP.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$JTEST.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$LIST_PROCS.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$LLS_VERIFY.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$LOADER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$LOOP.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$MONITOR.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$MRQ_TEST.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$MRS_SERVER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$MSGSHRV10.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$PSSVFY.EXE DMQ$DISK:[DMQ$V10.EXE] (continued on next page) DECmessageQ Files and Logical Names Installed on Your System B-15 DECmessageQ Files and Logical Names Installed on Your System B.1 File Names Table_B-3_(Cont.)_Run-time_Kit_Files_______________________ File_Name___________________Location_______________________ DMQ$QFLUSH.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$QMENU.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$QTRANSFER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$SBS_EXAMPLE.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$SBS_SERVER.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$SINK.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$SRC.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$TEST.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$TEST_LOCATE.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$VALID.EXE DMQ$DISK:[DMQ$V10.EXE] DMQ$PSSRTL.EXE______________DMQ$DISK:[DMQ$V10.USER.TEMPLATE] B.2 Logical Names DECmessageQ creates named logical name tables that are mapped into the context of processes that use DECmessageQ. See the DECmessageQ Management and Configuration Guide for VMS for a complete list of logical names. B-16 DECmessageQ Files and Logical Names Installed on Your System