| Date: 28-MAY-1997 08:52:52.82
From: DEC:.REO.REOVTX::WOOD_J "[email protected]"
Subj: Digital ASAP #29063: DECnet Plus
To: smtp%"[email protected]"
Hello Rod,
Re. problem logged with Digital ASAP re. DECnet Plus (#29063)
>My problem is with a client/server application using the DECnet
>non-transparent task-to-task programming interface.
>The application is written in C++ and uses $QIO calls.
>
>It works on VAX/VMS under VMS 5.5-2 -> 7.0 with DECnet Phase IV
>and I am now trying to build and run it under Alpha OpenVMS 7.1
>with DECnet Plus.
It sounds like you are changing most aspects of your build
environment: from VAX hardware to Alpha hardware; from OpenVMS
v7 to v7.1; from DECnet ph. IV to DECnet Plus; and from DEC C++
for OpenVMS VAX to DEC C++ for OpenVMS Alpha. Of these the changes
in hardware and DECnet are likely to be the most signifigant.
There is a guide to "Migrating an Application from OpenVMS VAX
to OpenVMS Alpha" located on the OpenVMS Alpha operating system
documentation compact disk, in Bookreader format. This describes
how the differences between the VAX & Alpha architectures affect
porting an application. Issues such as: data alignment; different
page sizes; and preserving the integrity of shared data are covered
in the guide.
To answer your specific questions on DECnet, I enclose extracts
from the "DECnet-Plus Planning Guide" manual which is on the
March 1997 OpenVMS Alpha layered product documentation compact
disks:
>1. the application should run under Alpha OpenVMS 7.1 with DECnet Plus
Yes your application should recompile & run under OpenVMS Alpha v7.1
with DECnet Plus, using the same $QIO interface. This assumes that your
application doesn't use undocumented/unsupported $QIO calls (e.g. such as
some of the special NETACP functions).
From the Planning manual:
++++
1.7 DECnet Phase IV Applications
DECnet-Plus supports DECnet Phase IV applications as
described in the following sections.
1.7.1 DECnet for OpenVMS Phase IV Applications
DECnet for OpenVMS Phase IV applications that use Queue
I/O Request ($QIO) system service calls continue to work in
DECnet-Plus without changes. You do not have to change
node names to DECnet Phase V format.
DECnet-Plus for OpenVMS offers both the $IPC and $QIO
interfaces. OpenVMS Interprocess Communication ($IPC)
system service is an operating system interface that is
new with DECnet-Plus for OpenVMS. This interface to
the Session Control layer lets you use DECnet software to
perform interprocess communications.
With $IPC, you can connect to the target application by
specifying its full name or its NSAP address, as well as the
Phase IV way of specifying node name and application object
number and name.
----
>2. clients and servers running under Alpha OpenVMS 7.1 with DECnet
> Plus should work with clients and servers running under earlier
> versions of VAX/VMS with DECnet Phase IV or DECnet Plus
Yes, you should be OK here too. From the Planning manual:
++++
1.2 Transition Features
DECnet-Plus software provides the following features to help
you during transition:
Coexistence of Phase IV and DECnet-Plus: backward
compatibility
DECnet-Plus software is compatible with DECnet Phase
IV software; DECnet-Plus systems can coexist with and
fully interoperate with Phase IV nodes. In addition to
supporting OSI protocols, DECnet-Plus systems continue
to support all Phase IV protocols (with the exception of the
Phase IV NICE network management protocol). With
this interoperability, you do not have to migrate your
network - or even an entire area - all at once.
----
Regards,
John Wood
Software Partner Engineering
Digital Equipment Co.
|