problem adding jobs to schedule

hiltsmi · Post by **hiltsmi** » Fri Nov 04, 2005 12:01 pm

I have a new install of DataStage. I can run jobs manually but when I try to schedule a job I get the following error message. I have been unable to schedule any jobs.

Error adding to schedule: at: garbage after time specification
(Command was: AT 14:00 /NEXT:5 vmdsr_sched.exe C:\Ascential\DataStage\Projects\Test_project copyDSlog 0/50 2)

Can anyone tell me what the problem is?

ArndW · Post by **ArndW** » Fri Nov 04, 2005 12:46 pm

First, see if "at" is even up and running on your machine; you can type in the command "at" in a dos shell to check this. Then, do you have access rights to add to the scheduler? I tried your command and it worked (you can try executing "AT 14:00 /NEXT:5 vmdsr_sched.exe C:\Ascential\DataStage\Projects\Test_project copyDSlog 0/50 2" in a cmd window on your server as well.

hiltsmi · Post by **hiltsmi** » Fri Nov 04, 2005 1:23 pm

I tried it in a command window and it gives me the same error message.

ArndW · Post by **ArndW** » Fri Nov 04, 2005 1:38 pm

Try adding something else, like a "dir" command; can you do that? If not, it is probably access rights.

ray.wurlod · Post by **ray.wurlod** » Fri Nov 04, 2005 3:13 pm

Assuming that the Scheduler service is running (the error message suggests you've got as far as trying to execute an AT command), the text of the message indicates a problem in DataStage. That there's "garbage after the time specification" in the AT command is something you need to take up with your support provider.

It looks like a valid AT command to me. The /NEXT switch is legal, the executable name is in the DataStage bin directory, and the remainder is the command line to vmdsr_sched.exe.

ray.wurlod · Post by **ray.wurlod** » Tue Dec 13, 2005 10:06 pm

Did you ever resolve this? I have just encountered it on a 7.5.1 system.

gomez · Post by **gomez** » Wed Jan 31, 2007 12:52 pm

I encounter this when I try to schedule a job. Can somebody help ?
Thanks

ray.wurlod · Post by **ray.wurlod** » Wed Jan 31, 2007 4:07 pm

If there had been a resolution it would probably have been posted here sometime in the past two years.

Have you asked your support provider?

gomez · Post by **gomez** » Wed Jan 31, 2007 5:25 pm

I dont understand who you mean by Support provider ?? Are they the tech support available within the organisation or IBM Ascential?

DSguru2B · Post by **DSguru2B** » Wed Jan 31, 2007 6:25 pm

IBM .

ray.wurlod · Post by **ray.wurlod** » Wed Jan 31, 2007 10:56 pm

Your vendor (the company from which you purchased DataStage) is expected to provide first line support - they take a percentage of the maintenance revenue.

If you bought DataStage through a reseller and then attempt to contact IBM support directly, you will be politely but firmly redirected back to your reseller.

DSguru2B · Post by **DSguru2B** » Thu Feb 01, 2007 7:40 am

You manager or who ever signed the PO will be having more information about it. Or maybe if you guys have a product admin at your site, he/she will be able to help you out.

gomez · Post by **gomez** » Tue Mar 20, 2007 3:08 pm

My guess was this is an installation issue or access restrictions. We have DataStage installed in development/production servers using the same license and they seem to be working fine with respect to scheduling. It is only the install on my desktop that throws up errors when I try to schedule the jobs

I would try a reinstall to see if that fixes the problem and then would get in touch with IBM for more help

Thanks to everyone who stepped in to help me!

soportesis · Post by **soportesis** » Wed Jun 06, 2007 12:54 pm

PROBLEM: DataStage is not able to find the correct AT.exe command and executes the first it finds according to the Windows system PATH.

SOLUTION: Move the C:\Windows\system32 directory towards the beginning of the PATH variable. You can do this trhough the Control Panel -> System (Advanced tab) -> Environment Variables.

ray.wurlod · Post by **ray.wurlod** » Wed Jun 06, 2007 9:16 pm

Welcome aboard. :D

Which AT command is it finding?
Will moving System32 to the front of PATH solve the "garbage after the time specification" issue, or is this a bug in DataStage?