Software Announcement May 4, 1999



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

Overview Key Prerequisites At a Glance A Strategic Solution for Connecting The mainframe based elements of Financial Institutions MERVA Version 4 run on any IBM MERVA ESA Version 4 provides:  System/390 computer with • MERVA ESA provides message OS/390 (and IMS or CICS ) or Usage of DB2 for message processing and funds transfer VSE (with CICS). Optionally, DB2 queuing functions used primarily in the is supported for message queuing. • TCP/IP support for MERVA Link finance industry. It includes network and the connection to the client links to the SWIFT II and Telex The workstation based elements run networks and to other MERVA on Intel based PCs with • Performance improvements installations. Data formats for other Windows NT Version 4. network connections can be added. • Enablement of Sysplex User applications can use the exploitable subsystems services of the MERVA products via Planned Availability Dates • MQI attachment under VSE/ESA the Application Programming Interface (API) and sequential batch • MERVA ESA: December 17, 1999 • 7x24 support, except for interfaces. • MERVA ESA Components: customization The MERVA ESA Components − Workstation based parts: The MERVA ESA Components product combines all the additional June 25, 1999 product combines all additional MERVA ESA features into a single features as part of a single product product for easy ordering. − Mainframe based parts: to simplify ordering: March 31, 2000 Together, MERVA ESA Version 4 and • MERVA USE and Branch for MERVA ESA Components Version 4 Windows NT with and without form IBM′s strategic solution for the SWIFT Link interconnection of financial • institutions. They replace and MERVA message processing improve on MERVA ESA Version 3 client for Windows NT and the elements of the MERVA • MERVA import/export facility family connected to it. 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.

This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: http://www.ibm.com.

IBM United States IBM is a registered trademark of International Business Machines Corporation. 299-108 Queue definition is very flexible. There is no restriction Description in the number of queues on a certain implementation. Furthermore, queues can be on the same system or on MERVA ESA is a scalable software product used to set distant MERVA systems, allowing users to establish a up and operate financial messaging systems in an cross-system or even a cross-country messaging isolated or enterprise-wide environment. It is used by infrastructure. financial institutions around the world to: Routing definition is also extremely flexible. Messages • Access financial networks (such as SWIFT and can be routed from any queue to any other queue without Real-Time-Gross Settlement [RTGS] networks) from a restriction. Routing can be conditional or unconditional. financial institution Message formatting allows users to adapt MERVA to the • Access financial networks from a global enterprise different message types used by the external networks perspective and therefore keep the existing applications independent • Create a service bureau for various network users of external message types (which constantly change). • Interconnect branches within an enterprise Network interfaces give MERVA users the capability to have one channel to manage all external connections to • Set up an RTGS interconnecting financial institutions financial networks (such as S.W.I.F.T., Telex, and RTGS systems like EAF, SIC, and MAS). MERVA offers standard • Synchronize remote multipurpose applications network interfaces and permits users to customize those It is the high level of interoperability of MERVA that are specific for a user or a country environment. installations that has been most valued by users around The standard network interfaces available with MERVA the world when setting up enterprise-wide financial are: messaging systems. • SWIFT Link MERVA can be considered middleware software whose • MERVA-to-MERVA Link main purpose is to interconnect financial applications with • MERVA-MQI Attachment financial networks. The product architecture is based on the capability to transfer a message For MERVA Link a sophisticated message integrity protocol guarantees that no message is lost or duplicated • from one point to another in real-time during transfer. For the MERVA-MQI Attachment MQ • in a very secure and highly reliable way Series ensures the message integrity. Standard • while providing communication protocols such as SNA and TCP/IP are − guaranteed delivery supported. Security features optionally encrypt and − full transaction integrity authenticate the message to be transferred. − scalable performance Telex and Fax network interfaces are provided by This functionality is used mostly by financial institutions connecting first to specialized Telex and Fax products. to transfer high-value payments around the world. Message processing functions provide users all MERVA ESA and its components run on various software necessary tools to better manage and control the flow of platforms: messages. Those functions are: Operating Transaction • Audit logging System Monitor Database • Archiving • Printing OS/390 CICS VSAM, DB2 • Security functions OS/390 IMS VSAM, DB2 • Monitoring VSE CICS VSAM, DB2 Windows NT N/A UDB Message processing can be performed on existing 3270 screens (or via emulator) and on an optionally attached MERVA product functionality is based on a set of common MERVA Message Processing Client. services plus individual functions that are needed for certain environments. The functionality of MERVA ESA Operation services allow all users to customize, can be extended by adding optional MERVA product administer, and run the MERVA system on a daily basis: features from the MERVA Components Version 4 product. • Customization services allow users to define all Message queuing and routing provides MERVA users the MERVA control data, such as the message type capability to define a message flow in which, for example, definition, queue definition, routing conditions, network payments are routed from one person (or one application) link specifications, printer formats, display formats, to another in a process in which several consecutive and user interface. steps (which are driven by conditions) must be followed. • In the case of a payment, these steps can be, for example: Administration services help users to define and manage system user access rights, connection links, • Creating the payment security keys, log files, and so on. MERVA′s global • Verifying the payment administration capabilities allow you to: • Correcting the payment − Centrally manage SWIFT security keys. All those • Authorizing the payment keys are received at a central level, entered into • Releasing the payment the system, then distributed and fully managed Message queuing and routing is the basic functionality of electronically. There is no longer a need for card MERVA. Messages are stored in logical queues in reader devices at the branch level. indexed or relational database tables (such as VSAM or − ′ Centrally monitor all connection links and all server IBM s Universal Data Base/IBM DB2). These messages states. are then routed from one queue to another queue based on predefined routing conditions.

