DSJ.LINKROWCOUNT is the info type.
The IDENT1 is an invisible Transformer stage that the job compiler has inserted because your design includes a link between two passive stages. Hope both the issue should get solved by including a transformer between the stages.
You also have microseconds_from_time() function. You need to pass it as a parameter to a job for the file creation. The job where you select the value from, write it in to a file. Using ExecuteCommand Stage, read the file using cat filename command and use the commandOutput to pass it as a parameter...
Try to include a Transformer in between the two passive stages and find the stage info for that. I rather use DSGetLinkInfo(JobHandle, StageName, LinkName, InfoType).
I could see your latest post that, Index is not crated. But Primary key index will be automatically be created when you have a primary key constraint in it.
As mentioned, the Building up of Index will take up a long time as the number of records getting increased. That might be one of the reason where you get high load rate at initial stages. But still, as per your previous statement, If you load the data without lookup, it loads within 5 min. In that c...
ODBC stage don't have the outlink in it. What you mean by this? If you drag a output link from a ODBC, you should get one. If you need to pass some parameter, drag a link from a transformer stage placed upfront. The value can be Job parameter. Make sure you limit it number of row to 1. And why you ...
What is your job desing? When does this error message prompts, is it after the data been loaded or as soon as the extract information apears?
Do you have any Before/After SQLs which refers to some other tables?
Restart will happen only upon failure. If you job finishes with warnings, the DSEngine will consider it "a finished" job and run from the next job onwards. Just to give you a heads up Since the job status is (Finished with warnings), it is considered as finished unless the warning is promoted to fa...
What document you are referring to? Production Manager should be able to import and run the jobs. "Users can view objects in the project, and perform tasks that affect the way a job runs rather than the jobs design; specifically they can: Run jobs Set job properties Set job parameter default values"
You may need to first list of parameters that been used. And you will need to loop through each parameter and find the list of jobs and stages using the query that Kim has used, instead of finding it for PROJDEF.
I guess its an updated video than that was available in his homepage couple of month back. Amazing job. But it takes some measurable work around to get it done in Version 7 of Datastage. So I quit, and waiting for some updated version in weeks. I guess it should be a easy installation for anything g...