Preview: S/390 Server Operating System

October 10, 1995
Announcement Number: 295-423


Document's Table of Contents:


(Corrected on October 17, 1995) The OS/390 Product Content section has been revised.

Abstract



In Brief . . .

OS/390 is built on the robust classic strengths you would expect from S/390. It represents a major step in the S/390 transformation.

  • MVS transformed into a leading edge server operating system delivering a modern set of server functions
    • Open and industry standards
    • Integrated client/server functions
    • Network-centric, computing support
    • S/390 and UNIX(1) application environment support
    • Object technology support
  • Reduced complexity through integration of existing products and features
    • Integrates functions of more than 25 products in the MVS environment
    • Simplified installation
    • Comprehensive testing performed before shipment to the customer
  • Total cost of computing characteristics competitive with alternate solutions

  • The broadest spectrum of application environments provided
    • Single set of interfaces for Software Developers' use
    • UNIX interfaces via robust OpenEdition(TM) and DCE-based functions
    • Client/server application support
    • Object programming support
    • Traditional S/390 application support
    • Leading edge S/390 communications server
----------------------------------------

Two years ago, IBM revealed the strategy for transforming mainframe bipolar hardware processors into smaller-in-size, energy efficient, larger-in-capacity, CMOS technology parallel servers. The new processors even have a new name -- S/390(R) Parallel Enterprise Server. Customers have embraced these new servers for affordable growth and the proven performance of the S/390 architecture. Today, however, we want to focus your attention on the transformation that has been taking place in support of the new S/390 Parallel Enterprise Server -- the transformation of the operating system software. Today, we are moving that transformation to center stage, sharing with you our vision for the S/390 server systems of tomorrow.

The next generation of operating systems for the S/390 will retain the classic strengths of the traditional MVS/ESA(TM), VM/ESA(R) and VSE/ESA(TM) operating systems that have been the backbone of many organizations' computing capabilities for years. These operating systems are being updated to deliver changes requested by our customers. Each of the new operating systems will be given new names. For this preview, the new operating system for MVS customers is being called OS/390.

OS/390 will be attractive to those customers currently using MVS. This new S/390 server operating system will be a network-ready, integrated operational environment. The base operating system functions of key products in the MVS environment will be installed and tested as one product prior to customer delivery. Installation of OS/390 will provide the base operating system, an open communications server, and distributed data and file services. Other integrated functions to be integrated represent the latest technological enhancements of the existing systems, including parallel sysplex support, object-oriented programming, OSF** Distributed Computing Environment (DCE), multimedia, and open application interfaces. A set of optional functions can be installed as an integrated and tested part of OS/390. As a result, the most available, high-performance, and scalable server operating system platform will be developed, tested and delivered as a single product, to meet your client/server needs. In addition, IBM will continue to offer a full range of services offerings customized to your environment. These services are designed to enable rapid deployment of OS/390 to meet the needs of your business.

We are working to develop comparable plans to meet the needs of our VM and VSE customers. The transformation will be staged to support customer plans for migration from current product releases to the new S/390 server operating systems. Current application and middleware investments will be protected, because this integration will not require programming changes. Value will be derived from the enablement of functional capabilities and productivity benefits. In addition, the total cost of computing characteristics will be competitive with alternative solutions.

OS/390 is currently planned to be made available in March 1996. Releases are currently planned to be delivered at approximately six-month intervals. New function will be delivered in a staged manner, over time.

Previews provide insight into IBM plans and directions. General availability, prices, ordering information and terms and conditions will be provided when the product is announced.

(R)   Registered trademark of International Business Machines
      Corporation
(TM)  Trademark of International Business Machines Corporation
**    Company, product, or service name may be a trademark or service
      mark of others.
(1)   Registered trademark in the United States and other countries
      licensed exclusively through X/Open Company Limited.



DESCRIPTION

OS/390 Overview

OS/390 is the base operating system and communications server for S/390. It extends the capacity and robustness of IBM servers to the largest scale in the industry. OS/390 is much more because it integrates the enterprise.

S/390 has been transformed to the enterprise server of today. OS/390 is S/390's open, scalable, object-enabled, large systems enterprise server operating system that completely replaces the base MVS operating system as previously delivered. OS/390 delivers a complete set of functions that represent the MVS system, plus new function. It reduces the complexity associated with planning and installing this new server operating system. A comprehensive set of tests include environments that help to meet or exceed our customer's quality expectations for OS/390.

Installation Flexibility: OS/390 provides the base for the parallel sysplex environment. All of the functions necessary for parallel sysplex have been tested in a parallel sysplex environment.

OS/390 will run on all ESA-capable machines supporting MVS/ESA SP Version 5 Release 2.2.



OS/390 Integrated Computing -- Applications

OS/390 provides a comprehensive and diverse application development and execution environment. The new integrated technology combines with the strengths of current application interfaces, which have been preserved, provides freedom of choice for application environments such as POSIX, XPG4 Base Profile, X/Open** UNIX, DCE, SOMobjects(TM), ISPF, TSO/E, Batch, and APPC. It provides the enterprise-wide client/server infrastructure businesses need for fast and flexible deployment of new applications.

