Software Announcement 299-108
May 4, 1999

IBM MERVA ESA Version 4 and MERVA ESA Components Version 4 Begin a New Era for Financial Message Processing

 ENUS299-108.PDF (81KB)


At a Glance

MERVA ESA Version 4 provides:

  • Usage of DB2 for message queuing
  • TCP/IP support for MERVA Link and the connection to the client
  • Performance improvements
  • Enablement of Sysplex exploitable subsystems
  • MQI attachment under VSE/ESA
  • 7x24 support, except for customization

The MERVA ESA Components product combines all additional features as part of a single product to simplify ordering:

  • MERVA USE and Branch for Windows NT with and without SWIFT Link
  • MERVA message processing client for Windows NT
  • MERVA import/export facility for Windows NT
  • MERVA Connection/400 and Connection/NT features
  • Directory Services support as a direct extension to MERVA ESA (MVS™)
  • Traffic reconciliation as a direct extension to MERVA ESA (MVS)

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

A Strategic Solution for Connecting Financial Institutions

MERVA ESA provides message processing and funds transfer functions used primarily in the finance industry. It includes network links to the SWIFT II and Telex networks and to other MERVA installations. Data formats for other network connections can be added. User applications can use the services of the MERVA products via the Application Programming Interface (API) and sequential batch interfaces.

The MERVA ESA Components product combines all the additional MERVA ESA features into a single product for easy ordering.

Together, MERVA ESA Version 4 and MERVA ESA Components Version 4 form IBM's strategic solution for the interconnection of financial institutions. They replace and improve on MERVA ESA Version 3 and the elements of the MERVA family connected to it.

Key Prerequisites

The mainframe based elements of MERVA Version 4 run on any IBM System/390® computer with OS/390® (and IMS™ or CICS®) or VSE (with CICS). Optionally, DB2® is supported for message queuing.

The workstation based elements run on Intel based PCs with Windows NT® Version 4.

Planned Availability Dates

  • MERVA ESA: December 17, 1999
  • MERVA ESA Components:
    • Workstation based parts: June 25, 1999
    • Mainframe based parts: March 31, 2000

Description

MERVA ESA is a scalable software product used to set up and operate financial messaging systems in an isolated or enterprise-wide environment. It is used by financial institutions around the world to:

  • Access financial networks (such as SWIFT and Real-Time-Gross Settlement [RTGS] networks) from a financial institution
  • Access financial networks from a global enterprise perspective
  • Create a service bureau for various network users
  • Interconnect branches within an enterprise
  • Set up an RTGS interconnecting financial institutions
  • Synchronize remote multipurpose applications

It is the high level of interoperability of MERVA installations that has been most valued by users around the world when setting up enterprise-wide financial messaging systems.

MERVA can be considered middleware software whose main purpose is to interconnect financial applications with financial networks. The product architecture is based on the capability to transfer a message

  • from one point to another in real-time
  • in a very secure and highly reliable way
  • while providing
    • guaranteed delivery
    • full transaction integrity
    • scalable performance

This functionality is used mostly by financial institutions to transfer high-value payments around the world.

MERVA ESA and its components run on various software platforms:

Operating           Transaction
System              Monitor              Database
 
OS/390              CICS                 VSAM, DB2
OS/390              IMS                  VSAM, DB2
VSE                 CICS                 VSAM, DB2
Windows NT          N/A                  UDB

MERVA product functionality is based on a set of common services plus individual functions that are needed for certain environments. The functionality of MERVA ESA can be extended by adding optional MERVA product features from the MERVA Components Version 4 product.

Message queuing and routing provides MERVA users the capability to define a message flow in which, for example, payments are routed from one person (or one application) to another in a process in which several consecutive steps (which are driven by conditions) must be followed. In the case of a payment, these steps can be, for example:

  • Creating the payment
  • Verifying the payment
  • Correcting the payment
  • Authorizing the payment
  • Releasing the payment

