APAR status
Closed as program error.
Error description
RCP is enabled, and columns are not defined, client character set is LATIN1_0A, character columns in the DDL for the table are defined as LATIN, data is loaded into a new dataset. They are expecting the character data in the schema for the created dataset to be set to 'string' but they are coming out as 'ustring' If so, is there a way we can disable this? Env. variable?
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users running jobs with TD-Connector and using "char" datatypes. **************************************************************** PROBLEM DESCRIPTION: char" data types are being read into "ustring" schema and not "string" schema. **************************************************************** RECOMMENDATION: Install the patch. This fix is included in Information Server 81 Fix Pack 1. ****************************************************************
Problem conclusion
Fixed the issue, as part of a Stage Property: "Describe Strings In Bytes", which when set to yes, reads "char" types into "string" schema.
Temporary fix
Comments
APAR Information
APAR number
JR31576
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
801
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-12-30
Closed date
2009-01-13
Last modified date
2009-12-22
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R801 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
22 December 2009