It especially provides the enabling for the following applications and environments:

  • UNIX
  • TSO/ISPF
  • Objects
  • Batch
  • APPC
OS/390 is the base for transaction processing with IMS(TM) TM and CICS(TM). It is also the base for database services like IMS DB, DB2(R) and others.

With OS/390, application developers will get a base package of open functions that are required in the client/server arena. In addition, the inclusion of SOMobjects for MVS and the Language Environment(R) for MVS library, that incorporates the C/C++, COBOL and PL/I Run Time library, makes OS/390 an exceptional application server.



Application Enablement -- Object Technology

Today's complex business environment has created an even more complex application development environment. Client/server and open computing demands, cost reductions, skills shortages and new technologies add up to greater demands on application developers. In order to meet this demand, many organizations have turned to object technology which provides the ability to create flexible and dynamic applications that can be adapted easily to business changes.

One of the keys to object-oriented programming is SOMobjects for MVS. The System Object Model (SOM) which is utilized by SOMobjects for MVS, defines an architecture for defining and managing binary object class libraries. SOM conforms with the Object Management Group's (OMG) Common Object Request Broker Architecture (CORBA). It allows applications written in different languages to use a common class library, while it enables libraries to be extended without affecting existing applications.

Use of objects for functions and data will enable simplified code sharing and reuse, data sharing among heterogeneous systems, and provide investment protection. It facilitates the development and revision of mission critical applications. Object-oriented (OO) technology reduces development cycle time and improves application time to market.

OO technology increases application code quality with the capability to build programs from existing, tested components.

OO technology provides a compatible development base with OS/2(R), AIX(R) and Windows+, which offers a greater level of application portability.



Distributed Applications

OS/390 provides distributed data access within a heterogeneous environment based on existing open systems standards. The OS/390 environment provides the services that allow a distributed application to interact with a collection of heterogeneous computers, running any operating system for which OSF DCE is available (like OS/2, AIX, HP-UX** and others) and connected to different types of networks. Besides the primary functions needed to support the Single UNIX specification, OS/390 includes data access functions for open distributed computing like DCE, Distributed File Server (DFS), and Network File System (NFS).

The Shell and Utilities function and the dbx debugger function support the developing and testing of UNIX applications. They provide the look and feel of UNIX and access to the appropriate data and libraries.

The S/390 Open Systems Adapter Support Facility (OSA/SF) element of OS/390 is a key enabler in a heterogeneous environment. This software tool provides a simple means to configure and manage S/390 Open Systems Adapters delivering connectivity to Ethernet, Token-Ring, and FDDI LANs. OSA/SF supports LAN Server for MVS and LANRES/MVS environments as well as enabling access to TCP/IP, SNA/APPN, and NetWare/IPX clients.

OpenEdition Distributed Computing Environment (DCE)

The OpenEdition DCE for OS/390 consists of:

  • OpenEdition DCE Base Services
  • OpenEdition DCE Security Server
  • OpenEdition DCE Distributed File Service
  • OpenEdition DCE Application Support (5655-064)
DCE is a comprehensive suite of integrated, yet modular technologies that support transparent interoperability and resource sharing in heterogeneous, networked environments. The DCE technologies include Remote Procedure Call (RPC), Directory, Security, Time, and DFS. DCE RPC provides programmers with powerful tools to build client/server applications. It extends the familiar and proven local procedure call model, masking much of the underlying network complexity. DCE Directory provides naming support which allows DCE services and applications to easily locate and look up information about resources in a distributed environment. DCE Security supports security-sensitive distributed computing including authentication of identities, authorization checking for access to services and resources, verification of data integrity, and data privacy. DCE Time services provides precise, fault-tolerant clock synchronization across networks of computers in the distributed environment.

The OpenEdition DCE Distributed File Service at the OSF DCE level 1.0.3a, is a distributed client/server application that allows users to easily share data in a distributed environment. It provides access to the Hierarchical File System (HFS) and the DCE local file system. DFS works in conjunction with DCE RPC, security and directory services. It supports the naming convention that allows unique naming of files throughout your enterprise for uniform access to data. Client caching of files and directories by DFS reduces the load on the system and network, resulting in improved performance. It also provides a high level of data consistency for distributed data by using an advanced token management and a client caching scheme. DFS allows you to replicate data across multiple servers. The replicated data is automatically updated by DFS, resulting in improved reliability and availability. DFS uses distributed databases to keep track of file location, and also uses authentication, and access control lists to improve the manageability of a distributed environment.

Network File System

Network File System provides access from an heterogeneous environment widely used in the UNIX environment. The DFSMS/MVS(TM) Network File System feature provides workstation access to MVS data sets. Support is provided for most data set organizations. This feature can also be used as a network file server. Workstations can treat the MVS hierarchical file system as an extension of their own file system. In this way the system has the look and feel of a UNIX system with the storage capacity, storage management, security and reliability of MVS.

Local Area Network (LAN) Services

LAN Services mean LANRES/MVS and LAN Server for MVS.

  • LANRES/MVS provides disk serving, print serving data distribution and central administration for Novell** NetWare** LANs.
  • LAN Server for MVS:
    • Provides an OS/2 compatible file system on MVS/ESA that works in conjunction with OS/2 LAN Server on the workstation
    • Allows multiple OS/2 LAN Servers and NFS clients to share a common data repository with full update capability for every client.
    • With this announcement, the multimedia capability of LAN Server for MVS with new functions is extended. It provides Quality-of-Service (QoS) by delivering multimedia assets to OS/2 LAN Server Ultimedia(R) workstation clients in a timely, usable and quality manner.
