Unattended mode: Difference between revisions
Jump to navigation
Jump to search
(Created page with "The UNATTENDED keyword of the Logging config statement will cause BR to run in unattended mode, which means it will run without a startup screen and until a program be...") |
No edit summary |
||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
The UNATTENDED keyword of the [[Logging]] [[config]] statement will cause BR to run in unattended mode, which means it will run without a startup screen and until a program begins to | The UNATTENDED keyword of the [[Logging]] [[config]] statement will cause BR to run in unattended mode, which means it will run without a startup screen and continue running until a program begins to wait for operator input, at which point it will exit BR. This also means BR will also exit if a MSGBOX, OPEN PREVIEW or OPEN SELECT is encountered. | ||
When BR is running in UNATTENDED mode: OPEN #253: redirects console PRINT output to this channel. This means you can capture your console PRINT strings. | |||
[[Category:Mode]] | [[Category:Mode]] | ||
[[Category:Terminology]] | [[Category:Terminology]] |
Latest revision as of 15:45, 23 September 2014
The UNATTENDED keyword of the Logging config statement will cause BR to run in unattended mode, which means it will run without a startup screen and continue running until a program begins to wait for operator input, at which point it will exit BR. This also means BR will also exit if a MSGBOX, OPEN PREVIEW or OPEN SELECT is encountered.
When BR is running in UNATTENDED mode: OPEN #253: redirects console PRINT output to this channel. This means you can capture your console PRINT strings.