Built-In Text Editor - Revision history

Laura at 04:30, 20 May 2014

2014-05-20T04:30:39Z

Laura: moved Getting Started to Built-In Text Editor: more accurate title for this page

2014-05-20T04:28:49Z

moved Getting Started to Built-In Text Editor: more accurate title for this page

← Older revision	Revision as of 04:28, 20 May 2014
(No difference)

Laura at 18:14, 19 September 2013

2013-09-19T18:14:51Z

← Older revision		Revision as of 18:14, 19 September 2013
Line 239:		Line 239:

	Speed improvements have been made when resorting via [[AIDX]].		Speed improvements have been made when resorting via [[AIDX]].

			==Configuration==

			See [[Config for Beginners]] for help with your configuration file, [[BRConfig.sys]].

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

Laura at 19:35, 16 September 2013

2013-09-16T19:35:45Z

← Older revision		Revision as of 19:35, 16 September 2013
Line 1:		Line 1:
	[[Business Rules!]] utilizes a very simple text editor for program entry. The editor is available in the system as soon as you start up; all you need to do is type. The options and features of the text editor can be summarized as follows~~, however~~, it is recommended that you use a third party [[:Category:Utilities_Third_Party\|editor]] for a faster editing experience. The		[[Business Rules!]] utilizes a very simple text editor for program entry. The editor is available in the system as soon as you start up; all you need to do is type. The options and features of the text editor can be summarized as follows. However, it is recommended that you use a third party [[:Category:Utilities_Third_Party\|editor]] for a faster editing experience. The
	options and features of the built-in text editor are summarized below:		options and features of the built-in text editor are summarized below:

Laura: /* Quitting Business Rules */

2013-08-05T20:30:03Z

Quitting Business Rules

← Older revision		Revision as of 20:30, 5 August 2013
Line 173:		Line 173:
	The [[SYSTEM]] command followed by an executable name can also be used to temporarily "SHELL OUT" to another program and then return to Business Rules.		The [[SYSTEM]] command followed by an executable name can also be used to temporarily "SHELL OUT" to another program and then return to Business Rules.

	If ~~no programs are running or~~ in ~~error~~ mode, you can also exit BR by simply closing the main window.		If BR is in READY mode, you can also exit BR by simply closing the main window.

	===Comments===		===Comments===

Laura: /* INSTALL SHIELD CHANGES */

2013-08-05T20:28:16Z

INSTALL SHIELD CHANGES

← Older revision		Revision as of 20:28, 5 August 2013
Line 128:		Line 128:

	If the user selects a new location, it is now properly honored by the installation setup. However, no changes are made to any user provided configuration files. This means YOU ARE RESPONSIBLE TO PROVIDE THE PROPER DRIVE STATEMENTS IN A BRCONFIG.SYS FILE PLACED ON THE INSTALLATION MEDIA prior to installation. These must specify the directories to be used AFTER installation.		If the user selects a new location, it is now properly honored by the installation setup. However, no changes are made to any user provided configuration files. This means YOU ARE RESPONSIBLE TO PROVIDE THE PROPER DRIVE STATEMENTS IN A BRCONFIG.SYS FILE PLACED ON THE INSTALLATION MEDIA prior to installation. These must specify the directories to be used AFTER installation.


	;To support updating with Install Shield:		;To support updating with Install Shield:

Laura: /* Basic Actions */

2013-08-05T20:26:59Z

Basic Actions

← Older revision		Revision as of 20:26, 5 August 2013
Line 3:		Line 3:

	==Basic Actions==		==Basic Actions==

			See the [[:Category:Commands\|Command Category]] and [[:Category:Statements\|Statement Category]] for details on each. Below is a simple description of basic actions in BR.
	===Changing a program line===		===Changing a program line===

Line 20:		Line 22:

	===Cut And Paste===		===Cut And Paste===
			The F7 and F8 keys are used to accomplish the tasks of marking, copying, moving and pasting all or a portion of a program line or command. Their functions are described in detail below:
	~~The Business Rules program editor now has cut and paste capability.~~ The F7 and F8 keys are used to accomplish the tasks of marking, copying, moving and pasting all or a portion of a program line or command. Their functions are described in detail below:

	===F7 (Mark/Copy)===		===F7 (Mark/Copy)===

Laura: /* Program debugging extensions */

2013-08-05T20:24:15Z

Program debugging extensions

