DSXchange

I would split them up into multiple files using grep.

grep "^1" file >newfile

The ^ matches the begining of a line the 1 is your record type.

We just had it happen. We are checking it out now.

Craig

Vincent has found everything else, right?

Change it to:

Quotes are killing you. You have embedded quotes. Remove them.

Are you sure you have write permission to the new uvtemp directory?

Roy

Thanks but we have it working to ordinary SQL Server. It is the cluster which is the problem.

I think WebSphere should be WebStage.

Here is a routine: * ----------------------------------------------------------------- * GetJobCategory(JobName) * Decription: Returns Job Category. * Written by: Kim Duke * Notes: * ----------------------------------------------------------------- Ans = '' RoutineName = "GetJobCategory...

Do a search on EtlStats. You can download it from ADN or my tips page. Lots of prewritten code to do this.

If it was me then I would create a job and select this into a hash file. I would write a routine to read this and return a different value if it found it.Call this routine in a sequence. Have links for each value returned. One to run the job another to sleep 15 minutes. You can do sleep in a routine.

Jay

You did not waste our time. We just could not see anything wrong with your code. We should of told you that.

You load in the path to the UNIX or DOS command like /bin/rm. The parameters for this command might be /data/seq/load*.txt.

You cannot load job parameters in here in version 7.1 or below. This is supposed to be fixed in 7.5.

Amen brother.

We cannot get ODBC to connect to SQL Server on a cluster from UNIX. The server name is something like SqlServer1\SqlServer1 in the DSN for Windows. It works fine. You cannot use this in UNIX. I think that name represents ClusterName\ServerName. Not sure. We have a support ticket open. Just wondering...