This chapter describes what you need to know before installing the Distributed Queuing Service for OpenVMS Systems (DQS) software on an OpenVMS AXP or OpenVMS VAX system. Table 1.1, “Summary: What You Need to Know” lists the topics included.

Related Information

Chapter 2, Do This First describes what you need to do before you install the DQS software.

Chapter 3, Using the PCSI Utility describes how to install the DQS client and server software with the PCSI utility. Chapter 4, Using the VMSINSTAL Utility describes how to install the DQS client and server software with the VMSINSTAL utility.

Refer to Distributed Queuing Service System Manager's Guide, for information on how to set up and manage DQS software on client and server nodes after installation.

For Information on Terms

This guide refers to DQS server nodes, client nodes, remote queues, and client queues. For a definition of these terms and concepts, refer to Chapter "Understanding the Distributed Queuing Service" in Distributed Queuing Service System Manager's Guide.

Hardware Required

DQS software can be installed on any Alpha AXP or VAX processor.

Operating System Versions

Installation of Distributed Queuing Service Version 1.3 for OpenVMS systems software requires one of the following:

Future Distributed Queuing Service for OpenVMS Systems releases may require higher versions of the operating system, as described in the online release notes or the product cover letter.

OpenVMS Tailoring Classes

The OpenVMS operating system comes with a variety of support options, or tailoring classes. Tailoring classes include such features as networking and RMS journaling. For full functionality of this layered product, the following tailoring classes are required:

Prerequisite Products

Table 1.2, “Summary: What You Need to Know” provides information on the software you must have installed on your system before installing DQS software.

For a complete list of the supported hardware configurations, required operating system components and software, see the DQS Software Product Description (SPD) included with your distribution kit. In addition, the SPD contains a complete list of prerequisite and optional software and their required version numbers.

Requirements

The DQS product supports the OpenVMS License Management Facility (LMF) provided by OpenVMS systems. Before you can start the DQS software, LMF requires that you register a License Product Authorization Key (License PAK) for the product. The License PAK is shipped with the kit if you ordered a license and media together; otherwise, it is shipped separately to a location specified by your license order. Use the LMF utility to register and load the information from your License PAK into your system’s license database.

Traditionally, each node that executes the DQS software requires a license.

Refer to the Distributed Queuing Service for OpenVMS Systems Software Product Description (SPD) for more information on DQS licensing. For information on how to license DQS software after it is installed, see the OpenVMS License Management Utility Manual .

Client Nodes

On a client node, every client queue you create that is not a generic or logical queue, creates one process. Also, the system creates a temporary process when the DQS software notifies the user of a print job completion.

Server Nodes

On server nodes, every incoming connection from a client node results in the creation of a process. Also, the notification process on a server node uses one permanent process.

Registration of Products with PCSI

If you are installing the DQS product with the PCSI utility, then any software product required for DQS installation must also be registered in the PCSI product database. Products installed with installation procedures other than the PCSI utility, such as the VMSINSTAL utility, cannot be registered in the PCSI product database.

For information on how to determine if products are registered in the PCSI database and how to register products in the database, see the section titled Perform First-Time Installation Activities in Chapter 2, Do This First.

New Startup File

Version 1.3 of the DQS software provides a new DQS$STARTUP.COM command procedure. Your older version of DQS$STARTUP.COM file is copied to DQS$STARTUP.COM_OLD. The new startup procedure does not contain DQS queue definitions or definitions for logical names that you can change. Instead an editable file, SYS$MANAGER:DQS$SYSTARTUP.TEMPLATE, is provided where you can make changes to DQS logical name definitions and define client queues. You copy this file by changing .TEMPLATE to .COM and making your changes.

Whenever, you execute the DQS startup procedure SYS$STARTUP:DQS$STARTUP.COM, it invokes the site-specific startup procedure SYS$MANAGER:DQS$SYSTARTUP.COM.

New Security and Queue Access System

Version 1.3 of the DQS software provides a new method to define a set of accessible server queues and to control access to these queues.

During the installation procedure, the DQS software attempts to use information from the currently running system to convert your server queue definitions into the new security and queue access system. This conversion may not be correct even though it is successful. After the installation you need to validate that your server queue definitions are correct.

Note

Make sure that the DQS software is running on the server node when you are installing server software. Conversion of your current server queue definitions into the new security and queue access system requires this. If DQS software is not running you have the following options:

Depending on your type of media and your system configuration, DQS installation takes:

DQS for OpenVMS AXP Kit

For OpenVMS AXP systems, the distribution kit contains:

DQS for OpenVMS VAX Kit

