HP-UX SNAplus2 Upgrade Guide

HP-UX 11i
Edition 3

Manufacturing Part Number: J2740-90025 E0603

United States © Copyright 2003 © Hewlett-Packard Company, 2003. All rights reserved.

Legal Notices
The information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office. Restricted Rights Legend Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the Commercial Computer Software Restricted Rights clause at FAR 52.227-19 for other agencies. HEWLETT-PACKARD DEVELOPMENT COMPANY L.P. 20555 S.H. 249 Houston, Texas 77070 U.S.A. Use of this document and any supporting software media supplied for this pack is restricted to this product only. Additional copies of the programs may be made for security and back-up purposes only. Resale of the programs, in their present form or with alterations, is expressly prohibited. Copyright Notice Copyright © 1997-2003 Hewlett-Packard Development Company L.P. All rights reserved. Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws.

2

Trademark Notices ActivePerl ® is a registered trademark of ActiveState Tool Corporation Apple® and Macintosh® are trademarks of Apple Computer, Inc., registered in the United States and other countries. AppleShare® is a registered trademark of Apple Computer, Inc. CHAMELEON™ is a trademark of NetManage, Inc. DIGITAL™ and PATHWORKS™ are trademarks of Digital Equipment Corporation. DiskAccess® is a registered trademark of Intergraph. EXCURSION™ is a trademark of Digital Equipment Corporation. Exeed® is a registered trademark of Hummingbird Communications Ltd. eXodus™ is a trademark of White Pine Software, Inc. Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Hewlett-Packard is independent of Sun Microsystems. MS-DOS® and Microsoft® are U.S. registered trademarks of Microsoft Corporation. NTRIGUE™ is a trademark of Insignia Solutions, Inc. NetMeeting ® is a registered trademark of Microsoft Corporation. Netscape ® is a registered trademark of Netscape Communications Corporation. OpenGL ® is a registered trademark of Silicon Graphics, Inc. Oracle ® is a registered trademark of Oracle Corporation. Oracle8 ™ is a trademark of Oracle Corporation. OSF/Motif™ is a trademark of the Open Software Foundation, Inc. in the U.S. and other countries. PC_Xware™ is a trademark, and WinCenter® is a registered trademark of Network Computing Devices, Inc. REFLECTION® and WRQ® are registered trademarks of WRQ, Inc. SGImeeting™ is a trademark of Silicon Graphics, Inc.

3

