DSXchange

Information on Demand (that's this month's catch phrase)

If there's one particular item you're after, I'm sure someone has downloaded it at some point.

This site may have some resonance.

Search the forum for "vertical pivot". There are several strategies available, depending on particular requirements (for example whether there is a known or arbitrary maximum number of rows to be pivoted). Therefore, without knowing the circumstances more fully, no-one is going to suggest "an" answe...

Seconds are rounded to the nearest whole number. 0 rows/sec can occur because the run tool less than 0.5 seconds; this is manifesting a strategy of avoidance of a divide by zero error.

That's a deficiency in the ODBC driver's implementation of SQLColumns() function (or perhaps in DB2-Connect). There's not a lot you can do about it. If you can get the column definitions with descriptions into a UNIX-based DB2 table, then you can probably import the table definitions using the plug-...

Shared containers have their own parameters that must be passed from the job that uses them. They have default values. The default value may be a reference to a job parameter (surrounded by "#" characters) but not one of the references to environment variables directly; that is, the environment vari...

Not sure whether they've gotten rid of it or just haven't figured out where to place it yet. They are remarkably silent when asked.

If they're sorted by NAME you can do it in a Transformer stage using stage variables, and avoid the overhead of calling a Routine. One pair of variables can detect the change in values in NAME, while another can keep track of the TYPE most recently seen for that NAME. Constraint expressions direct o...

Try being more focussed with your search, for example "failed to open RT_STATUS". Choose exact match or all words as the search methodology. They're definitely out there.

Was your support provider any help, particularly for the DSR_EXECJOB error?

The Aggregator stage follows exactly the same rules as SQL SELECT. Every column must either be grouped or have an aggregate function applied to it.

The Aggregator stage gives you eight aggregate functions where SQL only gives you five. But that doesn't change the rules.

I've managed 80,000 rows/second on my laptop doing a read-only job from a sequential file. The downside is, everything else I add to the job will reduce that rate.

Whatever you're missing, we're missing too. What I described is the only way you can miss a column on a SELECT * query. In hindsight it might have been clever to SELECT Department_Name FROM H_SK_ProductBrand_Test but hindsight, as we know, is the only perfect science. Might be worthwhile marking the...

The Datastage EE MVS edition contains optional components for working with IMS viewsets and data sets.

If you have a coarse enough hash file... (ok, yeah, so it crumbles).

You are on the right track. You may need to trim the rightmost space characters after removing the AM/PM designator. You will need to do some conversion of the date components to perform the arithmetic.

Keep RT_LOGnnnn as small as possible, if only for performance reasons.
You can archive and purge as often as you like.