How to schedule a Cognos Data Manager job on windows scheduler?

[bhanu.samas]

Hi,
Can anyone please assist me in scheduling cognos data manager jobs on windows scheduler on client machine itself. Because there is a problem with the network services so thats why we are unable to run jobs on Cognos Server.

Thanks,

-Bhanu

[MFGF]

Sure. Which bit are you struggling with?

If you launch the Data Manager designer and open your catalog, you can right-click a jobstream and choose the "Execute" option. This will display a dialog from which you can set execution options, but more importantly it will display the command line syntax for launching the jobstream from the command line. Copy this syntax, then cancel the Execute dialog.

Now create yourself a batch file and paste this command into it. Hint - if there is a -P switch in the command syntax, remove it, as this will result in a pause saying "press return to continue" at the end of the job.

If you have other jobstreams you want to fire off, copy their command line syntax into the batch file too.

Then schedule the batch file to run using your windows scheduler ('at' or similar)

Let us know if you have any specific questions along the way.

MF.

[bhanu.samas]

Thanks for the reply.  We have installed DM Designer on windows and DM Engine, Network Services on Linux with the cognos BI server. We have issues when running the DM jobs remotely on the sever. we are getting DM-NTC-0008 connection could not be made to the target machine error.

Could you please help.

[bhanu.samas]

I tried copying th command line syntax and ran it as a batch file. but it's not working.
"c:\program files\ibm\cognos\c10dm\bin\dsremote.exe" "dm client name" -P "databuild" "ORACLE" "userid/~E66AE90E228E9BAD0052AACAD434007189@oracledb" "build name" -XFD
could you please help.

[MFGF]

Does it work when you run it from within the Data Manager designer? If not, it's not an issue with scheduling - it means you don't have your remote access set up properly.  I notice you didn't remove the -P switch from the command either - you will need to do this before you put the command into a schedule or a batch file or else the processes will never complete (assuming you get your remote access issue sorted first.

Regards,

MF.