Conference iosg::all-in-1_v30

    Pam,

>However, there is a LN03.PRA in WPL$PRT (correct prots etc) - there is also
>an LN03A4.PRA there as well - if I change the printer device in the PT to
>LN03A4 it finds it (although does not print correctly) - but cannot find that
>of the LN03.

    Does a GOLD/L on the printer device field list the LN03 as a selection?

    You might also want to try printing with `hold job' and doing a
        $SHOW ENTRY/FULL
    of a job that fails, and of one using the LN03A4.PRA. See if there is
    any obvious difference (& post results here)

    Cheers,
        Paul.

1.  What happens if you do the formatting in the foreground?  The answer to
    this will show if it is only the background formatter which has
    problems accessing the LN03.PRA file. 


2.  Could you do the following and post the results.

    1.  $ STOP/QUEUE OA$FORMATTER to pause the background formatter queue

    2.  Submit a job to the background formatter as normal.

    3.  Do a $SHOW ENTRY/FULL

	The third parameter in the OA$PARAMS string is the name of the 
	device type which is passed to the WPS-PLUS formatter.  Is it 
	'LN03'?

    4.  $ START/QUEUE OA$FORMATTER to resume the queue


3.  Do you have any logical names called 'LN03' defined?  The WPS-PLUS
    formatter can have problems opening Printer Attribute files if a
    logical name is the same as the device type parameter. 



Richard

<< 3.  Do you have any logical names called 'LN03' defined?  The WPS-PLUS
    formatter can have problems opening Printer Attribute files if a
    logical name is the same as the device type parameter. 


It's always the easy ones that catch you out isn't it!

YES - there was a system logical LN03 defined for some reason - it's not
my system.  Worked OK once deassigned.  However, them fell fowl of the
VMS V5.5 & script symbiont problems - would not process PSPRINT, retained on
error.  Tried delete script server queues & init new ones but still problems.


Thanks for everyone's help.

Pam

PS Sorry for spelling errors - this is a ver slow remote line!!

I am having problems printing an .ln03 document from ALL-IN-1 3.0.

    I used the Update option from EM to set handling to LN03. From the print 
    menu I selected the LN03 print style and used GOLD Expand to change 
    PASSALL to Yes.

The job is always retained. So I used the technique described in .2 of stopping 
the queue and so on. While the queue was stopped $ sh entry /full gave the 
following :


  TEST            ALLIN1         712      56  Pending (queue paused)
    On Server queue OA$FORMATTER
    Submitted  4-JUN-1992 10:47 /NOBURST /NOFLAG /NOFEED /FORM=DEFAULT
    /PARAM=("OA$PARAMS=000,EUC1,LN03,1,OA$HLS_80","OA$FMTCTL=0") /PRIORITY=100
    /NOTRAILER
    File: _$1$DIA1:[ALLIN1.MGR.OA$TEMP]ZUECFEP9W.LN03;1 /NOBURST /NOFEED /NOFLAG
        /PASSALL /NOTRAILER

Starting the queue gave the following :

$ start/queue oa$formatter
Background formatter job TEST (entry 712) terminated with error status
%OA-E-BF_INVPARAMS, Invalid or missing OA$PARAMS value

But I don't know which OA$PARAMS value to change.
 
Steve.

I like my VXT2000: cut from STARS, paste in notes.....


If an old OA$FORMATTER.EXE file which is in SYS$SYSROOT:[SYSEXE] and          
is being executed instead of the new V2.4 file which is put in                
SYS$SYSCOMMON:[SYSEXE] you will see this problem.                             
                                                                              
This can be verified by:                                                      
                                                                              
    1.  Do a $ SHOW QUEUE/FULL OA$FORMATTER, and look for the 'on node::'     
        information.                                                          
                                                                              
    2.  Login to the 'node' and do a $ DIR SYS$SYSTEM:OA$FORMATTER.EXE and    
        see if there is an old file in SYS$SYSROOT and a newer file in        
        SYS$COMMON.                                                           
                                                                              
If so, delete the old file in the SYS$SYSROOT directory, stop and delete      
the OA$FORMATTER queue then restart the queue using:                          
                                                                              
  @OA$BUILD_SHARE:OA$FORMATTER_START OA$                                      

The print jobs should now complete successfully.                              
                                                                              
\The V2.3 OA$FORMATTER.EXE file is 1635 blocks                                
\the V2.4 OA$FORMATTER.EXE file is 1777 blocks