HP 3000 Manuals HP 3000 Manuals
Product HP AdvanceNet SNA NRJE Node Manager's Guide HP Part No. 30292-61000 Printed Apr 1990 Edition 2 E0490 Printed in U.S.A.
Notice Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, 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. Æ Copyright 1988, 1990, Hewlett-Packard Company. This document contains proprietary information, which is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard Company. The information contained in this document is subject to change without notice. Hewlett-Packard Co. 19420 Homestead Rd. Cupertino, CA 95014 U.S.A. Printing History New editions are complete revisions of the manual. Update packages, which are issued between editions, contain additional and replacement pages to be merged into the manual by the customer. The dates on the title page change only when a new edition or a new update is published. No information is incorporated into a reprinting unless it appears as a prior update; the edition does not change when an update is incorporated. Note that many product updates and fixes do not require manual changes and, conversely, manual corrections may be done without accompanying product changes. Therefore, do not expect a one-to-one correspondence between product updates and manual updates. Edition 1 May 1988 Edition 2 April 1990
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. Within the manual, any page changed since the last edition is indicated by printing the date the changes were made on the bottom of the page. Changes are marked with a vertical bar in the margin. If an update is incorporated when an edition is reprinted, these bars are removed but the dates remain. No information is incorporated into a reprinting unless it appears as a prior update. Pages Effective Date All April 1990
Documentation Map The following documentation map is intended to be a general guideline to the manuals containing information related to the product described in this manual. You may need information from one or all the manuals listed here.Preface Introduction This manual describes Hewlett-Packard Company's Systems Network Architecture Network Remote Job Entry (SNA NRJE) product for both the MPE V (NRJE/V) and MPE XL (NRJE/XL) operating systems. Systems Network Architecture (SNA) is a comprehensive specification for distributed data processing networks, developed by IBM.
NOTE In this manual, the term NRJE is used when the information being given is true for both NRJE/V and NRJE/XL. The terms NRJE/V and NRJE/XL are used when a distinction between the two subsystems is necessary.
NRJE allows HP 3000 users to submit batch jobs to a remote host system for processing. The host system uses one of the supported job entry subsystems in an SNA environment. You can submit a job and receive output by using either SNA NRJE commands or a set of procedures called intrinsics. If the data communications line is busy, your job is spooled and is automatically processed when the line becomes free. The IBM host sends output back to the remote SNA NRJE site for printing and storing on disc. SNA NRJE conforms to the protocols defined for a Physical Unit Type 2 (PU.T2), Logical Unit Type 1 (LU.T1) node in an SNA network. This manual describes the steps for configuring SNA NRJE on the HP 3000 system. Audience This manual addresses the HP node manager responsible for planning, configuring, and monitoring the operation of an HP 3000 SNA data communications subsystem. A node manager also handles data communications activities associated with the link between SNA NRJE and the host. The node manager should have knowledge of the MPE operating system, be familiar with how the host system operates, and have HP 3000 node manager (NM) and network administrator (NA) capabilities. Organization This manual is divided into the following chapters and appendix: Chapter 1, SNA NRJE Overview, contains an overview of SNA NRJE and the components of the network. Chapter 2, SNA NRJE Installation Guidelines, discusses installation procedures. Chapter 3, SNA NRJE Configuration, explains how to use the NM configuration manager (NMMGR) to create a hierarchical configuration file for SNA NRJE. Chapter 4, SNA NRJE Workstation Startup and Shutdown, describes how to establish and terminate SNA NRJE workstation sessions. Chapter 5, SNA NRJE Troubleshooting, gives you information about solving problems that might occur while installing, configuring, and running SNA NRJE. Chapter 6, Commands, contains the MPE and NRJE commands a node manager uses. Appendix A, Result Codes and Messages, contains the messages you might encounter while using SNA NRJE. Related HP Publications As an SNA NRJE node manager, you can find related information in these manuals: * Getting Started With SNA Node Management (30246-90002) (MPE V only) * Using the Node Management Services Utilities (32022-61005) (MPE XL only) * SNA Link Services Reference Manual (30246-90003) (MPE V only) * SNA Link/XL Node Manager's Guide (30291-61000) (MPE XL only) * SNA NRJE User/Programmer Reference Manual (30292-61001) * HP SNA Products: Manager's Guide Host System Programmer's Reference (5958-8542) * HP SNA Products: ACF/NCP and ACF/VTAM Guide Host System Programmer's Reference (5958-8543) * HP SNA Products: Job Entry Subsystem Guide Host System Programmer's Reference (5958-8544) * MPE V Command Reference Manual (32033-90006) * MPE Software Pocket Guide (30000-90049) * MPE V System Operation and Resource Management Reference Manual (32033-90005) * MPE V Intrinsics Reference Manual (32022-90007) * MPE XL Commands Reference Manual (32650-60002) * HP SNA Server/Access User's Guide (30254-90001) (MPE V only) * HP SNA Server/Access User's Guide (30254-61000) (MPE XL only) Syntax Conventions nonitalics Words in syntax statements which are not in italics must be entered exactly as shown. Punctuation characters other than brackets, braces, and ellipses must also be entered exactly as shown. For example: EXIT; italics Words in syntax statements that are in italics denote a parameter that must be replaced by a user-supplied variable. For example: CLOSE filename [ ] An element inside brackets in a syntax statement is optional. Several elements stacked inside brackets indicates the user may select any one or none of these elements. For example: [A] [B] User may select A or B or C or none. [C] { } When several elements are stacked within braces in a syntax statement, the user must select one of those elements. For example: {A} {B} User must select A or B or C. {C} ... A horizontal ellipsis in a syntax statement indicates that a previous element may be repeated. For example: [,itemname]...; In addition, vertical and horizontal ellipses may be used in examples to indicate that portions of the example have been omitted. , A shaded delimiter preceding a parameter in a syntax statement indicates that the delimiter must be supplied whenever (a) that parameter is included or (b) that parameter is omitted and any other parameter that follows is included. For example: itema[,itemb][,itemc] means that the following are allowed: itema itema,itemb itema,itemb,itemc itema,,itemc Å When necessary for clarity, the symbol Å may be used in a syntax statement to indicate a required blank or an exact number of blanks. For example: SET[modifier] Å (variable) underlining Brackets, braces, or ellipses appearing in syntax or format statements which must be entered as shown will be underlined. For example: LET var[[subscript]] = value Output and input/output parameters are underlined. A notation in the description of each parameter distinguishes input/output from output parameters. For example: CREATE (parm1,parm2,flags,error) shading Shading represents user input on the terminal's screen. For example: NEW NAME? ALPHA [Key Cap] A string in bold font enclosed by brackets may be used to indicate a key on the terminal's keyboard. For example, [Enter] indicates the carriage return key. [CTRL]-char Control characters are indicated by [CTRL] followed by the character. For example, [CTRL]-Y means the user presses the control key and the Y key simultaneously.
![[]](../../pic3k/M010429/MAP3c50.gif)