Software Announcement 299-090
April 13, 1999

IBM Classic Connect V2.1.1 Provides SQL Access to IMS and VSAM Data

 ENUS299-090.PDF (69KB)

(Corrected on May 3, 1999)

Changed Version-to-Version Upgrade Credits Apply section in Terms and Conditions.

At a Glance

IBM Classic Connect V2.1.1 provides:

  • SQL read access to IMS/MVS and VSAM/MVS
  • Data join/access via DataJoiner across DB2 Universal Database Family, IMS, VSAM, Oracle, Microsoft SQL Server, Sybase and other relational and non-relational data sources
  • SYSINDEXES, SYSKEYS, and RUNSTATS — available for DataJoiner query optimizer
  • Enterprise Server option for managing large pools of concurrent users
  • IMS DRA access path for multiuser support, in addition to single user DBB and BMP access
  • Dynamic configuration support allowing 7 x 24 operations
  • Improved performance, scalability, reliability, and security

For ordering, contact:

Your IBM representative, an IBM Business Partner, or IBM Americas Call Centers at 800-IBM-CALL (Reference: LE001).

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

Classic Connect V2.1.1 provides relational read-only access to IMS™ databases and VSAM data sets. Its communication, data access, and data mapping functions translate non-relational data using relational queries into relational formats on MVS™.

In conjunction with DataJoiner®, users can, from a variety of client platforms, submit a standard SQL query that accesses non-relational data consistently. It's as if the data was in a DB2® database.

A workstation end user can issue an SQL join across IMS, VSAM, DB2 Universal Database® for OS/390®, in addition to Oracle, Microsoft™ SQL server, Sybase, and a variety of other relational and non-relational data sources.

Key Prerequisites

  • Base System running MVS/ESA™ V5.1 (or OS/390 V1.3, if using TCP/IP)
  • DB2 DataJoiner V2.1.1 running under Windows NT® or AIX®
  • For the Data Mapper, an IBM-compatible workstation with at least a 486 processor
    • 4 MB RAM (8 MB recommended)
    • VGA monitor
    • Microsoft Windows 95, Windows 98, and Windows NT
    • 10MB of free hard disk space

Planned Availability Date

April 16, 1999

Description

Data Sources Accessed by Classic Connect

Classic Connect provides relational read-only access to IMS databases and VSAM data sets. It creates a logical, relational database, complete with logical tables that are mapped to actual data in IMS or VSAM databases. Specifically:

  • For IMS, each logical table corresponds to one or more segments of a path in an IMS full-function database. The fields of multiple segments in a path map to the columns of a logical table. Each unique set of segment instances for the given path maps to a row in a logical table.
  • For VSAM, each logical table corresponds to a VSAM data set. Each field of the data set maps to a column of the logical table; each record of the data set maps to a row. Classic Connect can read data from VSAM KSDS, RRDS, and ESDS data sets.

Using this relational structure, Classic Connect translates relational queries into DL1 calls or VSAM reads against IMS databases and VSAM data sets respectively, and returns the result in a relational (for example, a table) format.

Multiple logical databases can be defined for a single data source (such as, a set of VSAM data sets or a single IMS database). Multiple logical tables can be defined in a logical database.

Multiple logical tables can be defined for a single data entity (such as a VSAM data set or an IMS segment). For example, a single VSAM data set can have multiple logical tables defined for it, each one mapping data in a new way.

Consists of Four Major Components

  • Client Interface Module
  • Data Server
  • Enterprise Server
  • Data Mapper

Client Interface Module: The Client Interface Module is used to establish and maintain connections with Data Servers and Enterprise Servers. It performs the following functions:

  • Determines and loads the appropriate transport layer module, based on configuration parameters
  • Establishes communications with Data Servers and Enterprise Servers
  • Stores and retrieves data in the application storage areas
  • Presents error and feedback information to the application

The Client Interface Module can establish multiple connections to a Data Server or Enterprise Server on behalf of a single application program.

The Client Interface Module is contained in both DataJoiner and the sample applications (DJXSAMP) on MVS, AIX, and Windows NT. The sample applications are used during initial setup, for testing the configuration, and for problem determination. They are also useful for designing application queries.