SunForum® is a registered trademark of Sun Microsystems, Inc. in the United States and other countries. UNIX® is a registered trademark in the United States and other countries, licensed exclusively through The Open Group. VERITAS® is a registered trademark of VERITAS Software Corporation. VERITAS File System™ is a trademark of VERITAS Software Corporation. WinDD™ is a trademark of Tektronix, Inc. X Window System™ is a trademark of the Massachusetts Institute of Technology. This product includes software developed by the Apache Software Foundation. This documentation is based on information from the Apache SoftwareFoundation (http://www.apache.org). This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org). This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes PHP, freely available from the PHP Group (http://www.php.net).

4

Contents
1. Overview of Upgrading
Enhancements in SNAplus2 R6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Java CPI-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OLAR (Online Addition/Replacement) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhancements Offered by SNAplus2 R6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client-Server Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for Upgrading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 15 15 16 18 19 20

2. Upgrading from Earlier Versions of SNAplus2 to R6.0 and later
Summary of Changes Between Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning the Upgrade Process for a Client/Server System . . . . . . . . . . . . . . . . . . . . . . Upgrading the Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading a Complete Client/Server System in One Pass . . . . . . . . . . . . . . . . . . . . . . Phased Upgrade of a Running Client/Server System . . . . . . . . . . . . . . . . . . . . . . . . . . Restrictions in a Mixed Network of Current-Level and Back-Level Computers. . . . Upgrade Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changing the Configuration during the Upgrade Process . . . . . . . . . . . . . . . . . . . . . Adding New Servers or Clients During the Upgrade Process . . . . . . . . . . . . . . . . . . Upgrading a Windows Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 24 24 25 26 27 27 30 30 31

3. Porting Application Programs
Overview of Porting Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APPC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recompiling Existing Appications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CPI-C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminate_Application Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CSV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LOG_MESSAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TRANSFER_MS_DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . LUA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HLLAPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NM-API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sending NMVTs Without Requesting Acknowledgement . . . . . . . . . . . . . . . . . . . . . Sending and Receiving NMVTs, Acknowledgements, or Both . . . . . . . . . . . . . . . . . . 35 36 36 37 37 38 38 39 41 42 43 43 44

5

Contents
4. Changes in SNAplus2 Functions in R6.0 and later releases
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration and Manage Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping an LS When Sessions Have Ended . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TN Server User Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command-Line Management Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . snapstart and snapstop Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . snaplu,snapconn, and snapservice Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Text Configuration Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Browse Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace Help Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NetView Commands and UNIX Command Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network Management Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RTM Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Trace File Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client/Server Operation - Master Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Client/Server Data Files (sna.ini and sna.net) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RJE Workstations and RJE FCBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running RJE Workstation for the First Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDIR Passthrough for Output Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RJE Spool Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . RJE Job Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Invokable TPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APPC LUs, Modes, and Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APPC and CPI-C Applications Using Default LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . Auto-Activated Link Stations Used by Independent LU Sessions . . . . . . . . . . . . . . . . LUA Session Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Forcing Off Users and Resetting LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enhancements for SNAplus2 R6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 49 49 49 50 50 50 52 53 54 55 57 58 59 60 61 62 63 63 64 64 64 66 67 69 70 71 72 73

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

6

Preface
SNAplus2 is a software product that enables a server running HP-UX to exchange information with other nodes on an SNA network. The HP-UX SNAplus2 Upgrade Guide contains information on upgrading an existing SNAplus2 system to a later SNAplus2 Release.

7

Audience
This guide addresses the network administrator responsible for planning, configuring, and monitoring the operation of an HP 9000 SNA data communications network.This guide assumes that you have knowledge of the following: • SNA (Systems Network Architecture) and APPN (Advanced Peer-to-Peer Networking) concepts. For a list of books that provide this information, see “Related Publications”. SNAplus2 concepts and administration tools (see the HP-UX SNAplus2 Administration Guide).

Application programmers may also use this book to ensure that applications continue to run on upgraded systems.

Organization of This Guide
Chapter 1, “Overview of Upgrading.” This chapter summarizes the possible upgrade paths and client/server compatibility. Chapter 2, “Upgrading from Earlier Versions of SNAplus2 to R6.0 and later.” This chapter explains how to plan the process of upgrading the system, and lists the steps required to upgrade the system. Chapter 3, “Porting Application Programs.” Contains information about how to port applications written for the Earlier SNAplus2 Release APIs (application programming interfaces) for use with later SNAplus2 releases. Chapter 4, “Changes in SNAplus2 Functions in R6.0 and later releases.” Provides information about programs in earlier releases that are superseded by new programs in Release 6.0 and later releases. It also provides information about other features that have changed, including new features for release 6.1.

8

Typographic Conventions
Table 1 shows the typographic styles used in this document. Table 1 Typographic Conventions Special Element Document title File or path name Program or application Command or HP-UX utility General reference to all commands of a particular type Option or flag Parameter or Motif field Literal value or selection that the user can enter (including default values) Constant or signal Return value Variable representing a supplied value Environment variable Programming verb Function, call, or entry point 3270 key Keyboard keys Sample of Topography HP-UX SNAplus2 Administration Guide /usr/spool/uucp/myfile.bkp snapadmin define_node; cd query_* (indicates all of the administration commands that query details of a resource) -i

servername; domain
255; On node startup

SV_AUDIT LUA_UNSUCCESSFUL; 0; OK

oldfilename; LU_name; user_ID
PATH GET_LU_STATUS Terminate_Application ENTER
Ctrl+D; Enter

9

SNaplus2 Publications
SNAplus2 publications include user guides, administrator guides, and programmer guides. The following sections describe the contents of each book.

Publications for Users
SNAplus2 provides the following user guides: HP-UX SNAplus2 General Information Provides an introduction to SNAplus2 and explains key product concepts and features. HP-UX SNAplus2 3270/3179G Users Guide Explains how to perform the following functions when you use 3270 emulation: • • • • • • Starting and stopping 3270 emulation Transferring files Using customization features such as remapping your keyboard and displaying colors Interpreting status-line information Sending NetView user alerts Viewing response times

HP-UX SNAplus2 RJE Users Guide Explains how to start and stop the RJE workstation, queue a job for submission to the host, list the queued jobs, cancel a queued job, and send commands to the host's job entry subsystem (JES) console. HP-UX SNAplus2 and TN3270 Glossary Provides a comprehensive list of terms and their definitions used in the SNAplus2 library.

Publications for Administrators
SNAplus2 provides the following administrator guides: HP-UX SNAplus2 Installation Guide Explains how to install the SNAplus2 software and set up system files. 10

HP-UX SNAplus2 Upgrade Guide (this guide) Provides information about upgrading to the current version of SNAplus2 from previous versions. It includes information about converting configuration files, rebuilding applications that use the SNAplus2 application program interfaces (APIs), and changes in other SNAplus2 functions. HP-UX SNAplus2 Administration Guide Explains how to enable, configure, and manage SNAplus2. This guide provides information about SNA concepts, and an overview of the features provided by SNAplus2. It describes how to configure and manage SNAplus2 using the Motif administration program and provides guidance for users of the SNAplus2 command-line administration program. HP-UX SNAplus2 Administration Command Reference Explains how to use the SNAplus2 command-line administration program and shows the syntax of all SNAplus2 administration commands. HP-UX SNAplus2 Diagnostics Guide Explains how to investigate and resolve common problems and provides an overview of diagnostic tools, including logging and tracing.

Publications for Programmers
SNAplus2 provides the following programmer guides. Each guide includes conceptual and detailed reference information. HP-UX SNAplus2 APPC Programmers Guide Contains the information you need to write application programs using Advanced Program-to-Program Communication (APPC). HP-UX SNAplus2 CPI-C Programmers Guide Contains the information you need to write application programs using Common Programming Interface for Communications (CPI-C). HP-UX SNAplus2 3270 & TN3270 HLLAPI Programmers Guide Contains the information you need to write application programs using High-Level Language Application Program Interface (HLLAPI).

11

HP-UX SNAplus2 LUA Programmers Guide Contains the information you need to write applications using the Conventional LU Application Programming Interface (LUA). HP-UX SNAplus2 CSV Programmers Guide Contains the information you need to write application programs using the Common Service Verbs (CSV) application program interface (API). HP-UX SNAplus2 MS Programmers Guide Contains the information you need to write applications using the Management Services (MS) API. HP-UX SNAplus2 NOF Programmers Guide Contains the information you need to write applications using the Node Operator Facility (NOF) API.

Related Publications
• • IBM APPN Architecture and Product Implementations Tutorial, GG24-3669 IBM Systems Network Architecture: — LU 6.2 Reference—Peer Protocols, SC31-6808 — APPN Architecture Reference, SC30-3422. — Management Services, SC30-3346 — Formats, GA27-3136 — Technical Overview, GC30-3073

12

1

Overview of Upgrading
This chapter describes the enhancements offered by SNAplus2 R6.0 and R6.1, the possible upgrade paths, and client/server compatibility when upgrading your SNAplus2 system. This upgrade guide applies only to upgrading the previous versions of SNAplus2. It is NOT an upgrade from

Chapter 1

13

Overview of Upgrading

SNAplus. SNAplus is obsolete and no longer supported. If you are using SNAplus and want to move to the new SNAplus2 release of R6.1, you must upgrade your operating system to HP-UX 11i, remove the SNAplus products using swremove and then install the new SNAplus2 R6.1 release.

14

Chapter 1

Overview of Upgrading Enhancements in SNAplus2 R6.1

Enhancements in SNAplus2 R6.1
SNAplus2 offers the following new features in this version, R6.1. To use these features, you must upgrade your operating system to HP-UX 11i.

Java CPI-C
Java CPI-C supports the development of Java application programs that use Common Programming Interface for Communications (CPI-C) to exchange data in an SNA environment. A sample Java CPI-C program (JPing) is included in the /opt/sna/samples/JPing.java directory. For information on compiling, linking and running the program, see chapter 5 of the HP-UX SNAplus2 CPI-C Programmer’s Guide, J2744-90015, E0601. For information on writing Java CPI-C programs, see “Java CPI-C Considerations” in chapter 2 of the above manual.

OLAR (Online Addition/Replacement)
OLAR stands for Online Addition [and] Replacement. OLAR refers to the ability of a PCI I/O card to be replaced (removed and/or added) to an HP-UX computer system designed to support this feature without the need for completely shutting down and re-booting the system or adversely affecting other system components. Not all add-in cards have this capability. Currently, only PCI cards have the capability of using this feature. For detailed information on this procedure, see the Configuring HP-UX For Peripherals manual, HP Part Number B2355-90698. This manual is available on the documentation web site: http://www.docs.hp.com.

Chapter 1

15

Overview of Upgrading Enhancements Offered by SNAplus2 R6.0

Enhancements Offered by SNAplus2 R6.0
The SNAplus2 family offers higher scalability and increased functionality. Some of the enhancements and features include: • A highly-scalable number of links, users and sessions limited only by the available hardware resources (for example, the number of slots for adapter cards, disk space, physical memory, etc.) Multiple LAN support (Token Ring, 802.3 and FDDI simultaneously) The ability to specify the path to the SNAplus2 programs, if necessary Support for SNA over QLLC using the dual-port PSI card on D-class servers SNAplus2 APPN End Node product, which: — Allows remote LUs to be dynamically located as required instead of being configured explicitly at the local system — Allows a host that has the Dynamic Definition of Dependent LUs facility to dynamically define the dependent LUs of this node; this significantly reduces the host definitions. — Using the DLUR function working in conjunction with DLUS on the host provides the facility to route sessions for dependent LUs across an APPN network, instead of requiring a direct connection to this host. • Support for the APPN Connection Network feature in a Shared Access Transport Facility (SATF) environment (e.g. TR network) (suppresses the definition of a Link Station between each pair of communicating nodes). SNAplus2 API support compilation from C++ applications SNAplus2 RJE, providing: — Checkpoint restart capability for retransmission of incomplete RJE output data files; this can significantly reduce the transmission time in case of a low quality line.

• • • •

• •

16

Chapter 1

Overview of Upgrading Enhancements Offered by SNAplus2 R6.0 — Workstation customization at user level (a user interface allows the user to configure workstation parameters, FCBs, printers, and punches). • • An installation process that runs under SAM (System Administration Manager) A motif Administration GUI with extensive online help, replacing the snapconfig and snapmanage tools used by SNAplus and providing the dynamic reconfiguration of any node resources. Tracing enhancements: a dump file with SNA messages in hexadecimal as well as ASCII and EBCDIC interpretation, and a drawing file that shows SNA messages exchange in a flow diagram. ASCII character menu-based administration program usable from a nongraphic TTY-type terminal. Windows 32-bit client support TN3270E client/server support SNMP subagent integration

• • • •

Chapter 1

17

Overview of Upgrading Upgrade Paths

Upgrade Paths
The following table specifies the direct upgrade paths available (Y for Yes or N for No) from previous versions of SNAplus2. Table 1-1 Upgrade Paths From R5.2 SNAplus2 R5.0, R5.1 SNAplus2 R5.2 SNAplus2 R6.1020 SNAplus2 R6.1100 Y N N R6.1020 Y N N To R6.1100 Y Y Y R6.11i Y N Y Y

If the upgrade includes an upgrade of the operating system, see the considerations described in “Upgrading the Operating System”. You cannot downgrade to an earlier version; you can only upgrade to a later version of SNAplus2.

18

Chapter 1

Overview of Upgrading Client-Server Compatibility

Client-Server Compatibility
The following table specifies the compatibility (Y for Yes or N for No) between SNAplus2 client applications and SNAplus2 servers. Client applications are 3270, RJE, API programs, or administration programs running on an SNAplus2 client or server. (The first figure given for the client applications indicates the version of HP-UX running on the client computer, for example, an R5.2 client running under HP-UX 10.30). Table 1-2 Ser vers 10.10 R5.0 R5 or nonWOSA PC Y Y Y Y Y Y Client Applications 10.20 R5.1 10.30 R5.2 10.20 R6.1020 11.0 R6.1100 11i R6. 11i N N N Y Y Y

R5.0 R5.1 R5.2 R6.1 020 R6.1 100 R6.1 1i

Y Y Y Y Y Y

Y Y Y Y Y Y

Y Y Y Y Y Y

N N N Y Y Y

N N N Y Y Y

Chapter 1

19

Overview of Upgrading Preparing for Upgrading

Preparing for Upgrading
Before you begin, you will need to know the following information, have made some preliminary decisions, and have performed some preliminary actions: • Determine the type of upgrade. You have three options: — Upgrade a standalone system — Upgrade a client/server system in one pass — Upgrade a client/server system in a phased migration • For all systems involved, have available: — Network IP address — Password information • Read through the selected procedure(s) in this document BEFORE you begin the upgrade, and make note of any information you will need during the upgrade process. You should have this information available before you begin.

Finally, please appreciate that no two SNA configurations are identical, and that the information and procedures described in this document should therefore be taken as useful guidelines rather than as 100% accurate instructions. In some areas, you may need to adapt the procedures given here to your own particular system configuration.

20

Chapter 1

2

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later

Chapter 2

21

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later

This chapter describes how to upgrade an SNAplus2 system from earlier verions of SNAplus2 to SNAplus2 R6.0 and later versions.

22

Chapter 2

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Summary of Changes Between Releases

Summary of Changes Between Releases
A Release 6.0 or 6.1 system can read all Release 5 configuration files, and can run all applications built for Release 5. However, a Release 5 system cannot read a Release 6.0 or 6.1 configuration file, and cannot run an application that has been recompiled with Release 6.0 or 6.1 headers.

Chapter 2

23

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Planning the Upgrade Process for a Client/Server System

Planning the Upgrade Process for a Client/Server System
If your SNAplus2 Release 5 system is a client/server system, you have a choice of upgrade strategies. The appropriate strategy depends on the structure of your SNAplus2 Release 5 system and the way you use it. This section describes the options available and provides information to help you select the most appropriate strategy. You should review these options and plan the process before you start to use the information in the remaining chapters in this book. The simplest strategy is to upgrade all computers in the SNAplus2 system at the same time. This means that computers at different levels of the software do not need to interoperate, and so avoids the additional complexity involved in managing a mixed network. For more information, see “Upgrading a Complete Client/Server System in One Pass”. The disadvantage of this strategy is that the SNAplus2 software must be stopped on all computers in the network until you have completed the upgrade process on all of them, which may result in unacceptable downtime if you have a large network. If you cannot stop the complete system during the upgrade process, it is possible to upgrade the system as a phased process, so that the SNAplus2 software is stopped on only one computer at a time. This means that users can continue using the facilities of the SNAplus2 system during the upgrade process, with a minimum of disruption. However, this strategy places a few restrictions on interoperation between computers running different levels of the SNAplus2 software, and adds some complexity in administering the mixed-level system. For more information, see “Phased Upgrade of a Running Client/Server System”.

Upgrading the Operating System
Note that, if the upgrade includes an upgrade of the operating system, the kernel and SDLC configuration will be lost and must be recreated after the operating system upgrade.

24

Chapter 2

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Upgrading a Complete Client/Server System in One Pass

Upgrading a Complete Client/Server System in One Pass
It is better to upgrade the complete client/server system in one pass instead of a phased upgrade. To upgrade the system in one pass, follow this procedure: Step 1. Log in as root. Step 2. Stop the SNAplus2 software on all servers and clients. Step 3. Install the new version of the SNAplus2 software on all servers and HP-UX clients. For each computer: a. Run the swinstall utility to copy the software from the installation media. swinstall will rebuild the kernel. b. From the server or client computer, run SAM. c. Double-click on the "Networking and Communications" icon. d. Double-click on the "SNAplus2 Installation" icon. (SNAplus2 Installation may take a few minutes to come up.) Verify the configuration, if the operating system has not been upgraded. If the upgrade process includes an upgrade to the operating system, SNAplus2 must be reconfigured. (Do this in SAM by double-clicking the entry “SNAplus2 Environment”.) For assistance, use the SNAplus2 installation online help. e. Exit from SNAplus2 Installation. Step 4. Start the new SNAplus2 software on the master server first, and then on all remaining servers and HP-UX clients.

Chapter 2

25

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Phased Upgrade of a Running Client/Server System

Phased Upgrade of a Running Client/Server System
If you are currently running SNAplus2 Release 5 as a client/server system, you may need to keep the system running while you are upgrading to Release 6.0 or 6.1 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 5), and “current-level” is used to indicate a client or server running the newer version (Release 6.0 or 6.1 release). 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 6.0 or 6.1) 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.

