CEE5ABD

CEE5GRN

CEE5MDS

CEE5SPM

CEE5CIB

CEE5GRO

CEE5MTS

CEE5SRC

CEE5CTY

CEE5LNG

CEE5PRM

CEE5SRP

CEE5DMP

CEE5MCS

CEE5RPH

CEE5USR

CEE5GRC

 

 

 

Figure 56. Callable Services in LE/VSE 1.4 with Differing Names in OS/390 Language Environment

Note: Three further callable services are available in LE/VSE releases later than 1.4, and in LE/VSE 1.4 via APAR PQ08538. They are also available in OS/390 Language Environment. They are:

CEEMRCE CEE4SRP CEE5GRO

17.5.3.1 CEETDLI

The CEETDLI callable service in LE/VSE provides an interface to DL/I DOS/VS facilities. The OS/390 Language Environment callable service CEETDLI provides an interface to DL/I facilities that operate in IBM and CICS. You should read Chapter 8, ªDatabasesº on page169 and the appropriate DL/I and IMS publications, for more information.

17.5.4 LE/VSE 1.4 Locales

All locales provided in LE/VSE 1.4 are also provided in OS/390. This includes a number of locales and charmaps available in LE/VSE releases later than 1.4, and in LE/VSE 1.4 via APARs PQ08543 and PQ08547. Locales and the localedef utility, for OS/390 Language Environment, are described in the OS/390 C/C++ V2R4.0 Programming Guide.

17.6 CICS

This section discusses migration issues relating specifically to CICS.

17.6.1 COBOL and CICS

In OS/390 Language Environment, as in LE/VSE, some Language Environment COBOL run-time routines have the same names as their non-CICS counterparts. Therefore, if you plan to run COBOL programs in CICS, you must concatenate the library containing the Language Environment COBOL run-time routines in front of the library containing non-CICS routines, in the DFHRPL DD concatenation in your CICS startup job stream. Generally, the name of the Language Environment COBOL library is SCEECICS and the name of the non-CICS library is SCEERUN.

17.6.2 Run-time Options

The default settings for run-time options, for CICS, are the same for OS/390 Language Environment and for LE/VSE. Refer to the OS/390 Language Environment Programming Reference for the OS/390 Language Environment default settings.

366VSE to OS/390 Migration Workbook

Page 390
Image 390
IBM OS/390 manual 17.5.4 LE/VSE 1.4 Locales, Cobol and Cics, Ceetdli

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.