T.R | Title | User | Personal Name | Date | Lines |
---|
3194.1 | Need correct UAF record setup, too | GANTRY::HULL | Digital Consulting [Delivery]/Motown | Wed Aug 25 1993 19:56 | 18 |
| If the acct in question is a valid CM programmer, it must have the correct
UAF Rightlist identifier marked on his UAF record. My acct has full A1
Manager, App. Mgr, and CM Programmer, and these are all the Idents that
show up:
OA$ADMIN %X8001100E
OA$PRVAPP %X8001100F RESOURCE
OAFC$SYSMAN %X800100A3
OA$MANAGER %X800100A0
OA$MANAPP %X8001009F RESOURCE
So make sure he has OA$PRVAPP. If he is also flagged as an Application
Manager he'll need OA$MANAPP.
Regards,
Al
|
3194.2 | Missing OA$INI_GLOBALS somewhere? | IOSG::HULIN | Ian Hulin, a.k.a. Banquo's ghost -} | Thu Aug 26 1993 12:57 | 19 |
| Steve,
�.0 GET PROFIL.PRVAPP["MANAGER"] returns "M", but GET OA$PROFIL_PRVAPP
�.0 returns 0! What updates OA$PROFIL_PRVAPP? Seems tha two of them are out
�.0 of sync.
Al's probably got the right solution but here's something else to check.
Normally if GET PROFIL.<fieldname>[OA$USER] does the right thing, but GET
OA$PROFIL_<fieldname> doesn't, it can normally be cured by a quick
<OA$INI_GLOBALS to reset all the fast-access special symbols to their new
"correct" values.
HTH,
Cheers from beyond the rightsized grave,
Ian
|
3194.3 | | KERNEL::LOAT | Keep passing the open windows... | Thu Aug 26 1993 14:17 | 14 |
|
The customer editted the profile record, and changed it back to "A",
and then tried the symbol, and it had changed. We then checked the UAF
record, and this showed the OA$MANAPP identifier, so we did a write
change to set it back to "M" exited ALL-IN-1 and re-entered, and it
worked!
I noticed that the symbol didn't change until we exitted and
re-entered, so I think that .2 had the crucial info.
Thanx for the help everyone.
Steve.
|