Home | Previous Page | Next Page   Migration to a Later Version of a Database Server > Preparing for Migration > Preparing for Migration >

Changes in Dynamic Server 10.0, 9.40, 9.30, and 9.2x

This section describes changes in Dynamic Server 10.0:

Environment Variables

Dynamic Server 10.0, 9.40, 9.30, 9.21, and 9.20 introduced new environment variables that might affect your installation. You might also need to adjust the values of existing environment variables. For more information on environment variables, see the IBM Informix: Guide to SQL Reference and your IBM Informix: Dynamic Server Administrator's Guide.

Table 16 lists the new environment variables in Dynamic Server 10.0, 9.40, 9.30, 9.21, and 9.20.

Table 16. New Environment Variables
Version Environment Variable Description
10.0 IFX_EXTDIRECTIVES A client-side external optimizer directive to use as a temporary solution to problems when you do not want to change SQL statements in queries
10.0 IFX_NO_TIMELIMIT_
WARNING
A variable that supports time-limited license
10.0 IFX_ONPLOAD_AUTO_
UPGRADE
A variable that enables you to automatically upgrade the onpload database the first time you invoke an HPL utility using the ipload or onpladm command after you migrate to a new database server version
10.0 STDIO A TAPEDEV configuration parameter variable that improves the speed of HDR setup
9.40 CDR_LOGDELTA Determines when spooling of the Enterprise Replication queue occurs, based on the percentage of the logical log size. Use as directed by Technical Support.
9.40 CDR_PERFLOG Enables Enterprise Replication queue tracing. Use as directed by Technical Support.
9.40 CDR_ROUTER Determines whether intermediate processing for Enterprise Replication is allowed in a hierarchal topology. Use as directed by Technical Support.
9.40 CDR_RMSCALEFACT Sets the maximum number of Enterprise Replication DataSync threads per CPU VP. Use as directed by Technical Support.
9.40 USETABLENAME Disallows the use of a synonym of the table in certain SQL statements.
9.30 IFX_DEF_TABLE_LOCKMODE Specifies the default lock mode for database tables.
9.21 AFDEBUG Forces the database system to hang when a failure occurs.
9.21 JAR_TEMP_PATH Specifies a non-default local file system location for temporary .jar files of the Java virtual machine.
9.21 JAVA_COMPILER Disables JIT compilation.
9.21 JVM_MAX_HEAP_SIZE Sets a non-default upper limit on the size of the heap for the Java virtual machine.
9.20 IFX_LONGID Determines whether a given client application is capable of handling long identifiers.
9.20 IFX_UPDDESC Allows the execution of a DESCRIBE of an UPDATE statement.
9.20 STMT_CACHE Controls the use of the shared statement cache on a session.

In Dynamic Server 9.30, the environment variable DELIMIDENT must be set before a client starts to manipulate a table with an SQL DELETE statement that omits the FROM keyword.

Configuration Parameters

Dynamic Server 10.0, 9.40, 9.30, 9.21, and 9.20 introduced new configuration parameters that might affect your installation. You might also need to adjust the values of existing parameters. For more information on configuration parameters, see the IBM Informix: Dynamic Server Administrator's Reference and your IBM Informix: Dynamic Server Administrator's Guide.

Table 17 lists the new configuration parameters in Dynamic Server 10.0, 9.40, 9.30, 9.21, and 9.20. All parameters are located in the ONCONFIG file, unless otherwise noted.

