DSXchange

Odd, the message reads

Informix data type 'INT8' for column 'a_abc_uid' is not supported in SQL statement

. That looks like a pure DML error. Can you issue this SQL in your command line?

How about CAST(o_abc_uid as Integer), what happens when you attempt that? If it doesn't work, what is the error message?

I don't see a CAST at all in your SELECT; what did you try?

Since DataStage BASIC is a programming language the answer to your question is "yes, there are ways of doing this via programming other than using one of the inbuilt functions such as ICONV(string,'MCA').". I don't know why you would wish to write your own program code to do this, though.

I don't know what could be happening here. Does your UserID or Password contain `special' characters that might be causing problems in Profilestage. The import metadata looks like it might be hitting a table permissions/authority issue.

Have you been able to connect to that DB/2 instance from the command line with the same userid and password?

Klaus,

thanks! Since this customer has a case open about this problem and the local representative has stated that the 60-second limit is hardcoded I thought that passing on the ecase number would be a good way to get the problem resolved

Tausend Dank,

Klaus Schaefer wrote:...
Yes, I've got that patch for a SOLARIS and an AIX customer, both on release 7.51A...

Klaus - would it be possible for you to check and see if you have a patch or other reference number for this? Vielen Dank!

In your SELECT use the CAST function.

I comes as part of the extras for Microsoft Office and also with access and I think it might be available as a separate download from Microsoft as well. It is a simple tool and we've used it for years to check base connectivity for ODBC. If it doesn't work in MSQUERY then don't bother trying to figu...

Can you access the DB using that DSN through MSQuery?

As Craig has already stated, I would be very careful of doing a record level copy of any VOC file, be it in a real UniVerse account or a DataStage project directory. In addition to secondary key information there is the matter of the SQL attributes for accounts, users and files/tables that are set i...

As of 8 the repository information is stored in another database. I think it will be the same as it is now - the table information and relationships are available if you know where to look, but IBM will not publish that information.

The DDL or DICTionary for hashed files is usually stored in a file called D_{HashedFileName} . In order for this dictionary to be associated with the hashed file you will need to make reference to it in the local VOC file and refer to the file using that reference. In addition, oftentimes there is n...

GET.DSNINFO should help a bit - it is trying to get the DSN and something is going wrong. Have you declared this as a SYSTEM dsn?