DSXchange

I really didn't think XYZ was your jobname, and was hoping you didn't have a disallowed jobname. I didn't push the point of you changing the name, I "trusted" that you didn't use reserved characters.

Can you pls suggest me any setting has to be enabled for the batch? None that I know. The problem is now your job. If the job cannot be attached, that means something else is preventing the DSAttachJob API from securing the job. The DS BASIC manual doesn't tell why a job can't be attached other tha...

I know some existing Orchestrate customers who "backed in" to owning DataStage PX. By release 7.5, I would understand that handcrafted OSH scripts are poo-poo'd. I guess the core engine has been modified such that a from-scratch OSH script may not be possible. Your original question was not about mo...

I even tried by deleting the files which are created and started from first ..But no use.... Are the hashed files external path or did you leave the project as the default option? If you used the project as the default option you CANNOT remove the hashed file contents from Unix using the "rm" comma...

Also, if this job is supposed to create the hashed file, make sure the Create File checkbox is checked.

Welcome aboard!.

Is the hashed file supposed to exist prior to these jobs running? If so then make sure that the job that creates the hashed file does so with the appropriate directory path and permissions prior to this job running. If the file exists and this job can't see it, then it's either the file name, path o...

Shhhh. A PX job is just an OSH script generated plus custom operators from the GUI designer. The Orchestrate engine is now the PX engine, just by another name. I do believe you can still handcraft your OSH scripts if you'd like.

Okay, but run the Batch job that just runs XYZ. Does it work? If it does, then your problem is your original Batch job logic. All of those: ErrCode = DSSetParam(hJob7, "$PROJDEF", "$PROJDEF") lines look weird, that's not right. I don't know what's going on with that.

Verify the case sensitive job name is correct. Then, create a new Batch job from Director and use the Add Jobs functionality to add the job to that new Batch. Run that test Batch job and see if it works. If it does, then go back to your original Batch job and find the discrepancy and let us know you...

I'm recommending an intelligent job stream controlling process, a Sequencer or custom job control, be put into the enterprise scheduler. You need both devices in my opinion. It's not scalable to put every single script, job, program into the scheduler. Sometimes you write a script to run other scrip...

And forgive me in advance for my use of "hash" file instead of "hashed" file. That document was originally written back in 1999, prior to Ray Wurlod correcting my unforgiveable American misuse of the English language. I've tried to correct my terminology since, but I have a proliferation of existing...

Or checkout the newsletter archives

http://www.datastagexchange.com/Newslet ... ntpage.php

Put the minimum modulus high enough to prevent dynamic resizing. You're probably hitting a lot of resizing and that causes periodic "stalling" of processing as the hashed file grows.

With read caching the row on disk (no write caching) may be different than the row in memory, if the row in memory was paged into memory before the row was modified. If you need to reference a row in its modified form, you must NOT use read AND write caching. The point of read caching is that multip...