DSXchange

Trick it. Make the key column in your design the one that will appear in the WHERE clause, and mark the one that will appear in the SET clause non-key.

And is the source database possibly being updated while your selects are running?

There are competitive products to QualityStage. In my opinion none has the range of statistical (probabilistic) models available that QualityStage (formerly INTEGRITY from Vality) has. But the biggest kicker is how easy or difficult they are to integrate with your other tools - the interface between...

I thought the column name was DTM, not MODIFIED_ON. There is no SQL - anywhere - that allows you to query successfully with made-up column names.

You might look at separate logical partitions (LPARs) but these are totally separate, so you may end up having to have duplicated components.

To the best of my knowledge DataStage EE MVS does not have the ability to create COBOL subroutines. The External Routine stage allows existing routines to be called. One of its properties is the library containing that routine. I believe you're seeking like Create mainframe routine (to go with Creat...

Can you not schedule it from Director as 1 Jan with the Every option checked? Then just modify the crontab entry as required.

There are no actual data types within server jobs. Dividing by 100 was a perfectly valid method. So is substring (or Left() function).

I think Vinod means a Usage Analysis such as is done in Manager, rather than an ANALYZE.FILE. That said, the answer is that you must still SETFILE, and import the file definition. Alternately you can Save the hashed file definition from your job design and import it everywhere else it's needed. Usag...

"Best" is too subjective a term. 25 jobs is very many to maintain. 25 separate jobs will make troubleshooting easier. What/where are your priorities?

There's also a Help topic on DB2 configuration requirements. It's for DB2 Enterprise stage (parallel jobs) but it's still a useful checklist.

What is the data type of MYFIELD? Have you tried converting it to integer (say in a Transformer stage)? That should remove the zeroes - if it doesn't adding zero to the integer definitely will.

One way might be to count the number of pieces that should exist for job number xxx before promoting and verifying that number after promotion. RT_BPxxx, RT_SCxxx and RT_BPxxx.O. If you want to be thorough, do the same for RT_CONFIGxxx and RT_STATUSxxx using SQL queries (SELECT COUNT(*) FROM tablena...

Mandatory if the manual is to be believed. I believe it so have always key partitioned and sorted Join stage inputs. Perhaps you'd like to try without, and let us know the result?

Not running on a PX site at the moment. Can't say.