299-108 -2- • Operation services allow users to operate the MERVA Telex station handles all the Telex network-related system on a daily basis by ensuring continuous functions, and can also act as a stand-alone Telex. processing and reorganizing files. 2. MERVA Message Processing Client Application interfaces enable users to interconnect MERVA to existing and future financial applications. The The MERVA Message Processing Client provides a interfaces are: common graphical user interface for MERVA Server Systems (MERVA ESA, MERVA USE and Branch with • An Application Programming Interface (API), which or without SWIFT Link) for message processing allows you to: functions. The MERVA Client runs on any Windows NT workstation connecting to the MERVA Server − Read and write messages to and from internal through the TCP/IP protocol or APPC LU 6.2 (CPIC) queues protocol. − Route messages from one queue to another The functionality covers navigation through all − Reformat messages MERVA message queues authorized for this user in addition to standard message processing functions in − Check the syntax of SWIFT messages a state of the art GUI. The MERVA Client provides the following message processing functions: − Execute operator commands • Message creation. For each SWIFT message type, • User exits. panels are displayed for the entry of data in the • Connectivity features, which allow you to extend the various fields. Checking is carried out on all fields, MERVA API (on the workstation, for example, of and cross-field checks are provided where MERVA USE and Branch) across systems. Therefore, appropriate. Similar to the host functions, address financial applications can reside on remote AS/400 expansion, list selection, and detailed help are or Windows NT based systems. All other IBM and provided. non-IBM systems can be connected to MERVA using • Message verification. Verification requires that the integrated MQI Attachment. fields displayed without data must be retyped with the same information as originally entered. MERVA ESA Components Version 4 • Message authorization. Either one or two This software product provides the following features: authorization steps can be specified for messages prior to being sent to the appropriate network. 1. MERVA USE and Branch (with and without SWIFT • Link) Message editing. Correction of messages that were, for example, incorrectly verified can be MERVA USE and Branch and MERVA USE and Branch carried out using this function. with SWIFT Link consist of the following components: • Message displaying, printing, and deleting. • MERVA Base, which includes: Messages are retrieved based on the specified search criteria (for example, transaction reference − Secure Login and Select (SLS). number or message number) for display, print, − Bilateral Key Exchange (BKE). The BKE service and/or deletion. enables the user to automatically generate the • Template handling. Form messages can be saved bilateral keys necessary for the authentication as templates for later retrieval, update, and of financial messages. processing. − An API to allow you to develop your own The MERVA Client provides the same security as the applications and to handle Telex messages. server for users performing functions on the client. − Message queuing and routing as described for For example, the user must be authorized for the MERVA ESA. functions he wishes to perform, for the queues he want to access, or for the message types he wants to • Message processing functions, allowing you to: work with. − Display and print the diagnosis log. 3. Connection Features (NT and OS/400 ) − Start or stop the automatic printing of The Connection/400 and Connection/NT features allow messages. you to extend the MERVA API of MERVA USE and − Load messages from and unload messages to Branch across systems. This allows financial an external file (using API programs). applications residing on remote AS/400 or Windows NT based systems to be connected to MERVA USE − Purge messages according to the date. and Branch or MERVA USE and Branch with SWIFT Link (and from there via MERVA-to-MERVA All other message processing functions are Connection to MERVA ESA). performed through the MERVA Message Processing Client. To use Windows NT applications as banking • applications on a different system than the one MERVA Link. MERVA USE and Branch is running on, messages • SWIFT Link (MERVA USE and Branch with SWIFT created on the other system must be transferred to Link only). the MERVA system. Messages received from one of the networks must be transferred from the MERVA • Telex. MERVA USE and Branch and MERVA USE system to the other Windows NT system. and Branch with SWIFT Link provide API services to care for Telex messages. The Telex messages MERVA Connection/NT provides an interface for can then be forwarded to a Telex station. The application programs on another Windows NT system. It is called the Remote MERVA API. Using the

