Explore What’s New In UniData 8.1

1
Explore What’s New
In UniData 8.1
Jonathan Smith, Principal Technical Support Engineer

2
Abstract
 8.1 was the first major release of UniData in several years. This
presentation describes the new features and functionality we’ve
added. New features include 64-bit files, 64-bit builds, account-
based licensing, installation improvements, improvement to ADE,
IPV6 support … and the list goes on.
©2015 Rocket Software, Inc. All Rights Reserved.

3
Agenda
 File changes
 Encryption changes
 Installation
improvements
 64-bit builds
 Shared Memory
allocation
 Account-based licensing
 U2 Replication
 Security
 UniBasic
 IPv6
 Other changes

4
File Changes
• New Hash Type 3
• 64-bit Files
• New Dynamic File Split Type

5
New Hash Type 3
Becomes the default for newly created files
• Controlled via the DEFAULT_HASH_TYPE udtconfig tuneable
 Improved hashing of groups
• The general distribution is significantly improved compared to
other hash types
• In a number of specific customer examples where the existing
hash types gave a poor distribution, hash type 3 succeeded

6
New Hash Type 3
Before deciding on the new hash type…
• 13 candidates were examined
• 6 different test patterns over millions of keys were examined
including exact customer cases where dynamic files would overflow
extremely quickly
• We decided on the AP function which is a general hash function
listed in the NIST (National Institute of Standards and Technology)
Dictionary of Algorithms and Data Structures
• Testing on customer cases that did not perform well with Type 0 or
Type 1, we were able to demonstrate performance improvements,
some of them quite substantial

7
64-bit Files – 32-bit Restrictions
A UniData static hashed file or a sub-file of a dynamic
hashed file is limited to 2G in size
• Theoretically, a UniData dynamic file can grow to 500G until it
reaches 256 dat, over or idx files. The overall cost of the dynamic
file operations is high than static hashed files, and internal
management of the sub-files requires complicated code and hence
reduced file performance.
• In the information-hungry world we operate in today, this was
becoming a serious restriction for more and more user applications.
• The block-size of the data file is limited to 16K and as data records
are now getting larger and larger, this also is a performance
limitation of the 32-bit model.

8
64-bit Files
The 64-bit data model resolves these issues by allowing
data files sufficiently large that they will not reach a
limitation in the foreseeable future as the maximum size is
now 8 Exabytes
• The conversion from 32-bit to 64-bit will need to be done with the
RESIZE or memresize command
 memresize has also been modified to use buffer sizes greater than 4GB. It
should now be considered unlimited
• The address mode for RESIZE and memresize will remain the
same as currently defined in the file if no keyword is specified
 If a file is converted from one address model to another and has one or
more indexes, the indexes will also be converted to the new address mode

9
64-bit Files
Static files can grow past the previous 2GB boundary
• When you get the growth warning limit in the udt.errlog, you can
resize these files to 64-bit to avoid file corruption, potential loss of
data, and downtime
• When upgrading to 8.1.0, part of the upgrade plan could be to
resize all files over a given size to 64-bit to avoid waiting for the
warning. You can also take advantage of the increased buffer size
with memresize and, on UNIX, the “concurrent” option to resize a
file while it is in use.
64-bit files can have a block size of up to 2GB
• Allows you to store some previously problematic large records
without issue

10
Dynamic Whole File Splitting – Why Change?
 UniData dynamic files grew and shrank based on the
loading of individual groups
• For this type of file to perform well, records need to hash evenly and work
at their best when there is only a small standard deviation in terms of:
 The average record size for the KEYDATA style
 The average key size for the KEYONLY style
• When these styles are not hashed evenly, a UniData dynamic file can grow
unnecessarily large. This contributes to wasted disk space as well as
reducing the file scan performance (SELECT, SSELECT).
• In order to reduce unnecessary splitting, the UDT_SPLIT_POLICY
configurable was added prior to 8.1.0 and is still applicable to KEYDATA
and KEYONLY dynamic files

11
Dynamic Whole File Splitting - What Changed?
New dynamic file type: WHOLEFILE
• Changes its modulo based on the total file load rather than on an
individual group’s load
• The new whole-file based style works for both 32-bit and 64-bit
dynamic files
• The existing dynamic file types KEYONLY and KEYDATA will
continue to be supported
• udtconfig tuneables have been added for the default split and
merge values
• The default dynamic file type will be the new whole file based style
and is controlled with a udtconfig tuneable

13
Automatic Data Encryption (ADE) Changes
UniData indexes and keys can now be encrypted
Privileged ADE operations no longer require the
master key as a password
• Starting at 8.1.0, these operations are now protected by a
separate password which can be changed independently of
the master key

