| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
hello,
ALL-IN-1 v2.4
Can someone help me with the NOTES SET_MODERATOR function?
The customer has created a conference within GPC, and now wishes to
update the conference by using MC. When he chooses that option, it comes up
with the error
You are not the moderator of the conference.
The customer is on a cluster, and if he looks on the conference
profile, he sees himself as the moderator using the cluster alias name.
#OAN$USER_NODE is alos set up as the cluster alias when he enters GPC as
sys$cluster_node is defined. The ALL-IN-1 username is the same as the VMS
user name.
What else does the set_moderator flag check to come up with error?
Thanks for any help,
Julie
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1260.1 | KERNEL::OTHENJ | Tue Aug 18 1992 18:13 | 23 | ||
Hello,
Since entering the note, the customer now admits that he was using
the ALL-IN-1 manager account, so the ALL-IN-1 and VMS account ARE
different. The customer gets the error
You are not the moderator of the conference
when he enters MCP to restrict membership to Y. I am still confused
though, as I have found various articles which suggests that there are
problems with some moderator functions, but it should work if
set_moderator is used. I have tried it out on our system using ALL-IN-1
V2.4 patched up to K605, and I cannot get it to fail.
Does anyone know if this is an option that should fail, and if so
when is it fixed? I cannot find any reference to this in the release
notes for the patches, but I cannot get it to fail.
The customer has no patches on his system.
Thanks
Julie
| |||||
| 1260.2 | Read notes in conference | SIOG::T_REDMOND | Thoughts of an Idle Mind | Wed Aug 19 1992 16:07 | 10 |
There are many, many notes about how problems with GPC validation of
moderator (and other) privileges which were in V2.4. These have now
been addressed in V3.0.
Most of the problems lie with cluster alias versus node names etc etc
etc. Read the notes here and then see if the problem is indeed due to
the cluster name getting in the way of the node name or vice versa.
Then we'll see whether it's a different problem or not.
Tony
| |||||