SpoolPath: Difference between revisions

Latest revision as of 04:14, 6 December 2021

The SPOOLPATH BRConfig.sys configuration statement specifies where print spool files are temporarily stored during printing. Use it to specify a full OS pathname:

SPOOLPATH  :C:\BR\SPOOL
SPOOLPATH  :/br/spool       - Linux or MAC example -

SPOOLPATH defaults to a spool directory that runs off of the BR root of the first drive statement. If no such spool directory exists and SPOOLPATH is not specified then BR creates one. For example:

DRIVE   J:,C:\BR,x,\MYAPP

with no SPOOLPATH statement would result in spool files being placed in:

C:\BR\SPOOL\

The status of SPOOLPATH and REMOTESPOOLPATH settings are displayed in response to the STATUS SUBSTITUTE command (not the STATUS CONFIG command). Instead, STATUS SUBSTITUTE displays the status of SPOOLPATH and REMOTESPOOLPATH.

Client Spoolpath

For client / server configurations, SPOOLPATH @: client-pathname Sets the remote spool path on the client. This is also where PDF files are created.

The statement format is: SPOOLPATH @::client-OS-fullpath

SPOOLPATH  @::C:\BR\SPOOL

The '@:' tells BR that this path is on the client, or remote. The second colon in the example tells the client that this is not a relative pathname.

SPOOLPATH can be set concurrently for both client and server by specifying two SPOOLPATH statements. BR creates print files in the server spool directory during printing and forwards them to the client when the print file is closed.

The client-pathname has some unique characteristics:

Relative paths are assumed to be OS pathnames relative to the CLIENT_CURRENT_DIR folder, or the client startup directory if CLIENT_CURRENT_DIR is not specified.
If a full pathname is specified it must begin with a colon. (e.g. @::X:\path ). Otherwise, it will be preceded with the path to the client current working directory.
Specifying a relative remote pathname is not compatible with CLIENT_CURRENT_DIR SYNC.

@@ Line 1: / Line 1: @@
-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.
+The '''SPOOLPATH''' [[BRConfig.sys]]  configuration statement specifies where print spool files are temporarily stored during printing. Use it to specify a full OS pathname:
-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]].
+ SPOOLPATH  :C:\BR\SPOOL
+ SPOOLPATH  :/br/spool       - Linux or MAC example -
-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.
+SPOOLPATH defaults to a spool directory that runs off of the BR root of the first drive statement. If no such spool directory exists and SPOOLPATH is not specified then BR creates one. For example:
+ DRIVE   J:,C:\BR,x,\MYAPP
+with no SPOOLPATH statement would result in spool files being placed in:
+ C:\BR\SPOOL\
-The following are valid SpoolPath specifications:
+The status of SPOOLPATH and REMOTESPOOLPATH settings are displayed in response to the STATUS SUBSTITUTE command (not the STATUS CONFIG command). Instead, STATUS SUBSTITUTE displays the status of SPOOLPATH and REMOTESPOOLPATH.
- SPOOLPATH \\TMP
+====Client Spoolpath====
- SPOOLPATH :/usr/wbtmp
+For client / server configurations, SPOOLPATH @: client-pathname Sets the remote spool path on the client. This is also where PDF files are created.
+The statement format is: '''SPOOLPATH @::client-OS-fullpath'''
+ SPOOLPATH  @::C:\BR\SPOOL
-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.
+The ''''@:''''  tells BR that this path is on the client, or remote. The second colon in the example tells the client that this is not a relative pathname.
-In Br 4.3, the default spoolpath now defaults to SPOOL in the Root of the First Drive statement.   For Example C:\Spool.
+SPOOLPATH can be set concurrently for both client and server by specifying two SPOOLPATH statements. BR creates print files in the server spool directory during printing and forwards them to the client when the print file is closed.
-This works fine unless there are permission or other conflicts.
+The client-pathname has some unique characteristics:
+* Relative paths are assumed to be OS pathnames relative to the CLIENT_CURRENT_DIR folder, or the client startup directory if CLIENT_CURRENT_DIR is not specified.
+* If a full pathname is specified it must begin with a colon.  (e.g. @::X:\path ). Otherwise, it will be preceded with the path to the client current working directory.
+* Specifying a relative remote pathname is not compatible with CLIENT_CURRENT_DIR SYNC.
-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:
 *[[Option (Config)]] 49
 *[[SpoolCmd]]
+*[[Dll#Exceptions|Dll]] for its discussion on exceptions
 <noinclude>
 [[Category:Config]]
 </noinclude>

SpoolPath: Difference between revisions

Latest revision as of 04:14, 6 December 2021

Client Spoolpath

Navigation menu

Search