This option can be used to enable debug output. All significant operations will be logged on the standard output stream (normally the console). Debug output includes command line analysis, network initialisation, and normal network and print activity.

Debug output is enabled for all sessions, but only active sessions will actually produce a running display.

For example:-

C:\>lanprint lpt1 -d

The amount of output produced can be substantial. It will slow operations down slightly, but can be invaluable in tracking down a problem.

7.5.7 Formfeed between Files

Some print servers automatically add a trailing form feed character between print files. If the server does not do this then this option can be used to force a form feed to be appended to each print file.

For example:-

C:\>lanprint lpt1 lpt2 -f lpt3

The "-F" option is positional. If it is entered before the first shared resource, it applies to all resources. If it is entered after a resource, it applies to the previous resource only. In the example above, it applies to files printed on resource LPT2, but not LPT1 or LPT3.

7.5.8 Network Name

LANprint/PC must signal its presence on the NetBIOS network by registering a network name. The default name is "LANPRINT" padded up to a total of 16 characters by ASCII spaces. The name is normally registered as a group name, which allows several LANprint/PCs to co-exist on the NetBIOS network. This only makes sense if they are all providing access to the same print resources. If this is not the case, or if it is desirable to change the name to something more memorable, use this option to change the name.

For example:-

C:\>lanprint lpt1 lpt2=laser lpt3 -n:PRINT1

The network name can be 1 to 15 characters long. The name provided is converted to UPPER CASE, and space-filled to a length of 16 characters. This is the standard format for SMB Server Names.

When configuring the LANprint Symbiont Printer Database on the VAX, the network name ("PRINT1" here) is entered after the /server= qualifier to the device command(s). The resource name(s) are entered after the /resource= qualifier. Each print resource requires a separate device command.

Other clients that use the LAN Manager/SMB path name syntax should access LANprint/PC resources with paths such as \\PRINT1\LPT1 or \\PRINT1\LASER.

Where a number of LANprint/PC systems are being configured, it may be more practical to use the PC's DOS machine name instead of "LANPRINT" or another name. This name is usually defined during network startup (e.g. by PATHWORKS' STARTNET.BAT). This feature can be enabled by specifying "-N:*" as the network name option. In this case, LANprint/PC will ask DOS for the current machine name setting. If the machine name has been defined, then LANprint/PC will use it, space-filled to 16 characters, as before. If it has not been defined, then LANprint/PC will use the default name instead.

For example:-

C:\>lanprint lpt1 lpt2=laser lpt3 -n:*

Each resource can be protected by a password. When a client connects to the resource, it has to provide a matching password. If the passwords do not match, then the connect request will be rejected.

When a password is required for a resource, it is entered using a "-P" option after the name of the resource. Each password applies only to the preceding resource, so it is not possible to enter a valid password before the name of the first resource.

For example:-

C:\>lanprint lpt1 lpt2=laser -p:secret lpt3

The length of the password is determined by the client's network software. The SMB protocol specification defines 8 characters as the maximum length, but some network packages allow longer passwords. LANprint supports passwords up to 16 characters in length.

The password provided is converted to UPPER CASE, but is not space-filled.

7.5.10 Redirector Name

In normal operation, LANprint/PC registers its presence by a single space-filled network name. This format is correct for a server name. Some network packages require a server to have a redirector or machine name as well. This is a name that is the same as the server name, but is space-filled to fifteen characters length, and has a zero value byte in position 16.

LANprint/PC can register the redirector or machine name as well as its own (server) network name. The "-R" option is used to enable this operation.

For example:-

C:\>lanprint lpt1 lpt2 lpt3 -r

LANprint/PC does not actually use this name, but registering it will help some network browsers to 'see' LANprint/PC.

7.5.11 Sessions

The default number of sessions supported by LANprint/PC is four. This allows a maximum of four clients to have connections to LANprint/PC. As there are only three resources, they cannot all have print jobs going simultaneously, but many PC network packages will normally establish connections well in advance of any print activity. This option allows this facility to be controlled.

The maximum number of sessions allowed is specified by the "-S" option.

For example:-

C:\>lanprint lpt1 lpt2 lpt3 -s:8

The value provided should be in the range 1 to 16. If the value is out of range, it will be ignored and the default value (4) used instead.

LANprint/PC will attempt to start the specified number of sessions immediately. If there are insufficient sessions available on the local NetBIOS, an error will cause LANprint/PC to exit almost as soon as it starts.