-3- 299-108 Remote MERVA API, an application on Windows NT SSI/FX data on an IBM host to be used by user can be created to send messages to MERVA and application programs. receive messages from MERVA with a minimum effort. The complete SSI/FX database is stored on IBM′s Universal Data Base/IBM DB2 on the same 4. MERVA Import/Export Feature environment as MERVA ESA. The data is automatically updated by incoming and outgoing The MERVA Automatic Message Import/Export SWIFT messages and fully managed by MERVA ESA Facility consists of: Directory Services. • The automatic message import process. This 6. Traffic Reconciliation Feature process searches in a specified directory for message files. Message files that are found are The Traffic Reconciliation Feature allows an transferred to a specific message queue. organization to: • The automatic message export process. A specific • Create daily lists of SWIFT traffic activity MERVA message export queue triggers this process. Messages that are found are transferred • Analyze online whether SWIFT/Telex messages to message files of a specific directory. have been acknowledged or delivered • Import/export process profiles. These process • Process online customer inquiries on messages profiles allow you to customize the import/export sent queues, routing conditions, and message • Have a standard tool for message post-processing directories. • Track all the activities executed upon a message Message Transfer: Message transfer can be from when it was created to when it was performed in different ways. Because many products transmitted have a file transfer interface, message transfer between MERVA and other message-processing • Monitor the message exchange with remote products is done through files. MERVA systems Files can be exchanged through: • Generate reports on the message traffic to a specific correspondent • Local disk if the message-processing products run on the same machine. The Traffic Reconciliation Feature provides a set of six event monitors: • Global Local Area Network (LAN) drives if the message-processing products run on different PCs • The SWIFT Link — all incoming and outgoing but on a common LAN. messages from and to the SWIFT network. • Diskettes if the message-processing products run • The Telex Link — all Telex messages sent and on different stand-alone workstations. received. With the MERVA Automatic Message Import/Export • The MERVA Link — all messages exchanged with Facility you can automatically: other MERVA systems through an intra- or inter-banking network. • Export messages of different types into message files of different formats. • The MERVA queue management — put-off messages into MERVA queues or delete-off • Import message files of different formats into messages from such queues. messages of different types. • The MQI Attachment — all incoming and outgoing The MERVA Automatic Message Import/Export messages from and to the MQ Series based Facility also offers you: network. • Recovery function. • The MERVA journal — logging of all important and security sensitive events to provide a valuable Messages are not lost and are not transferred information source for audit, administrative, and twice. If an import or export process is abended management purposes. Each of the six monitors during a transfer process, the transfer is has the capability to intercept and extract data completed after the next restart of the transfer from MERVA and insert that data into a DB2 table. process. This whole process is done in real-time mode and • Multiple processing. in parallel with the operation in MERVA. This provides continuous up-to-date message traffic Several import and export transfers between data. different directories and queues can be performed at the same time. A separate process profile Year 2000 contains the transfer parameters and the process identification for each process. The respective These products are Year 2000 ready. When used in process owns these process profiles. accordance with their associated documentation, they are 5. MERVA Directory Services Feature capable of correctly processing, providing, and/or receiving date data within and between the twentieth and S.W.I.F.T.′s Standing Settlements Instructions/Foreign twenty-first centuries, provided that all products (for Exchange (SSI/FX) Directory service enables example, hardware, software, and firmware) used with the financial institutions to hold and manage an in-house products properly exchange accurate date data with SSI/FX database to help achieve them. Straight-Through-Processing (STP). MERVA ESA Directory Services enables users to fully integrate

299-108 -4- 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.

-5- 299-108 IBM US Announcement Supplemental Information

May 4, 1999

Switched (PSTN) connections to the SWIFT network Education Support require a modem that supports manual dialing, DTR dialing, or V.25 bis dialing (for 3745 only). A V.25 capable Visit the following Web site for additional information modem allows MERVA ESA controlled automatic dialing concerning education: and is recommended to ensure most integrated customization and processing. http://www.ibm.com/solutions/finance/merva/ A direct-access storage device compatible with the In addition, contact your IBM representative for course operating system is used for SWIFT Link data sets. information. Alternatively and/or as a backup function the component MERVA USE and Branch with SWIFT Link (see below) can Technical Information be used.

Specified Operating Environment Additional Machine Requirements for the MERVA Link The connection between the host processor and another Hardware Requirements MERVA ESA system, a MERVA USE and Branch system, or a system running MERVA USE and Branch with SWIFT MERVA ESA Version 4 will run native on all processors Link requires one of the following network control that are supported by OS/390 or VSE/ESA. The required facilities: size of processors depends on the operating system type. It also depends on whether the data communication • An IBM 37xx Communication Controller system used to control the operating of MERVA ESA • An Integrated Communication Adapter (ICA) Version 4.1 is CICS/ESA , CICS/VSE , or IMS/ESA . Files accessed by MERVA ESA Version 4.1 must reside MERVA-to-MERVA Connection between MERVA ESA and on either a tape device or DASD. There is no known MERVA USE and Branch (with or without SWIFT Link) is device type within these categories that can be operated described under MERVA ESA Components Version 4.  under MVS/ESA or OS/390 but would not be supported Additional Machine Requirements for the Workstation by MERVA ESA Version 4. Based Functions of MERVA ESA The dialog function can be used from any display terminal The machine requirements for using the workstation supported and operated by IMS/ESA, CICS/ESA, or based functions S.W.I.F.T. USE, Telex network connection CICS/VSE. via workstation, MERVA USE and Branch, and MERVA Message processing functions can also be performed via USE and Branch with SWIFT Link are described under the MERVA Message Processing Client for MERVA ESA Components Version 4.  Windows NT . MERVA ESA Components Version 4 If MERVA ESA Version 4.1 dialog functions are going to 1. MERVA USE and Branch and MERVA USE and Branch be used to display or enter data in the DBCS character with SWIFT Link set, a terminal of the 5550 family of display terminals is required. MERVA USE and Branch and MERVA USE and Branch with SWIFT Link will run native on all Intel-compatible Operator messages are issued via standard WTO macros processors that are supported by Windows NT. in single- and multi-line format. MERVA ESA Version 4.1 responses to a display subcommand are in table format Files accessed by these components must reside on and require a message length of at least 70 characters. an NTFS filesystem. The basic requirement (minimal configuration) is to have Dialog functions can be used from any terminal a host CPU connected to a teleprocessing network. supported and operated by Windows NT. Additional Machine Requirements for the SWIFT Link The estimated minimum machine requirements are: The connection to the SWIFT network using X.25 requires • Intel Pentium processor, 166 MHz or higher one Communication Controller of Type 3720, 3725, or • 3745, LIC type 1 (max. 19200 pbs) or LIC type 3. Physical 96 MB of RAM (128 MB recommended) connections to the S.W.I.F.T. network require LIC type 1 • 4 GB of available disk space, on an (EIA RS 232 or CCITT V.24) or type 3 (CCITT V.35) in 37xx NTFS-formatted drive controllers. • A CD-ROM drive for installation Note that the Communication Controllers 3746-900 and 3746-950 are not supported. However, a 3746-900 is • A diskette drive (software keys will be delivered always connected to a 3745 controller, which can be used. on a diskette) • Screen resolution of 1024 x 768 pixels or higher

