Announcement Letter Number 287-459 dated October 20, 1987
US - Last Revised on October 20, 1987

Brief Description of Announcement, Charges, and Availability

       CICS/VM is a new member of the CICS family of products.
Together with other VM supported functions, CICS/VM provides a
transaction processing capability designed to satisfy the needs of
integrated, multi-functional departmental systems.  CICS/VM is
intended for distributed VM systems where users characteristically
require the capability to perform a wide range of tasks, such as
decision support and office systems as well as commercial transaction
processing, from a single workstation.  Usability and smooth
transition between applications is key.  Systems in this distributed
environment are intended to be managed from a central location.  Use
of existing central site systems and application programming skills
minimizes the need for these skills at the distributed location.
       This announcement provides information on the first two
releases of CICS/VM.
       Monthly License Charge:  $1,500
       Graduated One-Time Charges (OTC):
      PROCESSOR             GRADUATED
        GROUP                  OTC
          10                $18,000
          20                 31,500
          30                 45,000
          40                 72,000
       Planned Availability:
o   May 1988 (Release 1)
o   First quarter 1989 (Release 2)

Customer Letter Section

o   Transaction processing for the VM environment
o   CICS command level API
o   Host connectivity
o   Local and remote data support
o   Logging, backout and recovery
o   System and application support
       The CICS/VM product will support the above highlights in two
closely timed releases.
       CICS/VM provides this support in a manner compatible with the
CICS/VS and CICS/MVS products, where this does not conflict with the
requirements for integration and the VM system design.
       CICS/VM is implemented in the VM/CMS environment and does not
operate as a subsystem in the same sense as CICS/VS or CICS/MVS.  End
users logging on to VM/CMS may execute a variety of applications,
including CICS/VM transactions.  CICS/VM applications can be invoked
in the same way as any other application under CMS and, where
possible, use VM system services.  CICS/VM is one of an integrated
set of CMS-based services.  In general, the end user will not
perceive direct use of a CICS/VM system.
       The following identifies whether function is included in
Release 1 or Release 2, as appropriate.  Where no distinction is
made, the function is available in both releases.
new product that provides a transaction processing capability for the
VM environment where multiple functions, such as office and business
professional facilities, are required in a fully integrated system.
CICS/VM is based on, and is compatible with, CICS/VS and CICS/MVS.
CICS/VM is designed to run under VM/SP; however, it is expected that
CICS/VM will be used mainly as an integral part of a VM/IS system
providing the wide range of function needed in this integrated
       The first release of CICS/VM has a basic level of integration
with VM/IS.  The support for central management of distributed
systems is not present.  It is intended to provide the capability to
plan and develop systems and applications for the integrated
environment.  This will be done at the central host site, using the
system and application programming skills already available.  These
skills should also be available at distributed sites during the
establishment of the pilot production systems.
With the availability of CICS/VM Release 2, there will be additional
integration with VM/IS enhancing capabilities for the management,
control, and maintenance of the distributed CICS/VM systems from the
central host site.  By using existing systems and applications skills
from the central host location, individual distributed sites do not
require a technical support staff.  A network of many distributed
CICS/VM systems can be supported from one central host, with a
minimal increase in personnel and skills being required.
       Users of the distributed system are likely to be non-data
processing people who require an easy-to-use system.  Since the
technical support can be accomplished remotely from the central host
location, skills required at the distributed sites are kept to a
minimum.  End-user tasks may include turning the equipment on and off
and, if required, operating a local printer.  Using VM facilities,
system messages and information are routed to a customer-defined
central location for processing by the support staff.  The end user
will be able to make use of the facilities of CICS/VM to perform
transaction processing using both local data and data kept at the
central site.  In addition, the user can make use of the wide variety
of other CMS functions available within this integrated VM
       On systems where CICS/VM has been ordered as a standalone
product to run on a VM/SP system, the integration and remote
management will be available only if additional VM products are
CICS/VM supports a rich subset of the command level Application
Programming Interface (API) of the CICS/VS and CICS/MVS products,
thus providing, at source program level, the capability to port
applications from the host to the distributed system, and vice versa.
       The CICS/VM API provides functional capability including local
