JANUS LOADXT: Difference between revisions

From m204wiki
Jump to navigation Jump to search
mNo edit summary
Line 23: Line 23:


<tr><th>dname</th>
<tr><th>dname</th>
<td>Refers to a previously allocated DD name, if preceded by the keyword <var>DDNAME</var>. 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>UNICODE</th>  

Revision as of 22:28, 7 December 2011

<section begin="desc" />Load translation table<section end="desc" />

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:
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 Janus SOAP system intrinsic methods.

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.

The UNICODE parameter is available as of version 7.6 of the Sirius Mods.

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 STANDARD translate table to its default:

JANUS LOADXT STANDARD DEFAULT

The DEFAULT parameter is available as of version 7.6 of the Sirius Mods.

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 DISPLAYXT.


See: Janus command list