						INSTALL.TXT
 

 * Before installing the NOVQSERV utility, read the userguide
(UGUIDE.TXT) file in its  entirety.  Also read the entirety of
the README.TXT file and the entirety of this file before 
installing. It is important that you understand what this
utility does and how it works to  make installation and
operation as seamless as possible.  Certain ambiguities as to
the  installation and operation of the NOVQSERV utility may be
clarified by reading and  understanding all of the
documentation... 



This utility must be installed on and run from a network drive. 
	    



This procedure assumes that you have previously copied the
entirety of the unzipped  NOVQSERV  archive to a network
directory.

_________________________________________________________________

CONFIGURATION and INSTALLATION:



 STEP 1. Modify the NOVQSERV.TAB queue service configuration
file.



       The NOVQSERV.TAB file specifies which queues the NOVQSERV
utility will extract jobs  from and where those jobs will be
redirected to.  The format of the NOVQSERV.TAB file is as 
follows:

|------------|-------------|-----------------|-----------|--------|-------------|     
| Column 1   | Column 2    | Column 3        | Column 4  |Column 5| Column 6    |
|------------|-------------|-----------------|-----------|--------|-------------| 
|server that |origin queue |server where     |destination|job type|filter       |
|origin queue|name (source)|destination queue|queue name |        |Specification|
|resides on  |             |resides (target) |(target)   |        |             |
|------------|-------------|-----------------|-----------|--------|-------------|

Column 1 represents the name of the Netware file server where
the queue named in column 2 is defined.  The value in this
column must specify an accessible Novell file server.  



Column 2 is the name of the queue which will have jobs extracted
from it by the NOVQSERV  machine.  The value in this column must
specify an existing queue that is defined on the  Novell server
listed in column 1.



Column 3 is the name of the server (Netware server, LPD server,
or other server) where the  destination queue named in column 4
is defined (lives).  



Column 4 is the name of the destination queue where extracted
jobs (from the queue named in  column 2) will be sent.  



*NOTE: Columns 3 and 4 need not specify a target server name and
a target queue name, they may be used to represent any
meaningful parameters to be passed to a NOVQSERV command (batch)
file.   The two strings (values) represented in these two
columns are blindly passed to the  appropriate command file
(explained next) and can therefore be used in a custom command 
(batch) file in any way deemed meaningful by you.  The value in
column 3 (destination server) is passed as %2 (parameter two),
and the value in column 4 (destination queue) is passed as %3
(parameter three).  



Column 5 is the job type to use for all jobs extracted from the
queue listed in column 2.  This field specifies how to operate
on jobs grabbed from the source queue. This field can be one of 
nine different values as follows:



Job Type        Meaning
--------        ----------------------------------------------------------

LPR             The QSLPR.BAT command file is called for each extracted job.  

NPRINT          The QSNPRINT.BAT command file is called for each extracted job.  

CUSTOM1         The CUSTOM1.BAT command file is called for each extracted job.  

CUSTOM2         The CUSTOM2.BAT command file is called for each extracted job.     

CUSTOM3         The CUSTOM3.BAT command file is called for each extracted job.  

CUSTOM4         The CUSTOM4.BAT command file is called for each extracted job  

CUSTOM5         The CUSTOM5.BAT command file is called for each extracted job.     

CUSTOM6         The CUSTOM6.BAT command file is called for each extracted job.     

CUSTOM7         The CUSTOM7.BAT command file is called for each extracted job. 

   

Column 6 is the filter specification for jobs
extracted from the source queue (specified in  column 2).  This
field specifies whether to filter the jobs as postscript 'P',
non-postscript  'A', or no filtering 'N'.

explanations of the three filtering options follow:


	'P' -   If you want to preclude non-postscript jobs from ever
getting to a postscript printer so as to avoid having many pages of
postscript code printed and backing  up other print jobs then the
'P' filtering option is useful. Because there is no universal standard as
to what a postscript file must contain, however, you must configure the 
NOVQSERV machine to recognize what a valid postscript job should look like.  
Look at the user guide (uguide.txt) and the sample NOVQSERV.CFG file
included in this directory to learn more about configuring postscript 
filtering.      



