SpoolPath - Revision history

Gordon.dye: /* Client SPOOLPATH */

2021-12-06T04:14:39Z

Client SPOOLPATH

← Older revision		Revision as of 04:14, 6 December 2021
Line 11:		Line 11:
	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.		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~~====		====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.		For client / server configurations, SPOOLPATH @: client-pathname Sets the remote spool path on the client. This is also where PDF files are created.

Gordon.dye at 04:13, 6 December 2021

2021-12-06T04:13:05Z

← Older revision		Revision as of 04:13, 6 December 2021
Line 11:		Line 11:
	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.		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===		====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.		For client / server configurations, SPOOLPATH @: client-pathname Sets the remote spool path on the client. This is also where PDF files are created.

Laura at 18:31, 31 July 2015

2015-07-31T18:31:37Z

← Older revision		Revision as of 18:31, 31 July 2015
Line 1:		Line 1:
	The '''SPOOLPATH''' [[BRConfig.sys]] configuration statement specifies where print spool files are temporarily stored during printing. ~~Specify~~ a full OS pathname:		The '''SPOOLPATH''' [[BRConfig.sys]] configuration statement specifies where print spool files are temporarily stored during printing. Use it to specify a full OS pathname:

	~~e.g.~~ SPOOLPATH :C:\BR\SPOOL		SPOOLPATH :C:\BR\SPOOL
	SPOOLPATH :/br/spool - Linux or MAC example -		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.		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:
	~~e.g.~~ DRIVE J:,C:\BR,x,\MYAPP with no SPOOLPATH statement would result in spool files being placed in:		DRIVE J:,C:\BR,x,\MYAPP
	C:\BR\SPOOL\		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).		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===		===Client SPOOLPATH===
	~~Client~~ SPOOLPATH ~~specifies where~~ on the client ~~spool files are to be placed~~. This is also where PDF files are created.		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'''		The statement format is: '''SPOOLPATH @::client-OS-fullpath'''
	SPOOLPATH @::C:\BR\SPOOL		SPOOLPATH @::C:\BR\SPOOL

	The ''''@:'''' tells BR that this path is on the client. The second colon in the example tells the client that this is not a relative pathname.		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.		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.

	~~STATUS SUBSTITUTE displays the status of SPOOLPATH and REMOTESPOOLPATH.~~

	The client-pathname has some unique characteristics:		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.		* 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.		* 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.		* Specifying a relative remote pathname is not compatible with CLIENT_CURRENT_DIR SYNC.


	See also:		See also:

Laura: /* Client SPOOLPATH */

2014-09-23T16:38:24Z

Client SPOOLPATH

← Older revision		Revision as of 16:38, 23 September 2014
Line 14:		Line 14:

	The statement format is: '''SPOOLPATH @::client-OS-fullpath'''		The statement format is: '''SPOOLPATH @::client-OS-fullpath'''
	~~e.g.~~ SPOOLPATH @::C:\BR\SPOOL		SPOOLPATH @::C:\BR\SPOOL

	The ''''@:'''' tells BR that this path is on the client. The second colon in the example tells the client that this is not a relative pathname.		The ''''@:'''' tells BR that this path is on the client. 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.		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.

			STATUS SUBSTITUTE displays the status of SPOOLPATH and REMOTESPOOLPATH.

	The client-pathname has some unique characteristics:		The client-pathname has some unique characteristics:

Laura at 18:10, 19 September 2014

2014-09-19T18:10:53Z

← Older revision		Revision as of 18:10, 19 September 2014
Line 28:		Line 28:
	*[[Option (Config)]] 49		*[[Option (Config)]] 49
	*[[SpoolCmd]]		*[[SpoolCmd]]
			*[[Dll#Exceptions\|Dll]] for its discussion on exceptions

	<noinclude>		<noinclude>
	[[Category:Config]]		[[Category:Config]]
	</noinclude>		</noinclude>

Gordon.dye at 01:54, 16 December 2013

2013-12-16T01:54:47Z

← Older revision		Revision as of 01:54, 16 December 2013
Line 2:		Line 2:

	e.g. SPOOLPATH :C:\BR\SPOOL		e.g. 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.		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.

Gordon.dye: total rewrite

2013-12-16T01:50:24Z

total rewrite

← Older revision		Revision as of 01:50, 16 December 2013
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. 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]]~~.		e.g. SPOOLPATH :C:\BR\SPOOL

	~~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.
			e.g. 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).

	SPOOLPATH ~~\\TMP~~		===Client SPOOLPATH===
	~~SPOOLPATH :/usr/wbtmp~~		Client SPOOLPATH specifies where on the client spool files are to be placed. This is also where PDF files are created.

			The statement format is: '''SPOOLPATH @::client-OS-fullpath'''
			e.g. 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. 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.
	~~In order~~ to ~~use~~ the ~~"Old Defaults"~~, ~~modify your wbconfig~~.~~sys~~		* 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.
	~~SPOOLPATH~~ .

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

	See also:		See also:

Laura: 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..."

2013-04-04T19:59:55Z

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

New page

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:
*[[Option (Config)]] 49
*[[SpoolCmd]]

<noinclude>
[[Category:Config]]
</noinclude>