[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

3730.0. "problems starting OA$FORMATTER under OpenVMS V6.0" by GIDDAY::JOYCE (Okay, who moved the goalposts?) Wed Jan 05 1994 01:07

Folks,

	I have a customer with the following problem...

	Over the Xmas break they upgraded their system to OpenVMS V6.0.  
	They relinked ALL-IN-1 and moved all the new images into the right
	places as instructed in the doco.

	When they reboot the system the OA$FORMATTER queue doesn't start and 
	they get the following error message...

		Starting OA$FORMATTER queue

		%OA-W-SNDJBC_OPERR, SEND_JBC operation error
		-SYSTEM-F-PROTINSTALL, protected images must be installed

	When the subsequently login they can manually start the queue using
	$ start/queue oa$formatter.  They can alternatively rerun the ALL-IN-1
	startup interactively and the queue is started okay.

	So, I think, that "something" is missing at the time that ALL-IN-1 is
	being started during reboot and that "something" is somehow present by 
	the time they can login to start the queue interactively.  They have
	not altered the order in which the layered products are started and
	ALL-IN-1 is fairly late in the order.

	I got them to edit the startup to SET WATCH and SET VER and got them
	to reboot.  The relevant extract (I think) of the log file is at the
	end of this note.  What is shows is that the error message is output
	immediately after an access to the PASMSG.EXE image but my guess is
	that this image is in fact used to display the error message.

	They have the one OA$FORMATTER queue; that is, they are not using
	generic and execution queues.  Their OA$FORMATTER_START.COM is also 
	at the end of this note.

	They have a simple work around - manually start the queue after a 
	reboot (adding the command to the end of SYSTARTUP_VMS.COM appears 
	to result in the same error) but understandably they are not satisfied
	to leave it like this and would like to know what's gone wrong!

	What images would SEND_JBC be looking at at this stage?

	After looking at this for two days, I need some help!

Thanks, Andy

*** SET WATCH log (extract) .....

$ @oa$build:OA$FORMATTER_START.COM OA$
$ !     OA$FORMATTER_START.COM
$ a1prefix = P1
$ processor = "OA$FORMATTER"
$ queue = "OA$FORMATTER"
 Starting OA$FORMATTER queue
$ If node .eqs. "WRBOOT"
$  then
$   ALLIN1/NOINIT/OVERRIDE
    SEND_JBC CREATE_QUEUE /PROCESSOR=CLI$PROCESSOR /QUEUE=CLI$QUEUE /WSEXTENT=800 /NO_GENERIC_QUEUE /RETAIN_ERROR_JOBS /CREATE_START
%XQP, Access PLIMSG.EXE;1 (5213,78,0) Status: 00000001
%XQP, Access PASMSG.EXE;1 (5210,91,0) Status: 00000001
%OA-W-SNDJBC_OPERR, SEND_JBC operation error
-SYSTEM-F-PROTINSTALL, protected images must be installed
$  endif
$ EXIT
%XQP, Access A1V30START.COM;1 (7141,159,0) Status: 00000001

*** Extract from OA$FORMATTER.COM file...
	
$ a1prefix = P1
$ processor = "''a1prefix'FORMATTER"
$ queue = "''a1prefix'FORMATTER"
$ Node = f$getsyi("NODENAME")
$ If node .eqs. "WRBOOT"
$  then
$   ALLIN1/NOINIT/OVERRIDE
    SEND_JBC CREATE_QUEUE /PROCESSOR=CLI$PROCESSOR /QUEUE=CLI$QUEUE -
	 /WSEXTENT=800 /NO_GENERIC_QUEUE /RETAIN_ERROR_JOBS /CREATE_START

{The SEND_JBC line is wrapped for the purposes of this note}

T.RTitleUserPersonal
Name
DateLines
3730.1NoneIOSG::NEWLANDRichard Newland, IOSG, REO2-G/L2Wed Jan 05 1994 11:1412
>>	What images would SEND_JBC be looking at at this stage?

SEND_JBC does not directly look for any images.  It sends a request to the 
Queue Manager which attempts to run the image (OA$FORMATTER) which is 
defined as the 'processor' for this queue.

My guess is that a shareable image referenced by OA$FORMATTER now has a 
reference to PASMSG.EXE.


Richard

3730.2$ RUN SYS$SYSTEM:OA$FORMATTER.EXE?KERNEL::LOATStop throwing those bloody spears!Wed Jan 05 1994 16:206
    
    How about running the OA$FORMATTER.EXE image interactively, and seeing
    what errors appear? Normally gives better error messages.
    
    Steve.