15
Installation Improvements - UNIX
A new script called udtsetup should now be used for
an install or upgrade
Upgrade validation
Custom configurations
Parameter file added for a ‘silent install’

16
Installation Improvements - UNIX
Web authorization and connection to U2BC records
URI (Uniform Resource Identifier) support
Backup and restore of udt environment
Check and correct file permissions
Improved logging with unique exit codes and
messages

17
Installation Improvements - Windows
Maintain current configuration for upgrade installation
Custom bat file can be run before or after the install
Parameter file added for a ‘silent install’
Backup and restore of udt environment
Improved logging

19
64-bit Builds
ALL builds will be 64-bit only
• No 32-bit builds
 64-bit builds will not install on a 32-bit OS
• Must have a compatible 64-bit compiler
• Any linked C routines, Windows dll’s, etc. must be 64-bit
compatible if it is required to perform a makeudt
• The compiler and OS version that UniData is built on is stored
in the port.note file

21
Shared Memory Allocation
Prior to 8.1.0, UniData UniBasic variable space was
allocated with Shared Memory from a system-wide
shared pool in order to reduce total system-wide
memory consumption
In 8.1.0, we moved to a heap memory allocation
model for UniBasic variable processing.
A future webinar to discuss these changes is planned

23
Account-based Licensing
An account or a group of accounts are defined as a
logical account
• The license count of the main UniData licence can be
subdivided into the logical accounts
• Aids in hosting multiple customer installations on the same
physical machine with only one instance of UniData
• Logical account can be configured to help ensure that
administrators always have a license seat to use if required
• Not currently supported with device licensing enabled

25
U2 Replication
Performance Monitor
• Allows the collection and display of detailed statistics for U2
Replication via the Extensible Administration Tool (XAdmin) or
command line interface of reptool
Data Compression
• Allows data to be compressed during the network transfer phase
• Reduces the data volume being transferred and the overall transfer
time
• Reduces any problems that customers may experience due to slow
network speeds

27
Security
The OpenSSL libraries are updated to version 1.0.1j
• UniData can now import both SHA-1 and SHA-2 certificates directly
• Minimum industry version to correct vulnerabilities, such as
Heartbleed and POODLE
• Tech Note available on how to update library to newer versions as
1.0.1m
U2 root certificate store
• This file contains a metadata section that stores data such as
version, creation and modification times, and so forth, and is
designed around the Microsoft certificate store to allow similar
interrogation

28
Security
Encrypted passwords
• SSL configuration files no longer contain clear text
passwords.
SSL certificate revocation list (CRL) processing
• Including the handling of standard based CRL files, multiple
CRLs (from different CAs), DER type CRL, delta CRLs, and
improved error reporting during CRL verification.

29
Security
SSL_PROTOCOLS
• Specifies the protocols allowed using SSL connections
• The allowed protocols are: SSLv3, TLSv1, TLSv1.1, TLSv1.2
SSL_OPTIONS
• Specifies additional options that will be set for SSL connections
• The valid options are: TLS_FALLBACK_SCSV, and
NO_TLS_FALLBACK_SCSV
More information in the release notes and Security
Features manual

30
Security
UniBasic SCR API now allows a specific SSL version control
UniBasic Security API now has SHA2 and PKCS#12 support
As part of the updating the OpenSSL libraries, various
obsolete handshake sequences are now rejected around
SSLv3 and SSLv2
Both the standard (non-secure) and SSL (secure) UniData
telnet services on Windows can now be selectively disabled
with XAdmin

32
UniBasic in UniData 8.1
 Local functions and subroutines are now supported
• These new subroutines are a block of code that you call like existing subroutines
and functions but they exist in the same source code file
• COMMON and EQUATE statements along with variables used in a local
subroutine only apply for that local subroutine
 MQSeries AMI and MQI Interface
• Existing UniBasic code using the U2AMI will now display the following message:
“Note: IBM is no longer supporting AMI. This feature is removed from UniData as
of UniData 8.1.0. Please use the new MQI feature as an alternative.”
 U2 Dynamic Objects (UDO) provide an object structure based on
JSON within UniBasic
• Starting at 8.1.0, UniData allows the conversion between XML and JSON data
within the objects

33
UniBasic in UniData 8.1
 The processing of an EQUATE statement now only incurs the same
execution time penalty as a comment line
• To take advantage of this enhancement, programs will be need to recompiled and
recataloged
 Introduction of a new @USER.TYPE of 3, which will be set if client access to
the system is from UniObjects, Intercall, or our other client tools
 SYSTEM(9012) has also be enhanced to return 1 if the client access is from
InterCall, UniObjects ,or other client tools; otherwise it returns 0
 SYSTEM(99) has been added to return the system time in the number of