26

Chapter 2

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Phased Upgrade of a Running Client/Server System

Restrictions in a Mixed Network of Current-Level and Back-Level Computers
The only restrictions in support for programs on back-level computers are as follows: • • • Current-level clients cannot connect to back-level servers. Applications that are recompiled with current-level header files cannot run on back-level servers or clients. Back-level servers cannot be administered by current-level servers or clients. Current-level servers cannot be administered by back-level servers or clients if new features have been configured. Applications on current-level servers or clients will be unable to use resources on back-level servers. SNAplus2 Release 5.1 servers do not support Release 6.1020 systems in a client/server system. (Refer to Table 1-2, “Client/Server Compatibility”). If your servers are Release 5.1 and you install a new system with Release 6.1020 software, you must do one of two things to maintain compatibility: either upgrade all systems to Release 6.1020, or downgrade the new system to Release 5.1 (by removing the Release 6.1020 software and then installing Release 5.1 software). If you do not have access to Release 5.1 software, contact your HP Support Center.

• •

Upgrade Steps
Before beginning the upgrade process, you need to determine the order in which the servers are to be upgraded. In general, you want the master server and backup servers in the upgraded network to be the same servers as in the original network running the back-level software. To achieve this, you should upgrade the master server first, then any backup servers in order of precedence, and then any peer servers. This makes it easier to ensure that the servers are set up in the upgraded network as master and backup servers in the correct order. If you intend to use different master and backup servers in the upgraded network from those in the original network, you should upgrade the new master server first, then the new backup servers in order.

Chapter 2

27

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Phased Upgrade of a Running Client/Server System Upgrading the Master Server Step 1. Log in as root. Step 2. Stop the SNAplus2 software on the master server, if it is running, by entering the command: /opt/sna/bin/snap stop Step 3. Install the new version of the SNAplus2 software on the master server: a. Run the swinstall utility to copy the software from the installation media. swinstall will rebuild the kernel. Note that running the swinstall utility will also automatically stop the SNAplus2 software, if it is running. b. From the master server, run SAM. c. Double-click on the "Networking and Communications" icon. d. Double-click on the "SNAplus2 Installation" icon. (SNAplus2 Installation may take a few minutes to come up.) Verify the configuration, if the operating system has not been upgraded. If the upgrade process includes an upgrade to the operating system, SNAplus2 must be reconfigured. (Do this in SAM by double-clicking the entry “SNAplus2 Environment”.) For assistance, use the SNAplus2 installation online help. e. Exit from SNAplus2 Installation. The new SNAplus2 software starts automatically. Upgrading the Other Servers For each server in turn, use the following procedure: Step 1. Log in as root. Step 2. Stop the SNAplus2 software on the server. Step 3. Install the new version of the SNAplus2 software on the server: a. Run the swinstall utility to copy the software from the installation media. swinstall will rebuild the kernel. Note that running the swinstall utility will also automatically stop the SNAplus2 software, if it is running. 28 Chapter 2

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Phased Upgrade of a Running Client/Server System b. From the server, run SAM. c. Double-click on the "Networking and Communications" icon. d. Double-click on the "SNAplus2 Installation" icon. (SNAplus2 Installation may take a few minutes to come up.) Verify the configuration, if the operating system has not been upgraded. If the upgrade process includes an upgrade to the operating system, SNAplus2 must be reconfigured. (Do this in SAM by double-clicking the entry “SNAplus2 Environment”.) For assistance, use the SNAplus2 installation online help. e. Exit from SNAplus2 Installation. Step 4. Start the new SNAplus2 software. Upgrading Clients After all the servers have been upgraded, you can upgrade the client computers. For each HP-UX client in turn, use the following procedure: Step 1. Log in as root. Step 2. Stop the SNAplus2 software on the client. Step 3. Install the new version of the SNAplus2 client software: a. Run the swinstall utility to copy the software from the installation media. swinstall will rebuild the kernel. Note that running the swinstall utility will also automatically stop the SNAplus2 software, if it is running. b. From the server, run SAM. c. Double-click on the "Networking and Communications" icon. d. Double-click on the "SNAplus2 Installation" icon. (SNAplus2 Installation may take a few minutes to come up.) Verify the configuration, if the operating system has not been upgraded. If the upgrade process includes an upgrade to the operating system, SNAplus2 must be reconfigured. (Do this in SAM by double-clicking the entry “SNAplus2 Environment”.) For assistance, use the SNAplus2 installation online help. e. Exit from SNAplus2 Installation.