Data Server: All data access is performed by Data Servers. A Data Server is responsible for the following functions:

  • Accepting SQL queries from DataJoiner or the sample applications (DJXSAMP)
  • Determining the type of data to be accessed
  • Rewriting the SQL query into the native file or database access language needed; A single SQL access could translate into multiple native data requests.
  • Optimizing queries based on generic SQL query rewrite and file- or database-specific optimization
  • Querying multiple data sources for JOINs
  • Translating result sets into a consistent relational format, which involves restructuring non-relational data into columns and rows
  • Sorting result sets as needed; for example, ORDER BY
  • Issuing all client catalog queries to the Classic Connect Meta Data Catalog

A Classic Connect Data Server accepts connection requests from DataJoiner and the sample applications on AIX, Windows NT, and MVS.

Enterprise Server: This optional component manages a large number of concurrent users across multiple data sources. An Enterprise Server contains the same tasks that a Data Server uses, with the exception of the query processor and the initialization services.

Like a Data Server, the Enterprise Server's Connection Handler is responsible for responding to client connection requests. However, when a connection request is received, the Enterprise Server does not forward the request to a query processor task for processing. Instead, the connection request is forwarded to a Data Source Handler (DSH) and then to a Data Server for processing. The Enterprise Server maintains the end-to-end connection between the client application and the target Data Server. It is responsible for sending and receiving messages between the client application and the Data Server.

The Enterprise Server is also used to perform load balancing. Using configuration parameters, the Enterprise Server determines the locations of the Data Servers that it will be communicating with and whether those Data Servers are running on the same platform as the Enterprise Server.

The Enterprise Server can automatically start a local Data Server if there are no instances active. It can also start additional instances of a local Data Server when the currently active instances have reached the maximum number of concurrent users they can service, or the currently active instances are all busy.

Data Mapper: The Classic Connect non-relational Data Mapper is a Microsoft Windows™-based application that automates many of the tasks required to create logical table definitions for non-relational data structures. The objective is to view a single file or portion of a file as one or more relational tables. The mapping must be accomplished while maintaining the structural integrity of the underlying database or file.

The Data Mapper interprets existing physical data definitions that define both the content and the structure of non-relational data. The tool is designed to minimize administrative work, using a definition-by-default approach.

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 twentieth and twenty-first centuries, provided that all products (for example, hardware, software, and firmware) used with the product properly exchange accurate date data with it.

Product Positioning

Classic Connect is a middleware product providing SQL access to IMS/MVS and VSAM/MVS. Classic Connect runs on an MVS/ESA or OS/390 system.

Hardware and Software Support Services

SmoothStart™/Installation Services

SmoothStart and Installation Services are not provided.

Trademarks

 
IMS, MVS, MVS/ESA, and SmoothStart are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
DataJoiner, DB2, DB2 Universal Database, OS/390, and AIX are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Microsoft and Windows are trademarks of Microsoft Corporation.
 
Windows NT is a registered trademark of Microsoft Corporation.
 
Other company, product, and service names may be trademarks or service marks of others.

Additional Detailed Operations of Classic Connect

Five Types of Services that Run in the Data Server Component

  • Region controller services, which include an MTO operator interface
  • Initialization services
  • Connection handler services
  • Query processor services
  • Logger services

Region Controller Services: The primary component of a Data Server is the region controller. The region controller is responsible for starting, stopping, and monitoring all of the other components of the Data Server. These different components are referred to as services. The services are implemented as individual load modules running as separate MVS™ tasks within the Data Server address space. Services can have multiple instances, and each instance can support multiple users.

The region controller determines which services to start based on SERVICE INFO ENTRY parameter settings.

Included in the region controller service is the MVS Master Terminal Operator (MTO) interface, which allows you to display and control the services and users that are being serviced by a Data Server. Using the MTO interface, you can also dynamically configure the Data Server.

