> For the complete documentation index, see [llms.txt](https://docs.editran.onesait.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/interfaz-generica-de-aplicacion/anexo-f.-tablas-traduccion-y-conversion.md). # Appendix F. Tables (translation and conversion) Depending on the installed version or the version installed on the remote side, different translation tables are applied. The first endpoint to translate is the one that determines the table to be used. There are different cases: * If the translating endpoint is CICS or IMS and has version 5.0 phase 2 or later, or if the translating endpoint is any other environment and has version 5.0 phase 0 or later, a translation table based on Codepage 1145 EBCDIC Spanish and ASCII ISO 8859 Latin-1 is applied. > The EBCDIC to ASCII translation (between Codepage 1145 EBCDIC Spanish and ASCII ISO 8859 Latin-1) is as follows (bold example, EBCDIC character x’FA’ is transformed into ASCII character x’B3’): > > ``` > | x0| x1| x2| x3| x4| x5| x6| x7| x8| x9| xA| xB| xC| xD| xE| xF| > 0x|x00|x01|x02|x03|x9C|x09|x86|x7F|x97|x8D|x8E|x0B|x0C|x0D|x0E|x0F| > 1x|x10|x11|x12|x13|x9D|x85|x08|x87|x18|x19|x92|x8F|x1C|x1D|x1E|x1F| > 2x|x80|x81|x82|x83|x84|x0A|x17|x1B|x88|x89|x8A|x8B|x8C|x05|x06|x07| > 3x|x90|x91|x16|x93|x94|x95|x96|x04|x98|x99|x9A|x9B|x14|x15|x9E|x1A| > 4x|x20|xA0|xE2|xE4|xE0|xE1|xE3|xE5|xE7|xA6|x5B|x2E|x3C|x28|x2B|x7C| > 5x|x26|xE9|xEA|xEB|xE8|xED|xEE|xEF|xEC|xDF|x5D|x24|x2A|x29|x3B|xAC| > 6x|x2D|x2F|xC2|xC4|xC0|xC1|xC3|xC5|xC7|x23|xF1|x2C|x25|x5F|x3E|x3F| > 7x|xF8|xC9|xCA|xCB|xC8|xCD|xCE|xCF|xCC|x60|x3A|xD1|x40|x27|x3D|x22| > 8x|xD8|x61|x62|x63|x64|x65|x66|x67|x68|x69|xAB|xBB|xF0|xFD|xFE|xB1| > 9x|xB0|x6A|x6B|x6C|x6D|x6E|x6F|x70|x71|x72|xAA|xBA|xE6|xB8|xC6|xA4| > Ax|xB5|xA8|x73|x74|x75|x76|x77|x78|x79|x7A|xA1|xBF|xD0|xDD|xDE|xAE| > Bx|xA2|xA3|xA5|xB7|xA9|xA7|xB6|xBC|xBD|xBE|x5E|x21|xAF|x7E|xB4|xD7| > Cx|x7B|x41|x42|x43|x44|x45|x46|x47|x48|x49|xAD|xF4|xF6|xF2|xF3|xF5| > Dx|x7D|x4A|x4B|x4C|x4D|x4E|x4F|x50|x51|x52|xB9|xFB|xFC|xF9|xFA|xFF| > Ex|x5C|xF7|x53|x54|x55|x56|x57|x58|x59|x5A|xB2|xD4|xD6|xD2|xD3|xD5| > Fx|x30|x31|x32|x33|x34|x35|x36|x37|x38|x39|xB3|xDB|xDC|xD9|xDA|x9F| > ``` > > The ASCII to EBCDIC translation (between ASCII ISO 8859 Latin-1 and Codepage 1145 EBCDIC Spanish) is as follows (bold example, ASCII character x’BE’ is transformed into EBCDIC character x’FA’): > > ``` > | x0| x1| x2| x3| x4| x5| x6| x7| x8| x9| xA| xB| xC| xD| xE| xF| > 0x|x00|x01|x02|x03|x37|x2D|x2E|x2F|x16|x05|x25|x0B|x0C|x0D|x0E|x0F| > 1x|x10|x11|x12|x13|x3C|x3D|x32|x26|x18|x19|x3F|x27|x1C|x1D|x1E|x1F| > 2x|x40|xBB|x7F|x69|x5B|x6C|x50|x7D|x4D|x5D|x5C|x4E|x6B|x60|x4B|x61| > 3x|xF0|xF1|xF2|xF3|xF4|xF5|xF6|xF7|xF8|xF9|x7A|x5E|x4C|x7E|x6E|x6F| > 4x|x7C|xC1|xC2|xC3|xC4|xC5|xC6|xC7|xC8|xC9|xD1|xD2|xD3|xD4|xD5|xD6| > 5x|xD7|xD8|xD9|xE2|xE3|xE4|xE5|xE6|xE7|xE8|xE9|x4A|xE0|x5A|xBA|x6D| > 6x|x79|x81|x82|x83|x84|x85|x86|x87|x88|x89|x91|x92|x93|x94|x95|x96| > 7x|x97|x98|x99|xA2|xA3|xA4|xA5|xA6|xA7|xA8|xA9|xC0|x4F|xD0|xBD|x07| > 8x|x20|x21|x22|x23|x24|x15|x06|x17|x28|x29|x2A|x2B|x2C|x09|x0A|x1B| > 9x|x30|x31|x1A|x33|x34|x35|x36|x08|x38|x39|x3A|x3B|x04|x14|x3E|xFF| > Ax|x41|xAA|xB0|xB1|x9F|xB2|x49|xB5|xA1|xB4|x9A|x8A|x5F|xCA|xAF|xBC| > Bx|x90|x8F|xEA|xFA|xBE|xA0|xB6|xB3|x9D|xDA|x9B|x8B|xB7|xB8|xB9|xAB| > Cx|x64|x65|x62|x66|x63|x67|x9E|x68|x74|x71|x72|x73|x78|x75|x76|x77| > Dx|xAC|x7B|xED|xEE|xEB|xEF|xEC|xBF|x80|xFD|xFE|xFB|xFC|xAD|xAE|x59| > Ex|x44|x45|x42|x46|x43|x47|x9C|x48|x54|x51|x52|x53|x58|x55|x56|x57| > Fx|x8C|x6A|xCD|xCE|xCB|xCF|xCC|xE1|x70|xDD|xDE|xDB|xDC|x8D|x8E|xDF| > ``` * If the translating endpoint has a version lower than 4.0 phase 4, in some cases an obsolete and non-symmetric translation table was applied. Those cases were: * Which translated in Editran without Editran compression * Which translated in Editran with Editran compression and with remote-iga-version < 3.1 * That Editran/MQ is used * In all other cases (the most common situation in all entities), an obsolete translation table (from MS-DOS) was applied. In the case of EBCDIC to ASCII (x’FA’ for x’FC’, it is different from the previous table, in this and other characters) > ``` > x00-x00 x10-x10 x20-xC0 x30-xCC x40-x20 x50-x26 x60-x2D x70-x9B > x01-x01 x11-x11 x21-xC1 x31-xCD x41-xFE x51-x82 x61-x2F x71-x90 > x02-x02 x12-x12 x22-xC2 x32-x16 x42-x83 x52-x88 x62-xB6 x72-xD2 > x03-x03 x13-x13 x23-xC3 x33-xCE x43-x84 x53-x89 x63-x8E x73-xD3 > x04-x9F x14-xB9 x24-xC4 x34-xD5 x44-x85 x54-x8A x64-xB7 x74-xD4 > x05-x09 x15-xBA x25-x0A x35-xD9 x45-xA0 x55-xA1 x65-xB5 x75-xD6 > x06-xB0 x16-x08 x26-x17 x36-xDA x46-xC6 x56-x8C x66-xC7 x76-xD7 > x07-x7F x17-xBB x27-x1B x37-x04 x47-x86 x57-x8B x67-x8F x77-xD8 > x08-xB1 x18-x18 x28-xC5 x38-xDB x48-x87 x58-x8D x68-x80 x78-xDE > x09-xB2 x19-x19 x29-xC8 x39-xDC x49-x7C x59-xE1 x69-x23 x79-x60 > x0A-xB4 x1A-xBC x2A-xC9 x3A-xDD x4A-x5B x5A-x5D x6A-xA4 x7A-x3A > x0B-x0B x1B-xBF x2B-xCA x3B-xDF x4B-x2E x5B-x24 x6B-x2C x7B-xA5 > x0C-x0C x1C-x1C x2C-xCB x3C-x14 x4C-x3C x5C-x2A x6C-x25 x7C-x40 > x0D-x0D x1D-x1D x2D-x05 x3D-x15 x4D-x28 x5D-x29 x6D-x5F x7D-x27 > x0E-x0E x1E-x1E x2E-x06 x3E-xF2 x4E-x2B x5E-x3B x6E-x3E x7E-x3D > x0F-x0F x1F-x1F x2F-x07 x3F-x1A x4F-xB3 x5F-xAA x6F-x3F x7F-x22 > x80-x9D x90-xF8 xA0-xE6 xB0-xBD xC0-x7B xD0-x7D xE0-x5C xF0-x30 > x81-x61 x91-x6A xA1-xF9 xB1-x9C xC1-x41 xD1-x4A xE1-xF6 xF1-x31 > x82-x62 x92-x6B xA2-x73 xB2-xBE xC2-x42 xD2-x4B xE2-x53 xF2-x32 > x83-x63 x93-x6C xA3-x74 xB3-xFA xC3-x43 xD3-x4C xE3-x54 xF3-x33 > x84-x64 x94-x6D xA4-x75 xB4-xB8 xC4-x44 xD4-x4D xE4-x55 xF4-x34 > x85-x65 x95-x6E xA5-x76 xB5-xF5 xC5-x45 xD5-x4E xE5-x56 xF5-x35 > x86-x66 x96-x6F xA6-x77 xB6-xF4 xC6-x46 xD6-x4F xE6-x57 xF6-x36 > x87-x67 x97-x70 xA7-x78 xB7-xAC xC7-x47 xD7-x50 xE7-x58 xF7-x37 > x88-x68 x98-x71 xA8-x79 xB8-xAB xC8-x48 xD8-x51 xE8-x59 xF8-x38 > x89-x69 x99-x72 xA9-x7A xB9-xF3 xC9-x49 xD9-x52 xE9-x5A xF9-x39 > x8A-xAE x9A-xA6 xAA-xAD xBA-x5E xCA-xF0 xDA-xFB xEA-xFD xFA-xFC > x8B-xAF x9B-xA7 xAB-xA8 xBB-x21 xCB-x93 xDB-x96 xEB-xE2 xFB-xEA > x8C-xD0 x9C-x91 xAC-xD1 xBC-xEE xCC-x94 xDC-x81 xEC-x99 xFC-x9A > x8D-xEC x9D-xF7 xAD-xED xBD-x7E xCD-x95 xDD-x97 xED-xE3 xFD-xEB > x8E-xE7 x9E-x92 xAE-xE8 xBE-xEF xCE-xA2 xDE-xA3 xEE-xE0 xFE-xE9 > x8F-xF1 x9F-xCF xAF-xA9 xBF-x9E xCF-xE4 xDF-x98 xEF-xE5 xFF-xFF > ``` > > In the case of ASCII to EBCDIC (x’FC’ for x’FA’) > > ``` > x00-x00 x10-x10 x20-x40 x30-xF0 x40-x7C x50-xD7 x60-x79 x70-x97 > x01-x01 x11-x11 x21-xBB x31-xF1 x41-xC1 x51-xD8 x61-x81 x71-x98 > x02-x02 x12-x12 x22-x7F x32-xF2 x42-xC2 x52-xD9 x62-x82 x72-x99 > x03-x03 x13-x13 x23-x69 x33-xF3 x43-xC3 x53-xE2 x63-x83 x73-xA2 > x04-x37 x14-x3C x24-x5B x34-xF4 x44-xC4 x54-xE3 x64-x84 x74-xA3 > x05-x2D x15-x3D x25-x6C x35-xF5 x45-xC5 x55-xE4 x65-x85 x75-xA4 > x06-x2E x16-x32 x26-x50 x36-xF6 x46-xC6 x56-xE5 x66-x86 x76-xA5 > x07-x2F x17-x26 x27-x7D x37-xF7 x47-xC7 x57-xE6 x67-x87 x77-xA6 > x08-x16 x18-x18 x28-x4D x38-xF8 x48-xC8 x58-xE7 x68-x88 x78-xA7 > x09-x05 x19-x19 x29-x5D x39-xF9 x49-xC9 x59-xE8 x69-x89 x79-xA8 > x0A-x25 x1A-x3F x2A-x5C x3A-x7A x4A-xD1 x5A-xE9 x6A-x91 x7A-xA9 > x0B-x0B x1B-x27 x2B-x4E x3B-x5E x4B-xD2 x5B-x4A x6B-x92 x7B-xC0 > x0C-x0C x1C-x1C x2C-x6B x3C-x4C x4C-xD3 x5C-xE0 x6C-x93 x7C-x49 > x0D-x0D x1D-x1D x2D-x60 x3D-x7E x4D-xD4 x5D-x5A x6D-x94 x7D-xD0 > x0E-x0E x1E-x1E x2E-x4B x3E-x6E x4E-xD5 x5E-xBA x6E-x95 x7E-xBD > x0F-x0F x1F-x1F x2F-x61 x3F-x6F x4F-xD6 x5F-x6D x6F-x96 x7F-x07 > x80-x68 x90-x71 xA0-x45 xB0-x06 xC0-x20 xD0-x8C xE0-xEE xF0-xCA > x81-xDC x91-x9C xA1-x55 xB1-x08 xC1-x21 xD1-xAC xE1-x59 xF1-x8F > x82-x51 x92-x9E xA2-xCE xB2-x09 xC2-x22 xD2-x72 xE2-xEB xF2-x3E > x83-x42 x93-xCB xA3-xDE xB3-x4F xC3-x23 xD3-x73 xE3-xED xF3-xB9 > x84-x43 x94-xCC xA4-x6A xB4-x0A xC4-x24 xD4-x74 xE4-xCF xF4-xB6 > x85-x44 x95-xCD xA5-x7B xB5-x65 xC5-x28 xD5-x34 xE5-xEF xF5-xB5 > x86-x47 x96-xDB xA6-x9A xB6-x62 xC6-x46 xD6-x75 xE6-xA0 xF6-xE1 > x87-x48 x97-xDD xA7-x9B xB7-x64 xC7-x66 xD7-x76 xE7-x8E xF7-x9D > x88-x52 x98-xDF xA8-xAB xB8-xB4 xC8-x29 xD8-x77 xE8-xAE xF8-x90 > x89-x53 x99-xEC xA9-xAF xB9-x14 xC9-x2A xD9-x35 xE9-xFE xF9-xA1 > x8A-x54 x9A-xFC xAA-x5F xBA-x15 xCA-x2B xDA-x36 xEA-xFB xFA-xB3 > x8B-x57 x9B-x70 xAB-xB8 xBB-x17 xCB-x2C xDB-x38 xEB-xFD xFB-xDA > x8C-x56 x9C-xB1 xAC-xB7 xBC-x1A xCC-x30 xDC-x39 xEC-x8D xFC-xFA > x8D-x58 x9D-x80 xAD-xAA xBD-xB0 xCD-x31 xDD-x3A xED-xAD xFD-xEA > x8E-x63 x9E-xBF xAE-x8A xBE-xB2 xCE-x33 xDE-x78 xEE-xBC xFE-x41 > x8F-x67 x9F-x04 xAF-x8B xBF-x1B xCF-x9F xDF-x3B xEF-xBE xFF-xFF > ``` All the translation tables used have the same translation in uppercase and lowercase without accents (except Ñ, ñ). In the case of accented characters or special symbols, the translations change. In principle, the new 5.0 (or 5.0.2) translation tables are "modern" tables that make applications correctly understand letters (accented and unaccented), numbers, and symbols. Normally, any problems that existed up to this version are solved with the same: * On outgoing transfers, if the remote side is ASCII, it can translate on send (in that case, the modern table will be applied, regardless of the product version installed on that remote side). * On incoming transfers, if the remote side is ASCII and has a product version installed lower than 5.0, you can tell it not to translate (Editran profile of the ASCII environment) and do it yourself during the download on z/OS (in that way the modern table will be applied and not the obsolete one from the ASCII environment) In any case, if the translation table does not work for you, you can apply the conversion table yourself (on send or receive), or the remote side can apply it too. In those cases, what is done is to adapt the outgoing or incoming characters to the expected characters. Ideally, the conversion table should be applied on receive (once the translation has been done, if there is one). In the Editran profiles (presentation session), send conversion tables or receive conversion tables can be included. In this case, an 8-position table name is specified. How and when are they applied?: 1. In the case of outgoing transfers. The conversion table is applied before translation (if this field was also marked). In this case, the load program: * If the original alphabet of the data is EBCDIC, it looks for a 9-position table, whose name is the combination of the 8-position name specified in the profile and the letter "E" or "F". * In the case where the sender has version 5.0.2 or later installed, it looks for the letter "F" * In the case where the sender has an earlier version installed, it looks for the letter "E" * If the original alphabet of the data is ASCII, it looks for a 9-position table, whose name is the combination of the 8-position name specified in the profile and the letter "A" or "B". * In the case where the sender has version 5.0.2 or later installed, it looks for the letter "B" * In the case where the sender has an earlier version installed, it looks for the letter "A" 2. In the case of incoming transfers (the receiving endpoint, a priori, does not know what the sending endpoint did with the translation). * If the receiving endpoint has version 5.0.2 or later installed. It verifies the product version (not the one in its profile, but the one the remote side actually has in the CSB header). * If the remote side has version > 4.1 installed * If the CSB header says the data arrives in EBCDIC and in the presentation session profile the RECEIVE TRANSLATE parameter has values "E" or "N" (in both cases, it does not translate on download). In this case, if there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "F". * If the CSB header says the data arrives in EBCDIC and in the presentation session profile the RECEIVE TRANSLATE parameter has value "A" (ASCII), it translates using the new table specified for the version it has (5.0.2). Once the translation is done, if there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "B". * If the CSB header says the data arrives in ASCII and in the presentation session profile the RECEIVE TRANSLATE parameter has values "A" or "N" (in both cases, it does not translate on download). In this case, if there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "B". * If the CSB header says the data arrives in ASCII and in the presentation session profile the RECEIVE TRANSLATE parameter has value "E" (EBCDIC), it translates using the new table specified for the version it has (5.0.2). Once the translation is done, if there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "F". * If the remote side has version lower than 5.0 installed * If the CSB header says the data arrives in EBCDIC and in the presentation session profile the RECEIVE TRANSLATE parameter has values "E" or "N" (in both cases, it does not translate on download). In this case, if there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "E". * If the CSB header says the data arrives in EBCDIC and in the presentation session profile the RECEIVE TRANSLATE parameter has value "A" (ASCII), it translates using the new table specified for the version it has (5.0.2). Once the translation is done, if there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "B". * If the CSB header says the data arrives in ASCII and in the presentation session profile the RECEIVE TRANSLATE parameter has values "A" or "N" (in both cases, it does not translate on download). In this case, if there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "A". * If the CSB header says the data arrives in ASCII and in the presentation session profile the RECEIVE TRANSLATE parameter has value "E" (EBCDIC), it translates using the new table specified for the version it has (5.0.2). Once the translation is done, if there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "F". * If the receiving endpoint has a version lower than 5.0.2 installed, when it downloads, once it has translated (or not), translate or not: * If the alphabet of the data downloaded at that moment is EBCDIC, and there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "E". * If the alphabet of the data downloaded at that moment is ASCII, and there is a receive conversion table in the presentation profile, it looks for a 9-position table whose name is the combination of the 8-position name specified in the profile and the letter "A". Conclusions about the conversion tables (if you have installed version > 5.0.1) * Outgoing transfers * If there is translation, apply the conversion table(s) ending in F or B (new) * If there is no translation, apply the conversion table(s) ending in E or A (old) * Incoming transfers * If translation is applied on receive, or if local v.iga (that of the sending endpoint) in cab.csb is > 4.1, the conversion table(s) ending in B or F (new) will be applied * If no translation is applied and local v.iga (that of the sending endpoint) in CAB cabo is < 5.0, old conversion tables are applied. Conversion tables are generated from a JCL and a program that creates a specific table: ```cobol //KI0F6AEA JOB (EGDC,KIT,,99),MODP.42-43,MSGCLASS=H,CLASS=A, // MSGLEVEL=1,NOTIFY=&SYSUID //********************************************************************* //** EDITRAN/G (CICS - MVS ENVIRONMENT) //** EDITRAN/G CONVERSION TABLE GENERATION-LISTING JCL //********************************************************************+ //ZTBGBTCO EXEC PGM=ZTBGBTCO,COND=(0,NE) //STEPLIB DD DSN=KI.EIDC.ZTBG.LOAD,DISP=SHR // DD DSN=KI.EGDC.ZTBP.LOAD31,DISP=SHR //ZTBGFTCO DD DSN=KI.PMED.CZTB.ZTBGFTCO,DISP=SHR //* DCB=(RECFM=FB,LRECL=265,BLKSIZE=0), //* DISP=(NEW,CATLG,DELETE), //* SPACE=(TRK,(10,10),RLSE) //ZTBGFLIS DD SYSOUT=*,DEST=H,DCB=(BLKSIZE=132) //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //******************************************************************* //* SHEET 01: FF-XXXXXXXXY WHERE: //* F=FUNCTION (00-SAVE, 01-LIST, 02-REWRITE) //* X=8-POSITION CONVERSION TABLE NAME (EDITRAN/G PROFILE) //* Y=TYPE OF CONVERSION (A,B,E,F) //* A=ASCII < 5.0 //* OUTGOING..: APPLIED WHEN TRAD-EMI=N //* INCOMING: APPLIED WHEN TRAD-REC=N AND V.IGA.REM<50 //* B=ASCII > 5.0 //* OUTGOING..: APPLIED WHEN TRAD-EMI=S //* INCOMING: APPLIED WHEN TRAD-REC=S OR V.IGA.REM>41 //* E=EBCDIC < 5.0 //* OUTGOING..: APPLIED WHEN TRAD-EMI=N //* INCOMING: APPLIED WHEN TRAD-REC=N AND V.IGA.REM<50 //* F=EBCDIC > 5.0 //* OUTGOING..: APPLIED WHEN TRAD-EMI=S //* INCOMING: APPLIED WHEN TRAD-REC=S OR V.IGA.REM>41 //* OTHER SHEETS: (FROM 1 TO 256 SHEETS) //* HEXADECIMAL VALUE (00-FF) = NEW HEXA VALUE (00-FF) //* (IF BOTH MATCH, THERE IS NO NEED TO SPECIFY THEM) //******************************************************************* //FICHAS DD * //FICHAS DD * FF-XXXXXXXXY 00=04 01=F4 ... ``` The program from the previous JCL will read the sheet records and in the first record it will find the function (00-save, 01-list, 02-rewrite), the profile conversion table name (XXXXXXXX), and a letter (A/B or E/F), indicating whether it is an ASCII or EBCDIC conversion table. If the function is 01, it will list the contents of the specified table. If the function is 00, it will then find the original hexadecimal value and the hexadecimal value to which it will be converted (if both are the same, there is no need to enter them), so that in the end it will save a table with all the values (256 values) with the key specified in the ZTBGFTCO file and a report will be generated with the result of the table contents. If the function is 02, it will rewrite the new characters indicated and will keep the characters modified in previous writes. The listing that appears with any option is the following: ``` CONVERSION TABLE NAME : TABCVXNCA OBJECT : CONTAINS VALUES : ASCII --------------------------------------------------------------------------------------------------- | ORIGINAL | CONVERTED || ORIGINAL | CONVERTED || ORIGINAL | CONVERTED || ORIGINAL | CONVERTED| --------------------------------------------------------------------------------------------------- | X'21' = X'32' || X'23' = X'A5' || X'5E' = X'AA' || X'7C' = X'A4' | --------------------------------------------------------------------------------------------------- | X'80' = X'C0' || X'81' = X'C1' || X'82' = X'C2' || X'83' = X'C3' | --------------------------------------------------------------------------------------------------- | X'84' = X'C4' || X'85' = X'BA' || X'86' = X'B0' || X'87' = X'BB' | --------------------------------------------------------------------------------------------------- ``` and so on until the changing hexadecimal characters are completed. To avoid problems, the following scheme is proposed: * Usually, the conversion table is applied by the receiver. * Usually, the translation is applied by the receiver. Since in versions lower than 5.0.2 only conversion tables ending in 'A' or 'E' could be created, version 5.0.2 provides: * Software to create tables ending in 'B' or 'F' * Migration programs, which, based on the conversion tables ALREADY CREATED by the user ending in 'A' and 'E', create new conversion tables ending in 'B' or 'F' to avoid, as far as possible, having to recreate them. If the migration program detects that applying a conversion table is not necessary (because the new translation solves the problem, it removes it from the presentation session) Usage example: You have installed Editran 5.0.2 and want to send, but you know that the Ñ character in your EBCDIC in hexadecimal appears to you as an x’7B’. The endpoint you are sending to is an ASCII that understands Ñ as a hexadecimal that it interprets as x’2B’. There are several solutions to this problem: * If translation is done on send, the new translation table is applied, so EBCDIC x’7B’ would be translated to ASCII x’D1’. The remote side would not receive its expected x’2B’. In this case there are several solutions: * On send, you could include a send conversion table ending in F, which would change value x’7B’ to value x’4E’. The subsequent send translation would translate x’4E’ to x’2B’, which is the value the remote side expected. * On send, do not include a send conversion table. In this case, the remote side receives an x’D1’. On that download: * If the receiver has a version installed < 5.0, it could include a receive conversion table ending in 'A', which would change x’D1’ to x’2B’, which is the value the remote side expected. * If the receiver has a version installed > 4.1, it could include a receive conversion table ending in 'B', which would change x’D1’ to x’2B’, which is the value the remote side expected. * If translation is not done on send: * If the remote side has a version higher than 4.1 installed. * The sender can include a send conversion table ending in 'F' that changes x’7B’ to x’4E’. The receiver applies the translation and would translate x’4E’ to x’2B’, which is the value the remote side expected. * The receiver applies translation x’7B’ to x’D1’ and then applies a conversion table ending in 'B' that changes x’D1’ to x’2B’, which is the value the remote side expected. * If the remote side has version lower than 5.0 installed * The sender can include a send conversion table ending in 'E' that changes x’7B’ to x’4E’. The receiver applies the OLD translation and would translate x’4E’ to x’2B’, which is the value the remote side expected. * The receiver applies translation x’7B’ to x’A5’ with its old translation table and then applies a conversion table ending in 'A' that changes x’A5’ to x’2B’, which is the value the remote side expected. Differences between the old and new translation tables (EBCDIC to ASCII): **EBCDIC characters that change from the old table to the new one.**
EBCDICAsc-oldAsc-newEBCDICAsc-oldAsc-newEBCDICAsc-oldAsc-newEBCDICAsc-oldAsc-new
x04x9Fx9Cx43x84xE4x77xD8xCFxB8xABxBD
x06xB0x86x44x85xE0x78xDExCCxB9xF3xBE
x08xB1x97x45xA0xE1x7BxA5xD1xBCxEExAF
x09xB2x8Dx46xC6xE3x80x9DxD8xBExEFxB4
x0AxB4x8Ex47x86xE5x8AxAExABxBFx9ExD7
x14xB9x9Dx48x87xE7x8BxAFxBBxCAxF0xAD
x15xBAx85x49x7CxA6x8CxD0xF0xCBx93xF4
x17xBBx87x4FxB3x7Cx8DxECxFDxCCx94xF6
x1AxBCx92x51x82xE9x8ExE7xFExCDx95xF2
x1BxBFx8Fx52x88xEAx8FxF1xB1xCExA2xF3
x20xC0x80x53x89xEBx90xF8xB0xCFxE4xF5
x21xC1x81x54x8AxE8x9AxA6xAAxDAxFBxB9
x22xC2x82x55xA1xEDx9BxA7xBAxDBx96xFB
x23xC3x83x56x8CxEEx9Cx91xE6xDCx81xFC
x24xC4x84x57x8BxEFx9DxF7xB8xDDx97xF9
x28xC5x88x58x8DxECx9Ex92xC6xDExA3xFA
x29xC8x89x59xE1xDFx9FxCFxA4xDFx98xFF
x2AxC9x8Ax5FxAAxACxA0xE6xB5xE1xF6xF7
x2BxCAx8Bx62xB6xC2xA1xF9xA8xEAxFDxB2
x2CxCBx8Cx63x8ExC4xAAxADxA1xEBxE2xD4
x30xCCx90x64xB7xC0xABxA8xBFxECx99xD6
x31xCDx91x65xB5xC1xACxD1xD0xEDxE3xD2
x33xCEx93x66xC7xC3xADxEDxDDxEExE0xD3
x34xD5x94x67x8FxC5xAExE8xDExEFxE5xD5
x35xD9x95x68x80xC7xAFxA9xAExFAxFCxB3
x36xDAx96x6AxA4xF1xB0xBDxA2xFBxEAxDB
x38xDBx98x70x9BxF8xB1x9CxA3xFCx9AxDC
x39xDCx99x71x90xC9xB2xBExA5xFDxEBxD9
x3AxDDx9Ax72xD2xCAxB3xFAxB7xFExE9xDA
x3BxDFx9Bx73xD3xCBxB4xB8xA9xFFxFFx9F
x3ExF2x9Ex74xD4xC8xB5xF5xA7
x41xFExA0x75xD6xCDxB6xF4xB6
x42x83xE2x76xD7xCExB7xACxBC
Differences between the old and new translation tables (ascii to EBCDIC). **ASCII characters that change from the old table to the new one.**
ASCIIEbc-oldEbc-newASCIIEbc-oldEbc-newASCIIEbc-oldEbc-newASCIIEbc-oldEbc-new
x7Cx49x4FxA0x45x41xC1x21x65xE2xEBx42
x80x68x20xA1x55xAAxC2x22x62xE3xEDx46
x81xDCx21xA2xCExB0xC3x23x66xE4xCFx43
x82x51x22xA3xDExB1xC4x24x63xE5xEFx47
x83x42x23xA4x6Ax9FxC5x28x67xE6xA0x9C
x84x43x24xA5x7BxB2xC6x46x9ExE7x8Ex48
x85x44x15xA6x9Ax49xC7x66x68xE8xAEx54
x86x47x06xA7x9BxB5xC8x29x74xE9xFEx51
x87x48x17xA8xABxA1xC9x2Ax71xEAxFBx52
x88x52x28xA9xAFxB4xCAx2Bx72xEBxFDx53
x89x53x29xAAx5Fx9AxCBx2Cx73xECx8Dx58
x8Ax54x2AxABxB8x8AxCCx30x78xEDxADx55
x8Bx57x2BxACxB7x5FxCDx31x75xEExBCx56
x8Cx56x2CxADxAAxCAxCEx33x76xEFxBEx57
x8Dx58x09xAEx8AxAFxCFx9Fx77xF0xCAx8C
x8Ex63x0AxAFx8BxBCxD0x8CxACxF1x8Fx6A
x8Fx67x1BxB0x06x90xD1xACx7BxF2x3ExCD
x90x71x30xB1x08x8FxD2x72xEDxF3xB9xCE
x91x9Cx31xB2x09xEAxD3x73xEExF4xB6xCB
x92x9Ex1AxB3x4FxFAxD4x74xEBxF5xB5xCF
x93xCBx33xB4x0AxBExD5x34xEFxF6xE1xCC
x94xCCx34xB5x65xA0xD6x75xECxF7x9DxE1
x95xCDx35xB6x62xB6xD7x76xBFxF8x90x70
x96xDBx36xB7x64xB3xD8x77x80xF9xA1xDD
x97xDDx08xB8xB4x9DxD9x35xFDxFAxB3xDE
x98xDFx38xB9x14xDAxDAx36xFExFBxDAxDB
x99xECx39xBAx15x9BxDBx38xFBxFCxFAxDC
x9AxFCx3AxBBx17x8BxDCx39xFCxFDxEAx8D
x9Bx70x3BxBCx1AxB7xDDx3AxADxFEx41x8E
x9CxB1x04xBDxB0xB8xDEx78xAExFFxFFxDF
x9Dx80x14xBExB2xB9xDFx3Bx59
x9ExBFx3ExBFx1BxABxE0xEEx44
x9Fx04xFFxC0x20x64xE1x59x45
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.editran.onesait.com/documentacion-editran/ibm-editran-v5.3-comun-z-os-en/interfaz-generica-de-aplicacion/anexo-f.-tablas-traduccion-y-conversion.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.