Mark -- If the database is clean, then there could be (a) an application logic error, (b) an inconsistency in the state (contents) of the database, (c) user error, (d) a glitch in the instructions, or (e) a GT.M bug (unlikely in this context, but always possible).
The Hui configuration manual was written for VistA circa 2003. Could (e) be the first hypothesis? [Essentially, I am out of my depth troubleshooting VistA configuration issues.] -- Bhaskar On Tue, 2005-03-08 at 09:51 -0800, Mark Street wrote: > Well, I had to sleep on it last night and regroup. After a fresh look at it > this morning I killed all mumps processes, fired it all back up again and did > a clean rundown. The rundown was successful. I then did a mupip integ, the > database was clean. > > I started taskman and listener, background filers and HL filer monitor > without > a hitch, then I logged in with both D ^XUP and D P^DI to try and ENTER OR > EDIT the HL COMMUNICATION SERVER PARAMETERS. I still get dumped back to an > OPTION prompt or a GTM prompt. > > Now, I am not fixated on this issue but setting this parameter is in the HUI > config manual. Every other parameter that I had to set in the manual worked > without a hitch. > > Oh well, I am still learning. > > On Tuesday 08 March 2005 04:30, Bhaskar, KS wrote: > > If you have structural integrity errors with the database, then bets are > > off with regard to correct operation of application code. > > > > Let's take this one step at a time: What does mupip integ say when you run > > it? > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Hardhats-members mailing list Hardhats-members@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hardhats-members