seconds since midnight 1 January 1970 in Coordinated Universal Time
(UTC)

35
IPv6
UniData 8.1.0 supports both IPv6 and IPv4
• Server side system calls are both IPv4 and IPv6 compatible
UniBasic functions added to allow the programmatic
setting of any client side connection preference
New UCI configuration line
IPVERSION =“IPV6” | “IPV4”
and the uci client connection will use this preference to
connect to the server (unirpcd)
New functions added for the Intercall client

37
Other Changes - SAVEDLISTS
Prior to 8.1.0, when creating a SAVEDLIST, UniData used
an internal hard-coded break point to control the size of
files created in the SAVEDLIST directory.
• This could result in many separate SAVEDLIST files being
generated by appending a sequential three-digit number (for
example, 000,001,002, etc.) to the list name.
Now the SAVEDLIST will be a single file with 000
appended to the list name.
• This behavior is controlled from the udtconfig tuneable
SINGLE_SAVEDLIST. The default is 1. If a user wants to return to
the old method, then the tuneable can be set to 0.

38
Other Changes - Windows
 The UniRPC service is now configured to be ‘multithreaded’ by default
 UDT.OPTIONS 120 added to resolve printing issues on some instances
of Windows 2012
 The performance of the Recoverable File System (RFS) has now been
dramatically improved for Windows
 Separate UniData event logs now appear in the Windows Event viewer
 UniData now recognizes administrator privileges for users who inherit
their administrative privileges through a domain group hierarchy

39
Other Changes – cleanupd
On UNIX, the cleanupd process has been redesigned in
order to improve the dead process detection phase and
make the resource cleanup easier
• Prior to these changes, race conditions could be encountered
which resulted in problems determining if a process had exited
• ‘NUSERS’ extra semaphores are required
• The ipcstat command has been modified and will report these
structures as a ‘live detection semaphore’
• When a process logs in, they acquire one of the semaphores; when
it exits (normally or abnormally) the semaphore will be released
• The cleanupd process now checks the status of the owner of the
semaphore in order to determine the status of process

40
Other Changes
The SAMPLE keyword has been added to SQL
AFTER EVENT TRIGGERS
udtconfig configurable changes
• HTTP_DEFAULT_VERSION controls the default HTTP version
used in UniBasic
• Several of the default values of the configurable parameters have
been increased to reduce the amount of tuning during installation
Improved error reporting back to UniObjects.NET and
UOJ connections

41
Previously Supported Components
Objectcall
• No longer functional in 8.1
On the UNIX version, the udtinstall and updatesys
scripts are in 8.1.0. However the new udtsetup script
is now the recommended script for installations and
upgrades

42
Next Steps
Other presentations:
• 8.1 in Depth: Meet the New UDT 64-bit Files
• Troubleshooting UDT
• Lab: UniData 8.1 Administration
• Lab: U2 Replication
• U2 Replication for HADR
• U2 Replication and EDA
• HADR Best Practices
• SaaS Best Practices and Account Based Licensing

43
Disclaimer
THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.
WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED
IN THIS PRESENTATION, IT IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.
IN ADDITION, THIS INFORMATION IS BASED ON ROCKET SOFTWARE’S CURRENT PRODUCT PLANS AND STRATEGY,
WHICH ARE SUBJECT TO CHANGE BY ROCKET SOFTWAREWITHOUT NOTICE.
ROCKET SOFTWARE SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR
OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION.
NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF:
• CREATING ANY WARRANTY OR REPRESENTATION FROM ROCKET SOFTWARE(OR ITS AFFILIATES OR ITS OR
THEIR SUPPLIERS AND/OR LICENSORS); OR
• ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF
ROCKET SOFTWARE.

44
Trademarks and Acknowledgements
The trademarks and service marks identified in the following list are the exclusive properties of Rocket Software,
Inc. and its subsidiaries (collectively, “Rocket Software”). These marks are registered with the U.S. Patent and
Trademark Office, and may be registered or pending registration in other countries. Not all trademarks owned by
Rocket Software are listed. The absence of a mark from this page neither constitutes a waiver of any intellectual
property rights that Rocket Software has established in its marks nor means that Rocket Software is not owner of
any such marks.
Aldon, CorVu, Dynamic Connect, D3, FlashConnect, Pick, mvBase, MvEnterprise, NetCure,
Rocket, SystemBuilder, U2, U2 Web Development Environment, UniData, UniVerse, and
wIntegrate
Other company, product, and service names mentioned herein may be trademarks or service marks of
others.

Explore What’s New In UniData 8.1

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (6)

Semelhante a Explore What’s New In UniData 8.1

Semelhante a Explore What’s New In UniData 8.1 (20)

Último

Último (20)

Explore What’s New In UniData 8.1