| Re: .0
>My customer has recently upgraded to ALL-IN-1 V3 and defined a cluster alias
>for their system. They have encountered the following problems:
>
>1. Users who used to be Moderators of conferences are no longer able
> to perform moderator functions. Their attempts are rejected with an
> access denied message.
This sounds normal to me. You will need to change the access lists for
all the members in all the conferences to use the cluster alias. By
the way, this is VAX Notes (or actually, I think it is DECnet) and not just
GPC. If you use one of the other interfaces you should see the same
phenomenon.
>2. After a user reads a note, exists GPC, then re-enters GPC, the note is still
> in an Unseen state, that is, comes up on an index of Unseen Notes.
I am not sure about this one. Do you know if the conference is being
closed when the user exits GPC?
>3. Previously the author field in the note contained only the author's username.
> Now it contains alias-name::username. My customer would like to display
> only username. (Note the cluster alias was only required to implement
> an X.400 Message Router gateway. All users are in fact on the same node)
Can you check this out with one of the other VAX Notes interfaces (e.g.
the TPU interface). I doubt that it is GPC which is doing this, since
we do not have control over the authour's name. Maybe it is a newer
version of VAX Notes which accounts for the change.
I hope this helps,
John
|
| 3. If you disable cluster aliasing for the notes object in NCP this
might fix this problem.
Actually it might fix all the others too.
But as John says, this is almost certainly not a GPC problem. In fact
it probably isn't a notes "problem" either, but the way that Notes
works.
Graham
|