Chapter 2

29

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Phased Upgrade of a Running Client/Server System Step 4. Restart the SNAplus2 software. For each Windows client in turn, use the procedure in “Upgrading a Windows Client”.

Changing the Configuration during the Upgrade Process
While the network contains both Release 5 and Release 6.0 or 6.1 computers, you can manage both using Release 5 administration tools, as long as you are not using any new Release 6.0 or 6.1 features.

CAUTION

If you use the Release 6.0 or 6.1 administration tools to configure new features on Release 6.0 or 6.1 servers, and then subsequently use Release 5 tools, the configuration information for the new features will be lost.

Adding New Servers or Clients During the Upgrade Process
If you need to add a new computer, either a server or a client, to the SNAplus2 system while you are in the process of upgrading it, you can do either of the following: • Install the R5 software on this computer. This procedure ensures that the new computer can access the resources of all servers, both Release 5 and Release 6.0 or 6.1, as soon as it is installed. You then need to upgrade it later to the new release. Add the machine in the same way you added the existing servers and clients, following the same order as described earlier in this section (servers in order of precedence, and then clients). If you are adding a server, this server cannot become a master or backup server until it is upgraded (because you cannot change the sna.net file on back-level servers during the upgrade process). Alternatively, you can install the Release 6.0 or 6.1 software on this computer. Installing this software will avoid having to upgrade later, but it means that the new computer can access only resources on Release 6.0 or 6.1 servers (either new or upgraded).

30

Chapter 2

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Upgrading a Windows Client

Upgrading a Windows Client
The upgrade process for Windows clients requires that a current-level server is available and started. To upgrade the client, use the following procedure: Step 1. Stop SNAplus2 applications running on the client. Step 2. Check that the NAP (Network Access Process) is not running on the client. Step 3. Reinstall the SNAplus2 client software by running the installation program that is provided with the client.

Chapter 2

31

Upgrading from Earlier Versions of SNAplus2 to R6.0 and later Upgrading a Windows Client

32

Chapter 2

3

Porting Application Programs
This chapter provides information about how to port applications written for back-level SNAplus2 APIs for use with the current-level SNAplus2 API libraries.

Chapter 3

33

Porting Application Programs

Each individual API is described separately in the following sections of this chapter. If your application uses more than one of the SNAplus2 APIs, for example, if an APPC application uses the CSV (common service verb) API for character translation and message logging, you should refer to all the appropriate sections.

34

Chapter 3

Porting Application Programs Overview of Porting Applications

Overview of Porting Applications
The SNAplus2 API libraries have been designed to be backward-compatible, and to include all the functions that were available in the back-level software as well as new functions specific to the current-level software. This means that, in most cases, when upgrading from SNAplus no migration is required because the application will automatically use the new shared libraries. When upgrading from Release 5 to Release 6.0 or 6.1, you can run existing applications without any change to the application. However, if you want to add a new function, for example adding the TP Server for APPC, you must extend the application and relink the program. In many cases, the current-level API implements new functions using VCB fields that were marked as “reserved” in the back-level API. If your application sets all reserved fields to 0, as recommended, it will operate with the new libraries with no change in function; however, unpredictable results may occur if reserved fields are not set to zero.

Chapter 3

35

Porting Application Programs APPC

APPC
If you are not making changes to the application's source code, no action is necessary; the application can run unchanged with the new shared libraries.

Recompiling Existing Appications
In SNAplus, the VCB field immediately following the opext field is named reserv2 and is reserved. In Release 5, the opext field was renamed format. The format field is used to distinguish between two versions of a VCB. When migrating applications from previous versions of SNAplus, no source code changes are required because the SNAplus2 system overwrites the application supplied value. However, it is recommended that you explicitly set this field to zero for future compatibility.

36

Chapter 3

Porting Application Programs CPI-C

CPI-C
No action is necessary to migrate a CPI-C (Common Programming Interface Communications) application; the application can run unchanged with the new shared libraries. However, if the application uses the Terminate_Application function, see “Terminate_Application Function”, for further information.

Terminate_Application Function
The CPI-C Terminate_Application function is no longer required by any SNAplus2 CPI-C application. This function was originally added to SNAplus CPI-C to overcome a limitation in the CPI-C interface, which restricted the application to only one Accept_Conversation call, but this limitation has now been removed The current version of SNAplus2 supports Terminate_Application, so existing CPI-C applications that use this function can be used without source code modifications. However, the function will not be supported in future versions of SNAplus2. Begin removing this function from existing applications now, to ensure that they continue to work with later SNAplus2 versions.

Chapter 3

37

Porting Application Programs CSV

CSV
If the application uses either of the verbs LOG_MESSAGE or , see “LOG_MESSAGE” or “TRANSFER_MS_DATA” If the application does not use the LOG_MESSAGE verb, and you are not making changes to the application's source code, no action is necessary; the application can run unchanged with the new shared libraries.

LOG_MESSAGE
This verb has been modified from the version in SNAplus to work with the style of message logging introduced in SNAplus2 Release 5. Refer to the description of this verb in the HP-UX SNAplus2 CSV Programmers Guide for information. Applications can no longer log messages from the system message file. If your application logs messages from the system message file, you need to create a new user-defined message file, and modify the application to specify this file instead of the system message file. The source file format for user-defined message files and the program used to build the message file from the source file have been changed. If your application logs messages from a user-defined message file, you need to create a new source file and build a new message file from it; this file can then be used without changes to the application's source code. For more information about the new file format and on how to build the new message file, refer to the description of LOG_MESSAGE in the HP-UX SNAplus2 CSV Programmers Guide. In addition, note the following changes to the action of the LOG_MESSAGE verb: • The msg_act parameter now defines the log message type (problem, exception, or audit) used in Release 6, rather than the log message level that was used in SNAplus. The SNAplus2 CSV library continues to accept the old values for this parameter, and maps them to the new log message types as listed below. If this mapping does not correspond to the appropriate message type for your log messages, you should modify the source code to specify the new message type values.

38

Chapter 3

Porting Application Programs CSV

Table 3-1 Release 4 values SV_INTRV, SV_INTRV_16, SV_NO_INTRV_16 SV_NO_INTRV, SV_NO_INTRV_10 SV_NO_INTRV_8, SV_NO_INTRV_6 • Release 6 value SV_PROBLEM SV_EXCEPTION SV_AUDIT Release 6 message type Problem message Exception message Audit message

The msg_act parameter no longer defines whether the message is displayed on the system console; this information is now defined in the message file. You do not need to modify the application's source code because this parameter is ignored in Release 6.0 or 6.1, but ensure that the new message file specifies whether a message is a problem, exception, or audit. If the msg_act parameter corresponds to an audit or exception message, the message is logged only if the SNAplus2 configuration specifies that the appropriate type of logging is enabled. If it is not enabled, the verb still receives an OK return code but the message is not written to the log file. For example, if msg_act specifies SV_NO_INTRV_8 (which corresponds to an audit log) but audit logging is not enabled, the message is not logged. (In SNAplus, a message would be written to the log file even if it was at an audit log level that was not currently enabled.)

TRANSFER_MS_DATA
In SNAplus2 Release 6.0 or 6.1, this verb is provided as part of the MS API and not the CSV API. If you are not making modifications to the application's source code, no action is required as the application is still able to access TRANSFER_MS_DATA from within the CSV library. In future versions of SNAplus2, TRANSFER_MS_DATA will be supported only in the MS library and not in the CSV library.

Chapter 3

39

Porting Application Programs CSV If you want to use the application with future versions of SNAplus2, you must modify the application to include the MS header file and relink with the MS library. If you are making modifications to the source code, you need to modify the API header files that are included by the #include directive. The source code should already include the following line: #include <acssvcc.h> If the application does not use any of the other CSV verbs in addition to TRANSFER_MS_DATA, you can remove this line; if it uses other CSV verbs, leave this line in place. Add the following line to include the MS header file: #include <ms_c.h>

