IMS APPLICATION DEVELOPMENT FACILITY (IMSADF) II VERSION 2 RELEASE 2
NOW WITH CICS/OS/VS AND MVS/XA SUPPORT

Contents


Announcement Letter Number 286-375 dated September 8, 1986
US - Last Revised on September 8, 1986



Brief Description of Announcement, Charges, and Availability

       IMSADF II Version 2 Release 2 is an application generator for
MVS/370 and MVS/XA IMS/VS and CICS/OS/VS data base and data
communication systems.  Release 2 enhancements include:  support for
a CICS/OS/VS processing environment with IMS/VS DB, DB2, and VSAM
support, pseudo-conversational execution capability, SPA size
increased to 65K, and MVS/XA support.
       IMSADF II Version 2 Release 2 operates with IMS/VS DB/DC
including DB2 and/or CICS/OS/VS with IMS/VS DB and/or DB2 DB/DC
systems to reduce the time and effort required to develop, maintain
and expand data base and data communication applications.  Increased
capabilities in the areas of data independence, access control, data
integrity, and message routing between application system users are
also provided.
       Concurrent with availability of Release 2, IMSADF II Version 2
Release 1 will no longer be available.
Charges
                        Basic        Basic
                        OTC          MLC
Base Product            $33,000      $1,650
IMS/VS feature           21,890       1,100
CICS/OS/VS feature       21,890       1,100
       Planned Availability Date: September 12, 1986


Customer Letter Section

HIGHLIGHTS
o   CICS/OS/VS processing environment support (MVS)
    -   Equivalent in function to IMS/VS
    -   Provides application portability and application
        compatibility
    -   MVS/370 and MVS/XA support
    -   CICS/OS/VS - DL/I
    -   CICS/OS/VS - DB2
    -   CICS/OS/VS - DL/I & DB2
    -   CICS/OS/VS VSAM access support
    -   Pseudo-conversational and non-conversational execution
        drivers
    -   BMP execution driver
o   Re-entrant execution drivers
o   MVS/XA exploitation
o   Dynamic rule management
o   IADF enhancements
o   New audit operations
o   Direct high level audit language to static audit rule
o   Maximum SPA size increased (32K TO 65K)
o   Expanded NLS - Swedish, Spanish, Korean (Hanguel, DBCS)
DESCRIPTION
       The IMS Application Development Facility (IMSADF) is designed
to quickly and efficiently develop applications for IMS/VS and/or
CICS/OS/VS DB/DC systems.  The facility provides generalized
functions, relieving the need to code in a procedural language
(ASSEM, COBOL, or PL/I) many frequently developed and used modules.
These include modules that execute DL/1 calls, format and de-format
3270 screens, edit input data, verify user authority, and route
messages between applications and system users.  Application drivers
are furnished that provide the logic necessary to connect the
generalized functional modules into applications to be executed.  To
specify the required application function, the programmer defines
parameters, or rules, which are stored in data tables within the
facility.  During execution, the application drivers reference these
tables to perform the application to meet end-user requirements.
       IMSADF allows development of many IMS/VS or CICS/OS/VS
applications free of procedural code.  User exits are provided to
allow the coding of specialized editing or processing logic in a
procedural language.  The generalized functions (called common
modules) provide a high level application program interface (API) for
applications which require this exit logic.
       IMSADF provides a conversational dialogue  which allows a user
(based on his IMSADF user profile authorization) to browse, display,
update, delete, or insert any segment in any DL/I logical or physical
data base or row in a DB2 table.
       Applications are implemented by coding and generating the rule
descriptions of the data bases, the transaction rule(s) and,
optionally, input screen(s).  Screen field edits, data base record
validation, and processing logic definitions may be added to the
transaction specifications to perform user edit and processing
functions.  If a user transaction requires additional processing
logic, an exit routine can be added.
       The capability of augmenting standard processing with
