[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

927.0. "First print to OA$FORMATTER after re-boot problem" by COMICS::TALBOT (Trevor Talbot) Thu Jun 25 1992 11:29

    Hi,
    
    
    	Can anyone suggest the cause/fix for the following symptoms...
    
    A customer on vms 5.5 ALL-IN-1 v2.4 has a weekly problem with
    oa$formatter. They shutdown and re-boot the cluster each weekend and
    find that the very first job printed to the oa$formatter queue causes
    it to stop and the job doesn't print or the queue is crashed/dumped. 
    After a stop/queue/reset and start/queue oa$formatter all subsequent print 
    jobs go o.k until after the next re-boot. The first job has a final status 
    text in the accounting file of, 
    
    %SYSTEM-F-ACCVIO, access violation, reason mask=!XB
    
    	Some other final status codes found in the accounting file were:
    
    092F872A equates to, %WPSPLUS-E-GENERIC_MSG_TRA, error during operation
    092F868A equates to ?
    092F8562 equates to ?
    
    Where the 092F = WPS-PLUS facility.
    
    	They have re-linked to produce a new oa$formatter.exe and are using
    this image. There are no oa$formatter.dmp being produced at present,
    although when he was on vms 5.4 there were some. It doesn't matter if a
    priv'd user prints first or a non priv'd user. The same document is
    used on first and second prints.
    
    This problem according to the customer was seen from ALL-IN-1 V2.3 on
    vms v5.4, they have progressively upgraded s/w in the hope to clear it.
    This obviously hasn't worked, has anyone got suggestions on what to
    look at or for??
    
    
    -Trev
T.RTitleUserPersonal
Name
DateLines
927.1How and when is the OA$FORMATTER queue started?IOSG::NEWLANDRichard Newland, IOSG, REO1-D/4AThu Jun 25 1992 17:5821
I've seen a somewhat similar problem before.  It was caused by the site
having a command file which started all queues executing before the
ALL-IN-1 startup command file. 

This resulted in the OA$FORMATTER queue being started before the logical
KOA$HEAP_SIZE was defined, and therefore the KOALA heap size was 0 bytes. 
This meant that WPS-PLUS formats would fail.  However, ASCII formats would
still work because they do not use routines which require KOALA heap
storage. 

If the OA$FORMATTER queue was stopped and restarted some time later the
logical KOA$HEAP_SIZE had been defined and so a KOALA heap of sufficient
size was created and WPS-PLUS formats would work. 

Ask the customer if they are starting the OA$FORMATTER queue before the 
ALL-IN-1 start-up is performed.  Also, what happens if the very first 
background format job is for ASCII and not WPS-PLUS formatting?


Richard

927.2More of the same but I get a dump fileGIDDAY::SETHIMan from DownunderTue Jul 14 1992 07:4957
    Hi,
    
    I also have a customer with the same problem as .0. I have checked
    that OA$FORMATTER is not starting before ALL-IN-1 startup procedure has
    finished.  They are using the standard startup for ALL-IN-1 Version
    2.4 SYS$MANAGER:A1V24START.COM, KOA$HEAP_SIZE is defined as 96000,
    then the formatter queue is started.  ALL-IN-1 startup is submitted
    to a batch queue.  This is a VMS Version 5.4-3 system.
    
    When the first job is submitted the job is retained on error, the
    details are
    
    Server queue OA$FORMATTER, on VAX::, mounted form DEFAULT
        /BASE_PRIORITY=4 /DEFAULT=(FEED,FORM=DEFAULT) /OWNER=[SYSTEM]
        /PROCESSOR=OA$FORMATTER /PROTECTION=(S:E,O:D,G:R,W:W) /RETAIN=ERROR
    
      Jobname         Username     Entry  Blocks  Status
      -------         --------     -----  ------  ------
      PROBLEM_RISK_ELEMENTS__PORTFOL
                      HATTON         595       9  Retained on error
        %NONAME-E-NOMSG, Message number 092F872A
        Submitted 14-JUL-1992 13:01 /NOBURST /NOFLAG /NOFEED /FORM=DEFAULT
        /PARAM=("OA$PARAMS=000,PRINTER2,LN03,1,TEST3","OA$FMTCTL=2")
        /PRIORITY=100
        File: _$1$DIA1:[VAXUSERS.HATTON.A1]HAT005593.WPL;1 /NOBURST /DELETE
        /NOFEED/NOFLAG
    
    I could not get any details from accounting because they have enabled
    interactive process only.  However OA$FORMATTER as produced a dump file
    and I managed to get a few details from the dump file.
    
    $ analyze/process/full SYS$SYSROOT:[SYSEXE]OA$FORMATTER.DMP
    
    The command e/i @pc it gave the following details
    
    000D2D67:       MOVB     B^0FF(R1),B^13(R3)
    
    Also did an analyze/image and to check the image identification
    information 
    
            Image Identification Information
    
                    image name: "OA$FORMATTER"
                    image file identification: "ALL-IN-1 V2.4"
                    link date/time: 24-NOV-1990 14:42:23.95
                    linker identification: "05-05"
    
    I cannot find anything in Stars nor in previous notes.  If you require
    further information I shall be pleased to enter it.
    
    Thanks for your help
    
    Sunil
    
    What ever happened to the paperless office ?  Printer problems give me
    the :-(. 
                        
927.3More informationIOSG::NEWLANDRichard Newland, IOSG, REO1-D/4ATue Jul 14 1992 16:0416
Sunil,

1.  Does the creation date of the OA$FORMATTER.DMP file indicate that the 
    dump occurs when the first job is submitted to OA$FORMATTER queue.

    From the SHOW QUEUE information it appears that OA$FORMATTER is
    reporting the error returned to it from the WPS-PLUS formatter routine,
    and is doing what it is expected to do. 


2.  What happens if the first job sent to OA$FORMATTER is an ASCII format?
    It would be useful to know if it is the first job or the first WPS-PLUS 
    format job which fails.


Richard
927.4GIDDAY::SETHIMan from DownunderWed Jul 15 1992 04:0518
    G'day Richard,
    
    Having looked at the date of creation for the dump file and the date of
    the first job.  The dump occured soon after the job was submitted.
    
    The customer is re-booting the system this weekend.  I have asked her
    to create a file within ALL-IN-1 using EDT as the editor and print it. 
    Then print a WPS-PLUS file.
    
    At each stage I have asked her to check for any error and do a show
    que/dev/full oa$formatter.  If a job does stall check for a dump file.
    
    Hopefully I'll have some more details for you soon is there any more
    information you require ?
    
    Thanks
         
    Sunil
927.5Stop and restart OA$FORMATTERIOSG::NEWLANDRichard Newland, IOSG, REO1-D/4AWed Jul 15 1992 10:4515
Sunil,

Could you also get the customer to try the following.  After the system is
booted, ALL-IN-1 is started and OA$FORMATTER is running stop and restart
the OA$FORMATTER queue by doing:

	$ STOP/QUEUE/NEXT OA$FORMATTER
	$ START/QUEUE OA$FORMATTER

This will cause a new copy of the Symbiont image to be started.  I want to 
find out if the problem occurs every time OA$FORMATTER is started or only 
when it is started as part of a reboot and restart of ALL-IN-1.


Richard
927.6ASCII job prints okay not WPS-PLUSGIDDAY::SETHIMan from DownunderMon Jul 20 1992 03:1618
    G'day Richard,

    The customer re-booted the system this weekend and carried out the
    tests as requested.

    1. An ASCII file was printed as the very first file and it printed
       okay.  Then a WPS-PLUS file was printed and it was retained on error
       as before.  The customer did a STOP/QUEUE and START/QUEUE and sent
       another WPS-PLUS document to be printed this was retained on error
       and had an error message of %NONAME-E-NOMSG, Message number
       092F868A.

    2. Re-boot number two the customer did a $ STOP/QUEUE/NEXT OA$FORMATTER
       and START/QUEUE OA$FORMATTER.  A WPS-PLUS document printed okay.

    Thanks for your help
    
    Sunil
927.7Use Job ServicesIOSG::NEWLANDRichard Newland, IOSG, REO1-D/4AThu Jul 23 1992 19:2213
>    1. An ASCII file was printed as the very first file and it printed
>       okay.  Then a WPS-PLUS file was printed and it was retained on error
>       as before.  The customer did a STOP/QUEUE and START/QUEUE and sent
>       another WPS-PLUS document to be printed this was retained on error
>       and had an error message of %NONAME-E-NOMSG, Message number
>       092F868A.

Could you use ALL-IN-1 Job Services to get the job information so that the 
WPS-PLUS error id 092F868A is converted to a text string.


Richard

927.8The requested information from JSGIDDAY::SETHIMan from DownunderFri Jul 24 1992 05:0417
    G'day Richard,
    
    1. result from test 1 printed ASCII file first than WPS-PLUS
    
    The text string was converted to the following
    
     Retained job reason:
         %WPSPLUS-E-GENERIC_MSG_TRA, Error occurred during operation
    
    2. Another job had the following error
    
     Retained job reason:
         %WPSPLUS-E-SHARING_NOT_ALL, Cannot share files
     
    Thanks
    
    Sunil
927.9Ask in WPS-PLUS conferenceIOSG::NEWLANDRichard Newland, IOSG, REO1-D/4AFri Jul 24 1992 14:5212
From the information you have supplied the only consistent thing I can see 
is that the problems occur only with the WPS-PLUS Formatter.  Since these
problems do not occur on most system I can only guess that there is 
soemthing about the way your system is set up that causes the WPS-PLUS 
formatter to have problems.

I suggest you ask in the WPS-PLUS conference to see if anyone can suggest 
what types of problems cause the WPS-PLUS formatter to report the errors 
you have seen.


Richard