JANUS LOADXT: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
m (typo)
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{DISPLAYTITLE:JANUS LOADXT}}
{{DISPLAYTITLE:JANUS LOADXT}}
<span class="pageSubtitle"><section begin="desc" />Load translation table<section end="desc" /></span>
<span class="pageSubtitle">Load translation table</span>


This command specifies the name and, if necessary, the location of translate table
This command specifies the name and, if necessary, the location of translate table source code.
source code.


<var>JANUS LOADXT</var> specifies a name and location of a new or replacement Janus translate table. As described in [[Translate tables|"Translate tables"]], translate tables are used to convert received input or transmitted output on Janus connections. You can define as many different translate tables as you need for your environment.
<var>JANUS LOADXT</var> specifies a name and location of a new or replacement Janus translate table. As described in [[Translate tables]], translate tables are used to convert received input or transmitted output on Janus connections. You can define as many different translate tables as you need for your environment.


==Syntax==
==Syntax==
<p class="syntax">JANUS LOADXT tname -
<p class="syntax">JANUS LOADXT <span class="term">tname</span> {FILE | GROUP} <span class="term">fgname pname</span>
          {FILE | GROUP} fgname pname | DDNAME dname
            | DDNAME <span class="term">dname</span> | UNICODE | DEFAULT
          | UNICODE | DEFAULT
</p>
</p>


<table class="syntaxTable">
<table>
<tr><th>tname</th>
<tr><th>tname</th>
<td>The internal name given to the translate table. This name is used on the <var>XTAB</var> parameter of the <var>JANUS DEFINE</var> command to specify a translate table for a port. It is also used on <var>[[JANUS WEB ON]]</var> rules to specify a special translate table for web URLs. The name may be as long as 15 characters. An application may change translate tables using the <var>[[$WEB_SET]]</var> function.</td></tr>
<td>The internal name given to the translate table. This name is used on the <var>[[XTAB (JANUS DEFINE parameter)|XTAB]]</var> parameter of the <var>JANUS DEFINE</var> command to specify a translate table for a port. It is also used on <var>[[JANUS WEB ON]]</var> rules to specify a special translate table for web URLs. The name may be as long as 15 characters. An application may change translate tables using the <var>[[$Web_Set]]</var> function.</td></tr>
<tr><th>fgname</th>  
<tr><th>fgname</th>  
<td>The name of the <var class="product">[[Model 204]]</var> file or group.</td></tr>
<td>The name of the <var class="product">Model&nbsp;204</var> file or group.</td></tr>


<tr><th>pname</th>  
<tr><th>pname</th>  
Line 23: Line 21:


<tr><th>dname</th>
<tr><th>dname</th>
<td>Refers to a previously allocated DD name. This parameter is only valid under MVS systems.</td></tr>
<td>Refers to a previously allocated DD name. This parameter is only valid under z/OS systems.</td></tr>


<tr><th>UNICODE</th>  
<tr><th><var>UNICODE</var></th>  
<td>Loads as Janus translation table <var class="term">tname</var> a table that is identical (except as described below) to the current Janus SOAP Unicode table (which is used for parsing an XML document and for non-EBCDIC serialization of an XmlDoc). The difference between the table to be loaded and the Janus SOAP Unicode table is that, since there is no concept of &#x201C;untranslatable&#x201D; in the use of the Janus translation tables, the following translations are included:
<td>Loads, as Janus translation table <var class="term">tname</var>, a table that is identical (except as described below) to the current <var class="product">[[Janus SOAP]]</var> [[Unicode tables|Unicode table]] (which is used for parsing an XML document and for non-EBCDIC serialization of an <var>[[XmlDoc class|XmlDoc]]</var>). The difference between the table to be loaded and the Janus SOAP Unicode table is that, since there is no concept of "untranslatable" in the use of the Janus translation tables, the following translations are included:


<table class="syntaxTable">
<table>
<tr><th>ASCII to EBCDIC</th>  
<tr><td nowrap>ASCII to EBCDIC</td>  
<td>Untranslatable ASCII code points are translated to EBCDIC X'FF'.</td></tr>
<td>Untranslatable ASCII code points are translated to EBCDIC X'FF'.</td></tr>
<tr><th>EBCDIC to ASCII</th>
<td>Untranslatable EBCDIC code points are translated to ASCII X'3A', the ASCII colon character (<code>:</code>).


