System (command) - Revision history

Gordon.dye: /* Comments and Examples */

2023-07-26T02:04:13Z

Comments and Examples

← Older revision		Revision as of 02:04, 26 July 2023
Line 30:		Line 30:
	The statement below tests to see what type of operating system the program is running on, then executes the appropriate SYSTEM command for the operating system:		The statement below tests to see what type of operating system the program is running on, then executes the appropriate SYSTEM command for the operating system:

	00100 IF WBPLATFORM$="WINDOWS" THEN EXECUTE "SYSTEM DIR" :!ELSE EXECUTE "SYSTEM ls -al /usr/BR"		00100 IF WBPLATFORM$="WINDOWS" THEN EXECUTE "SYSTEM DIR" ELSE EXECUTE "SYSTEM ls -al /usr/BR"

	===Using Batch Files with System Exits===		===Using Batch Files with System Exits===

Gordon.dye at 08:11, 30 January 2023

2023-01-30T08:11:40Z

← Older revision		Revision as of 08:11, 30 January 2023
Line 7:		Line 7:
	==Using SYSTEM to exit BR==		==Using SYSTEM to exit BR==

	Entering SYSTEM or it's short form, SY into the command line while in ready mode will exit BR. The same can be done using an [[Execute]] Statement or a procedure file. Optionally, ~~the~~ SYSTEM LOGOFF may be used when in client server to clear the login credentials. The next time client server is started, the user will be requested to enter their credentials.		Entering SYSTEM or it's short form, SY into the command line while in ready mode will exit BR. The same can be done using an [[Execute]] Statement or a procedure file. If the SYSTEM command is followed by a single number the system exits and passes the number to the OS as a BR return exit value.

			Optionally, SYSTEM LOGOFF may be used when in client server to clear the login credentials. The next time client server is started, the user will be requested to enter their credentials.

	[[image:Sy.jpg]]		[[image:Sy.jpg]]
Line 14:		Line 16:
	==Using SYSTEM to send commands to the operating system==		==Using SYSTEM to send commands to the operating system==
	===Comments and Examples===		===Comments and Examples===
	One use of the SYSTEM command is to run a program. In the following example, the SYSTEM command runs a program called BACKUP. By default, the ~~first~~ program waits until the ~~other~~ program has finished running, and then continues where it left off. The syntax includes the SYSTEM keyword and then the OS command, which in this case is the program name and location of the data to handle.		One use of the SYSTEM command is to run a program. In the following example, the SYSTEM command runs a program called BACKUP. By default, the BR program waits until the called program has finished running, and then continues where it left off. The syntax includes the SYSTEM keyword and then the OS command, which in this case is the program name and location of the data to handle.

	SYSTEM BACKUP C:\\*.DAT A: /S		SYSTEM BACKUP C:\\*.DAT A: /S

	When the same command is used with an ~~asterisks~~ preceding the program name, BACKUP, the BR program restores its own screen upon re-entry:		When the same command is used with an asterisk preceding the program name, BACKUP, the BR program restores its own screen upon re-entry:

			SYSTEM * BACKUP C:\\*.DAT A: /S

			Furthermore, when the same command is used with one or more system-call-flags (described below) ''preceding the program name'' the functionality of the system call is augmented. Note that the OS command flags often need to be right after the program name and ahead of the OS command parameters. But they can also appear after the OS command parameters:

	SYSTEM BACKUP C:\\.DAT A: /S		SYSTEM -s * BACKUP C:\\*.DAT A: /S

	The statement below tests to see what type of operating system the program is running on, then executes the appropriate SYSTEM command for the operating system:		The statement below tests to see what type of operating system the program is running on, then executes the appropriate SYSTEM command for the operating system:

	00100 IF ~~FILE~~$~~(0)(1:3)~~="~~CON:~~" THEN EXECUTE "SYSTEM DIR" :!ELSE EXECUTE "SYSTEM ls -al /usr/BR"		00100 IF WBPLATFORM$="WINDOWS" THEN EXECUTE "SYSTEM DIR" :!ELSE EXECUTE "SYSTEM ls -al /usr/BR"

	===Using Batch Files with System Exits===		===Using Batch Files with System Exits===