This announcement is provided for your information only. For additional information, contact your IBM representative, call 800-IBM-4YOU, or visit the IBM home page at: http://www.ibm.com.

IBM United States IBM is a registered trademark of International Business Machines Corporation. 299-108 To perform the S.W.I.F.T. USE functionality, in addition 3. Connection/400 to above requirements, the following are needed: The Connection/400 feature runs on an AS/400 • A Basic (BCR) and/or Secure (SCR) card reader system connected to MERVA USE and Branch or as required by S.W.I.F.T. MERVA USE and Branch with SWIFT Link via SNA. MERVA Connection/400 can communicate with • An asynchronous port on the workstation for each MERVA USE and Branch and MERVA USE and Branch connected SCR or BCR with SWIFT Link. PC hardware requirements can be • 5 MB of disk space for each 3,000 correspondents found in the section for MERVA USE and Branch. Additional Machine Requirements for Multi-User 4. Connection/NT Support Connection/NT is supported on any system running MERVA′s Multi-User support is implemented using Windows NT 4.0. Microsoft Windows Terminal Server. For each The remote MERVA API Client can be installed on any additional user the memory should be increased by Windows NT system with approximately one 20 MB of RAM. megabyte of free space on its hard disk. Additional Machine Requirements for the MERVA 5. MERVA Import/Export Feature Connectivity MERVA Import/Export Facility for Windows NT is MERVA Link, the remote MERVA family clients, and supported on any system running Windows NT 4.0. the connection features support the interconnection of MERVA systems within an SNA network using The following machine requirements are needed to LU 6.2 services or a TCP/IP network (except install the MERVA Automatic Message Import/Export Connection/400). So one of the network control Facility for Windows NT: facilities supporting such a communication method is required (for example, an IBM 37xx communication • Any workstation that runs under Windows NT controller), along with a networking interface card on Version 4.0 or a subsequent release the PC, for example an ATM or SDLC card. • 16 MB or more RAM and 20 MB or more additional Additional Machine Requirements for the SWIFT Link hard disk space 6. MERVA Directory Services Feature The connection to the SWIFT network using the X.25 protocol requires the following: The MERVA Directory Services Feature runs on the • ARTIC X.25 Interface CoProcessor Adapter (PCI or same system as MERVA ESA. ISA bus). 7. Traffic Reconciliation Feature − Public Switched Telephone Network (PSTN) The Traffic Reconciliation Feature runs on the same connections to the S.W.I.F.T. network require a system as MERVA ESA. cable and a modem that supports V.25 bis dialing. A V.25 bis capable modem allows IBM Software Requirements MERVA ESA Components Version 4 Release 1 controlled automatic dialing and is MERVA ESA recommended to ensure most integrated customization and processing. The following control programs and subsystems are required for MERVA ESA Version 4 Release 1. However, − Device driver: IBM ARTIC Support for it will run also on subsequent releases or modification Windows NT. levels unless otherwise stated. − X.25 software: IBM ARTIC Support for X.25 Windows NT. Operating System • Encryptor box Secure X.25 provided by S.W.I.F.T. • VSE/ESA Version 2 Release 3 or higher (5690-VSE) The encryptor box from S.W.I.F.T. can be used • OS/390 Version 2 Release 4 or higher (5647-A01) between the computer and the modem. This Database and Communications Systems encryptor box is optional for PSTN connections, but mandatory for PSPDN connections. • CICS/VSE Version 2 Release 3 (5686-026) • 2. Message Processing Client CICS/ESA Version 4 (5685-018) • IMS/ESA Version 5 (5695-176) • Processor: Any workstation that runs under Windows NT Version 4.0 or a subsequent release. For VSE/CICS , the HL Assembler for VSE (5696-234) is A Pentium with 133 MHz or an equivalent also required. processor is recommended. Additional Program Requirements for the SWIFT Link • RAM: 32 MB RAM or more is needed. For the IBM 37xx Communications Controller one of the • Disk space: The program files require following NCPs is needed: approximately 30 MB of disk space. • ACF/NCP Version 4 (5668-854) Release 3.1 (MVS • Printer: Any printer supported by Windows NT. and VSE) • Interface device: Any interface device supported • ACF/NCP Version 5 (5668-738) Release 4 (MVS and by the end user communication software (for VSE) example, Token Ring Card or SDLC Adapter for remote connections). • ACF/NCP Version 6 (5688-231) Release 1, 2, or 3 (MVS only)

