CONTENTS Title Page Copyright Page Preface 1 New and Changed Features 1.1 Rdb/VMS V4.1 Has Multiple Version Support for Running Both V4.0 and V4.1 on the Same Node or in the Same VAXcluster 1.2 Deinstall/Delete Command Procedure 1.3 New Update Rules in Rdb/VMS V4.1-Modify and Erase Operations May Fail in RDO, RDBPRE, and RDML 1.4 Online Help 1.4.1 Accessing DCL-Level Help Topics Related to Rdb/VMS Using the Standard Version of Rdb/VMS V4.1 1.4.2 Accessing DCL-Level Help Topics Related to Rdb/VMS Using the Varianted Version of Rdb/VMS V4.1 1.5 Rdb/VMS Security Auditing 1.5.1 Security Audit Log Format Is Changed 1.5.2 RMU/SET AUDIT and RMU/SHOW AUDIT Commands Have New and Changed Qualifiers and Keywords 1.6 Query Optimizer Enhancements 1.6.1 Displaying Estimated Query Cost 1.6.2 Limiting Query Execution with the Query Governor 1.6.3 Setting a Preferred Query Optimization Mode 1.6.4 Quick Index Lookup in the Dynamic Optimizer 1.6.5 Improved OR Optimization 1.6.6 MIN/MAX Aggregate Optimization 1.6.7 Improved View Optimization 1.6.8 Preventing Anomalous Updates That Can Occur with Subqueries 1.7 Using Global Buffers 1.7.1 Enabling Global Buffers 1.7.2 Applications That Benefit from Using Global Buffers 1.8 Journal Fast Commit Transaction Processing and Commit to Journal Optimization 1.8.1 Commit to Journal Optimization 1.9 Recovering from a Lost .AIJ File When Journal Fast Commit Transaction Processing Is Enabled 1.10 Carry-Over Locks Optimization Can Be Disabled 1.11 After-Image Journal Optimization 1.12 Changes to the EXPORT/IMPORT Statements for V4.1 1.12.1 SQL and RDO IMPORT and EXPORT Statements Support All New Rdb/VMS V4.1 Features 1.12.2 Changed Syntax for the SQL IMPORT Statement 1.12.3 Changed Syntax for the SQL EXPORT Statement 1.12.4 NO EXTENSIONS Error Checking 1.13 Online DBA Activities 1.14 Offline DBA Activities 1.15 Rdb/VMS Now Supports Creating Storage Areas for Segmented Strings and List Data on WORM Optical Disks 1.16 Other New and Changed Features for V4.1 That Affect All Interfaces 1.16.1 Performance Improvement for Creating Tables and Views 1.16.2 New On-Disk Format for Segmented Strings (List of Byte Varying) 1.16.3 Storing Lists Randomly Across Storage Areas 1.16.4 Change in Utilization of SPAM Thresholds 1.16.5 Nontext Fields with Collating Sequences Are No Longer Allowed 1.16.6 Default Lock Timeout Interval 1.16.7 Batch Writes to Disk 1.16.8 Minimum Value for the SPAM Interval Is Changed from 256 to 216 1.16.9 Table Metadata Lock WAIT/NOWAIT Behavior Is Changed and a Single User Request for a Freeze Lock Is Now Queued 1.16.10 Change in Operation of Index Deletion 1.16.11 Buffers for Storage Areas Are No Longer Invalidated When the Lock Mode Is Changed (from CR <=> CU) 1.16.12 Change in Getting Event Flags from the RDB$RDBSHR_EVENT_FLAGS Logical Name 1.16.13 .RUJ Files Are No Longer Created with the UIC of the Process That Created the File 1.16.14 Changes to RDB$FIELDS and RDB$FIELD_VERSIONS System Relations 1.16.15 .AIJ File Is Now Initialized Upon Creation 1.16.16 VAXcluster Nodes up to 96 Are Now Supported 1.16.17 Change to SYS REQUEST Error Called from 113 1.16.18 Prototype Syntactic Forms of Vertical Record Partitioning Are Not Possible in V4.1 Storage Map Statements 1.17 SQL: New and Changed Features and Statements for V4.1 1.17.1 Multischema Databases 1.17.2 Sample Multischema Database 1.17.3 Authorization Identifiers 1.17.4 Multischema Naming 1.17.5 Run-Time SQL Kit 1.17.6 Reserved Words as Identifiers 1.17.7 Nested View Updates with CHECK OPTION 1.17.8 RESTRICT Argument Now Implicit for DROP TABLE Statement 1.17.9 SINGLE Predicate Replaces UNIQUE Predicate 1.17.10 SQLDA2 Structure 1.17.11 ORDER BY and LIMIT TO Clauses Are Allowed in Subqueries 1.17.12 Constraint Keyword Changes 1.17.13 Connections 1.17.14 Extended Dynamic Cursors 1.17.15 Optional Colons in Module Language Parameters 1.17.16 Error Literals 1.17.17 Date-Time Data Types and Date Arithmetic 1.17.18 Date-Time Functions 1.17.19 QUADWORD Is Changed to BIGINT 1.17.20 C Language and CDD Support for CHAR Data Types 1.17.21 ALTER DOMAIN Now Allows DATE to Be Converted to VARCHAR 1.17.22 Segmented String Storage on Write-Once Read-Many (WORM) Devices 1.17.23 Logical Area Thresholds for Uniform Areas 1.17.24 Interactive SET EXECUTE and SHOW EXECUTION MODE Statements 1.17.25 Interactive SET WARNING and SHOW WARNING MODE Statements 1.17.26 Interactive SET FLAGGER and SHOW FLAGGER MODE Statements 1.17.27 SET ALIAS Statement 1.17.28 SQLDA.SQLVAR Has a Structure Name in VAX C 1.17.29 SQL INSERT Statement Now Accepts Value Expressions 1.17.30 Journal Fast Commit Transaction Processing and Commit to Journal Optimization 1.17.31 Global Buffers 1.17.32 Changed Behavior for the ALTER TABLE Statement 1.17.33 SQL Code Generation Improvements 1.17.34 Commit-Time and Rollback Optimization for Explicitly Closed Cursors in Embedded SQL and SQL Module Language 1.17.35 Update Locking for Cursors 1.17.36 Sample Programs in Precompiled SQL and SQL Module Language 1.17.37 Deprecated Syntax 1.17.38 New SHOW DEFAULT Statement 1.17.39 VAX Data Distributor Statements Are Dynamically Executable 1.17.40 SQL Now Produces Bugcheck Dump Files When an Internal Error Is Detected 1.18 SQL/Services: New and Changed Features for V4.1 1.18.1 New SQL/Services APIs for THINK C, Windows 3.0, and SunOS 1.18.2 A New Network Transport Supported by SQL/Services: TCP/IP 1.18.3 Detached Processes Have Replaced Batch Queues for Processing Execution Servers 1.18.4 SQL/Services Server Report Utility for Execution Server Process Reporting 1.18.5 SQL/Services Deprecates Support for Filter Expressions 1.18.6 SQL/Services Multiple Version Support 1.18.7 SQL/Services Support for New SQL Features 1.18.8 SQL/Services VMS API Is Shipped with Rdb/VMS Run-Time Kit 1.18.9 SQL/Services Provides MS-DOS Executable Forms of the SQLSRV$DYNAMIC Sample Program 1.18.10 Changes to the SQL/Services Configuration File 1.18.11 SQL/Services Database Class Servers Are Supported in Rdb/VMS Version 4.1 1.18.12 Null Termination of ASCII Strings 1.18.13 New API Routine SQLSRV_SQLDA_REF_DATA Is Added 1.18.14 OS/2 Support 1.19 RDO: New and Changed Features and Statements for V4.1 1.19.1 SHOW FIELD Statement Displays the New SQL Date-Time Data Types 1.19.2 Additional RDO Enhancements for V4.1 1.19.3 RDO IMPORT Supports the Full Range of New V4.1 Features 1.19.4 Support for Carry-Over Locks 1.19.5 Support for Default Lock Wait 1.19.6 Support for Fast Commit Transaction Processing and Commit to Journal Optimization 1.19.7 Support for Global Buffers 1.19.8 Support for Query Governor 1.19.9 Support for Modifiable Logical Area Thresholds for Uniform Storage Areas 1.19.10 SET LINE_LENGTH Statement Is Restricted to 512 Bytes 1.19.11 Clarification of Behavior of F_FLOATING Data Type 1.20 RDBPRE: New and Changed Features and Statements for V4.1 1.20.1 Query Governor 1.21 RDML: New and Changed Features and Statements for V4.1 1.21.1 Query Governor 1.22 RMU: New and Changed Features for V4.1 1.22.1 Indirect File References Can Be Used for the Following RMU Command Qualifiers 1.22.2 RMU/DUMP and RMU/CLOSE Commands No Longer Require VMS SYSPRV Privilege 1.22.3 New RMU Command Qualifiers Common to More Than One RMU Command 1.22.4 RMU/ANALYZE, RMU/ANALYZE/INDEXES, and RMU/ANALYZE/PLACEMENT Commands 1.22.5 RMU/BACKUP Command 1.22.6 RMU/BACKUP/AFTER_JOURNAL Command 1.22.7 RMU/CONVERT Command 1.22.8 RMU/COPY_DATABASE Command 1.22.9 RMU/DUMP/AFTER_JOURNAL Command 1.22.10 RMU/DUMP/BACKUP Command 1.22.11 RMU/DUMP/EXPORT Command 1.22.12 RMU/EXTRACT Command 1.22.13 RMU/LOAD Command 1.22.14 RMU/MOVE_AREA Command 1.22.15 RMU/OPEN Command 1.22.16 RMU/OPTIMIZE/AFTER_JOURNAL Command 1.22.17 RMU/RECOVER Command 1.22.18 RMU/REPAIR Command 1.22.19 RMU/RESTORE Command 1.22.20 RMU/RESTORE/ONLY_ROOT Command 1.22.21 RMU/SHOW LOCKS Command 1.22.22 RMU/SHOW STATISTICS Command 1.22.23 RMU/SHOW USERS Command 1.22.24 RMU/UNLOAD Command 1.22.25 RMU/VERIFY Command 1.23 New and Changed Rdb/VMS Logical Names for V4.1 1.23.1 The Logical Name RDMS$BIND_VM_SEGMENT Changed 1.23.2 Setting the Query Optimizer Elapsed Time Limit with the Logical Name RDMS$BIND_QG_TIMEOUT 1.23.3 Setting the Query Optimizer Row Number Delivery Limit with the Logical Name RDMS$BIND_QG_REC_LIMIT 1.23.4 Specifying the RDM$BIND_CKPT_TRANS_INTERVAL Logical Name to Define a Checkpoint Interval 1.23.5 Using the RDMS$USE_OLD_UPDATE_RULES Logical Name in RDO to Preserve Update Behavior 1.23.6 Using the RDMS$USE_OLD_SEGMENTED_STRING Logical Name 1.23.7 Using the RDMS$BIND_SEGMENTED_STRING_COUNT Logical Name 1.23.8 Using the RDMS$BIND_SEGMENTED_STRING_DBKEY_SCOPE Logical Name 1.23.9 Using the RDB$CHARACTER_SET Logical Name 1.23.10 RDMS$BIND_WORK_FILE Logical Name Is Changed 1.23.11 New Logical Name, RDM$BIND_STATS_DISABLED, Disables the Writing of Database Statistics for a Process 1.23.12 New Logical Name, RDM$MON_USERNAME, Allows the Monitor Process to Inherit Quotas of the Specified User 1.24 Obsolete Statements and Features 1.24.1 SQL Deprecated Features and Incompatible Changes for Rdb/VMS Version 4.1 1.24.2 Obsolete RDO Statements Removed Completely 1.24.3 RDO Obsolete Statements and Features 1.25 Summary of Documentation Additions and Changes for V4.1 2 Software Errors Fixed 2.1 General Information 2.1.1 VMS Sort Utility for VMS V5.1, V5.2, and V5.3 Caused Problems with Rdb/VMS Databases 2.2 Software Errors Fixed in V4.1 That Apply to All Interfaces 2.2.1 Rdb/VMS Behavior Had Changed so That Buffers Were Emptied on Rollback 2.2.2 Lock-Related Looping Problem 2.2.3 NOWAIT Transactions Started During a Recovery Process Caused an RDMS-F-AREABUSY Fatal Error 2.2.4 Bugcheck Sometimes Resulted When a Sorted Index Rebalanced Itself 2.2.5 Locking Protocol Problem Caused Bugchecks 2.2.6 SPAM Pages Were Not Updated Correctly 2.2.7 Global Section Was Corrupted When a User Had Multiple Attaches 2.2.8 Range Query Returned Unexpected Results 2.2.9 Some Update-Intensive Applications Experienced a Performance Degradation in Rdb/VMS V4.0 Compared to V3.1B 2.2.10 Rdb/VMS Doing a Remote Fetch Went into a Compute Bound Loop When the Network Link Failed 2.2.11 Wrong RDBINTSHR.EXE Image Was Installed for Interactive License Customers 2.2.12 Active Transactions in Application Programs Could Not Recover from Network Failures 2.2.13 Using Event Flags Caused Conflicts with Other Software Products 2.2.14 An Access Violation Resulted When DECdtm Services and DECnet Services Were Not Running 2.2.15 If a Commit Failed During a One-Phase Commit Protocol When an Explicit Distributed Transaction Was Run, It Cause$ 2.2.16 The Rdb/VMS DISTRIBTRAN Privilege Was Not Available for Remote Database Access 2.2.17 Problem with the Use of Virtual Memory 2.2.18 Virtual Memory Increased with Some Fourth-Generation Languages 2.2.19 Remote File Specifications Were Incorrectly Formatted 2.2.20 SORTWORK Files Were Not Closed Properly During Image Rundown 2.2.21 Monitor Produced a Bugcheck in the MON$FIND_USER Routine 2.2.22 A Bugcheck Was Produced Within the Monitor Log File During Heavy Monitor Activity 2.2.23 Rdb/VMS Monitor Failed When the Last User Finished on a Particular Database 2.2.24 Defining a Remote Logical Name Denied Access to the Local Node 2.2.25 Transfer of Large Blocks of Data over the Network Resulted in an Error 2.2.26 Problem When Database Was Defined as Remote 2.2.27 RDB$REMOTE Account That Has SYSTEM as Owner Creates Installation Problems 2.2.28 Rdb/VMS Did Not Accept the Database File Specification in a Logical Name 2.2.29 UPDATE Privilege Access for a Table with DACCESS Audit Event Was Not Captured 2.2.30 DACCESS Audit Event Required a Minimal Set of Privileges for Auditing to Occur 2.2.31 Audited Privileges for DACCESS Audit Event for Views and View-Columns Were Not Being Imported 2.2.32 Audited Privileges for DACCESS Audit Event for Columns Were Not Being Copied to the New Column Definition DuringT 2.2.33 Deleting and Then Creating a Logical Area and Accessing the Schema Caused a Page Checksum Bugcheck 2.2.34 Partitioned Sorted Index Stored the First Record Incorrectly 2.2.35 Partitioned Sorted Indexes Resulted in Various Problems 2.2.36 You Could Not Define Views Based on System Relations 2.2.37 Altering Domain and Column Attribute Caused FLDINUSE Error 2.2.38 Unnecessary Privileges Were Stored for the Database or Tables 2.2.39 BUGCHECK Occurred on Rollback/Redefinition of CREATE STORAGE MAP . . . STORE LIST Statement 2.2.40 Problem in PSII$DELETE_EMPTY_NODE Caused an Error 2.2.41 Defining a Partitioned Hashed Index Resulted in Corruption 2.2.42 Unable to Delete a Collating Sequence That Was No Longer in Use 2.2.43 Nontext Fields with Collating Sequences Produced Incorrect Results with Constraints 2.2.44 CHANGE DATABASE Statement Resulted in Bad Parameter Error Message 2.2.45 Change in Operation of Index Deletion 2.2.46 Privilege Violation in Batch-Update Caused Database Corruption 2.2.47 Collating Sequence Problems 2.2.48 Improper Error Displayed When Exporting and Importing to Use a Different Collating Sequence 2.2.49 ALTER STORAGE MAP Statement Caused a Bugcheck When Combined with Disabling Compression 2.2.50 Synchronization Problem for an Empty Sorted Index 2.2.51 Defining a View Caused a Bugcheck When a Sorted Index Was Previously Defined 2.2.52 Collating Sequences That Used Two-to-Two Character Mapping Could Bugcheck 2.2.53 Disabling Compression When Changing a Table's Storage Map to Use a Different Storage Area Caused a Bugcheck 2.2.54 REORGANIZE Clause Caused a Bugcheck 2.2.55 REORGANIZE PAGES Had No Affect When Moving Records from the RDB$SYSTEM Storage Area into a New Storage Area and P 2.2.56 Area Allocation Was Displayed Incorrectly 2.2.57 Several Miscellaneous Problems Occurred with Triggers 2.2.58 Interaction of a Trigger with the Modify of a Segmented String May Cause a ``NO_RECORD'' Failure on Commit 2.2.59 Problem with Improper Interactions Between Trigger Actions and Triggering Statements 2.2.60 An Incorrect Value Was Stored or a Bugcheck Resulted When Using BEFORE UPDATE or BEFORE MODIFY Triggers 2.2.61 Certain Queries Using Substrings Produced Incorrect Results 2.2.62 Updating the Cardinality of a Relation Caused a Bugcheck 2.2.63 CONTAIN Predicate Caused Uppercase Type in the Second Byte of Some Two-Octet Characters 2.2.64 Negate Operator Incorrectly Propagated the NULL Bit While Processing a Record Stream 2.2.65 UPDATE Operation Stored Incorrect Results 2.2.66 UPDATE Operation Caused a Bugcheck 2.2.67 Unacceptable VALID IF from CDO 2.2.68 MODIFY Operation Caused Index Corruption on Partitioned Hash Indexes 2.2.69 RDB$DBKEY_LENGTH System Field Was Incorrect for Certain Views 2.2.70 View Updates and the CHECK OPTION Clause Worked Incorrectly 2.2.71 Problem Comparing Different Data Types 2.2.72 COMPUTED BY Columns Allocated Space Within the Stored Row 2.2.73 Unnecessary Evaluation of Certain Types of Constraints Occurred on Record Insertion 2.2.74 Unexpected Lock Conflict on Freeze Error Messages Was Possible 2.2.75 Arithmetic Overflow Happened Unnecessarily for SUM Function 2.2.76 Comparing Integer and Text Fields Caused Problems 2.2.77 Arithmetic Exception Resulted When Joining Integer Columns 2.2.78 COBOL Lines Were Generated That Did Not Comply with the ANSI Standards 2.2.79 Optimization of Constraint Processing Was Limited 2.2.80 Rdb/VMS Hung on a SELECT Statement When a Column Data Type Was Changed from INTEGER to CHARACTER to DATE 2.2.81 NOWAIT Transactions Had Their Buffers Invalidated at Commit Time 2.2.82 Bugcheck Occurred with an Exception at RDMS$$RSS$ASN_FOR_RSS$NDX 2.2.83 INSERT Command to Double the Contents of a Table Resulted in an I/O Loop 2.2.84 Query Using Descending Indexes Returned Incorrect Results 2.2.85 Query with SQL LIKE Returned Incorrect Results 2.2.86 Query with Compressed Indexes Returned Incorrect Results 2.2.87 Query Returned Incorrect Results 2.2.88 Poor Performance Was Observed with Queries Using Dynamic OR Optimization Within the Leaf Retrieval 2.2.89 Query Returned Records in Wrong Order if Sorted in Descending Order with the SQL ORDER BY <column-name> DESCENDID 2.2.90 Shared Write Queries Consumed More Memory Than Expected 2.2.91 Query Optimizer Caused Various Bugchecks When Queries Were Run 2.2.92 Poor Performance Was Experienced While Retrieving Views by Dbkey 2.2.93 Wrong Results Were Returned from Queries That Used Collating Sequences and the STARTING WITH "" Relational Operat 2.2.94 Queries with Computed Expressions and Indexes Returned the Wrong Results 2.2.95 Queries with Computed Expressions Returned the Wrong Results 2.2.96 Key-Only Boolean Optimization Was Underutilized by the Query Optimizer 2.2.97 Total Relation Boolean Was Not Generated Properly in a Leaf Strategy 2.2.98 Using Placement via Sorted Index Clause to Store Rows in a Uniform Area Could Cause the Wrong Query Optimizer StC 2.2.99 Incorrect Results Were Returned on Join Operations Using Partitioned Indexes 2.2.100 Join Query Matched a Null Aggregate or Expression to a Column with Zeros or Blanks and Produced Incorrect Results 2.2.101 Read/Write Query with Multiple Range Predicates on an Index Column Performed Poorly 2.2.102 Query Optimizer Did Not Choose Index-Only Retrieval When the Dbkey Was Selected 2.2.103 Optimizer Did Not Recognize That an Index Segment Was Compressed 2.2.104 Multisegmented Index Was Not Selected When a Not-Equal Predicate Was Specified 2.2.105 Singleton Subselect Statement Returned Incorrect Results 2.2.106 Query with a FOR Loop and MODIFY Statement Followed by a PRINT Statement Returned Incorrect Results 2.2.107 Query with a Computed-By Field and OR Logic Returned Incorrect Results 2.2.108 Query with Keys Scanned the Index Instead of Using Direct Tree Lookup 2.2.109 RDBPRE Query Using Dynamic OR Optimization Returned Wrong Results 2.2.110 SQLMOD Query Returned Empty Rows 2.2.111 Under Certain Circumstances a Committed Update Was Not Completely Written to the .AIJ File 2.2.112 Problem with SPAM Thresholds in a Recover Operation 2.2.113 After-Image Journal File Create or Modify Operation Allowed Nonsystem Concealed Logical Names to Be Used 2.2.114 Recovery Failed When It Tried to Undo a Create Logical Area Operation 2.2.115 Recovery-Unit Journal (.RUJ) Files Could Not Be Created Using Angle Brackets (<>) 2.2.116 Bugcheck Occurred if the .AIJ File Could Not Be Opened, Possibly Resulting in LAT Termination 2.2.117 RMU/MONITOR/START Operation at System Startup with Global Buffers Enabled Could Result in an Exceeded Quota Error 2.3 SQL Software Errors Fixed in V4.1 2.3.1 ALTER DOMAIN Statement Did Not Allow the DATE Data Type to Be Converted to VARCHAR 2.3.2 Altering Column from One Data Type to Another Could Cause Various Exceptions When Records Containing NULL ValuesC 2.3.3 ALTER STORAGE MAP Command Resulted in the Loss of Data 2.3.4 Importing a Database with Tables Containing Lists (Segmented Strings) Failed 2.3.5 SQL IMPORT Printed Dates in the User's Format 2.3.6 Source Attributes for Storage Maps Were Not Saved in Pre-V3.1 SQL IMPORT Operations 2.3.7 INDEX Percent Fill and Node Size Information 2.3.8 Complete Export Consistency 2.3.9 More Informative Error Message 2.3.10 Earlier Information Not Previously Exported 2.3.11 Certain Trigger Definitions Caused a Bugcheck 2.3.12 Triggers Created with Long Source Text Strings Were Improperly Displayed 2.3.13 Triggers Created from Programs Had Their Source Text Truncated by a Word 2.3.14 SQL_DYNAMIC.C Sample Program Error Is Fixed 2.3.15 Null Handling Problem Occurred When Using SQL Module Language and Dynamic SQL Availability 2.3.16 Incorrect Conversion of Numeric Data Types Caused Erroneous Values for Scales 2.3.17 SQLTYPE Value Fixed in the SQLDA 2.3.18 Bugcheck Returned by the System When a User with Incorrect Privileges Showed Protection on a Schema 2.3.19 Record Parameters Could Not Be Used Where Values Were Expected 2.3.20 SQL Incompatibilities in Rdb/VMS V4.0 That Are Fixed in Rdb/VMS V4.0B and V4.1 2.3.20.1 Incompatibilities Between Object Modules 2.3.20.2 Incompatibilities Between TABLE and LIST Cursors 2.3.20.3 Incompatibilities Between Cursors and COMMIT or ROLLBACK Statements 2.3.21 Message Vector Contained Erroneous Information About the Number of Longwords Used 2.3.22 Data Dictionary (CDD/Plus) Fields with Scales Were Not Always Properly Translated 2.3.23 UNION Queries Returned Incorrect Data on Numeric Data Types 2.3.24 Modules That Used the DECLARE TRANSACTION Statement Were Ignoring TXN Attributes 2.3.25 Embedded SQL Ada Programs Could Not Use LIST Cursors 2.3.26 Views That Selected Dbkeys Caused a Bugcheck 2.3.27 Dynamic SQL Statements with Indicator Arrays Were Not Correctly Handled Prior to Rdb/VMS V4.0B 2.3.28 SQL Allocated More Memory Than Necessary During a Dynamic SET TRANSACTION Statement 2.3.29 Preparing a Statement with D-Float Parameters Caused a Bugcheck 2.3.30 Memory Was Lost Between Database Attaches 2.3.31 Using the IGNORE CASE Option of the LIKE Clause Sometimes Resulted in a Query That Incorrectly Returned No Rows 2.3.32 SQL SELECT Statement Resulted in an Invalid BLR Error 2.3.33 Storage of Records Containing NULL Values Using Dynamic SQL Caused an Arithmetic Exception 2.3.34 Input VARCHAR Parameter Actual Value Was Longer Than Procedure Parameter 2.3.35 SELECT Operation of an Altered Table Resulted in an Infinite Loop 2.3.36 Opening a Cursor That Was Already Opened Caused the Cursor to Lose Its State 2.3.37 Executing the ROLLBACK Statement with OPEN List Cursors Left List Cursors in an Unusable State 2.3.38 Executing the COMMIT Statement with OPEN List Cursors Did Not Commit the Newly Created Lists 2.3.39 OPEN Statement of an INSERT TABLE CURSOR Did Not Properly Return Error Status 2.3.40 Records Included from the Data Dictionary in the C Preprocessor Did Not Null-Terminate Character Strings 2.4 SQL/Services Errors Fixed in V4.1 2.4.1 Trailing Characters Appeared on SQL/Services Sample Program Error Messages 2.4.2 sqlsrv_fetch_many Routine Caused Problems on the Macintosh Platform 2.4.3 Unpredictable Results Occurred When Trying to Store Segmented Strings from the Macintosh Environment Using DECnet 2.4.4 Certain Calls to the sqlsrv_fetch_many Routine Caused Problems 2.4.5 Authorization Failure Occurred When SYSUAF Flag LOCKPWD Was Set 2.4.6 Column Limit Raised to 500 2.4.7 SQL/Services Failure Did Not Produce a Bugcheck File 2.4.8 SQL$STARTUP.COM Startup File Contained an Error in the SQL/Services Startup Logical Name 2.4.9 Node Names Containing Numeric Characters Were Improperly Made Uppercase in OS/2 API 2.4.10 SQLSRV_ASCII_STRING Data Type and NULL Termination 2.4.11 Compilation Error Fixed for SQL/Services ULTRIX Sample Application 2.4.12 SQL/Services MS-DOS IVP Failure Is Fixed 2.4.13 SQL/Services Length Packet Split Problem Is Fixed 2.4.14 Problem Freeing Network Connections for SQL/Services ULTRIX API Is Fixed 2.4.15 VMS Application Programming Interface (API) Installation Failed Without Rdb/VMS 2.4.16 Failure of SQL/Services Communication Server to Report Error Status Is Fixed 2.4.17 SQL/Services Shutdown Procedure Problem Is Fixed 2.4.18 SQL/Services Startup File Changes 2.4.19 SQL/Services Macintosh API Code Fixes 2.4.19.1 SQL/Services Now Allows Changing the Name of the Macintosh System Folder 2.4.19.2 SQL/Services SQLSRV$Volume installation Volume Can Now Be Accessed on the Macintosh 2.4.19.3 SQL/Services Now Looks for PATHWORKS DECnet Tool Instead of DECtask Tool 2.4.19.4 SQL/Services Macintosh API Fix for Macintosh Systems Based on the Motorola 68000 Chip 2.4.20 SQL/Services Proxy File Fixes 2.4.21 SQL/Services Client Application Logging Fixes 2.4.22 SQL/Services API Fetch Routines Are Fixed 2.4.23 More Pertinent Error Message Is Returned When Passing an Invalid Class Name in the sqlsrv_set_server_class Routin 2.5 RDO and RDBPRE Software Errors Fixed in V4.1 2.5.1 Bugcheck Was Returned Because the CHANGE FIELD Had No VALID IF Clause 2.5.2 Incorrect Value Was Stored During an RDO STORE or MODIFY Operation 2.5.3 Multiple RDO Statements in a FOR Loop Caused Unpredictable Results 2.5.4 Query Using Static OR and a Common Subexpression in Two or More OR Legs Produced Incorrect Results 2.5.5 RDO IMPORT Operation Did Not Save All SQL Defined Attributes 2.5.6 RDO IMPORT Statement Default Is CDD_LINKS, as Documented 2.5.7 RDO IMPORT Failed to Detect Illegal Zero Values Specified on the IMPORT Command 2.5.8 Problem with Callable RDO and Varying String Descriptors 2.5.9 RDB$INTERPRET Now Fully Supports VS (Varying String) Descriptors 2.5.10 RDBPRE Generated Incorrect Code for Request Handles 2.5.11 Wrong Number of Records Was Returned by a Query in an Inner FOR Loop 2.6 RDML Software Errors Fixed in V4.1 2.6.1 Shared Fields in a Relation and a View Caused a Bugcheck 2.6.2 RDML-E-READ_ONLY Error Was Returned When Attempting to Update COMPUTED BY Fields 2.6.3 Precompiler Aborted When Processing RDB$MISSING in an RSE 2.6.4 Code Was Incorrectly Generated for RDB$MISSING in the GET Statement 2.6.5 Error Resulted in Generating Double Precision Constants for Pascal 2.6.6 Changing Records in CDD/Plus Caused an Error 2.6.7 CDD/Plus Informational Message Caused RDML to Abort Compilation 2.6.8 RDML Generated a Fatal Error Message When It Encountered an Informational CDD/Plus Message 2.6.9 Problem with RDML Read-Only Field 2.7 RMU Software Errors Fixed in V4.1 2.7.1 TA90E and TA91 Tape Drives Were Not Recognized in Rdb/VMS V4.0 and V4.0A 2.7.2 Returned DCL $STATUS Was Inconsistent Between RMU Commands 2.7.3 Index Cardinality Was Not Maintained When an Application Performed Only a Few Insertions or Deletions 2.7.4 Behavior of RMU/BACKUP Was Confusing When Tape Volume Protection Was Used 2.7.5 RMU/BACKUP Command Was Incompatible with the VMS MOUNT/NOUNLOAD Commands 2.7.6 RMU/BACKUP Command Required Tapes on Each Drive to Be Mounted 2.7.7 RMU/BACKUP Command Failed to Overlap the Rewind-Dismount and Write of the Next Volume 2.7.8 VMS BACKUP Was Incompatible with the RMU/BACKUP and RMU/RESTORE Commands 2.7.9 Problems with Tape Label Checking in the RMU/BACKUP and RMU/RESTORE Commands 2.7.10 RMU/RESTORE Stopped Searching a Tape for the Named Backup File if It Encountered a Zero-Length File 2.7.11 AIJ No-Quiet-Point Backup Could Corrupt the .AIJ File 2.7.12 /INTERVAL Qualifier of the RMU/BACKUP/AFTER_JOURNAL Command Miscalculated a Specified Interval Value 2.7.13 RMU/CLOSE/CLUSTER/WAIT/ABORT=FORCEX Command Hung the Database 2.7.14 Privileges Required to Execute the RMU/DUMP, RMU/OPEN, and RMU/CLOSE Commands 2.7.15 RMU/CONVERT Command Failed with a Default Collating Sequence Defined 2.7.16 RMU/COPY or RMU/MOVE Command Incorrectly Copied Area Inventory Pages (AIP) 2.7.17 DISTRIBTRAN Privilege Was Not Audited Correctly by Security Auditing Facility 2.7.18 Problem with RMU/SHOW USERS and RMU/SHOW SYSTEM Commands and VMS WORLD Privileges 2.7.19 RMU/REPAIR Command Caused Database Corruption-Problem I 2.7.20 RMU/REPAIR Command Caused Database Corruption-Problem II 2.7.21 SPAM Threshold Calculations Resulted in Errors Reported by the RMU/VERIFY Command 2.7.22 RMU/VERIFY Reported False AIPENTMBZ Warning Messages 2.7.23 Hashed Index Verification Caused Buffer Flushing Problem 2.7.24 RMU/VERIFY Did Not Properly Verify Databases Converted to V4.1 Using the RMU/CONVERT/NOCOMMIT Command 2.7.25 RMU/VERIFY Could Report False BADSEGDBK Errors 2.7.26 RMU/VERIFY Did Not Do .AIJ File Verification if the User Did Not Have Sufficient Privileges to Open the .AIJ File 2.7.27 RMU/VERIFY/INDEX or RMU/VERIFY/ALL Command Caused a Bugcheck if You Had Hashed Indexes Defined 2.7.28 RMU/VERIFY Command Returned Spurious Errors Involving Fragmented Records 2.7.29 RMU/VERIFY Command Reported False MINGTRSIZ Error Messages 2.8 Software Errors Related to CDD/Plus Fixed in V4.1 2.8.1 Using CDD/Plus to Specify Collating Sequences Returned an Error 2.8.2 SQL or RDO Hung During Integrate Operation and a Ctrl/Y Was Not Possible 2.9 CDD/Plus Software Errors Fixed That Affected Rdb/VMS 2.10 Software Errors Fixed in Rdb/VMS That Affected Other Products 2.10.1 Invalid Data Was Sent to DECtrace for the Transaction Event 3 Known Problems, Restrictions, and Other Notes 3.1 Known Problems and Restrictions for General Knowledge in V4.1 3.1.1 Error Message Files Are Altered by DECpresent V1.0 3.1.2 VMS Lock Remastering Changed in VMS V5.4 3.1.3 Multiversion Problem Exists in V4.1 Process Environment When You Run RMONSTOP and RMONSTART Procedures for Either 3.2 Known Problems and Restrictions for All Interfaces in V4.1 3.2.1 System Table Changes from V4.0 to V4.1 Cause DEC RdbExpert for VMS to Fail with NONULLIND Error 3.2.2 Placement Using Sorted Indexes Can Result in Performance Degradation over Time as Rows Are Added and Index Key VU 3.2.3 Deleted Space Is Not Reused Until the Next Database Attach 3.2.4 Digital Does Not Support Access to Rdb/VMS Through an Asychronous System Trap (AST) Service Routine in a User App 3.2.5 V4.1 Multiplex Feature Should Be Disabled if Remotely Attaching to V4.1 and V3.1 or V4.0 Databases 3.2.6 Segmented String Records Should Match the Page Size When Stored on WORM Optical Disk Devices 3.2.7 VAX RALLY Application Fails When Snapshots Are Enabled Deferred 3.2.8 Using Quoted Threshold Values for Binary Data Types for Partitioning Data or Indexes Results in Data or Index Cor 3.2.9 Triggers That Affect Subject Table Rows Can Cause Loops or Inconsistent Results 3.2.10 Collating Sequences Producing Too Many Nulls May Result in a Bugcheck Dump 3.2.11 Sequential Retrieval Causes Problems with Dynamic Optimizer 3.2.12 You Cannot Correctly Import a Database That Contains Computed-By Columns That Reference Other Computed-By Columns 3.2.13 Table Name Must Match Dictionary Record Name 3.2.14 Certain Reserved Words Cannot Be Used as Database Handles for RDBPRE or as Aliases for SQL$PRE and SQL$MOD 3.2.15 Transaction Handle and Messages Vector Are Not Always Available in Callable RDO 3.3 SQL Notes of General Interest for V4.1 3.3.1 Using the SMALLINT Data Type and VAX C 3.4 SQL Known Problems and Restrictions in V4.1 3.4.1 SQL Users Using the Multiversion Kit Must Link with the SQL$USER Logical Name 3.4.2 Using LIST STORAGE AREA Clause on CREATE DATABASE Statement Causes Unexpected I/O to WORM Device 3.4.3 You Cannot Import a Multischema Database to Earlier Versions 3.4.4 You Cannot Use EXPORT WITH NO EXTENSIONS if INTERVAL Is Defined 3.4.5 SQL Object Module Incompatibility 3.4.6 Confusion Over the Use of ASCII and ASCIZ in Dynamic SQL and C Programs 3.5 SQL/Services Known Problems and Restrictions in V4.1 3.5.1 Process Logical Names Are Not Supported in SQL/Services 3.5.2 SQL/Services Compatibility Issue with the Order of Include Files 3.5.3 New DATE, TIME, TIMESTAMP, and INTERVAL Data Types Are Not Directly Supported by SQL/Services 3.5.4 Problem with SQL/Services CDev for the Macintosh and the New Release of PATHWORKS for Macintosh V1.1 3.5.5 Invalid Length Is Returned by SQLSRV_VARBYTE Data Type 3.5.6 Allocating Space for SQLSRV_VARCHAR and SQLSRV_VARBYTE Data Types Can Cause a Problem 3.5.7 SQL/Services Compatibility Issues 3.5.7.1 SQL/Services (Version 4.0 or Higher) Server Uses Proxy-Like and Default Access to Authorize Version 3.0 or 3A 3.5.7.2 SQL/Services V4.0 Server Error -2031 Returned to V3.1 Client APIs 3.5.7.3 SQL/Services IVP Failure Caused by -2003 Network Error 3.6 RDO and RDBPRE Known Problems and Restrictions in V4.1 3.6.1 RDO Restrictions in V4.1 3.6.2 RDO CONVERT Operation on V3.0 Databases Causes Database Corruption When the Database Is Converted to V4.0, V4.0Ao 3.6.3 RDO Export Operation May Return SQL Error Messages 3.6.4 RDO Import Operation Error Message Results from Importing a Multischema Database Referencing CDD/Plus 3.6.5 Aggregate Expressions in RDO Return an Error 3.6.6 Loss of Precision for Text to Quadword Assignment in RDB$INTERPRET 3.7 RMU Known Problems and Restrictions in V4.1 3.7.1 Problems Using RMU Commands with SYSMAN 3.7.2 Problem Using VMS ALLOCATE Command with RMU Commands 3.7.3 Concealed Logicals Are Supported but No Longer Recommended for Use After V4.0 3.7.4 Restrictions on Using RMU Commands with the /WORM and /NOSPAMS Qualifiers 3.7.5 Do Not Delete After-Image Journal (.AIJ) Backup Files if the AIJ Backup Fails or Is Terminated 3.7.6 RMU/EXTRACT Known Problems and Restrictions in V4.1 3.7.6.1 VALID IF Clauses Are Converted to Domain Level CHECK( ) Constraints 3.7.6.2 Triggers in RDO Allow Users to Define a Trigger Action Within a Join of Two or More Tables 3.7.6.3 VMS Style Dates and CURRENT_TIMESTAMP 3.7.6.4 Blank Lines in Multiline Descriptions Are Removed by RDO 3.7.6.5 RMU/EXTRACT Column Default Value Restriction 3.7.6.6 Partial Support for RdbAccess for VAX RMS Is Provided by Rdb/VMS V4.1 3.7.7 Attaches to an "OPEN IS MANUAL" Database That Is Currently Closed Are Not Allowed 3.7.8 Clarification on the Meaning of "Granted" and "Requested" in RMU/SHOW LOCKS Output Displays 3.7.9 False BADFNMAIJ Errors Are Returned from RMU/VERIFY During Root Verification 3.8 CDD/Plus (CDD/Repository) Known Problems, Restrictions, and Notes for V4.1 3.8.1 Using CDD/Repository Global Fields with Rdb/VMS 3.8.2 Compatibility of CDD/Repository (Previously Called CDD/Plus) and Rdb/VMS 3.9 CDD/Plus V4.2A and V4.3 Known Problems and Restrictions for V4.1 3.9.1 Changing the Rdb/VMS Database File Name 3.9.2 Using CDD/Plus in a Multiversion Environment 3.9.3 New DATE Data Types Are Not Supported by CDD/Plus V4.3 3.9.4 SQL Interface Restrictions for CDD/Plus V4.3 and Earlier Versions 3.9.5 Integrate Sometimes Fails with a NO_META_UPDATE Error 3.9.6 CDD/Plus V4.2 and V4.3 Restriction 3.10 Restrictions Lifted by CDD/Plus Version 4.3 3.11 Rdb/VMS Documentation Errors and Omissions for V4.1 3.11.1 Buffer Management Changes for V4.0 3.11.2 New Logical Name RDM$MON_USERNAME Is Not Documented in the Main V4.1 Documentation Set 3.11.3 Maintenance Operations for and Characteristics of WORM Media Not Previously Described in the V4.1 Documentation 3.11.3.1 Maintenance Operations on WORM Media 3.11.3.2 WORM Media Characteristics and Assumptions 3.11.4 Database Key Recommendation Is Clarified 3.11.5 Specification of Correlation Name in Table References Is Restricted 3.11.6 Correction for Database Keys Example 3.11.7 RMU/SHOW STATISTICS Formatted Binary Output File Changes Are Not Documented 3.11.8 Description of the Space Used by the New Segmented String Structures on WORM Disks in the VAX Rdb/VMS Guide to DI 3.11.9 SQLDA2 Null Indicator Data Type Is Incorrect 3.11.10 SQL ALTER DOMAIN and RDO CHANGE FIELD Statement Restriction Is Undocumented 3.11.11 Examples of Specifying Preferred Optimization Mode Show Incorrect SQL Syntax 3.11.12 Reference to Example of Initialized Parameter Is Incorrect 3.11.13 INSERT Statement VALUES Clause Is Missing an Argument 3.11.14 Value Returned by AVG Function 3.11.15 CREATE STORAGE AREA Is Missing List Storage Area Syntax 3.11.16 CREATE STORAGE MAP STORE LISTS Clause Syntax Is Incorrect 3.11.17 Embedding Quotation Marks in Literals Table Is Incorrect 3.11.18 Not All CDO and DTR Edit Strings Are Accepted by SQL 3.11.19 Corrections to Tables in the VAX Rdb/VMS Guide to Using SQL/Services 3.11.20 The VAX Rdb/VMS RDO Reference Manual Appendix C Omits VAX Data Distributor Commands 3.11.21 RDB$MISSING Is Evaluated at Compile Time, Not Run Time 3.11.22 SORTWORKn Logical Name Description Is Inaccurate 3.11.23 Clarification on Setting the Read-Only and Read/Write Attributes for the RDB$SYSTEM Storage Area and Using the RC 3.11.24 Clarification on the Relationship Between the Number of Users and the Number of Nodes Supported on a Database 3.11.25 Clarification on Why Snapshot Files Grow in Size 3.11.26 Request Handle Syntax Is Treated Differently in Statistical Expressions 3.11.27 Documentation Error Regarding Microsoft C Compatible Assembler Required for the SQL/Services MS-DOS Application I 3.11.28 Description of RMU/SHOW STATISTICS Checkpoint Display Needs Clarification 3.11.29 Using RDML and the Two-Phase Commit Protocol by Calling the DECdtm System Service Calls Implicitly and ExplicitlD 3.11.30 Explanation of the ``Lock Conflict on Freeze'' Errors 3.11.31 Explanation of RMU/SHOW STATISTICS Blocking AST 3.11.32 Clarification of Behavior of the RDO F_FLOATING Data Type 3.11.33 Explanation of RMU/SHOW STATISTICS Stall Messages 3.11.34 RDMS$BIND_VALIDATE_CHANGE_FIELD Logical Name Was Not Documented in V4.0 3.11.35 RDMS$BIND_VM_SEGMENT Logical Name Was Misnamed in the V3.1 Documentation and Was Not Documented in V4.0 3.12 SQL/Services Troubleshooting Suggestions 3.12.1 Common SQL/Services Network Errors 3.12.2 Common SQL/Services Fatal Execution Server Errors 3.12.3 Common SQL/Services API Installation Failures 3.12.4 SQL/Services Compatibility Issues 3.12.4.1 SQL/Services V4.0, V4.0A, V4.0B, and V4.1 Server Uses Proxy-Like and Default Access to Authorize V3.0 or V3.A 3.12.4.2 SQL/Services V4.0, V4.0A, V4.0B, or V4.1 Server Error -2031 Returned to V3.1 Client APIs 3.12.4.3 Queue Manager Must Be Started for the SQL/Services IVP to Work 3.13 Restrictions Retained from V4.0 3.13.1 Known Problems and Restrictions for All Interfaces for V4.0 3.13.1.1 Improving the Performance of the Export Operation Using the DCL SET Command to Change the Default Extend Para 3.13.1.2 SNAPSHOTS DEFERRED May Stall Transactions 3.13.1.3 PLACEMENT VIA INDEX Clause Prohibits Shadow Clustering 3.13.1.4 RDB$SYSTEM Storage Area Cannot Be Read-Only When a Relation Is Readied in Exclusive or Batch-Update Mode 3.13.1.5 Joined Relations Do Not Allow ``MODIFY'' if Using the WITH Clause 3.13.1.6 Using RDML/C to Update a View Returns Errors 3.13.1.7 DECLARE and START Stream Are No Longer Allowed for Certain Views 3.13.1.8 A Clarification of the Storage Algorithm for Mixed Pages 3.13.1.9 Adjustment of Cardinalities in V4.0 Is Likely to Cause Poorer Optimizer Performance 3.13.1.10 SELECT on SCHEMA (in V4.1, SELECT on DATABASE) (READ on DATABASE) ACE Is Now Required 3.13.1.11 Rdb/VMS Network Link Failure Does Not Allow FINISH (in V4.1, DISCONNECT) to Tidy Up Transactions 3.13.1.12 VAX Data Distributor Copy Processes Do Not Process Database Pages Ahead of an Application 3.13.1.13 Setting an Appropriate WSEXTENT Relative to WSQUOTA for SORT/MERGE Operations 3.13.1.14 Attempting to Acquire a Lock Could Cause an Infinite Loop 3.13.2 SQL Known Problems and Restrictions for V4.0 3.13.2.1 SQL Allows False Redefinition of the DATE Data Type 3.13.2.2 Problem Adding a New Field to CDO Defined Record and Not to Last Position 3.13.2.3 Module Language Passes Extraneous Characters with Inexact Dynamic Descriptors 3.13.2.4 Close List Cursor Before Fetching Rows from Table Cursor 3.13.2.5 SELECT Statement with GROUP BY Clause Did Not Return Date Fields in EDIT STRING Format 3.13.2.6 When Using the BETWEEN Operator, You Should Specify the Lower Value First 3.13.2.7 Cautions on Using ANY, ALL, or IN Clauses in Constraint Definitions 3.13.2.8 SQL Does Not Recognize a Record During SQL Precompile Time 3.13.2.9 Release of Cursor Statements Referencing Prepared Statements Causes Problems 3.13.2.10 SQL Does Not Translate Logical Names Referencing Source Databases 3.13.2.11 Problem with Transferring a Table to an Existing Database Containing the Same Table Name 3.13.3 RDO Known Problems and Restrictions for V4.0 3.13.3.1 RDO SHOW USERS and SHOW MONITOR Statements Do Not Work for Remotely Accessed Databases 3.13.4 RDML Known Problems and Restrictions for V4.0 3.13.4.1 RDML Generates an Error Message When Attempting to Store or Modify Read-Only (COMPUTED BY) Fields 3.13.5 RMU Known Problems and Restrictions for V4.0 3.13.5.1 Non-Updatable Fields Cannot Be Unloaded Using the RMU/UNLOAD Command 3.13.5.2 Single-File Databases Require the /ROOT Qualifier When Using the RMU/MOVE_AREA Command 3.13.5.3 Shortened Form of RMU/RESTORE Command Does Not Work Properly 3.13.5.4 Installing RMU with Privileges 3.13.6 CDD/Plus Restrictions for V4.0 3.13.6.1 Minimum Supported Version of CDD/Plus 3.13.6.2 Using CDD/Plus with PERSONNEL.COM 3.13.6.3 Some Views Are Not Accepted by VAX CDD/Plus V4.2 3.13.6.4 GRANT and REVOKE Statements Generate MBLRSYNERR Message if Attached by Path Name 3.13.7 Restrictions Lifted by CDD/Plus Version 4.2 3.13.7.1 Incompatibilities Between Rdb/VMS V4.0 and CDD/Plus That Have Been Lifted by VAX CDD/Plus Version 4.2 3.14 Restrictions Retained from V3.1 3.14.1 Known Problems and Restrictions for All Interfaces for V3.1 3.14.1.1 Object Modules Created with V3.1 and V4.0 Are Not Downward-Compatible 3.14.1.2 FIRST n Is Not Considered During Optimization 3.14.1.3 With the Exception of Views, Do Not Add Fields to Relations, or Define Indexes, Triggers, and Other Databaseo 3.14.1.4 Performance Considerations for Using VARYING STRING or COLLATING SEQUENCE Attribute for Index Keys 3.14.1.5 Sorting or Implied Sorting for Projection on a Dbkey Is Not Worthwhile 3.14.1.6 Many Attaches to and Detaches from the Same or Multiple Databases While Using Search Lists to Point to the DU 3.14.1.7 Unexpected Setting of the NULL Attribute After an IMPORT Operation 3.14.1.8 RDO IMPORT Statement Generates Bugcheck Dumps if the Index Definition Fails 3.14.1.9 IMPORT Statement Fails to Complete Index Definition with Users Attached to the Database 3.14.1.10 Using LIB$DT_INPUT_FORMAT to Change Date Input Format Sometimes Causes Access Violation 3.14.1.11 Operations on F-Floating Data Round to Whole Numbers 3.14.1.12 Rdb/VMS Interaction with Data Distributor V2.1 May Generate Bugcheck Dumps 3.14.1.13 Batch-Update Transactions Can Cause a Bugcheck Dump to Occur if an Index Definition Fails 3.14.1.14 Rdb/VMS Logical Name, RDMS$BIND_WORK_VM, Has an Upper Limit of 65,000 Bytes 3.14.1.15 Reserving a Table in Exclusive Mode May Prevent Operations from Being Performed on Other Tables in the Same A 3.14.1.16 Problem Defining COLLATING SEQUENCE IS NORWEGIAN NORWEGIAN 3.14.1.17 Snapshot File Name, File Type, or Version Number Cannot Be Changed for Single-File Databases 3.14.1.18 Rdb/VMS and VMS Debugger Interaction 3.14.1.19 Using Rdb/VMS from a VMS Detached Process 3.14.2 SQL Known Problems and Restrictions for V3.1 3.14.2.1 DDL Statements Cannot Refer to Objects Before Their Creation 3.14.2.2 Deleting Metadata in Rdb/VMS 3.14.2.3 SQL Schema Compilation Fails on the First Fatal Error 3.14.2.4 COMMENT ON Statement Cannot Be Used in CREATE SCHEMA Statement 3.14.2.5 Dynamic Cursors Cannot Access Views Created with GROUP BY or UNION Clause 3.14.2.6 You Cannot Use INCLUDE Statement in Variable Declaration 3.14.2.7 SQL Ada Precompiler Does Not Support the Correct Overloading of Subprograms 3.14.2.8 SQL Precompiler Does Not Evaluate Expressions in Variable Declarations or Understand Literals 3.14.2.9 SQL Ada Precompiler Does Not Support Named Literals or Ranges 3.14.2.10 SQL Module Language Processor Fails on the First Fatal Error 3.14.3 SQL/Services Known Problems and Restrictions for V3.1 3.14.3.1 Disable VAX SQL/Services V1.0 Startup Procedure 3.14.4 RDO and RDBPRE Known Problems and Restrictions for V3.1 3.14.4.1 Database Handle Scope 3.14.4.2 RDO CHANGE INDEX Restriction Is Now Signaled 3.14.4.3 Problem of Different Optimizations of the Same Query from Different Environments 3.14.4.4 Restrictions on Using Missing Value Fields in Nested Queries 3.14.4.5 STORE WITHIN and DISABLE/ENABLE COMPRESSION Clauses Cannot Both Be Specified 3.14.5 RDML Known Problems and Restrictions for V3.1 3.14.5.1 Variables Cannot Be Database Handles 3.14.5.2 RDML Run-Time Object Library No Longer Requires You to Link with VAXCRTL or VAXCRTLG Object Libraries or ShaI 3.14.5.3 RDML/EPascal Ignores /LINKAGE=PROGRAM_SECTION Qualifier 3.14.5.4 RDML/Pascal Does Not Understand Some Character String Value Expressions 3.14.5.5 RDML/Pascal Does Not Accept All Possible Valid Pascal Host Language Variables 3.14.5.6 RDML Does Not Allow Nested Comments 3.14.5.7 C Host Variables 3.14.5.8 C String Continuation Character 3.14.5.9 Path Name and the DATABASE Statement 3.14.6 RMU Known Problems and Restrictions for V3.1 3.14.6.1 Using the /USERS_MAX and /NODES_MAX Qualifiers with the RMU/RESTORE Command Requires Both Qualifiers on the F 3.14.6.2 The RMU/BACKUP/AFTER_JOURNAL /CONTINUOUS /UNTIL="TOMORROW:+00:50" Command Fails for V3.1A and VMS V5.3 or V5. 3.14.6.3 There Is a 17-Character Limit for File Names When You Back Up Databases to Tape 3.14.6.4 RMU/DUMP/BACKUP Command Specifying a Value of 1 or 2 for the /ACTIVE_IO Qualifier Causes the AIJ Dump to Stal 3.14.6.5 RMU/SHOW STATISTICS Command Does Not Record All Statistics in the Binary File 3.14.6.6 Dumping the .AIJ File Is Incompatible with Normal Usage 3.14.6.7 RMU/RESTORE Command May Initialize the SPAM Thresholds in One or More Storage Areas 3.14.7 DSRI Notes and Restrictions Retained from V3.1 3.14.7.1 RCI Instantiation Number Must Be Zero for Remote Access 3.14.7.2 Context Variables That Are Not Unique Within a Request Cause Invalid BLR 3.14.8 CDD/Plus Restrictions Retained from Rdb/VMS V3.1 3.14.8.1 CDD/Plus COMPUTED BY Fields Are Not Currently Supported in Rdb/VMS Relations or Views 3.14.8.2 EXPORT WITH NOEXTENSIONS Statement Can Corrupt the CDD$DATABASE A Additional Release Notes for Rdb/VMS V4.1 A.1 Special SQL Images Provide a Bridge for Date-Time Compatibility A.2 Additional Release Notes for Rdb/VMS V4.1 A.2.1 Deprecated Default Semantics of the ORDER BY Clause A.2.2 Creating a Storage Map on a View Caused a Bugcheck Dump A.2.3 Multiple Database Recovery (DBR) Instances Attempted to Recover the Same .RUJ File and Resulted in DBR Bugcheck A.2.4 AIJ Recovery Failed Because TSNs Did Not Match Database Root Information A.2.5 AIJ File Modification on One Node Was Not Reflected on Another Node A.2.6 Memory Corruption Problem Related to the Number of Users Caused a Bugcheck A.2.7 Bugcheck Resulted When Attempting to Deassign an Invalid File Channel During a Database Detach A.2.8 Problem Running RDML on a System with No Rdb/VMS License A.2.9 Performance Problem Is Observed with Rdb/VMS Distributed Update Transactions in a Mixed VMS V5.4 and V5.5 OperatE A.2.10 A Distributed Transaction Abort Error Will Change from a Warning to an Error in a Future Release of Rdb/VMS A.2.11 Fractional Seconds Precision Is Not Handled Correctly A.2.12 An RDB-E-UNRES_REL Error May Be Returned After You Issue an ALTER STORAGE MAP Statement A.2.13 Mapping Values for an Index Cannot Be Used in an RDO or SQL Import Operation A.2.14 A Detach from the Database Sometimes Results in a Bugcheck A.2.15 RDO Concatenate Expression with Two Databases Can Return Incorrect Results A.2.16 RDO Concatenate Expression in the Nested FOR Loops Can Return Incorrect Results A.2.17 RDBPRE Upgrade from Rdb/VMS V3.0B to V4.0A Results in Run-Time Error BAD_REQ_HANDLE Upon Recompilation A.2.18 RMU/EXTRACT Does Not Recognize the Keyword ALL in View Definitions A.2.19 RMU/EXTRACT Does Not Correctly Extract an RDO-Defined Trigger Containing More Than One STORE Clause in a FOR Loop A.2.20 Index Loses Attributes After an Integrate Operation A.2.21 CDD/Repository, Rdb/VMS: Record and Field Interaction A.2.22 Information Omitted from the VAX Rdb/VMS Installation Guide Regarding the Installation of the SQL$INT.EXE and SQI A.2.23 Documentation Omitted Information Indicating That an .OAIJ File Can Be Displayed Using the RMU/DUMP/AFTER_JOURNAC A.2.24 CREATE STORAGE MAP Diagram Errors A.2.25 CAST Documentation Errors A.2.26 The VAX Rdb/VMS RMU Reference Manual and RMU Help Are Unclear on When You Can Optimize .AIJ Files and IncorrectlF B Summary of Rdb/VMS V4.1 Documentation EXAMPLES 1-1 Using the RDMS$USE_OLD_UPDATE_RULES Logical Name 1-2 Using the RDMS$BIND_WORK_FILE Logical Name 2-1 Triggers Properly Displayed 2-2 Trigger Text Truncated 2-3 Cursor Losing Its State 2-4 Executing ROLLBACK with LIST CURSORS 2-5 Executing COMMIT with OPEN LIST Cursors 2-6 OPEN Not Returning Error Information 2-7 Records from the Data Dictionary Not Terminated with the NULL Character TABLES 1 Differences in Relational Terminology 1-1 Sample Programs in Precompiled SQL and SQL Module Language 1-2 Available Transports for SQL/Services APIs 1-3 Output Selection Using Various Combinations of RMU/EXTRACT Qualifiers 1-4 Side-by-Side Comparison of the Two Stall Messages Screens 1-5 SQL Deprecated Features and Incompatible Changes for Rdb/VMS Version 4.1 1-6 Obsolete Statements 3-1 Compatibility Between Storage Area Attributes and Disk Drive Types 3-2 Embedding Quotation Marks in Literals 3-3 CDO Edit Strings Supported by SQL 3-4 SQL Statements That Can Be Dynamically Executed 3-5 SQL Statements That Cannot Be Dynamically Executed B-1 Rdb/VMS Documentation and Part Numbers