Initialization Services: Initialization services are special tasks used to initialize and terminate different types of interfaces to underlying database management systems or MVS system components. Currently, two initialization services are provided:

  • IMS™ BMP/DBB/DLI Initialization Service — Used to initialize the IMS region controller to access IMS data using a BMP/DBB interface
  • IMS DRA Initialization Service — Used to initialize the Classic Connect DRA interface and to connect to an IMS DBCTL region to access IMS data using the DRA interface

Connection Handler (CH) Services: A CH service task is responsible for listening for connection requests from DataJoiner® and the sample applications. Connection requests are routed to the appropriate query processor task for subsequent processing.

Classic Connect supplies three typical transport layer modules that can be loaded by the CH task:

  • TCP/IP
  • SNA LU 6.2
  • MVS Cross Memory Services

The MVS client application, DJXSAMP, can connect to a Data Server using any of these methods. However, the recommended approach for local clients is to use MVS Cross Memory Services. DataJoiner or DJXSAMP2 sample applications on AIX® and Windows NT® use TCP/IP or SNA to communicate with a remote Data Server.

Query Processor Services: The query processor is the component of the Data Server that is responsible for translating client SQL into database- and file-specific data access requests. The query processor treats IMS and VSAM data as a single data source and is capable of processing SQL statements that access either IMS, VSAM, or both. Multiple query processors can be used to separately control configuration parameters, such as those that affect tracing and governors, to meet the needs of individual applications.

The query processor can service SELECT statements. It invokes one or more subsystem interfaces (SSIs) to access the target database or file system referenced in an SQL request. The following SSIs are supported:

  • IMS BMP/DBB Interface — Allows IMS data to be accessed through an IMS region controller. The region controller is restricted to a single PSB for the Data Server, limiting the number of concurrent users a Data Server can handle.
  • IMS DRA Interface — Allows IMS data to be accessed using the IMS DRA interface. The DRA interface supports multiple PSBs and is the only way to support a large number of users. This is the recommended interface.
  • VSAM interface — Allows access to VSAM ESDS, KSDS or RRDS files. This interface also supports use of alternate indexes.

Classic Connect supplies a RUNSTATS utility program that is used to update population statistics for the logical tables and their associated indexes and keys. This information can be used by the query processor to optimize JOINs.

Logger Service: A logger service is a task that is used for system monitoring and trouble shooting. A single logger task can be running within a Data Server. During normal operations, you will not need to be concerned with the logger service.

Data Mapper Details: The Data Mapper accomplishes the creation of logical table definitions for non-relational data structures by creating Meta Data Grammar from existing non-relational data definitions (COBOL copybooks). The meta data grammar is used as input to the Classic Connect Meta Data Utility to create a Meta Data Catalog that defines how the non-relational data structure is mapped to an equivalent logical table. The Meta Data Catalogs are used by query processor tasks to facilitate both the access and translation of the data from the non-relational data structure into relational result sets.

The Data Mapper import utilities create initial logical tables from COBOL copybooks. A visual point-and-click environment is used to refine these initial logical tables to match site- and user-specific requirements. You can utilize the initial table definitions automatically created by Data Mapper, or customize those definitions as needed.

Multiple logical tables can be created that map to a single physical file or database. For example, a site may choose to create multiple table definitions that all map to an employee VSAM file. One table is used by department managers who need access to information about the employees in their departments; another table is used by HR managers who have access to all employee information; another table is used by HR clerks who have access to information that is not considered confidential; and still another table is used by the employees themselves who can query information about their own benefits structure. Customizing these table definitions to the needs of the user is not only beneficial to the end-user but recommended.

The Data Mapper contains embedded FTP support to facilitate file transfer from and to the mainframe.

The steps involved are:

  1. Import existing descriptions of your non-relational data into Data Mapper. COBOL copybooks and IMS-DL/I database definitions (DBDs) can be imported into the Data Mapper.
    The Data Mapper creates default logical table definitions from the COBOL copybook information. If these default table definitions are suitable for end-users, skip to 3.
  2. Refine or customize the default table definitions as needed by the users. For example, importing the record layout for the VSAM customer master file creates the default Customer_Table. Two additional tables can also be created from the original:
    • Marketing_Customer_Table, which contains only those data elements required by the marketing department
    • Service_Customer_Table, which contains only those data elements required by support representatives
  3. Generate the actual Meta Data Grammar that will be used by the Meta Data Utility on MVS.
  4. Transfer the logical table definitions to the mainframe where the database or file resides. These definitions are then used as input to the Meta Data Utilities, which create the Meta Data Catalogs.

