25.3.2.2 CBPDO

Custom-Built Product Delivery Option is a software delivery package consisting of uninstalled products without integrated service. You must use SMP/E to install the individual OS/390 elements and features, and their service, before you can IPL.

This method is not recommended for the new OS/390 installation.

25.4 Set Up Standards, Procedures, and Documentation

You now have a running system that is tailored to your environment and users. Your next step is to set up and document standards and procedures for all those people that will be using and operating it.

25.4.1 Installation Standards

As you develop your new OS/390 environment and your applications and user community grow, it is very important to develop good standards for all your resources and users. It is much easier to do this from the beginning than to go in later and impose standards and procedures were there were little or none beforehand.

25.4.1.1 Data Management Standards

DFSMS naming standards are not trivial, but there is a lot of guidance. This is really part of the DFSMS implementation process, which is a whole study in itself. The DFSMS FIT Redbooks have suggestions for naming the constructs and worksheets to assist with the migration. A good rule, as always, is to keep it fairly simple. Here are some suggestions for name-significant characters:

Data Classes - Start the name with D or DC, and include DSORG, RECFM, LRECL, or Space requirements.

Storage Classes - Start it with an S or SC. Examples are SCSTAND, SCPREF, SCFAST, and SCNOSMS. Distinguish service but dont use parameter values.

Management Classes - Start the name with M or MC. Use the remaining

characters for indicating which service elements separate it from the other classes. For example, MCNOMIG for data sets that you dont want to have

migrate/recalled. Other attributes could include Backup, Archive, Migration, and Space attributes.

Storage Groups - Start the name with G or SG. The name should identify the type of data associated with the pool. For example, use things such as SGWORK (for temp), SGPRIME (for batch production), or define storage groups according to size, for example SGLARGE for large and SGSMALL for small data sets. The advantage to this is reducing fragmentation on the volumes and reducing out-space abends for new allocations and extents.

Storage systems education is available for your systems programming staff. See IBM Education and Trainings storage systems course curricula for your area. Contact your IBM Representative or their web site at:

http://www.training.ibm.com/ibmedu/roadmaps/mainframe/storsys/

Chapter 25. Prepare the Migration Environment

407

Page 431
Image 431
IBM OS/390 Set Up Standards, Procedures, and Documentation, Installation Standards, Cbpdo, Data Management Standards, 407

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.