Using Impromptu Scheduler. 1

[louiserutherford]

Hi,
I am using Impromptu 7 and want to schedule a task to run on a server. The help tells me to:
1. From the Tools menu, click Options.
2. Click the New Task.
3. Select the computer on which new tasks run by default.
However when I go to the New task tab there is only the option to set the time to execute the task, there is no option to select a computer. Is there any reason for this? Do I need to install anything else to enable this function?
Any help would be appreciated.

Thanks

Louise

 

[kenzolai]

Hi Louise,
When I started to use Cognos product in version 6.6, I was told by Cognos Technical support that there is no server component in Impromptu that allows for scheduling. What you need to do is to use the sscheduler to schedule your task. That is to say specify the imr files that you want to schedule from your PC and output it to printer or any other formats you want.

 

[DrSimon]

Admittedly I don't use Version 7.0, but what kenzolai says is what I do. You need to install Cognos (Impromptu & Scheduler) on that server and have Scheduler running in the foreground where it will call the local copy of Impromptu
Simon Rouse

 

[tinmar]

Hi Louise,

I find by going to the tools, scheduler then by inserting the imr as the reoccurning will do it. If you don't have a server specifically for cognos, then you may need to have your computer running when you are to schedule your reports.

 

[drlex]

You need to have scheduler running on the host computer (server, PC) on which cognos is installed, and the computer running.

If you are using user class security in your installation, remember to either give the host computer an OS sign-on in access manager or include an appropriate user and password within the macro to pass to Impromptu/PP.

From personal experience, the maintenance cycle of our IT dept and the propensity of the servers to re-boot on unknown events (but not login on) , I found that making Scheduler one of the programs on start-up and hacking the registry (*careful*) so that the server automatically logs on keeps cognos running 24/7.

lex

 

[DrSimon]

I'm very interested in running Scheduler as a service on a server which is effectively what lex is talking about. Lex - what aspect of the registry needs to be 'hacked'?
Simon Rouse

 

[drlex]

Simon,
The registry hack is to enable automatic log-on - see

http://www.wugnet.com/tips/display.asp?ID=1794

for details.
Your IT dept may be a little upset about it. And please, take a copy of the registry before tinkering.

Scheduler is being started automatically by virtue of adding a shortcut to schdl_go.exe to the startup menu; I haven't added it to services like Task Scheduler.
lex

 

[DrSimon]

Lex
Humble apologies for not thanking you for this earlier. I've been in the middle of a major implementation so I've only just noticed it, still - better late than never. It may well come in handy. As for the IT dept getting upset .. I'm in the IT dept, so we'll have to make sure that it doesn't open any security holes if we use it.
Simon Rouse

 

[drlex]

Simon,
You're welcome - thanks for the commendation.
Note that if you have a policy for changing passwords, the hack will have to be amended afterwards. This can often get overlooked if you are doing an install as a contractor rather than as a permanent employee. It's also something that might not get recreated on OS migration - everyone ready to go to Windows Server 2003?

Subliminal Thought for the Day: