Technical Notes

Verastream Integration Broker 9.7 Patch 4 (for Windows): Fixes, Features, and File Download
Technical Note 40029
Last Reviewed 09-Jun-2005
Applies To
Verastream Integration Broker version 9.7
Summary

Verastream Integration Broker 9.7 Patch 4 contains product updates for the Windows platform. This technical note lists requirements and the changes made to the product. It also includes information about updating an existing installation and performing a new installation (and patching that installation) of Verastream Integration Broker version 9.7.

This document is organized into the following sections:

Requirements

If you are patching an existing installation, this product update is intended for Verastream Integration Broker version 9.7, which shipped in December 2004. This patch is for Windows installations only.

Obtaining the Update

Verastream Integration Broker 9.7 Patch 4 for Windows, VIB97_patch_4_windows.zip, is cumulative—it includes fixes originally included in Patches 1–3, and is available from Attachmate's Download Library.

Important Patch Information: Before you can download or search for a patch from Attachmate, you must enter your volume purchase account (VPA) number for the software to which the patch will be applied.

Files Contained in this Update

File Name	Installation Location(s)
snsys.dll	<verastream>/bin/sn450sys.dll
sn4.lib	<verastream>/lib/sn4.lib
snvhi50.dll	<verastream>/shared/snvhi50.dll <verastream>/bin/sn450vhi.dll
snvhij50.dll	<verastream>/shared/snvhij50.dll <verastream>/bin/sn450vhi.dll
snvhi55.dll	<verastream>/shared/snvhi55.dll <verastream>/bin/sn450vhi.dll
snvhij55.dll	<verastream>/shared/snvhij55.dll <verastream>/bin/sn450vhi.dll

Issues Fixed By This Update

The following issue is resolved in Verastream Integration Broker 9.7 Patch 4. (A description of this issue is included below.)

The following issues are resolved in Verastream Integration Broker 9.7 Patch 3. (Descriptions of these issues are included below.)

The following issues are resolved in Verastream Integration Broker 9.7 Patch 2 and are included in subsequent patch releases. (Descriptions of these issues are included below.)

The following issue is resolved in Verastream Integration Broker 9.7 Patch 1 and is included in subsequent patch releases. (A description of this issue is included below.)

Issue No. 278297 -- AppConn method SetCurrentRecordSetByName was not always called when necessary

Most of the VIB VHI component methods change the current entity and/or record set before executing the actual AppConn method. (This is addressed in patch 4.)

First, when necessary, the current entity is set using [SetCurrentEntity()]. And after that, when necessary, the current record set is set using the AppConn method [SetCurrentRecordSetByName()].

This last step however, was executed only when the entity needed to be changed.

Issue No. 276685 -- Replication recovery causes CSX to restart servers

The replication protocol sometimes has to remove and reconstruct the replicated information in a directory server. (This is addressed in Patch 3.)

The CSX was notified of this and reacted by restarting the servers.

Issue No. 278156 -- CSX switch may not restart components after replication recovery

The replication protocol sometimes has to remove and reconstruct the replicated information in a directory server. (This is addressed in Patch 3.)

The pre-start setting that the CSX switch places in the daemon was reset by this operation.

Be able to run linknova in every environment

When the installation area of Verastream Integration Broker is reached using a logical, it is now possible to run linknova.com. (This is addressed in Patch 2.)

For instance, the following script will now work (it did not before):

Issue No. 277985 -- Added support for transactions to the RMS and RMS COBOL adapter

The RMS and RMS COBOL backend now use transactions (called Journaling on OpenVMS) as soon as the VIB VSL functions TR_BEGIN, TR_COMMIT and/or TR_ABORT are used. (This is addressed in Patch 2.)

For transactions, options [TRANSACTIONS] and [ABORT_ON_EXIT] are introduced.

By default UPD always removes all locks on the current record, even if it was set by LOCK. This behavior is now switchable with option [UPD_UNLOCK].

Please refer to the detailed document [Transactions in VIB].

Issue No. 278016 -- COBOL pictures like "S9V999999 COMP." were incorrectly processed

A change in VIB 9.7 for COMP and RMS Cobol introduced 2, 4 and 8 bytes as storage space for pictures without precision. COMP(n), with n between 1 and 4, is stored in two bytes, values for n between 5 and 9 are stored in 4 bytes and COMP(n) with n > 9 is stored in 8 bytes. (This is addressed in Patch 2.)

For pictures with precision however the implementation was not completed yet. Only 8 bytes were possible (example S9V999999 for instance needs 4 bytes) and the precision was removed. Now also 2, 4 and 8 bytes are used, while the precision is retained.

Issue No. 278036 -- Fixed a bug in record locking

A NEXT after a LOCK (record) also tried to lock the next record. Only LOCK should be able to lock the record, functions like FIRST and NEXT only read the record. (This is addressed in Patch 2.)

Issue No. 276914 -- Add on an RMS and RMS COBOL table failed with EMFAILED

When an ADD was executed after a failing NEXT, RMS error "%RMS-F-RSZ, invalid record size" was returned. This was translated by VIB into EMFAILED. (This is addressed in Patch 2.)

Issue No. 270703 -- Improved functionality of shared memory segment containing multiple applications

You can now create a shared memory segment containing multiple applications. (This is addressed in Patch 1.)

To initialize such a segment, issue the following command: "nova -w -eshminit file=<some text file>"

In the text file, that you can create with any editor, you must specify a list of applications to place into shared memory. Each line of the file must contain the following:

A line starting with the keyword APPL indicates an application that must be placed into shared memory.

The optional arguments work exactly like the arguments of LOADMODULE/SUBAP, see the VSL reference for details.

Note that for a PI application, you must specify TYPE="pia".

An typical example of this file is:

The modules (subapplications) loaded by your PI application are already automatically included in the shared memory segment, and do not have to be listed in the text file. If your application loads subapplications during runtime, with LOAD/SUBAP or LOADMODULE/SUBAP, you can add these subapplications to the shared memory segment by specifying SUBAP lines below the APPL line.

For example, if you have a main application "main" that loads two subapplications, you could specify this as follows:

Updating the Verastream Integration Broker Installation

First, stop the daemon service. (The daemon can be restarted after the update.) In order to update your Verastream Integration Broker installation, all files in this patch should be replaced in the following manner:

New installation of Verastream Integration Broker

In order to newly install Verastream Integration Broker including this patch, perform the following steps:

1. Create a temporary directory, like [c:/tmp/vs9.7p4].
2. Copy the patch [VIB97_patch_4_windows.zip] to [c:/tmp/vs9.7p4].
3. From the Installation CD (drive is `X`), copy the files in the folder [X:/windows] to [c:/tmp/vs9.7p4].
4. Extract the patch files from [c:/tmp/vs9.7p4/VIB97_patch_4_windows.zip].
5. From Windows Explorer, double-click [c:/tmp/vs9.7p4/setup32.exe].
6. Remove the temporary directory [c:/tmp/vs9.7p4].

Related Technical Notes

10999

Verastream Integration Broker Technical Notes