DFSMS/MVS VERSION 1 RELEASE 2 AND 3 NETWORK FILE SYSTEM IMPROVES PRODUCTIVITY AND USABILITY

DFSMS/MVS Version 1 Release 2 and 3 Network File System Improves Productivity and Usability

September 10, 1996
Announcement Number: 296-323

Document's Table of Contents:

At a Glance
DESCRIPTION
TECHNICAL INFORMATION
ORDERING INFORMATION
TERMS AND CONDITIONS
CHARGES

At a Glance

DFSMS/MVS Version 1 Release 2 and 3 for client/server enterprises includes:

DFSMS/MVS Version 1 Release 2 and 3 Network File System (DFSMS/MVS NFS) enhancements:
- A new MVS NFS client that allows access to other NFS server platforms
- NFS listing of attributes and deletion of migrated data sets that may now occur without DFSMShsm(TM) recall
DFSMS/MVS access method support to allow conventional MVS programs access to OpenEdition MVS and remote NFS server UNIX data

Overview

DFSMS/MVS(R) Version 1 Release 3 provides a total storage management solution for disk, optical, and tape storage. DFSMS/MVS allows you to incorporate the values and priorities of your business into the automation of storage management. DFSMS/MVS Network File System (DFSMS/MVS NFS) also enables your MVS system to become a major participant in your distributed enterprise with new functionality of an NFS client.

New in DFSMS/MVS Version 1 Release 2 and 3

IBM continues to improve DFSMS/MVS, the industry-leading storage management solution, with the following enhancements.

IBM's DFSMS/MVS NFS feature has added significant capabilities which will allow MVS/ESA(TM) to access data on other NFS server machines (MVS/ESA, RS/6000(TM), SUN, HP, PCs using OS/2(R)) on a TCP/IP network.
DFSMS/MVS NFS is now provided in two functional levels. Today we are introducing DFSMS/MVS NFS Version 1 Release 3. The previously available level is referred to as DFSMS/MVS Version 1 Release 2 NFS. Both will remain available to satisfy customer needs. DFSMS/MVS Version 1 Release 3 NFS is intended for use by customers with MVS/SP(TM) 5.2.2. DFSMS/MVS Version 1 Release 2 NFS is for use by customers using MVS/SP(TM) 4.3, 5.1, or 5.2. Refer to the table in the Software Requirements section for relationships between DFSMS/MVS, MVS/SP, and DFSMS/MVS release levels of the NFS features.
DFSMS/MVS access method support allows conventional MVS programs access to OpenEdition(R) MVS and remote NFS server UNIX(1) data.

Visit our DFSMS/MVS NFS Home Page on the World Wide Web --

http://www.storage.ibm.com/ storage/software/sms/smshome.htm

Or go directly to the DFSMS NFS home page --

http://www.storage.ibm.com/ storage/software/nfs/nfshome.htm

Planned Availability Date

September 13, 1996

DESCRIPTION

DFSMS/MVS Version 1 Release 2 and 3 has been enhanced to include the following.

DFSMS/MVS Network File System Feature (NFS) Enhancements

IBM's DFSMS/MVS NFS feature adds significant capabilities which will allow MVS/ESA on a TCP/IP network to access data on other NFS server machines (MVS/SP, RS/6000, SUN, HP, PCs using OS/2, and so on).

MVS Network File System Client

A new NFS client is provided by the DFSMS/MVS NFS feature for the MVS platform. The NFS protocols have become one of the most pervasive methods for interoperability between different types of operating systems. The NFS protocol is designed to allow transparent access between a client system and the server system with the files contained on the server system appearing as if they were available locally on the client system. The NFS client program on the client system will map local file system calls into network calls and send a request for data or control information to the NFS server. In this way, NFS client and server will deliver remote data to an application without special interfaces in the application.

Evolving from the UNIX environment, many systems support both NFS server capabilities and NFS client capabilities. For some time, the DFSMS/MVS product has had NFS server support as a feature. Now we are announcing the availability of NFS client support as included in the DFSMS/MVS NFS feature. The DFSMS/MVS NFS client program supports the SUN NFS Version 2 protocols. It utilizes RPC requests to communicate with remote NFS servers over a TCP/IP network. This enables one MVS system to exchange data files with another using the NFS client/server technology. This also allows an MVS/ESA system to actively share data with another MVS/ESA system. Each MVS system with the DFSMS/MVS Version 1 Release 3 NFS client can read from or write to any other MVS system which has the DFSMS/MVS NFS feature installed. DFSMS/MVS NFS provides the capability of OpenEdition MVS applications to read or write MVS conventional data sets and OpenEdition Hierarchical File System (HFS) files on another MVS system.