specialized exit routines that use services provided by IMSADF common
modules is a major feature of IMSADF.  This capability allows even
the most complex IMS/VS or CICS/OS/VS DB/DC applications to employ
IMSADF facilities and achieve significant productivity benefits.  The
functional enhancements provided in this release have broadened the
scope of applications that can be developed entirely with standard
processing, and greatly reduced the need for exit routines.
       In addition, IMSADF provides a message handling application to
send/receive and queue messages between user groups and individual
users, and a text processing application for simple text processing.
ENHANCEMENTS
The enhancements contained in this release of IMSADF II Version 2 are
described below.
CICS/OS/VS PROCESSING ENVIRONMENT SUPPORT (MVS):  The CICS/OS/VS
processing environment support provides the productivity, ease-of-use
and development characteristics of IMSADF II to CICS/OS/VS with
IMS/VS DB and/or DB2 customers.  This support is essentially
equivalent in function to the support currently provided to IMS/VS
users.  IMSADF applications can now be compatible with and portable
between IMS/VS and CICS/OS/VS processing environments.
       To the end user, the view of the applications is compatible
across both environments.  The developer view of the rule definitions
is compatible across both environments and in most cases the
generated rules will run in either environment.
       The CICS/OS/VS support requires CICS/OS/VS Release 1.7 and is
MVS/370 or MVS/XA only.
       IMSADF II Version 2 Release 2 supports the following
CICS/OS/VS data base/data communication (DB/DC) processing
environments:
    CICS/OS/VS - DL/I & VSAM
    CICS/OS/VS - DB2 & VSAM
    CICS/OS/VS - DL/I & DB2 & VSAM.
       VSAM  access support includes key sequenced data sets, entry
sequenced data sets, and relative record data sets.  VSAM access is
supported by both IMSADF II standard processing and exit processing.
       IMSADF II Version 2 provides three different execution drivers
which interpret the application specifications (called rules) and
perform the application.
       The execution drivers provide online pseudo-conversational,
non-conversational and batch transaction processing and off-line
IMS/VS DB batch processing capability.  The three execution drivers
correspond to three types of online processing:
o   Pseudo-conversational transaction processing
           Multiple screen iteration processing that can include data
    base access and manipulation (add, delete, update), and saving of
    intermediate results in temporary storage.
o   Non-conversational transaction processing
           A single screen iteration processing that can include data
    base access and manipulation (add, delete, update) and does not
    require use of temporary storage.
o   Batch transaction processing
           This mode can be used for processing of batched
    transactions from a sequential file.  The sequential file can be
    created by online data collection transactions (screen iterations
    where the messages are recorded in the sequential file), or an
    offline process for later, deferred processing (batch).  This
    mode can also be used for extended online processing, which can
    involve massive data base manipulation (add, delete, update) with
    intermediate application controlled checkpointing for restarting.
o   Offline batch DL/I processing
           In addition, the Batch Message Processing driver also
    supports off-line batch IMS/VS DB (DL/I) processing under MVS/370
    or MVS/XA.
RE-ENTRANT EXECUTION DRIVERS:  The IMSADF II Version 2 online
execution facilities have been made fully re-entrant to satisfy
CICS/OS/VS environmental requirements.  This benefits IMS/VS users as
well, since only a single copy of the execution facilities will be
required for each IMS/VS system instead of a copy for each IMS/VS
message processing region.
MVS/XA EXPLOITATION:  IMSADF II Version 2 has provided support to
utilize MVS/XA capabilities.  In general, the execution facilities
will execute in either 31 bit mode or 24 bit mode except for
restrictions imposed by either of the IMS/VS or CICS/OS/VS host
subsystems.
       IMSADF objects such as the execution drivers, common modules,
input transaction rules, segment/table layout rules, static audit
rules, mapper rules, and output format rules are loaded above the 16
MB line.
       IMSADF objects such as mini-drivers, segment/table handler
rules, exit routines, primary option and secondary option menu rules
are loaded below the 16 MB line.
DB2 DYNAMIC RULE CAPABILITY:  IMSADF II Version 2 now supports using
Database 2 tables to store dynamic rules (User Profile, Audit and
Message) for both IMS/VS and CICS/OS/VS.  This support is an
installation option that creates either three DL/I data bases or 14
DB2 tables.  Both online interactive and batch transactions are
provided to browse, display and update the data bases and tables.
DYNAMIC RULE MANAGEMENT:  A new IMSADF II facility is provided to
manage static rules dynamically.  The facility will automatically
maintain in virtual storage the most active static rules.  During

