SpoolPath

From BR Wiki
Revision as of 19:59, 4 April 2013 by Laura (talk | contribs) (Created page with "The '''SpoolPath''' BRConfig.sys specification identifies the directory in which the spoolfile is to be created. When this specification is not used, Business Rules! D...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The SpoolPath BRConfig.sys specification identifies the directory in which the spoolfile is to be created. When this specification is not used, Business Rules! DOS, DOS NetWork and OS/2 versions create the spoolfile in the current directory by default. Business Rules Unix, Linux and AIX versions create the spoolfile in the /usr/tmp directory by default.

When using SpoolPath, you should be sure that the specified pathname with the spool file name falls within the operating system's limits for file name lengths. The specified path should not end with a back or forward slash. SpoolPath is not available for use with the Config command.

Unix/Linux considerations: The specified SpoolPath should be no more than two directories from the root, as problems with the lp command that Business Rules uses to spool files may otherwise result. SpoolPath specs may use either Unix / Linux-style or Business Rules-style directory names. If you wish to use Unix / Linux-style names, you must be sure start file names with a colon; this will prevent substitutions and conversion to uppercase.

The following are valid SpoolPath specifications:

SPOOLPATH \\TMP
SPOOLPATH :/usr/wbtmp


In BR 4.2, CONFIG SpoolPath may be used to change the location of the spool files. Also note that the actual names of the print jobs changed considerably.

In Br 4.3, the default spoolpath now defaults to SPOOL in the Root of the First Drive statement. For Example C:\Spool.

This works fine unless there are permission or other conflicts.

In order to use the "Old Defaults", modify your wbconfig.sys

SPOOLPATH .

Also [SPOOLPATH @:] may be used to define the clients spoolpath for use with client server.

See also: