UPCASE (JANUS DEFINE parameter) - Revision history

JAL: remove displaytitle

2016-01-27T17:51:22Z

remove displaytitle

← Older revision		Revision as of 17:51, 27 January 2016
Line 1:		Line 1:
	~~{{DISPLAYTITLE:UPCASE}}~~
	<span class="pageSubtitle">Convert client "names" to uppercase</span>		<span class="pageSubtitle">Convert client "names" to uppercase</span>

Line 8:		Line 7:
	Note that it is possible to have lower case userids and passwords in <var class="product">Model 204</var>. For example, the userids <code>HOMER</code>, <code>homer</code>, and <code>Homer</code> would be treated as three separate userids by <var class="product">Model 204</var>. The <var>UPCASE</var> parameter simplifies the interaction between clients (where names tend to be in lowercase) and <var class="product">Model 204</var> (where they tend to be in uppercase).		Note that it is possible to have lower case userids and passwords in <var class="product">Model 204</var>. For example, the userids <code>HOMER</code>, <code>homer</code>, and <code>Homer</code> would be treated as three separate userids by <var class="product">Model 204</var>. The <var>UPCASE</var> parameter simplifies the interaction between clients (where names tend to be in lowercase) and <var class="product">Model 204</var> (where they tend to be in uppercase).

	'''Note:''' The <var>UPCASE</var> parameter never results in data being converted to uppercase. That is, if a client sends variable <code>@customer</code> with a value of <code>Dolly Dinkle</code>, and <var>UPCASE</var> is active for the connection, the <var class="product">User Language</var> application would see a variable called <code>@CUSTOMER</code> with a value of <code>Dolly Dinkle</code>.		<p class="note">'''Note:''' The <var>UPCASE</var> parameter never results in data being converted to uppercase. That is, if a client sends variable <code>@customer</code> with a value of <code>Dolly Dinkle</code>, and <var>UPCASE</var> is active for the connection, the <var class="product">User Language</var> application would see a variable called <code>@CUSTOMER</code> with a value of <code>Dolly Dinkle</code>. </p>

	For <var>[[JANUS DEFINE#type\|SDS]]</var> ports, the <var>UPCASE</var> parameter means that all table and column names passed from the Adaptive Server will be converted to uppercase. This means that when defining the columns and tables (using <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var>), the names must all be uppercase. It also means that if an <var>SDS</var> port has the <var>UPCASE</var> parameter set but has mixed case table and column names, those tables and columns will be inaccessible.		For <var>[[JANUS DEFINE#type\|SDS]]</var> ports, the <var>UPCASE</var> parameter means that all table and column names passed from the Adaptive Server will be converted to uppercase. This means that when defining the columns and tables (using <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var>), the names must all be uppercase. It also means that if an <var>SDS</var> port has the <var>UPCASE</var> parameter set but has mixed case table and column names, those tables and columns will be inaccessible.

JALWiccan: Automatically generated page update

2013-04-16T22:27:15Z

Automatically generated page update

← Older revision		Revision as of 22:27, 16 April 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:UPCASE}}		{{DISPLAYTITLE:UPCASE}}
	<span class="pageSubtitle"~~><section begin="desc" /~~>Convert client "names" to uppercase~~<section end="desc" />~~</span>		<span class="pageSubtitle">Convert client "names" to uppercase</span>

	<var>UPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>UPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

JALWiccan: 1 revision

2012-03-01T21:27:35Z

1 revision

← Older revision	Revision as of 21:27, 1 March 2012
(No difference)

JAL2 at 21:27, 1 March 2012

2012-03-01T21:27:33Z