The applicable configuration parameters (set in NOVQSERV.CFG) are:              

		postscript scan chars

		postscript dump chars

		ps filter string

		pass all postscript queue jobs

		enable dumps

		discardfile

		dumpfile      


	'A' -   If you want to preclude postscript jobs from ever
getting to a non-postscript printer so as to avoid the printer hanging up 
or getting confused then the 'A' filtering option is useful.  Be careful about 
how you tune the NOVQSERV postscript filtering, though.  ANY job grabbed from 
an 'A' filtered queue will look like a postscript job to the NOVQSERV machine 
if it contains ANY of the ps filter strings specified in the NOVQSERV.CFG file, 
and will therefore be discarded.  See the 'P' filtering option and the 
associated parameters found in the NOVQSERV.CFG file along with the userguide 
(uguide.txt) for more information on postscript filtering. 
				  

	'N' -   This option disables filtering.  No filter is applied to
jobs extracted from the origin (source) queue, they are passed through to the
appropriate command (batch) file regardless of whether they are postscript 
or not. This option should be used with queues that have jobs ultimately 
directed to a printer which auto-switches between postscript and non-
postscript printing modes (e.g. an HP IVsi).  This filter option should also 
be used with any queues that have jobs ultimately destined for a custom 
command (batch) file - unless, of course, the command file requires only 
postscript or non-postscript jobs.
				  

	Generally speaking, the 'P' and 'A' filter options are useful
in conjunction with queues that are used for printing. However, if you have 
created a command file that specifically requires either postscript or 
non-postscript files to operate on, there is nothing which prevents you from 
utilizing one of these filter options.    

					  
	*NOTE: The discard notification which is sent to the
appropriate destination queue when a job is discarded (filtered) from a 'P' 
or 'A' filtered queue only appears with queues that are either job type LPR 
or NPRINT (discard notices still appear on the NOVQSERV screen and in the 
discard log file [and dump log file if appropriate] in the event of a
different job type).

		    
	The NOVQSERV.TAB file may not include any comments.  If you are
configuring the NOVQSERV utility to service (origination) queues which 
reside on more than one file server, make sure  that you group all queues 
which live on a particular server together in the NOVQSERV.TAB file.   
In other words, do not alternate between queues residing on different file 
servers.  The overhead required to switch the NOVQSERV connection to the 
proper file server dictates more efficient  operation when all serviced
queues defined on a particular server are grouped together.

		    
NOVQSERV.TAB correct groupings:            
----------------------------------------------
ORIGSRV fromqueue SOMELPRSRV dstqueue LPR A      

ORIGSRV somequeue SOMELPRSRV dstpsqueue LPR P     

ORIGSRV anotherqueue NVLPSRV novpsqueue NPRINT P      

ORIGSRV adiffqueue NVLPSRV hp4siqueue NPRINT N      

NOVSRV2 somequeue NVLPSRV novpsqueue NPRINT P      

NOVSRV2 herequeue SOMELPRSRV dstqueue LPR A      

NOVSRV2 adiffqueue NOSERVER noqueue CUSTOM1 N


NOVQSERV.TAB incorrect (inefficient) groupings:            
-----------------------------------------------
ORIGSRV fromqueue SOMELPRSRV dstqueue LPR A      

NOVSRV2 somequeue NVLPSRV novpsqueue NPRINT P      

ORIGSRV somequeue SOMELPRSRV dstpsqueue LPR P      

NOVSRV2 herequeue SOMELPRSRV dstqueue LPR A      

ORIGSRV anotherqueue NVLPSRV novpsqueue NPRINT P      

ORIGSRV adiffqueue NVLPSRV hp4siqueue NPRINT N     

NOVSRV2 adiffqueue NOSERVER noqueue CUSTOM1 N



	*NOTE: If you are configuring the NOVQSERV utility to
service (origination) queues residing on more than one file server, be 
certain to read the userguide (UGUIDE.TXT) section on configuring the 
NOVQSERV.CFG file for multiple servers.
		      
		      

A sample NOVQSERV.TAB is included for reference.

		      

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



STEP 2.  Create a user so that the NOVQSERV machine will be able
to login and/or attach to the  file server(s) that have queues
to be serviced.  Use the same method that you use to create a 
general user, and be certain that you give the user (any
username that you like will do) a  password.  You must create
this user (with the same username and password as you used on
the  first file server - these must both be synchronized across
all file servers that the NOVQSERV  machine will service) on all
file servers that are listed in column 1 (origin servers) of the
 NOVQSERV.TAB file.  



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



