/XRL/8

 

 

 

 

17, 17, 258, 259

CONDIF

2043CH17

 

 

 

 

 

 

352

17.1.2, Conceptual Differences between LE/VSE and OS/390

 

 

Language Environment

 

 

 

 

361

 

LVMC

2043CH17

 

 

 

 

 

 

352

17.2,

VSE to OS/390 Migration Considerations

LEVCON

2043CH17

 

 

 

 

 

 

352

17.2.1,

LE/VSE-conforming Languages

NONLEMG

2043CH17

 

 

 

 

 

 

354

17.4,

Migrating from Non-LE/VSE Run-time Environments

C370HD

2043CH17

 

 

 

 

 

 

355

17.4.2,

C/370

 

 

 

 

 

353

 

MIGLEV

2043CH17

 

 

 

 

 

 

359

17.5,

Migrating from LE/VSE

 

 

 

 

353

 

LEVX

2043CH17

 

 

 

 

 

 

364

17.5.2,

User Exits and Abnormal Termination Exits

 

 

 

 

367

 

ASMX4

2043CH17

 

 

 

 

 

 

364

17.5.2.1,

Assembler User Exits

ABTX4

2043CH17

 

 

 

 

 

 

365

17.5.2.3,

Abnormal Termination Exits

REXX

2043CH18

 

 

 

 

 

 

369

Chapter

18,

Procedure Language REXX

 

 

 

 

17, 17

 

CVUTIL

2043IMBD

 

 

 

 

 

 

373

Part

4,

Converting VSE Utilities to OS/390 Utilities

 

 

 

 

3, 4

 

SORT

2043CH19

 

 

 

 

 

 

375

Chapter

19,

SORT

 

 

 

 

18, 18

 

SRTJCL

2043CH19

 

 

 

 

 

 

375

19.1,

JCL Statements

 

 

 

 

375

 

SRTCTLS

2043CH19

 

 

 

 

 

 

377

19.2,

Control Statements

 

 

 

 

375

 

SRTADDS

2043CH19

 

 

 

 

 

 

379

19.3, Additional DFSORT/VSE Migration Considerations

 

 

 

 

375

 

DITTO

2043CH20

 

 

 

 

 

 

381

Chapter

20,

DITTO

 

 

 

 

18, 18, 244

DTCOMP

2043CH20

 

 

 

 

 

 

381

20.1, Compatibility with Previous Releases of DITTO

 

 

 

 

381

 

NLSFUN

2043CH20

 

 

 

 

 

 

382

20.2, DITTO Functions that are No Longer Supported

 

 

 

 

381

 

NRFUN

2043CH20

 

 

 

 

 

 

383

20.3, DITTO Functions that are Not Recommended

 

 

 

 

381

 

FUNCODE

2043CH20

 

 

 

 

 

 

384

20.4, DITTO Function Code Synonyms

 

 

 

 

381

 

NLSBAT

2043CH20

 

 

 

 

 

 

384

20.5, Batch Keywords that are No Longer Supported

 

 

 

 

381

 

NRBAT

2043CH20

 

 

 

 

 

 

385

20.6, Batch Keywords that are Not Recommended

 

 

 

 

381

 

DTSEC

2043CH20

 

 

 

 

 

 

385

20.7,

DITTO/ESA Security

 

 

 

 

381

 

BRVSAM

2043CH21

 

 

 

 

 

 

387

Chapter

21,

VSAM Backup/Restore

LIBR

2043CH22

 

 

 

 

 

 

389

Chapter

22,

Librarian

 

 

 

 

17, 17

 

LPLOG

2043CH23

 

 

 

 

 

 

393

Chapter

23,

LISTLOG/PRINTLOG - Printing Log Streams

FCOPDSS

2043CH24

 

 

 

 

 

 

397

Chapter

24,

VSE/Fast Copy and OS/390 DFSMSdss

 

 

 

 

17, 17

 

MIGENV

2043IMBD

 

 

 

 

 

 

399

Part

5,

 

Setting Up the Migration Environment

 

 

 

 

3, 4

 

SETUPEN

2043CH25

 

 

 

 

 

 

401

Chapter

25,

Prepare the Migration Environment

 

 

 

 

481, 482, 512

SETISC

2043CH25

 

 

 

 

 

 

404

25.2.5,

Inter-Systems Connectivity

SETSTDS

2043CH25

 

 

 

 

 

Page 653 Page 655
Page 654
Image 654
IBM OS/390 manual XRL/8
Page 653 Page 655

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