Line 47:		Line 53:

	==Syntax==		==Syntax==
	SYSTEM [< code for OS>\|[*]<OS command>]		SYSTEM [<numeric code for OS> \| [system-call-flag] <OS command> ]
	[[Image:System.png]]		[[Image:System.png]]

Line 59:		Line 65:
	'''OS command''' parameter is an operating system command which BR passes to the operating system for execution. If the result of the command requires no operator action, BR is immediately reentered after the command finishes execution. Since BR is active during the entire process, all variable values and memory remain the same. When the '''OS command''' parameter is preceded by an asterisk, the BR screen is restored upon re-entry. The '''OS command''' parameter must be a '''string variable''' or a string enclosed in quotes.		'''OS command''' parameter is an operating system command which BR passes to the operating system for execution. If the result of the command requires no operator action, BR is immediately reentered after the command finishes execution. Since BR is active during the entire process, all variable values and memory remain the same. When the '''OS command''' parameter is preceded by an asterisk, the BR screen is restored upon re-entry. The '''OS command''' parameter must be a '''string variable''' or a string enclosed in quotes.

	~~Additional~~ Flags ~~that~~ can alter the behavior of the shell call as follows:		==System Call Flags==
			System Call Flags can alter the behavior of the shell call as follows:

	{\|		{\|

Gordon.dye at 18:10, 18 November 2021

2021-11-18T18:10:57Z

← Older revision		Revision as of 18:10, 18 November 2021
Line 115:		Line 115:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="60"\|'''-r'''\|\|~~"Restore" means that~~ Windows always performs shell in a separate window. ~~(Unix ignores shell standard out data)~~. If -r is omitted. then Unix forwards standard out and stdin data to and from the client window.		\|width="60"\|'''-r'''\|\|Restores screen after running the command. Windows always performs a shell call in a separate window, so this flag is essentially ignored. This is the same as sys *command. If -r is omitted. then Unix forwards standard out and stdin data to and from the client window.
	~~\|-valign="top"~~
	\|width="60"\| \|\|Restores screen after running command on all systems. In windows, the screen is always restored, so this flag is essentially ignored. This is the same as sys *command. The newer syntax is more readable and preferred.
	\|-valign="top"		\|-valign="top"
	\|}		\|}

GomezL: /* Using SYSTEM to exit BR */

2019-03-26T06:54:53Z

Using SYSTEM to exit BR

← Older revision		Revision as of 06:54, 26 March 2019
Line 7:		Line 7:
	==Using SYSTEM to exit BR==		==Using SYSTEM to exit BR==

	Entering SYSTEM or it's short form, SY into the command line while in ready mode will exit BR. The same can be done using an [[Execute]] Statement or a procedure file.		Entering SYSTEM or it's short form, SY into the command line while in ready mode will exit BR. The same can be done using an [[Execute]] Statement or a procedure file. Optionally, the SYSTEM LOGOFF may be used when in client server to clear the login credentials. The next time client server is started, the user will be requested to enter their credentials.

	[[image:Sy.jpg]]		[[image:Sy.jpg]]

GomezL at 15:50, 1 November 2018

2018-11-01T15:50:30Z

← Older revision		Revision as of 15:50, 1 November 2018
Line 63:		Line 63:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="60"\|'''-E or -e'''\|\|"Errors" indicates that any Operating System errors returned from the shell should be reported (as error ~~4500+~~). Otherwise shell call operating errors are ignored. Occasionally Windows returns error values for fairly nominal exceptions. So the -e is provided as an error return sensitivity level flag.		\|width="60"\|'''-E or -e'''\|\|"Errors" indicates that any Operating System errors returned from the shell should be reported (as error 4300). Otherwise shell call operating errors are ignored. Occasionally Windows returns error values for fairly nominal exceptions. So the -e is provided as an error return sensitivity level flag. Further information can be obtained by querying SYSERR or SYSERR$
	\|-valign="top"		\|-valign="top"
	\|}		\|}

