Related Redbooks

Here is a list of DFSMS ²Fast Implementation Techniques² (FIT) Redbooks:

∙

∙

∙

∙

∙

DFSMS FIT: Fast Implementation Techniques Process Guide, SG24-4478

Get DFSMS FIT: Fast Implementation Techniques, SG24-2568DFSMS FIT Forms and Foils, SG24-2570

DFSMS FIT: Fast Implementation Techniques Installation Examples, SG24-2569DFSMS/MVS V1R4 Technical Guide, SG24-4892

25.4.1.2 MVS Naming Standards

The following OS/390 resources are all identified by names. Some names are seven or eight characters, others can be up to 16 or 44 characters in length. By using significant positions of the name, you can more easily manage and control them for registration, security, and general systems management purposes.

Most installations use the first character of the name to identify the resource type or production application, such as P (Production), T (Test), S (Systems Programming), and I (Inventory Applications).

There are lots of entities to name in MVS. It is a good idea (if not required) to start these names with an alphabetic character (A-Z). This is not a complete list, but below are some resources that need names.

Data Sets

Names can be up to 44 characters long and start with a high-level qualifier that identifies both who owns the data set (such as a user ID, project, application, or group), along with an indication of production, test, or systems. Use these long names, with specific levels of the DSName to indicate the following:

∙

∙

∙

System vs. Production vs. Test; Temporary vs. Permanent Application Name or ID

Version Level

The data set name doesn¢t need to identify the access method being used. (The main reason people used to do this was because of the old VSAM catalog volume ¢ownership¢. Since this is no longer an issue with ICF catalogs, there is no need to include this.) Some other things not to include in the data set name because they will probably change: department, location management criteria, device type, or expiration date.

Generation Data Groups

The only difference here is that the data set name loses one level of

qualification, the lowest level. Don¢t use the generation to indicate a different type of data. For example, don¢t use ¢ (+1) ¢ for reports and ¢ (+2) ¢ for

intermediate files. Have separately named GDGs instead.

DASD and Tape Volume Serials

DASD and tape volumes are typically labeled so that they can be logically related to an application, geometry, storage group, or purpose, for example TSOxxx or PAYxxx. Keep in mind how you are going to list volumes from ISMF. For example, if I want to list all of my work or TSO packs, it would be nice to simply enter WRK* or TSO*.

408VSE to OS/390 Migration Workbook

Page 431 Page 433
Page 432
Image 432
IBM OS/390 manual MVS Naming Standards, Related Redbooks, Data Sets, Generation Data Groups, Dasd and Tape Volume Serials
Page 431 Page 433

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