Randy Smith <[log in to unmask]> wrote:
>> Problem is sometimes LOGOFF will log them off other times is shows them
>>ripe for aborting; but never logs them off.
>
>As I stated in a previous reply, we experience similar problems with logging
off sessions. I'm supplying the part of of our logoff =
job that runs at 11:30pm each night to abort all sessions logged onto a
particular account.
 
!RUN MAIN.PUB .VESOFT;PARM=1
SETVAR HPAUTOCONT TRUE
SETVAR HPAUTOCONTTOPLEVEL TRUE
REPEAT
     ECHO ABORTIO LDEV=![RJOB.LDEVIN]
     ABORTIO ![RJOB.LDEVIN]
     ECHO ABORTJOB USERSET=![RJOB.FMTLOGON]
FORJOBS @.CFS&ONLINE
LISTF @[log in to unmask],ACCESS
ABORTJOB @.CFS;[log in to unmask]@.CFS
EXIT
 
I've also taken this situation a step further by installing a product
from Carolian Systems called SmartAlert. If it sees any CFS jobs or
sessions still executing after the logoff job logs off, it calls an
operator. There are still a few "bugs" with this package I'm working out
with the vendor, but we don't get blindsided first thing in the morning
with a backup that is no good. We've also been logging what DTC ports
seen to not allow logoffs and we've downed them.
 
Mike Kapsak
BFGoodrich Aerospace