Laura: /* Parameters */

2015-07-27T18:48:17Z

Parameters

← Older revision		Revision as of 18:48, 27 July 2015
Line 63:		Line 63:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="60"\|'''-E or -e'''\|\|("~~errors~~") indicates that any Operating System errors returned from the shell should be reported (as error 4500+) Otherwise shell call operating errors are ignored. Occasionally Windows returns error values for fairly nominal exceptions. So the -e is provided as an error return sensitivity level flag.		\|width="60"\|'''-E or -e'''\|\|"Errors" indicates that any Operating System errors returned from the shell should be reported (as error 4500+). Otherwise shell call operating errors are ignored. Occasionally Windows returns error values for fairly nominal exceptions. So the -e is provided as an error return sensitivity level flag.
	\|-valign="top"		\|-valign="top"
	\|}		\|}
Line 83:		Line 83:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="60"\|'''-s'''\|\|Server Shell Call (this is the default for Unix). If -s is omitted, on Windows, then this shell call is performed on the client.		\|width="60"\|'''-s'''\|\|Server Shell Call (this is the default for Unix). If -s is omitted on Windows, then this shell call is performed on the client.
	\|-valign="top"		\|-valign="top"
	\|}		\|}
Line 107:		Line 107:
	For [[OSX]] 10.6 you need		For [[OSX]] 10.6 you need

	sys -c \| (pipe) ~~(shell~~ commands~~) to~~ make BR Continue after executing the sys -c (continue),		sys -c \| (pipe) Shell commands with a pipe make BR Continue after executing the sys -c (continue), if you do not insert the \| pipe, then the script does not run under Br [[4.18]] and up.
	if you do not insert the \| pipe, then the script does not run under Br [[4.18]] and up.		This was found on a Macintosh client that just updated to OSX 10.6.x
	We found ~~this today~~ on ~~one of our~~ Macintosh ~~clients~~ that just updated to OSX 10.6.x

	\|-valign="top"		\|-valign="top"
Line 116:		Line 115:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="60"\|'''-r'''\|\|("~~restore~~") Windows always performs shell in a separate window. (Unix ignores shell standard out data) If -r is omitted. then Unix forwards standard out and stdin data to and from the client window.		\|width="60"\|'''-r'''\|\|"Restore" means that Windows always performs shell in a separate window. (Unix ignores shell standard out data). If -r is omitted. then Unix forwards standard out and stdin data to and from the client window.
	\|-valign="top"		\|-valign="top"
	\|width="60"\| \|\|Restores screen after running command on all systems. In windows, the screen is always restored, so this flag is essentially ignored. This is the same as sys *command. The newer syntax is more readable and preferred.		\|width="60"\| \|\|Restores screen after running command on all systems. In windows, the screen is always restored, so this flag is essentially ignored. This is the same as sys *command. The newer syntax is more readable and preferred.

Laura: /* Parameters */

2015-07-27T18:44:35Z

Parameters

← Older revision		Revision as of 18:44, 27 July 2015
Line 69:		Line 69:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="60"\|'''-M or -m'''\|\|("~~minimize~~"~~) flag has been enhanced~~.		\|width="60"\|'''-M or -m'''\|\| Run the program "minimized".
	\|-valign="top"		\|-valign="top"
	\|width="60"\| \|\|If a lower case m is specified, the process or program runs in a DOS command shell without displaying the DOS window, but with a corresponding icon on the task bar (effectively running the shelled process/program "minimized") This is only applicable in Windows. It is ignored on all other systems. If -m is omitted, the shelled program will open in a separate application window.		\|width="60"\| \|\|If a lower case m is specified, the process or program runs in a DOS command shell without displaying the DOS window, but with a corresponding icon on the task bar (effectively running the shelled process/program "minimized") This is only applicable in Windows. It is ignored on all other systems. If -m is omitted, the shelled program will open in a separate application window.