Some of the functions supported by the DFSMS/MVS NFS client include:

Create/Delete files
Read/Write files
List directories
NFSSTAT and SHOWMOUNT commands
Support for UNIX-style credentials authentication, such as UID, GID, and permission bits
Additional Security Authorization Facility (SAF) protection to a remote DFSMS/MVS NFS server with the MVSLOGIN command
Support for simple data conversion of single-byte character sets

The DFSMS/MVS NFS client support operates as a physical file system under UNIX Services (OpenEdition). This allows applications which use the OpenEdition POSIX-compliant system interfaces to utilize the NFS client functions with few changes to those applications. By extension, this also enables conventional MVS Basic Sequential Access Method (BSAM), Queued Sequential Access Method (QSAM), Virtual Storage Access Method (VSAM) ESDS applications, in addition to OpenEdition MVS applications and users, and transparent access to data on any remote NFS server platform supporting SUN Network File System (NFS) Version 2 protocols.

Note: The DFSMS/MVS NFS client function works on both DFSMS/MVS Version 1 Release 2 and 1.3.

Obtaining Attributes of Migrated Data Sets without Recall

DFSMS/MVS Version 1 Release 3 allows data set attribute accessibility for Data Facility Storage Management Subsystem (DFSMS) managed data sets even if the data set is migrated by DFSMShsm. Supported data set types are DFSMS-managed PS, VSAM ESDS, VSAM KSDS, VSAM RRDS, PDS, and PDSE.

With the above function (the DFSMS/MVS Version 1 Release 3 managed data sets that have been previously accessed by the DFSMS/MVS Version 1 Release 3 NFS server prior to volume migration), the DFSMS/MVS Version 1 Release 3 NFS server is able to obtain the attributes of migrated data sets without physically recalling them. Depending on the DFSMS policies and data set size, this could result in significantly improved response time for DFSMS/MVS NFS lookup and getattr requests.

Access Method Support for OpenEdition MVS Files

DFSMS/MVS Version 1 Release 3 Access Methods offer a new opportunity to access enterprise data in an open system environment. Many applications written to use the BSAM/QSAM access methods, and some applications written to use the VSAM ESDS access, now have transparent access to files associated with OpenEdition MVS. With this support, the MVS conventional application, using the normal record or block interfaces provided by the MVS access methods, can access files residing in remote NFS server platforms. This support will map between this record/block interface and the byte-oriented structure of the OpenEdition or remote files. The following files can be accessed by specifying the PATH=pathname parameter on the BSAM, QSAM, or VSAM JCL DD statement, or SVC 99.

Local OpenEdition Files
OpenEdition regular files are managed by the DFSMSdfp(TM) Hierarchical File System (HFS). Each HFS file is an identified unit of text or binary data and is byte-oriented (versus record-oriented). The HFS file system supports the file name and pathname up to 255 characters in length. Within the HFS file name, special characters and lower case characters may be embedded.
Remote Files
A remote file is any regular file residing in a remote NFS server platform which supports the SUN NFS Version 2 protocols. With this function, MVS applications written to use BSAM, QSAM, and VSAM ESDS data sets can access remote files via the DFSMS/MVS NFS client and the network environment just as if the remote files were local.
Local FIFO Special Files
A FIFO (First-In-First-Out) special file, or named pipe, is an OpenEdition MVS special file. A FIFO special file is defined in a DD statement with both PATH= and DSNTYPE=PIPE. A FIFO file provides data connections between programs. A FIFO file typically sends data from one program (or process) to another; both ends of a FIFO file can be used in a single program task. All data in a FIFO file vanishes when the last program using it closes it.
Local Character Special Files
Character special file is an OpenEdition MVS special file that defines a null or a dummy file (for example, /dev/null).

Note: This capability is only available on DFSMS/MVS Version 1 Release 3. Refer to the informational APAR II09184 for more details.

OPEN SYSTEMS

