My Maintain application runs .FEX procedures as part of customer billing. I need to monitor the .FEX processing command messages (record counts and error messages) as billing is running. Is there a way to get these messages to appear in a separate window without turning on debug or trace for everything?

Thanks, Kent

you should just be able to view source in the report output window. If you need more info, try using -SET &ECHO=ALL;
If there is no output window, (i.e. you are only creating a hold file) maybe you can insert a "dummy" report to get a window to open.

Kent

That's an interesting one.

If you are running the fexes from maintain with EXEC blahblah, getting the output back is straightforward. All the message output you would see when running a TABLE are in the system FOCMSG stack, a single field stack with a field of Msg which has an A80 format I think. It's what you do with this ouptut that determines what happens.

If you were to display it on a form, then the Maintain will stop, as control is passed to that form. Not good.

The only thing I can come up with, and it's late and I've had a bad afternoon, is to take the messages from the FOCMSG stack and load into a file. Another browser window can then report off this file of messages. If you put a timer on you can get it to refresh every so often. Also you can screen the messages to give only the information you want.

You may be able to get this into a frame on the same browser window, but not given that much thought.

So a file with a parent key of, say, HYYMDm and a child with line number as the key and an A80 field for the message line would do.

Then you can report the latest messages, or also go back in time if you want. Clear it out when the run is complete and the messages no longer needed.

Hope this helps.

Sorry you had a bad afternoon Alan....

Take a good glas of wine.

In the developer you can open a separate window, that gives you the running info, is that the same info that is written to the FOCMSG?

Frank

Exactly Frank

The output that you get in the DS window is the output in FOCMSG.

Bad afternoon was courtesy of Maintain as well!

If you EXEC a procedure from inside of Maintain, anything echo'd to the screen is returned in FOCMSG.MSG. You just have to be careful if you perform more than one EXEC. The data placed into FOCMSG.MSG always starts at row 1. A way around this is to use a separate stack, like MSGSTK. For example:

COMPUTE MSGSTK.MSG/A80;
EXEC Report1
Stack copy from FOCMSG INTO MSGSTK(MSGSTK.FOCCOUNT+1);
EXEC Report2
Stack copy from FOCMSG INTO MSGSTK(MSGSTK.FOCCOUNT+1);
etc...

Now, the output from each of the reports is preserved, and you can display this stack in an HTMLTable. If you just want the number of rows, you will have to loop through the stack and just take the data you want.

However, if you are launching the reports via Weblink or JavaScript, FOCMSG does not pick up the screen data.

Alan, I am sorry to hear that Maintain caused you so stress. Even though you are a Guru, you can still ask for help

Mark

Mark,

You already know the problem I had/am having - the js error........

I will check with programming this morning and see if there was any progress with that issue. Sorry!!

Mark