readable, such as, a file called MASTER.PAYROLL.WEEKLY. This might be just too tempting to your average system hacker. A better choice might be

MR.PY.WK.

C.2.4 User Name

This qualifier should allow the end creator to assign their own unique name to identify the particular set of a certain type of data; for example, with a master circuit file, there would be a distinction between MYPART and YOURPART, or MYPART1 versus MYPART2. Some other examples of these are:

∙

∙

∙

∙

∙

∙

Part number (#0135678)

Print program (PRTPROGM)

New York Area (NEWYORK)

X15 Model (X15MODEL)

Geological site #458 (GEO#458)

Branch office #57 (BROFC057)

The intent of this level of qualification is to uniquely identify one piece of a type of data from another piece of the same type of data. Examples of this show the distinction between ²TELPHLOG.NEWYORK² and ²TELPHLOG.CALIF² or between ²PGMSRCE.MYPGM1² and ²PGMSRCE.MYPGM2². This should use the entire qualifier (that is, all of the eight characters).

C.2.5 Data Set Level

Another level of qualification that is sometimes useful in application areas is the level of the piece of data. Some examples of this are listed below:

∙Design level or version or release level (for example, for engineering, programming, documentation)

∙Change number, an arbitrary number to indicate a constantly increasing number for subsequent improvements on a piece of data

∙Cyclic level (for example, yearly, monthly, weekly, daily)

C.3 Things Not to Include in the Data Set Name

There are certain pieces of information that should never be part of the data set name. The general category of this data is that information which is very likely subject to change. This type of qualification usually doesn¢t add anything meaningful in terms of identifying the data for storage management reasons. Some examples of this are shown in subsequent sections.

C.3.1 Department Number

This is a piece of information that is sure to change either due to re-organization, or movement of projects or individuals.

Appendix C. DFSMS Naming Conventions 547

Page 570 Page 572
Page 571
Image 571
IBM OS/390 manual User Name, Data Set Level, Things Not to Include in the Data Set Name, Department Number
Page 570 Page 572

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