SQL/DS data base support, File Control, extra partition transient
data, temporary storage, interval control, Basic Mapping Support
(BMS) and built-in functions.  Support is provided for the subset of
3270 type terminals supported by the VM operating system.  CICS/VM
commands, which, via the VM spool, enable output to be directed to
any printer supported by the VM operating system.  Some functions of
the CICS API are not supported, either because the underlying
operating system support does not exist in VM, or because the
function is not appropriate to the VM environment.
       The CICS/VM translator will detect API statements that are not
supported by CICS/VM and notify the user.  Applications containing
these statements will not compile.
       A complete list of the API supported by CICS/VM will be
published in the CICS/VM Application Programming manual (SC33-0570).
NOTE:  CICS/VM does not support the CICS macro level API, so existing
applications that use the macro level API will need to be converted
before they can be ported to, and used on, a CICS/VM system.
Host connectivity is key to the establishment of a central site with
distributed sites subordinate to it.
       In CICS/VM Release 1 access to CICS function at the host is
provided as a 3270 session to the host and uses VM dial facilities.
IBM provides a sample EXEC with CICS/VM, which can be used to
initiate this session as required.  This connection is transparent to
both the user and the application program.  In Release 1, this is a
bisynchronous connection.
       In CICS/VM Release 2 the implementation of this access is
changed to use SNA LUTYPE6.2 protocols and VTAM.  This connection is
also transparent to the user as well as application programs.
       CICS/VM Releases 1 and 2 permit function shipping only from
the distributed CICS/VM system to its CICS/VS or CICS/MVS host site.
Transaction routing, function shipping from the host to the
distributed CICS/VM system and CICS/VM to CICS/VM communication is
not supported.
A wide range of data access is supported by CICS/VM, allowing user
application programs to access both local and remote data.
       Local data can be stored in SQL/DS data bases or VSAM files.
       SQL/DS data may be accessed using EXEC SQL commands and may be
shared by CICS/VM applications and non-CICS CMS applications running
under CMS.
       Access to shared VSAM files is available through a file server
(a virtual machine that handles data requests) provided by CICS/VM.
VSAM files are accessed using the appropriate file control statements
of the CICS/VM API.  Only applications using CICS/VM file control
statements may concurrently share these VSAM files.
       Multiple VSAM file servers may be implemented.
       CICS/VM can access remote host data contained in VSAM or BDAM
files using CICS/VM API file control requests or in DL/I data bases
accessible to a CICS/VS or CICS/MVS system using the CALL or EXEC DLI
interfaces.  This access is provided through the CICS and
communications facilities described under HOST CONNECTIVITY.
CICS/VM provides dynamic logging for backout recovery facilities in
much the same way as CICS/VS and CICS/MVS.
       Logging for transaction backout is provided for local shared
VSAM files by the CICS/VM file server.  Dynamic Transaction Backout
will be performed following a transaction ABEND, and during emergency
restart if the server should ABEND.
       SQL/DS data integrity is ensured through the use of CICS
SYNCPOINT, either issued explicitly by the application, or implicitly
in the case of abnormal termination.
       In CICS/VM Release 2, support for temporary storage

(auxiliary) and extra partition transient data is added, both of
which are recoverable.  This requires SQL/DS.
       Update with full integrity on a local SQL/DS data base, or on
VSAM files under the control of a single file server is supported.
Integrity of host data is maintained by the host CICS/VS or CICS/MVS
       In the same Logical Unit of Work (LUW), a CICS/VM transaction
may update local or remote files; however, if both are updated in a
single LUW, data integrity may not be maintained if a server fails
during SYNCPOINT processing.
CICS/VM provides a wide range of support for the application
programmer.  The capabilities include support compatible with CICS/VS
and CICS/MVS, with the addition of some items appropriate to the VM
environment.  This support includes:
o   Translate and compile facilities
o   Translate time verification and diagnosis of the CICS/VM API
o   BMS map generation and test support
o   A debug capability
o   Runaway task detection.
       A CICS transaction executing in a CMS virtual machine will not
cause other virtual machines, or the CICS/VM file servers, to fail,
even if it contains program errors.
       CICS/VM provides for the system programmer in several ways:
o   Definition of resources (local and remote files and queues, local
    programs and remote DL/I data bases) is done by editing a CMS
    file containing fixed format statements.  CICS/VM provides
    samples of all resource definition statements.  In Release 2, a
    panel-driven interface is provided for this.  Centrally created
    definition files can be ported to the distributed nodes, where,
    if required they can be tailored to meet specific needs.
           Definition of terminal tables is not required.  Terminal
    definition and control is provided through the VM operating
           Since CICS/VM users are in fact CMS users, CICS functions,
    such as master terminal and other operation support commands, are
    performed using VM operator commands.  Some additional commands
    are provided, for example, to inquire and control the VSAM
o   CICS/VM Release 2, when used within a VM/IS configuration can be
    installed, serviced and managed from a central site.  In addition
    the system programmer will be able to perform problem
    determination activities from a customer selected central
       The following basic publications are shipped with the program.
TITLE                                                 NUMBER
CICS/VM Release 1 Licensed Program
  Specifications                                      GC33-0572
CICS/VM System Support and
  Administration                                      SC33-0573
CICS/VM Application Programming                       SC33-0570
CICS/MVS 2.1 Application Programmer's
  Reference                                           SC33-0512
       CICS/VM General Information (GC33-0571) and CICS/MVS 2.1
Application Programmer's Reference (SC33-0512) will be available from
IBM by December 1987.  To order, contact your IBM representative.
       Additional copies of the remaining basic publications will be
available after product availability.
       SLSS is available by order number or by product number.
       Education will be provided by Marketing and Customer
Education.  Additional information will be provided at product
       Planned availability is May 1988 for Release 1, and first
quarter 1989 for Release 2.
MACHINE REQUIREMENTS:  CICS/VM requires the following minimum system
o   A System/370 processor that supports the VM/SP operating system
    identified below
o   DASD to support the CICS/VM requirements, which will vary
    dependent upon user needs.  As a guide, DASD requirements for
    CICS/VM Release 1 are:
    1.  Installation of CICS/VM -- 10MB
    2.  Storage per application -- 2-10KB
    3.  Storage per user -- 15KB.
           The DASD requirements for CICS/VM Release 2 will be
    provided at availability of CICS/VM Release 2.
           The requirements for storage for applications and users
    are for guidance only.  Users should evaluate their requirements
    and adjust the above numbers to reflect the needs of their own
o   A minimum of one 3270 protocol compatible 1920-character display
    station with at least 12 program function keys
o   Any direct access storage device supported by the operating
o   Any magnetic tape drive supported by the operating system is
    required for installation and maintenance.
o   If access to host data is required, a PVM connection (bisync) to
    the host is needed with CICS/VM Release 1.  The ability to use
    VM/VTAM in CICS/VM Release 2 removes this requirement.
PROGRAMMING REQUIREMENTS:  IBM recommends ordering CICS/VM as a part
of VM/IS (5664-301).  With VM/IS planned to be available May 1988,
other VM products required for an integrated system are obtained at
the same time in an easy-to-install package.
       CICS/VM will also be available as a standalone product.  When
ordered as a standalone product, the prerequisite products listed
below are required for CICS/VM Release 1:
NOTE:  The VM products required to provide the fully integrated VM/IS
equivalent environment are not included as prerequisites in the list
o   VM/SP Release 5 (5664-167) with or without the High Performance
    Option (HPO)
           CICS/VM will also run on subsequent releases or
    modifications of the above operating system unless otherwise
    stated.  CICS/VM does not run on earlier releases of the above
    operating system.
o   Structured Query Language/Data System (SQL/DS) Version 2
    (5688-004), or later, is required for relational data base
o   VSE/VSAM Version 1 Release 3 (5746-AM2), or later, is required
    for local file control support.
o   If CICS/VM function shipping is used to access CICS/VS or
    CICS/MVS on a processor other than the local VM system,
    VM/Pass-Through Facility Version 1 Release 2 or 3 (5748-RC1) is
    required.  If use of the 3270 Extended Data Stream is required
    then VM/Pass-Through Facility Release 3 must be installed.
o   Function shipping to CICS/VS or CICS/MVS requires one of the
    following programs running in the remote processor:
    -   CICS/MVS Version 2 Release 1 (5665-403)
    -   CICS/OS/VS Version 1 Release 7 (5740-XX1)
    -   CICS/DOS/VS Version 1 Release 7 (5746-XX3)
o   CICS/VM supports applications written for the following
    -   VS COBOL II Compiler and Library, Release 2 (5668-958)
           Note:  CICS/VM does not support the national language
    facilities provided by this release.
    -   OS/VS COBOL Compiler and Library, Version 1 Release 2
        Modification Level 4 (5740-CB1)
    -   PL/I Optimizing Compiler and Libraries, Release 4 or 5
    -   The Assembler component of VM/SP
    -   Assembler H Version 2 Release 1 (5668-962)
o   If use of SDF is desired, SDF II Release 1 (5664-307) is
o   If access to DL/I data at a remote CICS/VS or CICS/MVS system is
    required, CICS/VM supports DL/I calls, through both the CALL and
    EXEC DLI interfaces, to the following:
    -   IMS/VS Version 1 Release 3 (5740-XX2)
    -   IMS/VS Version 2 Release 1 (5665-332), or later
    -   DL/I DOS/VS Version 1 Release 7 Modification Level 1
NOTE:  Running under the control of CICS/VS or CICS/MVS.
       The software requirements for CICS/VM Release 2 will be
broadly similar to those for Release 1.  Detailed information will be
provided in a later announcement.
COMPATIBILITY:  Applications developed to run on CICS/VM are

generally source compatible with CICS/DOS/VS, CICS/OS/VS and
CICS/MVS, provided they use the CICS/VM command level API and do not
depend on internal control block structures or make use of native VM
interfaces.  CICS/VM applications requiring VS COBOL II cannot be
ported to a CICS/DOS/VS system.  Applications developed for
CICS/DOS/VS, CICS/OS/VS and CICS/MVS are generally source compatible
with CICS/VM if they use only the subset of the CICS command level
API supported by CICS/VM.  Applications written in OS/VS COBOL or
Assembler are portable between CICS/DOS/VS and CICS/VM if, in
addition, they use only the common subsets of these languages.
       BMS maps are also source compatible using BMS macros.
       Users are able to develop applications at the central site for
distributed users using existing CICS products and skills, and port
them to the distributed sites for use, and vice versa.  For SQL/DS
applications in CICS/VM Release 1, the SQL/DS prepare step must be
performed on the system on which the application will run so the
resulting access module may be stored in the data base.  Applications
that are ported must be translated and compiled on the target
operating system.
       Applications developed on CICS/VM Release 1 will run unchanged
on Release 2 without the need for re-translation or re-compilation.
       The CICS macro level application programming interface is not
supported by CICS/VM, either for translation or execution.
       CICS/VM is an integrated offering that runs in the VM/CMS
Systems Application Architecture environment.  This permits the
intermixing of elements of Systems Application Architecture Common
Programming Interfaces, such as SQL, with interfaces provided by
LIMITATIONS:  CICS/VM is designed for use in distributed operations
where the need is for a transaction processing capability to be
available to end users as one option in an integrated system.  In
this environment usability is the key requirement.
       CICS/VM  will  provide a high degree of compatibility with the
CICS/VS and CICS/MVS products.  CICS/VM  operates in an integrated
rather than a dedicated environment, hence system constraints differ.
CICS/VM is not a recommended migration target for existing CICS/VS or
CICS/MVS installations.  Rather, CICS/VM will be used to add a new
distributed capability, or as a means to off-load work from a central
site.  It is expected that CICS/VM will form a complementary
transaction processing capability within an enterprise beside the
existing CICS/VS and CICS/MVS products.
       If CICS/VM and CICS/CMS are both installed on the same
processor, any single virtual machine will require a re-IPL of CMS
after using either product before using the other to ensure, for
example, that CMS nucleus extensions are removed.
PERFORMANCE CONSIDERATIONS:  The performance of CICS/VM is dependent
on the capabilities of the processor it is running on, the function
being used, and the other applications being run simultaneously on
that processor.  CICS/VM will have a greater requirement for CPU and
real memory resources than that of CICS/VS or CICS/MVS for equivalent
       The performance of CICS/VM is affected by its integration with
the VM operating system.  For example:
o   The use of VM facilities for CICS/VM terminal control results in
    an increase in path length, but allows integration with other VM
o   The different implementation of shared data access in a VM
    environment when compared to that of other CICS environments.
       Users requiring a higher transaction throughput should
consider use of the CICS/VS or CICS/MVS products.
CUSTOMER RESPONSIBILITIES:  It is recommended that CICS/VM release 1
is installed at the central site on a 937X processor, where it can be
used to develop the applications and design and implement the
controls needed for the initial distributed systems.  This can be
done using the central site skills and resource with no impact on the
planned end users.  With the availability of Release 2, CICS/VM can
be installed at the central location, and then under the control of
this site, be ported with the required applications to the remote
       CICS/VM may be installed as a Discontiguous Shared Segment