Table 17. New Configuration Parameters
Version New Configuration Parameter Description
10.0 ALRM_ALL_EVENTS Specifies whether ALARMPROGRAM runs for all events that are logged in the MSGPATH or only specified noteworthy events.
10.0 BUFFERPOOL Specifies configuration information for a buffer pool for each different page size used by a dbspace.
10.0 CDR_SUPPRESS_
ATSRISWARN
Enterprise Replication configuration parameter that specifies whether comma- separated error and warning numbers are suppressed from ATS and RIS files.
10.0 DR_IDXAUTO Determines how a secondary database server reacts to a high-availability data-replication failure.
10.0 DS_NONPDQ_QUERY_MEM Enables you to increase the amount of sort memory that is available for a query that is not a PDQ query.
10.0 EXT_DIRECTIVES An external optimizer directive that provides a temporary solution to problems when you do not want to change SQL statements in queries
10.0 FAST_RESTART_CKPT_
FUZZYLOG
Enables the flushing of dirty-pages table (DPT) records to the physical log on fuzzy checkpoints during the roll-forward phase of recovery. Like FAST_RESTART_PHYSLOG, this parameter decreases recovery time.
10.0 FAST_RESTART_PHYSLOG Enables the database server to perform physical logging on fuzzy checkpoints during the roll-forward phase of recovery.
10.0 IFX_EXTEND_ROLE Enables a database server administrator (DBSA) to prevent unauthorized users from registering DataBlade user-defined routines (UDRs).
10.0 LISTEN_TIMEOUT Sets the incomplete connection timeout period. The default value is 10 seconds.
10.0 MAX_INCOMPLETE_
CONNECTIONS
Restricts the number of incomplete requests for connections.
10.0 ONLIDX_MAXMEM Limits the amount of memory that is allocated to the preimage log pool and to the updator log pool in shared memory. You can use this configuration parameter if you plan to complete other operations on a table column while executing the CREATE INDEX ONLINE statement on the column.
10.0 TBLTBLFIRST Specifies the first extent size of tblspace tblspace in kilobytes.
10.0 TBLTBLNEXT Specifies the next extent size of tblspace tblspace in kilobytes.
9.40 ASF_SOCTCP_BACKLOG Specifies the number of connections queuing when using Sockets (SOCTCP).
9.40 CDR_DBSPACE Defines the default dbspace for the Enterprise Replication syscdr database.
9.40 CDR_ENV Sets Enterprise Replication environment variables CDR_LOGDELTA, CDR_PERFLOG, CDR_ROUTER, and CDR_RMSCALEFACT.
9.40 CDR_MAX_
DYNAMIC_LOGS
Specifies the number of dynamic log file requests that Enterprise Replication can make in one server session.
9.40 ENCRYPT_CDR Enables and sets the level of network encryption for Enterprise Replication.
9.40 ENCRYPT_CIPHER Specifies the ciphers to use for encryption for Enterprise Replication.
9.40 ENCRYPT_MAC Specifies the level of message authentication coding to use for Enterprise Replication.
9.40 ENCRYPT_MACFILE Specifies MAC key files for Enterprise Replication.
9.40 ENCRYPT_SWITCH Defines the frequency at which ciphers and secret keys are re-negotiated for Enterprise Replication.
9.40 HPL_DYNAMIC_LIB_
PATH
For the High-Performance Loader, sets the location of the shared-library file containing custom-code functions. Located in the plconfig file.
9.40 HPLAPIVERSION For the High-Performance Loader, sets whether custom-code functions can use different input and output data lengths. Located in the plconfig file.
9.40 PLOG_OVERFLOW_PATH Sets the location of the temporary space to extend the physical log during fast recovery.
9.30

CDR_QHDR_DBSPACE

Specifies the dbspace Enterprise Replication uses to store the transaction record headers spooled from the send and receive queues.
9.30 CDR_QDATA_SBSPACE Specifies the sbspace Enterprise Replication uses to store spooled transaction row data.
9.30 DEF_TABLE_LOCKMODE Sets the lock mode to row for every newly created table.
9.30 DYNAMIC_LOGS Controls dynamic log allocation. This parameter is not in the default ONCONFIG file.
9.30 SBSPACETEMP Specifies the name of the default temporary sbspace for storing temporary smart large objects.
9.21

DS_HASHSIZE

Specifies the number of hash buckets in the data-distribution cache for statistics generated by the UPDATE STATISTICS statement.
9.21 DS_POOLSIZE Specifies the maximum number of entries in each hash bucket for statistics generated by the UPDATE STATISTICS statement.
9.21 STMT_CACHE_HITS Specifies the number of references to a statement before it is fully inserted in the SQL statement cache.
9.21 STMT_CACHE_NOLIMIT Controls whether to insert qualified statements into the SQL statement cache after its size is greater than the STMT_CACHE_SIZE value.
9.21 STMT_CACHE_NUMPOOL Specifies the number of memory pools for the SQL statement cache.
9.20 ALLOW_NEWLINE Controls whether the database server allows the newline character (\n) in a quoted string.
9.20 DD_HASHMAX Specifies the maximum number of tables in each hash bucket in the data-dictionary cache.
9.20 DD_HASHSIZE Specifies the number of hash buckets or lists in the datadictionary cache.
9.20 OPT_GOAL Specifies optimization goals.
9.20 PC_HASHSIZE Specifies the number of hash buckets in the caches that the database server uses.
9.20 PC_POOLSIZE Specifies the maximum number of entries in several memory caches that the database server uses.
9.20 STMT_CACHE Determines whether the database server uses the SQL statement cache.
9.20 STMT_CACHE_SIZE Specifies the size of the SQL statement cache.
9.20 SYSSBSPACENAME Specifies the name of the sbspace for statistics collected by the UPDATE STATISTICS statement for certain user-defined data types.

Table 18 lists the configuration parameters that were altered or removed in Dynamic Server 10.0, 9.40, and 9.30. No changes were made to configuration parameters in Dynamic Server 9.21 and 9.20.

Table 18. Altered Configuration Parameters
Version Altered Configuration Parameter Description of Change
10.0 BUFFERS Removed. Information now specified with the BUFFERPOOL configuration parameter.
10.0 LRUS Removed. Information now specified with the BUFFERPOOL configuration parameter.
10.0 LRU_MAX_ DIRTY Removed. Information now specified with the BUFFERPOOL configuration parameter.
10.0 LRU_MIN_ DIRTY Removed. Information now specified with the BUFFERPOOL configuration parameter.
9.40 ALARMPROGRAM Can be set to the alarmprogram.sh file to enable event alarms.
9.40 CDR_QDATA_SBSPACE Can accept up to 32 sbspaces.
9.40 CDR_QDATA_SBFLAGS Removed. Enterprise Replication always uses the default log mode of the sbspace for spooling row data.
9.40 DBSERVERALIASES Can accept up to 32 server alias values.
9.40 LTAPEBLK The default value is 32 KB.
9.40 LTAPESIZE Can accept a value of 0 to read or write to the end of the tape device.
9.40 LRU_MAX_DIRTY Can accept a value of type INTEGER or FLOAT. (This configuration parameter was removed in Version 10.0.)
9.40 LRU_MIN_DIRTY Can accept a value of type INTEGER or FLOAT. (This configuration parameter was removed in Version 10.0.)
9.40 OPTICAL_LIB_PATH Is valid for both UNIX and Windows. Must be set to the location of the storage manager library.
9.40 TAPEBLK The default value is 32 KB.
9.40 TAPESIZE Can accept a value of 0 to read or write to the end of the tape device.
9.30

AFF_NPROCS

Removed; superseded by the VPCLASS configuration parameter.
9.30

AFF_SPROC

Removed; superseded by the VPCLASS configuration parameter.
9.30

CDR_LOGBUFFERS

Removed.
9.30

CDR_LOGDELTA

Removed.
9.30

CDR_NIFRETRY

Removed.
9.30

CDR_NUMCONNECT

Removed.
9.30

JDKVERSION

New default value of 1.3.
9.30 JVPJAVAHOME New default value of /usr/informix/extend/krakatoa.
9.30

JVPJAVALIB

New default value that is platform dependent.
9.30

JVPJAVAVM

New default value that is platform dependent.
9.30

LBU_PRESERVE

Removed; configured an obsolete utility.
9.30

LOGSMAX

Removed.
9.30 LTXHWM Removed from the default ONCONFIG file, but is still valid.
9.30 LTXEHWM Removed from the default ONCONFIG file, but is still valid.
9.30 NOAGE Removed; superseded by the VPCLASS configuration parameter.
9.30 NUMAIOVPS Removed; superseded by the VPCLASS configuration parameter.
9.30 NUMCPUVPS Removed; superseded by the VPCLASS configuration parameter.

SQL Reserved Words

Dynamic Server 10.0, 9.40, 9.30, 9.21, and 9.20 support new SQL keywords that are reserved words and might affect migration of your applications. Although you can use almost any word as an SQL identifier, syntactic ambiguities might occur if you use an SQL reserved word. An ambiguous statement might not produce the results you want.

The list below shows new SQL reserved words. For more information about SQL reserved words, see the IBM Informix: Guide to SQL Syntax.

Version 10.0:

Version 9.40

Version 9.30

Version 9.21

Version 9.20

Version 9.20 and 7.31

Version 9.20 and 7.30

System Catalog and sysmaster Changes

The system catalog tables and sysmaster database are different from those for database servers earlier than Dynamic Server 9.20, which includes changes to some column widths, data types, and treatment of null values. Also, some tables have additional columns, and some tables were added or deleted.

Remote Queries on System Catalog Tables Between 7.x and 9.x or later

Certain system catalog tables use data types in Dynamic Server 9.x or later that are not supported in Dynamic Server 7.x. Remote queries that issue a SELECT * statement on these system catalog tables from Dynamic Server 7.x to Dynamic Server 9.x or later will fail.

For example, the following queries that originate on a Dynamic Server 7.x fail when executed on Dynamic Server 9.x or later:

SELECT * FROM dbname@remoteserver:sysindices;
SELECT * FROM dbname@remoteserver:sysindexes;

Instead of using an asterisk as the Projection clause, specify the required column names explicitly. You cannot specify any columns that have user-defined types.

Difference in sysindexes

In Version 7.x, sysindexes is a table. In Dynamic Server 10.0, 9.40, 9.30, and 9.2x, sysindexes is a view. The ALTER TABLE statement fails for sysindexes because this statement is not valid for altering a view.

Column-Width Changes

Version 9.20 and later versions of Dynamic Server provide long identifiers. All identifiers in the system catalog tables and the sysmaster database reflect these new limits on identifier length. The IBM Informix: Guide to SQL Syntax defines identifiers, which specify the names of database objects.

The column widths for identifiers that refer to database objects and other identifiers changed from CHAR(18) to VARCHAR(128,0) in the following system catalog tables:

sysaggregates
sysams
sysattrtypes
sysblobs
syscasts
syscolattribs
syscolumns
sysconstraints
sysdomains

sysfragauth
sysfragments
sysindexes
sysindices
sysobjstate
sysopclasses
sysopclstr
sysprocedures

sysroutinelangs
syssynonyms
syssyntable
systabamdata
systables
systracemsgs
systriggers
sysxtdtypes

Identifiers changed from CHAR(18) to CHAR(128) in the following sysmaster database tables:

arc_dbspace
arc_dbspace_set
arc_phys_dev
arc_rep_table
arc_replicate
arc_server
arc_version
arc_vset
arc_vset_view
flags_text
syscfgtab
sysconfig

syscrtadt
sysdatabases
sysdbslocale
sysdbspaces
sysdbspartn
sysdbstab
sysdic
sysdiccache
sysdistcache
sysdsc
sysextents
sysextspaces

syslocks
sysopendb
sysprc
sysproccache
sysptprof
syssdblock
syssqlcurall
syssqlcurses
syssqlstat
systabnames
systrans
systxptab

Column widths for user login identifiers changed from CHAR(8) to CHAR(32) in some system catalog tables and sysmaster database tables. The following system catalog tables changed:

sysaggregates
sysams
syscasts
syscolauth
sysconstraints
sysdomains
sysfragauth
sysindexes

sysindices
syslangauth
sysobjstate
sysopclasses
sysopclstr
sysprocauth
sysprocedures
sysroleauth

syssynonyms
syssyntable
systabauth
systables
systriggers
sysusers
sysxtdtypeauth
sysxtdtypes

The following sysmaster database tables changed:

sysaudit
sysdatabases
sysdbspaces
sysdbspartn
sysdbstab
sysdic

sysdiccache
sysdistcache
sysdsc
sysextspaces
sysprc
sysproccache

sysrstcb
sysscblst
syssessions
systabnames
sysuserthreads

Columns that include pathnames or other values changed from CHAR(128) to CHAR(256) in the following sysmaster database tables:

sysadtinfo
syschktab
syschunks

syscrtadt
sysdrcb
sysdri

sysmchktab

The path for a physical device changed from CHAR(128) to CHAR(260) in the following sysmaster database table:

arc_phys_dev

Columns widths changed from CHAR(20) to CHAR(128) for longer object names in the following sysmaster database tables:

sysdrcb
sysdris

Column widths changed from CHAR(37) to CHAR(257) in the following sysmaster database tables:

sysdistcache
sysdsc

sysprc
sysproccache

Column widths changed from DECIMAL(16,0) to DECIMAL(32,0) in the following sysmaster database table:

syssesprof

The tabauth column of the systabauth system catalog table is now CHAR(9) instead of CHAR(8). The 9th character indicates the Under privilege.

Data Type Changes

The preceding section on column-width changes lists columns that have changed from the CHAR data type to the VARCHAR data type.

One or more columns changed from the SMALLINT data type to the integer data type in the following sysmaster database tables:

sysdbspaces
sysdbstab

sysdic
sysrstcb

syssdblock

The CHAR data type changed to the STAT data type in the following system catalog table:

sysdistrib

Changes in Treatment of Null Values

No nulls allowed changed to nulls allowed for some columns in the following sysmaster database tables:

