1 INFO-VAX	Sun, 23 Jul 2000	Volume 2000 : Issue 408       Contents:? Re: %SYSINIT-E, Error mounting system device, status = 000008c4 ? Re: %SYSINIT-E, Error mounting system device, status = 000008c4 ? Re: %SYSINIT-E, Error mounting system device, status = 000008c4 ? Re: %SYSINIT-E, Error mounting system device, status = 000008c4 ' Re: determining free disk space via DCL  Re: Editor Commands  Help default boot & time Re: Help default boot & time Re: Help default boot & time Re: Help default boot & time$ New SKC Postings on www.acersoft.com" Re: Undocumented commands in UCX ?" Re: Undocumented commands in UCX ?  F ----------------------------------------------------------------------  % Date: Sat, 22 Jul 2000 17:50:29 -0500 / From: "Dwight Brooks" <dbrooks@prosoftauto.com> H Subject: Re: %SYSINIT-E, Error mounting system device, status = 000008c4: Message-ID: <8ld8j0$3bu0$1@newssvr05-en0.news.prodigy.com>    I agree it is most likely ODS-5.H However, this disk boots on a VAX 4000-90 as it is a single disk system.I A guy from another company mentioned ODS-5 supports new/different cluster  sizes.) I'm not sure what affect that has either. I It almost seems to me that the bootstrap or some firmware/microcode is an  old version of VMS.  Does that make sense?  -Dwight   : "JF Mezei" <jfmezei.spamnot@videotron.ca> wrote in message$ news:3979D9E3.E9CC1A@videotron.ca... > Dwight Brooks wrote:A > > On my VAXes, I'm running VMS 6.2 and I cannot mount the disk. 0 > > I get illegal volume structure or something.K > > However, if I take the disk to an Alpha running VMS 7.2, I can mount it  > > and read it. > J > My initial reaction is that your drive is ODS-5 structure which can only be" > understood by VMS 7.2 and above. > I > Can VMS boot from ODS-5 disks, are are these only for secondary disks ?  > F > Since the drive is the boot drive, it woudl be logical to state (but perhaps K > not absolutely sure) that if the drive is in ODS-5 format, that the OS it H > contains would be 7.2, and as such, when you boot from that drive, 7.2 would E > be used and would have no problems with ODS-5, unless VMS 7.2 still  requires > ODS-2 as boot disk ?   ------------------------------  % Date: Sat, 22 Jul 2000 20:46:36 -0400 * From: David A Froble <davef@tsoft-inc.com>H Subject: Re: %SYSINIT-E, Error mounting system device, status = 000008c4- Message-ID: <397A406C.905746E2@tsoft-inc.com>    Dwight Brooks wrote: > " > I agree it is most likely ODS-5.J > However, this disk boots on a VAX 4000-90 as it is a single disk system.K > A guy from another company mentioned ODS-5 supports new/different cluster  > sizes.+ > I'm not sure what affect that has either. K > It almost seems to me that the bootstrap or some firmware/microcode is an  > old version of VMS.  > Does that make sense? 	 > -Dwight   M There is some mis-information here.  VMS 7.2 and above, on both VAX and Alpha J support small cluster sizes on large disks.  Pre-V7.2 does not support theM smaller cluster sizes.  VMS V7.2 and above on Alpha supports ODS-5.  VAX does P not support ODS-5.  All this is depending on a memory that isn't always correct. :-)   N I'm guessing you may have a large disk with a clustersize supported only underI V7.2 and above.  Also, a VAX system disk and an Alpha system disk are not N compatible.  So, if the disk boots (not mount) on a VAX 4000 model 90, then isL is a VAX system disk, and might have the small clustersize that requires VMS V7.2.   P As for why it won't boot on a VAX 4000 model 105A, I have no clue.  What are the messages you get?    Dave   --  4 David Froble                       Tel: 724-529-04504 Dave Froble Enterprises, Inc.      Fax: 724-529-0596> DFE Ultralights, Inc.              E-Mail: davef@tsoft-inc.com6 T-Soft, Inc.  170 Grimplin Road  Vanderbilt, PA  15486   ------------------------------  % Date: Sat, 22 Jul 2000 21:16:09 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> H Subject: Re: %SYSINIT-E, Error mounting system device, status = 000008c4, Message-ID: <397A4757.BF4CDE7A@videotron.ca>   David A Froble wrote: O > There is some mis-information here.  VMS 7.2 and above, on both VAX and Alpha L > support small cluster sizes on large disks.  Pre-V7.2 does not support theO > smaller cluster sizes.  VMS V7.2 and above on Alpha supports ODS-5.  VAX does  > not support ODS-5.    G Actually, it is not VAX that does not support ODS-5, it is VMS-VAX that  doesn't include support for it.   N Seems to me that if the hardware gets to a SYSINIT stage, it means that it hasK found , acceessed and loaded the bootstrap from the hard drive and begun to F load the operating system, at which point it would become a VMS issue.  R On the other hand, the poster stated that the drive boots fine on another machine.  J Question: is it possible that on the machine on which the drive works, theL machine actually boots off another node in a cluster, and it is only when itJ attempts to access the pagefile(s) that it attempts to mount the drive and% realises that the drive is not right.   I Having the actual boot logs from the time you do the B" command until the  error message would be usefull.   M Also, if you can mount the drive on a system, doing a SHOW DEV /FULL and post % the log of that would also be useful.    ------------------------------  % Date: Sun, 23 Jul 2000 00:05:18 -0400 2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>H Subject: Re: %SYSINIT-E, Error mounting system device, status = 000008c47 Message-ID: <200007230005_MC2-AD22-6F5F@compuserve.com>            Dwight,   E         There have been some reports that /IMAGE backups made without J /NOALIAS can't be restored properly.  The reports I've seen have involved=  aF backup made on VAX/VMS V6.2 and restored under VMS V7.2.  HELP and the2 manuals say that "/NOALIAS is highly recommended".  G         I don't know where to tell you to go from here.  I thought that H SHOW DEVICE /FULL would show the structure level but it does not; I justG tried it on my Alphastation!  There does not seem to be any easy way to G find out what the structure level is.  It's a problem I've never had to J deal with.  It will be a cold day in hell before I initialize a volume as=  G ODS-5; I have no need for DOS/Windows compatibility in the area of file D names.  In sixteen years I've never needed to mount an ODS-1 volume.  E         My first thought was that the booting problem was a matter of J SYSGEN parameters but that was before I thought to decode the hexadecimal=  H status in the  subject line (the message body is a better place for thatJ sort of thing IMHO).  It may still be a matter of SYSGEN parameters so yo= u H might try a conversational boot and USE DEFAULT and then WRITE active toH boot with a generic set of parameters that is supposed to boot anything.  E         If you have software support, it's time and past time to call  Compaq and ask for help.    ' Message text written by "Dwight Brooks"  >  Richard,< My customer is using /IMAGE but I didn't ask about /NOALIAS. Hwo would that affect it? = On my VAXes, I'm running VMS 6.2 and I cannot mount the disk. , I get illegal volume structure or something.G However, if I take the disk to an Alpha running VMS 7.2, I can mount it  and read it.< Someone else mentioned the ODS structure but my question is:@ The ODS is based on the O/S, why can this disk boot on a 4000-90 and not a 4000-105?  -Dwight  <    ------------------------------  % Date: Fri, 21 Jul 2000 14:58:52 +0100 ' From: Adrian Birkett <abirkett@csc.com> 0 Subject: Re: determining free disk space via DCL' Message-ID: <3978571B.7BCEBE71@csc.com>    Try along the lines of :  : $ write sys$output f$getdvi("sys$sysdevice:","freeblocks") 121383 $    just replace the disk name.    Regards,   Ade    operagost@my-deja.com wrote:  H > Is there a lexical or something that I can use to determine free spaceH > on a disk? The problem is that, using VMS 5.5-2 we're limited to ~8 GBJ > disks. What we're doing is storing Oracle archive logs on a raid-5, thenI > moving the older ones to another disk with a daily batch file. However, B > sometimes database activity increases and the logs overflow diskH > capacity. I'd like to optimize the use of this array and avoid lockingF > up the archiver by moving files to a second, non-redundant disk only > when necessary.  > ( > Sent via Deja.com http://www.deja.com/ > Before you buy.    ------------------------------  # Date: Sat, 22 Jul 2000 21:05:33 GMT  From: rinkjustice1@my-deja.com Subject: Re: Editor Commands) Message-ID: <8ld2an$npp$1@nnrp1.deja.com>   G > In article <396d6a06.78564810@news.dal.ca>, hx_101@hotmail.com (Horse 
 Nuts) writes: H > :Looking for a reference to editor commands!!! Anyone have any links??  9 You'll find a good vi(m) tutorial and list of commands at  http://www.hardcorelinux.com.    Hope this helps.    & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  # Date: Sun, 23 Jul 2000 00:58:44 GMT  From: unixguys@my-deja.com! Subject: Help default boot & time ( Message-ID: <8ldfvv$fc$1@nnrp1.deja.com>  E I picked up a 4000/600 recently, loaded VMS 7.2 etc, but I find after G setting default boot device, it doesn't seem to save after a cold boot.   F Also does VMS "always" ask for the time when booting up or are both of3 these problems related to a dead internal battery ?   B If so does anyone know where this would be located in the machine.  G Also when mounting the cd via mount dka400 vaxvms072 the cd mounts with E the message %MOUNT-I-MOUNTED, VAXVMS072 mounted on _HOBBY$DKA400: but G for the life of me I cannot find on the filesystem where it is mounted, F so what is the trick to mounting and accessing the drive to read files etc. on the cd. ?    Thanks in advence.    & Sent via Deja.com http://www.deja.com/ Before you buy.    ------------------------------  % Date: Sat, 22 Jul 2000 21:57:34 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> % Subject: Re: Help default boot & time , Message-ID: <397A5109.B47F2CC3@videotron.ca>   unixguys@my-deja.com wrote: G > I picked up a 4000/600 recently, loaded VMS 7.2 etc, but I find after I > setting default boot device, it doesn't seem to save after a cold boot.  > H > Also does VMS "always" ask for the time when booting up or are both of5 > these problems related to a dead internal battery ?   N I beleive that both would be symptoms of a failed battery. You may wish to letM the machine run for a few days to recharge the batteries (on older vaxes, the ) batteries were nickel cadmium batteries).   I > Also when mounting the cd via mount dka400 vaxvms072 the cd mounts with G > the message %MOUNT-I-MOUNTED, VAXVMS072 mounted on _HOBBY$DKA400: but I > for the life of me I cannot find on the filesystem where it is mounted,    CD :== "SET DEF"J CD DKA400:[000000]    will get you to the root of that drive's filesystem.   ------------------------------  % Date: Sat, 22 Jul 2000 21:25:53 -0500 7 From: "David J. Dachtera" <djesys.nospam@earthlink.net> % Subject: Re: Help default boot & time - Message-ID: <397A57B1.C4DE03ED@earthlink.net>    unixguys@my-deja.com wrote:  > G > I picked up a 4000/600 recently, loaded VMS 7.2 etc, but I find after I > setting default boot device, it doesn't seem to save after a cold boot.    Yeah. Could be a bad battery.   A I'm a bit fuzzy on VAX 4000/600 (it IS a VAX, right?), but if the G commands are at all similar to the Alpha console, you should be using a E command like "set bootdef_dev dka300" if dka300 is your boot (system) 3 disk. Otherwise it might just be "SET BOOT DKA300".    H > Also does VMS "always" ask for the time when booting up or are both of5 > these problems related to a dead internal battery ?  > D > If so does anyone know where this would be located in the machine.  D Again, could be a symptom of a bad battery. Could also be one of the system parameters. See:    $ mc sysman ' SYSMAN> help param param timepromptwait    ...or...   $ mc sysgen " SYSGEN>  help param timepromptwait   I > Also when mounting the cd via mount dka400 vaxvms072 the cd mounts with G > the message %MOUNT-I-MOUNTED, VAXVMS072 mounted on _HOBBY$DKA400: but I > for the life of me I cannot find on the filesystem where it is mounted, H > so what is the trick to mounting and accessing the drive to read files > etc. on the cd. ?   C Well, remember that unlike UN*X, VMS views disk volumes as separate B entities. The closest parallel would be a drive letter in DOS. TheG "root" directory on each disk is [000000] (six zeroes), though VMS also 7 supports the old RSX-like and RSTS/E-like syntax [0,0].   3 To "recurse" directories, use an ellipsis, like so:   , $ DIRECTORY/SIZE=ALL/DATE DKA400:[000000...]   --   David J. Dachtera  dba DJE Systems  http://www.djesys.com/  : Unofficial Affordable OpenVMS Home Page and Message Board: http://www.djesys.com/vms/soho/    ------------------------------  % Date: Sat, 22 Jul 2000 23:43:47 -0400 - From: JF Mezei <jfmezei.spamnot@videotron.ca> % Subject: Re: Help default boot & time , Message-ID: <397A69F1.AEA47A8C@videotron.ca>   "David J. Dachtera" wrote:
 > $ mc sysman ) > SYSMAN> help param param timepromptwait   H For some reason, the VMS gods have decided to change it with VMS 7.2 ...  % SYSMAN> help sys_param timepromptwait    ------------------------------  # Date: Sun, 23 Jul 2000 01:45:26 GMT 0 From: "Terry C. Shannon" <shannon@world.std.com>- Subject: New SKC Postings on www.acersoft.com & Message-ID: <Fy4nAx.4EJ@world.std.com>  I There's recent material on the new GS-Series, the Himalaya S74000 series, K and Compaq's ZLE strategy posted on http://www.acersoft.com. There's also a ; 1.25MB PPT file of my July 13 OZTUG presentation in Sydney.   E I expect that my writeup on CHARON-VAX will be posted shortly. In the 8 interim, the writeup is available on www.charon-vax.com.   cheers,    terry s    ------------------------------  # Date: Sat, 22 Jul 2000 22:47:51 GMT ( From: Terry Kennedy <terry@gate.tmk.com>+ Subject: Re: Undocumented commands in UCX ? ' Message-ID: <Fy4FBr.M14@spcuna.spc.edu>   2 Richard B. Gilbert <DRAGON@compuserve.com> writes:K >         Can you say "Unix"?   The original UCX was a port of the Berkeley I > code.  It was a late port, the other vendors; TGV, TWG, etc. had a head  > start of several years.   H   So? Have you looked at the banner MultiNet spits out at startup? Hint:F "MultiNet V4.2 Rev A-X (4.3bsd-tahoe+ Networking)". That looks pretty  Berkeley-ish to me...   K   And MultiNet adds a thin veneer of VMS-ness on top of some of the lesser- K used stuff - you get the default single-line command recall, but not multi- I line, and the management interface is TOPS-ish. Apparently nobody can fix K the bugs in the management interface parser - I can generate "?Internal er- K ror" messages at will, and of course there's the infamous "?Not confirmed".   H   But the basic functionality of MultiNet is excellent, so folks use it.  M >         TCPIP services V5.0 is a port of the Digital Unix code.  I've heard I > both that the whole thing is DU and that "major parts" are DU.  I think M > that the "major parts" is closer to the truth; the user interface obviously < > makes a few concessions to VMS and compatibility with UCX>  N   The kernel is based on the DU code (it had VMS conditionals put in to handleN VMS-isms, but then that code got sent back to the DU group to be used as theirN code base - this from talking to the principal UCX architect at the Providence '99 Symposium).   L >         Anyway, what did you expect from a background like that?  Consider6 > yourself lucky if it works at all!!!!  (5.0 didn't!)  J   UCX always suffered from a "ready or not, ship it" management style, andM the Customer Support Center mangled bug reports so badly that UCX engineering N couldn't figure out what they were saying (I saw the before and after versionsL of some of my bug reports as proof of this). Also, when they were developingM 5.0, apparently management insisted that they spend a lot of time fixing bugs N in the prior versions (a dead-end code base) rather than getting a quality 5.0 out the door faster.  - 	Terry Kennedy             http://www.tmk.com 5         terry@tmk.com             Jersey City, NJ USA    ------------------------------  % Date: Sun, 23 Jul 2000 00:17:02 -0400u2 From: "Richard B. Gilbert" <DRAGON@compuserve.com>+ Subject: Re: Undocumented commands in UCX ?07 Message-ID: <200007230017_MC2-AD22-6F99@compuserve.com>s  H         I've never had the opportunity to work with Multinet!  I wish it were otherwise.E  D         I believe that *all* VMS TCP/IP packages except CMU-TEK wereG originally ports of the Berkeley code.  The other vendors had a several G year head start in which to find and fix the Berkeley bugs.  DEC didn'tbJ really want to be in the TCP/IP business in the first place and it showed= ! =X  H Their choice of a third party TCP/IP product to sell and support (FusionJ from Network Research) was ill conceived.  If they had had the wit do buy=  J and market the Stanford package which later became Multinet, we would all=   have been a lot better off.s  % Message text written by Terry Kennedy03 >Richard B. Gilbert <DRAGON@compuserve.com> writes:oJ >         Can you say "Unix"?   The original UCX was a port of the Berkel= eyJ > code.  It was a late port, the other vendors; TGV, TWG, etc. had a head=   > start of several years.u  H   So? Have you looked at the banner MultiNet spits out at startup? Hint:G "MultiNet V4.2 Rev A-X (4.3bsd-tahoe+ Networking)". That looks pretty =n   Berkeley-ish to me...e <<   ------------------------------   End of INFO-VAX 2000.408 ************************