After completing these steps, you are ready to use Classic Connect operational components with your tools and applications to access your non-relational data.

Education Support

Classic Connect will be touched upon in the following classes:

Course                             Course
Title                              Code
 
Using DataJoiner                   DW202
DataJoiner Administration          DW212

Descriptions of all classroom and self-study courses are contained in the Catalog of IBM Education and Training.

Call IBM Education and Training at 800-IBM-TEACH (426-8322) for catalogs, schedules and enrollments, or visit the Web at:

Technical Information and Specified Operating Environment

Hardware Requirements

Minimum Disk Space Requirements for Installation: To install a Classic Connect system and the required C Runtime files, approximately 66 cylinders of disk space are required. During installation, all the libraries referenced in this section are created. All disk space amounts are for 3390 storage units.

The Classic Connect system is installed using the IBM MVS SMP/E product. The SMP/E product is used to apply, monitor, and ensure the integrity of service updates to the products installed under its control. SMP/E installs a target set of run-time libraries as well as a distribution set of backup libraries. The target library DD names, as well as the low-level qualifiers of their data set names, all begin with the letter "S"; the distribution libraries begin with the letter "A." Both sets of libraries and the disk requirements of each are shown in the following table:

                                                  Disk Space
Contents                           Component      Requirements
 
APF authorized load library        SDJXLOAD       15 cylinders
Configuration parameters           SDJXCONF       1 cylinder
Sample JCL                         SDJXSAMP       1 cylinder
C runtime library                  SDJXSASC       6 cylinders
  (packaged separately)
Macro library for use with         SDJXMAC        1 cylinder
  SYSTEM exits and client
  application
System messages catalog            SDJXMENU       4 tracks
SMP/E "Distribution" copy          ADJXLOAD       15 cylinders
  of SDJXLOAD
SMP/E "Distribution" copy          ADJXCONF       1 cylinder
  of SDJXCONF
SMP/E "Distribution" copy          ADJXSAMP       1 cylinder
  of SDJXSAMP
SMP/E "Distribution" copy          ADJXMAC        1 cylinder
  of SDJXMAC
SMP/E "Distribution" copy          ADJXMENU       4 tracks
  of SDJXMENU

Operational Disk Space Requirements: In addition to the installation libraries, if you are running the Data Servers as started tasks, you need to place the Data Server JCL procedure in a procedure library that is accessed when a start command is issued to activate a Data Server. Because you already have these procedure libraries allocated, and the size of the Data Server procedures is relatively small, no additional disk space should be required for this aspect of implementing Classic Connect.

The only other set of permanent data sets that you need are for the Meta Data Catalogs. The disk space required for the Meta Data Catalogs depends on the number of non-relational-to-relational mappings that you have defined. Additionally, you will need to decide whether to create new sets of the Meta Data Catalogs for each application that you create or whether all of, or a group of, related applications will share the same Meta Data Catalogs.

Disk space requirements for the Meta Data Catalogs are minor. The Meta Data Catalogs consist of index and data components. The Meta Data Catalogs contain approximately 100 logical tables with a total of approximately 2,000 columns. The disk space requirement for the index component is one cylinder, while the data component is three cylinders. You can safely assume that approximately five cylinders of disk space is required for each set of Meta Data Catalogs that you create.

To summarize, you will need about 60 cylinders of 3390 disk space for the basic operational infrastructure and another three to five cylinders for each set of Meta Data Catalogs that you implement. For planning purposes, assume you will need approximately 71 cylinders of permanent disk space to operate Classic Connect.

Another, and much more difficult to estimate, disk space requirement is for temporary disk space required to process user queries. If you use the immediate return of data feature, many types of queries do not require any temporary disk space. However, if a query contains a scalar function or a sorting operator (for example, an ORDER BY clause), then the result set must be spooled to temporary disk for summarization or sorting. If the result set is small, the use of temporary disk space may not be necessary based on the size of the file buffer cache.