For OpenVMS VAX systems, the distribution kit contains:

Contact your VSI representative if any of the components of your kit are missing.

The DQS client and server software and documentation are also available online on the Consolidated Distribution CD-ROM.

Before Starting

Before you begin the installation, review the installation procedure.

Options

You can select to set up your system as:

A DQS server system can accept print requests from DQS client systems. DQS client systems initiate remote print requests.

When you select the DQS server option, the installation procedure also provides client support.

Overview

The DQS software operates in VMScluster environments. Printing within the VMScluster system does not require the DQS software. However, printing between VMScluster systems requires that you install the DQS software on each VMScluster.

VMScluster Considerations

When installing the DQS software on a VMScluster system, plan for the following:

Privileges Needed

To install DQS software, you must be logged in to an account that has SETPRV or at least the following privileges:

VSI recommends that you use the system manager account, SYSTEM. This account provides the privileges necessary to register your Product Authorization Key (PAK) and install the DQS software.

Determine Account Privileges

Determine your account privileges as follows:

$ SHOW PROCESS/PRIVILEGES Return

The DQS product provides online release notes. You should review the release notes because they describe new features and differences among multiple versions of the DQS software, as well as changes in the installation procedure.

For information on how to access the release notes before or after a PCSI installation, see Chapter 3, Using the PCSI Utility.

For information on how to access the release notes during or after a VMSINSTAL installation, see Chapter 4, Using the VMSINSTAL Utility.

Minimum Requirements

To Verify and Change Values

Use the OpenVMS Authorize utility to verify and change process quotas for the installation account in the user authorization file (SYSUAF.DAT). (Some sites may restrict the use of the OpenVMS Authorize utility to certain accounts or people.)

Example

To verify and then change the BYTLM quota for the account- name installation account, you might enter the following command sequence:

$ RUN SYS$SYSTEM:AUTHORIZE Return

UAF> SHOW account-name Return

UAF> MODIFY account-name /BYTLM = 18000 Return

UAF> EXIT Return

$ LOGOUT Return

For more information on modifying account quotas, see the description of the Authorize utility in the OpenVMS System Management documentation subkit.

Requirements

DQS requirements for free disk storage space are different during installation than after installation. Table 2.3, “Disk Space Requirements” summarizes the storage requirements. The numbers provided are approximate. Installation and use of the DQS software should not require more than the number of blocks listed in Table 2.3, “Disk Space Requirements”.

Extra for Server Account Directory

In addition, the disk where the server account directory is located requires extra space for temporary storage of files queued for printing. Disk space for storing files to be printed does not have to be on the system disk. See Distributed Queuing Service System Manager's Guide, chapter "Configuring and Managing a DQS Server" for information on how to move the server account directory to another device.

Procedure

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 Return

If you need to create free disk space, refer to the the OpenVMS Upgrade and Installation Manual or the OpenVMS DECwindows Motif Installation Guide.

If you need to move the server account to another disk, refer to Chapter 5, After Installing DQS Software, the section entitled Move the Server Account Directory to Another Device.

Reason

The DQS software installation requires fewer blocks of free disk space if you create a temporary working directory on an alternate device.

Before You Begin

You have the option of creating the working directory on the alternate device before you begin the installation. For example, to create the working directory [INSTALL] on the alternate device DUA2, enter:

$ CREATE/DIRECTORY DUA2:[INSTALL] Return

Options

Consider the following when deciding whether to specify a temporary working directory when installing the DQS software.

Examples

You can enter the following command to install the DQS software using an alternate working directory:

Using a DFS-mounted Disk

You can specify a DFS-mounted disk as your alternate working device. However, the DFS client (installation procedure) is unable to determine available disk space on the DFS-mounted disk and incorrectly reports a total of -1 free blocks.

Before using a DFS-mounted disk, determine its free disk space. Log in to the system on which the disk is locally mounted and enter the command:

$ SHOW DEVICE Return

Refer to Table 2.3, “Disk Space Requirements” for the amount of free disk space that must be on the DFS-mounted disk to complete the DQS installation.

Requirement

The DQS product supports the License Management Facility (LMF) provided by the OpenVMS systems. Before you can run the DQS IVP and start the DQS software, LMF requires that you register a License Product Authorization Key (License PAK) for the product. License PAK information is provided with the DQS product. Register and load this information into your system’s license database using the LMF utility.

Procedure

To register your license:

For complete information on using the LMF utility, see the OpenVMS License Management Utility Manual.

Overview

This section explains how to use the System Generation utility (SYSGEN) and the AUTOGEN utility to prepare your system for installation of the DQS software. AUTOGEN uses system configuration data to automatically set system parameters.

