			     README.TXT


This directory contains version 1.0 of NOVQSERV and the corresponding 
QSCFG utility. 

This utility is a Novell job server with built in print server
and queue  redirection facilities.  This utility should function
properly with versions 2.x,  3.x, and 4.x of Netware.

This software is shareware, and may be freely redistributed as long as
the redistribution includes the entirety of this archive with no
modifications.

_____________________________________________________________________

Three documentation files are included with this package:

	README.TXT
	INSTALL.TXT
	UGUIDE.TXT
	
Three associated postscript versions of these files are also provided.
If you have a postscript printer, use the postscript versions.

To print the postscript documentation, send each of the following files
to a postscript printer:

	README.PS
	INSTALL.PS
	UGUIDE.PS
	GRAPHIC.PS (a graphical representation of NOVQSERV)

	(Do not send DMPTEMP.PS - it is not documentation)

--------------------------------------------------------------------------

WHY NOVQSERV MAY PROVE USEFUL:  


	There are a couple of different functionalities provided by
NOVQSERV which may prove useful at your Novell site.  Firstly,
NOVQSERV provides the ability to service multiple Netware print
queues and reroute jobs from those queues to other Netware print
queues (on the same or different Netware file server).  Jobs may
also be rerouted to LPD serviced queues (via an LPR service -
this service and associated TCP/IP stack must be purchased
separately and installed on the NOVQSERV machine by you).  This
print server 'funnel' functionality allows hardware print server
devices to be attached to (account located on) a 'central' file
server.  Allowing print server devices to be located on a
'centralized' printing file server may provide several benefits
at a given site.  Maintenance and printing configuration changes
can be simplified, and the annoyance of many print server
devices each taking up a Netware connection slot can be
circumvented.  Usually, every print server device requires its
own Netware connection slot.  Thus, if you have twenty different
print  server devices strewn around your building, each one
takes up a connection on every Netware file server which it is
configured to service (accept print jobs from).  These 
unnecessarily used connections can preclude members of your user
community from gaining the Netware connections that they require
to do work.

    

	Under Netware 3.x, the maximum connection count available
(unless  you're at one of the lucky sites which obtained a 1000
user version before they were discontinued) is 250 users. 
Having many print server devices using up a fraction of these
available slots can cause a LAN manager (in charge of a user
saturated file server) much grief.  By funneling  print jobs
from the queues of multiple Netware servers to a 'central'
printing file server, the redundant connections required by most
print  server devices can be prohibited.  Simply configure the
print server devices to attach only to the 'central' file server
and service its queues (and use its connections).  Then set up a
NOVQSERV machine to funnel the print jobs from up to 7 Netware
servers to the 'central' server where they can then be serviced
by the print server devices (and actually printed).  Now, the
connections on 7 servers, otherwise necessary so that the print
server devices could service those 7 file servers have been
reduced to the connections necessary only at the 'central' file
server.  The NOVQSERV user takes up one connection per serviced
file server, so if you have 20 print server devices available to
the user community, then you've now returned 19 Netware
connections (per serviced file server) for user community usage. 

	

*NOTE: Up to 8 origination (source) file servers can be serviced
with  the registered version of NOVQSERV, however, if any serviced 
queues are set up for NPRINT type jobs and the destination file server 
for any of those queues is a server other than the 7 specified for
servicing (appearing in column 1 of NOVQSERV.TAB), then one file server 
connection slot (out of the 8 maximum) must be reserved for the
destination NPRINT file server.  If 8 file servers are configured to be 
serviced (in the NOVQSERV.TAB file column 1) and a job is grabbed from a 
serviced queue (column 2 of NOVQSERV.TAB) set for job type NPRINT, then 
when nprint.exe is initiated by the QSNPRINT.BAT command file, you
will see a message to the effect that there are no connection
slots found available.  Nprint.exe requires an available connection slot 
so that it can connect to the file server where the destination queue resides.    
Nprint.exe should automatically relinquish the temporary connection that it 
uses to send a job to a destination queue, so only one connection slot need 
be kept free, regardless of the number of NPRINT job type configured queues 
set in the NOVQSERV.TAB file.  Essentially what this means is that if you 
wish to use any queues configured for job type NPRINT (or any custom job type
which will require a new file server connection - on a not yet connected file 
server), you get a maximum of 7 origination file servers where source queues
(to be serviced) can reside.  If you do not use any queues configured for job 
type NPRINT (or any custom job type which will require a connection to a not 
yet connected file server), you get a maximum of 8 origination file servers 
where source queues can reside.           
			
	Along with freeing up connection slots, NOVQSERV provides postscript   
