Chapter 6 - Revision history

Mikhail.zheleznov: Fixed incorrect instructions

2019-12-21T17:20:32Z

Fixed incorrect instructions

← Older revision		Revision as of 17:20, 21 December 2019
Line 120:		Line 120:
	Starting Balance: $456.98		Starting Balance: $456.98

	Withdrawal/debits: $34.20, 2.56, 98.42, 17.99, 10.00, 155.54, 49.72		Withdrawal/debits: $34.20, 2.56, 98.42, 17.99, 10.00

			Credits: 155.54, 49.72


	Now figure the balance by hand, with a calculator or with Business Rules! commands. Match the ending balance that the program came up with to this balance. Which is correct? It is important for you to check the results of all the programs you write in this manner.		Now figure the balance by hand, with a calculator or with Business Rules! commands. Match the ending balance that the program came up with to this balance. Which is correct? It is important for you to check the results of all the programs you write in this manner.

	Using the figures above, the CHECKBAL program should have given you an ending balance of $88.05. Please, compare this result to your own calculations.		Using the figures above, the CHECKBAL program should have given you an ending balance of $499.07. Please, compare this result to your own calculations.

	LIST your program again and see if you can determine the cause of this miscalculation. The best first place to look is at the statements that contain mathematical assignments (such as LET statements). Are the formulas correct?		LIST your program again and see if you can determine the cause of this miscalculation. The best first place to look is at the statements that contain mathematical assignments (such as LET statements). Are the formulas correct?

Mikhail.zheleznov: Formatting

2019-12-21T16:55:45Z

Formatting

← Older revision		Revision as of 16:55, 21 December 2019
Line 122:		Line 122:
	Withdrawal/debits: $34.20, 2.56, 98.42, 17.99, 10.00, 155.54, 49.72		Withdrawal/debits: $34.20, 2.56, 98.42, 17.99, 10.00, 155.54, 49.72


	Now figure the balance by hand, with a calculator or with Business Rules! commands. Match the ending balance that the program came up with to this balance. Which is correct? It is important for you to check the results of all the programs you write in this manner.		Now figure the balance by hand, with a calculator or with Business Rules! commands. Match the ending balance that the program came up with to this balance. Which is correct? It is important for you to check the results of all the programs you write in this manner.

Mikhail.zheleznov: Corrected result of example

2019-12-21T16:54:49Z

Corrected result of example

← Older revision		Revision as of 16:54, 21 December 2019
Line 124:		Line 124:
	Now figure the balance by hand, with a calculator or with Business Rules! commands. Match the ending balance that the program came up with to this balance. Which is correct? It is important for you to check the results of all the programs you write in this manner.		Now figure the balance by hand, with a calculator or with Business Rules! commands. Match the ending balance that the program came up with to this balance. Which is correct? It is important for you to check the results of all the programs you write in this manner.

	Using the figures above, the CHECKBAL program should have given you an ending balance of $42.09. ~~Your~~ own calculations ~~should have come to $499.07~~.		Using the figures above, the CHECKBAL program should have given you an ending balance of $88.05. Please, compare this result to your own calculations.

	LIST your program again and see if you can determine the cause of this miscalculation. The best first place to look is at the statements that contain mathematical assignments (such as LET statements). Are the formulas correct?		LIST your program again and see if you can determine the cause of this miscalculation. The best first place to look is at the statements that contain mathematical assignments (such as LET statements). Are the formulas correct?

Mikhail.zheleznov: Added information about using single versus double quotes, as it relates to case sensitivity when using LIST

2019-12-21T16:38:35Z

Added information about using single versus double quotes, as it relates to case sensitivity when using LIST

← Older revision		Revision as of 16:38, 21 December 2019
Line 55:		Line 55:

	===More about LIST===		===More about LIST===

			LIST command is case-sensitive when used with double quotes like this:

			LIST "a"

			The result will display only lines which contain only lowercase "a", but NOT uppercase "A".


			LIST command is case-insensitive when used with single quotes like this:

			LIST 'a'

			The result will display all lines which contain lowercase "a" and uppercase "A".


	The LIST command provides all sorts of helpful ways to make the life of a programmer easier. Besides using it to list an entire program or to search for a certain piece of information, you can use it to display a screen full of program lines starting with the program line you indicate. The following command causes the system to display line 10 and the full screen of information that follows:		The LIST command provides all sorts of helpful ways to make the life of a programmer easier. Besides using it to list an entire program or to search for a certain piece of information, you can use it to display a screen full of program lines starting with the program line you indicate. The following command causes the system to display line 10 and the full screen of information that follows:

Laura: /* 6.10 LOGGING */

2013-08-28T19:45:55Z

6.10 LOGGING

