DSXchange

Hi,

DataStage won't know wheather the data you are going to load has NULL or Not. That's why it is giving a warning message. You can better discard that message. But if you want to get rid of that msg, as Kumar told, use Modify stage.

Hi Kumar,

Since I am adding a new line character, though we write 1 record, the output file will have 'Count' # of records for each record.

Hi, As long as you are going to write the output to a sequential file it is very simple. Assume that your field delimiter is tab and record delimiter is new line. What you have to do is create a output stage with only one field and the field value will be fld = Str(link.Name:'\t':link.Age:'\n',link....

Hi Srividhya, Still you can follow whatever tardifma's logic with a little change. create fields current_key,old_key, current_last_field and old_last_field. Even you can use your input fields instead of defining current_key and current_last_field. Now define each field like this in the same sequence...

Hi,

Instead of using Lookup stage, what you can do is, do the outer join of your main table with the lookup table and pass it to a TRANSFORMER stage. There you can have 3 outputs and you can add your constraints there.

Hi Aliso, Even if you want to do the concatenation after several steps, still u can do the hard coding in the source stage itself. In the source stage instead of concatenating there, pass that value as a separate column and at the place where you want to concatenate, there just concatenate the fields.

Hi,

As u told, I did the following things and still got the same error

1. Output to NUL.
2. Constraint 1=2
3. No TRANSFOMER stage.

In all 3 occassions, I got the same old error message after the status saying 'Step execution finish with status=OK' and startup time and run time details.

Hi Arndw,

My OS is Windows and is there any alternative for /dev/null? The reason for using TRANSFORMER stage is, my table has timestamp fields and it has NULL value also. So direct ODBC -> SEQUENTIAL gives the fixed length NULL value error.

Hi Ray, I feel that, the configuration file may not be the reason, because we are using the same config file for all our jobs. Below is my OSH code. Parallel job initiated # OSH / orchestrate script for Job EquipmentSAPFileLoad compiled at 23:38:24 07 FEB 2006 #######################################...

I am sorry ArndW. I wanted to type 'I am getting the same error message', ie main_program: Fatal Error: Caught unknown exception in main program: terminating. Contents of phantom output file => DataStage Job 63 Phantom 7246 I am getting this error message after the DS loading the data to the flat fi...

Hi Arndw, Thanks for your information. As u said, when I ran the job, it told me the error. Actually I had messed up variables. After fixing the problem, it executed. But after the job completion, I am still getting the error. In fact, the # of rows in the table were written to the file successfully...

Hi, I have not done such a comparison. But as mentioned in the help file, SWITCH stage is analogous to C switch statement. So, if ur selection is a simple if ... then .... else .... TRANSFORMER stage would be a better choice, but if u have a nested if stmt like if .... then .... else if... then ... ...

Hi, I have a job which is created for doing a simple job: create flat file from a sql server table. So, my job has odbc stage -> transformer -> sequence stage. I added the transformer stage just to change data type of some of the fields, basically from timestamp to varchar. Now, when I compile and t...

Hi Suri,

I feel if you give more details like what is the input source and is there any changes before writing to the file, etc. Then only we can help u.

Hi Madhav, There are multiple ways to do that. If you want it to write to a sequential file, you can read each record and whle writing it to a sequential file, write it with the record delimiter as 'comma(,)'. So all the records will be written to a single record. Other way is, create 2 stage variab...