DSXchange

What is different, what has changed, and what map is being specified? It really is impossible to offer cogent comment without this knowledge. The answer "nothing is different" is unacceptable. Clearly something is different.

The forums are not the place to search for documentation. You may have the documentation that was delivered with the software (that is, all the manuals). If not, request your support provider to get them for you.

I can't help with the actual question, having no experience with XMS.

rep wrote:So in the future if anyone reads this thread, my post will look like I'm typing jibberish.....again.

Isn't Gibberish the language they speak in Gibraltar?

Parse into separate columns then use a Pivot stage. Probably the easiest parse is to combine the record into a single field using a Transformer stage then run that through a Column Import stage.

No, that can happen on any VPN, and you don't need version 8. It probably means that the job was only partially saved. I'd look first in the local repository (DS_JOBS and DS_JOBOBJECTS) to try to see how complete the local record is. If that looks complete then I'd be looking in the XMETA database.

Well we can save you half that task - there's no "append" for hashed files.

Will have to do some research to determine which field in a DS_JOBOBJECTS record contains the overwrite/append flag. It will be a record with an OLETYPE of CSeqInput, in case you'd like to get started on that research.

Substrings and concatenation will be the most efficient, and remember that there are no data types within DataStage server jobs. Right(InLink.TheString,2) : "/" : InLink.TheString[5,2] : "/" : Left(InLink.TheString,4) Another nice thing about this solution is that...

Yes, I can understand that the former figure might have given you pause. DSXchange needs revenue to survive, but doesn't want to price itself out of the market either. Thank you for checking.

----> Sort ----> Copy -----------> Join --------> Copy ---> Filter1 ---> | ^ | | | | | | V +-> Aggregator --+ Filter2 ----> Sort stage generates key change column. Filter1 isolates those rows for which key change column is 1. Filter 2 isolates those rows for which key change column is not 1. Aggreg...

Edit your post. Wrap it (the design) in Code tags then use Preview until it IS right.

Purchase a premium membership or have your employer do so on your behalf.

Premium membership is not expensive, at less than 30c (Rs12) per day. It is one of the ways that the hosting and bandwidth costs incurred by DSXchange are met. No premium memberships = no DSXchange.

Caveat poster

* I don't believe there's a Latin word to cover "one who posts on a web site", though scriptor (writer) may come close.

Caveat poster

Definitely not because @OUTROWNUM is unique to each partition of data. You could construct a sequence using @PARTNUM and @PARTCOUNT (do check these names - I am not on site at the moment). Please do not ask for non-premium format; premium membership is one of the ways that the hosting and bandwidth ...

Look in your DB2 error documentation for error code -443 and -727. This will probably also offer suggestions for rectifying the situation.