From what I understand their most current version does NOT include the
files that were sent to me.  This is something they put in that was
specific for our problem, but I believe if it works that it sure should
become part of their general release.  One other thing I was told was
that the 'nscontrol killsess' command is not supported (??) and that may
be a reason it would not be included.  We have had the same problem you
have with abortjob/logoff hanging LAN sessions.  In most cases, it
doesn't try and abort them at all it seems.  Hopefully, the latest
version of Security/3000 combined with the 2 'beta' files will help.
 
Still waiting for a fix, wilson.
 
FROM:
 
       Wilson Wong
       Communications Technology Center
       3101 Northup Way, Suite 100
       Bellevue, WA  98004
       (206) 803-9764
       [log in to unmask]
 
On Mon, 26 Feb 1996 [log in to unmask] wrote:
 
> Wilson - your comment re: the 'nscontrol killsess' command inclusion by
> VESoft into the LOGOFF code is interesting because we specifically
> exclude VT sessions ($NOLANABORT) from our LOGOFF scripts due to a
> long-standing problem of having :ABORTJOB occasionally hang LAN
> sessions which are only then knocked off by a system restart.  If
> VESoft is using 'nscontrol killsess' on these sessions, this might
> solve this particular issue for us.  Did they mention whether this
> would become part of their general release versions?
>
> By the way, we've developed a command file for our operators which
> allows them to kill all VT-connected sessions by using the 'nscontrol
> killsess=" command.  They run this to clean up VT connections prior to
> an MPEX %ABORTJOB for DTC sessions.
>
> =======================================================================
> Lee Gunter                           Voice:  503-375-4498
> HMO Oregon                             FAX:  503-375-4401
> E-Mail:  [log in to unmask]  Private E-Mail:  [log in to unmask]
> =======================================================================
>
> The opinions expressed, here, are mine and mine alone, and do not
> necessarily reflect those of my employer.
>
>
>
>
>
>
> ______________________________ Reply Separator _________________________________
> Subject: Re: Vesoft - Security 3000 not always working
> Author:  Wilson Wong <[log in to unmask]> at ~INTERNET
> Date:    2/26/96 9:40 AM
>
>
> We too are using Security/3000 and have been having problems with the
> LOGOFF feature.  Some of our users would receive the abort warning
> message but never be aborted similar to what you are reporting.  It
> became a much bigger problem when the warning messages began filling the
> system console buffers and eventually locked up the system.  After
> numerous system lockups I called both the HP Response Center and Vesoft.
> To make a VERY long story short, VESOFT has sent me a new logoffab.pub
> and clogoff.backg file that has additional code for aborting a user.  I
> believe they added a nscontrol killsess command.  These 2 new files along
> with the code to only attempt to abort a user a certain number (2?) of
> times may solve the problem.  I tested it briefly and it seemed to be
> promising, but I am waiting for Vesoft to send me their latest version so
> I can try it with the 2 new files.
>
> FROM:
>
>        Wilson Wong
>        Communications Technology Center
>        3101 Northup Way, Suite 100
>        Bellevue, WA  98004
>        (206) 803-9764
>        [log in to unmask]
>
> On Mon, 19 Feb 1996, Carl E. Ruth II wrote:
>
> > I am using SECURITY/3000 version 25. from VESOFT software.  The
> > software is running on a HP955 with an operating system of mpix v5.0.
> > Our main application software is  MANMAN  from ASK software version
> > 7.1.
> >
> >  We have had the Security package for a couple of years; but, we used
> > it mainly for logon menu's and not much of anything else.  Well now we
> > want to use the LOGOFF features and we canna get everything to work
> > correctly consistently.
> >
> > At the bottom of this posting you will find our current
> > LOGOFF.DATA.VESOFT configuration file.
> >
> > My main concern is group three (3).  With group three (3) we have
> > defined a large group of users who might still be logged on our system
> > from 01:00 to 03:00am and if they show no activatiy for 5 minutes they
> > are to be aborted.  Problem is sometimes LOGOFF will log them off
> > other times is shows them ripe for aborting; but never logs them off.
> >
> > What am I doing wrong?
> >
> >  Why does Security sometimes show these sessions "RIPE FOR ABORTING"
> > yet never log them off?
> >
> > Why does Security sometimes take these exact same sessions and abort
> > them like it is supposed to.
> >
> > Is anyone running Security and ASK together?
> >
> > TIA for any help or suggestions.
> >
> > Carl R.
> > Senior Flunky :-)
> >
> > The streams job we use to start LOGOFF is as follows:
> > !job logoff,manager/xxxxxxxx.fluids,mpex;outclass=140,8
> > !mpex
> > Sec backg startjob
> > Sec backg start,logoff
> > Exit
> > !eoj
> >
> >
> >
> > LOGOFF.DATA.VESOFT:
> >
> > $MESSAGE "YOU DID NOT FINISH LOGGING OFF LAST NIGHT!"
> > $PAUSETIME 420
> > $TIMEOUT 14400
> >      $TERMINALS INCLUDE 49
> >
> > $TIMEOUT 19800
> >      $USERS INCLUDE [log in to unmask]
> >
> > $TIMEOUT 300
> >      $USERS INCLUDE TUBE.MANMAN
> >      $SELECT "BETWEEN (CLOCK, 5PM, 3AM)"
> >
> > $TIMEOUT 300
> >      $USERS INCLUDE [log in to unmask]
> >      $USERS INCLUDE [log in to unmask]
> >      $USERS INCLUDE [log in to unmask]
> >      $USERS INCLUDE [log in to unmask]
> >      $USERS INCLUDE [log in to unmask]
> >      $USERS INCLUDE [log in to unmask]
> >      $USERS INCLUDE [log in to unmask]
> >      $USERS INCLUDE TIMEKEEP.MANMAN
> >      $SELECT "BETWEEN (CLOCK, 1AM, 3AM)"
> >
>
>