DSXchange

I would use the UNIX split command or dd to split this file into multiple files before running the jobs. This allows each job to read less data. You will need the disk space to do this.

Both EtlStats and DwNav are designed to store a history of run times and row counts of completed jobs. I really have never taught about a process to see how much work the server was doing at any given time. Maybe useful. Let us know what you come up with. Ray's solution could be used in a filter.

SELECT DS_JOBS.NAME AS JOB_NAME, DS_JOBS.CATEGORY, DS_JOBOBJECTS.NAME AS OBJECT_NAME, DS_JOBOBJECTS.OLETYPE, EVAL DS_JOBOBJECTS."if index(upcase(@RECORD),'PROJDEF',1) > 0 then 'FOUND' else ''" AS FOUND FMT '5L' FROM DS_JOBS, DS_JOBOBJECTS WHERE DS_JOBS.JOBNO = DS_JOBOBJECT...

This is available in 7.5.1 in case anyone cares.

Ray is trying to hold us back so we never catch him.

The ulimit command will describe how big a file you can create. You also need that much space on the disk drive.

index() will tell you where in the string it exists.

Describe the job. What stages and how many rows otherwise call support.

If you write a job which reads from Oracle and writes to either a hash file or a sequential file then these are easy to read or write to in BASIC in either a routine or a batch job. I usually start jobs from batch jobs and not routines. As to the routine returning start and end dates as one field. I...

You need to create a batch job or a routine. A batch job is a job with no stages just code. In the job properties there is a control code tab. In this screen there is a drop down list of all the jobs. Select the job you want to run and it will add all the code to set the parameters and run the job. ...

This bug is on 2000 sp3 and sp4 and XP.

Thanks. I appreciate the compliment even though I get no respect from my friend Hester.

We have the same issue. We got the patch and now cannot edit routine activities. We reported it last week. We are waiting on another patch.

Let you know when we get it.

To do any kind of lookup requires something to be in common between the 2. All hash files require one or more fields to be the key fields. The same is true if you lookup using an ODBC stage or a plugin.

You have OpenSeq ... then without an end statement before the repeat statement.

Next time bracket your code with alt c and format it ahead of time.