Line 77:		Line 77:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="60"\| \|\|If an upper case M is specified, the same thing happens except the task does not appear on the taskbar. Furthermore [[SPOOLCMD]] calls use lowercase m.		\|width="60"\| \|\|If an upper case M is specified, the same thing happens except the task does not appear on the taskbar. It runs invisibly. Furthermore [[SPOOLCMD]] calls use lowercase m.
	\|-valign="top"		\|-valign="top"
	\|}		\|}
Line 89:		Line 89:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="60"\|'''-@'''\|\|Client Shell Call (default for Windows). If -@ is omitted, on Unix - shell call is performed on the server.		\|width="60"\|'''-@'''\|\|If using Client Server, then it runs the program on the client. Client Shell Call is the default for Windows. If -@ is omitted, on Unix the shell call is performed on the server.
	\|-valign="top"		\|-valign="top"
	\|width="60"\| \|\|(search path not implemented on client)		\|width="60"\| \|\|(search path not implemented on client)
Line 103:		Line 103:
	{\|		{\|
	\|-valign="top"		\|-valign="top"
	\|width="60"\|'''-c'''\|\|("~~continue~~") Windows launches task and resumes BR operation where it left off. For Unix, the command is framed with NOHUP and &. If -c is omitted, then the shell call waits til the process is finished ( up to the # seconds specified in SHELL LIMITS) before returning to BR.		\|width="60"\|'''-c'''\|\|The main program "continues" to run while running the called one. Windows launches the task and resumes BR operation where it left off. For Unix, the command is framed with NOHUP and &. If -c is omitted, then the shell call waits til the process is finished (up to the # seconds specified in SHELL LIMITS) before returning to BR.

	For [[OSX]] 10.6 you need		For [[OSX]] 10.6 you need

Laura: /* Comments and Examples */

2015-07-27T18:28:39Z

Comments and Examples

← Older revision		Revision as of 18:28, 27 July 2015
Line 14:		Line 14:
	==Using SYSTEM to send commands to the operating system==		==Using SYSTEM to send commands to the operating system==
	===Comments and Examples===		===Comments and Examples===
	One use of the SYSTEM command is to run a program. In the following example, the SYSTEM command runs a program called BACKUP. By default, the first program waits until the other program has finished running, and then continues where it left off.		One use of the SYSTEM command is to run a program. In the following example, the SYSTEM command runs a program called BACKUP. By default, the first program waits until the other program has finished running, and then continues where it left off. The syntax includes the SYSTEM keyword and then the OS command, which in this case is the program name and location of the data to handle.

	SYSTEM BACKUP C:\\*.DAT A: /S		SYSTEM BACKUP C:\\*.DAT A: /S

Laura: /* Using SYSTEM to exit BR */

2015-07-27T18:19:15Z

Using SYSTEM to exit BR

← Older revision		Revision as of 18:19, 27 July 2015
Line 9:		Line 9:
	Entering SYSTEM or it's short form, SY into the command line while in ready mode will exit BR. The same can be done using an [[Execute]] Statement or a procedure file.		Entering SYSTEM or it's short form, SY into the command line while in ready mode will exit BR. The same can be done using an [[Execute]] Statement or a procedure file.

	[[image:Sy.~~png~~]]		[[image:Sy.jpg]]
	[[image:System2.~~png~~]]		[[image:System2.jpg]]

	==Using SYSTEM to send commands to the operating system==		==Using SYSTEM to send commands to the operating system==

Laura at 18:18, 27 July 2015

2015-07-27T18:18:15Z

← Older revision		Revision as of 18:18, 27 July 2015
Line 4:		Line 4:

	System can be executed from [[READY mode]], from a [[procedure file]], or with the [[Execute]] [[statement]].		System can be executed from [[READY mode]], from a [[procedure file]], or with the [[Execute]] [[statement]].

			==Using SYSTEM to exit BR==

			Entering SYSTEM or it's short form, SY into the command line while in ready mode will exit BR. The same can be done using an [[Execute]] Statement or a procedure file.

			[[image:Sy.png]]
			[[image:System2.png]]

	==Using SYSTEM to send commands to the operating system==		==Using SYSTEM to send commands to the operating system==