25.5.1.4 NetView FTP Access

You can also use the same VTAM connections to send bulk data between the two systems with NetView FTP.

See NetView FTP V2 MVS Installation, Operation, and Administration, SH12-5657.

25.5.1.5 Providing NJE Connection to the OS/390 System

You can connect VSE/POWER and OS/390 JES2 systems together via NJE to route jobs and output from one system to the other. In addition to the POWER and JES2 books, see NJE Installation, Operation and Use with JES2 and Other Systems, GG22-9339 for guidance and examples.

25.5.2 MVS BCP Customization

There are many parameters and installation exit points which you can use to further customize your OS/390 system. The following information is not a complete list, but a short overview of the members in Parmlib and exit points which may be used.

See the OS/390 MVS Initialization and Tuning Guide, GC28-1751 for storage considerations, paging, and SRM guidance.

See Chapter 1 of OS/390 MVS Initialization and Tuning Reference, GC28-1752 for general information called ²System Tailoring²:

MVS Hardware Configuration Definition

System Tailoring at Initialization Time

Understanding the Master Scheduler Job Control Language

Overview of Parmlib Members

Implicit System Parameters

Managing System Security -- APF-Authorized Library List

Specifying Installation Exits

Specifying LNKLST Concatenations

25.5.2.1 SYS1.PARMLIB Parameters

There are dozens of ²named² members of SYS1.PARMLIB for OS/390 Release 4 customization. They are described in the OS/390 MVS Initialization and Tuning Reference.

There are also many other members that can be used to tailor base elements of OS/390, optional features, other IBM products, and ISV products. See the appropriate product documentation for specifics.

25.5.2.2 MVS Exits

There are many installation defined exit points in OS/390 components where installations can insert their own code to affect normal processing. There are exits for SMF, DFSMS, IPCS, JES2, RACF, TSO/E, MPF, and many other functions. However, these are not usually necessary and can be more trouble than they are worth. (Exits often need to be re-assembled or re-worked with future system upgrades.)

Chapter 25. Prepare the Migration Environment

415

Page 439
Image 439
IBM manual MVS BCP Customization, NetView FTP Access, Providing NJE Connection to the OS/390 System, MVS Exits

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.