| 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 |
A customer didn't open the SYSTEM account to do an ALL-IN-1 upgrade
installation (V2.4 - V3.0A) so I had to use the ALLIN1 account with the
privilege SETPRV :-(
I only had a little problem during the execution of A1$POSTINSTALL.
This procedure tries to grant the identifier OAFC$SYSMAN to the
installing account and executes immediatly if this fails. Since ALLIN1
already owns this identifier at this point but the current process which
is checked for the posession of OAFC$SYSMAN doesn't, A1$POSTINSTALL
fails and you have to do the remaining tasks after the installation.
$ALLIN1 /NOINIT /NOCUSTOM /LANGUAGE=language/OVERRIDE=SHUTDOWN
OA$FLO_OPEN_LIB oa$lib:oaform
OA$FLO_OPEN_LIB oa$lib:memres
OA$FLO_OPEN_LIB oa$lib:manager
OA$FLO_OPEN_LIB oa$lib:admin
OA$FLO_OPEN_LIB oa$lib:cm
OA$INI_SUBPROCESS
DO oa$lib:oafc$server_create_73
DISPLAY "ALL-IN-1 running -- Starting local File Cabinet Server"
DO oa$lib:oafc$server_startup_det
etc.
To prevent this problem you may revoke this identifier from ALLIN1
before A1$POSTINSTALL starts to execute and grant it again after the
installation has completed.
Stefan
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3917.1 | Fixed in PFR | IOSG::HALLC | Denser than a Black Hole Singularity | Fri Feb 25 1994 22:07 | 7 |
Stefan, Thanks for the report. This is a known problem and I have fixed it for a Possible Future Release. Cheers, Chris. | |||||