Required Values

Table 2.4, “Minimum Required System Parameter Values” lists the minimum required system parameters for the installation. These values do not represent the number required to run your system and other software.

If your your system does not have the necessary global pages and global section SYSGEN parameters, the installation fails.

Check Global Pages and Sections Parameters

To install and run DQS software, you must have sufficient free global pages and global sections. First find out how many free global pages and sections you have on your system. Then use AUTOGEN if you need to increase the global pages and global sections system parameters.

To check the values of the global pages and global sections parameters, use the DCL WRITE command with the F$GETSYI lexical function as follows:

$ WRITE SYS$OUTPUT F$GETSYI("CONTIG_GBLPAGES")
7578
$ WRITE SYS$OUTPUT F$GETSYI("FREE_GBLSECTS")
143

If the SYSGEN values displayed by the system are greater than the values listed in Table 2.4, “Minimum Required System Parameter Values”, you do not need to increase them. If the values of the global pages and global sections parameters displayed by the system are less than the values listed in Table 2.4, “Minimum Required System Parameter Values”, you must increase their values. Proceed to the next section.

Change Global Pages and Sections Parameters

Use the AUTOGEN command procedure to change system parameters. AUTOGEN automatically adjusts values for parameters that are associated with the values you reset manually.

ADD_GBLPAGES = 2000

$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT Return

The AUTOGEN utility automatically adjusts some of the SYSGEN parameters based on the consumption of resources since the last reboot. If you do not want to take advantage of this automatic adjustment, include the NOFEEDBACK qualifier on the AUTOGEN command line. For example,

$ @SYS$UPDATE:AUTOGEN GETDATA REBOOT NOFEEDBACK Return

For more information about using the AUTOGEN utility, see the OpenVMS System Manager’s Utilities Reference Manual.

PCSI Utility

These activities apply if you are installing the DQS software with the PCSI utility.

Register Products in PCSI Database

The PCSI utility checks for software products required for installation and use of the DQS software. These products need to be registered in the PCSI product database.

For example, DQS installation requires either of the following:

To determine if the required operating system software is registered and to register the product, if required, do the following:

Using the Motif Interface

Perform the following steps to check the operating system software on Motif:

$ PRODUCT Return

Using the DCL Command Line Interface

Perform the following steps to check the operating system software from DCL:

$ PRODUCT SHOW PRODUCT *VMS Return

$ PRODUCT REGISTER PRODUCT -
_$ VMS/VERSION=6.0 /SOURCE=SYS$UPDATE: Return

Overview

Near the beginning of the installation, the installation utility asks if you completed the pre-installation tasks. VSI recommends that you do a system disk backup before installing any software. Use the backup procedures that are established at your site.

For details on performing a system disk backup, see the section on the Backup utility in the OpenVMS System Management documentation subkit.

Before proceeding with the installation of the software, refer to the flowchart in Distributed Queuing Service for OpenVMS Systems Installation Guide.

Procedure

To extract a copy of the release notes for the DQS product to an online disk, enter:

$ PRODUCT EXTRACT RELEASE_NOTES DQS /VERSION=Vn.n /FILE=output-file-name Return

Where:

By default the PCSI utility searches the location defined by

PCSI$SOURCE. If the software kit is in another location, this location must be specified with the /SOURCE qualifier on the command line.

$ PRODUCT EXTRACT RELEASE_NOTES DQS /VERSION=Vn.n /SOURCE=location /FILE=output-file-name Return

After extracting the release notes to a file, you can print or view the file. You do not need to install the software before you extract the release notes.

After the Installation

After you install DQS software, type or print the release notes file from:

SYS$HELP:DQSnnn.RELEASE_NOTES

The nnn represents the version number. For example, 013 stands for Version 1.3.

Command To Use

To start the installation of the DQS software, enter the PRODUCT INSTALL command at the DCL prompt.

If this is the first time you are installing the DQS software, include the /HELP qualifier on the command line. /HELP provides detailed explanations about the product and product options. When you perform subsequent installations or upgrades, you can choose to bypass the explanations to save time.

The following command installs Version 1.3 of the DQS software with detailed explanations:

$ PRODUCT INSTALL DQS/VERSION=1.3 /HELP Return

The installation utility displays messages like the following and asks if you want to continue:

$ PRODUCT INSTALL DQS/VERSION=1.3 /HELP Return
The following product has been selected:
DEC [AXP|VAX]VMS DQS Vn.n [Available]

