3.4.1.3 Estimated Schedule for ABC Responsibilities

The following is an estimated schedule for the ABC responsibilities. The actual schedule will be determined at project start.

Table 5. ABC Responsibilities

 

Month Number

1

2

3

4

5

6

7

8

9

 

 

 

 

 

 

 

 

 

 

 

Month Initial

J

J

A

S

O

N

D

J

F

 

 

 

 

 

 

 

 

 

 

 

 

 

01

- Manage ABC Conversion Responsibilities

**

**

**

**

**

**

**

**

**

 

 

 

 

 

 

 

 

 

 

 

02

- Participate in Project Planning

*

*

*

 

*

 

 

 

 

 

 

 

 

 

 

*

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

03

- Operate MVS Environment

**

**

**

**

**

**

**

**

**

 

 

 

 

 

 

 

 

 

 

 

04

- Provide Office Space and Project Support

*

 

 

 

 

 

 

 

 

Tools

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

05

- Determine and Supply VSE Material to be

*

*

*

*

*

*

*

*

 

Converted

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

06

- Assist with Conversion Specifications

 

**

**

 

 

 

 

 

 

**

 

 

**

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

07

- Apply Manual Modifications to VSE

 

*

*

*

 

 

 

 

 

Material (If any)

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

08

- Set up MVS Operations Tools

 

 

 

**

**

**

**

**

 

 

 

 

 

 

 

 

 

 

 

 

09

- Perform Online Application Tests

 

 

 

**

**

**

**

 

 

 

 

 

 

 

 

 

 

 

 

 

10

- Perform Batch Application Tests

 

 

 

*

**

**

**

*

 

 

 

 

 

 

 

 

 

 

 

 

11

- Participate in Applications Switchover to

 

 

 

 

 

 

 

**

*

MVS

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

12

- Support Initial MVS Operations

 

 

 

 

 

 

 

 

**

 

 

 

 

 

 

 

 

 

 

 

3.4.1.4 Estimated Schedule for SER Responsibilities

The following is an estimated schedule for the SER responsibilities. The actual schedule will be determined at project start.

Table 6. SER Responsibilities

 

Month Number

1

2

3

4

5

6

7

8

9

 

 

 

 

 

 

 

 

 

 

 

Month Initial

J

J

A

S

O

N

D

J

F

 

 

 

 

 

 

 

 

 

 

 

 

 

01

- Provide MVS Resources

*

 

*

*

 

 

*

 

 

 

 

 

 

 

 

 

 

 

 

 

02

- Install, Maintain, and Support MVS

**

**

**

**

**

**

**

**

**

Environment

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

03

- Assist with Conversion Specifications

 

**

**

 

 

 

 

 

 

**

 

 

**

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

04

- Participate in Applications Switchover to

 

 

 

 

 

 

 

**

*

MVS

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

05

- Support Initial MVS Operations

 

 

 

 

 

 

 

 

**

 

 

 

 

 

 

 

 

 

 

 

Chapter 3. Developing the Plan

55

Page 79
Image 79
IBM OS/390 manual Estimated Schedule for ABC Responsibilities, Estimated Schedule for SER Responsibilities

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.