Edward Gill <[log in to unmask]> wrote:
>Hi all,
>
>Over the weekend we had to do a reload on our 950 (with 5.0) because we
>lost a disk drive and after the reload finished we found out that, so far,
>one account had ACDs set for all but one file and the ACDs did not exist
>before the reload. We deleted the account, built it again and just did a
>restore of that account and they appeared again. We got rid of the account
>again and restored the files from a different set of tapes, from our 992
>(with 5.0), and they were there again. After attempting to clear these with
>the ALTSEC command, that said the ACDs were not set, we contacted HPRC and
>was told to try the ACCOUNT= parm on the restore to see if that would clear
>them. It did but I have no idea why. Has anyone, other than us, had to go
>through this and if so did you ever find out what caused them to turned on
>on only one account and no others?
 
While I haven't heard of a problem with exactly your symptoms,
I have seen something similar with a site here in Germany,
which raises some questions:
 
1) Did you look at the ACD information with a LISTF ,-2 ?
   if Yes, did it show as @.@ : RACD (and no other ACDs) ?
2) Maybe you can reproduce this by restoring one (rather
   unimportant) file from that backup without using the
   ;ACCOUNT= option ?
   If so, could you look at it with an HFS syntax-ed LISTFILE,
   i.e. LISTFILE /ACCOUNT/GROUP/FILE,-3 and compare the listed
   GROUP ID value with your ACCOUNT name ?
 
I am suspicous that these are different.
BTW: it is perfectly ok, that MPE puts an ACD on a file, when
the GROUP ID (GID) is different from the ACCOUNT, the question
here would be, why don't the files have the same GROUP ID as
the account (if my suspect is correct).
 
 
Hope this helps,
 
Goetz.