arc_ae_view
arc_db_file_view
arc_directory_view
arc_file_copy_view
arc_file_view

arc_pendreq_view
arc_req_vset_view
arc_request_view
arc_save_set_view
arc_vol_lock_view

arc_volume_view
arc_vset_user_view
arc_vset_view

Columns Added

One or more columns have been added to the following system catalog tables:

sysams
sysdistrib

sysprocedures
sysroutinelangs

Several columns have been added to the following sysmaster database table:

sysdbstab

Tables Added or Deleted

The following tables have been added to the sysmaster database:

logmessage
syscdrack_buf
syscdrack_txn
syscdrctrl_buf

syscdrctrl_txn
syscdrprog
syscdrq
syscdrrecv_buf

syscdrrecv_txn
syscdrtx

The following table has been deleted from the sysmaster database:

arc_change_log

Changes for Dynamic Server 10.0

The sysdirectives system catalog table was added.

The sysbufpool system-monitoring interface (SMI) table was added, and the following changes were made to other SMI tables:

In addition, tables added to the sysscdr database are removed.

Changes for Dynamic Server 9.40

The following new system catalog table was added:

syssequences

A new collation column has been added to the following system catalog tables:

sysconstraints
sysindices

sysprocplan

systrigbody

Changes for Dynamic Server 9.30

The following tables were deleted from the sysmaster database in Version 9.30:

arc_ae_view
arc_db_file_view
arc_dbspace
arc_dbspace_set
arc_directory_view
arc_file_view
arc_file_copy_view

arc_pendreq_view
arc_phys_dev
arc_rep_table
arc_replicate
arc_req_vset_view
arc_request_view
arc_save_set_view

arc_server
arc_version
arc_vol_lock_view
arc_volume_view
arc_vset
arc_vset_user_view
arc_vset_view

Feature Changes

The following feature changes are in Dynamic Server 10.0:

In addition, the DRAUTO configuration parameter, which was removed from Dynamic Server in Version 9.3, is again included in the ONCONFIG file. For a description of this parameter, see The DRAUTO Configuration Parameter.

The following feature changes are in Dynamic Server 10.0 as well as Dynamic Server versions 9.40, 9.30, and 9.2x:

The DRAUTO Configuration Parameter

The DRAUTO configuration parameter was present in some earlier versions of Dynamic Server, including Version 7.3. It was removed from Version 9.3, but is included in Version 10.0. This parameter determines how a secondary database server reacts to a high-availability data-replication (HDR) failure.

If the DRAUTO configuration parameter in the ONCONFIG file of the secondary database server in an HDR pair is set to 1 (RETAIN_TYPE) or 2 (REVERSE_TYPE) and the primary database server in the pair fails, the secondary database server automatically becomes the standard database server. It first rolls back any open transactions and then comes into on-line mode as the standard database server. For more information on using this parameter, see the IBM Informix: Dynamic Server Administrator's Guide.

Detached Indexes

By default, all new indexes that the CREATE INDEX statement creates in Dynamic Server 10.0, 9.40, 9.30, or 9.2x are detached and stored in separate tablespaces from the data (unless the deprecated "IN TABLE" syntax is specified). Indexes created in Version 7.x are attached until you rebuild them.

You cannot revert detached indexes to Version 7.x. To enable reversion to Version 7.x, retain the Version 7.x attached index behavior by setting the environment variable DEFAULT_ATTACH in the application environment. You can attach only B-tree indexes that are nonfragmented and that are on nonfragmented tables (the Version 7.x behavior). All other indexes, including extensibility related indexes such as R-trees and UDT indexes, must be detached.

Changes in ON-Bar Commands

Between Dynamic Server 7.x and Dynamic Server 9.x and later, the syntax of the following ON-Bar commands changed:

Dynamic Server 7.x:
onbar -r -v
Dynamic Server 9.x or later:
onbar -v
Dynamic Server 7.x:
onbar -l
Dynamic Server 9.x or later:
onbar -b - l
Chunk Format

Dynamic Server 9.40 introduced for the following chunk features that cannot be reverted:

To facilitate backward compatibility, these features are not enabled by default. To enable these features, use the onmode -BC command.

The onmode -BC command has the following options that allow you to stage your migration to these features:

Libraries No Longer Installed in the /usr/lib Directory

Dynamic Server 9.40 and 10.0 do not include the following libraries in the /usr/lib directory on UNIX:

VARCHAR Column Limit

