TS DataServerTS DataServer


Contact Us  |  Enhancements  |  Changes

Enhancements [up]

TS ODBC DataServer™

  1. A new message "Record is Locked" is displayed when an UPDATE or DELETE is issued for a locked record.
  2. Performance improvement. PRM JOURNALING is ignored if the server is installed as Read-Only.

TS Network DataServer™

  1. Stand-alone activation program.
  2. Added ENABLE disk-no,"RECONNECT", allowing Basic to reestablish a connection.

TS ORACLE DataServer™/TS DataServer™ for MS SQL Server

  1. Stand-alone activation program.
  2. Added ENABLE disk-no,"RECONNECT", allowing Basic to reestablish a connection.
  3. Performance improvement for TS DataServer for MS SQL Server. Implemented additional caching of the cursor used for each channel for READ, eliminating some library calls.
  4. Performance improvement. Some Basic side logic for READ has been modified to improve performance in sequential reading on secondary sorts. WRITE with DOM= are now faster, a pre-READ to determine if we need to do INSERT or UPDATE is no longer executed.
  5. SET CTC and CTC(). Allow the setting of and retrieving of the COMMIT COUNT from Basic.
  6. If data for the numeric is all spaces and PRM SQL-NUMERIC-NULLS is set and PRM ORA-DONTWRITENULLS is not set, numeric fields will be written to the database as NULL.

TS DataServer™ for MS SQL Server

  1. Support modification of text fields from SQL Server.

Changes [up]

TS ODBC DataServer

  1. Reference: ORDER BY
    ODBC SERV 0009

    Recognize ORDER BY secondary keys that include date type 5 with time and date type 8 with time.
  2. Reference: Y/N and Date fields
    ODBC SERV 0010

    Allow Y/N and Date fields to be set empty as in FORMAT INIT.
  3. Reference: V8.6.0 Only
    ODBC SERV 0013

    A problem causing connect failures with Reason 107 has been fixed.

TS Network DataServer

  1. Reference: ADDSORT/REMSORT
    Fixed ADDSORT and REMSORT problems when the file is accessed via the DataServer.

TS DataServer for MS SQL Server/TS ORACLE DataServer

  1. Reference: SQL Date Type 5
    Fixed an SQL date type 5 length 6 problem where the 50/50 year rule was being erroneously applied. For example, with that date type if a user entered a date with the year 1958, it was getting stored on the server side as 2058.