JANUS LOADXT: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
mNo edit summary |
||
| Line 25: | Line 25: | ||
<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 MVS 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 <var class="product">[[Janus SOAP]]</var> 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: | <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 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 | <table> | ||
<tr>< | <tr><td>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>< | |||
<td>Untranslatable EBCDIC code points are translated to ASCII X'3A', the ASCII colon character (< | <tr><td>EBCDIC to ASCII</td> | ||
<td>Untranslatable EBCDIC code points are translated to ASCII X'3A', the ASCII colon character (<tt>:</tt>). | |||
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 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. | ||
| Line 43: | Line 44: | ||
</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 “undo” 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>) installed with the <var class="product">Sirius Mods</var>. 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"> | <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"> | <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>. | The <var>DEFAULT</var> parameter is available as of version 7.6 of the <var class="product">Sirius Mods</var>. | ||
| Line 57: | Line 58: | ||
</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 dataset and member you want to load. Use the <var class="product">Model 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 | |||
</p> | </p> | ||
Then use the <var>JANUS LOADXT</var> command to load the translate table: | Then use the <var>JANUS LOADXT</var> command to load the translate table: | ||
<p class="code"> | <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. | 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. | <li>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. | ||
<li>For information about coding your own translate tables, see [[Translate tables|"Translate tables"]]. For information about displaying your translate table(s), see <var>[[JANUS DISPXT]]</var>. | |||
</ul> | |||
==See also== | |||
<ul> | |||
<li>[[List_of_Janus_commands|Janus command list]] | |||
</ul> | |||
[[Category:Janus commands|JANUS LOADXT]] | [[Category:Janus commands|JANUS LOADXT]] | ||
Revision as of 18:11, 16 April 2013
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 MVS 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:
| ||||
| DEFAULT | Loads as Janus translation table tname the initial default Janus translation table (named STANDARD) installed with the Sirius Mods. 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 JANUS LOADXT STANDARD DEFAULT The DEFAULT parameter is available as of version 7.6 of the Sirius Mods. |
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 dataset 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
The LOADXT 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 LOADXT 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 DRAIN or FORCE a Janus port when replacing translate tables.
- If LOADXT 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 JANUS DISPXT.