If debug output has been enabled (see the Debugging section above), then any activity will be displayed on a session by session basis. Each operation will be logged against a particular session number. If several sessions are active simultaneously, then the output will be intermingled.

7.5.12 Timeout

A timeout is normally applied to all network operations so that LANprint/PC can recover from deadlock problems. The default value of 30 seconds will allow most operations to complete without problems, but a client that will not allow LANprint/PC to send a command response within this time will be disconnected. In NetBIOS terms, the session is aborted.

A NetBIOS timeout is defined using the "-T" option.

For example:-

C:\>lanprint lpt1 lpt2 lpt3 -t:0

This example uses a value of zero to disable timeouts. The value is specified in seconds. It should be in the range 0 to 127 inclusive. Out of range values will be ignored, and the default (30) used instead.

7.5.13 Unique Names

The default option is for LANprint/PC to identify itself on the network by registering a group network name. Such a name need not be unique on the network, though it has to be unique on the LANprint/PC system. This option will prevent an identical name being registered on the NetBIOS network, as unique names are just that.

The add unique names option is enabled by option "-U".

For example:-

C:\>lanprint lpt1 lpt2 lpt3 -n:PRINT1 -u

A shorter form of the above command is available. The network name can be specified using -U:name. This will also be registered as a unique name.

7.5.14 Verbose Mode

In normal mode, LANprint/PC will only output error messages. It has a verbose mode in which status messages will be output as well. This is not to be confused with debug output, which is much more extensive.

If the "-V" verbose option is specified, LANprint/PC will produce the following output:-

C:\>lanprint lpt1 lpt2=laser -p:secret lpt3=draft -a:2 -v LANprint for PATHWORKS - Version 1.1 - 10-Sep-1993. Copyright (c) 1993 BTVC & Vector Networks Limited. All Rights Reserved. LANprint/PC Print Gateway Program LANPRINT. LANprint/PC: Server Resource Table: No Local Device Resource Alias Network Path Password -- --------------- --------------- ----------------------------------- ----- 1 LPT1 LPT1 \\LANPRINT\LPT1 <No> 2 LPT2 LASER \\LANPRINT\LASER <Yes> 3 LPT3 DRAFT \\LANPRINT\DRAFT <No> -- --------------- --------------- ----------------------------------- ----- Server initialisation complete. Starting to Serve the Network. To shut the Server down safely, type <Control-C> once. To force the Server to exit, type <Control-C> twice.

Verbose mode will also show when clients connect and disconnect.

This appendix contains background notes on installing LANprint, and includes example installation sequences for both VMS and PC components of the package. It also includes instructions for removing LANprint from the VMS host and from the PC.

A.1 Introduction to VMSINSTAL

This section is included for those VMS users who do not have access to the full VMS documentation set; it can be ignored by users experienced with the use of VMSINSTAL.

