  SET LOGINS problem in batch? 
 The Question is:
 
We have a client using Visibility.  We are trying
to setup a monthly job for them.  When the monthly
job runs they need to set it so that no users
can logon to the system.  The job is setup
something like the following:
 
   Get user input
   Zap
   set logins/inter=0
   submit monthly_jobs.job
 
The job also is being run in batch mode.
When this runs the job stops after executing the
set logins.  I've also tried
   set logins/inter=1
but this still didn't help.
 
Should we run the set logins as a seperate
process before running our month end process?
 
We are new to VMS so this may be a simple
question but he has us stumped.  Any
help would be greatly appreciated?
 
Thank You
 
Robert Haack
 
 The Answer is:
 
  Use SET NOON or similar ON-based error trapping to determine the cause
  of the problem in (or near) the execution of the SET LOGINS command.
  In particular, look for privilege or other problems with the command.
 
  The Wizard has just tried using SET LOGINS/INTER=64 in a batch job,
  and it works as expected.  The following example was used:
 
    $ ty x.com
    $ set noon
    $ oldvfy = f$verify(1)
    $ set login/inter=64
    $ show default
    $ exit
    $
 
  Another approach would be to create a system-wide logical name, and
  check for it in the system-wide login.  Users could log in, but if
  the logical name is found they will receive the translation of the
  logical name (a reason, for instance), and then be logged out.  The
  user interface application(s) or procedure(s) could also check for
  the same logical name at appropriate points in the user processing.
 
  Please contact the customer support center if unable to resolve this
  problem.
 
