DECmessageQ___________________________________ Installation and Configuration for OpenVMS February 1995 This document contains instructions for installing DECmessageQ for OpenVMS on AXP and VAX systems. Revision/Update Information: This is a revised document. Software Version: DECmessageQ for OpenVMS AXP, Version 3.0 DECmessageQ for OpenVMS VAX, Version 3.0 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ February 1995 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. © Digital Equipment Corporation 1995. All Rights Reserved. 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: AXP, CDD, DECmessageQ, DECnet, DECstation, OpenVMS, PATHWORKS, RX, TK, ULTRIX, VAX, VAX C, VAXELN, VAXstation, VMS, VMScluster, and the DIGITAL logo. 88open is a registered trademark of 88open Consortium, Ltd. AppleShare, AppleTalk, Macintosh, and MacTraps are registered trademarks of Apple Computer, Inc. Hewlett- Packard and HP are registered trademarks and HP 9000- 300 and HP-UX are trademarks of Hewlett-Packard Company. IBM and OS/2 are registered trademarks of International Business Machines Corporation. Motif is a registered trademark of Open Software Foundation, Inc. MS-DOS and Windows are registered trademarks and Excel is a trademark of Microsoft Corporation. MultiNet is a registered trademark of TGV, Inc. NFS, Sun, and SunOS are registered trademarks of Sun Microsystems, Inc. Pathway Access is a registered trademark of The Wollongong Group, Inc. PostScript is a registered trademark of Adobe Systems, Incorporated. THINK C is a trademark of Symantec Corporation. UNIX is a registered trademark of UNIX System Laboratories, Inc. Xerox is a registered trademark of Xerox Corporation. This document is available on CDROM. This document was prepared using VAX DOCUMENT, Version 2.1. ________________________________________________________________ Contents Preface.................................................. xvii 1 Preparing for DECmessageQ Installation Overview ............................................. 1-1 Introduction....................................... 1-1 In This Chapter.................................... 1-1 DECmessageQ Basic Concepts and Terms ................. 1-2 Overview........................................... 1-2 Supported Protocols................................ 1-2 Additional Terms................................... 1-3 User Processes..................................... 1-4 DECmessageQ Server Processes....................... 1-5 Symbolic Names..................................... 1-7 Global Memory...................................... 1-7 Configuring Distributed Systems Using DECmessageQ .... 1-8 Design Paradigms................................... 1-9 Traditional Functional Model.................... 1-9 Object-Oriented Methodology..................... 1-10 Determining Queue Sizes............................ 1-11 Simulating Worst-Case Load Scenario................ 1-12 Failover Provisions................................ 1-13 Design Summary..................................... 1-13 Getting Ready to Install DECmessageQ ................. 1-14 In This Section.................................... 1-14 Checking Media Contents............................ 1-14 Reading Release Notes.............................. 1-14 Verifying Required Operating System Components..... 1-15 Installing Optional Software for OpenVMS Systems... 1-16 License Inclusion with Product Kit................. 1-16 Licensing Requirements............................. 1-16 Registering the License............................ 1-17 iii Loading the License for a VMScluster............... 1-19 System Parameters and Memory Allocation Requirements......................................... 1-20 Checking System Parameter Values................... 1-20 Calculating Values for GBLPAGES and GBLSECTIONS.... 1-21 Installation Procedure Requirements .................. 1-21 In This Section.................................... 1-21 Installation Time.................................. 1-23 Privileges......................................... 1-23 Disk Space......................................... 1-24 Process Account Quotas............................. 1-25 VMSINSTAL Requirements............................. 1-25 System Backup...................................... 1-25 Considerations for OpenVMS Systems ................... 1-26 Upgrade............................................ 1-26 Concurrent Versions................................ 1-26 2 Installing DECmessageQ Overview ............................................. 2-1 Introduction....................................... 2-1 In This Chapter.................................... 2-1 The Installation Procedure ........................... 2-2 In This Section.................................... 2-2 Simplified VMSINSTAL Log........................... 2-3 Invoking VMSINSTAL................................. 2-6 Confirming Backup.................................. 2-7 Selecting Release Notes Option..................... 2-7 Selecting Kit Type................................. 2-8 Confirming License Registration.................... 2-8 Installing DECmessageQ Kits........................ 2-9 Installing OpenVMS Help Files...................... 2-9 Specifying a Device................................ 2-10 Selecting Run-Time Libraries on VAX Systems........ 2-11 Running IVP ....................................... 2-11 Purging Files...................................... 2-12 Viewing Informational Messages..................... 2-12 Installation Error Messages .......................... 2-13 In This Section.................................... 2-13 Major Failure Messages............................. 2-14 Error Conditions................................... 2-14 Additional Information............................. 2-14 Post-Installation Tasks for DECmessageQ .............. 2-14 iv Editing System Startup and Shutdown Files.......... 2-15 Configuring and Managing the System................ 2-15 Determining and Reporting Problems................. 2-15 Upgrading to DECmessageQ Version 3.0 ................. 2-16 In This Section.................................... 2-16 Purpose of Upgrade................................. 2-16 Conversion Requirements............................ 2-17 Conversion Major Steps............................. 2-18 Executing DMQ$CVT_V2TO3 Utility.................... 2-18 Using the Conversion Main Menu..................... 2-18 Converting One Bus or Group..................... 2-20 Performing Manual Conversion.................... 2-22 A Sample Installation for OpenVMS VAX Full Development Kit for VAX Systems ................. A-1 Running IVP .......................................... A-14 B Sample Installation for OpenVMS AXP Full Development Kit ................................. B-1 Installation Verification Procedure .................. B-14 C Sample DMQ$INIT.TXT File D Files Installed on Your System AXP Development Base Kit Files ....................... D-2 AXP Run-Time Only Kit Files .......................... D-11 VAX Development Base Kit Files ....................... D-15 VAX Run-Time Only Kit Files .......................... D-25 Index v Examples 1-1 Running the VMSLICENSE Utility ............... 1-17 A-1 Sample Full Development Kit Installation ..... A-1 B-1 Sample Full Development Kit Installation ..... B-1 Figures 1-1 DECmessageQ Multiplatform Support ............ 1-3 Tables 1-1 Minimum Required System Parameter Values ..... 1-21 2-1 Installation Steps ........................... 2-2 D-1 Standard AXP Development Base Kit Files ...... D-2 D-2 Optional AXP Development Base Kit Files ...... D-10 D-3 Standard AXP Run-Time Only Kit Files ......... D-11 D-4 Optional AXP Run-Time Only Kit Files ......... D-14 D-5 Standard VAX Development Base Kit Files ...... D-15 D-6 Optional VAX Development Base Kit Files ...... D-24 D-7 Standard VAX Run-Time Only Kit Files ......... D-25 D-8 Optional VAX Run-Time Only Kit Files ......... D-28 vi ________________________________________________________________ Preface What Is DECmessageQ DECmessageQ software is a programming tool that enables applications to send and receive messages among networked systems through queued messaging. A message queue is an intermediate storage point between applications that allows message data to be stored in memory or written to disk for recoverability. DECmessageQ software integrates applications running on Windows and Windows NT PCs, UNIX and OpenVMS workstations and servers, and Macintosh systems. DECmessageQ uses a single application programming interface (API) for all environments (except for IBM mainframes) supporting application portability and insulating applications from changes in operating system and network software. DECmessageQ also offers productivity tools for developers to simulate, capture, and replay messages for testing purposes without creating a distributed application test environment. Why Use DECmessageQ DECmessageQ software enhances: o Productivity by providing a standard integration approach that speeds development and insulates applications from changes in network and operating system software. o Portability by offering an application programming interface for building applications that run in all industry-leading environments. xvii o Simplicity by providing a common communication mechanism for distributed applications to send and receive messages. o Reliability by offering a simple and reliable queuing mechanism for message delivery. o Interoperability by integrating UNIX, Windows NT, OpenVMS, Macintosh, MS-DOS, and OS/2 applications. What Is in Your Kit In addition to your DECmessageQ license certificate, you receive a distribution kit containing: Media The distribution media appropriate for your system SPD/SSA Software Product Description and System Support Addendum describing the supported environments Cover letter Instructions for printing late-breaking news about this release Documentation Introduction to Messaging Installation and Configuration Guide Programmer's Guide Online help Where to Call for Help DECmessageQ software is covered by a one-year software warranty. If you experience a problem with DECmessageQ, you can call Digital Equipment Corporation (Digital) Customer Support Center at 1-800-DIGITAL (1-800-344-4825) for assistance 24 hours a day, 7 days a week. Please have your DEC number ready when you call. In addition to the one year warranty, Digital offers a variety of software support options for DECmessageQ. To obtain more information about purchasing a support contract, contact your local Digital sales representative. xviii What Is New in Version 3.0 The following are the most important new and enhanced features of DECmessageQ Version 3.0: o The DMQ$INIT.TXT file contains major changes, including significant changes to the Message Recovery Services (MRS) section. You must edit the DMQ$INIT.TXT file to configure your DECmessageQ Version 3.0 system. A conversion utility, DMQ$CVT_V2TO3.COM is provided to assist in moving from DECmessageQ for OpenVMS, Verion 2.1 group initialization file to DECmessageQ for OpenVMS, Version 3.0 group initialization files (see Chapter 2). o All recoverable journal files have been changed to a new common disk format. Earlier files must be deleted or converted to the new format prior to starting DECmessageQ for OpenVMS, Version 3.0. A conversion utility, DMQ$CUT_V2TO3.COM is provided to convert the format of journal files. Refer to Chapter 2 for information on how to use this utility. o The DMQ$STARTUP.COM command procedure will block until all requested servers have started and initialized. This differs from earlier releases, which returned control as soon as the servers started. o The DECmessageQ main menu, the DMQ$MGR_UTILITY menu, and the DMQ$MONITOR menu has new options. These menus now allow you to dynamically manage and monitor DECmessageQ configuration and operation without restarting the application. o Two new DECmessageQ server processes have been added. The JRN_SERVER (Journal Control Server) handles all auxiliary recovery journals. The EVENT_LOGGER (central error log facility) handles all error and trace logging. o Destination queue files (DQF) are dynamically created and deleted as needed by the recovery system, instead of being preallocated fixed-size files. xix o DECmessageQ Version 3.0 provides dynamic, menu-driven, debug and enable/disable output tracing that can be used to troubleshoot DECmessageQ problems with any process connected to a group. o A new queue quota makes it easier to control the amount of message buffer pool used by a particular queue. Documentation Conventions The following conventions are used in this guide: ________________________________________________________________ Convention_______Description____________________________________ Ctrl/x Ctrl/x indicates that you hold down the key labeled Ctrl while you press another key or a pointing device button. x A lowercase italic x indicates the generic use of a letter. For example, xxx indicates any combination of three alphabetic characters. n A lowercase italic n indicates the generic use of a number. For example, 19nn indicates a 4- digit number in which the last 2 digits are unknown. [ ] In format descriptions, brackets indicate optional elements. You can choose none, one, or all of the options. (Brackets are not optional, however, in the syntax of a directory name in a VMS file specification.) Items in brackets in a query are the system's default answers. Press the Return key in response to a prompt to accept the default answer. italic type Italic type emphasizes important information, indicates variables, and indicates complete titles of manuals. New terms are also shown in italic type and are defined in the glossary in DECmessageQ Introduction to Messaging. xx ________________________________________________________________ Convention_______Description____________________________________ boldface type Boldface type is used to distinguish routine call arguments and command parameters when they appear in text. system output The monospaced typeface is used to indicate system output or the exact name of a command, option, partition, pathname, directory, or file. This typeface also represents information displayed on the screen. UPPERCASE Words in uppercase indicate a command, the name of a file, the name of a file protection code, or an abbreviation for a system privilege. lowercase In format descriptions, words in lowercase indicate parameters or arguments to be specified by the user. $ A dollar sign indicates the default Digital Command Language (DCL) prompt. Return This command indicates that you press the key labeled Return on the keyboard. Enter This command indicates that you type the information that follows and press the Return _________________key.___________________________________________ xxi 1 ________________________________________________________________ Preparing for DECmessageQ Installation Overview Introduction This chapter discusses DECmessageQ basic terms and con- cepts as well as the planning, preparations, and systems requirements necessary for a successful installation of DECmessageQ software on OpenVMS systems. In This Chapter This chapter covers the following topics: o DECmessageQ Basic Concepts and Terms o Configuring Distributed Systems Using DECmessageQ o Getting Ready to Install DECmessageQ o System Parameters and Memory Allocation Requirements o Installation Procedure Requirements o Considerations for OpenVMS Systems DECmessageQ Installation and Configuration Guide for OpenVMS 1-1 Preparing for DECmessageQ Installation DECmessageQ Basic Concepts and Terms Overview DECmessageQ for OpenVMS is an implementation of a message queuing bus, which supports interprocess communications between independent tasks in a distributed environment. This tool provides a single interface to send and receive messages between applications running on computer systems from many vendors. The basic unit of DECmessageQ system management is the message queuing group, which consists of a number of queues and services. A DECmessageQ message queuing group is a collection of message queues that are used by an application and that share access to a local interprocess communications (IPC) facility and DECmessageQ servers. A message queuing group can also support more than one application. The message queuing group is connected to other message queuing groups on other systems by network links (remote messaging). Supported Protocols DECmessageQ has full heterogeneous communications capability for directing DECmessageQ messages across message queuing groups to any supported platforms. DECmessageQ for OpenVMS software resides on top of DECnet and Transmission Control Protocol/Internet Protocol (TCP/IP) networking software and various intra-CPU communications mechanisms. On VAX and AXP systems, DECmessageQ for OpenVMS supports communications using DECnet, TCP/IP, LU6.2 protocol, and Ethernet. 1-2 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Figure 1-1 illustrates that heterogeneous applications running in a multivendor network environment can send and receive messages through a DECmessageQ for OpenVMS server. Additional Terms In a DECmessageQ messaging environment, interprocess communication is enabled through the DECmessageQ message queuing bus. The message queuing bus is a set of DECmessageQ message queuing groups that are configured to communicate with each other. A message queue provides an area for an application to store and retrieve messages. A message queue is configured by the application developer and managed by DECmessageQ. To receive DECmessageQ messages, an application must be associated with at least one queue. Message queues can be thought of as attachment points on the message queuing bus. A message queue is a physical resource with a unique ID within a group and can be permanent or temporary. A permanent queue exists whether or not a process is attached to it. A temporary queue exists only when a process is attached to the message queuing bus. DECmessageQ supports three types of message queues: primary, secondary, and multireader. o Primary Queue (PQ) The primary queue acts as the main mailbox for a user process. A user process can have only one primary queue, although it may be associated with queues of other types. When the user process reads a message from its primary queue, the message is removed from the queue. Messages are read in first-in/first-out (FIFO) order unless another order is specified. o Secondary Queue (SQ) DECmessageQ Installation and Configuration Guide for OpenVMS 1-3 Preparing for DECmessageQ Installation The secondary queue acts as an alternate mailbox for the user process to receive messages. o Multireader Queue (MRQ) A multireader queue acts as a central mailbox that is used by several user processes (applications). Many user processes can simultaneously attach and read messages from a multireader queue. User Processes User processes are the application programs that communicate using DECmessageQ software. User processes running on the same system can share the same message queuing group or can reside in different groups. User processes running on different systems are defined in different groups. Remote applications communicate through cross-group communications. All user processes in a DECmessageQ for OpenVMS message queuing group share several sections of global memory, run-time libraries (RTLs), and are served by the following DECmessageQ server processes: 1-4 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation o COM server o SBS server o MRS server o CLS server o Link driver o Event logger o Journal server DECmessageQ Server Processes DECmessageQ for OpenVMS servers are detached processes that provide services in addition to basic message queuing. They implement portions of the DECmessageQ application programming inteface (API) or communicate with other DECmessageQ message queuing groups. Figure 1-2 shows the servers and other process components of a message queuing group. DECmessageQ Installation and Configuration Guide for OpenVMS 1-5 Preparing for DECmessageQ Installation o COM Server: The COM server creates and maintains the message queuing environment for the message queuing group and provides many of the DECmessageQ message-based services. The COM server also coordinates the actions of the link drivers such as cross-group communication. It contains a DECnet link driver that is used to communicate to other OpenVMS systems and older version of DECmessageQ software. o Message Recovery Services (MRS): The Message Recovery Services server manages the disk storage required to handle recoverable message traffic. The DECmessageQ message recovery system guarantees message delivery in the event of system, network, or application failures. Messages designated as recoverable are directed to an MRS server for storage and removal from storage when delivery is confirmed by a user or another MRS server. Refer to Chapter 6 for more information on MRS. o Selective Broadcast Services (SBS): The Selective Broadcast Services server controls the broadcasting of data between an application program and multiple receiving application programs. In addition, the SBS Server provides AVAIL/UNAVAIL message-based services. Refer to Chapter 7 for more information on SBS. o Client Lib Server (CLS): The Client Lib Server controls the access of the Windows-based client applications to the message queuing functionality available using DECmessageQ for UNIX[[R]], Windows NT[[R]], or OpenVMS. Refer to the DECmessageQ Installation and Configuration Guide for OpenVMS for more information on the Client Lib Server. 1-6 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation o Link Drivers: A link driver provides transparent communications over a particular network transport. DECmessageQ for OpenVMS supports up to three link drivers simultaneously, as follows: o TCP/IP o DECnet to OSF/1[[R]] or ULTRIX[[R]] o DECnet to OpenVMS and DECmessageQ client groups (driver included in the COM server) o Journal Server: The journal server controls journal management functions handling opening, closing, and dumping of all auxiliary journal files. Refer to Chapter 11 for more information on journal management. Symbolic Names DECmessageQ can translate symbolic names into queue addresses. Symbolic queue names are defined in the group name table (GNT), the queue configuration table (QCT) in the DMQ$INIT.TXT file, and in the DMQ$TYPCLS.TXT file. Local symbols are stored in the global sections and global symbols are stored in the Distributed Name Service (DNS) namespace. Refer to Chapter 8 for more information. Global Memory The DECmessageQ global memory provides storage for queue names and addresses and allocates memory space for message queuing groups and message buffers. Refer to Chapter 5 for more information on how to configure global memory. DECmessageQ Installation and Configuration Guide for OpenVMS 1-7 Preparing for DECmessageQ Installation Configuring Distributed Systems Using DECmessageQ The basic unit of DECmessageQ system management is the message queuing group. Message queuing groups consist of several message queues and share access to a common set of DECmessageQ servers. Message queuing groups are connected to one another by network links. Management of each message queuing group is a relatively independant task. Therefore, it is best to assign each DECmessageQ message queuing group with a small set of application functions. Large or complex systems should be implemented as a network of queuing groups. On large OpenVMS systems, the task of installing software is often assigned to a system manager who may not have detailed knowledge of each installed product. The system manager must learn the system resources required by each application, such as the size of the paging file, and amount of global memory and disk space required. OpenVMS SYSGEN parameters may have to be increased to accommodate installation of additional applications. To run DECmessageQ and it applications, the system manager must configure the system with the appropriate resources to support the needs of all message queuing groups. While some DECmessageQ system parameters automatically adjust from default settings according to the load and available resources, the systems designer may have to make some decisions regarding DECmessageQ resources and then set the parameters accordingly. Queues need to be assigned to particular application services and various pools need to be sized. While this can be done in an iterative, ad-hoc way during the development stage, it also helps to have a well-planned design and system model, and to make sizing decisions based on this model. 1-8 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Design Paradigms There are many design paradigms for distributed systems. No matter which paradigm is used, it should produce an abstract description that describes the information used by the system, and the things that happen in the system. The abstract description is then transformed into a network of queues, application servers that read from the queues, and messages that flow between the application servers and encapsulate the characteristics and behavior. Each application server in a good design is assigned a specific function or a limited number of related functions to perform. Traditional Functional Model Using a traditional design methodology such as Yourdon /DeMarco[1], the system would be described by a series of data flow diagrams which show data flowing to and from abstract processes and data stores. When using such a methodology, once the system data flow is known, the process of breaking down the diagram into physical processes and messages can start. Often a one- to-one association between physical process and abstract process can be made; for example, a process bubble in the diagram becomes a physical process. In some cases, several actions will be assigned to one physical process. You should also consider the storage of data in media under application control, such as shared memory, disk files, or data base packages. The details of the choice for the type of storage are driven by access time requirements: how long the data must be stored, and how the data will be used. The decision to place data in some type of data store, necessitates the assignment of a physical process to manage writes or reads and writes to the data store. Data stores are often local to a particular computer or network ___________________ [1] See the Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design by Edward Yourdon and Larry L. Constantine, Prentice-Hall, Inc., 1979. DECmessageQ Installation and Configuration Guide for OpenVMS 1-9 Preparing for DECmessageQ Installation node. The assignment of a server process to manage the store and a design that buffers access to the server by message queuing leads to a design with wide distributed access, fast and deterministic access times, and good scalability. The location of physical processes on a network is sometimes well known because a data store managed by a service must be located on a particular node. In other cases, the decision to assign physical processes to network nodes is driven by load balancing considerations. Object-Oriented Methodology One of the difficulties that arise from a traditional design approach is that specification often becomes biased toward the flow of data rather than the understanding of the important underlying processes of the system. Object- oriented[2] analysis and design changes the focus from the data to the process, and produces a series of models in addition to the traditional functional model. The end result is a series of abstract "objects" and "methods". When object-oriented systems are implemented using DECmessageQ, each object is assigned to an application server process and a queue. The invokation of a method on an object corresponds to sending a message to an application server associated with the object. At this stage in the design, there is enough information to assign physical processes to DECmessageQ groups and to assign network node locations to those groups. ___________________ [2] "Object-Oriented Modeling and Design," Rambaugh, Blaha, Premerlani, Eddy, Lorensen, Prentice-Hall, Inc., 1991. 1-10 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Determining Queue Sizes In addition to the system flow, you need to determine expected arrival rates to key inputs of the system. One way to estimate this is to look at the expected or required response times to any particular action. So, if a input stream needs an response time of 0.5 seconds, you might expect that the arrival rate for that particular input might be 2 events per second. (The worst case then, as far as the system load, would be that the 2 events per second rate would be maintained over some relatively long period of time, say five minutes.) The sum of input rates from all the events to a particular service determines a maximum input rate (and queue size) that the service must handle. If the events are correlated closely to messages, then the input messaging rates to the system can be determined. The messaging rates for key inputs to the system, as well as the service rates for various processes, determine the queue size that the system needs to be configured to handle. A rough way to do this is to use the following calcula- tion[3] for each queue: Assume for the purposes of calculation that arrivals occur randomly and independently of one another, with an average arrival rate that can be somehow determined or estimated. Let, L = mean number of arrivals per time interval S = mean service time per arrival P = utilization = fraction of time service is busy = l * S Q = mean number of messages in the queue ___________________ [3] You can use more sophisticated analyti- cal formulas; for example, refer to the Queueing Systems, Volume 1: Theory by Leonard Kleinrock, John Wiley & Sons, Inc., 1975. DECmessageQ Installation and Configuration Guide for OpenVMS 1-11 Preparing for DECmessageQ Installation Then for most systems, the value of "q" should be between the two following values: Q_DET = P/(1-P) - P * P/2 * (1-P)) assumes constant service times Q_EXP = P/(1-P) assumes random service times In many systems, you will need to consider the effect of server outages. Server outages occur when a server is unable to perform its function because it is explicitly shut down or because a key network link is down. When the server is down, the application must must be able to take some type of action, such as storing the messages to be forwarded when the server becomes active again. Queue sizing analysis should also be done for the case when the server is down, and for when it is restarting. The queuing load during restart operations is often significantly larger than during normal operation. In the case where the service and arrival rates are not known, the design and implementation work can still proceed by using the trial-and-error method. If there is not enough of a particular resource, add more and try again until the operation works. Simulating Worst-Case Load Scenario Another scheme to determine the resources that are required is to write input driver programs that simulate the worst-case load. Test drivers of this type are highly recommended, even when a complete systems design is available. Test drivers can be used in many phases of the project cycle, including design, modeling, implementation, and testing. Servers can be also simulated, in a simple way, by programs coded as simple loops that read from an input queue, then pause for some interval before reading the next item. Using this methodology, you can build a high- level simulation that runs on the hardware and network (or a very similar network) on which the target application will run. Examining the resources used by the model can be very helpful in sucessfully sizing the production system. 1-12 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Failover Provisions Failover provisions must be taken into account early in the design process. Failover requires at least operational planning, and in most cases, requires an application code to be written to support the failover process. If failover capability is required, it should be designed as an integral part of the application. It is difficult to "back fit" a failover process once an application is in production. In addition, recovery journals reside on some physical media. This media must be accessible to both the primary node where the application is originally running and the backup node to which the application will fail over. In a VMScluster, the media is easily accessible because access to disks can span network nodes. Outside of a VMScluster, it is still possible by physically moving or copying the media. Refer to DECmessageQ Installation and Configuration Guide for OpenVMS for more information on failovers. Design Summary The following list summarizes basic questions you should consider when planning a distributed system that uses DECmessageQ: o Which applications must communicate with each other? o Which computer systems do these applications run on? o Where are the computer systems located? o What networks and operating systems are these computer systems using? o Where are users located? o What backup/failover capability is needed? o How will applications be developed and tested? o What is an average transaction rate? o What is the depth of backing storage? o What are the service/arrival rates? o What is the application data flow? DECmessageQ Installation and Configuration Guide for OpenVMS 1-13 Preparing for DECmessageQ Installation o What are failover provisions to back up the applica- tion? Getting Ready to Install DECmessageQ In This Section This section describes: o Checking Media Contents o Reading Release Notes o Verifying Required Operating System Components o Installing Optional Software for OpenVMS Systems o License Inclusion with Product Kit o Licensing Requirements o Registering the License o Loading the License for a VMScluster Checking Media Contents Your bill of materials (BOM) and Indented Bills Report (BIL) specify the number and contents of your media kit. Be sure to verify the contents of your kit with this information. If your kit is damaged or if you find that parts of it are missing, contact Digital for a replacement kit. Reading Release Notes DECmessageQ provides online release notes. Digital strongly recommends that you read the release notes before starting the installation. Refer to a copy of the release notes provided with your DECmessageQ software kit. You can also access the release notes online as described in The Installation Procedure. ________________________Note ________________________ Significant new features had been added to this DECmessageQ release that require file format conversions. Refer to Upgrading to DECmessageQ 1-14 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Version 3.0 for instructions on upgrading to DECmessageQ for OpenVMS, Version 3.0. _____________________________________________________ Verifying Required Operating System Components You must install one of the following operating system software prior to installing DECmessageQ: o DECmessageQ for OpenVMS AXP On AXP systems, DECmessageQ requires OpenVMS AXP. o DECmessageQ for OpenVMS VAX The OpenVMS VAX software comes with a variety of support options or classes. Classes include such features as networking and VAX RMS Journaling. For specific versions of the operating systems supported and a complete list of the available classes, refer to the Software Support Addendum (SSA) that accompanies the Software Product Description (SPD). DECmessageQ Installation and Configuration Guide for OpenVMS 1-15 Preparing for DECmessageQ Installation Installing Optional Software for OpenVMS Systems If you plan to use DECmessageQ for OpenVMS software to communicate with UNIX systems, ULTRIX systems, or other systems that support the Transmission Control Protocol /Internet Protocol (TCP/IP) and NFS protocol suites, install one of the following products on your system prior to installing DECmessageQ software: o DEC TCP/IP Services for OpenVMS o Wollongong Pathway Access[[R]] for OpenVMS o TGV MultiNet[[R]] for OpenVMS Refer to the Software Support Addendum (SSA) that accompanies the Software Product Description (SPD) for specific version numbers of networking software. License Inclusion with Product Kit If you ordered the license and media together, Digital ships the License Product Authorization Key (License PAK) with the media kit; otherwise, Digital ships the license PAK separately to a location provided on your license order. Licensing Requirements Before you install and run DECmessageQ Version 3.0 on a newly licensed node or VMScluster, you must first register a License Product Authorization Key (License PAK) by using the License Management Facility (LMF). If you are installing the DECmessageQ software as an update on a node or cluster already licensed for this software, you have already completed the License PAK registration requirements. You must register and load your license for DECmessageQ before you start the installation in order to run the Installation Verification Procedure (IVP) and use the software. If you are installing prerequisite or optional software along with DECmessageQ, review the PAK status and install the PAKs for any prerequisite or optional software before you install DECmessageQ. 1-16 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Registering the License To register a license under OpenVMS: __________________________________________________________ Step________________________Action________________________ 1. Log in to the SYSTEM account. 2. Do one of the following: Invoke the SYS$UPDATE:VMSLICENSE.COM procedure. When it prompts you for information, respond with data from your License PAK. Or, at the DCL prompt, enter the LICENSE REGISTERcommand with the appropriate qualifiers that correspond to License PAK information. 3. If you plan to use DECmessageQ on more than one node in a VMScluster configuration, perform a license load on the other nodes after you complete this installation. ____See_Chapter_2_for_more_information.___________________ For complete information on using LMF, refer to the OpenVMS License Management Utility Manual. Example 1-1 shows how to use the VMSLICENSE utility. Example 1-1 Running the VMSLICENSE Utility ------------------------------------------------------------------------------- $ set default sys$update $ @vmslicense VMS License Management Utility Options: 1. REGISTER a Product Authorization Key 2. AMEND an existing Product Authorization Key 3. CANCEL an existing Product Authorization Key 4. LIST the Product Authorization Keys 5. MODIFY an existing Product Authorization Key 6. DISABLE an existing Product Authorization Key (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS 1-17 Preparing for DECmessageQ Installation Example 1-1 (Cont.) Running the VMSLICENSE Utility 7. DELETE an existing Product Authorization Key 8. COPY an existing Product Authorization Key 9. MOVE an existing Product Authorization Key 10. ENABLE an existing Product Authorization Key 11. SHOW the licenses loaded on this node 12. SHOW the unit requirements for this node 99. EXIT this procedure Type '?' at any prompt for a description of the information requested. Press Ctrl/Z at any prompt to exit this procedure. Enter one of the above choices [1] Do you have your Product Authorization Key? [YES] Use the REGISTER option to add a new license to a license database. A Product Authorization Key (PAK) provides the product name and information you need to register the license. You must enter all the information provided by your PAK exactly as it appears. PAK ID: Issuer [DEC] Authorization Number [] PRODUCT ID: Product Name []dmq-dev Producer [DEC] NUMBER OF UNITS: Number of Units []100 KEY LEVEL: Version [] Product Release Date []1-dec-1994 KEY TERMINATION DATE: Key Termination Date [] RATING: Availability Table Code []H Activity Table Code [] (continued on next page) 1-18 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Example 1-1 (Cont.) Running the VMSLICENSE Utility MISCELLANEOUS: Key Options []alpha Product Token [] Hardware-Id [] Checksum [] License Database File: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB Issuer: DEC Authorization: Producer: DEC Product Name: DMQ-DEV Units: 100 Release Date: 1-DEC-1994 Version: Termination Date: Availability: H Activity: Options: ALPHA Token: Hardware ID: Checksum: Is this information correct? [YES] Registering DMQ-DEV license in SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB... Do you want to LOAD this license on this system? [YES] ------------------------------------------------------------------------------ Enter 99 to exit the utility. Loading the License for a VMScluster To use DECmessageQ on a VMScluster configuration, you must load the license for DECmessageQ on each node in the cluster. For example, to install a development kit on an AXP system, enter the following at the system prompt: $ License Load DMQ-DEV DECmessageQ Installation and Configuration Guide for OpenVMS 1-19 Preparing for DECmessageQ Installation To install a run-time only kit, enter the following at the system prompt: $ License Load DMQ-RTO You have to load the DECmessageQ license (for a VMScluster) only once. It stays loaded after reboots. ________________________Note ________________________ The LICENSE LOAD command will fail if the license has not been registered on the cluster. _____________________________________________________ System Parameters and Memory Allocation Requirements This section describes how to: o Check system parameter values o Find minimum required system parameter values o Find the number of free global pages and global sections Checking System Parameter Values To check the values of your system parameters, use the SYSGEN utility, as shown in the example below: $ RUN SYS$SYSTEM:SYSGEN SYSGEN> SHOW GBLPAGFIL SYSGEN> EXIT For DECmessageQ, the values displayed should equal or exceed the value of each system parameter listed in Table 1-1. This table uses the symbol n to represent the current setting value. The number n plus the number listed in the Minimum Value column of the table is the minimum required system parameter values for the DECmessageQ installation. Depending on the kinds of programs and applications running at your site, you may need higher values for some settings. 1-20 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Table_1-1_Minimum_Required_System_Parameter_Values________ System Parameter_____Minimum_Value_______________________________ GBLPAGES[1] n + 2000 GBLPAGFIL n + 1000 GBLSECTIONS[1]n + 18 [1]The_values_listed_for_these_system_parameters_represent the number of free global pages and global sections required for the installation, not the total number you need to run your system and other software. __________________________________________________________ Calculating Values for GBLPAGES and GBLSECTIONS To install and run DECmessageQ, you must have sufficient free global pages and global sections. To find the number of free global pages and global sections, use the WRITE command with the F$GETSYI lexical function. 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 "Checking System Parameter Values", you need not increase the values for these parameters. If the value of free global pages or global sections is less than the value in "Checking System Parameter Values", you must increase the system parameter setting. To increase the GBLPAGES and GBLSECTIONS system parameters, use the AUTOGEN utility. Installation Procedure Requirements In This Section This section describes: o Installation Time o Privileges DECmessageQ Installation and Configuration Guide for OpenVMS 1-21 Preparing for DECmessageQ Installation o Disk Space o Process Account Quotas o VMSINSTAL Requirements o System Backup 1-22 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Installation Time The following table includes the approximate times needed for installing DECmessageQ for OpenVMS, Version 3.0. Note that actual times will vary depending on the type of media and system configuration. Times given in this table include installing the DECmessageQ development kit and running the Installation Verification Procedure (IVP). Both systems given as examples are standalone systems. __________________________________________________________ _____________Examples_____________ Time Platform____(Approx.)___System________Time________________ AXP 35-50 DECstation 35 minutes minutes 3000 Model 500 VAX 1-1.5 VAXstation 50 minutes hours 4000 Model ________________________90________________________________ Privileges To install DECmessageQ, you must be logged on to an account that has either SETPRV or at least the following privileges: ALTPRI GRPNAM SYSLCK CMKRNL NETMBX SYSNAM DETACH OPER SYSPRV EXQUOTA PSWAPM TMPMBX GROUP SYSGBL WORLD ________________________Note ________________________ The VMSINSTAL command procedure turns off the BYPASS privilege at the start of the installation. _____________________________________________________ DECmessageQ Installation and Configuration Guide for OpenVMS 1-23 Preparing for DECmessageQ Installation Disk Space The following table summarizes DECmessageQ disk space requirements: __________________________________________________________ Blocks Used During Blocks Required After Kit_____________________InstallatioInstallation___________ AXP_Platform______________________________________________ OpenVMS AXP Development 115,000 110,000 OpenVMS AXP Run-Time 45,000 40,000 only OpenVMS Help Library 400 (optional) TCP/IP support 1,000 (optional) LU6.2 support 10,000 (optional) __________________________________________________________ VAX_Platform______________________________________________ OpenVMS VAX Development 50,000 45,000 OpenVMS VAX Run-Time 35,000 20,000 only OpenVMS Help Library 400 (optional) TCP/IP support 1,000 (optional) LU6.2 support 10,000 (optional)________________________________________________ To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt: $ SHOW DEVICE SYS$SYSDEVICE 1-24 DECmessageQ Installation and Configuration Guide for OpenVMS Preparing for DECmessageQ Installation Process Account Quotas The account you use to install DECmessageQ must have suf- ficient quotas to enable you to perform the installation. The following table lists the process quotas required for the installation account executing the VMSINSTAL command procedure. __________________________________________________________ Account Quota_______#Value________________________________________ ASTLM 24 BALM 18 BYTLM 18,000 DIOLM___________18________________________________________ Use the AUTHORIZE utility to verify and change user account quotas. User account quotas are stored in the SYSUAF.DAT file. VMSINSTAL Requirements When you invoke VMSINSTAL, it checks the following: o Your default device and directory to SYS$UPDATE o Your account privileges o Your account quotas o Any users 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. To stop the installation process and correct the situation, enter NO or press . Correct the problem and restart the installation. System Backup At the beginning of the installation, VMSINSTAL asks if you have backed up your system disk. Digital recommends that you back up the system disk before installing any software. You should also back up the target disk where DECmessageQ will be installed. DECmessageQ Installation and Configuration Guide for OpenVMS 1-25 Preparing for DECmessageQ Installation 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 (BACKUP) in the System Management Subkit. Considerations for OpenVMS Systems Upgrade Refer to Chapter 2 for instructions on upgrading to DECmessageQ for OpenVMS, Version 3.0. Chapter 2 also provide information on how to access the online release notes which have additional information about upgrading your DECmessageQ for OpenVMS installation. Concurrent Versions DECmessageQ software allows different software ver- sions to run concurrently on the same OpenVMS system. However, running DECmessageQ for OpenVMS, Version 1.0, Version 2.0, Version 2.1 and Version 3.0 concurrently requires special considerations. For more information on running multiple versions concurrently on the same CPU, refer to the release notes. 1-26 DECmessageQ Installation and Configuration Guide for OpenVMS 2 ________________________________________________________________ Installing DECmessageQ Overview Introduction This chapter provides a detailed description of the DECmessageQ installation procedure and related topics. ________________________Note ________________________ To end 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 restart the installation. _____________________________________________________ See Appendix A for a sample installation on OpenVMS VAX systems. See Appendix B for a sample installation on OpenVMS AXP systems. In This Chapter This chapter describes: o The Installation Procedure o Installation Error Messages o Post-Installation Tasks for DECmessageQ o Upgrading to DECmessageQ Version 3.0 DECmessageQ Installation and Configuration Guide for OpenVMS 2-1 Installing DECmessageQ The Installation Procedure DECmessageQ for OpenVMS is installed by invoking the VMSINSTAL utility. This command procedure will prompt you for various installation options. When it is complete, the DECmessageQ for OpenVMS application is installed on your system. Next, you perform system configuration as described in Part II of this manual. ________________________Note ________________________ Make sure that the license for DECmessageQ is registered and loaded on your system before you begin installing DECmessageQ software. _____________________________________________________ In This Section This section describes the installation procedure, as summarized in Table 2-1: Table_2-1_Installation_Steps______________________________ Step________________________Action________________________ 1. Invoking VMSINSTAL 2. Confirming Backup 3. Selecting Release Notes Option 4. Selecting Kit Type 5. Confirming License Registration 6. Installing DECmessageQ Kits 7. Installing OpenVMS Help Files 8. Specifying a Device 9. Selecting Run-Time Libraries on VAX Systems 10. Running IVP 11. Purging Files 12._Viewing_Informational_Messages________________________ 2-2 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ Simplified VMSINSTAL Log The following is a simplified VMSINSTAL log illustrating the installation steps. For a sample of the complete VMSINSTAL log, refer to Appendix A. ---------------------------------------------------------------------------- $ set default sys$update $ @vmsinstal dmqvax030 DKA400:[DMQVAX030.KIT] VAX/VMS Software Product Installation Procedure V5.5-2 It is 28-NOV-1994 at 09:23. 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: DMQVAX V3.0 Beginning installation of DMQVAX V3.0 at 09:23 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. * Install the development kit [NO]: y Product: DMQ-DEV-V Producer: DEC Version: 3.0 Release Date: 1-DEC-1994 * Does this product have an authorization key registered and loaded? y ==================================================================== The DECmessageQ for OpenVMS VAX installation is divided into two parts: 1) Base kit 2) Demo programs directory ==================================================================== * Install base DECmessageQ kit [YES]? y * Install DECmessageQ demo programs [YES]? y * Install the help text [YES]? n * Enter the DEVICE where DECmessageQ will reside [SYS$SYSDEVICE]: dka200: %DMQVAXBLDC-I-DECTCP, DEC TCP/IP Link Driver and CLS Server will be built %DMQVAXBLDC-I-TGVTCP, TGV Multinet TCP/IP Link Driver and CLS Server will be built %DMQVAXBLDC-I-TWGTCP, Wollongong TCP/IP Link Driver and CLS Server will be built DECmessageQ Installation and Configuration Guide for OpenVMS 2-3 Installing DECmessageQ * Link with the standard VAXCRTL [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 OpenVMS VAX have now been asked. The installation will continue for approximately 20-90 minutes, depending on load, CPU type and kit media. ======================================================================= %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... ...Linking DMQ$SET_LNM_TABLEC30 %DMQVAXBLDC-I-LINKALL, Link all DECmessageQ for OpenVMS VAX images .... %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 DEMO_BUILD - Build the DECmessageQ Demonstration Software. %DEMO_BUILD-I-DONE, DECmessageQ demonstration software built. ...Linking DMQ$EXECRTLV30 (DMQ$EXECRTL) ...Linking DMQ$PSSRTL-VAXV30 (DMQ$PSSRTL) ...Linking DMQ$ENTRYRTLV30 (DMQ$ENTRYRTL) ...Linking DMQ$MSGSHRV30 (DMQ$MSGSHR) ...Linking DMQ$COM_SERVER ...Linking DMQ$EVENT_LOGGER ...Linking DMQ$JRN_SERVER ...Linking DMQ$SBS_SERVER ...Linking DMQ$MRS_SERVER ...Linking DMQ$UCX_TCPIP_LD ...Linking DMQ$TGV_TCPIP_LD ...Linking DMQ$TWG_TCPIP_LD ...Linking DMQ$DECNET_LD ...Linking DMQ$CLS_DECNET ...Linking DMQ$CLS_TGV ...Linking DMQ$CLS_TWG ...Linking DMQ$CLS_UCX ...Linking DMQ$LOADER ...Linking DMQ$CHECK_LICENSE ...Linking DMQ$SET_LNM_TABLEV30 ...Linking DMQ$FORCEX ...Linking DMQ$LLS_VERIFY ...Linking DMQ$LOOP ...Linking DMQ$MONITOR ...Linking DMQ$TEST 2-4 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ ...Linking DMQ$MRQ_TEST ...Linking DMQ$IVP ...Linking DMQ$SBS_EXAMPLE ...Linking DMQ$PSSVFY ...Linking DMQ$MGR_UTILITY ...Linking DMQ$DSPBLK ...Linking DMQ$DNSLOAD ...Linking DMQ$TEST_LOCATE ...Linking DMQ$QMENU ...Linking DMQ$VALID ...Linking DMQ$SRC ...Linking DMQ$SINK ...Linking DMQ$JTEST ...Linking DMQ$QTRANSFER ...Linking DMQ$CVT_V2TO3_JMSG ...Linking DMQ$CVT_V2TO3_RMSG ...Linking DMQ$WAIT_FOR_SERVICE ...Linking DMQTESTM %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... %DMQ-I-SETUP, Setting up DECmessageQ IVP environment %DMQ-I-SETUP, Clearing DECmessageQ logicals from process logical name table... Removing logical DMQ$DISK from table LNM$PROCESS_TABLE %DMQ-I-SETUP, Creating IVP group 0000_00001 in directory ..... %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 - 28-NOV-1994 9:58:31.49 %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 ...Starting DMQ_C_000000001 (COM Server) %DMQ-I-COMSTART, DECmessageQ COM Server DMQ_C_0000_00001 successfully started DECmessageQ Installation Verification Program. %DMQ-I-CLNUP, Cleaning up %DMQ-I-DELETEGRP, Deleting group files for bus 0000 group 00001 %DMQ-I-CLNUP, Clearing logical name table DMQ$LNM_0000_00001 %DMQ-S-SUCCESS, DECmessageQ for VMS IVP successfully completed. Installation of DMQVAX V3.0 completed at 10:02 VMSINSTAL procedure done at 10:02 DECmessageQ Installation and Configuration Guide for OpenVMS 2-5 Installing DECmessageQ --------------------------------------------------------------------------- The following sections provide detailed description of the VMSINSTAL steps. Invoking VMSINSTAL To invoke VMSINSTAL, use the following command: @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 one of the following installation names: DMQAXP030 for AXP systems DMQVAX030 for VAX systems device-name The name of the device on which you plan to mount the media. For example, DKA500: is the device name for a CD-ROM reader. OPTIONS N An optional parameter indicating that you want to view or print the release notes before the installation. If you do not include the OPTIONS N parameter, VMSINSTAL does not ask you about the release notes. Digital recommends that you read the release notes before installing DECmessageQ. If you are restarting the installation and have already reviewed the release notes, you need not specify OPTIONS N. The following example invokes VMSINSTAL to install DECmessageQ from CD-ROM reader DKA500 and shows the system response. This example uses the OPTIONS N release note parameter. 2-6 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ $ @SYS$UPDATE:VMSINSTAL DMQAXP030 DKA500: OPTIONS N OpenVMS Alpha Software Product Installation Procedure V1.5 It is dd-mmm-yyyy at hh:mm. 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 during the installation procedure. Confirming Backup The procedure requests that you confirm system backup: * Are you satisfied with the backup of your system disk [YES]? Digital recommends that you always back up your system disk before performing an installation. If you are satisfied with the backup of your system disk, press . Otherwise, enter NO to discontinue the installation. After you back up your system disk, you can restart the installation. ________________________Note ________________________ DECmessageQ software can be installed on any disk. Be sure to backup the disk on which DECmessageQ is installed. _____________________________________________________ Selecting Release Notes Option After several informative messages, the procedure asks you to select a release notes option, as follows: %VMSINSTAL-I-RESTORE, Restoring product save set A ... 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]: DECmessageQ Installation and Configuration Guide for OpenVMS 2-7 Installing DECmessageQ 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. Next, VMSINSTAL displays the following question: * Do you want to continue the installation [N]?: %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. To continue the installation, enter Y. Otherwise, press . In either case, the release notes are copied to a file in the SYS$HELP directory as SYS$HELP:DMQAXP030.RELEASE_NOTES or SYS$HELP:DMQVAX030.RELEASE_NOTES. Selecting Kit Type Choose the development or the run-time only kit. * Install the development kit [NO]? y You have the option of choosing the run-time only kit. To install the development kit, register and load a Product Authorization Key (PAK). 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 ________________________ Before installing the demo programs, you must install a base kit on your system. _____________________________________________________ Confirming License Registration The DECmessageQ Version 3.0 software is released in two PAK versions: one for AXP systems and one for VAX systems. The PAK name designations are: o For AXP: DMQ-xxx o For VAX: DMQ-xxx-V 2-8 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ Respond to license registration queries. The following example shows the license information for the AXP development kit. Product: DMQ-DEV Producer: DEC Version: 3.0 Release Date: 1-DEC-1994) * 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 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, stop the installation, register and load your PAK, and then restart the installation. See Registering the License for information on responding to license queries when installing DECmessageQ on an OpenVMS VAX system. Installing DECmessageQ Kits The DECmessageQ for OpenVMS installation is divided into two parts: o Base kit o Demo programs directory You may select to install the kit and help file. * Install base DECmessageQ kit [YES]? y * Install DECmessageQ demo programs [YES]? y Installing OpenVMS Help Files You now have the option of installing OpenVMS help files. * Would you like the help text installed [YES]? DECmessageQ Installation and Configuration Guide for OpenVMS 2-9 Installing DECmessageQ The help library provides general DECmessageQ information online and is accessed by entering the following command at the DCL prompt: $ HELP DECMESSAGEQ The help library includes details on all server messages and application programming interface (API) routines, information for linking and compiling DECmessageQ applications, a list of the DECmessageQ logical names, and a description of the DECmessageQ utilities. Specifying a Device You must now enter the device where the DECmessageQ software will reside. * Enter the DEVICE where DECmessageQ will reside [SYS$SYSDEVICE]: The default device is SYS$SYSDEVICE, but you can install DECmessageQ on any disk. 2-10 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ ________________________Note ________________________ Installing DECmessageQ software on rooted directo- ries will produce unpredictable results. Specify a device name or a logical name of a device. _____________________________________________________ The system automatically builds the TCP/IP link drivers. The DEC TCP/IP link driver is the default. You can choose other link drivers by editing the DMQ$BOOT.COM command procedure. ________________________Note ________________________ DECmessageQ links to all supported TCP/IP link drivers that it finds. Therefore, TCP/IP must be installed and started prior to this installation. _____________________________________________________ Selecting Run-Time Libraries on VAX Systems Select the type of run-time library (RTL) you are going to use. DECmessageQ for OpenVMS VAX links with the VAX C RTL which comes in two variants, depending on which level of floating point precision is required, VAXCRTL (D float) or VAXCRTLG (G float). DECmessageQ does not use floating point instructions. Therefore, it is unaffected by which C RTL is selected. However, other products that link to DECmessageQ may require a particular C RTL. For example, Motif requires VAXCRTL. Type Y and press to install VAXCRTLG, or type N and press to install VAXCRTL. * Link with VAXCRTL instead of VAXCRTLG [YES]? Running IVP You may now choose to run the Installation Verification Procedure (IVP). * Do you want to run the IVP after the installation [YES]? The IVP for DECmessageQ verifies that the installation is successful. Digital recommends that you run the IVP. DECmessageQ Installation and Configuration Guide for OpenVMS 2-11 Installing DECmessageQ After DECmessageQ is installed, you can run the IVP independently to verify that the software is available on your system. You may need to run the IVP after a system failure to make sure that users can access DECmessageQ. Purging Files You now have the option to purge files from previous versions of DECmessageQ that are superseded by this installation. * Do you want to purge files replaced by this installation [YES]? Purging is recommended; however, if you need to keep files from a previous installation of this version of DECmessageQ software, enter NO in response to the question. Viewing Informational Messages The installation procedure now displays a number of informational messages that report on the progress of the installation. There are no further questions that require a user response. 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-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... ...Linking DMQ$SET_LNM_TABLEV30 %DMQVAXBLDC-I-LINKALL, Link all DECmessageQ for OpenVMS VAX images .... %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 . . %VMSINSTAL-I-MOVEFILES, files will now be moved to their target directories... 2-12 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ 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. Installation of DMQAXP V3.0 completed at hh:mm VMSINSTAL procedure done at hh:mm These messages indicate that the entire installation procedure is complete. ________________________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, log out and log in again. _____________________________________________________ ______________________ Warning ______________________ If you have been using a previous version of DECmessageQ and wish to continue to use your user areas, you MUST perform the upgrade conversion be- fore you can run your applications using DECmessageQ for OpenVMS, Version 3.0. Refer to Upgrading to DECmessageQ Version 3.0 for more information. _____________________________________________________ Installation Error Messages In This Section This section describes: o Error messages o Error conditions o Additional information DECmessageQ Installation and Configuration Guide for OpenVMS 2-13 Installing DECmessageQ Major Failure Messages If errors occur either during the installation 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 Version 3.0 has failed. If the IVP fails, you see these messages: The DECmessageQ V3.0 Installation Verification Procedure failed. %VMSINSTAL-E-IVPFAIL, The IVP for DECmessageQ V3.0 has failed. Error Conditions Any of the following error conditions may cause the installation to fail: 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 OpenVMS help library is currently in use. o The product license has not been registered and loaded. Additional Information For descriptions of the error messages generated by these conditions, refer to the OpenVMS documentation on system messages, recovery procedures, and OpenVMS software installation. For information on installation requirements, see Chapter 1. Post-Installation Tasks for DECmessageQ This section describes the tasks to be performed after installing DECmessageQ: o Editing System Startup and Shutdown Files o Configuring and Managing the System 2-14 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ o Determining and Reporting Problems Editing System Startup and Shutdown Files After DECmessageQ is installed, you can add automatic startup and shutdown command procedures to the SYSTARTUP and SYSHUTDOWN command procedures. Placing the DECmessageQ startup commands in SYSTARTUP automatically starts DECmessageQ when the OpenVMS system boots. Placing the DECmessageQ shutdown commands in SYSHUTDOWN causes a clean DECmessageQ shutdown on a OpenVMS system shutdown. Configuring and Managing the System See the DECmessageQ Installation and Configuration Guide for OpenVMS for information on the following tasks: o Modifying the system parameters to run DECmessageQ software and ensure optimal system performance o Modifying user account privileges and quotas o Tuning the system o Installing DECmessageQ software as a shared image Determining and Reporting Problems If you encounter a problem while using DECmessageQ, report it to Digital using the following software problem reporting procedures. 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 postpaid reader's comments form if the problem concerns the DECmessageQ documentation. There are two postpaid reader's comments forms at the end of each manual. Use the form from the manual in which you found the error. Include the section and page number. DECmessageQ Installation and Configuration Guide for OpenVMS 2-15 Installing DECmessageQ 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 previously indicated or follow instructions provided by Digital for reporting SPD nonconformance problems. Upgrading to DECmessageQ Version 3.0 In This Section This section describes: o Purpose of Upgrade o Conversion Requirements o Conversion Major Steps o Executing DMQ$CVT_V2TO3 Utility o Using the Conversion Main Menu o Converting One Bus or Group o Performing Manual Conversion Purpose of Upgrade To continue to use your DECmessageQ data files created with previous versions of DECmessageQ, you must perform the upgrade conversion before you can run your applica- tions using DECmessageQ for OpenVMS, Version 3.0. After you have successfully installed DECmessageQ for OpenVMS, Version 3.0 on your system, use the DMQ$CVT_ V2TO3.COM conversion utility to upgrade the group initialization file for a DECmessageQ Version V2.X message queuing group to the new DECmessageQ for OpenVMS Version 3.0 format. You can also build new DECmessageQ data files from very beginning by running the DECmessageQ management utilities as described in Chapters 3, 10 and 11. 2-16 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ Conversion Requirements The conversion utility has the following requirements: o DECmessageQ for OpenVMS, Version 3.0 must be success- fully installed. o The message queueing group you wish to convert must be down. This means that all processes using DECmessageQ for this group must be exited and the DECmessageQ server processes must be shut down. o Review DECmessageQ initialization defaults for new fields in the DMQ$INIT.TXT before the group is restarted. DECmessageQ Installation and Configuration Guide for OpenVMS 2-17 Installing DECmessageQ Conversion Major Steps The conversion utility performs the following steps which require some user input: 1. Asks the user what disk contains the DECmessageQ Version 2.X directory 2. Locates the existing groups on the given disk 3. Asks the user what disk contains the DECmessageQ Version 3.0 directory 4. Creates a configuration file used to track the conversion 5. Allows a user to select desired conversion options 6. Creates a new Version 3.0 directory tree 7. Converts DMQ$INIT.TXT and DMQ$TYPCLS.TXT files 8. Updates the include files and text libraries 9. Converts any DQF or SAF journal files for this group into Version 3.0 format Executing DMQ$CVT_V2TO3 Utility To execute the conversion utility, enter at the DCL prompt: $ @ddcu:[DMQ$V30.CVT]DMQ$CVT_V2TO3 This command invokes the DMQ$CVT_V2TO3 Utility and allows you to access the utility's menus. Using the Conversion Main Menu After you invoke the utility, the system displays the Conversion main menu. 2-18 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ Figure 2-1 shows the Conversion main menu. The main menu provides the following options: __________________________________________________________ Option_____Use_it_to...___________________________________ HELP Provide online help information about the utility. SETUP Locate the groups on the desired disk. Run the setup FIRST, before starting any conversions. This option asks you the needed questions to determine what disk drive holds the DECmessageQ Version 2 and Version 3 directories. The Version 2 directory is then searched for DECmessageQ groups. A list of the groups is created and placed in a configuration file. This configuration file is used throughout the conversion process to track the process. The configuration file is named DMQ$CVT_V2TO3_'node'.CFG. DECmessageQ Installation and Configuration Guide for OpenVMS 2-19 Installing DECmessageQ __________________________________________________________ Option_____Use_it_to...___________________________________ Each group entry in the configuration file carries a status field which is updated on the successful completion of each phase of the conversion. The states are described as follows: 1. NONE - Nothing has been done. 2. FILE - The new files have been created with DMQ$CREATE_GROUP. 3. INIT - The DMQ$INIT.TXT file has been converted. 4. SYMB - The DMQ$TYPCLS.TXT file has been converted. 5. MAKE - The include files and text libraries have been created. 6. RMSG - Recoverable messages in the DQF and SAF files have been converted. 7. DONE - Group conversion is completed. ALL Convert all groups to the new format. This menu option begins the automatic conversion of all DECmessageQ groups that were located in the SETUP. The conversion continues until all groups reach the DONE status, indicating completion. ONE Select either an entire bus (containing multiple groups) or one group to be converted. MANUAL Select each phase of the conversion for every group allowing you to walk through each phase ___________of_the_conversion._____________________________ Converting One Bus or Group Use the ONE option to pick a specific DECmessageQ bus or group to be converted. o By selecting a bus, the conversion utility automat- ically includes any groups matching the desired bus number. 2-20 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ o By selecting a group, you can pick a single bus/group for the conversion. When you select the ONE option, the CONVERT ONE BUS or GROUP menu is displayed. (Figure 2-2). From this menu you can select one of following two automatic operations: __________________________________________________________ Option_____Use_it_to...___________________________________ BUS Receive a list of the DECmessageQ bus/group configuration discovered during the SETUP step. You can then enter the desired bus number for the conversion. The selected groups are redisplayed and a final YES or NO confirmation question is asked before the utility begins operation. GROUP Display the same DECmessageQ bus or group configuration as described above. You can then enter a bus number followed by a group number. The selected group is redisplayed and a final YES or NO confirmation question is ___________asked_before_the_utility_starts._______________ DECmessageQ Installation and Configuration Guide for OpenVMS 2-21 Installing DECmessageQ For each bus or group, the status is maintained in the conversion configuration file. If some phase of the conversion suddenly ends, a correction can be made, and the process can be restarted. The conversion will continue from the point where it stopped. Performing Manual Conversion Use the MANUAL menu option to walk through each phase of the conversion. You can select each phase of the conversion process on an individual group basis. You are first asked to pick a bus or group from the configuration file. Once this selection is made, you can be manually select each phase of the conversion. ________________________Note ________________________ The manual operation of the utility depends on the configuration file created in the SETUP phase. Run SETUP from the conversion main menu before proceeding with the manual steps. _____________________________________________________ When you select the MANUAL option, the system provides the menu selections listed in (Figure 2-3). The following table describes the MANUAL menu functions: __________________________________________________________ Option_____Use_it_to...___________________________________ PICK Select a BUS/GROUP from the configuration file created in the SETUP phase. FILE Execute the DMQ$CREATE_GROUP procedure to create the directory tree and populate the DMQ$USER files. INIT Convert the DMQ$INIT.TXT file. All user-supplied information in the file is preserved. It is highly recommended to review this file before restarting the group. SYMB Convert the DMQ$TYPCLS.TXT file. 2-22 DECmessageQ Installation and Configuration Guide for OpenVMS Installing DECmessageQ __________________________________________________________ Option_____Use_it_to...___________________________________ MAKE Create the language include file and text libraries if you have a DECmessageQ development license loaded. RMSG Read any recoverable messages remaining in the SAF and/or DQF files and transfer these ___________messages_to_the_new_MRS_format.________________ ________________________Note ________________________ Select the PICK option first to choose a bus or group for the conversion steps. The PICK option sets a process logical name which points to a bus or group in the conversion configuration file. Each of the manual steps then translates this logical name to determine which bus or group is the target for the conversion operation. The state of the conversion is tracked in the configuration file. The file can be reviewed at any time using the SETUP option from the conversion main menu. Although not required, Digital recommends that you run each step in the top-down order given in the menu list. _____________________________________________________ DECmessageQ Installation and Configuration Guide for OpenVMS 2-23 A ________________________________________________________________ Sample Installation for OpenVMS VAX This appendix contains sample installations of the DECmessageQ software on OpenVMS VAX systems. Full Development Kit for VAX Systems Example A-1 is a sample installation for the DECmessageQ full development kit. This sample was run on a system that had no previous version of DECmessageQ installed. Example A-1 Sample Full Development Kit Installation $ set default sys$update $ @vmsinstal dmqvax030 DKA400:[DMQVAX030.KIT] VAX/VMS Software Product Installation Procedure V5.5-2 It is 28-NOV-1994 at 09:23. 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: DMQVAX V3.0 Beginning installation of DMQVAX V3.0 at 09:23 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS A-1 Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation ************************************************************** * * * DECmessageQ for OpenVMS VAX V3.0 * * * * * * Installation Procedure * * * * * * Copyright Digital Equipment Corporation 1990, 1994. * * All rights reserved. * * * * * * Restricted Rights: Use, duplication, or disclosure by the * * U.S. Government is subject to restrictions as set forth in * * subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR * * 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. * * * * This software is proprietary to and embodies the * * confidential technology of Digital Equipment Corporation. * * Possession, use, or copying of this software and media is * * authorized only pursuant to a valid written license from * * Digital or an authorized sublicensor. * * * ************************************************************** * Install the development kit [NO]: y Product: DMQ-DEV-V Producer: DEC Version: 3.0 Release Date: 1-DEC-1994 * Does this product have an authorization key registered and loaded? y ==================================================================== The DECmessageQ for OpenVMS VAX installation is divided into two parts: (continued on next page) A-2 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation 1) Base kit 2) Demo programs directory ==================================================================== * Install base DECmessageQ kit [YES]? * Install DECmessageQ demo programs [YES]? * Install the help text [YES]? n * Enter the DEVICE where DECmessageQ will reside [SYS$SYSDEVICE]: dka200: %DMQVAX-I-DECTCP, DEC TCP/IP Link Driver and CLS Server will be built %DMQVAX-I-TGVTCP, TGV Multinet TCP/IP Link Driver and CLS Server will be built %DMQVAX-I-TWGTCP, Wollongong TCP/IP Link Driver and CLS Server will be built ================== Select the VAX C RTL ====================== DECmessageQ for OpenVMS VAX links with the VAX C RTL which comes in two variants, depending on which level of floating point precision is required, VAXCRTL (D float) or VAXCRTLG (G float). Some programs and layered products require one or the other, in order to link correctly. DECmessageQ does not use floating point instructions and therefore is unaffected by which C RTL that is selected. However, the MOTIF based DECmessageQ utilities (i.e. dmqtestm & dmqlu62_control) will not be built if VAXCTRLG is selected since MOTIF requires VAXCRTL. =============================================================== * Link with VAXCRTL instead of VAXCRTLG [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 OpenVMS VAX have now been asked. The installation will continue for approximately 20-90 minutes, depending on load, CPU type and kit media. ======================================================================= (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS A-3 Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... ...Linking DMQ$SET_LNM_TABLEV30 %DMQVAX-I-LINKALL, Link all DECmessageQ for OpenVMS VAX images .... %DMQ-S-TBLCREATE, Created DECmessageQ LNM table DMQ$LNM_0000_00001 %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 ...Linking DMQ$EXECRTLV30 (DMQ$EXECRTL) ...Linking DMQ$PSSRTL-VAXV30 (DMQ$PSSRTL) ...Linking DMQ$ENTRYRTLV30 (DMQ$ENTRYRTL) ...Linking DMQ$MSGSHRV30 (DMQ$MSGSHR) ...Linking DMQ$COM_SERVER ...Linking DMQ$EVENT_LOGGER ...Linking DMQ$JRN_SERVER ...Linking DMQ$SBS_SERVER ...Linking DMQ$MRS_SERVER ...Linking DMQ$UCX_TCPIP_LD ...Linking DMQ$TGV_TCPIP_LD ...Linking DMQ$TWG_TCPIP_LD ...Linking DMQ$DECNET_LD ...Linking DMQ$CLS_DECNET ...Linking DMQ$CLS_TGV (continued on next page) A-4 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation ...Linking DMQ$CLS_TWG ...Linking DMQ$CLS_UCX ...Linking DMQ$LOADER ...Linking DMQ$CHECK_LICENSE ...Linking DMQ$SET_LNM_TABLEV30 ...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$MGR_UTILITY ...Linking DMQ$DSPBLK ...Linking DMQ$DNSLOAD ...Linking DMQ$TEST_LOCATE ...Linking DMQ$QMENU ...Linking DMQ$VALID ...Linking DMQ$SRC ...Linking DMQ$SINK ...Linking DMQ$JTEST ...Linking DMQ$QTRANSFER ...Linking DMQ$CVT_V2TO3_JMSG ...Linking DMQ$CVT_V2TO3_RMSG ...Linking DMQ$WAIT_FOR_SERVICE ...Linking DMQTESTM DEMO_BUILD - Build the DECmessageQ Demonstration Software. 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. (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS A-5 Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation ===================================================================== The DECmessageQ for OpenVMS VAX Installation has completed successfully. Before programs can access DECmessageQ for OpenVMS, a privileged user must configure a DECmessageQ group with DKA200:[DMQ$V30.EXE]- DMQ$CREATE_GROUP.COM. Then DKA200:[DMQ$V30.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 Installation and Configuration Guide" 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 DKA200:[DMQ$V30.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 DKA200:[DMQ$V30.EXE]. An extra copy of the Release Notes DMQVAX030.RELEASE_NOTES has been placed in DKA200:[DMQ$V30.DOC]. ===================================================================== %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... DECmessageQ for VMS IVP Command Procedure V3.0-01 %DMQ-I-SETUP, Setting up DECmessageQ IVP environment %DMQ-I-SETUP, Clearing DECmessageQ logicals from process logical name table... Removing logical DMQ$DISK from table LNM$PROCESS_TABLE (continued on next page) A-6 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation %DMQ-I-SETUP, Creating IVP group 0000_00001 in directory DKA200:[DMQ$V30.USER. 0000_00001] %CREATE-I-CREATED, DKA200:[DMQ$V30.USER.0000_00001] created %CREATE-I-CREATED, DKA200:[DMQ$V30.LOG.0000_00001] created %CREATE-I-CREATED, DKA200:[DMQ$V30.MRS.0000_00001] created %DMQ-I-COPYFILE, Copying DMQ$BOOT.COM %DMQ-I-COPYFILE, Copying DMQ$INIT.TXT %DMQ-I-COPYFILE, Copying DMQ$SET_SERVER_LOGICALS.COM %DMQ-I-COPYFILE, Copying DMQ$SET_SERVER_QUOTAS.COM %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-VAXV30.OBJ %DMQ-I-COPYFILE, Copying PSSSYNTAX.MAR %DMQ-I-COPYFILE, Copying P_ENTRY.H %DMQ-I-COPYFILE, Copying P_GROUP.H %DMQ-I-COPYFILE, Copying P_PROCES.H %DMQ-I-COPYFILE, Copying P_RETURN.H (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS A-7 Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation %DMQ-I-COPYFILE, Copying P_SYMBOL.H %DMQ-I-COPYFILE, Copying P_TYPECL.H %DMQ-I-COPYFILE, Copying SYCUSTOMIZE.COM %DMQ-I-COPYFILE, Copying DMQ.TLB %DMQ-I-COPYFILE, Copying DMQ.MLB ...Linking DMQ$PSSRTL0000_00001-VAXV30 (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 system 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 - 28-NOV-1994 9:58:31.49 Bus: 0000 Group: 00001 Disk: DKA200: Start Servers: Yes DMQ Version: DMQ$V30 User Area: DMQ$DISK:[DMQ$V30.USER.0000_00001] Log Area: DMQ$DISK:[DMQ$V30.LOG.0000_00001] PSS file: DMQ$USER:DMQ$PSSRTL0000_00001-VAXV30.EXE %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 %DMQ-W-NOGMTLNM, DMQ$GMT_OFFSET not set %DMQ-I-FORCEX, Forcing image termination on process "DMQ_C_000000001" %SYSTEM-W-NONEXPR, nonexistent process (continued on next page) A-8 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation ...Installing DMQ$MSGSHR ...Installing DMQ$EXECRTL ...Installing DMQ$PSSRTL ...Installing DMQ$ENTRYRTL ...Installing DMQ$SET_LNM %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 ...Starting DMQ_C_000000001 (COM Server) %RUN-S-PROC_ID, identification of created process is 2FA06F6F DmQ I 58:53.2 Time Stamp - 28-NOV-1994 9:58:53.23 DmQ I 58:53.2 DECmessageQ System Loader starting... DmQ I 58:55.0 Parsing PROFILE Table DmQ I 58:55.6 Parsing X-Group Configuration Table DmQ I 58:56.0 Parsing Routing Table DmQ I 58:56.0 Parsing CLS Table DmQ I 58:56.0 Parsing Buffer Pool Configuration Section DmQ I 58:56.1 Parsing Queue Configuration Table DmQ I 58:56.4 Parsing SBS Configuration Table DmQ I 58:56.4 Parsing MRS Configuration Table DmQ I 58:56.4 Parsing Group Name Table DmQ I 58:56.6 DECmessageQ load successfully completed -------------------------------------------------------------------- Waiting for requested servers to indicate they are ready for traffic -------------------------------------------------------------------- (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS A-9 Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation %DMQ_0000_00001-EVENT_LOGGER-I-Event Logger (V3.0-11) Starting at 28-NOV-1994 9:58:59.03 %DMQ_0000_00001-EVENT_LOGGER-I-Open DMQ$LOG:DMQ$EVL_0000_00001.LOG log file %DMQ_0000_00001-COM_SERVER-I-COM Server (V3.0-00) starting at 28-NOV-1994 9:58:49 %DMQ_0000_00001-COM_SERVER-I-Created MCS and LLS containing 790 pagelets %DMQ_0000_00001-COM_SERVER-I-Begin initial configuration database load %DMQ_0000_00001-COM_SERVER-I-Created 25 entry Group table containing 167 pagelets %DMQ_0000_00001-COM_SERVER-I-Group table contains 57 TCBs, 86 NTs and 250 RTs %DMQ_0000_00001-COM_SERVER-I-Created 200 entry Group Name Table containing 35 pagelets %DMQ_0000_00001-COM_SERVER-I-Automatic reset of counters at 28-NOV-1994 9:58:57 %DMQ_0000_00001-COM_SERVER-I-Group 1 (ONE) Initialized %DMQ_0000_00001-EVENT_LOGGER-I-Event Logger Initialized DmQ I 59:03.3 Time Stamp - 28-NOV-1994 9:59:03.37 DmQ I 59:03.3 Waiting for COM_SERVER DmQ I 59:03.3 Waiting for MRS_SERVER DmQ I 59:03.3 Waiting for SBS_SERVER DmQ I 59:03.3 Waiting for EVL_SERVER DmQ I 59:03.3 Waiting for JRN_SERVER %DMQ_0000_00001-JRN_SERVER-I-JRN Server (V3.0-06) Starting %DMQ_0000_00001-MRS_SERVER-I-MRS Server (V3.0-07) Starting %DMQ_0000_00001-SBS_SERVER-I-SBS Server (V3.0-07) Starting %DMQ_0000_00001-MRS_SERVER-I-Space alloted for 128 queues, 512 messages %DMQ_0000_00001-MRS_SERVER-I-Max DQF areas:1000, maximum size:512000 pages %DMQ_0000_00001-MRS_SERVER-I-Max SAF areas:1000, maximum size:512000 pages %DMQ_0000_00001-SBS_SERVER-I-SBS Server Initialized %DMQ_0000_00001-MRS_SERVER-I-MRS Server Initialized %DMQ_0000_00001-JRN_SERVER-I-JRN Server Initialized DmQ I 59:48.3 All servers responded %DMQ-I-COMSTART, DECmessageQ COM Server DMQ_C_0000_00001 successfully started DECmessageQ Installation Verification Program. Part I: Validate Call API ========================= (continued on next page) A-10 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation Test 1.1:PAMS_ATTACH_Q to Permanent Primary Q by number Attached to Primary Q 1.90 Test 1.2:PAMS_EXIT Test 2.1:PAMS_ATTACH_Q to Permanent Primary Q by name Attached to Primary Q 1.90 Test 2.2:PAMS_EXIT Test 3.1:PAMS_ATTACH_Q to Permanent Primary Q with a Secondary Q Attached to Primary Q 1.191 Attached to Secondary Q 1.192 Test 3.2:PAMS_EXIT Test 3.3:PAMS_EXIT Test 4.1:PAMS_ATTACH_Q to Temporary Primary Q Attached to Primary Q 1.203 Test 4.2:PAMS_ATTACH_Q to Temporary Secondary Q Attached to Secondary Q 1.204 Test 4.3:PAMS_DETACH_Q of Secondary Q Detached from Secondary Q 1.204 Test 4.4:PAMS_ATTACH_Q to Permanent Secondary Q Attached to Secondary Q 1.195 Test 5.1:PAMS_LOCATE_Q with Synchronous ACK Queue 'COM_SERVER' - address is 1.100 Test 5.2:PAMS_LOCATE_Q with Asynchronous ACK Queue 'MRS_SERVER' Located - address is 1.98 Test 5.3:PAMS_LOCATE_Q of alias names Queue 'QUEUE_SERVER' - address is 1.100 Queue 'AVAIL_SERVER' - address is 1.99 Queue 'IVP_UNIVERSAL_MOT1' - address is 1.5001 Test 5.4:PAMS_LOCATE_Q from process cache Queue 'MRS_SERVER' - address is 1.98 Test 6.1:PAMS_PUT_MSG to Primary Q Test 6.2:PAMS_GET_MSG from Primary Q Test 6.3:PAMS_PUT_MSG to Secondary Q Test 6.4:PAMS_GET_MSG from Secondary Q Test 6.5:PAMS_PUT_MSG to Primary Q Test 6.6:PAMS_GET_MSGW from Primary Q Test 6.7:PAMS_GET_MSGA [Event Flag Wakeup] Test 6.8:PAMS_GET_MSGA [AST Wakeup] Test 7.1:LOOP BACK of Messages to COM Server Test 8.1:PAMS_SET_TIMER... tid = 8 (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS A-11 Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation Test 8.2:PAMS_WAIT_TIMER Waiting 5 seconds ...... Test 8.3:PAMS_GET_MSG [Receive Timer MSG] Test 8.4:PAMS_CANCEL_TIMER [cancel before timer rings] Test 8.5:PAMS_CANCEL_TIMER [cancel after timer rings] Test 9.1:PAMS_SET_SELECT & Selective Recieve Test 9.2:PAMS_CANCEL_SELECT Part II: Validate DECmessageQ Servers ===================================== Test 20.1:PAMS_DETACH_Q of Secondary Q Detached from Secondary Q 1.195 Test 20.2:Requesting a list of all queues Test 20.3:PAMS_ATTACH_Q to Permanent Secondary Q Attached to Secondary Q 1.195 Test 20.4:Requesting a list of attached queues Test 20.5:PAMS_DETACH_Q of Secondary Q Detached from Secondary Q 1.195 Test 20.7:PAMS_ATTACH_Q to Permanent Secondary Q Attached to Secondary Q 1.195 Test 20.8:Q_NOTIFY on Secondary Q attach Test 20.9:Disabling Queue Notify Request Test 21.1:PAMS_EXIT Test 21.2:PAMS_ATTACH_Q to Permanent Primary Q by name Attached to Primary Q 1.90 Test 21.3:Sending Recoverable Messages thru Primary Q 1.90 Test 22.1:PAMS_EXIT Test 22.2:PAMS_ATTACH_Q to Permanent Primary Q by name Attached to Primary Q 1.90 Test 22.3:Private Broadcast on MOT 1.4999 [IVP_PRIVATE_MOT1] Test 22.4:Univeral Broadcast on MOT 1.5001 [IVP_UNIVERSAL_MOT1] Test 22.5:AVAIL on Primary Q 1.90 Test 22.6:PAMS_ATTACH_Q to Permanent Secondary Q Attached to Secondary Q 1.195 Test 22.7:AVAIL on Secondary Q 1.195 Test 22.8:PAMS_DETACH_Q of Secondary Q Detached from Secondary Q 1.195 (continued on next page) A-12 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation Part III: Validate Error Handling ================================= Test 30.0:PAMS_ATTACH_Q to Primary Q Twice Test 30.1:PAMS_GET_MSGW Timeout... 5 seconds Test 30.2:PAMS_PUT_MSG with Bad Priority Test 30.3:PAMS_PUT_MSG with Bad Delivery Test 30.4:PAMS_PUT_MSG with Bad UMA Test 30.5:Requesting a list of all groups Test 30.6:PAMS_PUT_MSG (WF_MEM) to unknown group %DMQ_0000_00001-EVENT_LOGGER-I-Message Undeliverable %DMQ_0000_00001-EVENT_LOGGER-I-+ Discarded msg - Src=32000.90 Tgt=1.155 Class=7 Type=77 %DMQ_0000_00001-EVENT_LOGGER-I-+ Org-Src=1.90 Org-Tgt=32000.90 Size=1 Seq=005A0001:00002701 %DMQ_0000_00001-EVENT_LOGGER-I-%PAMS-E-NOTACTIVE, Target process is not currently active - message not sent Test 30.7:PAMS_PUT_MSG (WF_MEM) to unknown group from AST level %DMQ_0000_00001-EVENT_LOGGER-I-Message Undeliverable %DMQ_0000_00001-EVENT_LOGGER-I-+ Discarded msg - Src=32000.90 Tgt=1.155 Class=7 Type=77 %DMQ_0000_00001-EVENT_LOGGER-I-+ Org-Src=1.90 Org-Tgt=32000.90 Size=1 Seq=005A0001:00002801 %DMQ_0000_00001-EVENT_LOGGER-I-%PAMS-E-NOTACTIVE, Target process is not currently active - message not sent Test 99.0:PAMS_EXIT IVP Test Summary Report ======================= Part I: Call API - SUCCESSFUL Part II: Servers - SUCCESSFUL Part III: Error Handling - AS EXPECTED (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS A-13 Sample Installation for OpenVMS VAX Example A-1 (Cont.) Sample Full Development Kit Installation %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-I-FORCEX, Forcing image termination on process "DMQ_C_000000001" %DMQ-S-IMGTERM, Process "DMQ_C_000000001" image terminated %DMQ-I-RTLREM, Removed DMQ$MSGSHR %DMQ-I-RTLREM, Removed DMQ$EXECRTL %DMQ-I-RTLREM, Removed DMQ$ENTRYRTL %DMQ-I-RTLREM, Removed DMQ$SET_LNM %DMQ-I-RTLREM, Removed DMQ$PSSRTL %DMQ-I-CLNUP, Cleaning up %DMQ-I-DELETEGRP, Deleting group files for bus 0000 group 00001 %DMQ-I-CLNUP, Clearing logical name table DMQ$LNM_0000_00001 %DMQ-S-SUCCESS, DECmessageQ for VMS IVP successfully completed. Installation of DMQVAX V3.0 completed at 10:02 VMSINSTAL procedure done at 10:02 $ Running IVP You typically run the Installation Verification Procedure (IVP) during installation. You can also run it separately to ensure the integrity of installed files in the event system problems occur. To execute the IVP separately from the installation procedure, enter the following command: $ @[DMQ$V30.EXE]DMQ$IVP You can also run the IVP from the DECmessageQ main menu without stopping the application. A-14 DECmessageQ Installation and Configuration Guide for OpenVMS B ________________________________________________________________ Sample Installation for OpenVMS AXP This appendix contains sample installations of the DECmessageQ software on OpenVMS AXP systems. Full Development Kit Example B-1 is a sample installation for the DECmessageQ full development kit. This sample was run on a system that had no previous version of DECmessageQ installed. Example B-1 Sample Full Development Kit Installation $ set default sys$update $ @vmsinstal dmqaxp030 DKA400:[DMQAXP030.KIT] OpenVMS ALPHA Software Product Installation Procedure V1.5 It is 29-NOV-1994 at 14:05. 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: DMQAXP V3.0 Beginning installation of DMQAXP V3.0 at 14:05 %VMSINSTAL-I-RESTORE, Restoring product save set A ... %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS B-1 Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation ************************************************************** * * * DECmessageQ for OpenVMS AXP V3.0 * * * * * * Installation Procedure * * * * * * Copyright Digital Equipment Corporation 1990, 1994. * * All rights reserved. * * * * * * Restricted Rights: Use, duplication, or disclosure by the * * U.S. Government is subject to restrictions as set forth in * * subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR * * 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. * * * * This software is proprietary to and embodies the * * confidential technology of Digital Equipment Corporation. * * Possession, use, or copying of this software and media is * * authorized only pursuant to a valid written license from * * Digital or an authorized sublicensor. * * * ************************************************************** * Install the development kit [NO]: y Product: DMQ-DEV Producer: DEC Version: 3.0 Release Date: 1-DEC-1994 * Does this product have an authorization key registered and loaded? y (continued on next page) B-2 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation ==================================================================== The DECmessageQ for OpenVMS AXP installation is divided into two parts: 1) Base kit 2) Demo programs directory ==================================================================== * Install base DECmessageQ kit [YES]? * Install DECmessageQ demo programs [YES]? * Install the help text [YES]? n * Enter the DEVICE where DECmessageQ will reside [SYS$SYSDEVICE]: dkb500: %DMQAXP-I-DECTCP, DEC TCP/IP Link Driver and CLS Server will be built %DMQAXP-I-DNS, DNS support will be installed * 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 OpenVMS AXP have now been asked. The installation will continue for approximately 15-45 minutes, depending on load, CPU type and kit media. ======================================================================= %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... ...Linking DMQ$SET_LNM_TABLEV30 %DMQAXP-I-LINKALL, Link all DECmessageQ for OpenVMS AXP images .... %DMQ-S-TBLCREATE, Created DECmessageQ LNM table DMQ$LNM_0000_00001 %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS B-3 Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation ...Linking DMQ$EXECRTLV30 (DMQ$EXECRTL) ...Linking DMQ$PSSRTL-AXPV30 (DMQ$PSSRTL) ...Linking DMQ$ENTRYRTLV30 (DMQ$ENTRYRTL) ...Linking DMQ$MSGSHRV30 (DMQ$MSGSHR) ...Linking DMQ$COM_SERVER ...Linking DMQ$EVENT_LOGGER ...Linking DMQ$JRN_SERVER ...Linking DMQ$SBS_SERVER ...Linking DMQ$MRS_SERVER ...Linking DMQ$UCX_TCPIP_LD ...Linking DMQ$DECNET_LD ...Linking DMQ$CLS_DECNET ...Linking DMQ$CLS_UCX ...Linking DMQ$LOADER ...Linking DMQ$CHECK_LICENSE ...Linking DMQ$SET_LNM_TABLEV30 ...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$MGR_UTILITY ...Linking DMQ$DSPBLK ...Linking DMQ$DNSLOAD ...Linking DMQ$TEST_LOCATE ...Linking DMQ$QMENU ...Linking DMQ$VALID ...Linking DMQ$SRC ...Linking DMQ$SINK ...Linking DMQ$JTEST ...Linking DMQ$QTRANSFER ...Linking DMQ$CVT_V2TO3_JMSG ...Linking DMQ$CVT_V2TO3_RMSG ...Linking DMQ$WAIT_FOR_SERVICE ...Linking DMQTESTM (continued on next page) B-4 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation DEMO_BUILD - Build the DECmessageQ Demonstration Software. 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. ===================================================================== The DECmessageQ for OpenVMS AXP Installation has completed successfully. Before programs can access DECmessageQ for OpenVMS, a privileged user must configure a DECmessageQ group with DKB500:[DMQ$V30.EXE]- DMQ$CREATE_GROUP.COM. Then DKB500:[DMQ$V30.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 Installation and Configuration Guide" 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 DKB500:[DMQ$V30.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 DKB500:[DMQ$V30.EXE]. An extra copy of the Release Notes DMQAXP030.RELEASE_NOTES has been placed in DKB500:[DMQ$V30.DOC]. ===================================================================== %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... DECmessageQ for VMS IVP Command Procedure V3.0-01 %DMQ-I-SETUP, Setting up DECmessageQ IVP environment %DMQ-I-SETUP, Clearing DECmessageQ logicals from process logical name table... Removing logical DMQ$DISK from table LNM$PROCESS_TABLE (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS B-5 Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation %DMQ-I-SETUP, Creating IVP group 0000_00001 in directory DKB500:[DMQ$V30.USER. 0000_00001] %CREATE-I-CREATED, DKB500:[DMQ$V30.USER.0000_00001] created %CREATE-I-CREATED, DKB500:[DMQ$V30.LOG.0000_00001] created %CREATE-I-CREATED, DKB500:[DMQ$V30.MRS.0000_00001] created %DMQ-I-COPYFILE, Copying DMQ$BOOT.COM %DMQ-I-COPYFILE, Copying DMQ$INIT.TXT %DMQ-I-COPYFILE, Copying DMQ$SET_SERVER_LOGICALS.COM %DMQ-I-COPYFILE, Copying DMQ$SET_SERVER_QUOTAS.COM %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-AXPV30.OBJ %DMQ-I-COPYFILE, Copying PSSSYNTAX.MAR %DMQ-I-COPYFILE, Copying P_ENTRY.H %DMQ-I-COPYFILE, Copying P_GROUP.H %DMQ-I-COPYFILE, Copying P_PROCES.H %DMQ-I-COPYFILE, Copying P_RETURN.H (continued on next page) B-6 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation %DMQ-I-COPYFILE, Copying P_SYMBOL.H %DMQ-I-COPYFILE, Copying P_TYPECL.H %DMQ-I-COPYFILE, Copying SYCUSTOMIZE.COM %DMQ-I-COPYFILE, Copying DMQ.TLB %DMQ-I-COPYFILE, Copying DMQ.MLB ...Linking DMQ$PSSRTL0000_00001-AXPV30 (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 system 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 - 29-NOV-1994 14:31:23.11 Bus: 0000 Group: 00001 Disk: DKB500: Start Servers: Yes DMQ Version: DMQ$V30 User Area: DMQ$DISK:[DMQ$V30.USER.0000_00001] Log Area: DMQ$DISK:[DMQ$V30.LOG.0000_00001] PSS file: DMQ$USER:DMQ$PSSRTL0000_00001-AXPV30.EXE %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 %DMQ-W-NOGMTLNM, DMQ$GMT_OFFSET not set %DMQ-I-FORCEX, Forcing image termination on process "DMQ_C_000000001" %SYSTEM-W-NONEXPR, nonexistent process (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS B-7 Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation ...Installing DMQ$MSGSHR ...Installing DMQ$EXECRTL ...Installing DMQ$PSSRTL ...Installing DMQ$ENTRYRTL ...Installing DMQ$SET_LNM %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 ...Starting DMQ_C_000000001 (COM Server) %RUN-S-PROC_ID, identification of created process is 2FC0017A DmQ I 31:53.2 Time Stamp - 29-NOV-1994 14:31:53.22 DmQ I 31:53.2 DECmessageQ System Loader starting... DmQ I 31:55.0 Parsing PROFILE Table DmQ I 31:55.6 Parsing X-Group Configuration Table DmQ I 31:56.0 Parsing Routing Table DmQ I 31:56.0 Parsing CLS Table DmQ I 31:56.0 Parsing Buffer Pool Configuration Section DmQ I 31:56.1 Parsing Queue Configuration Table DmQ I 31:56.4 Parsing SBS Configuration Table DmQ I 31:56.4 Parsing MRS Configuration Table DmQ I 31:56.4 Parsing Group Name Table DmQ I 31:56.6 DECmessageQ load successfully completed (continued on next page) B-8 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation -------------------------------------------------------------------- Waiting for requested servers to indicate they are ready for traffic -------------------------------------------------------------------- %DMQ_0000_00001-EVENT_LOGGER-I-Event Logger (V3.0-11) Starting at 29-NOV-1994 14:31:59.03 %DMQ_0000_00001-EVENT_LOGGER-I-Open DMQ$LOG:DMQ$EVL_0000_00001.LOG log file %DMQ_0000_00001-COM_SERVER-I-COM Server (V3.0-00) starting at 29-NOV-1994 14:31:49 %DMQ_0000_00001-COM_SERVER-I-Created MCS and LLS containing 790 pagelets %DMQ_0000_00001-COM_SERVER-I-Begin initial configuration database load %DMQ_0000_00001-COM_SERVER-I-Created 25 entry Group table containing 167 pagelet s %DMQ_0000_00001-COM_SERVER-I-Group table contains 57 TCBs, 86 NTs and 250 RTs %DMQ_0000_00001-COM_SERVER-I-Created 200 entry Group Name Table containing 35 pagelets %DMQ_0000_00001-COM_SERVER-I-Automatic reset of counters at 29-NOV-1994 14:31:57 %DMQ_0000_00001-COM_SERVER-I-Group 1 (ONE) Initialized %DMQ_0000_00001-EVENT_LOGGER-I-Event Logger Initialized DmQ I 32:03.3 Time Stamp - 29-NOV-1994 14:32:03.37 DmQ I 32:03.3 Waiting for COM_SERVER DmQ I 32:03.3 Waiting for MRS_SERVER DmQ I 32:03.3 Waiting for SBS_SERVER DmQ I 32:03.3 Waiting for EVL_SERVER DmQ I 32:03.3 Waiting for JRN_SERVER %DMQ_0000_00001-JRN_SERVER-I-JRN Server (V3.0-06) Starting %DMQ_0000_00001-MRS_SERVER-I-MRS Server (V3.0-07) Starting %DMQ_0000_00001-SBS_SERVER-I-SBS Server (V3.0-07) Starting %DMQ_0000_00001-MRS_SERVER-I-Space alloted for 128 queues, 512 messages %DMQ_0000_00001-MRS_SERVER-I-Max DQF areas:1000, maximum size:512000 pages %DMQ_0000_00001-MRS_SERVER-I-Max SAF areas:1000, maximum size:512000 pages %DMQ_0000_00001-SBS_SERVER-I-SBS Server Initialized %DMQ_0000_00001-MRS_SERVER-I-MRS Server Initialized %DMQ_0000_00001-JRN_SERVER-I-JRN Server Initialized DmQ I 32:48.3 All servers responded %DMQ-I-COMSTART, DECmessageQ COM Server DMQ_C_0000_00001 successfully started DECmessageQ Installation Verification Program. Part I: Validate Call API ========================= (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS B-9 Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation Test 1.1:PAMS_ATTACH_Q to Permanent Primary Q by number Attached to Primary Q 1.90 Test 1.2:PAMS_EXIT Test 2.1:PAMS_ATTACH_Q to Permanent Primary Q by name Attached to Primary Q 1.90 Test 2.2:PAMS_EXIT Test 3.1:PAMS_ATTACH_Q to Permanent Primary Q with a Secondary Q Attached to Primary Q 1.191 Attached to Secondary Q 1.192 Test 3.2:PAMS_EXIT Test 3.3:PAMS_EXIT Test 4.1:PAMS_ATTACH_Q to Temporary Primary Q Attached to Primary Q 1.203 Test 4.2:PAMS_ATTACH_Q to Temporary Secondary Q Attached to Secondary Q 1.204 Test 4.3:PAMS_DETACH_Q of Secondary Q Detached from Secondary Q 1.204 Test 4.4:PAMS_ATTACH_Q to Permanent Secondary Q Attached to Secondary Q 1.195 Test 5.1:PAMS_LOCATE_Q with Synchronous ACK Queue 'COM_SERVER' - address is 1.100 Test 5.2:PAMS_LOCATE_Q with Asynchronous ACK Queue 'MRS_SERVER' Located - address is 1.98 Test 5.3:PAMS_LOCATE_Q of alias names Queue 'QUEUE_SERVER' - address is 1.100 Queue 'AVAIL_SERVER' - address is 1.99 Queue 'IVP_UNIVERSAL_MOT1' - address is 1.5001 Test 5.4:PAMS_LOCATE_Q from process cache Queue 'MRS_SERVER' - address is 1.98 Test 6.1:PAMS_PUT_MSG to Primary Q Test 6.2:PAMS_GET_MSG from Primary Q Test 6.3:PAMS_PUT_MSG to Secondary Q Test 6.4:PAMS_GET_MSG from Secondary Q Test 6.5:PAMS_PUT_MSG to Primary Q Test 6.6:PAMS_GET_MSGW from Primary Q Test 6.7:PAMS_GET_MSGA [Event Flag Wakeup] Test 6.8:PAMS_GET_MSGA [AST Wakeup] Test 7.1:LOOP BACK of Messages to COM Server Test 8.1:PAMS_SET_TIMER... tid = 8 (continued on next page) B-10 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation Test 8.2:PAMS_WAIT_TIMER Waiting 5 seconds ...... Test 8.3:PAMS_GET_MSG [Receive Timer MSG] Test 8.4:PAMS_CANCEL_TIMER [cancel before timer rings] Test 8.5:PAMS_CANCEL_TIMER [cancel after timer rings] Test 9.1:PAMS_SET_SELECT & Selective Recieve Test 9.2:PAMS_CANCEL_SELECT (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS B-11 Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation Part II: Validate DECmessageQ Servers ===================================== Test 20.1:PAMS_DETACH_Q of Secondary Q Detached from Secondary Q 1.195 Test 20.2:Requesting a list of all queues Test 20.3:PAMS_ATTACH_Q to Permanent Secondary Q Attached to Secondary Q 1.195 Test 20.4:Requesting a list of attached queues Test 20.5:PAMS_DETACH_Q of Secondary Q Detached from Secondary Q 1.195 Test 20.7:PAMS_ATTACH_Q to Permanent Secondary Q Attached to Secondary Q 1.195 Test 20.8:Q_NOTIFY on Secondary Q attach Test 20.9:Disabling Queue Notify Request Test 21.1:PAMS_EXIT Test 21.2:PAMS_ATTACH_Q to Permanent Primary Q by name Attached to Primary Q 1.90 Test 21.3:Sending Recoverable Messages thru Primary Q 1.90 Test 22.1:PAMS_EXIT Test 22.2:PAMS_ATTACH_Q to Permanent Primary Q by name Attached to Primary Q 1.90 Test 22.3:Private Broadcast on MOT 1.4999 [IVP_PRIVATE_MOT1] Test 22.4:Univeral Broadcast on MOT 1.5001 [IVP_UNIVERSAL_MOT1] Test 22.5:AVAIL on Primary Q 1.90 Test 22.6:PAMS_ATTACH_Q to Permanent Secondary Q Attached to Secondary Q 1.195 Test 22.7:AVAIL on Secondary Q 1.195 Test 22.8:PAMS_DETACH_Q of Secondary Q Detached from Secondary Q 1.195 (continued on next page) B-12 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation Part III: Validate Error Handling ================================= Test 30.0:PAMS_ATTACH_Q to Primary Q Twice Test 30.1:PAMS_GET_MSGW Timeout... 5 seconds Test 30.2:PAMS_PUT_MSG with Bad Priority Test 30.3:PAMS_PUT_MSG with Bad Delivery Test 30.4:PAMS_PUT_MSG with Bad UMA Test 30.5:Requesting a list of all groups Test 30.6:PAMS_PUT_MSG (WF_MEM) to unknown group %DMQ_0000_00001-EVENT_LOGGER-I-Message Undeliverable %DMQ_0000_00001-EVENT_LOGGER-I-+ Discarded msg - Src=32000.90 Tgt=1.155 Class=7 Type=77 %DMQ_0000_00001-EVENT_LOGGER-I-+ Org-Src=1.90 Org-Tgt=32000.90 Size=1 Seq=005A0001:00002701 %DMQ_0000_00001-EVENT_LOGGER-I-%PAMS-E-NOTACTIVE, Target process is not currently active - message not sent Test 30.7:PAMS_PUT_MSG (WF_MEM) to unknown group from AST level %DMQ_0000_00001-EVENT_LOGGER-I-Message Undeliverable %DMQ_0000_00001-EVENT_LOGGER-I-+ Discarded msg - Src=32000.90 Tgt=1.155 Class=7 Type=77 %DMQ_0000_00001-EVENT_LOGGER-I-+ Org-Src=1.90 Org-Tgt=32000.90 Size=1 Seq=005A0001:00002801 %DMQ_0000_00001-EVENT_LOGGER-I-%PAMS-E-NOTACTIVE, Target process is not currently active - message not sent Test 99.0:PAMS_EXIT IVP Test Summary Report ======================= Part I: Call API - SUCCESSFUL Part II: Servers - SUCCESSFUL Part III: Error Handling - AS EXPECTED %DMQ-I-COMSTOP, Preparing to stop DECmessageQ COM Server DMQ_C_0000_00001 (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS B-13 Sample Installation for OpenVMS AXP Example B-1 (Cont.) Sample Full Development Kit Installation %DMQ-S-SETLNM, Set to DECmessageQ LNM table DMQ$LNM_0000_00001 %DMQ-I-FORCEX, Forcing image termination on process "DMQ_C_000000001" %DMQ-S-IMGTERM, Process "DMQ_C_000000001" image terminated %DMQ-I-RTLREM, Removed DMQ$MSGSHR %DMQ-I-RTLREM, Removed DMQ$EXECRTL %DMQ-I-RTLREM, Removed DMQ$ENTRYRTL %DMQ-I-RTLREM, Removed DMQ$SET_LNM %DMQ-I-RTLREM, Removed DMQ$PSSRTL %DMQ-I-CLNUP, Cleaning up %DMQ-I-DELETEGRP, Deleting group files for bus 0000 group 00001 %DMQ-I-CLNUP, Clearing logical name table DMQ$LNM_0000_00001 %DMQ-S-SUCCESS, DECmessageQ for VMS IVP successfully completed. Installation of DMQAXP V3.0 completed at 14:33 Adding history entry in VMI$ROOT:[SYSUPD]VMSINSTAL.HISTORY Creating installation data file: VMI$ROOT:[SYSUPD]DMQAXP030.VMI_DATA VMSINSTAL procedure done at 14:33 $ Installation Verification Procedure You typically run the Installation Verification Procedure (IVP) during installation. You can also run it separately to ensure the integrity of installed files in the event system problems occur. To execute the IVP separately from the installation procedure, enter the following command: $ @[DMQ$V30.EXE]DMQ$IVP You can also run the IVP from the DECmessageQ main menu without stopping the application. B-14 DECmessageQ Installation and Configuration Guide for OpenVMS C ________________________________________________________________ Sample DMQ$INIT.TXT File The following is a sample of the DECmessageQ DMQ$INIT.TXT file that is used to customize the DECmessageQ software. ************************************************************************* * * * DECmessageQ Initialization File * * * ************************************************************************* * %VERSION 3.0 * %PROFILE ***** Profile Parameters ***** * ACCEPT_KILL_CMD NO ! Control MONITOR terminate requests ENABLE_XGROUP NO ! Enable DECmessageQ cross-group access XGROUP_VERIFY NO ! Limit incoming cross-group connections ENABLE_MRS YES ! Enable DECmessageQ Message Recovery Services ENABLE_JRN YES ! Enable DECmessageQ Message Journaling Services ENABLE_SBS YES ! Enable DECmessageQ Selective Broadcast Services ENABLE_QXFER NO ! Enable DECmessageQ MRS Queue Transfer Services FIRST_TEMP_QUEUE 200 ! Select start of temp queue pool (200-950) XGROUP_TABLE_SIZE 25 ! Select max number of group entries (25-32000) NAME_TABLE_SIZE 200 ! Select max number of GNT entries (100-32000) RCV_MSG_QUOTA_METHOD MAX ! Select type of rcv msg quota deductions (MIN | MAX) ATTACH_TMO 600 ! Select PAMS_ATTACH_Q timeout (100-36000) PAMSV25_MODE NO ! Select PAMS V2.5 compatiable DECnet object * %EOS * %XGROUP ***** Cross-Group Connection Table ****** DECmessageQ Installation and Configuration Guide for OpenVMS C-1 Sample Installation for OpenVMS AXP * * DMQ * DMQ Group Gen Buff Recnt --Window--- *Group name ID System Cnt Pool Timer Delay Size Trnsprt Addr *--------------- ----- ---------------- --- ---- ----- ----- ----- ------- ----- ONE 1 GVAX01 S 75 -1 -1 -1 DECNET TWO 2 GVAX01 S -1 -1 -1 -1 DECNET TWO 2 GVAX02 S -1 -1 -1 -1 DECNET TWO 2 GVAX03 S -1 -1 -1 -1 DECNET MVII 75 MVII01 S 100 -1 -1 -1 DECNET MVII 75 MVII02 S 100 -1 -1 -1 DECNET MVII 75 MVII03 S 100 -1 -1 -1 DECNET PC 122 MYPC N 50 -1 -1 -1 DECNET *THREE 3 riscy N -1 -1 -1 -1 TCPIP 4095 * %EOS * %ROUTING * initial routing table * * Target Route-Thru * Group Group * ------ ---------- * 1 2 * 2 4 * 3 4 * 4 2 * 5 4 * 6 2 * 7 4 * %EOS * %CLS **** Client Lib Server Configuration Table **** * * Maximum # * Endpoint Transport of Clients * -------- --------- ---------- * 5000 TCPIP 16 * 5001 TCPIP 16 * 6000 DECNET 32 * %EOS * C-2 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS AXP %BUFFER ***** Buffer Pool Configuration Table ******* * Reserve *Msg-Block-Type Byte-Size Number Warning-level Count *-------------- --------- ------ ------------- --------- SMALL 256 50 10 2 MEDIUM 5000 10 2 0 LARGE 32000 3 1 0 %EOS * * %QCT ***** Queue Configuration Table ****** * * ---Pool Quota--- UCB Q Q Confrm Perm Name Check * Queue Name Num Bytes Msgs Ctrl Send Type Own Style Act Scope ACL *------------------- ---- ------- ---- ---- ---- ---- ---- ----- ---- ----- ---- * Sample Queues queue_1 1 35000 100 All . . . II Y L N queue_2 2 35000 100 Msg . . . EI Y L N queue_3 3 35000 100 Byte . . . EO Y L N queue_4 4 35000 100 None . . . . Y L N queue_5 5 35000 100 . . . . . Y L N queue_6 6 35000 100 . . . . . Y L N queue_7 7 35000 100 . . . . . Y L N queue_8 8 35000 100 . . . . . Y L N queue_9 9 35000 100 . . . . . Y L N queue_10 10 35000 100 . . . . . Y L N * * SBS Server uses the following UCB numbers for Optimized Delivery * sbs_eth_control 74 0 0 . E . . . . L N sbs_eth_chan1 75 0 0 . E . . . . L N sbs_eth_chan2 76 0 0 . E . . . . L N * * The following are for the DECmessageQ demo in [DMQ$Vnn.demo.vms] * demo_io_server_1 101 35000 100 . . . . . N L N demo_io_server_2 102 35000 100 . . . . . N L N demo_io_server_3 103 35000 100 . . . . . N L N demo_io_server_4 104 35000 100 . . . . . N L N demo_io_server_mrq 105 35000 100 . . M . . Y L N demo_archive 106 35000 100 . . . . . N L N demo_io_broadcast_1 5101 0 0 . . . . . . L N DECmessageQ Installation and Configuration Guide for OpenVMS C-3 Sample Installation for OpenVMS AXP demo_io_broadcast_2 5102 0 0 . . . . . . L N * * Queues 90-100 & 150-199 are reserved for DECmessageQ utilities temporary_q 0 35000 100 . . . . . . L N screen_process 0 35000 100 . . . . . . L N spare1 90 100000 100 . . . . . Y L N all_ucbs 91 0 0 . . . . . . L N timer_queue 92 0 0 . . . . . . L N null 93 0 0 . . . . . . L N internal1 94 35000 100 . . . . . Y L N qtransfer_server 95 1000000 1000 None . . . . N L N dead_letter_queue 96 35000 100 . . . . . Y L N mrs_server 98 1000000 1000 None . . . . N L N sbs_server 99 1000000 1000 None . . . . N L N avail_server 99 1000000 1000 None . . . . N L N com_server 100 1000000 1000 None . . . . N L N declare_server 100 1000000 1000 None . . . . N L N connect_server 100 1000000 1000 None . . . . N L N queue_server 100 1000000 1000 None . . . . N L N pams_transport 100 1000000 1000 None . . . . N L N dmq_loader 150 250000 100 . . . . . N L N dcl_by_q_name 151 0 0 . . . . . . L N tcpip_ld 152 1000000 1000 None . . . . N L N decnet_ld 153 1000000 1000 None . . . . N L N reserved_ld 154 1000000 1000 None . . . . N L N event_logger 155 1000000 1000 None . . . . N L N jrn_server 156 1000000 1000 None . . . . N L N mrs_failover 157 0 0 . . . . . N L N dmq_fulltest_pq 191 250000 100 . . . . . N L N dmq_fulltest_sq 192 250000 100 . . S 191 . N L N example_q_1 193 64000 100 . . . . . N L N example_q_2 194 64000 100 . . . . . N L N IVP_unowned_sq 195 250000 100 . . S . . N L N IVP_private_MOT1 4999 0 0 . . . . . . L N IVP_universal_MOT1 5001 0 0 . . . . . . L N * %EOS * * %SBS ******* SBS Server Initialization Section ************ * MOT_MODE DNA ! DNA or ETH primary service C-4 DECmessageQ Installation and Configuration Guide for OpenVMS Sample Installation for OpenVMS AXP MOT_LOW 4800 ! 4000 - 4900 MOT_MID 5000 ! must be 5000 MOT_HIGH 5200 ! 5100 - 6000 * *ETH_DEVICE ESA0: ! VMS device name of the Ethernet board * * <<<<<<<<<<<<<<<<<< Warning >>>>>>>>>>>>>>>>>>> * The protocol and Ethernet addresses show below are not registered * and are not guaranteed to not cause a conflict. Use them with * discretion. * * |------ MCA ----| |Prot #| |- UCB queue -| *CNTRL_CHAN AB-AA-34-56-78-90 81F0 74 * * |------ MCA ----| |Prot #| |- UCB queue -| *SET 0 AB-12-34-56-78-90 81F1 75 *MAP 5101 0 ! map a MOT to an Ethernet channel *MAP 5102 0 ! map a MOT to an Ethernet channel * * |------ MCA ----| |Prot #| |- UCB queue -| *SET 1 AB-12-34-56-78-92 81F2 76 *MAP 5103 1 ! map a MOT to an Ethernet channel * %EOS * * %MRS ******* MRS/JRN Servers Initialization Section ************ * AREA_SIZE 512 ! disk blks per file (min:128, max:16384, def:512) NUM_DQF_AREAS 1000 ! min:100, max:1000000, default:1000 NUM_SAF_AREAS 1000 ! min:0, max:1000000, default:1000 NUM_PCJ_AREAS 1000 ! min:0, max:1000000, default:1000 NUM_DLJ_AREAS 1000 ! min:0, max:1000000, default:1000 NUM_MESSAGES 512 ! min:128, max:2147483647, default:512 NUM_QUEUES 128 ! min:128, max:2147483647, default:128 CACHE_PERCENTAGE 90 ! % rcv msg quota for MRS msgs (min:1, max:100, ! def:90) USE_HIGH_WATER_MARK YES ! checkpt MRS sizing params to disk (YES/NO) LOAD_MRS_CTRS YES ! init recoverable msg ctrs on startup (YES/NO) RCVR_ONLY_CONFIRM YES ! limit msg confirms to receiving process (YES/NO) XGRP_JRN_CTRL NO ! allow JRN cntrl msgs from other groups (YES/NO) REDELIVERY_TIMER 10 ! integer seconds (min:0, max:5000, default:10) DECmessageQ Installation and Configuration Guide for OpenVMS C-5 Sample Installation for OpenVMS AXP * PCJ_FILENAME DMQ$MRS:MRS_%bg.PCJ ! char[64] - %bg is a macro that DLJ_FILENAME DMQ$MRS:MRS_%bg.DLJ ! char[64] - expands to bus_group * %EOS * %GNT ********* Group Name Table Section ********************* * * Queue Name Queue Addr Scope *------------------------------ ---------- ----- *global_queue1 1.234 G lcl_queue1 134 L lcl_queue2 135 L lcl_queue3 136 L * %EOS * %END C-6 DECmessageQ Installation and Configuration Guide for OpenVMS D ________________________________________________________________ Files Installed on Your System The DECmessageQ installation procedure installs a number of files on your system. This appendix lists the files created on your system, depending on the kit installed. All files are installed on the device indicated by the logical name DMQ$DISK which is assigned during the installation. Depending on the platform you use, the installed files are: o AXP Development Base Kit files o AXP Run-Time Only Kit files o VAX Development Base Kit files o VAX Run-Time Only Kit files DECmessageQ Installation and Configuration Guide for OpenVMS D-1 Files Installed on Your System AXP Development Base Kit Files Table D-1 and Table D-2 list the names of the files created on your AXPServer system when the DECmessageQ development base kit is installed, Table_D-1_Standard_AXP_Development_Base_Kit_Files_______________ DMQ$DISK:[DMQ$V30.CVT]__________________________________________ DMQ$CVT_V2TO3.COM DMQ$CVT_V2TO3_ALL.COM DMQ$CVT_V2TO3_BUS.COM DMQ$CVT_V2TO3_DOIT.COM DMQ$CVT_V2TO3_HLP1.TXT DMQ$CVT_V2TO3_HLP2.TXT DMQ$CVT_V2TO3_HLP3.TXT DMQ$CVT_V2TO3_HLP4.TXT DMQ$CVT_V2TO3_INIT.COM DMQ$CVT_V2TO3_LU62.TXT DMQ$CVT_V2TO3_MAIN.MNU DMQ$CVT_V2TO3_MAKE.COM DMQ$CVT_V2TO3_MAN.MNU DMQ$CVT_V2TO3_MCHK.COM DMQ$CVT_V2TO3_MENU.COM DMQ$CVT_V2TO3_MFILE.COM DMQ$CVT_V2TO3_MINIT.COM DMQ$CVT_V2TO3_MJRN.COM DMQ$CVT_V2TO3_MMAKE.COM DMQ$CVT_V2TO3_MMRS.COM DMQ$CVT_V2TO3_MPICK.COM DMQ$CVT_V2TO3_MRMSG.COM DMQ$CVT_V2TO3_MRS.MNU DMQ$CVT_V2TO3_MSYMB.COM DMQ$CVT_V2TO3_NEWQS.TXT DMQ$CVT_V2TO3_ONE.MNU DMQ$CVT_V2TO3_PICKABUS.COM DMQ$CVT_V2TO3_PICKAGRP.COM DMQ$CVT_V2TO3_RMSG.COM DMQ$CVT_V2TO3_RULES.TXT DMQ$CVT_V2TO3_SET.COM DMQ$CVT_V2TO3_SYMB.COM ________________________________________________________________ DMQ$DISK:[DMQ$V30.DOC]__________DMQ$DOC:________________________ DMQAXP030.RELEASE_NOTES DMQ_UCB_PROG_GUIDE.LINE (continued on next page) D-2 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXAMPLES]_____DMQ$EXAMPLES:___________________ BOUNCE.C BOUNCE_ROUNDTRIP.README BUILD_EXAMPLES.COM BUILD_PAMS_TASK_EXAMPLES.COM BUILD_PASCAL_PEN_FILE.COM COBOL_RECEIVER.COB COBOL_SENDER.COB DMQ$MRQ_TEST.C DMQ$QMENU.C DMQ.H DMQ_MSG.H ECHO.PSS GETMSG_AST.C GETMSG_EF.C PAMPRTMSG.C PAMPRTSTS.C PAMSAMPLE.FOR PAMSAMPLE_C.C PAMSAMPLE_C.LNK PAMSSLEEP.C PAMS_EXAMPLE.PLI PAMS_TASK_PKG.ADA PAMS_TASK_PKG_.ADA PAMS_TASK_SENDER.ADA PAMS_TASK_TESTER.ADA PRECOMPILE.COM PRECOMPILED_SAMPLE.PAS PUT_WF_REPLY.C ROUNDTRIP.C SENDER.C SENDER.PSS SIMPLE.C SIMPLE_ADA_RUN_SERVER.COM SIMPLE_BUILD.COM SIMPLE_CLIENT.ADA SIMPLE_CLIENT.C SIMPLE_CLIENT.FOR SIMPLE_RUN_SERVER.COM SIMPLE_SERVER.ADA SIMPLE_SERVER.C SIMPLE_SERVER.FOR TTAST.C WATCHDOG.C X_ATTNAM.C X_ATTNUM.C X_ATTTMP.C (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS D-3 Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXAMPLES]_____DMQ$EXAMPLES:___________________ X_BASIC.C X_BUILD.COM X_EXIT.C X_GET.C X_GETALL.C X_GETEM.C X_GETPRI.C X_GETSEL.C X_GETSHO.C X_GETW.C X_LNKSTA.C X_LOCATE.C X_PUTDLJ.C X_PUTSLF.C X_RECOVR.C X_SELECT.C X_SHOPND.C X_TIMER.C ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXAMPLES.MRS]_________________________________ DQF_CONTROL.C JTEST.C SINK.C SRC.C VALID.C ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXAMPLES.SBS]_________________________________ AVAILMSGDEF.H AVAIL_EXAMPLE.C BRDCST_EXAMPLE.C SBSMSGDEF.H SBS_EXAMPLE.C ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXAMPLES.UCBS]________________________________ BUILD_MBX_UCB.COM CNTRLC.C MBX.C MBX.LNK MBXRCV.C MBXSND.C TTSND.C (continued on next page) D-4 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXE]__________DMQ$EXE:________________________ DMQ$ATTACH_PERM_Q.LNK DMQ$CHECK_LICENSE.EXE DMQ$CHECK_LICENSE.LNK DMQ$CHECK_LICENSE.MAP DMQ$CLS.LNK DMQ$CLS_DECNET.EXE DMQ$CLS_DECNET.MAP DMQ$CLS_START.COM DMQ$CNV_INIT.COM DMQ$COM_SERVER.EXE DMQ$COM_SERVER.LNK DMQ$COM_SERVER.MAP DMQ$COM_START.COM DMQ$COPY_LNM_TABLE.COM DMQ$CREATE_ANSI_COBOL_ DMQ$CREATE_GROUP.COM FILES.COM DMQ$CUSTOMIZE.COM DMQ$CVT_V2TO3_JMSG.EXE DMQ$CVT_V2TO3_JMSG.LNK DMQ$CVT_V2TO3_JMSG.MAP DMQ$CVT_V2TO3_RMSG.EXE DMQ$CVT_V2TO3_RMSG.LNK DMQ$CVT_V2TO3_RMSG.MAP DMQ$DEASSIGN.COM DMQ$DECNET_LD.EXE DMQ$DECNET_LD.LNK DMQ$DECNET_LD.MAP DMQ$DELETE_GROUP.COM DMQ$DETACH_PROCESS.COM DMQ$DMQCS_DUMP_GSECT.LNK DMQ$DQF_CONTROL.LNK DMQ$DSPBLK.EXE DMQ$DSPBLK.LNK DMQ$DSPBLK.MAP DMQ$ENTRYRTL-AXP.OPT DMQ$ENTRYRTL.LNK DMQ$ENTRYRTLV30.EXE DMQ$ENTRYRTLV30.MAP DMQ$ETHTEST.LNK DMQ$EVENT_LOGGER.EXE DMQ$EVENT_LOGGER.LNK DMQ$EVENT_LOGGER.MAP DMQ$EXECRTL.LNK DMQ$EXECRTLV30.EXE DMQ$EXECRTLV30.MAP DMQ$FORCEX.COM DMQ$FORCEX.EXE DMQ$FORCEX.LNK DMQ$FORCEX.MAP DMQ$FULLTEST.COM (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS D-5 Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXE]__________DMQ$EXE:________________________ DMQ$FULLTEST_SPAWN.COM DMQ$IVP.COM DMQ$IVP.EXE DMQ$IVP.LNK DMQ$IVP.MAP DMQ$JRN_SERVER.EXE DMQ$JRN_SERVER.LNK DMQ$JRN_SERVER.MAP DMQ$JTEST.EXE DMQ$JTEST.LNK DMQ$JTEST.MAP DMQ$LLS_VERIFY.EXE DMQ$LLS_VERIFY.LNK DMQ$LLS_VERIFY.MAP DMQ$LOADER.EXE DMQ$LOADER.LNK DMQ$LOADER.MAP DMQ$LOOP.EXE DMQ$LOOP.LNK DMQ$LOOP.MAP DMQ$MACWRITE.COM DMQ$MENU.COM DMQ$MGR_UTILITY.EXE DMQ$MGR_UTILITY.LNK DMQ$MGR_UTILITY.MAP DMQ$MONITOR.EXE DMQ$MONITOR.LNK DMQ$MONITOR.MAP DMQ$MRQ_TEST.EXE DMQ$MRQ_TEST.LNK DMQ$MRQ_TEST.MAP DMQ$MRS_SERVER.EXE DMQ$MRS_SERVER.LNK DMQ$MRS_SERVER.MAP DMQ$MSGSHR.LNK DMQ$MSGSHR.OBJ DMQ$MSGSHRV30.EXE DMQ$MSGTBLBLD.COM DMQ$PEXIT.LNK DMQ$PRCTBLBLD.COM DMQ$PROCESS_START.COM DMQ$PSSBUILD.COM DMQ$PSSRTL.LNK DMQ$PSSVFY.EXE DMQ$PSSVFY.LNK DMQ$PSSVFY.MAP DMQ$PSSVFYD.LNK DMQ$QMENU.EXE DMQ$QMENU.LNK DMQ$QMENU.MAP (continued on next page) D-6 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXE]__________DMQ$EXE:________________________ DMQ$QTRANSFER.EXE DMQ$QTRANSFER.LNK DMQ$QTRANSFER.MAP DMQ$QTRANSFER_START.COM DMQ$SBS_AVAIL_REGRESSION_ DMQ$SBS_EXAMPLE.EXE TEST.LNK DMQ$SBS_EXAMPLE.LNK DMQ$SBS_EXAMPLE.MAP DMQ$SBS_SERVER.EXE DMQ$SBS_SERVER.LNK DMQ$SBS_SERVER.MAP DMQ$SBS_SINK.LNK DMQ$SBS_SRC.LNK DMQ$SCAN_SYSTEM_FOR_DMQ.COM DMQ$SET_LNM_TABLE.COM DMQ$SET_LNM_TABLE.LNK DMQ$SET_LNM_TABLEV30.EXE DMQ$SHUTDOWN.COM DMQ$SINK.EXE DMQ$SINK.LNK DMQ$SINK.MAP DMQ$SRC.EXE DMQ$SRC.LNK DMQ$SRC.MAP DMQ$STARTUP.COM DMQ$START_SERVER.COM DMQ$TEST.EXE DMQ$TEST.LNK DMQ$TEST.MAP DMQ$TEST_LOCATE.EXE DMQ$TEST_LOCATE.LNK DMQ$TEST_LOCATE.MAP DMQ$VALID.EXE DMQ$VALID.LNK DMQ$VALID.MAP DMQ$WAIT_FOR_SERVICE.EXE DMQ$WAIT_FOR_SERVICE.LNK DMQ$WAIT_FOR_SERVICE.MAP LINK.COM LINKALL.COM PAMPRTMSG_STUB.OBJ (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS D-7 Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.LIB]__________DMQ$LIB:________________________ CLS.OLB CLS.OPT CNV.OLB DMQ$DNS_LINK.OPT DMQ$IVP.TLB DMQ$OLB.OPT DMQ.MLB DMQ.OPT DMQ.TLB DNS.OLB ETH_UCB.OLB EXEC.OLB MRS.OLB MSG.OLB PORTABLE.OLB PSS.OLB PSS_STUBS.OLB SBS.OLB UCB.OLB (continued on next page) D-8 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.USER.TEMPLATE]________________________________ DMQ$BOOT.COM DMQ$INIT.TXT DMQ$PSSRTL-AXPV30.EXE DMQ$PSSRTL-AXPV30.MAP DMQ$SET_SERVER_LOGICALS.COM DMQ$SET_SERVER_QUOTAS.COM DMQ$TYPCLS.TXT HIDDEN_DATA_TYPES.PAS PAIENTBLI.TXT PAIENTPAS.TXT PAIGRPBLI.TXT PAIGRPPAS.TXT PAIPRCBLI.TXT PAIPRCPAS.TXT PAISTSBLI.TXT PAISTSDBLI.TXT PAISTSDPAS.TXT PAISTSPAS.TXT PAISYMBLI.TXT PAISYMPAS.TXT PAITYPBLI.TXT PAITYPPAS.TXT PAMS_ADA_ENTRY_POINT_.ADA PAMS_ADA_GROUP_.ADA PAMS_ADA_PROCESS_.ADA PAMS_ADA_RETURN_STATUS_.ADA PAMS_ADA_RETURN_STATUS_DEF_ PAMS_ADA_SYMBOL_DEF_.ADA .ADA PAMS_ADA_TYPE_CLASS_.ADA PSSBUILD.MLB PSSSYNTAX-AXPV30.OBJ PSSSYNTAX.MAR P_ENTRY.H P_GROUP.H P_PROCES.H P_RETURN.H P_SYMBOL.H P_TYPECL.H SYCUSTOMIZE.COM_________________________________________________ DECmessageQ Installation and Configuration Guide for OpenVMS D-9 Files Installed on Your System Table_D-2_Optional_AXP_Development_Base_Kit_Files_______________ DMQ$DISK:[DMQ$V30.EXE]_____DMQ$EXE:_____________________________ ____________Optional_AXP_Files-DEC_TCP/IP_Installed_____________ DMQ$CLS_UCX.EXE DMQ$CLS_UCX.MAP DMQ$UCX_TCPIP_LD.EXE DMQ$UCX_TCPIP_LD.LNK DMQ$UCX_TCPIP_LD.MAP ________________________________________________________________ ___________Optional_AXP_Files-TGV_MultiNet_Installed____________ DMQ$CLS_TGV.EXE DMQ$CLS_TGV.MAP DMQ$TGV_TCPIP_LD.EXE DMQ$TGV_TCPIP_LD.LNK DMQ$TGV_TCPIP_LD.MAP ________________________________________________________________ ________Optional_AXP_Files-Wollongong_Pathway_Installed_________ DMQ$CLS_TWG.EXE DMQ$CLS_TWG.MAP DMQ$TWG_TCPIP_LD.EXE DMQ$TWG_TCPIP_LD.LNK DMQ$TWG_TCPIP_LD.MAP ________________________________________________________________ _______________Optional_AXP_Files-Motif_Installed_______________ DMQTESTM.EXE DMQTESTM.LNK DMQTESTM.MAP ________________________________________________________________ ____________Optional_AXP_Files-DECnet/OSI_Installed_____________ DMQ$DNSLOAD.EXE DMQ$DNSLOAD.LNK DMQ$DNSLOAD.MAP_________________________________________________ D-10 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System AXP Run-Time Only Kit Files Table D-3 and Table D-4 list the names of the files created on your AXPServer system when the DECmessageQ run-time only kit is installed, Table_D-3_Standard_AXP_Run-Time_Only_Kit_Files__________________ DMQ$DISK:[DMQ$V30.CVT]__________________________________________ DMQ$CVT_V2TO3.COM DMQ$CVT_V2TO3_ALL.COM DMQ$CVT_V2TO3_BUS.COM DMQ$CVT_V2TO3_DOIT.COM DMQ$CVT_V2TO3_HLP1.TXT DMQ$CVT_V2TO3_HLP2.TXT DMQ$CVT_V2TO3_HLP3.TXT DMQ$CVT_V2TO3_HLP4.TXT DMQ$CVT_V2TO3_INIT.COM DMQ$CVT_V2TO3_LU62.TXT DMQ$CVT_V2TO3_MAIN.MNU DMQ$CVT_V2TO3_MAKE.COM DMQ$CVT_V2TO3_MAN.MNU DMQ$CVT_V2TO3_MCHK.COM DMQ$CVT_V2TO3_MENU.COM DMQ$CVT_V2TO3_MFILE.COM DMQ$CVT_V2TO3_MINIT.COM DMQ$CVT_V2TO3_MJRN.COM DMQ$CVT_V2TO3_MMAKE.COM DMQ$CVT_V2TO3_MMRS.COM DMQ$CVT_V2TO3_MPICK.COM DMQ$CVT_V2TO3_MRMSG.COM DMQ$CVT_V2TO3_MRS.MNU DMQ$CVT_V2TO3_MSYMB.COM DMQ$CVT_V2TO3_NEWQS.TXT DMQ$CVT_V2TO3_ONE.MNU DMQ$CVT_V2TO3_PICKABUS.COM DMQ$CVT_V2TO3_PICKAGRP.COM DMQ$CVT_V2TO3_RMSG.COM DMQ$CVT_V2TO3_RULES.TXT DMQ$CVT_V2TO3_SET.COM DMQ$CVT_V2TO3_SYMB.COM ________________________________________________________________ DMQ$DISK:[DMQ$V30.DOC]_____DMQ$DOC:_____________________________ DMQAXP030.RELEASE_NOTES DMQ_UCB_PROG_GUIDE.LINE (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS D-11 Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXE]_____DMQ$EXE:_____________________________ DMQ$CHECK_LICENSE.EXE DMQ$CLS_DECNET.EXE DMQ$CLS_START.COM DMQ$CNV_INIT.COM DMQ$COM_SERVER.EXE DMQ$COM_START.COM DMQ$COPY_LNM_TABLE.COM DMQ$CREATE_ANSI_COBOL_FILES.COM DMQ$CREATE_GROUP.COM DMQ$CUSTOMIZE.COM DMQ$CVT_V2TO3_JMSG.EXE DMQ$CVT_V2TO3_RMSG.EXE DMQ$DEASSIGN.COM DMQ$DECNET_LD.EXE DMQ$DELETE_GROUP.COM DMQ$DETACH_PROCESS.COM DMQ$DSPBLK.EXE DMQ$ENTRYRTL-AXP.OPT DMQ$ENTRYRTLV30.EXE DMQ$EVENT_LOGGER.EXE DMQ$EXECRTLV30.EXE DMQ$FORCEX.COM DMQ$FORCEX.EXE DMQ$FULLTEST.COM DMQ$FULLTEST_SPAWN.COM DMQ$IVP.COM DMQ$IVP.EXE DMQ$JRN_SERVER.EXE DMQ$JTEST.EXE DMQ$LLS_VERIFY.EXE DMQ$LOADER.EXE DMQ$LOOP.EXE DMQ$MENU.COM DMQ$MGR_UTILITY.EXE DMQ$MONITOR.EXE DMQ$MRQ_TEST.EXE DMQ$MRS_SERVER.EXE DMQ$MSGSHRV30.EXE DMQ$MSGTBLBLD.COM DMQ$PROCESS_START.COM DMQ$PSSBUILD.COM DMQ$PSSVFY.EXE DMQ$QMENU.EXE DMQ$QTRANSFER.EXE DMQ$QTRANSFER_START.COM DMQ$SBS_EXAMPLE.EXE (continued on next page) D-12 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXE]_____DMQ$EXE:_____________________________ DMQ$SBS_SERVER.EXE DMQ$SCAN_SYSTEM_FOR_DMQ.COM DMQ$SET_LNM_TABLE.COM DMQ$SET_LNM_TABLEV30.EXE DMQ$SHUTDOWN.COM DMQ$SINK.EXE DMQ$SRC.EXE DMQ$STARTUP.COM DMQ$START_SERVER.COM DMQ$TEST.EXE DMQ$TEST_LOCATE.EXE DMQ$VALID.EXE DMQ$WAIT_FOR_SERVICE.EXE ________________________________________________________________ DMQ$DISK:[DMQ$V30.LIB]_____DMQ$LIB:_____________________________ CLS.OPT DMQ$DNS_LINK.OPT DMQ$IVP.TLB DMQ.OPT ________________________________________________________________ DMQ$DISK:[DMQ$V30.USER.TEMPLATE]________________________________ DMQ$BOOT.COM DMQ$INIT.TXT DMQ$PSSRTL-AXPV30.EXE DMQ$SET_SERVER_LOGICALS.COM DMQ$SET_SERVER_QUOTAS.COM SYCUSTOMIZE.COM ________________________________________________________________ SYS$LIBRARY_____________________________________________________ DMQ$ENTRYRTL.IFF________________________________________________ DECmessageQ Installation and Configuration Guide for OpenVMS D-13 Files Installed on Your System Table_D-4_Optional_AXP_Run-Time_Only_Kit_Files__________________ Optional AXP Files-User Selected LU6.2 Support DMQ$DISK:[DMQ$V30.LIB]_____DMQ$LIB:_____________________________ DMQ$OLB.OPT MSG.OLB DNS.OLB ________________________________________________________________ DMQ$DISK:[DMQ$V30.USER.TEMPLATE]________________________________ DMQ$TYPCLS.TXT ________________________________________________________________ ____________Optional_AXP_Files-DEC_TCP/IP_Installed_____________ DMQ$CLS_UCX.EXE DMQ$UCX_TCPIP_LD.EXE ________________________________________________________________ ___________Optional_AXP_Files-TGV_Multinet_Installed____________ DMQ$CLS_TGV.EXE DMQ$TGV_TCPIP_LD.EXE ________________________________________________________________ ________Optional_AXP_Files-Wollongong_Pathway_Installed_________ DMQ$CLS_TWG.EXE DMQ$TWG_TCPIP_LD.EXE ________________________________________________________________ _______________Optional_AXP_Files-MOTIF_Installed_______________ DMQTESTM.EXE ________________________________________________________________ ____________Optional_AXP_Files-DECnet/OSI_Installed_____________ DMQ$DNSLOAD.EXE_________________________________________________ D-14 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System VAX Development Base Kit Files Table D-5 and Table D-6 list the names of the files created on your VAX Server system when the DECmessageQ development base kit is installed, Table_D-5_Standard_VAX_Development_Base_Kit_Files_______________ DMQ$DISK:[DMQ$V30.CVT]__________________________________________ DMQ$CVT_V2TO3.COM DMQ$CVT_V2TO3_ALL.COM DMQ$CVT_V2TO3_BUS.COM DMQ$CVT_V2TO3_DOIT.COM DMQ$CVT_V2TO3_HLP1.TXT DMQ$CVT_V2TO3_HLP2.TXT DMQ$CVT_V2TO3_HLP3.TXT DMQ$CVT_V2TO3_HLP4.TXT DMQ$CVT_V2TO3_INIT.COM DMQ$CVT_V2TO3_LU62.TXT DMQ$CVT_V2TO3_MAIN.MNU DMQ$CVT_V2TO3_MAKE.COM DMQ$CVT_V2TO3_MAN.MNU DMQ$CVT_V2TO3_MCHK.COM DMQ$CVT_V2TO3_MENU.COM DMQ$CVT_V2TO3_MFILE.COM DMQ$CVT_V2TO3_MINIT.COM DMQ$CVT_V2TO3_MJRN.COM DMQ$CVT_V2TO3_MMAKE.COM DMQ$CVT_V2TO3_MMRS.COM DMQ$CVT_V2TO3_MPICK.COM DMQ$CVT_V2TO3_MRMSG.COM DMQ$CVT_V2TO3_MRS.MNU DMQ$CVT_V2TO3_MSYMB.COM DMQ$CVT_V2TO3_NEWQS.TXT DMQ$CVT_V2TO3_ONE.MNU DMQ$CVT_V2TO3_PICKABUS.COM DMQ$CVT_V2TO3_PICKAGRP.COM DMQ$CVT_V2TO3_RMSG.COM DMQ$CVT_V2TO3_RULES.TXT DMQ$CVT_V2TO3_SET.COM DMQ$CVT_V2TO3_SYMB.COM ________________________________________________________________ DMQ$DISK:[DMQ$V30.DOC]__________DMQ$DOC:________________________ DMQVAX030.RELEASE_NOTES DMQ_UCB_PROG_GUIDE.LINE ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXAMPLES.MRS]_________________________________ DQF_CONTROL.C JTEST.C SINK.C SRC.C VALID.C (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS D-15 Files Installed on Your System Table_D-5_(Cont.)_Standard_VAX_Development_Base_Kit_Files_______ DMQ$DISK:[DMQ$V30.EXAMPLES.SBS]_________________________________ AVAILMSGDEF.H AVAIL_EXAMPLE.C BRDCST_EXAMPLE.C SBSMSGDEF.H SBS_EXAMPLE.C ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXAMPLES.UCBS]________________________________ BUILD_MBX_UCB.COM CNTRLC.C MBX.C MBX.LNK MBXRCV.C MBXSND.C TTSND.C ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXAMPLES]_____DMQ$EXAMPLES:___________________ BOUNCE.C BOUNCE_ROUNDTRIP.README BUILD_EXAMPLES.COM BUILD_PAMS_TASK_EXAMPLES.COM BUILD_PASCAL_PEN_FILE.COM COBOL_RECEIVER.COB COBOL_SENDER.COB DMQ$MRQ_TEST.C DMQ$QMENU.C DMQ.H DMQ_MSG.H ECHO.PSS GETMSG_AST.C GETMSG_EF.C PAMPRTMSG.C PAMPRTSTS.C PAMSAMPLE.FOR PAMSAMPLE_C.C PAMSAMPLE_C.LNK PAMSSLEEP.C PAMS_EXAMPLE.PLI PAMS_TASK_PKG.ADA PAMS_TASK_PKG_.ADA PAMS_TASK_SENDER.ADA PAMS_TASK_TESTER.ADA PRECOMPILE.COM PRECOMPILED_SAMPLE.PAS PUT_WF_REPLY.C ROUNDTRIP.C SENDER.C SENDER.PSS SIMPLE.C (continued on next page) D-16 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System Table_D-5_(Cont.)_Standard_VAX_Development_Base_Kit_Files_______ DMQ$DISK:[DMQ$V30.EXAMPLES]_____DMQ$EXAMPLES:___________________ SIMPLE_ADA_RUN_SERVER.COM SIMPLE_BUILD.COM SIMPLE_CLIENT.ADA SIMPLE_CLIENT.C SIMPLE_CLIENT.FOR SIMPLE_RUN_SERVER.COM SIMPLE_SERVER.ADA SIMPLE_SERVER.C SIMPLE_SERVER.FOR TTAST.C WATCHDOG.C X_ATTNAM.C X_ATTNUM.C X_ATTTMP.C X_BASIC.C X_BUILD.COM X_EXIT.C X_GET.C X_GETALL.C X_GETEM.C X_GETPRI.C X_GETSEL.C X_GETSHO.C X_GETW.C X_LNKSTA.C X_LOCATE.C X_PUTDLJ.C X_PUTSLF.C X_RECOVR.C X_SELECT.C X_SHOPND.C X_TIMER.C (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS D-17 Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXE]__________DMQ$EXE:________________________ DMQ$ATTACH_PERM_Q.LNK DMQ$CHECK_LICENSE.EXE DMQ$CHECK_LICENSE.LNK DMQ$CHECK_LICENSE.MAP DMQ$CLS.LNK DMQ$CLS_DECNET.EXE DMQ$CLS_DECNET.MAP DMQ$CLS_START.COM DMQ$CNV_INIT.COM DMQ$COM_SERVER.EXE DMQ$COM_SERVER.LNK DMQ$COM_SERVER.MAP DMQ$COM_START.COM DMQ$COPY_LNM_TABLE.COM DMQ$CREATE_ANSI_COBOL_ DMQ$CREATE_GROUP.COM FILES.COM DMQ$CUSTOMIZE.COM DMQ$CVT_V2TO3_JMSG.EXE DMQ$CVT_V2TO3_JMSG.LNK DMQ$CVT_V2TO3_JMSG.MAP DMQ$CVT_V2TO3_RMSG.EXE DMQ$CVT_V2TO3_RMSG.LNK DMQ$CVT_V2TO3_RMSG.MAP DMQ$DEASSIGN.COM DMQ$DECNET_LD.EXE DMQ$DECNET_LD.LNK DMQ$DECNET_LD.MAP DMQ$DELETE_GROUP.COM DMQ$DETACH_PROCESS.COM DMQ$DMQCS_DUMP_GSECT.LNK DMQ$DQF_CONTROL.LNK DMQ$DSPBLK.EXE DMQ$DSPBLK.LNK DMQ$DSPBLK.MAP DMQ$ENTRYRTL-VAX.OPT DMQ$ENTRYRTL.LNK DMQ$ENTRYRTLV30.EXE DMQ$ENTRYRTLV30.MAP DMQ$ETHTEST.LNK DMQ$EVENT_LOGGER.EXE DMQ$EVENT_LOGGER.LNK DMQ$EVENT_LOGGER.MAP DMQ$EXECRTL.LNK DMQ$EXECRTLV30.EXE DMQ$EXECRTLV30.MAP DMQ$FORCEX.COM DMQ$FORCEX.EXE DMQ$FORCEX.LNK (continued on next page) D-18 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXE]__________DMQ$EXE:________________________ DMQ$FORCEX.MAP DMQ$FULLTEST.COM DMQ$FULLTEST_SPAWN.COM DMQ$IVP.COM (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS D-19 Files Installed on Your System Table_D-5_(Cont.)_Standard_VAX_Development_Base_Kit_Files_______ DMQ$DISK:[DMQ$V30.EXE]__________DMQ$EXE:________________________ DMQ$IVP.EXE DMQ$IVP.LNK DMQ$IVP.MAP DMQ$JRN_SERVER.EXE DMQ$JRN_SERVER.LNK DMQ$JRN_SERVER.MAP DMQ$JTEST.EXE DMQ$JTEST.LNK DMQ$JTEST.MAP DMQ$LLS_VERIFY.EXE DMQ$LLS_VERIFY.LNK DMQ$LLS_VERIFY.MAP DMQ$LOADER.EXE DMQ$LOADER.LNK DMQ$LOADER.MAP DMQ$LOOP.EXE DMQ$LOOP.LNK DMQ$LOOP.MAP DMQ$MACWRITE.COM DMQ$MENU.COM DMQ$MGR_UTILITY.EXE DMQ$MGR_UTILITY.LNK DMQ$MGR_UTILITY.MAP DMQ$MONITOR.EXE DMQ$MONITOR.LNK DMQ$MONITOR.MAP DMQ$MRQ_TEST.EXE DMQ$MRQ_TEST.LNK DMQ$MRQ_TEST.MAP DMQ$MRS_SERVER.EXE DMQ$MRS_SERVER.LNK DMQ$MRS_SERVER.MAP DMQ$MSGSHR.LNK DMQ$MSGSHR.OBJ DMQ$MSGSHRV30.EXE DMQ$MSGTBLBLD.COM DMQ$PEXIT.LNK DMQ$PRCTBLBLD.COM DMQ$PROCESS_START.COM DMQ$PSSBUILD.COM DMQ$PSSRTL.LNK DMQ$PSSVFY.EXE DMQ$PSSVFY.LNK DMQ$PSSVFY.MAP DMQ$PSSVFYD.LNK DMQ$QMENU.EXE DMQ$QMENU.LNK DMQ$QMENU.MAP DMQ$QTRANSFER.EXE DMQ$QTRANSFER.LNK DMQ$QTRANSFER.MAP DMQ$QTRANSFER_START.COM DMQ$SBS_AVAIL_REGRESSION_ DMQ$SBS_EXAMPLE.EXE TEST.LNK (continued on next page) D-20 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System Table_D-5_(Cont.)_Standard_VAX_Development_Base_Kit_Files_______ DMQ$DISK:[DMQ$V30.EXE]__________DMQ$EXE:________________________ DMQ$SBS_EXAMPLE.LNK DMQ$SBS_EXAMPLE.MAP DMQ$SBS_SERVER.EXE DMQ$SBS_SERVER.LNK DMQ$SBS_SERVER.MAP DMQ$SBS_SINK.LNK DMQ$SBS_SRC.LNK DMQ$SCAN_SYSTEM_FOR_DMQ.COM DMQ$SET_LNM_TABLE.COM DMQ$SET_LNM_TABLE.LNK DMQ$SET_LNM_TABLEV30.EXE DMQ$SHUTDOWN.COM DMQ$SINK.EXE DMQ$SINK.LNK DMQ$SINK.MAP DMQ$SRC.EXE DMQ$SRC.LNK DMQ$SRC.MAP DMQ$STARTUP.COM DMQ$START_SERVER.COM DMQ$TEST.EXE DMQ$TEST.LNK DMQ$TEST.MAP DMQ$TEST_LOCATE.EXE DMQ$TEST_LOCATE.LNK DMQ$TEST_LOCATE.MAP DMQ$VALID.EXE DMQ$VALID.LNK DMQ$VALID.MAP DMQ$WAIT_FOR_SERVICE.EXE DMQ$WAIT_FOR_SERVICE.LNK DMQ$WAIT_FOR_SERVICE.MAP LINK.COM LINKALL.COM PAMPRTMSG_STUB.OBJ (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS D-21 Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.LIB]__________DMQ$LIB:________________________ CLS.OLB CLS.OPT CNV.OLB DMQ$DNS_LINK.OPT DMQ$IVP.TLB DMQ$OLB.OPT DMQ.MLB DMQ.OPT DMQ.TLB DNS.OLB ETH_UCB.OLB EXEC.OLB MRS.OLB MSG.OLB PORTABLE.OLB PSS.OLB PSS_STUBS.OLB SBS.OLB UCB.OLB (continued on next page) D-22 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.USER.TEMPLATE]________________________________ DMQ$BOOT.COM DMQ$INIT.TXT DMQ$PSSRTL-VAXV30.EXE DMQ$PSSRTL-VAXV30.MAP DMQ$SET_SERVER_LOGICALS.COM DMQ$SET_SERVER_QUOTAS.COM DMQ$TYPCLS.TXT HIDDEN_DATA_TYPES.PAS PAIENTBLI.TXT PAIENTPAS.TXT PAIGRPBLI.TXT PAIGRPPAS.TXT PAIPRCBLI.TXT PAIPRCPAS.TXT PAISTSBLI.TXT PAISTSDBLI.TXT PAISTSDPAS.TXT PAISTSPAS.TXT PAISYMBLI.TXT PAISYMPAS.TXT PAITYPBLI.TXT PAITYPPAS.TXT PAMS_ADA_ENTRY_POINT_.ADA PAMS_ADA_GROUP_.ADA PAMS_ADA_PROCESS_.ADA PAMS_ADA_RETURN_STATUS_.ADA PAMS_ADA_RETURN_STATUS_DEF_ PAMS_ADA_SYMBOL_DEF_.ADA .ADA PAMS_ADA_TYPE_CLASS_.ADA PSSBUILD.MLB PSSSYNTAX-VAXV30.OBJ PSSSYNTAX.MAR P_ENTRY.H P_GROUP.H P_PROCES.H P_RETURN.H P_SYMBOL.H P_TYPECL.H SYCUSTOMIZE.COM_________________________________________________ DECmessageQ Installation and Configuration Guide for OpenVMS D-23 Files Installed on Your System Table_D-6_Optional_VAX_Development_Base_Kit_Files_______________ DMQ$DISK:[DMQ$V30.EXE]_____DMQ$EXE:_____________________________ ____________Optional_VAX_Files-DEC_TCP/IP_Installed_____________ DMQ$CLS_UCX.EXE DMQ$CLS_UCX.MAP DMQ$UCX_TCPIP_LD.EXE DMQ$UCX_TCPIP_LD.LNK DMQ$UCX_TCPIP_LD.MAP ________________________________________________________________ ___________Optional_VAX_Files-TGV_MultiNet_Installed____________ DMQ$CLS_TGV.EXE DMQ$CLS_TGV.MAP DMQ$TGV_TCPIP_LD.EXE DMQ$TGV_TCPIP_LD.LNK DMQ$TGV_TCPIP_LD.MAP ________________________________________________________________ ________Optional_VAX_Files-Wollongong_Pathway_Installed_________ DMQ$CLS_TWG.EXE DMQ$CLS_TWG.MAP DMQ$TWG_TCPIP_LD.EXE DMQ$TWG_TCPIP_LD.LNK DMQ$TWG_TCPIP_LD.MAP ________________________________________________________________ _______________Optional_VAX_Files-Motif_Installed_______________ DMQTESTM.EXE DMQTESTM.LNK DMQTESTM.MAP____________________________________________________ D-24 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System VAX Run-Time Only Kit Files Table D-7 and Table D-8 list the names of the files created on your VAX Server system when the DECmessageQ run-time only kit is installed, Table_D-7_Standard_VAX_Run-Time_Only_Kit_Files__________________ DMQ$DISK:[DMQ$V30.CVT]__________________________________________ DMQ$CVT_V2TO3.COM DMQ$CVT_V2TO3_ALL.COM DMQ$CVT_V2TO3_BUS.COM DMQ$CVT_V2TO3_DOIT.COM DMQ$CVT_V2TO3_HLP1.TXT DMQ$CVT_V2TO3_HLP2.TXT DMQ$CVT_V2TO3_HLP3.TXT DMQ$CVT_V2TO3_HLP4.TXT DMQ$CVT_V2TO3_INIT.COM DMQ$CVT_V2TO3_LU62.TXT DMQ$CVT_V2TO3_MAIN.MNU DMQ$CVT_V2TO3_MAKE.COM DMQ$CVT_V2TO3_MAN.MNU DMQ$CVT_V2TO3_MCHK.COM DMQ$CVT_V2TO3_MENU.COM DMQ$CVT_V2TO3_MFILE.COM DMQ$CVT_V2TO3_MINIT.COM DMQ$CVT_V2TO3_MJRN.COM DMQ$CVT_V2TO3_MMAKE.COM DMQ$CVT_V2TO3_MMRS.COM DMQ$CVT_V2TO3_MPICK.COM DMQ$CVT_V2TO3_MRMSG.COM DMQ$CVT_V2TO3_MRS.MNU DMQ$CVT_V2TO3_MSYMB.COM DMQ$CVT_V2TO3_NEWQS.TXT DMQ$CVT_V2TO3_ONE.MNU DMQ$CVT_V2TO3_PICKABUS.COM DMQ$CVT_V2TO3_PICKAGRP.COM DMQ$CVT_V2TO3_RMSG.COM DMQ$CVT_V2TO3_RULES.TXT DMQ$CVT_V2TO3_SET.COM DMQ$CVT_V2TO3_SYMB.COM ________________________________________________________________ DMQ$DISK:[DMQ$V30.DOC]_____DMQ$DOC:_____________________________ DMQVAX030.RELEASE_NOTES DMQ_UCB_PROG_GUIDE.LINE (continued on next page) DECmessageQ Installation and Configuration Guide for OpenVMS D-25 Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXE]_____DMQ$EXE:_____________________________ DMQ$CHECK_LICENSE.EXE DMQ$CLS_DECNET.EXE DMQ$CLS_START.COM DMQ$CNV_INIT.COM DMQ$COM_SERVER.EXE DMQ$COM_START.COM DMQ$COPY_LNM_TABLE.COM DMQ$CREATE_ANSI_COBOL_FILES.COM DMQ$CREATE_GROUP.COM DMQ$CUSTOMIZE.COM DMQ$CVT_V2TO3_JMSG.EXE DMQ$CVT_V2TO3_RMSG.EXE DMQ$DEASSIGN.COM DMQ$DECNET_LD.EXE DMQ$DELETE_GROUP.COM DMQ$DETACH_PROCESS.COM DMQ$DSPBLK.EXE DMQ$ENTRYRTL-VAX.OPT DMQ$ENTRYRTLV30.EXE DMQ$EVENT_LOGGER.EXE DMQ$EXECRTLV30.EXE DMQ$FORCEX.COM DMQ$FORCEX.EXE DMQ$FULLTEST.COM DMQ$FULLTEST_SPAWN.COM DMQ$IVP.COM DMQ$IVP.EXE DMQ$JRN_SERVER.EXE DMQ$JTEST.EXE DMQ$LLS_VERIFY.EXE DMQ$LOADER.EXE DMQ$LOOP.EXE DMQ$MENU.COM DMQ$MGR_UTILITY.EXE DMQ$MONITOR.EXE DMQ$MRQ_TEST.EXE DMQ$MRS_SERVER.EXE DMQ$MSGSHRV30.EXE DMQ$MSGTBLBLD.COM DMQ$PROCESS_START.COM DMQ$PSSBUILD.COM DMQ$PSSVFY.EXE DMQ$QMENU.EXE DMQ$QTRANSFER.EXE DMQ$QTRANSFER_START.COM DMQ$SBS_EXAMPLE.EXE DMQ$SBS_SERVER.EXE DMQ$SCAN_SYSTEM_FOR_DMQ.COM (continued on next page) D-26 DECmessageQ Installation and Configuration Guide for OpenVMS Files Installed on Your System ________________________________________________________________ DMQ$DISK:[DMQ$V30.EXE]_____DMQ$EXE:_____________________________ DMQ$SET_LNM_TABLE.COM DMQ$SET_LNM_TABLEV30.EXE DMQ$SHUTDOWN.COM DMQ$SINK.EXE DMQ$SRC.EXE DMQ$STARTUP.COM DMQ$START_SERVER.COM DMQ$TEST.EXE DMQ$TEST_LOCATE.EXE DMQ$VALID.EXE DMQ$WAIT_FOR_SERVICE.EXE ________________________________________________________________ DMQ$DISK:[DMQ$V30.LIB]_____DMQ$LIB:_____________________________ CLS.OPT DMQ$DNS_LINK.OPT DMQ$IVP.TLB DMQ.OPT ________________________________________________________________ DMQ$DISK:[DMQ$V30.USER.TEMPLATE]________________________________ DMQ$BOOT.COM DMQ$INIT.TXT DMQ$PSSRTL-VAXV30.EXE DMQ$SET_SERVER_LOGICALS.COM DMQ$SET_SERVER_QUOTAS.COM__SYCUSTOMIZE.COM______________________ DECmessageQ Installation and Configuration Guide for OpenVMS D-27 Files Installed on Your System Table_D-8_Optional_VAX_Run-Time_Only_Kit_Files__________________ Optional VAX Files-User Selected LU6.2 Support DMQ$DISK:[DMQ$V30.LIB]_____DMQ$LIB:_____________________________ DMQ$OLB.OPT MSG.OLB DNS.OLB ________________________________________________________________ DMQ$DISK:[DMQ$V30.USER.TEMPLATE]________________________________ DMQ$TYPCLS.TXT__________________________________________________ DMQ$DISK:[DMQ$V30.EXE]_____DMQ$EXE:_____________________________ ____________Optional_VAX_Files-DEC_TCP/IP_Installed_____________ DMQ$CLS_UCX.EXE DMQ$UCX_TCPIP_LD.EXE ________________________________________________________________ ___________Optional_VAX_Files-TGV_Multinet_Installed____________ DMQ$CLS_TGV.EXE DMQ$TGV_TCPIP_LD.EXE ________________________________________________________________ ________Optional_VAX_Files-Wollongong_Pathway_Installed_________ DMQ$CLS_TWG.EXE DMQ$TWG_TCPIP_LD.EXE ________________________________________________________________ _______________Optional_VAX_Files-MOTIF_Installed_______________ DMQTESTM.EXE ________________________________________________________________ ____________Optional_VAX_Files-DECnet/OSI_Installed_____________ DMQ$DNSLOAD.EXE_________________________________________________ D-28 DECmessageQ Installation and Configuration Guide for OpenVMS ________________________________________________________________ Index A Communication transports ___________________________ supported by AXP systems, AUTOGEN utility, 1-21 1-2 AXP systems supported by VAX systems, required operating system 1-2 for, 1-15 Concurrent versions on an OpenVMS system, B__________________________ 1-26 Backup Conversion Utility, 2-16 before installation, 1-25 confirming during D__________________________ installation, 2-7 DECmessageQ Broadcasting upgrading, 2-16 See Selective Broadcast DECmessageQ software Services (SBS) checking media contents Buffer Pool Configuration for, 1-14 Table conceptual overview of, See also DMQ$INIT.TXT 1-2 file purging previous versions during installation, Buses 2-12 See Message queuing buses DECnet communicating from a VAX C__________________________ system using, 1-2 Client Lib Server communicating from an AXP definition of, 1-6 system using, 1-2 COM Server DECmessageQ software See alsoServers relation to, 1-2 definition of, 1-6 links, creation of, 1-6 Command procedures Definitions VMSLICENSE, 1-17 Client Lib Server, 1-6 COM servers, 1-6 Index-1 Definitions (cont'd) GBLPAGFIL parameter DECmessageQ servers, 1-5 minimum required value global memory, 1-7 for, 1-20 Journal servers, 1-7 GBLSECTIONS parameter link drivers, 1-7 calculating, 1-21 message queues, 1-3 minimum required value message queuing buses, for, 1-20 1-3 Global memory Message Recovery Services definition of, 1-7 (MRS), 1-6 GNT Selective Broadcast See Group Name Table Services (SBS), 1-6 (GNT) symbolic names, 1-7 Group Name Table (GNT) user processes, 1-4 See also DMQ$INIT.TXT Disk space file for installation, 1-24 Distributed systems Groups planning, 1-8 See Message queuing DMQ$INIT.TXT, C-1 groups DQF See Destination queue H__________________________ files (DQFs) Help files selecting during E__________________________ installation, 2-9 Error messages installation, 2-13 I__________________________ Ethernet Initialization sections communicating from a VAX See DMQ$INIT.TXT file system using, 1-2 Installation Verification communicating from an AXP Procedure (IVP) system using, 1-2 registering and loading F license before running, ___________________________ 1-16 Failure messages, 2-14 running during installation, 2-11 G__________________________ Installing DECmessageQ, GBLPAGES parameter 2-1 to 2-23 calculating, 1-21 disk space for, 1-24 minimum required value error conditions for, for, 1-20 2-14 error messages resulting from, 2-13 Index-2 Installing DECmessageQ Links (cont'd) See also Link Connect preparing for, 1-1 to Table 1-26 LMF privileges for, 1-23 See License Management procedure, 2-2 to 2-13 Facility (LMF) requirements for, 1-21 to LU6.2, communicating from a 1-26 VAX system using, 1-2 system parameters for, 1-20 M time for, 1-23 ___________________________ IVP Manager utility See Installation See MGR_UTILITY utility Verification Procedure Memory (IVP) See Global memory Message queues J__________________________ definition of, 1-3 Journal Server Message queuing buses definition of, 1-7 definition of, 1-3 Message Recovery Services (MRS) K__________________________ definition of, 1-6 Kits Message Recovery Services selecting during (SRS) installation, 2-9 See also Servers L MOT ___________________________ See Multipoint Outbound License Management Facility Target (MOT) (LMF), 1-16 MRS Licenses See Message Recovery confirming registration Services (MRS) during installation, Multipoint broadcasting 2-8 See Selective Broadcast loading on a VMScluster, 1-19 Services (SBS) registering, 1-16 Multireader queue, 1-4 Link drivers DECnet/OpenVMS, 1-7 N__________________________ definition of, 1-7 Names OSF/1, 1-7 See Symbolic names TCP/IP, 1-7 ULTRIX, 1-7 Index-3 O__________________________ R__________________________ Online release notes, 1-14 Release notes Operating systems, required file location of, 2-8 versions of, 1-15 selecting during installation, 2-7 P__________________________ Routing PAK See Message Routing See Product Authorization Run-time environments Key removing libraries during Primary queue, 1-3 installation, 2-11 Privileges for installation, 1-23 S__________________________ Processes SAF files See also User processes See Store and forward account quotas for (SAF) files installation, 1-25 SBS restoring symbol table See Selective Broadcast for, after installation Services (SBS) , 2-13 Secondary queues, 1-3 Product Authorization Keys Selective Broadcast (PAKs), 1-16 Services (SBS) registering and loading, See also Servers 1-16 definition of, 1-6 Q Servers ___________________________ definition of, 1-5 QCT Shutdown procedure See Queue Configuration adding to SYSHUTDOWN Table command procedure, Queue Configuration Table 2-15 (QCT) Startup procedure See also DMQ$INIT.TXT adding to SYSTARTUP file command procedure, Queue size 2-15 Determining, 1-11 Symbolic names Queues definition of, 1-7 SYSGEN See Message queues checking system parameter values with, 1-20 Index-4 SYSHUTDOWN command UCB procedure, 2-15 See User callbacks SYSTARTUP command procedure User processes , 2-15 See also Processes System parameters definition of, 1-4 for installation, 1-20 resources shared by, 1-4 Utilities T__________________________ AUTOGEN, 1-21 TCP/IP VMSINSTAL, 1-25, 2-6 See Transmission Control V Protocol/Internet ___________________________ Protocol (TCP/IP) VAX systems Transmission Control concurrent versions Protocol/Internet considerations for, Protocol (TCP/IP) 1-26 communicating from a VAX optional software for, system using, 1-2, 1-16 1-16 required operating system communications process, for, 1-15 1-6 VMSclusters DECmessageQ software loading licenses on, 1-19 relation to, 1-2 VMSINSTAL utility Troubleshooting invoking, 2-6 reporting problems during requirements, 1-25 , 2-15 VMSLICENSE command procedure, 1-17 U__________________________ Index-5