Search found 15603 matches
- Fri Oct 21, 2005 1:59 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: exit code 157
- Replies: 5
- Views: 2358
Rafidwh, I didn't see you mention anything about reading a flat file in this post, but later on I saw the error message that you were unable to view a flat file. Do as Ray suggested and see if the permissions are correct. Go into a UNIX shell and see if you can do a cat of the file with the same use...
- Fri Oct 21, 2005 1:55 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DS Basic to handle file
- Replies: 11
- Views: 2940
Kirtikumar, when changing a sequential file, it is better to create a copy than to edit the original. After the new file is written you can delete the original and rename the new file if you wish. Here is some code that will do what you want, add error handling to your taste and since I just typed i...
- Fri Oct 21, 2005 1:43 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: exit code 157
- Replies: 5
- Views: 2358
Hello Rafidfwh, it is a bit like me saying "When I turn my car engine on there is a red light. What is my problem"? No quite as bad in your case. Is the execution of a job causing this or something else? What does your job do (read or write to/from a database, and if so, which one and how, use any s...
- Fri Oct 21, 2005 1:39 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: DataStage scheduling issues
- Replies: 6
- Views: 1362
Venu, when you say your jobs "hang", do you mean that they start and have a status of "running" in the DataStage Director? I can see no reason why a job would behave differently because of the time it was scheduled. On UNIX when you schedule jobs to run from the Director they will be put into the de...
- Thu Oct 20, 2005 11:50 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: File Writing Limitations
- Replies: 2
- Views: 877
Hemant, you haven't confronted any file writing limitations in DataStage routines in this case. When you OPENSEQ a sequential file the file pointer is positioned at the beginning of the file. If you start writing to the file then you are going to overwrite your data and then truncate it when you clo...
- Thu Oct 20, 2005 11:39 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Time and TimeStamp with microseconds
- Replies: 20
- Views: 10190
- Thu Oct 20, 2005 10:58 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: 10 pounds in a 5 pound bag
- Replies: 28
- Views: 5576
- Thu Oct 20, 2005 9:50 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: 10 pounds in a 5 pound bag
- Replies: 28
- Views: 5576
Craig, the answer comes as a 32-bit digit, so the displayed value is going to chew up a lot of spaces, what I meant is that this can be compressed into 4 bytes using a MBOC conversion. I have a routine here somewhere that does that {it also makes sure that no @FM is in the string, so that it can be ...
- Thu Oct 20, 2005 6:55 am
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: Time and TimeStamp with microseconds
- Replies: 20
- Views: 10190
Madhusv, this is a different problem altogether. Your error is (I think) occurring when doing a view-data or an import of metadata. I assume that you are getting other data types loaded in correctly? Remember that an oracle timestamp is different from a DB/2 timestamp. Please post your response in a...
- Thu Oct 20, 2005 4:59 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Installation of DS 7.5.1A
- Replies: 4
- Views: 1029
Rajeev, the restrictions on Windows are only regarding the Parallel Extender package and have nothing to do with operations of Server. You have posted your question in the Server forum so you should not have to worry about limited functionality when installing. PX, on the other hand, will have limit...
- Thu Oct 20, 2005 4:55 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: How do I specify TAB delimited files
- Replies: 7
- Views: 3401
(1) This is not a FAQ, please post it in the correct forum (2) Nothing in this forum is urgent; at least not to anybody but the poster. Urgent and critical issues need to be raised with your support provider, they are paid to respond to problems like this. The forum is a loose agglomeration of volun...
- Thu Oct 20, 2005 4:52 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: 10 pounds in a 5 pound bag
- Replies: 28
- Views: 5576
Srinagesh, actually, that is a really good solution. I was so concentrated on the string 'compression' function that the (now obvious) table-based solution that you have come up with completely escaped me. With th lookup file you could use a shorter key as well - just start with 1 and work upwards f...
- Thu Oct 20, 2005 1:45 am
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: 10 pounds in a 5 pound bag
- Replies: 28
- Views: 5576
Craig, the job ran through without a collision on all permutations of a 10-character string using CRC32. I just realized that this is not guarantee that it won't get a duplicate on a 9 or 11 length string - but the chances of a collision using 12 CRC32'd number on a 200 character string string are s...
- Wed Oct 19, 2005 1:50 pm
- Forum: IBM<sup>®</sup> DataStage Enterprise Edition (Formerly Parallel Extender/PX)
- Topic: understanding SQL*Loader ctl file in OE stage...
- Replies: 10
- Views: 2365
Prabu, If I want to force inserts and not use the bulk load process, I will choose the options 'update then insert' or 'insert then update' and afterwards choose 'custom sql' for both; then I'll cut-and-paste one to the other, so that both actually do the update or insert. But if you only have inser...
- Wed Oct 19, 2005 1:16 pm
- Forum: IBM<sup>®</sup> Infosphere DataStage Server Edition
- Topic: Handling ^M
- Replies: 17
- Views: 3774