T.R | Title | User | Personal Name | Date | Lines |
---|
3149.1 | Its still needed | SYSTEM::HELLIAR | http://samedi.reo.dec.com/ | Fri Jun 06 1997 08:41 | 8 |
| COlin,
The translation license is STILL needed, either separately or as part
of one of the package licenses. Tne only except to this, is if you ONLY
use the by-pass translation feature and hence dont need any translation
services.
Graham
|
3149.2 | Contact for Order Nos? | BERN02::MUNT | | Fri Jun 06 1997 13:20 | 10 |
| Graham,
Thanks for the reply. Unfortunatley as I mentioned the SPD for V3.1A
does not list the licenses and
order numbers for Translation Services. The customer in question
requires both TRADACOMS and EDIFACT. Are 2 licenses required? Do you
know where I could find the order numbers?
Thanks
...colin
|
3149.3 | Just the one | METSYS::HELLIAR | http://samedi.reo.dec.com/ | Fri Jun 06 1997 15:13 | 9 |
| Colin,
I've asked for the part number of the Translation License.
As far as I am concerned only one Translation license need be
purchased per server. i.e. the one license covers EDIFACT/ODETTE,
X12/TDCC, and TRADACOMS.
Graham
|
3149.4 | translation license is a red herring on UNIX | SYSTEM::REID | David Reid, EDI engineering | Fri Jun 06 1997 15:18 | 14 |
| Actually, you only need the package license, as this includes
translation, comms (of your choice) and application client
In addition you need the CommandCenter license (for UNIX) or
the FileBridge development license (for OpenVMS).
The reason the translation license was in the internal PAKs
is historical.
You cannot buy DEC/EDI without one of the Comms options.
I hope that helps,
d:){=| David.
|