For a query, once the file buffer cache is exhausted, the result set is spilled to temporary DASD. You control the size and location of where the temporary files are written using the LD TEMP SPACE configuration parameter.

Assume that the amount of temporary storage required is twice the size of the total result set. For example, if the result set is 3 MB, then approximately 6 MB of temporary storage are required to stage the result set output.

The total amount of temporary DASD that is required is based on the types of queries and the number of concurrent users. For example, if you have 50 concurrent users all issuing queries that retrieve 3 MB of data, and the queries contain an ORDER BY clause, then 300 MB of temporary DASD are required to service all 50 users concurrently.

Runtime Storage Requirements: The amount of virtual storage required to operate a Classic Connect system varies based upon these factors:

  • The number and types of components configured
  • How each component is configured
  • The number of concurrent users being serviced
  • The complexity of the queries being run by each user

Tape Requirement: The system must have an appropriate tape unit for installing the product.

Hardware Requirements for the Data Mapper The Data Mapper runs on an IBM-compatible workstation PC.

Minimum System Requirements for Windows NT and Windows™ 95/98

Hardware             Memory       Monitor    Disk Drives
 
IBM-compatible       4 MB RAM     VGA        Hard drive
  PC with at                                   with 10 MB
  least a 486                                  free
  processor

Software Requirements

Software Requirements for Classic Connect

Minimum Release Level Requirements: The following table identifies minimum release level requirements for some of the different components that make up a Classic Connect system.

The release levels listed in the following table are minimum release levels required for Classic Connect. More recent release levels are also valid.

.------------------+-------------------------------------------.
|System Component  |Minimum Release Level                      |
|------------------+-------------------------------------------|
|Base System       |MVS/ESA (TM) Release 5.1 (or OS/390 (R)    |
|                  |  V1.3, if using TCP/IP)                   |
|                  |                                           |
|VSAM SSI          |DFSMS/MVS (R) V1.2                         |
|                  |                                           |
|IMS/ESA (R)       |IMS V5.1                                   |
|                  |                                           |
|TCP/IP CI         |TCP/IP V3.2 with Berkeley Sockets          |
|                  |  interface option installed, or Interlink |
|                  |  TCP/IP V2.1.                             |
|                  |                                           |
|VTAM (R) LU6.2 CI |Any supported version of VTAM. (VTAM       |
|                  |  V4.4 on MVS requires PTF UW39398)        |
|                  |                                           |
|TME 10 (TM)       |PTF UW51238 (TME 10 NetView C Runtime      |
|NetView (R) C     |  Library V6.0 is shipped                  |
|                  |  with Classic Connect V2.1.1.)            |
|                  |                                           |
|DB2 (R) DataJoiner|V2.1.1 running under AIX with PT           |
|                  |  U462821, or later, or under Windows NT   |
|                  |  with PTF IP21560, or later.              |
'------------------+-------------------------------------------'

Note: PTF requirements are subject to change. Always check the DataJoiner Web site for the latest PTF levels:

For APPC connectivity between Classic Connect and DataJoiner for Windows NT, you need Microsoft™ SNA Server V3.0 service pack 3, or later.

APF Authorization Requirements: Both the Data Server and Enterprise Server require the Classic Connect load library to be APF authorized in most situations, including for the configuration used in the Installation Verification Procedure (IVP). After the system installation has been verified, APF authorization can be removed if the configuration does not include any use of the Cross Memory transport layers or any of the security or accounting Exits. The C runtime library must be APF-authorized.

Software Requirements for the Data Mapper: One of the following:

  • Microsoft Windows 95/98, or
  • Microsoft Windows NT

Compatibility

Compared to DataJoiner Classic Connect V1.2 Classic Connect V2.1.1 is upwardly compatible with DataJoiner Classic Connect 1.2.

