DBCS and NODBCS (JANUS DEFINE parameters): Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:DBCS and NODBCS}}
<span class="pageSubtitle">Double-byte character set setting</span>
<span class="pageSubtitle"><section begin="desc" />Double-byte character set setting<section end="desc" /></span>


<var>DBCS</var> and NODBCS are parameters on [[JANUS DEFINE]], whichs define and sets characteristics of a Janus port. See the [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].
<var>DBCS</var> and <var>NODBCS</var> are parameters on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port.  


This parameter indicates whether or not the <var class="product">Model 204</var> <var>DBCS</var> parameter is to be automatically set to 1 on requests to a <var>[[JANUS DEFINE#type|WEBSERV]]</var> port. The default of <var>NODBCS</var> leaves the <var>DBCS</var> parameter unaffected on requests to a <var>WEBSERV</var> port.


 
Setting the <var class="product">[[Janus Web Server]]</var> <var>DBCS</var> parameter so web requests to a particular port can use DBCS is necessary if an Online running with double-byte character support (DBCSENV is non-zero) does not have DBCS set on for sdaemon threads.  
This parameter indicates whether or not the ''Model 204'' <var>DBCS</var> parameter is to be automatically set to 1 on requests to a WEBSERV port. The default of NODBCS leaves the <var>DBCS</var> parameter unaffected on requests to a WEBSERV port.
 
Setting the ''[[Janus Web Server]]'' <var>DBCS</var> parameter so web requests to a particular port can use DBCS is necessary if an Online running with double-byte character support (DBCSENV is non-zero) does not have DBCS set on for sdaemon threads.  


The most likely use of the <var>DBCS</var> parameter is in an environment that serves both DBCS and non-DBCS terminals and browsers.  
The most likely use of the <var>DBCS</var> parameter is in an environment that serves both DBCS and non-DBCS terminals and browsers.  
Line 14: Line 11:
For information about specifying DBCS support at the application level, see the $Web_DBCS parameter.  
For information about specifying DBCS support at the application level, see the $Web_DBCS parameter.  


<var>DBCS</var> and NODBCS are valid only for WEBSERV ports.
<var>DBCS</var> and <var>NODBCS</var> are valid only for <var>WEBSERV</var> ports.


==References==
==See also==
<ul>
<li>[[List of Janus commands]]
<li>[[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]]
</ul>


See: [[List of Janus commands]] | [[JANUS DEFINE#parmlist|List of JANUS DEFINE parameters]].


[[Category:JANUS DEFINE parameters|DBCS and NODBCS]]
[[Category:JANUS DEFINE parameters|DBCS and NODBCS]]

Latest revision as of 22:24, 15 January 2016

Double-byte character set setting

DBCS and NODBCS are parameters on JANUS DEFINE, which defines and sets characteristics of a Janus port.

This parameter indicates whether or not the Model 204 DBCS parameter is to be automatically set to 1 on requests to a WEBSERV port. The default of NODBCS leaves the DBCS parameter unaffected on requests to a WEBSERV port.

Setting the Janus Web Server DBCS parameter so web requests to a particular port can use DBCS is necessary if an Online running with double-byte character support (DBCSENV is non-zero) does not have DBCS set on for sdaemon threads.

The most likely use of the DBCS parameter is in an environment that serves both DBCS and non-DBCS terminals and browsers.

For information about specifying DBCS support at the application level, see the $Web_DBCS parameter.

DBCS and NODBCS are valid only for WEBSERV ports.

See also

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=DBCS_and_NODBCS_(JANUS_DEFINE_parameters)&oldid=82445"