INTRODUCTION
	------------


		This is an update to the PRINT verb submitted in the spring
	'84 SIG tape. Some bugs were found and have been fixed. This verb
	makes remote printing transparent to a user.











		***************************************************

			INSTALLATION GUIDE FOR THE PRINT VERB

		***************************************************



	1.	DESCRIPTION OF PROGRAMS


		a. DECPRINT.COM  - 	This is a command procedure used
		on a local print.

		b. DIABLO.COM    -	This command procedure prints the
		output file(s) on a local, 80 column, letter quality 
		printer. You may not use this but it must be installed.
		It creates its own 80 column header page as a replacement
		for DEC's header page.

		c. FILTABLE.FOR  -	A fortran program to add or delete
		the computer's alternate choices if it determines a node
		is down.

		d. PRINTABLE.DAT -	The file created by the program
		FILTABLE.FOR. This file is an indexed file, with one key
		a character string 15 bytes in length.

		e. REMDIA.COM	 -	This command procedure is used 
		for a remote print on a high quality printer as described
		above for DIABLO.COM.

		f. PRINT.CLD    -	The command language definition 
		file describing the new print verb characteristics. Note
		that this description is identical to DEC's except for 
		the image activated by the verb. This cld must be executed
		for each user on login with the "set command" command or
		better yet at system startup inserting it in the dcltable.

		g. REMPRT.COM    -	This command procedure is used
		for normal printing to a remote node.

		h. REMPRT.FOR    -	This is a fortran program which
		is activated by the print verb. The program must be 
		edited to modify the open statement for PRINTABLE.DAT and
		the LIB$DO_COMMAND 's to point to the correct device and
		directory. No other programs are needed to compile and 
		link the program.



	2.	WHERE TO PUT THEM


			I would suggest that the programs be put in their
		own directory . I have kept the working version on the 
		system disk under our library directory : 
		sys$sysroot:[utclib.network] .


		The directory should contain the following:

		decprint.com
		diablo.com
		printable.dat
		remdia.com
		remprt.cld
		remprt.exe
		remprt.for     (and executable)
		remprt.com
		filtable.for   (and executable)

		The default directory for DECnet (ours is [NETUSR]) should
		contain:

		remprt.com
		remdia.com

		This is repeated all nodes that are to participate
		in the remote print.




	3.	COORDINATING THE LOGICAL NAMES BETWEEN NODES


	Printer's logical names reflect location of the printer within the
	building and not physical devices. This makes any routing by the 
	program transparent to the user. Printer logical names are three 
	characters long with the following syntax :

		P1A
	________|||
	| _______||
	| |	  |
	| |	  v
	| |	  Position of printer : Location of printer on a specific
	| |	  floor. (A-Z). Could be thought of a the face of a clock
	| |	  with A being 12:00 --> L being 6:00 --> Z being 11:59 etc.
	| |
	| v
	| Floor Number : This value specifies which floor the printer is 
	| 		 located on (0-9).
	|
	|
	v
	Printer type : Type of printer to be used. Currently, the software
		       supports two types :

			P --> Normal printers
			D --> Diablo printers (letter quality)



		At system startup logical names following the syntax
	just mentioned should be defined. Logical printer names 
	pointing to printers on that system will end with a single 
	colon ":" , signifying a physical device. Logical printer names 
	pointing to remote cpu printers will be defined with the remote
	cpu DECnet node name, always ending with "::". This is how the
	image determines if a remote print is needed. SYS$PRINT and
	SYS$DIABLO are also allowed as correct queue names. Here are
	some examples.


	DEFINE/SYSTEM P1A	TXD7:

	This a local cpu print , on a regular DEC printer, 1st floor,
	location A.

	DEFINE/SYTEM  D6D	IRIS::

	This is a remote cpu print, on node IRIS:: , on a DIABLO letter
	quality printer, 6th floor, location D.



	On the cpu node IRIS however, the definations would be reversed
	showing P1A as cpu node EAGLE::

	DEFINE/SYSTEM P1A	EAGLE::

	and queue D6D as a local print to a physical device.

	DEFINE/SYSTEM D6D	TTB8:




		**********************************************


	If you have any problems feel free to contact me at


		UNITED TECHNOLOGY
		BUILDING SYSTEMS
		433 Las Colinas Boulevard
		Irving, Texas  75039
		(214) 830 - 7501

	Attn: DUANE RIECH