dhagen,
I think you are correct, unfortunately my Perl knowledge is pretty limited so I don't know how to do this. If someone out there has done this, please let me know.

TexasStingray,
They are on different boxes.

Jim,

As TS intimated, that will make a difference as the MRE fexes reside on the Client under IBI/WBEFOCUSnn/basedir whereas the fexes under the app path reside on the Reporting Server (hence two different sign-ons in Dev Studio to access each one).

T

Tony & TS,

Sorry about the confusion, but after reading Tony's post, the client and the reporting server must be on the same box. I can look at our webfocus box and the app path fexes are in ibi/apps folders and the MRE fexes are in the ibi/WebFOCUS52/basedir folders.

By default, we started developing most of our fexes in MRE. I've been trying to decide if we should be developing in the app path folders. We currently are using VMS Focus mostly in a batch mode. We would like to convert all of this to WebFocus so I'm trying to create a batch type environment in WebFocus. If you have any advise in this area, I'm listening.

Thanks for the posts, and again, sorry for the confusion.

Jim

Jim,

The easiest way would be to run everything through report caster. That way the reports can exist either in MRE or on the server. The results can then be mailed directly to the user requesting the schedule.

In WF52, you can use a routine called DSTRUN to go from html prompt page to load the request into the report caster schedule.

My two cents.

dhagen,

We currently use report caster for most of our scheduling. The biggest problem I have with RC is that I haven't figured out how to save the focus messages that are created when the fex runs. This information is necessary for trouble shooting problems with scheduled jobs. In the old focus environment you could filedef SYSPRINT to a log file and you had it. This doesn't seem to work in WebFocus or at least I can get it to work. If you could solve this for me, I would be very excited.

Jim