BRconfig.sys - Revision history

Gordon.dye at 06:04, 6 December 2021

2021-12-06T06:04:01Z

← Older revision		Revision as of 06:04, 6 December 2021
Line 74:		Line 74:

	{{:Color}}		{{:Color}}

	~~===Com===~~

	~~{{:Com}}~~

	===Command Console Colors===		===Command Console Colors===

Gordon.dye at 04:20, 6 December 2021

2021-12-06T04:20:39Z

← Older revision		Revision as of 04:20, 6 December 2021
Line 95:		Line 95:
	{{:DataHilite}}		{{:DataHilite}}

	===~~DECIMAL~~===		===Decimal Statement===
	{{:Decimal (Config)}}		{{:Decimal (Config)}}

Line 265:		Line 265:
	{{:@Login_Name}}		{{:@Login_Name}}

	===~~MAXRECALL~~===		===MaxRecall===
	{{:MAXRECALL}}		{{:MAXRECALL}}

	===~~MAX_SORT_MEMORY~~ nn MB===		===Max_Sort_Memory nn MB===

	'''Max_Sort_Memory''' sets the maximum amount of work memory used for sorting and indexing. This prevents long sorting operations from dominating a workstation's memory.		'''Max_Sort_Memory''' sets the maximum amount of work memory used for sorting and indexing. This prevents long sorting operations from dominating a workstation's memory.
Line 283:		Line 283:
	{{:Option (Config)}}		{{:Option (Config)}}

	===~~PAGEOFLOW~~===		===PageOflow===
	{{:PAGEOFLOW (Config)}}		{{:PAGEOFLOW (Config)}}

Line 324:		Line 324:
	{{:SpoolPath}}		{{:SpoolPath}}

	===~~STATUSLINE~~===		===StatusLine===
	{{:Statusline}}		{{:Statusline}}

Line 339:		Line 339:
	{{:TypeAhead}}		{{:TypeAhead}}

	===~~USERLEVEL~~===		===UserLevel===
	{{:Userlevel}}		{{:Userlevel}}

Gordon.dye at 03:41, 6 December 2021

2021-12-06T03:41:41Z

← Older revision		Revision as of 03:41, 6 December 2021
Line 36:		Line 36:
	The environment variable will probably be most useful for specifying user-specific information. The BRConfig.sys specifications for which it is expected to be most useful include [[Substitute]] and [[Include]].		The environment variable will probably be most useful for specifying user-specific information. The BRConfig.sys specifications for which it is expected to be most useful include [[Substitute]] and [[Include]].

	==~~Configuration~~ Specifications==		==Specifications==


Line 91:		Line 91:
	[[image:ccc.jpg]]		[[image:ccc.jpg]]

	===DataHilite ~~and INSERT Mode~~===		===DataHilite===

	{{:DataHilite}}		{{:DataHilite}}

Gordon.dye at 23:27, 5 December 2021

2021-12-05T23:27:55Z

← Older revision		Revision as of 23:27, 5 December 2021
Line 1:		Line 1:
	The '''Business Rules! configuration file''' (generally referred to as the "'''BRConfig.sys'''") contains specifications that ~~put~~ standards ~~into effect for all [[Business Rules!]] processing for a [[workstation]]~~.		The '''Business Rules! configuration file''' (generally referred to as the "'''BRConfig.sys'''") contains ''environmental specifications'' that support the use of standards to be applied across multiple operating environments. In other words when an environment changes your application need not change. Only the configuration file needs to change.

	BRConfig.sys specifications are ~~held~~ in a ~~common~~ text file which Business Rules! automatically accesses at [[BR32.exe]] start-up. You can create and edit this file with any text editor ~~or word processor that can save in a plain text format~~. The line length is limited to 800 characters. See also [[Config for Beginners]].		BRConfig.sys specifications are specified in a plain text file which Business Rules! automatically accesses at [[BR32.exe]] start-up. You can create and edit this file with any text editor. The line length is limited to 800 characters. See also [[Config for Beginners]].

	===~~Enacting~~ BRConfig.sys===		===Invoking BRConfig.sys===
	Whenever [[Business Rules!]] is started with the [[BR32.exe]] command, it automatically searches for a Business Rules! configuration file. Unless you specify otherwise (as a parameter for the BR startup command), Business Rules! assumes that the configuration file is named BRConfig.sys (or BRCONFIG.SYS). Older versions of the Business Rules! configuration file defaulted to the name WBConfig.sys. If BRConfig.sys is not found ~~than~~ WBConfig.sys will be searched for and used if possible.		Whenever [[Business Rules!]] is started with the [[BR32.exe]] command, it automatically searches for a Business Rules! configuration file. Unless you specify otherwise (as a parameter for the BR startup command), Business Rules! assumes that the configuration file is named BRConfig.sys (or BRCONFIG.SYS). Older versions of the Business Rules! configuration file defaulted to the name WBConfig.sys. If BRConfig.sys is not found then WBConfig.sys will be searched for and used if possible.

	There is no limit to the number of configuration files that may exist. If you want Business Rules! to access a configuration file that has a name other than BRConfig.sys (or WBConfig.sys), you must specify its name as part of the BR start-up command. (See the explanation of the [[BR32.exe]] [[command]] or the [[Getting Started]] for more information.)		There is no limit to the number of configuration files that may exist. If you want Business Rules! to access a configuration file that has a name other than BRConfig.sys (or WBConfig.sys), you must specify its name as part of the BR start-up command. (See the explanation of the [[BR32.exe]] [[command]] or the [[Getting Started]] for more information.)

	Business Rules! configuration files may include one or more of the system's ~~powerful~~ BRConfig.sys specifications. A comment, when separated from the specification by one or more spaces, may follow each of these specifications. When Business Rules! is started, the screen displays BRConfig.sys specifications that contain errors. These errors are ignored (default settings are used for any specification with an error), and processing continues without interruption.		Business Rules! configuration files may include one or more of the system's BRConfig.sys specifications. A comment, when separated from the specification by one or more spaces, may follow each of these specifications. When Business Rules! is started, the screen displays BRConfig.sys specifications that contain errors. These errors are ignored (default settings are used for any specification with an error), and processing continues without interruption.

	The remainder of this article contains details about individual BRConfig.sys specifications.		The remainder of this article contains details about individual BRConfig.sys specifications.
Line 14:		Line 14:
	Each specification in the BRConfig.sys file may be followed by at least one space, an exclamation point (!) and a comment. Business Rules! will ignore everything after the exclamation point.		Each specification in the BRConfig.sys file may be followed by at least one space, an exclamation point (!) and a comment. Business Rules! will ignore everything after the exclamation point.

	~~In older (prior to [[4.2]]) versions of BR! the BRConfig.sys file MUST have a drive statement and a server statement, for example:~~		Note: If BR is unable to remove the [[WBServer.dat]] file when the first user logs in, it will attempt to truncate the file to zero bytes before proceeding.

	~~drive c:, c:, c:, br3.83v~~
	~~wbserver c:\ br3.83v~~

	Note: If BR is unable to remove the [[WBServer.dat]] file when the first user logs in, it will ~~now~~ attempt to truncate the file to zero bytes before proceeding.

	==Overriding BRConfig.sys specifications==		==Overriding BRConfig.sys specifications==
Line 25:		Line 20:
	Most specifications set in the BRConfig.sys file can be replaced or overridden in programs by using the syntax "execute 'config XXXXXXXX'" where "XXXXXXXX" is one of many available keywords and associated values. [[Config]] does not actually change the file; it simply overrides the specification in the file. CONFIG will take effect when a program is active. It may be used in a procedure file and it may be specified with the [[Execute]] statement.		Most specifications set in the BRConfig.sys file can be replaced or overridden in programs by using the syntax "execute 'config XXXXXXXX'" where "XXXXXXXX" is one of many available keywords and associated values. [[Config]] does not actually change the file; it simply overrides the specification in the file. CONFIG will take effect when a program is active. It may be used in a procedure file and it may be specified with the [[Execute]] statement.

	~~In [[4.17]]+ a~~ listing of the current specifications and their values can be viewed after Business Rules! is started by entering [[STATUS CONFIG]] at a command prompt from within Business Rules.		A listing of the current specifications and their values can be viewed after Business Rules! is started by entering [[STATUS CONFIG]] at a command prompt from within Business Rules.

	==Defaults==		==Defaults==
Line 35:		Line 30:
	===%env-var%===		===%env-var%===

	All BRConfig.sys specifications and [[Config]] commands ~~now~~ will accept an [[environment variable]] specified in the format %env-var%, where "env-var" is the name of an environment variable that has already been set up at the operating system level.		All BRConfig.sys specifications and [[Config]] commands will accept an [[environment variable]] specified in the format %env-var%, where "env-var" is the name of an environment variable that has already been set up at the operating system level.

	Whenever an environment variable specified in this format is encountered, Business Rules! will substitute the contents of the environment variable in the BRConfig.sys specification. If the specified environment variable is not defined at the operating system level, no substitution will occur. (In some cases an error will result, but in others the environment variable format will be accepted as a literal specification.)		Whenever an environment variable specified in this format is encountered, Business Rules! will substitute the contents of the environment variable in the BRConfig.sys specification. If the specified environment variable is not defined at the operating system level, no substitution will occur. (In some cases an error will result, but in others the environment variable format will be accepted as a literal specification.)

Gordon.dye: /* Graphic Image Cache (Client Server Only) */

2019-06-30T17:39:14Z

Graphic Image Cache (Client Server Only)

← Older revision		Revision as of 17:39, 30 June 2019
Line 225:		Line 225:

	The default is CACHE_ON		The default is CACHE_ON

			[[image:ConfigPic.png]]

	This setting may be overridden on a case by case basis by specifying CACHE_ON or CACHE_OFF following the image filename, for example:		This setting may be overridden on a case by case basis by specifying CACHE_ON or CACHE_OFF following the image filename, for example:

Gordon.dye: /* Graphic Image Cache (Client Server Only) */

2019-06-30T17:36:12Z

Graphic Image Cache (Client Server Only)

← Older revision		Revision as of 17:36, 30 June 2019
Line 222:		Line 222:
	The caching of Picture images on the client is available. Whenever a picture is sent to a BR client the image is saved on the client along with its filename. If another reference is made to the same image (while caching is on), the cached image is used instead of re-forwarding the image to the client. A config statement can turn caching off or on:		The caching of Picture images on the client is available. Whenever a picture is sent to a BR client the image is saved on the client along with its filename. If another reference is made to the same image (while caching is on), the cached image is used instead of re-forwarding the image to the client. A config statement can turn caching off or on:

	~~CONFIG~~ PICTURE ( CACHE_ON CACHE_OFF )		PICTURE CACHE_ON \| CACHE_OFF

	The default is CACHE_ON		The default is CACHE_ON
Line 228:		Line 228:
	This setting may be overridden on a case by case basis by specifying CACHE_ON or CACHE_OFF following the image filename, for example:		This setting may be overridden on a case by case basis by specifying CACHE_ON or CACHE_OFF following the image filename, for example:

	00100 MYIMAGE$="mugshot.jpg,CACHE_OFF" temporarily ~~overrides~~ cache default		00100 MYIMAGE$="mugshot.jpg,CACHE_OFF" to temporarily override cache default
	-or-		-or-
	00200 PRINT FIELDS "1,10,P 3/7,, 20" : "mugshot.jpg,CACHE_OFF" ! temporarily overrides cache default		00200 PRINT FIELDS "1,10,P 3/7,, 20" : "mugshot.jpg,CACHE_OFF" ! temporarily overrides cache default

Gordon.dye: /* Command Console Colors */

2019-06-27T17:00:52Z

Command Console Colors

← Older revision		Revision as of 17:00, 27 June 2019
Line 90:		Line 90:
	The name of this program is: COMCONSL.BR		The name of this program is: COMCONSL.BR

	00100 EXECUTE "CONFIG ATTRIBUTE [~~console~~]/#HRGB:R"		00100 EXECUTE "CONFIG ATTRIBUTE [CMD_CONSOLE]/#HRGB:R"
	00200 EXECUTE "CONFIG SCREEN C [~~console~~]"		00200 EXECUTE "CONFIG SCREEN C [CMD_CONSOLE]"

	====Output====		====Output====

Gordon.dye: /* Command Console Colors */

2019-06-27T16:08:52Z

Command Console Colors

← Older revision		Revision as of 16:08, 27 June 2019
Line 90:		Line 90:
	The name of this program is: COMCONSL.BR		The name of this program is: COMCONSL.BR

	00100 EXECUTE "CONFIG ATTRIBUTE [X]/#HRGB:R"		00100 EXECUTE "CONFIG ATTRIBUTE [console]/#HRGB:R"
	00200 EXECUTE "CONFIG SCREEN C [X]"		00200 EXECUTE "CONFIG SCREEN C [console]"

	====Output====		====Output====

John at 16:01, 19 November 2014

2014-11-19T16:01:12Z

← Older revision		Revision as of 16:01, 19 November 2014
Line 308:		Line 308:
	{{:RD}}		{{:RD}}

	===~~REM~~===		===Rem===
			{{::Rem (config)}}
	~~When '''~~Rem~~''' is placed at the beginning of a line in the [[BRConfig.sys]] file, it disables the line and BR will ignore it as a remark or comment when starting.~~

	===RpnStack===		===RpnStack===

Laura: /* Syntax */

2014-05-12T17:33:12Z

Syntax

← Older revision		Revision as of 17:33, 12 May 2014
Line 280:		Line 280:

	====Syntax====		====Syntax====
			CONFIG GUI {ON\|OFF}
	[[Image:Gui.png]]		[[Image:Gui.png]]