← Older revision		Revision as of 20:24, 5 August 2013
Line 190:		Line 190:
	===Display===		===Display===

	DISPLAY variable-name / ALL [ OFF / PRINT ] [ >filename ]		DISPLAY variable-name / ALL [ OFF / PRINT ] [ >filename ]

	;Shows the value of 'variable' or all variables, after any changes, plus the line number associated with the change(s), in the format:<br>		;Shows the value of 'variable' or all variables, after any changes, plus the line number associated with the change(s), in the format:<br>
	line-number (that caused the change) variable-name new-value
			line-number (that caused the change) variable-name new-value

			Simply typing the name of the variable into BR will display its current value. Combing this with STEP mode can help the debugging process.

	===Program Flow===		===Program Flow===
	In STEP mode GO indicates GO RUN. Enter indicates GO STEP.		In STEP mode GO indicates GO RUN. Pressing <Enter> indicates GO STEP.

	===Break variable-name / line / label: [ OFF ]===		===Break variable-name / line / label: [ OFF ]===
	~~Causes~~ the program to go into step mode when the variable contents are changed, or the specified line is encountered. Both "BREAK variable" and "DISPLAY variable" may be active on the same variable concurrently.		The [[BREAK]] command causes the program to go into step mode when the variable contents are changed or the specified line is encountered. Both "BREAK variable" and "DISPLAY variable" may be active on the same variable concurrently.

	DISPLAY and BREAK debug commands work with specific array elements.~~<br>~~		DISPLAY and BREAK debug commands work with specific array elements. For example, BREAK CUSTOMER$(6) will cause a program break whenever CUSTOMER$(6) is changed.
	~~e.g.~~ BREAK CUSTOMER$(6) will cause a program break whenever CUSTOMER$(6) is changed.

	:1.) Debug data can be redirected to a file.		:1.) Debug data can be redirected to a file.
	:2.) Debug commands will generate errors 1006 and 1070 instead of ignoring commands with errors.		:2.) Debug commands will generate errors [[1006]] and [[1070]] instead of ignoring commands with errors.
	:3.) Debug now displays up to 240 characters of scalar or array element data instead of just 80 characters.		:3.) Debug now displays up to 240 characters of scalar or array element data instead of just 80 characters.

Laura: /* Operating Mode */

2013-08-05T20:19:33Z

Operating Mode

← Older revision		Revision as of 20:19, 5 August 2013
Line 184:		Line 184:

	===Operating Mode===		===Operating Mode===
	{{:~~Operating~~ Mode}}		When you press Ctrl-A, BR will enter ATTN mode. The operating mode portion of the status line (columns 1-7) contains information about what Business Rules is currently doing. For details on each see [[Operating Mode]] or the [[:Category:Mode\|Mode Category]].

	==Program debugging extensions==		==Program debugging extensions==

Laura: /* Installing Business Rules */

2013-08-05T20:16:24Z

Installing Business Rules

← Older revision		Revision as of 20:16, 5 August 2013
Line 113:		Line 113:
	WBSERVER F:\\CENTRAL\\		WBSERVER F:\\CENTRAL\\

	The WBSERVER.DAT file must be common among the various workstations on a network in order for file sharing to work properly. BR produces error 4175 when a file is opened by the second of two workstations that use different WBSERVER.DAT files.		The WBSERVER.DAT file must be common among the various workstations on a network in order for file sharing to work properly. BR produces error [[4175]] when a file is opened by the second of two workstations that use different WBSERVER.DAT files.

	;Fonts		;Fonts
Line 124:		Line 124:
	===INSTALL SHIELD CHANGES===		===INSTALL SHIELD CHANGES===

	After the License Approval, the installation location is confirmed with a browse option and the automatic creation of any missing directories~~. This much is unchanged~~.		After the License Approval, the installation location is confirmed with a browse option and the automatic creation of any missing directories.

	If the user selects a new location, it is now properly honored by the installation setup. However, no changes are made to any user provided configuration files. This means YOU ARE RESPONSIBLE TO PROVIDE THE PROPER DRIVE STATEMENTS IN A BRCONFIG.SYS FILE PLACED ON THE INSTALLATION MEDIA prior to installation. These must specify the directories to be used AFTER installation.		If the user selects a new location, it is now properly honored by the installation setup. However, no changes are made to any user provided configuration files. This means YOU ARE RESPONSIBLE TO PROVIDE THE PROPER DRIVE STATEMENTS IN A BRCONFIG.SYS FILE PLACED ON THE INSTALLATION MEDIA prior to installation. These must specify the directories to be used AFTER installation.


Line 145:		Line 145:
	[[Installshield]] now permits retention of a pre-existing BRConfig.sys file. During installation, the user will be asked if it should be overwritten.		[[Installshield]] now permits retention of a pre-existing BRConfig.sys file. During installation, the user will be asked if it should be overwritten.

	===Using Business Rules===		==Using Business Rules==

	[[Business Rules!]] must be installed on your system before you can start it~~. See the Installation instructions that came with your system for the proper procedure~~.		[[Business Rules!]] must be installed on your system before you can start it.

	Once [[Business Rules!]] has been installed, you should make sure that the system is accessing the directory within which Business Rules resides.		Once [[Business Rules!]] has been installed, you should make sure that the system is accessing the directory within which Business Rules resides.

	Business Rules must be started from the host operating system with the br start-up command. Since the Unix and Linux operating systems are case sensitive, the command must be entered in lowercase on these systems.		Business Rules must be started from the host operating system with the br start-up command. Since the Unix and Linux operating systems are case sensitive, the command must be entered in lowercase on these systems. See the above section for details.

	The BR start-up command accepts some useful specifications that are outlined in the next section. If you are impatient to get started, however, the following commands show the shortest possible way to start Business Rules.		===Version and Station Number===

	Under DOS and UNIX the BR startup command is simply br, under Windows the command is the name of your particular Business Rules executable file. For instance, if your [[Business Rules!]] program is BR32.exe, then you'd type in BR32 to start [[Business Rules!]]. This command can be connected to a desktop shortcut.


	Version and Station Number

	;Information you should have at hand when you call for support:		;Information you should have at hand when you call for support:
