DSXchange

A quick-and-dirty method would be to export the project to a .dsx or .xml file and do a text search for occurrences of the file name in that file. Of course this only work where you specifically used the name and not a parameter. In addition, you can use the built-in metadata tools if you always loa...

Mandar,

you would need to write a sequence job, in that you call the UNIX command "wc -l {yourfilename}" to return you the number of lines, then you can conditionally call a job if this returned number is greater than zero.

dhwankim,

could you explain the

JdDSSJOBUpdate_T1_JC_JOB_PARAMETERS_Hf

part - I'm afraid I don't know what you mean.

It sounds like you have the "clear file" option set when writing to the hash file. If you uncheck this then the file's contents will not get deleted on subsequent runs.

The error message is that DataStage has waited longer than it thinks to start a job; this is most likely due to the system's resources being bottlenecked during this initial startup phase. Please monitor your CPU usage when the job starts, if it is over 95% for periods of 10-15 seconds then this is ...

Does the same server job timeout each time? I suspect that it does not; could you stagger your 30 concurrent calls by making some of them depend upon others finishing? Also, monitor your cpu usage while these are running, vmstat should be detailed enough.

The Key management routine uses a file called SDKSequences and your argument is the key into that file. You can either code a DataStage basic code to delete or change this value or you can even do it as part of a DataStage job if you prefer that approach.

You could write an end-of-job subroutine that only gets executed upon job completion. In this routine you would call one of the DataStage routines, perhaps DSGetLogSummary with the DSJ.LOGWARNING key, to get all your warnings and write them to a sequential file all at once.

vmalviya, if your incoming source data is sorted upon the column(s) that you want to use to identify unique records then you can can declare stage variables in a transform that simply compare these to the last record, and if they match to constrain the output. Unsorted data is more difficult, in the...

KillBill,

glad to be of help, but I can't take credit for Craig explaining what had actually happened in your case (but I think that I might have found the error had Craig not been quicker off the mark)

-ARnd.

KillBill,

glad to be of help, but I can't take credit for Craig explaining what had actually happened in your case (but I think that I might have found the error had Craig not been quicker off the mark)

-ARnd.

If that is the case you are right, it most likely isn't due to corruption. What files does the reset complain about, and what other error messages do you get? Perhaps we can track it from that side.

D**m, he's good!!! And I always wondered why engineering bothered to put the initial value in!!!

Thanks,

John, that's a good approach, I usually use a COMMON in the routine to skip subsequent calls; and the overhead to PCL a function or subroutine has much more overhead than an IF-THEN construct. But in either case we are adding unneeded extraneous code for each row, so for efficiency it does make sens...

Shantanu,

the basic idea is good, but a stage variable will get executed for each row passed through the transformer... This will probably slow down your job considerably. Better a combination - use the routine, but call it from a parent Sequencer.