Logging GFE's (AREV Specific)
At 22 MAY 1998 12:05:14PM Dave Bennett wrote:
Because of users, not informing us of gfes and restoring files. I would like to record any gfe error message that displays on the system. Thank you in advance.
At 22 MAY 1998 06:11PM Victor wrote:
One method is to modify the following records in SYSMESSAGES:
FS495
FS493
FS125
FS127
FS126
FS494
FS124
For each one, change the type (field 1) to "C". This changes the message to one which performs a catalyst call. The code and command then go in the field where the message normally goes separated by a @VM or "|". Look at @ANS for passed values. Send your final message you wish the user to see back to @ANS.
Read the values section of the documentation for MSG in the Rbasic manual for more detailed information.
At 01 JUN 1998 01:25PM Dave Bennett wrote:
I tried the change of the first field in the message table and when the system calls the message for a gfe it still just calls the message using code "A" not reading the first field. Any other suggestions?
At 01 JUN 1998 04:09PM Victor Engel wrote:
Yeah. You're right. Actually, it replaces whatever is there with "RE" in order to solicit a response to the message. My idea works for MSG calls, but it evidently does not work for io error messages. If it were me, I'd try one or both of these ideas.
* I think the message is being displayed by STDIOERR, which in turn calls MSG. I'd try to figure out the calling syntax for this routine and put a shell around it in order to trap what you need.
* Put an MFS on SYSMESSAGES. This one can be very tricky, because one false step will result in an infinite loop, since an error in the MFS could trigger a read of the SYSMESSAGES file to report an error. Better yet, put an MFS on the MESSAGES file to avoid this problem.