DSXchange

You haven't really detailed exactly what functionality you are looking for that you think is missing.

Job name doesn't matter, all that matters is the stage name. And the stage name is what displays on the General tab. Your trigger has DemandPlanningFCST in it, not DemandPlanningHIST btw.

Nagin wrote:But, the standards here require using only parallel jobs.

That's a silly 'standard'. Use whatever job type is appropriate to the task.

Is 'DemandPlanningFCST' the name of your Job Activity stage - not the job it runs, but the name of the stage that runs it? It needs to be.

I understand all that. Here is the fly in the ointment: When we execute the customjob.sh shell script from UNIX command prompt, job is getting started That only tells you that the script is syntactically correct, not that it is appropriate for running under any kind of a scheduler's environment. Yo...

It's your script, not the 'application engine' stuff I would wager. And you completely ignored this from Arnd:

ArndW wrote:I would start with adding "-MODE NORMAL" to the command line. But how about printing out stderr in your script as well?

Post your actual script - that can't be it. 'Project Name'? 'Job Name'?

No.

Depends on where you add it.

Hey, I resemble that remark! And me and my ilk are to be ignored at your peril!

Uncle Ray wrote:I've created one tonight - the first 112 lines are comments.

Shocking. Absolutely shocking. <cough>

(we now return you to your regularly scheduled discussion)

hitmanthesilentassasin wrote:Is it possible to define the column structure(meta data) in a file and then import it?

If you are asking if you can you put table definitions in a flat file (say, like DDL files) and import from there instead of the actual table - the answer is 'no'.

ps. CAPITALS and Arnd's specific OConv function call are the same thing, as the CAPITALS transform just does the function call for you. Without any mis-typing.

1. No.
2. You should consider upgrading the Oracle client on your DataStage sever to 10g. What kind of 'advanced features' are you thinking about? Most would need to be specifically coded into your design, I would think.

I actually think the answer is 'no'.

anshumangupta1206 wrote:If I modify this parameter at job level , will the value at sequencer level be modified ?

What kind of 'modification' do you mean here?

Right, "Program "DSU.GetChampLigneV2":" would mean a User supplied DataStage routine named GetChampLigneV2, but is it really that large? Wowzers.

That would put it up in Bland or Duke territory.