UPCASE (JANUS DEFINE parameter): Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (1 revision)
mNo edit summary
Line 1: Line 1:
{{DISPLAYTITLE:UPCASE}}
{{DISPLAYTITLE:UPCASE}}
<span class="pageSubtitle"><section begin="desc" /><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 [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].
UPCASE is a parameter on [[JANUS DEFINE]], 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 OPENSERV ports, column names for SDS ports and header parameters, header values, cookie names, and form field names for WEBSERV 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.


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).


This parameter indicates that all client "names" are to be converted to upper case. "Names" includes userids and passwords, variable names for OPENSERV ports, column names for SDS ports and header parameters, header values, cookie names, and form field names for WEBSERV 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.
<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 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).<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>  


For SDS 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 JANCAT), the names must all be upper case. It also means that if an SDS port has the UPCASE parameter set but has mixed case table and column names, those tables and columns will be inaccessible.  
For SDS 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 JANCAT), the names must all be upper case. It also means that if an SDS port has the UPCASE parameter set but has mixed case table and column names, those tables and columns will be inaccessible.  
Line 14: Line 14:
The UPCASE parameter is the opposite of NOUPCASE. The default is for all ports to have UPCASE set.  
The UPCASE parameter is the opposite of NOUPCASE. The default is for all ports to have UPCASE set.  


Valid for &P$WBSYB port types.
Valid for WEBSERV, OPENSERV and SDS port types.


==References==
==References==

Revision as of 16:22, 14 March 2011

<section begin="desc" />Convert client "names" to upper case.<section end="desc" />

UPCASE is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port. See the 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 OPENSERV ports, column names for SDS ports and header parameters, header values, cookie names, and form field names for WEBSERV 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.

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).

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".

For SDS 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 JANCAT), the names must all be upper case. It also means that if an SDS port has the UPCASE parameter set but has mixed case table and column names, those tables and columns will be inaccessible.

The UPCASE parameter is the opposite of NOUPCASE. The default is for all ports to have UPCASE set.

Valid for WEBSERV, OPENSERV and SDS port types.

References

See: List of Janus commands | List of JANUS DEFINE parameters.