installation, the size of the static rules pool to be managed is
defined.  This facility does not require a preload rule.
       In an MVS/XA system all eligible rules are loaded above the 16
MB line.  Other rules are loaded below the 16 MB line and are managed
in the installation defined pool.  In an MVS/370 system the facility
will manage all static rules in the installation defined pool.
       The system will automatically adjust during a day's operations
to changes in transaction mix and processing activity.
IADF ENHANCEMENTS:  Interactive application definition panels have
been enhanced to improve ease-of-use characteristics.  The menu
panels have been modified to provide more of a developer function
orientation and less of a product function orientation.  Panel
terminology has been changed to be more generic and less product
specific.  In addition, IADF will now extract message and profile
rules from batch driver input to load IADF tables.  IADF native
prototyping now includes support for simulating data base updating,
secondary key browsing, and default screens.  IADF has added a
facility for selectively tracing CLIST execution of IADF functions.
IADF transaction generation and transaction control table management
functions have been rewritten and performance significantly improved.
NEW AUDIT OPERATIONS:  New audit operations have been provided to
test for changed segment data, previous audit error, and
unconditional audit execution halt/stop.  In addition, new audit
operations have been provided to invoke the data mapper common module
routine to gather/scatter fields and copy segment operations.
HIGH LEVEL AUDIT LANGUAGE ENHANCEMENTS:  The high level audit
language processor has been enhanced to create static audit rules
directly from HLAL source without first updating the audit rule data
base.  In addition, processor limits have been raised for IF/DOWHILE
from 200 to 400, nested IF from 25 to 50, and GOTO from 50 to 100.
SPA SIZE INCREASED:  The maximum SPA size has been increased from 32K
to 65K when using the work database to allow users increased
capabilities in developing applications that manipulate large
segments or many segments.
EXPANDED NLS:  National language support has been expanded to include
the Swedish, Spanish and Korean (Hanguel, DBCS) languages.  German,
French, Portuguese and Japanese (Kanji, DBCS) languages were
supported in Version 2 Release 1.
PUBLICATIONS
       IMS Application Development Facility II General Information
Manual (GH20-6591) is available.
       The following publications supporting IMSADF II Version 2 can
be ordered:
o   Licensed Program Specifications (GH20-0006*)
o   User Reference (SH20-6592)
o   Installation Guide (SH20-6593*)
o   Application Development Reference (SH20-6594)
o   Application Development Guide (SH20-6595)
o   Rules Documentation User's Guide (SH20-6596)
o   Data Dictionary Extension User's Guide (SH20-6597)
o   Diagnosis Guide (LY20-6401*)
o   Master Index (SH20-6599)
o   Interactive ADF User's Guide (SH20-6601)
o   Interactive ADF Administration Guide (SH20-6602)
o   DB2 Application Specifications Guide (SH20-6603)
* One copy is supplied automatically with the machine-readable
  material shipped from IBM Software Distribution.
SCHEDULE
       Planned availability is September 12, 1986.
TECHNICAL INFORMATION
       SPECIFIED OPERATING ENVIRONMENT
HARDWARE REQUIREMENTS:  The machine configuration required for IMSADF
II is determined by the requirements of the host operating system,
the selected DB/DC subsystem, and the objectives of the installation.
The customer must have at least the minimum hardware configuration
for IMS/VS DB/DC, CICS/OS/VS with IMS/VS DB, or CICS/OS/VS with
DATABASE 2.
       The minimum system requirements for which the IMS Application
Development Facility has been designed to operate are:
o   IBM System/370 capable of supporting MVS/370 or MVS/XA and IMS/VS
    DB/DC or
o   IBM System/370 capable of supporting MVS/370 or MVS/XA and
    CICS/OS/VS with IMS/VS DB