Open Blueprint(TM): The Open Distributed Computing Structure is IBM's solution for open, client/server, and distributed computing across systems platforms. The structure, formally known as Open Blueprint, includes industry-accepted standards, protocols, interfaces, and IBM extensions to provide the flexibility to accommodate new technologies as they emerge in today's dynamic open computing environment.

The Open Blueprint is supported by this announcement.

PRODUCT POSITIONING

DFSMS/MVS NFS helps to achieve a UNIX-like system with the capacity, storage management, and reliability of an MVS system. With both NFS client and server capability, DFSMS/MVS NFS enables your MVS system to be a more enhanced participant in your distributed environment.

DFSMS/MVS NFS will continue to be a separately orderable feature.

TECHNICAL INFORMATION

Specified Operating Environment

Hardware Requirements: The DFSMS/MVS NFS feature operates on the same hardware as DFSMS/MVS Version 1 Release 3.

The DFSMS/MVS NFS feature requires a minimum of 9.5 megabytes of direct access storage.

Software Requirements

DFSMS/MVS Network File System

                        | DFSMS/MVS 1.2   |  DFSMS/MVS 1.3  |
                        |-----------------+-----------------|
                        | MVS/SP          | MVS/SP          |
DFSMS/MVS 1.2 NFS       | 4.3, 5.1, 5.2   | 4.3, 5.1, 5.2   |
------------------------+-----------------+-----------------|
DFSMS/MVS 1.3 NFS       | MVS/SP 5.2.2    | MVS/SP 5.2.2    |

Network File System feature of DFSMS/MVS
- Server (HDZ11SM)
  - Software Requirements to Install and Run HDZ11SM:

Product Level

SMP/E Version 1 Release 8.1 (5668-949) or later. This is required for installation only.

DFSMS/MVS DFSMS/MVS Version 1 Release 2 or subsequent releases.

Note: DFSMS/MVS Version 1 Release 3 allows data set attribute accessibility for SMS-managed data sets, without having to recall the data set if the data set is migrated.

MVS/ESA SP 5.2.2 (5655-068 and 069), OpenEdition MVS Sockets (FMID HOT1130), and OpenEdition MVS System Services (FMID HOM1130).

TCP/IP Version 3 Release 1 for MVS (5655-HAL)

Language Version 1 Release 5 (5688-198) or Environment later; or IBM C/C++ Language Support feature of MVS/ESA SP 5.2.2.

RACF(TM) MVS Version 2.1 (5695-039) or subsequent releases or equivalent. This is required for execution only.

Note: You can also choose not to use RACF; see "Protecting Your Data" in Chapter 2 of "Planning for Installation" in the DFSMS/MVS Version 1 Release 3 Network File System Customization and Operation Manual (SC26-7029).

Client (HDZ11SE)
- Software Requirements to Install and Run HDZ11SE:

Product Level

SMP/E Version 1 Release 8.1 (5668-949) or later. This is required for installation only.

DFSMS/MVS Version 1 Release 2 (5695-DF1) with PTF UW90206 or subsequent releases.

Note: DFSMS/MVS Version 1 Release 3 allows BSAM, QSAM, and VSAM ESDS applications access to files stored on remote NFS servers through the DFSMS/MVS NFS client. Refer to Info APAR II09184

MVS/ESA SP 5.2.2, OpenEdition MVS Sockets (FMID HOT1130), and OpenEdition MVS System Services (FMID HOM1130).

TCP/IP Version 3 Release 1 for MVS (5655-HAL).

Language Version 1 Release 5 (5688-198) or Environment later; or IBM C/C++ Language Support feature of MVS/ESA SP 5.2.2.

RACF MVS Version 2.1 (5695-039) with PTF UW90162 or subsequent releases or equivalent. This is required for execution only.

Access Method Support for OpenEdition MVS Files
- DFSMS/MVS Version 1 Release 3 Small Programming Enhancements (SPE): APARs OW17101 and OW20771.
- MVS/ESA SP Version 5 Release 2.2 is required for Access Method Support for OpenEdition/MVS Files function.
- Additionally, DFSMS/MVS Version 1 Release 3 NFS client and all its required software are required for Access Method Support for OpenEdition/MVS Files function accessing to remote NFS server platform.

Limitations

NFS Feature of DFSMS/MVS
- MVS NFS Client and Server
  Both the MVS NFS client and server only support SUN NFS Version 2 protocols.
