∙

∙

∙

∙

∙

∙

Enhanced interface to the World Wide Web (WWW) adds support for 3270-based transactions.

The CICS Gateway for Java has been ported for execution on OS/390 as an OpenEdition (R) application with CICS TS as the CICS server in a two-tier configuration.

REXX for CICS (Development and Runtime) added as two new elements of

CICS TS.

Support for S/390 (R) Parallel Sysplex extended with a new system management facility for defining and installing CICS resources across multiple CICS occurrences that are managed by the CICSPlex SM function on S/390 systems.

New DB2 resource definitions with resource definition online (RDO) as alternative to resource control table (RCT) definitions allowing 7 day, 24 hour availability.

Added client/server capability, with support for client partner LU6.2 applications across a TCP/IP network.

Key Prerequisites

∙

∙

OS/390 or MVS/ESA SP Version 5.2 or later

Either OS/390 Version 2 Release 4 DASD-only logging for single-system sysplex or a coupling facility for Parallel Sysplex

6.1.2 Essential Supplemental Reading and Migration Support Material

One of the critical components to a successful migration is access to all required manuals. Therefore, you are advised to order all CICS Transaction Server for OS/390 1.2 manuals as soon as possible.

For the latest information on what manuals are available with CICS, you should review the Planning for Installation, GC33-1789 and Release Guide for CICS Transaction Server, GC33-1570.

Pre-CICS for VSE/ESA subsystems migrating to CICS Transaction Server for OS/390 must read prior CICS/VSE Release Guides for possible migration task(s) that may not be addressed otherwise. CICS/VSE 2.3 customers should review the CICS/ESA Migration Guide 3.1, CICS/ESA Migration Guide 3.2, CICS/ESA 3.3 Release Guide, CICS/ESA Migration Guide 4.1, and CICS Transaction Server Migration Guide, GC33-1571. Also, your IBM service provider can access the CA1B SupportPac package on the Hursley TXPPACS disk. This package is a CICS/MVS 2.1.2 to CICS/ESA 4.1 migration cookbook, which should give you a perspective of changes to CICS/ESA for MVS users, plus CICS/VSE differences.

For example: An installation migrating from CICS/DOS/VS 1.6 should read the CICS/VSE Release Guides for 1.7, 2.1, 2.2, CICS/ESA Migration Guides 3.1, 3.2, CICS/ESA 3.3 Release Guide, CICS/ESA Migration Guide 4.1, and CICS Transaction Server Migration Guide, GC33-1571.

Note: IBM facilitates access to IBM manuals via the INTERNET. Using the

INTERNET location:′http://www.ibm.com/′, you can access IBM′s BookServer, your electronic library of books on the World Wide Web.

BookServer allows you to easily manage and display electronic books grouped into catalog collections and bookshelves. BookManager′s high-performance, morphological searching capabilities let you search books and entire bookshelves for the information you need.

134VSE to OS/390 Migration Workbook

Page 157 Page 159
Page 158
Image 158
IBM OS/390 manual Cics TS, Key Prerequisites
Page 157 Page 159

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