The Janus SOAP Unicode table translations are also used for the <var>[[AsciiToEBCDIC]]</var> and <var>[[EBCDICToAscii]]</var> Janus SOAP system intrinsic methods.
<tr><td>EBCDIC to ASCII</td>
<td>Untranslatable EBCDIC code points are translated to ASCII X'3A', the ASCII colon character (<tt>:</tt>).


To view the specific translations in effect after loading the Unicode table, you can use the UNICODE Display command to determine the codepage and view the character mappings used at your site. [[Translate tables]] contains an example of these <var>UNICODE</var> commands.
The <var class="product">Janus SOAP</var> Unicode table translations are also used for the <var>[[AsciiToEbcdic (String function)|AsciiToEbcdic]]</var> and <var>[[EbcdicToAscii (String function)|EbcdicToAscii]]</var> intrinsic functions.


The <var>UNICODE</var> parameter is available as of version 7.6 of the <var class="product">[[Sirius Mods]]</var>.
To view the specific translations in effect after loading the Unicode table, you can use the <var>[[UNICODE command#Display forms of UNICODE|UNICODE Display]]</var> command to determine the codepage and view the character mappings used at your site. [[Translate tables]] contains an example of these <var>UNICODE</var> commands. </td></tr>
</td></tr>
</table>
</table>
</td></tr>
</td></tr>


<tr><th>DEFAULT</th>
<tr><th><var>DEFAULT</var></th>


<td>Loads as Janus translation table <var class="term">tname</var> the initial default Janus translation table (named <code>STANDARD</code>) installed with the <var class="product">Sirius Mods</var>. This parameter can be used as an &#x201C;undo&#x201D; command: for example, if you had loaded the Unicode table and named it <code>STANDARD</code>:
<td>Loads, as Janus translation table <var class="term">tname</var>, the initial default Janus translation table (named <code>STANDARD</code>). This parameter can be used as an "undo" command: for example, if you had loaded the Unicode table and named it <code>STANDARD</code>:


<p class="code"> JANUS LOADXT STANDARD UNICODE</p>
<p class="code">JANUS LOADXT STANDARD UNICODE</p>


Then the following command reverts the <code>STANDARD</code> translate table to its default:
Then the following command reverts the <code>STANDARD</code> translate table to its default:


<p class="code"> JANUS LOADXT STANDARD DEFAULT</p>
<p class="code">JANUS LOADXT STANDARD DEFAULT</p>
 
The <var>DEFAULT</var> parameter is available as of version 7.6 of the <var class="product">Sirius Mods</var>.
</td></tr>
</td></tr>
</table>
</table>


You can specify existing external translate table source if you use the <var>DDNAME</var> keyword. 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 <var class="product">Model 204</var> <var>ALLOCATE</var> command to do this.
==Usage notes==
<ul>
<li>You can specify existing external translate table source if you use the <var>DDNAME</var> keyword. 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 data set and member you want to load. Use the <var class="product">Model&nbsp;204</var> <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>
<p>
Then use the <var>JANUS LOADXT</var> command to load the translate table: </p>
<p class="code">JANUS LOADXT <i>newtable</i> DDNAME IBMXTAB</p>
<p>
This <var>LOADXT</var> command reads the new translate table and converts it into an internal format. If the source contains no errors, the new translate table replaces any existing translate table that has the same internal name. </p>
<p>
Any <em>active</em> Janus connections using the same-named translate table are not affected by the <var>LOADXT</var> command. The old translate table stays in memory until the last user releases it. Any new Janus connections, however, immediately begin to use the new translate table. Therefore, it is never necessary to <var>[[JANUS DRAIN|DRAIN]]</var> or <var>[[JANUS FORCE|FORCE]]</var> a Janus port when replacing translate tables. </p></li>


Then use the <var>JANUS LOADXT</var> command to load the translate table:
<li>If <var>LOADXT</var> detects any errors with the new translate table source, the translate table is not loaded, and any existing table that has the same name remains unchanged. </li>
 
<p class="code">  JANUS LOADXT newtable DDNAME IBMXTAB</p>
 
The <var>LOADXT</var> command reads the translate table and converts it into an internal format. If the source contains no errors, the translate table replaces any old translate table with the same name. Any active Janus connections using the named translate table will not be affected by the <var>LOADXT</var> command. The old translate table stays in memory until the last user releases it. Any new Janus connections, however, will immediately begin using the new translate table. Therefore, it is never necessary to <var>[[JANUS DRAIN|DRAIN]]</var> or <var>[[JANUS FORCE|FORCE]]</var> a Janus port when replacing translate tables.
 
If <var>LOADXT</var> detects any errors with the new translate table source, the translate table will not be loaded, and any existing table with the same name will remain unchanged.


For information about coding your own translate tables, see [[Translate tables]]. For information about displaying your translate table(s), see <var>[[JANUS DISPLAYXT]]</var>.
<li>For information about coding your own translate tables, see [[Translate tables]]. For information about displaying your translate table(s), see <var>[[JANUS DISPXT]]</var>. </li>
</ul>


==See also==
<ul>
<li>[[List of Janus commands|Janus command list]]
</ul>


See: [[List_of_Janus_commands|Janus command list]]
[[Category:Janus commands|JANUS LOADXT]]
[[Category:Janus commands|JANUS LOADXT]]

Latest revision as of 20:29, 11 January 2018

Load translation table

This command specifies the name and, if necessary, the location of translate table source code.

JANUS LOADXT specifies a name and location of a new or replacement Janus translate table. As described in Translate tables, translate tables are used to convert received input or transmitted output on Janus connections. You can define as many different translate tables as you need for your environment.

Syntax

JANUS LOADXT tname {FILE | GROUP} fgname pname | DDNAME dname | UNICODE | DEFAULT

tname The internal name given to the translate table. This name is used on the XTAB parameter of the JANUS DEFINE command to specify a translate table for a port. It is also used on JANUS WEB ON rules to specify a special translate table for web URLs. The name may be as long as 15 characters. An application may change translate tables using the $Web_Set function.
fgname The name of the Model 204 file or group.
pname The name of the procedure that contains the source.
dname Refers to a previously allocated DD name. This parameter is only valid under z/OS systems.
UNICODE Loads, as Janus translation table tname, a table that is identical (except as described below) to the current Janus SOAP Unicode table (which is used for parsing an XML document and for non-EBCDIC serialization of an XmlDoc). The difference between the table to be loaded and the Janus SOAP Unicode table is that, since there is no concept of "untranslatable" in the use of the Janus translation tables, the following translations are included:
ASCII to EBCDIC Untranslatable ASCII code points are translated to EBCDIC X'FF'.
EBCDIC to ASCII Untranslatable EBCDIC code points are translated to ASCII X'3A', the ASCII colon character (:).

The Janus SOAP Unicode table translations are also used for the AsciiToEbcdic and EbcdicToAscii intrinsic functions.

To view the specific translations in effect after loading the Unicode table, you can use the UNICODE Display command to determine the codepage and view the character mappings used at your site. Translate tables contains an example of these UNICODE commands.
DEFAULT Loads, as Janus translation table tname, the initial default Janus translation table (named STANDARD). This parameter can be used as an "undo" command: for example, if you had loaded the Unicode table and named it STANDARD:

JANUS LOADXT STANDARD UNICODE

Then the following command reverts the STANDARD translate table to its default:

JANUS LOADXT STANDARD DEFAULT

Usage notes

  • You can specify existing external translate table source if you use the DDNAME keyword. 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 data set and member you want to load. Use the Model 204 ALLOCATE command to do this.

    ALLOCATE IBMXTAB WITH SCOPE=SYSTEM DSN=TCPIP.AEZAXLT1 - MEMBER=US OLD SEQUENTIAL VOLUME=OS260R

    Then use the JANUS LOADXT command to load the translate table:

    JANUS LOADXT newtable DDNAME IBMXTAB

    This LOADXT command reads the new translate table and converts it into an internal format. If the source contains no errors, the new translate table replaces any existing translate table that has the same internal name.

    Any active Janus connections using the same-named translate table are not affected by the LOADXT command. The old translate table stays in memory until the last user releases it. Any new Janus connections, however, immediately begin to use the new translate table. Therefore, it is never necessary to DRAIN or FORCE a Janus port when replacing translate tables.

  • If LOADXT detects any errors with the new translate table source, the translate table is not loaded, and any existing table that has the same name remains unchanged.
  • For information about coding your own translate tables, see Translate tables. For information about displaying your translate table(s), see JANUS DISPXT.

See also