OSI/MHS Configuration and Management Manual

ManualsBrandsHP ManualsServerHP NonStop G-Series

OSI/MHS Configuration

and Management

Manual

Abstract

This manual describes how to plan, install, configure, and manage the Open

Systems Interconnection/Message Handling System (OSI/MHS) subsystem.

This manual also describes how to use an OSI/MHS subsystem with Distributed

Systems Management (DSM) and Open Systems Interconnection/Application

Services (OSI/AS). The manual is intended for people who plan, install,

configure, run, manage, and operate an OSI/MHS subsystem.

Product Version

OSI/MHS D42

OSI/MHS H01

Supported Release Version Updates

This manual supports G06.15 and all subsequent G-series RVUs and the H06.03 RVU

and all subsequent H-series RVUs until otherwise indicated by its replacement

publication..

Part Number Published

424827-003 August 2005

Summary of content (542 pages)

PAGE 1
OSI/MHS Configuration and Management Manual Abstract This manual describes how to plan, install, configure, and manage the Open Systems Interconnection/Message Handling System (OSI/MHS) subsystem. This manual also describes how to use an OSI/MHS subsystem with Distributed Systems Management (DSM) and Open Systems Interconnection/Application Services (OSI/AS). The manual is intended for people who plan, install, configure, run, manage, and operate an OSI/MHS subsystem.
PAGE 2
Document History Part Number Product Version Published 132295 OSI/MHS D41 February 1997 424827-001 OSI/MHS D42 December 1999 424827-002 OSI/MHS D42 August 2002 424827-003 OSI/MHS D42 OSI/MHS H01 August 2005
PAGE 3
OSI/MHS Configuration and Management Manual Glossary Index Examples What’s New in This Manual xiii Manual Information xiii New and Changed Information About This Manual xv Who Should Read This Manual? What’s in This Manual? xvi Related Manuals xvii Your Comments Invited xxii Notation Conventions xxii Abbreviations xxvi Figures xiv xv 1. Introduction to OSI/MHS X.
PAGE 4
1. Introduction to OSI/MHS (continued) Contents 1. Introduction to OSI/MHS (continued) Application Interfaces With OSI/MHS 1-31 Transfer X400 Gateway 1-31 Gateway Components 1-31 Message Flow Through the Transfer X400 Gateway General User Gateway 1-35 P7 API Interface 1-35 Summary 1-36 1-32 2.
PAGE 5
2. Management Environment for OSI/MHS (continued) Contents 2. Management Environment for OSI/MHS (continued) MTA (Message Transfer Agent) Objects PROCESS Objects 2-63 ROUTE Objects 2-67 SUBSYS (Subsystem) Objects 2-69 Summary 2-73 2-60 3.
PAGE 6
4. Installing Your OSI/MHS Subsystem Contents 4. Installing Your OSI/MHS Subsystem Other Prerequisite Products 4-1 Installation and Profile Files 4-2 Installation File Keywords.
PAGE 7
5. Configuring Your OSI/MHS Subsystem (continued) Contents 5.
PAGE 8
7. Managing Your OSI/MHS Subsystem (continued) Contents 7.
PAGE 9
8. Sizing and Tuning Your OSI/MHS Subsystem (continued) Contents 8.
PAGE 10
9. Troubleshooting Your OSI/MHS Subsystem (continued) Contents 9. Troubleshooting Your OSI/MHS Subsystem (continued) Effects on the System 9-57 Recovery Checklist 9-57 LO and RS Process Interface Problems Problem Description 9-57 Problem Example 9-59 Problem Reporting 9-67 Effects on the System 9-67 Recovery Checklist 9-67 Summary 9-67 9-57 A.
PAGE 11
C. Mailbox Save and Restore Utilities (continued) Contents C. Mailbox Save and Restore Utilities (continued) SAVEMBOX C-2 SAVEMBOX Operation C-3 SAVEMBOX Examples C-4 RESTMBOX C-5 RESTMBOX Operation C-6 RESTMBOX Examples C-7 Errors and Error Recovery C-8 D.
PAGE 12
Contents F. Routing Support for O/R Names Containing Teletex Attributes F. Routing Support for O/R Names Containing Teletex Attributes How an MTA Routes an MPDU Containing Teletex Attributes F-1 How a Message Store Processes an MPDU Containing Teletex Attributes How OSI/MHS Supports Teletex Attributes in a Bind Request F-2 Example F-2 EMS Messages F-3 Downgrading F-4 The Conversion Table F-4 F-2 G.
PAGE 13
Figures (continued) Contents Figures (continued) Figure 1-13. Figure 1-14. Figure 1-15. Figure 1-16. Figure 1-17. Figure 1-18. Figure 2-1. Figure 2-2. Figure 2-3. Figure 2-4. Figure 2-5. Figure 2-6. Figure 2-7. Figure 2-8. Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 5-1. Figure 5-2. Figure 5-3. Figure 5-4. Figure 5-5. Figure 5-6. Figure 5-7. Figure 5-8. Figure 6-1. Figure 9-1. Figure 9-2. Figure 9-3. Figure 9-4. Figure 9-5. Figure 9-6. Figure 9-7. Figure 9-8. Figure 9-9.
PAGE 14
Figures (continued) Contents Figures (continued) Figure 9-11. Figure 9-12. Figure D-1. Figure D-2. Figure E-1. Figure E-2. Deleting Stored Messages 9-47 CUG Violation 9-49 Use of the OSI Addresses D-6 Complete Address Configuration D-11 Routing Within a Domain E-2 Routing by O/R Name E-6 Tables Table i. Table 1-1. Table 2-1. Table 2-2. Table 2-3. Table 2-4. Table 2-5. Table 4-1. Table 4-2. Table 8-1. Table 9-1. Table 9-2. Table 9-3. Table 9-4. Table 9-5. Table D-1. Table F-1.
PAGE 15
What’s New in This Manual Manual Information OSI/MHS Configuration and Management Manual Abstract This manual describes how to plan, install, configure, and manage the Open Systems Interconnection/Message Handling System (OSI/MHS) subsystem. This manual also describes how to use an OSI/MHS subsystem with Distributed Systems Management (DSM) and Open Systems Interconnection/Application Services (OSI/AS).
PAGE 16
What’s New in This Manual New and Changed Information New and Changed Information This publication has been updated to reflect support of H-series systems. References to D-series systems have been deleted.
PAGE 17
About This Manual The OSI/MHS Configuration and Management Manual describes how to plan, install, configure, manage, and maintain an Open Systems Interconnection/Message Handling System (OSI/MHS) subsystem.
PAGE 18
What’s in This Manual? About This Manual Table i. Standards and Recommendations for the OSI Layers and Application Layer Services (page 2 of 2) ISO Standard CCITT Recommendation Description of Contents 8327 X.225 Session Layer protocol 8822 X.216 Presentation Layer service 8823 X.226 Presentation Layer protocol 8824 X.208 Abstract Syntax Notation 1 (ASN.1) 8825 X.209 Basic Encoding Rules (BER) 8649 X.217 Service ACSE 8650 X.227 Protocol ACSE 9066-1 X.
PAGE 19
Related Manuals About This Manual • • • • • • • • • Section 8, Sizing and Tuning Your OSI/MHS Subsystem, explains how to adjust the configuration of OSI/MHS and related software to improve performance. Section 9, Troubleshooting Your OSI/MHS Subsystem, explains how to diagnose problems in your system. Appendix A, Examples of Configuration Files, contains the SCF command files to configure the OSI/MHS subsystem described in Section 5, Configuring Your OSI/MHS Subsystem.
PAGE 20
Related Manuals About This Manual • • • • • OSI/MHS P7 Application Programmatic Interface (P7 API) Manual contains programming and reference information for C and TAL programmers who use the P7 API procedures.
PAGE 21
Related Manuals About This Manual Figure i. OSI/MHS Manual Set OSI/MHS Orientation Guide Concepts OSI/MHS GPI Programming Guide OSI/MHS GPI Reference Manual OSI/MHS Configuration and Management Manual OSI/MHS Administrative Utility (AU) Manual OSI/MHS P7 API Manual Programming Management Methods and Tools Management Reference for Operators Operator Messages Manual Reference for Automating Management OSI/MHS Management Programming Manual OSI/MHS SCF Reference Manual VST 999.
PAGE 22
Related Manuals About This Manual • • • Introduction to Networking for HP NonStop Himalaya NS-series Servers. This manual provides an overview of networking and data communications products for NS-series servers. SCF Reference Manual for G-Series RVUs. This manual describes the operation of SCF and tells system and network managers how to use SCF to configure, control, and inquire about data communications subsystems running on G-series systems. SCF Reference Manual for H-Series RVUs.
PAGE 23
Related Manuals About This Manual Figure ii.
PAGE 24
Notation Conventions About This Manual running on NonStop S-series servers to access Ethernet and token-ring networks. (G-series) • • • X25AM Configuration and Management Manual. This manual describes the configuration of the X25AM communications subsystem. OSI/AS SCF Reference Manual . This manual describes how to use SCF commands to install, control, and inquire about the OSI/AS subsystem. OSI/TS SCF Reference Manual.
PAGE 25
General Syntax Notation About This Manual General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
PAGE 26
General Syntax Notation About This Manual … Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that you can repeat the enclosed sequence of syntax items any number of times. For example: M address-1 [ , new-value ]... [ - ] {0|1|2|3|4|5|6|7|8|9}... An ellipsis immediately following a single syntax item indicates that you can repeat that syntax item any number of times. For example: "s-char..." Punctuation.
PAGE 27
Notation for Messages About This Manual !i:i. In procedure calls, the !i:i notation follows an input string parameter that has a corresponding parameter specifying the length of the string in bytes. For example: error := FILENAME_COMPARE_ ( filename1:length , filename2:length ) ; !i:i !i:i !o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has a corresponding input parameter specifying the maximum length of the output buffer in bytes.
PAGE 28
Abbreviations About This Manual { } Braces. A group of items enclosed in braces is a list of all possible items that can be displayed, of which one is actually displayed. The items in the list might be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
PAGE 29
Abbreviations About This Manual EDIMG. EDI messaging EDIMS. EDI messaging system EDIN. EDI notification EDI-MS. EDI message store EDI-UA. EDI user agent EIT. Encoded information type G3. Group 3 (facsimile) G4. Group 4 (facsimile) GIP. Gateway Interface Process (HP term) GPI. Gateway Programmatic Interface (HP term) IA5. International Alphabet No. 5 IDU. Internal data unit IM. Interpersonal messaging IPC. Interprocess communication IPM. Interpersonal message IPN. Interpersonal notification ISO.
PAGE 30
Abbreviations About This Manual MTS. Message transfer system NBPS. Nonbasic parameters OM. Object management O/R. Originator/recipient OSI. Open Systems Interconnection OSI/MHS. Open Systems Interconnection/Message Handling System (HP term) P1. Protocol 1 (message-transfer protocol) P2. Protocol 2 (interpersonal-messaging protocol) P3. Protocol 3 (message-submission-and-delivery protocol) PDAU. Physical delivery access unit PDU. Protocol data unit PRMD. Private management domain RTS.
PAGE 31
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
PAGE 32
Change Bar Notation About This Manual OSI/MHS Configuration and Management Manual—424827-003 xxx
PAGE 33
1 Introduction to OSI/MHS The Open Systems Interconnection/Message Handling System (OSI/MHS) is an implementation of the 1988 X.400 Message Handling System (MHS) Recommendations. OSI/MHS allows you to build a large-scale X.400 messaging network on HP NonStop™ computers. The OSI/MHS subsystem runs on most computers that use the NonStop Kernel operating system. OSI/MHS can interoperate with NonStop systems and other X.400 systems, including systems that follow the 1984 X.400 recommendations.
PAGE 34
X.400 Message Handling Systems Introduction to OSI/MHS X.400 Message Handling Systems An X.400 message handling system (MHS) has several types of components. Figure 1-1 shows a high-level overview of an MHS. An MHS user can be either a person or a computer process. A user can send a message (the user is then referred to as an originator) or receive a message (the user is then referred to as a recipient). Each user has a user agent (UA).
PAGE 35
Introduction to OSI/MHS OSI/MHS The remainder of this section describes OSI/MHS. OSI/MHS OSI/MHS is a powerful store-and-forward messaging subsystem that provides you with access to the X.400 network and allows you to implement such services as funds transfer, ordering, billing, and large-scale electronic-mail connectivity. OSI/MHS provides the following functions: • • • • • • Serves as a message transfer agent between adjacent MTAs Provides access to the X.
PAGE 36
Architecture Introduction to OSI/MHS Figure 1-2. Overview of a OSI/MHS Subsystem OSI/MHS Subsystem RS MS Remote User LOGICAL MTA (MR Class) RS MS LO GI Remote User Gateway LO Local User Local User VST 003.VSD OSI/MHS is an application built upon Open Systems Interconnection/ Application Services (OSI/AS) and its underlying subsystems. You must have OSI/AS, Open Systems Interconnection/Transport Services (OSI/TS), and either the X.
PAGE 37
Architecture Introduction to OSI/MHS Figure 1-3 shows the structure of the OSI/MHS environment. Figure 1-3. OSI/MHS Environment User User PS Mail Transfer Subsystem Proprietary Message System Transfer X400 Gateway OSI/MHS Subsystem GPI X.400 Gateway GI Group GIP User User Local UA Local UA LO Group RS Group RS LO MS Group MR Group SC MRP MS RTS OSI/AS OSI/TS TCP/IP X25AM TLAM/PAM X.
PAGE 38
Introduction to OSI/MHS Roles of OSI/MHS As Figure 1-3 shows, an OSI/MHS subsystem consists of the following groups (collections of processes): • • • • • MR groups (one or more), which provide the MTA function RS groups (zero or more), which provide the remote operations service GI groups (zero or more), which provide gateway interfaces LO groups (zero or more), which provide local operations services MS groups (zero or more), which provide long-term storage of messages You can also provide password se
PAGE 39
Roles of OSI/MHS Introduction to OSI/MHS Figure 1-4. Adjacent MTA Message Transfer No nStop System MTA 1 OSI/MHS MTA 2 MTA 4 MTA 3 VST 0 05.VS D In Figure 1-4, if MTA 3 wants to send a message to MTA 4, the message must go though MTA 1, which is the OSI/MHS subsystem. In this example, OSI/MHS relays messages between other MTAs. Using OSI/MHS as a Gateway OSI/MHS can act as a gateway between Transfer applications, such as PS Mail, and the X.400 network.
PAGE 40
Roles of OSI/MHS Introduction to OSI/MHS Figure 1-5. Gateway Function of OSI/MHS NonStop System Transfer Mail Proprietary System Transfer X400 Gateway GPI MTA OSI/MHS X.400 Network VST 006.VSD The Transfer X400 gateway, which is described later in this section, provides access to the X.400 network for Transfer applications, such as PS Mail. You can use PS Mail to transfer messages to an X.400 recipient defined as an MS user on OSI/MHS or to an adjacent MTA for external delivery.
PAGE 41
Roles of OSI/MHS Introduction to OSI/MHS Figure 1-6. Message Store Function of OSI/MHS No nStop System Re mote UA Messa ge Store Re mote UA MTA OSI/MHS Lo cal UA Lo cal UA VST 0 07.VS D OSI/MHS provides interfaces to allow local or remote UAs to access a message store. A remote UA uses the P7 protocol and the Remote Operations Service Element (ROSE) protocol. A local UA uses the P7 Application Programmatic Interface (P7 API).
PAGE 42
Standards Implemented Introduction to OSI/MHS Standards Implemented X.400 is the official messaging protocol for the European community and for Government OSI Profile (GOSIP) networks in the United States. OSI/MHS conforms to the following 1988 International Telegraph and Telephone Consultative Committee (CCITT) X.400 Recommendations: X.400 MHS: System and Service Overview X.402 MHS: Overall Architecture X.407 MHS: Abstract Service Definition Conventions X.
PAGE 43
Introduction to OSI/MHS OSI/MHS Components The P1 protocol defines the messages sent between cooperating MTAs. There are three types of P1 message protocol data units (MPDUs): • • • User message—includes the envelope (which contains information on how to transfer the message) and its contents. Probe—includes the envelope only. A probe serves as a test to whether you can send the message. Report—notifies the user whether the mail has been sent.
PAGE 44
Configuration and Control Introduction to OSI/MHS DSM architecture. For detailed information on the programmatic management interface, see the OSI/MHS Management Programming Manual. Regardless of the method you use, management commands go through the MHS manager process, which constructs a configuration database, controls the various groups, and returns status and configuration information. Figure 1-7 shows the configuration and control components. Figure 1-7.
PAGE 45
Introduction to OSI/MHS • • • • • • • • • Message Relay (MR) Group Receives and responds to commands sent by management applications that exchange Subsystem Programmatic Interface (SPI) messages with the SCP Receives and responds to commands from the SCF product module (through the SCP) Maintains the configuration database Provides online configuration ability Maintains the states of objects under its control Uses the Transaction Management Facility (TMF) for database configuration Reports significant ev
PAGE 46
Message Relay (MR) Group Introduction to OSI/MHS Figure 1-8. Message Relay Group Tran sfer X4 00 Gateway OSI/MHS Su bsystem MR Group MRP RTS MS Group s SC MR PDU Store RS Grou ps OSI /A S Ad ja cen t MTA VST 009.VS D The MR group contains the following: • • • • Message relay (MR) process Reliable transfer service (RTS) process Store cleaner (SC) process MR protocol data unit (PDU) store Each OSI/MHS subsystem must have at least one MR group.
PAGE 47
Introduction to OSI/MHS • • • • • • Message Relay (MR) Group Delivery of messages, and scheduling of messages for delivery Submittal of messages Routing of messages Encoding and decoding of message headers Report generation Recovery The MR process also manages associations, and it provides access management for both the Message Transfer System (MTS) user and the gateway. The MR process is multithreaded in that it allows simultaneous processing of messages.
PAGE 48
Introduction to OSI/MHS Message Store (MS) Group Message Store (MS) Group A message store is used for long-term storage of messages. With a message store, you do not have to be connected to the subsystem when a message arrives; you can log on to the system through a UA whenever you want to read or send messages. When OSI/MHS receives a message destined for an MS user (defined to OSI/MHS as an APPL object), OSI/MHS stores the message in the mailbox for that user.
PAGE 49
Remote Operations Service (RS) Group Introduction to OSI/MHS MS PDU Store Each MS group has one PDU store. The PDU store consists of a data file and a log file. The data file is for storage of protocol data units (PDUs). The log file contains records that indicate the processing steps taken on specific PDUs. These files are defined for each MS group. Figure 1-9. Message Store (MS) Group OSI/MHS Sub system LO Grou ps MS Group MS MR Group s MS PDU Store RS Grou ps MS SQL DB OSI /A S VST 0 10.
PAGE 50
Remote Operations Service (RS) Group Introduction to OSI/MHS presentation services of OSI/AS. Different RS groups “listen” for incoming association requests on the same or different OSI addresses. When a user at a workstation connects to or dials up the message store, the RUA sends a bind request into the system. The RS group has to direct that incoming bind request to the correct MS group for that user. (Individual users are assigned to a particular MS group.
PAGE 51
Introduction to OSI/MHS Local Operations Service (LO) Group An RS group contains the following: • • Remote operations service (RS) process RS PDU store An OSI/MHS subsystem can have zero, one, or more RS groups. If the subsystem includes MS groups, it must have at least one RS group.
PAGE 52
Local Operations Service (LO) Group Introduction to OSI/MHS When a user wants to retrieve a message, the MS group finds the message in the message store and tells the LO group where to find it. The body of the message does not go through the MS group; the LO group accesses it directly from the MS PDU store and sends it to the user. When a user submits a message, the message request goes to the MS group, which allocates a PDU ID. Then the LO group writes the message directly into the MS PDU store.
PAGE 53
Introduction to OSI/MHS Gateway Interface (GI) Group Local Operations Service (LO) Process The LO process is a single, restartable process that provides the following functions: • • • Interfaces to local users through the P7 API Creation and deletion of PDUs in the MR or MS PDU stores as submit and retrieval operations are successfully completed Local Operations Service Element (LOSE) functions LO PDU Store Each LO group has one PDU store. The PDU store consists of a data file and a log file.
PAGE 54
OSI/MHS Interface to OSI/AS Introduction to OSI/MHS Figure 1-12 shows a GI group. Figure 1-12. Gateway Interface (GI) Group GPI OSI/MHS Subsystem GI Group MS Groups MR Groups GI MR PDU Store GI PDU Store VST 038.VSD A GI group contains the gateway interface (GI) process and a PDU store. An OSI/MHS subsystem can have zero, one, or more GI groups.
PAGE 55
OSI/MHS Interface to OSI/AS Introduction to OSI/MHS (LANs), TCP/IP over X25AM, or TLAM for access to the Internet. On G06 and later RVUs, you must use PAM (port access method) to configure OSI/MHS. The interface to OSI/AS by an RTS process or an RS process is provided through a set of procedures called the APS procedures, which communicate with the Application, Presentation, and Session (TAPS) process. The APS procedures and the TAPS process are part of OSI/AS.
PAGE 56
Introduction to OSI/MHS Message Flow Between External Entities and OSI/MHS Message Flow Between External Entities and OSI/MHS The next few pages briefly describe how OSI/MHS communicates with adjacent MTAs and RUAs. Communication Between Adjacent MTAs and OSI/MHS An adjacent MTA communicates with OSI/MHS through the RTS process in an MR group. Each MHS subsystem can have multiple MR groups, and each RTS process can support up to 20 concurrent associations.
PAGE 57
Communication Between Adjacent MTAs and OSI/MHS Introduction to OSI/MHS Figure 1-14. Message Flow Between Adjacent MTAs Using OSI/MHS OSI/MHS MR Group MRP Ad ja cen t MTA 1 Ad ja cen t MTA 2 PDU RTS OSI/AS VS T 013.VS D Transferring a Message From an Adjacent MTA (MTA 1) to OSI/MHS The following steps describe a message flow between adjacent MTAs: 1. The sending MTA (MTA 1) attempts to bind to OSI/MHS by initiating an association request to OSI/MHS. 2.
PAGE 58
Introduction to OSI/MHS Communication From Remote UAs to OSI/MHS 4. MTA 2 accepts that association request if all criteria for connection establishment are satisfied. 5. When an association is established, OSI/MHS transfers the message to MTA 2. Communication From Remote UAs to OSI/MHS A remote UA (that conforms to the 1988 P7 protocol) communicates with OSI/MHS through the RS process in an RS group. Only the RUA is capable of initiating associations to OSI/MHS.
PAGE 59
Communication From Remote UAs to OSI/MHS Introduction to OSI/MHS Figure 1-15. Message Flow From a Remote UA to an MS User on OSI/MHS OSI/MHS MR Group MS Group MRP MS RS Grou p PDU RS Re mote UA OSI/AS VST 0 14.VS D The following steps describe a sample message flow from a remote UA to a single MS user on OSI/MHS: 1. The UA attempts to bind to OSI/MHS by requesting an association with OSI/MHS. 2.
PAGE 60
X.400 Addressing Introduction to OSI/MHS X.400 Addressing Addressing in an X.400 system occurs through the O/R address and route-selection criteria. It also depends on the underlying OSI addressing, as described in Appendix D, OSI Address Configuration in OSI/MHS. Originator/Recipient (O/R) Address Every OSI/MHS user has an O/R address. An O/R address is a logical address that identifies the access point of a user to the MHS.
PAGE 61
Route-Selection Criteria Introduction to OSI/MHS Table 1-1.
PAGE 62
Introduction to OSI/MHS Route-Selection Criteria network addresses or numeric user identifiers If there is a match, and if other O/R address elements defined for the route also match, the message can be routed. For example, if a message is being routed to a recipient at network address 4938541, and no specific route is found, the set of partially wild-carded O/R addresses is examined.
PAGE 63
Introduction to OSI/MHS Application Interfaces With OSI/MHS Application Interfaces With OSI/MHS There are three interfaces you can use to integrate messaging applications with OSI/MHS: the Transfer X.400 gateway, the general user gateway (based on the Gateway Programmatic Interface), and the P7 Application Programmatic Interface. Transfer X400 Gateway The Transfer X400 gateway provides communication between the Transfer subsystem and the OSI/MHS subsystem.
PAGE 64
Message Flow Through the Transfer X400 Gateway Introduction to OSI/MHS Figure 1-16. Transfer X400 Gateway and OSI/MHS Tran sfer S ubsystem Tran sfer X 400 Gateway Tran sfer DB Servers Importer Processes Exporter Processes Tran sfer Da ta base Que ue Man age r Que ue Fil e ADMIN en tri es MESSAGE en tri es EXP ORT en tri es En try Man age r Processes Wait Ma nag er Process OSI/MHS Su bsystem MR Group MRP PDU Store VST 0 15.
PAGE 65
Message Flow Through the Transfer X400 Gateway Introduction to OSI/MHS Figure 1-17. Exporting a Message Through the Transfer X400 Gateway Tran sfer S ubsyste m Tran sfer X 400 Gateway Tran sfer DB Se rvers 4 5 Importer Processes Exporter Processes Tran sfer Da ta base Queue Man age r 3 Que ue Fi le 2 1 ADMIN en tries MESS AGE en tries EXP ORT en tries En try Manage r Processes OSI/MHS Su bsystem Wai t Ma nag er Process 6 MR Group 5 MRP PDU Store VST 0 16.
PAGE 66
Message Flow Through the Transfer X400 Gateway Introduction to OSI/MHS Importing a Message From OSI/MHS to Transfer Figure 1-18 shows the message flow when you import a message from OSI/MHS to Transfer through the Transfer X400 gateway. Figure 1-18.
PAGE 67
Introduction to OSI/MHS General User Gateway 2. The RTS writes the message to the PDU store. 3. The RTS notifies the MR process about the completed message. 4. The MR process reads, decodes, and delivers the message to an entry manager process in the Transfer X400 gateway. 5. The MR process sends an entry (that includes the PDU ID) to the message queue in the queue file. 6. The importer process receives the MESSAGE queue entry and begins to process the PDU. 7.
PAGE 68
Introduction to OSI/MHS Summary Summary OSI/MHS is a 1988 X.400 implementation with MTA and message-store functions. It has several programmatic interfaces for messaging and management applications. It provides services over both wide area networks (WANs) and local area networks (LANs), using X25AM, TLAM, or TCP/IP running over X25AM, or TLAM. On G06 and later RVUs you must use PAM (port access method) to configure OSI/MHS.
PAGE 69
2 Management Environment for OSI/MHS OSI/MHS is an OSI application that uses the OSI/AS subsystem for underlying OSI services. OSI/MHS uses OSI/AS to communicate with other message transfer agents (MTAs) and user agents (UAs). OSI/MHS also supports Distributed Systems Management (DSM) facilities for subsystem management. This section describes the tools for managing OSI/MHS. These tools consist of components both within and outside of the OSI/MHS subsystem.
PAGE 70
Management Environment for OSI/MHS The OSI/MHS Databases control commands. The MHS manager is the first process started in the subsystem and is represented by the first object created: the MON object. You use SCF commands or a management application to communicate with the MHS manager. You can add, start, stop, delete, control, and monitor OSI/MHS components through the MHS manager. The MHS manager executes your commands to configure subsystem objects and the components they represent.
PAGE 71
The OSI/MHS Databases Management Environment for OSI/MHS Figure 2-1. OSI/MHS Databases OSI/MHS Database Registration Database Association Configuration Database Routing User PDU Store Database GI LO MS SQL Database MR MS RS VST 018.VSD Table 2-1. Contents of the OSI/MHS Databases (page 1 of 2) This Database… Includes… Which Contains… Registration Association database Records of MTA objects (representing adjacent MTAs). User database Records of APPL objects (each representing a UA).
PAGE 72
The OSI/MHS Databases Management Environment for OSI/MHS Table 2-1. Contents of the OSI/MHS Databases (page 2 of 2) This Database… Includes… Which Contains… Entry database A record for each message in one of the three delayed-message queues (deferred, link-retry, or route-retry). Each queue is represented by an ENTRY object. OSI address database A record of information for each OSI address that is defined to this OSI/MHS subsystem.
PAGE 73
Management Environment for OSI/MHS The OSI/MHS Databases PDU Store When it is no longer needed, data in a PDU store is removed by the MR group’s StoreCleaner or the MS group’s RUA DELETE. However, the space remains allocated until it is released by a FUP DEALLOCATE command. If a FUP DEALLOCATE command does not release all or most of the allocated space, you may need to reorganize the file internally using the FUP RELOAD command.
PAGE 74
Management Environment for OSI/MHS The OSI/MHS Databases SQLCI DUP MS0m*, new-work-SV, SAVEALL ON where m is the ordinal number of the MS group you want to move. 6. Enter the following commands: SQLCI CREATE CATALOG new-msg-store-SV SQLCI VOLUME current-msg-store-SV 7. If current-msg-store-SV is used only by this MS group enter the following: SQLCI DUP *, new-msg-store-SV, Catalog new-msg-store-SV, SAVEALL ON 8.
PAGE 75
Management Environment for OSI/MHS DSM Management Components Change MSG-store-SV to new-MSG-store-SV Change Work-SV to new-Work-SV 15.
PAGE 76
DSM Management Components Management Environment for OSI/MHS can be used as delivered or customized to meet special requirements. For more information on password servers see OSI/MHS Security Interfaces on page 2-11. The DSM tools that you use to manage your OSI/MHS subsystem are SCF, EMS, PTrace, and ViewPoint. This subsection describes the DSM components that make up the OSI/MHS management environment.
PAGE 77
Subsystem Control Facility (SCF) Management Environment for OSI/MHS Figure 2-3. Event Management Interfaces to OSI/MHS OSI/MHS Subsystem LO Group MR Group MR Group Group MS MS Group GI Group MHS Manager RS Group Event Management Service (EMS) Event Management Interface Alternate Collector Collector Accounting Events Event Messages Event Log Processes for Other Subsystems Event Log Distributo r Filter Terminal VST 020.
PAGE 78
Management Environment for OSI/MHS Subsystem Control Point (SCP) Facility (SCF) Reference Manual describes the general features, syntax, and semantics of SCF. The OSI/MHS SCF Reference Manual provides the subsystemspecific syntax and semantics. Subsystem Control Point (SCP) SCP is an intermediate process between SCF and the OSI/MHS subsystem. It provides security by restricting access to certain commands and provides tracing support for OSI/MHS. SCP is opened automatically by SCF.
PAGE 79
Management Environment for OSI/MHS PTrace PTrace You use the SCF management interface to start and stop the tracing of OSI/MHS subsystem processes. The trace information is gathered in trace files. You use the PTrace program to select, format, and display the trace data. The PTrace Reference Manual gives general information about PTrace. For PTrace information specific to OSI/MHS, see the OSI/MHS SCF Reference Manual.
PAGE 80
Management Environment for OSI/MHS MS Bind Password Server Interface MS Bind Password Server Interface If you develop a password server using the MS bind password server interface, the MS process sends a request to your application when it receives an MS bind request, or an MS register request to change credentials, from a user agent. The MHS manager process sends a request to your application when it receives an ADD, ALTER, or DELETE APPL command from SCF or a management application.
PAGE 81
Management Environment for OSI/MHS SCF Command Interface The File Utility Program (FUP) lets you secure files, including the code files for subsystem processes, to restrict unauthorized access to those files. The authority to read, write, execute, or purge a file can be restricted to one user or to the members of a user group and can be further constrained to permit access only from the local system.
PAGE 82
SCF Command Format Management Environment for OSI/MHS SCF Command Format Each complete SCF command that applies to an OSI/MHS subsystem has the form command object-type object-name [attributes] command is the name of the SCF command, for example, DELETE. object-type designates the type of object to which the command is directed: for example, the ROUTE object type, representing X.400 message routes. (The object type is omitted for the null object.
PAGE 83
Management Environment for OSI/MHS • • The ALTER command omits the GROUP keyword because the preceding ASSUME command specified that keyword. The object name has three parts: • • • • SCF Command Format $ZMHS is the OSI/MHS subsystem name. #RS is the RS CLASS name. RSGROUP1 is the RS GROUP name. This ALTER command is valid only if the GROUP object to which it applies has already been added. The following ASSUME command saves even more keystrokes: ASSUME GROUP $ZMHS.
PAGE 84
Management Environment for OSI/MHS SCF Command Format further security restriction on nonsensitive commands. The nonsensitive SCF commands for the OSI/MHS subsystem are as follows: INFO Displays the current attribute values of an object. LISTOPENS Identifies the processes that have opens or OPEN requests against a PROCESS object or other subsystem process.
PAGE 85
SCF Command Format Management Environment for OSI/MHS START Starts the operation of an object, changing its state from STOPPED to STARTED. STATS Displays accumulated performance statistics for an object, then resets all its statistics counters (if you specify the RESET option). STOP Stops operation of an object in an orderly manner, changing its state from STARTED to STOPPED. SUSPEND Suspends operation of an object, changing its state from STARTED to SUSPENDED.
PAGE 86
How to Use SCF to Manage Your OSI/MHS Subsystem Management Environment for OSI/MHS Table 2-2. Commands by Object Type (page 2 of 2) null SUBSYS ROUTE PROCESS MTA MON GROUP GATEWAY ENTRY DLISTMEMBER DLIST CUGMEMBER CUG CLASS Commands SUSPEND∗ APPL Object Types X TRACE∗ VERSION A X X X X X ∗ This is a sensitive command. ∗∗ This is a sensitive command only when the RESET option is used.
PAGE 87
OSI/MHS Objects Management Environment for OSI/MHS Figure 2-4 shows the hierarchy of the object types that OSI/MHS supports. The lines indicate that each object type is influenced by the attributes of the object type higher up in the hierarchy. (The null object type is not part of this hierarchy.) Figure 2-4. OSI/MHS Objects SUBSYS CLASS GROUP GATEWAY APPL DLIST DLISTMEMBER MON CUG MTA CUGMEMBER ROUTE ENTRY PROCESS VST021.
PAGE 88
Management Environment for OSI/MHS OSI/MHS Objects more groups of the same kind. Each group contains one or more processes. For example, the MS class includes all the MS groups in the OSI/MHS subsystem, and each MS group contains one MS process and one PDU store. An APPL object defines information about users of OSI/MHS message stores—that is, about user agents—or users of gateways. APPL objects are subordinate to the SUBSYS object.
PAGE 89
Management Environment for OSI/MHS OSI/MHS Objects In an OSI/MHS subsystem, every object name has a second qualifier that is always required: the name of the MHS manager process that you specify during installation. Therefore, every OSI/MHS object name starts with [\system.]$manager-process where system is the name of the NonStop system that runs the MHS manager process for this subsystem. manager-process is the process name chosen for the MHS manager process.
PAGE 90
Management Environment for OSI/MHS APPL Objects The wild-card characters are: • • The question mark (?), which is used as a placeholder for a single unspecified character The asterisk (∗), which is used as a placeholder for zero or more unspecified characters For example, to issue a command to all groups within a class, replace the group qualifier with an asterisk. Thus the partial name $ZMHS.#RS.∗ would apply to all the RS groups (#RS is the class qualifier).
PAGE 91
Management Environment for OSI/MHS APPL Objects Message Store (MS) APPL Object A message store (MS) APPL object type represents an X.400 user agent (UA) to the OSI/MHS subsystem. The user application enables the UA to submit messages to, and retrieve them from, one of the subsystem message stores.
PAGE 92
Management Environment for OSI/MHS APPL Objects Figure 2-5. APPL Object States ADD UNDEFINED START STOPPED DELETE STARTED STOP or ABORT STOP or ABORT ACTIVATE SUSPEND SUSPENDED Note: Boxes represent the states of an APPL object, and arrows represent the SCF commands that change its state. VST 025.
PAGE 93
Management Environment for OSI/MHS APPL Objects reject the UA request to submit a message, and it will reject an incoming message addressed to the UA. You suspend an APPL object by directing a SUSPEND command to it. You cannot alter its attributes while it is in the SUSPENDED state. UNDEFINED means that no user application with the specified name is defined to the MHS manager.
PAGE 94
Management Environment for OSI/MHS APPL Objects : ABORT Forces the state of an OSI/MHS APPL object from STARTED or SUSPENDED to STOPPED. For message-store APPL objects: If the UA for a user application is already associated with the subsystem, the results of an ABORT command are that the subsystem aborts the association, and the UA receives an error message the next time it tries to access the message store. The results are the same for a STOP command with the FORCED option.
PAGE 95
Management Environment for OSI/MHS DELETE APPL Objects For message-store APPL objects: Deletes an OSI/MHS APPL object definition from the MS user and routing databases. You must delete all user applications attached to an MS group before you delete the MS. Before deleting a user application, you must stop it. However, before you stop it, you might want to suspend it for a while.
PAGE 96
Management Environment for OSI/MHS STATUS Displays the operational status of an MS APPL object. STOP Changes the state of an APPL object from STARTED or SUSPENDED to STOPPED. APPL Objects You must stop a user application before you delete it. For message-store APPL objects: To be sure of stopping a user application, you must include the FORCED option in the STOP command.
PAGE 97
Management Environment for OSI/MHS APPL Objects The following sequence of commands adds user application number 27 to MS group 6, and first establishes, then alters, the application password. The user performs these actions using the required attributes ACCESS-TYPE, ACCESS-NAME, and USER-PASSWORD. ACCESS-NAME specifies the message store group that serves this APPL.
PAGE 98
Management Environment for OSI/MHS CLASS Objects An example of a specific APPL is one gateway correspondent: it is unique and maps only to that gateway correspondent. A specific APPL object specifies personal name or common name attributes, such as SUR-NAME, GIVEN-NAME, and INITIALS. Note. HP recommends that you use generic APPL objects for your Transfer X400 and general user gateways, because they are easier to maintain than specific APPL objects.
PAGE 99
Management Environment for OSI/MHS • CLASS Objects Find out the attribute values and operational status of the class CLASS Object Summary States An OSI/MHS class can go through a sequence of states that depend on and summarize the states of its subordinate objects. You can use the SCF STATUS command to inquire about the summary state of a class. Other SCF commands allow you to change its summary state. Figure 2-6.
PAGE 100
Management Environment for OSI/MHS CLASS Objects Table 2-3.
PAGE 101
Management Environment for OSI/MHS CLASS Objects SCF Commands for CLASS Objects You can direct any of the following SCF commands to the OSI/MHS CLASS object specified or assumed in the command: ABORT Changes the summary state of an OSI/MHS class from STARTED to STOPPED. For the CLASS object to be in the STOPPED state, the subordinate GROUP objects must first be in the STOPPED state.
PAGE 102
Management Environment for OSI/MHS START CLASS Objects Changes the summary state of an OSI/MHS class from STOPPED to STARTED. You issue a START CLASS command as part of a normal startup, after you start the SUBSYS object and before you start the GROUP object. The transition from a STOPPED to a STARTED state is immediate: there is no STARTING state for a CLASS object. You must start a class to start its subordinate groups. You can accomplish both with the START CLASS, SUB ALL command.
PAGE 103
Management Environment for OSI/MHS CUG (Closed User Group) Objects NAMES CLASS $ZMHS.#MR, SUB ONLY STATUS CLASS $ZMHS.#RS, SUB ALL, SEL STARTED The MS CLASS object has only one attribute: namely, the maximum number of mailboxes in the message store of each MS group. The number of APPL objects you create for any MS group must not exceed the number of mailboxes you allow for the MS class. The maximum number of mailboxes in the PDU store of any MS group is set by the ADD command that creates the MS class.
PAGE 104
Management Environment for OSI/MHS CUG (Closed User Group) Objects system is the name of the system (node) that runs the MHS manager process for this OSI/MHS subsystem. manager-process is the name you have given the MHS manager process (the MON object). This name must be a letter followed by zero through three alphanumeric characters. cug is the name that distinguishes this CUG object from all the other objects in this OSI/MHS subsystem, and in particular from the other CUG objects.
PAGE 105
Management Environment for OSI/MHS CUGMEMBER (Closed User Group Member) Objects CUGMEMBER (Closed User Group Member) Objects The CUGMEMBER object type identifies a member of a closed user group. The attributes of this object specify the O/R name of the member.
PAGE 106
Management Environment for OSI/MHS DLIST (Distribution List) Objects SCF Commands for CUGMEMBER Objects You can direct any of the following SCF commands to the OSI/MHS CUGMEMBER object specified or assumed in the command: ADD Defines a CUGMEMBER object to the OSI/MHS subsystem. ALTER Changes one or more attributes of an OSI/MHS CUGMEMBER object. DELETE Deletes a CUGMEMBER object definition from the OSI/MHS subsystem configuration.
PAGE 107
Management Environment for OSI/MHS DLIST (Distribution List) Objects Naming DLIST Objects A DLIST object name has the following form: [\system.]$manager-process.#dlist system is the name of the system (node) that runs the MHS manager process for this OSI/MHS subsystem. manager-process is the name you have given the MHS manager process (the MON object). This name must be a letter followed by zero through three alphanumeric characters.
PAGE 108
Management Environment for OSI/MHS DLISTMEMBER (Distribution List Member) Objects The following is an example of using an ADD DLIST command to define a distribution list. This example shows that the DLIST object name is $ZMHS.#SALES. ADD DLIST $ZMHS.
PAGE 109
Management Environment for OSI/MHS ENTRY Objects SCF Commands for DLISTMEMBER Objects You can direct any of the following SCF commands to the OSI/MHS DLISTMEMBER object specified or assumed in the command: ADD Defines a DLISTMEMBER object to the OSI/MHS subsystem. ALTER Changes one or more attributes of an OSI/MHS DLISTMEMBER object. DELETE Deletes a DLISTMEMBER object definition from the OSI/MHS subsystem configuration.
PAGE 110
Management Environment for OSI/MHS ENTRY Objects priority, and probable delay of the messages on the queues. The three queues (that is, the three ENTRY objects) are: Deferred Message Queue This queue holds messages whose transmission is deferred to a specific later time at the request of their originators. Start-time, which you can display by using the STATUS command, is the time the message is placed in the deferred message queue.
PAGE 111
Management Environment for OSI/MHS ENTRY Objects If a message is placed on the route-retry queue more than once, the delay increases as specified by the appropriate CLASS attribute from this list (depending on the category of message): URGENT-ROUTE-RETRY-GROW NORMAL-ROUTE-RETRY-GROW NONURGENT-ROUTE-RETRY-GROW REPORT-ROUTE-RETRY-GROW The delay time increases exponentially with each retry, according to the following formula: delay =xxx-ROUTE-RETRY-DELAY * (1.
PAGE 112
Management Environment for OSI/MHS ENTRY Objects manager-process is the name you have given the MHS manager process (the MON object). This name must be a letter followed by zero through three alphanumeric characters. entry is the name that distinguishes this ENTRY object from all the other objects in this OSI/MHS subsystem, and in particular from the other ENTRY objects.
PAGE 113
Management Environment for OSI/MHS GATEWAY Objects GATEWAY Objects A GATEWAY object identifies the gateways that are attached to the OSI/MHS subsystem. You can configure Transfer X400 gateways and general user gateways.
PAGE 114
Management Environment for OSI/MHS GATEWAY Objects exit gateway before OSI/MHS decodes or routes them. Typically, an exit gateway is configured in cases where messages received from remote systems are to be examined or modified by an external GPI-based application prior to normal processing by OSI/MHS. GW-PNAME specifies the name of the entry manager process(es). GW-PNAME is a list of up to five entry manager process names.
PAGE 115
Management Environment for OSI/MHS GATEWAY Objects gateway is the name of the GATEWAY object. For example, a GATEWAY object name could be $ZMHS.#TG. SCF Commands for GATEWAY Objects You can direct any of the following SCF commands to the OSI/MHS GATEWAY object specified or assumed in the command: ADD Defines a GATEWAY object to the OSI/MHS subsystem. ALTER Changes one or more attributes of an OSI/MHS GATEWAY object.
PAGE 116
Management Environment for OSI/MHS GROUP Objects This example shows the GATEWAY object name is $ZMHS.#GW1, and it is associated with two entry manager processes: $EM01 and $EM02. This gateway is a 1984 implementation. In this example, the OSI/MHS subsystem will validate each message before transferring it to the gateway, and it will respond to probes destined for the gateway.
PAGE 117
Management Environment for OSI/MHS • • • • GROUP Objects Add, delete, and alter the specified group Start and stop the group and the process(es) it contains Find out the name(s) of the process(es) configured in the group Find out the names of some or all groups in the OSI/MHS subsystem GROUP Object Summary States An OSI/MHS GROUP object can go through a sequence of states that depends on the states of its subordinate PROCESS object(s).
PAGE 118
Management Environment for OSI/MHS GROUP Objects STOPPING is a transitional state. It means that a STOP or ABORT command was directed at a GROUP object, but one or more PROCESS objects in the group have not yet stopped. The UNDEFINED state means that no group with the specified name is defined to the MHS manager.
PAGE 119
Management Environment for OSI/MHS GROUP Objects class is the name of the CLASS object that includes this OSI/MHS group. The class name must be one of the following: GI (in a gateway interface group name) LO (in a local service group name) MR (in a message relay group name) MS (in a message store group name) RS (in a remote operations service group name) gsystem is the name of the system on which you install this OSI/MHS group. gsystem should be the same system where the MHS manager resides.
PAGE 120
Management Environment for OSI/MHS GROUP Objects SCF Commands for GROUP Objects You can direct any of the following SCF commands to the OSI/MHS GROUP object specified or assumed in the command: ABORT Forces the state of an OSI/MHS group from STARTED to STOPPED. Before the GROUP object can be in the STOPPED state, its subordinate PROCESS object(s) must stop. The ABORT command does this automatically, and during the time this takes, the group is in the STOPPING state.
PAGE 121
Management Environment for OSI/MHS ALTER GROUP Objects Alters one or more attributes of an OSI/MHS group. Most of the attributes refer to the process(es) contained in the group. The ALTER command for an MS GROUP object allows you to specify whether or not MS bind authentication parameters are to be validated using an external password server process. If so, you also specify the name of the password server. For more information on password servers, see OSI/MHS Security Interfaces on page 2-11.
PAGE 122
Management Environment for OSI/MHS STOP GROUP Objects Changes the state of an OSI/MHS group from STARTED to STOPPED. Before the GROUP object can be in the STOPPED state, the subordinate PROCESS object(s) must stop. The STOP command does this automatically, and, during the time this takes, the group is in the STOPPING state. This occurs differently depending on whether you use the MAX option or the FORCED option. The FORCED option is the default.
PAGE 123
Management Environment for OSI/MHS PRI PDU-STORE PDU-LOG-FILE WORK-SV MS-PNAME MSG-STORE-SV MR-COUNT MON (Monitor) Objects 130, MHS1MS1.PDUMS1, MHS1MS1.LOGMS1, MHS1MS1, $MHS1.#I11, MHS1MS1, SYS & & & & & & Note that the MS process name used, $MHS1.#I11, includes the name of the MHS manager process, but omits system, class, and group names. This form of the process name is required by the attribute MS-PNAME and has nothing to do with the preceding ASSUME command.
PAGE 124
Management Environment for OSI/MHS MON (Monitor) Objects Naming MON Objects For any OSI/MHS subsystem, the MON object name is the name given the MHS manager process. The same name is used for the null object. This name has the form: [\system.]$manager-process system is the name of the system (node) that runs the MHS manager process for this OSI/MHS subsystem. manager-process is the process name of the MHS manager process. This name must be a letter followed by zero through three alphanumeric characters.
PAGE 125
Management Environment for OSI/MHS ALTER MON (Monitor) Objects Alters one or more attributes of the MHS manager process pair. These affect the manager backup process and associated files and the collection of subsystem event messages by EMS. ALTER works dynamically for attributes such as CPU and BACKUPCPU while MON is in a STARTED state. You can alter the attributes without stopping the MHS manager.
PAGE 126
Management Environment for OSI/MHS null Objects Examples of Commands for the MON Object The following are examples of commands for the MON object.
PAGE 127
Management Environment for OSI/MHS null Objects created and the MON object defined. The null object is used to list the objects in the subsystem or to obtain the subsystem version ID. null Object States The null object does not have a summary state, even though all the objects within the subsystem are subordinate to it. The SCF STATUS command, which returns state information, does not apply to the null object.
PAGE 128
Management Environment for OSI/MHS MTA (Message Transfer Agent) Objects Examples of Commands for the null Object The following examples show how you can use the null object to seek information about your subsystem: ASSUME NAMES $ZMHS VERSION $ZMHS == resets any previously set ASSUME command Notice that commands for the null object—unlike those for all other OSI/MHS objects— do not specify the object type before the object name.
PAGE 129
Management Environment for OSI/MHS MTA (Message Transfer Agent) Objects system is the name of the system (node) that runs the MHS manager process for this OSI/MHS subsystem. manager-process is the name you have given the MHS manager process (the MON object). This name must be a letter followed by zero through three alphanumeric characters.
PAGE 130
Management Environment for OSI/MHS ALTER MTA (Message Transfer Agent) Objects Alters one or more attributes of an OSI/MHS MTA object. The attributes describe an actual adjacent MTA. The REM-MTA-NAME attribute is not valid for this command; you can neither alter nor add the name of an adjacent MTA once you have added the corresponding MTA object. The name must be included in the original object definition the first time you add it to the subsystem.
PAGE 131
Management Environment for OSI/MHS PROCESS Objects NAMES MTA $ZMHS.#WASHDC, SUB ALL NAMES MTA $ZMHS.#NYC05, SUB ONLY The following command shows the attributes you must include when adding an MTA object. The last four attributes set a pair of OSI addresses for the object. Up to seven pairs are possible; at least one pair is required. ADD MTA $ZMHS.
PAGE 132
Management Environment for OSI/MHS PROCESS Objects Types of PROCESS Objects OSI/MHS defines five types of PROCESS objects: one for RS groups, one for MS groups, and three for MR groups. Table 2-5.
PAGE 133
Management Environment for OSI/MHS PROCESS Objects process is the name used to distinguish this PROCESS object from all other objects in this OSI/MHS subsystem, and in particular from other PROCESS objects. The name must be an alphabetic character followed by zero through three alphanumeric characters. In this context, the process name is not preceded by a dollar sign ($), but it is preceded by a pound sign (#) if the gsystem qualifier is omitted.
PAGE 134
Management Environment for OSI/MHS PROCESS Objects SCF Commands for PROCESS Objects You can direct any of the following SCF commands to the OSI/MHS PROCESS object specified or assumed in the command: NAMES Displays the names of some or all PROCESS objects in this OSI/MHS subsystem. When used for the PROCESS object type, this command never displays names for any other object type, because a PROCESS object has no subordinate objects.
PAGE 135
Management Environment for OSI/MHS ROUTE Objects The first several examples illustrate the nonsensitive commands you can use to obtain information about a PROCESS object: NAMES PROCESS $ZMHS.#MSP1 STATS PROCESS $ZMHS.#MSP3 STATUS PROCESS $ZMHS.#MSP2 STATUS PROCESS $ZMHS.#MSP2, DETAIL The next example shows a sensitive command you can use for information: STATS PROCESS $ZMHS.#MSP3, RESET This STATS command differs from the earlier, nonsensitive example because it resets the statistics counters.
PAGE 136
Management Environment for OSI/MHS ROUTE Objects Naming ROUTE Objects A ROUTE object name has the form: [\system.]$manager-process.#mta.route system is the name of the system (node) that runs the MHS manager process for this OSI/MHS subsystem. manager-process is the name you have given the MHS manager process (the MON object). This name must be a letter followed by zero through three alphanumeric characters. mta is the object name for the adjacent MTA to which messages travel that take this route.
PAGE 137
Management Environment for OSI/MHS SUBSYS (Subsystem) Objects Examples of Commands for ROUTE Objects The following are examples of commands for ROUTE objects. The following examples show nonsensitive commands you can use to obtain information about OSI/MHS ROUTE objects: NAMES ROUTE $ZMHS.∗ NAMES ROUTE $ZMHS.#BOSTON1.ROUTE∗ NAMES ROUTE $ZMHS.#NYC05 INFO ROUTE $ZMHS.#OSIMHS003.ROUTE1 INFO ROUTE $ZMHS.#OSIMHS003.ROUTE1, DETAIL INFO ROUTE $ZMHS.#∗.
PAGE 138
Management Environment for OSI/MHS SUBSYS (Subsystem) Objects Figure 2-8. SUBSYS Object Summary States ADD UNDEFINED START STOPPED STARTED DELETE STOP or ABORT STOPPING Note: Boxes represent the stable subsystem states; ovals represent transition states; and arrows represent the SCF commands that change the state of the subsystem. VST 022.VSD STARTED, for an OSI/MHS subsystem, is the state that allows you to start the subsystem subordinate objects.
PAGE 139
Management Environment for OSI/MHS SUBSYS (Subsystem) Objects manager-process is the name you have given the MHS manager process (the MON object). This name must be a letter followed by zero through three alphanumeric characters. subsystem is the name you have chosen to distinguish the SUBSYS object from all the other objects in this OSI/MHS subsystem. This name must be a letter followed by 0 through 15 alphanumeric characters.
PAGE 140
Management Environment for OSI/MHS ALTER SUBSYS (Subsystem) Objects Alters one or more attributes of the OSI/MHS subsystem. The SUBSYS object must be in a STOPPED state before you alter it. This requires that all classes and subordinate objects (GROUP and PROCESS) also be in a STOPPED state. The entire system, except for the MHS manager, must be shut down before you issue the ALTER command on the SUBSYS object. DELETE Deletes the SUBSYS object definition from the OSI/MHS configuration database.
PAGE 141
Management Environment for OSI/MHS Summary they are also known as the registration database. If you follow the default installation procedure, they will reside in one subvolume. After you install the OSI/MHS subsystem, you use ADD commands to configure it. You start by adding the SUBSYS object: ADD SUBSYS $ZMHS.#SUBS1, USER-FNAME $VOL1.REGDB.APPLS, MTA-ASSOC-FNAME $VOL1.REGDB.MTAS, ROUTING-FNAME $VOL1.REGDB.
PAGE 142
Management Environment for OSI/MHS Summary This section described the OSI/MHS objects and the implications of the SCF commands on those objects. Section 7, Managing Your OSI/MHS Subsystem, provides examples of how to manage the subsystem, using these commands. Once you understand the basic concepts behind OSI/MHS and the environment in which it functions, you are ready to begin planning the requirements, parameters, and configuration of your subsystem.
PAGE 143
3 Planning Your OSI/MHS Subsystem Planning your OSI/MHS subsystem is a challenging task. You start by defining the characteristics of your user community, and of existing and planned applications. Then you consider the requirements those characteristics place on your network, and you gradually narrow your focus until you have defined a complete and appropriate configuration. At each step you must make decisions that often determine your next step.
PAGE 144
Planning Your OSI/MHS Subsystem • • • What Are Your Network Planning Considerations? What communication networks will you use? (X.25? LAN? TCP/IP over one or both of these?) What are the expected message rates and sizes? OSI/MHS supports messages up to 10 MB for relay to an adjacent MTA, for delivery to a general user gateway, and for delivery to or submission by a local user agent.
PAGE 145
Planning Your OSI/MHS Subsystem • Using OSI/MHS for Adjacent MTA Message Transfer Any combination of the above You also need to consider whether your subsystem will be used as an ADMD or a PRMD. See Appendix B, Configuration Checklists, for checklists to help you describe your subsystem. Using OSI/MHS for Adjacent MTA Message Transfer You can use OSI/MHS in a message-switching network. A message-switching network provides a public service for X.
PAGE 146
Planning Your OSI/MHS Subsystem Using OSI/MHS to Communicate With the Transfer Subsystem In planning your OSI/MHS subsystem, you must consider your subsystem, each adjacent MTA, and each nonadjacent MTA through which you want to transfer messages. Appendix B, Configuration Checklists, contains checklists for: • • • Describing your subsystem Planning an adjacent MTA Planning a nonadjacent MTA Using OSI/MHS to Communicate With the Transfer Subsystem You can transfer X.
PAGE 147
Planning Your OSI/MHS Subsystem • • Using OSI/MHS P7 API to Communicate With Local Users What is your expected message volume and how will it affect availability? Message volume affects the number of entry manager processes you want to use. (You can have up to five entry manager processes.) Message volume also determines the size of the entry manager queue files and log queue files.
PAGE 148
Planning Your OSI/MHS Subsystem Using OSI/MHS as a Message Store To connect to the MS, a UA accesses the message store through the OSI/AS services using an X.25 or LAN connection. If you plan to use the OSI/MHS subsystem as a message store, you should consider the following: • • • • How many MS users will you have? (Each MS group can have up to 1000 user mailboxes.
PAGE 149
Planning Your OSI/MHS Subsystem How Will You Determine Route-Selection Criteria? How Will You Determine Route-Selection Criteria? Route selection is part of the process of determining which path through the network a message will take to reach its final destination. The ROUTE objects defined within the OSI/MHS subsystem determine to which adjacent MTA a particular message will be routed.
PAGE 150
Planning Your OSI/MHS Subsystem International Regulations Concerning Management Domains Figure 3-1. Example of Route Selection Country A Country B PRMD 1 ADMD 1 MTA 1 MTA 2 MTA 4 MTA 3 VST 026.VSD After you determine the answers to the route-selection questions, you can continue to the next level of issues. These issues appear in the following list and are described in more detail in the following subsections.
PAGE 151
Planning Your OSI/MHS Subsystem International Regulations Concerning Management Domains CCITT Recommendations CCITT recommendations restrict international message transfer to ADMD-to-ADMD routing. For example, if you want to send a message from PRMD-1 in country A to PRMD-2 in country B, the message must follow the path shown in Figure 3-2. Figure 3-2. CCITT ADMD-to-ADMD Routing Country A Country B ADMD 1 PRMD 1 MTA ADMD 2 MTA MTA PRMD 2 MTA VST 027.
PAGE 152
Planning Your OSI/MHS Subsystem O/R Name Addressing Forms O/R Name Addressing Forms A major consideration in network planning is O/R name conventions. In X.400 messaging there are many ways to name people and objects.
PAGE 153
Planning Your OSI/MHS Subsystem Link Retries and Route Retries Figure 3-4. Alternate Routes Co untry A Co untry B PRMD 1 ADMD 1 MTA 1 MTA 4 Ro ute 1 MTA 2 MTA 3 Ro ute 2 (Altern ate Route) VS T 0 29.VS D If you want to define alternate routes, you must determine how to configure link retries, route retries, and priorities. The following paragraphs describe these topics. Link Retries and Route Retries Links are defined by pairs of OSI addresses that are configured for each MTA.
PAGE 154
Planning Your OSI/MHS Subsystem Link Retries and Route Retries are no more addresses for MTA2, the RTS process reports to the MR process that it was unable to transfer to MTA2. At that point, the MR process uses a routing table to determine if there are any alternate routes to MTA2. If there is an alternate route, then the MR process returns the message to the RTS process for transfer and the link-retry procedure begins for that route.
PAGE 155
Planning Your OSI/MHS Subsystem Link Retries and Route Retries Figure 3-5. Link and Route-Retry Attribute Relationships PRMD 1 2 MTA1 3 4 Route 1 (3 links) 6 Route 2 (4 links) 5 7 MTA2 MTA3 1 From MTA4 8 9 10 11 1 Message arrives at MTA 3 from MTA4, for delivery to user at MTA1. Retrieve arrival time in domain from message; ROUTE-RETRY-TIME is measured from that time. 2 Try link 1 on route 1. LINK-RETRY-TIME is measured from here. 3 Try link 2 on route 1. 4 Try link 3 on route 1.
PAGE 156
Planning Your OSI/MHS Subsystem Priorities With link retry, if all the links fail and the link-retry time expires, no report or error event message is produced. OSI/MHS records each link retry in the InternalTraceInformation field of the X.400 message. It records each route retry in the TraceInformationElement field of the X.400 message. Adjust the RETRY-TIME attributes as needed to prevent retries from consuming too much processing power and memory.
PAGE 157
Planning Your OSI/MHS Subsystem Resilience and Expandability However, for better performance, you may want to spread the workload across multiple CPUs. For example, if you wanted to distribute the workload of a single MR group, you could put the MR process on one CPU and the RTS and SC processes on another. Do not put processes from different groups on the same processor. For example, do not put a process from MR group 1 on the same CPU as a process from MR group 2.
PAGE 158
Planning Your OSI/MHS Subsystem • MS Groups What pattern of message flow do you expect? How do you want to set up your store cleaner? (How often should it run?) MS Groups You can determine the number of message stores you need by the number of users you anticipate. Each message store can support up to 1000 users. Each MS group has its own PDU store database and SQL database. When you add MS groups, you also add these databases.
PAGE 159
Planning Your OSI/MHS Subsystem High Performance Each group has its own PDU store as a separate database, which you can configure to reside on several disk volumes. All the groups in the OSI/MHS subsystem are controlled by a single MHS manager process and they can all use the same OSI/AS services. Each subsystem represents one MTA. From an external view, an adjacent MTA does not know to which of the groups it is connected. You can configure several MTAs (OSI/MHS subsystems) on the same system.
PAGE 160
Planning Your OSI/MHS Subsystem Manageability Manageability OSI/MHS is fully integrated with DSM. You can manage it from ViewPoint and see events reported through the Event Management Service (EMS). You can manage a network of distributed systems from one location. OSI/MHS itself provides extensive data for accounting and message tracking.
PAGE 161
4 Installing Your OSI/MHS Subsystem This section explains how to install OSI/MHS, either as a new product or as an upgrade from a previous version.
PAGE 162
Installing Your OSI/MHS Subsystem Installation and Profile Files RUN SQLCI CREATE SYSTEM CATALOG [$diskSQL]; INITIALIZE SQL; EXIT $disk specifies the disk where the SQL catalog will reside. That disk must be TMF audited. Installation and Profile Files To install an OSI/MHS subsystem, you supply values in an installation file (a profile file on S-series systems) and then follow the installation procedure.
PAGE 163
Installing Your OSI/MHS Subsystem Installation File Keywords. Table 4-1.
PAGE 164
Installing Your OSI/MHS Subsystem Keyword Groups Table 4-1. Installation File Keywords (page 3 of 3) Keyword Meaning CREATE_SAMPLE_CONFIG YES or NO ROUTE_DATABASE_CONVERSION YES or NO MS_DATABASE_CONVERSION YES or NO Only one keyword and value is accepted for each line. You can add comments by using two equals signs (==) at the beginning of a line. Keyword Groups The keywords for the PDU stores listed in Table 4-1 are in five groups: MR, MS, RS, GI, and LO.
PAGE 165
Installing Your OSI/MHS Subsystem Keyword Defaults You must specify at least one pair of MR_ keywords for every OSI/MHS subsystem. You do not need to specify any MS_ keywords unless you plan to configure message stores. You do not need to specify any RS_ keywords unless you plan to configure remote operations service groups. You do not need to specify any GI_ keywords unless you plan to configure gateway interfaces.
PAGE 166
Installing Your OSI/MHS Subsystem Installation File Examples Examples of complete installation files are included in the OSI/MHS software, in the ISV subvolume ZOSIMHS. Copies of these files are also included in Appendix A, Examples of Configuration Files. Example 4-1 shows the basic installation file. This is the default file created when you first run the installation procedure. Example 4-1.
PAGE 167
Installing Your OSI/MHS Subsystem Installation File Examples Example 4-2 shows an extended new installation file for multiple MR, MS, RS, GI, and LO groups. ) Example 4-2.
PAGE 168
Installing Your OSI/MHS Subsystem Installation File Examples Example 4-2. Extended New Installation File Example, Install2 (page 2 of 2) GI_PDU_STORE_DATA1 GI_PDU_STORE_LOG1 GI_PDU_STORE_DATA2 GI_PDU_STORE_LOG2 GI_PDU_STORE_DATA3 GI_PDU_STORE_LOG3 GI_PDU_STORE_DATA4 GI_PDU_STORE_LOG4 $myvol.mh1gidb.pdugi1 $myvol.mh1gidb.loggi1 $myvol.mh1gidb.pdugi2 $myvol.mh1gidb.loggi2 $myvol.mh1gidb.pdugi3 $myvol.mh1gidb.loggi3 $myvol.mh1gidb.pdugi4 $myvol.mh1gidb.
PAGE 169
Installing Your OSI/MHS Subsystem Installation File Examples Example 4-3 shows an extended upgrade installation for multiple MR, MS, RS, GI, and LO groups. Example 4-3.
PAGE 170
Installing Your OSI/MHS Subsystem Installation File Examples Example 4-3. Extended Upgrade Installation File Example, Install3 (page 2 of 2) GI_PDU_STORE_DATA1 GI_PDU_STORE_LOG1 GI_PDU_STORE_DATA2 GI_PDU_STORE_LOG2 GI_PDU_STORE_DATA3 GI_PDU_STORE_LOG3 GI_PDU_STORE_DATA4 GI_PDU_STORE_LOG4 $myvol.mh1gidb.pdugi1 $myvol.mh1gidb.loggi1 $myvol.mh1gidb.pdugi2 $myvol.mh1gidb.loggi2 $myvol.mh1gidb.pdugi3 $myvol.mh1gidb.loggi3 $myvol.mh1gidb.pdugi4 $myvol.mh1gidb.
PAGE 171
Installing Your OSI/MHS Subsystem Installing OSI/MHS for the First Time Installing OSI/MHS for the First Time To start a new installation, you run the OSI/MHS installation procedure. This procedure reads an installation file (such as the ones shown in Example 4-1 and Example 4-2). The procedure then prompts you for input. The input values you supply determine the type of installation. At the end of this process, the installation menu displays your input values and asks you to confirm them.
PAGE 172
Installing Your OSI/MHS Subsystem Starting the Installation Procedure Note. When you create an RDF (Remote Database Facility) in a backup system, MHSINST provides an option called RDF that allows you to audit and change the alternate file locations of all database files If you use MHSINST for this purpose, you should not specify INSTFILE. For detailed information about how to use the RDF option, see Appendix G, Remote Duplicate Database Facility (RDF) Support.
PAGE 173
Installing Your OSI/MHS Subsystem Starting the Installation Procedure If your response is yes, the following message is displayed. Prototype installation created in file "". -> Please edit this installation file and then run "mhsinst" (You can use "mhsinst instfile " to re-run the installation.) again.<- Exiting mhsinst You can then edit the installation file to reflect your subsystem setup and the operations you want the system to perform.
PAGE 174
Installing Your OSI/MHS Subsystem The Installation Menu SQL is required, so answer yes. The system verifies that SQL is running and then displays the following information and question. If you respond "yes" to the next question, some first time installation values will be selected and might change some of the values read from the installation file ().
PAGE 175
Installing Your OSI/MHS Subsystem The Installation Menu Example 4-4. Installation Menu 1) OSI/MHS ISV $system.zosimhs 2) OSI/MHS Subvolume $myvol.osimhs 3) OSI/MHS Manager Process Name 4) OSI/MHS Configuration Database $myvol.zmhsdb 5) OSI/MHS Routing File Name $myvol.zmhsdb.route 6) OSI/MHS MTA Association File Name $myvol.zmhsdb.assoc 7) OSI/MHS User File Name $myvol.zmhsdb.user 8) OSI/MHS Distribution List File Name $myvol.zmhsdb.dl 9) OSI/MHS Distribution List Member File Name $myvol.zmhsdb.
PAGE 176
Installing Your OSI/MHS Subsystem Description of the Installation in Progress items 8 and 25, enter those item numbers, separated by a comma, after the prompt. Press RETURN to continue. Please choose one or more items from the menu above to verify and optionally change. Please enter a number, a comma separated list of numbers, or one of the words "none" or "all": 8,25 The installation program displays the value for item 8 and asks you if it is correct.
PAGE 177
Installing Your OSI/MHS Subsystem Description of the Installation in Progress Items 1 through 14 The first 14 items on the installation menu have to do with copying ISVs and setting security. Screen displays describe each step as it is carried out. The following is a sample of the information given during the installation procedure. Begin: Purge of old files in OSI/MHS subvolume ($myvol.osimhs) End: Purge of old files in OSI/MHS subvolume ($myvol.
PAGE 178
Installing Your OSI/MHS Subsystem Description of the Installation in Progress If an error occurs, an error message is displayed and the installation stops. Check the output location for the complete FUP output. Note. The MR process has the object file name MTA, although some MTA functions are performed by the RTS and SC processes in the MR class. 17) Secure New Executable Object Files.
PAGE 179
Installing Your OSI/MHS Subsystem Description of the Installation in Progress 20) SQL Compile MS Program. In this step, SQL compiles the MS program into the MS SQL catalog (the same catalog specified by the keyword MS_SQL_DATABASE1). You should run this step during a first-time installation if you plan to configure a message store, and when you move to a new version of OSI/MHS. This step also compiles the SAVEMBOX and RESTMBOX utilities described in Appendix C, Mailbox Save and Restore Utilities.
PAGE 180
Installing Your OSI/MHS Subsystem Description of the Installation in Progress If an error occurs, an error message is displayed and the installation stops. Check the output location for the complete FUP output. 22) Create MS Databases. This step creates the MS SQL catalogs, tables, and indexes, in addition to the MS PDU stores. The SQL objects are secured as specified by the keyword SQL_TABLE_SECURITY. The MS PDU stores are secured as specified by the keyword OSIMHS_FILE_SECURITY.
PAGE 181
Installing Your OSI/MHS Subsystem Exiting From a Successful Installation the MS PDU stores. If your answer is no, installation ends. You must correct the file names in the installation file, then run the installation program again. MS PDU store(s) specified in the installation file $myvol.osimhs.install2: Data file --------#1 #2 #3 #4 Log file -------- $myvol.mh1msdb.pdums1 $myvol.mh1msdb.pdums2 $myvol.mh1msdb.pdums3 $myvol.mh1msdb.pdums4 $myvol.mh1msdb.logms1 $myvol.mh1msdb.logms2 $myvol.mh1msdb.
PAGE 182
Installing Your OSI/MHS Subsystem Upgrading From an Earlier RVU When you complete the OSI/MHS installation, all the required databases and a sample configuration file have been created. The next step is to configure your subsystem, as described in Section 5, Configuring Your OSI/MHS Subsystem, Upgrading From an Earlier RVU The following subsections address the possible upgrades you may be including as part of your installation procedure.
PAGE 183
Installing Your OSI/MHS Subsystem Upgrading from D20 or D21 to D22 or D41 Upgrading from D20 or D21 to D22 or D41 Running the OSI/MHS installation procedure for a D22 or D41 upgrade is very similar to running it for a new installation. The significant differences are as follows: • • • There is probably an installation file on your system (although if not, you can create one). You may want to choose different options in the installation file and installation menu.
PAGE 184
Installing Your OSI/MHS Subsystem Upgrading from RVU D22 to D41 To avoid a temporary loss of service, you can upgrade the OSI/MHS subsystem in two stages. The two-stage upgrade lets you use parts of OSI/MHS while the MS database is being converted. The MS D22 database formats for OSI/MHS D41 are not compatible with the D20 and D21 versions. If the databases cannot be converted to the D22 database format, you cannot restart the MS groups.
PAGE 185
Installing Your OSI/MHS Subsystem • Upgrading in One Stage SQL compiling the MS program. At this point the installation menu appears. Follow the instructions in “Installing OSI/MHS for the First Time” to complete the installation. If You Are Using MS Groups If you are using MS groups, these groups must be converted to the D22 or D41 format. Therefore, you must make sure that the MS Database Conversion option appears on the installation menu.
PAGE 186
Installing Your OSI/MHS Subsystem Upgrading in Two Stages Setting the Database Conversion Options on the Installation Menu. To place the Route Database Conversion and MS Database Conversion options on the installation menu interactively, run the installation procedure as described under Installing OSI/MHS for the First Time on page 4-11. Answer yes to the question: Are MS groups to be installed? [y] The following warning appears. Press RETURN to continue.
PAGE 187
Installing Your OSI/MHS Subsystem Upgrading in Two Stages OSI/MHS converts the MS database tables to the D22 or D41 format. While the conversion is taking place, you can start and use parts of your OSI/MHS subsystem. The simplest way to do a two-stage installation is by setting keyword values in the installation file. Stage 1 Open the installation file as described earlier in this section. Edit the file to reflect your OSI/MHS subsystem.
PAGE 188
Installing Your OSI/MHS Subsystem Upgrading in Two Stages The following warning appears. Warning: MS databases for OSI/MHS D22 version are incompatible with D20 or D21 versions, which must be converted. This is achieved by executing the MS Database Conversion step. Migration from C31 to D22 conversion is NOT supported Migration from D20 to D22 conversion is required. Migration from D21 to D22 conversion is required. MS Database Conversion step will not purge existing files unless directed to. Note.
PAGE 189
Installing Your OSI/MHS Subsystem Upgrading in Two Stages Example 4-5.
PAGE 190
Installing Your OSI/MHS Subsystem Returning to a Previous RVU After the MS SQL databases are converted, the following message appears. End: Conversion of MS Database(s) complete(s) Note. The MS database conversion creates a set of temporary work files in the MS SDL database. There is one temporary file for each file that is being converted (AUT, GEN, BCR, RRT, IPM). Each file name is preceded with an x (xAUT, xGEN, and so on).
PAGE 191
5 Configuring Your OSI/MHS Subsystem This section describes how to create SCF configuration files for a sample corporate user. The corporation is not real, but the configuration described is realistic. Three sample MTAs are defined. Each illustrates and highlights different features of an OSI/MHS subsystem.
PAGE 192
Configuring Your OSI/MHS Subsystem Overview of Corporate User Figure 5-1. Corporate Network of Three MTAs Country: US ADMD: TELENET PRMD: DEVICEIND MHS Message Store Transfer X400 Gateway MTA1 GPI Organization: SALES NEWYORK * Message Store MTA2 Organization: SHIPPING MTA3 Transfer X400 Gateway Organization: MANUFACTURING BOSTON* Packet Switch Network Legend *SALES and MANUFACTURING are the organization names for OSI/MHS on their respective systems.
PAGE 193
Configuring Your OSI/MHS Subsystem Message Flow name of the NonStop system on which the Transfer X400 gateway resides gets mapped to the X.400 organization name.) • • • • • • • • • Routing criteria are based on organization name. Routes are defined such that all message traffic between MTA1 and MTA3 is relayed through MTA2. A catchall route is defined for both MTA1 and MTA3 to forward all messages unknown within this network to MTA2.
PAGE 194
Configuring Your OSI/MHS Subsystem Message Flow Figure 5-2. OSI/MHS Message Flow Example Lo cal UA 1 1 Re mote UA 7 1 MHS Tran sfer Ap pl icatio n Messa ge Store 1 Tran sfer X40 0 Gateway Lo cal UA Re mote UA Messa ge Store 2 Tran sfer Ap pl icatio n 6 2 MTA1 MTA3 MTA2 7 6 Tran sfer X40 0 Gateway 2 GPI 4 5 3 5 1 Prop ri etary System Pa cket Switch Ne two rk VST 0 31.VS D The following text describes the steps shown in Figure 5-2: 1.
PAGE 195
Configuring Your OSI/MHS Subsystem Format of Configuration Descriptions 5. A similar process occurs at MTA2. MTA2 determines that the message needs to be relayed to MTA3. An association initiated by MTA2 is established to MTA3, and the message is relayed. 6. MTA3 checks the recipient name and determines that the message is for a local MS user specified by APPL object #TerryJones. The message is then delivered and stored in the mailbox for that local MS user.
PAGE 196
Configuring Your OSI/MHS Subsystem APPL (Gateway) Object ROUTE SUBSYS The order in which you will normally configure these object types is the following: SUBSYS CLASS GROUP PROCESS GATEWAY APPL DLIST DLISTMEMBER CUG CUGMEMBER MTA ROUTE You need to define these object types to the MHS manager process according to their positions in the object hierarchy. You must define your SUBSYS object before your CLASS objects and each CLASS object before the GROUP objects it contains.
PAGE 197
Configuring Your OSI/MHS Subsystem • APPL (MS) Object ORG-NAME (ORG)—specifies the name of the node where a Transfer gateway user resides. In this example, the node name for MTA1 is NEWYORK, and for MTA3, the node name is BOSTON. The node name for the general gateway user defined by MTA1 is FAX. APPL (MS) Object The message-store APPL object attributes used in these examples are: • • • ACCESS-TYPE (ACC-TYPE)—specifies the access type, which is MS for an APPL object in an MS group.
PAGE 198
Configuring Your OSI/MHS Subsystem • CUG Object MAX-MSG-LEN—specifies the maximum size of message that can be sent within this closed user group.
PAGE 199
Configuring Your OSI/MHS Subsystem CUGMEMBER Object CUGMEMBER Object The CUGMEMBER object attributes used in these examples are: • • • • ISO-COUNTRY-NAME—specifies the country name for this closed user group member. ADMD—specifies the administration domain name for this closed user group member. PRMD—specifies the private domain name for this closed user group member. ORG-NAME—specifies the organization name for this closed user group member.
PAGE 200
Configuring Your OSI/MHS Subsystem • • • GATEWAY Object ORG-UNIT-1—specifies the organizational unit name for this distribution list member. SUR-NAME—specifies the surname part of the personal name for this distribution list member. GIVEN-NAME—specifies the given-name part of the personal name set for this distribution list member. GATEWAY Object The GATEWAY object attributes used in these examples are: • • • • • VINTAGE—specifies gateway implementation, which is 84 for the Transfer X400 gateway.
PAGE 201
Configuring Your OSI/MHS Subsystem • GROUP Object (Local Operation) GI-PNAME (GI)—names the gateway interface process in the GI group. GROUP Object (Local Operation) The LO GROUP object attribute used in these examples is: • LO-PNAME (LO)—names the local operations process in the LO group. GROUP Object (Message Relay) The MR GROUP object attributes used in these examples are: • • • SC-PNAME (SC)—names the store cleaner process in the MR group.
PAGE 202
Configuring Your OSI/MHS Subsystem MTA (Adjacent MTA) Object MTA (Adjacent MTA) Object In the sample configuration, a password exchange is required when an association is established, so you must use the first three attributes listed below. The other attributes are optional. • • • • • REM-LOGON-VALIDATION (REM-LOGON)—must have a value of ON. REM-OUR-PASSW (OUR-PWD)—specifies the password of the source (sending) MTA.
PAGE 203
Configuring Your OSI/MHS Subsystem • • • SUBSYS (Subsystem) Object ADMD—specifies the name of the administration management domain for the final destination of this route. PRMD—specifies the name of the private management domain for the final destination of this route. ORG-NAME—specifies the organization name for the final destination of this route. Note. The ROUTE attributes listed above do not appear in the MTA configuration diagrams but are included in the MTA configuration files.
PAGE 204
Configuring Your OSI/MHS Subsystem • Configuring MTA2 MTA-NAME (MTANAME)—specifies the MTA name of this OSI/MHS subsystem. This is used by adjacent MTAs to identify this MTA. Configuring MTA2 MTA2 has three MR groups connected to the OSI/AS services by a common OSI address. This MTA operates as a network relay. Figure 5-3 shows the topology and major components of the MTA2 configuration. Figure 5-3. MTA2 Components MTA2 MR 1 MR 2 MR 3 X.25 OSI/AS OSI/TS X2 5AM MTA1 MTA3 VST 032.
PAGE 205
Configuring Your OSI/MHS Subsystem Objects and Attributes Figure 5-4.
PAGE 206
Configuring Your OSI/MHS Subsystem Installation and Configuration Files for MTA2 Figure 5-4. MTA2 Configuration Diagram (page 2 of 2) ROUTE To MTA1 ORG: SALES To MTA1 ORG: NEWYORK To MTA3 ORG: MANUFACTURING To MTA3 ORG: BOSTON PRIMARY1 PRIMARY2 BACKUP1 BACKUP2 ROUTE To MTA3 ORG: MANUFACTURING PRIMARY1 To MTA3 ORG: BOSTON To MTA1 ORG: SALES PRIMARY2 BACKUP1 To MTA1 ORG: NEWYORK BACKUP2 VST 33B.VSD This MTA operates as a relay. It includes no MS or RS groups.
PAGE 207
Configuring Your OSI/MHS Subsystem • Configuring MTA3 OSI/AS and OSI/TS configuration file. This file contains the OSI addresses for MTA2. It also defines the connections to network services, such as PAM (delivered with G06 and later RVUs), and X.25. Appendix A, Examples of Configuration Files, contains the SCF command file needed to configure OSI/AS and OSI/TS for MTA2. It also includes an overview of the OSI addresses for MTA2.
PAGE 208
Configuring Your OSI/MHS Subsystem • • • • • • • • • Objects and Attributes Two MR groups share an X.25 normal mode connection; two MR groups share a LAN connection. Two RS groups share one OSI address to receive association requests from remote UAs. This is a multigroup configuration. The RS groups share an X.25 normal mode connection. Four MS groups are defined, with mailboxes for users whose access is through the RS groups. Two adjacent MTAs are defined: MTA1 and MTA2 (there are no other MTAs).
PAGE 209
Configuring Your OSI/MHS Subsystem Objects and Attributes Figure 5-6.
PAGE 210
Configuring Your OSI/MHS Subsystem Objects and Attributes Figure 5-6.
PAGE 211
Configuring Your OSI/MHS Subsystem Installation and Configuration Files for MTA3 Installation and Configuration Files for MTA3 MTA3 requires the following files for installation and configuration: • • • An installation file. The installation file contains the keywords and keyword values needed to install and name the databases and other files for MTA3. After creating this file online, you execute it as explained in Section 4, Installing Your OSI/MHS Subsystem. An OSI/MHS configuration file.
PAGE 212
Configuring Your OSI/MHS Subsystem Configuring MTA1 Figure 5-7. MTA1 Components Transfer X400 Gateway Client Application General Use r Gateway P7 API MTA1 GI1 GI2 MS1 LO1 MS2 MR1 MR2 X.25 normal mode MS4 MS3 MR3 RS1 RS3 RS2 MR4 X.25 1980 mode LO2 LAN X.25 1980 mode RS4 LAN OSI/AS OSI/TS X25AM 1980 mode X25AM normal mode TLAM Potential link to MTA3 (not configured in example files) MTA2 MTA3 VST 036.VSD The major features of this configuration are: • • • • Two GI groups.
PAGE 213
Configuring Your OSI/MHS Subsystem • • • • • • • • • • • Configuring MTA1 Four RS groups that listen on two OSI addresses: an X.25 mode connection and a LAN connection. Three OSI addresses that can receive association requests from adjacent MTAs. Two adjacent MTAs: MTA2 and MTA3 (there are no other MTAs). Four routes defined to each adjacent MTA. Backup (alternate) routes. The primary routes that go to MTA2 (indicated by a solid line). The backup routes that go to MTA3 (indicated by a dashed line).
PAGE 214
Configuring Your OSI/MHS Subsystem Objects and Attributes Objects and Attributes Figure 5-8 shows the OSI/MHS objects and their attributes needed to configure MTA1. Figure 5-8.
PAGE 215
Configuring Your OSI/MHS Subsystem Objects and Attributes Figure 5-8. MTA1 Configuration Diagram (page 2 of 3) GI CLASS GROUP (GI) CPU PRI PDU-STORE PDU-LOG-FILE WORK-SV GI-PNAME GIGRP1 1,2 130 MHS1GI1,PDUGI1 MHS1GI1,LOGGI1 MHS1GI1 $MHS1.#GI1 GIGRP2 2,3 130 MHS1GI2,PDUGI2 MHS1GI2,LOGGI2 MHS1GI2 $MHS1.#GI2 LO CLASS GROUP (LO) CPU PRI PDU-STORE PDU-LOG-FILE WORK-SV GI-PNAME LOGRP1 1,2 130 MHS1LO1,PDULO1 MHS1LO1,LOGLO1 MHS1LO1 $MHS1.#LO1 LOGRP2 2,3 130 MHS1LO2,PDULO2 MHS1LO2,LOGLO2 MHS1LO2 $MHS2.
PAGE 216
Configuring Your OSI/MHS Subsystem Objects and Attributes Figure 5-8.
PAGE 217
Configuring Your OSI/MHS Subsystem Installation and Configuration File for MRA1 Installation and Configuration File for MRA1 MTA1 requires the following files for installation and configuration: • • • An installation file. The installation file contains the keywords and keyword values needed to install and name the databases and other files for MTA1. After creating this file online, you execute it as explained in Section 4, Installing Your OSI/MHS Subsystem. An OSI/MHS configuration file.
PAGE 218
Configuring Your OSI/MHS Subsystem OSI/MHS Configuration and Management Manual—424827-003 5- 28 Summary
PAGE 219
6 Starting, Stopping, and Updating Your OSI/MHS Subsystem After you have planned, installed, and configured your OSI/MHS subsystem, the next step is to start the subsystem. This section describes how to start, stop, and update your OSI/MHS subsystem.
PAGE 220
Starting, Stopping, and Updating Your OSI/MHS Subsystem Defining External Password Servers 4. If your subsystem includes gateways, define and start the entry managers and wait manager before starting the GI groups. The entry and wait managers are server processes that are used with gateway associations. Each of these steps is described in detail below. Defining External Password Servers You can write an external password server by using the OSI/MHS management programming commands.
PAGE 221
Starting, Stopping, and Updating Your OSI/MHS Subsystem Specifying MHS Manager Startup Commands Options for the RUN Command NAME Specifies the name of the MHS manager process. The name that you specify here must be the same as the value you supply to the MHSMGR_PNAME keyword in the installation file. You must run all MHS manager processes with this option. NOWAIT Causes TACL to return control to the user after starting the MHS manager process. OUT Defines the out file to be used as the log file.
PAGE 222
Starting, Stopping, and Updating Your OSI/MHS Subsystem Specifying MHS Manager Startup Commands Note. The home terminal is routinely opened by several processes, but there is a system-level constraint on the number of opens of the home terminal. If that number is exceeded, confusing errors or a drastic performance degradation will result. To avoid this condition, declare a spool file or a device other than the home terminal as the destination for messages from the various processes.
PAGE 223
Starting, Stopping, and Updating Your OSI/MHS Subsystem Specifying MHS Manager Startup Commands the traffic on the primary collector ($0) will likely be higher than is desirable if all the accounting events are going to it. PROCESSES Argument: maximum number of child processes supported Default: 100 Sets the maximum number of processes the MHSMGR can run. The value must be less than 400. If you specify a value of 400 or greater, the MHS manager fails at startup time.
PAGE 224
Starting, Stopping, and Updating Your OSI/MHS Subsystem Defining All Objects to the MHS Manager Process Examples of Starting the MHS Manager Process The following examples demonstrate two methods of setting MHS manager startup parameters: one as PARAM command parameters, the other as RUN command line options. You can start the MHS manager process by using PARAM command parameters, as follows: CLEAR ALL PARAM CONFIG-DB-SVOL $myvol.
PAGE 225
Starting, Stopping, and Updating Your OSI/MHS Subsystem Starting the OSI/MHS Subsystem Objects Management Environment for OSI/MHS, Appendix A, Examples of Configuration Files, and the OSI/MHS SCF Reference Manual. Although the installation procedure creates an input file for SCF, this file does not include all of the attributes that you need to define. The installation procedure does not have enough information to determine some of the values, such as OSI addresses.
PAGE 226
Starting, Stopping, and Updating Your OSI/MHS Subsystem Combining the Steps Combining the Steps You can combine the previous steps in one command file. The following example shows the orderly startup of an OSI/MHS subsystem using a command file. CONFIRM ON ALLOW ALL == start an alternate collector EMSACOLL/name $ALT,NOWAIT,CPU 1/BACKUP 0 == start the MHSMGR process CLEAR ALL PARAM CONFIG-DB-SVOL $DATA4.T3CDB PARAM COLLECTOR $0 PARAM COLLECTOR-1 $AC01 PARAM BACKUPCPU 3 PARAM SWAPVOL $DATA1 RUN $MYVOL.
PAGE 227
Starting, Stopping, and Updating Your OSI/MHS Subsystem • • Defining and Starting the Entry and Wait Managers One log file One queue file Together, the entry and wait managers and their associated files are referred to as the queue manager. The queue manager is associated with the OSI/MHS subsystem but is not part of the subsystem. Figure 6-1 illustrates the relationship of the queue manager to an OSI/MHS subsystem. • • • The queue file serves the MRP and the GPI.
PAGE 228
Starting, Stopping, and Updating Your OSI/MHS Subsystem Defining and Starting the Entry and Wait Managers You can use management programming commands to write the entry and wait manager processes, and then use TACL commands to define and start the processes. As an alternative, you can write and compile the processes by using TAL, C, or another supported language. You can then define the processes as Pathway servers and run them under Pathcom. Note.
PAGE 229
Starting, Stopping, and Updating Your OSI/MHS Subsystem set set set set server server server server out autorestart program process Defining and Starting the Entry and Wait Managers $S.#EMSERV.OUTF 3 $volX.QMGR.
PAGE 230
Starting, Stopping, and Updating Your OSI/MHS Subsystem Stopping the Subsystem Stopping the Subsystem To shut down the subsystem in an orderly manner, you stop the objects in the reverse order that you started them. This means that you must stop the GROUP objects first, then the CLASS objects, then the SUBSYS object. The APPL object is not in this list because it does not need to be stopped before stopping the subsystem. The MHS manager reports events as the objects are stopped.
PAGE 231
Starting, Stopping, and Updating Your OSI/MHS Subsystem Restarting the Subsystem 5. STATUS CLASS with the DETAIL option shows you the state of each group. 6. STOP MON stops the MHS manager. 7. EXIT takes you out of SCF. Restarting the Subsystem To restart the OSI/MHS subsystem, you first run the MHS manager and then start the objects. You do not need to define the objects because they already exist.
PAGE 232
Starting, Stopping, and Updating Your OSI/MHS Subsystem Summary You run the installation procedures as described in Section 4, Installing Your OSI/MHS Subsystem. The installation procedures compare the objects, check to see which objects have changed, and update those objects. Depending on your configuration, you might need to redefine objects or take other steps to complete the upgrade. See Upgrading From an Earlier RVU on page 4-22 for more information.
PAGE 233
7 Managing Your OSI/MHS Subsystem Managing your OSI/MHS subsystem to keep it running smoothly involves several types of tasks, covered in this section: • • Modifying the subsystem configuration • • • • • Group databases (PDU store and SQL databases) Objects that represent the executable portion of the subsystem (CLASS, GROUP, and PROCESS) Objects that represent the information flow through the subsystem (APPL, MTA, and ROUTE) Objects that represent the grouping of users within the subsystem (DLIST, DL
PAGE 234
Managing Your OSI/MHS Subsystem Using SCF Commands Interactively online, that change is not automatically made to the configuration file. You must edit the configuration file to reflect the configuration changes you make online. Likewise, when you change the configuration file, that change does not reflect the current system until you invoke that configuration file. This subsection describes these two methods of reconfiguring the system.
PAGE 235
Managing Your OSI/MHS Subsystem Group Databases Group Databases Each GI, LO, MR, MS, and RS group has a PDU store database associated with it. The MS group has an additional database associated with it: the SQL database. The SQL database has its own catalog, table, and indexes. For a full discussion of managing SQL databases, see the NonStop SQL Installation and Management Manual. An association exists between the message store PDU store database and the SQL database.
PAGE 236
Managing Your OSI/MHS Subsystem Managing Groups NAMES Command For a display of the names of all the objects in the subsystem, use the NAMES command.
PAGE 237
Managing Your OSI/MHS Subsystem Managing Groups This command displays the following screen. -> names $mhs1 MHS Names MON \NEWYORK.* MON $MHS1 SUBSYS MHS1 APPL JAMESJOHN TRANSFERGATEWAY JOHNSONJANET GENERALGATEWAY SMITHHARRY SMYTHELYNDA CLASS MR GROUP MR.\NEWYORK.MRGRP1 PROCESS \NEWYORK.$R11 \NEWYORK.$M11 \NEWYORK.$S11 GROUP MR.\NEWYORK.MRGRP2 PROCESS \NEWYORK.$R12 \NEWYORK.$M12 \NEWYORK.$S12 GROUP MR.\NEWYORK.MRGRP3 PROCESS \NEWYORK.$R13 \NEWYORK.$M13 \NEWYORK.$S13 GROUP MR.\NEWYORK.
PAGE 238
Managing Your OSI/MHS Subsystem Managing Groups PROCESS \NEWYORK.$I14 CLASS RS GROUP RS.\NEWYORK.RSGRP1 PROCESS \NEWYORK.$V11 GROUP RS.\NEWYORK.RSGRP2 PROCESS \NEWYORK.$V12 GROUP RS.\NEWYORK.RSGRP3 PROCESS \NEWYORK.$V13 GROUP RS.\NEWYORK.RSGRP4 PROCESS \NEWYORK.$V14 CLASS GI GROUP GI.\NEWYORK.GIGRP1 PROCESS \NEWYORK.$G11 GROUP GI.\NEWYORK.GIGRP2 PROCESS \NEWYORK.$G12 CLASS LO GROUP LO.\NEWYORK.LOGRP1 PROCESS \NEWYORK.$L11 GROUP LO.\NEWYORK.LOGRP2 PROCESS \NEWYORK.$L12 MTA MTA2 ROUTE MTA2.PRIMARY1 MTA2.
PAGE 239
Managing Your OSI/MHS Subsystem Managing Groups MTA MTA3 ROUTE MTA3.BACKUP1 MTA3.BACKUP2 GATEWAY TRANSFER GENERALGATEWAY ENTRY DEFERRED LINKRETRY MTA3.BACKUP3 MTA3.BACKUP4 ROUTERETRY DLIST SALES DLISTMEMBER JAMESJOHN SMITHHARRY JOHNSONJANET SMITHLYNDA DLIST MANUFACTURING DLISTMEMBER CHAPMANGRAHAM CLEESEJOHN GILLIAMTERRY JONESTERRY CUG DEVICEINDUSERSONLY CUGMEMBER SALES MANUFACTURING SHIPPING This display shows all of the objects for MTA1.
PAGE 240
Managing Your OSI/MHS Subsystem Managing Groups This command displays a simple summary of all the classes in the $MHS1 subsystem. -> status class $mhs1.*, detail MHS Detailed status CLASS GI State............. STARTED Groups-started.... 1 Groups-stopped.... 1 Groups-recov...... 0 Groups-starting... 0 Groups-stopping... 0 Groups-defined.... 2 MHS Detailed status CLASS LO State............. STARTED Groups-started.... 2 Groups-stopped.... 0 Groups-recov...... 0 Groups-starting... 0 Groups-stopping...
PAGE 241
Managing Your OSI/MHS Subsystem Managing Groups This command displays information about all the MR groups in $MHS1. -> status group $mhs1.#mr.*, detail MHS Detailed status GROUP MR.\NEWYORK.MRGRP1 State............. STARTED MHS Detailed status GROUP MR.\NEWYORK.MRGRP2 State............. STARTED MHS Detailed status GROUP MR.\NEWYORK.MRGRP3 State............. STARTED MHS Detailed status GROUP MR.\NEWYORK.MRGRP4 State.............
PAGE 242
Managing Your OSI/MHS Subsystem Managing Groups This command displays detailed information about all the MR groups in $MHS1. -> status group $mhs1.#mr.*,detail, sub all MHS Detailed status GROUP MR.\NEWYORK.MRGRP1 State............. STARTED MHS Detailed status PROCESS RTS \NEWYORK.$R11 GENERAL: CPU............... 0 Start-time........ 16 Dec 1994, 6:52:20.326 Fail-time......... 10 Dec 1994, 0:25:09.437 RTS-SPECIFIC: Inc-assocs........ 0 Out-assocs........ 0 MHS Detailed status PROCESS MRP \NEWYORK.
PAGE 243
Managing Your OSI/MHS Subsystem APPL-QUEUE: APPL-Name......... JAMESJOHN Managing Groups APPL-msg-count.... 0 MHS Detailed status GROUP MR.\NEWYORK.MRGRP3 State............. STARTED MHS Detailed status PROCESS RTS \NEWYORK.$R13 GENERAL: CPU............... 2 Start-time........ 16 Dec 1994, 6:52:05.371 Fail-time......... 00 ??? 0000, 0:00:00.0 RTS-SPECIFIC: Inc-assocs........ 0 Out-assocs........ 0 MHS Detailed status PROCESS MRP \NEWYORK.$M13 GENERAL: CPU............... Start-time........ Fail-time......
PAGE 244
Managing Your OSI/MHS Subsystem Managing Groups This screen displays information about the processes in the MR group. -> status group $mhs1.#mr.mrgrp1,detail,sub all MHS Detailed status GROUP MR.\NEWYORK.MRGRP1 State............. STARTED MHS Detailed status PROCESS RTS \NEWYORK.$R11 GENERAL: CPU............... 0 Start-time........ 16 Dec 1994, 6:52:20.326 Fail-time......... 10 Dec 1994, 0:25:09.437 RTS-SPECIFIC: Inc-assocs........ 0 Out-assocs........ 0 MHS Detailed status PROCESS MRP \NEWYORK.
PAGE 245
Managing Your OSI/MHS Subsystem Verifying the APPL, MTA, and ROUTE Objects This shows that RSGRP1, RSGRP3, and RSGRP4 are in the STARTED state. To see if there are any RS groups in the STOPPED state, enter: STATUS GROUP $MHS1.#RS.*, SUB ALL, SEL STOPPED If there are any RS groups in the STOPPED state, a display similar to the following appears. -> status group $mhs1.#rs.*, sub all, sel stopped MHS Detailed status GROUP RS.\COMM2.RSGRP2 State.............
PAGE 246
Managing Your OSI/MHS Subsystem Verifying the APPL, MTA, and ROUTE Objects This command displays the status of all the APPL objects in the subsystem. -> status appl $mhs1.
PAGE 247
Managing Your OSI/MHS Subsystem Verifying the APPL, MTA, and ROUTE Objects The INFO MTA command displays the following screen. -> info mta $mhs1.* MHS info MTA MTA MTA2 MHS info MTA Country-code MTA-name US MTA2 MTA MTA3 Country-code MTA-name US MTA3 The INFO MTA command shows all the MTA objects defined for a subsystem. The NAMES MTA command shows all the MTA and ROUTE objects defined for a subsystem, as displayed on the following screen. -> names mta $mhs1.* MHS Names MTA \NEWYORK.
PAGE 248
Managing Your OSI/MHS Subsystem Verifying the APPL, MTA, and ROUTE Objects Notice that you cannot use this command to display details about your subsystem: you use the INFO MTA command only for adjacent MTAs. -> info mta $mhs1.#mta2, detail MHS Detailed info MTA MTA2 *Logon-validation. ON *Applicn-context.. MTS-TRANSFER *Dialogue-mode.... MONOLOGUE *Max-msg-length... 2097152 *Local-init....... ON *Remote-init...... ON *Rem-P-SELECTOR-1. *Rem-S-SELECTOR-1. *Rem-T-SELECTOR-1. 4D5258323541 *Rem-NSAP-1.......
PAGE 249
Managing Your OSI/MHS Subsystem Verifying the APPL, MTA, and ROUTE Objects -> info mta $mhs1.#mta1, detail MHS E-00017 Object MTA1 Not Found INFO ROUTE Command To see the ROUTE objects defined for a subsystem, enter: INFO ROUTE $MHS1.*.* This command displays all of the ROUTE objects defined for MHS1. -> info route $mhs1.*.* MHS info ROUTE Route MTA2.PRIMARY1 MHS info ROUTE Priority 1 Route MTA2.PRIMARY2 MHS info ROUTE Priority 1 Route MTA2.PRIMARY3 MHS info ROUTE Priority 1 Route MTA2.
PAGE 250
Managing Your OSI/MHS Subsystem Verifying the DLIST, DLISTMEMBER, CUG, and CUGMEMBER Objects This command shows all the attributes defined for PRIMARY1 in MTA2. -> info route $mhs1.#mta2.primary1,detail MHS Detailed info ROUTE MTA2.PRIMARY1 *Priority......... *ISO-Country-name. *ADMD............. *PRMD............. *X121-Address..... *Terminal-ID...... *Numeric-user-ID.. *Common-name...... *Terminal-type.... *Org-Name......... *Org-Unit-1....... *Org-Unit-2....... *Org-Unit-3....... *Org-Unit-4.......
PAGE 251
Managing Your OSI/MHS Subsystem Verifying the DLIST, DLISTMEMBER, CUG, and CUGMEMBER Objects The DLIST and DLISTMEMBER objects do not have states associated with them; therefore, you cannot execute a STATUS command on these objects. You could enter an INFO command or a NAMES command, as follows: INFO DLIST $SALES.* NAMES DLIST $SALES.* The INFO DLIST command displays the following screen. -> info dlist $mhs1.
PAGE 252
Managing Your OSI/MHS Subsystem Maintaining the Interfaces to OSI/AS The INFO CUG command displays the following screen. -> info cug $mhs1.* MHS info CUG CUG DEVICEINDUSERSONLY Number-of-members 3 The INFO CUG command shows all the CUG objects defined for a subsystem. The NAMES CUG command shows all the CUG and CUGMEMBER objects defined for a subsystem, as displayed on the following screen. -> names cug $mhs1.* MHS Names CUG \NEWYORK.
PAGE 253
Managing Your OSI/MHS Subsystem Verifying OSI Addresses in MR and RS Groups This command displays detailed information about the SUBSYS object. -> info subsys $mhs1.#mhs1,detail MHS Detailed info SUBSYS MHS1 GENERAL SETTING: *Routing-fname.... *User-fname....... *MTA-assoc-fname.. *OSI-Mgr.......... ISO Country-name. ADMD-name........ PRMD-name........ MTA-name......... MTA-designator... \NEWYORK.$POSTD.MHS1.ROUTE \NEWYORK.$POSTD.MHS1.USER \NEWYORK.$POSTD.MHS1.ASSOC \NEWYORK.
PAGE 254
Managing Your OSI/MHS Subsystem Verifying OSI Addresses in MR and RS Groups This command displays detailed information about MRGRP1. -> info group $mhs1.#mr.mrgrp1,detail MHS Detailed info GROUP MR.\NEWYORK.MRGRP1 GENERAL: *CPU.............. 0 *Backup-CPU....... 1 *Priority......... 130 *PDU-Store........ \NEWYORK.$POSTD.MHS1MR1.PDUMR1 *PDU-Log-file..... \NEWYORK.$POSTD.MHS1MR1.LOGMR1 *Work-SV.......... \NEWYORK.$POSTD.MHS1MR1 MR-SPECIFIC: *RTS-Process-name. *RTS-CPU.......... *RTS-Backup-CPU...
PAGE 255
Managing Your OSI/MHS Subsystem Verifying OSI Addresses in MR and RS Groups This command displays information about TSEL 4d5258323541. -> info entry $uosi.#tsel.4d5258323541,detail OSIAS Detailed Info ENTRY \NEWYORK.$UOSI.#TSEL.4D5258323541 *Server............ \NEWYORK.$UOSI.#TAPS.UAS1 The server associated with this address is UAS1. INFO PROCESS Command To examine the UAS1 process more closely, enter: INFO PROCESS $UOSI.#TAPS.UAS1, DETAIL This command displays the following screen.
PAGE 256
Managing Your OSI/MHS Subsystem Verifying OSI Addresses in MR and RS Groups LISTOPENS PROCESS Command To see which processes have the UAS1 process open, enter: LISTOPENS PROCESS $UAS1 This command displays a screen similar to the following. -> listopens process $uas1 OSIAS Listopens PROCESS \NEWYORK.$UAS1 Openers \NEWYORK.$R14 \NEWYORK.$V11 \NEWYORK.$V13 \NEWYORK.$V14 \NEWYORK.$R11 \NEWYORK.$R13 \NEWYORK.$ZNET \NEWYORK.$R12 \NEWYORK.
PAGE 257
Managing Your OSI/MHS Subsystem Verifying OSI Addresses in MR and RS Groups This command displays a screen similar to the following. -> status su $uas1.#z0000dj,detail OSIAS Detailed Status SU \NEWYORK.$UAS1.#Z0000DJ State............... STARTED Opens............... 1 L4 SU............... \NEWYORK.$UTS1.#Z0000DJ Last Error.......... 0 Last Error Subcode.. 0 Last Error Source... L5 Protocol Version. 1 L5 Protocol State... STA01 Idle, no transport connection Disconnect Timeout.. Expedited...........
PAGE 258
Managing Your OSI/MHS Subsystem Verifying OSI Addresses in MTA Objects P-Sel............. S-Sel............. T-Sel............. 4D52 5832 3542 NSAP.............. 7032 8500 3012 Responding Address: (LOCAL) Application-Name.. AE-Title: AE-Title format. 0 AE-Qual......... AP-Title........ P-Sel............. S-Sel............. T-Sel............. NSAP.............. This shows the state of the UAS1 Z0000DJ connection. The RTS process in the MR group is waiting for an incoming association.
PAGE 259
Managing Your OSI/MHS Subsystem Monitoring EMS Events INFO MTA Command For information about a specific MTA, enter: INFO MTA $MHS1.#MTA2,DETAIL This command displays detailed information about MTA2. -> info mta $mhs1.#mta2, detail MHS Detailed info MTA MTA2 *Logon-validation. ON *Applicn-context.. MTS-TRANSFER *Dialogue-mode.... MONOLOGUE *Max-msg-length... 2097152 *Local-init....... ON *Remote-init...... ON *Rem-P-SELECTOR-1. *Rem-S-SELECTOR-1. *Rem-T-SELECTOR-1. 4D5258323541 *Rem-NSAP-1.......
PAGE 260
Managing Your OSI/MHS Subsystem Displaying Current Event Messages Section 9, Troubleshooting Your OSI/MHS Subsystem, includes a discussion of how to use event messages in troubleshooting and message tracking. You can use SCF or a management application to enable or suppress the reporting of certain types of event messages.
PAGE 261
Managing Your OSI/MHS Subsystem Displaying Saved Event Messages This command example runs a printing distributor to a terminal called $TERM1. The source of the event messages is the collector $0 (the collector on your local system), and the filter is the default filter, which accepts all event messages. The distributor $DIST1 displays messages for all events reported from the time you start the distributor until you stop it. This is an online printing distributor.
PAGE 262
Managing Your OSI/MHS Subsystem Using the EMS Analyzer The following source file (mhssrc) filters event messages for all events generated by the OSI/MHS subsystem: [#SET ZMHS^VAL^SSID [ZSPI^VAL^TANDEM].[ZSPI^SSN^ZMHS].0] FILTER select^only^OSI^MHS; BEGIN IF ZSPI^TKN^SSID = SSID (ZMHS^VAL^SSID) THEN PASS; END To compile the filter source code, enter the following commands: #PUSH myvar #LOAD /KEEP 1, LOADED myvar / & $system.zspidef.zspitacl #LOAD /KEEP 1, LOADED myvar / & $system.zspidef.
PAGE 263
Managing Your OSI/MHS Subsystem Using the EMS Analyzer Once the macro has finished running, you can start EMSA at any time. When you start EMSA, it checks your default subvolume for the EMSACSTM file and loads any commands that have been defined in that file. Setting up EMSA Filters In a typical OSI/MHS installation, network operators need to be able to switch quickly between various filters to display EMS messages in a particular context.
PAGE 264
Managing Your OSI/MHS Subsystem Using the EMS Analyzer [zspi^val^tandem].[zspi^ssn^zmhs].[zmhs^val^version] ] [#set zcmk^val^ssid [zspi^val^tandem].[zspi^ssn^zcmk].[zcmk^val^version] ] [#set zcom^val^ssid [zspi^val^tandem].[zspi^ssn^zcom].[zcom^val^version] ] [#set zems^val^ssid [zspi^val^tandem].[zspi^ssn^zems].[zems^val^version] ] [#set zspi^val^ssid [zspi^val^tandem].[zspi^ssn^zspi].
PAGE 265
Managing Your OSI/MHS Subsystem Using the EMS Analyzer Compiling EMSA Filters After creating the source filters, you compile them and place them in a location where they can be read by the EMSACSTM file at runtime. The following is an example of an obey file that loads the EMS Filter Compiler and then compiles the three filter sources, to create three filter object files. These files will be stored in the ZEMSA subvolume for common reference. (Remember that these are just examples.
PAGE 266
Managing Your OSI/MHS Subsystem Using the EMS Analyzer Comment F4 - selects all events except mhs. ALIAS F4 Alter,emslog $0,filter $system.zemsa.filtallo ALIAS today alter,starttime today ALIAS now alter,starttime now ALIAS bof alter,starttime bof start distributor , cpu 3, pri 100 alter, emslog $0 alter, starttime today alter, stoptime eof Comment - Alias command lists all the current Aliases to screen.
PAGE 267
Managing Your OSI/MHS Subsystem Using the EMS Analyzer When you run EMSA (by typing EMSA at the TACL prompt), it immediately loads the EMSACSTM file. The custom file just defined: 1. Starts an EMS distributor in CPU 3 and designates $0 as the source of the event log. (See the START DISTRIBUTOR command and the ALTER, EMSLOG command that follows it, near the end of the custom file.
PAGE 268
Managing Your OSI/MHS Subsystem Summary Summary Managing your OSI/MHS subsystem is an ongoing task. You need to: • • • • • • Maintain your configuration file and your current configuration so they are always the same. Make regular backups of your databases and follow the TMF procedures. Back up the message-store PDU and SQL databases at the same time to keep the backups consistent. Monitor the objects to determine the status of the subsystem.
PAGE 269
8 Sizing and Tuning Your OSI/MHS Subsystem This section describes performance tuning for the OSI/MHS subsystem.
PAGE 270
Sizing and Tuning Your OSI/MHS Subsystem Performance Tuning Steps Large Numbers of Retries The link and route-retry mechanisms of OSI/MHS ensure that OSI/MHS will retry connections on different addresses and through different adjacent MTAs if you set up your configuration accordingly.
PAGE 271
Sizing and Tuning Your OSI/MHS Subsystem Locations and Relationships of Message Handling Components implications of each network and application characteristic, in terms of sizing or performance, vary among successive versions of OSI/MHS. Your specialist will be better able to help you plan and tune your system if you can provide information of the types discussed here.
PAGE 272
Sizing and Tuning Your OSI/MHS Subsystem • Number and Distribution of Users The MTA attribute REM-MSG-OVERHEAD specifies how long it takes a specific adjacent MTA to process the transmission, not including the time it takes to transfer the message on the line.
PAGE 273
Sizing and Tuning Your OSI/MHS Subsystem Average and Maximum Message Size periods and the delivery requirements for those messages (for example, the proportions of urgent, normal, and nonurgent priority messages). Average and Maximum Message Size Sizing and throughput are affected by the average and maximum message size. The types of body parts and attachments also affect how messages are processed and therefore what overhead is associated with each message.
PAGE 274
Sizing and Tuning Your OSI/MHS Subsystem Using Parallelism in OSI/MHS MS Groups You can use parallel processing to optimize performance of your message store in either or both of the following ways: • • Define multiple MS groups and distribute the MS APPLs across them. This configuration typically provides better performance than having one MS process serve all message-store users. Associate multiple MR groups with the same MS group, using the MS group attribute MR-COUNT.
PAGE 275
Sizing and Tuning Your OSI/MHS Subsystem Configuring Supporting Software the same MTA; in this case, by listing the links in a different order in each MTA object definition, you can use multiple links to an adjacent MTA simultaneously. Note. SCF reports an error if you give any two links exactly the same set of addresses. To avoid this error in a configuration in which multiple MTA objects point to the same MTA, assign a different PSEL to each of the matching links.
PAGE 276
Sizing and Tuning Your OSI/MHS Subsystem Configuring Supporting Software You can also use X.25 hunt groups—multiple X.25 lines with the same DTE address— to distribute incoming or outgoing traffic across multiple lines. X25AM does not support this feature. To use it, you must obtain the lines from your network supplier and associate each with a different X25AM process. An MR group can service only one X.25 line.
PAGE 277
Sizing and Tuning Your OSI/MHS Subsystem Selecting and Allocating Physical Resources Event Management Service (EMS) Appropriate sizing for the Event Management Service depends on the size of the system as a whole and the number of applications having different filter requirements. The major issue specific to OSI/MHS is that enabling accounting events greatly increases the number of event messages OSI/MHS produces.
PAGE 278
Sizing and Tuning Your OSI/MHS Subsystem OSI/MHS Capacity Limitations Disk and Disk Cache The disk storage requirement for OSI/MHS varies from several hundred megabytes for a very small configuration to many thousands of megabytes for a very large configuration. Your HP analyst can help you determine the amount of disk space required. (As much as 30% of the disk space required is for TMF audit trails.
PAGE 279
Sizing and Tuning Your OSI/MHS Subsystem Optimizing Routing Table 8-1.
PAGE 280
Sizing and Tuning Your OSI/MHS Subsystem • Defining APPL Objects Give the following attributes values appropriate to the throughput characteristics of the adjacent MTA and the connection to that MTA: ASSOC-OPEN-TIME LINK-RETRY-TIME ROUTE-RETRY-TIME REM-MSG-THRUPUT REM-MSG-OVERHEAD MAX-MSG-TRANSFER-TIME Note that route-retry times can vary for normal, urgent, and nonurgent messages and for reports.
PAGE 281
Sizing and Tuning Your OSI/MHS Subsystem Tuning OSI/MHS Attributes Tuning OSI/MHS Attributes The default values of OSI/MHS attributes normally provide satisfactory performance for a medium-sized configuration. It is best not to modify values from their defaults unless you recognize a problem and understand the implications of a change you are about to make. GI Class Attributes For best performance results, use the defaults for the GI class attributes.
PAGE 282
Sizing and Tuning Your OSI/MHS Subsystem MR Group Attributes major sync occurs. The checkpoint size multiplied by the window size multiplied by 1K equals the amount of recovered data in retry transmission after a connection interruption. The WINDOW-SIZE and CHECKPOINT-SIZE attributes affect the amount of memory demand by an RTS process. For example, if the window size is 30 and the checkpoint size is 30, the maximum amount of memory required for a series of requests to OSI/AS is 30 x 30 x 1K (900K).
PAGE 283
Sizing and Tuning Your OSI/MHS Subsystem RS Class Attributes reorganizing the message store and mailboxes. Adding MS groups and distributing mailboxes across them can alleviate bottlenecks. For descriptions of the MS class attributes, see the OSI/MHS SCF Reference Manual. RS Class Attributes For best performance results, use the defaults for the RS class attributes. For descriptions of the RS class attributes, see the OSI/MHS SCF Reference Manual.
PAGE 284
Sizing and Tuning Your OSI/MHS Subsystem Access Methods Access Methods OSI uses X25AM and PAM to access other systems. Configuration of attributes such as frame size within X25AM can affect the speed of data transfer or delivery of messages to adjacent MTAs. For more information on performance tuning for X25AM and TLAM, see the X.25 Access Method (X25AM) Manual and the TLAM Configuration and Management Manual.
PAGE 285
Sizing and Tuning Your OSI/MHS Subsystem Peripheral Utility Program (PUP) Peripheral Utility Program (PUP) Use the PUP LISTCACHE command to monitor disk cache usage. If the proportion of cache hits is too low (less than 96-97 percent), dedicate more memory to the cache. Subsystem Control Facility (SCF) Use SCF to monitor the following aspects of OSI/MHS: • • • Link and route-retry queues: STATUS ENTRY command.
PAGE 286
Sizing and Tuning Your OSI/MHS Subsystem TMFCOM TMFCOM Use TMFCOM to monitor TMF transactions related to OSI/MHS processes and GPI applications. If many TMF aborts are associated with GPI applications, it is possible that there are too many applications for the level of incoming traffic. Handling Large Messages Adjust an existing configuration as follows to accommodate larger messages: • • • • • Decrease the number of object trees created for each GPI application (because the object trees are larger).
PAGE 287
9 Troubleshooting Your OSI/MHS Subsystem This section describes troubleshooting for the OSI/MHS subsystem.
PAGE 288
Troubleshooting Your OSI/MHS Subsystem Interconnection Problems With Other MTAs Configuration errors are of two major types: • • Local errors, such as OSI/MHS-to-OSI/AS address mismatches. This type of error involves MTA and MR group objects in OSI/MHS and ENTRY and PROCESS objects in OSI/AS. Interoperability or connection-oriented errors, such as incorrect passwords, invalid protocols, or incorrect MTA names.
PAGE 289
Troubleshooting Your OSI/MHS Subsystem Interconnection Problems With Other MTAs the message selects the highest priority route first. After the message has been routed, it is placed on a queue until the MR class attributes dictate that it is time to send the message • • The URGENT-COUNT and NON-URGENT-COUNT attributes specify how long the queue can become—how many messages can be on the queue—before OSI/MHS must attempt to send the message.
PAGE 290
Troubleshooting Your OSI/MHS Subsystem Interconnection Problems With Other MTAs route if one exists.) If a link is already open and is not being used, the MR process uses the open link rather than opening a new one. In addition to the addresses, the MTA passes the REM-DIALOGUE-MODE (which always has the value 0, for MONOLOGUE), the MTA-NAME defined for the SUBSYS object, and a password if the MTA attribute REM-LOGON-VALIDATION has a value of ON.
PAGE 291
Troubleshooting Your OSI/MHS Subsystem Interconnection Problems With Other MTAs checkpoint and window sizes. When it responds to MTA 1, the RTS process returns, as the values of checkpoint and window size, either its own preferred values or those of MTA 1, whichever are lower. The RTS process also checks the abstract syntax ID to ensure that the abstract syntax can be supported. After checking these parameters, the RTS process passes the bind request to the MR process. 7.
PAGE 292
Troubleshooting Your OSI/MHS Subsystem Interconnection Problems With Other MTAs report, OSI/MHS does not send a notification because such behavior would be contrary to the X.400 recommendations. Instead, it produces an unroutable report event message, as described in Unroutable Messages and Nondelivery Reports on page 9-25.) Table 9-1 and Table 9-2 summarize the OSI/MHS attributes used in association establishment and indicates relationships among the attributes.
PAGE 293
Troubleshooting Your OSI/MHS Subsystem Interconnection Problems With Other MTAs Table 9-1. Attributes Used by the Initiator in Association Establishment (page 2 of 2) Attribute Name Object Notes REM-P-SELECTOR-n MTA Value must match a value of MR-PSELECTOR on responder side. REM-S-SELECTOR-n MTA Value must match a value of MR-SSELECTOR on responder side. REM-T-SELECTOR-n MTA Value must match a value of MR-TSELECTOR on responder side. Must also match local OSI/AS ENTRY #TSEL.
PAGE 294
Troubleshooting Your OSI/MHS Subsystem Symptoms of Interconnection Problems Table 9-2. Attributes Used by the Responder in Association Establishment (page 2 of 2) Attribute Name Object Notes REM-T-SELECTOR-n MTA Responder must have value to match LOC-TSELECTOR on initiator side. REM-NSAP-n MTA Responder must have value to match LOCNSAP on initiator side. Special considerations apply to X.25 1980. CHECKPOINT-SIZE MR class Negotiated down between the two sides.
PAGE 295
Troubleshooting Your OSI/MHS Subsystem Symptoms of Interconnection Problems This event message is produced only if it was enabled (using SCF). Here are some examples of event message 35: 94-12-02 12:20:46 \CS7.$RK12 TANDEM.MHS.D20 000035 RTS Incoming Association Rejected; id(0); Reason: Unknown calling Session Address; Remote: NSAP=51 TSEL=51 SSEL=4B5353454C3141 PSEL= Local: NSAP=52 TSEL=52 SSEL=4B5353454C3241 PSEL= 94-12-02 12:20:46 \CS7.$RK11 TANDEM.MHS.
PAGE 296
Troubleshooting Your OSI/MHS Subsystem Problem Examples OSI/MHS is the initiator of an association. For example, the above display indicates 190 unsuccessful attempts by OSI/MHS to initiate an association. The counters are described in detail in the OSI/MHS SCF Reference Manual. RTS Process Abend Problem OSI/MHS RTS processes can abend under certain conditions when attempting to communicate with OSI/MHS MTA processes. These conditions are as follows: 1.
PAGE 297
Troubleshooting Your OSI/MHS Subsystem Problem Examples Figure 9-2 and Figure 9-3 illustrate the two MTAs. Figure 9-2 shows MTA1. Figure 9-2. MTA1 Components Transfer X400 Gateway Client Application General Use r Gateway P7 API MTA1 GI1 GI2 MS1 LO1 MS2 MR1 MR2 X.25 normal mode MS4 MS3 MR3 RS1 RS3 RS2 MR4 X.25 1980 mode LO2 LAN X.25 1980 mode RS4 LAN OSI/AS OSI/TS X25AM 1980 mode X25AM normal mode TLAM Potential link to MTA3 (not configured in example files) MTA2 MTA3 VST 036.
PAGE 298
Troubleshooting Your OSI/MHS Subsystem Problem Examples Figure 9-3 shows MTA2. Figure 9-3. MTA2 Configuration MTA2 MR 1 MR 2 MR 3 X.25 OSI/AS OSI/TS X25AM MTA1 MTA3 VST 092.VSD In this example, a message has been submitted to MTA1 from a Transfer PS Mail client to be delivered to the adjacent MTA2. In this case, MTA1 is the initiator of the association and MTA2 is the responder. Event message 35 is enabled. Note.
PAGE 299
Troubleshooting Your OSI/MHS Subsystem Problem Examples Sometimes a connection failure can be caused by a mismatch between the OSI/MHS configuration and the OSI/AS configuration. In such cases, one of the following event messages is produced: ZMHS-EVT-BAD-OSI-CONFIG ZMHS-EVT-BAD-OSI-RESOURCE ZMHS-EVT-FTL-OSI-CONFIG ZMHS-EVT-FTL-OSI-RESOURCE - event event event event message message message message 22 23 24 25 Each of these messages includes an OSI/AS API error code, followed by a subcode.
PAGE 300
Troubleshooting Your OSI/MHS Subsystem Problem Examples 2. Using SCF to trace RTS process actions 3. Using PTrace to display the results of the SCF trace This method is useful primarily if accounting events are disabled or if the events do not completely explain the problem. In general, it is useful to turn on accounting events as soon as you notice a problem in the STATS PROCESS display; information in the event messages can help you decide how to search the trace records.
PAGE 301
Troubleshooting Your OSI/MHS Subsystem U-ABORT........... 0 U-EXCEPT.......... 0 -> -> -> -> Problem Examples P-ABORT........... 0 P-EXCEPT.......... 0 == == Check the RTS processes stats == stats process $zk1.#rk11 MHS stats PROCESS RTS \CS7.$RK11: Reset-time........ Sample-time....... CPU............... Msgs-sent......... Msgs-received..... Inc-assocs-open... Inc-assocs-closed. Inc-assocs-rej.... Inc-assocs-fail... Inc-assocs-recovs. Inc-trans-fail.... Transfer-timeouts. U-ABORT........... U-EXCEPT..
PAGE 302
Troubleshooting Your OSI/MHS Subsystem Problem Examples User Link Lsap : 0 Orig FU : 1-0-201 Dest FU : 0-0-100 Unique : 738560419-506 Session Link Lsap 0 Orig FU : 0-0-0 Dest FU : 0-0-0 Unique : 0-0 Remote address PSEL : SSEL : TSEL : NSAP : Local address : PSEL : SSEL : TSEL : NSAP : Initiator : 1 Turn : 0 Checkpoint size : 1 Window size : 3 Safe store window : 2 Application Protocol : 1 Abstract syntax id : 0 Dialogue mode : 0 Local MTA name : Local Password : Remote MTA name : Remote Password : Recover
PAGE 303
Troubleshooting Your OSI/MHS Subsystem Problem Examples Initiator : 1 Turn : 0 Checkpoint size : 1 Window size : 3 Safe store window : 2 Application Protocol : 88 Abstract syntax id : 0 Dialogue mode : 0 Local MTA name : 4D544131 Local Password : 4D544132 Remote MTA name : Remote Password : Recovery time : 600 Recovery expiry : 0 Delay time : 60 Delay expiry : 0 PCD List size : 0 PCID : 0 Current session connection id User ref : 040751515A4B312030 Common ref : 170D3933303630323139323034355A Add ref : 1401
PAGE 304
Troubleshooting Your OSI/MHS Subsystem Problem Examples The connection parameters are highlighted in boldface in trace record number 1; they include the local and remote OSI addresses, the dialogue mode, the protocol, and the initiator’s MTA name and password. Their values must match those expected by the adjacent MTA; use SCF if that MTA is an OSI/MHS subsystem, or use whatever other means are available if it is not an OSI/MHS subsystem.
PAGE 305
Troubleshooting Your OSI/MHS Subsystem Msgs-sent......... Msgs-received..... Inc-assocs-open... Inc-assocs-closed. Inc-assocs-rej.... Inc-assocs-fail... Inc-assocs-recovs. Inc-trans-fail.... Transfer-timeouts. U-ABORT........... U-EXCEPT.......... 0 0 0 0 11 0 0 0 0 0 0 Problem Examples Msg-bytes-sent.... Msg-bytes-received Out-assocs-open... Out-assocs-closed. Out-assocs-rej.... Out-assocs-fail... Out-assocs-recovs. Out-trans-fail.... Recovery-timeouts. P-ABORT........... P-EXCEPT..........
PAGE 306
Troubleshooting Your OSI/MHS Subsystem Problem Examples MTA name : 4D544131 Password : 4D544132 -------------------------------------------Context 1129240 Status : 1 Valid user link : 0 Valid session link : 1 Direction : 1 State : 0 Queueing enabled : 0 User Link Lsap : 0 Orig FU : 0-0-0 Dest FU : 0-0-0 Unique : 0-0 Session Link Lsap 1 Orig FU : 0-0-100 Dest FU : 0-0-100 Unique : 739045815-0 Remote address PSEL : SSEL : TSEL : NSAP : Local address : PSEL : SSEL : TSEL : NSAP : Initiator : 1 Turn : 0 Check
PAGE 307
Troubleshooting Your OSI/MHS Subsystem Problem Examples TSEL : 52 NSAP : 52 Initiator : 0 Turn : 0 Checkpoint size : 1 Window size : 3 Safe store window : 2 Application Protocol : 88 Abstract syntax id : 0 Dialogue mode : 0 Local MTA name : Local Password : Remote MTA name : 4D544131 Remote Password : 4D544132 Recovery time : 600 Recovery expiry : 0 Delay time : 60 Delay expiry : 0 PCD List size : 3 PCID : 3 Current session connection id User ref : 040751515A4B312030 Common ref : 170D393330363032313932303
PAGE 308
Troubleshooting Your OSI/MHS Subsystem Problem Examples Table 9-5. RTS Refusal Code Mapping (page 2 of 2) No. Internal Name CCITT RTSE (Refuse reason) 5 BAD_TURN validation failure Initial turn is not owned by initiator. 6 NOT_ALLOWED_TO_OPEN rts busy This MTA is not configured for incoming associations (REMOTE-INIT off). 7 NO_MORE_ALLOWED rts busy Maximum number of associations reached for RTS.
PAGE 309
Troubleshooting Your OSI/MHS Subsystem Problem Reporting number 9) is 51. To correct this problem, alter the MTA object with the correct REMNSAP-1 value: -> assume mta $zk2.#mta1 -> alter, rem-nsap-1 51 -> info mta,detail MHS Detailed info MTA MTA1 *Password-server.. *Logon-validation. *Applicn-context.. *Dialogue-mode.... *Max-msg-length... *Local-init....... *Remote-init...... *Rem-P-SELECTOR-1. *Rem-S-SELECTOR-1. *Rem-T-SELECTOR-1. *Rem-NSAP-1....... *Loc-P-SELECTOR-1. *Loc-S-SELECTOR-1.
PAGE 310
Troubleshooting Your OSI/MHS Subsystem • • • Effects on the System OSI/AS (TAPS) traces, with minimum of L5, L6, ACSE trace records, and record size of 4042 (maximum value) SCF configuration files for OSI/AS and OSI/MHS EMS event log (with accounting events turned on) Effects on the System Interconnection problems cause minimal impact on the subsystem, with the exception of the connection to the adjacent MTA.
PAGE 311
Troubleshooting Your OSI/MHS Subsystem Unroutable Messages and Nondelivery Reports Unroutable Messages and Nondelivery Reports This subsection describes message flow among OSI/MHS processes in general and between the MR process and RTS in particular. An understanding of this message flow can make it easier to identify routing problems. It is also the basis for message tracking. Problem Description Each OSI/MHS process (RTS, MR, SC, MS, RS, and LO) consists of several functional units (FUs).
PAGE 312
Troubleshooting Your OSI/MHS Subsystem Problem Description Each message processed by the MTA is typically destined for more than one recipient. The MTA is responsible for splitting such messages, with multiple recipients requiring different routing. The MTA is also responsible for adding to each message both internal and external trace information, which records the path the message has taken through the MHS.
PAGE 313
Troubleshooting Your OSI/MHS Subsystem Problem Description Basic Routing Scenarios To understand whether an unroutable message will result in an event message or a nondelivery report, it is important to consider some of the possible message delivery operations within an MR group. Figure 9-4 illustrates some possibilities. Figure 9-4. Basic Message Flow OSIMHS MR Groups Other MTAs 1 RTS MRP 3 MS User 2 4 Other MTAs Gateway User VST 043.
PAGE 314
Troubleshooting Your OSI/MHS Subsystem Problem Examples Problem Examples The following is an example of the series of messages describing an unroutable report. The configuration is the same as the OSI/MHS configuration example shown in Appendix A, Examples of Configuration Files, and described in Section 5, Configuring Your OSI/MHS Subsystem. In this example, a Transfer X400 gateway user sends a message to a gateway user and a local MS user.
PAGE 315
Troubleshooting Your OSI/MHS Subsystem Problem Examples #UNROUTABLE (null); Recip.(1) MPDUid: 01234567890123456789012345678901 94-12-04 16:00:56 \CS7.$MK11 Report To: TANDEM.MHS.D20 000044 Routing #UNROUTABLE (null); Recip.(1) MPDUid: DESIGNATOR1 M0000000739234856057 94-12-04 16:00:57 \CS7.$MK11 Unroutable To: /c=OZ TANDEM.MHS.D20 000007 Report /a=UNDefined /p=? /o=NOTKnown /pn=?.?/, Size: 307 MPDUid: DESIGNATOR1 M0000000739234856057 94-12-04 16:00:57 \CS7.$MK11 MR.\CS7.MRGRP1 $MK11: TANDEM.MHS.
PAGE 316
Troubleshooting Your OSI/MHS Subsystem Problem Reporting value of 0. The unroute reason codes are described in the OSI/MHS Management Programming Manual and contained in the following list: No.
PAGE 317
Troubleshooting Your OSI/MHS Subsystem Recovery Checklist errors. If the PDU store becomes overburdened with unroutable PDUs, contact your HP representative about diagnostic software that can delete the unwanted PDUs.
PAGE 318
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions The OSI/MHS SCF Reference Manual provides information about trace options and trace record formats. The OSI/MHS Management Programming Manual describes each event message and the tokens in each message and indicates which tokens are displayed or printed if you use the event-message templates supplied with OSI/MHS.
PAGE 319
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions Notification Handler This functional unit within the MR process produces reports in response to probes and unroutable messages and, when required, to acknowledge deliveries. It also receives incoming delivery and nondelivery reports. P1 Decode This functional unit in the MR process translates an incoming message from encoded ASN.1 (BER) format to a local (value tree) representation.
PAGE 320
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions Figure 9-5. Message Relay MRP 3 Router MTA Association Manager P1 Decode P1 Encode 6 7 MR PDU Store Incoming PDU Outgoing PDU Adjacent MTA1 Adjacent MTA2 RTS 1 2 8 4 5 9 VST 044.VSD 1. Event message 35 (ZMHS-EVT-RTS-ASSOC-OP) reports that the RTS process accepted an incoming association. 2. Event message 36 (ZMHS-EVT-RTS-TRANSFER) reports that the RTS process received a message from the adjacent MTA. 3.
PAGE 321
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions 9. Event message 37 (ZMHS-EVT-RTS-ASSOC-END) reports that the RTS process has closed the association with the MTA to which the message was relayed. In this example, the message to be relayed came from an adjacent MTA. If it had come from a gateway or a user agent, event messages 35 and 36 would not have been produced. (Examples later in this section describe those cases.
PAGE 322
Troubleshooting Your OSI/MHS Subsystem • Event-Message Sequences for Common MHS Functions Event messages 44, 7, and 8 include a message identifier that you can use to link the routing event with the summary and recipient information. The message identifier is the X.400 MPDU ID, represented by tokens with names of the form ZMHS-TKN-MID-nnnn. Additionally, messages 44 and 8 include the recipient O/R name (represented by tokens with names of the form ZMHS-TKN-OR-nnnn).
PAGE 323
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions 2. Event message 36 (ZMHS-EVT-ACCT-RTS-TRANSFER) indicates that the RTS process received a report from the adjacent MTA. 3. Event message 44 (ZMHS-EVT-ACCT-MRP-ROUTE) indicates that router has identified the gateway user to whom the report should be delivered and has placed the report on the queue for the gateway access unit. 4.
PAGE 324
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions OSI/MHS Receives a Message and Delivers It to a MessageStore User Figure 9-7 illustrates the steps taken when OSI/MHS receives a message from a remote user agent and delivers it to a message-store user. The numbers on the figure represent the event messages in the order in which they are produced; the description after the figure gives the actual event numbers. Figure 9-7.
PAGE 325
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions 5. Event message 44 (ZMHS-EVT-ACCT-MRP-ROUTE) indicates that router has identified the message-store user to whom the message should be delivered. 6. Event message 7 (ZMHS-EVT-ACCT-MSG) indicates that the message was delivered to the MS process and provides summary information about the message. The message has not yet been placed in the user’s mailbox. 7.
PAGE 326
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions Message Submitted for Deferred Delivery by Local User Agent Figure 9-8 illustrates the steps taken when an LUA submits a message to OSI/MHS for deferred delivery. The numbers on the figure represent the event messages in the order in which they are produced; the description after the figure gives the actual event numbers. Figure 9-8.
PAGE 327
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions 6. Event message 47 (ZMHS-EVT-ACCT-MS-OPERATION) indicates that an MS Submit operation was performed: that the LUA submitted the X.400 message to OSI/MHS for routing and, in this case, deferred delivery. (This event message reports the result of the MS operation; the submission and deferral actually occurred before event 11.) 7. Event message 43 (ZMHS-EVT-LOS-ASSOC-END) indicates that the LUA closed the association. 8.
PAGE 328
Troubleshooting Your OSI/MHS Subsystem • Event-Message Sequences for Common MHS Functions Event messages 41 and 42 include the DSM object name (ZCOM-TKNOBJNAME) of the APPL object representing the sender, and event message 44 contains the DSM object name (ZCOM-TKN-OBJNAME) of the ROUTE object used to relay the message.
PAGE 329
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions Figure 9-9. Expanding a Distribution List MR PDU Store MRP 2 5 6 Distribution List Expansion Expanded PDU 7 Router 1 Delivered PDU 3 4 8 9 Gateway Access Unit Gateway P1 Decode Incoming PDU VST 048.VSD 1. Event message 44 (ZMHS-EVT-ACCT-MRP-ROUTE) indicates that the router has identified the individual recipient and has queued the message for the gateway access unit. 2.
PAGE 330
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions users, only one copy of the message is delivered to the gateway access unit, and therefore this event message occurs only once.) 9. Event message 8 (ZMHS-EVT-ACCT-RECIP-INFO) occurs three times, once for each member of the distribution list. Each instance of the message provides information about a different recipient.
PAGE 331
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions Figure 9-10. Delivering and Responding to a Probe MRP 4 5 UA Access Manager 3 6 Router Notification Handler MTA Association Manager P1 Encode P1 Decode 9 10 MR PDU Store Incoming PDU Adjacent MTA1 Outgoing PDU RTS 1 2 7 8 VST 049.VSD 1. Event message 35 (ZMHS-EVT-ACCT-RTS-ASSOC-OP) indicates that the RTS process accepted an incoming association. 2.
PAGE 332
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions 7. Event message 35 (ZMHS-EVT-ACCT-RTS-ASSOC-OP) indicates that the RTS process has established an outgoing association. 8. Event message 36 (ZMHS-EVT-ACCT-RTS-TRANSFER) indicates that the RTS process sent the report to the adjacent MTA. 9. Event message 7 (ZMHS-EVT-ACCT-MSG) indicates that the report was sent and provides summary information about the report. 10.
PAGE 333
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions Event Message Number(s) Token Name(s) (ZMHS-TKN-) Token Semantics 44 (probe) ZCOM-TKN-OBJNAME APPL object name of probe recipient 44 (report) ZCOM-TKN-OBJNAME ROUTE object name for report 7, 36 (report) PDUID Outgoing PDUID A Remote User Deletes Stored Messages Figure 9-11 illustrates the steps taken when an RUA requests that OSI/MHS delete messages from the message store.
PAGE 334
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions 1. Event message 38 (ZMHS-EVT-ROS-ASSOC-OP) indicates that the RS process accepted an association from an RUA. 2. Event message 47 (ZMHS-EVT-ACCT-MS-OPERATION) indicates that an MS Bind operation was performed and that the MS process responded to the RS process. 3.
PAGE 335
Troubleshooting Your OSI/MHS Subsystem • Event-Message Sequences for Common MHS Functions Event messages 38 and 39 include the DSM object name (ZCOM-TKNOBJNAME) of the APPL object representing the user, and event message 44 contains the DSM object name (ZCOM-TKN-OBJNAME) of the mailbox owner, which is normally the same.
PAGE 336
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions 1. Event message 30 (ZMHS-EVT-ACCT-CUG-VIOL) indicates that the router discovered a CUG violation. That is, it discovered that a recipient of an incoming message is not a member of the same closed user group as the originator and has queued the message for the notification handler. 2. Event message 31 (ZMHS-EVT-ACCT-CUG-VIOL-RECIP) provides information about the invalid recipient. 3.
PAGE 337
Troubleshooting Your OSI/MHS Subsystem Event-Message Sequences for Common MHS Functions to the valid recipient both include the O/R name of that recipient in tokens of the form ZMHS-TKN-OR-nnnn. • • • • The instance of event message 7, 8, and 44 pertaining to the report include the same report identifier in tokens of the form ZMHS-TKN-MID-nnnn.
PAGE 338
Troubleshooting Your OSI/MHS Subsystem Interconnection Problems With Gateways Interconnection Problems With Gateways Several types of problems can arise when you attempt to connect OSI/MHS with a gateway or during the subsequent operation of a gateway.
PAGE 339
Troubleshooting Your OSI/MHS Subsystem Problem: Missing Entry or Wait Manager Process problem, you can usually look for the process name in your configuration and startup files and identify either a missing START command or a name mismatch between the ADD and START commands. If the required process was not defined in the configuration, the status codes are different, and there might or might not be an event message.
PAGE 340
Troubleshooting Your OSI/MHS Subsystem Problem: Insufficient Memory for Gateway The GPI application receives the error OM_RC_PERMANENT_ERROR in response to an open call. The primary code returned by the status call is ZGPI_RC_OPEN_ERROR, and the secondary code is 14 (device does not exist). The operations staff discovers the following event messages in the event log: 94-12-10 10:43:29 \LAS.0,0 TANDEM.CPU.D20 000101 Processor Down, CPU 2 ... 94-12-10 10:45:04 \LAS.$PG11 TANDEM.MHS.D20 000012 $ZG1 GI.
PAGE 341
Troubleshooting Your OSI/MHS Subsystem Problem: Insufficient Memory for Gateway GPI_Initialize_, based on anticipated message size and other factors, and how much space must be available on the swap volume. The GPI library needs up to 80.5 MB for two object trees of the maximum size. The swap space for a GI process is required not only to manage object trees, but also to support mapping between the object and value trees that represent X.400 messages.
PAGE 342
Troubleshooting Your OSI/MHS Subsystem Problem: Insufficient Memory for Gateway *GI-Backup-CPU.... -1 *GI-Priority...... -1 $posta subv 49> dsap $postc,short Disk Space Analysis Program -- T9543D20 - (17JUN94) -- 12/2/94 Compaq Computers Incorporated 1981, 1983, 1985-1993 Free Space Short Report Volume $POSTC (M) Y -- Capacity (Mb) -Total Free 895 6.31 % Free 0 12:39:25 -- Free Extents -Count Biggest 591 4.
PAGE 343
Troubleshooting Your OSI/MHS Subsystem Problem Reporting Problem Reporting If memory problems persist after you adjust the GPI_Initialize parameters and change the swap volume, save the following information and provide it to your HP representative: • • • • • • The event log The MR PDU store and log The entry manager message queue file The DSAP output Information about the application and the messages it processes VPROC of the library module and GIP Effects on the System There is minimal effect on the
PAGE 344
Troubleshooting Your OSI/MHS Subsystem Problem Description The LO process communicates through a programmatic interface with a customer or third-party application running on a HP NonStop™ system. The P7 API application runs on the same physical system as the OSI/MHS subsystem. The LO and RS processes interface to the MS and MR process in the same manner. They provide similar statistics, status, and trace information.
PAGE 345
Troubleshooting Your OSI/MHS Subsystem Problem Example Problem Example This subsection provides an example of LO and RS process interface problems. The method used to identify the problem includes: 1. Using SCF to display RS or LO process statistics 2. Using SCF to trace RS or LO process actions 3. Using PTrace to display the results of the SCF trace This method is useful primarily if accounting events are disabled or if the events do not completely explain the problem.
PAGE 346
Troubleshooting Your OSI/MHS Subsystem MTA-delivered..... UAs-logged-on..... UA-cancel......... UA-fetch.......... UA-submitted...... UA-summary........ 1 1 0 0 0 0 Problem Example MTA-reports....... UAs-logged-off.... UA-delete......... UA-list........... UA-probes......... 0 1 0 0 0 15 Dec 1994, 15:35:18.071 15 Dec 1994, 15:54:52.838 0 Protocol-errors... 0 Msg-bytes-sent.... 0 Msg-bytes-received 0 Inc-assocs-closed. 0 0 0 0 0 MHS stats PROCESS LO \CS7.$LK11: Reset-time........ Sample-time.......
PAGE 347
Troubleshooting Your OSI/MHS Subsystem Reset-time........ Sample-time....... CPU............... Msgs-sent......... Msgs-received..... Inc-assocs-open... Inc-assocs-closed. Inc-assocs-rej.... Inc-assocs-fail... Inc-assocs-recovs. Inc-trans-fail.... Transfer-timeouts. U-ABORT........... U-EXCEPT.......... Problem Example 15 Dec 1994, 15:35:18.822 15 Dec 1994, 15:54:53.623 0 Protocol-errors... 0 Msg-bytes-sent.... 0 Msg-bytes-received 0 Out-assocs-open... 0 Out-assocs-closed. 0 Out-assocs-rej....
PAGE 348
Troubleshooting Your OSI/MHS Subsystem Problem Example The display shows that an association was rejected. To determine why the Inc-assocrej counter has increased, examine the event log: 94-12-15 15:45:46 \CS7.$IK51 TANDEM.MHS.D20 000019 $ZK1 MS.\CS7.MSGRP5 $IK51: Invalid password attempt from 94-12-15 15:45:47 \CS7.$OK11 application UAMS19 TANDEM.MHS.D20 000038 ROS Association Rejected; Assoc. id(0); Bind Error; 94-12-15 16:15:47 \CS7.
PAGE 349
Troubleshooting Your OSI/MHS Subsystem Problem Example NSAP: 51 Remote address PSEL: 4B54524F535053454C3141 SSEL: 4B54524F535353454C3141 TSEL: 52 NSAP: 52 PDU Id = MEMORY PDU -------------------------------------------Context Control Block Index : 0 State : LISTENING CEPI : 4294967286 IL Conn: 740184754 0 Layer : 4294967295 Entity : 0 12/15/94 16:15:45.348668 >000.033306 #2 MHSDECODE DECODE OF PDUID: MEMORY PDU PDUSIZE : 87 PROTOCOL : ExternalFrag RESULT : SUCCESS 12/15/94 16:15:45.442878 >000.
PAGE 350
Troubleshooting Your OSI/MHS Subsystem PROTOCOL RESULT Problem Example : msBindUAPFrag : SUCCESS 12/15/94 16:15:45.723111 >000.
PAGE 351
Troubleshooting Your OSI/MHS Subsystem Problem Example 4 encoding (CHOICE) 1 singleASN1Type (ANY) msBindUAPFrag (CHOICE) 3 msBindErrorUAPParams (INTEGER) 0 12/15/94 16:15:47.259976 >000.016956 #10 PDUID PDUSIZE PROTOCOL OPERATION : : : : MHSEPDUMAN MEMORY PDU 12 ExternalFrag ENCODE 000000: 28 0A 02 01 07 A0 05 B2 03 0A 01 00 12/15/94 16:15:47.421353 >000.
PAGE 352
Troubleshooting Your OSI/MHS Subsystem *Numeric-user-ID.. *Common-name...... *Terminal-type.... *Org-Name......... *Org-Unit-1....... *Org-Unit-2....... *Org-Unit-3....... *Org-Unit-4....... *Sur-name......... *Given-name....... *Initials......... *Generation....... *Dom-Type-1....... *Dom-Value-1...... *Dom-Type-2....... *Dom-Value-2...... *Dom-Type-3....... *Dom-Value-3...... *Dom-Type-4....... *Dom-Value-4...... ...
PAGE 353
Troubleshooting Your OSI/MHS Subsystem Problem Reporting Problem Reporting If you are sure that an LO or RS process interface problem was caused neither by a configuration error nor by an operator action (like stopping an APPL object), and you wish to report an LO or RS process interface problem for investigation, provide the following information to your HP representative: • • • • • • • EMS logs, including accounting events Complete traces of LO or RS process Detailed description of the problem Descrip
PAGE 354
Troubleshooting Your OSI/MHS Subsystem OSI/MHS Configuration and Management Manual—424827-003 9- 68 Summary
PAGE 355
A Examples of Configuration Files This appendix contains the files required to install and configure each OSI/MHS MTA described in Section 5, Configuring Your OSI/MHS Subsystem. It also contains the SCF command files that configure OSI/AS and OSI/TS to support each MTA, and an overview of these configurations.
PAGE 356
Examples of Configuration Files Installation File for MTA1 Installation File for MTA1 The source code for this example is provided in the file EXISMTA1. ============================================================= == Source file: EXISMTA1 == OSI/MHS Installation file for MTA 1 == Describes the contents and the location of each == installed element, and determines what operations == take place during installation.
PAGE 357
Examples of Configuration Files == == == Installation File for MTA1 MR Group #2 MR_PDU_STORE_DATA2 MR_PDU_STORE_LOG2 MHS1MR2.PDUMR2 MHS1MR2.LOGMR2 MR Group #3 MR_PDU_STORE_DATA3 MR_PDU_STORE_LOG3 MHS1MR3.PDUMR3 MHS1MR3.LOGMR3 == == MR Group #4 MR_PDU_STORE_DATA4 MHS1MR4.PDUMR4 MR_PDU_STORE_LOG4 MHS1MR4.
PAGE 358
Examples of Configuration Files Installation File for MTA1 COMPILE_MS_INIT_PROGRAM YES CREATE_CATALOG YES COMPILE_MS YES CREATE_OSIMHS_DATABASE YES CREATE_MS_DATABASES YES CREATE_MR_DATABASES YES CREATE_RS_DATABASES YES CREATE_GI_DATABASES YES CREATE_LO_DATABASES YES CREATE_SAMPLE_CONFIG NO ============================================================= == NOTE: Assumes prior installation of ISVs ============================================================= OSI/MHS Configuration and Management Manual—42482
PAGE 359
Examples of Configuration Files OSI/MHS Configuration Command File for MTA1 OSI/MHS Configuration Command File for MTA1 The source code for this example is provided in the file EXCFMTA1. ============================================================= == Source file: EXCFMTA1 == SCF CONFIGURATION FILE FOR MTA 1 == Defines objects and attributes for this MTA == PRMD: DEVICEIND == ORG-NAME: SALES == Many attribute values shown here are defaults. They == are included to clarify the configuration process.
PAGE 360
Examples of Configuration Files OSI/MHS Configuration Command File for MTA1 ACCT-PROBE-SUBMIT ON, & ACCT-PROBE-DELIVER ON, & ACCT-PROBE-RELAY ON, & ACCT-REPORT-GEN ON, & ACCT-REPORT-DELIVER ON, & ACCT-REPORT-RELAY ON, & ACCT-UNROUTEABLE ON, & ACCT-SUBMIT-RECIP-INFO ON, & ACCT-DELIVER-RECIP-INFO ON, & ACCT-RELAY-RECIP-INFO ON, & ACCT-GEN-RECIP-INFO ON, & ACCT-UNROUTE-RECIP-INFO ON ============================================================= ============================================================= ==
PAGE 361
Examples of Configuration Files == ADD CLASS #MS, NUMBER-OF-MAILBOXES OSI/MHS Configuration Command File for MTA1 & 1000 ============================================================= == == Add CLASS REMOTE SERVICE #RS == ADD CLASS #RS, & number-of-associations 20 ============================================================= == == Add CLASS GATEWAY INTERFACE #GI == ADD CLASS #GI ============================================================= == == Add CLASS LOCAL OPERATIONS #LO == ADD CLASS #LO ===========
PAGE 362
Examples of Configuration Files MRP-PNAME SC-PNAME MR-T-SELECTOR MR-NSAP OSI/MHS Configuration Command File for MTA1 $MHS1.#M12, $MHS1.#S12, 4D5258323541, 703285003011 & & & ============================================================= == == Add MESSAGE RELAY GROUP #MR.MRGRP3 == ADD GROUP #MR.MRGRP3, & CPU 2, & BACKUP 3, & PRI 130, & PDU-STORE MHS1MR3.PDUMR3, & PDU-LOG-FILE MHS1MR3.LOGMR3, & WORK-SV MHS1MR3, & RTS-PNAME $MHS1.#R13, & MRP-PNAME $MHS1.#M13, & SC-PNAME $MHS1.
PAGE 363
Examples of Configuration Files OSI/MHS Configuration Command File for MTA1 ============================================================= == == Add MESSAGE STORE GROUP #MS.MSGRP2 == ADD GROUP #MS.MSGRP2, & CPU 3, & BACKUP 0, & PRI 130, & PDU-STORE MHS1MS2.PDUMS2, & PDU-LOG-FILE MHS1MS2.LOGMS2, & WORK-SV MHS1MS2, & MS-PNAME $MHS1.#I12, & MSG-STORE-SV MHS1MS2, & MR-COUNT SYS ============================================================= == == Add MESSAGE STORE GROUP #MS.MSGRP3 == ADD GROUP #MS.
PAGE 364
Examples of Configuration Files PDU-LOG-FILE WORK-SV RS-PNAME RS-P-SELECTOR RS-T-SELECTOR RS-NSAP OSI/MHS Configuration Command File for MTA1 MHS1RS1.LOGRS1, MHS1RS1, $MHS1.#V11, 5053454C, 5253583235, 703238502810 & & & & & ============================================================= == == Add REMOTE SERVICE GROUP #RS.RSGRP2 == ADD GROUP #RS.RSGRP2, & CPU 2, & BACKUP 3, & PRI 130, & PDU-STORE MHS1RS2.PDURS2, & PDU-LOG-FILE MHS1RS2.LOGRS2, & WORK-SV MHS1RS2, & RS-PNAME $MHS1.
PAGE 365
Examples of Configuration Files OSI/MHS Configuration Command File for MTA1 == Add GATEWAY INTERFACE GROUP #GI.GIGRP1 == ADD GROUP #GI.GIGRP1, CPU 1, BACKUP 2, PRI 130, PDU-STORE MHS1GI1.PDUGI1, PDU-LOG-FILE MHS1GI1.LOGGI1, WORK-SV MHS1GI1, GI-PNAME $MHS1.#G11 & & & & & & & ============================================================= == == Add GATEWAY INTERFACE GROUP #GI.GIGRP2 == ADD GROUP #GI.GIGRP2, & CPU 2, & BACKUP 3, & PRI 130, & PDU-STORE MHS1GI2.PDUGI2, & PDU-LOG-FILE MHS1GI2.
PAGE 366
Examples of Configuration Files OSI/MHS Configuration Command File for MTA1 == ADD GATEWAY #TRANSFER, VINTAGE VALIDATION GW-PNAME 84, ON, $XXQ0 ADD GATEWAY #GENERALGATEWAY, VINTAGE VALIDATION GW-PNAME GW-AUX-PNAME PASSWORD 88, OFF, $GX10, $GWOU, PrivateGateway & & & & & & & & ============================================================= ============================================================= == == ADD GATEWAY APPL OBJECTS == ============================================================= ADD APPL
PAGE 367
Examples of Configuration Files ENCODED-INFO-TYPE-VOICE ADD APPL #GeneralUser, ACCESS-TYPE ACCESS-NAME ISO-COUNTRY-NAME ADMD PRMD ORG-NAME DEL-MAX-MSG-LEN OSI/MHS Configuration Command File for MTA1 OFF GW, GENERALGATEWAY, US, TELENET, DEVICEIND, FAX, 2000000 & & & & & & & ============================================================= ============================================================= == == ADD MS APPL OBJECTS == ============================================================= == ADD APPL #James
PAGE 368
Examples of Configuration Files OSI/MHS Configuration Command File for MTA1 ACCESS-NAME MSGRP4, & USER-PASSWORD PWDLS, & ISO-COUNTRY-NAME US, & ADMD TELENET, & PRMD DEVICEIND, & ORG-NAME SALES, & ORG-UNIT-1 MSUSERS, & SUR-NAME Smythe, & GIVEN-NAME Lynda ============================================================= ============================================================= == == ADD DLIST AND DLISTMEMBEROBJECTS == ============================================================= ADD DLIST #SALES, & DL-ISO-C
PAGE 369
Examples of Configuration Files GIVEN-NAME OSI/MHS Configuration Command File for MTA1 Janet ADD DLISTMEMBER #SALES.
PAGE 370
Examples of Configuration Files ADMD PRMD ORG-NAME ORG-UNIT-1 SUR-NAME GIVEN-NAME OSI/MHS Configuration Command File for MTA1 TELENET, DEVICEIND, MANUFACTURING MSUSERS, Jones, Terry & & & & & ============================================================= ============================================================= == == ADD CUG and CUGMEMBER OBJECTS == ============================================================= ADD CUG #DEVICEINDUSERSONLY, & CONTENT-TYPE-CHECK OFF, & MAX-MSG-LEN 1000000 ADD CUGMEMBER
PAGE 371
Examples of Configuration Files LOC-NSAP-1 REM-MTA-NAME ISO-COUNTRY-NAME X121-COUNTRY-NAME COUNTRY-NAME REM-ADMD REM-PRMD OSI/MHS Configuration Command File for MTA1 703285003011, MTA2, US, 310, UNITEDSTATESOFAMERICA, TELENET, DEVICEIND & & & & & & ============================================================= ============================================================= == == Add ROUTE 1 GOING TO MTA2 == ADD ROUTE #MTA2.
PAGE 372
Examples of Configuration Files OSI/MHS Configuration Command File for MTA1 == Add MTA OBJECT TO REPRESENT ADJACENT MTA3 == ============================================================= ADD MTA #MTA3, & REM-LOGON-VALIDATION ON, & REM-OUR-PASSW MTA1, & REM-THEIR-PASSW MTA3, & REM-APPLIC-CONTEXT MTS-TRANSFER, & REM-DIALOGUE-MODE MONOLOGUE, & REM-MAX-MSG-LEN 2097152, & REM-LOCAL-INIT ON, & REM-REMOTE-INIT ON, & REM-TSELECTOR-1 4D5258323541, & REM-NSAP-1 373033323835303033323132, & LOC-TSELECTOR-1 4D525832354
PAGE 373
Examples of Configuration Files ORG-NAME OSI/MHS Configuration Command File for MTA1 BOSTON ============================================================= == == Add ROUTE 4 GOING TO MTA2 via MTA3 == ADD ROUTE #MTA3.
PAGE 374
Examples of Configuration Files Overview of the OSI Configuration for MTA1 Overview of the OSI Configuration for MTA1 The OSI services connections for MTA1 are as follows: MTA 1 Configuration - OSI Stack connections SCF configuration files : OSICFG1 RSGRP1 RSGRP3 MRGRP1 MRGRP3 MRGRP4 RSGRP2 RSGRP4 MRGRP2 | | | | | | | X25 | | LAN |X25 |X25 |LAN | | | | | | | | | | _|___|____________|_______|_________|____ | OSI Stack OSIMGR $UOSI | | TAPS $UAS1 | | TSP $UTS1 | |_________________________________________| |
PAGE 375
Examples of Configuration Files Overview of the OSI Configuration for MTA1 The following are the OSI addresses for each local group in MTA1: RSGRP 1 & 2 - X25 SNPA 10 port number NSAP 703238503010 TSEL 5253583235 SSEL DTE address + port number "RSX25" null PSEL null RSGRP 3 & 4 − LAN SNPA FE08008E000259 FE + MAC address> NSAP 49000108008E00025901 TSEL 52534C414E SSEL null PSEL 490001 + MAC address + 01 "RSLAN" null MRGRP1 & MRGRP2 − X25 normal mode SNPA 11 port number NSAP 70328500
PAGE 376
Examples of Configuration Files Overview of the OSI Configuration for MTA1 MTA1 to MTA2 connectionnormal mode SNPA 20 port number NSAP 703285003020 DTE address TSEL 4D5258323541 "MRX25A" MTA1 to MTA3 connection1980 mode SNPA 30 port number NSAP 373033323835303033323132 ASCII DTE address TSEL 4D5258323542 "MRX25B" OSI/MHS Configuration and Management Manual—424827-003 A -22
PAGE 377
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA1 OSI/AS and OSI/TS Configuration Command File for MTA1 The source code for this example is provided in the file EXASMTA1. ============================================================= == == == This is a sample OSI/AS and OSI/TS (stack) == == configuration file. It defines the OSI/AS and OSI/TS == == addresses that correspond to OSI/MHS MTA1.
PAGE 378
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA1 ============================================================= == == =============== Configure common PROCESS section ========== == == ============================================================= ASSUME PROCESS $UOSI == assign X.25 IOP ADD #NSP.X25A, NAME $SX1 == Assign LAN IOP ADD #NSP.LAM1, NAME $LAM1 == Define TSP ADD #TSP.UTS1, NAME $UTS1, CPU 1, BACKUPCPU 0, CODEFILE TSPOBJ == Define TAPS ADD #TAPS.
PAGE 379
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA1 ============================================================= == MRGRP1 and MRGRP2 listen on same X.25 normal mode address ============================================================= == Define MRGRP1 ADD ENTRY #APPL.MRGRP1, TSEL 4D5258323541, & NSAP 703285003011 ADD ENTRY #TSEL.4D5258323541, SERVER $UOSI.#TAPS.UAS1 ADD ENTRY #NSAP.703285003011, SERVER $UOSI.#TSP.UTS1, & & PROFILE $UOSI.#L4.
PAGE 380
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA1 ADD ENTRY #SNPA.12, SERVER $UOSI.#NSP.X25A, & PROFILE $UOSI.#L3.MTA1PROB ADD PROFILE #L3.MTA1PROB, X25DESTADDR '703285003012', & X25REMOTENET X25XA, & X25NEGOTIATE (L3WINDOW,PKTSIZE, THRUPUT), & X25PORT 12 ============================================================= == MRGRP4 listens on LAN address ============================================================= == Define MRGRP4 ADD ENTRY #APPL.
PAGE 381
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA1 ============================================================= == Define RSGRP2 ADD ENTRY #APPL.
PAGE 382
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA1 X25NEGOTIATE (L3WINDOW,PKTSIZE, THRUPUT), & X25PORT 20 ============================================================= == Define remote address for MTA 3 ADD ENTRY #APPL.MTA3, TSEL 4D5258323542, & NSAP 373033323835303033323132 ADD ENTRY #TSEL.4D5258323542 ADD ENTRY #NSAP.373033323835303033323132 ADD ENTRY #SNPA.30, SERVER $UOSI.#NSP.X25A, & PROFILE $UOSI.#L3.MTA3PROA ADD PROFILE #L3.
PAGE 383
Examples of Configuration Files Installation File for MTA2 Installation File for MTA2 The source code for this example is provided in the file EXISMTA2. =========================================================== == OSI/MHS Installation configuration file for MTA 2 == (Message RELAY function only) =========================================================== OSIMHS_ISV ZOSIMHS OSIMHS_SUBVOL R25MHS MHSMGR_PNAME $MHS2 SQL_SYSTEM_CATALOG $SYSTEM.
PAGE 384
Examples of Configuration Files OSI/MHS Configuration Command File for MTA2 OSI/MHS Configuration Command File for MTA2 The source code for this example is provided in the file EXCFMTA2. ============================================================= == Source file: EXCFMTA2 == SCF CONFIGURATION FILE FOR MTA 2 == Defines objects and attributes for this MTA == PRMD: DEVICEIND == ORG-NAME: SHIPPING == Many attribute values shown here are defaults. They == are included to clarify the configuration process.
PAGE 385
Examples of Configuration Files OSI/MHS Configuration Command File for MTA2 == ADD SUBSYS #MHS2, & ROUTING-FNAME MHS2.ROUTE, & USER-FNAME MHS2.USER, & MTA-ASSOC-FNAME MHS2.
PAGE 386
Examples of Configuration Files OSI/MHS Configuration Command File for MTA2 ACCT-UNROUTE-RECIP-INFO ON ============================================================= ============================================================= == ADD CLASS. ============================================================= == Add CLASS MESSAGE RELAY #MR.
PAGE 387
Examples of Configuration Files OSI/MHS Configuration Command File for MTA2 == ADD GROUP #MR.MRGRP1, & CPU 0, & BACKUP 1, & PRI 130, & PDU-STORE MHS2MR1.PDUMR1, & PDU-LOG-FILE MHS2MR1.LOGMR1, & WORK-SV MHS2MR1, & RTS-PNAME $MHS2.#R21, & MRP-PNAME $MHS2.#M21, & SC-PNAME $MHS2.#S21, & MR-T-SELECTOR 4D5258323541, & MR-NSAP 703285003020 ============================================================= == Add MESSAGE RELAY GROUP #MR.MRGRP2. == ADD GROUP #MR.
PAGE 388
Examples of Configuration Files OSI/MHS Configuration Command File for MTA2 == ADD GROUP #MR.MRGRP3, & CPU 2, & BACKUP 0, & PRI 130, & PDU-STORE MHS2MR3.PDUMR3, & PDU-LOG-FILE MHS2MR3.LOGMR3, & WORK-SV MHS2MR3, & RTS-PNAME $MHS2.#R23, & MRP-PNAME $MHS2.#M23, & SC-PNAME $MHS2.
PAGE 389
Examples of Configuration Files REM-ADMD OSI/MHS Configuration Command File for MTA2 TELENET, & REM-PRMD DEVICEIND ============================================================= ============================================================= == Add ROUTE 1 GOING TO MTA1. == ADD ROUTE #MTA1.PRIMARY1, & PRI 1, & ISO-country-name US, & ADMD TELENET, & PRMD DEVICEIND, & ORG-NAME SALES ============================================================= == Add ROUTE 2 GOING TO MTA1. == ADD ROUTE #MTA1.
PAGE 390
Examples of Configuration Files OSI/MHS Configuration Command File for MTA2 == Add MTA OBJECT TO REPRESENT ADJACENT MTA3.
PAGE 391
Examples of Configuration Files OSI/MHS Configuration Command File for MTA2 == ADD ROUTE #MTA3.PRIMARY2, & PRI 1, & ISO-country-name US, & ADMD TELENET, & PRMD DEVICEIND, & ORG-NAME BOSTON ============================================================= == Add ROUTE 2 GOING TO MTA1 via MTA3 (Backup route). == ADD ROUTE #MTA3.
PAGE 392
Examples of Configuration Files Overview of the OSI Configuration for MTA2 Overview of the OSI Configuration for MTA2 The OSI services connections for MTA2 are as follows: MTA 2 ConfigurationOSI Stack connections MRGRP1 MRGRP2 MRGRP3 | |X25 | | _______________|_________________________ | OSI Stack OSIMGR $VOSI | | TAPS $VAS1 (8,9) | | TSP $VTS1 (8,9) | |_________________________________________| | | $SX1 Note: $SX1 is connected to a X.25 switch.
PAGE 393
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA2 OSI/AS and OSI/TS Configuration Command File for MTA2 The source code for this example is provided in the file EXASMTA2. ============================================================= == == == This is a sample OSI/AS and OSI/TS (stack) == == configuration file. It defines the OSI/AS and OSI/TS == == addresses that correspond to OSI/MHS MTA2.
PAGE 394
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA2 == == ============================================================= ASSUME PROCESS $VOSI == assign X.25 IOPs ADD #NSP.X25A, NAME $SX1 == define TSP ADD #TSP.VTS1, NAME $VTS1, CPU 1, BACKUPCPU 0, & CODEFILE TSPOBJ == Define TAPS ADD #TAPS.VAS1, NAME $VAS1, CPU 1, BACKUPCPU 0, & CODEFILE TAPSOBJ == Start TSP and TAPS PARAM TSP^PROTO^ID ON START PROCESS #TSP.VTS1 START PROCESS #TAPS.
PAGE 395
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA2 == == ============================================================= == == MTA2 has three local groups: MRGRP1, MRGRP2, MRGRP3 All three groups listen on same X.25 normal mode address ============================================================= == Define MRGRP1 ADD ENTRY #APPL.MRGRP1, TSEL 4D5258323541, & NSAP 703285003020 ADD ENTRY #TSEL.4D5258323541, SERVER $VOSI.#TAPS.VAS1 ADD ENTRY #NSAP.703285003020, SERVER $VOSI.
PAGE 396
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA2 == MTA3 == ============================================================= == Define remote address for MTA 1 ADD ENTRY #APPL.MTA1, TSEL 4D5258323541, & NSAP 703285003011 ADD ENTRY #TSEL.4D5258323541, SERVER $VOSI.#TAPS.VAS1 ADD ENTRY #NSAP.703285003011 ADD ENTRY #SNPA.11, SERVER $VOSI.#NSP.X25A, & PROFILE $VOSI.#L3.MTA1PROF ADD PROFILE #L3.
PAGE 397
Examples of Configuration Files Installation File for MTA3 Installation File for MTA3 The source code for this example is provided in the file EXISMTA3. ============================================================= == Source file: EXISMTA3 == OSI/MHS Installation file for MTA 3 == Describes the contents and the location of each == installed element, and determines what operations == take place during installation.
PAGE 398
Examples of Configuration Files Installation File for MTA3 ============================================================= == MR Group #1 == == == == == == MR_PDU_STORE_DATA1 MHS3MR1.PDUMR1 MR_PDU_STORE_LOG1 MHS3MR1.LOGMR1 MR Group #2 MR_PDU_STORE_DATA2 MHS3MR2.PDUMR2 MR_PDU_STORE_LOG2 MHS3MR2.LOGMR2 MR Group #3 MR_PDU_STORE_DATA3 MHS3MR3.PDUMR3 MR_PDU_STORE_LOG3 MHS3MR3.LOGMR3 MR Group #4 MR_PDU_STORE_DATA4 MHS3MR4.PDUMR4 MR_PDU_STORE_LOG4 MHS3MR4.
PAGE 399
Examples of Configuration Files Installation File for MTA3 ============================================================= == RS Group #1 == == RS_PDU_STORE_DATA1 MHS3RS1.PDURS1 RS_PDU_STORE_LOG1 MHS3RS1.LOGRS1 RS Group #2 RS_PDU_STORE_DATA2 MHS3RS2.PDURS2 RS_PDU_STORE_LOG2 MHS3RS2.
PAGE 400
Examples of Configuration Files OSI/MHS Configuration Command File for MTA3 OSI/MHS Configuration Command File for MTA3 The source code for this example is provided in the file EXCFMTA3. ============================================================= == SCF CONFIGURATION file for MTA 3 == PRMD: DEVICEIND == ORG-NAME: MANUFACTURING == Many attribute values shown here are defaults. They == are shown for clarification/education purposes == only.
PAGE 401
Examples of Configuration Files OSI/MHS Configuration Command File for MTA3 ACCT-SUBMIT-RECIP-INFO ON, & ACCT-DELIVER-RECIP-INFO ON, & ACCT-RELAY-RECIP-INFO ON, & ACCT-GEN-RECIP-INFO ON, & ACCT-UNROUTE-RECIP-INFO ON ============================================================= ============================================================= == ADD CLASS. ============================================================= == Add CLASS MESSAGE RELAY #MR.
PAGE 402
Examples of Configuration Files OSI/MHS Configuration Command File for MTA3 == Add MESSAGE RELAY GROUP #MR.MRGRP2. == ADD GROUP #MR.MRGRP2, & CPU 1, & BACKUP 2, & PRI 130, & PDU-STORE MHS3MR2.PDUMR2, & PDU-LOG-FILE MHS3MR2.LOGMR2, & WORK-SV MHS3MR2, & RTS-PNAME $MHS3.#R32, & MRP-PNAME $MHS3.#M32, & SC-PNAME $MHS3.#S32, & MR-T-SELECTOR 4D5258323541, & MR-NSAP 703285003230 ============================================================= == Add MESSAGE RELAY GROUP #MR.MRGRP3. == ADD GROUP #MR.
PAGE 403
Examples of Configuration Files OSI/MHS Configuration Command File for MTA3 WORK-SV MHS3MS1, & MS-PNAME $MHS3.#I31, & MSG-STORE-SV MHS3MS1, & MR-COUNT SYS ============================================================= == Add MESSAGE STORE GROUP #MS.MSGRP2. == ADD GROUP #MS.MSGRP2, & CPU 2, & BACKUP 1, & PRI 130, & PDU-STORE MHS3MS2.PDUMS2, & PDU-LOG-FILE MHS3MS2.LOGMS2, & WORK-SV MHS3MS2, & MS-PNAME $MHS3.
PAGE 404
Examples of Configuration Files RS-PNAME RS-T-SELECTOR RS-NSAP OSI/MHS Configuration Command File for MTA3 $MHS3.#V31, 5253583235, 703285003231 & & ============================================================= == Add REMOTE SERVICES GROUP #RS.RSGRP2. == ADD GROUP #RS.RSGRP2, & CPU 1, & BACKUP 0, & PRI 130, & PDU-STORE MHS3RS2.PDURS2, & PDU-LOG-FILE MHS3RS2.LOGRS2, & WORK-SV MHS3RS2, & RS-PNAME $MHS3.
PAGE 405
Examples of Configuration Files ADMD PRMD ORG-NAME ORG-UNIT-1 SUR-NAME GIVEN-NAME OSI/MHS Configuration Command File for MTA3 TELENET, DEVICEIND, MANUFACTURING, MSUSERS, Chapman, Graham ADD APPL #CleeseJohn, ACCESS-TYPE ACCESS-NAME USER-PASSWORD ISO-COUNTRY-NAME ADMD PRMD ORG-NAME ORG-UNIT-1 SUR-NAME GIVEN-NAME MS, MSGRP2, UAMS21, US, TELENET, DEVICEIND, MANUFACTURING, MSUSERS, Cleese, John ADD APPL #GilliamTerry, ACCESS-TYPE ACCESS-NAME USER-PASSWORD ISO-COUNTRY-NAME ADMD PRMD ORG-NAME ORG-UNIT-1 SUR
PAGE 406
Examples of Configuration Files OSI/MHS Configuration Command File for MTA3 REM-MAX-MSG-LEN 2097152, & REM-LOCAL-INIT ON, & REM-REMOTE-INIT ON, & REM-TSELECTOR-1 4D5258323541, & REM-NSAP-1 703285003020, & LOC-TSELECTOR-1 4D5258323541, & LOC-NSAP-1 703285003230, & REM-MTA-NAME MTA2, & REM-ADMD TELENET, & REM-PRMD DEVICEIND, & ISO-COUNTRY-NAME US, & X121-COUNTRY-NAME 310, & COUNTRY-NAME UNITEDSTATESOFAMERICA ============================================================= ======================================
PAGE 407
Examples of Configuration Files OSI/MHS Configuration Command File for MTA3 REM-LOGON-VALIDATION ON, & REM-OUR-PASSW MTA3, & REM-THEIR-PASSW MTA1, & REM-APPLIC-CONTEXT MTS-TRANSFER, & REM-DIALOGUE-MODE MONOLOGUE, & REM-MAX-MSG-LEN 2097152, & REM-LOCAL-INIT ON, & REM-REMOTE-INIT ON, & REM-TSELECTOR-1 4D5258323542, & REM-NSAP-1 373033323835303033303132, & LOC-TSELECTOR-1 4D5258323541, & LOC-NSAP-1 703285003230, & REM-MTA-NAME MTA1, & REM-ADMD TELENET, & REM-PRMD DEVICEIND, & ISO-COUNTRY-NAME US, & X121-COUN
PAGE 408
Examples of Configuration Files OSI/MHS Configuration Command File for MTA3 ============================================================= == Add ROUTE 4 GOING TO MTA2 VIA MTA1. == ADD ROUTE #MTA1.
PAGE 409
Examples of Configuration Files Overview of the OSI Configuration for MTA3 Overview of the OSI Configuration for MTA3 The OSI services connections for MTA3 are as follows: MTA 3 Configuration - OSI Stack connections RSGRP1 MRGRP1 MRGRP3 RSGRP2 MRGRP2 MRGRP4 | | | X25 | |X25 |LAN | | | | | | _|______________|___________|_____________ | OSI Stack | | TAPS $WAS1 OSIMGR $WOSI1 | | TSP $WTS1 | |_________________________________________| | | | | $LAM2 $SX1 Note: $SX1 is connected to a X.25 switch.
PAGE 410
Examples of Configuration Files Overview of the OSI Configuration for MTA3 MTA3 to MTA1 connection: 1980 mode SNPA 12 NSAP 373033323835303033303132 TSEL 4D5258323542 <"MRX25B"> OSI/MHS Configuration and Management Manual—424827-003 A -56
PAGE 411
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA3 OSI/AS and OSI/TS Configuration Command File for MTA3 The source code for this example is provided in the file EXASMTA3. ============================================================= == == == This is a sample OSI/AS and OSI/TS (stack) == == configuration file. It defines the OSI/AS OSI/TS == == addresses that correspond to OSI/MHS MTA3.
PAGE 412
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA3 ============================================================= ASSUME PROCESS $WOSI == assign X.25 IOPs ADD #NSP.X25A, NAME $SX1 == assign LAN IOP ADD #NSP.LAM1, NAME $LAM1 == define TSP ADD #TSP.WTS1, NAME $WTS1, CPU 1, BACKUPCPU 0, & CODEFILE TSPOBJ == define TAPS ADD #TAPS.WAS1, NAME $WAS1, CPU 1, BACKUPCPU 0, & CODEFILE TAPSOBJ == Start TSP and TAPS PARAM TSP^PROTO^ID ON START PROCESS #TSP.WTS1 START PROCESS #TAPS.
PAGE 413
Examples of Configuration Files == == OSI/AS and OSI/TS Configuration Command File for MTA3 MRGRP3 and MRGRP4 RSGRP1 and RSGRP2 LAN X.25 normal ============================================================= == MRGRP1 and MRGRP2 listen on same X.25 normal address ============================================================= == Define MRGRP1 ADD ENTRY #APPL.MRGRP1, TSEL 4D5258323541, NSAP 703285003230 ADD ENTRY #TSEL.4D5258323541 , SERVER $WOSI.#TAPS.WAS1 ADD ENTRY #NSAP.703285003230, SERVER $WOSI.#TSP.
PAGE 414
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA3 == Same address as MRGRP1 ============================================================= ============================================================= == MRGRP3 and MRGRP4 listen on same LAN address ============================================================= == Define MRGRP3 ADD ENTRY #APPL.MRGRP3, TSEL 4D524C414E, & NSAP 49000108008E00035502 ADD ENTRY #TSEL.4D524C414E, SERVER $WOSI.#TAPS.WAS1 ADD ENTRY #NSAP.
PAGE 415
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA3 == Same address as RSGRP1 ============================================================= ============================================================= == Define remote addresses for adjacent MTAs (MTA1 and == == MTA2) == ============================================================= == Define MTA1 ADD ENTRY #APPL.MTA1, TSEL 4D5258323542, & NSAP 3730323835303033303132 ADD ENTRY #TSEL.4D5258323542, SERVER $WOSI.#TAPS.
PAGE 416
Examples of Configuration Files OSI/AS and OSI/TS Configuration Command File for MTA3 OSI/MHS Configuration and Management Manual—424827-003 A -62
PAGE 417
B Configuration Checklists This appendix contains checklists that you can use when planning your OSI/MHS subsystem configuration.
PAGE 418
Configuration Checklists • Configuring closed user groups • • CUG object CUGMEMBER object You may want to make copies of these checklists to help you configure your subsystem. These lists are not comprehensive. See the OSI/MHS SCF Reference Manual for complete descriptions of all the attributes affecting OSI/MHS objects.
PAGE 419
Configuration Checklists Describing Your OSI/MHS Subsystem Describing Your OSI/MHS Subsystem You describe your OSI/MHS subsystem through the SUBSYS object, the MR CLASS object, and the MR GROUP object.
PAGE 420
Configuration Checklists Describing Your OSI/MHS Subsystem Time for a normal message? _______________________________________ Time for an urgent message? ______________________________________ Time for a nonurgent message? ____________________________________ Time for a report? _______________________________________________ What is the size of each data packet sent by the RTS?______________________ Do you want a specific time at which the store cleaner is to run? ______________ Is CUG checking enabled? _
PAGE 421
Configuration Checklists Describing an Adjacent MTA Describing an Adjacent MTA You describe an adjacent MTA through the MTA object and the MR class.
PAGE 422
Configuration Checklists Describing an Adjacent MTA What is the OSI address of this adjacent MTA (minimum required is NSAP)? Rem-P-selector? ________________________________________________ Rem-S-selector? ________________________________________________ Rem-T-selector? ________________________________________________ Rem-NSAP? ___________________________________________________ What is the OSI address of your subsystem (minimum required is NSAP)? Loc-P-selector? __________________________________________
PAGE 423
Configuration Checklists Planning Routing Criteria for Adjacent and Nonadjacent MTAs Planning Routing Criteria for Adjacent and Nonadjacent MTAs You need to determine the routes for users or sets of users on different systems. To do this, you plan routing criteria for adjacent and nonadjacent MTAs for these users through the ROUTE object.
PAGE 424
Configuration Checklists Configuring a General User Gateway Configuring a General User Gateway You configure a general user gateway through the following objects: • • GATEWAY object GI CLASS object The following questions describe GATEWAY object attributes: Is this gateway a 1984 or a 1988 implementation? _________________________ Do you want the OSI/MHS subsystem to check validation information before transferring the message to the gateway? What are the entry manager process names? (You can have from
PAGE 425
Configuration Checklists Configuring a Transfer Gateway Configuring a Transfer Gateway You configure a Transfer gateway through the GATEWAY object.
PAGE 426
Configuration Checklists Configuring a Transfer Application Configuring a Transfer Application You configure a Transfer application through the APPL object of the GW type. When using the Transfer X400 gateway, the country name, ADMD name, and PRMD name must be the same as yours. The only question you need consider about the gateway APPL object is: What is your node name? ____________________________________________ (This is your organization unit name.
PAGE 427
Configuration Checklists Configuring a Remote User Agent Configuring a Remote User Agent You configure a remote user agent through the following objects: • • • APPL object of the MS type MS CLASS object RS CLASS object The following questions describe the O/R name attributes of the APPL object.You must be specific enough to make this APPL object unique from all others. What is the country name? (Only specify if different from yours.
PAGE 428
Configuration Checklists Configuring a Local User Agent Configuring a Local User Agent You configure a local user agent through the following objects: • • • APPL object of the MS type MS CLASS object LO CLASS object The following questions describe the O/R name attributes of the APPL object. You must be specific enough to make this APPL object unique. What is the country name? (Only specify if different from yours.)______________ What is the ADMD name? (Only specify if different from yours.
PAGE 429
Configuration Checklists Configuring a Distribution List Configuring a Distribution List You configure a distribution list through the following objects: • • DLIST object DLISTMEMBER object The following questions describe the O/R name attributes of the DLIST object. You must be specific enough to make this DLIST object unique from all others. What is the country name? (Only specify if different from yours.)______________ What is the ADMD name? (Only specify if different from yours.
PAGE 430
Configuration Checklists Configuring a Closed User Group Configuring a Closed User Group You configure a closed user group through the following objects: • • CUG object CUGMEMBER object The following questions describe the attributes of the CUG object. What is the name of the closed user group? ______________________________ Are content-type checks to be performed? _______________________________ If so, what are the content types allowed?_____________________________ No.
PAGE 431
C Mailbox Save and Restore Utilities This appendix describes the two utility programs that are used to save and restore the contents of an MS APPL object’s mailbox. The term “mailbox” is used to refer to the messages contained in an individual MS APPL object’s message store. SAVEMBOX saves a specified mailbox to a named save file.
PAGE 432
Mailbox Save and Restore Utilities SAVEMBOX basis of which the user will retrieve or filter messages from the message store. You specify them when you define the APPL object for the user.) SAVEMBOX SAVEMBOX stores a specified mailbox in a specified mailbox save file.
PAGE 433
Mailbox Save and Restore Utilities SAVEMBOX Operation verbose is used to switch on a verbose mode of operation, in which SAVEMBOX sends a number of text messages (to the OUT file) that detail its operation. This parameter has possible values of ON (verbose) and OFF (nonverbose). The default is OFF. This parameter is optional. It is best to specify a disk file or spooler location as the OUT file, in case you need to provide it in connection with a problem report.
PAGE 434
Mailbox Save and Restore Utilities SAVEMBOX Examples SAVEMBOX Examples This example illustrates the RUN SAVEMBOX command without the VERBOSE option: COMM 1> SAVEMBOX APPL=$ZD1.#UAMS11 INSTALL-SV=$LOGICE.DJOSIMHS SAVEFILE=FOO MAXEXTENTS 200 & & SAVEMBOX - MHS - T6990022 - 30APR95 - D22 SAVEMBOX Saving APPL $ZD1.
PAGE 435
Mailbox Save and Restore Utilities RESTMBOX RESTMBOX RESTMBOX restores a specified mailbox from a specified mailbox save file. The syntax for RESTMBOX is: [RUN] RESTMBOX [/run-options/] APPL=appl-name & SAVEFILE=mailbox-save-file & INSTALL-SV=installation-sv & [MODE=RESTORE|APPEND] & [VERBOSE=OFF|ON] run-options are the standard options allowed for the RUN command as defined in the TACL Reference Manual. Note that the IN option is not applicable since this program does not read any input.
PAGE 436
Mailbox Save and Restore Utilities RESTMBOX Operation It is best to specify a disk file or spooler location as the OUT file, in case you need to provide it in connection with a problem report. Note that a single equals (=) sign must exist between parameter keywords and parameter values and that no spaces are allowed on either side of the equal sign. The only delimiter allowed between parameters is a space.
PAGE 437
Mailbox Save and Restore Utilities RESTMBOX Examples RESTMBOX does no validation of a saved and restored APPL O/R name. If messages are saved from an APPL object that has one O/R name and restored to an APPL object that has a different O/R name, no warning message is issued. RESTMBOX Examples This example illustrates the RUN RESTMBOX command without the VERBOSE option: COMM 5> RESTMBOX APPL=$ZD1.#UAMS13 INSTALL-SV=$LOGICE.
PAGE 438
Mailbox Save and Restore Utilities Errors and Error Recovery Errors and Error Recovery When a SAVEMBOX error occurs, SAVEMBOX stops processing and issues an error message. Check the error message, correct the problem, then run SAVEMBOX again. Be sure to delete any partially created mailbox save file that might exist. When a RESTMBOX error occurs, RESTMBOX stops processing and issues an error message. Check the error message, correct the problem, then run RESTMBOX again.
PAGE 439
Mailbox Save and Restore Utilities Errors and Error Recovery (0102) could not lock MS PDU. The following errors are defined for RESTMBOX only. (0200) mailbox-save-file corrupted. The specified mailbox save file is corrupted. Determine the reason for corruption, correct the problem, and retry the command. (0201) mailbox not empty. An attempt was made to run RESTMBOX in RESTORE mode to a non-empty mailbox. Specify an empty mailbox and retry RESTMBOX in RESTORE mode. (0202) mailbox-save-file does not exist.
PAGE 440
Mailbox Save and Restore Utilities Errors and Error Recovery OSI/MHS Configuration and Management Manual—424827-003 C -10
PAGE 441
D OSI Address Configuration in OSI/MHS This appendix describes how to configure the OSI addresses in an OSI/MHS subsystem to allow connections to other NonStop™ MTAs and MTAs from different vendors. OSI addressing is a complex area in an X.400 environment. Much of this complexity is due to the flexibility that is allowed in configuring OSI/MHS subsystems.
PAGE 442
OSI Address Configuration in OSI/MHS Configuring the OSI Stack and OSI/MHS in One File c. Purge and recreate the Management Information Base (MIB). d. Start the OSI manager. 2. Configure the common PROCESS section. a. Define the X25 and LAN processes (lines). b. Define the NSP, TSP, and TAPS processes. c. Start the TSP and TAPS processes. 3. Configure the common PROFILE section. a. Configure Layer 4 service characteristics for TSP processes. b. Configure Layer 5 service characteristics for TAPS processes.
PAGE 443
OSI Address Configuration in OSI/MHS MR-T-SELECTOR MR-NSAP Configuring the OSI Stack and OSI/MHS in Separate Files 4D5258323541, 703285003011 & == OSI stack configuration for MRGRP1 add entry #tsel.4D5258323541, server $uosi.#taps.uas1 add entry #nsap.703285003011, & server $UOSI.#TSP.UTS1, & profile $UOSI.#L4.L4WAN, & snpa 11, & netaddr-mode normal add entry #snpa.11, server $uosi.#nsp.x25a, profile $uosi.#L3.mta1proA == #L3 profile for X.25 connection add profile #L3.
PAGE 444
OSI Address Configuration in OSI/MHS Configuring the OSI Stack and OSI/MHS in Separate Files c. Purge and recreate the Management Information Base (MIB). d. Start the OSI manager. 2. Configure the common PROCESS section. a. Define the X.25 and LAN processes. b. Define the NSP, TSP, and TAPS processes. c. Start the TSP and TAPS processes. 3. Configure the common PROFILE section. a. Configure Layer 4 service characteristics for TSP processes. b. Configure Layer 5 service characteristics for TAPS processes.
PAGE 445
OSI Address Configuration in OSI/MHS Address Requirements for OSI/MHS x25destaddr '703285003231', X25remotenet X25xa, & x25negotiate (L3window,pktsize,thruput), x25port 31 This command is from the OSI/MHS configuration file: == OSI/MHS configuration for RSGRP1 ADD GROUP #RS.RSGRP1, CPU BACKUP PRI PDU-STORE PDU-LOG-FILE WORK-SV RS-PNAME RS-T-SELECTOR RS-NSAP 2, 1, 130, MHS3RS1.PDURS1, MHS3RS1.LOGRS1, MHS3RS1, $MHS3.
PAGE 446
OSI Address Configuration in OSI/MHS Address Requirements for OSI/MHS Figure D-1 shows how these addresses are used. Figure D-1.
PAGE 447
OSI Address Configuration in OSI/MHS SCF Commands Used to Configure OSI and MHS The 1980 version of X.25 does not contain the addressing extensions to carry the NSAP address in the OSI network layer, and therefore the NSAP address is derived from the X.25 NUA. The 1984 version of X.25 has the necessary addressing extensions, and therefore the NSAP address can be carried in the X.25 call request packet and be independent of the X.25 NUA. This appendix emphasizes the requirements for addressing in an X.
PAGE 448
OSI Address Configuration in OSI/MHS Address Notation Thus, there are three groups of SCF addresses—the MR- addresses, the LOCaddresses and the REM- addresses—that have to be defined both to OSI/MHS and to the OSI Manager process. Between them they define all six addresses used in an MTA connection; some of these SCF commands define more than one OSI address simultaneously. Note. Only five of the six addresses are defined, because OUT(R) is not validated and can take any value.
PAGE 449
OSI Address Configuration in OSI/MHS Configuring the Remote Addresses The example below illustrates some of the commands needed to define IN(D). An example of a complete set of commands appears in Putting It All Together on page D-11. This list is only an indication of the main commands that are used: ADD GROUP #MR., ... MR-T-SELECTOR , MR-NSAP & & ADD ENTRY #TSEL., PROFILE ..., SERVER ... ADD ENTRY #NSAP., L4PROFILE ..., SERVER ...,& SNPA ...
PAGE 450
OSI Address Configuration in OSI/MHS Configuring the Remote Addresses OUT(D) is defined in the OSI stack commands associated with the REM-address parameters of the ADD MTA command, as shown in the following list: ADD MTA #, ... REM-TSELECTOR1 , REM-NSAP1 & & ADD ENTRY #TSEL. ADD ENTRY #NSAP., L4PROFILE, L3PROFILE ... The ADD ENTRY #NSAP command is the same command used in the definition of OUT(S), above.
PAGE 451
OSI Address Configuration in OSI/MHS Putting It All Together Putting It All Together Figure D-2 illustrates schematically a complete OSI/MHS local and adjacent MTA configuration for an X.25 (1980) connection. The figure shows only those fragments of commands that relate to address configuration, and the relationships between these commands. Figure D-2. Complete Address Configuration ADD GROUP #MR., & MR-TSELECTOR , MR-NSAP ADD ENTRY #TSEL.
PAGE 452
OSI Address Configuration in OSI/MHS Putting It All Together The complete set of OSI addresses defined by this configuration is as follows: Outgoing associations: Local (source) TSEL: Local (source) NUA: Remote (destination) TSEL: Remote (destination) NUA: Incoming associations: Local (destination) TSEL: Local (destination) NUA: Remote (source) TSEL: Remote (source) NUA: Some
PAGE 453
OSI Address Configuration in OSI/MHS A Sample Configuration Any of these terms may be set to any desired convenient value. The value used will have no influence on the ultimate OSI connection. However, it is often convenient to use values that are related to those used in the OSI connection. One point to note, in particular, about Figure D-2 is how the REM-NSAP-n parameter of the ADD MTA command defines not only , but also, indirectly, both and .
PAGE 454
OSI Address Configuration in OSI/MHS Local MR Group Address Configuration pri 170, & pdu-store $stafed.mhsmrdb.pdumr1, & pdu-log-file $stafed.mhsmrdb.logmr1, & work-sv $stafed mhsmrdb, & rts-pname $zmhs.art1, & mrp-pname $zmhs.amr1, & sc-pname $zmhs.asc1, & sc-pri 140, & mr-t-selector 313131, & mr-nsap 3233343232333530303136313031 == ********** Add OSI address entries for IN(D) ************ == Note: the same entries are used for OUT(S) in this == example.
PAGE 455
OSI Address Configuration in OSI/MHS Adjacent MTA Address Configuration networks, the #SNPA entry also defines a #L3 profile, which can be used to specify various parameters for incoming connections to the X.25 network layer. The #L3 profile defines a port number, which will be used to listen for incoming X.25 calls. It can also include such parameters as whether packet-size negotiation or reverse charging are allowed.
PAGE 456
OSI Address Configuration in OSI/MHS Adjacent MTA Address Configuration loc-nsap-1 3233343232333530303136313031, & rem-applic-context MTS-TRANSFER == ***** Add OSI address entries for OUT(D) and IN(S) ****** == In this example the entries defined for IN(D) in "Local == MR Group Address Configuration" are reused for OUT(S). ADD ENTRY $zosi.#TSEL.4D4853415431 ADD ENTRY $zosi.#NSAP.333131303432313030303931323036, & L3PROFILE $zosi.#L3.Carl1, & L4PROFILE $zosi.#L4.
PAGE 457
OSI Address Configuration in OSI/MHS Advanced Addressing Configurations Remote NSAP The #NSAP entry for the REM-NSAP-1 parameter of the ADD MTA command () defines a #L4 profile and a #L3 profile. The #L3 profile defines the X.25 NUA of the adjacent MTA and also the subaddress that will be used in the X.25 calling address for outgoing connections.
PAGE 458
OSI Address Configuration in OSI/MHS Different Incoming Calling Address and Outgoing Called Address For example, if the PROFILE command is replaced by the one below, the effect will be to change OUT(S) while leaving all other addresses unchanged. ADD PROFILE $zosi.#L3.Carl1, & X25DESTADDR "311042100091206" , X25PORT 02 New value of OUT(S) OUT(S): t-selector = 313131 X.
PAGE 459
OSI Address Configuration in OSI/MHS Different Incoming Calling Address and Outgoing Called Address The most likely way in which these addresses differ is in the NSAP component; that is, differs from . There is a simple way to achieve this effect when using 1980 X.25. The addresses can be configured by setting the REM-NSAP- parameter on the ADD MTA command to , and setting the X25DESTADDR parameter, on the ADD PROFILE command, to .
PAGE 460
OSI Address Configuration in OSI/MHS Use of SSEL and PSEL Addresses Use of SSEL and PSEL Addresses The configurations shown in the examples can easily be extended to use SSEL and PSEL addresses. In the ADD GROUP #MR command, these addresses are included in the definition of IN(D). Here is an example: ADD GROUP $zmhs.#mr.
PAGE 461
E Routing in OSI/MHS OSI/MHS Routing Principles OSI/MHS gives you many options for determining how messages are routed through your network. These routing options are consistent with general rules and guidelines defined by implementors’ groups and standards bodies. No group defines absolute rules for routing, and existing guidelines are not very specific. Here are some terms related to routing: • • • • A route is a specific path through a message handling system.
PAGE 462
Routing in OSI/MHS OSI/MHS Routing Principles Figure E-1. Routing Within a Domain Country A ADMD 1 MTA PRMD 1 Route 2 GW MTA Route 1 MS UA MTA1 Route 3 Country B PRMD 2 MTA MTA MTA VST 039.VSD Routes must be defined at each MTA to determine where the MTA will send messages for any possible recipients. You define routes using SCF or a management application; for each route, you define the recipient or set of recipients to be reached by the route.
PAGE 463
Routing in OSI/MHS Basic Routing Components and Logic In Figure E-1 there are three routes from MTA 1: • Route 1 is for users on a different MTA but still part of the same PRMD. In this situation, additional routing criteria (such as organization name, organizational unit name, or domain-defined attributes) are required.
PAGE 464
Routing in OSI/MHS Network Types and Routing Requirements The routing table is a finite state machine-like table containing the rules for searching the database. The rules cover all of the following cases and vary according to which O/R name attributes are present: • • • • O/R name form: X.121 O/R name form: numeric O/R name form: mnemonic Interdomain routing (to another MTA) Note that any name form can result in interdomain routing. (For more information about X.400 name forms, see X.
PAGE 465
Routing in OSI/MHS Network Types and Routing Requirements Here are some examples of possible O/R name attributes for a configuration that has five message-store users, a gateway for X.121, and one adjacent MTA. In the list below, C is country name, A is ADMD name, P is PRMD name, O is organization name, U is organizational unit name, P is personal name, D is domain-defined attribute, and x is X.121 address. The hyphen (-) means that no value is specified.
PAGE 466
Routing in OSI/MHS Network Types and Routing Requirements Figure E-2. Routing by O/R Name yes X.
PAGE 467
Routing in OSI/MHS Trace Information and Internal Trace Handling Trace Information and Internal Trace Handling OSI/MHS handles external and internal trace information as described in the 1988 X.400 recommendations (Blue Book, Recommendation X.411). Internal trace information is added to a message every time a route retry is attempted. This action results in an increase in the size of the message with successive retries.
PAGE 468
Routing in OSI/MHS Underspecified and Overspecified O/R Names Underspecified Names OSI/MHS can route underspecified messages to local recipients in the same domain. For example, if a message is received for user Fred Bloggs (Surname Bloggs, Given Name Fred) in the local domain, and the corresponding APPL object has been added as Fred Bloggs Jr (Surname Bloggs, Given Name Fred, Qualifier Jr), the message is still routed to that APPL, if it is unique. (If another APPL identifies Fred Bloggs S.
PAGE 469
Routing in OSI/MHS Routing Rules Defined by NIST and X.400 This scheme works well for most O/R names, but in some cases it can result in large sequential disk searches. For example, if all users had the same organization name and a message arrived with that organization name and domain-defined attribute 2, a search would be made of all the records until the right one was discovered. OSI/MHS does not attempt to match part of a field. For instance, Fred Bloggs does not match Frederick Bloggs.
PAGE 470
Routing in OSI/MHS Route and Link Retry Logic OSI/MHS Configuration and Management Manual—424827-003 E -10
PAGE 471
F Routing Support for O/R Names Containing Teletex Attributes The teletex character set is an extended alphabet for use in international text communication. In addition to the standard ASCII character set, the teletex character set includes accents and umlauts (diacritical marks) applied to Latin characters, as well as a number of special alphabetical combinations such as IJ ligatures.
PAGE 472
Routing Support for O/R Names Containing Teletex Attributes How a Message Store Processes an MPDU Containing Teletex Attributes How a Message Store Processes an MPDU Containing Teletex Attributes If a message store is the recipient of an MPDU containing teletex O/R name attributes, the message store processes the MPDU as follows: • • It stores the MPDU’s O/R name attributes in its SQL database, placing each teletex value in the field that normally holds the corresponding printable value.
PAGE 473
Routing Support for O/R Names Containing Teletex Attributes EMS Messages 8. To retrieve the message, the owner of the mailbox could specify either the printable form of the common name O/R attribute (common-name) or the teletex form (teletex-common-name). EMS Messages All event messages that contain tokens for O/R name components have been expanded to contain new tokens for corresponding teletex O/R name tokens.
PAGE 474
Routing Support for O/R Names Containing Teletex Attributes Downgrading Downgrading OSI/MHS follows the CCITT Recommendation X.419, Appendix B, Section B.2.8 with respect to downgrading of O/R attributes for relay to 1984 systems. • • If the O/R address contains both a teletex string attribute and the corresponding printable string attribute, the teletex string is discarded.
PAGE 475
Routing Support for O/R Names Containing Teletex Attributes The Conversion Table Table F-1.
PAGE 476
Routing Support for O/R Names Containing Teletex Attributes The Conversion Table Table F-1.
PAGE 477
Routing Support for O/R Names Containing Teletex Attributes The Conversion Table Table F-1.
PAGE 478
Routing Support for O/R Names Containing Teletex Attributes OSI/MHS Configuration and Management Manual—424827-003 F-8 The Conversion Table
PAGE 479
G Remote Duplicate Database Facility (RDF) Support The Remote Database Facility (RDF) product allows customers who have computer systems at multiple sites to safeguard their OSI/MHS transactions and database if disaster strikes at a particular location. When customers use RDF, an alternate site can take over from the damaged site in minutes or seconds, thus avoiding a lengthy resource outage.
PAGE 480
Remote Duplicate Database Facility (RDF) Support Installing the RDF Subsystem Installing the RDF Subsystem RDF must be installed on both the primary and backup HP NonStop™ systems. HP distributes RDF/IMP and RDF/IMPX software on an independent product release compact disk (CD). The Readme file on the CD gives complete instruction on how to install these product, as does the latest version of the Compaq NonStop™ RDF/IMP and IMPX System Management Manual in the Independent Product TIM collection.
PAGE 481
Remote Duplicate Database Facility (RDF) Support Performing Disaster Recovery 8. The tables for each MS subvolume must be copied from the primary to the backup system. Before doing this, use FUP SECURE to change the security permissions of the tables to “nnnn”, Then, use the SQLCI command to copy the tables: > SQLCI>Dup\primary-system.MS-subvol.??? Where SQL, & > \backup-system.MS-subvol.*, & > Catalog \backup-system.MS-subvol, Saveall > Use FUP SECURE to resecure the tables on both systems. 9.
PAGE 482
Remote Duplicate Database Facility (RDF) Support Performing Disaster Recovery The optional NAME parameter of the TACL RUN command specifies a processname for the PDUDIAG process. PARAM DB-SUBVOL [dbvol]dbsubvol RUN PDUGDIAG [/NAME process-name/]ZMHS RDF 4. Start the OSI/MHS backup subsystem.
PAGE 483
Glossary The following glossary defines terms used in this manual and in other OSI/MHS manuals. Both industry-standard terms and HP terms are included. This list covers HP OSI/MHS as a whole; therefore, not all terms given here are used in this particular manual. abstract syntax. A representation of the way in which components of information are to be specified in a communication.
PAGE 484
Application Layer. Layer 7 of the OSI Reference Model. This layer provides the interface between user programs (application processes) and the OSI network. Layer 7 includes the standards for services such as file transfer, electronic mail, and terminal access. archive queue. A queue to which you can move an object from the input queue during a finish-transfer-in operation requested of the GPI.
PAGE 485
attribute position. In the GPI, the position of an attribute in an object. attribute syntax. The form of an attribute value. It may be string, Boolean, enumeration, integer, or object. attribute type. In general, an element defining the form or range of a value. In the GPI, a name suggesting the kind of information a value represents: for instance, MH-T-COUNTRY-NAME. See also attribute syntax. attribute value. The data for specific instance of an attribute.
PAGE 486
client. An application or program that uses another software component, typically called a “service” or a “server.” For instance, a GPI client uses the GPI service. The XAPIA specifications use the term “client application.” closed user group. See CUG. collector. An EMS process that accepts event messages from subsystems and logs them in the event log. See also distributor. command file. An EDIT file that contains sequences of commands. Sometimes called an OBEY file. command message.
PAGE 487
configuration file. An SCF command file that contains all the configuration information about one subsystem. See also OSI/MHS subsystem. configured object. An object whose characteristics have been defined to OSI/MHS through SCF or a management application. See also nonconfigured object. confirm primitive. In OSI, a primitive issued when a service user is to be informed about its request. This is one of four types of service primitives. See also service primitive. connection.
PAGE 488
data communications standard definitions. In DSM, the set of declarations provided by HP for use in all management applications that manage or retrieve event messages from HP NonStop data communications subsystems. The names of these definitions start with either ZCOM or ZCMK. See also definition files, SPI standard definitions, or EMS standard definitions. Data Link Layer. Layer 2 in the OSI Reference Model.
PAGE 489
distribution list. A list of users to whom it is possible to address messages collectively. The distribution list name logically represents the names of all members of the list. OSI/MHS and Transfer both support distribution lists. DLIST object. An object type, used in OSI/MHS management interfaces, that identifies a local distribution list within the OSI/MHS subsystem. DLISTMEMBER object.
PAGE 490
entry manager process. A queue manager process that you must specify when configuring the Transfer X400 gateway. You can specify up to five entry manager processes. envelope. The part of a message that contains information needed to transfer the message and to deliver it to its intended recipients.
PAGE 491
error token. In DSM programmatic interfaces, a token in a response message that indicates the reason an error occurred in performing a programmatic command. HP NonStop subsystems enclose each error token in an error list, which can also contain additional information about the error. A response record must contain a return token and can also contain error lists to explain the error further. event. In DSM, a significant change in some condition in the system or network.
PAGE 492
extension. In X.400, an element of service that was defined in the 1988 recommendations but was not present in the 1984 recommendations. Some 1988 extensions are explicitly supported by the GPI, whereas others are not. Those that are supported are represented by explicit attributes in the GPI. The extensions that are not explicitly supported by the GPI are made available as BER-encoded data; GPI objects that include unsupported extensions contain one or more instances of the MH-CEXTENSIONS class.
PAGE 493
GATEWAY object. An object type, used in OSI/MHS management interfaces, that defines and controls the Transfer X400 gateway or a gateway application based on the Gateway Programmatic Interface (GPI). GI (gateway interface) class. The OSI/MHS CLASS object that identifies the set of all GI groups in an OSI/MHS subsystem. GIP (Gateway Interface Process) . The server that moves messages between a proprietary message system and OSI/MHS. An application, or “client” uses the GPI library for access to the GIP.
PAGE 494
indication primitive. In OSI, a primitive issued when a service user is to be informed about an event. This is one of four types of service primitives. See also service primitive. input queue. A queue on which the GPI service places messages, probes, and reports received from the X.400 network to be accessed by a client gateway application. Install program. The HP program that installs new or updated software on the system from SUT tapes and creates the ISVs. installation file.
PAGE 495
exchange of goods and services and to develop mutual cooperation in areas of intellectual, scientific, technological, and economic activity. ISO Reference Model for Open Systems Interconnection. See OSI Reference Model. ISV (installation subvolume). A subvolume produced from the SUT during the Install process. The Install process creates many ISVs. The ISV named ZOSIMHS contains all of the OSI/MHS object files (MTA, RTS, SC, MS, RS, GI, LO, and MHSMGR), softdocs, and installation macros. LAN.
PAGE 496
local user agent. See LUA. logical MTA. All of the MR groups in an OSI/MHS subsystem.
PAGE 497
long string. In the GPI, a string that cannot be passed in an attribute descriptor but must be manipulated a segment at a time by using the GPI_OM_READ_ and GPI_OM_WRITE_ procedures. At GPI initialization, a client program specifies the maximum length string that can be passed in a descriptor. All strings longer than the specified maximum are long strings. LUA (local user agent). A process that submits and retrieves messages on behalf of a user, through a message store on the same system as the user agent.
PAGE 498
In X.400, an information object that consists of an envelope and its contents. The envelope identifies the originator and the potential recipient of the message and documents its path through the system. message store. The part of an MHS subsystem that provides capabilities for message storage. message transfer agent. See MTA. MHS (message handling system). A set of components providing for exchange of various types of information, such as interoffice memoranda, among correspondents in a network.
PAGE 499
MS (message store) class. The OSI/MHS CLASS object that identifies the set of all MS groups in an OSI/MHS subsystem. MS group. The OSI/MHS group that implements the message store-and-forward function. The MS group consists of a single MS process, an MS SQL catalog, an MS SQL database, and an MS PDU store. There can be zero, one, or more MS groups in a single OSI/MHS subsystem. MS process.
PAGE 500
node. In general, a system or device that follows the protocols of a specific network and that other systems or devices in that network can address. In Expand (the proprietary network for HP NonStop syestems), a computer system that is part of an Expand network of computer systems. A node address is designated by a symbol before the name (for example, \NY in file names or @NY in Transfer correspondent names). nonadjacent MTA. An MTA in the X.400 network that has no direct path to your OSI/MHS subsystem.
PAGE 501
NSAP address. The global, network-unique address of an end system’s network service access point, through which Network Layer services are provided to local users, and through which Transport Layer services are provided to remote systems. null object. An object type, used in management interfaces, that occurs when a subsystem supports exactly one object of a given type and the type of that object can be deduced from the name.
PAGE 502
might have the object type SU (subdevice). A subsystem identifies a set of object types for the objects it manages. The SCF interfaces to NonStop data communications subsystems use standard keywords to identify the types. The corresponding programmatic interfaces have object-type numbers (represented by symbolic names such as ZCOM-OBJ-SU) suitable for passing to the SPI SSINIT procedure. In the GPI, a category of objects having a common purpose and structure is called a “class.” octet.
PAGE 503
environment, under control of a specified MHS manager. There can be more than one OSI/MHS subsystem on a NonStop system. OSI/MHS subvolume. The subvolume that contains all files required by an OSI/MHS subsystem, such as executable object and configuration files. The MHS manager must always reside in this subvolume, but some of the other executable files can reside elsewhere, as defined by the MHS manager. OSI Reference Model.
PAGE 504
P3 protocol. The X.400 message submission and delivery protocol, which defines a standard for the submission and delivery of messages and the interaction of UAs and MTAs. P7 protocol. The X.400 protocol defining access to the message store by remote or local user agents. package. A set of GPI object classes that are grouped together because they are functionally related and defined in the same specification.
PAGE 505
subsystem implements, for LANs, the services of the Data Link Layer and layers below. PAM replaces the LAN Access Method (TLAM) for G06 and later RVUs. port address. For X25AM lines, the logical port number used to specify the address of the connection to the X.25 network. For TLAM lines, the address used by TLAM to specify the address of the connection to a LAN controller. Presentation Layer. Layer 6 in the OSI Reference Model.
PAGE 506
PROCESS object. An object type, used in OSI/MHS management interfaces, that defines a process to the OSI/MHS subsystem. You use the PROCESS object to trace and monitor OSI/MHS processes. programmatic command. In DSM, a command issued by a program rather than by a human operator. See also interactive command. programmatic interface. A mechanism by which a program can interact with other software. programmed operator.
PAGE 507
$RECEIVE. The name of a special file through which a process receives and optionally replies to messages from other processes. recipient. A person or application that receives a message from a message handling system. registration database. An OSI/MHS database that consists of three files: APPL, route, and adjacent MTA. reliable transfer service. See RTSE. remote MTA. An adjacent or nonadjacent MTA. Any MTA other than your local OSI/MHS subsystem. Remote Operations Service. See ROSE. remote system.
PAGE 508
contain error lists that include error tokens. A response can consist of multiple response records, spread across one or more response messages. result file. In the P7 API, a file used for retrieving results from the OSI/MHS subsystem. The file number is returned by a call to the LOS_OPEN_ procedure. See also send file. return token. In DSM programmatic interfaces, the token that indicates whether a command was successful and, if not, why it failed. The token code for the return token is ZSPI-TKN-RETCODE.
PAGE 509
RS (remote operations service) process. The process in the RS group that implements the ROSE protocol. The RS interfaces to the OSI/AS services, manages associations from RUAs, encodes and decodes messages, and creates and deletes PDUs in the MR or MS PDU stores as submit and retrieval operations are successfully completed. RS (remote operations service) group. The OSI/MHS group that implements the remote operations service, giving remote user agents access to an X.400 network through a message store.
PAGE 510
provides security features, version compatibility, support for tracing, and support for applications implemented as NonStop process pairs. segment. See string segment. selector. In OSI, an address component that refers to one or more service access points (SAPs) of the Transport, Session, or Presentation Layer and is used to establish and maintain connections. Remote systems and local users specify the selectors as part of an address called the “n-address.” See also SAP. send file.
PAGE 511
In the P7 API, an interaction between a client program and an LO group, established when a client program successfully calls the LOS_OPEN_ procedure. Once a session is established, the client program can request P7 operations by calling other P7 API procedures. A session is ended by calling the LOS_CLOSE_ procedure. session identifier. A designator generated by the GPI when the client program establishes a session and used by the program to indicate which session is requesting a GPI service.
PAGE 512
SPI procedures. In DSM, the set of operating system procedures used to build and decode buffers for use in system and network management and in certain other applications. These procedures are SSINIT, SSNULL, SSPUT, SSPUTTKN, SSGET, SSGETTKN, SSMOVE, and SSMOVETKN. SPI standard definitions. In DSM programmatic interfaces, the set of declarations available for use with the SPI procedures, regardless of the subsystem.
PAGE 513
subsystem. The software and/or hardware facilities that provide users with access to a set of communications services. In DSM, a program or set of processes that manages a cohesive set of objects. Each subsystem has a process through which applications can request services by issuing commands defined by that subsystem; in some cases, this process is the entire subsystem. Many subsystems also have interactive interfaces. See also OSI/MHS subsystem. Subsystem Control Facility. See SCF.
PAGE 514
summary state. In DSM interfaces to HP NonStop data communications subsystems, one of the generally defined possible conditions of an object, with respect to the management of that object. A summary state differs from a state in two ways. First, a summary state pertains only to the management of an object, whereas a state may convey other kinds of information about the object.
PAGE 515
teletex string. An extended alphabet for use in international text communication. In addition to the standard ASCII character set, the teletex character set includes accents and umlauts (diacritical marks) applied to Latin characters, as well as a number of special alphabetical combinations such as IJ ligatures. The teletex character set is based on CCITT recommendation T.61. terminal O/R address. An O/R address that identifies a user by a network address and, if required, a terminal type.
PAGE 516
Transfer. The HP NonStop proprietary messaging system, which supports communications among people, input/output devices, and processes. Transfer application. A set of processes that communicate with each other and with the Transfer subsystem and work together to perform a common task. Transfer X400 gateway. The application that allows Transfer correspondents to exchange packages with users on other host systems that support the international X.400 message-system standards. transport address. See TSAP.
PAGE 517
user message. An octet string, which can be of a standardized content type, such as IPM or EDI. A user message can contain one of a variety of encoded information types, such as text, facsimile, graphics, or voice. value. See attribute value. value position. The position of a value of a multivalued attribute. ViewPoint console application. An extensible interactive application for operators, provided as part of DSM. ViewPoint allows a system or a network to be controlled from a single terminal.
PAGE 518
X.400 message. Generic term that means a message, a probe, or report. XDIR server. A process that prescribes a specific mapping between X.400 O/R names and Transfer correspondent names and that also has access to the content of incoming and outgoing messages. The XDIR server is called by the importer and exporter processes of the Transfer X400 gateway.
PAGE 519
XAPIA (X.400 Application Program Interface Association). An organization active in defining and promoting standard programming interfaces for use in X.400 networks. $RECEIVE. The name of a special file through which a process receives and optionally replies to messages from other processes.
PAGE 520
OSI/MHS Configuration and Management Manual—424827-003 Glossary -38
PAGE 521
Index A ABORT command caution for CLASS objects 2-33 caution for MON object 2-56 description 2-16 Accounting Event performance implications 8-9 Accounting events in message tracking 9-31 ACTIVATE command 2-16 ADD command APPL object examples 2-29, 2-30 CLASS object examples 2-35 CUG object examples 2-36 CUGMEMBER object examples 2-38 description 2-16 DLIST object examples 2-40 DLISTMEMBER object examples 2-41 GATEWAY object examples 2-47 GROUP object examples 2-54 MTA object examples 2-63 ROUTE object examp
PAGE 522
Index B APPL objects (continued) example SCF commands 2-29/2-30 generic and specific types 2-29 message store (MS) ABORT and ADD notes 2-25/2-26 configuration checklist B-11/B-12 DELETE command caution 2-27 description 2-23 example configuration 5-7 example SCF commands 2-28/2-29 mailbox description C-1 STOP and SUSPEND notes 2-28 naming 2-25 SCF commands descriptions of 2-25/2-28 table of 2-17 states 2-23/2-25 verifying 7-13/7-14 Application characteristics performance tuning factors 8-4 Application requ
PAGE 523
Index C CLASS objects (continued) RS B-11 description 2-19, 2-30 example configuration 5-7 naming 2-32 SCF commands descriptions of 2-33/2-34 examples of 2-34/2-35 table of 2-17 states 2-31 types of (qualifying class names) 2-31 Cleaner interval 8-13 Closed user group (CUG) 2-35 performance implications 8-12 COLLECTOR parameter, PARAM command 6-4 Collectors, event See Event Management Service (EMS) COLLECTOR-1 parameter, PARAM command 6-4 Command files example for restarting the subsystem 6-13 example for
PAGE 524
Index C Configuring (continued) distribution list B-13 general user gateway B-8 local user agent B-12 OSI/MHS subsystem B-3/B-4 remote user agent (RUA) B-11 routing criteria for MTAs B-7 Transfer application B-10 Transfer X400 gateway B-9 components for 1-13 control and inquiry interfaces 2-8 example business, overview corporate network 5-1/5-3 description of format used 5-5/5-6 message flow 5-3/5-5 example files for MTA1 5-21 MTA2 5-14/5-17, 5-21, 5-27 MTA3 5-17 example objects for business APPL (GW) 5-6
PAGE 525
Index D D Data integrity, planning for 3-17 Databases closed user group 2-2/2-4 configuration 2-2/2-4 distribution 8-8 distribution list 2-2/2-4 GI contents of 2-2/2-4 GI PDU components 1-22 LO contents of 2-2/2-4 LO PDU components 1-21 managing 7-2 MR contents of 2-2/2-4 MR PDU components 1-15 MS contents of 2-2/2-4 creating, new installation 4-20/4-21 MS PDU function 1-17 MS SQL 1-16 OSI/MHS creating, new installation 4-19/4-20 performance tuning 8-15 registration 2-2/2-4 routing 2-67, E-3 RS contents o
PAGE 526
Index E DLISTMEMBER objects (continued) naming 2-40 SCF commands descriptions of 2-41 examples of 2-41 table of 2-17 states 2-40 Do not START MS… (error) C-9 DTE address D-6 E EIT-CHECK attribute 2-45 EMS See Event Management Service (EMS) EMSACOLL command 2-58 EMSDIST 7-28/7-30 Encoding messages 1-14, 9-33 Entry manager 1-31, 9-52 Entry manager, defining and starting 6-8 ENTRY object of OSI/AS D-7 ENTRY objects description 2-20, 2-41 naming 2-43 OSI addresses, verifying 7-22/7-23 SCF commands descriptio
PAGE 527
Index G File I/O monitoring 8-16 File System error (error 0006) C-8 File Utility Program (FUP) 2-13, 4-17 Filters, event See Event Management Service (EMS) Functional unit 9-25 Functional units partial list of 9-32 G Gateway access unit 9-32 description 1-7/1-8 general user 1-35 insufficient memory for 9-54 interconnection problems 9-52 See also APPL objects, GATEWAY objects, Transfer X400 gateway Gateway interconnection problem recovery checklist 9-57 Gateway interface (GI) group See GI groups Gateway i
PAGE 528
Index H GROUP objects (continued) types of (qualifying class names) 2-50 wild-card characters in names 2-51 Groups defining multiple 8-3 GW-AUX-PNAME attribute 2-46 GW-PNAME attribute 2-46 GW-TYPE attribute 2-45 H Halting the subsystem 6-12/6-13 Help installation procedure, online 4-12 Hierarchy of object types 2-18/2-20 Home terminal assigning process as 8-7 Hunt groups, X.
PAGE 529
Index L Installation procedure, new installation (continued) OSI/MHS databases, creating 4-19/4-20 overview 4-11 sample configuration file, creating 4-21 starting 4-11/4-14 utilities used 4-17 Installing D22 upgrade 4-23 D41 upgrade 4-23 example installation files default file 4-6 extended new installation 4-7 extended upgrade installation 4-9/4-10 MTA1, example MTA object A-2 MTA2, example MTA object 5-16, 5-21, 5-27, A-29 MTA3, example MTA object A-43 installation file keyword defaults 4-5 installation
PAGE 530
Index M Local UAs configuration checklist B-12 Local UAs, configuration checklist B-12 Log file, creating 6-3 LOG parameter, PARAM command 6-5 LOGFILE parameter, PARAM command 6-5 Logging of message processing status 9-25 Loop suppression E-7 M Mail boxes RESTMBOX utility C-5/C-7, C-8/C-9 SAVEMBOX utility C-2/C-4 uses of SAVEMBOX and RESTMBOX C-1 Mailboxes definition 1-8 description C-1 errors C-8/C-9 number of 1-16 overview C-1 Management domains, recommendations 3-9 Manager process See MHS manager proc
PAGE 531
Index M Messages encoding and decoding 1-14 large 8-18 multirecipient 1-13 types 1-11 Messages, event See Event Management Service (EMS) MHS See Message handling systems (MHS), Comaq OSI/MHS MHS databases See Databases MHS manager process defining objects to 6-6/6-7 description 1-12/1-13, 2-1 examples of starting 6-6 PARAM command 6-4/6-5 RUN command 6-1/6-3 stopping 2-56 MHS user 1-2 MHSMGR See MHS manager process Mnemonic O/R address 1-28 Modifying the configuration 7-1/7-2 MON object caution for ABORT
PAGE 532
Index N MTA objects (continued) configuring MTA1 5-21 configuring MTA2 5-14/5-17, 5-21, 5-27 configuring MTA3 5-17 important attributes 5-12 MTA description 1-2 naming 2-60/2-61 OSI addresses, verifying 7-26, 7-27 performance tuning 8-11 performance tuning factors 8-6 SCF commands 2-61 descriptions of 2-61 examples of 2-62/2-63 table of 2-17 See Adjacent MTAs states 2-60 verifying 7-14/7-16 MTA1, example MTA object component diagram 5-21/5-23 configuration command file A-5 configuration diagram 5-24 insta
PAGE 533
Index O Nondelivery reason code 9-29 Nondelivery report 9-27 Nondelivery reports 1-13 example 9-28 troubleshooting 9-25 Nonsensitive commands 2-15 NonStop fundamentals, planning for 3-16 NonStop process pairs 3-17 NonStop SQL compile step warning message 4-17 installing 4-13 MS program compiling, new installation 4-19 MS SQL catalog creating, new installation 4-18 description 1-16 MS store databases creating, new installation 4-20/4-21 description 1-16 MS utility, compiling 4-18 required for message store
PAGE 534
Index O OSI addresses (continued) MR and RS groups, verifying in 7-21/7-26 MTA groups, verifying in 7-26/7-27 OSI/AS, redefining in 6-7 OSI addressing in connection establishment D-6 OSI manager process (OSI/AS) 7-20/7-21 OSI/AS subcodes in OSI/MHS event messages 9-13 OSI/AS subsystem example command files MTA1 A-23 MTA2 A-39 MTA3 A-57/A-61 example configurations MTA1 A-20/A-22 MTA2 A-38 MTA3 A-55 interfaces LO groups 1-19 OSI/MHS 1-22/1-23 RS groups 1-17 OSI manager process 7-20/7-21 performance tuning 8
PAGE 535
Index P O/R name (continued) overspecified E-9 planning issues 8-11 routing implications E-4 See O/R address underspecified E-8 wildcarded E-7 P P1 decoding 9-33 P1 encoding 9-33 P1 protocol 1-10 P1 user exit gateway 1-35 P1-EXIT attribute 2-45 P2 protocol 1-10 P7 API See P7 Application Programmatic Interface (P7 API) P7 Application Programmatic Interface (P7 API) accessing an MS 1-19 description 1-35 planning for 3-5 P7 protocol 1-6, 1-10, 1-26 Parallel processing performance tuning 8-3 PARAM command 6-
PAGE 536
Index Q Planning considerations (continued) Transfer X400 gateway issues 3-4 PRI parameter, RUN command 6-3 PRIMARY command description 2-16 MON object examples 2-58 Printing distributor, EMS 7-28/7-30 See Event Management Service (EMS) Priorities for alternate routes 3-14 Private Management Domain (PRMD) CCITT routing recommendations 3-9 description 1-9 MOTIS routing recommendations 3-9 PRMD See Private Management Domain (PRMD) Probes 1-11 Problem reporting interconnection problems 9-23 LO process 9-67 R
PAGE 537
Index R Reliable transfer service (RTS) process 1-15 Remote addresses using SCF to define D-9 Remote Duplicate Database Facility G-1 Remote MTAs, configuration checklist B-7 Remote operations service element (ROSE) protocol 1-9, 1-17 See RS GROUP objects Remote operations service (RS) group See RS GROUP objects 1-1 Remote operations service (RS) process 1-19 Remote user agents (RUAs) configuration checklist B-11 description 1-2 example of message flow 1-26/1-27 interface to mailbox 1-17 interface to OSI/M
PAGE 538
Index S Route-selection criteria (continued) link and route retry issues 3-11/3-14 management domain issues 3-8/3-9 O/R address issues 3-10 planning example 3-7 planning issues 3-7, 8-3, 8-11 priority issues 3-14 See ROUTE objects verifying 3-14 Routing algorithm E-4 alternate routes, planning issues 3-10 configuring 2-67 database E-3 caution for 2-67 description 1-29/1-30 link retry message queue 2-42 O/R name used in E-5 principles of OSI/MHS E-1 route retries performance tuning 8-1, 8-14 route retries,
PAGE 539
Index S SCF (continued) description 1-11 general object naming conventions 2-20/2-22 how to use 2-18 nonsensitive commands 2-15 object hierarchy 2-18/2-20 OSI address configuration with D-7 overview of interface 2-7/2-9, 2-13 See individual object types sensitive commands 2-16 SCP description 1-11, 2-10 overview of interface 2-7/2-9 Security 2-11 master password server (MPS) 2-12 MS SQL catalog 4-18, 4-19 MS store database files 4-20/4-21 OSI/MHS database files 4-19/4-20 securing new executable object fil
PAGE 540
Index T STOP command (continued) CLASS object examples 2-35 description 2-17 MON object examples 6-12 SUBSYS object examples 2-73 Stopping the subsystem 6-12/6-13 Store cleaner (SC) process 1-15, 9-26 SU objects (OSI/AS), verifying 7-24/7-26 subcodes OSI/AS 9-13 Submission protocol 1-2 Subscribed attributes 2-23, C-1 Subsys not configured (error 0004) C-8 SUBSYS object configuration checklist B-3 description 2-19, 2-69 example configuration 5-13/5-14 naming 2-70 OSI manager process name, finding 7-20/7-21
PAGE 541
Index U Transaction Management Facility (TMF) performance tuning 8-16 relationship to OSI/MHS 1-3, 2-2 Transfer application, configuration checklist B-10 Transfer X400 gateway 1-6 APPL object 2-22 components 1-31 configuration checklist B-9 configuration examples 5-17, 5-21 description 1-7/1-8 message flow from OSI/MHS 1-34/1-35 message flow to OSI/MHS 1-32/1-33 overview 1-31 planning for 3-4 See also GATEWAY objects Troubleshooting connection problem example 9-10 interconnection with gateway 9-52 interco
PAGE 542
Index Z X25AM subsystem (continued) normal , 1980 mode 5-21 performance tuning 8-16 relationship to OSI/MHS 1-3 X.25 addressing requirements D-6 hunt groups 8-8 performance tuning 8-8 X.400 address See O/R address X.400 protocols 1-10 X.400 standards implemented 1-10/1-11 X.