These LAN services expand to enterprise LAN users the capability of Workgroup LAN servers to support databases and very large data assets. This provides central management, high capacity, and high performance for an integrated solution to meet the challenges of distributed computing at the local, regional and global level.



Communications Server for OS/390

User access to, and sharing of, information and services on local and remote servers is essential to gaining value from client/server solutions. IBM considers networking so important that we've included our world-class set of networking services in the OS/390 base and named it Communications Server.

With this leading edge, open, networking support, OS/390 serves mission-dependent, business-to-business and business-to-consumer communications across LANs and enterprise wide-area networks (WANs) and the Internet. Among its key benefits are:

  • Connectivity to a broad set of client applications and vendor platforms
  • Easy deployment for client/server
  • Unmatched network performance and availability
  • Application choice independent of network choice
  • Investment protection for current S/390 applications
The following looks at these in more detail:
  • Connectivity to broad set of users and vendor platforms

    As the hub for business transactions and information exchange, network access to the S/390 by customers and employees should not be constrained by the brand of workstations, servers and platforms in use. For many reasons, there is usually a diverse mix in most organizations (for example, OS/2, Windows, UNIX, MVS, VM and VSE, and so on).

    The programming interfaces (for example, APPC, RPC, SOCKETS, SNA (3270)) and wide-area networking protocols (SNA, Transmission Control Protocol/Interconnect Protocol (TCP/IP)) supported by OS/390 are prevalent throughout the information technology industry (TCP/IP is the base networking protocol for the Internet). Support of all these interfaces provides the flexibility for the S/390 users to share information and transactions less constrained by the variety of workstations and servers platforms in the LAN, WAN or the Internet.

  • Easy deployment for client/server

    OS/390 and the Communications Server provide a rich set of communications programming interfaces. Whether an APPC, OpenEdition DCE RPC, or Berkeley Software Distribution (BSD) Sockets interface best meets the needs of your client/server applications design and implementation, OS/390 supports your choice.

    Additionally, APPN(R) eliminates tedious, coordinated SNA network definitions so client/server implementers can easily capitalize on the strengths of SNA's APPN/APPC networking functions.

    The ISPF Client/Server end-to-end solution when coupled with TCP/IP provides an easy deployment of client/server graphical interface.

  • Unmatched performance and availability

    APPN/High-Performance Routing (HPR) offers superb performance for APPN networks. APPN/HPR and TCP/IP networks accommodate route failures without disrupting end users.

    Support for a wide range of communications technologies includes connection to Asynchronous Transfer Mode (ATM) networks when higher speeds are required.

  • Application choice independent of network choice

    The choice of communications programming interfaces can dictate the underlying network protocol. A valuable application written to Berkeley Sockets may well need to be shared with users across an SNA network or, conversely, an APPC application across a TCP/IP network.

    Working with like services in the users' partner network, Communications Server for OS/390 allows the application decision to be made independent of the network choice -- giving freedom to make the optimum choices for the business needs.

  • Investment protection for current S/390 applications

    Communications Server for OS/390 allows the enterprise to move forward, taking advantage of leading edge networking solutions, while protecting current investments in 3270, or other S/390 applications running on VTAM(R) or TCP/IP.

    Communications Server for OS/390 is comprised of the following program products for MVS/ESA:

    • VTAM Version 4.3
    • VTAM Version 4.3 AnyNet(TM)/MVS feature
    • TCP/IP Version 3 (the then most current release)
    Its coexistence and interoperability is identical to that of the products listed above. Applications interfaces are upward compatible so that those that run on prior releases of VTAM or TCP/IP should continue to function unchanged.



Data Server Choice

In addition to the traditional S/390 strengths, enhancements to LAN Services create a server environment on OS/390 to allow clients transparent access to OS/390 resources. Support is provided for users of NetWare, IBM LAN Server and Network File System. OS/390 systems and NetWare LAN servers can be integrated in a way that helps maximize user productivity and delivers unique business solutions. Services include disk serving, print serving, data distribution and LAN administration.

OS/390 systems and IBM LAN servers can be combined to bring the data management, bandwidth and high I/O capacity of the S/390 system to the user. Workstation applications may use S/390 system resources without modification. This file serving capability coupled with the Quality of Service enhancements delivered with OS/390 are especially well suited for environments requiring access to a large numbers of multimedia objects such as digitized pictures and videos.

For users of TCP/IP, the File Transfer Protocol (FTP) is supported, allowing information to be easily exchanged between OS/390 and other systems. Network File System support provides access to information managed by OS/390.



OS/390 Security Integration

One of the major challenges that face the business is enterprise-wide security, especially in a heterogeneous environment. New function included in the OpenEdition DCE Security Server provides a fully functional OSF DCE 1.1 level security server. Customers can now configure their DCE cell with a security server on the central OS/390 enterprise server. Availability of this critical DCE technology component in OS/390 addresses a key customer requirement supporting use of DCE in production environments. The OS/390 Security Server includes the OpenEdition DCE Security Server and RACF(TM). Therefore, both the local and distributed security functions are now available as a single OS/390 feature.