Line 169:		Line 164:
	:7.) Session Id - [[Session$]]		:7.) Session Id - [[Session$]]

			===Status Line===
			Once you start Business Rules, you will notice that the bottom row contains information about the mode, message area, Error Code, line number, program name, procedure status, BR license serial number, and cursor position by row and column number. See [[Status Line]] for details.

	~~===Message Area===~~

	~~The message area portion of the status line (columns 9- 37) contains information about what action is required from the programmer or operator in a particular situation.~~

	~~===Program Name===~~

	~~The program name portion of the status line (columns 49-56) displays the last eight characters of the name of the currently executing program.~~

	~~===Procedure Status===~~

	The procedure status portion of the status line (columns 58-59) displays information about the currently active procedure file. A "P" followed by a number that represents the nested level of the currently active procedure will appear in this position whenever a procedure or sub-procedure is being executed. When a program calls a procedure, or when a procedure is initiated with the [[PROC]]]] command, "P1" is displayed. If that procedure then calls another procedure, "P2" is displayed, and so on. When no procedure file is running this portion of the status line is blank.

	~~===Serial Number===~~

	~~The serial number portion of the status line (columns 61-69) always displays the serial number of the Business Rules system in use.~~

	===Quitting Business Rules===		===Quitting Business Rules===
			The only proper way to exit Business Rules is with the [[SYSTEM]] command. Use of this command returns all control to the operating system. Remember to save all important programs or data before using this command.
	;The only proper way to exit Business Rules is with the [[SYSTEM]] command. Use of this command returns all control to the operating system. Remember to save all important programs or data before using this command:

	The [[SYSTEM]] command followed by an executable name can also be used to temporarily "SHELL OUT" to another program and then return to Business Rules.		The [[SYSTEM]] command followed by an executable name can also be used to temporarily "SHELL OUT" to another program and then return to Business Rules.

	~~===Row and Column / Release Number===~~		If no programs are running or in error mode, you can also exit BR by simply closing the main window.

	~~On Windows versions of Business Rules, the row and column numbers of the cursor's current location appear~~ in ~~the ninth field (columns 75-79). The row number is displayed first~~, ~~then a colon and the column number.~~

	~~On Unix / Linux versions of [[Business Rules!]] (columns 76-79) display~~ the ~~Business Rules release number~~.

	===~~Special Syntax Consideration~~===		===Comments===

	In addition to the syntax described by syntax diagrams, [[Business Rules!]] commands may include a comment at the end of the command. At least one space and an exclamation point must separate the comment from the rest of the command (!).		In addition to the syntax described by syntax diagrams, [[Business Rules!]] commands may include a comment at the end of the command. At least one space and an exclamation point must separate the comment from the rest of the command (!).

	~~===The Status Line===~~		===Interrupting a Program or Procedure===

	Once you have entered Business Rules, you will see the Business Rules sign-on screen and some licensing information. You may press ENTER to hurry the presentation of the licensing information if you wish.

	When the licensing information has left the screen, the status line will appear. The status line is the bottom or 25th line on the screen. Some Unix / Linux terminals do not fully support 25-line displays; if you are using one of these terminals, you will need to press the Esc key to see the status line except when an error occurs in which case the status line is displayed automatically.

	~~For information about how to alter the information or attributes in the status line, see the [[STATUSLINE]] and [[SCREEN]] specifications on the [[BRConfig.sys]] page. See also the [[MSG$]] function.~~

	===Interrupting a Procedure===

	Procedure files may be interrupted in the same manner as ~~identified above for a program~~. However, one difference is that pressing Ctrl-A causes a procedure file to interrupt and cancel the currently executing command. Typing CLEAR PROC ONLY while a procedure is interrupted will end it; typing GO will cause it to continue executing with the next command in the procedure.		Procedure files may be interrupted in the same manner as programs, by pressing Ctrl-A. However, one difference is that pressing Ctrl-A causes a procedure file to interrupt and cancel the currently executing command. Typing CLEAR PROC ONLY while a procedure is interrupted will end it; typing GO will cause it to continue executing with the next command in the procedure.

	===Operating Mode===		===Operating Mode===