DSXchange

OK, we've eliminated one possibility (assuming you tested Query Analyzer from the DataStage server machine). Next is to try to figure out what is meant by "An unknown DBMS type". Can you enable ODBC tracing for this particular DSN, and try once again to connect. You will gather a huge amount of info...

All you want and more can be found in the Parallel Job Developer's Guide manual.
The section on data types in Chapter 2, and the chapters on Split Vector and Make Vector stages will be a good starting point.

There's nothing in DataStage. It's primarily an issue of management and co-operation between developers. Do they really need to test on 1.4 million rows? What's wrong with testing on 100 rows initially? Can the large jobs be scheduled to run overnight? And so on. With administrator access to the ser...

Within the Parameters grid, specify the parameter type as Encrypted.

Since the class A IP addresses indicate different domains, you will also need to ensure that there is connectivity, using ping from the DataStage server machine to the machine where SQL Server is installed. If you can't ping the other machine, you will need to talk with your network administrator ab...

How to use crontab on Windows?!!!

The "scheduler" interface in Director is the lowest common denominator between what you achieve with cron and AT. That's why it seems so limited. You can always modify the queued AT entry from a CMD shell.

Most of the built-in and SDK functions are cataloged with "DSX" prefix.

The ds_ipcgetnext() function is part of row buffering. Therefore, whether by default or explicitly in your job, you have row buffering enabled.

The error message has nothing whatsoever to do with the key management functions, which uses persistent external storage.

Perhaps his F1 (Help) key is broken?

The BASIC code itself isn't all that useful.
... unless you've memorized every single BASIC op-code, which is a major waste of time!

If you can figure out some way of loading everything after field 1 into a variable-length vector, the Split Vector stage will do exactly what you want.

You want the parent tables (operational masters) loaded first, you design your job sequence so that they are loaded first. Then, once they're all done (which you can enforce using an "All" Sequencer), you can load the tables that refer to them (the operational details). It's really that simple.

Short of removing the executables from the client, I don't think this is possible out of the box. Technically you could intercept the subroutine call to the helper subroutine, but that would require knowledge that is not in the public domain.

You could create a job control routine to do this. Error handling omitted for clarity and brevity. ThisJob = DSGetJobInfo(DSJ.ME, DSJ.JOBNAME) Open "DS_JOBS" To DSJobs.fvar Then ClearSelect 9 Select DSJobs.fvar To 9 Loop While ReadNext JobName From 9 If JobName Matches "1A0X&q...

Please let us know whether this approach achieves the desired result. I am sure that there will be others who need something like this in the future. (Or convert to Red Brick, where automatic maintenance of precomputed views "just happens"! )