o   IBM System/370 capable of supporting MVS/370 or MVS/XA  and
    CICS/OS/VS with IBM DATABASE 2
o   A nine-track tape drive for installing distributed material.
       IMSADF II has been designed to support the IBM 3270
Information Display System family.  Terminals must be at least 24
lines of 80 columns in size and be supported by the IMS/VS DC system
and the IMS/VS MFS facility, or CICS/OS/VS and the CICS/OS/VS BMS
facility.
       IMSADF II in CICS/OS/VS with DL/I and IMS/VS DB/DC host
processing environments supports the 3277, 3275, 3278, 3279, 5555,
and 3290 with an appropriate control unit.
SOFTWARE REQUIREMENTS:  IMSADF II has been designed to operate with
current releases of MVS/370 and MVS/XA (31 bit mode) environments
with IMS/VS and/or CICS/OS/VS.
       IMSADF II will operate with the following programming systems:
o   IMS/VS Version 1 DB/DC Release 2, Release 3, Version 2 Release 1,
    or subsequent releases unless otherwise specified, or
o   IMS/VS Version 1 DB/DC Release 3, Version 2 Release 1, and
    DATABASE 2 (DB2) Release 1, Release 2, or subsequent releases
    unless otherwise specified, or
o   CICS/OS/VS Version 1 Release 7 with IMS/VS Version 1 Release 3
    DB, IMS/VS Version 2 Release 1 DB, or subsequent releases unless
    otherwise specified, or
o   CICS/OS/VS Version 1 Release 7 with DATABASE 2 Release 1, Release
    2 or subsequent releases unless otherwise specified, or
o   CICS/OS/VS Version 1 Release 7 with IMS/VS Version 1 Release 3
    DB, or IMS/VS Version 2 Release 1 DB and DATABASE 2 Release 1,
    Release 2, or subsequent CICS/OS/VS, IMS/VS and DB2 releases
    unless otherwise specified.
       For IMS/VS or CICS/OS/VS operating system requirements, refer
to the IMS/VS or CICS/OS/VS programming systems support in the
appropriate documentation.
       For IBM Database 2 operating system requirements (MVS/370 or
MVS/XA is required), refer to IBM Database 2 Installation Guide.
       ISPF Version 2 Release 1 and ISPF/PDF Version 2 Release 1, or
a subsequent release, is required to use IMSADF II Version 2
ISPF-based application definition and installation dialogs.
       If an MVS installation elects to include the IMSADF II Data
Dictionary Extension, OS/VS DB/DC Data Dictionary Release 5 is
required, or a subsequent release unless otherwise specified.
       If an MVS installation elects to include the IMSADF's RACF
support, RACF Version 1 Release 5 is required, or a subsequent
release unless otherwise specified.
       If an MVS installation elects to include IMSADF's ISPF based
dialogs support, ISPF Version 2 Release 1 and ISPF/PDF Version 2
Release 1 is required, or a subsequent release unless otherwise
specified.
       If an MVS installation elects to include the IMSADF's BTS
support, BTS Version 1 Release 2 is required, or a subsequent release
unless otherwise specified.
       SMP/4 or SMP/E is required to install and add product
maintenance.
VIRTUAL STORAGE REQUIREMENTS:  The minimum virtual requirements to
operate IMSADF II Version 2 satisfactorily are:
o   Adequate storage for IMS/VS DB/DC with at least:
    -   512K for conversational or non-conversational message regions
    -   512K for batch message region
    -   1536K for batch message region or batch region running Rules
        Documentation facility.
o   1536K MVS batch region running High Level Audit Language program
o   1024K MVS batch region running Rules Generator program
o   Adequate storage for CICS/OS/VS with IMS/VS DB and/or IBM
    DATABASE 2 with at least:
    -   512K for a CICS/OS/VS region running pseudo-conversational or
        non-conversational transactions
    -   512K for a CICS/OS/VS region running batch message
        transactions
    -   1536K for a CICS/OS/VS region running Rules Documentation
        facility.
       Virtual storage requirements are described in more detail in
