D,

  I am sorry you are still having this problem, I had not noticed a memo
from you and thought the best.  These messages seem to be indicating that
adsm.sys directory or its files are being modified during backup.  Since
you have validated that there are not 2 ADSM processes running, this seems
unlikely.  Another possibility is that the registry backup process that
ADSM starts is not completing before ADSM attempts to backup the files.
Since nobody else is reporting this problem, this also seems unlikely.

Some questions come to mind.  Are you running any sort of
mirroring/clustering/high availability software on these machines?
What is the parm in the dsm.opt that governs registry backup set at
currently?

If I were you, I would consider some of these steps.   Some of them fall
into the "I just want to fix the problem, not explain it" category.

Delete adsm.sys directory:

Delete the adsm.sys subdirectory completely and attempt to
run the backup again.  There should be nothing accessing this
directory when an adsm backup is not running.  If you get an error, you may
have run chkdsk.

If backup still fails:
  Uninstall and re-install ADSM.
  rerun backup.

If backup still fails:
  Grab IBM tech support and get them to tell you what trace options are
going to identify this problem.  Run the trace and let them interpret it
for you.

If they say it is not an ADSM problem, then:


Audit the access to these files:
  Start the "User Manager" on the NT machine.
  Under the Policies menu, select Audit and choose
   FILE and OBJECT Access.
 Run the command line backup  (try just backing up adsm.sys)
 Turn off auditing.
  Your event log should be full of access data.  Look @ adsm.sys
  See if there are some simultaneous access, and by who/what/where.



  I am going to play with the auditing on my machine to see what a good
backup looks like.  You may have to do the same to a machine that you know
works to compare against the one that fails.

Good luck,
Dan T.

ps.  Let us know how things go.



----------
> From: Iseli,Dominique,VEVEY,FC-SIL/INF <Dominique.Iseli AT NESTLE DOT COM>
> From: Iseli,Dominique,VEVEY,FC-SIL/INF <Dominique.Iseli AT NESTLE DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: dsmc incr failed to backup registry in adsm.sys on nt
> Date: Thursday, January 08, 1998 3:05 AM
>
> hello, we still cannot backup registry on nt 351 and nt 4. something
> wrong with adsm.sys.
> we run adsm mvs 3.1 and client nt v3 downloaded from web.we migrated
> from v2.
> problem occurs with command mode only (dsmc incr)
>
>
> here is dsmerror.log.
> 01/07/1998 10:09:20 AltStreamSize(): CreateFile: Win32 RC=32
> 01/07/1998 10:09:20 AltStreamSize(): CreateFile: Win32 RC=32
> 01/07/1998 10:09:20 AltStreamSize(): CreateFile: Win32 RC=32
> 01/07/1998 10:09:20 AltStreamSize(): CreateFile: Win32 RC=32
> 01/07/1998 10:09:20 AltStreamSize(): CreateFile: Win32 RC=32
> 01/07/1998 10:09:44 ANS1228E Sending of object
> 'C:\adsm.sys\Registry\VEVSAP01\Machine' failed
> 01/07/1998 10:09:44 ANS1840E File
> 'C:\adsm.sys\Registry\VEVSAP01\Machine' changed during processing.  File
> skipped.
> 01/07/1998 10:09:45 ANS1228E Sending of object
> 'C:\adsm.sys\Registry\VEVSAP01\Users' failed
> 01/07/1998 10:09:45 ANS1840E File 'C:\adsm.sys\Registry\VEVSAP01\Users'
> changed during processing.  File skipped.
>
>
>
> We checked with nthandle and none was using adsm.sys. We also stpped the
> adsm scheduler service.
> When using gui to backup registry, everything work fine.
> Can we have help ?