40

Chapter 3

Porting Application Programs LUA

LUA
If you are not making changes to the application's source code, no action is necessary; the application can run unchanged with the new shared libraries.

Chapter 3

41

Porting Application Programs HLLAPI

HLLAPI
If you are not making changes to the application's source code, no action is necessary; the application can run unchanged with the new shared libraries.

42

Chapter 3

Porting Application Programs NM-API

NM-API
The NM-API is replaced by the MS API, which provides a much wider range of functions. An NM-API application must be rewritten to use the appropriate MS verbs. The following paragraphs provide information about the mapping between NM-API verbs and the equivalent MS verbs, depending on the function required by the application. For more information about the MS verbs described here, including error return codes, refer to the HP-UX SNAplus2 MS Programmers Guide.

Sending NMVTs Without Requesting Acknowledgement
If the NM-API application uses the NM_SEND verb to send NMVTs without requesting acknowledgment, and does not use the NM_RECEIVE verb to receive NMVTs, the only MS verb required is TRANSFER_MS_DATA (which replaces the NM_SEND verb). The parameters for TRANSFER_MS_DATA should be set as follows:

data_type options

SV_NMVT Set bits 0–3 of this parameter as follows: Bit 0 Bit 1 Bit 2 Bit 3 Set to 1 (do not add Date/Time Subvector) Set to 1 (do not add Product Set ID Subvector) Set to 0 (send the NMVT to the remote system) Set to 0 (log the data in the SNAplus2 error log file)

Bits 4–7 are reserved, and must be set to 0.

originator_id The origintr_id parameter from the NM_OPEN verb that preceded the NM_SEND verb. pu_name dlen
Set this parameter to eight binary zeros. The datalength parameter from the NM_SEND verb.

Chapter 3

43

Porting Application Programs NM-API

dptr

The dptr parameter from the NM_SEND verb.

The NM_OPEN and NM_CLOSE verbs are no longer required, and must be removed.

Sending and Receiving NMVTs, Acknowledgements, or Both
If the NM-API application uses the NM_RECEIVE verb to receive NMVTs, or if it issues NM_SEND with the options parameter set to request an acknowledgment from the host and then uses NM_RECEIVE to receive the response, it must be redesigned to use the asynchronous receive mechanism provided by the MS API. The following paragraphs explain how each verb in the original application should be replaced by MS verbs. NM_OPEN The NM_OPEN verb must be replaced by the CONNECT_MS_NODE and REGISTER_NMVT_APPLICATION verbs. The parameters to these verbs should be set as follows: CONNECT_MS_NODE

node_name

Name of the SNAplus2 node to connect to. For the stand-alone version of SNAplus2, you can set this parameter to all binary zeros; you do not need to specify the node name. For the client/server version, setting this parameter to all binary zeros indicates the default local node (on the same SNAplus2 server as the application).

REGISTER_NMVT_APPLICATION

ms_appl_name
The origintr_id parameter that was supplied to the NM_OPEN verb.

ms_vector_key_type
Set this parameter to AP_ALL_KEYS (to accept all major vector keys).

44

Chapter 3

Porting Application Programs NM-API

conversion_required
Set this parameter to AP_NO (to indicate that the application is an NMVT-level application and not an MDS-level application). Callback routine supplied to REGISTER_NMVT_APPLICATION The callback routine supplied to the REGISTER_NMVT_APPLICATION verb should include the code for processing received NMVTs (which would have followed the NM_RECEIVE verb in the original application). It should also include code for processing the MS_STATUS indication. For more information about the requirements for this callback routine, refer to the information about callback routines in the HP-UX SNAplus2 MS Programmers Guide. NM_CLOSE The NM_CLOSE verb must be replaced by the UNREGISTER_NMVT_APPLICATION and DISCONNECT_MS_NODE verbs. The parameters to these verbs should be set as follows: UNREGISTER_NMVT_APPLICATION

ms_appl_name

The ms_appl_name parameter that was supplied to the REGISTER_NMVT_APPLICATION verb (taken from the origintr_id parameter supplied to the NM_OPEN verb).

DISCONNECT_MS_NODE (no parameters required)

Chapter 3

45

Porting Application Programs NM-API NM_RECEIVE The NM_RECEIVE verb is no longer required, and must be removed. Processing of the received NMVT, which would normally follow the NM_RECEIVE verb, should be moved to the callback routine supplied to the REGISTER_NMVT_APPLICATION verb, as described for NM_OPEN. NM_SEND The NM_SEND verb should be replaced by the TRANSFER_MS_DATA verb. The parameters to this verb should normally be set as described in “Sending NMVTs Without Requesting Acknowledgement”. The only exception is when the supplied NMVT is a response to an NMVT previously received from the host; in this case, the pu_name parameter on TRANSFER_MS_DATA must be set to the pu_name parameter in the NMVT_RECEIVED data structure containing the received NMVT.

46

Chapter 3

4

Changes in SNAplus2 Functions in R6.0 and later releases

Chapter 4

47

Changes in SNAplus2 Functions in R6.0 and later releases Introduction

Introduction
This chapter provides information about the following: • Programs in SNAplus that are no longer available and the new functions that have replaced them. These changes apply to R6.0 and later releases. New features of the product that have been added for SNAplus2 R6.1.

48

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases Configuration and Manage Programs

Configuration and Manage Programs
The Configuration and Manage programs from SNAplus have been replaced by the command-line administration program snapadmin and the Motif administration program xsnapadmin. For more information about these programs, refer to the HP-UX SNAplus2 Administration Guide. In addition, note that the SNA software must be started on the local node before you can modify the configuration. If you are configuring resources for a node other than the local node, the SNA software must also be started on the server where the target node runs. (The node does not need to be started in either case.)

Stopping an LS When Sessions Have Ended
The Manage program in SNAplus provided an option to stop a connection when all sessions using it had ended. This function is no longer supported when stopping an LS. Instead, you can define the LS as a limited resource so that it is stopped automatically when sessions are no longer using it. For more information, refer to the section that describes managing connectivity components in the HP-UX SNAplus2 Administration Guide.

TN Server User Configuration
When configuring TN Server users, you can define the configuration to include a default user record (which enables any TN3270 program user to access TN Server), and then exclude individual users by configuring them explicitly but not configuring any sessions for them to use. In SNAplus, this configuration could be set up using either the menu-based configuration program or the text configuration programs. The Motif administration program enables you to define the default user record, but does not allow you to define user records with no sessions configured. If you need to exclude individual users, you can define the required configuration records either by using the command-line administration program or by editing the configuration file. The Motif administration program does not display the configuration of the excluded users, but the configuration still operates as it did in SNAplus.

Chapter 4

49

Changes in SNAplus2 Functions in R6.0 and later releases Command-Line Management Utilities

Command-Line Management Utilities
The command-line management utilities from SNAplus (snapstart, snapstop, snaplu, snapconn, and snapservice) have been replaced by other programs.

snapstart and snapstop Commands
The command snapstart and snapstop daemons, which start and stop the SNA software, have been replaced by the commands snap start and snap stop. For more information about these commands, refer to the chapter on starting the SNAplus2 software in the HP-UX SNAplus2 Administration Guide. If you are upgrading from a stand-alone version of SNAplus, starting the SNA software no longer starts the local node and connectivity components automatically, as it did in SNAplus. To start these components as soon as the SNA software is started, use the following procedure: Step 1. Modify the node configuration file to define connectivity components as “initially active”; this ensures that the components are started automatically as soon as the node is started. If an LS is defined as “initially active,” the DLC and port that it uses are also started automatically. Step 2. Create a shell script that issues snap start followed by snapadmin init_node; this starts the SNA software and then starts the local node. Use this script to start the SNA software, instead of issuing the snap start command directly. The other snapstart and snapstop commands, which start and stop connectivity components, have been replaced by start_* and stop_* commands issued to the command-line administration program snapadmin. For more information about this program, refer to the HP-UX SNAplus2 Administration Guide.

snaplu,snapconn, and snapservice Commands
These commands have been replaced by commands issued to the command-line administration program snapadmin, as follows:

50

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases Command-Line Management Utilities snaplu This is replaced by the following snapadmin commands: query_lu_0_to_3 Return information about LUs used for 3270, RJE, and LUA. query_local_lu Return information about LUs used for APPC and CPI-C. snapconn This is replaced by the following snapadmin commands: start_dlc, start_port, start_ls Start connectivity components. stop_dlc, stop_port, stop_ls Stop connectivity components. query_dlc, query_port, query_ls Return information about the status of connectivity components. snapservice This is replaced by the following snapadmin commands: set_trace_type, add_dlc_trace, remove_dlc_trace Set tracing options for SNAplus2 components. query_trace_type, query_dlc_trace Return information about tracing options. set_log_type Set logging options for SNAplus2 components. query_log_type Return information about logging options.

Chapter 4

51

Changes in SNAplus2 Functions in R6.0 and later releases Text Configuration Programs

Text Configuration Programs
The text configuration programs from SNAplus, which convert between the binary configuration file format used by SNAplus components and a readable ASCII text file, are no longer required because the configuration file is now stored in ASCII text format. For information about the configuration file format used in Release 6, refer to the HP-UX SNAplus2 Administration Guide.

52

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases Browse Program

Browse Program
The trace file formatting functions of the Browse program have been replaced by new command-line utilities, as follows: snapfilter snaptrcfmt Filter trace files to include only the required information. Format trace file information into ASCII text, readable using a standard text editor.

For more information about these utilities, refer to the chapter that describes tracing in the HP-UX SNAplus2 Administration Guide. The log file formatting functions of the Browse program are no longer required because the log file is now in a readable ASCII text format and does not require further formatting. For more information about the new log file format, refer to the chapter on log messages, in the HP-UX SNAplus2 Administration Guide. The file copying and resetting functions of the Browse program have been replaced by options on the set_trace_file and set_log_file commands issued to the snapadmin program. For more information about these options, refer to the HP-UX SNAplus2 Administration Guide.

Chapter 4

53

Changes in SNAplus2 Functions in R6.0 and later releases Trace Help Utility

Trace Help Utility
The trace help utility has been replaced in Release 6 by new command-line utilities, as follows: snapfilter snaptrcfmt Filter trace files to include only the required information. Format trace file information into ASCII text, readable using a standard text editor.

For more information about these utilities, refer to the chapter on tracing, in the HP-UX SNAplus2 Administration Guide.

54

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases NetView Commands and UNIX Command Facility

NetView Commands and UNIX Command Facility
NetView Commands in SNAplus have been replaced by the Remote Command Facility (RCF). RCF consists of the Service Point Command Facility (SPCF), which enables the NetView operator to manage SNAplus2 components, and the UNIX Command Facility (UCF), which enables the NetView operator to issue HP-UX commands on the SNAplus2 computer. The overall syntax of commands issued at the NetView console is the same as in Release 4, but the detailed syntax of individual commands has been changed. The changes for each group of commands are as follows: Network Access Commands These commands are no longer supported. You do not need to identify the name of the Netview operator before issuing other commands, so the login-sp command is no longer required. The function of the display-applicats (Display Applications) command, which lists the service components running on the SNAplus system, can be provided by using SPCF to issue query_* administration commands from the Netview console; see “Node commands,” next, for more information. Node Commands Node commands in SNAplus have been replaced by SPCF commands. These provide the same functions as the Release 4 node commands, but use the syntax of SNAplus2 administration commands (as they would be specified to the snapadmin program). UNIX Command Facility (UCF) The syntax of UCF commands is the same as in Release 4. However, note the following changes to the way UCF is used: • The login-sp command is no longer required before issuing UCF commands. 55

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases NetView Commands and UNIX Command Facility • Any output generated after the command completes is not returned to UCF. For example, if you issue a command followed by & to run it in the background, UCF receives the operating system message giving the process ID of the background command, but does not receive any subsequent output that may be generated. Similarly, you can use UCF to start a daemon process, but you cannot see any output generated by the process. The format of the output messages from UCF has been changed slightly.

For more information about SPCF and UCF, refer to the chapter on managing SNAplus2 from NetView, in the HP-UX SNAplus2 Administration Guide.

56

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases Network Management Connection

Network Management Connection
In SNAplus, the configuration included a Network Management connection, which was used to identify the NetView host to which network management data was sent. This connection was used to route network management data from all nodes on the SNAplus LAN. SNAplus2 no longer has a concept of a LAN-wide default connection for this data. Instead, each server is responsible for routing network management data (either from applications on the server, or from applications on clients that route the data to this server) to a NetView host; if different servers on the SNAplus2 LAN are in different NetView administration domains, this may not be the same host for all servers. The define_default_pu administration command can be used to define the default PU (and hence the default host LS) on which this data is sent from a specific node. To reproduce the SNAplus behavior, in which the data from all servers is sent to the same NetView host, you need to ensure that each node has an LS defined to this host, and use define_default_pu on each node to route the data over this LS.

Chapter 4

57

Changes in SNAplus2 Functions in R6.0 and later releases RTM Statistics

RTM Statistics
SNAplus sent RTM statistics to Netview using unsolicited NMVTs. This behavior is outside the official IBM architecture and has been corrected in SNAplus2 R.5, R.6 and later releases. In general, SNAPlus2 will only send RTM statistics if explicitly requested by Netview (i.e. in response to a request for statistics). To allow SNAplus2 to send unsolicited RTM statistics, Netview must send a RTM Control NMVT requesting unsolicited RTM data.

58

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases Log Messages

Log Messages
Error and audit logging has been changed, as follows: • Log message files are now formatted ASCII text files, with the header information for each message displayed in easily readable text. You no longer need to use the Browse program for viewing log files; you can use a standard ASCII text editor. All information related to a log message, including cause and action, is included in the log file, or (if succinct logging is being used) is accessed using the snaphelp utility. There is no additional documentation for log messages; the HP-UX SNAplus Diagnostics Guide from SNAplus, which included the cause and action information, has been retired. The log message levels used in SNAplus (16, 12, 10, 8, 6) have been replaced by three log message types (Problem, Exception, and Audit). Many of the messages used in SNAplus have been retired and replaced by new messages. In addition, message numbers have been reassigned so that each component has a well-defined range of numbers. This means that you should not attempt to search Release 6 log message files for a particular message that was used in SNAplus (either by searching for the message number or by searching for specific message text).

• •

For more information about SNAplus2 log messages, refer to the chapter on log messages in the HP-UX SNAplus2 Administration Guide.

Chapter 4

59

Changes in SNAplus2 Functions in R6.0 and later releases Trace File Format

Trace File Format
Trace information for kernel components is stored now in binary files. These files can be processed using new command-line utilities to select specific information and to format it as readable ASCII text. The text file format generated is different from the SNAplus format. The command-line utilities to process trace information are as follows: snapfilter snaptrcfmt Filter trace files to include only the required information. Format trace file information into ASCII text, readable using a standard text editor.

For more information about these utilities and the trace file format, refer to the chapter on tracing in the HP-UX SNAplus2 Administration Guide. Tracing on user-space applications is still stored in ASCII text files, as in SNAplus. The only difference in the trace format is that message data is interpreted both as EBCDIC and as ASCII, in two separate columns, rather than being interpreted character by character as either ASCII or EBCDIC.

60

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases Client/Server Operation - Master Server

Client/Server Operation - Master Server
In a SNAplus client/server system, a computer was set up as a client simply by not configuring the software for the node and connectivity components. Because of this, it was possible to set up the system so that the master server did not include a node (and was therefore effectively a client computer). You can still run the master server without a node. However, the Release 6 software on this computer must be the server version and not the client version, because the client installation does not include some components that are required for the computer to act as a configuration file server.

Chapter 4

61

Changes in SNAplus2 Functions in R6.0 and later releases Client/Server Data Files (sna.ini and sna.net)

Client/Server Data Files (sna.ini and sna.net)
In SNAplus, the file sna.ini contains information about the resources that can be used on a particular server, and specifies that the SLIM is to be started. In SNAplus2 Release 6 and later, the sna.ini file is used only by the back-level SLIM component and by the SDLC component for the DOWNLOAD statement. To determine other resource information, SNAplus2 does the following: • • Resources are defined as belonging to a particular node (which runs on a specified server). When the SNAplus2 software is started, it starts the SLIM if the SNA network data file sna.net is present, and takes no action if it is not present.

