Dynamic Host Configuration Protocol is used in some TCP/IP environments to assign Internet IP addresses dynamically, as each system boots. LANprint's TCP/IP support will operate correctly in a DHCP environment providing all target systems are in the same broadcast area (wide area connections to DHCP-configured nodes will not work) and providing there is no entry for those nodes in the NBHOSTS file. If all nodes are using DHCP then you can delete NBHOSTS.DAT if it has been created by previous activity.

3.3.7 Changing the Default Network Transport

LANprint allows to set the default network transport during the installation. This can be either DECnet or TCP/IP. You can change this after the installation if you wish, by editing SYS$MANAGER:VIALPPSTARTUP.COM such that the DEFAULT_TRANSPORT symbol is defined to be either "DECnet" or "TCP/IP". You can then shutdown LANprint and restart it on the new transport. If you had previously specified the non-default transport explicitly, e.g. by using "/lan_name=tcp" in LPPDATABASE.DAT, then these will continue to work after the default transport has switched to TCP/IP, for instance.

3.3.8 User-Modifiable Files

The host installation includes files which are user-modifiable. Four of these are expected to be edited by system managers, and are thus not purged by the installation procedure. These are the LANprint remote printer database binary file and its template, the LANprint startup file, described in Section 3.3.3, and the LANprint shutdown file, described in Section 3.11. Table 3-1 lists all user-modifiable files.

Table 3-1 User-Modifiable Files

Filename	Description
LPPDATABASE.DAT	LANprint Printer Database Template File
LPPDATABASE.BIN	LANprint Printer Database Binary File
VIALPPSTARTUP.COM	LANprint Startup Command Procedure
VIALPPSHUTDOWN.COM	LANprint Shutdown Command Procedure
NBHOSTS.DAT 1	TCP/IP NetBIOS Name Resolution Support File

LANprint defines system-wide logical names in VIALPPSTARTUP.COM, as listed in Table 3-2, with their normal equivalences.

Table 3-2 Logical Names Defined by LANprint

Logical Name	Normal Equivalence
VIAROOT	SYS$COMMON:
LPPDIR	VIAROOT:[VIA.DECNET]
LP$DEFAULT_TRANSPORT	DECnet
LP$VERSION	v1.2
NETBIOS_NAMESCOPE 1 2	not normally defined
NETBIOS_TCPDEVICE 1 3	not normally defined
VNLDNBSHR	VIAROOT:[VIA.DECNET]VNLDNBSHR
VNLNBSHR	VIAROOT:[VIA.DECNET]VNLDNBSHR
VNLTNBSHR	VIAROOT:[VIA.TCP]VNLTNBSHR

VNLDNBSHR and VNLTNBSHR are used to locate the NetBIOS shareable images and must be defined in executive mode in the system logical name table, otherwise no applications will be able to find the shareable images. The VNLNBSHR logical is used to identify the default transport - either VNLDNBSHR.EXE for DECnet support, or VNLTNBSHR.EXE for TCP/IP.

If debugging is enabled for any print queues, the logical name LPP_DEBUG_DEVICE should also be defined in the SYSTEM logical name table.

3.3.10 Configuring DECwindows Bookreader

This package includes files which allow a copy of this manual to be accessed online with the DECwindows Bookreader application. If the Bookreader documentation files were requested during the installation dialogue they will have been copied to the [VIA.DOC] directory on the installation disk. It is necessary to get Bookreader to search this area for the documents to appear in Bookreader's library list, or, the files can be integrated into the SYS$SYSROOT:[DECW$BOOK] area. Telling Bookreader to search the [VIA.DOC] directory is less intrusive than making changes to the LIBRARY.DECW$BOOKSHELF file in SYS$SYSROOT:[DECW$BOOK], so we recommend the following procedure:-

• Login as user SYSTEM, default directory SYS$MANAGER:
• If you have not already done this,

  $ copy decw$private_apps_setup.template *.com