Do you want to continue [YES] Return
*** DEC [AXP][VAX]VMS DQS Vn.n: DEC [AXP][VAX]VMS DQS Vn.n for OpenVMS

    Requires from nnn to nnn disk blocks depending upon configuration.
    The DEC Distributed Queuing Service for OpenVMS Systems uses the
    DECnet networking system to extend the standard OpenVMS queue
    system to enable users to print jobs connected to other systems
    than their own, and to show the status of, cancel, and change the
    specifications of their jobs on those systems.

   Copyright © 1994 Digital Equipment Corporation
   All Rights Reserved. Unpublished rights reserved under the copyright
   laws of the United States.
.
.
.

Specifying Kit Location

You can specify the location (source) of the DQS kit in one of two ways:

For this example, MYDISK$:[NEW_PRODUCTS] contain s the DQS kit for installation.

Command Line Features

You can also request features like purging files and running the installation verification procedure (IVP) by adding appropriate qualifiers to the PRODUCT INSTALL command line. Table 3.2, “Features You Can Request When Starting an Installation” lists features you can control with command qualifiers.

For more detailed information on all features that you can request when starting an installation, refer to DCL help for the PRODUCT INSTALL command.

DCL HELP Options

The following DCL help options are available:

Overview

During installation, the PCSI utility allows you to accept or change the defaults. Default values are enclosed in brackets ([ ]).

DQS Default Values

The DQS software offers you the option to install or not install the server software on the system. The client software is always installed. The initial installation default is to install client software only.

The DQS client software will be installed automatically on this node
Do you want to install the DQS server software on this node? [NO]

If you are installing the DQS software on a system that has a printer that you want to make available to clients on other systems, then you enter YES and press the Return key.

This action changes the default value for this question to YES. The next time you install the DQS software, the question is:

The DQS client software will be installed automatically on this node
Do you want to install the DQS server software on this node? [YES]

Verify Tasks

During the installation procedure, you are asked if you completed the preinstallation tasks for the DQS software.

You need to complete the pre-installation tasks to install the DQS software.
 Do you want to continue [YES] 

Tasks Checked by PCSI Utility

The PCSI utility might verify that any or all of the following is true, depending on your product:

When the PCSI utility detects a problem in any of these areas, it asks if you want to terminate the installation. If you want to stop the installation, press the Return key. If you want to continue, enter NO.

Not Checked by PCSI Utilty

The PCSI utility does not check process quotas or system parameters. You need to make sure that these values are sufficient.

You must also make sure that the DQS software is running if you are upgrading from a version of the software before Version 1.3 and you are installing server software.

To stop and restart the installation:

Valid Responses

The following are valid responses to questions asked during an installation:

Questions You Are Asked

While installing the DQS software with the DCL interface, you might be asked the following questions. (Refer to Appendix B, Sample Installations to see sample installation dialogs.)

Progress

As an installation procedure progresses, the system displays a percentage to indicate how much of the installation is done. For example:

Portion Done: 10%...20%...30%...40%...50%...70%...80%...90%...100%
The following product has been installed:
DEC VAXVMS DQS V1.3
.
.
.

If you started the installation using the /LOG qualifier, the system displays details of the installation.

To start the installation of the DQS software, enter the SET DISPLAY and PRODUCT commands at the DCL prompt.

$ SET DISPLAY/CREATE/NODE=mynode
$ PRODUCT Return

PCSI Main Window

The PCSI main window opens (see Figure 3.1, “PCSI Main Window”). The items in this window include the following:

Procedure to Install

Use the following procedure to install the DQS software using the Motif interface (see Figure 3.2, “PCSI Installation Window”).

Motif Help Options

The following Motif help options are available:

Motif help topics

Motif help describes how to get started performing a task from the Motif interface.

For information about how you can customize menus by adding and removing menu items, refer to the Customize help topic for each menu.

How to Select

After you select the product, you can select and display information about product options by clicking on icons or by choosing items from the Options menu. You can also double-click on the options name to get a full description of the option.

Available Options

The DQS product offers these options:

The client software is always installed, but does not need to be configured for a server node. Choose to install the server software if your node has a printer that you want to make available to clients on other systems in the network.

Procedure

To stop and restart the installation:

How to Recover

This section describes how to recover from errors during product installation.

If the installation procedure fails for any reason, the following message is displayed:

%PCSI-E-OPFAILED, operation failed
Terminating is strongly recommended.
Do you want to terminate? [YES]

An error during the installation can occur if one or more of the following conditions exist:

If you receive any error message beginning with %PCSI-, refer to OpenVMS System Messages and Recovery Procedures Reference Manual for an explanation and possible solution to the problem.