Check the definition of each node in the configuration file after upgrading to R6 or a later release to ensure that the appropriate resources are associated with the node. The SNA network data file sna.net identifies the master configuration file server and backup master servers; the installation process sets up an initial version of this file to identify the master configuration file server, to which you can add backup master servers as required. This is now a binary file instead of a text file; you cannot edit it directly, as you could in SNAplus. Instead, after starting the SNAplus2 software on the master server, you issue SNAplus2 administration commands to this file to add or remove backup master servers; the file is automatically copied to other servers when you make changes to it. For more information, refer to the information about client/server operation in the HP-UX SNAplus2 Administration Guide.

62

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases RJE Workstations and RJE FCBs

RJE Workstations and RJE FCBs
In R6.0 and later releases, the definition of RJE FCBs and much of the definition of RJE workstations (including the printer and punch devices associated with them) is held in an RJE workstation style file, rather than in the configuration file as in SNAplus. For details of the contents of this file, refer to the HP-UX SNAplus2 RJE Users Guide. The environment variables used with RJE in SNAplus have also been replaced by options in this file. The configuration file migration tool creates a style file for each workstation in the SNAplus configuration file. The name of the file is wkstn.sty, where wkstn is the name of the RJE workstation; it is created in the same directory as the output configuration file. This file does not contain a define_minor_options record; this record is set up when you first run the workstation, as described in “Running RJE Workstation for the First Time”. On the RJE workstation, copy the style file to /etc/opt/sna if this was not already done by the migration utility. The file's access permissions must be one of the following: • • Ownership by either the primary user of the workstation or root, with read access for the owner Group ownership by either the group configured for the workstation or the SNAplus2 administration group, with read access for the owner and group

The workstation cannot run unless this directory contains an RJE style file with the appropriate name. (All other files and subdirectories associated with the workstation are still created when the workstation is first started, as in SNAplus.)

Running RJE Workstation for the First Time
The information in this section applies when running RJE workstations for the first time after migrating the configuration to Release 6 or later.

Chapter 4

63

Changes in SNAplus2 Functions in R6.0 and later releases RJE Workstations and RJE FCBs Before running a workstation, set up the same combination of environment variables that were used with this workstation in Release 4. When you start the workstation, SNAplus2 reads the environment variables, and writes out a define_minor_options record to the style file based on these options. For subsequent runs of the workstation, SNAplus2 uses the minor options defined in the workstation style file; the RJE environment variables are ignored, and SNAplus2 does not make any modifications to the style file.

PDIR Passthrough for Output Devices
The “PDIR passthrough” option on RJE output devices was enhanced in Release 6 to include additional parameters (the REQID parameter and the five DSNAME parameters) that the host may send in PDIRs. For more information about these parameters, refer to the HP-UX SNAplus2 RJE Users Guide. If PDIR passthrough is specified when output is sent to a program, SNAplus2 passes the DSNAME parameters to the program; if PDIR passthrough is specified when output is sent to a file or directory, SNAplus2 writes the DSNAME parameters and the REQID parameter to the PDIR file. If you are migrating output programs or tools that parse PDIR files, you should check that they continue to operate correctly with the additional parameters.

RJE Spool Commands
In SNAplus, the RJE spool commands for submitting, listing, and canceling jobs could be used whether or not the SNAplus software was started. Beginning in Release 6, the SNAplus2 software must be started before using these commands.

RJE Job Logging
If your SNAplus implementation provided the facility for writing messages to the audit log file to track the progress of RJE jobs, note the following: • The format of log files has been changed, so any tools used to parse the log files for RJE job log messages requires modification to use the new format.

64

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases RJE Workstations and RJE FCBs • The environment variable that controlled RJE job logging has now been replaced by an option in the workstation style file, as described earlier in this section. This means that RJE job logging is enabled for the workstation, rather than for an individual job submission command. You cannot enable or disable it for individual jobs, except by modifying the style file and restarting the workstation to implement the change.

Chapter 4

65

Changes in SNAplus2 Functions in R6.0 and later releases Invokable TPs

Invokable TPs
In SNAplus, all invokable TPs (both auto-started and operator-started) must be defined in the configuration file; this definition includes the computer where the TP runs, and whether the TP is queued or nonqueued. Information on a queued TP is broadcast to servers when the TP starts, so that incoming Allocate requests arriving at LUs on servers elsewhere in the LAN can be routed to it. This model is changed as follows: • TPs no longer need to be defined in the central configuration file (except when they require certain advanced configuration parameters). Auto-started TPs are defined in a separate file on the computer where they run; operator-started TPs do not generally need to be defined except to override certain default settings. For more information, refer to the chapter that defines invokable TPs in the HP-UX SNAplus2 Administration Guide. A queued TP can be defined to be broadcast queued, which means that information about a TP is broadcast to servers when it starts so that it can be located dynamically. The default is nonbroadcast, which means that it only receives incoming Allocate requests explicitly targeted at the computer where it runs. The configuration of a local LU specifies whether to route incoming Allocate requests to a particular target computer, or to attempt to locate a broadcast copy of the TP. For more information, refer to the description of the define_local_lu command in the HP-UX SNAplus2 Administration Guide. When an incoming Allocate request arrives for a TP that is not defined in the invokable TP data file and so cannot be auto-started, SNAplus2 rejects the request if the TP has not already been started by an operator. It does not provide either a timeout during which the TP must be started or a console message requesting the operator to start the TP, as it did in SNAplus.

66

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases APPC LUs, Modes, and Sessions

APPC LUs, Modes, and Sessions
The following features of APPC configuration and management have been changed. • Instead of requiring implicit modes to be defined for each LU-LU-mode combination, an SNAplus2 node now has a single default mode defined, which is used if an application specifies an unrecognized mode name. You do not need to define an implicit mode for each LU-LU-mode combination, because SNAplus2 no longer requires LU-LU-mode combinations to be defined before communications can be established. Implicit partner LUs no longer need to be defined, because SNAplus2 no longer requires LU-LU-mode combinations to be defined before communications can be established. Mode definitions now specify a single maximum RU size (which can be negotiated with the partner LU). There is no facility for specifying the minimum acceptable RU size or for specifying different maximum sizes for sending and receiving. The priority (high or low) of a mode is now specified in the definition of the class of service (COS) it uses, rather than being specified explicitly in the mode definition. There is no facility for specifying the partner LU's minimum contention winner session limit. This parameter is defined in the configuration of the partner LU at the remote system, and is not required in the local SNAplus2 configuration. There is no longer a requirement for specifying the send pacing count. In Release 6, sessions normally use adaptive pacing, which does not require a fixed pacing count. The pacing count is required only when communicating with a partner system that does not support adaptive pacing; in this case, the receive pacing count defined in the partner system's configuration is used. In SNAplus, sessions using a particular mode may be activated automatically when the connection associated with that mode is started, so that they will already be active when an application attempts to use the mode. In Release 6, the mode is not associated with a specific LS, and so the sessions are not activated until an application first attempts to use the mode. If you need to activate 67

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases APPC LUs, Modes, and Sessions sessions before the application attempts to use them, you can do this by issuing the activate_session administration command for the local LU, partner LU, and mode used by the application.

68

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases APPC and CPI-C Applications Using Default LUs

APPC and CPI-C Applications Using Default LUs
Instead of specifying a local LU name explicitly, an application can request to use a default local LU (by specifying a blank LU name on the APPC TP_STARTED verb, or by not setting the APPCLLU environment variable for a CPI-C application). In SNAplus, the LU was not selected until the application issued the Allocate, so the application could issue multiple Allocates for the same TP and get a different LU from the default pool for each one. In Release 6, the default LU is selected when the APPC application issues TP_STARTED, or when the CPI-C application issues its first Allocate call; all conversations from this TP use the same local LU. For dependent LUs, which cannot support parallel sessions, this means that the application cannot have multiple concurrent conversations in one TP (from one TP_STARTED verb) because the LU only supports one conversation at a time. For an APPC application, you can support multiple concurrent conversations by redesigning the application so that it issues a separate TP_STARTED verb for each conversation. Each of these verbs is then assigned to a different local LU in the pool. In addition, if you are defining partner LUs that can be accessed using default LUs, partner LU definitions in Release 6 are specific to a node and are not defined globally for all nodes in the SNAplus2 domain. If you are defining default LUs on more than one node, you need to ensure that the partner LUs are defined on all of these nodes, so that the appropriate partner LU can be accessed from any of the default LUs.

