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 |
This is a strange problem with our ALL-IN-1 startup. When the system is rebooted, the process OA$FCV cannot be found. The A1V24START.COM has to be executed again manually to start this process. We recently upgraded the system from 2.3 to 2.4, could this be the cause? :-), Adam.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
105.1 | Any error messages or other clues? | BUFFER::VICKERS | Winners take action not keep score | Wed Feb 26 1992 14:48 | 10 |
I'm not aware of anything in the upgrade from V2.3 to V2.4 that might be the cause of the problem but it could be related. Are there any error messages generated during the system startup that might offer a clue? This sort of potential problem is a good reason to have ALL-IN-1 start via a batch job so that you can examine the log file later. Hang in there, don | |||||
105.2 | Some points to be checked out | EEMELI::SALMINEN | Hannu Salminen, PTG -Finland | Thu Mar 26 1992 11:05 | 47 |
The cause of the problem may be some environmental restriction also. Starting OA$FCV process is done in A1V24START procedure in section: $START_OA$FCV: $!+++ $! Subroutine to wind up OA$FCV $!--- $ say " Starting OA$FCV" $ context = "" $ $FIND_OA$FCV: $ $ pid = f$pid(context) $ if pid .eqs. "" then goto RUN_OA$FCV $ name = f$getjpi(pid, "prcnam") $ if name .nes. "OA$FCV" then goto FIND_OA$FCV $ stop /id='pid' $ wait 0:0:3 $ $RUN_OA$FCV: $ $ define/nolog/user sys$output nl: $ run oa$lib_share:OAFCV /detach - /uic = [1,4] - /process_name = "OA$FCV" Possible failure in process OA$FCV creation may happen e.g. if the ALLIN1 VMS-account has too low PRCLM user quota in SYSUAF. Some too low SYSGEN parameter (MAXPROCESSCNT) may also prevent this detached process creation. Check ACCOUNTNG file with the following command to get an idea of the cause of process termination $ ACCOUNTING/PROCESS=DETACH/FULL/SINCE= ... One more thing to be checked out is the version of OAFCV.EXE, there may be several versions (from old ALL-IN-1 versions) of this image, and some old one matches first in the search list. Regards, Hannu |