Most Distributed Queuing Service for OpenVMS Systems software messages have the same format as standard OpenVMS system messages: %DQS-E-ident, text.

If the installation fails, you must restart the installation procedure. If the installation fails due to an IVP failure, contact a VSI Services representative.

During the Installation

You can read or print the DQS release notes before installating the DQS software. To do this, you must include OPTIONS N on the command line when you invoke the VMSINSTAL procedure:

$ @SYS$UPDATE:VMSINSTAL DQS013 MUA0: OPTIONS N Return

OPTIONS N allows you to select release notes options:

Release notes included with this kit are always copied to SYS$HELP.

Additional Release Notes Options:
   1. Display release notes
   2. Print release notes
   3. Both 1 and 2
   4. None of the above
* Select option [3]: Return

Queue name [SYS$PRINT]: Return

Job DQS013 (queue queue, entry nnn) started on device

VSI recommends that you read the release notes before installing the DQS software for the first time.

After you have answered the questions regarding the release notes, this message is displayed:

* Do you want to continue the installation [N]? YES Return

Enter YES or NO, as appropriate. If you enter YES and press the Return key, the procedure continues with this message:

%VMSINSTAL-I-RELMOVED, The products release notes have been successfully moved to SYS$HELP.

After the Installation

After the installation procedure completes, release notes are available from the following location:

SYS$HELP:DQSnnn.RELEASE_NOTES

The nnn represents the version number. For example, 013 stands for Verison 1.3.

Before You Start

Before you start the installation of the DQS software, log in to the system manager account. The system manager account has the necessary privileges to run the VMSINSTAL utility.

Logging Your Installation Procedure

If you want to save a copy of your VMSINSTAL session for future reference, you can enter the SET HOST 0 /LOG command at the system prompt before starting the installation of the software. This creates the log file SETHOST.LOG in your current default directory.

Command Line

To start the installation of the DQS software, enter the following command at the DCL prompt:

$ @SYS$UPDATE:VMSINSTAL DQSnnn dev: [OPTIONS N,AWD=dev:[dir]] Return

@SYS$UPDATE:VMSINSTAL invokes the VMSINSTAL procedure. In addition, you can supply the following information in the command line:

SYS$SPECIFIC:[SYSUPD.DQS$nnn]

In response to the VMSINSTAL command, a banner like the following may be displayed on the screen:

OpenVMS VAX Software Product Installation Procedure Vx.x

It is 11-JUN-1994 at 15:47.
Enter a question mark (?) at any time for help.

To stop the installation procedure at any time, press Ctrl/Y. The installation procedure deletes all files it has created up to that point and exits.

If you want to retry the installation procedure after you press Ctrl/Y, you must invoke VMSINSTAL again, as shown in the section titled Starting the Installation Procedure.

Valid Responses

The VMSINSTAL utility asks a series of questions to which you must provide answers. The following are valid responses to questions asked during an installation:

Questions You Are Asked

During the installation of the DQS software with the VMSINSTAL utility, you are asked the following questions:

Getting Help on VMSINSTAL Questions

To get help on any of the VMSINSTAL questions, enter a question mark ( ? ) in response to the question.

After validating that you have loaded the DQS License PAK, VMSINSTAL asks no more questions.

No further questions.

Status Messages

The DQS installation procedure then creates the DQS$SERVER account and directory, installs the client software, installs the server software if selected, and creates the DQS network object. VMSINSTAL displays informational messages about the status of the installation, like the following:

%VMSINSTAL-I-RESTORE, Restoring product saveset B...
%VMSINSTAL-I-ACCOUNT, This installation creates an ACCOUNT named DQS$SERVER.
%UAF-I-ADDMSG, user record successfully added
%UAF-I-RDBADDMSGU, identifier DQS$SERVER value: [000300,000311] added to rights database

       DQS$SERVER account is created.
%VMSINSTAL-I-ACCOUNT, This installation updates an ACCOUNT named DQS$SERVER.
%UAF-I-MDFYMSG, user record(s) updated
%VMSINSTAL-I-SYSDIR, This product creates system disk directory
                                                      SYS$COMMON:[DQS$SERVER].
[DQS$SERVER] directory is created in SYS$COMMON: area.

Installing DQS SERVER software . .
 .
Installing DQS CLIENT software . . 
.
DQS network object is created.

Informational Messages

VMSINSTAL displays the following informational messages that concern system parameter requirements and postinstallation procedures:

******************************************************************
*              Instructions for completing DQS installation *
******************************************************************
   o Please follow the post installation instructions which have
     been outlined in the DQS V1.3 Installation Guide.
   o Please be sure to edit your OpenVMS System Startup Procedure
     and add the following line to invoke the DQS Startup Procedure:
            $ @SYS$STARTUP:DQS$STARTUP.COM
   o Once you have completed the DQS post installation procedures
     you can invoke the DEC DQS installation verification procedure
     to test your customizations. To invoke this file start DQS
     and type:
            $ @SYS$TEST:DQS$IVP.COM
   o This installation has updated the DCL Tables. Therefore
     users must log out and then back in, in order to use the
     QSHOW, QDELETE, and QSET commands for displaying, deleting,
     and modifying jobs on the remote server queues.
   o Please read the DQS V1.3 release notes located in the file
     SYS$HELP:DQS013.RELEASE_NOTES .
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...

Verification Messages

If you indicated that you want to run the IVP as part of the installation, the following messages are displayed; otherwise, this step is skipped:

Beginning of the DQS V1.3 Installation Verification Procedure.
  Copyright Digital Equipment Corporation 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.
  %DQS-I-QUESUCCESS IVP test successful
End of the DEC DQS for OpenVMS V1.3 Installation Verification Procedure

The IVP checks to see if files are installed in the correct locations. Then, the IVP displays the following message:

%DQS-I-QUESUCCESS IVP test successful

Procedure Ending Messages

Once installation is completed, this message appears:

Installation of DQS Vn.n completed at hh:mm
VMSINSTAL procedure done at hh:mm

The message from VMSINSTAL means that the installation and verification (if selected) of the DQS software has com pleted successfully. If VMSINSTAL reports a failure, review the installation prerequisites.

You can run the IVP at any time to check the DQS software.

Refer to Chapter 5, After Installing DQS Software for more information on postinstallation procedures, including:

For details on setting up the DQS queues, see Distributed Queuing Service System Manager's Guide.

This section describes the tasks you may need to perform if this is a new installation of the DQS software on a DQS server node and tells you where to look for more information, if needed.

Move DQS Server Account Directory

The DQS server uses a directory to temporarily store copies of the files that it is printing for DQS clients. These print files vary in size. Depending on the requirements of your environment, you may need to move this directory to an alternate device. DQS software provides a command procedure that enables you to change or move this directory to a different device.

If needed, move the DQS server account default directory to another device.

Reference

See the section titled Move the Server Account Directory to Another Device in Distributed Queuing Service System Manager's Guide, chapter "Configuring and Managing a DQS Server" for details.

Define Server Queues

Before client nodes can access remote queues on your server node using the DQS software, define the set of queues on a DQS server node that may be made accessible to remote queues.

Reference

See the section titled Setting Up Remote Queues in Distributed Queuing Service System Manager's Guide, chapter "Configuring and Managing a DQS Server" for details.

Customize Server Software

If you need to change DQS server logical definitions that relate to the behavior of the server software, do the following:

Reference

See Distributed Queuing Service System Manager's Guide, chapter "Configuring and Managing a DQS Server" for details on managing a DQS server.

The next sections describe the tasks you may need to perform if this is a new installation of the DQS software on a DQS client node and tells you where to look for more information, if needed.

Customize Client Software

Customize the DQS client software for your specific environment.

If you need to change DQS client logical definitions that relate to the behavior of the client software, do the following:

See the Distributed Queuing Service System Manager's Guide, chapter "Configuring and Managing a DQS Client" for details on managing a DQS client.

This section describes the tasks you may need to perform on all sytems if this is a new installation of the DQS software.

Edit System Startup File

Edit the system startup file and add the command line that starts the DQS software.

DECnet Phase IV systems

With DECnet Phase IV networking software, the DQS software must start after the network has started. You must position this new command line after the line that invokes the network startup command procedure. The following is a sample portion of a system startup file that has been edited to start the DQS software:

$ @SYS$MANAGER:STARTNET.COM    ! Start DECnet software
    .
    .
    .
$ @SYS$STARTUP:DQS$STARTUP.COM    ! Then start DQS software

Some installations use a batch job to start the network. With DECnet Phase IV networking software, the job that starts the network must complete before the DQS software can be started. The following portion of a system startup file shows one way to ensure that the network starts before the DQS software:

$ SUBMIT -
 SYS$MANAGER:STARTNET.COM, - ! Start DECnet software, first
    .
    .
    .
 SYS$STARTUP:DQS$STARTUP.COM ! Then, start DQS software

DECnet Phase V systems

These examples do not apply to the networks running the DECnet/OSI Phase V networking software. DECnet Phase V software is started automatically. Check system startup requirements for any restrictions on the placement of the DQS startup command.