Classic Connect V2.1.1 is:

  • Easier to install and configure
  • More reliable due to greatly reduced complexity
  • Up to three or more times faster — but that is very dependent on the query itself.
  • With the Enterprise Server we have more user concurrency. Each Data Server easily supports 50 users concurrently. An Enterprise Server can then be used to dispatch queries across multiple Data Servers allowing support of hundreds of users.

There is also a change in the terms and conditions. DataJoiner Classic Connect V1.2 was licensed under the IBM International Program License Agreement (IPLA). Classic Connect V2.1.1 terms and conditions fall under the IBM Customer Agreement (ICA) or the IBM International Customer Agreement (IICA).

Planning Information

Installability: To facilitate conversion DataJoiner can support simultaneous access of V1.2 and V2.1.1 of Classic Connect. This is achieved by using different protocols when creating a server mapping within DataJoiner. Separate environment variables point to the separate Classic Connect configuration files.

In this way current users of DataJoiner Classic Connect V1.2 can install the new Classic Connect V2.1.1 and migrate DataJoiner based applications one at a time. This saves users from having to upgrade all software and applications simultaneously.

Additionally, the DataJoiner Classic Connect V1.2 Projection Utility can be used with Classic Connect V2.1.1 to create new Meta Data Catalogs. However, to exploit the new functions, VSAM and IMS data should be re-mapped using the new Classic Connect V2.1.1 Data Mapper.

Direct Customer Support: Direct customer support is provided by S/390 Support Line. This fee service can enhance your productivity by providing voice and electronic access into the IBM support organization. S/390 Support Line will help answer questions pertaining to usage, how to and suspected software defects for eligible products.

Installation and technical support is provided by IBM Global Services. For more information on services, call 800-IBM-4YOU (426-4968).

Packaging: The Classic Connect V2.1.1 program will be shipped on two tapes:

  • Classic Connect V2.1.1 machine-readable material
  • C Runtime library

There is a choice of three formats:

  • 3480 1/2-in Data Cartridge; 34K bpi uncompressed
  • 4-mm Data Cartridge; Modified; 2GB uncompressed
  • 9-Track 6250 BPI Distribution Tape Reel (DTR)

The Data Mapper component is shipped with DataJoiner PTFs.

Copies of the following publications are included:

                                             Order
Title                                        Number
 
DB2 DataJoiner Classic Connect:              SC26-9319
  Installation, Configuration, and
  Reference Guide V2.1.1
DB2 DataJoiner Classic Connect               SC26-9318
  Data Mapper: Installation and
  User's Guide V2.1.1
IBM Classic Connect V2.1.1                   GC26-9317
  Licensed Program Specifications (LPS)

System Integrity

IBM will accept APARs where the installation of this licensed program causes an exposure to the system integrity of MVS. This program is intended to run authorized.

MVS System Integrity Applies: Yes

DPPX/BASE System Integrity Applies: Yes

Security, Auditability, and Control

Classic Connect V2.1.1 uses the security and auditability features of MVS. Additional security is provided when addressing through DataJoiner via authorizations required to access a given DataJoiner nickname. The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.

Ordering Information

New Licensees

Orders for new licenses will be accepted now.

Shipment will begin on the planned availability date.

New users of Classic Connect V2.1.1 should specify:

        Type                    Model
 
        5655                     B73

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 (OTC) feature number. Also specify the feature number of the desired distribution medium.

                                                  ESL OTC
                                   Program        Feature
Description                        Number         Number
 
Classic Connect V2.1.1             5655-B73       1012
  for use with IMS data
 
Classic Connect V2.1.1             5655-B73       1025
  for use with VSAM data

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

Parallel Sysplex® 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. If applicable, specify the PSLC Level A, PSLC Level B, PSLC Level C and PSLC Level D features and quantities.

If there is more than one program copy in a Parallel Sysplex, the charge for all copies is associated to one license 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 (NC) Identifier feature on the licenses.

There are two tables of PSLC Feature numbers. The first table is to be used when Classic Connect is to access IMS data. The second table is for access to VSAM data.

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

When Accessing IMS Data

                     IMS
                     PSLC          PSLC Basic License
Machine            Feature         MLC Feature
MSU Capacity        Number         Description
 
