DSXchange

I've been a long time user of the old print screen and MS Paint combination. But don't tell the Ascential lawyers! Very handy for moving bits of a job into documentation and administrator guides. I've been assured (by Ascential) that producing in-house documentation is OK, provided their ownership ...

In 7.5 you can have the Director client on your PDA using the real time interface (RTI).

Apart from that there's nothing from Ascential, but check out Kim Duke's offeringsparticularly DSWebMon.

Since reset is a form of run you will not be able to allow reset to a user ID that does not have authority to run the job.

Hijacker hihack! DYNAMIC hash files do not use the resizing commands, only the static hashfiles. Dynamic hashed files DO use the RESIZE command. The "modulo" figure is interpreted as minimum modulus, the "separation figure" is mapped to group size (sep 8 = group size 2, any other sep = group size 1)...

Contact Ascential to learn about training available in India. Peter Zeglis (peter.zeglis@ascentialsoftware.com) will be able to give you this information. You have a clear need. Answers to some of your questions can be found here, in on-line help, at Ascential Developer Net and/or in the manuals.

Look in the .odbc.ini file; there will be an entry for the SQL Server driver. Its library name is of the form vmmsssnn.so (or .sl).
Search the forum; others have done this before you.

Re-read the message back from Oracle. At the operating system prompt, use the oerr command to get more information about this error. What it suggests is that you can not parallel-load a table that has triggers or constraints enabled, which does seem odd but not impossible. Someone more knowledgable ...

Being cheap, I tend to use Alt PrintScreen and edit it (mainly tidy up the edges before pasting the image into documentation) with MS Paint or some other (free) image editor. Works fine for me, and the price is acceptable.

Look in the BASIC manual for the following subroutines, the first of which is exactly what you want.

!GET.PATHNAME
!MAKE.PATHNAME

For me the biggest factor is the oft-neglected facet of total cost of ownership "ease of maintenance".
I believe that DataStage's graphical design metaphor offers the most easily maintained mechanism in the market.

You can view the schedule using the DOS command AT with no command line options.
You can capture this output into a routine using a call to DSExecute with the Shell argument set to "DOS".

Why does that text look vaguely familiar? Could it be because I've read the manual?

Please don't copy large slabs of the manuals into these fora; it wastes disk space. Everyone who has DataStage has the manuals. All you needed to do was to refer to the correct place in the manual.

Ah, yes, but Special K's!

NEVER use a STOP statement in a Routine.

DataStage routines must always return, so that the "cleanup" can be managed gracefully even though something has gone wrong.

If they're all in the same database, join them with SQL; you may require outer joins depending on the exact relationships.

If they're from disjoint databases, you can use the ODBC stage's multi-row return from lookup capability.