The following chapters use some special symbols to define the syntax of various commands, qualifiers and parameters. These comprise one or more items. Each item is a group of alphabetic or numeric characters including some punctuation characters. The blank characters, space and tab, are used to separate items and cannot normally be included in an item. The <Return> or <Enter> keys are used to terminate a line of text input.

When the command line is scanned, most items will be converted from UPPER CASE (capital letters) to lower case. It is not normally important whether items are entered in lower or upper case. In the rare instances where case is significant, items can be protected by being enclosed in "double quotes".

Computer input and output is shown in Courier typeface. In the examples shown below, all user input is shown in Courier bold.

The symbolic names of each of the component items which make up the command its options, and parameters, are shown in italics (e.g. target, or target). When you type the command, the item should be replaced by an appropriate entry.

Repetition of an item is indicated by a horizontal or vertical ellipsis: ...

When optional qualifiers are allowed by a command, the descriptive name of the optional item is enclosed in square brackets, including any blank characters that may be required (e.g. [ optional_qualifier]). You should not type the square brackets.

Where a number of alternative options can be provided, these are shown enclosed in braces, and separated by the vertical bar character '|'.

For example:

LANSAVE {FULL | INCREMENTAL} - {@CONTROL-FILE-NAME | \\PCNAME\RESOURCE[\PATH] TAPE:SAVESET}

To simplify the syntax definition expressions where it is not necessary to be explicit, blank characters are simply left as blank spaces between items and the presence of a <Return> character at the end of a line is assumed. In common with normal DCL command processing, it is possible to extend a command over several lines by the addition of a trailing dash character ('-') to each preceding line. Also, any comments should be preceded by an exclamation mark character ('!').

Most of the command definitions include examples. In these examples, the DCL $ prompt is displayed on your terminal by VMS. The following items on the line (shown in bold) are what you type in. Some of the examples also include a display of the output that would be expected. This is shown on following lines (in Courier), as it would normally appear. Command examples on MS-DOS follow the same pattern.

Throughout this manual the term VMS is used to represent both the VMS and OpenVMS operating systems.

The terms "Send", "Write", and "Transmit" are used interchangeably throughout this document, as are the terms "Read" and "Receive", and "Task" and "Process". The term "Adapter" is used to refer to both the hardware and software of the NetBIOS interface to the network.

Text that has been added or revised in this version is marked with a change bar, as shown to the left.

The following privileges should be enabled for the SYSTEM account: NETMBX, OPER, TMPMBX, SETPRV, SYSPRV, SYSNAM, CMKRNL. These privileges are sufficient to start the package and to use all LANprint utility programs. Users who wish to submit jobs to a LANprint queue simply require write (W) or execute (E) access to the queue.

The installation process comprises two parts. It is necessary to install the host software on the selected VMS system(s) or cluster, and also, if necessary, you can install the MS-DOS LANprint/PC software on a gateway PC which is to re-direct print jobs to print servers that do not allow a direct SMB/LAN Manager protocol connection. This chapter provides step-by-step guidelines on installing both host and PC software. Appendix A includes further reference information, and example installation & configuration dialogues.

LANprint includes native (re-compiled) support for Alpha AXP systems, thus offering the full performance benefit of the Alpha architecture.

Please refer to Chapter 2 for disk space, operating system, and network software requirements for this package.

If you are intending to use LANprint with a LANlink or LANbridge package, you should refer to the documentation supplied with that package for details on installing and configuring the network transport on the host and on the PC(s) before starting the installation of LANprint.

LANprint is installed on VMS using VMSINSTAL. The package files are copied into directory tree SYS$COMMON:[VIA...], or a user-specified area, during the installation process. More detailed instructions concerning the VMSINSTAL procedure can be found in Appendix A.

LANprint may be installed on a single VMS system or VMScluster. Where multiple single systems are to be licensed, or multiple VMSclusters, LANprint must be installed separately on each one.

LANprint is supplied as an evaluation kit. This kit will function for a limited period and must be upgraded for permanent use with a Product Licence Key which can be obtained from your supplier. The product keying process is described later in this chapter.

Before commencing the installation process, it is essential that the host DECnet or TCP/IP configuration and any PC PATHWORKS installations have been completed and tested to ensure correct operation.