- Obtaining Attributes of Migrated Data Sets Without Recall
  This enhancement in the DFSMS/MVS NFS server only supports DFSMS-managed PS, VSAM ESDS, VSAM KSDS, VSAM RRDS data sets, PDS, and PDSE at the data set level only (not at the member level). This enhancement supports DFSMShsm-migrated datasets.
- This new DFSMS/MVS NFS feature will only execute on MVS/SP 5.2.2. For those customers who are still on MVS/SP 4.3, 5.1, or 5.2, the DFSMS/MVS Version 1 Release 2 NFS feature will have to be ordered/used. For further information on this release, which became available September 1994, refer to Software Announcement 294-200, dated April 6, 1994. Feature media numbers for the DFSMS/MVS Version 1 Release 2 NFS feature are: 5323 (9/6250 BPI tape), 5324 (3480 cartridge tape), and 5338 (4-mm data cartridge).
- Customers on MVS/SP 5.2.2 or later system releases should use the feature media numbers specified in this announcement to obtain this new DFSMS/MVS NFS release.
Access Method Support for OpenEdition MVS Files and Remote Files
This function has the following restrictions:
- BSAM/QSAM interfaces and functions that are not supported when accessing OpenEdition MVS files or remote files
  - OPEN for update processing
  - EXCP processing
  - RECFM=V(B)S (spanned record format)
  - NOTE/POINT, BSP, and CLOSE TYPE=T for FIFO or character special files or if PATHOPTS=OAPPEND is specified
- VSAM ESDS interfaces and functions that are not supported when accessing OpenEdition MVS files or remote files:
  - STRNO greater than 1
  - chained RPLs
  - Shared resources
  - Update and backward processing
  - Direct processing or POINT for FIFO and character special files
  - ERASE
  - VERIFY
  - SHOWCAT
  - JRNAD, UPAD, and EXCEPTION exits
- Variable length binary records do not retain record boundaries during conversion to a byte stream. During reading, each record, except the last, is assumed to be the maximum.

User-Group Requirements

DFSMS/MVS NFS Feature
- MVS NFS Client
  PASR REQ00012483 -- MVS NFS client is required to allow MVS access to data residing on remote NFS server platforms.
Access Method Support for OpenEdition MVS Files
- A function to permit access to HFS files via SAM access method is required. See the OpenEdition MVS: A First Look GUIDE document written by the GUIDE MVS group, dated 1993.

ORDERING INFORMATION

Current Licensees

For customers who are still on MVS/SP 4.3, 5.1, or 5.2, the DFSMS/MVS Version 1 Release 2 NFS feature is still available. Refer to Software Announcement 294-200, dated April 6, 1994, for ordering information.

Prices are unaffected by this announcement, therefore the billing feature numbers are the same. If you are ordering DFSMS/MVS Version 1 Release 2, refer to Software Announcement 294-200 for media feature numbers. Current licensees of DFSMS/MVS Version 1 Release 2 will be sent a program reorder form which may be returned directly to IBM Software Manufacturing Solutions (SMS). The mailing of these reorder forms is scheduled to be completed by day of announcement (September 10, 1996). Reorder forms returned to SMS will be processed within 10 work days of receipt.

New Licensees

Orders for new licenses will be accepted now. Shipment will begin on the planned availability date. New users of DFSMS/MVS Version 1 Release 3 should specify:

Type Model

5695 DF1

Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. For a graduated one-time charge or graduated monthly license charge, specify one of the following feature numbers as applicable and corresponding to the group that contains the designated machine.

Also, specify the feature number of the desired distribution medium.

Basic Basic Graduated Graduated Monthly One-Time License Charge License Charge Group Feature Number Feature Number Offering

18 0940 1008 NFS Feature 20 0941 1009 NFS Feature 25 0942 1010 NFS Feature 28 0943 1011 NFS Feature 29 0944 1012 NFS Feature 30 0945 1013 NFS Feature 31 0946 1014 NFS Feature 32 0947 1015 NFS Feature 35 0948 1016 NFS Feature 38 0949 1017 NFS Feature 40 0950 1018 NFS Feature 50 0951 1019 NFS Feature 60 0952 1020 NFS Feature 70 0953 1021 NFS Feature 80 0954 1022 NFS Feature

PR/SM(TM) or MOSP License: In ordering a Multiple Operating System license for a graduated one-time charge or graduated monthly license charge, specify the following feature numbers corresponding to the group that contains the designated machine.

