Chain - Revision history

Gordon.dye: /* Parameters */

2024-08-27T04:24:00Z

Parameters

← Older revision		Revision as of 04:24, 27 August 2024
Line 43:		Line 43:
	The differtence between PROC and SUBPROC is that PROC will close the current (lowest level) PROC file (if one is running) before starting the specifified procedure, whereas SUBPROC will not affect a currently running PROC file.		The differtence between PROC and SUBPROC is that PROC will close the current (lowest level) PROC file (if one is running) before starting the specifified procedure, whereas SUBPROC will not affect a currently running PROC file.

	The parameters following file-ref apply only to programs and not procedures.		The parameters following the file-ref apply only to programs and not procedures.

	Following the file-ref information, CHAIN can take three optional parameters, but these parameters should be included only when chaining to a program.		Following the file-ref information, CHAIN can take three optional parameters, but these parameters should be included only when chaining to a program.

Gordon.dye: /* Parameters */

2024-08-27T04:23:02Z

Parameters

← Older revision		Revision as of 04:23, 27 August 2024
Line 42:		Line 42:

	The differtence between PROC and SUBPROC is that PROC will close the current (lowest level) PROC file (if one is running) before starting the specifified procedure, whereas SUBPROC will not affect a currently running PROC file.		The differtence between PROC and SUBPROC is that PROC will close the current (lowest level) PROC file (if one is running) before starting the specifified procedure, whereas SUBPROC will not affect a currently running PROC file.

			The parameters following file-ref apply only to programs and not procedures.

	Following the file-ref information, CHAIN can take three optional parameters, but these parameters should be included only when chaining to a program.		Following the file-ref information, CHAIN can take three optional parameters, but these parameters should be included only when chaining to a program.

Gordon.dye: /* Technical Considerations */

2024-08-27T04:18:18Z

Technical Considerations

