4.namelists

5.process definitions

6.storage classes

These objects can be manipulated, that is, defined, deleted, changed, by the MQSeries commands.

Commands can be issued from:

∙

∙

∙

∙

∙

the initialization input data sets

the MVS console

the system-command input queue

the COMMAND function of the CSQUTIL utility

the operations and control panels using ISPF.

When you migrate to a CICS/ESA environment, your channels are special. They must be handled from the CICS region rather than through the MQSeries region: You monitor and control the channels to remote queue managers with the DQM (Distributed Queue Management) panels. Each MVS queue manager has a set of DQM CICS transactions for controlling interconnections to compatible remote queue managers using CICS ISC facilities.

The DQM channel control function (CCF) provides the administration and control of message channels. The channel definition file (CDF):

∙

∙

∙

∙

is a VSAM file

is indexed on channel name holds channel definitions

must be available to the CICS regions in which the channel control program runs and where the MQSeries Channel adapters run.

You use channel definition panels to:

∙

∙

∙

create, copy, display, alter, find and delete channel definitions

start channels, reset channel sequence numbers, stop channels and so on display status information about channels.

As you can see, the VSE/ESA related MQSeries objects (and more) exist also for MQSeries for MVS/ESA. Similarly, most of the parameters used to define these objects are identical or have an equivalent which allows you to reproduce or extend the definition you used under MQSeries for VSE/ESA.

But you can also see that the way the objects are defined is different in the OS/390 environment. There is no way to directly migrate the VSE/ESA definitions.

With the MQPUTIL program shipped with MQSeries for VSE.ESA V.1.4 you can print a listing with the MQSeries system, queues, and channels defined under VSE/ESA. You have to use this listing to recreate equivalent definitions for MQSeries for MVS/ESA. You will have to:

∙

∙

print the listing under VSE/ESA

check the DEFINE commands in the MQSeries Command Reference, SC33-1369 to find matching parameters to recreate the queue manager and queue definitions

∙

∙

decide on the environment from which you want to issue the commands

run the commands

204VSE to OS/390 Migration Workbook

Page 227 Page 229
Page 228
Image 228
IBM manual VSE to OS/390 Migration Workbook
Page 227 Page 229

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