[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

1500.0. "%OA-E-BF_INVPARAMS when printing/queue man dies" by KIRKTN::GMURRAY (Have Mercy I Cry City !) Thu Sep 24 1992 12:53

    
    	Hi,
    
    	When trying to print to any queue from a newly upgraded Diamond
    system, I get the following error :
    
    	%OA-E-BF_INVPARAMS, Invalid or missing OA$PARAMS value
    			 Background formatter job A_GIL_DOCUMENT (entry 624) tes
    
	This error just repeats and repeats. When I look at the formatter
    queue, bizarre things are happening, ie :
    
    	Server queue OA$FORMATTER, busy, on OISDEV::, mounted form DEFAULT
    
        Entry  Jobname         Username     Blocks  Status
        -----  -------         --------     ------  ------
          618  PRINT           ALLIN1           15  Starting at block 12735
          623  A_GIL_DOCUMENT  ALLIN1           95  Starting at block 31730
          675  LOG_AND_STATUS  ALLIN1            7  Starting at block 2345
          624  A_GIL_DOCUMENT  ALLIN1           95  Pending
    
    	After a short while, the queue manager stops !
    
    	I'm trying a relink to see if that will cure it. Has anyone seen
    anything like this before ?
    
    	Thanks,
    
                Gil
T.RTitleUserPersonal
Name		DateLines
1500.1Relink didn't helpKIRKTN::GMURRAYHave Mercy I Cry City !Thu Sep 24 1992 13:5418
    
    	Nope, the relink didn't do it.
    
    	A directory of oa$build:oa$formatter gives :
    
    	Directory DISK$ALLIN1:[ALLIN1.SOURCES_BRITISH]
    
    	OA$FORMATTER.EXE;2   24-SEP-1992 11:34:28.80   1660 blocks
    
    	Directory DISK$ALLIN1:[ALLIN1.SOURCES_SHARE]
    
    	OA$FORMATTER.EXE;13   6-FEB-1992 14:53:34.45   1780 blocks
    
	So it looks like it would pick up the correct version alright.
    
    	Confused,
    
    			Gil
1500.2Move it to SYS$SYSTEMKAOFS::M_MORINLe diable est aux vaches!Thu Sep 24 1992 14:437
You must move OA$FORMATTER.EXE to SYS$SYSTEM yourself.  Once you've done that
check that the one you just moved is the latest one.  i.e. there shouldn't be
one in SYSROOT overriding it.  If this was the case, then stop OA$FORMATTER,
delete it, and re-start it with oa$formatter_start.com

Mario
1500.3See topic 134IOSG::NEWLANDRichard Newland, IOSG, REO1-D/4AThu Sep 24 1992 14:5526
There are two issues here:

1.  Symbiont image .EXE files are always run from SYS$SYSTEM.  Do a
    directory of SYS$SYSTEM:OA$FORMATTER.EXE and check that you are running 
    the new OA$FORMATTER.

    Running an old OA$FORMATTER is probably the cause of the
    '%OA-E-BF_INVPARAMS, Invalid or missing OA$PARAMS value' errors because 
    the new V3.0 print sub-system will be creating jobs on the 
    OA$FORMATTER queue which the old OA$FORMATTER cannot execute.


2.  What version of VMS are you using?

    There were problems in the new VMS job controller shipped with VMS 
    V5.5.  One of the problems that occurred is exactly what you reported, 
    that is, after OA$FORMATTER reported an %OA-E-BF_INVPARAMS error the
    VMS Job Controller would keep scheduling the same job and eventually
    crash. 

    The problems with the VMS V5.5 Job Controller are discussed in topic
    134 in this conference. 


Richard
1500.4SYS$SYSROOT:[SYSEXE]OA$FORMATTER as diagnosed MASALA::GMURRAYHave Mercy I Cry City !Thu Sep 24 1992 20:5414
    
    	Thanks Mario, Richard,
    
    		You were both right - I had an old version of
    	OA$FORMATTER.EXE in SYS$SYSROOT:[SYSEXE]. After I had deleted it,
    	and started anew, everything worked fine.
    
    		To answer you question - we are running VMS 5.5, and 
    	thankfully not experiencing that other problem !
    
    		Cheers,
    
    				Gil