1                    1000          PSLC Base, 1 MSU
2                    1001          PSLC Base, 2 MSUs
 
3                    1002          PSLC Base, 3 MSUs
 
4 -- 45              1003          PSLC Level A, 1 MSU
                     1004          PSLC Level A, 42 MSUs
 
46 -- 175            1005          PSLC Level B, 1 MSU
                     1006          PSLC Level B, 10 MSUs
                     1007          PSLC Level B, 50 MSUs
 
176 -- 315           1008          PSLC Level C, 1 MSU
                     1009          PSLC Level C, 10 MSUs
                     1010          PSLC Level C, 50 MSUs
 
316 or more          1026          PSLC Level D, 1 MSU
                     1027          PSLC Level D, 50 MSUs
 
NA                   1011          PSLC NC IDENTIFIER

When Accessing VSAM Data

                     IMS
                     PSLC          PSLC Basic License
Machine            Feature         MLC Feature
MSU Capacity        Number         Description
 
1                    1013          PSLC Base, 1 MSU
2                    1014          PSLC Base, 2 MSUs
 
3                    1015          PSLC Base, 3 MSUs
 
4 -- 45              1016          PSLC Level A, 1 MSU
                     1017          PSLC Level A, 42 MSUs
 
46 -- 175            1018          PSLC Level B, 1 MSU
                     1019          PSLC Level B, 10 MSUs
                     1020          PSLC Level B, 50 MSUs
 
176 -- 315           1021          PSLC Level C, 1 MSU
                     1022          PSLC Level C, 10 MSUs
                     1023          PSLC Level C, 50 MSUs
 
316 or more          1028          PSLC Level D, 1 MSU
                     1029          PSLC Level D, 50 MSUs
 
NA                   1024          PSLC NC IDENTIFIER

Examples of Table Use

Example 1: For a single machine with 11 MSUs and accessing VSAM, the PSLC features would be: 1015 — quantity 1 and 1016 — quantity 8.

Example 2: For two machines in a Parallel Sysplex which have an aggregation of 60 MSUs and used for accessing VSAM, the PSLC features would be:

  • PSLC chargeable license #1:
    • 1015 — quantity 1, 1017 — quantity 1,
    • 1018 — quantity 5, and 1019 — quantity 1
  • PSLC no-charge license #2: 1024 — quantity 1

Basic Machine-Readable Material

.----------------+-------+---------------------------------.
|                |Feature|                                 |
|Environment     |Number |Distribution Medium              |
|----------------+-------+---------------------------------|
|S/390           | 5802  |2-3480 1/2-inch Data Cartridges  |
|  for IMS Data  |       |  34K bpi uncompressed           |
|                |       |                                 |
|S/390           | 5260  |2-4 mm Data Cartridges; Modified;|
|  for IMS Data  |       |  2 GB uncompressed              |
|                |       |                                 |
|S/390           | 5801  |2-9 Track 6250 BPI Distribution  |
|  for IMS Data  |       |  Tape Reels (DTR)               |
|                |       |                                 |
|S/390           | 5812  |2-3480 1/2-inch Data Cartridges  |
|  for VSAM Data |       |  34K bpi uncompressed           |
|                |       |                                 |
|S/390           | 5261  |2-4 mm Data Cartridges; Modified;|
|  for VSAM Data |       |  2 GB uncompressed              |
|                |       |                                 |
|S/390           | 5811  |2-9 Track 6250 BPI Distribution  |
|  for VSAM Data |       |  Tape Reels (DTR)               |
'----------------+-------+---------------------------------'

Customization Options: Select the appropriate feature numbers 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, specify feature number 3470 to ship media only. For future updates, specify feature number 3480 to ship media updates only. If, in the future, publication updates are required, order an MES to remove feature number 3480; then, the publications will ship with the next release of the program.

                                                    Feature
Description                                         Number
 
Initial Shipments
 
Serial Number Only (suppresses shipment             3444
 of media and documentation)
 
Ship Media Only (suppresses initial                 3470
 shipment of documentation)
 
Ship Documentation Only (suppresses                 3471
 initial shipment of media)
 
Update Shipments
 