If you are migrating from Dynamic Server 7.3x, the number of VARCHAR columns per table for Dynamic Server 10.0, 9.40, 9.30, or 9.2x has been reduced from 231 to 195, within a row size of 32,762 bytes and based on a page size of 2 kilobytes. Before you upgrade to Dynamic Server 10.0, ensure that your tables obey this restriction.

Stored Procedure Parameter Limit

Dynamic Server 10.0, 9.40, 9.30, or 9.2x have a limit of 341 parameters for each stored procedure.

Limitation on Using Routines in Distributed Transactions

User-defined routines and built-in routines, such as round(), cannot be used in distributed transactions involving Dynamic Server 9.2x or 9.30. For Dynamic Server 9.40 and 10.0, routines in distributed transactions are only supported among Version 9.40 and 10.0 database servers.

Case-Sensitive Name Space

If you have case-insensitive schemas, you might need to revise them because Dynamic Server 10.0, 9.40, 9.30, or 9.2x have a case-sensitive name space. This can affect the resolution of blobspaces and SPL names.

New Administration Tools

Dynamic Server 10.0, 9.40, 9.30, and 9.21 do not support IECC. The IECC functionality for these database servers comes from the following sources:

Server Studio JE

Included in the IBM Informix Dynamic Server bundle is a CD containing Server Studio JE (Java Edition). Server Studio JE is the result of an extensive collaboration between IBM and Advanced Global Systems LTD (AGS).

Before using any Server Studio features, you must first register with AGS. When you use Server Studio to build the first connection to a database server, you will find information on how to register. Once registered, you will receive an email with a certificate to install. You must install this certificate to access Server Studio features.

Once you have registered, you can use the following features for an unlimited period of time:

In addition, during the first 30 days of use, several other modules are enabled on a trial basis. After the 30-day-trial period, the unlicensed add-on modules will not work and will generate expiration messages. To continue using the add-on modules after 30 days, you must obtain a license for those modules directly from Advanced Global Systems LTD (AGS).

Some of the add-on modules that are available inside Server Studio JE are:

For a complete list of the currently available add-on modules visit the AGS website at www.agsltd.com.

IBM Informix Server Administrator

IBM Informix Server Administrator (ISA) is a browser-based tool that provides Web-based system administration for all Informix 10.0, 9.40, 9.30, 9.2x, 8.40, 8.3x, 8.21, 7.3x, and 7.24 database servers. ISA provides access to database server command-line functions and presents the output in an easy-to-read format.

With ISA, you can use a browser to perform these common database-server administration tasks:

The database server CD-ROM distributed with your product includes ISA. For information on how to install ISA, see the following file on the CD-ROM.

Operating System
File
UNIX or Linux
/SVR_ADM/README
Windows
\SVR_ADM\readme.txt
Management of the SQLHOSTS Connectivity Information on Windows

On Windows, IBM Informix products store the SQLHOSTS information in registry keys. Windows provides the regedt32 utility, which enables you to manage registry keys, but it is recommended that you do not use regedt32.

If you have used Setnet32 to manage SQLHOSTS information, you can continue to do so; however, Setnet32 does not enable you to assign a database server to a database server group.

For Enterprise Replication, use ISA.

Maximum index key size difference between 9.x or later and 7.3

Before reverting to Dynamic Server 7.3, you must drop any index whose key size is greater than 254. Dynamic Server 9.4 supports a maximum index key size of 255 for VARCHAR and NVARCHAR types. However, Dynamic Server 7.3 only supports a maximum index key size of 254.

New Features

This section list new features in Dynamic Server 10.0, 9.40, 9.30, 9.21, and 9.20. Read your release notes and documentation notes for late-breaking information on new features.

New Features in Dynamic Server 10.0

Dynamic Server 10.0 introduces the following new features:

New Features in Dynamic Server 9.40

Dynamic Server 9.40 introduces the following new features:

New Features in Dynamic Server 9.30

Dynamic Server 9.30 has the following new features:

New Features in Dynamic Server 9.21

Dynamic Server 9.21 introduced the following new features:

New Features in Dynamic Server 9.20

Dynamic Server 9.20 introduced the following new features:

Version 9.20 Features from Universal Server 9.14

Dynamic Server 9.20 includes the following features that were first released in Universal Server 9.1x:

Version 9.20 Features from Dynamic Server 7.30

Dynamic Server 9.20 also has features first released in Dynamic Server 7.30:

Home | [ Top of Page | Previous Page | Next Page | Contents | Index ]