Code - Revision history

Laura at 17:03, 22 May 2014

2014-05-22T17:03:20Z

← Older revision		Revision as of 17:03, 22 May 2014
Line 8:		Line 8:
	008050 IF YEAR < 1987 THEN STOP 1122		008050 IF YEAR < 1987 THEN STOP 1122

	Line ~~850~~ sets CODE to 1122.		Line 8050 sets CODE to 1122.

	The procedure that runs these two programs could test the value of CODE with a SKIP command as follows:		The procedure that runs these two programs could test the value of CODE with a SKIP command as follows:

Laura at 20:03, 20 May 2014

2014-05-20T20:03:27Z

← Older revision		Revision as of 20:03, 20 May 2014
Line 1:		Line 1:
			CODE
	The '''CODE''' [[internal function]] indicates the termination status of a [[program]] as set by the [[STOP]] or [[END]] [[statement]]. This completion code may be used in a [[procedure file]] with the [[SKIP]] [[command]] or it may be used in a subsequent program.		The '''CODE''' [[internal function]] indicates the termination status of a [[program]] as set by the [[STOP]] or [[END]] [[statement]]. This completion code may be used in a [[procedure file]] with the [[SKIP]] [[command]] or it may be used in a subsequent program.

John: moved CODE to Code

2014-02-26T19:35:33Z

moved CODE to Code

← Older revision	Revision as of 19:35, 26 February 2014
(No difference)

John at 19:35, 26 February 2014

2014-02-26T19:35:12Z

← Older revision		Revision as of 19:35, 26 February 2014
Line 1:		Line 1:
	The '''CODE''' internal function indicates the termination status of a [[program]] as set by the [[STOP]] or [[END]] [[statement]]. This completion code may be used in a [[procedure file]] with the [[SKIP]] [[command]] or it may be used in a subsequent program.		The '''CODE''' [[internal function]] indicates the termination status of a [[program]] as set by the [[STOP]] or [[END]] [[statement]]. This completion code may be used in a [[procedure file]] with the [[SKIP]] [[command]] or it may be used in a subsequent program.

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

Mikhail.zheleznov: *

2012-01-19T12:32:04Z

← Older revision		Revision as of 12:32, 19 January 2012
Line 3:		Line 3:
	===Comments and Examples===		===Comments and Examples===

	Suppose that a procedure normally runs two programs, but should not run the second program if there is a data- entry error (e.g., invalid date) in the first program. The first program could set the CODE variable to a non- zero value if this type of error is detected. For example,		Suppose that a procedure normally runs two programs, but should not run the second program if there is a data entry error (e.g., invalid date) in the first program. The first program could set the CODE variable to a non- zero value if this type of error is detected. For example,

	008050 IF YEAR < 1987 THEN STOP 1122		008050 IF YEAR < 1987 THEN STOP 1122
Line 19:		Line 19:
	[[ERR]] is often tested in procedures in a similar way.		[[ERR]] is often tested in procedures in a similar way.

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

	When the system call (either Ctrl-] or the [[System]] command) starts and then exits a secondary software program before returning to BR, the Code function will reflect any return code that the secondary program has passed to the operating system. As soon as BR is reactivated, the value of CODE can be tested to Verify whether or not the secondary program was successful.		When the system call (either Ctrl-] or the [[System]] command) starts and then exits a secondary software program before returning to BR, the Code function will reflect any return code that the secondary program has passed to the operating system. As soon as BR is reactivated, the value of CODE can be tested to Verify whether or not the secondary program was successful.

Mikhail.zheleznov: edit

2012-01-17T14:31:46Z

edit

← Older revision		Revision as of 14:31, 17 January 2012
Line 21:		Line 21:
	====Technical Considerations====		====Technical Considerations====

	When the system call (either Ctrl-] or the [[~~SYSTEM~~]] command) starts and then exits a secondary software program before returning to BR, the Code function will reflect any return code that the secondary program has passed to the operating system. As soon as BR is reactivated, the value of CODE can be tested to Verify whether or not the secondary program was successful.		When the system call (either Ctrl-] or the [[System]] command) starts and then exits a secondary software program before returning to BR, the Code function will reflect any return code that the secondary program has passed to the operating system. As soon as BR is reactivated, the value of CODE can be tested to Verify whether or not the secondary program was successful.

	This feature is available on Unix / Linux versions of Business Rules! only.		This feature is available on Unix / Linux versions of Business Rules! only.

Mikhail.zheleznov: edit

2012-01-13T14:28:55Z

edit

New page

The '''CODE''' internal function indicates the termination status of a [[program]] as set by the [[STOP]] or [[END]] [[statement]]. This completion code may be used in a [[procedure file]] with the [[SKIP]] [[command]] or it may be used in a subsequent program.

===Comments and Examples===

Suppose that a procedure normally runs two programs, but should not run the second program if there is a data- entry error (e.g., invalid date) in the first program. The first program could set the CODE variable to a non- zero value if this type of error is detected. For example,

008050 IF YEAR < 1987 THEN STOP 1122

Line 850 sets CODE to 1122.

The procedure that runs these two programs could test the value of CODE with a SKIP command as follows:

RUN PROGA
SKIP 1 IF CODE>0
RUN PROGB

===Related Functions===

[[ERR]] is often tested in procedures in a similar way.

====Technical Considerations====

When the system call (either Ctrl-] or the [[SYSTEM]] command) starts and then exits a secondary software program before returning to BR, the Code function will reflect any return code that the secondary program has passed to the operating system. As soon as BR is reactivated, the value of CODE can be tested to Verify whether or not the secondary program was successful.

This feature is available on Unix / Linux versions of Business Rules! only.

<noinclude>
[[Category:Internal Functions]]
[[Category:Procedure Commands]]
</noinclude>