Chapter 2 of the Installation Guide.  A summary follows:

o   The virtual storage IMS/VS message region requirement to run the
    distributed sample application is 402K.  Refer to Figure 1 for
    the IMS/VS storage map for MVS/370 and MVS/XA users.
    -   For MVS/XA users, 260K is above the 16 MB line in addition to
        most application rules.
    -   If MFC1Version 20 is placed in the Link Pack Area (LPA), or
        Extended Link Pack Area (ELPA), 260K is not required in each
        message region in which IMSADF II Version 2 transactions
        execute.
o   The CICS/OS/VS region requirement for the first active user to
    run the distributed sample application is 408K.  Refer to Figure
    2 for the CICS/OS/VS storage map for MVS/370 and MVS/XA users.
    -   For MVS/XA users, 260K is above the 16 MB line in addition to
        most application rules.
           Each subsequent CICS/OS/VS active user requires
    approximately 80K storage for work areas, in addition to rules
    and transaction drivers (if different IMSADF II Version 2
    applications are selected).
           Region sizes may vary depending on the number of buffers
    defined at your location for both MVS and IMS/VS data sets.
  MVS/370                       MVS/XA
  - - - - :--------------------:
          |                    |
  16 MB   |  MFC1V20 (260K)    |
          |--------------------|
          |                    |
          | Application RULES  |
          |    (variable)      |- - - -
          |    (SAMP=8K)       |16 MB
          |--------------------|
          |                    |
          |  Work Areas (80K)  |
          |     (minimum)      |
          |--------------------|
          |                    |
          |  ????V50 (30K)     |
          |--------------------|
          |                    |
          |Transaction Drivers |
          |(variable, SAMP=8K) |
          |--------------------|
          |      Sign on/      |
          |    Sign off (16K)  |
          '--------------------'
Figure 1.  IMSADF II Version 2 IMS/VS DC storage map for MVS and
MVS/XA users
  MVS/370                       MVS/XA
  - - - - :--------------------:
          |                    |
  16 MB   |  MFC1V20 (260K)    |
          |--------------------|
          |                    |
          |  Application RULES |
          |     (variable)     |- - - -
          |     (SAMP=8K)      |16 MB
          |--------------------|
          |                    |
          |  Work Areas (80K)  |
          |      (minimum)     |
          |--------------------|
          |                    |
          |    ????C30 (36K)   |
          |--------------------|
          |                    |
          |Transaction Drivers |
          |(variable, SAMP=8K) |
          |--------------------|
          |     Sign on/       |
          |   Sign off (16K)   |
          '--------------------'
       Figure 2.  IMSADF II Version 2 CICS/OS/VS storage map for MVS
and MVS/XA users
       A comparison of the MVS/370 and MVS/XA use of virtual storage
by IMSADF II Version 2 is illustrated in Figure 1 for an IMS/VS
message processing region and in Figure 2 for a CICS/OS/VS processing
region.  The positioning of the 16 MB virtual storage (dotted) line
is shown for MVS/370 users on the left and for MVS/XA users on the
right of the map.
       The size of IMSADF II Version 2 transaction drivers varies
according to exit usage.  The size given is for the distributed
sample application.
       Rules are load modules that provide application logic and data
layouts.  Most rules reside above the 16 MB line in MVS/XA.  Most
rules are relatively small, except for static audit load modules,
which contain editing logic and can be considered as programs.  Their
size varies, but could be quite large.  There may be either one per
IMSADF II Version 2 transaction, or one can service many IMSADF II
Version 2 transactions or applications.
       The figures depict private virtual storage area requirements
although MFC1V20 can be placed in LPA or ELPA common virtual storage
areas.
COMPATIBILITY:  IMSADF II Version 2 includes all existing function of
IMSADF II Version 1 (5668-937) and IMSADF II Version 2 Release 1.
       The combination of the functional and performance enhancements