STEP 3.   Login to the NOVQSERV home file server (the first one
listed to be serviced in  column 1 of the NOVQSERV.TAB file). 
This will be the file server that the NOVQSERV machine 
(remember the user that you created for the NOVQSERV utility...)
first logs into before the  actual NOVQSERV.EXE executable is
run.  Be certain when you (not the NOVQSERV username) login 
(now) that you have supervisory privileges.  You must have
supervisory privileges because the  QSCFG.EXE utility (explained
in step 4) needs to modify the file server's bindery.



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



STEP 4.  Run the QSCFG.EXE utility from the same directory that
the NOVQSERV.TAB file resides in. This utility configures the
Netware bindery (of a file server that will have queues
serviced)  such that the NOVQSERV user has rights to service the
queues listed in the NOVQSERV.TAB file. When this utility is
run, it prompts for the username of the NOVQSERV machine (the
username created in step 2 for each serviced file server, and
what the NOVQSERV PC will eventually login  or attach as) and
then scans the NOVQSERV.TAB file before modifying the bindery as
necessary.   Make sure before running this utility that you are
logged into the server where the origination  (source) queues to
be serviced reside (or if there are multiple origination file
servers, the  first origination file server listed in column 1
of the NOVQSERV.TAB file - the home file server)  and that the
default drive (if it is a network drive) is mapped to the same
server (the one where  the origination queues reside, and also
the one you are logged into).  If your default drive is  mapped
to a different server, that server's bindery will be used and
the bindery of the proper  server (where the source queues
reside and where you are logged in) will not be properly
modified.          



If your NOVQSERV.EXE utility is capable of servicing multiple
file servers and your NOVQSERV.TAB file is configured to do so
(the unregistered version of NOVQSERV can service only up to two
origination file servers...  the registered version can service
up to 8 origination  file servers.), then you must run this
utility once for each origination server listed in column 1  of
the NOVQSERV.TAB file.          



Follow the previous instructions just as for the first
origination file server - make sure that you created the
NOVQSERV user (with the same username and password that you used
when creating the  NOVQSERV user on the home file server - 
username and password must be synchronized on all origination
file servers that are serviced!), then login to the appropriate
origination file server (any one that has not had this
configuration utility run on it yet) and/or run this utility
(QSCFG.EXE) from a drive that is mapped to the same appropriate
file server.  You don't have to necessarily login to the  file
server that you want to allow the NOVQSERV machine to service. 
Attaching and mapping a drive to that file server will work as
long as you have that drive set as the default drive when you
run the QSCFG utility (make sure that a copy of the NOVQSERV.TAB
file is also in this directory).  The file server which the
current default drive is mapped to automatically becomes the
default file server for any bindery operations performed - which
is why this method will work.  Remember that whether you login
to an origination file server or just attach to it and map a
drive, you must have supervisory rights in order for this
configuration utility to complete successfully (it must be able
to modify the bindery).



A file named ADDQUES.LOG will be created (or overwritten if it
already exists) in the default directory every time the
QSCFG.EXE utility is run.  This file will contain results for
the attempted  QSCFG.EXE operations.  If any of the origination
queues specified in the NOVQSERV.TAB file could not be made
serviceable for the NOVQSERV user, go back to the NOVQSERV.TAB
file and make sure that there were no typos made in the
origination server or origination queue columns (columns 1 and
2).  Also be sure that you were attempting to run the QSCFG.EXE
utility while logged in or attached with supervisory privileges.
These are the two most common problems encountered at QSCFG.EXE
run time.                                    



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



STEP 5.  Set up an automated way for the NOVQSERV machine to
start up on reboot.  This is a suggestion - the NOVQSERV utility
can be invoked manually if you desire (why you would I don't
know).  



The appropriate ODI drivers and desired Netware shell must be
loaded, then the NOVQSERV user (created previously) logged into
the home file server.  After the user is logged in, the NOVQSERV
user should change to the directory where the NOVQSERV utility
(and associated support files) resides, then NOVQSERV can be
kicked off to start servicing jobs. 



_________________________________________________________________
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. 

