[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | DECforms |
Notice: | This is not an official software support channel. Kit info: 4.L |
Moderator: | DSSDEV::FORMS |
|
Created: | Thu Mar 23 1989 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4004 |
Total number of notes: | 16520 |
3991.0. "Strange CDD problem when converting from TDMS" by OSBONN::PER (Per Nisslert, SWAS Gothenburg, Sweden) Thu Mar 20 1997 11:15
As part of a VAX-to-Alpha port of an application we will convert from
TDMS to DECforms. We do have the PRAXA product, but are experiencing
what looks as CDD problems (surprised?). CVTDMS says something along
the lines of "expected to find CDD$REQUEST_LIBRARY, found &�"(/$%&�.
Yes, the output is actually garbled similar to the above, which to me
indicates a bug in the PRAXA product. We have tried all sorts of tricks
to verify the CDD, but to no avail.
Just for the fun of it, I decided to try the converter supplied by
DECforms. Lo and behold, DECforms at least gave a readable error
message, similar to "protocol of object is CDD$DIRECTORY instead of
CDD$REQUEST_LIBRARY". Looking at the object with all sorts of DMU
commands, reveals nothing strange, it does look like a perfectly
ordinary TDMS request library.
Now, has anybody seen anything remotely resembling this?
I might add that the CDD we are reading is in active use by the
application developers on VAX without any (apparent) problems.
Any ideas are welcome!
Per
T.R | Title | User | Personal Name | Date | Lines
|
---|