Non-DCE applications can also take advantage of DCE security features through the Generic Security Services API. By using the GSS API, applications do not have to provide their own user registry. Instead, they can exploit the DCE Registry without having to completely redesign their underlying distribution model.

Interoperability between OpenEdition DCE and RACF allows DCE-based servers, running on OS/390, to use DCE for authentication and RACF for access control. Interoperation between OpenEdition DCE and RACF provides identity mapping between DCE principals and MVS userids and single authentication within the DCE-RACF domain. In addition, administration tools are provided as part of the OpenEdition DCE-RACF interoperability function that aid in administering user data in the DCE + RACF environment.

OpenEdition DCE-RACF interoperability reduces the complexity end users face when wanting to access information between the OS/390 and DCE environments.

OS/390 Product Content

OS/390 is a set of MVS base, open, client/server and applications-enabling functions orderable with one program number and delivered as one product. Customers may see a reduction in the time and skill necessary to plan, order, and integrate the following base MVS and communication server elements.

OS/390 contains equivalent function at or beyond the release levels listed for the following currently available products:

  • Base Server elements
    • MVS/ESA SP(TM) Version 5.2.2
      • BCP Version 5.2.2
      • JES2 Version 5.2.0
      • HCD
      • OpenEdition DCE Base Services (OSF DCE level 1.1)
      • OpenEdition DCE Distributed File Service (DFS) (OSF DCE level 1.0.3a)
      • ESCON(R) Director support
      • LANRES/MVS Version 1.3.1
      • LAN Server for MVS Version 1.1 with enhancements
      • MICR/OCR support
      • OpenEdition MVS Services (MVS Version 5.2.2 level)
      • OpenEdition MVS Debugger (MVS Version 5.2.2 level)
      • OpenEdition MVS Shell and Utilities (MVS Version 5.2.2 level)
      • SOMobjects for MVS Runtime Library Version 1.1.0
    • Bulk Data Transfer (BDT) base Version 2
    • BookManager(R) Read Release 3
    • DFSMSdfp(TM) Version 1.3.0
    • DFSMS/MVS Network File System Feature Version 1.2.0
    • EREP/MVS Version 3.5.0
    • GDDM(R) Version 3.1.1 (including PCLK and OS/2 Link)
    • High Level Assembler Version 1.2.0
    • ICKDSF Release 16
    • ISPF Version 4.2.0
    • Language Environment for MVS Version 1.5.0
    • OSA Support Facility Release 1
    • SMP/E(TM) Version 1.8.1
    • TSO/E Version 2.5
    • VisualLift RTE Version 1.1.1
  • Communications Server elements
    • VTAM Version 4.3 with AnyNet/MVS
    • TIOC
    • TCP/IP Version 3 (the then most current release)
Customers will have the ability to replace OS/390 base server or communications server functions with a product that provides similar functions. A mechanism will be provided when ordering and pricing information is available. All OS/390 integrated testing results and performance claims will be voided with such replacement.

IBM plans to deliver optional features that have a high affinity to the base OS/390 system. The initial list of optional features is:

  • BookManager Build/MVS Release 3
  • Bulk Data Transfer (BDT) Release 2 File-to-File
  • Bulk Data Transfer (BDT) Release 2 JES3 SNA NJE
  • IBM C/C++ Version 3 Release 2
  • GDDM-REXX Version 3.1.1
  • JES3 Version 5.2.1
  • TCP/IP CICS Sockets Version 3 (the then most current release)
  • TCP/IP IMS Sockets Version 3 (the then most current release)
  • Security Server (RACF Version 2.2 + OpenEdition DCE Security Server at OSF DCE level 1.1)
  • RMF(TM) Version 5.2
  • VisualLift ADE Version 1.1.1
  • SOMobjects for MVS Application Development Environment (ADE) Version 1.1.0
  • OpenEdition DCE User Data Privacy (DES and CDMF)
  • OpenEdition DCE User Data Privacy (CDMF)
  • Language Environment Data Decryption (DES)
  • TCP/IP Kerberos DES
  • TCP/IP Kerberos non-DES
  • TCP/IP Network Print Facility
  • TCP/IP Offload to OS/2
  • Preconfigured CD for PC Server 500 System/390(R)
IBM also plans to deliver optional products that have a high affinity to the base OS/390 system. The initial list of optional products is:
  • DFSMShsm
  • DFSMSrmm
  • DFSMSdss
Integration Testing: To further reduce migration time, the OS/390 product will be system integration tested using a production-like environment. This environment includes systems management function provided by SystemView for MVS and subsystems such as CICS, IMS and DB2. This additional testing supplements existing functional testing with a focus on tasks performed by customers in the production environment, thus helping establishments move more quickly to new function. System integration testing will be provided for all releases of OS/390.

New Delivery Option: IBM plans to provide a new delivery option for OS/390 that will be based on the system replace vehicle concept. The system replace vehicle combines selected functions from both the CBIPO and other existing delivery vehicles. It will be ordered through a checklist, allowing product selection. It will be delivered in a dump by dataset format with DLIBs and TARGET libraries already generated which will include integrated maintenance. Customers can take advantage of IBM Services offerings for both system customization and advanced function enablement.



