| TLE has been trying to solve this problem for weeks, without success.
They do everything imaginable; the destination still isn't recognized.
If they ever solve it and can figure out why, I'll post the fix.
One problem we ran into on our cluster did not manifest itself as
"unrecognized destination." Instead, there was some sort of "font not
found" message well along in the process. The problem was that
DOCUMENT V1.1 puts its startup file in sys$startup instead of
sys$manager, but we were still executing the old one in sys$manager.
Once we found this, the process worked fine.
Good hunting.
Andy
|
| I'm not sure if I can help, but I'll try
First of all, you don't need DECwindows, RAGS, MOPS, UTOX, or VOYER
installed to use the online doctype.
You do need the SDC version of DOCUMENT V1.1. This must be the REAL
SDC version, not the V1.1 that was pre-released internally a couple
weeks earlier or a field test version. I don't remember why, but it
has to be the latest.
Then you need to install the internal kit.
Finally, you need to backup the CUP$VOILA saveset. Make sure you
specify /NEW_VERSION on the BACKUP command.
After you have done these 3 steps, you should be able to find the
VOILA doctype in DOC$DESTINATIONS.DAT (I forget which one, local or
standard). You should also be to do directory listings of
DOC$VOILA_TOOLS: and DOC$VOILA_FONTS: If these fail, retrace your
installation steps.
The other thing to check is that you are not running an old setup
file (as mentioned in .1) or calling an old setup file from your
login.com.
I hope this helps.
joe
|
| If the following is your welcome message, then you are very likely running
V1.1 instead of FT1.1, because the CUP/ML kit was released with
instructions only for installing on V1.1.
I think you can check the version in your .LOG file or on the screen
when you run DOCUMENT--the version should come up right after you
enter the DOCUMENT command.
Running DOCUMENT V1.1, with CUP/ML local kit V1.1. Type SDMLINFO for details.
|