We have one instance of Report Caster (ver 7.1.6) that connects to 2 reporting servers - both version 7.1.7, one of which is on the mainframe and the other on AIX. Different applications use one or the other reporting server. The Maximum Threads setting on RC is set to 25, and the Maximum Connection setting on each server is set to 10. However, RC send the first 25 jobs in its queue to whichever server the application uses, regardless of whether the server can run the job or not.

We want to be able to schedule jobs to both servers to run simultaneously. Any one have any ideas on how to achieve this?

Based on my understanding this won't work proper. The report will run based on the time specified in the server. Whichever runs fast, that will distribute the report. And also you need to configure the server with your mail exchange server.

Hope this helps,

I'm a little confused as to what you're trying to do. An application will only work on a single reporting server so a single job will only run on the server where it exists. When you say "whether the server can run the job or not" are you talking about available agents on the reporting server?

In my case, Application1 runs on the MVS server and Application2 runs on the AIX server. Both use the same Report Caster Distribution server. What I want to have happen is that Report Caster submit jobs to both servers, based on the Maximum Connection parameter of the Data Server (as configured in the RC Console). So, if the first 500 reports are for the AIX server, and the next 200 for the MVS server, it would submit report nos 1-10 to the AIX server and skip over the next 490 reports (since AIX server is at capacity) and send report nos 501-510 to the MVS server. All 700 reports are scheduled for the same time, with the same priority level.

It won't work that way because they all use the same queue within Report Caster. They are dished from that queue in the order they are added - regardles of the capacities of the Reporting servers. You would have to use separate queues which, in this case, would require separate instances of ReportCaster.

Darin Lee. Thanks for the info. That is something I wished to avoid if possible. Maybe I'll open it as an NFR.

Good idea. We have a very similar configuration (server on Z/OS and Linux) and could probably use that feature as well. Don't know how it would be done but we can let them worry about that.

Darin. Just FYI. I spoke to IBI about this, and opened it as an NFR yesterday. For the moment, I'm probably going to have to use a separate installation of RCaster.