Information -- Makes the System Go

OS/390 takes more steps to:

  • Increase customers' ability to find and use information on the screen, which increases productivity
  • Reduce the amount of hardcopy customers need, which reduces cost
OS/390 provides BookManager READ/MVS as an integrated function on the host. BookManager READ provides a powerful search and viewing capability that makes it possible to use softcopy as the main source of information. Many customers are already familiar with softcopy, which is easy to learn because it is modeled on manuals.

Customers will receive:

  • A small set of hardcopy information that is needed to plan for and install OS/390
  • A complete set of softcopy information, shipped on a platform-independent CD-ROM
Details for obtaining a complete set of hardcopy information will be available when pricing and ordering information is available.

New Function Included in OS/390

The following new function will be delivered in a staged manner, over time. Releases are planned to be delivered at approximately six month intervals.



OS/390 Release 1



OS/390 OpenEdition DCE



OpenEdition DCE Base Services

To allow customers to take full advantage of distributed computing in their networks, IBM has upgraded the OpenEdition DCE Base Services for MVS/ESA to the Open Software Foundation (OSF) DCE Version 1.1 level. It offers major improvement in the areas integration services, enhanced enterprise support and administration and programming aids.

Integration services allow non-DCE resource managers access to DCE services, providing a common point of administration for the customer. Three new integration services provided in OSF DCE Version 1.1 are:

  • Generic Security Services (GSS API)
  • Extended Registry Attributes (ERA)
  • RPC Encoding Services
GSS API enables non-RPC network applications operating within a DCE environment to use the DCE services for authentication, data integrity and data privacy.

ERA extends the DCE Registry to allow for storing non UNIX operating system data.

RPC Encoding services are an interface for non-DCE programs to the marshalling services of DCE. It enables non-DCE communications programs to use DCE to pack and unpack data sent over the network instead of these programs inventing their own mechanisms to do the same thing.

Enhanced enterprise support extends the scalability and robustness of DCE. New enhanced enterprise support features are:

  • Delegation
  • Audit
  • Extended login and password management
Delegation enables an intermediate server to act on behalf of clients and assume the identity of the original client.

Audit allows tracking of security-related events within DCE. Specific events can be audited, filters can be used, and the destination of output can be specified. The security and time servers of DCE use the audit service.

Extended login and password management reduces the chance of a user's password being compromised. Password management enables DCE sites to deploy their own password strength-checking mechanisms against the DCE Registry.

Improved administration and programming aids address management and administration interfaces, both at the user and programmer level. Improvements are attained through the following features:

  • DCE Control Program (DCECP)
  • DCE Daemon (DCED)
  • Access Control List (ACL) Library
  • Backing Store Library
DCECP is a command line interface for DCE administration. It covers most of the functionality of the current control programs, but from within one program and with a more consistent interface.

DCED is a replacement and an enhancement for RPCD and SEC_CLIENTD. It provides new functionality in the area of application management and auto-start of DCE servers upon receipt of an RPC intended for a registered (but not active) server.

The ACL Library is an implementation of an ACL manager that can be incorporated into DCE application servers.

The Backing Store Library is a persistent store for DCE application servers. It can index items it stores via UUIDs.

OpenEdition DCE Base Services has extended the security services provided in OSF DCE Version 1.1 to include the following additional enhancements:

  • Interoperation between OpenEdition DCE and RACF that provides identity mapping between DCE principals and MVS userids, single authentication within the OpenEdition DCE -- RACF domain, and some security administration tools for the DCE+RACF environment

  • Support for the Commercial Data Masking Facility (CDMF) algorithm for user data encryption.
Investment Protection: The DCE architecture allows application development and deployment to be performed on any platform supporting the Distributed Computing Environment. A process running on one workstation can interoperate with one or more processes on other computing platforms, even when they are from different vendors with different operating systems. DCE does this transparently (that is, without users or programmers having to specify which network communication protocols to use). In addition, time synchronization, security and directory services are provided in an integrated environment.

Non-DCE applications can also take advantage of DCE security features through the Generic Security Services API in the OpenEdition DCE Base Services. By using the GSS API, applications do not have to provide their own user registry. Instead, they can exploit the DCE Registry without having to completely redesign their underlying distribution model.

Interoperability between DCE and RACF allows DCE-based servers, running in an MVS system, to use DCE for authentication and MVS RACF for access control.

Connection Oriented RPC has been added to this release of OpenEdition DCE Base Services. Now, applications can use either connectionless (UDP) or connection-oriented (TCP) communication protocols.

Function integrated into OS/390 from MVS/ESA SP Version 5 Release 2.2 plus VTAM AnyNet/MVS provides support for OpenEdition Converged Sockets. Converged sockets support means that customers using DCE RPC socket applications now have the capability to dynamically and simultaneously choose to communicate across either APPN/SNA, TCP/IP, or both networks.

All of the above allow you to mix and match or reuse existing computing resources to best meet the needs of your business.

