Run - Revision history

Gordon.dye: /* Parameters */

2024-02-28T19:34:45Z

Parameters

← Older revision		Revision as of 19:34, 28 February 2024
Line 61:		Line 61:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="10%"\|'''"PROC" '''\|\|accept input from the procedure file that contains this command, for all INPUT, LINPUT, and RINPUT statements. Normally the input for these statements would come from the keyboard. The RUN PROC option has no effect on INPUT FIELDS or RINPUT FIELDS statements.		\|width="10%"\|'''"PROC" '''\|\|accept input from the procedure file that contains this command, for all INPUT, LINPUT, and RINPUT statements. Normally the input for these statements would come from the keyboard. The RUN PROC option has no effect on INPUT FIELDS or RINPUT FIELDS statements. (see Technical Considerations below)
	\|-valign="top"		\|-valign="top"
	\|}		\|}

Gordon.dye: /* Technical Considerations */

2024-02-28T19:33:23Z

Technical Considerations

← Older revision		Revision as of 19:33, 28 February 2024
Line 81:		Line 81:
	==Technical Considerations==		==Technical Considerations==

	# BR closes a procedure before executing the last line. Thus when RUN file-ref is included as the last line, there is a clean trade-off in the number of open files on the system. But RUN PROC cannot be used as the last line because the procedure will be closed before the program starts to look for data in the procedure (an easy solution is to add a ~~blank line or~~ comment line after the RUN PROC command).		# BR closes a procedure before executing the last line. Thus when RUN file-ref is included as the last line, there is a clean trade-off in the number of open files on the system. But RUN PROC cannot be used as the last line because the procedure will be closed before the program starts to look for data in the procedure (an easy solution is to add a comment line ( ! - exclamation point ) after the RUN PROC command).
	~~# The use of RUN PROC does not alter the forward slash's (/) capability of terminating INPUT, LINPUT and RINPUT statements. See the INPUT statement for additional information~~.
	# RUN >file-ref remains in effect until another RUN command is issued. Output redirected to a file is not accessible until the file is closed by another RUN command.		# RUN >file-ref remains in effect until another RUN command is issued. Output redirected to a file is not accessible until the file is closed by another RUN command.

Gordon.dye: /* Parameters */

2024-02-28T19:30:26Z

Parameters

← Older revision		Revision as of 19:30, 28 February 2024
Line 59:		Line 59:
	\|}		\|}

	~~The RUN command with the~~ "PROC" ~~parameter works only within a procedure file. It instructs BR to~~ accept input from the procedure file for all INPUT, LINPUT, and RINPUT statements. Normally the input for these statements would come from the keyboard. The RUN PROC option has no effect on INPUT FIELDS or RINPUT FIELDS statements.		{\|
			\|-valign="top"
			\|width="10%"\|'''"PROC" '''\|\|accept input from the procedure file that contains this command, for all INPUT, LINPUT, and RINPUT statements. Normally the input for these statements would come from the keyboard. The RUN PROC option has no effect on INPUT FIELDS or RINPUT FIELDS statements.
			\|-valign="top"
			\|}

	If you wish to start running the program from a point other than the beginning, you can use "line-num" to specify the first line of execution.		If you wish to start running the program from a point other than the beginning, you can use "line-num" to specify the first line of execution.

John at 15:50, 12 April 2018

2018-04-12T15:50:05Z

← Older revision		Revision as of 15:50, 12 April 2018
Line 1:		Line 1:
	The '''Run (RU)''' command begins execution of a program. When RUN is used to redirect printer output to a file or screen (RUN> filename) the redirection is now stopped only when the system returns to READY mode (when no programs or procedures remain active). This allows redirection to work with a procedure file that contains multiple RUN commands. Previously, the redirection remained active only until the next RUN command was issued.		The '''Run (RU)''' [[command]] begins execution of a program. When RUN is used to redirect printer output to a file or screen (RUN> filename) the redirection is now stopped only when the system returns to READY mode (when no programs or procedures remain active). This allows redirection to work with a procedure file that contains multiple RUN commands. Previously, the redirection remained active only until the next RUN command was issued.

	==Comments and Examples==		==Comments and Examples==

Laura: /* Syntax */

2014-05-08T17:03:54Z

Syntax