Message queuing and routing is the basic functionality of MERVA. Messages are stored in logical queues in indexed or relational database tables (such as VSAM or IBM's Universal Data Base/IBM DB2). These messages are then routed from one queue to another queue based on predefined routing conditions.

Queue definition is very flexible. There is no restriction in the number of queues on a certain implementation. Furthermore, queues can be on the same system or on distant MERVA systems, allowing users to establish a cross-system or even a cross-country messaging infrastructure.

Routing definition is also extremely flexible. Messages can be routed from any queue to any other queue without restriction. Routing can be conditional or unconditional.

Message formatting allows users to adapt MERVA to the different message types used by the external networks and therefore keep the existing applications independent of external message types (which constantly change).

Network interfaces give MERVA users the capability to have one channel to manage all external connections to financial networks (such as S.W.I.F.T., Telex, and RTGS systems like EAF, SIC, and MAS). MERVA offers standard network interfaces and permits users to customize those that are specific for a user or a country environment.

The standard network interfaces available with MERVA are:

  • SWIFT Link
  • MERVA-to-MERVA Link
  • MERVA-MQI Attachment

For MERVA Link a sophisticated message integrity protocol guarantees that no message is lost or duplicated during transfer. For the MERVA-MQI Attachment MQ™ Series ensures the message integrity. Standard communication protocols such as SNA and TCP/IP are supported. Security features optionally encrypt and authenticate the message to be transferred.

Telex and Fax network interfaces are provided by connecting first to specialized Telex and Fax products.

Message processing functions provide users all necessary tools to better manage and control the flow of messages. Those functions are:

  • Audit logging
  • Archiving
  • Printing
  • Security functions
  • Monitoring

Message processing can be performed on existing 3270 screens (or via emulator) and on an optionally attached MERVA Message Processing Client.

Operation services allow all users to customize, administer, and run the MERVA system on a daily basis:

  • Customization services allow users to define all MERVA control data, such as the message type definition, queue definition, routing conditions, network link specifications, printer formats, display formats, and user interface.
  • Administration services help users to define and manage system user access rights, connection links, security keys, log files, and so on. MERVA's global administration capabilities allow you to:
    • Centrally manage SWIFT security keys. All those keys are received at a central level, entered into the system, then distributed and fully managed electronically. There is no longer a need for card reader devices at the branch level.
    • Centrally monitor all connection links and all server states.
  • Operation services allow users to operate the MERVA system on a daily basis by ensuring continuous processing and reorganizing files.

Application interfaces enable users to interconnect MERVA to existing and future financial applications. The interfaces are:

  • An Application Programming Interface (API), which allows you to:
    • Read and write messages to and from internal queues
    • Route messages from one queue to another
    • Reformat messages
    • Check the syntax of SWIFT messages
    • Execute operator commands
  • User exits.
  • Connectivity features, which allow you to extend the MERVA API (on the workstation, for example, of MERVA USE and Branch) across systems. Therefore, financial applications can reside on remote AS/400® or Windows NT based systems. All other IBM and non-IBM systems can be connected to MERVA using the integrated MQI Attachment.

MERVA ESA Components Version 4

This software product provides the following features:

  1. MERVA USE and Branch (with and without SWIFT Link)

    MERVA USE and Branch and MERVA USE and Branch with SWIFT Link consist of the following components:

    • MERVA Base, which includes:
      • Secure Login and Select (SLS).
      • Bilateral Key Exchange (BKE). The BKE service enables the user to automatically generate the bilateral keys necessary for the authentication of financial messages.
      • An API to allow you to develop your own applications and to handle Telex messages.
      • Message queuing and routing as described for MERVA ESA.
    • Message processing functions, allowing you to:
      • Display and print the diagnosis log.
      • Start or stop the automatic printing of messages.
      • Load messages from and unload messages to an external file (using API programs).
      • Purge messages according to the date.

      All other message processing functions are performed through the MERVA Message Processing Client.

    • MERVA Link.
    • SWIFT Link (MERVA USE and Branch with SWIFT Link only).
    • Telex. MERVA USE and Branch and MERVA USE and Branch with SWIFT Link provide API services to care for Telex messages. The Telex messages can then be forwarded to a Telex station. The Telex station handles all the Telex network-related functions, and can also act as a stand-alone Telex.
  2. MERVA Message Processing Client

    The MERVA Message Processing Client provides a common graphical user interface for MERVA Server Systems (MERVA ESA, MERVA USE and Branch with or without SWIFT Link) for message processing functions. The MERVA Client runs on any Windows NT workstation connecting to the MERVA Server through the TCP/IP protocol or APPC LU 6.2 (CPIC) protocol.

    The functionality covers navigation through all MERVA message queues authorized for this user in addition to standard message processing functions in a state of the art GUI. The MERVA Client provides the following message processing functions:

    • Message creation. For each SWIFT message type, panels are displayed for the entry of data in the various fields. Checking is carried out on all fields, and cross-field checks are provided where appropriate. Similar to the host functions, address expansion, list selection, and detailed help are provided.
    • Message verification. Verification requires that fields displayed without data must be retyped with the same information as originally entered.
    • Message authorization. Either one or two authorization steps can be specified for messages prior to being sent to the appropriate network.
    • Message editing. Correction of messages that were, for example, incorrectly verified can be carried out using this function.
    • Message displaying, printing, and deleting. Messages are retrieved based on the specified search criteria (for example, transaction reference number or message number) for display, print, and/or deletion.
    • Template handling. Form messages can be saved as templates for later retrieval, update, and processing.

    The MERVA Client provides the same security as the server for users performing functions on the client. For example, the user must be authorized for the functions he wishes to perform, for the queues he want to access, or for the message types he wants to work with.

  3. Connection Features (NT and OS/400®)

    The Connection/400 and Connection/NT features allow you to extend the MERVA API of MERVA USE and Branch across systems. This allows financial applications residing on remote AS/400 or Windows NT based systems to be connected to MERVA USE and Branch or MERVA USE and Branch with SWIFT Link (and from there via MERVA-to-MERVA Connection to MERVA ESA).

    To use Windows NT applications as banking applications on a different system than the one MERVA USE and Branch is running on, messages created on the other system must be transferred to the MERVA system. Messages received from one of the networks must be transferred from the MERVA system to the other Windows NT system.

    MERVA Connection/NT provides an interface for application programs on another Windows NT system. It is called the Remote MERVA API. Using the Remote MERVA API, an application on Windows NT can be created to send messages to MERVA and receive messages from MERVA with a minimum effort.

  4. MERVA Import/Export Feature

    The MERVA Automatic Message Import/Export Facility consists of:

    • The automatic message import process. This process searches in a specified directory for message files. Message files that are found are transferred to a specific message queue.
    • The automatic message export process. A specific MERVA message export queue triggers this process. Messages that are found are transferred to message files of a specific directory.
    • Import/export process profiles. These process profiles allow you to customize the import/export queues, routing conditions, and message directories.

    Message Transfer: Message transfer can be performed in different ways. Because many products have a file transfer interface, message transfer between MERVA and other message-processing products is done through files.

    Files can be exchanged through:

    • Local disk if the message-processing products run on the same machine.
    • Global Local Area Network (LAN) drives if the message-processing products run on different PCs but on a common LAN.
    • Diskettes if the message-processing products run on different stand-alone workstations.

    With the MERVA Automatic Message Import/Export Facility you can automatically:

    • Export messages of different types into message files of different formats.
    • Import message files of different formats into messages of different types.

    The MERVA Automatic Message Import/Export Facility also offers you:

    • Recovery function.

      Messages are not lost and are not transferred twice. If an import or export process is abended during a transfer process, the transfer is completed after the next restart of the transfer process.

    • Multiple processing.

      Several import and export transfers between different directories and queues can be performed at the same time. A separate process profile contains the transfer parameters and the process identification for each process. The respective process owns these process profiles.

  5. MERVA Directory Services Feature

    S.W.I.F.T.'s Standing Settlements Instructions/Foreign Exchange (SSI/FX) Directory service enables financial institutions to hold and manage an in-house SSI/FX database to help achieve Straight-Through-Processing (STP). MERVA ESA Directory Services enables users to fully integrate SSI/FX data on an IBM host to be used by user application programs.

    The complete SSI/FX database is stored on IBM's Universal Data Base/IBM DB2 on the same environment as MERVA ESA. The data is automatically updated by incoming and outgoing SWIFT messages and fully managed by MERVA ESA Directory Services.

  6. Traffic Reconciliation Feature

    The Traffic Reconciliation Feature allows an organization to:

    • Create daily lists of SWIFT traffic activity
    • Analyze online whether SWIFT/Telex messages have been acknowledged or delivered
    • Process online customer inquiries on messages sent
    • Have a standard tool for message post-processing
    • Track all the activities executed upon a message from when it was created to when it was transmitted
    • Monitor the message exchange with remote MERVA systems
    • Generate reports on the message traffic to a specific correspondent

    The Traffic Reconciliation Feature provides a set of six event monitors:

    • The SWIFT Link — all incoming and outgoing messages from and to the SWIFT network.
    • The Telex Link — all Telex messages sent and received.
    • The MERVA Link — all messages exchanged with other MERVA systems through an intra- or inter-banking network.
    • The MERVA queue management — put-off messages into MERVA queues or delete-off messages from such queues.
    • The MQI Attachment — all incoming and outgoing messages from and to the MQ Series based network.
    • The MERVA journal — logging of all important and security sensitive events to provide a valuable information source for audit, administrative, and management purposes. Each of the six monitors has the capability to intercept and extract data from MERVA and insert that data into a DB2 table. This whole process is done in real-time mode and in parallel with the operation in MERVA. This provides continuous up-to-date message traffic data.

Year 2000

These products are Year 2000 ready. When used in accordance with their associated documentation, they are 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 products properly exchange accurate date data with them.

Euro Currency

These programs are EuroReady.

Product Positioning

MERVA ESA and MERVA ESA Components form IBM's strategic solution for the interconnection of financial institutions, especially via the S.W.I.F.T. network and intranets. They are System/390 products with distributed components on Intel based PCs running Windows NT. Connectivity is reached through APIs, a specific MERVA Link component, and an integrated MQ interface.

Hardware and Software Support Services

SmoothStart™/Installation Services

IBM Installation Services are provided for MERVA Version 4 by IBM Global Services or your IBM Business Partner at an additional cost. For additional information, contact your IBM representative and ask for Installation Services for MERVA Version 4.

Trademarks

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

Education Support

Visit the following Web site for additional information concerning education:

In addition, contact your IBM representative for course information.

Technical Information

Specified Operating Environment

Hardware Requirements

MERVA ESA Version 4 will run native on all processors that are supported by OS/390® or VSE/ESA. The required size of processors depends on the operating system type. It also depends on whether the data communication system used to control the operating of MERVA ESA Version 4.1 is CICS/ESA®, CICS/VSE®, or IMS/ESA®. Files accessed by MERVA ESA Version 4.1 must reside on either a tape device or DASD. There is no known device type within these categories that can be operated under MVS/ESA™ or OS/390 but would not be supported by MERVA ESA Version 4.

The dialog function can be used from any display terminal supported and operated by IMS/ESA, CICS/ESA, or CICS/VSE.

Message processing functions can also be performed via the MERVA Message Processing Client for Windows NT®.

If MERVA ESA Version 4.1 dialog functions are going to be used to display or enter data in the DBCS character set, a terminal of the 5550 family of display terminals is required.

Operator messages are issued via standard WTO macros in single- and multi-line format. MERVA ESA Version 4.1 responses to a display subcommand are in table format and require a message length of at least 70 characters.

The basic requirement (minimal configuration) is to have a host CPU connected to a teleprocessing network.

Additional Machine Requirements for the SWIFT Link

The connection to the SWIFT network using X.25 requires one Communication Controller of Type 3720, 3725, or 3745, LIC type 1 (max. 19200 pbs) or LIC type 3. Physical connections to the S.W.I.F.T. network require LIC type 1 (EIA RS 232 or CCITT V.24) or type 3 (CCITT V.35) in 37xx controllers.

Note that the Communication Controllers 3746-900 and 3746-950 are not supported. However, a 3746-900 is always connected to a 3745 controller, which can be used.

Switched (PSTN) connections to the SWIFT network require a modem that supports manual dialing, DTR dialing, or V.25 bis dialing (for 3745 only). A V.25 capable modem allows MERVA ESA controlled automatic dialing and is recommended to ensure most integrated customization and processing.

A direct-access storage device compatible with the operating system is used for SWIFT Link data sets.

Alternatively and/or as a backup function the component MERVA USE and Branch with SWIFT Link (see below) can be used.

Additional Machine Requirements for the MERVA Link

The connection between the host processor and another MERVA ESA system, a MERVA USE and Branch system, or a system running MERVA USE and Branch with SWIFT Link requires one of the following network control facilities:

  • An IBM 37xx Communication Controller
  • An Integrated Communication Adapter (ICA)

MERVA-to-MERVA Connection between MERVA ESA and MERVA USE and Branch (with or without SWIFT Link) is described under MERVA ESA Components Version 4.

Additional Machine Requirements for the Workstation Based Functions of MERVA ESA

The machine requirements for using the workstation based functions S.W.I.F.T. USE, Telex network connection via workstation, MERVA USE and Branch, and MERVA USE and Branch with SWIFT Link are described under MERVA ESA Components Version 4.

MERVA ESA Components Version 4

  1. MERVA USE and Branch and MERVA USE and Branch with SWIFT Link

    MERVA USE and Branch and MERVA USE and Branch with SWIFT Link will run native on all Intel-compatible processors that are supported by Windows NT.

    Files accessed by these components must reside on an NTFS filesystem.

    Dialog functions can be used from any terminal supported and operated by Windows NT.

    The estimated minimum machine requirements are:

    • Intel Pentium™ processor, 166 MHz or higher
    • 96 MB of RAM (128 MB recommended)
    • 4 GB of available disk space, on an NTFS-formatted drive
    • A CD-ROM drive for installation
    • A diskette drive (software keys will be delivered on a diskette)
    • Screen resolution of 1024 x 768 pixels or higher

    To perform the S.W.I.F.T. USE functionality, in addition to above requirements, the following are needed:

    • A Basic (BCR) and/or Secure (SCR) card reader as required by S.W.I.F.T.
    • An asynchronous port on the workstation for each connected SCR or BCR
    • 5 MB of disk space for each 3,000 correspondents

    Additional Machine Requirements for Multi-User Support

    MERVA's Multi-User support is implemented using Microsoft™ Windows™ Terminal Server. For each additional user the memory should be increased by 20 MB of RAM.

    Additional Machine Requirements for the MERVA Connectivity

    MERVA Link, the remote MERVA family clients, and the connection features support the interconnection of MERVA systems within an SNA network using LU 6.2 services or a TCP/IP network (except Connection/400). So one of the network control facilities supporting such a communication method is required (for example, an IBM 37xx communication controller), along with a networking interface card on the PC, for example an ATM or SDLC card.

    Additional Machine Requirements for the SWIFT Link

    The connection to the SWIFT network using the X.25 protocol requires the following:

    • ARTIC X.25 Interface CoProcessor Adapter (PCI or ISA bus).
      • Public Switched Telephone Network (PSTN) connections to the S.W.I.F.T. network require a cable and a modem that supports V.25 bis dialing. A V.25 bis capable modem allows IBM MERVA ESA Components Version 4 Release 1 controlled automatic dialing and is recommended to ensure most integrated customization and processing.
      • Device driver: IBM ARTIC Support for Windows NT.
      • X.25 software: IBM ARTIC Support for X.25 Windows NT.
    • Encryptor box Secure X.25 provided by S.W.I.F.T. The encryptor box from S.W.I.F.T. can be used between the computer and the modem. This encryptor box is optional for PSTN connections, but mandatory for PSPDN connections.
  2. Message Processing Client
    • Processor: Any workstation that runs under Windows NT Version 4.0 or a subsequent release. A Pentium with 133 MHz or an equivalent processor is recommended.
    • RAM: 32 MB RAM or more is needed.
    • Disk space: The program files require approximately 30 MB of disk space.
    • Printer: Any printer supported by Windows NT.
    • Interface device: Any interface device supported by the end user communication software (for example, Token Ring Card or SDLC Adapter for remote connections).

  3. Connection/400

    The Connection/400 feature runs on an AS/400® system connected to MERVA USE and Branch or MERVA USE and Branch with SWIFT Link via SNA. MERVA Connection/400 can communicate with MERVA USE and Branch and MERVA USE and Branch with SWIFT Link. PC hardware requirements can be found in the section for MERVA USE and Branch.

  4. Connection/NT

    Connection/NT is supported on any system running Windows NT 4.0.

    The remote MERVA API Client can be installed on any Windows NT system with approximately one megabyte of free space on its hard disk.

  5. MERVA Import/Export Feature

    MERVA Import/Export Facility for Windows NT is supported on any system running Windows NT 4.0.

    The following machine requirements are needed to install the MERVA Automatic Message Import/Export Facility for Windows NT:

    • Any workstation that runs under Windows NT Version 4.0 or a subsequent release
    • 16 MB or more RAM and 20 MB or more additional hard disk space
  6. MERVA Directory Services Feature

    The MERVA Directory Services Feature runs on the same system as MERVA ESA.

  7. Traffic Reconciliation Feature

    The Traffic Reconciliation Feature runs on the same system as MERVA ESA.

Software Requirements

MERVA ESA

The following control programs and subsystems are required for MERVA ESA Version 4 Release 1. However, it will run also on subsequent releases or modification levels unless otherwise stated.

Operating System

  • VSE/ESA Version 2 Release 3 or higher (5690-VSE)
  • OS/390 Version 2 Release 4 or higher (5647-A01)

Database and Communications Systems

  • CICS/VSE Version 2 Release 3 (5686-026)
  • CICS/ESA Version 4 (5685-018)
  • IMS/ESA Version 5 (5695-176)

For VSE/CICS®, the HL Assembler for VSE (5696-234) is also required.

Additional Program Requirements for the SWIFT Link

For the IBM 37xx Communications Controller one of the following NCPs is needed:

  • ACF/NCP Version 4 (5668-854) Release 3.1 (MVS™ and VSE)
  • ACF/NCP Version 5 (5668-738) Release 4 (MVS and VSE)
  • ACF/NCP Version 6 (5688-231) Release 1, 2, or 3 (MVS only)
  • ACF/NCP Version 7 (5648-063) Release 1, 2, 3, 4, 5, 6, or 7 (MVS and VSE)

In addition, IBM MERVA Extended Connectivity for ESA Version 3 Release 2 is needed:

  • MERVA Extended Connectivity for MVS/ESA Version 3 Release 2 (5655-110)
  • MERVA Extended Connectivity for VSE/ESA Version 3 Release 2 (5686-080)

Additional Program Requirements for the MERVA Link

This network connection is required for implementation of the S.W.I.F.T. USE functions on either a PC or an RS/6000™. For communication between MERVA systems one of the following is required:

  • ACF/VTAM® VSE Version 3 Release 1.1 (5666-313)
  • ACF/VTAM Version 3 Release 4 (5685-085) for MVS/ESA

Together with:

  • ACF/NCP Version 4 (5668-854) Release 3.1 (MVS and VSE)
  • ACF/NCP Version 5 (5668-738) Release 4 (MVS and VSE)
  • ACF/NCP Version 6 (5688-231) Release 1, 2, or 3 (MVS only)
  • ACF/NCP Version 7 (5648-063) Release 1, 2, 3, 4, 5, 6, or 7 (MVS and VSE)

Additional Program Requirements for TCP/IP Based Attachment for MERVA Message Processing Client under VSE

  • TCP/IP for VSE/ESA Version 1 Release 3 (5686-A04)

Additional Program Requirements if DB2® Is to Be Used

For OS/390:

  • DB2 for OS/390 Version 5 Release 1 (5655-DB2)

For VSE:

  • DB2 for VM and VSE Version 5 Release 1 (5648-158)

Additional Program Requirements for the MQI Attachment and the Inter-Service Communication between Multiple MERVA ESA Instances

For OS/390:

  • MQSeries® for MVS/ESA Version 1 Release 2 (5695-137)

For VSE/CICS:

  • MQSeries for VSE/ESA Version 2 Release 1 (5686-A06)
  • ACF/VTAM for VSE/ESA Version 4 Release 2 (5666-363) or TCP/IP for VSE/ESA Version 1 Release 3 (5686-A04)
  • Language Environment (LE) for VSE Runtime Library Version 1 Release 4 (5696-067)

MERVA ESA Components Version 4 Release 1

  1. MERVA USE and Branch and MERVA USE and Branch with SWIFT Link

    Operating System

    MERVA USE and Branch and MERVA USE and Branch with SWIFT Link are based on Microsoft Windows NT 4.0, Service Pack Level 4, US English. They also run on subsequent releases or modification levels of this operating system, unless otherwise stated.

    License Management

    MERVA USE and Branch expects the License Use Management program product iFOR/LS Version 4.0.1 using the software key capability.

    Database System

    • DB2 Universal Database® Workgroup Edition Version 5.2, Service Pack Level 9084 and subsequent releases

    Communications Systems

    • The SNA support is based on the availability of:
      • Personal Communication Version 4.2, and subsequent releases, or
      • IBM eNetwork™ Communications Server for Windows NT Version 6.0

      Examples will be described for the IBM eNetwork Communication server.

      SNA must be started as a Windows NT Service. The service must run under a user account other than System Account . The users access control list must contain the MERVA user group (for example, umerva1).

    • The TCP/IP support is based on the availability of TCP/IP, which is part of the Microsoft Windows NT 4.0 product.

    MERVA USE and Branch and MERVA USE and Branch with SWIFT Link also require the following software:

    • Object REXX Runtime Edition Version 1.0.2.3
    • Java™ Runtime Environment (JRE) Version 1.2

    Additional Program Requirements for Multi-User Support

    • Microsoft Windows Terminal Server, Terminal Server Edition

    Additional Program Requirements for the API

    MERVA USE and Branch and MERVA USE and Branch with SWIFT Link will support the C programming language to write application programs using the API functions. The following compilers are supported:

    • Visual Age for C++ for Windows Compiler Version 3.5.4
    • Microsoft Visual C++ 6.0

    Additional Program Requirements for the SWIFT Link

    • The SWIFT Link connection is based on IBM ARTIC Support for X.25 on Windows NT.
  2. MERVA Message Processing Client
    • Operating system: Microsoft Windows NT Version 4.0 with Fix Package 4, or a subsequent release is needed.
    • Communication software for remote connections:

      For SNA APPC:

      • IBM eNetwork Personal Communication Version 4.2 (5639-B94) or a subsequent release.
      • IBM eNetwork Communications Server for Windows NT Version 6.0 (5639-F25) or a subsequent release.

      For TCP/IP:

      • The TCP/IP support is incorporated in the Windows NT 4.0 operating system.
  3. Connection/400

    An LU 6.2 connection between Communications Server and OS/400® must be customized for the PC connection.

    MERVA Connection/400 requires an APPC LU 6.2 session between the PC and the AS/400. This can be achieved by Token Ring, SDLC, Twinax, and other types of connection for which Communications Manager SNA Server and OS/400 provide support for an LU 6.2 session. For a list of the alternatives available and the hardware required for each, refer to the appropriate books listed in the bibliography of the Connection/400 documentation (SH12-6340).

    Programs Required on the MERVA USE and Branch Side:

    • Communications Server, including the latest available Corrective Service Diskette (CSD) level, or a subsequent release

    Programs Required on the AS/400:

    • OS/400 Version 3.1, including the latest available Corrective Service Diskette (CSD) level, or a subsequent release
    • A compiler for one of the following languages:
      • IBM C/ILE
      • IBM RPG/ILE
      • IBM COBOL/ILE

    Note that EPM/OPM is not supported anymore. Only ILE is supported.

  4. MERVA Connection/NT

    The following software must be installed on the client side:

    • Windows NT 4.0.
    • Personal Communications for NT Version 4.2 or Communications Server for NT Version 6.0 or a subsequent release. The TCP/IP support is based on the availability of TCP/IP, which is part of the Microsoft Windows NT 4.0 product.
    • The C Compiler Visual Age for C++ 3.5.4.

    Personal Communications (or Server for NT) is required only if an SNA APPC connection is used for the communication between the Remote MERVA API Client and Server. Personal Communications is not required if a TCP/IP connection is used for that purpose; in this case TCP/IP must be installed on the Windows NT system. Communications Server for NT provides the same functionality as Personal Communications for NT and more. Whenever Personal Communications for NT is mentioned, Communications Server for NT is also sufficient for the task.

    The MERVA Connection/NT Client Application System and the MERVA Server System must be interconnected by a Data Communication Link. As specified by the used Data Communication Service (SNA APPC or TCP/IP), Token Ring, SDLC, Twinax, or other types of intersystem links can be used. A corresponding data link adapter must be installed in the Windows NT system.

  5. MERVA Import/Export Facility for Windows NT

    The following are required:

    • Windows NT Version 4.0 or a subsequent release of the operating system
    • MERVA USE and Branch or MERVA USE and Branch with SWIFT Link as a MERVA environment on the server
  6. Mainframe Based Features:

    The requirements are the same as already described for MERVA ESA including the requirement for a DB2 database, which is prerequisite for the MERVA Directory Services Feature and Traffic Reconciliation Feature.

    In addition the following is required for the MERVA Directory Services:

    • IBM Language Environment for MVS/VMS Version 1 Release 4 (5688-198).

Compatibility: MERVA ESA Version 4 is upwardly compatible with MERVA ESA Version 3.3.

The new MERVA USE and Branch and MERVA USE and Branch with SWIFT Link can be used with MERVA ESA Version 3.3 and MERVA ESA Version 4.

The SSI support feature can also be used with MERVA ESA Version 3.3.

MERVA USE and Branch and MERVA USE and Branch with SWIFT Link are upwardly compatible with MERVA USE and Branch OS/2® and MERVA OS/2 (LAN and Standalone). Migration aids allow easy migration.

Limitations: MERVA USE and Branch and MERVA USE and Branch with SWIFT Link do not support more than 20 MERVA Message Processing Clients.

Performance Considerations: In a Sysplex installation, the performance of MERVA ESA depends on the exploitation of Sysplex through the used subsystems.

User Group Requirements: This announcement satisfies or partially satisfies more than 50 requirements from one or more of the MERVA user group communities. Requirements satisfied include:

  1. Common Requirements

    AC4-0002       MERVA Link TCP/IP support
    AC7-0005       Unload messages based on a date filter
    AC8-0012       MERVA ESA Migration Documentation
    
  2. MERVA Requirements (toward existing products MERVA OS/2 and MERVA AIX®)

                   Availability of workstation based functions
                    on Windows NT
    DC8-0006       Increase the limit of 16 automatic print
                    queues to 999
    DC8-0007       Increase the limit of 99 print queues to
                    9999
    DC7-0006       Identification on MERVA panels
    DC7-0007       Increase limit of 400 routing names to
                    1024
    DC7-0009       DB2 reorg functionality provided by
                    MERVA
    DC7-0010       Show MRN after message creation
    DC7-0018       BIC expansion on printed messages
    DC7-0021       Expansion on message types
                   Increase the count of queue-management
                    attaches in parallel
                   Increase the number of target queues in
                    routing from 4 to 12
    
  3. MERVA ESA Requirements

    BC6-0006       MERVA Link customizable sub-pool
    BC6-0012       API: line-by-line printer output
    BC6-0013       Allow test commands in production
    BC6-0017       Display all pages for JRN command
    BC7-0002       DB2 with SWIFT SSI
    BC7-0003       Automatic line switching
    BC7-0016       Journal dataset switch
    BC7-0018       Re-Print Notification
    BC7-0022       SWIFT Link Help Menu
    BC7-0026       Protect imbedded part of messages
    BC7-0027       SWIFT Link Performance Improvements
    BC8-0005       High water mark for QDS
    BC8-0008       Sorted queue display
    BC8-0010       Provide DSLISYNP also for CICS
    BC8-0021       New Fields in MERVA ESA User File
    BC8-0022       More fields in DSLBA05B
    BC8-0028       EDIFACT mapping for MT 121
    
  4. Traffic Reconciliation Requirements

    BC7-1006       Deliver the Foreign Key Definitions
    BC7-1013       Utility for deletion of DB2-entries
    BC7-1015       Insert facility IMRI as batch program
    BC7-1018       Unload and deletion into a seq.file
    BC7-1023       Monitor MQI activities
    BC7-1025       Spec. of queue names in IMRPRM
    BC7-1026       Add columns to FINOMIR and FINOHDR
    BC7-1031       M-Link messages in FIN tables
    BC7-1032       Select a query by cursor
    BC7-1039       Online Help for Traffic Recon Msg and
                    Codes
    BC8-1001       PFK Layout with RECON Panels
    BC8-1006       Correct confusing text
    BC8-1007       Query Q001 TRN rather than MUR
    BC8-1010       Support SWIFT mixed upper and lower
                    case
    BC8-1011       Queries independent from CommLink
    

Planning Information

Installability: For the migration of the workstation based functions of MERVA ESA — be it locally attached to MERVA ESA or via MERVA-to-MERVA Connection in a different location — migration from IBM OS/2 to Microsoft Windows NT is required.

A migration guide and migration tools are available to help you perform this task.

Packaging: MERVA ESA is made available on tapes and cartridges for MVS and VSE. There is only one set of MVS material, regardless of whether MERVA ESA is to be installed with CICS or IMS™.

All Windows NT based features (MERVA USE and Branch, MERVA USE and Branch with SWIFT Link, MERVA Message Processing Client, MERVA Import/Export Facility for Windows NT, MERVA Connection/NT) will be made available on a single CD called MERVA ESA Components for Windows NT. A license key is needed to run the appropriate software.

It is the responsibility of the customer (supported by the IBM sales representative) to obtain the password from the source indicated in the program package(s).

System Integrity

IBM will accept APARs where the installation of MERVA ESA introduces an exposure to the system integrity of MVS. Refer to the MVS Integrity Software Announcement dated October 21, 1981. This program is intended to run unauthorized.

Security, Auditability, and Control

The security features of MERVA ESA V3 remain the same in MERVA ESA V4.1:

  • Password protection is used for end-user access to the MERVA ESA V4.1 system.
  • The signon to MERVA ESA and to the user file maintenance function can be controlled by an external security manager (ESM), for example RACF®. For MERVA ESA running under CICS/VSE, the signon functions can be controlled by the basic security manager (BSM) of VSE/ESA Version 2 Release 4.
  • Access to message processing functions is controlled by user file records.
  • MERVA ESA V4.1 defines and controls different user classes:
    • Operating: authorized and normal operators
    • File maintenance: display only, editing, and authorizing users
    • Message processing: data entry and authorizing users
  • The Authenticator Key File and the User File are scrambled and therefore not readable by other applications or users.
  • Message authentication is performed according to S.W.I.F.T. standards.
  • MERVA Link SNA APPC conversation security is completely handled by APPC/MVS.
  • MERVA Link provides a conversation security function in the TCP/IP environment.

The features currently provided are:

  • MERVA ESA V4 journal.
  • Reconciliation of messages via a relational database.
  • Security features of the SWIFT II network, implemented in MERVA ESA SWIFT Link according to the S.W.I.F.T. User Handbook.
  • In addition Version 4 provides a utility (DSLBA17R) to check the last sign-on date, last password change date, and last User File update date of all or specified users.

The security features of the Windows NT based features of MERVA ESA Components are:

  • Password protection is used for end-user access to MERVA USE and Branch and MERVA USE and Branch with SWIFT Link.
  • Access to MERVA USE and Branch and MERVA USE and Branch with SWIFT Link functions is controlled by user access rights.
  • The four-eyes principle can be used in message processing and in the User Administration task.
  • Data objects are protected by check values.
  • MERVA programs are controlled by file permission (execute).
  • The Authenticator Key File is handled according to SWIFT USE standards.
  • The User File is protected and therefore not readable by other applications or users.
  • Message authentication is performed according to SWIFT standards.

Auditability Considerations

The features currently provided are:

  • MERVA USE and Branch logging and trace files
  • The audit log database, containing records for the following when they occur on the MERVA USE and Branch system:
    • User events
    • Process events
    • Message flow events
    • Customization events
  • Security features of the S.W.I.F.T. network, implemented in MERVA USE and Branch and MERVA USE and Branch with SWIFT Link according to the S.W.I.F.T. User Handbook
  • Windows NT Event log for:
    • Fatal errors in MERVA Control Process (start/stop phase)
    • Trace entries of the self-written TCP/IP inetd daemon service
    • Fatal errors in the MERVA logging (for example, file system full condition)

The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.

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:

Ordering Information

New Licensees

Orders for new licenses can be placed now.

Shipment will begin on the planned availability date.

New users of MERVA ESA and MERVA ESA Components should specify:

         Type           Model
 
         5648           B29
         5648           B30

Basic License

  1. MERVA ESA (5648-B29). To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the basic feature and the feature numbers for the desired tier (usage level, that is, the number of messages processed in multiples of 10,000) and the number of copies requested in this tier. For example, to order usage within Tier 4, order incrementally by specifying tier 1 (quantity 1), Tier 2 with the full quantity (9), Tier 3 with the full quantity (90), and Tier 4 with the remaining number.

    Messages processed includes messages sent and received to/from the SWIFT network and the Telex network (if connected directly) but also messages processed through the FMT (Financial Message Transfer) facility.

    Specify the feature number of the desired distribution medium shown below.

    Base charge feature:  0029
     
    Usage charge features:
     
                                                 Basic
    Tier           Usage Level                   MLC
     
     1                  50 to    10,000          0030
     2              10,001 to   100,000          0031
     3             100,001 to 1,000,000          0032
     4           Greater than 1,000,000          0033
    

    Usage is counted per 10,000 messages processed per average month.

  2. MERVA ESA Components (5648-B30), usage based features. To order a basic license, specify the program number and feature number 9001 for asset registration. Specify the feature number of the usage based feature requested and the feature number for the desired tier (usage level) and the number of copies requested in this tier. For example, to order usage within Tier 3, order incrementally by specifying Tier 1 with the full quantity (5), Tier 2 with the full quantity (15), and Tier 3 with the remaining number. Specify the feature number of the desired distribution medium shown below.

    Note that the Annual Support Charge is required if OTC is chosen. It is to be billed annually.

    • MERVA USE and Branch

                                                           Annual
                                       Basic     Basic     Support
      Tier             Usage Level     MLC       OTC       Charge
       
       1               1 to   5        0072      0080      0084
       2               6 to  20        0073      0081      0085
       3       Greater than  20        0074      0082      0086
      

      Usage is counted per copy installed.

    • MERVA USE and Branch with SWIFT Link

                                                           Annual
                                       Basic     Basic     Support
      Tier             Usage Level     MLC       OTC       Charge
       
       1               1 to   5        0056      0064      0068
       2               6 to  20        0057      0065      0069
       3       Greater than  20        0058      0066      0070
      

      Usage is counted per copy installed.

    • MERVA Message Processing Client

                                                           Annual
                                       Basic     Basic     Support
      Tier             Usage Level     MLC       OTC       Charge
       
       1               1 to   5        0040      0048      0052
       2               6 to  20        0041      0049      0053
       3       Greater than  20        0042      0050      0054
      

      Usage is counted per copy installed.

  3. MERVA ESA Components (5648-B30), flat per use features.

                                                                  Annual
                                                Basic    Basic    Support
    Feature                       Platform      MLC      OTC      Charge
     
    Connection/NT                 Windows NT    0028     0029     0030
    Connection/400                OS/400        0031     0032     0033
    MIE/NT                        Windows NT    0037     0038     0039
    Directory                     OS/390        0034     0035     0036
     Services
    Traffic                       OS/390        0025     0026     0027
     Reconciliation
    

Basic Machine-Readable Material

  1. MERVA ESA (5648-B29).

                                         Feature     Distribution
    Description          Environment     Number      Medium
     
    Base Product         MVS             5812        3480 Cartridge
    Base Product         MVS             6671        4-mm Cartridge
    Base Product         MVS             5811        6250 bpi Tape
    Base Product         VSE             5802        3480 Cartridge
    Base Product         VSE             6955        4-mm Cartridge
    Base Product         VSE             5801        6250 bpi Tape
    
  2. MERVA ESA Components (5648-B30). Basic material does not apply; only optional features are available for this product.

Customization Options: 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
 
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)
 
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 Fulfillment (SDF) receives the order. SDF will then ship the order via overnight air transportation.

Optional Machine-Readable Material: To order, select the feature number for the desired distribution medium:

  1. MERVA ESA (5648-B29). No optional material is available for this product. All features are to be ordered through MERVA ESA Components (5648-B30).
  2. MERVA ESA Components (5648-B30).

                                                  Feature  Distribution
    Description                      Environment  Number   Medium
     
    MERVA NT Based Components
    MERVA USE and Branch             Windows NT   5869     CD-ROM
    MERVA USE and Branch - Key       Windows NT   3020     Diskette
    MERVA NT Based Components
    MERVA USE and Branch             Windows NT   5869     CD-ROM
     with SWIFT Link
    MERVA USE and Branch             Windows NT   3010     Diskette
     with SWIFT Link - Key
    MERVA NT Based Components
    Connection/NT                    Windows NT   5869     CD-ROM
    Connection/400                   OS/400       5804     QIC120
    Connection/400                   OS/400       5905     8-mm Tape
    MERVA NT Based Components
    MERVA MIE/NT                     Windows NT   5869     CD-ROM
    MERVA MIE/NT - Key               Windows NT   3040     Diskette
    MERVA NT Based Components
    MERVA Message Processing         Windows NT   5869     CD-ROM
     Client
    MERVA Message Processing         Windows NT   3030     Diskette
     Client - Key
    MERVA Directory Services         MVS          5812     3480 Cartridge
    MERVA Directory Services         MVS          6956     4-mm Cartridge
    MERVA Directory Services         MVS          5821     6250 bpi Tape
    MERVA Traffic Reconciliation     MVS          5802     3480 Cartridge
    MERVA Traffic Reconciliation     MVS          6957     4-mm Cartridge
    MERVA Traffic Reconciliation     MVS          5831     6250 bpi Tape
    

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

