T.R | Title | User | Personal Name | Date | Lines |
---|
1606.1 | Depends on the Document type | IOSG::NEWLAND | Richard Newland, IOSG, REO1-D/4A | Wed Oct 14 1992 12:15 | 18 |
| The parts of CDA used by ALL-IN-1 V2.4 when printing depends on the type of
document being printed and the type of output being produced. Some
document types will not use use CDA at all.
ALL-IN-1 will call the CDA Convert routine, specifying the formats of the
input and output files. The CDA routines will then invoke the appropriate
front end and back end as specified by the file formats. For example if
you a printing a DDIF document to a PostScript printer then front end will
be 'DDIF' and the back end will be 'PS'.
What type of documents cannot be printed, and what errors are being
reported?
Can you do an equivalent CDA convert from DCL?
Richard
|
1606.2 | Some more info | SEDTU5::Glyn-Davies | | Wed Oct 14 1992 12:28 | 13 |
| Richard,
I am picking this up from Christine and I have a little bit more information.
I believe that the customer is trying to print WPS-PLUS files.
The problem seems to occur when they try to start the OA$FORMATTER queue. This
results in a 'file not found' message but no indication of what the file in question
is.
Hope this helps,
Glyn
|
1606.3 | Try $ RUN OA$FORMATTER | IOSG::NEWLAND | Richard Newland, IOSG, REO1-D/4A | Wed Oct 14 1992 12:57 | 14 |
| In ALL-IN-1 V2.4 OA$FORMATTER does not perform CDA formatting, so I'm
puzzled that upgrading CDA has caused it to fail.
If the OA$FORMATTER queue cannot be started it may be that the
OA$FORMATTER.EXE image cannot be activated. If you do:
$ RUN SYS$SYSTEM:OA$FORMATTER.EXE
you may get some more error messages from the image activator which will
indicate which file cannot be found.
Richard.
|
1606.4 | Wrong version of IMG$SHRLIB.EXE | SEDTU5::Glyn-Davies | | Thu Oct 15 1992 16:29 | 21 |
| Richard,
Thanks for you help.
I have just returned from the customer and everything is running OK now.
I ran the OA$FORMATTER.EXE from the DCL command line and got the
following error:
Image file not found [SYSLIB]DECW$XMLIBSHR.EXE.
After some ferreting around it looks as if the OA$FORMATTER links
against IMG$SHRLIB.EXE which in turn was linked against
DECW$XMLIBSHR.EXE.
I restored the old copy of IMG$SHRLIB.EXE, restarted OA$FORMATTER.EXE
and everything now works fine.
Thanks again,
Glyn
|