IBM AS/400 manual Inlcnn, Linkpcl, Rmtcpname Lclcpname, Rmtnetid Lclnetid, Rvscrg, Snbu, Ssap Dsap

Page 42

 

AS/400

Remote AS/400

 

AS/400 Prompt

Parameter

Parameter

Notes

 

 

 

 

Exchange identifier

EXCHID

EXCHID

If used, the local AS/400 controller description EXCHID

 

 

 

must match the remote AS/400 line description

 

 

 

EXCHID. The first three digits of the exchange identifier,

 

 

 

known as the block number, is 056 for the AS/400 line.

 

 

 

You can use the WRKLIND command to determine this

 

 

 

value.

 

 

 

 

Initial connection

INLCNN

INLCNN

Values specified for each system must be coordinated;

 

 

 

INLCNN(*ANS) must not be specified for both systems.

 

 

 

 

Link protocol

LINKPCL

LINKPCL

For X.25 connections, values specified for each system

 

 

 

must match; both must be *QLLC or *ELLC.

 

 

 

 

Remote control point

RMTCPNAME

LCLCPNAME

RMTCPNAME specified on the local AS/400 system

name

 

 

controller description must match the local control point

 

 

 

name specified in the network attributes of the remote

 

 

 

AS/400 system.

 

 

 

 

Remote network

RMTNETID

LCLNETID

RMTNETID specified on the local AS/400 system

identifier

 

 

controller description must match the local network ID

 

 

 

specified in the network attributes of the remote AS/400

 

 

 

system.

 

 

 

 

Data link role

ROLE

ROLE

The value specified for the local AS/400 controller

 

 

 

description ROLE parameter must match the remote

 

 

 

AS/400 line description ROLE value.

 

 

 

 

X.25 reverse charging

RVSCRG

RVSCRG

Values specified for each system must be coordinated.

 

 

 

 

Switched network

SNBU

SNBU

Values specified for each system must match.

backup

 

 

 

 

 

 

 

Source service access

SSAP

DSAP

SSAP specified for the local AS/400 system must match

point

 

 

the DSAP specified in the remote AS/400 controller

 

 

 

description.

 

 

 

 

Station address

STNADR

STNADR

Values specified for each system must match, unless

 

 

 

both controller descriptions specify ROLE(*NEG).

 

 

 

 

Note: For asynchronous controllers (CRTCTLASC command), if the remote system controller description specifies RMTVFY(*YES), the local system controller description must specify a local identifier (LCLID parameter) and local location name (LCLLOCNAME parameter). The remote system must also create a configuration list with the LCLID and LCLLOCNAME values from the local system controller description.

For more information on AS/400 parameters, see the Communications Configuration book.

Matching AS/400 device description parameters for a remote AS/400 system

You must coordinate communications configuration parameters between local and remote AS/400 systems. The parameters are described in the following table. This table shows those prompts and parameters that must be coordinated when you specify device descriptions for the local and remote AS/400 systems.

To configure a local AS/400 to a remote AS/400:

vSee “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.

vUse the following table for the device description.

36Version 5

Image 42
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 server description Configuring AS/400 for communicationsCreating a network interface description Creating a line descriptionVersion Optimizing communications performance Adjusting WAN protocols for optimum AS/400 performanceAdjusting the WAN line speed for optimum AS/400 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 LAN line speed considerations for IOPs Improving data path performanceAddcmne SBSDlibname/sbsname DEVdevname* MODEmodename Example Communications subsystem configuration Set up the communication entriesExample 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 Subsystems QusrwrkVersion Communications applications User written Appc applicationsDistributed data management DDM Version Communications applications Version Communicating with host systems Matching AS/400 parameters for a host systemSSAP/DSAP/remote-adapter-address Name Rmtnetid Vtamlst Netid Maxframe Group MaxdataRmtcpname Vtamlst Sscpname Ssap SapaddrLocadr Locaddr Mode Modeent LogmodeLcllocname Dfhtct Netname Locpwd Dfhtct BindpwdModd Modeent Logmode Examples Connecting AS/400 to a host systemAS/400 Host Definition AS/400 Prompt 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 Adptadr Communicating with a remote AS/400 systemAS/400 Remote AS/400 AS/400 Prompt AdrinsertAS/400 Remote AS/400 AS/400 Prompt Parameter Cnnpwd X25DCECnnnbr Netadr Dsap SsapRmtcpname Lclcpname InlcnnLinkpcl Rmtnetid LclnetidConnecting one AS/400 to another AS/400 system Version Communicating with a remote AS/400 system Version Communicating with remote workstation controllers Matching AS/400 parameters for 5494 controllersRmtcpname AS/400 5494 Prompt AS/400 Parameter Field Subfield ValueLAN RmtnetidAS/400 5494 Prompt AS/400 Parameter Field Subfield Linktype LANMatching 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 AS/400 Prompt Parameter Field Subfield AS/400 ValueField Subfield AS/400 Value Communicating with remote workstation controllers Matching AS/400 parameters for a 5494 connected by Example Connecting AS/400 to a 5494 controller connected by LinktypeIBM 5494 Remote Control Unit Planning Guide, GA27-3936 Ellc DftpktsizeLinkpcl Qllc NetlvlAS/400 5494 Prompt Field Subfield ValueCommunicating with remote workstation controllers Matching AS/400 parameters for a 3174 controller 3174 AS/400 Configuration PromptMatching AS/400 parameters for 3x74 controller Questions3174 AS/400 Configuration Prompt Parameter Questions NRZ or Nrzi Encoding Switched Short-Hold ModeMatching AS/400 parameters for a 3274 controller Control Unit AddressExample Connecting an AS/400 to a 3174 control unit 3274 AS/400Prompt Parameter Number Matching AS/400 parameters for finance controllers Matching AS/400 parameters for 470x finance controllersAS/400 AS/400 Prompt Parameter Macro Matching AS/400 parameters for Fbss finance controllers AS/400 AS/400 PromptMacro Parameter Line mode Switched lineService access point for PC PC addressMatches the Fbss Identification number Service access point for Host/37xx/4700Identification block and Identification number Data Link ControlExample Connecting AS/400 to a finance network Matching AS/400 parameters for retail controllersMatching AS/400 parameters for 3651 retail controllers AS/400 Definition AS/400 Prompt Parameter StatementAS/400 Definition AS/400 Prompt AS/400 Parameter Sdlclin Bit Bit ValueMatching AS/400 parameters for 3684 retail controllers 3684 AS/400 Definition Prompt3684 AS/400 Definition Prompt Parameter CNN*MP SNBU*NO Matching AS/400 parameters for 4680/4690 Line parameterAS/400 Parameter Linecon Bit Bit Value SNBU*YES MODEMRATE*FULLAS/400 Prompt AS/400 Parameter Line Parameter Exchid parameter specified on the AS/400 Crtctlrtl commandMatching AS/400 parameters for 4680/4690 Link parameter CNNLocal node Hex Wire constant RTS?Matching AS/400 parameters for 4684 retail controllers Remote node HexExamples Connecting AS/400 to a 4690 retail controller Version Communicating with remote workstation controllers Version Troubleshooting communications problems Displaying message queues to solve communication problemsJob logs and communication problems QsysarbSolving communication problems using communications trace QpasvrpSystem service tools and communication problems Trace option settingSolving communication problems using the system problem log Trace fullUsing error messages to aid in error recovery Solving communication problems using status informationConsiderations for system tuning during error recovery Solving communication problems using reason codesReason Codes for Rejected Program Start Requests Reason Code Reason DescriptionReason Code Reason Description Networking concepts Advanced Peer-to-Peer NetworkingAdvanced program-to-program communications Dependent LU requester supportHigh-performance routing HPR architecture option setsInternetwork packet exchange support What is Systems Network Architecture What is TCP/IPATM on AS/400 Common networking standardsLocal area network standards Distributed data interface networkWireless network Token-ring networksBinary synchronous communications Wide area network standardsAsynchronous 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.