← Older revision		Revision as of 04:18, 27 August 2024
Line 54:		Line 54:
	# RUN command options, which are active in the initial program, will remain active in the chained program. These options include RUN PROC and output redirected to a file (see the RUN command for more information).		# RUN command options, which are active in the initial program, will remain active in the chained program. These options include RUN PROC and output redirected to a file (see the RUN command for more information).
	# In Business Rules, there is no need for a USE statement in the program being chained. USE is treated as a comment and is maintained only for compatibility with IBM Business BASIC.		# In Business Rules, there is no need for a USE statement in the program being chained. USE is treated as a comment and is maintained only for compatibility with IBM Business BASIC.
	# Although Business Rules checks most statements for proper syntax as they are entered, the file-ref parameter of the CHAIN statement is not checked until execution (this is also true in the OPEN statement). In this case, variables and quoted strings cannot be checked until execution. ~~Execution errors may arise from text entered as literally inside quotes. The same errors result when a string variable is used as the file-ref if that string does not validly specify an existing file.~~		# Although Business Rules checks most statements for proper syntax as they are entered, the file-ref parameter of the CHAIN statement is not checked until execution (this is also true in the OPEN statement). In this case, variables and quoted strings cannot be checked until execution. # IBM Business BASIC restricted the use of CHAIN statements within IF statements; if the THEN clause was a CHAIN statement, the ELSE clause was not permitted. This restriction does not apply to Business Rules. The following statement is allowed: 90 IF X=0 THEN CHAIN "MENU" ELSE CHAIN "PR2"
	# IBM Business BASIC restricted the use of CHAIN statements within IF statements; if the THEN clause was a CHAIN statement, the ELSE clause was not permitted. This restriction does not apply to Business Rules. The following statement is allowed: 90 IF X=0 THEN CHAIN "MENU" ELSE CHAIN "PR2"
	# The rules for the default extension of a program name, which is specified in a CHAIN statement, are the same as the rules for the LOAD command. In short, the system first looks for an extension of .BR; if that is not present, the system then looks for .BRO. You can change these defaults with the CHAINDFLT specification in the BRConfig.sys file. You can also override the defaults from within the CHAIN statement by specifying your own extension, as in the following example:900 CHAIN "C:\MAIN\MENU.OLD"		# The rules for the default extension of a program name, which is specified in a CHAIN statement, are the same as the rules for the LOAD command. In short, the system first looks for an extension of .BR; if that is not present, the system then looks for .BRO. You can change these defaults with the CHAINDFLT specification in the BRConfig.sys file. You can also override the defaults from within the CHAIN statement by specifying your own extension, as in the following example:900 CHAIN "C:\MAIN\MENU.OLD"
	# The ability to pass specified variables from a program to a procedure is not explicitly supported in Business Rules because ~~all~~ values of all variables are available at the end of a program. These variables retain their values until a SORT, INDEX, CLEAR, or LOAD command is encountered from the keyboard or from a procedure file. This means that any variable from the ~~previous~~ program could be tested by a SKIP command in a procedure file. (Notice that this also means those values of all variables are ~~still~~ available after program termination for ~~printing~~ and debugging.)		# The ability to pass specified variables from a program to a procedure is not explicitly supported in Business Rules because the values of all variables are available at the end of a program. These variables retain their values until a SORT, INDEX, CLEAR, or LOAD command is encountered from the keyboard or from a procedure file. This means that any variable from the calling program could be tested by a SKIP command (or therwise used) in a procedure file. (Notice that this also means those values of all variables are available to an opertor after program termination for interrogation [displaying contents] and debugging.)
	# Like most Business Rules statements, CHAIN may be used in immediate mode like a command (except with the EXECUTE statement, where commands may not terminate a program.) Within a procedure, the following two commands are equivalent: PROC EOM - CHAIN "PROC=EOM"The next two commands would also be equivalent within a procedure: SUBPROC EOM - CHAIN "SUBPROC=EOM" Although using CHAIN, as a command may not seem very useful because the simpler PROC and SUBPROC alternatives exist, ~~it does allow for~~ variables ~~to be passed~~ from ~~a procedure~~ to a program. For example, a procedure file might start a program to print designated messages for certain completion codes as follows: LOAD PROG1 - RUN - X=CODE - SKIP 1 IF X=0 - CHAIN "MESSAGE", X		# Like most Business Rules statements, CHAIN may be used in immediate mode like a command (except with the EXECUTE statement, where commands may not terminate a program.) Within a procedure, the following two commands are equivalent: PROC EOM - CHAIN "PROC=EOM". The next two commands would also be equivalent within a procedure: SUBPROC EOM - CHAIN "SUBPROC=EOM". Although using CHAIN, as a command may not seem very useful because the simpler PROC and SUBPROC alternatives exist, CHAIN allows a procedure to pass variables from it's parent or itself to a program. For example, a procedure file might start a program to print designated messages for certain completion codes as follows: LOAD PROG1 - RUN - X=CODE - SKIP 1 IF X=0 - CHAIN "MESSAGE", X. This passes the variable X (created by PROG1 or the procedure) to be passed to the program named MESSAGE. The same is true if a program CHAINS to a procedure and the procedure simply forwards variables from the chaining program to anotherr program.
			# CHAIN "PROC=XYZ" is similar to EXECUTE "PROC XYZ", except EXECUTE does not end the program. That being said, the procedure has the authority to end the program that called it via EXECUTE.
	# If the FILES keyword is used to keep files open, file pointers are not moved. Thus, pointers, which were at the end of the file in the first program, will also be at the end of the file in the second program; you may use a RESTORE statement to reposition a file pointer.		# If the FILES keyword is used to keep files open, file pointers are not moved. Thus, pointers, which were at the end of the file in the first program, will also be at the end of the file in the second program; you may use a RESTORE statement to reposition a file pointer.

Gordon.dye: /* Comments and Examples */

2024-08-27T03:52:04Z

Comments and Examples

← Older revision		Revision as of 03:52, 27 August 2024
Line 16:		Line 16:
	00900 CHAIN "PROC=GLPOST"		00900 CHAIN "PROC=GLPOST"

	00080 NAME$="EDITLIST"		00080 NAME$="EDITLIST.PRC"
	00090 X$="SUBPROC=GLPROG\"&NAME$		00090 X$="SUBPROC=GLPROG\"&NAME$
	00100 CHAIN X$		00100 CHAIN X$

			When a program chains to a procedure (PROC or SUBPROC), the procedure acts much like the operator stopped the program and started entering commands. A procedure is a set of commands. (However a procedure can skip forward or backward within itself.) While it is emulating a series of commands, the program that initiated the procedure is retained in memory even though the CHAIN statement terminated it. Therefore its variable contents are accessible to the procedure.

	The following example specifies that the string array A$ and the numeric variables B and C are to retain their values in the chained-to program:		The following example specifies that the string array A$ and the numeric variables B and C are to retain their values in the chained-to program:

Gordon.dye: /* Parameters */

2024-08-27T03:29:14Z

Parameters

← Older revision		Revision as of 03:29, 27 August 2024
Line 35:		Line 35:

	===Parameters===		===Parameters===
	The only required parameter of the CHAIN statement is the "file-ref", which specifies the program, procedure, or sub-procedure to be executed. This name and subdirectory information may be specified as a quoted literal string or as a string variable. If the file-ref is preceded with the string "PROC=", the CHAIN initiates a procedure. If the file-ref is preceded with the string "SUBPROC=", the CHAIN initiates a sub-procedure. If neither of these is present, the CHAIN statement attempts to load and run a program.		The only required parameter of the CHAIN statement is the "file-ref", which specifies the program, procedure, or sub-procedure to be executed. This name and subdirectory information may be specified as a quoted literal string or as a string variable.

			If the file-ref is preceded with the string "PROC=", the CHAIN initiates a procedure. If the file-ref is preceded with the string "SUBPROC=", the CHAIN initiates a sub-procedure. If neither of these keywords is present, the CHAIN statement attempts to load and run a program.

			The differtence between PROC and SUBPROC is that PROC will close the current (lowest level) PROC file (if one is running) before starting the specifified procedure, whereas SUBPROC will not affect a currently running PROC file.

	Following the file-ref information, CHAIN can take three optional parameters, but these parameters should be included only when chaining to a program.		Following the file-ref information, CHAIN can take three optional parameters, but these parameters should be included only when chaining to a program.
Line 41:		Line 45:
	"FILES" indicates that all files are to remain open and at their current positions. If you do not specify "FILES", the CHAIN statement closes all files except procedure files.		"FILES" indicates that all files are to remain open and at their current positions. If you do not specify "FILES", the CHAIN statement closes all files except procedure files.

	The "MAT array-name" and "variables" parameters allow the specified arrays or variables to retain their current values in the chained program. If several are used they are seperated by commas.		The "MAT array-name" and "variables" parameters allow the specified arrays or variables to retain their current values in the chained-to program. If several are used they are seperated by commas.

	===Technical Considerations===		===Technical Considerations===

Gordon.dye: /* Syntax */

2024-08-27T03:10:49Z

Syntax

← Older revision		Revision as of 03:10, 27 August 2024
Line 25:		Line 25:

	===Syntax===		===Syntax===
	CHAIN {"<program name>"\|”PROC=<name>”\|”SUPROC=<name>”\|”<path>\<name>”} [,FILES] [,MAT<array name>][,...] [,<~~variables~~>][,...]		CHAIN {"<program name>"\|”PROC=<name>”\|”SUPROC=<name>”\|”<path>\<name>”} [,FILES] [,MAT<array name>][,...] [,<variable name>][,...]

	[[file:Chain.png\|700px]]		[[file:Chain.png\|700px]]

Gordon.dye: /* Syntax */

2024-03-03T06:23:29Z

Syntax

← Older revision		Revision as of 06:23, 3 March 2024
Line 25:		Line 25:

	===Syntax===		===Syntax===
	CHAIN {<program name>\|”PROC=<name>”\|”SUPROC=<name>”\|”<path>\<name>”} [,FILES] [,MAT<array name>][,...] [,<variables>][,...]		CHAIN {"<program name>"\|”PROC=<name>”\|”SUPROC=<name>”\|”<path>\<name>”} [,FILES] [,MAT<array name>][,...] [,<variables>][,...]

	[[file:Chain.png\|700px]]		[[file:Chain.png\|700px]]

Snafoo972 at 02:28, 28 December 2022

2022-12-28T02:28:36Z

← Older revision		Revision as of 02:28, 28 December 2022
Line 22:		Line 22:
	The following example specifies that the string array A$ and the numeric variables B and C are to retain their values in the chained-to program:		The following example specifies that the string array A$ and the numeric variables B and C are to retain their values in the chained-to program:

	60000 CHAIN PROG$ MAT A$,B,C		60000 CHAIN PROG$,MAT A$,B,C

	===Syntax===		===Syntax===

Gordon.dye: /* Technical Considerations */

