Networking and Data Communications Library Tandem OSI/AS and OSI/TS Supplement (Includes RFC-1006 Support) Abstract Part Number Edition Published Product Version Release ID Supported Releases This manual supplements the C30.08/D10 editions of the seven-manual set for OSI/AS and OSI/TS. It describes RFC-1006 support and other general changes to these manuals. 107751 First January 1995 OSI/AS D30 and OSI/TS D30 D30.00 This manual supports D30.
Document History Edition Part Number Product Version Earliest Supported Release Published First 107751 D30 D30.00 January 1995 New editions incorporate any updates issued since the previous edition. A plus sign (+) after a release ID indicates that this manual describes function added to the base release, either by an interim product modification (IPM) or by a new product version on a .99 site update tape (SUT). Ordering Information For manual ordering information: domestic U.S.
New and Changed Information This manual supplements the C30.08/D10.
New and Changed Information (This page left intentionally blank) iv 107751 Tandem Computers Incorporated
Contents About This Manual ix Notation Conventions Section 1 xiii Introduction to RFC-1006 Overview of the Tandem OSI Architecture 1-1 TCP/IP as the NSP Process 1-3 Comparison of OSI and Internet Layer Architectures OSI/AS and OSI/TS on Top of TCP/IP 1-5 Introduction to the Tandem TCP/IP Subsystem TCP/IP Internet Addressing 1-9 1-4 1-7 Changes in the Transport Layer When Using RFC-1006 1-15 Transport Layer Protocols 1-15 Transport Service User Data 1-16 Transport Expedited Data 1-16 Larger TPDU Size
Contents ALTER SERVICE #L4 3-4 ALTER SU 3-5 CHECK SU 3-6 INFO SERVICE #L4 3-10 INFO SU 3-11 STATUS SU 3-12 OSI/AS SCF Commands Changed to Support RFC-1006 IP Address in the ENTRY Object 3-15 ADD ENTRY #APPL 3-16 ADD ENTRY #NSAP 3-16 ADD ENTRY #SNPA 3-16 ADD PROCESS 3-17 ADD PROFILE #L4 3-18 ALTER ENTRY #APPL 3-19 ALTER ENTRY #NSAP 3-19 ALTER ENTRY #SNPA 3-20 ALTER PROCESS 3-20 ALTER PROFILE #L4 3-21 ALTER SERVICE #L4 3-22 CHECK ENTRY 3-24 CHECK SU 3-26 INFO ENTRY #APPL 3-30 INFO ENTRY #NSAP 3-30 INFO ENTRY
Contents OSI/TS PTrace Changes Section 4 3-47 RFC-1006 Configuration Command Files IP Address Conversion Program 4-1 OSI/AS Configuration Example 4-3 OSI/TS Configuration Example 4-5 OSI/MHS RS Group Configuration Example Section 5 TPDUs Used by RFC-1006 CC-TPDU 5-2 CR-TPDU 5-5 DR-TPDU 5-9 DT-TPDU 5-11 ED-TPDU 5-12 ER-TPDU 5-13 Section 6 Socket Errors Returned by TCP/IP to OSI/TS Section 7 Programming With the Sockets Interface Section 8 4-8 Programming a Client 7-1 Programmi
Contents Figure 1-9. Internet Address Formats 1-13 Figure 1-10. Internet Class B Address Format With a Subnet Address Figure 1-11. Subnets on HOST9 Figure 1-12. Transport Packet 1-13 1-14 1-17 Figure 2-1. Configuring OSI/TS, TCP/IP, and NSP Processes in OSI/TS 2-6 Figure 2-2. Single TSP Process Interfacing With a Single TCP/IP Process 2-8 Figure 2-3. Single TSP Process Interfacing With Multiple TCP/IP Processes 2-10 Figure 2-4.
About This Manual About the OSI/AS and The OSI/AS subsystem and the OSI/TS subsystem together provide core services that OSI/TS Manual Set support the seven-layer OSI Reference Model. With the addition of support for RFC1006, services are also provided to allow OSI applications to communicate over the Internet. The set of manuals for these two products is listed in Table 0-1.
About This Manual What Is in This Manual? What Is in This This manual is intended to be used as a supplement to the seven-manual OSI/AS and Manual? OSI/TS set. Sections 1 through 6 provide information on Tandem’s RFC-1006 implementation in OSI/AS and OSI/TS. RFC-1006 allows OSI/TS to connect to the Transmission Control Protocol (TCP), which is a Transport Layer protocol specified in the Internet Reference Model. Section 7 provides general information that applies to all the OSI/AS and OSI/TS manuals.
About This Manual Your Comments Invited What Is Not in This Manual? Configuration of the TCP/IP, X25AM, and TLAM subsystems is not covered in this manual; see the following manuals: Tandem TCP/IP Configuration and Management Manual SCF Reference Manual for Tandem TCP/IP Tandem TCP/IP Management Programming Manual TLAM Configuration and Management Manual System Generation Manual for X25AM Standards This manual and the other Tandem OSI manuals are written for those familiar with the Implemented by OSI stan
About This Manual Your Comments Invited in your message. If your comments are specific to a particular manual, include the part number and title of the manual in your message. The Reader Comment Card is located at the back of the printed manual and as a separate file in the CD Read Document List. You can fax the card to (408) 285-6660 or mail the card to the address printed on the card. Many of the improvements you see in Tandem manuals are a result of suggestions from our customers.
Notation Conventions General Syntax Notation UPPERCASE LETTERS The following list summarizes the notation conventions for syntax presentation in this manual. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: CHECK SU lowercase italic letters Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
Notation Conventions General Syntax Notation 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...
1 Introduction to RFC-1006 This section contains the following information: Overview of Tandem OSI architecture Introduction to the Tandem TCP/IP subsystem Changes in the Transport Layer when using RFC-1006 Tandem OSI/AS and OSI/TS have implemented the Request for Comments (RFC) 1006 standard entitled “ISO Transport Service on Top of the TCP,” Version 3.
Introduction to RFC-1006 Overview of the Tandem OSI Architecture Figure 1-1. Tandem OSI Architecture: OSI/AS and Underlying Subsystems Layer Application Presentation Session OSI/MHS Subsystem Other OSI/AS Applications OSI/TS Applications OSI/FTAM Subsystem OSI/AS Subsystem Transport TCP/IP Subsystem OSI/TS Subsystem Network Data Link X25AM Subsystem X25AM Subsystem TLAM Subsystem TLAM Subsystem Controllers Controllers Controllers Controllers RS-232C, RS-449, X.21, V.
Introduction to RFC-1006 Overview of the Tandem OSI Architecture TCP/IP as the NSP Process As with previous OSI/AS and OSI/TS releases, X25AM and TLAM may still be specified as NSP processes, but if you want to run OSI applications over the Internet, you instead specify TCP/IP as the NSP process. A single Transport Service Provider (TSP) process can support TCP/IP, X25AM, and TLAM connections simultaneously. You do not need to add a separate TSP process to use RFC-1006.
Introduction to RFC-1006 Overview of the Tandem OSI Architecture Comparison of OSI and Internet Layer Architectures This section provides a brief summary of the OSI and Internet Layer architectures and describes how the OSI upper layers connect to the TCP/IP lower layers. Figure 1-3 shows each of the seven layers of the International Organization for Standardization (ISO) Reference Model with the comparable layer of the Internet Reference Model beside it. The Internet Reference Model has five layers.
Introduction to RFC-1006 Overview of the Tandem OSI Architecture OSI/AS and OSI/TS on Top of TCP/IP Figure 1-4 shows the combination of the OSI upper layers and the TCP/IP lower layers. The three OSI upper layers remain the same and provide the application services. The OSI Transport Protocol Data Units (TPDUs) interface with the TCP/IP Transport Layer through the sockets interface. Figure 1-5 illustrates the subsystem interfaces. Figure 1-4.
Introduction to RFC-1006 Overview of the Tandem OSI Architecture Figure 1-5.
Introduction to RFC-1006 Introduction to the Tandem TCP/IP Subsystem Introduction to the A Tandem TCP/IP subsystem runs on the Tandem NonStop Kernel operating system Tandem TCP/IP over a TLAM or X25AM I/O process. It has a wide range of capabilities provided by a Subsystem number of individual components that act alone or together. Figure 1-6 shows the Tandem TCP/IP subsystem components and their relationships to the TLAM, X25AM, and OSI/TS subsystems. Figure 1-6.
Introduction to RFC-1006 Introduction to the Tandem TCP/IP Subsystem Sockets Interface The TCP/IP subsystem components interface with the TCP/IP process through the sockets interface, as shown in Figure 1-6. The Tandem socket library routines are based on the sockets programmatic interface primitives in the UNIX operating system (BSD 4.3).
Introduction to RFC-1006 Introduction to the Tandem TCP/IP Subsystem See the Tandem TCP/IP Configuration and Management Manual for more information on Tandem TCP/IP components. TCP/IP Internet Addressing This section provides summary information on the Internet and Internet addressing. More detailed information on addressing is provided in the TCP/IP Configuration and Management Manual.
Introduction to RFC-1006 Introduction to the Tandem TCP/IP Subsystem Figure 1-7. Hosts and a Gateway in an Internetwork Network NETA Internet Address = 98.0.0.0 Network NETB Internet Address = 37.0.0.0 HOST9 37.1.0.8 HOST6 37.0.8.1 HOST1 98.0.2.9 Gateway HOST2 98.0.3.1 HOST4 98.0.1.6 37.0.4.1 HOST10 37.1.3.5 HOST7 37.0.3.9 HOST11 37.2.2.9 HOST3 98.0.7.4 HOST8 37.0.3.2 HOST12 37.2.8.1 095 As described in RFC 950, each network can be divided into a number of subnetworks, or subnets.
Introduction to RFC-1006 Introduction to the Tandem TCP/IP Subsystem Figure 1-8. Subnetworks Network NETA Internet Address = 98.0.0.0 Network NETB Internet Address = 37.0.0.0 Gateway HOST1 98.0.2.9 Gateway HOST4 98.0.1.6 37.0.4.1 HOST2 98.0.3.1 HOST6 37.0.8.1 37.1.0.1 Subnet NETC Internet Address = 37.1.0.0 HOST9 37.1.0.8 HOST10 37.1.3.5 HOST7 37.0.3.9 Subnet NETD Internet Address = 37.2.0.0 Gateway HOST3 98.0.7.4 HOST8 37.0.3.2 37.2.0.1 HOST11 37.2.2.9 HOST12 37.2.8.
Introduction to RFC-1006 Introduction to the Tandem TCP/IP Subsystem Every TCP/IP transport endpoint (socket) is addressable by the combination of an Internet protocol (IP) address and a port number. The connection between two applications can be identified by: The Internet address of the local node The port number of the application on the local node The Internet address of the remote node The port number of the application on the remote node Servers use ports 1 through 1023.
Introduction to RFC-1006 Introduction to the Tandem TCP/IP Subsystem Figure 1-9. Internet Address Formats Class A Address Bit 0 0 8 16 Network Address Class B Address Bit 0 16 Network Address Class C Address Bit 0 24 31 Local Address 8 1 1 0 31 Local Address 8 10 24 16 24 Network Address 31 Local Address Note: Bit 0 is the most significant bit.
Introduction to RFC-1006 Introduction to the Tandem TCP/IP Subsystem Tandem TCP/IP Subnet Addressing Tandem TCP/IP defines a IP address on a Tandem system by use of the TCP/IP SCF SUBNET object. Each subnet is represented by an IP address. Through each subnet, the TCP/IP process interfaces with each TLAM or X25AM IOP and controller. Figure 1-11 illustrates what subnets on HOST9 (shown in Figure 1-8) might look like. Figure 1-11.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 Changes in the This section provides an overview of the following features of OSI/TS when using Transport Layer When RFC-1006: Using RFC-1006 Transport Layer protocols: OSI transport protocol class 0 is used along with Transmission Control Protocol (TCP). Transport service user data: Exchange of transport user data during connection establishment is supported. Transport expedited data: Transport expedited data service is supported.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 Transport Service User Data When TCP/IP is the NSP process, user data is exchanged during connection establishment. Up to 32 octets of transport service user data can be exchanged during connection establishment in CR-TPDUs and CC-TPDUs. If you use a CONTROL 17 or CONTROL 11 procedure to request or respond to connection establishment, user data cannot be sent in the CR- and CC-TPDUs.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 The following TPDUs are not used by OSI/TS when using RFC-1006: AK-TPDU EA-TPDU RJ-TPDU DC-TPDU Note RFC983 is an earlier version of a protocol for connecting ISO transport services on top of the TCP, and it was superseded by the RFC1006 standard.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 Transport Packet Header This field contains the following three fields: Version This field is 8 bits long. It has the value of 3, which represents Version 3 of the RFC 1006 standard. Reserved This field is unused. Packet Length This field is 16 bits long. It indicates the length of entire TCP transport packet, in octets. This length is the length of the transport packet header (4 octets) plus the length of the TPDU.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 Table 1-3. OSI Transport Service Primitives Connection Establishment Primitive Function T-CONNECT.REQUEST A calling transport service user indicates that it wants to establish a connection. A called transport service user indicates that it is waiting for an incoming connection. A called transport service user is notified that connection establishment is in progress.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 OSI Network Service Primitives The OSI Network Layer provides the following OSI network service primitives, as defined in ISO 8073, to the network service user, with the exception of N-ATTACH, which is a Tandem-specific primitive. Table 1-4 describes the network Service primitive. Table 1-4. OSI Network Service Primitives Connection Establishment Primitive Function N-CONNECT.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 TCP Service Primitives TCP offers the following service primitives to the transport and network user, as defined in RFC 793 and as shown in Table 1-5. Table 1-5. Internet TCP Service Primitives Events Primitive Function Connected Connect fails Data ready Errored Closed Open succeeded (ACTIVE or PASSIVE). ACTIVE open failed. Data can be read from the connection. Connection has an error and is now closed.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 Table 1-6. Service Primitives Mapping Connection Establishment OSI NS Primitive TCP Primitive Sockets Calls File-System Calls N-CONNECT. REQUEST ACTIVE open Control 17 N-ATTACH PASSIVE open N-CONNECT. INDICATION N-CONNECT. RESPONSE N-CONNECT.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 Parameter Mapping Between OSI Network Service and TCP Table 1-7 lists the OSI network service primitives parameters and shows the corresponding TCP service primitives parameters. Table 1-7.
Introduction to RFC-1006 Changes in the Transport Layer When Using RFC-1006 is performed on the server (by calling Accept_nw2 socket routine). This will result in an N-CONNECTION.CONFIRMATION event on the transport service client. In OSI/TS, a TS server does not listen (perform a PASSIVE open, or perform an NATTACH action) until the called TS-user performs a T-ATTACH action.
2 RFC-1006 Subsystem Configuration This section describes how to configure your OSI/TS and OSI/AS subsystems interactively, using SCF, when using RFC-1006. The configuration information presented in this section is for the Tandem RFC-1006 implementation only. To configure OSI/TS or OSI/AS using TLAM or X25AM as the NSP process, see the Tandem OSI/TS Manual or the Tandem OSI/AS Configuration and Management Manual.
RFC-1006 Subsystem Configuration Configuring OSI/TS Configuring OSI/TS This section contains the following information: OSI/TS SCF attributes used for TCP/IP protocol selection Configuring OSI/TS, TCP/IP, and NSP processes New OSI/TS startup PARAMs for RFC-1006 OSI/TS SCF Attributes Used for TCP/IP Protocol Selection The OSI/TS Transport Service Provider (TSP) process performs services on behalf of an associated OSI/TS subdevice (SU) object—when the SU is acting as a client (initiator) or server (respon
RFC-1006 Subsystem Configuration Configuring OSI/TS Transport Protocol Class The CLASS attribute specifies the preferred protocol class. For RFC-1006, CLASS must be 0. If the protocol class is configured with a value other than 0, during connection establishment, OSI/TS will reject the connection attempt. To configure the protocol class, use the ADD SU command with the CLASS attribute. The command syntax is: ADD [ SU su-name ] ,[ CLASS { 0 | 1 | 2 | 3 | 4 } ] Example: ADD SU $TSP2.#TP10, CLASS 0 ...
RFC-1006 Subsystem Configuration Configuring OSI/TS To configure the remote IP address, use the ADD SU command with the REMOTENSAP attribute. The command syntax is: ADD [ SU su-name ] , [ REMOTENSAP “address” ] address is the remote IP address. Examples: ADD ADD ADD ADD SU SU SU SU $TSP2.#TP10, LOCALNSAP $TSP2.#TP10, LOCALNSAP $TSP2.#TP7, REMOTENSAP $TSP2.#TP7, REMOTENSAP "130.252.12.3" ... "82FC0C03" ... "130.252.12.3" ... "82FC0C03" ...
RFC-1006 Subsystem Configuration Configuring OSI/TS Configuring OSI/TS, TCP/IP, and NSP Processes This section describes how to configure OSI/TS with TCP/IP and the underlying subsystems. Figure 2-1 shows configurations on four separate Tandem systems. Figure 2-1 only shows TLAM connections, however, the same configurations can be made when connecting TCP/IP to X25AM IOPs. System A has a simple configuration, with one OSI/TS process connected to one TCP/IP process, connected to one TLAM I/O process (IOP).
RFC-1006 Subsystem Configuration Configuring OSI/TS Figure 2-1.
RFC-1006 Subsystem Configuration Configuring OSI/TS Note The following pages describe various connection possibilities between OSI/TS and TCP/IP. Read through each example in the order in which they are presented. The more complex examples may be easier to understand if you read the simpler examples first. There are some differences that may be easier to understand when read in the order they are presented. The examples show the same configuration on each side of the connection.
RFC-1006 Subsystem Configuration Configuring OSI/TS Single TSP Process Interfacing With a Single TCP/IP Process When you use the SCF ADD SU command and assign a local or remote IP address to an SU by specifying the local or remote NSAP, you are defining a specific path for connections that will be made to or from that SU. Figure 2-2 illustrates the client and server roles for a single TSP process interfacing with a single TCP/IP process. Figure 2-2.
RFC-1006 Subsystem Configuration Configuring OSI/TS TSP Process in Client Role When the TSP process is in the client role as shown in Figure 2-2, if you assign local IP address IPAddress1 to #lan1a, all outgoing connection requests are routed via Subnet1; if you assign the remote IP address IPAddress3 to #lan1a, the incoming connect requests on the server side of the connection are routed through Subnet3.
RFC-1006 Subsystem Configuration Configuring OSI/TS Single TSP Process Interfacing With Multiple TCP/IP Processes Figure 2-3 illustrates the client and server roles for a single TSP process interfacing with multiple TCP/IP processes. Better performance may be achieved by only running one TCP/IP process per system. Figure 2-3. Single TSP Process Interfacing With Multiple TCP/IP Processes Tandem NonStop System A - in the client role SU $tsp1.#lan1a SU $tsp1.#lan1b SU $tsp1.
RFC-1006 Subsystem Configuration Configuring OSI/TS TSP Process in Client Role In the client role, the subdevices attached to TSP1 have a choice of which NSPDEVICE to use, either TCP/IP1 or TCP/IP2. Once this assignment is decided, this example is essentially the same as for a single TSP process client process interfacing with a single TCP/IP process. REMOTENSAP is required and specifies the remote IP address on the server side of the connection. LOCALNSAP is optional.
RFC-1006 Subsystem Configuration Configuring OSI/TS Multiple TSP Processes Interfacing With a Single TCP/IP Process It is possible to configure multiple TSP processes to interface with a single TCP/IP process, but this type of configuration may result in poor performance because the TCP/IP process has more work to do than a TSP process. Figure 2-4 illustrates the client and server roles for multiple TSP processes interfacing with a single TCP/IP process. Figure 2-4.
RFC-1006 Subsystem Configuration Configuring OSI/TS TSP Process in Client Role NSPDEVICE is required and must specify TCP/IP1. REMOTENSAP is required and specifies the remote IP address on the server side of the connection. LOCALNSAP is optional. If you don’t specify it, TCP/IP uses its routing table to determine which local IP address or subnet to use and will use whatever subnet is available. Examples 1 and 2 associate the SUs with the local TCP/IP process and the remote IP addresses.
RFC-1006 Subsystem Configuration Configuring OSI/TS TSP^TCPIP^BUF^SIZE PARAM TSP^TCPIP^BUF^SIZE [ buffer-size ] TSP^TCPIP^BUF^SIZE This parameter specifies the size (in bytes) of a dedicated OSI/TS buffer used for receiving and storing incoming data on each TCP/IP connection (subdevice). It is used by the calling and responding sides of a connection. This buffer is allocated during connection establishment and is deallocated after connection release.
RFC-1006 Subsystem Configuration Configuring OSI/AS Configuring OSI/AS OSI/AS SCF Attributes Used for TCP/IP Protocol Selection This section describes the attributes an OSI/AS user needs to configure the OSI/AS subsystem to use TCP/IP as the NSP process. Table 2-2 summarizes the OSI/AS SCF attributes that have meaning when using RFC1006. Section 3, “RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems,” describes the SCF attributes in more detail. Table 2-2.
RFC-1006 Subsystem Configuration Configuring OSI/AS Use the INFO PROFILE #L4 or INFO SERVICE #L4 command to see the configured CLASS attribute. Expedited Data The EXPEDITED attribute specifies whether the transport expedited data transfer service is supported. This attribute is valid when TCP/IP is the NSP. To enable the expedited data transfer service, use the ADD PROFILE #L4 command with the EXPEDITED attribute.
RFC-1006 Subsystem Configuration Configuring OSI/AS If you want to check the status of the NSP process, use STATUS PROCESS command with the DETAIL option. 2. Use the ADD PROCESS command to register a TSP process name with the OSI manager process. The command syntax is: ADD [ PROCESS indirect-process-name ] , { NAME guardian-process-name } guardian-process-name is the name of the TSP process. Example: ADD PROCESS $OSIM.#TSP.
RFC-1006 Subsystem Configuration Configuring OSI/AS 2. Use the ADD ENTRY #NSAP command to register the local NSAP entry (IP address) with the OSI manager. This step also associates the SNPA entry (from Step 1) with this NSAP entry and assigns a TSP process to handle all connections that use this NSAP entry. The command syntax is: ADD [ ENTRY entry-name ] , [ L4SERVER indirect-process-name ] , [ NETADDR-MODE { NORMAL | X25-1980 } ] [ SNPA string ] entry-name specifies the NSAP, the local IP address.
RFC-1006 Subsystem Configuration Configuring OSI/AS TPDU Size To configure the TPDU size, use the ADD PROFILE #L4 command with the TPDUSIZE attribute. The command syntax is: ADD [ PROFILE profile-name ] , TPDUSIZE { 128 | 256 | 512 | 1024 | 2048 | 4096 | 8192 | 16384 | 32768 | 65531 } Example: ADD PROFILE $OSIM.#L4.PROF2, TPDUSIZE 65531 Use the ALTER PROFILE #L4 or ALTER SERVICE #L4 command to change the value of the TPDUSIZE attribute.
RFC-1006 Subsystem Configuration Configuring OSI/AS (This page left intentionally blank) 2–20 107751 Tandem Computers Incorporated
3 RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems This section describes RFC-1006 changes to: OSI/TS SCF commands OSI/AS SCF commands Other useful SCF commands OSI/TS Event Messages OSI/AS and OSI/TS PTrace records OSI/TS SCF The following OSI/TS SCF attributes have new meaning and new values when using Commands Changed TCP/IP as the NSP: to Support RFC-1006 CLASS EXPEDITED LOCALNSAP NSPDEVICE REMOTENSAP TPDUSIZE These attributes are used in the following commands: ADD SU ALTER SERVICE #L4 ALTER SU
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 This section provides a description of these commands in alphabetical order. Descriptions are provided only for those attributes and display fields whose meanings have changed for RFC-1006. Display fields whose meanings have changed for RFC-1006 are displayed in boldface.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 LOCALNSAP (ZLOC-NSAP) defines the local IP address for TCP/IP networks. Value: Dotted decimal notation or eight-digit hexadecimal string. Default: No default value is provided. NSPDEVICE (ZNSP-DEV) specifies the name of the local TCP/IP process. The TCP/IP process must exist, but does not need to be on the same system as the OSI subsystem.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 ALTER SERVICE #L4 The following attribute-specs for the ALTER SERVICE #L4 command have new meaning when using RFC-1006: [ CLASS { 0 | 1 | 2 | 3 | 4 } [ EXPEDITED { ON | OFF } [ TPDUSIZE { 128 | 256 | 512 | 1024 | 2048 | 4096 | 8192 | 16384 | 32768 | 65531 } ] ] ] CLASS (ZCLASS) specifies the preferred transport protocol class. Value: For TCP/IP networks, CLASS must be 0.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 Note ALTER SU The OSI/AS MAXCONNECTIONS attribute can restrict the size of the SPDU sent to OSI/TS. Specifying a smaller value for MAXCONNECTIONS allows the TAPS process to send larger SPDUs. Both the Tandem OSI/AS SCF Reference Manual and the Tandem OSI/AS Configuration and Management Manual discuss the MAXCONNECTIONS attribute in more detail.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 REMOTENSAP (ZRMT-NSAP) defines the remote IP address for TCP/IP networks. RESET returns this attribute to the default value (no address specified). Value: Dotted decimal notation or eight-digit hexadecimal string. TPDUSIZE (ZTPDU-SIZE) specifies, in bytes, the maximum length of a TPDU. The TPDU size is negotiated between transport peers. The calling transport entity proposes a TPDU size in the CR-TPDU.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 The format of the display for the CHECK SU command with the DETAIL option is: OSITS Detailed Check SU $DG4L.* -------------------------------------------------------------------ASU: -------------------------------------------------------------------TAP: OSIAS Detailed Status SU $DG5L.#ZDG0001 State............... Opens............... Opener.............. Opener Id........... Loopback............
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 Called Address: (REMOTE) Application Name.. R0000 AETitle AETitle Format.. 0 AEQualifier..... APTitle......... PSel.............. SSel.............. TSel.............. NSAP.............. 6100 6100 6100 82FC 00 00 00 0C39 (130.252.12.57) Responding Address: (REMOTE) Application Name.. AETitle: AETitle Format.. 0 AEQualifier..... APTitle......... PSel.............. SSel.............. TSel..............
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 Expedited shows whether the transport expedited data transfer service is supported. NSAP (for the Calling, Called and Responding Address) shows the IP address for the application entry name. Both the dotted decimal notation and eight-digit hexadecimal string are displayed. NSP SU shows the name of the network I/O process subdevice created by TSP to convey transport protocol data units (TPDUs).
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 RemoteNSAP shows the remote IP address. Both the dotted decimal notation and the eight-digit hexadecimal string are displayed. NSP: You must issue the appropriate TCP/IP SCF command to obtain information on the TCP/IP subsystem. INFO SERVICE #L4 The format of the display for the INFO SERVICE #L4 command without the DETAIL option is: OSITS Info SERVICE Name $WHC1.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 Class (ZCLASS) shows the preferred protocol class. Expedited (ZEXPEDITED) shows whether the transport expedited data transfer service is supported. TPDUSize (ZTPDU-SIZE) shows, in octets, the maximum length of a TPDU. INFO SU The format of the display for the INFO SU command without the DETAIL option is: OSITS Info SU Name $WHC1.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 Class (ZCLASS) shows the preferred protocol class. Expedited (ZEXPEDITED) shows whether the transport expedited data transfer service is supported. LocalNSAP (ZLOC-NSAP) shows the local IP address. Both the dotted decimal notation and eight-digit hexadecimal string are displayed. NSPDevice (ZNSP-DEV) shows the name of the local TCP/IP process. RemoteNSAP (ZRMT-NSAP) shows the remote IP address.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS SCF Commands Changed to Support RFC-1006 NSP SU (ZNSP-SU) shows the name of the network I/O process subdevice created by TSP to convey transport protocol data units (TPDUs). The name shows either a network I/O process subdevice currently in use for an active transport connection or for receiving a connection, or the name is the network I/O process subdevice last used by the TSP to convey TPDUs over this subdevice.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 OSI/AS SCF The following SCF/AS attributes have new meaning and new values when using Commands Changed TCP/IP as the NSP: to Support RFC-1006 CLASS EXPEDITED NAME NSAP TPDUSIZE These attributes are used in the following commands: ADD ENTRY #APPL ADD ENTRY #NSAP ADD ENTRY #SNPA ADD PROCESS ADD PROFILE #L4 ALTER ENTRY #APPL ALTER ENTRY #NSAP ALTER ENTRY #SNPA ALTER PROCESS ALTER PROFILE #L4 ALTER SERVICE #
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 This section provides a description of these commands in alphabetical order. Descriptions are provided only for those attributes and display fields whose meanings have changed for RFC-1006. Display fields whose meanings have changed for RFC-1006 are displayed in boldface.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 ADD ENTRY #APPL The following attribute-specs for the ADD ENTRY #APPL command have new meaning when using RFC-1006: [ L3SERVER indirect-process-name ] [ NSAP string ] L3SERVER (ZL3-SERVR) defines the name of the TCP/IP process that establishes the TCP connection for this #APPL entry. This attribute is used only for local entry names. Value: An NSP process name in the following format: $osi-mgr-name.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 The following attribute-spec for the ADD ENTRY #SNPA command has a new meaning when using RFC-1006: [ L3SERVER indirect-process-name ] L3SERVER (ZL3-SERVR) defines the name of the local TCP/IP process that services the local SNPA. This is a required attribute for local SNPAs only. Value: A TCP/IP process name in the following format: $osi-mgr-name.#NSP.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 ADD PROFILE #L4 The following attribute-specs for the ADD PROFILE #L4 command have new meaning when using RFC-1006: [ CLASS { 0 | 1 | 2 | 3 | 4 } [ EXPEDITED { ON | OFF } [ TPDUSIZE { 128 | 256 | 512 | 1024 | 2048 | 4096 | 8192 | 16384 | 32768 | 65531 } ] ] ] CLASS (ZCLASS) specifies the preferred transport protocol class. Value: For TCP/IP networks, CLASS must be 0.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 Note The OSI/AS MAXCONNECTIONS attribute can restrict the size of the SPDU sent to OSI/TS. Specifying a smaller value for MAXCONNECTIONS allows the TAPS process to send larger SPDUs. Both the Tandem OSI/AS SCF Reference Manual and the Tandem OSI/AS Configuration and Management Manual discuss the MAXCONNECTIONS attribute in more detail.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 ALTER ENTRY #SNPA The SNPA entry name only represents a Tandem internal number, not the real local SNPA address. It is used internally to eventually associate an NSP process with an NSAP address (IP address). The NSP process handles all connections that use the specified NSAP address. For more details on internal numbers, refer to the SCF Reference Manual for Tandem OSI/AS.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 Value: A TCP/IP process name in the following format: [\system].$process-name The name of a TCP/IP process located on the same system as the OSI manager process can be up to six characters (the $ sign followed by five characters).
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 Use the INFO SU command to see the value of the configured TPDUSIZE. Use the STATUS SU command to see the actual TPDUSIZE used when the connection was established. Value: 128 | 256 | 512 | 1024 | 2048 | 4096 | 8192 | 16384 | 32768 | 65531 Note The OSI/AS MAXCONNECTIONS attribute can restrict the size of the SPDU sent to OSI/TS.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 TPDUSIZE (ZTPDU-SIZE) specifies, in bytes, the maximum length of a TPDU. The TPDU size is negotiated between transport peers. The calling transport entity proposes a TPDU size in the CR-TPDU. The called transport entity compares this proposed value with its own value and specifies the smaller of the two values as the negotiated value in the CC-TPDU sent to the calling transport entity.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 CHECK ENTRY The format of the display for the CHECK ENTRY command is: OSIAS Detailed Check ENTRY $DGM.#APPL.L0000 #APPL entry values: *AEQualifier.. *APTitle...... *PSel......... 600000 *SSel......... 600000 *TSel......... 600000 *NSAP......... 82FC6FEB (130.252.111.235) *Loopback..... OFF *DeleteTime... -1 (static SU) *L5Profile.... *L4Profile.... *L3Profile.... *L5Server..... *L4Server..... *L3Server.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 L4 Service: *Altclass................ *CheckTSel............... *Connecttimeout.......... *Expedited............... *Inactivetimeout......... *InboundCRCongestionThld. *InboundTPDUProtoErrThld. *L4TimeoutThld........... *MaxRexmit............... *NetType................. *OutboundCRErrThld....... *PassiveMUX.............. *RecvSecurity............ *RefTimeout.............. *SendSecurity............
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 L3Server shows the L3 server that was specified when the SNPA entry was configured. Class shows the preferred transport protocol class value. Expedited shows whether the transport expedited data transfer service is supported. TPDUSize shows, in octets, the maximum length of a TPDU.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 The format of the display for the CHECK SU command with the DETAIL option is: OSIAS Detailed Check SU $DG5L.#ZDG0001 -------------------------------------------------------------------ASU: -------------------------------------------------------------------TAP: OSIAS Detailed Status SU $DG5L.#ZDG0001 State............... Opens............... Opener.............. Opener Id........... Loopback............
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 Called Address: (REMOTE) Application Name.. R0000 AETitle AETitle Format.. 0 AEQualifier..... APTitle......... PSel.............. SSel.............. TSel.............. NSAP.............. 6100 6100 6100 82FC 00 00 00 0C39 (130.252.12.57) Responding Address: (REMOTE) Application Name.. AETitle: AETitle Format.. 0 AEQualifier..... APTitle......... PSel.............. SSel.............. TSel..............
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 NSAP (for the Calling, Called and Responding Address) shows the IP address for the application entry name. Both the dotted decimal notation and the eight-digit hexadecimal string are displayed. NSP SU shows the name of the network I/O process subdevice created by TSP to convey transport protocol data units (TPDUs).
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 NSP: You must issue the appropriate TCP/IP SCF command to obtain information on the TCP/IP subsystem. INFO ENTRY #APPL The format of the display for the INFO ENTRY #APPL command is: OSIAS Detailed Info ENTRY \PENGUIN.$E250R.#APPL.B00L *AEQualifier.. *APTitle...... *PSel......... *SSel......... *TSel......... *NSAP......... *Loopback..... *DeleteTime... *L5Profile.... *L4Profile.... *L3Profile....
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 The format of the display for the INFO ENTRY #NSAP command with the DETAIL option is: OSIAS Detailed Info ENTRY \PENGUIN.$E250R.#NSAP.82FC2898 (130.252.40.152) *SNPA......... *NetAddr-Mode. *L4Profile.... *L3Profile.... *L4Server..... 5354 NORMAL $E250R.#L4.L4PFILE1 $E250R.#TSP.O4ARN Name shows the name of the ENTRY object. NetAddr-Mode (ZNETADDR-MODE) shows the addressing mode of the network service.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 INFO PROCESS The format of the display for the INFO PROCESS command without the DETAIL option is: OSIAS Info PROCESS *Name *Primary *Backup CPU CPU 1 2 $E250R *Priority *Codefile 149 \PENGUIN.$DATA3.OSID30.OSIMGRR Name (ZNAME) shows the name of the PROCESS object. This is the only field in the display for NSP processes.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 The format of the display for the INFO PROFILE #L4 command with the DETAIL option is: OSIAS Detailed Info PROFILE \PENGUIN.$E250R.#L4.L4PFILE2 *Altclass......... *Class............ *Disconntimeout... *Extendedformat... *L4window......... *Multiplex........ *Recvsecurity..... *Rexmittimeout.... *Tconpri.......... *TTRtimeout....... *Windowtimeout.... 0 0 0:02:00.00 OFF 4 OFF 0:00:10.00 0 0:01:30.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 OSIAS Detailed Info SERVICE \PENGUIN.$E250R.#L4 *Altclass................ *CheckTSel............... *Connecttimeout.......... *Expedited............... *Inactivetimeout......... *InboundCRCongestionThld. *InboundTPDUProtoErrThld. *L4TimeoutThld........... *MaxRexmit............... *NetType................. *OutboundCRErrThld....... *PassiveMUX.............. *RecvSecurity............ *RefTimeout..........
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/AS SCF Commands Changed to Support RFC-1006 SUBSYS (ZCOM-TKN-OBJNAME in LISTOBJECTS SUBSYS command) shows a list of the SUBSYS objects associated with the OSI manager process. STATUS SU The format of the display for the STATUS SU command with the DETAIL option is: OSIAS Detailed Status SU \PENGUIN.$E5ARP.#Z000000 State............... Opens............... Opener.............. Opener Id........... Loopback............ DeleteTime..........
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems Other Useful SCF Commands NSAP.............. 82FC 2898 (130.252.40.152) Responding Address: (LOCAL) Application Name.. B00R AETitle: AETitle Format.. 0 AEQualifier..... APTitle......... PSel.............. SSel.............. 5354 TSel.............. 5354 NSAP.............. 82FC 2898 (130.252.40.152) Expedited (ZFU-EXPEDITED) shows whether the transport expedited data transfer service is supported.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems Other Useful SCF Commands OSITS Stats SERVICE $MTS0.#L4 Reset Time.. 16 Apr 1991, 10:04:02.899 Sample Time. 16 Apr 1991, 12:31:42.524 TPDUs-sent................................... 0 TPDUs-received............................... 0 TPDUs-resent................................. 0 UserBytes-sent............................... UserBytes-received........................... ExpBytes-sent................................ ExpBytes-received......................
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems Other Useful SCF Commands UserBytes-sent shows the number of octets of user data that have been sent and acknowledged. UserBytes-received shows the number of octets of nonduplicate data received and returned to the user application. ExpBytes-sent shows the number of octets of user data that have been sent in expedited TPDUs and acknowledged.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems Other Useful SCF Commands InboundTPDUProtoErr is the number of times OSI/TS receives a TPDU (other than CR-TPDU) that can be associated with a transport connection and is invalid or constitutes a protocol error. InboundTPDUProtoErrThld shows the threshold number against which the counter InboundTPDUProtoErr is compared. InboundTPDUXsumErr is the number of times OSI/TS discarded a TPDU due to checksum failure.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems Other Useful SCF Commands OutboundTPDUProtoErr is the number of times OSI/TS receives a DR-TPDU or ER-TPDU as the response to any TPDU it initiated other than the CR-TPDU. OutboundTPDUProtoErrThld shows the threshold number against which the counter OutboundTPDUProtoErr is compared. Current-Tcon shows the number of open transport connections; it is modified every time a transport connection is established or released.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems Other Useful SCF Commands SUBNETMASK is a 32-bit integer that specifies which portion of the network number and the IP host address is to be masked to define a subnet. STATS SU Command The format of the display for the STATS SU command is: OSITS Stats SU $MTS0.#Z123123 Reset Time.. 16 Apr 1991, 10:12:54.386 Sample Time. 16 Apr 1991, 12:31:57.054 TPDUsSent......... TPDUsResent....... UserBytesSent..... ExpeditedBytesSent 0 0 0 0 TPDUsRecv.........
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems Other Useful SCF Commands ExpeditedBytesRecv shows the number of octets of nonduplicate data received in expedited TPDUs that were returned to the user application. STATUS PROCESS Command The format of the display for the STATUS PROCESS command for a TCP/IP process is: SCF> STATUS PROCESS TCPIP Status PROCESS \SYSA.$ZTC0 Status: STARTED Proto State TCP TIME-WAIT TCP TIME-WAIT TCP ESTAB TCP TIME-WAIT Laddr 130.252.12.3 130.252.12.3 130.252.12.3 130.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems Other Useful SCF Commands FIN-WAIT-1 if waiting for a terminate connection request from the remote TCP site or if waiting for acknowledgment of the terminate connection request, the process has sent previously. FIN-WAIT-2 if waiting for a termination of data to be received after having sent a FIN (termination of data being sent). CLOSE-WAIT if waiting for a terminate connection request from the local user.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS EMS Event Changed to Support RFC-1006 SendQ is the number of bytes of data in the send queue of the socket. RecvQ is the number of bytes of data in the receive queue of the socket. OSI/TS EMS Event The following event message has a new meaning when using RFC-1006: Changed to Support RFC-1006 309: ZOS4-EVT-ACCESSERR 3–44 This is not a critical event.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS EMS Event Changed to Support RFC-1006 Unconditional Tokens ZEMS-TKN-EMPHASIS ZEMS-TKN-CONSOLE-PRINT ZCOM-TKN-SUBJ-PROC ZSPI-TKN-ERRLIST ZSPI-TKN-ERROR ZSPI-TKN-PROC-ERR ZTCI-TKN-SOCK-FUNC ZSPI-TKN-FUNCTION ZFIL-TKN-FILENAME ZFIL-TKN-XFILENAME ZSI-TKN-ENDLIST token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type token-type ZSPI-TYP-BOOLEAN. ZSPI-TYP-BOOLEAN. ZSPI-TYP-CRTPID.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems OSI/TS EMS Event Changed to Support RFC-1006 ZSPI-TKN-ERRLIST and ZSPI-TKN-ENDLIST enclose a standard SPI error list, as described in the Distributed Systems Management (DSM) Programming Manual. The contents of this error list provide information on the file-system error that occurred. ZSPI-TKN-ERROR is the standard SPI error token described in the Distributed Systems Management (DSM) Programming Manual.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems PTrace Records Changed to Support RFC-1006 ZFIL-TKN-FILENAME for C-series systems, is the name of the file on which the error occurred. ZFIL-TKN-XFILENAME for D-series systems, is the name of the file on which the error occurred. Probable Cause OSI/TS reports this event for one of the following reasons: The OSI/TS subdevice is configured incorrectly. For a TSP process that is part of an OSI/AS subsystem, the OSIMGR database is configured incorrectly.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems PTrace Records Changed to Support RFC-1006 New NetIO operation types, representing TCP/IP socket functions, are shown in the PTrace displays. In cases where the socket operation includes a copy of the SOCKADDR_IN structure as a parameter, PTrace produces a formatted display of the TCP port number and IP address if the PTrace user has requested DETAIL ON. Sample NetIO records are shown below.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems PTrace Records Changed to Support RFC-1006 Port No shows the TCP port number used in the request. IP Address shows the IP address used in the request, if any. If this number shows as 0.0.0.0 when it is a bind, the TSP process will accept incoming connection requests on any available TCP/IP subnet. NetIO Open-NoWait Control Block The following trace record is for Tandem internal use only and shows the starting of a No-Wait process-file OPEN operation.
RFC-1006 Changes to the SCF, SPI, and PTrace Subsystems PTrace Records Changed to Support RFC-1006 (This 3–50 page left intentionally blank) 107751 Tandem Computers Incorporated
4 RFC-1006 Configuration Command Files This section contains examples of command files of operating system and SCF commands to set up particular subsystem configurations. Since each of these examples contains a mixture of SCF and non-SCF commands, use the OBEY command to invoke the appropriate file.
RFC-1006 Configuration Command Files IP Address Conversion Program Alternatively, you may be able to make use of the following SCF commands, as the displays for these commands show both IP address formats: Command CHECK ENTRY CHECK SU INFO ENTRY #NSAP INFO SU, DETAIL STATUS SU, DETAIL OSI/TS X X X OSI/AS X X X X X The source-code file for this example is provided as part of the OSI/TS software. It resides (by default) in $SYSTEM.ZOSITS.EXADCVTC. Below is the source code of this program.
RFC-1006 Configuration Command Files OSI/AS Configuration Example /* * It must be an 8-digit hex string */ if (strlen(argv[1]) == 8) { DNUMIN(argv[1], &l, 16, &error, PLAIN_FLAG); if (!error) { in.
RFC-1006 Configuration Command Files OSI/AS Configuration Example fup purge (ZOSIDB,ZOSIDB0) ! fup /in dbfup/ == == Create new OSI manager process. == $SYSTEM.SYS01.OSIMGR/nowait, name $OSIM, swap $DISK1 , cpu 2/ 3 & ============================================================= == SCF commands for configuring the subsystem: ============================================================= allow all errors ============================================================= == Configure OSI manager process.
RFC-1006 Configuration Command Files OSI/TS Configuration Example ==== (SNPA assignment is not needed for remote NSAPs.) ==== IP address can be entered in dotted decimal notation ==== or in an eight-digit hex string. ==== add entry $OSIM.#nsap.133.205.1.57 ==== ==== Add TSEL information for local TSEL. ==== add entry $OSIM.#tsel.44a1 & , l5server $OSIM.#taps.TAPS1 , profile $OSIM.#L5.L5p1 & ==== ==== Add address information for remote TSEL. ==== add entry $OSIM.#tsel.
RFC-1006 Configuration Command Files OSI/TS Configuration Example == before you use the OBEY command to invoke this file. == == NOTE: Before using this command file, you must supply == names and addresses that reflect your environment. ============================================================= == allow all errors == == Abort any processes and subdevices that are running and == that have the same name as you are configuring. == abort su ($tsp1.*, $tsp2.*) == Allow time to clean up all SUs.
RFC-1006 Configuration Command Files OSI/TS Configuration Example add su $tsp2.#sub2 , , , , , , nspdevice $ztc1 localtsel "404142" remotetsel "505152" localnsap "133.205.1.57" remotensap "130.252.111.25" tpdusize 2048 & & & & & , , , , , , , class 0 nspdevice $ztc1 localtsel "606162" remotetsel "707172" localnsap "133.205.1.64" remotensap "130.252.111.32" tpdusize 8192 & & & & & & ============================================================= == Start the subdevices.
RFC-1006 Configuration Command Files OSI/MHS RS Group Configuration Example OSI/MHS RS Group This example shows how to configure an OSI/MHS RS Group to use RFC-1006. A Configuration Example similar example can be used to configure the other MHS groups. Figure 4-1 shows the configuration for this example. Figure 4-1.
RFC-1006 Configuration Command Files OSI/MHS RS Group Configuration Example ============================================================================ == OSI/MHS : RS Group Configuration File ============================================================================ == File name : GRRSRFC == File type : SCF command file == Description : Configuration for the RS group RS2: used with RFC 1006 == Version : OSI/MHS == Usage : File is used by START_MTA COLD or SCF ===========================================
RFC-1006 Configuration Command Files OSI/MHS RS Group Configuration Example == Add SNPA (Subnetwork point of attachment) DELETE #SNPA.123 ADD == == == == #SNPA.123 , SERVER $OMGR.#NSP.TCPIP2 Add NSAP (IP address) IP address can be entered in dotted decimal notation or in an eight-digit hex string. RS group rs2 is listening on RFC-1006 IP-Addr: 168.87.46.2 = %hA8572E02 DELETE #NSAP.168.87.46.2 ADD #NSAP.168.87.46.2 , SERVER $OMGR.#TSP.OTS1 , SNPA 123 , PROFILE #L4.
5 TPDUs Used by RFC-1006 This section describes the TPDUs that are used by RFC-1006. Table 5-1 lists the six TPDUs used by OSI/TS when using RFC-1006. Table 5-1.
TPDUs Used by RFC-1006 CC-TPDU CC-TPDU Connect Confirm (CC) TPDUs, when used with RFC-1006, are different from OSI/TS CC-TPDUs in the following ways: RFC-1006 permits you to select a much larger DT-TPDU size (up to 65531 octets). The size specified must not be larger than the proposed DT-TPDU size in the CRTPDU. RFC-1006 permits you to select the use of transport expedited data transfer service. This information is contained in the Variable Part field.
TPDUs Used by RFC-1006 CC-TPDU SRC-REF Identifies the responder that this CC-TPDU is being sent to. This value is in octets 5 and 6. Class Class specifies the selected OSI transport protocol class selected by the transport entity initiating the CC-TPDU. It has the value of 0000 and is in bits 8 to 5 of octet 7. Options Options is not used when using RFC-1006, it is set to 0000. It is in bits 4 to 1 of octet 7. Variable part The Variable part is used to define less frequently used parameters.
TPDUs Used by RFC-1006 CC-TPDU Parameter Code This field can contain either the TSAP-ID, the TPDU Size, or the Additional Option Selection: TSAP-ID When identifying the TSAP-ID (the configured SCF TSEL ENTRY object), the value of 1100 0001 identifies the called TSAP and the value of 1100 0010 identifies the called TSAP.
TPDUs Used by RFC-1006 CR-TPDU TPDU Size When identifying the TPDU Size, the values are as follows: Value TPDU Size 0001 0000 0000 1111 0000 1110 0000 1101 0000 1100 0000 1011 0000 1010 0000 1001 0000 1000 0000 0111 65531 32768 16384 8192 4096 2048 1024 512 256 128 Additional Option Selection When identifying the Additional Option Selection, if bit 1 is 1, transport ED transfer service is used; if bit 1 is 0, transport ED transfer service is not used.
TPDUs Used by RFC-1006 CR-TPDU Figure 5-3. CR-TPDU Octet 1 2 3,4 5,6 7 8-p LI CR CDT DST-REF SRC-REF Class Options Variable Part p+1,q User Data TPDU Header 060 LI The length indicator shows the TPDU header length in octets. This value does not include the length of the LI and User Data fields. The value is a binary number with a maximum value of 254 (1111 1110). This value is in octet 1. CR The connection request code is set to 1110. This value is in bits 8 to 5 of octet 2.
TPDUs Used by RFC-1006 CR-TPDU Variable Part The Variable part is used to define less frequently used parameters. Each defined parameter contains three fields: Parameter Code Parameter Length Indicator Parameter Value Information about the following three parameters can be included: Transport Service Access Point Identifier (TSAP-ID) TPDU Size Additional Option Selection - this field is always included in the CR-TPDU Figure 5-4 illustrates the Variable Part field of the CR-TPDU.
TPDUs Used by RFC-1006 CR-TPDU Additional Option Selection When identifying the Additional Option Selection, indicates if transport expedited data transfer service is used. The value is 1100 0110. Parameter Length Indicator This field can contain either the TSAP-ID, the TPDU Size, or the Additional Option Selection: TSAP-ID When identifying the TSAP-ID, indicates the length of the TSAP contained in Parameter Value. TPDU Size When identifying the TPDU Size, the value is 1 octet.
TPDUs Used by RFC-1006 DR-TPDU Additional Option Selection When identifying the Additional Option Selection, if bit 1 is 1, transport ED transfer service is used; if bit 1 is 0, transport ED transfer service is not used. User Data Up to 32 octets of transport user data are permitted in the CR-TPDU. DR-TPDU The Disconnect Request (DR) TPDU is unchanged when using RFC-1006. Figure 5-5 illustrates the DR-TPDU. Figure 5-5.
TPDUs Used by RFC-1006 DR-TPDU Reason The reason defines the cause of the transport connection disconnect. This field can have the following values: Value Meaning 0 1 2 3 A reason is not specified. Congestion at the TSAP. The Session entity is not attached to the TSAP. The address is unknown. Variable Part Contains additional information related to the clearing of the connection. Figure 5-6 illustrates the Variable Part field of the DR-TPDU.
TPDUs Used by RFC-1006 DT-TPDU DT-TPDU The Data Transfer (DT) TPDU is unchanged when using RFC-1006. Figure 5-7 illustrates the DT-TPDU. Figure 5-7. DT-TPDU Octet 1 LI 2 DT 3 4 to end TPDU-NR EOT User Data TPDU Header 070 LI The length indicator shows the TPDU header length in octets. This value does not include the length of LI and User Data and has the value of 2. DT The data transfer code is 1111 0000. This value is in octet 2.
TPDUs Used by RFC-1006 ED-TPDU ED-TPDU Expedited Data (ED) TPDUs, when used with RFC-1006, are different from OSI/TS ED-TPDUs. The new format of the ED-TPDU is similar to the DT-TPDU; the only difference is the value of the TPDU code. Figure 5-8 illustrates the RFC-1006 EDTPDU. Figure 5-8. ED-TPDU Octet 1 LI 2 3 ED TPDU-NR EOT 4 to end User Data TPDU Header 075 LI The length indicator shows the TPDU header length in octets.
TPDUs Used by RFC-1006 ER-TPDU ER-TPDU The Error (ER) TPDU is unchanged when using RFC-1006. Figure 5-9 illustrates the ER-TPDU. Figure 5-9. ER-TPDU Octet 1 2 LI ER 3,4 5 DST-REF Reject Cause 6-p Variable Part TPDU Header 115 LI The length indicator shows the TPDU header length in octets. This value does not include the length of LI and User data. The value is indicated by a binary number with a maximum value of 254 (1111 1110). This value is in octet 1. ER The error code is set to 0111 0000.
TPDUs Used by RFC-1006 ER-TPDU Variable Part Contains additional information on the rejected TPDU. Each defined parameter contains three fields: Parameter Code Parameter Length Indicator Parameter Value Figure 5-10 illustrates the Variable part field of the ER-TPDU. Figure 5-10. Variable Part of the ER-TPDU Bits 8 • • • Octets n+1 Parameter Code n+2 Parameter Length Indicator n+3 Parameter Value 1 110 Parameter Code The value is 1110 0001. Parameter Length Indicates the length of Parameter Value.
6 Socket Errors Returned by TCP/IP to OSI/TS This section lists the socket errors that can be returned in the external variable errno by the routines in the sockets interface library. This list is only a subset of the error codes sent by TCP/IP. Only those errors that can be received by the OSI/TS process are listed. The descriptions given here are general; you should interpret each error according to the type and circumstances of the call.
Socket Errors Returned by TCP/IP to OSI/TS 4108 ENOPROTOOPT Cause. A call to getsockopt_nw or setsockopt_nw specified an option that was unknown to the specified protocol. Effect. The call failed. Recovery. This is an internal error. 4110 ESOCKTNOSUPPORT Cause. The socket type specified in a call to socket_nw is not supported by the Tandem TCP/IP software. Effect. The call failed. Recovery. This is an internal error. 4113 EAFNOSUPPORT Cause.
Socket Errors Returned by TCP/IP to OSI/TS 4120 ECONNRESET Cause. The peer process reset the connection before the operation completed. Effect. The connect call failed. Recovery. Retry the call again later. 4123 ENOTCONN Cause. The specified socket was not connected (the connect_nw call has not been called yet). Effect. The call failed. Recovery. Ensure that the socket is connected, then retry the operation. 4124 ESHUTDOWN Cause.
Socket Errors Returned by TCP/IP to OSI/TS (This page left intentionally blank) 6–4 107751 Tandem Computers Incorporated
7 Programming With the Sockets Interface The programming steps that are required for a client or server program to communicate with TCP/IP are described in the Tandem TCP/IP Programming Manual or Tandem TCP/IP Applications User's Manual, but there are some minor differences when using RFC-1006, so this information is presented here for the reader's convenience. Table 7-1 summarizes the steps followed by a detailed description of each step. Table 7-1. Nowait Client and Server Steps Client 1. 2. 3. 4.
Programming With the Sockets Interface Programming a Server 2. Create a socket. The call to SOCKET_NW creates a socket. As part of its operation, it calls the OPEN procedure to open a file for interprocess communication. The socket number it returns actually is the file number obtained from OPEN. 3. Bind the socket to the local IP address and any client port from 1024 up. The BIND_NW call associates any local client port and the local Internet address with the socket.
Programming With the Sockets Interface Programming a Server 2. Create a socket. The call to SOCKET_NW creates a socket. As part of its operation, it calls the OPEN procedure to open a file for interprocess communication. The socket number it returns actually is the file number obtained from OPEN. 3. Bind the socket to a local well-known server port and the local IP address. The server calls BIND_NW to permanently associate the socket with the local wellknown port.
Programming With the Sockets Interface Programming a Server both). Calling SHUTDOWN is optional; if it is not done, the call to CLOSE performs the implicit SHUTDOWN function. 8. Close one socket or both of the sockets. To release the connection, call SHUTDOWN_NW and the CLOSE procedure on the second socket. The first socket created in step 2 should not be shut down or closed until the transport process is aborted.
8 General OSI/AS and OSI/TS Manual Changes and Corrections This section contains information of general interest to OSI/AS and OSI/TS users (not just RFC-1006 users). This section contains the following information: Descriptions of external changes that have been made since the C30.08/D10 product release of OSI/AS and OSI/TS Changes and corrections to the C30.08/D10 release of the OSI/AS and OSI/TS manuals This section is organized by of the Tandem Problem Report (TPR) that describes the problem.
General OSI/AS and OSI/TS Manual Changes and Corrections Detailed Description When using the Presentation Protocol, ISO 8823, in X.410-1984 mode, applications pass user data to remote applications in the user-data parameter of the APS_ASSOC_CONNECTREQ_ procedure. This user data is mapped directly, unchanged, as the “User data” parameter of the S-CONNNECT request session service primitive in the Session Layer. S 931219 1838 10619 Summary The OSI/TS example file EXEMST1 contains an error.
General OSI/AS and OSI/TS Manual Changes and Corrections The following pages give the corrected source code for this file. The source code file for this example is provided as part of the OSI/TS software. It resides (by default) in $SYSTEM.ZOSITS.EXEMST1.
General OSI/AS and OSI/TS Manual Changes and Corrections ! OSI/TS subsystem definitions ?NOLIST, SOURCE $system.zspidef.zos4tal ?LIST ! Global declarations LITERAL true = 1; LITERAL false = 0; INT .rcv^name[0:11] := ["$RECEIVE",8*[" "]], rcv, ! $RECEIVE file number .startup^msg[0:99], ct^rd, ! count read .distr^name[0:11] := [12*[" "]], distr, ! distributor file number .
General OSI/AS and OSI/TS Manual Changes and Corrections ! Filter name-related variables INT .coll^name[0:11] := ["$0",11*[" "]], .filt^name[0:11] := [12 *[" "]]; ! External declarations for GUARDIAN 90 and SPI procedures ?NOLIST ?SOURCE $SYSTEM.SYSTEM.
General OSI/AS and OSI/TS Manual Changes and Corrections END; ! WHILE END; ?PAGE ! *********************************************************** ! * send^spi^cmd * ! *********************************************************** ! ! ! ! ! This procedure puts the finishing touches on an SPI command that has been prepared by another procedure, such as the spi^cmd^set^source procedure below. The send^spi^cmd procedure subsequently sends the command to the distributor and checks the response.
General OSI/AS and OSI/TS Manual Changes and Corrections END; ?PAGE ! *********************************************************** ! * spi^cmd^set^source * ! *********************************************************** ! This procedure builds an SPI command that directs the ! distributor to use a collector as the source of event ! messages. INT PROC spi^cmd^set^source; BEGIN ! Initialize spi^buf for distributor CONTROL command.
General OSI/AS and OSI/TS Manual Changes and Corrections CALL DEBUG; ! Send the command to the distributor. spi^err := send^spi^cmd; RETURN spi^err; END; ?PAGE ! *********************************************************** ! * displ^event * ! *********************************************************** ! This procedure displays, at your terminal, the event ! message just retrieved. PROC displ^event(event^buf); INT .
General OSI/AS and OSI/TS Manual Changes and Corrections ?PAGE ! *********************************************************** ! * getevent^loop * ! *********************************************************** ! ! ! ! ! ! ! ! ! ! This procedure consists of a loop to retrieve event messages. Each time through the loop, the procedure gets an event message and calls displ^event to display it at your terminal.
General OSI/AS and OSI/TS Manual Changes and Corrections spi^err := SSMOVETKN(ZSPI^TKN^CONTEXT, spi^buf, 1, ! source sav^buf, 1); ! destination IF spi^err <> ZSPI^ERR^OK THEN CALL DEBUG; ! Move the updated command to spi^buf for next time ! through the loop.
General OSI/AS and OSI/TS Manual Changes and Corrections ! Create a name for the distributor process. CALL CREATEPROCESSNAME (distr^name); IF <> THEN CALL DEBUG; ! On the initial open (no SPI), the distributor will get ! the same startup message read by the application, but ! with a parameter string for type (C = CONSUMER). s^startup^param ':=' "TYPE C"; startup^msg[36] := 0; ! Terminate startup message. ! Start the distributor process.
General OSI/AS and OSI/TS Manual Changes and Corrections CALL STOP; END; S 931210 1343 14562 Summary The Tandem OSI/AS Management Programming Manual needs a better description of EMS token ZEMS-TKN-CRTPID. Manuals Affected Tandem OSI/AS Management Programming Manual Detailed Description The EMS token ZEMS-TKN-CRTPID is valid only on C-series systems or on D-series systems when running low pin.
General OSI/AS and OSI/TS Manual Changes and Corrections 2. some implementations require the binary value %H03010100 be included in the CUD Field to identify the Transport entity 3. some implementations require another binary value of up to 16 bytes (or 32 characters) of user-defined information be specified. OSI/TS users can now explicitly enable the sending of the transport protocol ID %H03010100 or a CUD Field value of their choice. The following exceptions apply: Fast Select is not supported.
General OSI/AS and OSI/TS Manual Changes and Corrections MAXCONNECTIONS specifies the maximum number of concurrent transport connections allowed within a TSP process. Value: 1 through 1024 Default: 1024 S 930930 1104 13659 Summary The ZNSP-TYPE field of the ZAPS-DDL-LL-ERROR-BUF contains a new value. Manuals Affected Tandem OSI/AS Programming Manual Detailed Description The following description for ZAPS-DDL-LL-ERROR-BUF shows the correct values for the ZNSP-TYPE field.
General OSI/AS and OSI/TS Manual Changes and Corrections ZNSP-TYPE specifies the type of connection. The named value ZAPS-VAL-NSP-xxx designates the connection type, as follows: ZAPS-VAL-NSP-X25 (value 1): X25AM connection ZAPS-VAL-NSP-LAN (value 2): TLAM connection ZAPS-VAL-NSP-TCPIP (value 3): TCP/IP connection S 930923 1534 9718 Summary There is garbled text in the last paragraph on page 2-11 in the Tandem OSI/AS Configuration and Management Manual.
General OSI/AS and OSI/TS Manual Changes and Corrections Detailed Description The OSI/AS MIB is now opened in protected mode so that it can be backed up while it is open. S 910906 2048 11518 Summary Support for larger object IDs has been added to OSI/AS.
General OSI/AS and OSI/TS Manual Changes and Corrections How Applications Use This Feature: Input of Expanded Object IDs: When an application needs to place an expanded object ID in part of an existing ZAPSDDL structure, it must first compress the expanded object ID by calling the new APS procedure, APS_OBJID_COMPRESS_. The compressed object ID, which occupies the same amount of space as the ZAPS-DDLOBJ-ID structure, can now be copied to the appropriate place in the ZAPSDDL structure.
General OSI/AS and OSI/TS Manual Changes and Corrections ZOBJ-ID is an array of up to 24 doubleword integers, representing up to 16 levels in the object identifier hierarchy. New APS_OBJID_COMPRESS_ procedure call: This new procedure converts an expanded object ID into a compressed object ID.
General OSI/AS and OSI/TS Manual Changes and Corrections error returned value Return values are: ZAPS-ERR-OK ZAPS-ERR-PARAM-BOUNDS ZAPS-ERR-PARAM-MISSING ZAPS-ERR-PARAMETER compressed-object-id input INT .EXT:ref:(ZAPS-DDL-OBJ-ID) is the compressed form of an object ID. expanded-object-id output INT .EXT:ref:(ZAPS-DDL-OBJ-ID-32) is the expanded form of an object ID. Considerations: If the object ID cannot be expanded, the error ZAPS-ERR-xxx parameter is returned.
General OSI/AS and OSI/TS Manual Changes and Corrections compress-objid input INT is a flag telling APS how to handle object IDs. The value ZAPS-VAL-TRUE indicates that all object IDs are returned through the APS_ASSOC_GETPARAM_ procedure in compressed form (regardless as to how they were given to APS). The value ZAPS-VAL-FALSE or the absence of the parameter indicates that no APS procedures return object IDs in compressed form.
General OSI/AS and OSI/TS Manual Changes and Corrections There are new considerations for this procedure. When using the Presentation Protocol, ISO 8823, in X.410-1984 mode, applications pass user data to remote applications in the user-data parameter of the APS_ASSOC_CONNECTREQ_ procedure. This user data is mapped directly, unchanged, as the “User data” parameter of the S-CONNNECT request session service primitive in the Session Layer.
General OSI/AS and OSI/TS Manual Changes and Corrections [ APTITLE { “{” list “}” | “(” list “)” } ] APTITLE defines the AP title for the #APPL entry being added or altered. AP title values are locally administered. Value: An APTITLE must be a valid ASN.1 object identifier. It must contain at least two integers, up to a maximum of 16 integers. The first integer must be between 0 and 2, inclusive. The second integer must be between 0 and 39, inclusive.
General OSI/AS and OSI/TS Manual Changes and Corrections def ZOSI-DDL-AS-TITLE-32. 02 ZAE-TITLE-TYPE 02 ZAE-TITLE-FORMAT-2. 03 ZAE-QUALIFIER-ISPRESENT 03 ZAE-QUALIFIER 03 ZAP-TITLE END. type ZOSI-DDL-INT. type ZSPI-BBL-BOOLEAN. type ZSPI-DDL-INT2. type ZOSI-OBJ-ID-32. ZAE-TITLE-TYPE specifies which type of application entity title is used. The following values are valid in this field: ZOSI-VAL-AE-TITLE-FORMAT0 No application entity title is used.
General OSI/AS and OSI/TS Manual Changes and Corrections The ZAE-TITLE-32 definition has been added to the ZOSI-DDL-ADD-ENTRY-APPL structure: def ZOSI-DDL-ADD-ENTRY-APPL. 02 ZSERV-LEV 02 ZPSAP-LEP 02 ZPSAP 02 ZTSEL-LEP 02 ZTSEL 02 ZSSEL-LEP 02 ZSSEL 02 ZPSEL-LEP 02 ZPSEL 02 ZAE-TITLE 02 ZPSAP-PIBBLE 02 ZL3-PROF 02 ZL4-PROF 02 ZL5-PROF 02 ZL3-SERVR 02 ZL4-SERVR 02 ZL5-SERVR 02 ZDEL-TIME 02 ZLOOPBACK 02 ZAE-TITLE-32 end.
General OSI/AS and OSI/TS Manual Changes and Corrections The ZAE-TITLE-32 definition has been added to the ZOSI-DDL-ALTER-ENTRY-APPL structure: def ZOSI-DDL-ALTER-ENTRY-APPL.
General OSI/AS and OSI/TS Manual Changes and Corrections The ZAE-TITLE-32 definition has been added to the ZOSI-DDL-INFO-ENTRY-APPL structure: def ZOSI-DDL-INFO-ENTRY-APPL.
General OSI/AS and OSI/TS Manual Changes and Corrections The ZCALLING-AE-TITLE-32, ZCALLED-AE-TITLE-32, AND ZRESPOND-AETITLE-32 definitions have been added to the ZOSI-DDL-STATUS-SU structure: def ZOSI-DDL-STATUS-SU. 02 ZSUMSTATE 02 ZOPENS-ALLOWED 02 ZOPEN-CNT 02 ZCEPI-APS 02 ZLAST-SL-ERR 02 ZLAST-SL-ERR-SUBCODE 02 ZLAST-SL-ERR-SOURCE 02 ZL4-SUNAME 02 ZINITIATOR 02 ZCALLING-ADDR.
General OSI/AS and OSI/TS Manual Changes and Corrections 04 ZAE-TITLE type ZOSI-DDL-AE-TITLE. ZSERV-LEV type ZSPI-DDL-ENUM. ZDEL-TIME type ZSPI-DDL-INT2. ZUSER-ID type ZSPI-DDL-USERID. ZOPENER-LEN type ZSPI-DDL-INT. ZOPENER type ZSPI-DDL-CHAR36. ZL4-SUNAME32 type ZSPI-DDL-FNAME32. ZTSP-LAST-FS-ERRCODE type ZSPI-DDL-INT. ZTSP-TCON-STATE-AT-LAST-ERR type ZSPI-DDL-INT. ZTSP-TCON-SUBSTATE-AT-LAST-ERR type ZSPI-DDL-INT. ZCALLING-AE-TITLE-32 type ZOSI-DDL-AE-TITLE-32.
Index A ADD ENTRY command in OSI/AS 3-16/17 ADD PROCESS command in OSI/AS 3-17 ADD PROFILE L4 command in OSI/AS 3-18 ADD SU command in OSI/TS 3-2 ALTER ENTRY command in OSI/AS 3-19/20 ALTER PROCESS command in OSI/AS 3-20 ALTER PROFILE L4 command in OSI/AS 3-21 ALTER SERVICE L4 command in OSI/AS 3-22 in OSI/TS 3-4 ALTER SU command in OSI/TS 3-5 APS_ASSOC_CONNECTREQ_ procedure use of X.
Index Configuration (continued) OSI/AS subsystem expedited data 2-16 Internet address 2-16 Network Service Provider process 2-16 SCF attributes 2-15 TPDU size 2-19 transport protocol class 2-15 OSI/TS subsystem expedited data 2-3 Internet address 2-3 Network Service Provider process 2-4 SCF attributes 2-2 TPDU size 2-4 transport protocol class 2-3 with TCP/IP and NSP processes 2-5 TCP/IP subsystem 2-1 Connection establishment, transport service procedure 1-23 Connection release, transport service procedure
Index Example files EXADCVTC 4-1 EXCFG7 4-3 EXCFG8 4-5 EXEMST1, correction to 8-2 IP address-to-hexadecimal string utility 4-1 OSI/AS configuration 4-3 OSI/MHS RS Group configuration 4-8 OSI/TS configuration 4-5 EXPEDITED attribute used in ADD PROFILE L4 3-18 used in ADD SU 3-2 used in ALTER PROFILE L4 3-21 used in ALTER SERVICE L4 3-4, 3-22 used in ALTER SU 3-5 I INFO ENTRY command in OSI/AS 3-30/31 INFO PROCESS command in OSI/AS 3-32 INFO PROFILE L4 command in OSI/AS 3-32 INFO SERVICE L4 command in OSI/A
Index LOCALNSAP attribute used in ADD SU 3-3 used in ALTER SU 3-5 used in CHECK SU 3-6, 3-26 M Management Information Base See MIB MAXCONNECTIONS attribute used in ALTER PROCESS 8-13 MAXCONNECTIONS attribute, range of values 8-13 MIB backups 8-15 use of null entries 8-14 N NAME attribute used in ADD PROCESS 3-17 used in ALTER PROCESS 3-20 NAMES PROCESS command in OSI/AS 3-34 NAMES SUBSYS command in OSI/AS 3-34 NETADDR-MODE attribute used in ADD ENTRY NSAP 3-16 used in ALTER ENTRY NSAP 3-19 Network service
Index OSI/AS subsystem architecture 1-1 subsystem interfaces 1-5 OSI/TS changes in expedited data service 1-16 changes in TPDU size 1-16 changes in TPDUs 1-16 changes in Transport Layer protocols 1-15 changes in transport service user data 1-16 encapsulation of TPDU into the transport packet 1-17 network service primitives 1-20 service primitives 1-18 service primitives mapping to TCP transport 1-21 subsystem architecture 1-1 subsystem interfaces 1-5 transport packet format and length 1-17 transport servic
Index R REMOTENSAP attribute used in ADD SU 3-3 used in ALTER SU 3-6 S Server and client programming steps 7-1/4 Service primitives 1-18 Service primitives mapping between OSI and TCP transports 1-21 Socket errors See Errors Sockets 1-11 STATUS SU command in OSI/AS 3-35 in OSI/TS 3-12 Subsystem configuration See Configuration Subsystem interfaces 1-5 T TCP lower layers with the OSI upper layers 1-5 TCP service primitives 1-21 TCP service primitives mapping to OSI transport 1-21 TCP/IP as the NSP 1-3 Intern
Index TPDUs CC-TPDU 5-2/5 changes in TPDU size 1-16 CR-TPDU 5-5/9 DR-TPDU 5-9/10 DT-TPDU 5-11 ED-TPDU 5-12 encapsulation of TPDU into the transport packet 1-17 ER-TPDU 5-13/14 not used by RFC-1006 1-16, 5-1 transport packet format and length 1-17 used by RFC-1006 1-16, 5-1 TPDUSIZE attribute used in ADD PROFILE L4 3-18 used in ADD SU 3-3 used in ALTER PROFILE L4 3-21 used in ALTER SERVICE L4 3-4, 3-23 used in ALTER SU 3-6 Transport service primitives 1-18 Transport service procedures 1-23 W Well-known port
