DSXchange

Thanks Craig. (That's why I added a "brain-lock" disclaimer).

Ok, brain-lock alert! We upgraded from 6.0 to 7.5.2 on Windows. There are routines in sequence that are not working after the upgrade. For example, I have a routine that reads a parameter from a text file, in this case, an email address. Here is the log message it produces: -------------------------...

We can run the query without a problem in UniData.

I've contacted IBM support on this and they are working on it. I'll submit the final verdict here. Thanks again, Ray.

Hi Ray,

Thanks for responding. The one overriding factor in all of this is that we never saw this error in DS ver. 6. With the upgrade to 7.5.2, we now see this error. Could it be that since ver. 7 uses UniObjects instead of ObjectCall, there would be a different timeout involved?

Forgot to mention that if I select all 20 million rows without the SELECT criteria in the UniData stage, it will get past the error spot and start sourcing the rows.

This one is new to me. We upgraded DS from 6.0 to 7.5.2 on Windows 2000 Server SP4, running all Server jobs. Before the upgrade, all jobs ran fine in 6.0. However, after installing 7.5.2, I'm now having an issue with one job. The source is UniData (Infolease) and the target is Oracle. This job does ...

Well, it's seems to be working now. I don't know why Windows would behave like this, but I deleted the dsadm user and re-created it. Now it works fine. FYI: This is a standard barebones installation with just DataStage on it, so I don't know why it would have behaved that way. Anyway, thanks for the...

I'm having issues setting up Version Control on a Windows Server 2003 environment. Here's the initial info: DS Version: 7.5.1A VC Version: 7.5 OS: Windows Server 2003 I've set up a user dsadm and made him a member of the Administrators group. I then create the VERSION project on the server, logging ...

I'm using an ODBC stage to call an MS SQLSERVER stored procedure. The job runs fine if rows are returned. If no rows are found, the stored procedure is coded to print a return message. When this return message is printed, the job interprets it as a failure condition and aborts. Is there anyway to ig...

I may not have refreshed the view in Director. I'll have to play some more and post the results here later.

After trying some different scenarios, I think I have a solution which is not great, but works. I think the problem I was having in my BASIC code is that I was performing a DSAttachJob on the crashed job. This was causing a fatal error because it was not runnable. My code was this: JOB.NAME = 'sjob0...

Sorry, I meant to say RT_STATUS, RT_CONFIG, and RT_LOG. Yes, I did clear those three files and still shows "Running" as the status.

I'll try changing the autopurge settings. As far as the job statuses, the last job that aborted had a status of finished befor the sequence tried to run it. The sequence thought that the job was not runnable for whatever reason. Let me try to rerun with the autopurge settings changed. Since this occ...

Arnd, I'm not sure what you are referring to in the first paragraph of your latest reply. The job is being called by a sequence, not a job control. I'm not coding BASIC to perform an OPEN, but your comments about the LOCKED clause are good to know for future reference. We are doing an automated purg...

(Sorry, this is also posted on Enterprise Edition forum by mistake) Hi, We are having intermittent wierd happenings with job sequences. We're running DS 7.5 on Win Serv 2000. Occasionally, a sequence will abort because it can't attach a job. But in the log for that job, it says the previous run was ...