C.1

Data Set Naming Guidelines

543

C.2

Components of a Data Set Name

544

C.2.1

High-Level Qualifier (HLQ)

544

C.2.2

Relative Importance

546

C.2.3

File Contents

546

C.2.4

User Name

547

C.2.5

Data Set Level

547

C.3

Things Not to Include in the Data Set Name

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

547

C.3.1

Department Number

547

C.3.2

Application Location

548

C.3.3

Management Criteria

548

C.3.4

Output Device Type

548

C.3.5

Expiration Date

548

C.3.6

Access Method

549

C.3.7

Job Name

549

C.4

Common Applications - Naming Conventions

549

C.4.1

TSO Naming Conventions

549

C.4.2

VSAM Data Set Naming Conventions

550

C.4.3

DB2 Naming Conventions

550

C.4.4

Generation Data Sets

551

Appendix D. Special Notices

553

Appendix E. Related Publications . . . . . . . . . . . . . . . .

E.1

International Technical Support Organization Publications

E.1.1

OS/390 and MVS Redbooks

E.1.2

Other Redbooks

E.2

OS/390 Product Publications

E.2.1

Planning Books

E.2.2

OS/390 Online Product Library

E.3

Other Publications

E.4

Other Sources

E.4.1

Books on the Internet

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

E.5

Redbooks on CD-ROMs

How to Get ITSO Redbooks . . . . . . . . . . . . . . . . . . . .

How IBM Employees Can Get ITSO Redbooks . . . . . . . . .

How Customers Can Get ITSO Redbooks . . . . . . . . . . . .

IBM Redbook Order Form . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . .

557

. . . . . . . .

557

. . . . . . . . .

557

. . . . . . . . .

557

. . . . . . . . .

557

. . . . . . . . .

558

. . . . . . . . .

558

. . . . . . . . .

559

. . . . . . . . .

559

. . . . . . . . .

559

. . . . . . . . .

559

. . . . . . . . .

561

. . . . . . . . .

561

. . . . . . . . .

562

. . . . . . . . .

563

Glossary

565

List of Abbreviations

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

583

Index

591

ITSO Redbook Evaluation

593

xviVSE to OS/390 Migration Workbook

Page 18
Image 18
IBM OS/390 manual Appendix E. Related Publications, 565, List of Abbreviations 583, 591, 593

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.