• Edit DECW$PRIVATE_APPS_SETUP.COM and insert the following lines

  $! $! Re-define the DECW$BOOK DCL symbol to cause Bookreader to search $! the [VIA.DOC] directory, in addition to searching the default $! area(s). (The DECW$BOOK symbol is defined by DECW$STARTAPPS.COM as $! SYS$SYSROOT:[DECW$BOOK], and can be redefined to search a CDROM $! and any other areas, separated by commas. DECW$STARTAPPS.COM uses $! this symbol to define the DECW$BOOK logical name that is used by $! Bookreader itself). $ $ decw$book == "sys$sysroot:[decw$book],sys$common:[via.doc]" $

  Note This example assumes that LANprint has been installed on the system disk. Otherwise, substitute the installation area for SYS$COMMON above. The order in which areas are listed in the definitions will affect the order in which libraries are shown in Bookreader.

• Reboot the system or enter a command such as the following to cause the new definition to take effect:

  $ define/exec/table=decw$logical_names decw$book - _$ sys$sysroot:[decw$book],sys$common:[via.doc]

You may wish to cause Bookreader to open all library files found in the DECW$BOOK search list, rather than the default of just opening the first one found. This is done by editing the Bookreader Resource File, DECW$SYSTEM_DEFAULTS:DECW$BOOKREADER.DAT, and the relevant line can be changed to say:-

BookreaderLibrary.shelf_to_open_on_startup: all

You may also wish to cause Bookreader to highlight hotspots (e.g. tables, figures, etc) by changing the relevant line to say:-

BookreaderTopic.show_hot_spots: true

Refer to Bookreader's online help pulldown for more details on customising Bookreader (e.g. topic Modifying the Bookreader Display), and to the DECwindows Motif User Guide for further details on resource files.

3.4 Checking that the Symbiont is Running

If the package startup operation is successful, the DCL command SHOW QUEUE/FULL queue_name should produce the following display:-

Server queue VLC_LASER, idle, on VLC::VLC_LASER, mounted form DEFAULT /BASE_PRIORITY=4 /DEFAULT=(FORM=DEFAULT) Lowercase /OWNER=[SYSTEM] /PROCESSOR=LPPSYMBIONT /PROTECTION=(S:E,O:D,G:R,W:W)

and if you have set up spooled devices, a command such as SHOW DEVICE/FULL NPA0:, should produce a display such as:-

Printer NPA0:, device type unknown, is online, record-oriented device, carriage control, device is spooled through an intermediate device. Error count 0 Operations completed 0 Owner process "" Owner UIC [0,0] Owner process ID 00000000 Dev Prot S:RWLP,O:RWLP,G:RWLP,W:RWLP Reference count 0 Default buffer size 1024 Page width 1024 Page Length 0 No Carriage_return No Formfeed Uppercase No Passall No Wrap No Printall No Fallback No Tab No Truncate Intermediate device: DKA300: Associated queue: VLC_LASER

If this is the case, the package should be ready for print requests.

3.5 Console Messages

The Symbiont will display a sign-on message when it is started that includes a Copyright notice, the software version, and the expiry date of any evaluation period. If a queue is started and the Symbiont fails to find the network transport nominated for that queue, the Symbiont will display a diagnostic message to that effect and the queue startup will fail. If this happens, you should check that the network software is running and that it is correctly specified in the database file. The default network transport for LANprint is DECnet. Please refer to Section 2.4 for details of network transports, and minimum versions, supported.

The Symbiont will emit status messages when it is unable to send a print job to a remote system. This can result from network faults, remote system faults, or remote system overloading. Such messages are described in detail in Appendix B and Appendix C. The Symbiont attempts to recover from such transient faults by retrying the network operation. Each failed retry attempt produces a console message.

3.6 Installation on DOS

LANprint includes LANprint/PC software which can be installed if it is required to gain access to certain remote printers. It is not normally necessary on any network that supports the SMB/LAN Manager print protocols, as LANprint can usually connect directly to these print servers. However, it can be useful to allow printing to non-SMB print servers, such as Novell NetWare, Banyan VINES, or indeed potentially any network that provides printer redirection (or 'capture') and that will allow a LANprint-compatible NetBIOS to be loaded in the gateway PC.

