DSXchange

To me, it's simple: use flat files for 'staging' when your processes can support sequential media / processing. There's way too much overhead to use a database for simple staging, as a general rule I only do that when I need to use the staged data in sql joins.

I agree with you about the benifits Control-M and DataStage together can leverage. But my question is, to be precise, is DataStage Schedular a complete replacement-solution to CONTROL-M? To be precise, no. As noted twice now, there is no such thing as the DataStage Scheduler, on UNIX that function ...

Not sure if there is a 'proper link' here for your old version or even if this advice applies. In the current DataStage versions, there is online help for the ODBC stage that explains what needs to be done. Bring it up from the Designer, switch to the Index tab and type ODBC. Mine shows several sub-...

Or 7.5.2 is tighter, enforcing things that you could get away with in the earlier version.

Str( #PARAM#,Size)

'Size' would be the number of times to repeat the value, the size of the resulting string.

Or $DSHOME/include/dsapi.h

There are multiple ways to do this, depends on what you are trying to accomplish. You could write some 'job control' to get a list of all jobs in the project and loop through them one by one, checking their current status and building a list of those found to be running. I usually just run this from...

Hmm... ok. Time to mark the thread as Resolved then, it seems.

Both use OCI, assuming you set the DRS stage to Oracle rather than ODBC. The 'advantage' of the DRS stage is the alleged ability to switch databases on the fly, which never works out as easily as the brochure says it will. We have Oracle here and use the OCI stages exclusively. With the DRS set to O...

All of the advice here on recovering is specific to the releases that preceeded 8, I would imagine it changes significantly in the latest release. Have you involved your official Support provider yet?

Looks like a 'normal' fixed-width file, have you tried to read it? Do you have a more specific question?

There is no 'DataStage Scheduler' per se, it is simply an interlude or interface to your native UNIX scheduler - cron. And with Control-M being your Enterprise scheduler, I doubt you would be 'allowed' to use cron... we use it as well and I would get whacked if I started running crap via cron. While...

Then it doesn't sound like you've actually changed the table you are importing.

You would obviously have to manually change the metadata not only in the Manager / repository but in the job(s) where you've used it as well.

No time for urgent!

I
already
said
that.