Start DQS Software

The installation procedure does not start the DQS software. On all nodes that you want to run the DQS software, execute this command:

$ @SYS$STARTUP:DQS$STARTUP.COM Return

You can also use the SYSMAN utility to start DQS software in a VMScluster environment.

Running IVP

To run the IVP independently of the installation procedure, enter the following command at the DCL prompt:

$ @SYS$TEST:DQS$IVP.COM Return

The DQS IVP is a command procedure that verifies that the DQS files are installed correctly. The installation procedure places the IVP command file, DQS$IVP.COM, in the SYS$TEST directory.

To troubleshoot a failed IVP, you can verify that each directory contains its proper file names by entering the following command at the DCL prompt:

$ DIRECTORY SYS$COMMON:[SYS*]*DQS* Return

Activate DCL Command Table

The installation procedure modifies the DCL command table so that the DQS commands are recognized and processed.

Users who are logged on during the installation process can use the DQS PRINT command immediately. However, other DQS commands: QSHOW, QDELETE/ENTRY, QSET/ENTRY are not available.

Notify all logged-in users who want to use the QSHOW, QDELETE/ENTRY, QSET/ENTRY commands that they need to do either of the following:

This section describes the tasks you may need to perform if this is an upgrade installation of the DQS software on a DQS server node and tells you where to look for more information, if needed.

Move DQS Server Account Directory

The DQS server uses a directory to temporarily store copies of the files that it is printing for DQS clients. These print files vary in size. Depending on the requirements of your environment, you may need to move this directory to an alternate device. DQS software provides a command procedure that enables you to change or move this directory to a different device.

Reference

See the section titled Move the Server Account Directory to Another Device in Distributed Queuing Service System Manager's Guide, chapter "Configuring and Managing a DQS Server" for details.

Verify Queue Access Definitions

If your DQS server system is running the DQS software during the installation procedure, the procedure converts the Version 1.n server queue access definitions to the new format provided with DQS Version 1.3 software. The installation procedure creates the following file, which should contain the queue access definitions for your environment:

SYS$MANAGER:DQS$SERVER_CONFIG.TXT

The queue access definitions are specified in your DQS$STARTUP.COM file. The installation procedure renames your previous DQS$STARTUP.COM to DQS$STARTUP.COM_OLD.

Please review your DQS$STARTUP.COM_OLD file and compare it to the queue access definitions in the new .TXT file

Check the following log file for any issues encountered during the conversion of your queue definitions to the new security and access format:

$ TYPE SYS$UPDATE:DQS$CONVERT_SECURITY.LOG Return

Remove Rightslist IDs

After DQS Version 1.3 software has been running on your system for a few weeks and you are satisfied with the operation of the new queue access mechanism, you may want to remove all the DQS$NODE_xxxx rightslist identifiers from your rightslist database. Do not do this until you are sure that you do not want to go back to a DQS Version 1.2 environment.

Use the OpenVMS Authorize utility to remove the rightslist identifiers that were used prior to DQS version 1.3.

The DQS V1.3 rightslist identifiers have the form DQS$NODE_nodename, where nodename is a 6-character DECnet node name.

Procedure

Use the following procedure to remove a rightslist identifier:

$ MCR AUTHORIZE
UAF> REMOVE/IDENTIFIER DQS$NODE_nodename
UAF> EXIT

Example

The following example removes DQS$NODE_SMEDLY and DQS$NODE_JON JON from the rights list database:

$ MCR AUTHORIZE
UAF> REMOVE/IDENTIFIER DQS$NODE_SMEDLY
Identifier DQS$NODE_SMEDLY value: %X800100A2 removed from rights data base
UAF> REMOVE/IDENTIFIER DQS$NODE_JONJON
Identifier DQS$NODE_JONJON value: %X800100A3 removed from rights data base
UAF> EXIT

Customize Server Software

With DQS Version 1.3, the DQS startup procedure is divided into two files:

DQS$STARTUP.COM invokes SYS$MANAGER:DQS$SYSTARTUP.COM, which contain s all the customizations.

A site-specific startup template that you can customize is provided your convenience:

SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.TEMPLATE

Procedure

To change server logical definitions, perform the following:

DQS server queue access is no longer defined by adding logical definitions to the startup procedure. Do not copy the following logicals to your DQS$SYSTARTUP.COM file:

See Distributed Queuing Service System Manager's Guide, chapter "Configuring and Managing a DQS Server" for details on customizing a DQS server.

This section describes the tasks you may need to perform if this is an upgrade installation of the DQS software on a DQS client node and tells you where to look for more information, if needed.

