9.5.2 Networking Definitions

You will have some other systems with an MQSeries product installed which are connected to your VSE/ESA to allow MQSeries applications to communicate. When you migrate your VSE/ESA to OS/390 you will have to re-establish connection to those systems.

In this section we will discuss the networking considerations. There are also MQSeries definitions which refer to remote MQSeries systems. These are discussed in the next section.

We assume again, that we only talk about straight forward migration. In this context this means that we only need to re-establish the SNA/LU6.2 connections. MQSeries for MVS/ESA also supports TCP/IP as a communications protocol. But since this is not supported for MQSeries for VSE/ESA, it will not be part of the direct migration effort.

There are two parts to consider:

1.establish SNA connection between OS/390 and the other systems running MQSeries

2.check and, if necessary, modify the SNA definitions in the remote systems to connect to OS/390 rather than to VSE/ESA.

On the OS/390 side you will have to set up VTAM definitions equivalent to the definitions you made in VSE/ESA. You may be able to modify and use the VSE/ESA B-books containing the equivalent definitions.

What you need to do on the remote systems depends on what has changed. In an ideal case: If you could reuse the same communications hardware, such as communications controllers and so on, and define the same names for VTAM resources under OS/390 which you used under VSE/ESA, you would not have to change anything. More realistically, however, you will probably at least have to change remote addresses (such as MAC addresses) and remote names (such as partner LU names) on all the systems you want to connect to OS/390.

9.5.3 Defining MQSeries Object and Operating

Under VSE/ESA you will have defined the following MQSeries system elements:

1.the queue manager

2.message queues

3.channels.

These elements and their properties are defined through CICS panels. No command interface exists for MQSeries for VSE/ESA.

The definitions are stored in the MQSeries configuration file.

In MQSeries for MVS/ESA, there are six different types of object:

1.queue managers

2.queues

3.channels

Note: If you are using CICS for distributed queuing, channels are not objects, and cannot be manipulated using MQSeries commands (see below).

Chapter 9. Telecommunications Subsystems 203

Page 227
Image 227
IBM OS/390 manual Networking Definitions, Defining MQSeries Object and Operating

OS/390 specifications

IBM OS/390, a versatile operating system, was a cornerstone in enterprise environments and played a pivotal role in mainframe computing. Released in the mid-1990s, OS/390 combined the strengths of IBM's MVS (Multiple Virtual Storage) with new features and enhancements, targeting scalability, reliability, and performance in demanding business applications.

One of the key features of OS/390 was its robust support for multiple users and processes. The system allowed thousands of concurrent users to access applications and data, ensuring high availability and minimizing downtime—a critical requirement for many large organizations. This scalability was supported through various enhancements in memory management and processor scheduling, enabling optimal resource allocation across diverse workloads.

OS/390 was known for its superior workload management capabilities. The Workload Manager (WLM) component allowed administrators to define service policies, specifying how system resources would be allocated according to the priority of tasks. This ensured that critical business processes received the necessary resources while less critical tasks were managed more flexibly.

Another significant characteristic of OS/390 was its commitment to security. The operating system provided comprehensive security features, including user authentication, data encryption, and auditing capabilities. This focus on security was vital for organizations handling sensitive data, ensuring compliance with regulations and safeguarding against unauthorized access.

OS/390 also supported advanced technologies that facilitated integration and development. The system included features like the IBM CICS (Customer Information Control System) for transaction processing and IMS (Information Management System) for database management. These technologies allowed organizations to build robust, high-performance applications tailored to specific business needs.

The ease of network integration was another strength of OS/390. With the advent of the Internet and global connectivity, OS/390 systems could easily interface with various network protocols, enabling businesses to operate in a connected world. This inclusion paved the way for many organizations to expand their capabilities and offer new services, driving digital transformation.

In conclusion, IBM OS/390 represented a significant advancement in mainframe technology, combining scalability, security, and robust workload management. Its rich feature set and support for critical enterprise applications solidified its role as a vital component of many organizations' IT infrastructures, ensuring they could meet their operational challenges head-on while supporting future growth. As technology continues to evolve, the legacy of OS/390 remains influential in the realm of computing.