IBM AS/400 manual Subsystems, Qusrwrk

Page 21

are written for one type of network protocol to run over a different type of network protocol. For example, without AnyNet, your choice of application program interface (API) dictates your choice of network protocol, or your choice of network protocol dictates your choice of APIs.

AnyNet allows you to mix and match applications with network protocols. In fact, you can do this without changing your application programs. Your destination address (such as a remote location) determines the type of network protocol to use.

vAnyNet/400 Sockets

This support converts TCP/IP addresses to SNA addresses that are based on tables that are configured by the network administrator. Programs supported include File Transfer Protocol (FTP), Simple Mail Transfer Protocol (SMTP), Simple Network Management Protocol (SNMP), PING, and user-written sockets programs.

TCP/IP over SNA

TCP/IP over IPX

vAnyNet/400 APPC (advanced program-to-program communications)

This support allows programs that are written to traditional APPC APIs (such as ICF, CPI-Communications, and CICS/400) to be run over non-APPC networks. The application program uses Location names to specify the source and destination address. A TCP/IP domain name server converts these location names to IP addresses. Programs supported include distributed data management (DDM), Distributed Relational Database Architecture (DRDA), SNA distribution services (SNADS), display station pass-through, Client Access, user-written CPI-Communications programs, and user-written ICF programs .

APPC over TCP/IP

APPC over IPX

For more information about using both AnyNet and nonAnyNet sockets, see the Sockets Programming book.

Subsystems

A subsystem is a single, predefined operating environment through which the system coordinates work flow and resource usage. 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

Used for interactive jobs

QBATCH

Used for batch jobs

QBASE

Used for both interactive and communications batch jobs

QCMN

Used for communications batch jobs

QSERVER

File server system

QSYSWRK

Used for general system work

QUSRWRK

This is the default subsystem used for TCP/IP Client Access Host Servers that used to run in

QSYSWRK.

A new subsystem can also be defined with the Create Subsystem Description (CRTSBSD) command.

Chapter 3. Optimizing communications performance 15

