Conference iosg::all-in-1_v30

883.0. "OA$SCRIPT_SYMBIONT will not start" by KERNEL::OTHENJ () Wed Jun 17 1992 13:10

Hi,

	Can someone help me with my understanding of the Script Symbiont??

	A customer is using ALL-IN-1 v3.0 with a5.5. The customer did a 
relink after the VMS upgrade, and had problems with the script symbiont 
after that.

When he tries to start the script symbiont queue, he receives the error

%jbc-e-symdel, unexpected symbiont process termination
-jbc-e-symcreprc, error creating symbiont process !as

	The customer installed v3.0 on 17-May, and has a date on 
sys$system:oa$script_symbiont.exe of 12-mar, which is the same as our 
system. I told the customer to delete the queue , using the commands below, 
and this is the result;

@oa$lib:script_queues_all delete
%DELETE-I-DELETED, OA$SCRIPT_BRITISH deleted

$ show que/full oa$script_british
%jbc-e-nosuchque, no such que

@oa$lib:script_queues_init british

$ show que/full oa$script_british
Server queue OA$SCRIPT_BRITISH, stopped, on CD4000::, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /NOENABLE_GENERIC
  /LIBRARY=BRITISH /OWNER=[SYSTEM] /PROCESSOR=OA$SCRIPT_SYMBIONT
  /PROTECTION=(S:E,O:D,G:R,W:W) /RETAIN=ERROR /SCHEDULE=(NOSIZE)

@oa$lib:script_queues_all start
%jbc-e-symdel, unexpected symbiont process termination

$ show que/full oa$script_british
Output queue OA$SCRIPT_BRITISH, stopped, on CD4000::, mounted form DEFAULT
  /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /NOENABLE_GENERIC
  /LIBRARY=BRITISH /OWNER=[SYSTEM] /PROCESSOR=OA$SCRIPT_SYMBIONT
  /PROTECTION=(S:E,O:D,G:R,W:W) /RETAIN=ERROR /SCHEDULE=(NOSIZE)

	As soon as he tries to start the queue, the queue turns into an 
output queue! I have looked through notes etc, and cannot find a similar 
situation to this. No process oa$symbiont_nnn processes are running, or 
hibernating, on the system. the customer has not customised any of the 
command files above.

	The customer does not have a co-existent system.

		Any ideas what could be causing the problem??


			Thanks
				Julie
    

The job controller and the script symbiont are obviously not talking to each 
other here!

> 	As soon as he tries to start the queue, the queue turns into an 
>       output queue! 

This seems to be standard behaviour when a symbiont goes down, the queue 
reverts to a print queue or an output queue. I'm not sure that it really means
anything.

Could you try de-installing the OA$SCRIPT_SYMBIONT.EXE image, and then attempt 
to restart the queue with OA$SCRIPT_QUEUES_ALL START? This may fix the problem.

Cheers,
Derek

    Hi!
    
    The hint in .1 worked for me, except that I had to do a
    @OA$LIB:OA$SCRIPT_QUEUES_INIT BRITISH first.
    
    Why does it matter if the symbiont is installed in memory?
    
    Best regards,
    Allan

	It's a mystery to me. I only discovered this by accident on an A5.5
	system which John Wolfe gave me access to. I haven't discovered 
	whether the problem is general to all A5.5 systems, or whether the
	problem is system-dependent.

	Cheers,
	Derek

    Hi,
    
    	Thanks for the replies - I have also found that by de-installing
    the oa$script_symbiont image, and then re-init the queue, the problem
    was solved. Does anyone know out there why the image cannot be
    installed??
    
    
    				Julie