(DCSS) either as a part of the installation or afterwards.  The
customer should refer to the CICS/VM System Support and
Administration Manual (SC33-0573) to determine the most appropriate
INSTALLABILITY:  CICS/VM is designed to be easy to install.  The
installation process is EXEC and panel driven, with no requirements
for complex table definition or system generation activity.
       For planning purposes a user virtual machine size of 2
Megabytes should be used.  Further information will be found in the
CICS/VM System Support and Administration Manual (SC33-0573).  If
CICS/VM is installed as a DCSS, then a virtual machine size of 1
Megabyte is needed.
PACKAGING:  CICS/VM will be supplied on 1600 bpi or 6250 bpi tapes,
or on 3480 tape cartridges for installation and can be loaded with
INSTFPP.  For customers who do not use INSTFPP, instructions for
loading the tape are included in the CICS/VM System Support and
Administration Manual (SC33-0573).
o   One tape at 1600 bpi OR
o   One tape at 6250 bpi OR
o   One 3480 tape cartridge.
       A library of publications is automatically shipped with the
       Security of access to the CICS/VM system is under the control
of the VM operating system, with access controlled by logon and
minidisk passwords.  If installed, VM/RACF, can be used for this
       Security within CICS/VM is concerned with the control of data
access.  This is done at two levels, associated with the CICS/VM
o   Installation defined routines can validate user authority before
    the connection to a server is completed.  Further information is
    given in the CICS/VM System Support and Administration Manual
o   For files only, a check is made on each file control request
    against installation defined tables.  These tables define the
    read/write access to files.
       When executing a transaction under CICS/VM its resources may
be controlled by a resource manager such as individual local file
servers, SQL/DS, CICS/VS or CICS/MVS.  If the CICS logical unit of
work requires update of resources, then, to ensure integrity of the
data, only the resources managed by a single resource manager may be
updated within a single logical unit of work.
       User management is responsible for evaluation, selection, and
implementation of security features, administrative procedures, and
appropriate controls in application systems and communication
       Ordering information will be provided at program availability.
LICENSING:  CICS/VM is licensed under the terms and conditions of the
Agreement for IBM Licensed Programs.
GRADUATED CHARGES AMENDMENT APPLIES:  Yes, for licenses obtained for
a graduated one-time charge.
license is required for each designated machine on which the licensed
program materials will be used except as otherwise provided by IBM.
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
Procurement Amendment (VPA) for Machines and Programs and the VPA
Exhibit for Graduated Charges.  CICS/VM (5684-011) is in Categories
G72, H72, J72 and K72.  The following discount schedule applies for
licenses obtained under the Graduated One-Time Charge option.
                            DISCOUNT PERCENT
  MINIMUM      GROUP 10   GROUP 20      GROUP 30  GROUP 40
  CATEGORY       G72        H72           J72       K72
     3           20%        10%           10%       10%
     5           25%        15%           15%       15%
     10          30%        20%           20%       20%
     20          35%        25%           25%       25%
       The VPA category specified must correspond to the processor
group applicable to the machines on which the programs will run.
       Only programs with the same category (for example, G72) may be
aggregated to determine the applicable discount percent.
       Processor group upgrades are not eligible for volume
       Volume discounting applies to both Basic and DSLO one-time
charge licenses.
WARRANTED:  Basic license:  Yes.  DSLO:  Not applicable.
This licensed program will be available with source licensed program
material for some modules designated as RESTRICTED MATERIALS OF IBM.
In addition, some modules will be available without source licensed
program materials.  These modules 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 six months written
       Central Service, including the IBM Support Center, for DSLO
licenses will be provided only through the customer location
designated for the basic license.
                  BASIC        DSLO
                 $1,500      $1,125
                  BASIC        DSLO
      GROUP        OTC         OTC
        10      $18,000     $13,500
        20       31,500      23,625
        30       45,000      33,750
        40       72,000      54,000
ONE-TIME CHARGE:  Customers who pay a graduated or non-graduated
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 a optional feature and charged for
separately.  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.
GRADUATED CHARGES:  The applicable graduated one-time charge will be
based on the processor group of the designated machine on which the
licensed program is licensed for use.  The charge for processor group
upgrades will be the difference in the current charges between the
two groups.  Licenses for which the customer has paid a graduated
one-time charge may be redesignated to a processor in the same
processor group or a lower processor group.  There will be no
adjustment or refund for processor group downgrades.

Contact IBM