DSXchange

Nor for any other version.

Job names are stored in DS_JOBS. Job design time configuration is stored in DS_JOBOBJECTS. Job run time configuration is stored in RT_CONFIGnnn where nnn is the job number from DS_JOBS. Job and stage run time information is stored in RT_STATUSnnn. Job log information is stored in RT_LOGnnn if local ...

Stage variable initialized to 0 that increments only if the value is "#FTP".

Remove Duplicates on the reference input link.

Why are you "not supposed to use a Transformer"?

Resist stupid reqirements!

You are correct. I meant to say "explicit Sort stage".

Use Row Generator or Column Generators or expressions involving Char() and Seq() functions to generate characters in the desired ranges. Use one per character. Concatenate them. Optionally return a random number of those characters, making sure that your rules remain met. For example, upper case let...

Yes, you'll get one row on the output for every row returned from the reference input.

Yes you can, but you will want to become very good friends with the DBA if you want to create such enormous transactions!

Depends what kind of BLOB. Technology is marching on. For example you might filter face pictures on whether or not they have spectacles (via Java calls). The new InfoSphere Streams connectivity may do some kind of what is effectively BLOB processing too. In general, though, it is still wise to consi...

Thismakes interesting reading.

Maybe time for a Malware scan. McAfee found nothing untoward.

I prefer to use explicit Join stage. By default the job designs are identical. The score will show a tsort operator in each case, with 20MB memory allocated per node. Environment variable APT_TSORT_STRESS_BLOCKSIZE affects every sort in the job. The Join stage allows me to allocate more memory to th...

The SELECT (if you have specified Partition Table) will run in parallel, the data will be returned partitioned according to Oracle's algorithm.

What you do with the partitioning after that must be guided by your job's stages' requirements.

Try "escaping" the quote characters.

First point - Auto will always yield correct results (though it may not perform optimally). Second point - Data Sets are read using the configuration with which they were written, even if this needs to be created on the fly, and mapped onto the configuration that the job is running. In short, it wil...