DSXchange

If i remember correctly, You could cascade Multiple XML stages also Something like this: <Cust> <Name> </Name> <AddressList> <Address> Address1 </Address> </AddressList> <PhoneList> <Phone> Phone1 </Phone> </PhoneList> </Cust> external source stage -----> xml stage1---(Get Name/AddressChunk) -----> ...

Well,

you don't "Have" to write routines... Just proper use of the transformer (Stage variables and the "if... then... else..." statement in the derivations) can get what you want.

screenshots would be difficult!!!! I havent worked with BAPI's a lot though i believe a BAPI returns a status code back to the calling program. This can be written to a file using the BAPI stage. Cant help you much there. However for IDoc stages, there are 2 types of issues that may come up : :arrow...

Have you considered removing the aggregator completely.

The hashed file will automatically give you the last written row (for a given key)

So, as long as you hashed file key is PolID, the aggregator may safely be ejected from your job.

Should improve performance too
IHTH.

I think the problem is to do with:
Trim will not take kindly to a null value as input

try this:

the SAP R/3 pack can do the following: 1. Extract/load data from/to SAP R/3 using IDOC's 2. Extract/load data from/to SAP R/3 using BAPI Calls 3. Given a Logical DB SQL Statement (Built via provided GUI in the stage), generates an ABAP program that extracts data from SAP using CPIC or Write to file....

Sumit, From what i understand of your issue: You are attempting to do an inner join between 2 tables in datastage via the Join Stage. The expectation is that the join should only extract rows that qualify( i.e. where invmst.sku# = invbal .sku# and invbal .store# = 250) from the INVMST stage. However...

Assumption Made: exactly 3 fields in file. first field is empno, last field is deptno and everything else in the middle is the salary. Possible Solution: Read the entire row in as one column: Col1 In a transformer, map 3 columns EMP<--Field(DSLink2.Col1,",",1,1) Sal<--Field(DSLink2.Col1,&q...

warning!!!! I have no TX experience but...


The command "Hostname" is supported in both Unix and WinXP (Therefore should be supported in WinServ2003).

That should give you only and exactly what you need.. if i understand the requirement right.

Server solution that will scale to any number of sub-columns: Source----->Transformer----->SeqFile----->Output IN the transformer, have 2 output columns Firstkey<--- In.key Data---< ereplace(in.DelimCol,"|",char(10):in.key:",") In the seqfile input link, set the following format:...

Dunno if this adds any value to the discussion but there is an option in the sequential file stage that's titled:

"Clean up on Failure" which is defaulted to true.

Setting it to false may give you some data in the file.

Change in metadata should not trigger re-partitioning; once done, logically speaking, only explicit repartitioning and (this section may be incorrect) stage-driven auto re-partitioning can change the partitioned data.

ray.wurlod wrote:Or, indeed, in an External Source stage. ...

Whoops!!! Typo!!!

Thanks Ray.. thats what I meant to say!!!

In an External Command Stage, use the following Source program:
replace <FilePath+Name> and <Delimiter> with the appropriate text.

HTH.

Here is the Job Paramter #FromClause# = prdtbl where #$LoadType# =1 Here is how the SQL looks when we use SQL generated option SELECT ABC FROM #FromClause# Assuming you call the job from a sequence, add a uservariable activity before the job activity stage and create one uservariable "FromClau...