User Productivity: One of the goals of DCE is to reduce the end user complexity of multiple IDs and passwords and repetitive signon procedures. The OpenEdition DCE -- RACF interoperability provided in the OpenEdition DCE Base Services reduces the complexity end users face when wanting to access information between the MVS and DCE environments.

System Management: The Distributed Computing Environment provides services that address the needs that are inherent in a distributed system. These services include management tools for administering the distributed system. DCECP is a new administrative tool that provides a consistent interface to DCE services. Previously, due to the diverse sources of DCE functions, administration varied from service to service.

In addition, administration tools are provided as part of the OpenEdition DCE -- RACF interoperability function that aid in administering user data in the DCE+RACF environment.

OpenEdition DCE Security Server

The OpenEdition DCE Security Server for MVS/ESA, part of the OS/390 optional Security Server feature along with RACF, provides a fully functional OSF DCE Version 1.1 level security server for MVS/ESA. Customers can now configure their DCE cell with a security server on the mainframe. Availability of this critical DCE technology component on OS/390 addresses a key customer requirement supporting use of DCE in production environments.



OS/390 LAN Server for MVS Version 1.1.0 Enhancements

Multimedia

Multimedia has emerged as the next step in the evolution of the information technology paradigm. It entails processing of large information objects, such as images, full-motion video, voice, graphics and text. Multimedia focuses on end-to-end business solutions applications. It provides a unique opportunity to increase productivity and to attain higher quality products and services. At the same time, due to large objects size and response time requirements, multimedia applications place significant demand on networks, servers, CPU, and LAN bandwidth. The guaranteed delivery of timely, usable, and quality multimedia is often referred to as Quality-of-Service (QoS). Quality delivery of video requires isochronous delivery where continuous multimedia frames are delivered at sufficient speed to guarantee that no interruption or break-up of picture or sound occurs.

With this announcement, the LAN Server for MVS element of OS/390 significantly extends and makes available the capability for multimedia support and delivery of QoS. It provides the new capability of delivering hundreds of simultaneous video streams to user workstations. LAN Server for MVS with the S/390 Server builds on its demonstrated capability as a large-scale multimedia server.

LAN Server for MVS has been enhanced for performance, easy management of large data objects and QoS. User workstations access multimedia data via OS/2, DOS or Windows client requesters providing a totally seamless connection to audio and video data stored on the MVS system.

The large system capacity of the S/390 Server with LAN Server for MVS facilitates enterprise-wide implementation of storage intensive client/server multimedia applications, simplifying the administration and management of multimedia data. Video-on-demand applications permit access to movies and other recorded multimedia to start, pause, resume or stop the presentation according to the viewer's control. These multimedia applications can coexist with non-multimedia applications.

The LAN Server for MVS Version 1.1.0 with the Resource Manager function provides the management of MVS system resources to give uninterrupted data to the OS/2 Front End Processor (FEP). The LAN Server Ultimedia's RRS provides the resource reservation that maintains data transfer integrity from the FEP to the workstation multimedia client. The system resources that are managed end-to-end are: channel and LAN bandwidths, storage buffers, DASD space and bandwidth.

The LAN File Services/ESA (LFS/ESA) statement of direction (SOD) given in the LAN File Services/ESA Version 1 Release 1.1 announcement (dated September 13, 1994) to provide LFS MVS/ESA support for the required QoS capability to deliver multimedia to OS/2 LAN Server Ultimedia clients, is satisfied by this LAN Server for MVS Version 1.1.0 announcement.

Customer Benefits

LAN Server for MVS Version 1.1.0 continues to provide the OS/2 LAN Server and NFS file serving that was announced with LAN Server for MVS Version 1.1.0. For these customers, the new disk striping capability significantly extends the size of the LFS disk above the current addressing limit of 4GBs. This allows applications to exploit the storing and accessing of very large objects.

For the multimedia customers who require end-to-end bandwidth reservation, LAN Server for MVS Version 1.1.0 provides QoS to OS/2 video-on-demand clients by guaranteeing to deliver video, data, and audio at a specified rate. It introduces disk striping and the metafile dataset for managing multiple user access to the same file. Resource management function optimizes placement of multimedia data to best utilize the bandwidth and space of the disks. Support is provided for concurrent execution of multimedia and non-multimedia applications.

The multimedia customers who do not require the bandwidth reservation capability on the LAN will still benefit by having the QoS delivered to the FEP.

Application Trials

Several current pre-general-availability programs involve multimedia, distance learning, digital library, large image projects and interactive video-on-demand. These programs are already helping customers realize and implement solutions by integrating their LAN environments with the LAN Server for MVS and OS/2 LAN Server products. Participants in this program include:

  • Rensselaer Polytechnic Institute (RPI), New York
  • California Polytechnic State University
  • University of Nebraska
  • Okazaki City, Japan
  • Marist College, New York



Distributed Data Access Opportunities on OS/390 with DFSMS(TM)

