Technical Notes

Verastream Integration Broker 9.7 for OpenVMS Patch 2: Fixes, Features, and File Download
Technical Note 40028
Last Reviewed 26-May-2005
Applies To
Verastream Integration Broker version 9.7 for OpenVMS
Summary

This technical note lists updates made in Verastream Integration Broker 9.7 for OpenVMS patch 2. It also lists requirements, and includes information about updating an existing installation of Verastream Integration Broker version 9.7 for OpenVMS.

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 for OpenVMS, which shipped in December 2004.

Obtaining the Update

Verastream Integration Broker 9.7 for OpenVMS Patch 2 (accumulation of all patches since the shipping version) can be obtained from the Download Library at WRQ-AXPVMS-VIB-V0907-2-3.PCSI.

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	Installation Location
sn4.olb	nova$dev:[lib.]sn4.olb
sho_sys.olb	nova$dev:[lib.]sho_sys.olb
snrms.olb	nova$dev:[lib.]snrms.olb
mtfcmdline.fle	nova$dev:[pardir.]mtfcmdline.fle
linknova.com	nova$dev:[lib.]linknova.com

Issues Fixed By This Update

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

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

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. 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. 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.

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.

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.

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

You can now create a shared memory segment containing multiple applications.

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:

• the keyword APPL or SUBAP
• the name of the application
• optional arguments: FILE="..." DIRECTORY="..." TYPE="..."

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

Run the product utility to install this patch, and choose VIB 9.7-2, Partial (product upgrade):

Related Technical Notes

10999

Verastream Integration Broker Technical Notes