is expected to result in performance equivalent to or better than
IMSADF II V1 Release 1 depending on individual installation and
application characteristics.
PLANNING INFORMATION
CUSTOMER RESPONSIBILITY:  The installation of IMSADF II Version 2
requires a properly configured IMS/VS DB/DC system, or a CICS/OS/VS
system with IMS/VS DB and/or IBM DATABASE 2.  Appropriate terminals
and other devices are needed as required for IMS/VS, CICS/OS/VS and
the desired operating system (MVS/370 or MVS/XA).
INSTALLABILITY:  The System Modification Program (SMP) Release 4  or
SMP/E for OS/VS2 (MVS) and ISPF Version 2 Release 1, or a later
release, is required for installation.
       For users of IMSADF II Version 1 (5668-937) and IMSADF (IUP)
Release 1.3 (5796-PHX), regeneration of static rules will not be
required.  The IMSADF II Message Data Base must be unloaded and
reloaded.
SYSTEM INTEGRITY
       IBM will accept APARs where installation of IMSADF II
introduces an exposure to the system integrity of MVS.  See
Programming Announcement P81-174, dated October 21, 1981.  This
program is intended to run unauthorized.
SECURITY, AUDITABILITY, AND CONTROL
       IMSADF II runs as an application program under IMS/VS, or
CICS/OS/VS with MVS/XA or MVS/370 and is subject to the controls they
provide.  IMSADF II provides end-user sign-on validation and
authorization functions to control end-user access to data bases.
User profiles restrict data base access by segment type, processing
option, and mode of access (retrieve, delete, etc.).  A user exit
before and after each segment handler DL/I call is provided for user
written audit trails, access controls or other specialized
processing.
       User management is responsible for the evaluation, selection
and implementation of security features, for administrative
procedures, and for appropriate controls in application systems and
communication facilities.
       If sensitive data is sent over external communication
facilities, user management may wish to pursue the application of
cryptography.
ORDERING INFORMATION
       Current licensees of IMSADF II Version 2 must order this
release via MES.  Detailed ordering instructions are scheduled to be
mailed from IBM Software Distribution to all current licensees by
September 26, 1986.
NEW LICENSEES:  Orders will be accepted now.  New users of IMSADF II
Version 2 should specify:  Type:  5665, Model:  348.
BASIC LICENSE:  To order a basic license for new users, enter the
program number and feature #9001 for asset registration.  Enter
feature #4626 for one-time charge or #4627 for monthly license
charge.
DSLO:  To order a new Version 2 DSLO license, enter the program
number and feature #9617 for one-time charge.  Ordering  a DSLO
license will result in IBM Software Distribution maintaining a record
of this customer location as a DSLO user only.  All material for the
DSLO user 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.
ENVIRONMENT FEATURES:  The customer order must include either or both
of the IMS/VS or CICS/OS/VS environment features, depending on how
the customer plans to use the product.  To order the environment
features, select the appropriate additional feature numbers.  The
environment feature charge numbers must correspond to the base
feature charge number.  (For example: if feature number 4626
(one-time charge) is specified for the basic license, either or both

of the environment features #4587 (one-time charge) or #4589
(one-time charge) must be selected to get the IMS/VS and/or
CICS/OS/VS support.)
o   To order an IMS/VS environment feature, specify feature #4587 for
    basic one-time charge, #4588 for basic monthly license charge, or
    #6520 for DSLO one-time charge.
o   To order a CICS/OS/VS environment feature, specify feature #4589
    for basic one-time charge, #4590 for basic monthly license
    charge, or #6521 for DSLO one-time charge.
BASIC MACHINE-READABLE MATERIAL:  Consists of object modules, macros,
procs, DBDs, PSBs, MFS, Rules, JCL, and MFS.
       Specify the feature number of the desired distribution medium.
Basic license users must specify at least one feature number for the
base and at least one feature number for either the IMS/VS or
CICS/OS/VS environments.
                FEATURE      DISTRIBUTION
ENVIRONMENT      NUMBER         MEDIUM
Base              5327      9/1600 M tape
                  5328      9/6250 M tape
                  5329       3480 M tape
IMS/VS            6016      9/1600 M tape
                  6017      9/6250 M tape
                  6018       3480 M tape
