DEC Rdb SQL/Services Release Notes Version 6.1

*HyperReader

CONTENTS

  Title Page

  Copyright Page

  Send Us Your Comments

  Preface

  1      SQL/Services:  New and Changed Features
    1.1 Installing SQL/Services V6.1
      1.1.1      SQL/Services Software Requirement and Compatibility Information for V6.1
      1.1.2      Revised Macintosh Client Installation
      1.1.3      Revised SunOS Client Installation
    1.2 SQL/Services New and Changed Features for V6.1
      1.2.1      New and Changed Features for V6.1
      1.2.2      SQL/Services ODBC Driver for Windows NT Alpha PC Operating System Installation Procedure
      1.2.3      Programming Using Threads on Windows NT
      1.2.4      CAPTIVE Accounts Are Optionally Allowed
      1.2.5      SQLDA2 Usability Improvements for V6.1
      1.2.6      SQL/Services V6.1 Server Supports ANSI Date-Time Queries
      1.2.7      SQL/Services Support for Windows Socket Compliant Transports for TCP/IP
      1.2.8      The File sqlsrv$msg.txt Is Now Installed in SYS$HELP
      1.2.9      SQL/Services V6.1 Supports PATHWORKS V5.0 for DOS (TCP/IP)
      1.2.10     Process Dumps Are Now Generated for Fatal Errors in SQL/Services Servers on OpenVMS AXP
      1.2.11     Additional Options Are Available for Building the Sample Application on MS-DOS and MS Windows
        1.2.11.1     Building the Sample Application on the MS-DOS Operating System
        1.2.11.2     Building the Sample Application on the MS-DOS Operating System for MS Windows Version 3.0 or 3.1
      1.2.12     Additional Help Files Are Available for V6.1
      1.2.13     Terminology Changes for V6.1
    1.3 Deprecated Features

  2      Software Errors Fixed
    2.1 SQL/Services OpenVMS AXP and OpenVMS VAX Server Errors Fixed for V6.1
      2.1.1      When SQL/Services Was Shutdown Execute Server Processes Hung with Files Open Using DEC DB Integrator Gateway fo
      2.1.2      Problem with TIME(0) Columns
      2.1.3      Default Schema Name Is Now Set for Generic Servers
      2.1.4      SQL/Services Executors Now Performs a DISCONNECT ALL After the Client Releases the Association
      2.1.5      Communications Server No Longer Fails with SYSTEM-F-BADPARAM
      2.1.6      Ensure That SQL/Services Is Started from an Account That Has No Identifiers Granted to It to Prevent the ExecuN
      2.1.7      SQL/Services Duplicate Name Error Occurred During TCP/IP Startup
      2.1.8      Problem with Group Logical Names for Generic Class Servers
      2.1.9      Select List Caused an Execute Server Access Violation
    2.2 SQL/Services Client Errors Fixed for V6.1
      2.2.1      Access Violation in sqlsrv_allocate_sqlda_data
      2.2.2      Several Invalid Parameters or Invalid Combinations of Parameters on the sqlsrv_associate Routine Caused an Acce
      2.2.3      Memory Allocation for Data Exceeding the Boundaries of a Signed Integer Caused SQL/Services to Allocate Memory
      2.2.4      Problem with Error Handling When a Multifetch Operation Was Outstanding

  3      Known Problems, Restrictions, and Other Notes
    3.1 Generally Known Problems and Restrictions for DEC Rdb V6.1 That Affect SQL/Services
    3.2 SQL/Services Known Problems and Restrictions for V6.1
      3.2.1      SQL/Services for DEC OSF/1 Restrictions and Known Problems
      3.2.2      Problem with SQL and SQL/Services Error Messages on DEC OSF/1 and Windows NT
      3.2.3      SQL/Services DEC OSF/1 Client API Does Not Support Direct Manipulation of the SQLCA and SQLDA Structures
      3.2.4      Installation Problems
      3.2.5      Process Pools Can Fall Below MIN Value
      3.2.6      Character Sets Other Than the DEC Multinational Character Set Are Not Supported
      3.2.7      Communications Server and All Execute Servers Terminate Abnormally If the Database Class Server Account Is Disa
      3.2.8      DEC Rdb V4.1A Overwrites More Recent Versions of SQL/Services
      3.2.9      Use the Node Name for DECnet with the Windows NT Client
      3.2.10     Avoid Using Cursor Names Starting with "SQLSRV_"
      3.2.11     MS-DOS and MS Windows Client NetWare Known Restrictions
      3.2.12     Unresolved External References for Non-IPX/SPX (NetWare) Applications
      3.2.13     Nonblocking Synchronous Communications Restrictions
      3.2.14     Possible Problems When Multiple Copies of sqsapiw.dll Are in a PATH
      3.2.15     SQL/Services Software Installation Requirement and Compatibility Information Replaces the SPD
      3.2.16     Known Problem in the DEC Rdb Guide to Using SQL/Services Client APIs
      3.2.17     The DEC Rdb Guide to Using SQL/Services Client APIs Did Not Describe Changes to Size and Format of Integer and
      3.2.18     You Must Call SQLSRV_CLOSE_CURSOR( ) Before COMMIT WORK
      3.2.19     Process Logical Names Are Not Supported in SQL/Services
      3.2.20     SQL/Services Compatibility Issue with the Order of Include Files
      3.2.21     Invalid Length Is Returned by SQLSRV_VARBYTE Data Type
      3.2.22     Allocating Space for SQLSRV_VARCHAR and SQLSRV_VARBYTE Data Types Can Cause a Problem