Ship Media Updates Only (suppresses                 3480
 update shipment of documentation)
 
Ship Documentation Only (suppresses                 3481
 update shipment of media)
 
Suppress Updates (suppresses update                 3482
 shipment of media and documentation)
 
                                                    Feature
Description                                         Number
 
 
Expedite Shipments
 
Local IBM Office Expedite                           3445
 (for IBM use only)
 
Customer Expedite Process Charge                    3446
 ($30 charge for each product)

Expedite shipments will be processed to receive 72-hour delivery from the time IBM Software Delivery Solutions (SDS) receives the order. SMS will then ship the order via overnight air transportation.

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

                                                       Order
Title                                                  Number
 
DB2 DataJoiner Classic Connect:                        SC26-9319
  Installation, Configuration, and
  Reference Guide V2.1.1
 
DB2 DataJoiner Classic Connect                         SC26-9318
  Data Mapper: Installation and
  User's Guide V2.1.1
 
IBM Classic Connect V2.1.1                             GC26-9317
  Licensed Program Specifications (LPS)

Additional copies of unlicensed publications are available for a fee. These copies may be ordered from your IBM representative, direct order, or via the Publications Notification Systems (PNS) Web site at

Displayable Softcopy Publications: Classic Connect V2.1.1 manuals are offered in displayable softcopy form. All unlicensed manuals will be included in an IBM OS/390 Collection Kit.

These displayable manuals can be used with the BookManager® READ licensed programs in any of the supported environments. Terms and conditions for use of the machine-readable files are shipped with the files.

Licensed Documentation: 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.

Customer Financing: IBM Global Financing offers attractive financing to credit-qualified commercial and government customers and Business Partners in more than 40 countries around the world. IBM Global Financing is provided by the IBM Credit Corporation in the United States. Offerings, rates, terms and availability may vary by country. Contact your local IBM Global Financing organization. Country organizations are listed on the Web at:

Terms and Conditions

Licensing: ICA

Variable Charges Apply: No

Indexed Monthly License Charge (IMLC) Applies: No

Location License Applies: No

Use Limitations Applies: No

Educational Allowance: Yes, to qualified education customers.

Volume Discount: Not applicable

Version-to-Version Upgrade Credits Apply: Yes

                                                       Single
                                                      Version
                                                      Charging
Replaced Program         Replacement Program          Applies
 
Classic Connect          To a follow-on, if any         N/A*
  V2.1.1 (5655-B73)
*
Not Applicable

Warranted: Yes

Licensed Program Materials Availability

  • Restricted Materials of IBM: None
  • Non-Restricted Source Materials: None
  • Object Code Only (OCO): All

Testing Period: Two months (basic license only)

Program Services

  • Support Center applies: Yes. Access is available through the IBM Support Center.
  • Available until discontinued: 12 months' written notice

Support Line: S/390®

Charges

Contact your IBM representative for charges information for this announcement.

Call Now to Order

To order, contact the IBM Americas Call Centers, your local IBM representative, or your IBM Business Partner.

IBM Americas Call Centers, our national direct marketing organization, can add your name to the mailing list for catalogs of IBM products.

 Phone:     800-IBM-CALL
 Fax:       800-2IBM-FAX
 Internet:  ibm_direct@vnet.ibm.com
 Mail:      IBM Americas Call Centers
            Dept. LE001
            P.O. Box 2690
            Atlanta, GA  30301-2690
 Reference: LE001

To identify your local IBM Business Partner or IBM representative, call 800-IBM-4YOU.

Note: Shipments will begin after the planned availability date.

Trademarks

 
MVS, IMS, and MVS/ESA are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
DataJoiner, AIX, OS/390, DFSMS/MVS, IMS/ESA, VTAM, NetView, DB2, Parallel Sysplex, BookManager, and S/390 are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Windows and Microsoft are trademarks of Microsoft Corporation.
 
Windows NT is a registered trademark of Microsoft Corporation.
 
TME 10 is a trademark of Tivoli Systems, Inc. in the United States or other countries or both.
 
Other company, product, and service names may be trademarks or service marks of others.