![]() |
||||||||
![]() |
||||||||
![]() |
![]() |
![]() |
![]() |
![]() |
||||
![]() |
||||||||
Products | Support | Download | Contact | |||||
![]() |
Contents | Index | About the Icons
Earlier versions of PathWay from Wollongong had an incompatibility
with ScriptServer for OpenVMS. Attachmate's
version of PathWay appears to have addressed those issues.
If you're running an early version of Wollongong's Pathway
for VMS, click here for the old Technical
Memo; we suggest you consider upgrading. A discussion of what the issue was
and how we have tested with the current version follows.
ScriptServer's TCP/IP implementation is coded to Digital Equipment Corporation's
UCX Application Programming Interface (API). The success of this practice depends
on how well a vendor's TCP/IP implementation supports the UCX API. There were
problems in earlier versions with some of the non-synchronous receipt of messages
that ScriptServer relies upon in its default configuration that necessitated
the disabling of backchannel when using Wollongong's Pathway product.
Pathway for OpenVMS 3.0 was installed on a VAXStation 3100 running VMS 5.5-2. ScriptServer v5.1-1 was then used to create a TCP/IP queue on an HP LaserJet 4M Plus printer and our standard battery of tests was run. The queue started and performed in an entirely uneventful and expected manner.
© 2020 GrayMatter Software Corporation | ![]() |
Privacy policy | ![]() |
Terms of use |