3.1 Preparing to Install the Package

LANprint does not require any special VMS or SYSGEN parameters, but each symbiont process does consume a VMS process slot so you may wish to check the MAXPROCESSCNT parameter. It is also important to ensure that the appropriate VMS tailoring classes are restored if they have been removed from the system.

If you are installing an update to a previous version of this package, you should ensure that the previous version is not running before starting the new installation. See Section 3.11 for details on shutting down a running LANprint package, and Section 3.9 for details on the update procedure.

Checking MAXPROCESSCNT

Since the package makes use of Print Symbionts that are run as detached processes, you must beware of the system parameter MAXPROCESSCNT. This restricts the maximum number of processes that can run simultaneously in the system and it may be necessary for MAXPROCESSCNT to be increased if there are insufficient process slots available for the number of queues you require. Each Symbiont process can handle up to 16 queues, so this is normally only an issue on a system that has very few free process slots. The DCL SHOW MEMORY command will show the number of process slots available. If this is insufficient then AUTOGEN must be used to increase MAXPROCESSCNT - consult your VMS documentation for further details.

Tailoring Classes

This installation requires the presence of the entire 'Programming' and 'System Programming' tailoring classes. These are contained in the VMS 'Library' saveset. If you have used VMSTAILOR to remove either of these classes from your system, or any of their sub-classes, then these should be recovered in their entirety before this installation is attempted. Please refer to your VMS documentation for further details.

3.2 Host Installation

To install LANprint, login to the SYSTEM account on the selected VMS host. If you are installing LANprint on a VMScluster, make sure that you are logged in to a cluster node which contains a cluster-common system disk.

If this is an upgrade installation, you should shutdown any active LANprint print queues. See Section 3.11 for details on shutting down LANprint.

Execute VMSINSTAL using the following command:-

$ @sys$update:vmsinstal vialpp source options n

where source is the name of the distribution kit source tape drive (e.g. mua0:) or the name of the directory containing the distribution kit (in the case of CD-ROM kits, or where the kit has been uploaded from tape).

The first example below shows a typical installation from tape, and the second example shows an installation from CD:-

$ @sys$update:vmsinstal vialpp mka500: options n $ @sys$update:vmsinstal vialpp dka400:[vector.vialpp] options n

Please refer to Section 2.1 for details of disk space requirements for this package.

The installation procedure will ask whether the package should be installed on the system disk (the default). If you wish to install the software on another disk, you should enter the device name when prompted, preferably using a logical name. All Vector Networks products should be installed on the same disk, or you may suffer conflicts between different packages defining conflicting logical names.

For example:-

. . . * Disk name for this installation [SYS$COMMON] : disk$applications . . .

The default location is SYS$COMMON.

This package includes online documentation that can be accessed with the DECwindows Bookreader application on a workstation or X-Windows terminal. The installation procedure will ask if the online documentation files should be installed, and, if so, it will copy them to directory [VIA.DOC]. Please refer to Section 3.3.10 for details on configuring Bookreader to access these files.

The VMS LANprint kit also includes copies of this manual in PostScript format which can be installed on the VMS system's disk for subsequent printing on a PostScript printer. Vector Networks is happy for customers to print additional copies of this manual providing they remain unmodified; Vector Networks retains full copyright over the manual content. This PostScript version of the manual is provided in two formats: one paged for printing on A4 (297mm x 210mm) paper, and the other paged for US LTR (279mm x 216mm) paper. (Please refer to Section 2.1 for disk space requirements for these files.) These files are only useful to sites that have access to a PostScript printer. The installation procedure will ask if either of these files should be installed, and, if so, it will copy them to directory [VIA.DOC].

This package also includes PC software which is usually installed from PC floppy disk, however, the PC software is also included within the VMS kits as a further optionally installable item. This can be useful if you wish to install the PC software on a PATHWORKS file or disk service - you can copy (or import) the files directly into the service without having to use a PC. Note that these files must be copied in binary mode - they are already in DOS file format. The installation procedure will ask if the PC files should be installed on the VMS host's disk. If so, they are copied to directory [VIA.DOS.LANPRINT].

