DBCS and NODBCS (JANUS DEFINE parameters): Difference between revisions
m (1 revision) |
mNo edit summary |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:DBCS and NODBCS}} | {{DISPLAYTITLE:DBCS and NODBCS}} | ||
<span class="pageSubtitle"><section begin="desc" /> | <span class="pageSubtitle"><section begin="desc" />Double-byte character set setting<section end="desc" /></span> | ||
DBCS 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]]. | DBCS 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]]. | ||
Revision as of 16:12, 11 March 2011
<section begin="desc" />Double-byte character set setting<section end="desc" />
DBCS and NODBCS are parameters on JANUS DEFINE, whichs define and sets characteristics of a Janus port. See the List of JANUS DEFINE parameters.
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 in the Janus Web Server Reference Manual. see :hdref refid=webdbcs..
DBCS and NODBCS are valid only for WEBSERV ports.
References
See: List of Janus commands | List of JANUS DEFINE parameters.