← Older revision		Revision as of 17:03, 8 May 2014
Line 24:		Line 24:

	==Syntax==		==Syntax==
	RUN <file name> [TRACE [PRINT]][...] [{STEP\|PROC\|<line number>\|>[>]<file name>}[...]		RUN <file name> [ [[TRACE]] [PRINT]][...] [{[[STEP]]\|[[PROC]]\|<[[line number]]>\|>[>]<file name>}[...]

	[[Image:Run.png]]		[[Image:Run.png]]

Laura: /* Syntax */

2014-05-06T17:55:22Z

Syntax

← Older revision		Revision as of 17:55, 6 May 2014
Line 24:		Line 24:

	==Syntax==		==Syntax==
			RUN <file name> [TRACE [PRINT]][...] [{STEP\|PROC\|<line number>\|>[>]<file name>}[...]

	[[Image:Run.png]]		[[Image:Run.png]]

Laura: /* Parameters */

2013-01-08T21:25:56Z

Parameters

← Older revision		Revision as of 21:25, 8 January 2013
Line 36:		Line 36:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="10%"\|'''"File-~~ref~~'''\|\| is the name and path of the file you wish to run. BR to see that the named file exists, then performs a CLEAR operation and loads and begins executing the specified file. File names which are the same as any of RUN's parameters (TRACE, PRINT, STEP or PROC) cannot be specified with the RUN command. Also, file names that are also numbers cannot be specified with RUN (the number will be interpreted as a "line-num" parameter -see below) unless the extension is also specified (i.e., RUN 123.BR). It is important to note that the system will always clear current memory and load the specified file, even if that file is currently in memory -thus the potential exists for losing unstored program lines.		\|width="10%"\|'''"File-name"'''\|\| is the name and path of the file you wish to run. BR to see that the named file exists, then performs a CLEAR operation and loads and begins executing the specified file. File names which are the same as any of RUN's parameters (TRACE, PRINT, STEP or PROC) cannot be specified with the RUN command. Also, file names that are also numbers cannot be specified with RUN (the number will be interpreted as a "line-num" parameter -see below) unless the extension is also specified (i.e., RUN 123.BR). It is important to note that the system will always clear current memory and load the specified file, even if that file is currently in memory -thus the potential exists for losing unstored program lines.
	\|-valign="top"		\|-valign="top"
	\|}		\|}

Mikhail.zheleznov: Imported RUN command page from old wiki

2011-12-26T15:49:50Z

Imported RUN command page from old wiki

New page

The '''Run (RU)''' command begins execution of a program. When RUN is used to redirect printer output to a file or screen (RUN> filename) the redirection is now stopped only when the system returns to READY mode (when no programs or procedures remain active). This allows redirection to work with a procedure file that contains multiple RUN commands. Previously, the redirection remained active only until the next RUN command was issued.

==Comments and Examples==

RUN sets all variables to zero (or zero length) and begins executing at the lowest line number of the program. Open files stay open. Execution halts and an error message is displayed on the status line when an error occurs during program execution.

A running program stops when it reaches a STOP, END, or CHAIN statement within the program; all open files close (except when the optional FILES parameter is used in a CHAIN statement). A running program pauses when it reaches a PAUSE statement or when you press the Ctrl-A key combination. To resume execution, enter a GO command (see the options for the GO command in the GO section of this chapter).

The following command begins execution of the program in memory at line 350:

RUN 350

The next command executes the program in memory and sends all printer output to the file REPORT. The use of the double redirection arrow (>>) causes the output to be appended to the end of REPORT (rather than to overwrite it):

RUN >>REPORT

The command below begins execution of the program in memory and directs printer output to the screen:

RUN >CON:

The following command loads and begins execution of the program SCORE. All TRACE output is sent to the printer.

RUN B:SCORE TRACE PRINT

==Syntax==

[[Image:Run.png]]

==Defaults==

# RUN the program currently in memory.
# Send TRACE output to the screen.

==Parameters==

{|
|-valign="top"
|width="10%"|'''"File-ref'''|| is the name and path of the file you wish to run. BR to see that the named file exists, then performs a CLEAR operation and loads and begins executing the specified file. File names which are the same as any of RUN's parameters (TRACE, PRINT, STEP or PROC) cannot be specified with the RUN command. Also, file names that are also numbers cannot be specified with RUN (the number will be interpreted as a "line-num" parameter -see below) unless the extension is also specified (i.e., RUN 123.BR). It is important to note that the system will always clear current memory and load the specified file, even if that file is currently in memory -thus the potential exists for losing unstored program lines.
|-valign="top"
|}

{|
|-valign="top"
|width="10%"|'''"TRACE" '''||displays the line number of each line as it is being executed. Unlike STEP, it does not cause the program to pause before executing each statement. This parameter is very useful for debugging purposes. To turn TRACE off, you must interrupt BR (Ctrl-A) and use GO RUN to continue execution.
|-valign="top"
|}

{|
|-valign="top"
|width="10%"|'''"PRINT" '''||sends TRACE output to an attached printer.
|-valign="top"
|}

{|
|-valign="top"
|width="10%"|'''"STEP" '''||pauses the program before each statement is executed. The line number field in the status line tells you the next line number to be executed. That line is executed and the next line number appears when <CR> is pressed. STEP is useful for debugging of programs, as it allows you to closely follow the program's flow.
|-valign="top"
|}

The RUN command with the "PROC" parameter works only within a procedure file. It instructs BR to accept input from the procedure file for all INPUT, LINPUT, and RINPUT statements. Normally the input for these statements would come from the keyboard. The RUN PROC option has no effect on INPUT FIELDS or RINPUT FIELDS statements.

If you wish to start running the program from a point other than the beginning, you can use "line-num" to specify the first line of execution.

"File_ref saves to a file all program output that normally goes to the printer. Use of one redirection arrow (>) causes output to overwrite the contents of the specified file. Two redirection arrows (>>) cause the output to be appended to the end of the specified file.

The >file-ref can also redirect printer output to other communications devices. To send output to the screen, for example, use:

RUN >CON:

To send it to whatever device is connected to the first communications port, use:

RUN >AUX:

These strings must be translated with the SUBSTITUTE specification for BR or Linux versions. BR sends all program results to the specified file-ref location until you enter another RUN command.

==Technical Considerations==

# BR closes a procedure before executing the last line. Thus when RUN file-ref is included as the last line, there is a clean trade-off in the number of open files on the system. But RUN PROC cannot be used as the last line because the procedure will be closed before the program starts to look for data in the procedure (an easy solution is to add a blank line or comment line after the RUN PROC command).
# The use of RUN PROC does not alter the forward slash's (/) capability of terminating INPUT, LINPUT and RINPUT statements. See the INPUT statement for additional information.
# RUN >file-ref remains in effect until another RUN command is issued. Output redirected to a file is not accessible until the file is closed by another RUN command.

<noinclude>
[[Category:Commands]]
[[Category:Program Management Commands]]
</noinclude>