Chapter 4

69

Changes in SNAplus2 Functions in R6.0 and later releases Auto-Activated Link Stations Used by Independent LU Sessions

Auto-Activated Link Stations Used by Independent LU Sessions
In SNAplus, if a connection was configured as “activate on demand” (so that it was started when required by a session), and then failed while in use, the SNA software would attempt to restart it when the application tried to re-establish the session. In SNAplus2 R6.0 and later releases, if a dependent LU session was using the failed LS, the SNA software would attempt to restart it when required, as in SNAplus. However, if an independent LU session was using the failed LS, attempting to re-establish the session would not restart the LS; the LS must be reactivated by the System Administrator (using the Motif administration program or the start_ls command) before an independent LU session can use it.

70

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases LUA Session Activation

LUA Session Activation
The following features of LUA session activation have been changed: • In SNAplus, if the LU specified on an LUA RUI_INIT verb is defined to use a host connection that is currently inactive and not “activate on demand,” the verb waits for the connection to be started. In R6.0 and later releases, the verb returns with primary return code LUA_UNSUCCESSFUL. The secondary return code is an SNA sense code indicating that the host LS is inactive. In SNAplus, an LUA application could access only LUs that were explicitly defined for use with LUA (rather than for use with 3270 emulation or RJE). In R6.0 and later releases, the application can specify any type 0–3 LU. This enables the use of 3270 emulation programs that operate using LUA (such as the sample LUA application provided with SNAplus2, or emulation programs that may be provided by other vendors). You may need to check the LUs used by LUA applications, to ensure that applications are accessing the LUs intended for their use and not taking up LUs intended for 3270 emulation. When an R6.0 or later LUA application specifies the name of an LU in a pool, it accesses this LU if it is available, or any other available LU in the pool if the named LU is not available. In SNAplus, the application would access any free LU in the pool; SNAplus did not attempt to select the named LU in preference to other LUs in the pool.

Chapter 4

71

Changes in SNAplus2 Functions in R6.0 and later releases Forcing Off Users and Resetting LUs

Forcing Off Users and Resetting LUs
The functions of the SNAplus Manage program to force users or applications off the system, or to reset an LU (ending its sessions), are no longer supported. To force off a 3270 emulation program or API application, use the HP-UX systems kill command, specifying the process ID with which the application is running. For 3270, you can use the query_3270_user command to determine the process ID of a copy of the 3270 emulation program. To deactivate a session for a particular 3270 or LUA LU, use the deactivate_lu_0_to_3 command. To end sessions for an APPC LU, use the deactivate_session, deactivate_conv_group, or reset_session_limit commands. In SNAplus, the 3270 emulation program was forced off automatically when an administrator stopped the SNA software. In Release 6, the program continues to run. Any active sessions display a communications check code to indicate that the communications link to the host has been lost; when the SNA software is restarted and the link to the host is restored, the user can log on again and continue to use the sessions.

72

Chapter 4

Changes in SNAplus2 Functions in R6.0 and later releases Enhancements for SNAplus2 R6.1

Enhancements for SNAplus2 R6.1
The following features have been added to SNAplus2 R6.1. You must upgrade your operating system to HP-UX 11i to use these features: • Java CPI-C Java CPI-C supports the development of Java application programs that use Common Programming Interface for Communications (CPI-C) to exchange data in an SNA environment. See the HP-UX SNAplus2 CPI-C Programmers Guide, J2744-90015. • OLAR OLAR (Online Addition/Replacement) is the ability of a PCI I/O card to be added or replaced in an HP-UX computer system without the need to completely shutdown or reboot the system. The system hardware uses the per-slot power control combined with operating system support to enable this feature For detailed information on this procedure, see chapter 2 of the Configuring HP-UX For Peripherals manual, HP Part Number B2355-90698.

Chapter 4

73

Changes in SNAplus2 Functions in R6.0 and later releases Enhancements for SNAplus2 R6.1

74

Chapter 4

Index
A adding servers or clients during the upgrade process Release 5 to Release 6, 30 Advanced Program-to-Program Communications (APPC) feature changes, Release 6, 67 management changes, 67 porting to current level, 36 APPC (Advanced Program-to-Program Communications) feature changes, Release 6, 67 management changes, 67 porting to current level, 36 application programs APPC, 36 CSV (common service verb), 38 HLLAPI, 42 LUA, 41 NM-API, 43 applications forcing off system, 72 audit logging, 59 auto-activated link stations, used by independent LU sessions, 70 B back-level computers, 26 Browse program, 53 C class of service (COS), 67 client/server data files, 62 client/server operation, 61 client/server system upgrade strategy, 24 upgrading the complete system in one pass Release 5 to Release 6, 25 clients, adding during upgrade process Release 5 to Release 6, 30 command-line management utilities, Release 4, 50 Common Programming Interface Communications (CPI-C) Terminate_Application function, 37 using default LUs, 69 configuration changes during the upgrade process Release 5 to Release 6, 30 Configuration program introduction, 49 COS (class of service), 67 CPI-C (Common Programming Interface Communications) Terminate_Application function, 37 using default LUs, 69 CSV (Common Service Verb), 38 current-level computers, 26 D documentation set, 10 E enhancements SNAplus2 R6.1, 15 SNAplus2 R61, 73 error logging, 59 F functional changes between releases, 23 Release 6, complete list, 48 H high-level language application program interface (HLLAPI), porting to current level, 42 HLLAPI (High-Level Language Application Program Interface), porting to current level, 42 I invokable TPs defining, 66 J Java CPI-C, 15, 73 job logging, 64 L log file format, 59

75

Index
log messages, 59 logical unit (LU) default, 69 resetting, 72 LS (link station) stopping, 49 LU (logical unit) default, 69 resetting, 72 LUA porting, 41 session activation, 71 M Manage program introduction, 49 manual set, 10 master server, 61 msg_act parameter, 38 N NetView commands, 55 network access commands, 55 network management application programming interface (NM-API) applications porting to current level, 43 Network Management connection, 57 network management vector transports (NMVTs) sending and receiving, 44 sending without requesting acknowledgment, 43 NM_CLOSE verb, 45 NM_OPEN verb, 44 NM_RECEIVE verb, 46 NM_SEND verb, 46 NM-API (Network Management Application Programming Interface) applications porting to current level, 43 NMVTs (network management vector transports) sending and receiving, 44 sending without requesting acknowledgment, 43 node commands, 55 O OLAR (Online Addition/Replacement), 15, 73 output devices, PDIR passthrough, 64 P PDIR passthrough for output devices, 64 porting application programs APPC, 36 CSV, 38 HLLAPI, 42 LUA, 41 NM-API, 43 R RCF (Remote Command Facility), 55 Remote Command Facility (RCF), 55 Remote Job Entry (RJE) workstation FCBs, 63 running for the first time, 64 style files, 63 RJE (Remote Job Entry) workstation FCBs, 63 running for the first time, 64 style files, 63 S servers adding during upgrade process Release 5 to Release 6, 30 Service Point Command Facility (SPCF) component of the Remote Command Facility (RCF), 55 SNA (Systems Network Architecture) concepts, 8 network data file, 62 software, 49 starting, 50 stopping, 50 snapconn command (Release 4 utility), 51 snaplu command (Release 4 utility), 51 SNAplus2 R6.1 enhancements, 15, 73 snapservice command (Release 4 utility), 51 snapstart command (Release 4 utility), 50 snapstop command (Release 4 utility), 50 SPCF (Service Point Command Facility)

76

Index
component of the Remote Command Facility (RCF), 55 spool commands, 64 Systems Network Architecture (SNA) concepts, 8 network data file, 62 software, 49 starting, 50 stopping, 50 T Terminate_Application function, 37 text configuration, 52 TN Server users, 49 trace file format, 60 trace file formatting functions, 53 trace help facility, 54 tracing, 60 TRANSFER_MS_DATA, 39 typographic conventions, 9 U UCF (UNIX Command Facility), 55 UNIX Command Facility (UCF), 55 upgrade process client/server system, 24, 26 in one pass from Release 5 to Release 6, 25 configuration changes during Release 5 to Release 6, 30 user, forcing off the system, 72 W Windows client, 31

77