MOSP Basic MOSP Basic Graduated Graduated Monthly One-Time License Charge License Charge Group Feature Number Feature Number Offering

18 0974 1042 NFS Feature 20 0975 1043 NFS Feature 25 0976 1044 NFS Feature 28 0977 1045 NFS Feature 29 0978 1046 NFS Feature 30 0979 1047 NFS Feature 31 0980 1048 NFS Feature 32 0981 1049 NFS Feature 35 0982 1050 NFS Feature 38 0983 1051 NFS Feature 40 0984 1052 NFS Feature 50 0985 1053 NFS Feature 60 0986 1054 NFS Feature 70 0987 1055 NFS Feature 80 0988 1056 NFS Feature

Note: The group can be determined by referring to the Exhibit for IBM System/370(TM) and System/390(R) Machines (Z125-3901) and the Exhibit for Non-IBM Machines (Z125-3902) that are associated with the IBM Customer Agreement (Z125-4575).

Entry Support License (ESL): To order an ESL license, specify the program number, feature number 9001 for asset registration, and the applicable ESL one-time charge feature number. Also specify the feature number of the desired distribution medium.

ESL One-Time Charge Program Number/Description Feature Number

5695-DF1/NFS Feature 2106

Note: ESL machines can be determined by referring to the IBM Entry End User/390 Attachment (Z125-4379).

