DSXchange

As DSGuru has mentioned - you can use it in the Job control.

BASIC routines cannot be called from a Parallel Transformer, but only from a BASIC transformer.

Like ServerJobs is there ny property to set "Missing columns action"? rumu You can set the Reject Mode option inside the Sequential File stage to "Output" to capture all records that have a mismatch in the defined metadata, in a reject link. If you set this property to "Con...

You have not mentioned your problem. How are you trying to combine your records? Are you getting errors - if so what are they? Provide more details so that someone can help you better.

In a Parallel Transformer, only a C/C++ routine can be used.

If you need to use a BASIC routine - you will have to pull in the BASIC transformer instead of the Parallel one. You can also use these in the After/Before job subroutines, as well as in the Routine Activity in the Job Sequence.

Why not try replace the IsNull()/IsNotNull() with a NullToEmpty like this - If (i/p_column1 = "A" AND trim(NullToEmpty(ip_column2))<>"") Then ip_column2[1,7] ELSE SetNull() Or if you want to use to IFs (not adviced) - If i/p_column1 = "A" Then (If trim(NullToEmpty(ip_co...

but my best guess would be that even if you use an external sort stage, then PX might combine the operators at run time if you are doing nothing else. So in that case, it would be better NOT to use the external sort stage. But as i said, i might be wrong in my understanding, so please confirm it. A...

@OUTROWNUM would not work as in the Server edition, as in Parallel jobs it will get executed on each of the nodes. So if you set a constraint - @OUTROWNUM <= 50000 - each of the nodes would send you 50000 records each. System Variables (like @OUTROWNUM) can only be used in a Transformer stage. These...

Sreenivasulu wrote: You can use the removeduplicate stage in parallel version (if the project architecture allows this)

Removal of duplicates is not the requirement here!

sshettar wrote: but here the problem is that the hash file is removing duplicate records of that key column which i dont want it to happen .

bcoz you want pass rest of values in the file except for one column i need to pass the column name. Since your source is a single file, why not use a UNIX command (perhaps CUT) in an External Source stage to read everything except for the First column and then pass downstream. You can make this omm...

If you need to pass the number of rows as the parameter, then the best bet will be to build a Custom Stage using the Abort operator.

I haven't really used it in a live job, but have played with it quite successfully.

Aneesh

Since UtilityAbortToLog is written as a transform function, it can not be used in parallel jobs unless a BASIC Transformer stage is used...

Aneesh

chalasaniamith wrote:bcoz you want pass rest of values in the file except for one column i need to pass the column name.so i dont think it will work.

Yeah, then I guess you will have to work as Ray has hinted...

chalasaniamith wrote:thats true we have to give default value to the parameter.Otherwise it wont be compiled.And if we gave default value its not going to work.

You cannot type in anything other than numbers in the tab for the Abort After Rows. So there is no way you can pass a parameter to this.

If you dont pass the parameter does the job abort? that what your saying right? If you want the job to abort after encountering 5 rows that does not satisfy the constraint - then you would have to hard code 5 in the Abort After Rows option. What I meant is that you cannot pass 5 as a parameter to t...

yes thats true i want to pass the column name from table definition.. Is the table definiton for the file saved in the repository? In which case why dont you hardcode the column name in a Column generator and generate an additional column before sending it to the transformer? Since your requirement...