DSXchange

In a sequence job, I have "Automatically handle activities that fail" enabled and a generic exception handler that calls a routine to log a message and generate an email. One of the steps is an Execute Command activity. This shell command returns 0 on success, 1 if it didn't find the file ...

India2000 wrote:no they aren't ..I'm seperating out header nd details..reading them ..

As long as each record has a record type field, you can handle different record types and multiple files using the file pattern option in the Complex Flat File stage.

eostic wrote:I see nothing natural in that xml that would produce the output that you say you are expecting.

I agree with Ernie. The XML does not look right. Can you post the XSD?

Yes, there are other threads on this, I have read most / all of them and didn't really come up with a conclusive answer. I am experiencing a different pattern to those other threads. Job A creates about 10 data sets that job B uses for further processing. A sequence has a loop to run A and B multipl...

... or maybe just my lack of understanding. My frustration centres around the warning IIS-DSEE-TFIP-00063 "When checking operator: Dropping component "..." because of a prior component with same name." I first ran into grief with this on a DIFF stage. The diff stage requires colu...

Oops ... seem to be answering my own questions again. A colleague has found an option to omit null elements on the format page of the XML composer which seems to work. (Why it also needs to format the XML to do this I don't know.)

If the source is a database, then I'd make the input match the database specification which probably means varchar and nullable. The way I see it, you have 2 choices, but they relate to how you output the data. You sequential file stage has built in capability to handle nulls. You can use this. Alte...

In the current web service interface I am building, and in the next one I have to build, it seems to be universal that base level elements are defined with: nillable="true" minOccurs="0" Group elements typically have nillable="true" This is where the problem arises. We ...

OK, I have figured out what is going on. Because the XSD includes nillable="true", then when I supply null, the element is still produced but includes xsi:nil="true". If I remove nillable="true" from the XSD, then the element disappears from the XML. DataStage is doing ...

...it's the default behavior. If the field is null (using xmlOutput or 8.5 xml), the element simply does not appear.... you can optionally force it to blanks if you want, and can have blanks treat ... I would like this to be the case, but it is not my experience so far with the 8.5 XML stage. I hav...

madhavamaganti wrote:Sequential_File_0,0: Input buffer overrun at field "Sale_Date", at offset: 0.

Your input record is shorter than the definition of the record in your metadata.

SURA wrote:DATEADD. This function will returns a new datetime value based on adding an interval to the specified date.

Is there is any function can we use in Datastage to achive the same task?

Have a look at TimestampOffsetByComponents

To check for file existence, set the timeout to zero. Yes, I was doing that, but a time out still causes a warning to be logged. No file is a perfectly acceptable result for me so I'd prefer not to have the warning. I'm now using a Unix if command and it is working fine. Still had to resort to a fu...

Thanks Ray.

Yeah, I'm starting to think that I'll skip the WFF activity altogether. I really just want to know of the file is there or not, so I think I'll use a Unix command instead.

I've been having problems with a Wait For File activity going to the exception handler rather than the links indicated by triggers. After playing around with different options and examining the generated code, it is my belief that a Wait For File Activity generates incorrect job control code if * yo...