LANprint includes support for DECnet and/or TCP/IP (given a compatible VMS TCP/IP stack). The installation allows you to choose whether you want LANprint to default to the DECnet transport, or whether you want TCP/IP to be the default.

There is no Installation Verification Procedure (IVP) for this package.

The installation process will link all system-dependent images to suit your operating system version and will copy the LANprint Symbiont program image into system directory SYS$SYSTEM:. Unfortunately, there is no choice about print Symbionts being in this directory, as this is the only location that is searched by the VMS Job Controller when a Print Queue is started. Other package files will be copied to the SYS$COMMON:[VIA...] directory tree (all directories will be created if necessary).

An example Symbiont Startup command procedure is created and copied into directory SYS$COMMON:[VIA] during installation. After this file has been modified to suit the local configuration, the System Manager may wish to invoke it during system startup, see Section 3.3.1 and Section 3.3.3.

Similarly, a sample package shutdown command procedure (VIALPPSHUTDOWN.COM) will be copied to SYS$COMMON:[VIA]. This can be used to perform an orderly shutdown of the LANprint package, after appropriate modification. See Section 3.11.

VMSINSTAL will then exit.

Since LANprint contains a program image (NPDRIVER.EXE) which is linked against the VMS system symbol table, it may be necessary to repeat the installation process whenever a major update is applied to VMS.

Further instructions on VMSINSTAL are contained in Appendix A. Example A-1 shows a sample installation & configuration dialogue. Section 3.3 describes the steps required to configure the package before use.

3.3 Host Configuration

Once the host files have been installed, it will be necessary to edit the Printer Database template file, LPPDATABASE.DAT, to define print servers that are to be accessed with LANprint. Each remote print resource requires a separate entry in the template file. This file defines NetBIOS access and routing information to connect each VMS Print Queue with a remote print resource. The package includes a sample database with definitions for typical print resources. The format of the template file is described in Section 4.1.

When the template file has been edited, the Printer Database is constructed by running the Database builder program LPPDATABASE.EXE. This reads the template file and creates the RMS indexed file LPPDATABASE.BIN. Each record in this file defines one remote printer resource.

The contents of the Database can be verified using the query program LPPQUERY.EXE. Similarly, the connection to the remote print resource can be tested with the LPPPRINT.EXE program. This is a simple single file printing program which uses the Printer Database to access the remote print server. These programs are described in Section 5.2 and Section 5.3, respectively.

The Print Symbiont reads the Printer Database whenever a new print queue is started. The database file is accessed using the path LPPDIR:LPPDATABASE.BIN. If the LPPDIR logical name is not defined in the SYSTEM Name Table, or there is no Printer Database in that directory, then the Symbiont will exit with status %RMS-E-FNF, file not found. The database key is the name provided by the /ON=device_name qualifier to the DCL INITIALIZE/QUEUE command. This allows the Symbiont to obtain the routing information for the remote resource. If the record corresponding to the device_name parameter is not found in the Database, the DCL START/QUEUE command will fail with error %RMS-E-RNF, record not found.

You will also need to edit the template LANprint startup command procedure, SYS$COMMON:[VIA]VIALPPSTARTUP.COM, to define the correspondence between print servers and print queues. The startup command procedure contains guidance on how changes should be made, and it is further documented in Section 3.3.1 and Section 3.3.3.

If you wish to use the DECnet transport and if the remote print server systems have not been defined to NCP, then you should refer to Section 3.3.5 for details on how to setup LANprint for DECnet. If you wish to use TCP/IP and the print servers are outside the local broadcast area, then you should refer to Section 3.3.6 for details. You should not have any difficulty in getting a LANprint connection to work over either of these transports, but Section 3.3.5 and Section 3.3.6 provide more explanation about handling unusual transport environments. You can use both DECnet and TCP/IP transports simultaneously if you wish.

You can also edit the LANprint symbol definition command procedure, [VIA]VIALPPDEF.COM, as described in Section 3.3.4. It is not normally necessary to make any changes to this file as the LANprint utilities have a simple command interface with few configurable options. In order to make the symbols available to users you should invoke [VIA]VIALPPDEF.COM from the system default login command procedure, or from individual users' login command procedures, as described in Section 3.3.4.