[Info-vax] Odd Autogen error.

[Andrew Armstrong]

On Nov 1, 2:02 pm, Wilm Boerhout <wboerhout-deletet... at gmail.com>
wrote:
> Andrew Armstrong mentioned  on 1-11-2010 17:27:
>
>
>
> > I am getting an odd error in autogen:
> > %AUTOGEN-I-BEGIN, GETDATA phase is beginning.
> > %RMS-F-CHK, bucket format check failed for VBN = 13
> > %AUTOGEN-I-BADFILE, Bad versions of SYS$SYSTEM:PARAMS.DAT may exist.
> >          We recommend that you delete all versions and start again.
> > %AUTOGEN-F-ERROR, GETDATA phase was aborted due to an unexpected
> > error.
> > %RMS-F-CHK, bucket format check failed for VBN = 0
> > %RMS-F-CHK, bucket format check failed for VBN = 0
> > There is one case on itrc that had a similar message, but it was
> > caused by a mount command in file that autogen had to read in. All of
> > my mount commands are in systartup_vms.com, so I don't think that is
> > the problem here. This is OpenVMS VAX 7.3 with no patches installed,
> > running on SIMH under windows. The SIMH drive images are on a USB
> > drive.
>
> >   The error seems to have been caused by this line here, as the the
> > next line in the log is %RMS-F-CHK, bucket format check failed for VBN
> > = 13
> > READ/END_OF_FILE=getdata_specials190 tempfile record
> > this is my modparams, don't know if that is relevant:
> > SCSNODE="DUNES"
> > SCSSYSTEMID=1028
> > VAXCLUSTER=0
> > WINDOW_SYSTEM=1
> > ADD_GBLPAGES=10000
> > ADD_GBLSECTIONS=100
> > ADD_NPAGEDYN=800000
> > ADD_NPAGEVIR=800000
> > MIN_SPTREQ=6000
> > I am changing the SCSYSTEMID from 1029 to 1028 as I added wrong, and
> > adding the GBLPAGES,GBLSECTIONS,NPAGEDYN,NPAGEVIR, and the
> > MIN_SPTREQ=6000 as according to the instructions on
> >http://www.wherry.com/gadgets/retrocomputing/vax-simh.html. I have run
> > these instructions in the past, both on my VAX, and on several
> > different SIMH emulated vax, so I think that they are good...
>
> As
>
> $ SEARCH SYS$UPDATE:AUTOGEN.COM "FILE =",TEMPFILE
>
> suggests, the file at hand is probably SYS$SYSTEM:VMSPARAMS.DAT
>
> Inspect this file carefully. In most installations, it is empty but it
> may contain special parameter sets added by installed products. It may
> also contain garbage, or be corrupt and unreadable. Find the cause and
> correct it. You can also create an empty file with that specification.
> Use CREATE/FDL, including the following in the FDL file
>
> FILE
>          ORGANIZATION            sequential
> RECORD
>          CARRIAGE_CONTROL        carriage_return
>          FORMAT                  variable
>          SIZE                    1024
SYS$SYSTEM:VMSPARAMS.DAT was corrupt, and was the cause of the
problem. Thanks everyone for your help.