VMS Problem, please help.. - test-drb@ccmp.vtda.org

7 Apr 2012

Jonas Otter wrote:

...
  On Fri, 6 Apr 2012 14:30:23 +0200, Holm Tiffe <holm
at freibergnet.de> wrote:
 Hi,

I've tried to compile the VIM-7.3 Sources on my freshly installed VS4000,
and entered a pitfall here.
Since the C Compiler was complaining that the virtuel memory is exhaustet,
I'veed the PGFLQUOTA for the user to 104826 and the VIRTUALPAGCNT SYSGEN
Value to 2097152 (max was displayed as 4194304)
I've let run autogen and ebooted.

Now the system ewfuses to boot:

%SYSBOOT-W-WS default and quota raised to PHD+MINWSCNT
%SYSBOOT-F-VASOV, system virtual address space exeeded
?06 HLT INST
    PC= 00009631 PSL=041F0000  
 From the VMS error messages manual at
 http://h71000.www7.hp.com/doc/73final/6023/6023pro_019.html :

    VASOVF, system virtual address space limit exceeded

 *Facility:*SYSBOOT, System Bootstrap Facility
 *Explanation:*The combination of SYSGEN parameters used to specify 
 various capacities within the operating system have pushed the size of 
 the operating system address space over the limit allowed by the VAX 
 architecture.
 *User Action:*Reduce one of the parameters (BALSETCNT or VIRTUALPAGECNT 
 (VAX only)) that contribute to the virtual address space size required 
 by the OpenVMS system. By using AUTOGEN to set these values for your 
 system, you avoid selection of parameter combinations that cause system 
 space to overflow its architectural boundaries.

 To recover, perform a conversational boot (i.e. the boot process will 
 let you modify system parameters to recover from a situation like 
 yours). It is described here:
 http://h71000.www7.hp.com/doc/82final/aa-pv5mj-tk/00/00/34-con.html

 Use the "booting with default system parameters" section. You probably 
 then need to reduce VIRTUALPAGECNT below the value you have set (which 
 gives a 2GB virtual address space) because the VAX architecture allows 
 max. 2 GB virtual memory and you are probably just over the limit.

 The VMS documentation is excellent, you will find it online here:
 http://h71000.www7.hp.com/doc/

 and this is a good manual to start with:
 http://h71000.www7.hp.com/doc/82FINAL/aa-pv5mj-tk/aa-pv5mj-tk.HTMl
 (you will find it from the page above by following the link "OpenVMS 
 Operating System" to the left.

 /Jonas 
Ok, THX guys,
I've managed to get this thing running again, don't ask me how :-)

But my first problem, the cause of the fiddling with the system paramaters
persists.

This is the VIM73-69 source for VMS:

   The adequate command for mmk is:

        mmk /descrip=Make_vms.mms

     NOTE: Because of empty /auto/config.h (needed for Unix configure)
build
     will fail with very strange messages. Therefore before building, it is
     recommended to make one clean up, to prepare everything for OpenVMS
     development. The command is:

 Buffer: INSTALLVMS.TXT                              | Write | Insert |
Forward 

$ mms /descrip=Make_vms.mms

using DECW/Motif/XPM environment.
creating OS_VMS_MOTIF.OPT file.
cc
/def=("FEAT_BIG","HAVE_CONFIG_H","FEAT_GUI_MOTIF","HAVE_XPM"
 )
/opt/prefix=
all  /include=([.proto],decw$include:) BLOWFISH.C
%CLI-F-TEXT, Compiler abort - virtual memory limits exceeded.
%SYSTEM-F-ABORT, abort
%MMS-F-ABORT, For target BLOWFISH.OBJ, CLI returned abort status:
%X0000002C.
-SYSTEM-F-ABORT, abort
$ 

I've googled for the error and found this:

http://www.jcameron.com/vms/em12.htm

...that was the beginning of the problem.

$ set proc/priv=all
$ r authorize
UAF> sh holm

Username: HOLM                             Owner:  Holm Tiffe
Account:                                   UIC:    [200,201] ([HOLM])
CLI:      DCL                              Tables: DCLTABLES
Default:  DKA0:[HOLM]
LGICMD:   LOGIN
Flags: 
Primary days:   Mon Tue Wed Thu Fri        
Secondary days:                     Sat Sun
No access restrictions
Expiration:            (none)    Pwdminimum:  6   Login Fails:     0
Pwdlifetime:         90 00:00    Pwdchange:   3-APR-2012 20:05 
Last Login:  7-APR-2012 11:40 (interactive),  7-APR-2012 11:34
(non-interactive)
Maxjobs:         0  Fillm:       300  Bytlm:        32768
Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
Maxdetach:       0  BIOlm:        40  JTquota:       4096
Prclm:           2  DIOlm:        40  WSdef:          256
Prio:            4  ASTlm:       100  WSquo:          512
Queprio:         0  TQElm:        40  WSextent:      1024
CPU:        (none)  Enqlm:       200  Pgflquo:      40960
Authorized Privileges: 
  ACNT      ALLSPOOL  ALTPRI    AUDIT     BUGCHK    BYPASS    CMEXEC CMKRNL
  IMPERSONATDIAGNOSE  DOWNGRADE EXQUOTA   GROUP     GRPNAM    GRPPRV IMPORT
  LOG_IO    MOUNT     NETMBX    OPER      PFNMAP    PHY_IO    PRMCEB PRMGBL
  PRMMBX    PSWAPM    READALL   SECURITY  SETPRV    SHARE     SHMEM SYSGBL
  SYSLCK    SYSNAM    SYSPRV    TMPMBX    UPGRADE   VOLPRO    WORLD
Default Privileges: 
  NETMBX    TMPMBX
UAF> 

So what should I do next to try to compile that VIM source (hopefully w/o
to destroying the system again)

The VS4000 has 64 Mbytes of Ram, I think that should be sufficient to
compile something like this, so it seems to me that some quote values are
the problem.

Kind Regards,

Holm

-- 
      Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, 
     Freiberger Stra?e 42, 09600 Obersch?na, USt-Id: DE253710583
  www.tsht.de, info at tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741