DFSMS/MVS for OS/390 makes MVS a full function File Server that allows you to optimize performance and efficiency in a distributed network while still capitalizing on the capacity, security, and integrity that is available on MVS.

  • DFSMS/MVS Network File System (DFSMS/MVS NFS)

    DFSMS/MVS NFS enables you to remotely access MVS/ESA mainframe data from workstations, personal computers or other systems on a TCP/IP network that run client software using the SUN NFS** Version 2 protocol.

    DFSMS/MVS NFS acts as an intermediary to read, write, create or delete OpenEdition MVS files and conventional data sets. The data sets or OpenEdition MVS files on the mainframe appear as local directories and files to the client system. This server brings the resources of an MVS mainframe (that is, storage management, high-performance DASD, security, and centralized data) to client platforms. Current wide-spread availability of software supporting SUN NFS protocols makes DFSMS/MVS NFS the perfect choice for accessing data on MVS.

  • DFSMS/MVS Distributed FileManager (DFSMS/MVS DFM)

    Distributed FileManager is the MVS file server that uses the Distributed Data Management (DDM) architecture to provide remote access to applications on diverse platforms to data on MVS. Distributed FileManager uses the Advanced Program-to-Program Communication (APPC) protocol for network conversations. DDM architecture offers a vocabulary and a set of rules for sharing and accessing data among like and unlike computer platforms. DDM includes a set of standardized file models (Keyed, Relative Record, Sequential, and Stream).

    Distributed FileManager enables applications to take advantage of data sharing, centralized data access, system-managed storage, high-performance storage access, and security on MVS.

  • DFSMS/MVS Character Data Representation Architecture (CDRA)

    CDRA is an architecture that describes the representation of character data and certain control information. It allows information created on one system, with any national language character set and internal character representation, to interchange data with another computer system whether or not the exchanging systems use the same representation; for example, ASCII and EBCDIC representations are described as well as single-byte, double-byte, multiple-byte, or unicode character national language variants.

    A set of callable CDRA APIs are now available in DFSMS on OS/390 that allows use of CDRA to simplify the implementation of National Language Support for MVS products and applications. By being able to accept and produce character data in the form used on other systems, MVS can become "internationalized" and allow businesses to use the language of choice.



OS/390 Release 2



Future UNIX Branding

At the time IBM announced MVS/ESA SP Version 5 Release 2.2, (Software Announcement 295-072, dated February 28, 1995), IBM issued a Statement of Direction (SOD) of its intent to support the single UNIX specification and to submit a future release of MVS to X/Open Company Limited to obtain the X/Open UNIX brand for MVS. OS/390 is the future MVS operating system release IBM will submit for branding as a UNIX system.

MVS/ESA SP Version 5 Release 2.2 contains well over 1100 of the approximate 1200 Single UNIX Specification functions. IBM is adding the remainder of the UNIX functions to OS/390 and will submit OS/390 to obtain the X/Open UNIX Brand. The additional UNIX functions being added to OS/390 are:

  • STREAMS -- a mechanism for implementing networking services and other character-based I/O.
  • XTI (X/Open Transport Interface) -- an API (Application Programming Interface) for network communications. An independent transport-service interface allows multiple users to communicate at the transport level.
  • Regular Expressions -- a defined set of functions to support Single UNIX Specification parsing of regular expressions.
  • Context Switching -- routines which permit manipulation of the execution environment while running. The routines are useful for implementing user-level context switching within a process between multiple threads of control.
  • Sockets -- adjustments to BSD 4.3 sockets support for Single UNIX Specification behaviors.
  • Internationalized Curses -- double byte support for the curses library which provides terminal independent full screen APIs used to perform screen updating, getting input from the screen and cursor movement.
The OS/390 elements that are being enhanced to support the new UNIX functions listed above are:
  • C-language runtime library functions are being added to Language Environment for MVS.
  • OpenEdition MVS services
  • TCP/IP for MVS is being updated to support the sockets enhancements.
Only products branded as conforming to the Single UNIX specification may use the X/Open UNIX Brand. X/Open branding consists of the Single UNIX Specification, the relevant software testing tools and the UNIX trademark licensing terms and conditions. Vendors seeking to license the UNIX trademark must submit their product(s) to the X/Open branding program. In licensing the X/Open UNIX trademark, the vendor warrants and represents that their branded product:
  • Conforms to the specification.
  • Will continue to conform to the specification.
  • If there is a non-conformance, it will be rectified within an agreed time.
Software Vendors
  • No longer need to develop code for a broad range of UNIX systems, but instead can develop to a standard based on the X/Open** UNIX Brand.
  • Significantly reduce expenses developing and maintaining UNIX code.
  • Will be able to provide broader functional richness to applications by converging all effort to a single UNIX standard implementation.
IBM Customers
  • Will have a wider array of robust applications from which to select because software vendors, now able to develop more efficiently to a single UNIX standard, will be able to produce more products.
  • Will significantly reduce the cost for porting their UNIX applications to other platforms that carry the UNIX brand.
  • Will simplify their staff's multi-platform UNIX skills because of API standards that are based on the UNIX standard.



OS/390 ISPF Enhancements

The ISPF element in OS/390 continues to provide new functions that our customers need for building easier-to-use applications and more flexible access to system resources. These new functions include:

  • Client/Server:
    • APPC Support for Windows: ISPF C/S now supports APPC connections to Windows workstations.
    • Enhanced Graphic Support: ISPF supports more graphics and GUI controls to make your application even easier to use and more popular with your users.