299-108 -2- • ACF/NCP Version 7 (5648-063) Release 1, 2, 3, 4, 5, 6, Operating System or 7 (MVS and VSE) MERVA USE and Branch and MERVA USE and Branch In addition, IBM MERVA Extended Connectivity for ESA with SWIFT Link are based on Microsoft Windows Version 3 Release 2 is needed: NT 4.0, Service Pack Level 4, US English. They also run on subsequent releases or modification levels of • MERVA Extended Connectivity for MVS/ESA this operating system, unless otherwise stated. Version 3 Release 2 (5655-110) License Management • MERVA Extended Connectivity for VSE/ESA Version 3 Release 2 (5686-080) MERVA USE and Branch expects the License Use Management program product iFOR/LS Version 4.0.1 Additional Program Requirements for the MERVA Link using the software key capability. This network connection is required for implementation Database System of the S.W.I.F.T. USE functions on either a PC or an RS/6000 . For communication between MERVA systems • DB2 Universal Database Workgroup Edition one of the following is required: Version 5.2, Service Pack Level 9084 and subsequent releases • ACF/VTAM VSE Version 3 Release 1.1 (5666-313) Communications Systems • ACF/VTAM Version 3 Release 4 (5685-085) for MVS/ESA • The SNA support is based on the availability of: Together with: − Personal Communication Version 4.2, and subsequent releases, or • ACF/NCP Version 4 (5668-854) Release 3.1 (MVS and VSE) − IBM eNetwork Communications Server for Windows NT Version 6.0 • ACF/NCP Version 5 (5668-738) Release 4 (MVS and VSE) Examples will be described for the IBM eNetwork Communication server. • ACF/NCP Version 6 (5688-231) Release 1, 2, or 3 (MVS only) SNA must be started as a Windows NT Service. • The service must run under a user account other ACF/NCP Version 7 (5648-063) Release 1, 2, 3, 4, 5, 6, than System Account. The users access control or 7 (MVS and VSE) list must contain the MERVA user group (for Additional Program Requirements for TCP/IP Based example, umerva1). Attachment for MERVA Message Processing Client under • The TCP/IP support is based on the availability of VSE TCP/IP, which is part of the Microsoft Windows NT 4.0 product. • TCP/IP for VSE/ESA Version 1 Release 3 (5686-A04) MERVA USE and Branch and MERVA USE and Branch Additional Program Requirements if DB2 Is to Be Used with SWIFT Link also require the following software: For OS/390: • Object REXX Runtime Edition Version 1.0.2.3 •  • DB2 for OS/390 Version 5 Release 1 (5655-DB2) Java Runtime Environment (JRE) Version 1.2 For VSE: Additional Program Requirements for Multi-User Support • DB2 for VM and VSE Version 5 Release 1 (5648-158) • Microsoft Windows Terminal Server, Terminal Additional Program Requirements for the MQI Attachment Server Edition and the Inter-Service Communication between Multiple Additional Program Requirements for the API MERVA ESA Instances MERVA USE and Branch and MERVA USE and Branch For OS/390: with SWIFT Link will support the C programming • MQSeries for MVS/ESA Version 1 Release 2 language to write application programs using the API (5695-137) functions. The following compilers are supported: • For VSE/CICS: Visual Age for C++ for Windows Compiler Version 3.5.4 • MQSeries for VSE/ESA Version 2 Release 1 • Microsoft Visual C++ 6.0 (5686-A06) • ACF/VTAM for VSE/ESA Version 4 Release 2 Additional Program Requirements for the SWIFT Link (5666-363) or TCP/IP for VSE/ESA Version 1 • The SWIFT Link connection is based on IBM ARTIC Release 3 (5686-A04) Support for X.25 on Windows NT. • Language Environment (LE) for VSE Runtime Library 2. MERVA Message Processing Client Version 1 Release 4 (5696-067) • Operating system: Microsoft Windows NT MERVA ESA Components Version 4 Release 1 Version 4.0 with Fix Package 4, or a subsequent release is needed. 1. MERVA USE and Branch and MERVA USE and Branch with SWIFT Link • Communication software for remote connections:

-3- 299-108 For SNA APPC: The MERVA Connection/NT Client Application System and the MERVA Server System must be − IBM eNetwork Personal Communication interconnected by a Data Communication Link. As Version 4.2 (5639-B94) or a subsequent specified by the used Data Communication Service release. (SNA APPC or TCP/IP), Token Ring, SDLC, Twinax, or − IBM eNetwork Communications Server for other types of intersystem links can be used. A Windows NT Version 6.0 (5639-F25) or a corresponding data link adapter must be installed in subsequent release. the Windows NT system. For TCP/IP: 5. MERVA Import/Export Facility for Windows NT − The TCP/IP support is incorporated in the The following are required: Windows NT 4.0 operating system. • Windows NT Version 4.0 or a subsequent release 3. Connection/400 of the operating system • An LU 6.2 connection between Communications MERVA USE and Branch or MERVA USE and Server and OS/400 must be customized for the PC Branch with SWIFT Link as a MERVA environment connection. on the server 6. Mainframe Based Features: MERVA Connection/400 requires an APPC LU 6.2 session between the PC and the AS/400. This can be The requirements are the same as already described achieved by Token Ring, SDLC, Twinax, and other for MERVA ESA including the requirement for a DB2 types of connection for which Communications database, which is prerequisite for the MERVA Manager SNA Server and OS/400 provide support for Directory Services Feature and Traffic Reconciliation an LU 6.2 session. For a list of the alternatives Feature. available and the hardware required for each, refer to the appropriate books listed in the bibliography of In addition the following is required for the MERVA the Connection/400 documentation (SH12-6340). Directory Services: Programs Required on the MERVA USE and Branch • IBM Language Environment for MVS/VMS Side: Version 1 Release 4 (5688-198).

• Communications Server, including the latest Compatibility: MERVA ESA Version 4 is upwardly available Corrective Service Diskette (CSD) level, compatible with MERVA ESA Version 3.3. or a subsequent release The new MERVA USE and Branch and MERVA USE and Programs Required on the AS/400: Branch with SWIFT Link can be used with MERVA ESA • OS/400 Version 3.1, including the latest available Version 3.3 and MERVA ESA Version 4. Corrective Service Diskette (CSD) level, or a The SSI support feature can also be used with MERVA subsequent release ESA Version 3.3. • A compiler for one of the following languages: MERVA USE and Branch and MERVA USE and Branch − IBM C/ILE with SWIFT Link are upwardly compatible with MERVA − IBM RPG/ILE USE and Branch OS/2 and MERVA OS/2 (LAN and − IBM COBOL/ILE Standalone). Migration aids allow easy migration.

Note that EPM/OPM is not supported anymore. Only Limitations: MERVA USE and Branch and MERVA USE ILE is supported. and Branch with SWIFT Link do not support more than 20 MERVA Message Processing Clients. 4. MERVA Connection/NT The following software must be installed on the client Performance Considerations: In a Sysplex installation, side: the performance of MERVA ESA depends on the exploitation of Sysplex through the used subsystems. • Windows NT 4.0. User Group Requirements: This announcement satisfies • Personal Communications for NT Version 4.2 or or partially satisfies more than 50 requirements from one Communications Server for NT Version 6.0 or a or more of the MERVA user group communities. subsequent release. The TCP/IP support is based Requirements satisfied include: on the availability of TCP/IP, which is part of the Microsoft Windows NT 4.0 product. 1. Common Requirements • The C Compiler Visual Age for C++ 3.5.4. AC4-0002 MERVA Link TCP/IP support Personal Communications (or Server for NT) is AC7-0005 Unload messages based on a date filter required only if an SNA APPC connection is used for AC8-0012 MERVA ESA Migration Documentation the communication between the Remote MERVA API 2. MERVA Requirements (toward existing products Client and Server. Personal Communications is not MERVA OS/2 and MERVA AIX ) required if a TCP/IP connection is used for that purpose; in this case TCP/IP must be installed on the Availability of workstation based functions Windows NT system. Communications Server for NT on Windows NT provides the same functionality as Personal DC8-0006 Increase the limit of 16 automatic print Communications for NT and more. Whenever queues to 999 Personal Communications for NT is mentioned, Communications Server for NT is also sufficient for the task.

299-108 -4- DC8-0007 Increase the limit of 99 print queues to available on a single CD called MERVA ESA Components 9999 for Windows NT. A license key is needed to run the DC7-0006 Identification on MERVA panels appropriate software. DC7-0007 Increase limit of 400 routing names to 1024 It is the responsibility of the customer (supported by the DC7-0009 DB2 reorg functionality provided by IBM sales representative) to obtain the password from MERVA the source indicated in the program package(s). DC7-0010 Show MRN after message creation DC7-0018 BIC expansion on printed messages System Integrity DC7-0021 Expansion on message types Increase the count of queue-management IBM will accept APARs where the installation of MERVA attaches in parallel ESA introduces an exposure to the system integrity of Increase the number of target queues in MVS. Refer to the MVS Integrity Software Announcement routing from 4 to 12 dated October 21, 1981. This program is intended to run unauthorized. 3. MERVA ESA Requirements

BC6-0006 MERVA Link customizable sub-pool Security, Auditability, and Control BC6-0012 API: line-by-line printer output BC6-0013 Allow test commands in production The security features of MERVA ESA V3 remain the same BC6-0017 Display all pages for JRN command in MERVA ESA V4.1: BC7-0002 DB2 with SWIFT SSI • BC7-0003 Automatic line switching Password protection is used for end-user access to the BC7-0016 Journal dataset switch MERVA ESA V4.1 system. BC7-0018 Re-Print Notification • The signon to MERVA ESA and to the user file BC7-0022 SWIFT Link Help Menu maintenance function can be controlled by an external BC7-0026 Protect imbedded part of messages security manager (ESM), for example RACF . For BC7-0027 SWIFT Link Performance Improvements MERVA ESA running under CICS/VSE, the signon BC8-0005 High water mark for QDS functions can be controlled by the basic security BC8-0008 Sorted queue display manager (BSM) of VSE/ESA Version 2 Release 4. BC8-0010 Provide DSLISYNP also for CICS BC8-0021 New Fields in MERVA ESA User File • Access to message processing functions is controlled BC8-0022 More fields in DSLBA05B by user file records. BC8-0028 EDIFACT mapping for MT 121 • MERVA ESA V4.1 defines and controls different user 4. Traffic Reconciliation Requirements classes: − Operating: authorized and normal operators BC7-1006 Deliver the Foreign Key Definitions BC7-1013 Utility for deletion of DB2-entries − File maintenance: display only, editing, and BC7-1015 Insert facility IMRI as batch program authorizing users BC7-1018 Unload and deletion into a seq.file BC7-1023 Monitor MQI activities − Message processing: data entry and authorizing BC7-1025 Spec. of queue names in IMRPRM users BC7-1026 Add columns to FINOMIR and FINOHDR • The Authenticator Key File and the User File are BC7-1031 M-Link messages in FIN tables scrambled and therefore not readable by other BC7-1032 Select a query by cursor applications or users. BC7-1039 Online Help for Traffic Recon Msg and Codes • Message authentication is performed according to BC8-1001 PFK Layout with RECON Panels S.W.I.F.T. standards. BC8-1006 Correct confusing text • BC8-1007 Query Q001 TRN rather than MUR MERVA Link SNA APPC conversation security is BC8-1010 Support SWIFT mixed upper and lower completely handled by APPC/MVS. case • MERVA Link provides a conversation security function BC8-1011 Queries independent from CommLink in the TCP/IP environment.

Planning Information The features currently provided are: • MERVA ESA V4 journal. Installability: For the migration of the workstation based functions of MERVA ESA — be it locally attached to • Reconciliation of messages via a relational database. MERVA ESA or via MERVA-to-MERVA Connection in a • different location — migration from IBM OS/2 to Microsoft Security features of the SWIFT II network, Windows NT is required. implemented in MERVA ESA SWIFT Link according to the S.W.I.F.T. User Handbook. A migration guide and migration tools are available to • In addition Version 4 provides a utility (DSLBA17R) to help you perform this task. check the last sign-on date, last password change date, and last User File update date of all or specified Packaging: MERVA ESA is made available on tapes and users. cartridges for MVS and VSE. There is only one set of MVS material, regardless of whether MERVA ESA is to be The security features of the Windows NT based features installed with CICS or IMS . of MERVA ESA Components are: All Windows NT based features (MERVA USE and Branch, • Password protection is used for end-user access to MERVA USE and Branch with SWIFT Link, MERVA MERVA USE and Branch and MERVA USE and Branch Message Processing Client, MERVA Import/Export Facility with SWIFT Link. for Windows NT, MERVA Connection/NT) will be made

-5- 299-108 • Access to MERVA USE and Branch and MERVA USE and Branch with SWIFT Link functions is controlled by Ordering Information user access rights. • The four-eyes principle can be used in message New Licensees processing and in the User Administration task. Orders for new licenses can be placed now. • Data objects are protected by check values. Shipment will begin on the planned availability date. • MERVA programs are controlled by file permission (execute). New users of MERVA ESA and MERVA ESA Components should specify: • The Authenticator Key File is handled according to SWIFT USE standards. Type Model • The User File is protected and therefore not readable by other applications or users. 5648 B29 5648 B30 • Message authentication is performed according to SWIFT standards. Basic License Auditability Considerations 1. MERVA ESA (5648-B29). To order a basic license, specify the program number and feature number 9001 The features currently provided are: for asset registration. Specify the basic feature and • MERVA USE and Branch logging and trace files the feature numbers for the desired tier (usage level, that is, the number of messages processed in • The audit log database, containing records for the multiples of 10,000) and the number of copies following when they occur on the MERVA USE and requested in this tier. For example, to order usage Branch system: within Tier 4, order incrementally by specifying tier 1 (quantity 1), Tier 2 with the full quantity (9), Tier 3 with − User events the full quantity (90), and Tier 4 with the remaining − Process events number. − Message flow events − Customization events Messages processed includes messages sent and • Security features of the S.W.I.F.T. network, received to/from the SWIFT network and the Telex implemented in MERVA USE and Branch and MERVA network (if connected directly) but also messages USE and Branch with SWIFT Link according to the processed through the FMT (Financial Message S.W.I.F.T. User Handbook Transfer) facility. • Windows NT Event log for: Specify the feature number of the desired distribution medium shown below. − Fatal errors in MERVA Control Process (start/stop phase) Base charge feature: 0029 − Trace entries of the self-written TCP/IP inetd Usage charge features: daemon service − Fatal errors in the MERVA logging (for example, file Basic system full condition) Tier Usage Level MLC

The customer is responsible for evaluation, selection, and 1 50 to 10,000 0030 implementation of security features, administrative 2 10,001 to 100,000 0031 procedures, and appropriate controls in application 3 100,001 to 1,000,000 0032 systems and communication facilities. 4 > 1,000,000 0033 Usage is counted per 10,000 messages processed per Customer Financing average month.

IBM Global Financing offers attractive financing to 2. MERVA ESA Components (5648-B30), usage based credit-qualified commercial and government customers features. To order a basic license, specify the and Business Partners in more than 40 countries around program number and feature number 9001 for asset the world. IBM Global Financing is provided by the IBM registration. Specify the feature number of the usage Credit Corporation in the United States. Offerings, rates, based feature requested and the feature number for terms, and availability may vary by country. Contact your the desired tier (usage level) and the number of local IBM Global Financing organization. Country copies requested in this tier. For example, to order organizations are listed on the Web at: usage within Tier 3, order incrementally by specifying Tier 1 with the full quantity (5), Tier 2 with the full http://www.financing.ibm.com 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.

299-108 -6- • 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 > 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 > 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 > 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.

-7- 299-108 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