CICS/OS/VS        6019      9/1600 M tape
                  6020      9/6250 M tape
                  6021       3480 M tape
UNLICENSED DOCUMENTATION:  The memo to users, program directory, and
one copy of the following publications are supplied automatically
with the basic machine-readable material:
o   Licensed Program Specifications (GH20-0006)
o   Installation Guide (SH20-6593)
LICENSED DOCUMENTATION:  The following licensed material will be
available from IBM Software Distribution by September 12, 1986.  To
order, contact your IBM marketing representative.  The first copy
will be supplied automatically with the basic machine-readable
material.  Use the 8xxx feature number to order additional copies for
a fee.
                      ORDER         ADDITIONAL COPIES
TITLE                 NUMBER          FEATURE NUMBER
Diagnosis Guide     LY20-6401*             8599
       * Contains IBM restricted materials.
TERMS AND CONDITIONS
LICENSING:  This program is licensed under the terms and conditions
of the Agreement for IBM Licensed Programs.
INSTALLATION OR LOCATION LICENSE APPLIES:  No.  A separate license is
required for each designated machine on which the licensed program
materials will be used except as otherwise provided by IBM.
USAGE LICENSE APPLIES:  No
EDUCATIONAL ALLOWANCE:  A 15% educational allowance toward eligible
license charges is available to qualifying institutions in accordance
with the Educational Allowance Amendment.  The educational allowance
may not be added to any other discount or allowance.
VOLUME DISCOUNT:  Volume discounting is available under the Volume
License Amendment (VLA) to Agreement for IBM Licensed Programs and
the Exhibit for Selected System/370 Licensed Programs.  The following
discount schedule applies for licenses obtained under the One-time
Charge option:
          QUANTITY OF ELIGIBLE                DISCOUNT
           LICENSED PROGRAMS                  PERCENT
                 5 - 9                             6
                10 - 14                            9
                15 - 19                           12
               20 or more                         15
       The VLA discount applies to both Basic and DSLO one-time
charge licenses.
       This program (5665-348) is included in Category E of the VLA
Exhibit.  The quantity may be combined with quantities of other
programs in the same Category of the Exhibit to determine the
applicable discount.
       For further information regarding volume orders, contact your
IBM marketing representative.
WARRANTY:  Yes
LICENSED PROGRAM MATERIALS AVAILABILITY:  Restricted Materials:  No.
This licensed program will be available without source licensed
program materials.  It will be available in object code.
TESTING PERIOD:  Basic License - Two months.  DSLO - Not applicable.
PROGRAM SERVICES:  Central Service, including the IBM Support Center,
will be available until discontinued by IBM upon twelve months
written notice.  Central Service, including the IBM Support Center,
for DSLO licenses will be provided through the customer location
designated for the basic license.
       Local licensed program support is available under the terms
and conditions of the Agreement for Local Licensed Program Support
for IBM Licensed Programs at the monthly licensed program support
charge or monthly multiple licensed program support charge, or will
be provided at the applicable IBM Hourly Service rate.
PROGRAM CURRENCY:  Program Services previously announced for IMSADF
II Version 2 Release 1 will be available until September 15, 1987.
CHARGES
                                             MONTHLY
                              ONE-TIME       LICENSE
DESCRIPTION                   CHARGE         CHARGE
Base Product
     Basic:                  $33,000          $1,650
     DSLO:                    24,750
IMS/VS Environment
Feature
     Basic:                   21,890           1,100
     DSLO:                    16,410
CICS/OS/VS Environment
Feature
     Basic:                   21,890           1,100
     DSLO:                    16,410
                                                      MONTHLY
                               MONTHLY                MULTIPLE
                               LICENSED               LICENSED
                               PROGRAM                PROGRAM
                               SUPPORT                SUPPORT
                                CHARGE                 CHARGE
Local Program Support
     Base Product                $200                   $320
ONE-TIME CHARGE (OTC):  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 for a separate charge.  If a new version is
announced and the customer elects to license the new version for a
one-time charge and replace the prior version, an upgrade charge may
apply.