← Older revision		Revision as of 19:45, 28 August 2013
Line 500:		Line 500:
	{\|		{\|
	\|-		\|-
	\|\|'''0 - MAJOR_ERROR'''\|\|~~causes~~ major problems during execution		\|\|'''0 - MAJOR_ERROR'''\|\|major problems occurring during execution
	\|-		\|-
	\|\|'''1 - NOTABLE_ERROR'''\|\|unexpected error likely to cause problems		\|\|'''1 - NOTABLE_ERROR'''\|\|unexpected error likely to cause problems
Line 506:		Line 506:
	\|\|'''2 - MINOR_ERROR'''\|\|unexpected error that can be ignored		\|\|'''2 - MINOR_ERROR'''\|\|unexpected error that can be ignored
	\|-		\|-
	\|\|'''3 - MAJOR_EVENT'''\|\|starting program, exiting, shelling ~~...~~		\|\|'''3 - MAJOR_EVENT'''\|\|starting program, exiting and shelling
	\|-		\|-
	\|\|'''4 - SECURITY_EVENT'''\|\|logons, logon attempts etc		\|\|'''4 - SECURITY_EVENT'''\|\|logons, logon attempts etc
	\|-		\|-
	\|\|'''5 - MINOR_EVENT'''\|\|individual commands ~~...~~		\|\|'''5 - MINOR_EVENT'''\|\|individual commands entered during execution
	\|-		\|-
	\|\|'''9 - DEBUGGING_EVENT'''\|\|added for debugging purposes		\|\|'''9 - DEBUGGING_EVENT'''\|\|added for debugging purposes

Laura: /* 6.10 LOGGING */

2013-08-28T19:44:43Z

6.10 LOGGING

@@ Line 490: / Line 490: @@
 ===6.10 LOGGING===
-(Fill this in)
+The LOGGING config statement will provide logging for debugging purposes.
 NEXT:[[Chapter 7|Unformatted and Formatted Printing]]

Laura: /* 6.4 The RUN command’s STEP and TRACE options */

2013-08-28T19:33:25Z

6.4 The RUN command’s STEP and TRACE options

← Older revision		Revision as of 19:33, 28 August 2013
Line 137:		Line 137:
	RUN STEP TRACE or RUN TRACE STEP		RUN STEP TRACE or RUN TRACE STEP

	'''RUN STEP''' tells Business Rules! to pause after the execution of each program line. During the pause, Business Rules! is in STEP mode. The word STEP appears in the left corner of the status line, and the number of the next line to be executed appears on the right (near the center).		'''RUN STEP''' tells Business Rules! to pause after the execution of each program line. During the pause, Business Rules! is in STEP mode. The word STEP appears in the left corner of the status line, and the number of the next line to be executed appears on the right (near the center). In release 4.3 and later, stepping through a program will also display each statement just before executing it.

	'''STEP''' mode is much like ATTN mode in that it allows you to enter and execute most Business Rules! commands. Business Rules! will remain in STEP mode until you press Enter. It will then execute the next program line and re-enter STEP mode. Note that in release 4.3 and later, stepping through a program will display each program source statement just before executing it.		'''STEP''' mode is much like ATTN mode in that it allows you to enter and execute most Business Rules! commands. Business Rules! will remain in STEP mode until you press Enter. It will then execute the next program line and re-enter STEP mode. Note that in release 4.3 and later, stepping through a program will display each program source statement just before executing it.

Laura: /* Chapter 6 Exercise */

2013-08-28T19:31:53Z

Chapter 6 Exercise

← Older revision		Revision as of 19:31, 28 August 2013
Line 481:		Line 481:

	[[Solutions#CHAPTER 6\|Solution]]		[[Solutions#CHAPTER 6\|Solution]]

			===6.9 Using BREAK and DISPLAY===

			Two more tools that are useful for debugging (as of 4.1) are the BREAK and DISPLAY commands.

			While a program is loaded, you can always enter STATUS BREAK and all the program's current debug settings will be displayed on the screen.

			===6.10 LOGGING===

			(Fill this in)

	NEXT:[[Chapter 7\|Unformatted and Formatted Printing]]		NEXT:[[Chapter 7\|Unformatted and Formatted Printing]]

Laura: /* Debugging Features */

2013-08-28T19:15:24Z

Debugging Features

← Older revision		Revision as of 19:15, 28 August 2013
Line 6:		Line 6:
	*Use the LIST command to search for a character string.		*Use the LIST command to search for a character string.
	*Use PRINT as a command while the program is in execution.		*Use PRINT as a command while the program is in execution.
	*Use READ and DATA statements to automate data entry steps.
	*Use BREAK and DISPLAY.		*Use BREAK and DISPLAY.
	*Use LOGGING.		*Use LOGGING.
			*Use READ and DATA statements to automate data entry steps.

	As your programs become longer, the mistakes that you make will be more and more difficult to detect, which may result in a bug-filled program. A common error such as the following, where a numeric variable is assigned to a character string, could easily become lost in a program of 250 or more lines if the system did not provide a way to help you detect it:		As your programs become longer, the mistakes that you make will be more and more difficult to detect, which may result in a bug-filled program. A common error such as the following, where a numeric variable is assigned to a character string, could easily become lost in a program of 250 or more lines if the system did not provide a way to help you detect it:

Laura: /* Debugging Features */

2013-08-28T19:13:55Z

Debugging Features

← Older revision		Revision as of 19:13, 28 August 2013
Line 7:		Line 7:
	*Use PRINT as a command while the program is in execution.		*Use PRINT as a command while the program is in execution.
	*Use READ and DATA statements to automate data entry steps.		*Use READ and DATA statements to automate data entry steps.
			*Use BREAK and DISPLAY.
			*Use LOGGING.

	As your programs become longer, the mistakes that you make will be more and more difficult to detect, which may result in a bug-filled program. A common error such as the following, where a numeric variable is assigned to a character string, could easily become lost in a program of 250 or more lines if the system did not provide a way to help you detect it:		As your programs become longer, the mistakes that you make will be more and more difficult to detect, which may result in a bug-filled program. A common error such as the following, where a numeric variable is assigned to a character string, could easily become lost in a program of 250 or more lines if the system did not provide a way to help you detect it: