9.4.7 Bibliography

VSE/ESA

SC33-6601TCP/IP for VSE/ESA User′s Guide

SG24-2041The Native TCP/IP Solution for VSE

SG24-2040VSE/ESA as a Web Server

SC33-6686Writing Interlanguage Communication Applications

OS/390

SC28-1890OS/390 OpenEdition MVS Planning

SC28-1906OS/390 OpenEdition MVS Communications Server Guide

GC28-1920OS/390 Security Server (RACF) Planning: Installation and

Migration

SC28-1915OS/390 Security Server (RACF) Security Administrator

9.5 MQSeries

MQSeries represents a family of products which enable applications to use message queuing to participate in message-driven processing. With message-driven processing, applications can communicate across the same or different platforms, by using the appropriate message queuing software products. For example, VSE/ESA and OS/400 applications can communicate through MQSeries for VSE/ESA and MQSeries for OS/400 respectively. With MQSeries products, all applications use the same kinds of message headers. Communications protocols are hidden from the application.

MQSeries products implement a common application programming interface, the message queue interface (MQI), that is used on whatever platform the applications run. The calls made by the applications and the messages they exchange are common. This makes it much easier to write and maintain applications than using traditional methods. It also makes it easier to migrate message queuing applications from one platform to another.

The current releases on which the following migration discussion is based, are MQSeries for VSE/ESA Version 1.4 and MQSeries for MVS/ESA Version 1.2.

MQSeries for VSE/ESA 1.4 is a so-called level 1 product whereas the OS/390 version is a level 2 product. Level 2 products offer functions and facilities which extend those available in level 1 products. Since, generally speaking, level 1 functions are a subset of level 2 functions migration from MQSeries for VSE/ESA to MQSeries for MVS/ESA can be accomplished without loss of functionality in most cases.

The topics you should look into if you want to migrate from a VSE/ESA based

MQSeries environment to one based on an OS/390 system include:

∙

∙

the setup for MQSeries within your operating system environment

the networking definitions required to communicate with other MQSeries systems

∙

∙

the definition of your MQSeries objects such as queues and channels

the operating facilities offered to monitor MQSeries activities and diagnose and fix problems if they occur

Chapter 9. Telecommunications Subsystems 197

Page 220 Page 222
Page 221
Image 221
IBM OS/390 manual Bibliography, MQSeries
Page 220 Page 222

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