Download Print this page

IBM AS/400 Hardware User Manual

Ibm network hardware - networking hardware user manual
Hide thumbs

Advertisement

Quick Links

ERserver
iSeries
Networking
iSeries Communications Management

Advertisement

loading

  Also See for IBM AS/400

  Related Manuals for IBM AS/400

  Summary of Contents for IBM AS/400

  • Page 1 ERserver iSeries Networking iSeries Communications Management...
  • Page 3 ERserver iSeries Networking iSeries Communications Management...
  • Page 4 © Copyright International Business Machines Corporation 1998, 2001. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
  • Page 5: Table Of Contents

    Chapter 5. Communicating with host systems ..... 21 Matching AS/400 parameters for a host system ..... 21 Matching AS/400 line description parameters for a host system Matching AS/400 controller description parameters for a host system .
  • Page 6 Local area network standards ......91 ATM on AS/400 ....... . 91 Distributed data interface network .
  • Page 7: Part 1. Getting Started With As/400 Communications

    Many factors can affect the performance of the AS/400 in a communications environment. To achieve the best performance with your particular environment review the topics, Optimizing communications performance, and Communications applications.
  • Page 8 Version 5...
  • Page 9: Chapter 1. Print This Topic

    Chapter 1. Print this topic To view or download the PDF version, select Getting started with AS/400 communications (about 721 KB or 110 pages). To save a PDF on your workstation for viewing or printing: 1. Open the PDF in your browser (click the link above).
  • Page 10 Version 5...
  • Page 11: Chapter 2. Configuring As/400 For Communications

    AS/400 system and the network. To create line descriptions, do the following: 1. Type one of these commands on any AS/400 command line to define the type of line you are creating and press F4. v Create Line Description (Ethernet) (CRTLINETH)
  • Page 12 Version 5...
  • Page 13: Chapter 3. Optimizing Communications Performance

    Improving local area network (LAN) performance. v Improving data path performance. Improving wide area network performance To achieve better performance with your AS/400 when communicating in a wide area network (WAN), you need to consider the following: v “Adjusting WAN protocols for optimum AS/400 performance”...
  • Page 14: Wan Line Speed Considerations For Iops

    Use the AS/400 performance tools to get the utilization. v You can attach multiple IOPs to an AS/400 system. The maximum number of IOPs that can be attached is determined by the AS/400 model. It is important to distribute the work load across several IOPs if the performance capabilities of a single IOP is exceeded.
  • Page 15: Improving Local Area Network Performance

    For more information on performance tools, see the Performance Tools for AS/400 Improving local area network performance To achieve better performance with your AS/400 when communicating in a local area network (LAN), you need to consider the following. v “Adjusting LANs for optimum communications performance”...
  • Page 16: Lan Line Speed Considerations For Iops

    For more information on AS/400 communications, see the Communications Configuration LAN line speed considerations for IOPs When configuring an AS/400 system with communications lines and local area networks (LANs), you should not overload an input/output processor (IOP) to prevent possible system performance bottlenecks.
  • Page 17: Considerations For Subsystem Configuration For Error Recovery Performance

    Jobs that run in subsystems do all work that is performed on the AS/400. As the number of users on the system increases, it becomes important for you to consider how the communications and interactive subsystems should be configured.
  • Page 18: Communications Performance Considerations For Interactive Jobs

    Example: Communications subsystem configuration 1. Create a duplicate of QCMN: Set up the communication entries: 3. If desired, update your system startup program to start your new subsystems automatically. Communications performance considerations for interactive jobs An interactive job is one that uses a keyboard and character-type display. If a job needs the user to type on the keyboard and display character results, that job is probably considered interactive.
  • Page 19: Communications Performance Considerations For Batch Jobs

    Communications performance considerations for batch jobs Each piece of work run on the AS/400 system is called a job. Each job is a single, identifiable sequence of processing actions that represents a single use of the system. The basic types of jobs that are performed are interactive jobs, batch jobs, spooling jobs, autostart jobs, and prestart jobs.
  • Page 20: Performance Considerations For Anynet Communications

    “Performance considerations for AnyNet communications” AnyNet communications for the AS/400 system AnyNet is an IBM implementation of the Multiprotocol Transport Networking (MPTN) architecture, such as AnyNet/2 and AnyNet/Multiple Virtual Storage (MVS). AnyNet capability allows applications and associated services that use application programming interfaces, such as sockets, intersystem communications function (ICF), or CPI Communications, the flexibility to use alternative network protocols, such as Systems Network Architecture (SNA) or TCP/IP.
  • Page 21: Subsystems

    OS/400 can contain several that are independent operating subsystems. The run-time characteristics of a subsystem are defined in an object that is called a subsystem description. IBM supplies several subsystem descriptions that can be used with or without modification: QINTER...
  • Page 22 For more information about creating subsystems, see the Work Management book. Version 5...
  • Page 23: Chapter 4. Communications Applications

    Application program interface (API) performance considerations To achieve better performance with your AS/400, you need to consider the application programming interface (API) available on the AS/400. To optimize APPC performance, consider the following: © Copyright IBM Corp. 1998, 2001...
  • Page 24: Performance Considerations For Intersystem Communications Function

    To create device descriptions to get your system set up for ICF, do the following: 1. Type the appropriate Create Device Description commands on the AS/400 command line and press 2. Use the online help information to choose the parameter values.
  • Page 25: Performance Considerations For Common Programming Interface Communications

    To add or change communications entries to get the system set up for CPI Communications, do the following: 1. Type appropriate command on the AS/400 command line and press F4. v Add Communications Entry (ADDCMNE) v Remove Communications Entry (RMVCMNE) v Change Communications Entry (CHGCMNE) 2.
  • Page 26 Version 5...
  • Page 27: Chapter 5. Communicating With Host Systems

    The list contains only those configuration prompts and parameters that require coordination on both the AS/400 and the host system. In addition, some of the parameters that are listed may not apply to your particular configuration.
  • Page 28 IDBLK, IDNUM The AS/400 block number (digits 1-3 of the EXCHID) is always . The remaining 5 digits (based on the system serial number if *SYSGEN is used) are specified in the IDNUM parameter.
  • Page 29: Matching As/400 Controller Description Parameters For A Host System

    To configure an AS/400 to a host system: v See “Examples: Connecting AS/400 to a host system” on page 26 for an example of connecting an AS/400 to a host system. v Use the following table for the controller description parameter.
  • Page 30: Matching As/400 Device Description Parameters For A Host System

    LINE, PU, and LU. The following table lists only the lowest level definition statement that is used by the host system. To configure an AS/400 to a host system: v See “Examples: Connecting AS/400 to a host system” on page 26 for an example of connecting an AS/400 to a host system. Version 5...
  • Page 31: Matching As/400 Mode And Class-Of-Service Description Parameters For A Host System

    To configure an AS/400 to a host system: v See “Examples: Connecting AS/400 to a host system” on page 26 for an example of connecting an AS/400 to a host system. v Use the following table for the mode and class-of-service description parameter.
  • Page 32 Configuration parameters must be coordinated when you connect an AS/400 system to a host system. Example 1: AS/400 to host system over a nonswitched SDLC line. This diagram shows the AS/400 values that need to match the VTAM values when you use a nonswitched SDLC line.
  • Page 33 Example 2: AS/400 to host system over a token-ring line. This diagram shows the AS/400 values that need to match the VTAM values when you use a token-ring line. Chapter 5. Communicating with host systems...
  • Page 34 Example 3: AS/400 system for DLUR support with the host system. Version 5...
  • Page 35 This diagram shows the AS/400 values that need to match the VTAM values when you use AS/400 DLUR and VTAM. Example 4: AS/400 with APPN connection to VTAM This diagram shows the AS/400 values that need to match the VTAM values when you connect with APPN.
  • Page 36 Version 5...
  • Page 37: Configuring Dependent Lu Requester (Dlur)

    Use the Work with Mode Descriptions (WRKMODD) command and specify the option to delete CPSVRMGR. To configure the AS/400 system to communicate with DLUR, perform these steps: 1. Configure a host controller description 2. Configure device descriptions 3.
  • Page 38 Note: This must match the VTAM LU name with the corresponding local location address (LOCADDR) on VTAM. For more information on DLUR see, Dependent LU Requester Support (DLUR). Version 5...
  • Page 39: Chapter 6. Communicating With A Remote As/400 System

    Only those configuration prompts and parameters that require coordination on both the AS/400, and the remote AS/400 system are listed. In addition, some of the parameters that are listed may not apply to your particular configuration. See the following topics for more information: v “Matching AS/400 line description parameters for a remote AS/400 system”...
  • Page 40 *IEEE8023) or at least one system must specify *ALL. EXCHID Remote AS/400 controller description EXCHID must match the local AS/400 line description EXCHID. The first three digits of the exchange identifier, known as the block number, is the Work with Line Descriptions (WRKLIND) command to determine this value.
  • Page 41: Matching As/400 Controller Description Parameters For A Remote As/400 System

    AS/400 systems. To configure a local AS/400 to a remote AS/400: v See “Connecting one AS/400 to another AS/400 system” on page 37 for an example of connecting one AS/400 to another AS/400 system.
  • Page 42: Matching As/400 Device Description Parameters For A Remote As/400 System

    AS/400 systems. To configure a local AS/400 to a remote AS/400: v See “Connecting one AS/400 to another AS/400 system” on page 37 for an example of connecting one AS/400 to another AS/400 system.
  • Page 43: Connecting One As/400 To Another As/400 System

    RMTNETID Single session SNGSSN For more information on AS/400 parameters, see the Communications Configuration Connecting one AS/400 to another AS/400 system Configuration parameters must be coordinated when you specify controller, device, and line descriptions for the local and remote AS/400.
  • Page 44 This example shows the matching parameters between an AS/400 connecting to another AS/400 that uses X.25. Example 2: AS/400 to AS/400 using SDLC Version 5...
  • Page 45 This example shows the matching parameters between an AS/400 connecting to another AS/400 that uses SDLC. Example 3: AS/400 to AS/400 using one-way automatic dialing This example shows the matching parameters between an AS/400 connecting to another AS/400 that uses one-way automatic-dial function.
  • Page 46 Version 5...
  • Page 47: Chapter 7. Communicating With Remote Workstation Controllers

    To automatically connect the AS/400 to a 5494 controller, you can use the automatic remote controller (QAUTORMT) system value. v To manually connect the AS/400 to a 5494, you can use the following examples and the tables. The list contains only those configuration prompts and parameters that require coordination on both AS/400 and the 5494 controller.
  • Page 48 Version 5 5494 AS/400 Field Subfield Value 5494 Value Notes Values specified in the AS/400 line description (CRTLINTRN command) and for the 5494 Remote Controller Unit must match. Values specified for the AS/400 CRTCTLAPPC command and for the 5494 Remote Control Unit must match.
  • Page 49 Example: Connecting AS/400 to a 5494 controller connected by token-ring Configuration parameters must be coordinated when you connect an AS/400 system to a 5494 controller that is connected by token-ring. The following diagram shows the AS/400 parameters and 5494 parameters that need to match when you use token-ring. 5494...
  • Page 50: Matching As/400 Parameters For A 5494 Connected By Ethernet

    Ethernet. A description of these parameters are in the following table. Then the related fields and subfields from the 5494 configuration display, and the AS/400 configuration value and the matching 5494 value entered in the display subfield. You can coordinate these values manually or automatically.
  • Page 51 – See “Example: Connecting AS/400 to a 5494 controller connected by Ethernet” for an example of connecting AS/400 to a 5494 controller by Ethernet. – Use the following table to configure the AS/400 to a 5494 controller that is connected by Ethernet. For more information about configuring the 5494, see these books: v IBM 5494 Remote Control Unit Planning Guide, GA27-3936 v IBM 5494 Remote Control Unit User’s Guide, GA27-3852...
  • Page 52: Matching As/400 Parameters For A 5494 Connected By Frame Relay

    To manually configure the AS/400 to a 5494 controller: – See “Example: Connecting an AS/400 to a 5494 controller connected by frame relay” on page 47 for an example of connecting AS/400 to a 5494 controller by frame relay.
  • Page 53 Remote RMTLOCNAME location name Example: Connecting an AS/400 to a 5494 controller connected by frame relay Configuration parameters must be coordinated when you connect an AS/400 system to a 5494 controller. 5494 AS/400 Field Subfield Value *LAN Chapter 7. Communicating with remote workstation controllers...
  • Page 54: Matching As/400 Parameters For A 5494 Connected By Sdlc

    SDLC. These parameters are described in the following table. Then the related fields and subfields from the 5494 configuration display are listed next. These values are followed by the AS/400 configuration value and the matching 5494 value to be entered in the display subfield. You can coordinate these values automatically or manually.
  • Page 55 For more information about configuring the 5494, see these books: v IBM 5494 Remote Control Unit Planning Guide, GA27-3936 v IBM 5494 Remote Control Unit User’s Guide, GA27-3852 AS/400 AS/400 Prompt Parameter Field Connection type Duplex Duplex NRZI data NRZI...
  • Page 56 Example: Connecting AS/400 to a 5494 controller connected by SDLC Configuration parameters must be coordinated when you connect an AS/400 system to a 5494 controller. The following diagram shows the AS/400 parameters and 5494 parameters that need to match when you use SDLC.
  • Page 57 Chapter 7. Communicating with remote workstation controllers...
  • Page 58: Matching As/400 Parameters For A 5494 Connected By X.21

    5494 configuration display are listed next. These values are followed by the AS/400 configuration value and the matching 5494 value to be entered in the display subfield. You can coordinate these values automatically or manually. Pick one of these ways: v To automatically connect the AS/400 to a 5494 controller, you can use the automatic remote controller (QAUTORMT) system value.
  • Page 59 Example: Connecting AS/400 to a 5494 controller connected by X.21 Configuration parameters must be coordinated when you connect an AS/400 system to a 5494 controller. The following diagram shows the AS/400 parameters and 5494 parameters that need to match when you use X.21.
  • Page 60: Matching As/400 Parameters For A 5494 Connected By X.25

    5494 configuration display are listed next. These values are followed by the AS/400 configuration value and the matching 5494 value to be entered in the display subfield. You can coordinate these values automatically or manually. Pick one of these ways: v To automatically connect the AS/400 to a 5494 controller, you can use the automatic remote controller (QAUTORMT) system value.
  • Page 61 IBM 5494 Remote Control Unit User’s Guide, GA27-3852 AS/400 AS/400 Prompt Parameter Field Default DFTPKTSIZE packet size Local LCLLOCNAME location name X.25 link LINKPCL protocol Link type LINKTYPE X.25 NETLVL network level Remote RMTCPNAME control point name Remote RMTNETID...
  • Page 62 Example: Connecting AS/400 to a 5494 controller connected by X.25 Configuration parameters must be coordinated when you connect an AS/400 system to a 5494 controller. The following diagram shows the AS/400 parameters and 5494 parameters that need to match when you use X.25.
  • Page 63 Chapter 7. Communicating with remote workstation controllers...
  • Page 64: Matching As/400 Parameters For 3X74 Controller

    4 Ethernet Attachment, GA27-3994 has information about Ethernet support. To configure the AS/400 to a 3174 controller: v See “Example: Connecting an AS/400 to a 3174 control unit” on page 61 for an example of connecting an AS/400 to a 3174 retail controller.
  • Page 65 3174 controller, values specified for question 107 and for the ADPTADR parameter on the CRTLINTRN command must match. If the AS/400 system uses an Ethernet line through an 8209 LAN Bridge, see ″Appendix C: Local Area Network Addressing Considerations″ in the Communications Configuration book, for information about specifying the ADPTADR parameter on the CRTLINETH command.
  • Page 66: Matching As/400 Parameters For A 3274 Controller

    Note: If you are using a 3174 Model 1L Gateway to connect an AS/400 system to a host system on a Token-Ring, the value specified for item 900 (Token-Ring Network Address of the Gateway) must match the value specified for the ADPTADR parameter on the CRTCTLHOST command.
  • Page 67 Short-hold mode Station address STNADR Example: Connecting an AS/400 to a 3174 control unit Configuration parameters must be coordinated when you connect an AS/400 system to a 3174 controller. 3274 Sequence Number 3274 DTE Address For X.25 SVCs, the connection number specified on the CRTCTLRWS command and in sequence number 411 must match.
  • Page 68: Matching As/400 Parameters For Finance Controllers

    Communication System Controller Programming Library, GC31-2068. To configure the AS/400 to a 470x finance controller: v See “Example: Connecting AS/400 to a finance network” on page 67 for an example of connecting an AS/400 to a 4701 finance controller. v Use the following table to connect an AS/400 to a 4701 finance controller.
  • Page 69 SWITCHED(*YES) on the CRTCTLFNC command), include the SWM value on the ACB parameter (ACB = SWM). The values specified for the 4700 and the AS/400 system must match. The block number for the 4700 (first 3 digits of the AS/400 EXCHID parameter) must be The 4700 parameter values are decimal numbers;...
  • Page 70: Matching As/400 Parameters For Fbss Finance Controllers

    Communication System Controller Programming Library, GC31-2068. To configure the AS/400 to a FBSS finance controller: v See “Example: Connecting AS/400 to a finance network” on page 67 for an example of connecting an AS/400 to a 4701 finance controller. v Use the following table to connect an AS/400 to a 4701 finance controller.
  • Page 71 Display Token Ring PC address Communications If the AS/400 system uses a Token-Ring network line to connect to the FBSS controller, values specified for the FBSS and on the ADPTADR parameter on the CRTLINTRN command must match. If the AS/400 system uses an Ethernet line through an 8209 LAN Bridge, see ″Appendix C: Local Area...
  • Page 72 FBSS Identification block and matches the FBSS Identification number. Communication Data Link Control Servers Values specified for the FBSS and AS/400 configurations must match: v If the FBSS response is must be specified for the CRTCTLFNC command. v If the FBSS response is must be specified for the CRTCTLFNC command.
  • Page 73: Matching As/400 Parameters For Retail Controllers

    You must coordinate several AS/400 parameter values with retail controllers for retail communications. These values are specified for the AS/400 system and in the controller configuration. For an example on connecting an AS/400 to a 4690 retail controller, see “Examples: Connecting AS/400 to a 4690 retail controller” on page 75.
  • Page 74: Matching As/400 Parameters For 3651 Retail Controllers

    Matching AS/400 parameters for 3651 retail controllers You must coordinate several parameter values for retail communications. These values are specified for the AS/400 system and the 3651 retail controller. The following table lists those AS/400 parameters that must match values for the 3651 retail controllers.
  • Page 75 SWITCHED Note: For the AS/400 system, the 3651 QFHOST definition must specify DIRATT=NO. The value specified for the AS/400 parameters on the CRTLINSDLC command must match the values specified on the 3651 SDLCLIN parameter. For information about the SDLCLIN parameter, see “Specifying the SDLCLIN parameter for 3651 retail controllers”.
  • Page 76: Matching As/400 Parameters For 3684 Retail Controllers

    For information about SDLC, see “Synchronous data link control network” on page 94. Matching AS/400 parameters for 3684 retail controllers You must coordinate parameters with the AS/400 system and the 3684 retail controller. The following table lists those parameters. AS/400 parameters are listed in alphabetical order; the commands on which the parameters are specified are included in the rightmost column of the table.
  • Page 77 3684 LINECON parameter. Specifying the LINECON parameter for 3684 retail controllers The following table describes how to coordinate values that are specified for parameters on the AS/400 CRTLINSDLC and CRTCTLRTL commands. You must coordinate the values with bits that are specified for the 3684 LINECON parameter.
  • Page 78: Matching As/400 Parameters For 4680/4690 Line Parameter

    For more information about configuring the 4680, see the IBM 4680 Store System: Programming Guide. To configure the AS/400 to a 4680/4690 controller: v See “Examples: Connecting AS/400 to a 4690 retail controller” on page 75 for an example of an AS/400 connecting to a 4690 retail controller.
  • Page 79: Matching As/400 Parameters For 4680/4690 Link Parameter

    Guide. To configure the AS/400 to a 4680/4690 controller: v See “Examples: Connecting AS/400 to a 4690 retail controller” on page 75 for an example of an AS/400 connecting to a 4690 retail controller. v Use the following table to connect an AS/400 to a 4680/4690 retail controller.
  • Page 80: Matching As/400 Parameters For 4684 Retail Controllers

    Support Services: Planning and Installation Guide, SC33-0650. To configure the AS/400 to a 4684 controller: v See “Examples: Connecting AS/400 to a 4690 retail controller” on page 75 for an example of an AS/400 connecting to a 4690 retail controller.
  • Page 81 STNADR Examples: Connecting AS/400 to a 4690 retail controller AS/400 retail communications provide the ability to attach retail controllers to the AS/400 system. Retail communications manage data with the intersystem communications function (ICF) file. For communications to begin between programs, the retail communications device must first be configured and varied on.
  • Page 82 Example 2: AS/400 to 4690 PEER connection over token-ring network Version 5...
  • Page 83 Chapter 7. Communicating with remote workstation controllers...
  • Page 84 Version 5...
  • Page 85: Chapter 8. Troubleshooting Communications Problems

    Chapter 8. Troubleshooting communications problems If you suspect you have a problem with communications connectivity, the AS/400 system provides a set of tools to help you with problem analysis tasks. The list below contains some of the more common tools for communications problem analysis.
  • Page 86: Displaying The Product Activity Log To Solve Communication Problems

    1. Display or print the product activity log using these steps: v Type STRSST (Start System Service Tools) on any AS/400 command line, and press the Enter key. v In the System Service Tools menu, select Option 1 to display or print the product activity log.
  • Page 87: Solving Communication Problems Using Communications Trace

    QPASVRP Target 5250 display station pass-through primary server job. This job log is for target pass-through communications functions. QPASVRS Target 5250 display station pass-through secondary server job. These contain more detailed messages for target pass-through communication functions Subsystem jobs (QINTER and QCMN) Interactive subsystem and communication subsystem.
  • Page 88: System Service Tools And Communication Problems

    System service tools and communication problems You may sometimes need to obtain an error log printout or communications trace data that your IBM service representative can review. For the line trace, someone familiar with the protocol used on the line may need to review the files.
  • Page 89: Solving Communication Problems Using The System Problem Log

    To access the system problem log, type WRKPRB on any AS/400 command line, and press F4. Tips: You can select a subset of the problems that are listed in the problem log by selecting the problem status.
  • Page 90: Solving Communication Problems Using Status Information

    To check and change the communication configuration on the system, do the following: 1. Type the Work with Configuration Status (WRKCFGSTS) command on any AS/400 command line. 2. Press F4. The Work with Configuration Status display appears.
  • Page 91 Refer to Table 13 for an explanation on reason codes for failed program start requests. Table 1. Reason Codes for Rejected Program Start Requests Reason Code Reason Description Program start request received to a device that is not allocated to an active subsystem. Requested device is currently being held by a Hold Communications Device (HLDCMNDEV) command.
  • Page 92 Table 1. Reason Codes for Rejected Program Start Requests (continued) Reason Code Reason Description Program initialization parameters are not valid. Number of parameters for program not valid. Program initialization parameters required but not present. 1001 System logic error. Function check or unexpected return code encountered. 1002 System logic error.
  • Page 93: Chapter 9. Networking Concepts

    Advanced Peer-to-Peer Networking (APPN) is one type of data communications support that is provided by the AS/400 system. This support routes data in a network between two or more advanced program-to-program systems. The systems do not need to be directly connected in the same network or adjacent networks.
  • Page 94: Advanced Program-To-Program Communications

    The AS/400 APPC support handles the protocol needed for communicating between an application program that runs on your AS/400 system, and an application that runs on a remote system. The protocol consists of a set of verbs that are common to the local and remote systems in a network. However, the way in which each system provides a program interface to the verbs may differ.
  • Page 95: High-Performance Routing

    Internetwork packet exchange support If your group or business has an established Novell LAN, you can connect AS/400 into your business using the OS/400 Internetwork Packet Exchange (IPX). Chapter 9. Networking concepts...
  • Page 96: What Is Systems Network Architecture

    APPC, APPN, and HPR are some examples of the protocols included within SNA. They can be used to connect the AS/400 with other IBM systems, or non-IBM systems, to connect remote controllers, and to maintain a high-level of security on your system.
  • Page 97: Chapter 10. Common Networking Standards

    Chapter 10. Common networking standards These topics introduce the types of common networking standards that are supported by the AS/400 system. See the following topics for more information: v Local area network standards v Wide area network standards Local area network standards A LAN (local area network) is a communications system that allows interconnection and the sharing of resources between independent devices within a moderately sized geographic area.
  • Page 98: Token-Ring Networks

    (PTCs) make it possible for direct connection between the office and offsite locations. The AS/400 wireless network is a LAN that uses a Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) protocol to provide media access to competing stations. AS/400 wireless communications use spread-spectrum, direct sequence radio in the 2.4 gigahertz (GHz) band to provide connectivity between...
  • Page 99: Wide Area Network Standards

    AS/400 wireless LAN adapter and remote stations. Remote stations can be PTCs that are running 5250 emulation or LAN-connected systems that are equipped with compatible wireless adapters. There are other implementations of wireless LAN. Wide area network standards A wide area network (WAN) is a data communications network designed to serve an area of hundreds or thousands of miles--for example, public and private packet-switching networks, and national telephone networks.
  • Page 100: Integrated Services Digital Network

    Integration of voice and data transmissions v Integrated support of packet switching (X.31) For more information on ISDN, see the topics ISDN on AS/400 and ISDN data link control network. ISDN data link control network You can use ISDN data link control (IDLC) to connect two systems to exchange information over an ISDN B-channel.
  • Page 101: X.25 Network

    X.25 networks use the connection-mode network service. An AS/400 X.25 line can be connected through a packet-switching data network (PSDN) and an adjacent remote system by using either a nonswitched or switched physical line. A switched line connection is one that is established on demand between the AS/400 system and the X.25 network.
  • Page 102 Version 5...
  • Page 104 Printed in U.S.A.