[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

57.0. "JBC-E-SYMDEL, RMS-F-XAB OA$FORMATTER queue stopped" by SWAM2::MIYAMOTO_KY (Kyle Miyamoto DTN 531-5286) Wed Feb 19 1992 23:46

    The OA$FORMATTER symbiont process died.  The following appeared on the
    console (via JOB_CONTROL) prior to image termination:
    
    Message from user JOB_CONTROL on SSDVX1
    %JBC-E-INVMSG, invalid mailbox message received
    %JBC-E-INVMSG, invalid mailbox message received
    -SYSTEM-W-ENDOFFILE, end of file
    %JBC-E-SYMDEL, unexpected symbiont process termination
    -RMS-F-XAB, invalid XAB or XAB not accessible at 00000000
    
    I restarted the OA$FORMATTER queue and all seems well now but I would
    like to know what caused this problem and if/how it can be avoided.
    
    VMS v5.3-1 (a VAX 6430 which is part of a VAXcluster)
    ALL-IN-1 v2.3
    
    advTHANKSance...
    
    Kyle
T.RTitleUserPersonal
Name
DateLines
57.1Anyone there?SWAM2::MIYAMOTO_KYKyle Miyamoto DTN 531-5286Wed Feb 26 1992 20:135
    Since I'm not getting any replies, does anyone know to whom I can send
    mail to to get an answer?  How about another notes conference to
    cross-post it?
    
    Kyle >-(
57.2Too much rain?A1VAX::BARTHBridge-o-matic does it again!Thu Feb 27 1992 14:297
If you can't reproduce it, then it could be anything.  A flaky memory
module, a loose connection, a power hit, or even a software problem :^)

Since you are running V2.3 (you don't state which patch level you are at)
it's also possible that it's something which is fixed in V2.4.  

K.
57.3Tell me more!EEMELI::SALMINENHannu Salminen, PTG -FinlandMon Mar 09 1992 09:1017
OA$FORMATTER  errors may be due to many other sw. 
So, please tell more abouth the environment in your cluster:

	- Is there WP installed?

	- Startup order (DECWindows, ALL-IN-1, WP?)

	- Startup mode (direct/trough submit)

	- Is OA$FORMATTER a generic queue system or only in some
	  certain node of the cluster. (I remember this was common in v2.3)

	PROBLEM/SOLUTION kind of stories for this kind of OA$FORMATTER
	errors can be found from TIMA/STARS OA1 database.


					Regards,	Hannu