We are running HR-1 on ARev 3.0. We have a dedicated index server set up that works beautifully. We have written a subroutine that runs as a daily scheduler that will be called from the post index process hook, as established in the environment record for the index server.

We have a test environment that is set up identical to our production environment, including the index server login, etc. I have modified the SYSENV record for the index server login and set up the post index process hook to call our subroutine.

However, the subroutine is not being called. I have placed a message at the very beginning of the subroutine, before any processing is done just to make sure it is being called. I never see this message. I have verified the environment record multiple times, while logged in as the index server user to make sure the hook is still in place.

I have used post index processes on other applications just fine in the past, and this has me baffled. I'm hoping that I am missing something very simple.

Thanks in advance,

Matt Sorrell

BTW, the post index hook is not being used in the production environment. We are trying to test it first before rolling it out to the users.

Matt Sorrell

Matt,

I have been using such a scenario with HR-1 for some time. The process I came up with works in tandem with a DOS batch file which cycles Arev back on in the morning.

I found that there were times when the indexing would not seem to work properly, but I think it was related to using pcAnywhere. The solution was to change the PIF settings for the mouse. By setting the mouse to exclusive mode, the problem was avoided.

I don't know if that will solve your problem or not. I suspect not. What you can do though is to query the environment settings of the session after logging in. I do this by pressing CTRL-Break and typing [email protected] at the ! prompt. You should see your subroutine listed on line 80. Also check @index.time.

Remember that when processing completes you have to return control back to input.char or indexing will not be triggered after your program finishes. [email protected] if you'd like me to send you a copy of what we use.

Finally, make sure your DOS environment variable is being set properly. I had problems for a while and couldn't figure out what was going on until I finally realized (by typing SET at a DOS prompt) that the variable was not being set properly. One of the characters was being dropped, so Arev was actually using the default INI since the one specified could not be found.

Victor,

Thanks for the info. I checked the @ENVIRON.SET variable, and my subroutine is present in line 80. Does it matter if I call the subroutine with an "X" or an "S" catalyst call? I've tried it both ways.

I'm really stumped right now.

Matt Sorrell

Don't I feel stupid. It was a "windowing" problem. When I was logging in to test the function, I was running the app in a "normal" window instead of full screen. As soon as I ran it in a full screen window, everything worked beautifully.

Fortunately, our dedicated index server doesn't run Windows, so we won't have that problem.

Matt Sorrell

View this thread on the forum...