Documentation for MERVA ESA Version 4 Release 1 (5648-B29)

                                                  Order
Title                                             Number
 
MERVA ESA Licensed Specifications                 GH12-6973
MERVA ESA Advanced MERVA Link                     SH12-6390
MERVA ESA API Guide                               SH12-6374
MERVA ESA Operations Guide                        SH12-6375
MERVA ESA User's Guide                            SH12-6376
MERVA ESA Macro Reference                         SH12-6377
MERVA ESA Installation Guide                      SH12-6378
MERVA ESA Messages and Codes                      SH12-6379
MERVA ESA Customizing Guide                       SH12-6380
MERVA ESA Concepts and Components                 SH12-6381
MERVA ESA Diagnosis Guide                         SH12-6382
MERVA ESA System Programming Guide                SH12-6366
MERVA Documentation CD                            SK2T-9752-01

Documentation for MERVA ESA Version 4 Release 1 Components (5648-B30)

 
Title                                             Number
 
MERVA ESA Components -- Licensed                  GH12-6333
 Programming Specifications
MERVA ESA Workstation Based Functions             SH12-6383(1)
MERVA USE and Branch for Windows NT               SH12-6334
 -- User's Guide
MERVA Use and Branch -- Application               SH12-6336
 Programming Guide
MERVA USE and Branch -- Installation              SH12-6335
 and Customization Guide
