-E3380D

-E3380S

-E3990M3

-E3990M2

The above example would allow various filtering techniques the flexibility of recognizing different sets of data easily. Some examples of this follow:

∙

∙

∙

HLQ = E* -- All of the Engineering Data

HLQ = E3090* -- All of the 3090 CPU Family of Designs

HLQ = E3380* -- All of the 3380 DASD Family of Designs

C.2.2 Relative Importance

This level of qualification might indicate things such as:

∙

∙

∙

Production Data

Development Data

Test Data

In general, it would be important to be able to recognize the distinction between production data and test data. Other types of levels could be:

∙

∙

∙

Master Data

Update Data

Work Data

C.2.3 File Contents

This level of qualification should state what the data is. For example, an application strips some information out of the master database and builds a work file for subsequent processing. This file contains the employee id number and his job code. One might then call this file the ²employee- job code file². Other examples might include such things as:

∙Telephone call log (TELPHLOG)

∙Parts inventory file (PRTINVEN)

∙Parts unit cost file (PRTUCOST)

∙Payroll file (PAYROLL)

∙Checking account transaction file (CHKXACTN)

∙CADAM circuit design file (CKTDESGN)

∙Heat dissipation statistics file (HEATSTAT)

∙Simulation result file (SIMRSLTS)

∙Program source (PGMSRCE)

∙Life insurance account file (LIFEACCT)

∙User¢s Manual script file (USMANUAL)

∙Input manufacturing file (INPMANUF)

∙Transportation bill of lading file (XPRTBILL)

All of the above examples describe what the data is. There should be a unique character code for each data set type within a given application. This concept is demonstrated with each of the examples above.

Note: Eight characters have been used as the standard for the data set type in all of the above examples. This is probably a reasonable number of characters, although not mandatory. It may not even be a good idea to make file names too

546VSE to OS/390 Migration Workbook

Page 569 Page 571
Page 570
Image 570
IBM OS/390 manual Relative Importance, File Contents
Page 569 Page 571

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