JAL2 at 21:25, 31 October 2011

2011-10-31T21:25:59Z

← Older revision		Revision as of 21:25, 31 October 2011
Line 1:		Line 1:

	<var class="product">Janus Web Server</var> now supports use of the IBM Double Byte Character Set.		<var class="product">Janus Web Server</var> now supports use of the IBM Double Byte Character Set.
	This means that <var class="product">Janus Web Server</var> applications can exchange DBCS data with Web		This means that <var class="product">Janus Web Server</var> applications can exchange DBCS data with Web
Line 15:		Line 14:
	to double-byte characters is indicated by a special character known as a		to double-byte characters is indicated by a special character known as a
	"shift-out" (meaning shift out of single byte mode) and		"shift-out" (meaning shift out of single byte mode) and
	terminated by a "shift-in" (revert to single byte mode)		terminated by a "shift-in" (revert to single byte mode).
	Single-byte characters remain unchanged.		Single-byte characters remain unchanged.
	Although shift characters are not typically displayed (or sometimes displayed as spaces),		Although shift characters are not typically displayed (or sometimes displayed as spaces),
Line 51:		Line 50:
	[[$Web_Get_Cookie]]		[[$Web_Get_Cookie]]
	[[$Web_Parm]]		[[$Web_Parm]]
	[[$~~Web_Isindex_Parm~~]]		[[$Web_IsIndex_Parm]]
	</p>		</p>
	The following API functions return string lengths in bytes		The following API functions return string lengths in bytes
Line 61:		Line 60:
	[[$Web_Form_Parm_Len]]		[[$Web_Form_Parm_Len]]
	[[$Web_Hdr_Len]]		[[$Web_Hdr_Len]]
	[[$~~Web_Hdr_Parm_Len~~]]		[[$Web_Hdr_Parm_Lstr]]
	[[$Web_Len]]		[[$Web_Len]]
	[[$~~Web_Isindex_Len~~]]		[[$Web_IsIndex_Len]]
	[[$~~Web_Isindex_Parm_Len~~]]		[[$Web_IsIndex_Parm_Len]]
	[[$~~Web_Url_Parm_Len~~]]		[[$Web_URL_Parm_Len]]
	</p>		</p>

	[[Category:Janus Web Server]]		[[Category:Janus Web Server]]

JAL2: Created page with " `Janus Web Server` now supports use of the IBM Double Byte Character Set. This means that `Janus Web Server` applications can e..."

2011-10-31T21:19:41Z

Created page with " <var class="product">Janus Web Server</var> now supports use of the IBM Double Byte Character Set. This means that <var class="product">Janus Web Server</var> applications can e..."

New page

<var class="product">Janus Web Server</var> now supports use of the IBM Double Byte Character Set.
This means that <var class="product">Janus Web Server</var> applications can exchange DBCS data with Web
browsers which support Shift-JIS DBCS encoding.

To enable the DBCS feature on a <var class="product">Janus Web Server</var> port,
specify the <var>[[DBCS and NODBCS|DBCS]]</var> parameter on the port definition.
The online must also have the <var>CCAIN</var> parameter
<code>DBCSENV=1</code> to enable the <var class="product">Model 204</var> <var>DBCS</var> feature.

DBCS data is encoded differently in mainframe and PC environments.
On IBM mainframes, DBCS data is bracketed with "shift" characters to show where
double-byte data begins and ends.
A switch from single-byte characters
to double-byte characters is indicated by a special character known as a
"shift-out" (meaning shift out of single byte mode) and
terminated by a "shift-in" (revert to single byte mode)
Single-byte characters remain unchanged.
Although shift characters are not typically displayed (or sometimes displayed as spaces),
they do occupy space in a character string.
Programmers should take this into account when allocating string variables that may hold DBCS data.

On PCs, there are several different methods of encoding double-byte character data.
<var class="product">Janus Web Server</var> supports Shift-JIS encoding, also known as MS-Kanji.
Despite its name, Shift-JIS encoding
does not use shift characters to indicate the start and end of double-byte characters.
"Shift" in this case refers to the fact that the encoding ranges
that indicate double-byte characters skip, or shift, around ASCII
codes that already represent single-byte displayable characters.
Because of this, no intervening special characters are necessary to indicate a switch from
single-byte encoding to double-byte encoding.

In <var class="product">Model 204</var>, there are two types of DBCS data.
Pure DBCS data, which contains
double-byte characters only (so the shift out and shift in bytes are not required),
and mixed DBCS data, which contains a combination of single- and double-byte characters
requiring shift-out and shift-in bytes.
<var class="product">Janus Web Server</var> functions that return string
data always use the mixed DBCS format.
DBCS string input to <var class="product">Janus Web Server</var> functions must also be mixed format.

Some <var class="product">Janus Web Server</var> API functions work slightly differently when running in a
DBCS environment.
The following functions may return DBCS strings. Therefore if
substring arguments are provided on the call (either a starting position other than 1,
or an explicit length less than the string length), they operate on character
boundaries, not byte boundaries, since it is never advisable to split a DBCS character.
<p class="code">[[$Web_Cookie_Parm]]
[[$Web_Form_Parm]]
[[$Web_Hdr_Parm]]
[[$Web_Get_Cookie]]
[[$Web_Parm]]
[[$Web_Isindex_Parm]]
</p>
The following API functions return string lengths in bytes
unless using DBCS characters.
In this case, the number of characters in the
string is returned.
<p class="code">[[$Web_Cookie_Len]]
[[$Web_Form_Len]]
[[$Web_Form_Parm_Len]]
[[$Web_Hdr_Len]]
[[$Web_Hdr_Parm_Len]]
[[$Web_Len]]
[[$Web_Isindex_Len]]
[[$Web_Isindex_Parm_Len]]
[[$Web_Url_Parm_Len]]
</p>

[[Category:Janus Web Server]]

DBCS feature - Revision history

JAL2 at 21:25, 31 October 2011

JAL2: Created page with " Janus Web Server now supports use of the IBM Double Byte Character Set. This means that Janus Web Server applications can e..."

JAL2: Created page with " `Janus Web Server` now supports use of the IBM Double Byte Character Set. This means that `Janus Web Server` applications can e..."