Path: utzoo!utgpu!jarvis.csri.toronto.edu!me!radio!helios!root
From: root@helios.toronto.edu (Operator)
Newsgroups: comp.os.vms
Subject: Re: Weirdness from SYSGEN
Message-ID: <557@helios.toronto.edu>
Date: 2 May 88 21:48:38 GMT
References: <8804301802.AA01586@ucbvax.Berkeley.EDU>
Reply-To: sysruth@helios.physics.toronto.edu (Ruth Milner)
Organization: University of Toronto Physics/Astronomy Computing Consortium
Lines: 27

In article <8804301802.AA01586@ucbvax.Berkeley.EDU> OWEN@AUDUCVAX.BITNET (Larry Owen) writes:
>Has anyone ever seen this very inappropriate behavior before?  Any ideas
>as to what would cause this?
>
>$ run sys$system:sysgen
>SYSGEN>  USE CURRENT
>%SYSGEN-W-SETMIN, value set to minimum for parameter IJOBLIM
>SYSGEN>
>

IJOBLIM is the parameter that controls the number of interactive jobs (i.e. 
logged-in users). The "minimum" in this case is 1. What it means is that, at 
some point in history, someone did a SET LOGIN/INTERACTIVE=1 and, at some 
point after that, did a USE ACTIVE and WRITE CURRENT in SYSGEN (or some other 
combination that resulted in this value being stored). Therefore, when you go 
to USE CURRENT again, the minimum value is still there. It is of course easy 
to fix. Just USE CURRENT, SET IJOBLIM nn (pick your usual number), and WRITE 
CURRENT. 

The key here is that there is a DCL command to modify this parameter.
Most other parameters cannot be modified so easily.

-- 
 Ruth Milner          UUCP - {uunet,pyramid}!utai!helios.physics!sysruth
 Systems Manager      BITNET - sysruth@utorphys
 U. of Toronto        INTERNET - sysruth@helios.physics.toronto.edu
  Physics/Astronomy/CITA Computing Consortium