I have a client in Ohio on mvBase with Accuterm clients. Whenever anyone
terminates their Accuterm program, their port is frozen, and the only way
they can get back on, is to shutdown/reboot mvBase.

This has to be a simple fix, but I'm in Colorado, and can't determine what
their port statuses are, whether they have nailed ports or what. Can someone
advise me on what to do in this situation? I can provide more info if
needed. They just want to be able to preserve their ports.

Thanks,

Ed

"Ed Sheehan" wrote
mvBase "Exit" verb {directly or as part of a menu} Most users think it's ok to get to
a logon greeting then just yank the plug, but I'd suspect that would leave a relic
session.
Umm, that's only a guess -- am not using mvBase at our shop. Does mvBase run as an
application on top of another operating system, like Linux or Windows? Does it
have reset-user and reset-port commands, and if so do they help reclaim a lost port?

Also, try connecting using windows TELNET. I've found if mvBase has used
up all the user licences, TELNET will reveal a 'no user licences
available' type message that for some reason AccuTerm does not see.

Hi Ed,

I don't actually use Accuterm ( mvTERM does everything we want ) but what I
have set in the USER-COLD-START is

AUTO-LOGOFF { accountname } (D or

AUTO-LOGOFF 1-100 (D

This seems to work well for us when users just close mvTERM with logging off
first

There is also the AUTO-DISCONNECT - but not really used that

Craig

"Ed Sheehan" <NOedsSPAM (AT) xmission (DOT) com> wrote

I did mean to say

This seems to work well for us when users just close mvTERM without logging
off first

Craig

"Craig" <xxxxjjjj (AT) erferf (DOT) com> wrote

Got it. Thanks for your post. They'll try it near their next reboot cycle.

Ed

"Craig" <xxxxjjjj (AT) erferf (DOT) com> wrote

Hi Ed,

You don't have to wait for a reboot you can just issue the commands from
SYSPROG they stay active until a reboot! If they work for you then you can
add them to the USER-COLD-START.

Craig

"Ed Sheehan" <NOedsSPAM (AT) xmission (DOT) com> wrote

Because a locked port means a reboot of the whole system to get it back, and
because I can't guarantee them that this will work, they want to wait until
a scheduled reboot to try this, so if it doesn't work they don't have to do
an unscheduled reboot.

Ed

"Craig" <xxxxjjjj (AT) erferf (DOT) com> wrote