DSXchange

You need to execute in sequential mode to compress into a single archive. But you can certainly have a Sequential File stage downstream of a Compress stage.

You have to do some arithmetic. The first three months you need 1, the second three months you need 2, and so on. Mod(month,3) gives the wrong result, you need something like Int(month+(month<>(month-Mod(month,3))/3) If that seems abstruse, go with a functionally equivalent If..Then..Else construct....

Probably. When the next block of keys is obtained from the state file information has to be written back to it to record where it "left off".

The Compress stage can compress/gzip a data stream. What you do with it after that is up to you.

Welcome aboard.

What has changed from when it worked and now? Design, total load on the system, configuration, ... anything.

What are you trying to achieve?

July 1st of prior year?

Without a clear specification we would have to guess, which wastes both our times.

Moderator: please move to server forum

Create a routine to generate the rows as a dynamic array. Return that and replace each dynamic array delimiter character with newline character. Write to a text file then read back from that text file.

If root did the install there's no guarantee that the licence XML file was put in the "installed directories". Could be anywhere. Perform the find as root.

Data should be partitioned on the sort key.

I only included Oracle enterprise stage types. You may need to research the value in field 8 of the DS_JOBOBJECTS record for other Oracle stage types if you're also looking for these.

There is an excellent training DVD Programming with DataStage BASIC available from the DSXchange Learning Center

Be superuser.

You may need single quotes around the wildcard. It's unlikely that you have no XML files at all on the system.

Seriously, how often are table definitions changed in a real production environment. The usual (professional) approach is that such changes are planned, and advised to everyone involved, including ETL developers so that they can assess the impact. A proper software development lifecycle should apply...

Not "ur". The correct spelling is "your". Ur was a city in ancient Babylon or thereabouts.