DSXchange

It's pedantry time again! :D The number of input arguments to a transform function does have an upper limit, of 254. If you get anywhere near that, I'll personally fly to where you are and slap you severely on the wrist! The number of return arguments for a transform function is fixed at one. Howeve...

How exactly do you want to use this one line in your job sequence? I note that you specified a Routine Activity. If you use a Routine that incorporates code like that Vincent suggested, make sure that the value of the Output argument is assigned to the return variable (Ans). Your syntax does not wor...

DS 7.0 PX gives you the choice of TWO (count them!) Transformer stages. One is the original PX Transformer stage, the new one is called a BASIC Transformer stage, and works exactly like the server job Transformer stage (allowing the full gamut of BASIC functions and the like). I have to use the word...

Remember it's the DataStage server that's doing the import of metadata. Are the network drives mapped on THAT machine? (That is, have the appropriate mappings been set up, either with the Windows GUI or via the net use command, on the server machine?)

I agree pretty much 100% with Kim's last post. The programming language is there for when you need to tweak the way that something works because DataStage solution is not absolutely what you require. The same can be said for BuildOps and CustomOps in the parallel environment, custom routines in the ...

Well, it may "cause problems", but you have to learn to live with it. That's because "position" is how columns are identified in records in hashed files; by their ordinal position. The hashed file storage mechanism is precisely a delimited string; all values are stored as text, and the location of a...

You might also like to investigate the "MX0C" conversion, which converts each byte into two hex characters. For example, "ABC" becomes "313233".

It depends on what type of lookup stage you are going to use: OCI/ODBC: You have to define the appropriate SQL statement in the stage. You will have to supply the appropriate columns in the key expressions. Hash file: Not without some work. Unless performance is an issue, this solution is highly cu...

Hi, 1. if you have NLS installed you should have no problem getting the special characters. if you want to remove them you can use trim/ereplace functions. you can test hte ascii values fo those chars with the seq function. if your problem is more complex maybe you'll need to elaborate on the issue...

Has anyone actually read the EULA for Windows XP? It's one of the reasons I won't have anything at all to do with it.
My preference, in fact, is to stay with WinNT 4.0 sp6a, which has proven to be remarkably (for MS ) robust and stable.
But I do like Mac OSX (X.3?)

If you want the SSELECT filevariable statement to perform a numeric sort of the keys, change the definition of @ID in the file dictionary so that it is right-justified rather than left justified. For example:

It's good value to report these discrepancies to Ascential so that they can get it right next time around.
(Yeah, it's even better value if they got it right first time but they, too, are human.)

XA means the "master record" in a block of probable duplicates. It tends to have the highest composite weight. DA means one of the other records in a block of probably duplicates. RA means a "residual", a record with no probably duplicates. You have to remember to include these in your survivorship ...

The pattern characters were generated during the investigation phase, to allow you to see what kinds of tokens exist in your data. After all phases (investigation, standardization, matching and survivorship) all information typically has been carried through. All you need to do is to create another ...

In that case, you're not talking about a DS 390 job. There is no link collector stage in DS 390.