2017-05-06T15:42:24Z

Technical Considerations

← Older revision		Revision as of 15:42, 6 May 2017
Line 52:		Line 52:
	# The rules for the default extension of a program name, which is specified in a CHAIN statement, are the same as the rules for the LOAD command. In short, the system first looks for an extension of .BR; if that is not present, the system then looks for .BRO. You can change these defaults with the CHAINDFLT specification in the BRConfig.sys file. You can also override the defaults from within the CHAIN statement by specifying your own extension, as in the following example:900 CHAIN "C:\MAIN\MENU.OLD"		# The rules for the default extension of a program name, which is specified in a CHAIN statement, are the same as the rules for the LOAD command. In short, the system first looks for an extension of .BR; if that is not present, the system then looks for .BRO. You can change these defaults with the CHAINDFLT specification in the BRConfig.sys file. You can also override the defaults from within the CHAIN statement by specifying your own extension, as in the following example:900 CHAIN "C:\MAIN\MENU.OLD"
	# The ability to pass specified variables from a program to a procedure is not explicitly supported in Business Rules because all values of all variables are available at the end of a program. These variables retain their values until a SORT, INDEX, CLEAR, or LOAD command is encountered from the keyboard or from a procedure file. This means that any variable from the previous program could be tested by a SKIP command in a procedure file. (Notice that this also means those values of all variables are still available after program termination for printing and debugging.)		# The ability to pass specified variables from a program to a procedure is not explicitly supported in Business Rules because all values of all variables are available at the end of a program. These variables retain their values until a SORT, INDEX, CLEAR, or LOAD command is encountered from the keyboard or from a procedure file. This means that any variable from the previous program could be tested by a SKIP command in a procedure file. (Notice that this also means those values of all variables are still available after program termination for printing and debugging.)
	# Like most Business Rules statements, CHAIN may be used in immediate mode like a command (except with the EXECUTE statement, where commands may not terminate a program.) Within a procedure, the following two commands are equivalent:PROC EOM CHAIN "PROC=EOM"The next two commands would also be equivalent within a procedure:SUBPROC ~~EOMCHAIN~~ "SUBPROC=EOM"Although using CHAIN, as a command may not seem very useful because the simpler PROC and SUBPROC alternatives exist, it does allow for variables to be passed from a procedure to a program. For example, a procedure file might start a program to print designated messages for certain completion codes as follows:LOAD ~~PROG1RUNX~~=~~CODESKIP~~ 1 IF X=~~0CHAIN~~ "MESSAGE", X		# Like most Business Rules statements, CHAIN may be used in immediate mode like a command (except with the EXECUTE statement, where commands may not terminate a program.) Within a procedure, the following two commands are equivalent: PROC EOM - CHAIN "PROC=EOM"The next two commands would also be equivalent within a procedure: SUBPROC EOM - CHAIN "SUBPROC=EOM" Although using CHAIN, as a command may not seem very useful because the simpler PROC and SUBPROC alternatives exist, it does allow for variables to be passed from a procedure to a program. For example, a procedure file might start a program to print designated messages for certain completion codes as follows: LOAD PROG1 - RUN - X=CODE - SKIP 1 IF X=0 - CHAIN "MESSAGE", X
	# If the FILES keyword is used to keep files open, file pointers are not moved. Thus, pointers, which were at the end of the file in the first program, will also be at the end of the file in the second program; you may use a RESTORE statement to reposition a file pointer.		# If the FILES keyword is used to keep files open, file pointers are not moved. Thus, pointers, which were at the end of the file in the first program, will also be at the end of the file in the second program; you may use a RESTORE statement to reposition a file pointer.

Laura: /* Syntax */

2014-04-28T15:19:48Z

Syntax

← Older revision		Revision as of 15:19, 28 April 2014
Line 25:		Line 25:

	===Syntax===		===Syntax===
	CHAIN <program name>\|”PROC=<name>”\|”SUPROC=<name>”\|”<path>\<name>” [,FILES] {[,MAT<array name>] [,<variables>][,]}		CHAIN {<program name>\|”PROC=<name>”\|”SUPROC=<name>”\|”<path>\<name>”} [,FILES] [,MAT<array name>][,...] [,<variables>][,...]

	[[file:Chain.png\|700px]]		[[file:Chain.png\|700px]]