DBCS and NODBCS (JANUS DEFINE parameters): Difference between revisions
mNo edit summary |
mNo edit summary |
||
| Line 2: | Line 2: | ||
<span class="pageSubtitle"><section begin="desc" />Double-byte character set setting<section end="desc" /></span> | <span class="pageSubtitle"><section begin="desc" />Double-byte character set setting<section end="desc" /></span> | ||
<var>DBCS</var> and <var>NODBCS</var> are parameters on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port | <var>DBCS</var> and <var>NODBCS</var> are parameters on [[JANUS DEFINE]], which defines and sets characteristics of a Janus port. | ||
Revision as of 22:33, 29 February 2012
<section begin="desc" />Double-byte character set setting<section end="desc" />
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.