filtering (which can help keep finicky printers from getting confused and/or 
hung up by bad print job formats) and statistical tracking of jobs by queue. 
 
	Along with the inherent print redirection capability of the NOVQSERVer  
comes the ability to create a custom job server capable of automating up to 7 
distinct sequences of tasks.  Each sequence of tasks is defined  by way of a 
command (batch) file which reflects the operations required for each 
particular sequence of tasks.  Users capture jobs to a given  Netware queue
where they (jobs) are then redirected to the appropriate command (batch) file 
by the NOVQSERVer.  Virtually any sequence of tasks which  can be represented 
via a DOS batch file can be automated using NOVQSERV.
				      

REGISTRATION:
-------------
				      
	The demo version of NOVQSERV (distributed in this archive) can service  
up to fifteen queues defined on up to two file servers. The registered version 
of NOVQSERV can service up to 300 queues defined on up to eight  file servers.  
You can obtain a registered version of NOVQSERV by printing out the 
REGISTER.PS (or REGISTER.TXT) file, filling in the appropriate information
and returning the form along with payment to the listed address.
	

								
	Registration entitles you to free bug-fix upgrades (when available) 
and cheap (low cost) enhancement upgrades ...


	Anticipated future enhancements include customizable string filtering 
(similar to the postscript filtering included now) and additional parameters 
passable for custom job types.

			      
	     Mail regarding NOVQSERV can be sent to:            
			
			buzz@world.std.com


	All comments, questions, and suggestions are welcomed and will
be reviewed.  A response to all is not guaranteed, however, all correspondence 
will be read.  Only those who have registered NOVQSERV will receive replies...


FILES:
------

	The files that should be in this directory after unzipping the
