OSI/MHS Orientation Guide Abstract This manual describes some common tasks involved in building message handling systems using Compaq products. It also helps the reader to find related information in other Compaq manuals and educational offerings. Product Version OSI/MHS D42 Supported Releases This manual supports G06 and D41 releases and all subsequent releases until otherwise indicated in a new edition.
Document History Part Number Product Version Published 088261 OSI/MHS C31 March 1993 099929 OSI/MHS D20 September 1993 112291 OSI/MHS D30.02 July 1995 424829-001 OSI/MHS D42 December 1999 Ordering Information For manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contact your local sales representative. Document Disclaimer Information contained in a manual is subject to change without notice.
OSI/MHS Orientation Guide Glossary Index Figures Tables What’s New in This Manual v Manual Information v New and Changed Information v About This Manual vii Who Should Read This Manual? vii What’s in This Manual? vii Related Manuals and Other Sources viii Your Comments Invited xiii Notation Conventions xiii 1. Building Your Message Handling System What Is Message Handling? 1-1 1-2 X.
1. Building Your Message Handling System (continued) Contents 1.
2. X.400 Support on Compaq Integrity Systems Contents 2. X.400 Support on Compaq Integrity Systems X.400 Products for Integrity Series Systems 2-1 Integrating X.400 on NonStop and Integrity Series Systems 2-1 Case Study of Integrating X.400 on NonStop and Integrity Series Systems 2-2 Glossary Index Figures Figure i. Compaq OSI/MHS Manual Set ix Figure 1-1. Linking Mail Systems Across a Heterogeneous Network 1-3 Figure 1-2. User Agents and Message Transfer Agents Figure 1-3.
Contents Table 1-3. Manuals and Media for Using PS Mail Across an X.400 Network Table 1-4. Manuals and Media for Integrating Transfer Applications Other Than PS Mail With an X.400 Network 1-19 Table 1-5. Manuals and Media for Integrating an X.400 Messaging System With OSI/MHS 1-22 Table 1-6. Manuals and Media for Using the Gateway Programmatic Interface (page 1 of 2) 1-26 Table 1-7. Manuals and Media for Integrating a Remote User Agent 1-30 Table 1-8.
What’s New in This Manual Manual Information OSI/MHS Orientation Guide Abstract This manual describes some common tasks involved in building message handling systems using Compaq products. It also helps the reader to find related information in other Tandem manuals and educational offerings. Product Version OSI/MHS D42 Supported Releases This manual supports G06 and D41 releases and all subsequent releases until otherwise indicated in a new edition.
New and Changed Information What’s New in This Manual OSI/MHS Orientation Guide— 424829-001 vi
About This Manual This manual is the place to begin to learn about building messaging systems based on Compaq products. Whether your task is to build a new messaging system or to integrate an existing one with an X.
About This Manual Related Manuals and Other Sources Where to look. This part includes a table of manuals, courses, and other information to support the specific task. • Section 2, “X.400 Support on Compaq Integrity Series Systems,” is an overview of X.400 products for the Integrity Series (NonStop-UX) platform, with a brief discussion on integrating NonStop and Integrity Series systems in an X.400 network. Note.
Courses About This Manual Figure i. Compaq 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 CDT 999.
Standards and Recommendations About This Manual • • • System Management provides background for making system resource management decisions and policies for NonStop systems (five-day lecture/lab). C Programming on the Guardian Platform is an introduction to writing C programs for NonStop systems (three-day lecture/lab). TAL Programming teaches the student how to write applications using the Compaq Application Language (eight-day lecture/lab).
Standards and Recommendations About This Manual Table i. Standards and Recommendations for the OSI Stack and Application Layer Services (page 2 of 2) ISO Standard CCITT Recommen dation Description of Contents 8650 X.227 Protocol ACSE 9066-1 X.218 1988 reliable transfer service (RTS) definition 9066-2 X.228 1988 RTS protocol 9072-1 X.219 Remote operations service (ROS) definition 9072-2 X.229 1988 ROSE protocol Table ii.
Standards and Recommendations About This Manual Table ii. Standards and Recommendations for Message Handling Systems (page 2 of 2) ISO Standard or XAPIA Specification CCITT Recommendation Description of Contents XAPIA X.400 API Specification v. 1.0 and 2.0 Object classes and attribute types for 1984 and 1988 X.400 XAPIA OSI Object Management API Specification Object-management API functions XAPIA X.400 Gateway API Specification v. 4.
Conformance and Implementation Information About This Manual Conformance and Implementation Information To achieve interoperation among systems, you will need conformance information, both for Compaq OSI products and for other products with which Compaq products must interoperate. In addition to product-specific programming and management manuals, Compaq provides conformance information for its OSI product family in a manual entitled OSI PICS Manual.
General Syntax Notation About This Manual [ ] Brackets. Brackets enclose optional syntax items. For example: TERM [\system-name.]$terminal-name INT[ERRUPTS] A group of items enclosed in brackets is a list from which you can choose one item or none. The items in the list may be arranged either vertically, with aligned brackets on each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num] [ text] K [ X | D ] address-1 { } Braces.
Notation for Messages About This Manual Item Spacing. Spaces shown between items are required unless one of the items is a punctuation symbol such as a parenthesis or a comma. For example: CALL STEPMOM ( process-id ) ; If there is no space between two items, spaces are not permitted. In the following example, there are no spaces permitted between the period and any other items: $process-name.#su-name Line Spacing.
Notation for Messages About This Manual Bold Text. Bold text in an example indicates user input entered at the terminal. For example: ENTER RUN CODE ?123 CODE RECEIVED: 123.00 The user must press the Return key after typing the input. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned.
Notation for Management Programming Interfaces About This Manual % Percent Sign. A percent sign precedes a number that is not in decimal notation. The %þnotation precedes an octal number. The %Bþnotation precedes a binary number. The %Hþnotation precedes a hexadecimal number.
About This Manual Notation for Management Programming Interfaces OSI/MHS Orientation Guide— 424829-001 xviii
1 Building Your Message Handling System Before you start planning your network or application—and researching the Compaq products supporting your requirements—there are several questions to ask yourself and others in your organization: • • • • Are the applications you plan to support really messaging applications? Is X.
Building Your Message Handling System • X.400 Message Handling Systems Directory lookup requirements.
X.400 Message Handling Systems Building Your Message Handling System Figure 1-1. Linking Mail Systems Across a Heterogeneous Network Transfer and PS Mail Company X EDI Company Y Mail X.400 Network UNIX Mail SprintMail X.400 Telematic Services LAN E-mail System N Company Z EDI Legend = X.400 Gateway CDT 001.CDD As defined by X.
Building Your Message Handling System X.400 Message Handling Systems The protocols for communication among these components are labeled as follows in the Recommendations and most other documents describing X.400: • • • • P1 is the protocol between two MTAs. P2 is the protocol between two UAs (for exchange of interpersonal messages across the network). P3 is the protocol between a UA and an MTA, when the UA requests services of the MTA directly. P7 is the protocol between a UA and a message store (MS).
Compaq Messaging Products Building Your Message Handling System Figure 1-2. User Agents and Message Transfer Agents Message Handling System (MHS) Message Transfer System (MTS) UA P1 MTA P7 User MS UA P3 MTA MTA MS MTA UA UA User P2 User User CDT 002.CDD Compaq Messaging Products There are several categories of X.400 and related messaging products you can use with Compaq systems: • • • The OSI/MHS product family is the Compaq implementation of the 1988 X.400 Recommendations.
Building Your Message Handling System Tasks Described in This Section includes an X.400 gateway for integration with OSI/MHS and a gateway for exchange of messages with UNIX SMTP mail systems. • Various third parties, notably Compaq Alliance partners, offer other messaging products—for instance, X.400 UAs, EDI solutions, gateways, and management tools—for use on Compaq NonStop systems. In addition, a third-party solution is available for X.400 on Integrity Series (NonStop-UX) systems.
Building Your Message Handling System Tasks Described in This Section 8. Designing an Electronic Data Interchange (EDI) Application. You can design an EDI application consistent with the X.400 Recommendations or integrate an existing EDI application with an X.400 network. 9. Managing a Messaging Network. A variety of tools and instrumentation allow you to monitor, tune, and administer a messaging network. 10. Writing an Accounting or a Billing Application.
Setting Up a Messaging Network or Hub Building Your Message Handling System Figure 1-3. User Task Diagram PS Mail Other Apps. 11 1984 X.400 Network Transfer X400 Gateway 2 OSI/MHS MTA X.400 Network OSI/ MHS MTA GPI 4 Non-X.400 Network Accounting & Billing 10 OSI/MHS MTA 3 Management Tools 9 GW 1 RUA Asynchronous X.25 Network 5 OSI/MHS MTA MS NSDS P7API GPI LUA GW 7 8 X.
Building Your Message Handling System What You Need to Do electronic data interchange, and messaging systems on a variety of platforms. The network supports workstation access, including low-cost dial-up connections for asynchronous devices; it also supports interfaces for telex, facsimile, and physical delivery systems. The role of the NonStop systems is to store and transmit messages, regardless of type, in a manner consistent with the X.400 Recommendations.
What You Need to Know Building Your Message Handling System Figure 1-4. NonStop Systems Serving as a Backbone Messaging Network Transfer Gateway NonStop System Backbone Messaging Network (ADMD) NonStop System NonStop System X.400 (P1) OSI/MHS OSI/MHS X.500 Directory GPI GPI Client OSI/MHS NonStop System Facsimile Remote User Agent X.400 (P1) X.400 (P1) X.400 (P1) X.400 (P1) OSI/MHS P7 AP1 NonStop System Non-X.400 Mail System Transfer Applications OSI/ MHS X.
Building Your Message Handling System • • • • • • What You Need to Know The Event Management Service (EMS) NonStop Transaction Manager/MP (TM/MP) NonStop SQL/MP (if you will use a message store) The Compaq X.25 access method (X25AM) or the Compaq LAN Access Method (TLAM), or both Compaq OSI Application Services (OSI/AS) Compaq OSI Transport Services (OSI/TS) Note. If you plan to operate OSI/MHS over TCP/IP rather than OSI transport protocols, you also need the Compaq TCP/IP product.
Building Your Message Handling System • • • Where to Look Install any related software on other systems and devices in the network: for instance, LAN servers, X.400 gateways, and RUAs. Install and start messaging applications and gateways, such as access units and EDI software. Install and configure the X.500 directory service (if one is used). Steps to integrate a directory service are described in more detail in a following subsection, “Integrating a Directory Service With OSI/MHS.
Where to Look Building Your Message Handling System Transaction Services/MP, you would need both the NonStop TS/MP and Pathway Management Programming Commands Manual and the NonStop TS/MP and Pathway Management Programming Messages Manual. If you wish to use the Master Password Server provided by Compaq, or to develop your own password server, you also need the OSI/MHS Management Programming Manual.
Where to Look Building Your Message Handling System Table 1-1. Manuals and Media for Setting Up a Messaging Network or Hub (page 2 of 2) Subject Area Title Database Contents NonStop TM/MP Operations and Recovery Guide NonStop SQL/MP Installation and Management Manual EMS Manual Op. Sys. How to operate and manage the NonStop Transaction Manager/MP How to install and manage NonStop SQL/MP How to start printing of operator messages Operator Messages Manual Op. Sys.
Building Your Message Handling System Integrating a Compaq Transfer Application With an X.400 Network Integrating a Compaq Transfer Application With an X.400 Network Users and clients of the Compaq Transfer delivery system can communicate with users and applications across an X.400 network through OSI/MHS. What You Need to Do To integrate a Compaq Transfer application, such as electronic mail, with an X.400 network, you use a component called the Compaq Transfer X400 gateway, illustrated in Figure 1-5.
What You Need to Do Building Your Message Handling System Figure 1-5. Transfer X400 Gateway PS Mail or Other Transfer Application Transfer Delivery System Transfer Database Servers Transfer Database Transfer X400 Gateway Importer Processes Exporter Processes Queue Manager OSI/MHS CDT 005.CDD You do not need to do custom programming to integrate Compaq PS Mail with your network. If you have a Transfer system with correspondents already defined and an X.
Building Your Message Handling System What You Need to Know The Transfer X400 gateway performs a simple mapping between Transfer and X.400 names. (It maps the name of the Transfer correspondent to the surname field of an X.400 name, and it maps the Compaq system name to the organization field of an X.400 name.) If your network requires a different mapping, you can tailor a server—called an XDIR server—to your Transfer environment.
Building Your Message Handling System • • • Where to Look Receive and decode X.400 messages using the Transfer programmatic interface (if the application requires specific X.400 services). Map Transfer correspondent names to X.400 names and vice versa (if the application requires a mapping different from the one the gateway provides). Interpret X.400 status information. If your application requires specific X.
Integrating an X.400 Messaging System or Gateway With Compaq OSI/MHS Building Your Message Handling System In the table, represents a manual, represents a videotape, represents a workbook, represents a lecture course, and represents information available to Compaq technical support personnel through the Courier application. Table 1-2. Manuals and Media for Integrating PS Mail With an X.
What You Need to Do Building Your Message Handling System What You Need to Do The procedures and considerations for integrating an existing messaging system with OSI/MHS vary according to whether the system: • • Is a native X.400 messaging system or a non-X.400 system with an X.400 gateway, running outside the NonStop system Uses a gateway application on the NonStop system Figure 1-6 illustrates these options. Note. If you wish to integrate an application that runs as an X.
Building Your Message Handling System • • • • • Where to Look Set up your MHS environment on the NonStop system, as described in “Setting Up a Backbone Messaging Network or Hub.” Describe the remote MTA in your MHS configuration, using the Subsystem Control Facility (SCF). Specifically, define the MTA, the route or routes that connect OSI/MHS to the MTA, and the gateway (if the gateway for your application runs on the NonStop system).
Where to Look Building Your Message Handling System "About This Manual" lists and describes the X.400 Recommendations and related documents you might need to comply with specific national or international regulations and agreements. To obtain a list of existing X.400 applications and services with which OSI/MHS has been certified or shown to interoperate, contact your Compaq field representative.
Building Your Message Handling System Integrating Your Own Messaging System With Compaq OSI/MHS Integrating Your Own Messaging System With Compaq OSI/MHS One of the most common uses of X.400 message handling systems is to integrate existing messaging systems—for instance, proprietary electronic-mail systems, public telex systems, and even physical delivery systems—over a standard network. To communicate across an X.400 network, an existing messaging system needs a gateway.
What You Need to Know Building Your Message Handling System Figure 1-7. Functions of an X.400 Gateway X.400 Gateway Translate & Transfer Inbound Messages Non-X.400 Messaging System GPI GPI Client Library Gateway Interface Process OSI/MHS Translate & Transfer Outbound Messages CDT 007.CDD Note. If you wish to integrate an application that runs as an X.400 RUA, see the discussion of “Writing or Integrating a Remote User Agent,” later in this section.
Building Your Message Handling System Where to Look To integrate your gateway with the network, you need to know how to perform the following functions: • • • • Set up your MHS environment on the NonStop system, as described in “Setting Up a Backbone Messaging Network or Hub” earlier in this section Describe the gateway in your MHS configuration, using the Subsystem Control Facility (SCF) to define the GIP processes, identify the application as a gateway, and identify its users Specify the names of X.
Where to Look Building Your Message Handling System Manuals and Media Guide Table 1-6 includes Compaq manuals and educational media that help you integrate messaging applications and systems with OSI/MHS. Items are listed in one possible reading order, but you will certainly find yourself moving back and forth among the manuals as you work.
Building Your Message Handling System Writing or Integrating a Remote User Agent With Compaq OSI/MHS Table 1-6.
What You Need to Know Building Your Message Handling System Figure 1-8. Integrating a Remote User Agent With OSI/MHS Message Store MS MRP Message Relay Process + Reliable Transfer Service RTS RS MTA OSI/AS OSI/TS TLAM and/or X25AM P1 P7 MTA RUA CDT 008.CDD To integrate an RUA with OSI/MHS, you define the required MHS components (message stores, RS processes, and PDU stores) and describe the RUA to OSI/MHS as an application (APPL).
Building Your Message Handling System Where to Look To perform this task, you must understand the concepts of the X.400 P7 protocol and also more general X.400 concepts pertaining to naming, addressing, and routing. You also need to know enough about the architecture of OSI/MHS, the underlying OSI products, and how the standards for P7 and supporting OSI services are implemented on both sides of the connection to be able to troubleshoot interoperation or conformance problems, should they arise.
Writing and Integrating a Local User Agent With Compaq OSI/MHS Building Your Message Handling System Table 1-7. Manuals and Media for Integrating a Remote User Agent Subject Area Title Contents Introduction to Compaq Networking and Data Communications OSI Fundamentals ISP COMM/OSI Background on Compaq networking products, including MHS OSI OSI technical overview X.400 Concepts and Architecture video OSI/MHS Product Overview video MHS X.400 technical overview MHS X.
What You Need to Know Building Your Message Handling System Figure 1-9. Integrating a Local User Agent (LUA) With OSI/MHS Message Store MS Message Relay Process + Reliable Transfer Service MRP LO RTS MTA LUA P7 API OSI/AS OSI/TS TLAM I/O Device Protocol (Guardian 90 I/O Process) X25AM P1 P1 MTA MTA CDT 009.
Building Your Message Handling System • Where to Look The architecture of the local operations service and its support for multiple clients and multiple associations with clients To add a local user agent to your OSI/MHS configuration, you must know how to perform the following functions: • • • • Set up your MHS environment on the NonStop system, as described in “Setting Up a Backbone Messaging Network or Hub” earlier in this section.
Integrating a Directory Service With Compaq OSI/MHS Building Your Message Handling System order, but you will certainly find yourself moving back and forth among the manuals as you work. For brevity, Table 1-8 omits resources that describe how to set up an OSI/MHS environment. If you have not yet set up an MHS environment, also see the list for “Setting Up a Backbone Messaging Network or Hub” earlier in this section.
Building Your Message Handling System What You Need to Do A directory service is defined by CCITT Recommendation X.500. Specifically, X.500 defines the structure of the database, or X.500 directory, and it defines protocols used to access that directory. The Compaq X.500 directory service is NonStop Directory Services (NSDS). NSDS is actually a family of products that implements features of 1988 X.500 Recommendations and simplified access control, a key feature of 1993 X.500 Recommendations.
What You Need to Know Building Your Message Handling System Figure 1-10. Four Ways to Access NSDS NSDS Viewer Command Files NSDS Scriptor NSDS Application X.500 Directory XDS/XOM MDQ X.400 Network OSI/MHS Legend GW = Gateway Application RUA = Remote User Agent LUA = Local User Agent GPI = Gateway Programmatic Interface Compaq Provides CDT 016.
Developing EDI Applications With Compaq OSI/MHS Building Your Message Handling System Manuals and Media Guide Table 1-9 includes Compaq manuals and educational media that help you integrate a directory service with OSI/MHS. Items are listed in one possible reading order, but you will certainly find yourself moving back and forth among the manuals as you work. For brevity, Table 1-9 omits sources that describe how to set up an OSI/MHS environment.
What You Need to Do Building Your Message Handling System Many EDI implementations in Europe also reflect the recommendations of Trade EDI Systems (TEDIS), an EDI planning activity for the European Community. Given the increasing importance of X.400 messaging, networking service providers and private enterprises alike have sought convergence between EDI and X.400 standards. This interest has resulted in the X.435 Recommendation; the definition of a specific EDI protocol for use with X.400. Prior to X.
Building Your Message Handling System What You Need to Do You can develop both remote and local P7 user agents as EDI applications. The P7 interfaces provide X.435 support as well as support for P0 and P2 methods. With X.435 support, a user agent can submit and retrieve X.435 messages but cannot retrieve messages based on individual attributes within those messages. With P0 support, EDI information can be encoded as undefined content of an X.400 message.
What You Need to Know Building Your Message Handling System Figure 1-11. EDI Over X.400 (Content Type = P0) Undefined (Content Type = P2) Interpersonal Message (IPM) (Content Type = X.435) EDI Message (EDIM) Envelope Envelope Envelope Content = Content Content IPM Heading EDI Heading EDI Interchange EDI Interchange EDI Interchange CDT 010.
Where to Look Building Your Message Handling System • • Manuals describing the message formats, protocols, and standards conformance of the existing application (or requirements for a new application), and similar information for other EDI applications with which yours must interoperate. Copies of the CCITT X.400 series of Recommendations, including X.435, and of EDI standards and implementors’ agreements with which you choose to comply.
Building Your Message Handling System Managing a Messaging Network or Hub Managing a Messaging Network or Hub Compaq provides a variety of tools to help you manage your backbone messaging network or hub and receive some types of management data from messaging applications. What You Need to Do To manage a messaging network or hub, you are likely to engage in most of the following types of activities: • • • • • • Establishing and maintaining a configuration, including MHS and all underlying software.
What You Need to Know Building Your Message Handling System Table 1-12.
What You Need to Know Building Your Message Handling System Table 1-13.
Where to Look Building Your Message Handling System Figure 1-12. Actionview, From Insider Technologies (Illustration Used by Permission) Tandem X.
Where to Look Building Your Message Handling System Manuals and Media Guide Table 1-14 includes Compaq manuals and educational media that help you manage a messaging network. Items are listed in one possible reading order, but you will certainly find yourself moving back and forth among the manuals as you work. (If you will not be using the Transfer gateway to give users of Transfer access to the X.400 network, you do not need the manuals for Transfer or the NonStop Transaction Services/MP product.
Where to Look Building Your Message Handling System Table 1-14. Manuals and Media for Managing a Messaging Network or Hub (page 2 of 2) Subject Area Title Contents OSI/AS Installation and Configuration ISP OSI How to set up OSI upper layers X.
Writing an Accounting and Billing Application Building Your Message Handling System Writing an Accounting and Billing Application A common requirement of backbone messaging networks is the need to bill clients for the services they use. Even in a private network that does not use interdepartmental billing, it can be very useful to gather accounting information to gain a sense of how much, by whom, and in what ways the network is being used.
Building Your Message Handling System What You Need to Know OSI/MHS reports the specified events to a process called an EMS collector, which records the messages in a disk log. All messages are timestamped and contain various descriptive information. There are three main interfaces through which you can find out which events have occurred: • • • You can have the text form of messages printed on a printer, using an EMS printing distributor.
Where to Look Building Your Message Handling System Where to Look Compaq provides a set of manuals and courses to help you learn about Distributed Systems Management and the task of management programming.
Building Your Message Handling System Integrating 1984 and 1988 Messaging Systems Integrating 1984 and 1988 Messaging Systems Although several companies have announced products conforming to 1988 X.400, the great majority of existing systems implement the 1984 Recommendations. Even among those able to exchange messages in 1988 format, the underlying services, such as the reliable transfer service and the OSI stack, are of the earlier vintage.
Building Your Message Handling System • What You Need to Know Designing applications, and possibly upgrading 1984 applications, to take advantage of new features of the 1988 systems Note. Note that a P7 application cannot be the client of a 1984 MTA because neither the message store nor the P7 protocol exists in a 1984 system. A 1988 MTA can, however, relay information from a P7 user to a user on a 1984 system, with a possible loss of information in transit.
Where to Look Building Your Message Handling System • • Manuals and conformance statements (PICS) from other vendors whose X.400 products will communicate with OSI/MHS, and manuals describing applications you will use with OSI/MHS: for instance, third-party EDI applications and gateways that use the Gateway Programmatic Interface (GPI) Copies of the CCITT X.400 series of Recommendations for 1984 and 1988 “About This Manual” lists and describes the X.
Building Your Message Handling System OSI/MHS Orientation Guide— 424829-001 1- 53 Where to Look
Building Your Message Handling System OSI/MHS Orientation Guide— 424829-001 1- 54 Where to Look
2 X.400 Support on Compaq Integrity Systems Many organizations have a strategic commitment to open systems: that is, to systems based as much as possible on standard technologies. Indeed, the OSI Reference Model addresses precisely this interest, providing a means for systems of widely varying design to work together.
X.400 Support on Compaq Integrity Systems Case Study of Integrating X.400 on NonStop and Integrity Series Systems You integrate X.400 on the two types of systems by describing each system to the others as an MTA. Conceptually, the configuration task on each type of system is the same, although the interfaces for configuration might be quite different. Case Study of Integrating X.400 on NonStop and Integrity Series Systems Figure 2-2 illustrates a hypothetical X.
Case Study of Integrating X.400 on NonStop and Integrity Series Systems X.400 Support on Compaq Integrity Systems . Figure 2-1. Integrating X.400 on NonStop and Integrity Series Systems Satellite Nodes — Integrity Series (X.400, FTAM) Satellite Nodes — Integrity Series (X.400, FTAM) NonStop Systems (X.
X.400 Support on Compaq Integrity Systems Case Study of Integrating X.
Glossary The following glossary defines terms used in this manual and in other Compaq OSI/MHS manuals. Both industry-standard terms and Compaq terms are included. This list covers Compaq 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.
Glossary ASE (application service element). A set of functions in the Application Layer that supports either a large range of applications or a particular type of application, such as file transfer or transaction processing. ASN.1 (Abstract Syntax Notation One). A data description language for expressing abstract syntaxes in OSI. See also abstract syntax and BER. association. In OSI, a connection between Application Layer entities. See also connection.
Glossary bind. The act of establishing a connection. An MTA bind enables one MTA to establish an association with another MTA; an MS bind enables a user agent to establish an association with a message store. bit string. A series of bits treated as a unit. body part. The substance of an interpersonal message (IPM). An IPM user message can contain one or more body parts. Each body part can have one of a variety of encoded information types, such as text, facsimile, graphics, or voice.
Glossary communication. The transfer of information between or among different entities, or the information transmitted. In GPI manuals, this term is used to designate a message, a probe, or a report in statements that apply to all three of these types of X.400 messages. conditional token. In DSM event management, a token that is sometimes, but not always, present in a particular event message. See also unconditional token. configuration and control components.
Glossary critical event. A DSM event that is crucial to the operation of the system or network. Each subsystem determines which of its events are critical, designating them as such by setting the value of the emphasis token to TRUE. See also noncritical event. CUG (closed user group). A set of users who may communicate with one another. Closed user groups are an optional feature of OSI/MHS and are not part of the X.
Glossary diagnostic code. A value indicating why a message was not delivered (called a non-deliverydiagnostic code in the X.411 standard). DIB. See Directory Information Base. directory. A collection of open systems that cooperate to hold a logical database of information about a set of objects in the real world. directory information. In the DIT, the is a collection of entries you have created the directory to store. It consists of object entries and their attributes. Directory Information Base (DIB).
Glossary EMS (Event Management Service). A part of DSM used to provide event collection, event logging, and event distribution facilities. It provides for different event descriptions for interactive and programmatic interfaces, lets an operator or application select specific event-message data, and allows flexible distribution of event messages within a system or network. EMS has SPI-based programmatic interfaces for reporting events and retrieving event messages. EMS collector. See collector.
Glossary event management. The reporting and logging of events, the distribution and retrieval of information concerning those events, and the actions taken by operations personnel or software in response to the events. See also control and inquiry. Event Management Service. See EMS. event message. A special kind of SPI message that describes an event occurring in the system or network. See also command message or response message. event-message template.
Glossary filter. In EMS, a file containing a list of criteria against which incoming event messages can be evaluated to see if they can pass (all criteria met) or not pass (one or more criteria failed) through the filter. fixed structure. In DSM programmatic interfaces, a multifield structure declared for the value of a simple token. Fields cannot be added to fixed structures. See also extensible structure. forwarded IPM.
Glossary version token, and the checksum token. Command and response messages contain a specified set of header tokens; event messages, a different set with some overlap. See also SPI message. importer. In the Transfer X400 gateway, the server that moves messages from the X.400 network into the Transfer environment. See also exporter. inbound communication. A communication received from the X.400 network and available to a client. See also outbound communication. indication primitive.
Glossary the message was delivered to the intended or an alternate recipient, and whether its encoded information type (such as facsimile or videotex) was converted. ISO (International Organization for Standardization). A United Nations organization, established to promote the development of standards to facilitate the international exchange of goods and services and to develop mutual cooperation in areas of intellectual, scientific, technological, and economic activity.
Glossary 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).
Glossary alphabetic and up to three alphanumeric characters: for example, $ZMHS. See also manager process. MIB (management information base). A database used by the OSI manager to store and retrieve configuration information and information about applications. mnemonic O/R address. An O/R address that identifies a user by terms that are easily remembered. See also numeric O/R address. MON object. An object type, used in OSI/MHS management interfaces, that enables you to address commands to the MHS manager.
Glossary MTS (message transfer system). The part of a message handling system that contains the MTAs and that permits communication between user agents. MTS identifier. A unique identifier that distinguishes a communication from all other communications ever conveyed by the MTS within the MHS. multithreaded process. A process that handles multiple requests simultaneously. multivalued attribute. An attribute that can have more than one value. network address. See NSAP and NSAP address. Network Layer.
Glossary NonStop SQL. A relational database management system that combines the ease of use of the Structured Query Language (SQL) with the application performance provided by the Compaq NonStop Kernel. NonStop tools. The utility programs that perform everyday activities including editing, formatting, restoring, backing-up, sorting, spooling, binding, compiling, and installing. NonStop Transaction Manager/MP (NonStop TM/MP).
Glossary In DSM, an entity subject to independent reference and control by a subsystem: for example, the disk volume $DATA or the data communications line $X2502. An object typically has a name and a type known to the controlling subsystem. In GPI, a collection of elements (called “attributes”) used for constructing messages. See also root object, subobject, and superobject. object identifier. In ASN.1, a set of values identifying an object in an ASN.1 abstract syntax notation defined by the CCITT.
Glossary management activities. It maintains a management information base (MIB) that contains the configuration information about the OSI environment. There is one OSI manager process per OSI/AS subsystem. OSI/MHS (Open Systems Interconnection/Message Handling System). The Compaq implementation of an X.400 message handling system for Compaq NonStop systems. OSI/MHS database. The database that consists of the registration database and OSI/MHS configuration database. OSI/MHS ISV.
PAM Glossary P2 message. An X.400 message that consists of a heading followed by a series of data blocks, called body parts. The heading contains the message originator, recipients, and other service information. Each body part can contain a different form of data, and messages can be nested within body parts. 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.
Port Access Method (PAM) Glossary 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. This layer resolves the differences of varying data formats between systems of different vendors.
Port Access Method (PAM) Glossary PSAP (presentation service access point). A logical location between the Presentation and Application Layers, through which presentation services are made available to local users and through which application services are made available to remote systems. PSEL (presentation selector). An address at the boundary between the Presentation and Application Layers, through which connections are established and maintained.
Port Access Method (PAM) Glossary reserved object. An object on the input queue that the client program has started transferring in and to which the GPI has assigned an object identifier. A client program can examine or copy a reserved object (and its attributes) but not modify it. response. In OSI, see response primitive. In DSM, the information or confirmation supplied (as part of a response message) to an application by a subsystem in reaction to a DSM command. response message.
Port Access Method (PAM) Glossary routing. The selection of the adjacent MTA to which a message, probe, or report is transferred. routing database. A database in the OSI/MHS registration database that contains records of ROUTE objects and APPL objects. routing tables. The internal databases that hold the information about the O/R names. RS (remote operations service) class. The OSI/MHS CLASS object that identifies the set of all RS groups in an OSI/MHS subsystem. RS (remote operations service) process.
Port Access Method (PAM) Glossary Scriptor. See NSDS Scriptor. SCP (Subsystem Control Point). In DSM, the management process for all Compaq data communications subsystems. There can be several instances of this process. Applications using SPI send all commands for data communications subsystems to an instance of this process, which in turn sends the commands on to the manager processes of the target subsystems. SCP also processes a few commands itself.
Port Access Method (PAM) Glossary 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.
Port Access Method (PAM) Glossary apply to multiple subsystems. See also definition and definition files, data communications standard definitions or EMS standard definitions. SQL. See NonStop SQL. SSAP. A logical location between the Session and Presentation Layers, through which session services are made available to local users, and through which presentation services are made available to remote systems. SSEL (session selector).
Port Access Method (PAM) Glossary summary state. In DSM interfaces to Compaq 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.
Port Access Method (PAM) Glossary TLAM (Tandem LAN access method). A Compaq product that implements the services of the Data Link and Physical Layers for LANs. Transaction Management Facility (TMF) subsystem. The major component of the NonStop TM/MP product, which protects databases in online transaction processing environments. To furnish this service, the TMF subsystem manages database transactions, keeps track of database activity through audit trails, and provides database recovery methods. token.
Port Access Method (PAM) Glossary transport layer. Layer 4 in the OSI Reference Model. This layer provides reliable, transparent transfer of data between end systems and ensures that the data arrives at the correct destination. transport selector. See TSEL. TSAP (transport service access point). A logical location between the Transport and Session Layers, through which transport services are made available to local users, and through which session services are made available to remote systems.
Port Access Method (PAM) Glossary wild-card character. A character that stands for any possible character(s) in a search string or in a name applying to multiple objects. In DSM object-name templates, two wild-card characters can appear: ? for a single character and * for zero, one, or more consecutive characters. See also object-name template. working subvolume. A subvolume that contains temporary files used by the OSI/MHS subsystem processes. There is a separate working subvolume for each process group.
Port Access Method (PAM) Glossary OSI/MHS Orientation Guide— 424829-001 Glossary -30
Index Numbers 1984 and 1988 version integration 1-2, 1-52 1984 X.400 recommendations 1-2 A A 1-47 access control 1-13 access unit 1-4 accounting and billing applications 1-49 accounting application 1-47 Actionview 1-43 ADMD 1-9, 1-41, 1-42 administration management domain 1-9 administration of messaging networks 1-42 API developing X.
P Index P P1 protocol 1-4 P2 protocol 1-4 P3 protocol 1-4 P7 protocol 1-4 PRMDs 1-42 protocols P1 1-4 P2 1-4 P3 1-4 P7 1-4 PS Mail 1-11 with X.400 network 1-17 R remote user agent 1-27 RS group 1-28 RUA 1-27 T telex systems 1-23 transfer applications 1-11 integration with an X.400 network 1-15 transfer X.400 gateway 1-16 U user agent 1-3 X X400 support 2-1 X.400 catagories 1-5 Integrity Series 2-1 X.
