Problem Note 50944: The transcode bit might be changed to YES when you join database management system (DBMS) tables with TRANSCODE=NO
When you join two DBMS tables that contain a TRANSCODE=NO field, the setting on those variables might be changed to YES in the results of the query. Incorrect data might result when the data is moved from one operating system to another.
The following examples illustrate cases of incorrect results that might occur when the TRANSCODE field has been changed:
First Example (normal character column)
- A column contains the alphanumerical value '1234567890'. This is coded in EBCDIC as 'F1F2F3F4F5F6F7F8F9F0'x.
- If the value is transferred to a Windows operating environment with TRANSCODE=YES, the value '1234567890' stays but it is now (trans)coded in LATIN9 as '31323334353637383930'x.
- If the value is transferred to a Windows system with TRANSCODE=NO, the hexadecimal value
'F1F2F3F4F5F6F7F8F9F0'x stays, which in LATIN9 now means '??????????'.
Second Example (binaryKey)
- A column contains the binary data 'B7E34C4240F1'x. This would appear as '1/4T<? 1' in a z/OS operating environment.
- If the value is transferred to Windows with TRANSCODE=YES, the binaryKey is corrupted, as SAS tries to maintain the readable string '1/4T<? 1', but changes the hexadecimal value to 'BC543CE22031'x.
- For a binaryKey, you need to set TRANSCODE=NO to maintain the hexKey and not worry about the resulting.
To work around this issue, create SAS® data sets containing the DBMS tables and do the join operation in SAS.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | Base SAS | z/OS | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.2 TS2M3 | |
Microsoft Windows Server 2003 Datacenter 64-bit Edition | 9.2 TS2M3 | |
Microsoft Windows Server 2003 Enterprise 64-bit Edition | 9.2 TS2M3 | |
Microsoft Windows XP 64-bit Edition | 9.2 TS2M3 | |
Microsoft® Windows® for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2003 Datacenter Edition | 9.2 TS2M3 | |
Microsoft Windows Server 2003 Enterprise Edition | 9.2 TS2M3 | |
Microsoft Windows Server 2003 Standard Edition | 9.2 TS2M3 | |
Microsoft Windows Server 2003 for x64 | 9.2 TS2M3 | |
Microsoft Windows Server 2008 | 9.2 TS2M3 | |
Microsoft Windows Server 2008 R2 | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows Server 2008 for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Microsoft Windows XP Professional | 9.2 TS2M3 | |
Windows 7 Enterprise 32 bit | 9.2 TS2M3 | |
Windows 7 Enterprise x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Home Premium 32 bit | 9.2 TS2M3 | |
Windows 7 Home Premium x64 | 9.2 TS2M3 | |
Windows 7 Professional 32 bit | 9.2 TS2M3 | |
Windows 7 Professional x64 | 9.2 TS2M3 | 9.4 TS1M0 |
Windows 7 Ultimate 32 bit | 9.2 TS2M3 | |
Windows 7 Ultimate x64 | 9.2 TS2M3 | |
Windows Vista | 9.2 TS2M3 | |
Windows Vista for x64 | 9.2 TS2M3 | |
64-bit Enabled AIX | 9.2 TS2M3 | 9.4 TS1M0 |
64-bit Enabled HP-UX | 9.2 TS2M3 | 9.4 TS1M0 |
64-bit Enabled Solaris | 9.2 TS2M3 | 9.4 TS1M0 |
HP-UX IPF | 9.2 TS2M3 | 9.4 TS1M0 |
Linux | 9.2 TS2M3 | 9.4 TS1M0 |
Linux for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
OpenVMS on HP Integrity | 9.2 TS2M3 | 9.4 TS1M0 |
Solaris for x64 | 9.2 TS2M3 | 9.4 TS1M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | alert |
Date Modified: | 2013-09-24 15:38:46 |
Date Created: | 2013-09-03 10:58:17 |