DSXchange

Lance,

tried that as well. I am going to ask the DBAs to give me a view of the table using CHAR to see if that will work, but it will take a day or three to get that done on the mainframe.

I have a VARCHAR(1020) column which contains normal text plus embedded double-quote characters. When I load this into the Oracle enterprise stage using the bulk loader I get the job aborting because the Oracle data file doesn't expand/change the double quote characters but uses double-quotes as it's...

snassimr & Ray, I really had qualms about responding to this question; doing anything directly to the VOC is always dangerous (I've had my bad experiences over the years) and combining a SELECT with a DELETE.FILE was just asking for trouble. I'm glad that snassimr's next post wasn't titled "How ...

snassimr, I am not at a UniVerse enabled system now, but I think you can do a 'SELECT VOC WITH @ID LIKE ...TMP... AND WITH F1 LIKE F...' and subsequently do a DELETE.FILE on that select list. You can try the SELECT and do a subsequent 'LIST VOC' to see what you have seelected. The query and delete a...

The syntax in the Job Control code should read:



You do not need to specify the # hash marks in Job Control code to use parameters, and the quotes you used are also extraneous.

Happy coding...

hiltsmi, the hashed file mechanism can handle many concurrent reads and writes to files, just as any database system does. If one process READs a record that might have been updated by another process (or job), then you need to ensure is that all of your WRITEs and READs are done right off the hashe...

Ray,

just before leaving I found another table which gave the same error - and this one was using DB/2 VarChar(100), once I removed that column the table was readable. I have to find out about VarChar in DB/2 and the wire connect protocol to the host, perhaps I have missed something fundamental.

Vinay, if NLS is telling you that there are unmappable characters then chances are very high you do not have Shift-JIS incoming. Sometimes companies will use Gaiji characters which are not mappable as they are custom characters, but this is rarely used. How certain are you that you Japanese Kanji ar...

I don't have access to a test machine right now, but I would take the first day of the next month (using a substring function) and then converting it to Julian and subtracting 1, finally converting it back to timestamp.

I should have added you can call the job using {YourJobName}.{Instance}, so you just have to modify your scheduler's command line to include a differing instance.

How about using the system time as the invocation ID, or some other value.

What about your .odbc.ini and project uvodbc.config files?

I am trying to read a table which contains a column declared as VARCHAR(1000) in DB/2. When I remove the column everything works flawlessly. When I try to read the table or even do a view-data on it it aborts with Error executing View Data command: ##E TDOD 000001 14:44:34(000) <main_program> Dataty...

In that case your user session and the [background] DataStage job have different access. Try to put a DSLogInfo or DSExecute or other debugging statement in your job where you try to access this drive. I think that is where you are having issues.

Is this to a reject link? In that case I don't think you can make the warning disappear; you could put a transform stage between the database stage and your sequential output file, that should work.