DSXchange

You cannot write NULL values into Sequential File. You need to set NullFieldValue = '' in the Sequential file stage format tab.

The permanent solution is to increase your column length.

again re-generate it from starting

That won't help you maintaining the integrity among the tables.

The Answer depends. Are you storing the deposit and withdrawal information in the same table? If yes, there should another column that should be part of the key on that table that defines if the transaction(record) is a deposit or withdrawal. You should not be creating different Surrogate Keys for t...

How many Sequential File Stages do you have in your job? Are you trying to read other files with different wild cards or names in the same job? I have seen this happen when there were multiple Sequential file stages within the same job and one of the file was not present in the directory the job was...

That's an odd requirement. How you read the file should not matter as long as you are processing all the records required. Ray's suggestion to read the file in a single field and using a Transformer Stage should work fine.

You can either split your jobs to use less number of stages or update your configuration file to point to a resource where there is enough space.

Does it happen in jobs with Join Stage or LookUp Stages? I saw the same error in the past when I was getting Cartesian products out of a join Stage due to bad data. The process ended up using all the space defined within the config file and ran out of space and eventually aborted. What is the volume...

What is the error you are getting? There is no one particular solution to get rid of all the errors you are facing. Providing sample errors you are facing will help us help us.

You can
1. Define an output link where the constraint is defined as Field 1 <> Field2
2. Instead of the reject link, use a regular output link and check the Otherwise/Log Option.

Sreenivasulu wrote:Pls do not use SMS style dotted statementes.

And you just used one

The trigger conditions allow you to design/define what you want after the execution of the shell script (Execute Command Activity) or other prior Job Activities in the Job Sequence. You can go through the help to understand what each of the options within the drop down box of the trigger tab means.

In that case have you considered placing a copy stage before the CDC stage and reroute those two columns into a separate link and then join it with the output of CDC?

The simplest is writing the If Then Else with the output values that are related to less number of input columns.

abc123 wrote: 3)Make All non-key columns Value Keys.

You need to select Explicit Keys and Explicit Values and specifically mention the columns you want to do the compare on.

The Execute Command stages start based upon the input trigger they have from the Job Activity Stage. Have you set this to "Unconditional"? Hope the program will also invoke all exec command activities on corresponding success of their job activities even when JA7 failed at some point of ti...