Configuring dependent LU requester (DLUR)

Dependent LU Requester (DLUR) allows dependent secondary logical units (LU 0, 1, 2, and 3) an entry point into the APPN network. DLUR support gives the appearance of having an adjacent connection to VTAM, but allows traversing the APPN network through intermediate nodes.

Note: DLUR uses logmode CPSVRMGR. This is created internally as part of the APPN and DLUR support. If CPSVRMGR exists as a user-defined logmode on any of the systems in your network, it must be deleted. 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.Verify that an APPN connection into the network exists (host or APPC controller with *YES specified for the APPN parameter).

Configuring the host controller description

Use the Create Controller Description (SNA Host) (CRTCTLHOST) command to create the controller description. If you have already created a controller description for such functions as 3270 emulation or NRF, you must change the link type to *DLUR. Follow these steps:

1.Retrieve the configuration description for the Dependent LU Requester (DLUR) controller description using the Retrieve Configuration Source (RTVCFGSRC) command.

2.Edit the member to change the link type to *DLUR.

3.Convert the source to a CL program.

4.Create the CL program using the CRTCLPGM command.

5.Delete the configuration using the DLTCTLD command.

6.Call the CL program to create the new configuration.

An explanation of some of the fields on the Create Controller Description (SNA Host) (CRTCTLHOST) screen are as follows:

Local exchange identifier

Matches the ID block and ID number parameters from the PU definition on VTAM.

Dependent PU name

Matches the name of the PU specified on the PU definition on VTAM.

Note: If the local exchange identifier and the dependent PU name are specified, both must match the definitions on VTAM. If both parameter values do not match, the ACTPU will be rejected.

If the *DIAL value is specified for the INLCNN parameter, the primary DLUS name (PRIDLUS), and either the local exchange identifier (LCLEXCHID), or the dependent PU name (DEPPUNAME) must be specified.

Control point name and network identifier for the primary DLUS name

Matches the SSCP name and NETID parameters on the VTAM startup options.

For the last step see, Configuring the device descriptions.

Configuring the device descriptions

Use the Create Device Description (CRTDEVDSP) command to create the device.

Dependent location name

Matches the LU name on the LU definition on VTAM.

Chapter 5. Communicating with host systems 31

Page 36 Page 38
Page 37
Image 37
IBM AS/400 manual Configuring dependent LU requester Dlur, Configuring the host controller description
Page 36 Page 38

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.
Top Page Image Contents