VMSINSTAL is a command procedure supplied as standard with all VMS and MicroVMS systems and many software products are installed with it. It is the recommended way of installing optional products from any of several types of media. It supports magnetic tapes (0.5", TK50, etc), RX50 and RX23 floppy disks, console media (e.g. RX01's, TU58's), CD-ROMs, and various hard disks such as RZnn's, RD5n's, RL02's, etc.

In order to invoke VMSINSTAL you must login to the SYSTEM account (i.e. as the system manager, with default directory SYS$MANAGER:) and you should do the following preparation:-

• Ideally, ensure that there are no users logged on and that all batch jobs have completed, but this is not usually necessary. If this is an upgrade installation, then ensure that no users are actually using LANprint at the time.
• Ideally, prevent users from logging on. The following command could be used:

  $ set logins/interactive=0

• There is no need to shut down the DECnet or TCP/IP network, indeed, for LANprint, we recommend that you don't shutdown a running network.
• You should shutdown any previous version of this package, however. See Section 3.11 for details on shutting down LANprint.
• Ensure that your system disk is adequately backed-up.
• Physically mount the distribution media containing the software product.

If this has been completed you should invoke VMSINSTAL with a command of the following format:-

$ @sys$update:vmsinstal product source: options option_list

The product name is of the format "VIALPPvvu" where "vvu" represents the version number/update. The full product name for the LANprint Version 1.2 (i.e. version 1, update 2) is VIALPP012.

In the normal case where there is only one version of a package on a tape, then it is not necessary for you to specify the version number at all, and "VIALPP" is perfectly adequate. If there are several product kits on the tape, and you want to install them all, then you can use "*" as the product name: VMSINSTAL will then install one product after another and this will usually be faster than explicitly installing them one at a time.

The source: parameter represents the source device, i.e. the device containing the distribution volume, e.g. MUA0:.

OPTIONS must be included in full if any installation options are to be requested - this is recommended.

The option_list parameter specifies individual letters for each possible installation option. It is recommended that the single letter "N" is used for this parameter to cause any supplied release notes to be displayed or printed. For reference, the options list can contain the following letters but they must be adjacent with no intervening spaces:-

AWD= disk:	Alternate Working Device option - Lets you specify a different disk to be used for temporary files during the installation process. VMSINSTAL usually uses a subdirectory of the SYS$UPDATE: directory on the system disk for temporary files but if there is not enough space on that disk you can specify another mounted disk using this option, e.g. AWD=DKA400:. LANprint gives you an installation option to direct the main installation to a non-system disk, and using that in conjunction with the AWD option allows you to avoid all but a minimal impact on the system disk.
L	File Log option - Log all file activity to the terminal.
N	Release Notes option - Print or display the release notes if provided in the package - the release notes file would be called productvvu.RELEASE_NOTES, e.g. VIALPP012.RELEASE_NOTES.
R	Alternate Root option - Install the package in an alternate system root to the running system.

For further information on VMSINSTAL, please refer to your VMS Documentation.

A.2 Sample VMS Installation Log

Example A-1 shows a log of a VMS installation of LANprint.

Example A-1 Sample VMS Installation

$ @sys$update:vmsinstal vialpp mua0: options n VAX/VMS Software Product Installation Procedure V5.5-2 It is 31-JUL-1996 at 15:40. Enter a question mark (?) at any time for help. * Are you satisfied with the backup of your system disk [YES]? <Enter> The following products will be processed: VIALPP V1.2 Beginning installation of VIALPP V1.2 at 15:40 %VMSINSTAL-I-RESTORE, Restoring product save set A ... Release notes included with this kit are always copied to SYS$HELP. Additional Release Notes Options: 1. Display release notes 2. Print release notes 3. Both 1 and 2 4. None of the above * Select option [2]: <Enter> * Queue name [SYS$PRINT]: <Enter> Job VIALPP012 (queue SYS$PRINT, entry 5) started on SYS$PRINT * Do you want to continue the installation [NO]? y %VMSINSTAL-I-RELMOVED, Product's release notes have been moved to SYS$HELP. LANprint Installation This product is normally installed in the SYS$COMMON:[VIA] area on the system disk. However, it is possible to install it on a different disk if desired. * Do you want to install on the system disk [Y]? <Enter> This package requires a minimum of 2500 blocks of VMS disk space. This package includes online documentation files that can be read with the DECwindows Bookreader application. These files are no use if you don't have any DECwindows systems. You will increase the disk space requirement by approximately 1000 blocks if you install them. * Do you want Bookreader online documentation files installed [Y]? <Enter> This package includes PostScript files for the User Manual which can be printed if you have access to a PostScript printer. There are two versions of the manual available, paged for A4 paper, or for US LTR (8.5" x 11") paper. You can select any combination of these files. Each of these files is approximately 1200 disk blocks in size, so if you do not have any PostScript printers, or do not wish to print extra copies of the documentation, you can avoid the need for up to 2400 extra blocks by not having them installed. * Do you want the PostScript file installed for A4 paper [Y]? <Enter> * Do you want the PostScript file installed for US LTR paper [Y]? n You can also have the PC software installed onto the VMS disk rather than installing it from PC floppy disk. This allows you to copy the files directly into a PATHWORKS file or disk service on the VMS host without using a PC to do it. The software is identical to that on the v1.2 LANprint for PATHWORKS floppies. You will need approximately 200 extra blocks of disk space if you install the PC software on the host. * Do you want the LANprint PC software installed on the VMS disk [Y]? <Enter> Checking for 4900 free blocks... Sufficient space available. Installation continuing This product includes support for DECnet and/or TCP/IP (given a compatible VMS TCP/IP stack). You can choose whether you want DECnet to be the default transport for LANprint, which is the default, or whether you want TCP/IP to be the default. * Do you want DECnet as the default transport [Y]? n The default transport will be TCP/IP * Is this correct [Y]? <Enter> If this is a re-installation or an update we can purge old versions of new files if you wish. Files that are typically edited by System Managers will not be purged. Purging is normally preferred. * Do you want to purge files replaced by this installation [YES]? <Enter> There are no more questions for this installation. Installation continuing. %VMSINSTAL-I-RESTORE, Restoring product save set B ... %VMSINSTAL-I-RESTORE, Restoring product save set C ... %VMSINSTAL-I-RESTORE, Restoring product save set E ... %VMSINSTAL-I-RESTORE, Restoring product save set F ... Creating new directory structure... %VMSINSTAL-I-SYSDIR, This product creates system directory [VIA.EXE]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VIA.DECNET]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VIA.TCP]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VIA.DOC]. %VMSINSTAL-I-SYSDIR, This product creates system directory [VIA.DOS.LANPRINT]. Linking the NPDRIVER which is used for transparent print spooling. Do not be concerned by a "no user transfer address" warning. %LINK-W-USRTFR, image VLC$DKA300:[SYS0.SYSUPD.VIALPP012]NPDRIVER.EXE;1 has no us er transfer address NPDRIVER Linked successfully. Installation continuing with the LANprint Database Utilities and the LPPPRINT diagnostic program... The LANprint Symbiont and Utilities have been copied successfully. Installation continuing with optional files and key upgrade utilities. Optional files and key upgrade utilities copied successfully. Providing template Startup and Shutdown files... The installation of the LANprint package has completed successfully. Please check any Installation Documentation and Release Notes for any further work required: If you are going to use the package over the DECnet transport, you will have to define the PC DECnet node names to the VMS DECnet database with NCP (or with the supplied SYS$COMMON:[VIA.DECNET]NCPDEF.COM) if this has not been done already. You will also have to define PC and resource names in LPPDATABASE.DAT, build the database, and then start any queues. Thankyou and Goodnight! %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories... Installation of VIALPP V1.2 completed at 15:48 VMSINSTAL procedure done at 15:48 $ ! Start the queues that are defined in the template database $ $ @sys$common:[via]vialppstartup %VIALPPSTARTUP-I-DEFTRANSPORT Configuring DECnet as the default transport... %VIALPPSTARTUP-I-INSIMAGES Installing NetBIOS transport images as known files... %VIALPPSTARTUP-I-STARTQS Initializing and starting LANprint queues... %VIALPPSTARTUP-I-SPOOLSETUP Setting up transparent print spooling... %VIALPPSTARTUP-I-DONE LANprint queue startup completed. $ $ ! Define the LANprint command symbols $ $ @sys$common:[via]vialppdef $ $ ! Check the supplied database entry for VAX_PRINT, equivalent to \\VAX\PRINT $ $ lppquery vax_print LANprint - Version 1.2 - 31-Jul-1996 - Kit #07D4 Copyright (c) 1996 BTVC, Vector Networks Limited. All Rights Reserved LANprint Printer Database Query Program LPPQUERY Evaluation Package. Expires on 30-AUG-1996 Database File Query : LPPDIR:LPPDATABASE.BIN Network Device Name : <VAX_PRINT > Network Server Name : <VAX > LAN Adapter Name : < > Remote Resource : <PRINT > Remote Password : < > Printer Characteristics : 9. NetBIOS Session Timeouts : Rx 0, Tx 0 (0.5 seconds). Error Retry Timer : 1 minutes. Hold-On Timer : 1 minutes. Flow Control Timer : 0 minutes. Maximum Retry Count : 0. Operator ID : 2. Session Debug Flags : 0. Print Trailing FormFeed : <No> $ ! Example command to print a single file using the database to find VAX_PRINT $ ! This command requires a \\VAX\PRINT server & resource $ $ lppprint login.com vax_print $ $ ! Now edit the printer database to define a server & resource $ ! that do exist locally, e.g. \\NT\PRINT as queue NT_PRINT $ $ edit lppdir:lppdatabase.dat $ $ ! and rebuild the database $ $ lppdatabase $ $ ! Shutdown the example queues $ $ @sys$common:[via]vialppshutdown $ $ ! Edit the startup and shutdown procedures to reflect the queue(s) $ ! that you have defined $ $ edit viaroot:[via]vialppstartup.com $ edit viaroot:[via]vialppshutdown.com $ $ ! restart LANprint with the new queues $ $ @viaroot:[via]vialppstartup $ $ ! and now print through the NT_PRINT queue $ $ print/queue=nt_print adduser.com Job ADDUSER (queue NT_PRINT entry 6) started on NT_PRINT $