Image 21
Contents ERserver Page ERserver Page Contents Troubleshooting communications problems Part 1. Getting started with AS/400 communications Version Print this topic Version Creating a network interface description Configuring AS/400 for communicationsCreating a network server description Creating a line descriptionVersion Adjusting the WAN line speed for optimum AS/400 performance Adjusting WAN protocols for optimum AS/400 performanceOptimizing communications performance Improving wide area network performanceWAN line speed considerations for IOPs Adjusting LANs for optimum communications performance Adjusting LAN lines for optimum communications performanceImproving local area network performance Improving data path performance LAN line speed considerations for IOPsAddcmne SBSDlibname/sbsname DEVdevname* MODEmodename Set up the communication entries Example Communications subsystem configurationExample Interactive subsystem configuration Communications performance considerations for batch jobsMixing interactive and batch jobs on a WAN line Setting up the AnyNet environment Performance considerations for AnyNet communicationsAnyNet communications for the AS/400 system Qusrwrk SubsystemsVersion Communications applications User written Appc applicationsDistributed data management DDM Version Communications applications Version Matching AS/400 parameters for a host system Communicating with host systemsSSAP/DSAP/remote-adapter-address Name Rmtcpname Vtamlst Sscpname Maxframe Group MaxdataRmtnetid Vtamlst Netid Ssap SapaddrLcllocname Dfhtct Netname Mode Modeent LogmodeLocadr Locaddr Locpwd Dfhtct BindpwdAS/400 Host Definition AS/400 Prompt Examples Connecting AS/400 to a host systemModd Modeent Logmode Cosd Modeent COSCommunicating with host systems Version Communicating with host systems Version Configuring dependent LU requester Dlur Configuring the host controller descriptionConfiguring the device descriptions Version AS/400 Remote AS/400 AS/400 Prompt Communicating with a remote AS/400 systemAdptadr AdrinsertAS/400 Remote AS/400 AS/400 Prompt Parameter Cnnnbr Netadr X25DCECnnpwd Dsap SsapLinkpcl InlcnnRmtcpname Lclcpname Rmtnetid LclnetidConnecting one AS/400 to another AS/400 system Version Communicating with a remote AS/400 system Version Matching AS/400 parameters for 5494 controllers Communicating with remote workstation controllersLAN AS/400 5494 Prompt AS/400 Parameter Field Subfield ValueRmtcpname RmtnetidLinktype LAN AS/400 5494 Prompt AS/400 Parameter Field SubfieldMatching AS/400 parameters for a 5494 connected by Ethernet AS/400 5494 Prompt Parameter Field Subfield Value Version LAN Adptadr Matching AS/400 parameters for a 5494 connected by Sdlc Prompt Parameter Field Subfield AS/400 Value AS/400Field Subfield AS/400 Value Communicating with remote workstation controllers Matching AS/400 parameters for a 5494 connected by Linktype Example Connecting AS/400 to a 5494 controller connected byIBM 5494 Remote Control Unit Planning Guide, GA27-3936 Linkpcl Qllc DftpktsizeEllc NetlvlField Subfield Value AS/400 5494 PromptCommunicating with remote workstation controllers Matching AS/400 parameters for 3x74 controller 3174 AS/400 Configuration PromptMatching AS/400 parameters for a 3174 controller Questions3174 AS/400 Configuration Prompt Parameter Questions Matching AS/400 parameters for a 3274 controller Switched Short-Hold ModeNRZ or Nrzi Encoding Control Unit AddressExample Connecting an AS/400 to a 3174 control unit 3274 AS/400Prompt Parameter Number Matching AS/400 parameters for 470x finance controllers Matching AS/400 parameters for finance controllersAS/400 AS/400 Prompt Parameter Macro Matching AS/400 parameters for Fbss finance controllers AS/400 AS/400 PromptMacro Parameter Service access point for PC Switched lineLine mode PC addressIdentification block and Identification number Service access point for Host/37xx/4700Matches the Fbss Identification number Data Link ControlMatching AS/400 parameters for retail controllers Example Connecting AS/400 to a finance networkAS/400 Definition AS/400 Prompt Parameter Statement Matching AS/400 parameters for 3651 retail controllersAS/400 Parameter Sdlclin Bit Bit Value AS/400 Definition AS/400 Prompt3684 AS/400 Definition Prompt Matching AS/400 parameters for 3684 retail controllers3684 AS/400 Definition Prompt Parameter AS/400 Parameter Linecon Bit Bit Value Matching AS/400 parameters for 4680/4690 Line parameterCNN*MP SNBU*NO SNBU*YES MODEMRATE*FULLMatching AS/400 parameters for 4680/4690 Link parameter Exchid parameter specified on the AS/400 Crtctlrtl commandAS/400 Prompt AS/400 Parameter Line Parameter CNNMatching AS/400 parameters for 4684 retail controllers Wire constant RTS?Local node Hex Remote node HexExamples Connecting AS/400 to a 4690 retail controller Version Communicating with remote workstation controllers Version Displaying message queues to solve communication problems Troubleshooting communications problemsQsysarb Job logs and communication problemsQpasvrp Solving communication problems using communications traceTrace option setting System service tools and communication problemsTrace full Solving communication problems using the system problem logConsiderations for system tuning during error recovery Solving communication problems using status informationUsing error messages to aid in error recovery Solving communication problems using reason codesReason Code Reason Description Reason Codes for Rejected Program Start RequestsReason Code Reason Description Advanced Peer-to-Peer Networking Networking conceptsDependent LU requester support Advanced program-to-program communicationsHigh-performance routing HPR architecture option setsInternetwork packet exchange support What is TCP/IP What is Systems Network ArchitectureLocal area network standards Common networking standardsATM on AS/400 Distributed data interface networkToken-ring networks Wireless networkAsynchronous communications Wide area network standardsBinary synchronous communications Frame relay networksIntegrated services digital network Synchronous data link control networkIsdn data link control network Network Version
Related manuals
Manual 489 pages 47.95 Kb Manual 516 pages 58.6 Kb

AS/400 specifications

The IBM AS/400, now known as the IBM iSeries, is a midrange computer system that has been a cornerstone of enterprise computing since its introduction in 1988. Designed to provide a robust platform for business applications, the AS/400 is celebrated for its reliability, scalability, and integrated database capabilities.

One of the key features of the AS/400 is its Integrated Operating Environment, which blends hardware and software resources seamlessly. This integration allows businesses to execute diverse workloads, ranging from traditional applications to modern web-based services, all on a single platform. The operating system, OS/400 (now IBM i), offers a rich set of APIs and tools for developers, simplifying application development and management.

Another standout characteristic of the AS/400 is its built-in database, DB2 for i. This powerful relational database management system allows for efficient data handling and provides advanced features such as support for SQL, XML, and JSON, making it easier for businesses to manage their data and integrate it with other systems. The database's tight integration with the operating system enables high performance and security.

In terms of scalability, the AS/400 can accommodate small businesses as well as large enterprises, with the ability to support hundreds of users simultaneously. Its architecture allows for easy upgrades in hardware, meaning that organizations can scale their systems without replacing the entire infrastructure.

Security is another critical attribute of the AS/400. With a sophisticated security model, it offers built-in user authentication, access control, encryption, and auditing capabilities to protect data and applications from unauthorized access.

The AS/400 also supports multiple programming languages, including RPG, COBOL, Java, and PHP, giving organizations the flexibility to choose the development tools that best fit their needs. This diversity helps maintain legacy applications while also developing new ones that leverage modern technologies.

Moreover, the platform supports both traditional green-screen interfaces and modern graphical user interfaces, allowing organizations to transition smoothly into contemporary user experience paradigms.

Overall, the IBM AS/400 stands out as a resilient, flexible, and secure computing platform that enables organizations to effectively manage their business operations, streamline processes, and adapt to changing market demands. Its unique combination of integrated features and capabilities ensures that it remains relevant in today's fast-paced technology landscape.