Problem:

At times a custom character translation may be needed when transferring files to and from a Mainframe host.

Resolution:

To modify the translation table for file transfer:

1. In the Rumba mainframe display, choose Transfer > Configure
2. On the file transfer configuration dialog, click on the Advanced tab.
3. In the character set section, click Write to file.
4. When prompted for a file name, enter a name (such as MyXfer.dat) and click Save.
5. The character set will now show up in the list box as User Defined - MyXfer.dat. Click OK to close the dialog.
6. In Windows Explorer, locate the file you saved in step 4. It is typically saved in C:\\Documents and Settings\\username\\My Documents\\NetManage\\Rumba\\CodePage\\.
7. Open the file in Notepad. It should look similar in format to the following:

   # Column 1 : Ascii/Ansi (PC) Code
   # Column 2 : Matching EBCDIC (host) code
   # Column 3 : EBCDIC Code
   # Column 4 : Matching Ascii/Ansi Code
   # US    037    437
   # ASCII->EBCDIC        EBCDIC->ASCII
         00 00                 00 00
         01 01                 01 01
         02 02                 02 02
         03 03                 03 03
         04 37                 04 EC
         05 2D                 05 09
         06 2E                 06 CA
         07 2F                 07 7F
         08 16                 08 E2
         09 05                 09 D2
         0A 25                 0A D3
   ...

8. Make the desired changes to the file. The first two columns of hexadecimal numbers define the translation from ASCII to EBCDIC (uploads) and the second two define the translation from EBCDIC to ASCII (downloads). To change the translation for a specific character, find that character in the appropriate column, and change the hexadecimal value of its associated character to that desired. For example, to change the upload translation for the ASCII value 0xA0:
   
   1. Find the appropriate line in the translation .dat file:

            A0 45                 A0 E6

   2. Since the change is being made to the upload translation, you would modify the first (ASCII->EBCDIC) column. In this case, the table is changed so that ASCII A0 (hex) is translated to EBCDIC 46 (hex) when this character is encountered during a file upload:

            A0 46                 A0 E6

   3. The same logic can be applied to the download translation by modifying the second (EBCDIC->ASCII) column of the file. For example:

            46 C6                 46 A0

9. Once you have completed the modifications to the translation file, return to the Rumba Mainframe display and save your session. In the future, all file transfers invoked in this session will use the new custom translation table.