UniVerse v11.1.11 now available

This release is available for the following versions of these operating systems:

  • OS Platform OS Release(s) AIX POWER 5.3, 6.1, 7.1
  • HP/UX Itanium 11.23, 11.31
  • Windows x86 XP (SP3), 2003 (SP2 R2), VISTA (SP2), 2008 (SP1 R2), Windows 7 (SP1)
  • RedHat Enterprise Linux x86 5, 6
  • SuSE Linux Enterprise Server x86 11.0 (SP1)
  • Solaris SPARC 10, 11
  • Solaris x86 10, 11
  • HP/UX PA-RISC 11.23, 11.31

Problems Fixed in UniVerse Release 11.1.11 (Build 5919)

UNV-361 Beginning at UniVerse 11.1.11, the UniVerse server now supports the U2 Metadata Manager (MDM).

UNV-4422 UniVerse -- By default, when changing from print mode 1 to print mode 3 (i.e. hold file output), any printer location defined with print mode 1 would not be maintained.

UNV-5101 UniVerse -- At this release, an enhancement has been made to the output displayed in the INDEX.log file created by a BUILD.INDEX CONCURRENT process.

UNV-5173 UniVerse -- When building an index on a file using the BUILD.INDEX CONCURRENT command, a log file named INDEX.log is created in the I_filename directory to log the progress of the process.

UNV-12230 UniVerse SQL -- Changes were made at UniVerse 11.1.10 to handle a situation where SQL queries containing embedded new line characters were not handled correctly when passed to the UniVerse server from client-based tools.

UNV-12662 UniVerse -- On Linux and Solaris platforms, if multiple forms have been assigned to a printer, displaying the spooler status (i.e. usa -s) may have failed with a segmentation fault if the length of all form names exceeded 26 characters.

UNV-12943 UniVerse -- When using the screen based System Administration menu in the UV account to rollforward transaction logs, the length of the response to the "File path or name of select list" prompt was limited to 30 characters.

UNV-12988 U2 Data Replication -- Additional logging has been added at UniVerse 11.1.11 to log more information when replicating the CATALOG command through U2 Data Replication.

UNV-13029 UniVerse -- Beginning at UniVerse 11.1.0 on AIX and HP, the uvrestore command may have caused UniVerse to terminate abnormally when restoring data from an incremental backup.

UNV-13215 UniVerse BASIC -- Under certain circumstances, the UniVerse BASIC SubmitRequest function may have lost data.

UNV-13258 BCI -- At this release, the SQLGETDATA command has been added to BCI.

UNV-13315 UniVerse -- Due to an internal memory problem, UniVerse may have abnormally terminated when using FILEINFO().

UNV-13328 UniVerse -- On Windows platforms, if the MASTER OFF command was issued to log off all UniVerse users, it incorrectly stopped UniVerse daemon processes as well.

UNV-13372 UniVerse -- Beginning at UniVerse 11.1 on Windows, the PORT.STATUS command was incorrectly including the background UniVerse daemon processes in the number of UniVerse sessions displayed.

UNV-13451 UniVerse BASIC -- When using CallHTTP, you can use setHTTPDefault "AUTHENTICATE" to set up default credentials when connecting to websites where authentication is required.

UNV-13547 NLS -- A problem was discovered where UniVerse may have abnormally terminated when running with NLS enabled.

UNV-13613 UniVerse -- A problem during the installation process caused the .hs_fileinfo file in the HS.SALES account to be incorrect.

UNV-13630 BCI -- Before this release, the BCI SQLFetch() function caused UniVerse to abnormally terminate when the data returned by the SQLExecDirect function was separated by text marks (@TM) and exceeded 255 characters.

UNV-13651 U2 Data Replication -- Prior to this release, updates to directory files (Type 1 or Type 19) may have incorrectly changed group permissions of the directories on the subscribing system.

UNV-13689 UniVerse BASIC -- At UniVerse 11.1.10 only, a UniVerse BASIC program which used transactional semantics may have dumped core when performing a DELETE statement within a transaction.

UNV-13691 UniVerse SQL -- When upgrading to UniVerse 11.1.10 from a prior release, the SQL CREATE, ALTER and DROP table statements may have failed if associated multivalued attributes were involved in the SQL statement.

UNV-13708 UniVerse -- Prior to this release, the size of the disk shared memory segment on Linux platforms was limited to 256MB.

UNV-13726 U2 Data Replication -- Due to an issue discovered in Solaris zones, UniVerse licensing has been changed for Solaris platforms.

UNV-13826 U2 Data Replication -- At UniVerse 11.1.9 and 11.1.10, space as reserved for U2 Replication uvrw locking queues in UniVerse disk shared memory segment based on the GSEMNUM and NUSERS uvconfig parameters.

UNV-13854 UniVerse -- Under certain circumstances, calling the !SETPU subroutine to update the printer characteristics for a particular print unit resulted in additional print units being incorrectly updated with the information.

UNV-13859 UniVerse BASIC -- When using HTTP version 1.1, errors were written to the protocol log after submitting a request, and the process hung because the request timed out.

UNV-13876 UniVerse -- At UniVerse release 11.1.10, the install process generated the following error during the installation process.

UNV-13887 U2 Data Replication -- Under a very specific set of circumstances, updates being done by a UniVerse BASIC program might have caused a core dump and caused U2 Data Replication to suspend.

UNV-13892 U2 Data Replication -- The default value for the MAX_REP_SHMSZ uvconfig parameter has been changed at this release to match the default value of SHM_MAX_SIZE at 1073741824.

UNV-14014 U2 Data Replication -- On previous releases of 32-bit versions of UniVerse (i.e. Linux), the initial load of the U2 Replication object table would fail on 64-bit files larger than 2GB in size.

Rocket Software

77 Fourth Avenue Waltham MA 02451-1468 USA 720-475-8002

View more articles
menu
menu