Translate tables - Revision history

JAL: typo

2018-01-16T22:57:10Z

typo

← Older revision		Revision as of 22:57, 16 January 2018
Line 119:		Line 119:
	====Initial default STANDARD table====		====Initial default STANDARD table====
	If never modified at your site, this is the STANDARD Janus translate table pair:		If never modified at your site, this is the STANDARD Janus translate table pair:
	<p class="code"> * ASCII to EBCDIC table		<p class="code"> *
			* Translate table - STANDARD
			*
			* ASCII to EBCDIC table
	*		*
	00 01 02 03 37 2D 2E 2F 16 05 25 0B 0C 0D 0E 0F		00 01 02 03 37 2D 2E 2F 16 05 25 0B 0C 0D 0E 0F
Line 161:		Line 164:
	<li>You may want to use a Unicode table as your Janus translate table. See [[#Using the Unicode tables\|Using the Unicode tables]]. </li>		<li>You may want to use a Unicode table as your Janus translate table. See [[#Using the Unicode tables\|Using the Unicode tables]]. </li>

	<li>In the ASCII to EBCDIC table, ASCII square brackets (X'5B'/X'5D') are translated to ~~EBCDIc~~ X'AD'/X'BD', which is the same as codepage 1047. </li>		<li>In the ASCII to EBCDIC table, ASCII square brackets (X'5B'/X'5D') are translated to EBCDIC X'AD'/X'BD' (shown in bold), which is the same as codepage 1047. </li>

	<li>In the EBCDIC to ASCII table, EBCDIC X'AD'/X'BD', X'BA'/X'BB', and X'41'/X'42' are all translated to ASCII square brackets. The X'BA'/X'BB' translations are the same as codepage 0037. X'41'/X'42' are not in any codepage supported by the <var>UNICODE</var> command, but on some obsolete		<li>In the EBCDIC to ASCII table, EBCDIC X'AD'/X'BD', X'BA'/X'BB', and X'41'/X'42' are all translated to ASCII square brackets (shown in bold). The X'BA'/X'BB' translations are the same as codepage 0037. X'41'/X'42' are not in any codepage supported by the <var>UNICODE</var> command, but on some obsolete TN3270 terminals they were used for square brackets. </li>
	TN3270 terminals they were used for square brackets. </li>
	</ul>		</ul>

Line 192:		Line 194:
	For ease of editing, you might want to use the approach shown in [[JANUS DISPXT]] to copy the STANDARD table to a procedure, edit, then load the procedure with <var>JANUS LOADXT</var>.		For ease of editing, you might want to use the approach shown in [[JANUS DISPXT]] to copy the STANDARD table to a procedure, edit, then load the procedure with <var>JANUS LOADXT</var>.

	<p class="note"><b>Note:</b> Because the <code>STANDARD</code> table in the example above may already be a modified version of the STANDARD table distributed with Janus TCP/IP Base, if you definitely want to copy the distributed STANDARD table, issue the <var>USE</var> and <var>JANUS DISPXT</var> commands in a "private" Online where you are confident the table has not been modified.		<p class="note"><b>Note:</b> Because the <code>STANDARD</code> table in the example above may already be a modified version of the STANDARD table distributed with Janus TCP/IP Base, if you definitely want to copy the distributed STANDARD table, see [[#Initial default STANDARD table\|Initial default STANDARD table]] above, or issue the <var>USE</var> and <var>JANUS DISPXT</var> commands in a "private" Online where you are confident the table has not been modified. </p>

	==See also==		==See also==
Line 198:		Line 200:
	Janus topics: </p>		Janus topics: </p>
	<ul>		<ul>
	<li>[[Janus TCP/IP Base]]		<li>[[Janus TCP/IP Base]] </li>
	<li>[[Janus Web Server]]		<li>[[Janus Web Server]] </li>
	<li>[[Defining server ports]]		<li>[[Defining server ports]] </li>
	<li>[[Janus environment definition]]		<li>[[Janus environment definition]] </li>
	<li>[[Storage requirements]]		<li>[[Storage requirements]] </li>
	<li>[[Janus commands]]		<li>[[Janus commands]] </li>
	<li>[[Janus user parameters]]		<li>[[Janus user parameters]] </li>
	</ul>		</ul>

JAL: /* See also */ add descriptor

2018-01-16T22:45:17Z

JAL: revise section content; show default STANDARD translate tables

2018-01-16T22:32:13Z

revise section content; show default STANDARD translate tables

Show changes

JAL: add note: Unicode standard not same as Janus STANDARD

2018-01-12T22:38:03Z

add note: Unicode standard not same as Janus STANDARD

← Older revision		Revision as of 22:38, 12 January 2018
Line 27:		Line 27:

	<p class="code">UNICODE Display Table Standard </p>		<p class="code">UNICODE Display Table Standard </p>
			<p>
			The result of this <var>UNICODE</var> command begins with something like: </p>

	~~The result of this~~ <~~var~~>~~UNICODE</var> command begins with something like~~:		<p class="output">* The following commands produce the current Unicode translation tables:

	~~<p class="code">* The following commands produce the current Unicode~~		UNICODE Table Standard Base Codepage <i>pppp</i> </p>
	~~translation tables:~~		<p>
			where <var class="term">pppp</var> is the codepage in use.
	UNICODE Table Standard Base Codepage <i>pppp</i>
	</p>		</p>
			<p class="note"><b>Note:</b> The <code>Standard</code> keyword in the command above references the Unicode standard translation table, which is not to be confused with the initial default Janus translation table (whose name is typically shown in uppercase as "STANDARD"). </p></li>
	~~where~~ <~~var~~ class="~~term~~">~~pppp~~</~~var~~> is the ~~codepage~~ in ~~use~~. </li>

	<li>Using the above codepage, issue:		<li>Using the above codepage, issue:

JAL: merge first two sections

2018-01-12T19:48:23Z

merge first two sections

← Older revision		Revision as of 19:48, 12 January 2018
Line 1:		Line 1:
			==Background==
	Janus Connectivity products like [[Janus Web Server]] and [[Janus SOAP]] typically communicate with applications on remote computers. In many cases, these remote computers use different encodings for symbols, numerals, and letters or "characters." A character usually occupies a single byte of memory on any computer, but the character displayed for a particular bit value may vary.		Janus Connectivity products like [[Janus Web Server]] and [[Janus SOAP]] typically communicate with applications on remote computers. In many cases, these remote computers use different encodings for symbols, numerals, and letters or "characters." A character usually occupies a single byte of memory on any computer, but the character displayed for a particular bit value may vary.

	For example, in an ASCII encoding, the numeral "1" is represented by the hexadecimal value X'31'. On a computer that uses an EBCDIC encoding (IBM mainframes), the representation is X'F1'. Therefore a numeral "1" transmitted from an ASCII-based computer to an EBCDIC-based computer, or vice versa, will be misinterpreted. To avoid such misinterpretation, a method of converting a byte from one encoding to another is needed. Janus translate tables were implemented to solve this problem.		For example, in an ASCII encoding, the numeral "1" is represented by the hexadecimal value X'31'. On a computer that uses an EBCDIC encoding (IBM mainframes), the representation is X'F1'. Therefore a numeral "1" transmitted from an ASCII-based computer to an EBCDIC-based computer, or vice versa, will be misinterpreted. To avoid such misinterpretation, a method of converting a byte from one encoding to another is needed. Janus translate tables were implemented to solve this problem.

	~~==Versions and capability==~~		In early Janus versions, a fixed translate table provided the most common type of translation: that is, it converted ASCII to EBCDIC when receiving, and it converted EBCDIC to ASCII when sending. In most cases, this was adequate for the Janus products.
	In Janus ~~release 5.6 and earlier~~, a fixed translate table provided the most common type of translation: that is, it converted ASCII to EBCDIC when receiving, and it converted EBCDIC to ASCII when sending. In most cases, this is adequate for ~~any of~~ the Janus products. There are, however, many different types of EBCDIC and ASCII character sets, designed to display foreign language characters, currency, and other special symbols. To ensure these characters are transmitted and received correctly, a more flexible approach is required.

	~~In Janus 6.0~~, the translate table facility was expanded to allow simultaneous use of many different translate tables, and further, to allow user-written or customized translate tables.		However, to work with the many different types of EBCDIC and ASCII character sets, designed to display foreign language characters, currency, and other special symbols, a more flexible approach was introduced. The translate table facility was expanded to allow the simultaneous use of many different translate tables, and further, to allow user-written or customized translate tables.

	==Using translate tables==		==Using translate tables==
	To use a Janus translate table other than the ~~standard~~ table, you ~~must~~ do ~~one~~ of the following:		To use a Janus translate table other than the default table (which is named "STANDARD"), you can do any of the following:
	<ul>		<ul>
	<li>Code your own translate table source.</li>		<li>Code your own translate table source.</li>
Line 16:		Line 16:
	</ul>		</ul>

	You then use the <var>[[JANUS LOADXT]]</var> command to validate the new table, convert it to an internal format, and add ~~or replace~~ any existing table with the same name.		You then use the <var>[[JANUS LOADXT]]</var> command to validate the new table, convert it to an internal format, and name and add it (replacing any existing table with the same name).

	To use the most up-to-date Rocket-provided translation file, specify the following to load and name the Unicode table that handles Janus SOAP XML document translations:		To use the most up-to-date Rocket-provided translation file, specify the following to load and name the [[Unicode#Support for the ASCII subset of Unicode\|Unicode table]] that handles Janus SOAP XML document translations:

	<p class="code">JANUS LOADXT <i>xtabname</i> UNICODE </p>		<p class="code">JANUS LOADXT <i>xtabname</i> UNICODE </p>
Line 45:		Line 45:
	</ol>		</ol>

	To provide backward compatibility with earlier releases, two additional translate tables are loaded during Model 204 initialization. The standard table, named "STANDARD," is an exact copy of the translate table used with earlier Janus releases. This is the default translate table for all Janus ports, unless you define Web ports with DBCS support. In this case, the "JAPANIBM" translate table is used~~. Both these tables are built-in to the [[Sirius Mods]] code~~. As described in the next section, "Defining translate tables," the <var>JANUS DISPXT</var> and <var>JANUS LOADXT</var> commands let you view (or copy for modification purposes) and reload these translate tables.		To provide backward compatibility with earlier releases, two additional translate tables are loaded during Model 204 initialization. The standard table, named "STANDARD," is an exact copy of the translate table used with earlier Janus releases. This is the default translate table for all Janus ports, unless you define Web ports with DBCS support. In this case, the "JAPANIBM" translate table is used. As described in the next section, "Defining translate tables," the <var>JANUS DISPXT</var> and <var>JANUS LOADXT</var> commands let you view (or copy for modification purposes) and reload these translate tables.

	==Defining translate tables==		==Defining translate tables==
	You can define your own translate tables and load them with the <var>JANUS LOADXT</var> command. These tables can be defined in a Model 204 procedure file or group, or in a sequential file or ~~MVS~~ Partitioned Data Set		You can define your own translate tables and load them with the <var>JANUS LOADXT</var> command. These tables can be defined in a Model 204 procedure file or group, or in a sequential file or z/OS Partitioned Data Set (PDS).
	(PDS).

	A translate table must ~~define~~ a 256-byte EBCDIC-to-ASCII table, followed by a 256-byte ASCII-to-EBCDIC table. Comment lines are allowed, and they can begin with a semicolon (<tt>;</tt>) or an asterisk (<tt>*</tt>).		A translate table must include a 256-byte EBCDIC-to-ASCII table, followed by a 256-byte ASCII-to-EBCDIC table. Comment lines are allowed, and they can begin with a semicolon (<tt>;</tt>) or an asterisk (<tt>*</tt>).

	Comments are allowed on the same line as definition lines, provided they are preceded by either of the two comment characters.		Comments are allowed on the same line as definition lines, provided they are preceded by either of the two comment characters.

	You can define any number of bytes of the translate table on a single line, but it is easier to read and maintain if you define 16 bytes per line. Certain characters must be translated to their equivalent values in EBCDIC and ASCII for basic Janus functions to work correctly. Therefore, these characters are reserved for use by Janus, and they may not be translated to any other characters. These reserved characters are the following:		You can define any number of bytes of the translate table on a single line, but it is easier to read and maintain if you define 16 bytes per line.

			Certain characters must be translated to their equivalent values in EBCDIC and ASCII for basic Janus functions to work correctly. Therefore, these characters are reserved for use by Janus, and they may not be translated to any other characters. These reserved characters are the following:

	<p class="code"> 0-9		<p class="code"> 0-9
Line 81:		Line 82:
	</p>		</p>

	<var>JANUS LOADXT</var> ~~will validate~~ any table it attempts to load, and if these characters are not preserved when translating to ASCII and back, the table ~~will~~ not be loaded.		<var>JANUS LOADXT</var> validates any table it attempts to load, and if these characters are not preserved when translating to ASCII and back, the table is not loaded.

	Each character in the translate table is coded in hexadecimal format and must be two bytes long. Each two-byte hexadecimal string must be separated by one or more blanks.		Each character in the translate table is coded in hexadecimal format and must be two bytes long. Each two-byte hexadecimal string must be separated by one or more blanks.
Line 92:		Line 93:
	; ASCII-to-EBCDIC table for English (US) CECP Code Page 037		; ASCII-to-EBCDIC table for English (US) CECP Code Page 037
	; <b>00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F</b>		; <b>00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F</b>
	;		;
	00 01 02 03 37 2D 2E 2F 16 05 25 0B 0C 0D 0E 0F ; <b>00</b> ;		00 01 02 03 37 2D 2E 2F 16 05 25 0B 0C 0D 0E 0F ; <b>00</b> ;
	10 11 12 13 3C 3D 32 26 18 19 3F 27 1C 1D 1E 1F ; <b>10</b> ;		10 11 12 13 3C 3D 32 26 18 19 3F 27 1C 1D 1E 1F ; <b>10</b> ;

JAL: misc formatting

2018-01-09T23:33:20Z

misc formatting

Show changes

JAL: /* Defining translate tables */ misc formatting

2018-01-09T16:28:40Z

Defining translate tables: misc formatting

← Older revision		Revision as of 16:28, 9 January 2018
Line 54:		Line 54:

	==Defining translate tables==		==Defining translate tables==
			You can define your own translate tables and load them with the <var>[[JANUS LOADXT]]</var> command. These tables can be defined in a Model 204 procedure file or group, or in a sequential file or MVS Partitioned Data Set
	You can define your own translate tables and load them with the JANUS LOADXT command ~~(“JANUS LOADXT” on page 139)~~. These tables can be defined in a Model 204 procedure file or group, or in a sequential file or MVS Partitioned Data Set
	(PDS).		(PDS).

	A translate table must define a 256-byte EBCDIC-to-ASCII table, followed by a 256-byte ASCII-to-EBCDIC table. Comment lines are allowed and can begin with a semicolon (;) or an asterisk (*).		A translate table must define a 256-byte EBCDIC-to-ASCII table, followed by a 256-byte ASCII-to-EBCDIC table. Comment lines are allowed and can begin with a semicolon (<tt>;</tt>) or an asterisk (<tt>*</tt>).

	Comments are allowed on the same line as definition lines, provided they are preceded by either of the two comment characters.		Comments are allowed on the same line as definition lines, provided they are preceded by either of the two comment characters.
Line 88:		Line 87:
	</p>		</p>

	[[JANUS LOADXT]] will validate any table it attempts to load, and if these characters are not preserved when translating to ASCII and back, the table will not be loaded.		<var>JANUS LOADXT</var> will validate any table it attempts to load, and if these characters are not preserved when translating to ASCII and back, the table will not be loaded.

	Each character in the translate table is coded in hexadecimal format and must be two bytes long. Each two-byte hexadecimal string must be separated by one or more blanks.		Each character in the translate table is coded in hexadecimal format and must be two bytes long. Each two-byte hexadecimal string must be separated by one or more blanks.
Line 120:		Line 119:
	You can specify existing external translate table source when loading translate tables.		You can specify existing external translate table source when loading translate tables.

	For example, IBM supplies many translate tables with its TCP/IP product under MVS. You can use these tables directly with JANUS LOADXT. To use these tables, you must first allocate the dataset and member you want to load. Use the Model 204 ALLOCATE command to do this:		For example, IBM supplies many translate tables with its TCP/IP product under MVS. You can use these tables directly with <var>JANUS LOADXT</var>. To use these tables, you must first allocate the dataset and member you want to load. Use the Model 204 <var>ALLOCATE</var> command to do this:

	<p class="code"> ALLOCATE IBMXTAB WITH SCOPE=SYSTEM DSN=TCPIP.AEZAXLT1 -		<p class="code">ALLOCATE IBMXTAB WITH SCOPE=SYSTEM DSN=TCPIP.AEZAXLT1 -
	MEMBER=US OLD SEQUENTIAL VOLUME=OS260R		MEMBER=US OLD SEQUENTIAL VOLUME=OS260R
	</p>		</p>

	Then use the JANUS LOADXT command to load the translate table:		Then use the <var>JANUS LOADXT</var> command to load the translate table:

	<p class="code"> JANUS LOADXT name DDNAME IBMXTAB</p>		<p class="code">JANUS LOADXT <i>name</i> DDNAME IBMXTAB</p>

	You can obtain source copies of any previously loaded translate table (including internal tables) by using the JANUS DISPXT command and the Model 204 USE command. For example, to obtain a copy of the current translate table ~~“STANDARD~~,” issue the following commands:		You can obtain source copies of any previously loaded translate table (including internal tables) by using the <var>JANUS DISPXT</var> command and the Model 204 <var>USE</var> command. For example, to obtain a copy of the current translate table "STANDARD," issue the following commands:

	<p class="code"> USE ddname		<p class="code">USE <i>ddname</i>
	JANUS DISPXT STANDARD		JANUS DISPXT STANDARD </p>
	</p>

	You can then modify the source and reload the table using the [[JANUS LOADXT]] command.		You can then modify the source and reload the table using the <var>JANUS LOADXT</var> command.

	Note: Because the STANDARD table in the example above may already be a modified version of the STANDARD table distributed with Janus TCP/IP Base, if you definitely want to copy the distributed STANDARD table, issue the USE and [[JANUS DISPXT]] commands in a ~~“private”~~ Online where you are confident the table has not been modified.		<p class="note"><b>Note:</b> Because the <code>STANDARD</code> table in the example above may already be a modified version of the STANDARD table distributed with Janus TCP/IP Base, if you definitely want to copy the distributed STANDARD table, issue the <var>USE</var> and <var>JANUS DISPXT</var> commands in a "private" Online where you are confident the table has not been modified.

	==See also==		==See also==

JAL: /* References */

2013-04-29T01:11:50Z

References

← Older revision		Revision as of 01:11, 29 April 2013
Line 140:		Line 140:
	Note: Because the STANDARD table in the example above may already be a modified version of the STANDARD table distributed with Janus TCP/IP Base, if you definitely want to copy the distributed STANDARD table, issue the USE and [[JANUS DISPXT]] commands in a “private” Online where you are confident the table has not been modified.		Note: Because the STANDARD table in the example above may already be a modified version of the STANDARD table distributed with Janus TCP/IP Base, if you definitely want to copy the distributed STANDARD table, issue the USE and [[JANUS DISPXT]] commands in a “private” Online where you are confident the table has not been modified.

	==~~References~~==		==See also==
			<ul>
	~~See:~~ [[~~List_of_Janus_commands\|~~Janus ~~command list~~]], [[JANUS LOADXT]], [[JANUS DISPXT]]		<li>[[Janus TCP/IP Base]]
			<li>[[Janus Web Server]]
			<li>[[Defining server ports]]
			<li>[[Janus environment definition]]
			<li>[[Storage requirements]]
			<li>[[Janus commands]]
			<li>[[Janus user parameters]]
			<li>[[JANUS LOADXT]], [[JANUS DISPXT]]
			</ul>

	[[Category:Janus Web Server\|Translate tables]]		[[Category:Janus Web Server\|Translate tables]]
	[[Category:Janus commands\|Translate tables]]		[[Category:Janus commands\|Translate tables]]
	[[Category:Janus TCP/IP Base]]		[[Category:Janus TCP/IP Base]]

Dme at 14:13, 27 March 2013

2013-03-27T14:13:09Z

← Older revision		Revision as of 14:13, 27 March 2013
Line 138:		Line 138:
	You can then modify the source and reload the table using the [[JANUS LOADXT]] command.		You can then modify the source and reload the table using the [[JANUS LOADXT]] command.

	Note: Because the STANDARD table in the example above may already be a modified version of the STANDARD table distributed with Janus TCP/IP Base, if you definitely want to copy the distributed STANDARD table, issue the USE and [[JANUS ~~DISPLAYXT~~]] commands in a “private” Online where you are confident the table has not been modified.		Note: Because the STANDARD table in the example above may already be a modified version of the STANDARD table distributed with Janus TCP/IP Base, if you definitely want to copy the distributed STANDARD table, issue the USE and [[JANUS DISPXT]] commands in a “private” Online where you are confident the table has not been modified.

	==References==		==References==

	See: [[List_of_Janus_commands\|Janus command list]], [[JANUS LOADXT]], [[JANUS ~~DISPLAYXT~~]]		See: [[List_of_Janus_commands\|Janus command list]], [[JANUS LOADXT]], [[JANUS DISPXT]]

	[[Category:Janus Web Server\|Translate tables]]		[[Category:Janus Web Server\|Translate tables]]
	[[Category:Janus commands\|Translate tables]]		[[Category:Janus commands\|Translate tables]]
	[[Category:Janus TCP/IP Base]]		[[Category:Janus TCP/IP Base]]

Admin at 20:28, 9 March 2011

2011-03-09T20:28:42Z

← Older revision		Revision as of 20:28, 9 March 2011
Line 146:		Line 146:
	[[Category:Janus Web Server\|Translate tables]]		[[Category:Janus Web Server\|Translate tables]]
	[[Category:Janus commands\|Translate tables]]		[[Category:Janus commands\|Translate tables]]
			[[Category:Janus TCP/IP Base]]

← Older revision		Revision as of 22:45, 16 January 2018
Line 195:		Line 195:

	==See also==		==See also==
			<p>
			Janus topics: </p>
	<ul>		<ul>
	<li>[[Janus TCP/IP Base]]		<li>[[Janus TCP/IP Base]]
Line 203:		Line 205:
	<li>[[Janus commands]]		<li>[[Janus commands]]
	<li>[[Janus user parameters]]		<li>[[Janus user parameters]]
	~~<li>[[JANUS LOADXT]], [[JANUS DISPXT]]~~
	</ul>		</ul>