Preview: New Release With Major Enhancements -- IBM DFSMS/MVS Version 1 Release 5

Software Announcement
June 2, 1998
Announcement Letter Number: 298-176


Table of Contents:



At a Glance

DFSMS Version 1 Release 5 will allow for sysplex exploitation, improved performance, useability, availability, and interoperability with the following enhancements:

EXTRA! EXTRA! . . .

Subscribe to IBM iSource, your electronic source for customized IBM information! Go to our web site at http://www.ibm.com/isource or send an e-mail to info@isource.ibm.com with the word SUBSCRIBE in the body.



Overview

IBM intends to introduce a new release of DFSMS/MVS (R).

DFSMS/MVS Version 1 Release 5 will provide new functions and significant improvements in the following areas:

DFSMS/MVS Version 1 Release 5 will be: OS/390 UNIX System Services is only available on OS/390.

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



Intended Customers

Those who:



Key Prerequisites

The following programs or equivalents:

------------------------------

This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: http://www.ibm.com



DESCRIPTION

DFSMS/MVS Version 1 Release 5 will provide HFS users with the following significant improvements. First, much of the overhead and redundancies in earlier versions of HFS has been removed and you should see improvements in HFS performance. Second, HFS will support multi-volume datasets, thus eliminating growth restrictions on applications like Lotus (R) Domino (TM). Third, HFS will provide an interface which will allow you to perform additional functions such as retrieving statistics and dynamically extending HFS data sets. Finally, HFS will preserve the integrity of mounts in a shared environment.

DFSMS/MVS Version 1 Release 5 will improve the performance of shared catalogs in a parallel sysplex (R) environment. Users of DFSMShsm will be able to take advantage of the high availability application support inherent in sysplex support by using secondary host promotion. If a host or address space running DFSMShsm primary function fails, any secondary host can be promoted to take over these functions using standard XCF/sysplex function. Also, if a host or address space running Secondary Space Management (SSM) fails, another host in the sysplex can be promoted to take over this responsibility.

DFSMS/MVS Version 1 Release 5 will provide the ability to maintain multiple HSMplexes within a single GRSplex. Each HSMsubplex will have its own set of control data sets and manage its own set of user catalogs. This will ease requirements for merging DFSMShsm Control Data Sets as you merge existing complexes into sysplexes. Also, this allows for easier management of emerging Geoplexes. As you grow your complexes and merge them into sysplexes, IBM has concluded that the current maximum size of the DFSMShsm control datasets is an inhibitor to growth and sysplex implementation. To that end, in DFSMS/MVS Version 1 Release 5, the DFSMShsm control datasets will take full advantage of VSAM extended addressing introduced in DFSMS/MVS 1.3 -- growth in your installation will no longer be curtailed by the size of DFSMShsm's control datasets.

DFSMS/MVS OAM will exploit sysplex architecture and DB2 data sharing to enhance availability and allow instances of OAM to have full access to OAM objects. This removes the old limitation that only the system that owns the object can access it. OAM will also remove the 100 storage group limitation in a configuration. Users can now specify their own high level qualifier for the object groups and their associated DB2 tables.

DFSMS/MVS OAM will also exploit sysplex architecture to enhance availability and allow instances of OAM that belong to an XCF group, and are connected to DB2 subsystems, using DB2 data sharing to have full access to OAM objects, thereby removing the old limitation that only the system that owns the object can access it. OAM will now support more than 100 storage groups in a configuration. Users will also be able to specify their own high level qualifier for the object storage groups and their associated DB2 tables.

DFSMS/MVS Version 1 Release 5 will provide a series of new functions to DFSMSrmm. First, an API to allow for READ/WRITE access to the DFSMSrmm Control Data Set will be available. This API will allow you to write programs to query and update fields in the CDS. In addition, this API could be the basis of interaction between DFSMSrmm and other vendor programs for tape dataset stacking and production scheduling and control. This API will be available on DFSMS/MVS 1.3 and 1.4 as APAR OW30369. Separate retention and vaulting policies will be available for DFSMSrmm to allow for more flexibility in defining policies that will make conversion from competitive products easier. In addition, DFSMSrmm will also provide special handling instructions through a DD statement to better communicate with operations personnel, and to produce printed output such as printing labels, assigning volumes to loan or storage locations, or to identify future processing or removal from site. DFSMSrmm will extend support for sharing a single control data set across systems that do not share catalogs by tracking catalog status and enabling some functions to run on each system.

Naviquest allows you to do regression testing on your ACS routines, change SMS constructs in batch, and invoke batch reports through ISMF. It has been further enhanced to allow define alter, and display of Data Class, Storage Class, Base configuration and aggregate group. Thus, storage administrator productivity is increased.

To make a shared master catalog environment easier to use, DFSMS/MVS will provide a methodology to allow an alias in a shared master catalog to be interpreted differently on each system in the sysplex based on the parameter specifications supplied on each system.

For growth enablement, DFSMS/MVS will allow subsystems such as CICS and IMS to exceed the past limitation of 8,191 open datasets.

To enhance the useability of the DFSMS/MVS product line, functions like extended addressing, partial release, candidate volume space amount, and system managed buffering were made available to users of extended format VSAM key sequenced datasets in previous releases of DFSMS. DFSMS/MVS Version 1 Release 5 plans to provide support of extended format to VSAM ESDS, RRDS, VRRDS, and LDS along with the aforementioned extended format capabilities.

In the realm of interoperability, ANSI Version 4 tape label support will be available. This will allow for data interchange between MVS and non-S/390 (R) systems.

Basic Tape Library Support (BTLS) will continue to be supported in this release.

For enhancements to OS/390 Network File System (OS/390 NFS), formerly named DFSMS/MVS NFS, refer to Software Announcement 298-049 dated February 24, 1998.



Year 2000

This product is Year 2000 ready. When used in accordance with its associated documentation, it is capable of correctly processing, providing, and/or receiving date data within and between the 20th and 21st centuries, provided all other products (for example, software, hardware, and firmware) used with the product properly exchange accurate date data with it.

Trademarks

      DFSMShsm, DFSMSrmm, DFSMSdfp, IMS, DFSMS, OS/390, MVS/ESA, MVS,
      and SP are trademarks of International Business Machines
      Corporation in the United States or other countries or both.
      DFSMS/MVS, CICS, DB2, Parallel Sysplex, S/390, and AIX are
      registered trademarks of International Business Machines
      Corporation in the United States or other countries or both.
      UNIX is a registered trademark in the United States and other
      countries exclusively through X/Open Company Limited.
      Domino is a trademark of Lotus Development Corporation.
      Lotus is a registered trademark of Lotus Development
      Corporation.
      Other company, product, and service names may be trademarks or
      service marks of others.