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

This is a discussion on -SYSTEM-F-WRITLCK, write lock error - VMS ; 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 ...

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 20 of 23

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

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

    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

    $ product install 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

    $ show def
    SYS$SYSROOT:[SYSMGR]
    = SYS$SYSROOT:[SYSMGR]
    = SYS$COMMON:[SYSMGR]
    $

    what could cause this error?

    The following reports "error on bitmap". Is that important or relevant?

    $ show dev/full donkey$dqa0

    Disk DONKEY$DQA0:, device type DV-28E-C, is online, allocated, deallocate on
    dismount, mounted, software write-locked, file-oriented device, shareable,
    served to cluster via MSCP Server, error logging is enabled.

    Error count 0 Operations completed 1008
    Owner process "SYSTEM" Owner UIC [SYSTEM]
    Owner process ID 20E00429 Dev Prot S:RWPL,O:RWPL,G:R,W
    Reference count 2 Default buffer size 512
    Total blocks 2843136 Sectors per track 41
    Total cylinders 1692 Tracks per cylinder 41
    Logical Volume Size 2843108 Expansion Size Limit 2863104

    Volume label "I64BINFEB071" Relative volume number 0
    Cluster size 3 Transaction count 1
    Free blocks 253869 Maximum files allowed 355388
    Extend quantity 5 Mount count 1
    Mount status Process Cache name "_$1$DGA2:XQPCACHE"
    Extent cache size 64 Maximum blocks in extent cache 25386
    File ID cache size 64 Blocks in extent cache 0
    Quota cache size 0 Maximum buffers in FCP cache 4840
    Volume owner UIC [17,35] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD

    Volume Status: ODS-2, subject to mount verification, allocation inhibited
    because of error on bitmap, file high-water marking, write-back caching
    enabled.

    $

    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

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

    Anton Shterenlikht wrote:
    > 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
    >
    > $ product install 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
    >
    > $ show def
    > SYS$SYSROOT:[SYSMGR]
    > = SYS$SYSROOT:[SYSMGR]
    > = SYS$COMMON:[SYSMGR]
    > $
    >
    > what could cause this error?
    >
    > The following reports "error on bitmap". Is that important or relevant?
    >
    > $ show dev/full donkey$dqa0
    >
    > Disk DONKEY$DQA0:, device type DV-28E-C, is online, allocated, deallocate on
    > dismount, mounted, software write-locked, file-oriented device, shareable,
    > served to cluster via MSCP Server, error logging is enabled.
    >
    > Error count 0 Operations completed 1008
    > Owner process "SYSTEM" Owner UIC [SYSTEM]
    > Owner process ID 20E00429 Dev Prot S:RWPL,O:RWPL,G:R,W
    > Reference count 2 Default buffer size 512
    > Total blocks 2843136 Sectors per track 41
    > Total cylinders 1692 Tracks per cylinder 41
    > Logical Volume Size 2843108 Expansion Size Limit 2863104
    >
    > Volume label "I64BINFEB071" Relative volume number 0
    > Cluster size 3 Transaction count 1
    > Free blocks 253869 Maximum files allowed 355388
    > Extend quantity 5 Mount count 1
    > Mount status Process Cache name "_$1$DGA2:XQPCACHE"
    > Extent cache size 64 Maximum blocks in extent cache 25386
    > File ID cache size 64 Blocks in extent cache 0
    > Quota cache size 0 Maximum buffers in FCP cache 4840
    > Volume owner UIC [17,35] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD
    >
    > Volume Status: ODS-2, subject to mount verification, allocation inhibited
    > because of error on bitmap, file high-water marking, write-back caching
    > enabled.
    >
    > $
    >
    > many thanks
    > anton
    >


    At the very least you need to do an
    $ ANALYZE /DISK_STRUCTURE /REPAIR /CONFIRM DONKEY$DQA0:

    At worst, you had better hope you have a good backup!


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

    On 9/10/07, Anton Shterenlikht wrote:
    > 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
    >
    > $ product install 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
    >
    > $ show def
    > SYS$SYSROOT:[SYSMGR]
    > = SYS$SYSROOT:[SYSMGR]
    > = SYS$COMMON:[SYSMGR]
    > $
    >
    > what could cause this error?


    Please do a

    $ sho log sys$sysdevice

    and a

    $ sho log sys$sysroot

    It sounds like you destination drive is also write locked.

    Ken

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

    Anton Shterenlikht wrote:
    > 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
    >
    > $ product install 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
    >
    > $ show def
    > SYS$SYSROOT:[SYSMGR]
    > = SYS$SYSROOT:[SYSMGR]
    > = SYS$COMMON:[SYSMGR]
    > $
    >
    > what could cause this error?
    >
    > The following reports "error on bitmap". Is that important or relevant?
    >
    > $ show dev/full donkey$dqa0
    >
    > Disk DONKEY$DQA0:, device type DV-28E-C, is online, allocated, deallocate on
    > dismount, mounted, software write-locked, file-oriented device, shareable,
    > served to cluster via MSCP Server, error logging is enabled.
    >
    > Error count 0 Operations completed 1008
    > Owner process "SYSTEM" Owner UIC [SYSTEM]
    > Owner process ID 20E00429 Dev Prot S:RWPL,O:RWPL,G:R,W
    > Reference count 2 Default buffer size 512
    > Total blocks 2843136 Sectors per track 41
    > Total cylinders 1692 Tracks per cylinder 41
    > Logical Volume Size 2843108 Expansion Size Limit 2863104
    >
    > Volume label "I64BINFEB071" Relative volume number 0
    > Cluster size 3 Transaction count 1
    > Free blocks 253869 Maximum files allowed 355388
    > Extend quantity 5 Mount count 1
    > Mount status Process Cache name "_$1$DGA2:XQPCACHE"
    > Extent cache size 64 Maximum blocks in extent cache 25386
    > File ID cache size 64 Blocks in extent cache 0
    > Quota cache size 0 Maximum buffers in FCP cache 4840
    > Volume owner UIC [17,35] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD
    >
    > Volume Status: ODS-2, subject to mount verification, allocation inhibited
    > because of error on bitmap, file high-water marking, write-back caching
    > enabled.
    >
    > $
    >
    > many thanks
    > anton
    >

    Your default directory is set to DQA0: which is a DVD and is not writeable.

    Jeff Coffield

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

    On Mon, Sep 10, 2007 at 09:30:27AM -0400, Ken Robinson wrote:
    > On 9/10/07, Anton Shterenlikht wrote:
    > > 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
    > >
    > > $ product install 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
    > >
    > > $ show def
    > > SYS$SYSROOT:[SYSMGR]
    > > = SYS$SYSROOT:[SYSMGR]
    > > = SYS$COMMON:[SYSMGR]
    > > $
    > >
    > > what could cause this error?

    >
    > Please do a
    >
    > $ sho log sys$sysdevice
    >
    > and a
    >
    > $ sho log sys$sysroot
    >
    > It sounds like you destination drive is also write locked.


    Ken, thanks a lot:

    $ show log sys$sysdevice
    "SYS$SYSDEVICE" = "$1$DGA2:" (LNM$SYSTEM_TABLE)
    $ show log sys$sysroot
    "SYS$SYSROOT" = "$1$DGA2:[SYS0.]" (LNM$SYSTEM_TABLE)
    = "SYS$COMMON:"
    1 "SYS$COMMON" = "$1$DGA2:[SYS0.SYSCOMMON.]" (LNM$SYSTEM_TABLE)
    $

    I also tried to specify the destination with
    /DESTINATION = SYS$SYSDEVICE:[VMS$COMMON]

    the error is the same

    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

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

    On Mon, Sep 10, 2007 at 09:07:44AM -0400, Richard B. Gilbert wrote:
    > Anton Shterenlikht wrote:
    > >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
    > >
    > >$ product install 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
    > >
    > >$ show def
    > > SYS$SYSROOT:[SYSMGR]
    > > = SYS$SYSROOT:[SYSMGR]
    > > = SYS$COMMON:[SYSMGR]
    > >$
    > >
    > >what could cause this error?
    > >
    > >The following reports "error on bitmap". Is that important or relevant?
    > >
    > >$ show dev/full donkey$dqa0
    > >
    > >Disk DONKEY$DQA0:, device type DV-28E-C, is online, allocated, deallocate
    > >on
    > > dismount, mounted, software write-locked, file-oriented device,
    > > shareable,
    > > served to cluster via MSCP Server, error logging is enabled.
    > >
    > > Error count 0 Operations completed
    > > 1008
    > > Owner process "SYSTEM" Owner UIC
    > > [SYSTEM]
    > > Owner process ID 20E00429 Dev Prot
    > > S:RWPL,O:RWPL,G:R,W
    > > Reference count 2 Default buffer size
    > > 512
    > > Total blocks 2843136 Sectors per track
    > > 41
    > > Total cylinders 1692 Tracks per cylinder
    > > 41
    > > Logical Volume Size 2843108 Expansion Size Limit
    > > 2863104
    > >
    > > Volume label "I64BINFEB071" Relative volume number
    > > 0
    > > Cluster size 3 Transaction count
    > > 1
    > > Free blocks 253869 Maximum files allowed
    > > 355388
    > > Extend quantity 5 Mount count
    > > 1
    > > Mount status Process Cache name
    > > "_$1$DGA2:XQPCACHE"
    > > Extent cache size 64 Maximum blocks in extent cache
    > > 25386
    > > File ID cache size 64 Blocks in extent cache
    > > 0
    > > Quota cache size 0 Maximum buffers in FCP cache
    > > 4840
    > > Volume owner UIC [17,35] Vol Prot
    > > S:RWCD,O:RWCD,G:RWCD,W:RWCD
    > >
    > > Volume Status: ODS-2, subject to mount verification, allocation
    > > inhibited
    > > because of error on bitmap, file high-water marking, write-back
    > > caching
    > > enabled.
    > >

    >
    > At the very least you need to do an
    > $ ANALYZE /DISK_STRUCTURE /REPAIR /CONFIRM DONKEY$DQA0:
    >


    Richard, thanks:

    $ analyze/disk_structure /repair /confirm donkey$dqa0:

    Analyze/Disk_Structure/Repair for _DONKEY$DQA0: started on 10-SEP-2007 15:28:24.
    20

    %ANALDISK-I-SHORTBITMAP, storage bitmap on RVN 1 does not cover the entire devic
    e
    %ANALDISK-E-NOREPAIR, one or more volumes write locked - /REPAIR cancelled
    %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
    -SYSTEM-W-NOSUCHFILE, no such file
    $

    Is there a problem with this DVD media?

    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

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

    Anton Shterenlikht wrote:
    > On Mon, Sep 10, 2007 at 09:07:44AM -0400, Richard B. Gilbert wrote:
    >
    >>Anton Shterenlikht wrote:
    >>
    >>>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
    >>>
    >>>$ product install 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
    >>>
    >>>$ show def
    >>> SYS$SYSROOT:[SYSMGR]
    >>> = SYS$SYSROOT:[SYSMGR]
    >>> = SYS$COMMON:[SYSMGR]
    >>>$
    >>>
    >>>what could cause this error?
    >>>
    >>>The following reports "error on bitmap". Is that important or relevant?
    >>>
    >>>$ show dev/full donkey$dqa0
    >>>
    >>>Disk DONKEY$DQA0:, device type DV-28E-C, is online, allocated, deallocate
    >>>on
    >>> dismount, mounted, software write-locked, file-oriented device,
    >>> shareable,
    >>> served to cluster via MSCP Server, error logging is enabled.
    >>>
    >>> Error count 0 Operations completed
    >>> 1008
    >>> Owner process "SYSTEM" Owner UIC
    >>> [SYSTEM]
    >>> Owner process ID 20E00429 Dev Prot
    >>> S:RWPL,O:RWPL,G:R,W
    >>> Reference count 2 Default buffer size
    >>> 512
    >>> Total blocks 2843136 Sectors per track
    >>> 41
    >>> Total cylinders 1692 Tracks per cylinder
    >>> 41
    >>> Logical Volume Size 2843108 Expansion Size Limit
    >>> 2863104
    >>>
    >>> Volume label "I64BINFEB071" Relative volume number
    >>> 0
    >>> Cluster size 3 Transaction count
    >>> 1
    >>> Free blocks 253869 Maximum files allowed
    >>> 355388
    >>> Extend quantity 5 Mount count
    >>> 1
    >>> Mount status Process Cache name
    >>> "_$1$DGA2:XQPCACHE"
    >>> Extent cache size 64 Maximum blocks in extent cache
    >>> 25386
    >>> File ID cache size 64 Blocks in extent cache
    >>> 0
    >>> Quota cache size 0 Maximum buffers in FCP cache
    >>> 4840
    >>> Volume owner UIC [17,35] Vol Prot
    >>> S:RWCD,O:RWCD,G:RWCD,W:RWCD
    >>>
    >>> Volume Status: ODS-2, subject to mount verification, allocation
    >>> inhibited
    >>> because of error on bitmap, file high-water marking, write-back
    >>> caching
    >>> enabled.
    >>>

    >>
    >>At the very least you need to do an
    >>$ ANALYZE /DISK_STRUCTURE /REPAIR /CONFIRM DONKEY$DQA0:
    >>

    >
    >
    > Richard, thanks:
    >
    > $ analyze/disk_structure /repair /confirm donkey$dqa0:
    >
    > Analyze/Disk_Structure/Repair for _DONKEY$DQA0: started on 10-SEP-2007 15:28:24.
    > 20
    >
    > %ANALDISK-I-SHORTBITMAP, storage bitmap on RVN 1 does not cover the entire devic
    > e
    > %ANALDISK-E-NOREPAIR, one or more volumes write locked - /REPAIR cancelled
    > %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
    > -SYSTEM-W-NOSUCHFILE, no such file
    > $
    >
    > Is there a problem with this DVD media?
    >
    > thanks
    > anton
    >


    I missed the fact that it was a DVD! There might, indeed, be a problem
    with the file structure on it. ANALYZE /DISK_STRUCTURE is the only way
    I know of to repair file structure problems. If it won't work with a
    DVD then I guess you have to make a new DVD and get it right this time! :-)


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

    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?

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

    >$ show def
    > SYS$SYSROOT:[SYSMGR]
    > = SYS$SYSROOT:[SYSMGR]
    > = SYS$COMMON:[SYSMGR]


    I recommend setting the default not to a search list (like SYS$MANAGER,
    SYSTEM's homedir) but I don't think this is related to your problem.

    And I also recommend doing a logfile of the installation (like with
    $ SET HOST/LOG=SYS$SYSDEVICE:[INSTALL_LOGS]FORTRAN-V0801-2.I64 or .LOG)
    and using /LOG and /TRACE qualifiers with the PRODUCT command...

    >what could cause this error?


    Maybe default on a write locked device (which would mean your system disk
    is write locked - and then you have other problems than your current one).

    Or more likely a PCSI$DESTINATION logical pointing to a write locked device.

    But frankly, I don't know. I suspect the DVD, too.

    >The following reports "error on bitmap". Is that important or relevant?


    I wouldn't trust such a kit then (as long as it has no manifest file to
    gain trust again) but it is no proof that the kit is damaged I think.

    Good luck

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

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

    Anton Shterenlikht wrote:

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



    My first reaction is to suggest you take the PCSI file and move it to a
    real disk, and then try the "product" command again.

    It may be trying to create temporary files on the CD or create the
    release notes file on the CD.

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

    In article <20070910143225.GA32238@mech-aslap33.men.bris.ac.uk>, Anton Shterenlikht writes:
    >
    > $ analyze/disk_structure /repair /confirm donkey$dqa0:
    >
    > Analyze/Disk_Structure/Repair for _DONKEY$DQA0: started on 10-SEP-2007 15:28:24.
    > 20
    >
    > %ANALDISK-I-SHORTBITMAP, storage bitmap on RVN 1 does not cover the entire devic
    > e
    > %ANALDISK-E-NOREPAIR, one or more volumes write locked - /REPAIR cancelled
    > %ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
    > -SYSTEM-W-NOSUCHFILE, no such file
    > $
    >
    > 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.


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

    JF Mezei wrote:
    > Anton Shterenlikht wrote:
    >
    >> $ 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

    >
    >
    > My first reaction is to suggest you take the PCSI file and move it to a
    > real disk, and then try the "product" command again.


    Yes, that should do the trick (just tried it), although ...

    > It may be trying to create temporary files on the CD or create the
    > release notes file on the CD.


    .... the error message is:

    "... error writing ...
    DONKEY$DQA0:[FORT0811.KIT]HP-I64VMS-FORTRAN-V0801-2-1.PCSI;1"

    which is the original PCSI file (I checked it on my version,
    same volume label: "I64BINFEB071").

    Same error here. However, my version doesn't show the "error on
    bitmap".

    Is this a PCSI bug?

    System/VMS version: HP rx1620 ... running OpenVMS V8.2-1

    Albrecht

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

    Albrecht Schlosser wrote:

    > ... the error message is:
    >
    > "... error writing ...
    > DONKEY$DQA0:[FORT0811.KIT]HP-I64VMS-FORTRAN-V0801-2-1.PCSI;1"
    >
    > which is the original PCSI file (I checked it on my version,
    > same volume label: "I64BINFEB071").
    >
    > Same error here. However, my version doesn't show the "error on
    > bitmap".
    >
    > Is this a PCSI bug?
    >
    > System/VMS version: HP rx1620 ... running OpenVMS V8.2-1
    >
    > Albrecht


    You are still trying to write to DQA0: which you previously shown to be
    software write locked. Try copying the file to some normal disk.

    Jeff Coffield

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

    Jeffrey H. Coffield wrote:
    > Albrecht Schlosser wrote:
    >
    >> ... the error message is:
    >>
    >> "... error writing ...
    >> DONKEY$DQA0:[FORT0811.KIT]HP-I64VMS-FORTRAN-V0801-2-1.PCSI;1"
    >>
    >> which is the original PCSI file (I checked it on my version,
    >> same volume label: "I64BINFEB071").
    >>
    >> Same error here. However, my version doesn't show the "error on
    >> bitmap".
    >>
    >> Is this a PCSI bug?
    >>
    >> System/VMS version: HP rx1620 ... running OpenVMS V8.2-1
    >>
    >> Albrecht

    >
    > You are still trying to write to DQA0: which you previously shown to be
    > software write locked. Try copying the file to some normal disk.


    I did that! (Why didn't you read the whole message?)

    I wrote: "Yes, that should do the trick (_just_tried_it_), ..."

    The real problem is that PCSI ($ PRODUCT ...) seems to open the
    ..PCSI file on the DVD read/write, or really tries to write to the
    source .PCSI file! Hence my question: "Is this a PCSI bug?"

    Albrecht

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

    In article <516ir4-h1b.ln1@news.hus-software.de>, Albrecht Schlosser writes:
    >The real problem is that PCSI ($ PRODUCT ...) seems to open the
    >..PCSI file on the DVD read/write, or really tries to write to the
    >source .PCSI file! Hence my question: "Is this a PCSI bug?"


    Think again. If PCSI does it this way, then how to do a VMS install?
    (eg. OpenVMS Alpha from the VMS CD)

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

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

    Albrecht Schlosser wrote:
    > The real problem is that PCSI ($ PRODUCT ...) seems to open the
    > .PCSI file on the DVD read/write, or really tries to write to the
    > source .PCSI file! Hence my question: "Is this a PCSI bug?"



    PCSI does a lot of strange things. Don't question it.

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

    Peter 'EPLAN' LANGSTOeGER wrote:
    > Think again. If PCSI does it this way, then how to do a VMS install?
    > (eg. OpenVMS Alpha from the VMS CD)


    Does the CD use PRODUCT/PCSI to install VMS ? I would think it would be
    a DCL script that uses BACKUP to create/populate the system disk with
    all the quirks needed (aliases, boot block etc).

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

    In article <225d1$46e6d4d7$cef8887a$24432@TEKSAVVY.COM>, JF Mezei writes:
    >Peter 'EPLAN' LANGSTOeGER wrote:
    >> Think again. If PCSI does it this way, then how to do a VMS install?
    >> (eg. OpenVMS Alpha from the VMS CD)

    >
    >Does the CD use PRODUCT/PCSI to install VMS ? I would think it would be
    >a DCL script that uses BACKUP to create/populate the system disk with
    >all the quirks needed (aliases, boot block etc).


    It does use PRODUCT/PCSI with the /REMOTE qualifier (after setting up
    the neccessary logicals of course)

    How, do you think, will the PCSI database be populated with the products
    of the VMS installation (like CDSA. DECNET_OSI, DWMOTIF, SSL, TDC_RT, TCPIP,
    AVAIL_MAN, amm) if not with a real PCSI installation?

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

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

    Peter 'EPLAN' LANGSTOeGER wrote:
    > In article <...>, Albrecht Schlosser <...> writes:
    >> The real problem is that PCSI ($ PRODUCT ...) seems to open the
    >> ..PCSI file on the DVD read/write, or really tries to write to the
    >> source .PCSI file! Hence my question: "Is this a PCSI bug?"

    >
    > Think again. If PCSI does it this way, then how to do a VMS install?
    > (eg. OpenVMS Alpha from the VMS CD)


    Why think, about what? ;-)

    It's fine, if it works for OpenVMS installations, and sure you're
    right, but here it doesn't work, as it was shown.

    From the OP:

    %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

    Albrecht

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

    In article , Albrecht Schlosser writes:
    >Peter 'EPLAN' LANGSTOeGER wrote:
    >> In article <...>, Albrecht Schlosser <...> writes:
    >>> The real problem is that PCSI ($ PRODUCT ...) seems to open the
    >>> ..PCSI file on the DVD read/write, or really tries to write to the
    >>> source .PCSI file! Hence my question: "Is this a PCSI bug?"

    >>
    >> Think again. If PCSI does it this way, then how to do a VMS install?
    >> (eg. OpenVMS Alpha from the VMS CD)

    >
    >Why think, about what? ;-)
    >
    >It's fine, if it works for OpenVMS installations, and sure you're
    >right, but here it doesn't work, as it was shown.
    >
    > From the OP:
    >
    >%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


    I know what the OP wrote, I answered (a simple don't know, maybe the DVD).
    I only wanted to oppose your statement of a likely (or possible) cause
    "PCSI can't handle write locked sources" (or at least I read your post so)...

    Currently, I (still) suspect a PCSI$DESTINATION logical pointing to the DVD
    device or suspect the kit, but again, I don't know (and I also don't have
    this kitfile to check for other reasons)...

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

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

    Peter 'EPLAN' LANGSTOeGER wrote:
    >
    > In article , Albrecht Schlosser writes:
    > >Peter 'EPLAN' LANGSTOeGER wrote:
    > >> In article <...>, Albrecht Schlosser <...> writes:
    > >>> The real problem is that PCSI ($ PRODUCT ...) seems to open the
    > >>> ..PCSI file on the DVD read/write, or really tries to write to the
    > >>> source .PCSI file! Hence my question: "Is this a PCSI bug?"
    > >>
    > >> Think again. If PCSI does it this way, then how to do a VMS install?
    > >> (eg. OpenVMS Alpha from the VMS CD)

    > >
    > >Why think, about what? ;-)
    > >
    > >It's fine, if it works for OpenVMS installations, and sure you're
    > >right, but here it doesn't work, as it was shown.
    > >
    > > From the OP:
    > >
    > >%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

    >
    > I know what the OP wrote, I answered (a simple don't know, maybe the DVD).
    > I only wanted to oppose your statement of a likely (or possible) cause
    > "PCSI can't handle write locked sources" (or at least I read your post so)...
    >
    > Currently, I (still) suspect a PCSI$DESTINATION logical pointing to the DVD
    > device or suspect the kit, but again, I don't know (and I also don't have
    > this kitfile to check for other reasons)...


    See HELP PRODUCT INSTALL /REMOTE

    --
    David J Dachtera
    dba DJE Systems
    http://www.djesys.com/

    Unofficial OpenVMS Marketing Home Page
    http://www.djesys.com/vms/market/

    Unofficial Affordable OpenVMS Home Page:
    http://www.djesys.com/vms/soho/

    Unofficial OpenVMS-IA32 Home Page:
    http://www.djesys.com/vms/ia32/

    Unofficial OpenVMS Hobbyist Support Page:
    http://www.djesys.com/vms/support/

+ Reply to Thread
Page 1 of 2 1 2 LastLast