Running Batch Mode Impromtu via 3rd Party Scheduler

[Guest_imported]

I am attempting to run a Cognos script which opens an Impromptu Report from a third party scheduler--Tivoli's Maestro. The program hangs indefinately on the 'createobject' part of the script.

If I run the script myself, everything works fine, but something with not being able to run in batch mode (as in the -n -s options for transformer) is killing the process.

Cognos swears this can be done, but no one can tell me how. I have attached the code below. Any help is appreciated.

jb

*********************************************************

sub main

dim impapp as object

SET impapp = CreateOBJECT("Impromptu.Application&quot

impapp.Visible 0

end sub

 

[griffindm]

Does the error appear EXACTLY at the CreateObject call? Does Tivoli's Maestro call other OLE server objects correctly for you with your setup?
Other wise your code looks fine.

 

[s95827m]

Did you resolve this problem? I have the same problem with ZEKE schedular.

 

[zxzzzzzz]

I also am having the same problem with Tidal Sys*Admiral....

 

[griffindm]

Try running the macro as a batch file processing, using the call to Runmac32 with the compiled macro as an arguement. This lets the Cognos product do the OLE work, and just uses the 3rd party tools to invoke it.

Dave Griffin
The Decision Support Group
Reporting Consulting with Cognos BI Tools
"Magic with Data"

http://www.decisionsupportgroup.com

 

[MattFischer222]

I had this problem. Maestro doesn't like Script Editor. It was fixed here by calling a Perl Script that used the AT command to call a batch file that called Cognos Script Editor. I believe we made some changes to security too.

 

[metrok]

This is a late post, but I think I've found a solution to this problem. Using Microsoft article 259725 as it relates to your OS (in my case W2000) I was able to get a CreateObject line to work from a Cognos macro executed from a batch file kicked off by a scheduler. This process stopped working when we went from NT to W2000. By giving more rights (add ID or group for scheduler ID) to Access Permissions (Use Custom Access Permmissions)on the Security Tab under properties for Cognos Impromptu Report it finally worked.