DSXchange

Darn, next time maybe

It can but it wont be pretty. What i can think of is read the record as a single column, count the number of tabs using count() or dcount() and depending upon that concatenate the remaining tabs. Write it out as a single column again.

Run a shell on the file. Which checks for the number of tabs, if less than 10, then it will fill in the missing ones. It would be simple if the missing columns are towards the end. If they are in between then more manipulation is required.

Is that all that your doing, or is that the final step of your shell. If yes then instead of Print 1, do return 1.

Not everything will be outlined. In DataStage there are more ways than one to achieve a task. Are they all good ? No, Are they all supported? maybe not. Telnet execution might not be able to react to the return code, but before/after job subroutine does. So can a routine. Some functions have some ca...

When the error happens again, reset the job, some more log entries will be producted. They will be 'from the previous run' entries that Craig was referring to.

Granted. This will take more work than just a simple use of multiple pivot stages as the number of fields that are comma delimited are unknown. Pivot stage would have worked if the comma delimited columns (3, 4 and 5) were static. You need something like awk. Here is what i came up with. This script...

Do it at the OS level. Do a


Now you have that name in a file. Read it in your job and load it in the table. You can run this command in the before job subroutine 'ExecSH'

The sample input, is that your source. If it is then the output that you have shown is do-able as Ken suggested. It has been done time and again here. Search for it.

You will be able to find implented code here if you search, of exactly what Ken is saying.

Well, if DataStage is used properly then it wouldnt frustrate you. I have been using DS for doing different things, from awk scripts to calling ftp scripts, from file size checking on windoze box to using c routines. Its been good to me. You could create a routine and execute the shell via DSExecute...

I highly doubt you can do that, but will be happy to be proven wrong. A schema file just stores the schema and not the file properties.

I have no clue buddy. There is no return code either. Change the design, get it to execute in the before job subroutine. Atleast you can get a return code there inside the log to look at next time the script fails.

Seqential file stage's properties, go to options, you will see an option "First Line Is Column Name". Set that to True or False accordingly.

That message doesnt tell much. What is this stage "XFR_BRAND_LKP "? Reset the job, it will show up some more messages, post them here, they might tell us more.