COMMUNICATOR 3000 MPE/iX Release 5.5 (Non-Platform Software Release C.55.00)

Transact Contains Defect Fixes 

by Bill Toms 
Support Technology Center 

Introduction 

The release of Transact/iX version A.05.02 (HP30138) in MPE/iX-Express 3
based on General Release 5.0, contained 27 defect fixes.  The
compatibility mode version of Transact/V version A.10.02 (HP32247),
contained an additional 28 defect fixes.  These fixes are on the
PowerPatch tape (C.50.03).

This article highlights some of the corrections made to each product.
Please refer to the Software Release Bulletin for more details on these
fixes and all the other fixes.


NOTE  For the MPE/iX 5.5 Release, three additional defects have been
      fixed in Transact/iX, version A.05.04 (HP30138).


TRANSACT/iX 

The following paragraphs briefly describe the corrections made to
Transact/iX for some of the highest priority problems reported by
customers.

Compiler Needs Less Heap Space.   

The Transact/iX compiler now requires less NMHeap.  This prevents
compiles of most very large programs from aborting with an out of memory
message.  This became a problem for some programs starting with the
A.05.00 release of Transact/iX.

ACI Closes Files.   

When a program written in another language such as COBOL calls a
Transact/iX program using the Architected Call Interface (ACI), TRANIN
and various TRANDEBUG files no longer remain open after exiting the
Transact program.

NOMATCH Option in Serial Access.   

The match register is no longer checked when the NOMATCH option is
specified in FIND(SERIAL), GET(SERIAL) and OUTPUT(SERIAL) statements
applied to a TurboIMAGE database.

PERFORM= Option of a DELETE(CURRENT).   

The PERFORM= option of a DELETE(CURRENT) statement now executes the code
following the specified label as expected.  Previously, the jump to the
label was not taken.

DISPLAY Verb.   

The NEED= option of the FORMAT statement is now being checked when
DISPLAY is printing the last line of data on a page.

The trailing "-" in an edit-string now works consistently with the
trailing "CR" for items of type "9".

The output should now be consistent between Transact/V and Transact/iX
when specifying the LINE= option on a DISPLAY to a file.

KSAM File Usage.   

Several defects have been fixed related to KSAM files and dealing with
incorrect or incomplete retrievals, incorrect matching, partial keys, and
problems where the items are not specified in the same order as the
physical record.

PASSWORD is Padded.   

The PASSWORD option of the LIST statement now pads with blanks, just as
it once did.

TRANSACT/V 

The following paragraphs are intended to give Transact programmers some
insight into the areas of the product most affected.

DISPLAY Verb.   

The NEED= option of the FORMAT statement is now being checked when
DISPLAY is printing the last line of data on a page.

The trailing "-" in an edit-string now works consistent with the trailing
"CR" for items of type "9".

Multiple CCTL options in a FORMAT statement should now be applied to the
correct item even if there are fewer CCTLs than items.

Using the ROW= option when displaying to a file now skips to the correct
row in the file.

Use of DISPLAY and DISPLAY(FILE=filename) now keeps better track of line
counts, page breaks and the need to issue a CONTINUE Y/N? prompt.

The page numbering when displaying to a file should now be correct even
when that file has a blocking factor specified in the SYSTEM statement.

A CLOSE of a file should no longer result in an FSERR 0 if a DISPLAY has
been done to that file.

LET Verb.   

Several error situations with the LET statement have been fixed.  Also a
LET of a zero from a numeric type to an X or U type now results in a
single ascii zero instead of all blanks.

KSAM File Usage.   

Several defects have been fixed related to KSAM files and dealing with
incorrect or incomplete retrievals, incorrect matching, partial keys, and
problems where the items are not specified in the same order as the
physical record.

PASSWORD in a Called Subprogram.   

Two defects have been corrected concerning the result of the following
statement in a called subprogram where the password was a parameter in
the CALL statement:

     LIST item,PASSWORD;

Transact/V and Transact/iX are now more consistent with each other and
the manual.