HP-UX SNAplus2 Upgrade Guide HP-UX 11.0, 11i v1, and 11i v2 Edition 4 Manufacturing Part Number: J2740-90027 August 2003 United States © Copyright 2003 Hewlett-Packard Development Company L.P. 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.
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.
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).
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 . . . .
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
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.
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).
Typographic Conventions Table 1 shows the typographic styles used in this document. Table 1 Typographic Conventions Special Element Sample of Topography Document title HP-UX SNAplus2 Administration Guide File or path name /usr/spool/uucp/myfile.
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 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.
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.
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.
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.
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.
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.
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). Chapter 1 • 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.
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 To R5.2 R6.1020 R6.1100 R6.11i SNAplus2 R5.0, R5.1 Y Y Y Y SNAplus2 R5.2 - N Y N SNAplus2 R6.1020 N - Y Y SNAplus2 R6.1100 N N - Y If the upgrade includes an upgrade of the operating system, see the considerations described in “Upgrading the Operating System”.
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).
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.
2 Chapter 2 Upgrading from Earlier Versions of SNAplus2 to R6.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Upgrading from Earlier Versions of SNAplus2 to R6.
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.
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.
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.
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.
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.
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.
Porting Application Programs CSV Table 3-1 Release 4 values Release 6 value Release 6 message type SV_INTRV, SV_INTRV_16, SV_NO_INTRV_16 SV_PROBLEM Problem message SV_NO_INTRV, SV_NO_INTRV_10 SV_EXCEPTION Exception message SV_NO_INTRV_8, SV_NO_INTRV_6 SV_AUDIT 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.
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
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.
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.
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.
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.
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.
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”.
4 Chapter 4 Changes in SNAplus2 Functions in R6.
Changes in SNAplus2 Functions in R6.0 and later releases Introduction Introduction This chapter provides information about the following: 48 • 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.
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.
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.
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.
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.
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 Filter trace files to include only the required information. snaptrcfmt 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.
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 Filter trace files to include only the required information. snaptrcfmt 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.
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.
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.
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.
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).
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.
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 Filter trace files to include only the required information.
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.
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.
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.
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.
Changes in SNAplus2 Functions in R6.0 and later releases RJE Workstations and RJE FCBs • Chapter 4 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.
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.
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. Chapter 4 • 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.
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.
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).
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.
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: Chapter 4 • 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.
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.
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.
Changes in SNAplus2 Functions in R6.0 and later releases Enhancements for SNAplus2 R6.
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
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
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