Cost of Computing
  • Settable Site-Wide Defaults: ISPF reduces customers' systems management efforts by enabling the system programmer to set installation-specific options that each user formerly had to set for himself. The system default for CUA(TM) settings, command line location, and other items can now be set by the system programmer.

  • Expanded Codepage Support: ISPF makes it easier for more international users to use ISPF/MVS applications by adding support for new codepages for several European and Asian languages.



Year2000

IBM is strongly committed to provide the appropriate information, code, and guidance to help installations successfully transition to the year 2000 and beyond. OS/390 includes support for the transition from 1999 to 2000. The changes being incorporated address ambiguous uses of two-digit year fields (where 00 could mean 1900 or 2000). The support will address internal dates, dates in logs, and dates passed externally. Uses of dates that are unambiguous (for human viewing only; that is, date stamps on screens and printed reports) may continue to contain two-digit years.

OS/390 is well positioned for installations to begin making their applications Year2000 ready. IBM recommends that installations form a project well before 2000 to analyze, enhance, and test applications. IBM consulting services are available for those that wish to:

  1. Receive assistance in assessment and/or planning now for the Year2000.
  2. Receive assistance in planning for and/or management of release-to-release product migrations.
  3. Strategically transform their entire application portfolio while solving their Year2000 issues.
A comprehensive methodology is included that is complemented with technology tools for both planning and implementing Year2000 solutions. Contact your IBM or ISSC(R) representative regarding availability in your country.

The PC Server 500 System/390 offers a unique opportunity for Year2000 application development and testing. It is a flexible and cost effective platform for developing and testing Year2000 changes without affecting the production environment or other test environments.



PRODUCT POSITIONING



OS/390 Value

OS/390 extends the capacity and robustness of the MVS system, offering value in the following areas:

  • Application enablement
    • Continued and enhanced support for traditional S/390 APIs
    • Improved, consistent development base for customers and software vendor applications
    • Faster application deployment with visual and object oriented programming tools
    • Multiprotocol communications support for improved application choice
  • Client/Server
    • Easier client access
    • Server interoperability
  • Open, multivendor
    • Integrated open interfaces and LAN services
    • UNIX branding
  • Classic S/390 strengths
    • Better tested for higher reliability
    • Improved security and availability
    • Easier to manage
  • Total cost of computing -- Simplified planning, installation and maintenance



SystemView for MVS

SystemView for MVS is IBM's solution for MVS-based systems management. It offers a comprehensive array of systems management functions and associated support to help establishments more effectively manage their MVS system and network resources. SystemView for MVS provides configuration, change, performance, problem, security, and operations (system, network, console, data and print) management, all from a single user interface. For more information on the functions included in SystemView for MVS, see Software Announcement 295-417, dated October 3, 1995.



STATEMENTS OF GENERAL DIRECTION



Future Direction Of OS/390 As A Distributed Server Platform

IBM intends to deliver a component in OS/390 that for certain environments, provides very significant simplification of the MVS and S/390 skills needed to own and operate the system. This component contains automation and tools that allow the tasks previously performed by operators and system programmers to be handled by a system administrator. An example of the target environment would be a UNIX application development group using this as the platform for porting and testing their UNIX applications on MVS. Another environment that we are targeting is using OS/390 with this component as the base platform from which to build a distributed server solution where the end using department has no MVS skills.



DFSMS/MVS

IBM intends to develop a separate feature of DFSMS/MVS which will support certain additional MVS capabilities and to provide access to enterprise data in an open environment. IBM intends to provide the following:

  • NFS client capability, which will enable MVS to access data on different platforms that support certain SUN NFS protocols in the TCP/IP network environment.
  • Capability for certain MVS applications written to BSAM, QSAM, and VSAM ESDS access methods to allow access to files associated with OpenEdition MVS data on remote systems which support SUN NFS protocols, including other MVS systems.



Future MVS Packaging Direction

IBM intends (over the next year) to extend the OS/390 packaging and integrated testing concepts into more of the MVS product set. This means that product functions that are today shipped as individual and separately installed offerings may be grouped together in offerings where the collection of functions have logical affinity to each other. These groups would include SystemView, Database Management, and Transaction Processing as examples. The intent is to make these groups easier to install. Offerings that are made up of OS/390 and one or more of these groups will be tested as an integrated package.



SOMobjects

With the proliferation of client/server computing, it has become more important for applications to be able to communicate and share data across systems. With the distributed functions of the System Object Model (SOM), the power of SOM will be extended so that applications can access objects across systems (that is, in other processes) and even across systems from other vendors. The objective is to provide distributed object capability between MVS and other platforms, thereby offering a more complete end-to-end capability (Software Announcement 295-401, dated September 26, 1995). Currently, SOMobjects for MVS complies with the Common Object Request Broker Architecture (CORBA) 1.1 specification, published by the Object Management Group (OMG) and X/Open. In keeping with IBM's commitment to industry standards, IBM intends to comply with the CORBA 2.0 Interoperability specification in subsequent releases of the base operating system and will incorporate OMG's Object Services standards as appropriate.

The above statements represent IBM's current intended plans. IBM will continue to monitor business conditions and requirements and may make changes to these plans as required.



TECHNICAL INFORMATION

The specified operating environment will be described when pricing and ordering information is made available.

+     Trademark of Microsoft Corporation