DSXchange

Specifying any in sequencer will hold good i guess;

Can be like this Extract --> Nested Condition -->Transform A1 --> Transform A2 --> Seqeuncer(All) --> Load --> Transform AN In the nested condition activity, in the expression you can give the condition of country code. The above design run the jobs in parallel. If the transformation logic is same b...

Can you please specify what type of file it is. Fixed length or delimited. What is the total length of all columns? Do all the records in the file have this length. Specify all the property mentioned in format tab. Also try specifying "Number of readers per node" propery in sequential file...

in the sqlldr command you have the option of specifying where the dat, log file should be written with file name.

While specifying the file name in the option append the value of macro DSJOBSTARTTIMESTAMP. So each time new file will be created

Am not sure whether you checked this environment variable APT_TRANSFORM_COMPILE_OLD_NULL_HANDLING and replied.

If you are in 8.5 and still null is not handled by stage variable then, as IBM says Backward Compatibility Set APT_TRANSFORM_COMPILE_OLD_NULL_HANDLING=1, as a user-defined environment variable, to use the previous null handling mechanism at the project level OR Use the check box per Transformer Stag...

Your post is making me to explore more. :D
From 8.5 null is handled in stage variables.
http://www-01.ibm.com/support/docview.w ... wg21514921

reading this post will make you understand more.

stage variables dont handle null values properly in px transformer. So give it as blank. When it works, then in the column expression you can use SetNull() for blank. Just give a try. I read the entire logic i see a gap only here. Or else try this - in the stage variables property intialize the stag...

Please try the derivation as like below and check whether blank is getting populated.

In the before job subroutine use gzip or any other zip utility command and unzip the file. Then read the sequential file. You cannot read the zip file directly. If it is there, then it is a grt surprise for me.

OK from the sequencer pass the file name as paramter to a job where we have the connector stage. In the after/before sql call the update statement

update table_name set status='yes' where file_name = #pFileName#

Before we write the query, wont the file name and unique id have one to one mapping. If not, how you will find the unique id?

So one more question at what frequency this unique identifier can be reset. If it is for a run: 1) You can have a user variable activity side the loop and increment it. Guess there will be more better solution than this If it has to be unique over a period of time, you have to use a external sequenc...

You mean within in the loop you have to pass more than one parameter and that too differently?
Tell number of parameters and what are those.