The LANprint/PC software is normally installed on the gateway PCs, but it can equally be installed on a file server that can be accessed by those PCs. It is generally easier to install the software on the same drive as the majority of PATHWORKS files. The DOS software can be installed on a PATHWORKS file or disk service. It does not write back to the disk, so read-only access to the files is sufficient.

The DOS software supports MS-DOS versions 3.3, 4.0, 5.0, and 6.0. Versions of MS-DOS prior to 3.3 are not recommended.

The VMS software installation offers the option of installing the DOS software onto the VMS disk. The files can then be copied into a PATHWORKS file or disk service.

3.6.1 Installing the PC Software

The PC components of LANprint are usually supplied on PC floppy disk. They are installed using DOS batch files. The command syntax for the first step is:-

drive:install [source: [destination:]]

Note that the batch file location drive: should always be specified. The source: and destination: arguments specify the DOS disk drives that are to be used. The default source: device is A: and the default destination: device is C:. Note that the source: must be specified if the destination: argument is used.

For example, with the floppy disk containing the LANprint software in drive A:, run the install batch file as follows:

C:\>a:install

To install from floppy drive B: to destination drive H:, type:

C:\>b:install b: h:

The installation directory is destination:\LANPRINT. If this directory does not exist, it will be created automatically.

If the software has already been installed into the \LANPRINT subdirectory on a file server, and you wish to create a local installation on a PC, you can specify the directory path with the network drive specification (source:) on the INSTALL command line:

C:\>h:\lanprint\install h:\lanprint

Help information is available if the -H option is specified as the first argument:

C:\>a:install -h

The installation procedure creates \LANPRINT\STARTPRT.BAT, a sample batch file which can be used to start the LANprint/PC Gateway. You will need to edit STARTPRT.BAT to make any print redirections and to set any resource aliases that you wish to use. This is described in Section 3.6.2, with further detail on LANprint/PC command syntax in Chapter 7.

STARTPRT can be invoked with the following command:-

C:\>\lanprint\startprt

or, if invoked from another batch file, such as AUTOEXEC.BAT:-

CALL \LANPRINT\STARTPRT

The command syntax and options for LANprint/PC are described in Chapter 7. Example A-2 shows a sample DOS installation dialogue.

3.6.2 Configuring LANprint/PC

The sample STARTPRT.BAT file can be used to start LANprint/PC automatically. This file should be edited to alter the printer redirections to suit the local requirements. Redirections should be set up at the beginning, and they should be deleted after LANPRINT.EXE has exited. It is also wise to check the ERRORLEVEL on each USE, so that any errors can be handled correctly.

Note that, if LANPRINT.EXE starts up successfully, it will not stop until a <Control-C> is typed on the PC's keyboard.

3.6.3 Configuring Windows for LANprint/PC

The LANprint/PC Gateway is a foreground DOS program. It can be run either from the DOS prompt, or under MS-Windows. When it is run from the DOS prompt, the PC can't run any other programs until LANprint/PC is stopped. This normally dedicates the PC to the print gateway operation. Microsoft Windows offers the opportunity to run it in a 'DOS Box' ('MS-DOS Prompt' window) such that other Windows applications can be run on the same machine.

To simplify Windows setup, three additional sample files are provided. These are LANPRINT.GRP, a Windows Program Group, LANPRINT.ICO, a Windows icon, and LANPRINT.PIF, which is a Windows Program Information File. The Program Group file is used to install LANprint/PC on Windows. This can be done as follows:-

• Start Windows, pull down the Program Manager File menu, and select the New option on the menu. This will produce a New Program Object dialog box.
• Check that the Program Group radio button is pressed, and click on OK. The Program Group Properties box will appear.
• Move the cursor to the Description box, and type LANprint/PC. Tab or use the mouse to get to the Group File box, and type C:\LANPRINT\LANPRINT.GRP. If you installed LANprint/PC in a different location, use the appropriate path. Press OK, and Program Manager will create a new Program Group containing LANprint/PC.
• If you want to move LANprint/PC to another Program Group (e.g. the Startup Group, for automatic installation), make sure that both the LANprint/PC Group and the other Group are restored (i.e. not minimised). Place the mouse cursor on the LANprint/PC Icon, press the left mouse button and hold it down while you drag the Icon to the other Program Group window. Then, release the mouse button, and the Icon will be dropped into the new Group. Once you have done this, the empty LANprint/PC Group can be deleted.