299-108 -8- Unlicensed Documentation: A memo, a program Subsequent updates (technical newsletters or revisions directory, and one copy of the following publications are between releases) to the publications shipped with the supplied automatically with the basic machine-readable product will be distributed to the user of record for as long material: as a license for this software remains in effect. A separate publication order or subscription is not needed. Documentation for MERVA ESA Version 4 Release 1 (5648-B29) Customer Financing Order Title Number IBM Global Financing offers attractive financing to credit-qualified commercial and government customers MERVA ESA Licensed Specifications GH12-6973 and Business Partners in more than 40 countries around MERVA ESA Advanced MERVA Link SH12-6390 the world. IBM Global Financing is provided by the IBM MERVA ESA API Guide SH12-6374 Credit Corporation in the United States. Offerings, rates, MERVA ESA Operations Guide SH12-6375 terms, and availability may vary by country. Contact your MERVA ESA User′s Guide SH12-6376 local IBM Global Financing organization. Country MERVA ESA Macro Reference SH12-6377 organizations are listed on the Web at: MERVA ESA Installation Guide SH12-6378 http://www.financing.ibm.com 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 Terms and Conditions MERVA ESA System Programming Guide SH12-6366 MERVA Documentation CD SK2T-9752-01 Agreement: IBM Customer Agreement Documentation for MERVA ESA Version 4 Release 1 Variable Charges Apply: No Components (5648-B30) Indexed Monthly License Charge (IMLC) Applies: No Title Number Location License Applies: No MERVA ESA Components — Licensed GH12-6333 Use Limitation Applies: Yes, per number of messages Programming Specifications processed for MERVA ESA, and number of copies MERVA ESA Workstation Based Functions SH12-63831 installed for MERVA USE and Branch, MERVA USE and MERVA USE and Branch for Windows NT SH12-6334 Branch with SWIFT Link, and MERVA Client. — User′s Guide MERVA Use and Branch — Application SH12-6336 Note that messages sent and received over the S.W.I.F.T. Programming Guide network on an attached MERVA USE and Branch with MERVA USE and Branch — Installation SH12-6335 SWIFT Link are to be added to the number calculated for and Customization Guide the central MERVA ESA installation. Additional features, MERVA USE and Branch — Diagnosis SH12-6337 or authorizations, as appropriate must be obtained to Guide extend use levels. MERVA USE Administration Guide SH12-6338 MERVA Message Processing Client SH12-6341 Additional licenses or features, as appropriate, must be User′s Guide obtained to exceed usage limits. MERVA Connection/NT SH12-6339 MERVA Connection/400 SH12-6340 Educational Allowance Available: Yes, to qualified MERVA Automatic Message SH12-6389 education customers. Import/Export Facility User′s Guide MERVA Documentation CD SK2T-9752-00 Volume Orders: Not applicable MERVA ESA Directory Services SH12-63672 MERVA ESA Traffic Reconciliation SH12-63922 Version-to-Version Upgrade Credits Apply: No

Notes: Single 1 Available with MERVA ESA V4: December 17, 1999 Replaced Programs Replacement Programs Version 2 Available with the ESA based features: March 31, 2000 Program Program Program Program Charging Number Name Number Name Applies Additional copies of unlicensed publications are available for a fee after availability. These copies may be ordered 5655-039 MERVA ESA 5648-B29 MERVA ESA Yes from your IBM representative, through the Publication 4.1 Notification System (PNS), or by direct order. 5655-040 MERVA ESA 5648-B29 MERVA ESA Yes Displayable Softcopy Publications: MERVA manuals are 4.1 offered in displayable softcopy form. All unlicensed manuals are included. The displayable manuals are part 5686-063 MERVA ESA 5648-B29 MERVA ESA Yes of the basic machine-readable material and available as 4.1 the no-charge order number SK2T-9752. The files are shipped on CD-ROM. Warranty Applies: Yes

These displayable manuals can be used with the Licensed Program Materials Availability BookManager READ licensed programs in any of the supported environments. Terms and conditions for use • Restricted Materials of IBM: None of the machine-readable files are shipped with the files. • Non-Restricted Source Materials: None • Object Code Only (OCO): All

-9- 299-108 Testing Period: Two months (Basic license only) 3. MERVA ESA Components (5648-B30), flat per use features Program Services Annual • Support Center Applies: Yes Support • Available until Discontinued: Six months′ written Feature Platform MLC OTC Charge notice Connection/NT Windows $150 $ 5,400 $ 970 NT Connection/400 OS/400 150 5,400 970 Charges MIE/NT Windows 180 6,480 1,150 NT 1. MERVA ESA (5648-B29) Directory OS/390 750 27,000 4,860 Services Basic license charge (MLC): $2,400 Traffic OS/390 750 27,000 4,860 Reconciliation Basic Tier Usage Level MLC The annual support charge applies for OTC customers only. 1 50 to 10,000 $900 2 10,001 to 100,000 200/10,000 messages Use Level Charge: Charges for this program are based 3 100,001 to 1,000,000 40/10,000 messages on usage levels. When a customer upgrades to a higher 4 > 1,000,000 8/10,000 messages level of usage, a usage upgrade charge will apply, equal to the difference between the charge for the current level Usage is counted per 10,000 messages processed per of usage and the higher level of usage. average month. Trademarks 2. MERVA ESA Components (5648-B30), usage based features MVS/ESA, MVS, RS/6000, eNetwork, and IMS are trademarks of International Business Machines Corporation in the United • MERVA USE and Branch States or other countries or both. OS/390, CICS/ESA, CICS/VSE, IMS/ESA, AS/400, CICS, Annual ACF/VTAM, DB2, MQSeries, DB2 Universal Database, Support OS/400, OS/2, AIX, RACF, and BookManager are registered trademarks of International Business Machines Corporation Tier Usage Level MLC OTC Charge in the United States or other countries or both. Pentium is a trademark of Intel Corporation. 1 1 to 5 $360 $12,960 $2,330 Microsoft and Windows are trademarks of Microsoft 2 6 to 20 180 6,480 1,165 Corporation. 3 > 20 90 3,240 585 Windows NT is a registered trademark of Microsoft Corporation. Usage is counted per copy installed. The annual Java is a trademark of Sun Microsystems, Inc. support charge applies to OTC customers only. Other company, product, and service names may be • MERVA USE and Branch with SWIFT Link trademarks or service marks of others.

Annual Support Tier Usage Level MLC OTC Charge

1 1 to 5 $900 $32,400 $5,830 2 6 to 20 450 16,200 2,915 3 > 20 225 8,100 1,460 Usage is counted per copy installed. The annual support charge applies to OTC customers only. • MERVA Message Processing Client

Annual Support Tier Usage Level MLC OTC Charge

1 1 to 5 $40 $1,440 $260 2 6 to 20 20 720 130 3 > 20 10 360 65 Usage is counted per copy installed. The annual support charge applies to OTC customers only.

299-108 -10-