[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

3394.0. "NOSUCHFORM on OA$FORMATTER queue..." by TAV02::CHAIM (Semper ubi Sub ubi .....) Thu Oct 14 1993 09:56

I just implemented our first UPGRADE from an ALL-IN-1 V2.4 system to V3.0-1
(Hebrew). 

The installation itself went very smoothly. However, once the system was up and
running we discovered that we couldn't print to certain printers using specific
printer types via the oa$formatter. The error being returned was "No such
form".

The oa$formatter queue had retained on error, and I was able to see that the
there was indeed an error in the form name being passed in oa$params. It looked
something like this:

"OA$PARAMS=000,SYS$PRINT,LA210,  1,OA$HLS_13"
                               ^^           ^

NOTICE:

1. Two spaces preeceeding the COPIES parameter (usually not there)
2. The LAST character of the FORM name has been truncated.

o Printing directly to queue is fine
o The oa$printstyles.dat contains the correct form name
0 A1TRACE shows that the FORM name IS complete in the oa$params string
o Some styles work fine. I compared these with the ones that don't work (PT) 
  but I couldn't see any apparent differences.



I attempted to DELETE the LA210 entry and recreate it. After this creation it
did work the first time. However after EDITING it from the PT form, it became
"corrupted" again. 

I'm totally confused.

Thanks,

Cb.


T.RTitleUserPersonal
Name
DateLines
3394.1Customizations?IOSG::NEWLANDRichard Newland, IOSG, REO2-G/L2Thu Oct 14 1993 14:266
Are there any customizations?  

Have you tried running ALL-IN-1 with /NOCUSTOM? 


Richard
3394.2COPIES field cannot be RIGHT-JUSTIFY ...TAV02::CHAIMSemper ubi Sub ubi .....Thu Oct 14 1993 19:1910
It was not customization, however it was due to the fact that the COPIES field
on the WPPARG form (for Hebrew) was a right-justified field. I set this
attribute to the COPIES field on an ENGLISH system, and got the same behavior.

So it is a problem deep in the guts of ALL-IN0-1. However, the work-around is
satisfactory.

Thanks,

Cb.