DSXchange

I am a little uncomfortable with what we call load balancing. Ken's code is nice but it is a throttle to limit the number of jobs running at one time to x. So if you set x = 6 then only 6 jobs can run at a time. Nice but real load balancing needs a weighted average. I think we as a group can invent ...

Here is the second: * ------------------------------------------------------------ * ElapsedTime(StartDateTime,EndDateTime) * Decription: ElapsedSecs between StartDateTime and EndDateTime * Written by: Kim Duke * Notes: * StartDateTime = "2005-02-09 18:45:45" * EndDateTime = "...

Here is the first routine: * ------------------------------------------------------------ * ElapsedTime(StartDateTime,EndDateTime) * Decription: ElapsedTime between StartDateTime and EndDateTime * Written by: Kim Duke * Notes: * StartDateTime = "2005-02-09 18:45:45" * EndDateTime =...

This has been a bug for a long time. There is a routine to fix this included in EtlStats. There is also a job to fix old records in the EtlStats tables. It happens when the job crosses midnight.

Your login needs write permission to this file to connect using Designer or any of the client tools.

Try

dsjob -run -param 'acctype=a b c' <project name> <job name>

Search for

dsjob -logdetail

or

dsjob -logsum

In EtlStats there is a routine to call to send attachments using blat.exe for Windows and another using Craig's method calling a shell script named Email.ksh. Both are included in the zip file. I think both have been posted on this site.

If you look at the settings within DataStage it will tell you the compiler name and options used. You need to match these to create your own routines. Do a search there are several posts explaining how to do this.

Yes you need this in your dsenv file. You need to stop and restart DataStage when you change this file. This will allow OCI stages to work.

If you update the repository directly then IBM has the right to not support you. The exe is a part of one of the zip files on my tips and tricks page.

The dscc.exe is on your client. It will compile a job from the client command line or in a bat file.

If you are using server then Repository Assistant can help extract job designs into Access.

We did it in DataStage by running a job over and over until it selected 0 rows. What a mess. It is sort like drilling down one level at a time.

Another words you need to create a DSN for it.