MERVA USE and Branch -- Diagnosis                 SH12-6337
 Guide
MERVA USE Administration Guide                    SH12-6338
MERVA Message Processing Client                   SH12-6341
 User's Guide
MERVA Connection/NT                               SH12-6339
MERVA Connection/400                              SH12-6340
MERVA Automatic Message                           SH12-6389
 Import/Export Facility User's Guide
MERVA Documentation CD                            SK2T-9752-00
MERVA ESA Directory Services                      SH12-6367(2)
MERVA ESA Traffic Reconciliation                  SH12-6392(2)

Notes:

1
Available with MERVA ESA V4: December 17, 1999
2
Available with the ESA based features: March 31, 2000

Additional copies of unlicensed publications are available for a fee after availability. These copies may be ordered from your IBM representative, through the Publication Notification System (PNS), or by direct order.

Displayable Softcopy Publications: MERVA manuals are offered in displayable softcopy form. All unlicensed manuals are included. The displayable manuals are part of the basic machine-readable material and available as the no-charge order number SK2T-9752. The files are shipped on CD-ROM.

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.

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

Agreement: IBM Customer Agreement

Variable Charges Apply: No

Indexed Monthly License Charge (IMLC) Applies: No

Location License Applies: No

Use Limitation Applies: Yes, per number of messages processed for MERVA ESA, and number of copies installed for MERVA USE and Branch, MERVA USE and Branch with SWIFT Link, and MERVA Client.