Parallel Sysplex(TM) License Charge (PSLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the PSLC Base feature and applicable PSLC Level A and PSLC Level B features and quantity.

In a Parallel Sysplex, if there is more than one program copy, the charge for all copies should be associated with one copy by specifying the applicable PSLC feature numbers and quantity represented by the sum of the Service Units in Millions (MSUs) in your Parallel Sysplex. For all other program copies, specify the PSLC No Charge (N/C) Identifier feature.

Also, specify the feature number of the desired distribution medium.

PSLC PSLC Basic License Machine(s) Feature MLC Feature MSU Capacity Number Description

3 0143 PSLC Base, 3 MSUs

4 -- 45 0144 PSLC Level A, 1 MSU 0145 PSLC Level A, 42 MSUs

46 or more 0146 PSLC Level B, 1 MSU 0147 PSLC Level B, 10 MSUs 0148 PSLC Level B, 50 MSUs

NA 0149 PSLC N/C ID

Indexed Monthly License Charge (IMLC) Basic License: To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the IMLC Base 80 MSU feature and the applicable additional IMLC MSU feature(s) and quantity corresponding to the MSU rating of the designated machine.

Also, specify the feature number of the desired distribution medium.

IMLC IMLC Basic License Feature MLC Feature Number Description

1425 IMLC Base 80 MSUs 1426 IMLC 1 MSU 1427 IMLC 10 MSUs 1428 IMLC 50 MSUs

Basic Machine-Readable Material: To order, select the feature number of the desired distribution medium.

To order the new DFSMS/MVS Version 1 Release 3 NFS feature for the basic license, specify the program number (5695-DF1) and the feature number of the desired distribution medium.

Feature Environment Number Distribution Medium FMID

DFSMS/MVS 1.3 5841 9/6250 BPI tape HDZ11SM, NFS Feature HDZ11SE DFSMS/MVS 1.3 5842 3480 cartridge tape HDZ11SM, NFS Feature HDZ11SE DFSMS/MVS 1.3 5341 4-mm data cartridge HDZ11SM, NFS Feature HDZ11SE

Customization Options: Select the appropriate feature number(s) to customize your order to specify the delivery options desired. These features can be specified on the initial or MES orders.

Example: If publications are not desired for the initial order, and for future updates, specify feature numbers 3470 to ship media only, and 3480 to ship media updates only. In the future if publication updates were required, order an MES to remove feature number 3480, and the publications will ship with the next release for the program.

Feature Description Number

Initial Shipments

Serial Number Only (suppresses shipment of media and documentation) 3444

Ship Media Only (suppresses initial shipment of documentation) 3470

Ship Documentation Only (suppresses initial shipment of media) 3471

Update Shipments

Ship Media Updates Only (suppresses update shipment of documentation) 3480

Ship Documentation Only (suppresses update shipment of media) 3481

Suppress Updates (suppresses update shipment of media and documentation) 3482

Expedite Shipments

Local IBM Office Expedite (for IBM use only) 3445

Customer Expedite Process Charge ($30 charge for each product) 3446

Expedite shipments will be processed to receive 72-hour delivery from the time SMS receives the order. SMS will then ship the order via overnight air transportation.

DSLO License: To order a DSLO license, specify the program number, feature number 9901 for asset registration, and the feature number for a graduated one-time charge or graduated monthly charge that corresponds to the group containing the designated machine.

DSLO DSLO Graduated Graduated Monthly One-Time License Charge License Charge Group Feature Number Feature Number Offering

18 0957 1025 NFS Feature 20 0958 1026 NFS Feature 25 0959 1027 NFS Feature 28 0960 1028 NFS Feature 29 0961 1029 NFS Feature 30 0962 1030 NFS Feature 31 0963 1031 NFS Feature 32 0964 1032 NFS Feature 35 0965 1033 NFS Feature 38 0966 1034 NFS Feature 40 0967 1035 NFS Feature 50 0968 1036 NFS Feature 60 0969 1037 NFS Feature 70 0970 1038 NFS Feature 80 0971 1039 NFS Feature

PR/SM or MOSP License: In ordering a Multiple Operating System license for a graduated one-time charge or graduated monthly license charge, specify the following feature numbers corresponding to the group that contains the designated machine.

MOSP DSLO MOSP DSLO Graduated Graduated Monthly One-Time License Charge License Charge Group Feature Number Feature Number Offering

18 0991 1059 NFS Feature 20 0992 1060 NFS Feature 25 0993 1061 NFS Feature 28 0994 1062 NFS Feature 29 0995 1063 NFS Feature 30 0996 1064 NFS Feature 31 0997 1065 NFS Feature 32 0998 1066 NFS Feature 35 0999 1067 NFS Feature 38 1000 1068 NFS Feature 40 1001 1069 NFS Feature 50 1002 1070 NFS Feature 60 1003 1071 NFS Feature 70 1004 1072 NFS Feature 80 1005 1073 NFS Feature

Ordering a DSLO feature will result in IBM maintaining a record of this customer location as a DSLO user only. All material for the DSLO license must be ordered by the basic licensee. If a user selects DSLO, no other feature numbers are valid for this order and no program materials or updates will be shipped.

Unlicensed Documentation: A memo, program directory, and one copy of the following publications are supplied automatically with the basic machine-readable material.

Order Title Number

DFSMS/MVS Version 1 Release 3 SC26-7028 Network File System User's Guide

DFSMS/MVS Version 1 Release 3 SC26-7029 Network File System Customization & Operation

DFSMS/MVS Version 1 Release2 SC26-7019 Network File System Performance Tuning Guide

Subsequent updates (technical newsletters or revisions between releases) to the publications shipped with the product will be distributed to the user of record for as long as a license for this software remains in effect. A separate publication order or subscription is not needed.

TERMS AND CONDITIONS

The terms for DFSMS/MVS Version 1 Release 2, as previously announced in Software Announcement 294-200, dated April 1994, licensed under the IBM Customer Agreement, are unaffected by this announcement.

CHARGES

Prices are unaffected by this announcement.

One-Time Charge: Customers who pay a one-time charge for a licensed program receive enhancements and future releases, if any, at no additional charge. Significant new function may be offered as an optional feature and charged for separately. If a replacement program is announced and the customer elects to license the replacement program for a one-time charge and replace the prior program, an upgrade charge may apply.

Variable Charges: The applicable graduated one-time charge or graduated monthly license charge will be based on the group of the designated machine on which the licensed program is licensed for use. If the program is designated to a processor in a group for which no charge is listed above, the charge of the next higher group listed applies.

For upgrades of one-time charge licenses to a machine in a higher group, the upgrade charge will be the difference in the then current charges between the two groups.

For downgrades of one-time charge licenses to a machine in a lower group, there will be no adjustment or refund of one-time charges paid.

For upgrades or downgrades of monthly license charge licenses, the monthly license charge applicable to the higher or lower group will apply.

Entry Support License One-Time Charge: One-time charge authorizes use only on IBM Entry End User/390 Machines.

(R) Registered trademark of International Business Machines Corporation in the United States or other countries or both. (TM) Trademark of International Business Machines Corporation in the United States or other countries or both. (1) Registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.

Other trademarks and registered trademarks are the properties of their respective owners.