Customize Client Software

Customize the DQS client software for your specific environment.

With DQS Version 1.3, the startup procedure is divided into two files:

DQS$STARTUP.COM invokes SYS$MANAGER:DQS$SYSTARTUP.COM, which contains all the definitions.

A site specific startup template that you can customize is provided your convenience:

SYS$COMMON:[SYSMGR]DQS$SYSTARTUP.TEMPLATE

To change client logical definitions perform the following:

See Distributed Queuing Service System Manager's Guide, chapter "Configuring and Managing a DQS Client" for details on customizing a client.

This section describes the tasks you may need to perform on all sytems if this is an upgrade installation of the DQS software.

Edit System Startup File

Look in the system startup procedure for the one of the following lines:

DQS Version 1.3 software requires that the DQS software start from the SYS$STARTUP directory. Change the command to the following if it was not already changed:

@SYS$STARTUP:DQS$STARTUP.COM

Do this on each node of a cluster that you want to run the DQS software. DQS software then starts automatically when the node reboots.

Start DQS Software

The installation procedure does not start the DQS software. On all nodes that you want to run the DQS software, execute this command:

$ @SYS$STARTUP:DQS$STARTUP.COM Return

You can also use the SYSMAN utility to start DQS software in a VMScluster environment.

Run IVP

To run the IVP independently of the any installation procedure, enter the following command at the DCL prompt:

$ @SYS$TEST:DQS$IVP.COM Return

The DQS IVP is a command procedure that verifies that the DQS files are installed correctly. The installation procedure places the IVP command file, DQS$IVP.COM, in the SYS$TEST directory.

To troubleshoot a failed IVP, you can verify that each directory contains its proper file names by entering the following command at the DCL prompt:

$ DIRECTORY SYS$COMMON:[SYS*]*DQS* Return

Update Server Queues

After the DQS software is running, if you installed the DQS software on a server node, execute the following command procedure:

$ @SYS$MANAGER:DQS$SERVER_UPDATE_QUEUE_DEFNS Return

DQS Version 1.3 software does not require DQS queues to have the /RETAIN queue attribute. This command procedure allows you to change the definitions of your DQS queues to eliminate these attributes.

Activate DCL Command Table

The installation procedure modifies the DCL command table so that the DQS commands are recognized and processed.

Users who are logged on during the installation process can use the DQS PRINT command immediately. However, other DQS commands: QSHOW, QDELETE/ENTRY, QSET/ENTRY are not available.

Notify all logged-in users who want to use the QSHOW, QDELETE/ENTRY, QSET/ENTRY commands that they need to do either of the following:

This section describes the tasks you may need to perform on a VAXcluster system.

Edit System Startup File

Edit the system startup file and add the following line to start the DQS software for each cluster member where the DQS software is to execute:

$ @SYS$STARTUP:DQS$STARTUP

Replace DCL Tables

If you install DQS client software on a VMScluster member, the DCL tables are updated to include the DQS QSHOW, QDELETE /ENTRY, and QSET/ENTRY commands on that member only. To include these commands in the DCL tables of other cluster members, either execute the SYSMAN utility or issue the following commands from the system manager’s account on each cluster member:

$ INSTALL Return
INSTALL> REPLACE SYS$SHARE:DCLTABLES Return
INSTALL> EXIT Return
$

Define Network Object

The DQS network object must be defined on each node within the VMScluster where you want to run DQS software.

On DECnet Phase IV systems, use the Network Control Program. On DECnet/OSI Phase V systems, use the Network Control Language (NCL).

NCP Commands

To define the DQS object using NCP, execute the SYSMAN utility or follow these steps:

NCL Commands

To define the DQS object using NCL, execute the SYSMAN utility or enter the following NCL commands on each of the other nodes in the VMScluster environment:

s>(NCL>) CREATE SESSION CONTROL APPLICATION DQS
NCL> SET SESSION CONTROL APPLICATION DQS, -
_NCL> ADDRESS = {NUMBER=66}, IMAGE NAME = DQS$SERVER.EXE, -
_NCL> INCOMING PROXY = FALSE, OUTGOING PROXY=FALSE, -
_NCL> NODE SYNONYM=FALSE, USER NAME = "DQS$SERVER"
Node 0 Session Control Application dqs
at 1994-03-16-13:34:58.193-05:00I1.614
Characteristics
Addresses =
{
number = 66
}
Image Name = DQS$SERVER.EXE
Incoming Proxy = False
Outgoing Proxy = False
Node Synonym = False
User Name = "DQS$SERVER"
NCL> EXIT