Note that messages sent and received over the S.W.I.F.T. network on an attached MERVA USE and Branch with SWIFT Link are to be added to the number calculated for the central MERVA ESA installation. Additional features, or authorizations, as appropriate must be obtained to extend use levels.

Additional licenses or features, as appropriate, must be obtained to exceed usage limits.

Educational Allowance Available: Yes, to qualified education customers.

Volume Orders: Not applicable

Version-to-Version Upgrade Credits Apply: No

                                                         Single
Replaced Programs         Replacement Programs           Version
Program    Program        Program     Program            Charging
Number     Name           Number      Name               Applies
 
5655-039   MERVA ESA      5648-B29    MERVA ESA          Yes
                                       4.1
 
5655-040   MERVA ESA      5648-B29    MERVA ESA          Yes
                                       4.1
 
5686-063   MERVA ESA      5648-B29    MERVA ESA          Yes
                                       4.1

Warranty Applies: 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
  • Available until Discontinued: Six months' written notice

Trademarks

 
MVS/ESA, MVS, RS/6000, eNetwork, and IMS are trademarks of International Business Machines Corporation in the United States or other countries or both.
 
OS/390, CICS/ESA, CICS/VSE, IMS/ESA, AS/400, CICS, ACF/VTAM, DB2, MQSeries, DB2 Universal Database, OS/400, OS/2, AIX, RACF, and BookManager are registered trademarks of International Business Machines Corporation in the United States or other countries or both.
 
Pentium is a trademark of Intel Corporation.
 
Microsoft and Windows are trademarks of Microsoft Corporation.
 
Windows NT is a registered trademark of Microsoft Corporation.
 
Java is a trademark of Sun Microsystems, Inc.
 
Other company, product, and service names may be trademarks or service marks of others.