Ted Ashton writes:
>
> Ok, I'm confused:
>
> /ADMIN/ADMDEV:altsec bhesalp;delacd
> There is no ACD associated with the target file. (CIERR 7305)
> /ADMIN/ADMDEV:altsec bhesalp.admdev;delacd
> There is no ACD associated with the target file. (CIERR 7305)
> /ADMIN/ADMDEV:listfile bhesalp,-2
> ACCOUNT=  ADMIN       GROUP=  ADMDEV
>
> FILENAME        ------------ACD ENTRIES--------------
>
> BHESALP             $OWNER              : R,W,X,RACD
>                     $GROUP_MASK         : R,X,RACD
>                     $GROUP              : R,X,RACD
>                     @.@                 : R,X,RACD
>
> What's going on here?  By the by, I am the owner.

I saw a similar problem early this year when applying a System Dictionary Y2K
patch via Stage/iX.

Stage/iX sysaborted during bootup while trying to update SDCONV.PUB.SYS (the
only time it's ever failed me).  This was totally unexpected, and since it was
a heavy production night, I didn't have time to take a memory dump.  So I
rebooted with STARTBASE.

After the machine came back up, I listed the ACD for SDCONV.PUB.SYS and saw
some entries.  Hmmmm, those shouldn't be there, I'll just delete them with
:ALTSEC ;DELACD.  Wrong!  :ALTSEC said there were no ACDs, yet :LISTFILE said
there were ACDs.  Bizarre.

:PURGE the file.  :RESTORE from my previous backup.  No ACDs were on the
restored file!  Weird, weird, weird!

I was subsequently able to install the patch OK, and the ACD problem never
reproduced itself.

I suspect the ACD information in the label table was somehow corrupted.
--
Mark Bixby                      E-mail: [log in to unmask]
Coast Community College Dist.   Web: http://www.cccd.edu/~markb/
District Information Services   1370 Adams Ave, Costa Mesa, CA, USA 92626-5429
Technical Support               Voice: +1 714 438-4647
"You can tune a file system, but you can't tune a fish." - tunefs(1M)