← Older revision		Revision as of 21:27, 1 March 2012
Line 8:		Line 8:
	Note that it is possible to have lower case userids and passwords in <var class="product">Model 204</var>. For example, the userids <code>HOMER</code>, <code>homer</code>, and <code>Homer</code> would be treated as three separate userids by <var class="product">Model 204</var>. The <var>UPCASE</var> parameter simplifies the interaction between clients (where names tend to be in lowercase) and <var class="product">Model 204</var> (where they tend to be in uppercase).		Note that it is possible to have lower case userids and passwords in <var class="product">Model 204</var>. For example, the userids <code>HOMER</code>, <code>homer</code>, and <code>Homer</code> would be treated as three separate userids by <var class="product">Model 204</var>. The <var>UPCASE</var> parameter simplifies the interaction between clients (where names tend to be in lowercase) and <var class="product">Model 204</var> (where they tend to be in uppercase).

	'''Note:''' The <var>UPCASE</var> parameter never results in data being converted to uppercase. That is, if a client sends variable <code>@customer</code> with a value of <code>Dolly Dinkle</code>, and <var>UPCASE</var> is active for the connection, the User Language application would see a variable called <code>@CUSTOMER</code> with a value of <code>Dolly Dinkle</code>.		'''Note:''' The <var>UPCASE</var> parameter never results in data being converted to uppercase. That is, if a client sends variable <code>@customer</code> with a value of <code>Dolly Dinkle</code>, and <var>UPCASE</var> is active for the connection, the <var class="product">User Language</var> application would see a variable called <code>@CUSTOMER</code> with a value of <code>Dolly Dinkle</code>.

	For <var>[[JANUS DEFINE#type\|SDS]]</var> ports, the <var>UPCASE</var> parameter means that all table and column names passed from the Adaptive Server will be converted to uppercase. This means that when defining the columns and tables (using <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var>), the names must all be uppercase. It also means that if an <var>SDS</var> port has the <var>UPCASE</var> parameter set but has mixed case table and column names, those tables and columns will be inaccessible.		For <var>[[JANUS DEFINE#type\|SDS]]</var> ports, the <var>UPCASE</var> parameter means that all table and column names passed from the Adaptive Server will be converted to uppercase. This means that when defining the columns and tables (using <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var>), the names must all be uppercase. It also means that if an <var>SDS</var> port has the <var>UPCASE</var> parameter set but has mixed case table and column names, those tables and columns will be inaccessible.

JAL2 at 21:19, 1 March 2012

2012-03-01T21:19:54Z

← Older revision		Revision as of 21:19, 1 March 2012
Line 1:		Line 1:
	{{DISPLAYTITLE:UPCASE}}		{{DISPLAYTITLE:UPCASE}}
	<span class="pageSubtitle"><section begin="desc" />Convert client "names" to ~~upper case.~~<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Convert client "names" to uppercase<section end="desc" /></span>

	<var>UPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.		<var>UPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.
Line 14:		Line 14:
	The <var>UPCASE</var> parameter is the opposite of <var>[[NOUPCASE (JANUS DEFINE parameter)\|NOUPCASE]]</var>. The default is for all ports to have <var>UPCASE</var> set.		The <var>UPCASE</var> parameter is the opposite of <var>[[NOUPCASE (JANUS DEFINE parameter)\|NOUPCASE]]</var>. The default is for all ports to have <var>UPCASE</var> set.

	Valid for <var>WEBSERV</var>, OPENSERV and <var>[[JANUS DEFINE#type\|SDS]]</var> port types.		Valid for <var>WEBSERV</var>, <var>OPENSERV</var> and <var>[[JANUS DEFINE#type\|SDS]]</var> port types.

	==See also==		==See also==

JALWiccan: 1 revision

2012-03-01T21:15:18Z

1 revision

← Older revision	Revision as of 21:15, 1 March 2012
(No difference)

JALWiccan: 1 revision

2012-03-01T21:15:13Z

1 revision

← Older revision		Revision as of 21:15, 1 March 2012
Line 6:		Line 6:
	This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports, column names for <var>[[JANUS DEFINE#type\|SDS]]</var> ports and header parameters, header values, cookie names, and form field names for <var>[[JANUS DEFINE#type\|WEBSERV]]</var> ports. By setting <var>UPCASE</var> as a port parameter, the userid and password can be specified by the client in case insensitive form, that is, it can be specified in lower case.		This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports, column names for <var>[[JANUS DEFINE#type\|SDS]]</var> ports and header parameters, header values, cookie names, and form field names for <var>[[JANUS DEFINE#type\|WEBSERV]]</var> ports. By setting <var>UPCASE</var> as a port parameter, the userid and password can be specified by the client in case insensitive form, that is, it can be specified in lower case.

	Note that it is possible to have lower case userids and passwords in ''Model 204''. For example, the userids <code>HOMER</code>, <code>homer</code>, and <code>Homer</code> would be treated as three separate userids by ''Model 204''. The <var>UPCASE</var> parameter simplifies the interaction between clients (where names tend to be in lowercase) and ''Model 204'' (where they tend to be in uppercase).		Note that it is possible to have lower case userids and passwords in <var class="product">Model 204</var>. For example, the userids <code>HOMER</code>, <code>homer</code>, and <code>Homer</code> would be treated as three separate userids by <var class="product">Model 204</var>. The <var>UPCASE</var> parameter simplifies the interaction between clients (where names tend to be in lowercase) and <var class="product">Model 204</var> (where they tend to be in uppercase).

	'''Note:''' The <var>UPCASE</var> parameter never results in data being converted to uppercase. That is, if a client sends variable <code>@customer</code> with a value of <code>Dolly Dinkle</code>, and <var>UPCASE</var> is active for the connection, the User Language application would see a variable called <code>@CUSTOMER</code> with a value of <code>Dolly Dinkle</code>.		'''Note:''' The <var>UPCASE</var> parameter never results in data being converted to uppercase. That is, if a client sends variable <code>@customer</code> with a value of <code>Dolly Dinkle</code>, and <var>UPCASE</var> is active for the connection, the User Language application would see a variable called <code>@CUSTOMER</code> with a value of <code>Dolly Dinkle</code>.

JALWiccan: 1 revision

2012-02-29T22:33:29Z

1 revision

← Older revision	Revision as of 22:33, 29 February 2012
(No difference)

JAL2 at 22:33, 29 February 2012

2012-02-29T22:33:19Z

← Older revision		Revision as of 22:33, 29 February 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />Convert client "names" to upper case.<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Convert client "names" to upper case.<section end="desc" /></span>

	<var>UPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port~~. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]]~~.		<var>UPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.

	This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports, column names for <var>[[JANUS DEFINE#type\|SDS]]</var> ports and header parameters, header values, cookie names, and form field names for <var>[[JANUS DEFINE#type\|WEBSERV]]</var> ports. By setting <var>UPCASE</var> as a port parameter, the userid and password can be specified by the client in case insensitive form, that is, it can be specified in lower case.		This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports, column names for <var>[[JANUS DEFINE#type\|SDS]]</var> ports and header parameters, header values, cookie names, and form field names for <var>[[JANUS DEFINE#type\|WEBSERV]]</var> ports. By setting <var>UPCASE</var> as a port parameter, the userid and password can be specified by the client in case insensitive form, that is, it can be specified in lower case.

JAL2 at 19:29, 29 February 2012

2012-02-29T19:29:35Z

← Older revision		Revision as of 19:29, 29 February 2012
Line 2:		Line 2:
	<span class="pageSubtitle"><section begin="desc" />Convert client "names" to upper case.<section end="desc" /></span>		<span class="pageSubtitle"><section begin="desc" />Convert client "names" to upper case.<section end="desc" /></span>

	UPCASE is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].		<var>UPCASE</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist\|List of JANUS DEFINE parameters]].

	This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports, column names for <var>[[JANUS DEFINE#type\|SDS]]</var> ports and header parameters, header values, cookie names, and form field names for <var>[[JANUS DEFINE#type\|WEBSERV]]</var> ports. By setting UPCASE as a port parameter, the userid and password can be specified by the client in case insensitive form, that is, it can be specified in lower case.		This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for <var>[[JANUS DEFINE#type\|OPENSERV]]</var> ports, column names for <var>[[JANUS DEFINE#type\|SDS]]</var> ports and header parameters, header values, cookie names, and form field names for <var>[[JANUS DEFINE#type\|WEBSERV]]</var> ports. By setting <var>UPCASE</var> as a port parameter, the userid and password can be specified by the client in case insensitive form, that is, it can be specified in lower case.

	Note that it is possible to have lower case userids and passwords in ''Model 204''. For example, the userids HOMER, homer, and Homer would be treated as three separate userids by ''Model 204''. The UPCASE parameter simplifies the interaction between clients (where names tend to be in ~~lower case~~) and ''Model 204'' (where they tend to be in ~~upper case~~).		Note that it is possible to have lower case userids and passwords in ''Model 204''. For example, the userids <code>HOMER</code>, <code>homer</code>, and <code>Homer</code> would be treated as three separate userids by ''Model 204''. The <var>UPCASE</var> parameter simplifies the interaction between clients (where names tend to be in lowercase) and ''Model 204'' (where they tend to be in uppercase).

	<~~blockquote~~> ~~The~~ UPCASE parameter never results in data being converted to ~~upper case~~. That is, if a client sends variable "@customer" with a value of "Dolly Dinkle", and UPCASE is active for the connection, the User Language application would see a variable called "@CUSTOMER" with a value of "Dolly Dinkle".</~~blockquote~~>		'''Note:''' The <var>UPCASE</var> parameter never results in data being converted to uppercase. That is, if a client sends variable <code>@customer</code> with a value of <code>Dolly Dinkle</code>, and <var>UPCASE</var> is active for the connection, the User Language application would see a variable called <code>@CUSTOMER</code> with a value of <code>Dolly Dinkle</code>.

	For <var>[[JANUS DEFINE#type\|SDS]]</var> ports, the UPCASE parameter means that all table and column names passed from the Adaptive Server will be converted to ~~upper case~~. This means that when defining the columns and tables (using <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var>), the names must all be uppercase. It also means that if an <var>~~[[JANUS DEFINE#type\|~~SDS]]</var> port has the UPCASE parameter set but has mixed case table and column names, those tables and columns will be inaccessible.		For <var>[[JANUS DEFINE#type\|SDS]]</var> ports, the <var>UPCASE</var> parameter means that all table and column names passed from the Adaptive Server will be converted to uppercase. This means that when defining the columns and tables (using <var>[[JANCAT (JANUS DEFINE parameter)\|JANCAT]]</var>), the names must all be uppercase. It also means that if an <var>SDS</var> port has the <var>UPCASE</var> parameter set but has mixed case table and column names, those tables and columns will be inaccessible.

	The UPCASE parameter is the opposite of <var>[[NOUPCASE (JANUS DEFINE parameter)\|NOUPCASE]]</var>. The default is for all ports to have UPCASE set.		The <var>UPCASE</var> parameter is the opposite of <var>[[NOUPCASE (JANUS DEFINE parameter)\|NOUPCASE]]</var>. The default is for all ports to have <var>UPCASE</var> set.

	Valid for <var>WEBSERV</var>, OPENSERV and <var>[[JANUS DEFINE#type\|SDS]]</var> port types.		Valid for <var>WEBSERV</var>, OPENSERV and <var>[[JANUS DEFINE#type\|SDS]]</var> port types.