DSXchange

This is a bug that has a patch fix where DataStage does not honor the constraints for multiple output data links in a Transformer stage using Loops Conditions. The resolution is a patch, JR44926 (http://www-01.ibm.com/support/docview.wss?uid=swg1JR44926), that is not available for v8.5, but is avail...

You're very welcome NSIT. I stumbled on your post while searching for CFF array handling. I actually found very good information in IBM's Parallel Job Developer's Guide in Chapter 10. Also, Appendix C does a great job explaining FILLER creation. Now I'm just wondering why I subconsciously gave Ray m...

Yeah -- the Parallel CFF is very powerful, but it's so different from the Server CFF and it isn't documented very well. For that reason I cannot supply a reference; only hard-learned experience. The CFF processes one record at a time, but you've probably figured out by now that the CFF can "buf...

Our Sales Engineer just provided me with this information: "A new add-on product for managing data privacy/deidentification within Information Server is on the roadmap based on DataStage v8.5 release. It will be based on Optim data masking technology. No firm date is yet planned - rough estimat...

I met with our Sales Rep and Software Architect and asked if the de-identification features mentioned in the IOD Conference were related to the Optim products. They didn't believe so, but I got this information from the engineer assigned to my PMR: Is IBM Optim a tool, environment, consulting servic...

Sufficient pressure has been applied to our Sales Rep, our Technical Specialist, and the engineer working on the PMR. Now awaiting responses...

Thank you gentlemen for your time -- I used your information as ammunition in my PMR. We'll see what they say now. We've been writing de-identification code with Row Generators & Transformers, and our next step is external C++ routines. However, if IBM already has something available (now, or so...

We encountered the exact same error last week. After searching, I bumped $APT_MONITOR_SIZE to 100000. It didn't help. Then the developer told me she found a flaw in her code. In her Switch stage, one of the values was surrounded by double-quotes. In other words, the value was "3" and not 3...

lfong, Glad you got it working! Thanks for sharing the good news. You've learned the hard way that you have to define your output metadata first before filling out the rest of the stage. I was in the midst of typing this long reply, so instead of wasting it, perhaps someone else can benefit later. -...

Here's how I'd do it... Start with a Sequential File stage with the following metadata: COL1 Char(6) RecTyp Char(1) COL3 VarChar(23) Then run the stream through a Switch stage to produce 2 links (streams); one for each RecTyp. Then run the 2 links through 2 Column Import stages (giving a total of 4 ...

lfong, Prior to your Column Import you need to be able to separate the record type from the rest of the data. I suppose you are asking how to determine where your record type is because the records aren't fixed length. You can place a Transformer (or Modify, if brave) between your Sequential File &a...

DSaveAsBmp was exactly where I was headed when I said I would "check into other options". Your additional information should help provide a satisfactory solution. Once again I shall dupe my boss! Of course, an even better scenario is that my ADD friends in the QA department will forget abo...

Thanks Ray -- tried it -- identical results. Nuts. I tried "Multiple Job Compile" on JobReport alone, tested, then MJC on all the Kim routines, tested, then MJC on all the routines in the project, & tested once again. Then, I re-downloaded the DSX from Kim Duke's website, re-imported, ...

I have stumbled upon Kim Duke's Tips & Tricks from recommendations on this website (wow -- thanks Kim). The QA's are excited about automating the report generation at the category level. A few problems, though. It's narrowed down to the JobReport routine by Tony Curcio. Even attempts to run this...

Sorry, it was 1,073,741,824 bytes (2,097,152 * 512), not 1,073,751,824.