Vijay,

You can't restore library files in-place with ADSM.

This is an OS issue, not an ADSM issue.  The library files are in use
and
memory mapped since the file on disk acts as paging space for the loaded
code (text, in object-file language) that is being using by at least one
if not many running processes.  The OS will not allow anything (even
ADSM
with root privileges) to overwrite those files.

The only way to restore them is to restore them when they are not in
use.
That is what a mksysb does.  It boots off tape or network, creates a
filesystem in memory, restores enough files to run the restore from that
RAM
filesystem, then creates and restores the OS filesystems on disk.

I suppose some enterprising person could create something similar to a
mksysb
that restores via ADSM instead of the media...

Cheers...
Bruce


Vijay Havaralu wrote:
>
> We here  have problem in restoring AIX files  (system files with all readonly
> access) like
>
> /usr/lib/libauthm.a
>
> and other 50 over files of the filesystem that we are restoring using  command
> like
> dsmc res /usr/lib/libauthm.a
> returns the error  "Cannot restore -- due to write access denied"  error
>
> After selecting force write (over write write protect access) it repeats the
> error
> "write access denied",  and does not restore such files.
>
> Probably these fine might have been locked up by the system, whose process we
> may not be able
> to kill......We appreciate if anybody encountered such problems, and got away
> with restoring such
> locked/write protected files.....The files are being restored with root
> authority.  and AIX client
> ADSM version is 3.1.0  and MVS ADSM server version is 3.1.0
>
> Vijay,  x2743.

--
Bruce Elrick, Ph.D.                                 IBM Certified
Bruce Elrick, Ph.D.                                 IBM Certified
Specialist
belrick AT home DOT com                        ADSM, AIX Support, RS/6000 SP,
HACMP
(403) 870-4429                            Saltus Technology Consulting
Group