If you have installed LANprint/PC in the default location (i.e. C:\LANPRINT), then your installation is complete. If you installed LANprint/PC in a different location, some further changes are required. You will already have entered the new path in the Group File box above. It is also necessary to change the paths specified for the LANprint/PC Program Item, Icon, and LANPRINT.PIF file.

• Select the LANprint/PC Icon by single-clicking on it. Then, pull down the Program Manager File menu, and select the Properties option. This allows you to change the command line and working directory for LANPRINT.PIF. Press the Change Icon button and browse to the LANprint/PC installation directory, and double-click on LANPRINT.ICO to set the Icon. Click on the OK buttons when you have made the necessary changes. This will get you back to Windows.
• Windows' PIF Editor must be used to change the paths in the LANPRINT.PIF file. This is done by activating the PIF Editor, which is usually kept in the Windows Accessories Group. Pull down the File menu, and select the Open option. Use the browser to get to the LANprint/PC installation directory, and double-click on LANPRINT.PIF. Change the paths in the Program Filename and Start-Up Directory boxes to suit the new location. When you are happy with the changes, pull down the File menu again, and select Save. Exit from the PIF Editor.

LANprint/PC can then be started simply by double-clicking on the icon. This actually runs STARTPRT.BAT in a 'DOS Box'. It is set to run in a window, rather than full-screen. Once it has started, it is safe to minimise the window. LANprint/PC will continue in the background.

Stop LANprint/PC by restoring the window, and typing <Control-C>. It will exit immediately if it is idle. If it is in use, it will print a warning message, but will not exit until all users disconnect, or another <Control-C> is typed.

LANPRINT.PIF specifies the program priorities which are used for background and foreground execution. These are set to 10 and 100 respectively. The PIF file also includes the memory required to run STARTPRT.BAT. This should be at least 64 KBytes, but may need to be increased if any other commands in STARTPRT.BAT fail to run properly. Values in LANPRINT.PIF can be adjusted using the Windows PIF Editor. Any changes will take effect the next time LANprint/PC is started.

If you regularly have several LANprint clients connected to the same print server, or if you have several DECnet applications active on the print server node, it is conceivable that you might reach the limit on the number of simultaneous connections, or sessions, that the server's DECnet is configured to allow. This is quite unlikely as the LANprint Symbiont will usually only maintain a connection while actually spooling a print job, and this will usually complete in a short period. However, it can occur when trying to make a LANprint connection, or when using any other DECnet application, and is signalled by a "Call Rejected - No Listen Outstanding" error from LANprint on the VMS host. This is easy to correct with an NCP command that changes the number of connections, or links, that the DECnet stack will allow.

Execute the following command to see the current setting of the Maximum Links parameter:

C:\> ncp show executor characteristics

Read off the Maximum Links setting, increase it, perhaps by 10, and then use the result in the following command:

C:\> ncp define executor maximum links n

Where n is the new number of links you wish to configure.

Then, reboot the server node, and try again. It is not possible to increase the number of DECnet links on PCs without rebooting them. Please refer to the DECnet Network Management Guide in the PATHWORKS package for further detail on DECnet configuration.

If you are running LANprint over a LANlink transport, there may be a limit on the number of simultaneous NetBIOS sessions that the PC network software will allow. The LANprint Symbiont will retry Call requests that fail with a NetBIOS Session Table Full error, so it can be used on a LANlink with very few free sessions. If you are using LANprint with a LANbridge package, it is very likely that you will have to request extra NetBIOS sessions for the bridging machine itself. Please refer to the documentation with your LANlink or LANbridge package for further details.