DSXchange

Search the forum. Chuck Smith has a utility, Kim Duke has a utility. Or you can interrogate the Repository if you prefer to re-invent the wheel.

A wat is a Buddhist temple. I don't believe they use ETL tools all that much.

It should not be under the Compiler folder. My guess is that someone has edited the DSParams file inappropriately.

And there are parallel functions for doing these. LEARN!!!

DS_PXDEBUG should write the score to the directory indicated (this is not a True/False environment variable). Try using one or the other. APT_DUMP_SCORE should log an event containing the job score; the first line has the form "This step has N data sets".

If you export including default property values a fairly simple search/replace ought to be possible, unless you're inserting new stage variables. In that case, yes, it's doable with a DataStage BASIC routine. I've written them in the past, but always left them at customer sites. There's no such thin...

The "best" approach is to have your DataStage job exposed as a web service. Then you can invoke it from anywhere, anywhen.

Pass the query to the job run under control as a job parameter. Use a reference to this job parameter as the user-defined SQL in that job.

You can also create a job sequence with N streams of job activities. This will restrict execution to at most N jobs at a time. Job1 ----> Job5 ----> Job9 ----> Job13 ----> Job17 Job2 ----> Job6 ----> Job10 ----> Job14 ----> Job18 Job3 ----> Job7 ----> Job11 ----> Job15 ----> Job19 Job4 ----> Job8 --...

You can do what you propose, but you need to segregate populating the data file for the bulk loader with actual execution of the bulk loader.

Why not just create additional projects on the same server machine? Projects can be placed wherever you like - the location is established when each project is created. You do not require an additional copy of the server software (except, of course, to further enrich IBM with the licensing revenue f...

Can you create the loop in a job sequence, passing schema name, user ID, password and any other required information to the job on each iteration. The lists of parameters (connection strings, effectively) might be read from a file into user variables from which the StartLoop activity can set up the ...

Yes. You need to import or create the "table definition" of the flat file, so that ProfileStage understands where the "columns" begin and end, and where the "records" end.

The DataStage job log should report the pathname of the log/bad file that it used. And/or these probably are properties of the Oracle Enterprise stage.