HP-UX SNAplus2 R7 Upgrade Guide (September 2005)

Upgrading from Earlier Versions of SNAplus2 to R7
Phased Upgrade of a Running Client/Server System
Chapter 212
Phased Upgrade of a Running Client/Server
System
If you are currently running SNAplus2 Release 6 as a client/server
system, you may need to keep the system running while you are
upgrading to Release R7 to provide the minimum disruption to users. (If
you are able to stop the complete SNAplus2 system and upgrade all
computers at the same time before restarting, see “Upgrading a
Complete Client/Server System in One Pass”.)
The procedure described in this section enables you to continue using the
SNAplus2 system during all stages during upgrading. The SNAplus2
software needs to be stopped on only one computer at a time, and only
when you are upgrading the software on that computer. All other
computers on the network can continue to operate, whether they are
running the old or the new software. In this chapter, “back-level” is used
to indicate a client or server running the older version of the software
(Release 6), and “current-level” is used to indicate a client or server
running the newer version (Release 7).
The upgrade process involves upgrading each server in turn, and then
upgrading the clients after all the servers have been installed.
During the upgrade process the following activities can continue:
• Back-level clients are capable of connecting to back-level and
current-level servers.
• Applications can work unchanged (without recompilation or
relinking) on back-level and current-level servers.
• Back-level clients and servers can administer back-level servers, and
current-level clients and servers can administer current-level
servers.
• Current-level (Release 7) user applications (3270, RJE, API
programs) can run unchanged with Release 6.0 or 6.1 resources.
CAUTION Although, in principle, back-level clients and servers can administer
current-level servers, you should be aware of the following restrictions.