WSID - Revision history

Gordon.dye: /* Technical Considerations */

2013-12-16T02:25:49Z

Technical Considerations

← Older revision		Revision as of 02:25, 16 December 2013
Line 13:		Line 13:
	# WSID may be specified only in the [[BRConfig.sys]] file; it is not valid with the [[CONFIG]] command.		# WSID may be specified only in the [[BRConfig.sys]] file; it is not valid with the [[CONFIG]] command.
	# When WSID is specified both in BRConfig.sys and in the BR startup command, Business Rules! uses the value in the BR startup command.		# When WSID is specified both in BRConfig.sys and in the BR startup command, Business Rules! uses the value in the BR startup command.
			# The WSID integer may be followed with a plus sign (+) and an increment value, signifying that the login name may be assigned more than one WSID value.

	Any [[BRConfig.sys]] statements that begin with an "@" character are ignored unless the ~~LOGIN_NAME~~$ variable value matches the character string following the @ character. This will enable you to assign a block of WSID's to each user as follows:		Any [[BRConfig.sys]] statements that begin with an "@" character are ignored unless the [[Login Name$\|Login_Name$]] variable value matches the character string following the @ character. This will enable you to assign a block of WSID's to each user as follows:

	@mary WSID 10+1		@mary WSID 10+1
Line 28:		Line 29:
	BR supports multiple sessions in Windows client environments. Up to nine sessions per workstation are allowed without incrementing the number of users for licensing purposes. To support proper file sharing between multiple local sessions, a SESSION$ system variable is used, similar to WSID$. It consists of the WSID with the session ID (1-9) appended.		BR supports multiple sessions in Windows client environments. Up to nine sessions per workstation are allowed without incrementing the number of users for licensing purposes. To support proper file sharing between multiple local sessions, a SESSION$ system variable is used, similar to WSID$. It consists of the WSID with the session ID (1-9) appended.

	~~Another BRCONFIG.SYS statement is also supported:~~

	WSID=SESSION		WSID=SESSION specifies that WSID will have the session number appended to it.

	~~This~~ specifies that WSID will have the session number appended to it.

	THIS CAN CAUSE PROGRAMS TO FAIL WITH INVALID FILENAMES, if proper care is not applied, because it extends the WSID by one character.		THIS CAN CAUSE PROGRAMS TO FAIL WITH INVALID FILENAMES, if proper care is not applied, because it extends the WSID by one character.

Gordon.dye: /* Technical Considerations */

2013-12-16T02:10:17Z

Technical Considerations

← Older revision		Revision as of 02:10, 16 December 2013
Line 11:		Line 11:

	====Technical Considerations====		====Technical Considerations====
	# WSID may be specified only in the [[BRConfig.sys]] file; it is not valid with [[CONFIG]].		# WSID may be specified only in the [[BRConfig.sys]] file; it is not valid with the [[CONFIG]] command.
	# When WSID is specified both in BRConfig.sys and in the BR command, Business Rules! uses the value in the BR command.		# When WSID is specified both in BRConfig.sys and in the BR startup command, Business Rules! uses the value in the BR startup command.

	~~Now~~ that ~~Windows makes it convenient~~ to assign ~~login names with passwords, Business Rules! encourages their use in all environments.~~		Any [[BRConfig.sys]] statements that begin with an "@" character are ignored unless the LOGIN_NAME$ variable value matches the character string following the @ character. This will enable you to assign a block of WSID's to each user as follows:

	A new convention is provided when processing BRCONFIG.SYS statements. If any statement begins with an "@" character, it is ignored unless the LOGIN_NAME$ variable value matches the character string following the @ character. (See Section 4L New System Variables.) This will enable you to assign a block of WSID's to each user as follows:		@mary WSID 10+1

	@mary WSID 10,1
	@tom WSID 13		@tom WSID 13
	@george WSID 16,1		@george WSID 16+1

	~~This example allows Mary and George to have up to three logins each, whereas Tom would only be allowed one login (omitting the increment value restricts Tom to only WSID 13).~~

	~~Multiple logins are not applicable~~ to multiple ~~Windows sessions. They~~ only ~~apply~~ to ~~logging in at different Windows workstations, or on multiple UNIX sessions~~.		This example allows Mary and George to have multiple logins, whereas Tom would only be allowed one login (omitting the increment value restricts Tom to only WSID 13).

	~~A new configuration statement~~ WSID=UNIQUE ~~is supported, to give~~ each Windows session a new WSID. This differs from the default WSID assignment in that a fresh WSID is assigned for each new session under Windows. By default, each session on a Windows system is assigned the same WSID, with a new session ID number (up to 9 sessions).		WSID=UNIQUE gives each Windows session a new WSID. This differs from the default WSID assignment in that a fresh WSID is assigned for each new session under Windows. By default, each session on a Windows system is assigned the same WSID, with a new session ID number (up to 9 sessions).

	WSID=UNIQUE has the disadvantage of requiring each session to be licensed (each session is considered to be a new user). That is, this feature ends up being significantly more expensive than multiple sessions.		WSID=UNIQUE has the disadvantage of requiring each session to be licensed (each session is considered to be a new user). That is, this feature ends up being significantly more expensive than multiple sessions.

	BR supports multiple sessions in Windows environments. Up to nine sessions per workstation are allowed without incrementing the number of users for licensing purposes. To support proper file sharing between multiple local sessions, a ~~new~~ SESSION$ system variable is ~~defined~~, similar to WSID$. It consists of the WSID with the session ID appended.		BR supports multiple sessions in Windows client environments. Up to nine sessions per workstation are allowed without incrementing the number of users for licensing purposes. To support proper file sharing between multiple local sessions, a SESSION$ system variable is used, similar to WSID$. It consists of the WSID with the session ID (1-9) appended.

	~~;A new~~ BRCONFIG.SYS statement is supported:		Another BRCONFIG.SYS statement is also supported:

	WSID=SESSION		WSID=SESSION

