HP 3000 Manuals HP 3000 Manuals
900 Series HP 3000 Computer Systems HP SNA Products Remote System Configuration Guide HP Part No. J2220-61025 Printed in U.S.A. Edition Third Edition E0395
________________________________________________________________________ |The information contained in this document is subject to change | |without notice. | | | |Hewlett-Packard makes no warranty of any kind with regard to this | |material, including, but not limited to, the implied warranties of | |merchantability or fitness for a particular purpose. Hewlett-Packard | |shall not be liable for errors contained herein or for direct, | |indirect, special, incidental or consequential damages in connection | |with the furnishing or use of this material. | | | |Hewlett-Packard assumes no responsibility for the use or reliability | |of its software on equipment that is not furnished by Hewlett-Packard.| | | |This document contains proprietary information that is protected by | |copyright. All rights are reserved. Reproduction, adaptation, or | |translation without prior written permission is prohibited, except as | |allowed under the copyright laws. | ________________________________________________________________________ Copyright (c) 1992, 1993, 1995 by Hewlett-Packard Company ________________________________________________________________________ |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. | |Rights for non-DoD U.S. Government Departments and agencies are as set| |forth in FAR 52.227-19 (c) (1,2). | | | |Hewlett-Packard Company | |3000 Hanover Street | |Palo Alto, CA 94304 U.S.A. | ________________________________________________________________________ Restricted Rights Legend Printed 1995 Printing History New editions are complete revisions of the manual. Updates, which are issued between editions, contain additional and replacement pages to be merged into the manual. The dates on the title page change only when a new edition or a new update is published. Edition 1......................................December 1992 Edition 2......................................December 1993 Edition 3......................................March 1995 List of Effective Pages The List of Effective Pages gives the date of the current edition and of any pages changed in updates to that edition. All Pages......................................March 1995 Preface MPE/iX, Multiprogramming Executive with Integrated POSIX, is the latest in a series of forward-compatible operating systems for the HP 3000 line of computers. In HP documentation and in talking with HP 3000 users, you will encounter references to MPE XL, the direct predecessor of MPE/iX. MPE/iX is a superset of MPE XL. All programs written for MPE XL will run without change under MPE/iX. You can continue to use MPE XL system documentation, although it may not refer to features added to the operating system to support POSIX (for example, hierarchical directories). Finally, you may encounter references to MPE V, which is the operating system for HP 3000s, not based on PA-RISC architecture. MPE V software can be run on the PA-RISC (Series 900) HP 3000s in what is known as compatibility mode. This manual describes the requirements for configuring an IBM remote system for communications with Hewlett-Packard Systems Network Architecture (SNA) products. The following remote configurations are described: * Advanced Communication Function Network Control Program (ACF/NPC) and Advanced Communication Function Virtual Telecommunication Access Method (ACF/VTAM) * Job Entry Subsystem (JES) * Customer Information Control System (CICS) * Information Management System (IMS) * Distributed Office System Services (DISOSS) * AS/400 computer systems This manual does not describe the features and functions of HP SNA products. Refer to the product documentation for detailed information on product features. Audience The intended audience includes HP system and network administrators, and anyone who might be involved in configuring and supporting communications between HP SNA subsystems and supported remote systems. Assumptions This manual assumes that the reader has knowledge of the following: * SNA data communications. * The operating system environment of the HP system (MPE/V or MPE/iX). This manual is not intended as a replacement of any IBM configuration manuals. Manual Organization This manual is organized into the following chapters: Chapter 1, VTAM Configuration, describes the required NCP and VTAM configurations for HP SNA products running on MPE/V or MPE/iX platforms. Relevant NCP and VTAM macros and operands are described in the last section of the chapter. Chapter 2, JES Configuration, describes the required JES2, JES3, and POWER configurations for SNA NRJE (MPE/V and MPE/iX). Relevant JES and POWER macros and parameters are described in the second half of the chapter. Chapter 3, CICS Configuration, describes the required CICS configurations for SNA IMF (MPE/V and MPE/iX), LU 6.2 API (MPE/V and MPE/iX), LU 6.2 Base/V, and HP SNADS/iX. Relevant CICS macros and operands are described in the second half of the chapter. Chapter 4, IMS Configuration, describes the required IMS configurations for SNA IMF (MPE/V and MPE/iX). Relevant IMS macros and operands are described in the chapter. Chapter 5, DISOSS Configuration, describes the required DISOSS configuration HP SNADS/iX. This chapter describes how to use the worksheets that are provided to configure users. This chapter also describes the DISOSS Host User Profile (HUP) configuration for adding new users. Chapter 6, AS/400 Configuration, describes the required IBM AS/400 configurations for SNA IMF (MPE/V and MPE/iX), SNA IMF/iX over X.25, NS over SNA/iX, and LU 6.2 API/iX. Appendix A, VTAM Examples, contains sample NCP and VTAM configurations for various HP SNA products. Appendix B, JES Examples, contains sample JES and POWER configurations. Appendix C, CICS Examples, contains sample CICS configurations. Appendix D, IMS Examples, contains sample IMS configurations. Appendix E, DISOSS Examples, contains samples of HP configuration worksheets and DISOSS configurations. Appendix F, AS/400 Examples, contains sample AS/400 configurations. Conventions UPPERCASE In a syntax statement, commands and keywords are shown in uppercase characters. The characters must be entered in the order shown; however, you can enter the characters in either uppercase or lowercase. For example: COMMAND can be entered as any of the following: command Command COMMAND It cannot, however, be entered as: comm com_mand comamnd italics In a syntax statement or an example, a word in italics represents a parameter or argument that you must replace with the actual value. In the following example, you must replace filename with the name of the file: COMMAND filename bold italics In a syntax statement, a word in bold italics represents a parameter that you must replace with the actual value. In the following example, you must replace filename with the name of the file: COMMAND(filename) punctuation In a syntax statement, punctuation characters (other than brackets, braces, vertical bars, and ellipses) must be entered exactly as shown. In the following example, the parentheses and colon must be entered: (filename):(filename) underlining Within an example that contains interactive dialog, user input and user responses to prompts are indicated by underlining. In the following example, "yes" is the user's response to the prompt: Do you want to continue? >> yes { } In a syntax statement, braces enclose required elements. When several elements are stacked within braces, you must select one. In the following example, you must select either ON or OFF: COMMAND { ON } { OFF} [ ] In a syntax statement, brackets enclose optional elements. In the following example, OPTION can be omitted: COMMAND filename [OPTION] When several elements are stacked within brackets, you can select one or none of the elements. In the following example, you can select OPTION or parameter or neither. The elements cannot be repeated. COMMAND filename [ OPTION ] [ parameter] Conventions (continued) [...] In a syntax statement, horizontal ellipses enclosed in brackets indicate that you can repeatedly select the element(s) that appear within the immediately preceding pair of brackets or braces. In the example below, you can select parameter zero or more times. Each instance of parameter must be preceded by a comma: [,parameter][...] In the example below, you only use the comma as a delimiter if parameter is repeated; no comma is used before the first occurrence of parameter: [parameter][,...] |...| In a syntax statement, horizontal ellipses enclosed in vertical bars indicate that you can select more than one element within the immediately preceding pair of brackets or braces; however, each particular element can be selected only once. In the following example, you must select A, AB, BA, or B. The elements cannot be repeated. { A} |...| { B} ... In an example, horizontal or vertical ellipses indicate where portions of an example have been omitted. In a syntax statement, the space symbol shows a required blank. In the following example, parameter and parameter must be separated with a blank: (parameter) (parameter) The symbol indicates a key on the keyboard. For example, RETURN represents the carriage return key or Shift represents the shift key. CTRLcharacter CTRLcharacter indicates a control character. For example, CTRLY means that you press the control key and the Y key simultaneously.