Can a custom OpenVMS application communicate (read/write) to the latest PI3 (PI on Windows Server)?
PINet and PIonPINet are custom compiled to run against a specific PI Server and version.
If PINet is compiled against a PI3 Server version, it will work against the latest (2015) version of PI Server. Note that some functionality may be limited and this was never officially tested.
We no longer make PINet reshipments, because HP discontinued OpenVMS support:
With Hewlett-Packard’s discontinuation of OpenVMS support, OSIsoft can no longer guarantee our support of the PI System running on OpenVMS.
Operating System Alert: Support for OpenVMS and OSIsoft Software
However, we still offer technical support (through June 30th, 2016) in case you'd like to transition from OpenVMS.
If you are interested in upgrade scenarios, please contact your account manager. I'm copying our OpenVMS guru on this thread, Chuck Thompson.
We currently have two sets of PI2 systems running, wherein on the PI2
Server exist custom model code that communicates to PI via PI-API calls.
We're in the process of migrating to the latest PI3 Windows Server
platform, which appears to be straight-forward regarding the PI upgrade
(PI2 to PI3). However, we've just learned that the remaining custom model
code that also resides on the PI2 Server will not be able to communicate
from the OpenVMS (existing location) platform to the new PI3 Windows
Is there anyone out there that has encountered this problem or has a
Tech support for OSIsoft products on OpenVMS platforms (VAX, Alpha, Itanium) are generally extended to end of 2016. However, if you have an interface or an application node on OpenVMS platform, it is time to contact me or your OSIsoft account manager to discuss alternatives and a path forward.
Hi Dave - Your applications are probably not written using PI-API, but rather an even older set of programming tools called PI Toolkit. PI Toolkit was never available on other than the OpenVMS platforms and PI-API was only partially available on OpenVMS platforms.
If moving your applications to a supported OpenVMS's Itanium platform is not an option, your next best bet would appear to be re-writing applications for an alternate platform such as Windows or Windows Core. In many cases porting an existing application from OpenVMS to other platform isn't a cut & paste. Things like system services and system architecture will be very different - often large changes are required. For this reason we recommend customers consider rewriting applications and use of developer technologies and data access tools more in line with mainstream of PI System, e.g. AF SDK or ODBC or web services. While you are at it, you can also consider application implementation to take advantage of new functionality of PI System such as AF Analytics, AF asset model, and so on.
Retrieving data ...