archive follow (with explanations):


	- README.TXT

	this file in ascii format

	
	- README.PS

	this file in postscript format (send this to a postscript printer)

	
	- INSTALL.TXT

	the installation instructions in ascii format


	- INSTALL.PS

	the installation instructions in postscript format (send this to a 
	postscript printer)

	
	- UGUIDE.TXT

	the user guide in ascii format

	
	- UGUIDE.PS

	the user guide in postscript format (send this to a postscript 
	printer)

	
	- GRAPHIC.PS

	a picture representation of how the NOVQSERV utility operates  
	(send this to a postscript printer)

	
	- REGISTER.PS

	the registration/order form in postscript format  (send this to
	a postscript printer)

	
	- REGISTER.TXT

	the registration/order form in ascii format

	
	- NOVQSERV.EXE

	the NOVQSERV job/print server utility executable.

	
	- NOVQSERV.TAB                                  

	the configuration file containing the specifications for which
	queues are serviced and where jobs extracted from those queues are 
	redirected (jobs do NOT have to be redirected to a specific queue - 
	they may be destined for a command (batch) file and not sent to any
	specific destination queue). 


	- NOVQSERV.CFG                                  

	the configuration file containing all modifiable parameter
	values available for use with NOVQSERV.                       

	
	- DMPTEMP.PS                            

	this is the postscript template file used for creation of dump
	notices sent (to a destination queue) when a non-postscript job is 
	found in a postscript filtered origination (source) queue.  This file 
	should be flagged read-only after the archive is unzipped.                   

	
	- DMPTEMP.ANS                           

	this is the non-postscript template file used for creation of
	dump notices sent (to a destination queue) when a postscript job 
	is found in a non-postscript filtered origination (source) queue.  
	This file should be flagged read-only after the archive is unzipped.


	* the following command (batch) files are used to redirect jobs
	grabbed from a Novell origination (source) queue to some destination 
	(e.g. another Novell queue on the same or different file server, an 
	LPR style queue, or any custom target application).  When jobs 
	are extracted from a specified queue (serviced queues are configured 
	via the NOVQSERV.TAB file) they are first spooled in their entirety 
	to an intermediate file which is then passed (by filename) along with 
	the name of the destination server, destination queue (both also 
	specified via NOVQSERV.TAB), and name of the user who submitted the 
	job to one of the following command (batch) files.  The correct 
	command file to invoke for a particular queue (job grabbed from that
	queue) is dependent upon the job type assigned to that queue in the 
	NOVQSERV.TAB file. Generally speaking, anything that can be done via 
	the DOS command prompt (LPRing a file to a remote queue/printer, 
	converting a document or image to a new format, NPRINTing a job, etc.)
	can be specified as a NOVQSERV service command file.  Remember that you 
	can arrange the %1 (filename), %2 (destination server), %3 
	(destination queue), and %4 (user that submitted job) parameters in 
	any way you wish inside a NOVQSERV command (batch) file.           
						   

	- QSLPR.BAT                             

	this is the sample command (batch) file for use in redirecting
	jobs from a Novell queue to a destination queue serviced by an 
	LPD server.  To use this redirection service, LPR service must 
	be available to the NOVQSERV machine (if not obvious, an associated
	TCP/IP stack must be    properly configured and loaded on the
	NOVQSERV machine).

	The LPR switches provided in this command file will in all
	likelihood need to be modified in order for LPR service to function 
	properly. Specify any switches you desire depending on which LPR 
	(and associated TCP/IP stack)  service (FTP, Wollongong, etc.)
	you use and customize the way that jobs are LPR'd according to
	your printing environment.  Be certain that you can send a job 
	manually to a destination LPR queue as specified in this file (after 
	you've modified it if necessary) using the same switches before
	attempting to use this service with NOVQSERV.  In order to
	cause NOVQSERV to use this command file designate a (source) queue 
	as job type LPR in the NOVQSERV.TAB file.           
	

	- QSNPRINT.BAT                                  

	this is the sample command (batch) file for use in redirecting
	jobs from a Novell queue to another Novell queue.  The 
	destination Novell queue may reside on the same server as the
	origination (source) queue or it may reside on another Netware
	server.  This file may need to be modified if you wish to send 
	jobs to a destination queue residing on a Novell server other than 
	version 3.x.  The reason for this is that NPRINT has different 
	switches depending on which version you are using.  Be certain that 
	you can send a job manually to a destination Novell queue as specified 
	in this file (after you've modified it if necessary) using the same 
	switches (with NPRINT) before attempting to use this service
	with NOVQSERV.  In order to cause NOVQSERV to use this command
	file designate a (source) queue as job type NPRINT in the NOVQSERV.TAB 
	file. 

	
	- CUSTOM1.BAT                           

	this is a sample custom command (batch) file for use with
	queues designated as job type CUSTOM1.  Modify this command file 
	in any way you desire so as to perform an operation of value on a 
	file.  By setting up this command file to provide a valuable service 
	to clients, you can automate the task of job service by merely having 
	clients who require the service send jobs (via capture.exe or other 
	method) to a queue which is serviced by the NOVQSERV machine.                       

	
	- CUSTOM2.BAT                           

	this is a sample custom command (batch) file for use with
	queues designated as job type CUSTOM2.  Modify this command file 
	in any way you desire so as to perform an operation of value on a 
	file.  By setting up this command file to provide a valuable
	service to clients, you can automate the task of job service by
	merely having clients who require the service send jobs (via 
	capture.exe or other method) to a queue which is serviced by the 
	NOVQSERV machine. 

	
	- CUSTOM3.BAT                           

	this is a sample custom command (batch) file for use with queues 
	designated as job type CUSTOM3.  Modify this command file in any 
	way you desire so as to perform an operation of value on a file.  
	By setting up this command file to provide a valuable service to 
	clients, you can automate the task of job service by merely having 
	clients who require the service send jobs (via capture.exe or other 
	method) to a queue which is serviced by the NOVQSERV machine.  
	

	- CUSTOM4.BAT                           

	this is a sample custom command (batch) file for use with
	queues designated as job type CUSTOM4.  Modify this command file in 
	any way you desire so as to perform an operation of value on a file.  
	By setting up this command file to provide a valuable service to 
	clients, you can automate the task of job service by merely having 
	clients who require the service send jobs (via capture.exe or other 
	method) to a queue which is serviced by the NOVQSERV machine. 

	
	- CUSTOM5.BAT                           

	this is a sample custom command (batch) file for use with
	queues designated as job type CUSTOM5.  Modify this command file 
	in any way you desire so as to perform an operation of value on a 
	file.  By setting up this command file to provide a valuable
	service to clients, you can automate the task of job service by
	merely having clients who require the service send jobs (via 
	capture.exe or other method) to a queue which is serviced by the 
	NOVQSERV machine. 

	
	- CUSTOM6.BAT                                   

	this is a sample custom command (batch) file for use with
	queues designated as job type CUSTOM6.  Modify this command file in 
	any way you desire so as to perform an operation of value on a file.  
	By setting up this command file to provide a valuable service to 
	clients, you can automate the task of job service by merely having 
	clients who require the service send jobs (via capture.exe or other 
	method) to a queue which is serviced by the NOVQSERV machine. 

	
	- CUSTOM7.BAT                                   

	this is a sample custom command (batch) file for use with
	queues designated as job type CUSTOM7.  Modify this command file 
	in any way you desire so as to perform an operation of value on a 
	file.  By setting up this command file to provide a valuable
	service to clients, you can automate the task of job service by
	merely having clients who require the service send jobs (via 
	capture.exe or other method) to a queue which is serviced by the 
	NOVQSERV machine.

	
	- QSCFG.EXE                             

	this is the installation utility which provides the ability for
	the NOVQSERV machine to service origination (source) queues.  This 
	utility updates a file server's bindery such that the NOVQSERV user 
	can service the origination (source) queues specified in the 
	NOVQSERV.TAB file.  

	
	- STARTUP.BAT                   

	this is a sample batch file used for automatically logging the
	NOVQSERV machine in to a fileserver and initiating the NOVQSERV 
	utility after the (NOVQSERV) PC is rebooted. Note the way that 
	messages are disabled by the castoff all command.  If this is
	not done, then any message(s) broadcast to the NOVQSERV machine
	will interrupt its operation until the message(s) is cleared.  The 
	standard Novell ODI drivers and client (either NETX or VLM) are 
	required for the NOVQSERV machine to connect to the network and login 
	to a fileserver.
			
	Although the NETX shell works fine, a small performance boost
	can be expected under VLMs due to burst capability.                        

	This startup.bat file is just an example.  Some of you probably
	have better ways of automated machine startup.  The point is that 
	whenever the NOVQSERV machine is rebooted it should come back up 
	automatically.  



ADVISED READING: 
----------------
		
Read the included userguide (UGUIDE.TXT) and INSTALL.TXT files -
or the hardcopy postscript versions - in their  entirety before 
attempting to install and/or use the NOVQSERV utility.  Understanding 
what the NOVQSERVer does and how it works is imperative  in order 
that you may utilize it to your advantage.

 
			   
_________________________________________________________________
DISCLAIMER OF RESPONSIBILITY:

While significant effort has been undertaken to make certain
that this documentation is accurate and that the NOVQSERV
utility operates correctly, no responsibility for its operation
is assumed by the author or distributor.   No liability for
damages arising from or in conjunction with its usage is implied
or assumed by the author or distributor. 

