Strange Issue with scheduling a job

[Prashanth_ba]

Hi,

We are using datastage 7.5 to invoke a exe which will invoke business objects to refresh reports.

we are invoking the exe in the after job routine.

When i run this job independently, it runs fine.

When i schedule this job in datastage director, it fails.

I even tried creating a batch file, to kick start these exe's.

Even with the batch file, if i schedule the batch file in the windows server, it runs fine.

The same batch file, when i call it in the after job routine, it fails.

I even hardcoded all the parameters in the batch file and still the same result. It run fine when scheduled in the server or if the job is run independetly but failes when the job is scheduled or invoked from some other job.

I have run out of options. Any pointer would help me a lot

[ray.wurlod]

Try invoking it with the start command. To learn more, type START /? at a DOS prompt.

[Prashanth_ba]

Thanks...

I tried that also but that also didnt work....

There is a difference in Running a datastage job and scheduling a datastage job.

I am not able to figure that out.

[ray.wurlod]

Could it be something to do with (a) the user ID (and permissions), (b) quote characters (which DataStage might be stripping) or (c) environment variables?

[Prashanth_ba]

Could it be something to do with (a) the user ID (and permissions), (b) quote characters (which DataStage might be stripping) or (c) environment variables? ...

We are using admin account and hence it is not having permission issue.
Datastage is just calling the batch file name and secondly it runs fine when i run the job manually:cry:
It is creating issues when i schedule a job.

Since the code is using VB, i am thinking there might be something with the way business objects is getting invoked..

I ran few tests and one thing i found out is when there one instance of Business Objects running, it s not allowing any other instance to run...but this holds true only when i schedule a job....

There might be a difference in the way the objects are getting instantiated from scheduling to manually running a job.

I am not sure what else to try....

[Prashanth_ba]

Found out the problem but do not know what the solution is

We have defined this in the global area

Dim boApp As busobj.Application

And we are using the below statement in a private function which opens a BO report and changes the universe connection to supplied universe name

Set obj = boApp.Documents.Open(strSourceDirectory & strReportFilename, , True)

We are using two macros and once one of them is running, the second macro fails at the point when the Document.Open is being used.

If any of you have any idea on this then it will be helpfull for me

[chulett]

Wouldn't you be better off posting this question in a Business Objects forum?