Tables

1.

Comparison of VSE Functions & Components to OS/390 Replacements

16

2.

Whos Normal Activities are Affected?

26

3.Nine Month Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4.CNV Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

5.ABC Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

6.SER Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

7. VSE Job Control Statements Summary . . . . . . . . . . . . . . . . . . . . 86

8.MVS Job Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . 88

9. Overview of POWER JECL Statements . . . . . . . . . . . . . . . . . . . . 89

10.JES2 Control Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

11.

JES2 Input Sources (compared to POWER)

. . . . . . . . . . . . . . . . .

212

12.

POWER/JES2 Job Scheduling Comparison

. . . . . . . . . . . . . . . . .

213

13.

POWER/JES2 Output Service Comparison

. . . . . . . . . . . . . . . . .

215

14.FCB Name Prefixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

15.

POWER/ICCF, VM/CMS, and JES2/TSO Functional Comparison . . . .

219

16.

Accounting Records for NJE Activities

224

17.

POWER Macro to JES2 Parameter Mapping

226

18.

PLINE MACRO to JES2 Parameter Mapping

228

19.

PRMT MACRO to JES2 Parameter Mapping

228

20.

PRMT MACRO to JES2 Parameter Mapping

229

21.

PNODE MACRO to JES2 Parameter Mapping

230

22.

PCPTAB MACRO to JES2 Parameter Mapping

230

23.POWER Exit to JES2 Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

24.Queue Management Commands . . . . . . . . . . . . . . . . . . . . . . . 232

25.Task Management Commands . . . . . . . . . . . . . . . . . . . . . . . . 232

26.Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

27.Network Management Commands . . . . . . . . . . . . . . . . . . . . . . 233

28.File Control Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

29.Sending Commands and Messages . . . . . . . . . . . . . . . . . . . . . 234

30.PRINTDEV Parameter Comparison . . . . . . . . . . . . . . . . . . . . . . 239

31. VSE - OS/390 Command Comparison . . . . . . . . . . . . . . . . . . . . 242

32.Useful COBOL Publications . . . . . . . . . . . . . . . . . . . . . . . . . . 252

33. Action of COBOL Program Termination Statements . . . . . . . . . . . 257

34.COBOL and PL/I: What Runs Where? . . . . . . . . . . . . . . . . . . . . 351

35.Useful Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

36. REPORT and ISASIZE Options, C/370 and DOS PL/I . . . . . . . . . . . 355

37.C/370 Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . 355

38.

VS COBOL II Migration Considerations

356

39.

DOS/VS COBOL Migration Considerations

356

40.DOS PL/I Migration Considerations . . . . . . . . . . . . . . . . . . . . . 357

41.ILC Migration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . 358

42.Option Recommendations Differing between LE/VSE 1.1 and OS/390 Language Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

43.Option Recommendations Differing between LE/VSE 1.4 and OS/390 Language Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

44.Option Recommendations for CICS Differing between LE/VSE and

OS/390 Language Environment . . . . . . . . . . . . . . . . . . . . . . . . 367

45.OS/390 DASD Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

46.S/390 Software Product Mapping . . . . . . . . . . . . . . . . . . . . . . . 539

© Copyright IBM Corp. 1998

xix

Page 21
Image 21
IBM OS/390 manual Tables, Xix

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.