Laura: /* Technical Considerations */

2013-05-07T15:11:26Z

Technical Considerations

← Older revision		Revision as of 15:11, 7 May 2013
Line 41:		Line 41:

	<noinclude>		<noinclude>
	~~[[Category:Configuration and Environmental Settings]]~~
	[[Category:Config]]		[[Category:Config]]
	</noinclude>		</noinclude>

Laura: /* Technical Considerations */

2013-05-07T15:09:21Z

Technical Considerations

← Older revision		Revision as of 15:09, 7 May 2013
Line 41:		Line 41:

	<noinclude>		<noinclude>
			[[Category:Configuration and Environmental Settings]]
	[[Category:Config]]		[[Category:Config]]
	</noinclude>		</noinclude>

Laura: /* Technical Considerations */

2013-04-04T21:20:32Z

Technical Considerations

← Older revision		Revision as of 21:20, 4 April 2013
Line 11:		Line 11:

	====Technical Considerations====		====Technical Considerations====
	# WSID may be specified only in the [[BRConfig.sy]]s file; it is not valid with [[CONFIG]].		# WSID may be specified only in the [[BRConfig.sys]] file; it is not valid with [[CONFIG]].
	# When WSID is specified both in BRConfig.sys and in the BR command, Business Rules! uses the value in the BR command.		# When WSID is specified both in BRConfig.sys and in the BR command, Business Rules! uses the value in the BR command.

Laura: Created page with "The '''WSID''' config specification sets the '''Workstation ID''' (WSID$ and part of Session$). See the BR32.exe startup command for details on specifying ..."

2013-04-04T21:19:37Z

Created page with "The '''WSID''' config specification sets the '''Workstation ID''' (WSID$ and part of Session$). See the BR32.exe startup command for details on specifying ..."

New page

The '''WSID''' [[config]] specification sets the '''Workstation ID''' ([[WSID$]] and part of [[Session$]]). See the [[BR32.exe]] [[startup command]] for details on specifying the workstation ID at start-up by use of a command line parameter. While processing a Business Rules! program you will need to use WSID$ to check the value of WSID. The WSID In Use message tells who has the WSID.

====Syntax====
[[Image:Wsid.png]]

====Start-up Default====
01 for single-user systems. It is based on hardware port for Unix and Linux, and based on order of sign-on for Windows.

====Parameter====
"Integer" is any whole number from 1 to 999.

====Technical Considerations====
# WSID may be specified only in the [[BRConfig.sy]]s file; it is not valid with [[CONFIG]].
# When WSID is specified both in BRConfig.sys and in the BR command, Business Rules! uses the value in the BR command.

Now that Windows makes it convenient to assign login names with passwords, Business Rules! encourages their use in all environments.

A new convention is provided when processing BRCONFIG.SYS statements. If any statement begins with an "@" character, it is ignored unless the LOGIN_NAME$ variable value matches the character string following the @ character. (See Section 4L New System Variables.) This will enable you to assign a block of WSID's to each user as follows:

@mary WSID 10,1
@tom WSID 13
@george WSID 16,1

This example allows Mary and George to have up to three logins each, whereas Tom would only be allowed one login (omitting the increment value restricts Tom to only WSID 13).

Multiple logins are not applicable to multiple Windows sessions. They only apply to logging in at different Windows workstations, or on multiple UNIX sessions.

A new configuration statement WSID=UNIQUE is supported, to give each Windows session a new WSID. This differs from the default WSID assignment in that a fresh WSID is assigned for each new session under Windows. By default, each session on a Windows system is assigned the same WSID, with a new session ID number (up to 9 sessions).

WSID=UNIQUE has the disadvantage of requiring each session to be licensed (each session is considered to be a new user). That is, this feature ends up being significantly more expensive than multiple sessions.

BR supports multiple sessions in Windows environments. Up to nine sessions per workstation are allowed without incrementing the number of users for licensing purposes. To support proper file sharing between multiple local sessions, a new SESSION$ system variable is defined, similar to WSID$. It consists of the WSID with the session ID appended.

;A new BRCONFIG.SYS statement is supported:

WSID=SESSION

This specifies that WSID will have the session number appended to it.

THIS CAN CAUSE PROGRAMS TO FAIL WITH INVALID FILENAMES, if proper care is not applied, because it extends the WSID by one character.

<noinclude>
[[Category:Config]]
</noinclude>