-SYSTEM-F-WRITLCK, write lock error - VMS

This is a discussion on -SYSTEM-F-WRITLCK, write lock error - VMS ; In article , David J Dachtera writes: >See HELP PRODUCT INSTALL /REMOTE How is your hint related? No mention of write access/locks there... -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a ...

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2
Results 21 to 23 of 23

Thread: -SYSTEM-F-WRITLCK, write lock error

  1. Re: -SYSTEM-F-WRITLCK, write lock error

    In article <46E89C14.6EBF6725@spam.comcast.net>, David J Dachtera writes:
    >See HELP PRODUCT INSTALL /REMOTE


    How is your hint related? No mention of write access/locks there...

    --
    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

  2. Re: -SYSTEM-F-WRITLCK, write lock error

    On Mon, Sep 10, 2007 at 12:04:55PM -0500, Bob Koehler wrote:
    > In article <20070910143225.GA32238@mech-aslap33.men.bris.ac.uk>, Anton Shterenlikht writes:
    > >
    > > Is there a problem with this DVD media?

    >
    > Is this DVD-R, DVD+R, DVD-RW, or some other writeable media? Is
    > the driver stricly a reader, or does it have compatable -R, +R, or
    > -RW capabilities?
    >
    > The errors you are seeing all involve attempting to write to what
    > appears to be read-only storage.


    Bob, it looks like it is only a reader:

    $ mount/system donkey$dqa0 i64binfeb071
    %MOUNT-I-WRITELOCK, volume is write locked

    $ show dev/full donkey$dqa0

    Disk DONKEY$DQA0:, device type DV-28E-C, is online, mounted, software write-
    locked, [...]

    Also according to http://www.teac.co.jp/dspd/product/optical/dv-28ec.html
    this is a ROM device.

    In any case it shouldn't even try to write to DVD. At least when I
    installed FORTRAN on Alpha from a CD with the same PRODUCT INSTALL command
    I didn't have this problem.

    Anyway, copying the PCSI file worked fine, which I report in another port.

    many thanks
    anton

    --
    Anton Shterenlikht
    Room 2.6, Queen's Building
    Mech Eng Dept
    Bristol University
    University Walk, Bristol BS8 1TR, UK
    Tel: +44 (0)117 928 8233
    Fax: +44 (0)117 929 4423

  3. Re: -SYSTEM-F-WRITLCK, write lock error

    On Mon, Sep 10, 2007 at 05:15:02PM +0200, Peter 'EPLAN' LANGSTOeGER wrote:
    > In article <20070910121806.GA31695@mech-aslap33.men.bris.ac.uk>, Anton Shterenlikht writes:
    > >I'm trying to install fortran on I64 VMS8.3 from a layered product DVD and
    > >I get the following error:
    > >
    > >$ product extract release_notes fortran /source=donkey$dqa0:[fort0811.kit]
    > >%PCSI-E-WRITEERR, error writing DONKEY$DQA0:[FORT0811.KIT]HP-I64VMS-FORTRAN-V080
    > >1-2-1.PCSI;1
    > >-SYSTEM-F-WRITLCK, write lock error
    > >%PCSI-E-S_OPFAIL, operation failed
    > >%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition

    >
    > How about copying the kit to another disk before the update?
    > Will the COPY be successfull?


    Peter, JF, yes this worked fine, thank you for the suggestion.

    > How about a explicit /FILE= qualifier? Where does PCSI$DESTINATION point to?


    this logical isn't defined:

    $ show logical pcsi$destination
    %SHOW-S-NOTRAN, no translation for logical name PCSI$DESTINATION

    but in any case I used /DESTINATION qualifier, which should override
    PCSI$DESTINATION.

    many thanks
    anton

    --
    Anton Shterenlikht
    Room 2.6, Queen's Building
    Mech Eng Dept
    Bristol University
    University Walk, Bristol BS8 1TR, UK
    Tel: +44 (0)117 928 8233
    Fax: +44 (0)117 929 4423

+ Reply to Thread
Page 2 of 2 FirstFirst 1 2