GNV 2.1-1 start-up nit - VMS

This is a discussion on GNV 2.1-1 start-up nit - VMS ; I recently installed the GNV 2.1-1 kit on my XP1000, OpenVMS Alpha v8.3 with all ECOs applied. It seemed to work fine until the next system reboot, when SYS$UPDATE:GNV$STARTUP.COM failed with errors about the "mnt" symbol not being defined. So ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: GNV 2.1-1 start-up nit

  1. GNV 2.1-1 start-up nit

    I recently installed the GNV 2.1-1 kit on my XP1000, OpenVMS Alpha v8.3
    with all ECOs applied. It seemed to work fine until the next system
    reboot, when SYS$UPDATE:GNV$STARTUP.COM failed with errors about the
    "mnt" symbol not being defined. So I took a look at what it was doing
    and discovered that it defined the mnt symbol (in an auxiliary
    procedure called PSX$UP_STARTUP.COM), then deleted it, then attempted
    to use it.

    So I commented out the line that deleted the symbol and all appears to
    be going swimmingly.

    While I was rooting around in there I noticed that it was attempting to
    create mount points for the members of my system disk shadowset as well
    as the shadowset itself. I don't know that there's any particular harm
    in that on its own, but it doesn't sound like something I want it
    doing, so I added a line to make it skip shadowset members.

    My changes are below. Use at your own risk.


    $ gdiff -u sys$startupsx$up_startup.com;-0
    sys$startupsx$up_startup.com
    --- sys$startupsx$up_startup.com;-0 Fri Jan 5 16:40:00 2007
    +++ sys$startupsx$up_startup.com Sat Jul 14 12:50:19 2007
    @@ -131,7 +131,7 @@
    $! Restore state and cleanup.
    $! Then we are done.
    $ set process/parse='proc_parse'
    -$ delete/symbol/global mnt
    +$!$ delete/symbol/global mnt
    $
    $ exit ! PSX$UP_STARTUP.COM

    @@ -192,6 +192,7 @@
    $ if $$$dev .eqs. "" then return
    $ mntd = f$getdvi ($$$dev, "mnt")
    $ if .not. mntd then goto loop
    +$ if f$getdvi($$$dev, "SHDW_MEMBER") then goto loop
    $ if f$verify() then write sys$output "Device is mounted: ''$$$dev'"
    $ $$$vol = f$getdvi ($$$dev, "volnam")
    $ $$$devnam = $$$dev - ":" - "_"

    --
    Posted via a free Usenet account from http://www.teranews.com


  2. Re: GNV 2.1-1 start-up nit

    Craig A. Berry wrote:
    > I recently installed the GNV 2.1-1 kit on my XP1000, OpenVMS Alpha v8.3
    > with all ECOs applied. It seemed to work fine until the next system
    > reboot, when SYS$UPDATE:GNV$STARTUP.COM failed with errors about the
    > "mnt" symbol not being defined.


    Thanks. The developer working on GNV (Karl) has another release coming
    up and I know he's made extensive changes to this area. I suspect the
    bug has been fixed, but I sent him your post just to be sure.

    --
    John Reagan
    OpenVMS Pascal/Macro-32/COBOL Project Leader
    Hewlett-Packard Company

  3. Re: GNV 2.1-1 start-up nit

    In article , "Craig A. Berry" writes:
    >I recently installed the GNV 2.1-1 kit on my XP1000, OpenVMS Alpha v8.3


    Is GNV now able to be PCSI REMOVEd again?

    With GNV V2.1 I hosed 2 system disks...

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  4. Re: GNV 2.1-1 start-up nit

    In article <46a12e15$1@news.langstoeger.at>,
    peter@langstoeger.at (Peter 'EPLAN' LANGSTOeGER) wrote:

    > In article , "Craig A.
    > Berry" writes:
    > >I recently installed the GNV 2.1-1 kit on my XP1000, OpenVMS Alpha v8.3

    >
    > Is GNV now able to be PCSI REMOVEd again?


    Yes, I successfully uninstalled and reinstalled 2.1-1.

    --
    Posted via a free Usenet account from http://www.teranews.com


+ Reply to Thread