BASEstar_Open_Client________________________________ Release Notes June 1999 This document contains the release notes for BASEstar Open Client Version 3.2 for Compaq Tru64 UNIX systems. Revision/Update Information: This is a revised document. Software Version: BASEstar Open Client Version 3.2 Compaq Computer Corporation Houston, Texas ________________________________________________________________ June 1999 © Digital Equipment Corporation 1999. All Rights Reserved. The software described in this guide is furnished under a license agreement or nondisclosure agreement. The software may be used or copied only in accordance with the terms of the agreement. Compaq Computer Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. COMPAQ,the Compaq logo and the Digital logo are registered in the U.S. Patent and Trademark Office. Tru64 is a trademark of Compaq Computer Corporation. The following are trademarks of Digital Equipment Corporation: Alpha AXP, BASEstar, DEC, DECmessageQ, DECnet, DECnet-DOS, DECosap, DEComni, DIGITAL, DIGITAL UNIX, FMS, LN03, MicroVAX, NAS, OpenVMS, OpenVMS Alpha, PATHWORKS, PDAS, Rdb/VMS, ReGIS, ThinWire, TK, ULTRIX, VAX, VAXcluster, VAX COBOL, VAX FORTRAN, VAX Pascal, VAX RMS, VMS/ULTRIX Connection, and VT. Microsoft and Windows NT are registered trademarks of Microsoft Corporation. The following are third-party trademarks: Other product names mentioned herein may be the trademarks of their respective companies. This document was prepared using VAX DOCUMENT, Version 2.1. _________________________________________________________________ Contents Preface................................................... v 1 Introduction and General Release Notes 1.1 New and Changed Features With Respect to BASEstar Open Client Version V3.1......................... 1-1 1.2 BASEstar Open Documentation Set.................. 1-2 1.3 Pre-requisites................................... 1-3 2 Installation Release Notes 2.1 Installation Verification Procedure (UNIX platforms)....................................... 2-1 3 New and Changed Features 3.1 BASEstar Open Client No Longer Requires a Local Client Licence................................... 3-1 3.2 Simultaneous Access to a Local and A Remote Realm ................................................. 3-1 3.2.1 The bstr2 Client Library ...................... 3-2 3.2.2 The bstr2 API ................................. 3-2 3.2.3 Installing the bstr2 Components ............... 3-2 3.2.4 Setting the bstr2 Environment ................. 3-3 3.2.5 bstr2 Include File ............................ 3-3 3.2.6 bstr2 Library ................................. 3-3 3.2.7 Example ....................................... 3-3 iii 4 Restrictions 4.1 Fields in a Structure_Datatype................... 4-1 4.2 Checking the Mapping Path........................ 4-1 4.3 Checking Filter Expressions...................... 4-1 4.4 Datatype Congruency Checks....................... 4-1 4.5 Device Variable Address Checks................... 4-1 4.6 Device Time Format Not Converted................. 4-2 4.7 Spaces Not Accepted in File or Directory Names... 4-2 5 Bug Fixes 5.1 Incorrect Error Message When Attempting to Map to a Data_Point in a Different Domain............... 5-1 5.2 Abnormal Behavior of the bstr_get_object_type_info Procedure.............. 5-1 5.3 Watchdog Crash................................... 5-2 5.4 CLI Segmentation Fault (UNIX only)............... 5-2 5.5 Consecutive BSTR Sessions........................ 5-2 5.6 bstr_reference_recover........................... 5-2 5.7 Hang in Complex Network Environments............. 5-2 5.8 Recovery for User Port Objects................... 5-2 5.9 CLI and Unaligned Access......................... 5-3 5.10 Memory Leak with Ports and Packets............... 5-3 5.11 Recovery Procedure loop.......................... 5-3 5.12 bstr_get_type_info unresolved symbol(OpenVMS only)............................................ 5-3 5.13 bstr_reference_set()............................. 5-3 5.14 CREATE TRIGGER fails with INVALID_OPERAND........ 5-3 5.15 Non-privileged account problem(Windows NT only).. 5-4 5.16 Stack overflow in cli_bstr....................... 5-4 5.17 aligment warnings................................ 5-4 5.18 socket files left under /tmp .................... 5-5 5.19 Recovery loop ................................... 5-5 6 Known Problems 6.1 Inconsistency of Timer and Trigger Attributes on PODB............................................. 6-1 6.2 Hostname Length Restriction...................... 6-1 6.3 Concurrent put_value Operations on Mapped_Data_Points............................... 6-1 6.4 Assigning a Default Value to a Data_Point........ 6-2 6.5 Cannot Specify Producer in a Different Domain.... 6-2 iv 6.6 LOAD CONFIGURATION Command....................... 6-2 6.7 BASEstar Open TIME data type..................... 6-2 7 Documentation Release Notes 7.1 The BASEstar Open Application Programming Interface........................................ 7-1 7.1.1 General ....................................... 7-1 7.2 BASEstar Open Messages........................... 7-1 7.2.1 General Purpose and Common Services Messages .. 7-1 v _________________________________________________________________ Preface Kit Identification You can identify this kit by the identifier that BASEstar Open Client processes print on the log files: o Compaq Tru64 UNIX "BASEstar Open V3.2-0 (BSTBASE320)" v 1 _________________________________________________________________ Introduction and General Release Notes The structure of this document is as follows: o Chapter 1 provides a basic introduction to BASEstar Open Client Version 3.2. o Chapter 2 contains release notes relevant to the installation of BASEstar Open Client Version 3.2. o Chapter 3 describes new and changed features with respect to BASEstar Open Client Version V3.1. o Chapter 4 describes restrictions that apply to BASEstar Open Client Version 3.2. o Chapter 5 describes BASEstar Open Client Version V3.1 bugs that have been fixed in Version 3.2. o Chapter 6 describes the problems known to exist in BASEstar Open Client Version 3.2. o Chapter 7 contains release notes concerning documentation issues specific to BASEstar Open Client Version 3.2. 1.1 New and Changed Features With Respect to BASEstar Open Client Version V3.1 The new features provided by BASEstar Open Version 3.2 are as follows: o BASEstar Open Client no longer requires a local license; the BASEstar Open Server environment to which the client connects must grant a Client-Connection slot, which depends on a Client-Connection license that must be installed in the server environment. o Support for simultaneous access to a local and a remote realm Introduction and General Release Notes 1-1 Introduction and General Release Notes 1.2 BASEstar Open Documentation Set 1.2 BASEstar Open Documentation Set This manual describes a software component or aspects of the BASEstar Open family of products. The complete set of documents relating to the BASEstar Open family is as follows: o BASEstar Open: - BASEstar Open Introduction - BASEstar Open Reference Guide - BASEstar Open Command Language Interface - BASEstar Open Application Programming Interface - BASEstar Open Messages - Platform-specific installation and management guides - BASEstar Open Guide to DCM-Modeled Device Connectivity (for supported platforms) o BASEstar CIMfast (for supported platforms): - BASEstar CIMfast User's Guide - BASEstar CIMfast Programmer's Reference Guide - BASEstar CIMfast Guide to DECmessageQ Support (not available on Windows NT platforms) - BASEstar CIMfast Guide to SQL Support o DEComni API: - DEComni API and MMS User Guide - DEComni API Guide to Using Omni Directory Services (for supported platforms) - DEComni API Guide to Using OmniView (for supported platforms) - DEComni API Omni Definition Facility User Guide (for supported platforms) o Device Access Software documentation - Specific manuals for each supported device 1-2 Introduction and General Release Notes Introduction and General Release Notes 1.3 Pre-requisites 1.3 Pre-requisites BASEstar Open Client for Compaq Tru64 UNIX runs on the following architecture and software configurations: o An Alpha processor The BASEstar Open Client Software Product Description (SPD) provides a comprehensive list of the processors supported, together with any restrictions. o Digital UNIX Version 3.2C (or higher). o Compaq Tru64 UNIX Version 4.0F (or higher). By the time the product is shipped, the versions of these pre-requisites may have changed. Introduction and General Release Notes 1-3 2 _________________________________________________________________ Installation Release Notes 2.1 Installation Verification Procedure (UNIX platforms) To run the BASEstar Open Client Installation Verification Procedure (IVP) and the setup procedures, you must configure TCP/IP on the node where you intend to install the product. To check that your node is configured properly, type the following command: $ telnet `hostname` If you do not receive the login prompt, ask your system manager to check that TCP/IP has been configured correctly on your system. Installation Release Notes 2-1 3 _________________________________________________________________ New and Changed Features This chapter describes new and changed features with respect to BASEstar Open Client Version V3.1. 3.1 BASEstar Open Client No Longer Requires a Local Client Licence With Version 3.2, BASEstar Open Client no longer requires a local client licence; however when it connects to a BASEstar Open Version 3.2 Server, the Server itself grants or denies the connection, based on the availability, on the Server side, of a Client-Connection slot. The number of Client-Connection slots corresponds to the value of the Client-Connection licences that are loaded on the server node. Refer to the BASEstar Open Version 3.2 Release Notes for details about the new Client Licence Check mechanism. 3.2 Simultaneous Access to a Local and A Remote Realm BASEstar Open Version 3.2 Client provides a new BASEstar Open Client library that can be linked to a user application, together with the BASEstar Open Server library so that the application may get simultaneous access to a remote realm (via the Client library) as well as to a local realm (via the Server library). New and Changed Features 3-1 New and Changed Features 3.2 Simultaneous Access to a Local and A Remote Realm 3.2.1 The bstr2 Client Library An application can interface BASEstar Open within a BASEstar Open session that has been started by calling bstr_initialize and will be closed by calling bstr_finish. Only one session can be active at a time. When a BASEstar Open application starts, it loads the BASEstar Open Server or Client library; the library determines the relationship between the application and the realm or the realms to be serially accessed. The new bstr2 library allows an application to link with both the Server and the Client libraries without conflicts. 3.2.2 The bstr2 API The bstr API does not currently provide any mechanism to manage multiple BASEstar Open simultaneous sessions. To allow an application to work within a BASEstar Open Client session with a Server sesion already active, and distinguish between them, BASEstar Open Version 3.2 provides a new bstr2 API. The bstr2 API contains all and only the calls belonging to the usual BASEstar Open API, with the same arguments and semantics. Routine names are different, with bstr2_ prefix replacing bstr_ : therefore you have, for instance, bstr2_initialize, bstr2_finish, bstr2_reference_set etc. Every bstr2 routine matches and calls the corresponding bstr routine in the Client library, accessing its functionality but hiding its original name. By calling a bstr_ routine, the application accesses the functionality provided by the Server library. By calling bstr_ and bstr2_ routines, an application can run two simultaneous BASEstar Open sessions. 3.2.3 Installing the bstr2 Components The bstr2 components ( library, include files, and scripts) are installed during the BASEstar Open Client installation and require the BASEstar Open Server installation as a prerequisite. 3-2 New and Changed Features New and Changed Features 3.2 Simultaneous Access to a Local and A Remote Realm 3.2.4 Setting the bstr2 Environment Before running an application that calls bstr2 routines, the user must setup properly the BASEstar Open environment by running the script o /etc/bstr2users.csh (Compaq Tru64 UNIX) o BSTR$KITCLT:[ETC]BSTR2USERS.COM (OpenVMS) 3.2.5 bstr2 Include File The bstr2.h include file contains the definition of the bstr2_ routines. It is located in the directory referenced by the environment variable BSTR2_INCLUDE. 3.2.6 bstr2 Library The bstr2 library is o libbstr2cma.so (Compaq Tru64 UNIX) o BSTR2_SHR_CMA.EXE (OpenVMS) o bstr2.dll (Windows NT and Windows 95) and is located in the directory referenced by the environment variable BSTR2_LIB . Users cannot link the Client library when linking with the bstr2 library; however you must link with the Server library if the application calls bstr_ routines. 3.2.7 Example This sample program explains how to write a simple application that accesses simultaneously data points belonging to two realms. New and Changed Features 3-3 New and Changed Features 3.2 Simultaneous Access to a Local and A Remote Realm /************************************************************** test2.c **************************************************************/ #include #include #include #define ERROR(error_code, application_message) \ { \ bstr_t_error_text error_message; \ \ if (error_code != BSTR_S_NORMAL) { \ bstr_get_message(error_code, error_message, \ BSTR_C_ERROR_TEXT_LEN); \ fprintf(stderr, "Error: %s\n", application_message); \ fprintf(stderr, "Message: %s\n", error_message); \ } \ } bstr_t_status put_value1(char *dp, bstr_t_integer32 val) { bstr_t_status status; bstr_t_reference data_point = bstr_null_reference; printf("B Data point %s, new value : %d (0x%x)\n", dp, val, val); status = bstr_reference_set (dp, BSTR_C_DATA_POINT, BSTR_C_NOW, NULL, &data_point, NULL); ERROR(status, "Data_point bstr_reference_set failed."); status = bstr_data_point_put_value (&data_point, (bstr_t_value)&val, NULL); ERROR(status, "bstr_data_point_put_value failed."); status = bstr_reference_unset (&data_point); ERROR(status, "bstr_reference_unset failed."); return BSTR_S_NORMAL; } bstr_t_status put_value2(char *dp, bstr_t_integer32 val) { bstr_t_status status; bstr_t_reference data_point = bstr_null_reference; printf("B2 data point %s, new value : %d (0x%x)\n", dp, val, val); 3-4 New and Changed Features New and Changed Features 3.2 Simultaneous Access to a Local and A Remote Realm status = bstr2_reference_set (dp, BSTR_C_DATA_POINT, BSTR_C_NOW, NULL, &data_point, NULL); ERROR(status, "Data_point bstr2_reference_set failed."); status = bstr2_data_point_put_value (&data_point, (bstr_t_value)&val, NULL); ERROR(status, "bstr2_data_point_put_value failed."); status = bstr2_reference_unset (&data_point); ERROR(status, "bstr2_reference_unset failed."); return BSTR_S_NORMAL; } main() { bstr_t_status status; printf("Calling bstr_initialize ...\n"); status = bstr_initialize("R1", NULL); ERROR(status, "bstr_initialize"); printf("Calling bstr2_initialize ...\n"); status = bstr2_initialize("R2", NULL); ERROR(status, "bstr2_initialize"); put_value1("/dp1", 123); put_value2("/data2", 4567); status = bstr_finish() ; status = bstr2_finish() ; } This program can be compiled and linked by using the following command: Digital UNIX : cc -I$(BSTR_INCLUDE) -I$(BSTR2_INCLUDE) -o test2 test2.c \ -L$(BSTR_LIB) -lbstrcma -L$(BSTR2_LIB) -lbstr2cma OpenVMS: CC/INCL=(BSTR_INCLUDE,BSTR2_INCLUDE) TEST2.C LINK TEST2,BSTR_LIB:BSTR_CMA/OPTION,SYS$INPUT/OPTION BSTR2_SHR_CMA/SHARE The two realms R1 and R2 accessed by the application must be set up and started as usual. New and Changed Features 3-5 4 _________________________________________________________________ Restrictions This chapter describes all restrictions that apply to BASEstar Open Client Version 3.2. 4.1 Fields in a Structure_Datatype After creating a Structure_Datatype, it is not possible to modify or delete a field in the datatype. You must delete the datatype and then recreate it with the required fields. 4.2 Checking the Mapping Path When creating or modifying a Mapped_Data_Point, BASEstar Open does not perform validity checks on the mapping_path attribute. 4.3 Checking Filter Expressions When creating or modifying a Filter, BASEstar Open does not perform validity checks on the mapping_path attribute. 4.4 Datatype Congruency Checks When creating or modifying a Trigger, BASEstar Open does not check the datatype congruency of Filter and Event parameters with the Filter expression and the Event datatype. 4.5 Device Variable Address Checks When creating or modifying a Named_ or Unnamed_Variable, BASEstar Open does not check the address. Restrictions 4-1 Restrictions 4.6 Device Time Format Not Converted 4.6 Device Time Format Not Converted If the type of a Device_Data_Point or the type of field in a Device_Data_Point is TIME, BASEstar Open does not convert the corresponding value to the BASEstar Open internal format. Therefore, the BASEstar Open time routines do not work. 4.7 Spaces Not Accepted in File or Directory Names BASEstar Open cannot handle file or directory names that contain space characters. This limitation extends to the names of snapshot and work directories (if the user decides to modify the default name). 4-2 Restrictions 5 _________________________________________________________________ Bug Fixes This chapter describes BASEstar Open Client Version V3.0 and Version V3.1 bugs that have been fixed in Version 3.2. 5.1 Incorrect Error Message When Attempting to Map to a Data_Point in a Different Domain BASEstar Open does not allow you to create a Mapped_Data_ Point that maps to a Data_Point in a different Domain, as in the example below: SET CONTEXT /DOM2 CREATE MAPPED_DATA_POINT DP1_MAP -datatype INTEGER_16 \ -mapped /DOM1/DP_1 However, previous versions of BASEstar Open did not display an error message if you attempted to perform this operation. BASEstar Open Version 3.2 displays the following error message in response to the same operation: E-BSTR_S_BAD_PARAMETER: Invalid parameter value E-BSTR_S_DOMAIN_NOT_ALLOWED: Object 'DP_1' must belong to domain '/DOM2' 5.2 Abnormal Behavior of the bstr_get_object_type_info Procedure In previous versions of BASEstar Open, if you supplied the bstr_get_object_type_info procedure with the reference of a Data_Point, it returned the size of the Data_Point interms of the number of bytes occupied, together with a reference to the datatype object of the Data_Point in question. However, if you attempted to use the datatype reference, several problems became evident. For example, the first attempt to execute bstr_object_get_attributes resulted in a BSTR_S_INTERNAL_ERROR; a subsequent attempt was successful. This problem no longer exists in BASEstar Open Version 3.2. Bug Fixes 5-1 Bug Fixes 5.3 Watchdog Crash 5.3 Watchdog Crash In previous versions of BASEstar Open Client, there was a tendency for the Watchdog to crash (protection fault) while attempting to establish a connection with the server system. This was due to the inability of the Watchdog to handle server hostnames of more than 30 characters in length. This problem no longer exists in BASEstar Open Version 3.2. 5.4 CLI Segmentation Fault (UNIX only) In previous versions of BASEstar Open, the CLI sometimes crashed with a segmentation fault when executing PUT VALUE and GET VALUE commands. This problem no longer exists in BASEstar Open Version 3.2. 5.5 Consecutive BSTR Sessions BASEstar Open did not release all resources correctly if you invoke bstr_initialize() after calling bstr_finish() in a multithreaded environment. This problem no longer exists in BASEstar Open Version 3.2. 5.6 bstr_reference_recover BASEstar Open did not process correctly bstr_reference_ recover() in a multithreaded application. This problem no longer exists in BASEstar Open Version 3.2. 5.7 Hang in Complex Network Environments BASEstar Open entered into a hang status when multiple network cards were available and a network failure occurred when dynamic routing was not configured. This problem no longer exists in BASEstar Open Version 3.2. 5.8 Recovery for User Port Objects BASEstar Open Client did not perform correctly the recovery procedure on user Port objects. This problem no longer exists in BASEstar Open Version 3.2. 5-2 Bug Fixes Bug Fixes 5.9 CLI and Unaligned Access 5.9 CLI and Unaligned Access BASEstar Open Client might cause some unaligned accesses when reading naturally aligned data with the CLI get value commands. This problem no longer exists in BASEstar Open Version 3.2. 5.10 Memory Leak with Ports and Packets BASEstar Open Client generated a memory leak where two application programs exchanged data via the Port/Packet mechanism. This problem no longer exists in BASEstar Open Version 3.2. 5.11 Recovery Procedure loop The BASEstar Open Client recovery procedure entered into an infinite loop if the bstr_reference_set() procedure was not performed successfully on all the objects defined as recoverable. This problem no longer exists in BASEstar Open Version 3.2. 5.12 bstr_get_type_info unresolved symbol(OpenVMS only) The API function bstr_get_type_info, although prototyped in bstrppb.h, was reported by the linker as an "unresolved symbol". Now the problem has been fixed. 5.13 bstr_reference_set() Calling bstr_reference_set() with 'type' (3rd argument) set to: BSTR_C_ON_FIRST_USE | BSTR_C_RECOVERY_REQ resulted in an unusable reference. bstr_reference_set() returned BSTR_S_NORMAL, but as soon as one attempted to use the reference, for example in a bstr_data_point_get_value() call, BSTR_S_INTERNAL_ERROR was returned. The problem has been fixed in Version 3.2. 5.14 CREATE TRIGGER fails with INVALID_OPERAND The creation of a trigger failed when the associated filter has an EXPRESSION containing any of the #S , #OS, #V and #OV operands, and the associated data_point is either an ARRAY or a STRUCTURE. That was a regression now fixed. Bug Fixes 5-3 Bug Fixes 5.15 Non-privileged account problem(Windows NT only) 5.15 Non-privileged account problem(Windows NT only) The problems occurring in the setup and activation of BASEstar Client WNT when running under a non-privileged account were caused by the access to the LOCAL_MACHINE registry tree. The problem has been fixed in Version 3.2. Now it is possible to use a non-privileged account to setup BASEstar Open Client. 5.16 Stack overflow in cli_bstr It happened that running cli_bstr the following message appear: Stack overflow: pid 28148, proc cli_bstr .... Memory fault (coredump) It was due to a bug in the datatypes VODB navigation. The problem has been fixed BASEstar Open Version 3.2. 5.17 aligment warnings The following cli_bstr commands result in aligment warnings on Compaq Tru64 UNIX: create array_datatype STRING_3 \ -datatype VISIBLE_CHAR \ -array_type FIXED_LEN \ -num_of_elements 3 \ -description "3 Character String" create structure_datatype BUG_STRUCT -members (s:STRING_3 bug_d:D_FLOAT) create array_datatype BUG_ARRAY -datatype BUG_STRUCT \ -array_type VARIABLE_LEN -num_of_elements 5 crea data_point bug_demo -datatype BUG_ARRAY BSTR> get value data_point bug_demo varying array[5] of BUG_STRUCT (now 3) [ 0]: structure BUG_STRUCT { s: array[3] of VISIBLE_CHAR 123 bug_d: Unaligned access pid=7528 va=47c94 pc=120077e6c ra=120076b8c type=ldt 1.200000 The problem has been fixed BASEstar Open (BSO_ PRODUCT__VERSION). 5-4 Bug Fixes Bug Fixes 5.18 socket files left under /tmp 5.18 socket files left under /tmp The client watchdog did not delete socket files o when client application terminated without cleaning up the environment (e.g. terminated by "kill -9") o when the client application got an error while trying to connect to a realm. The problem has been fixed in BASEstar Open Client Version 3.2. 5.19 Recovery loop When a BASEstar Open Client called bstr_reference_set with recovery enable on N objects and one of these failed (e.g. OBJECT_NOT_FOUND), the retry attempts for reconnection go on forever (recovery loop). The problem has been fixed in BASEstar Open Client Version 3.2. Bug Fixes 5-5 6 _________________________________________________________________ Known Problems This chapter describes the problems known to exist in BASEstar Open Client Version 3.2. 6.1 Inconsistency of Timer and Trigger Attributes on PODB At present, when you create or modify Timer object definitions on the PODB, BASEstar Open only performs basic checks on the attributes of the object (for example, it checks that an integer value is an integer value). As a result, it is possible to create Timer object definitions with invalid attributes. Likewise, BASEstar Open only performs basic checks on Trigger objects whose trigger_ evaluation attribute is set to ON_TIMEOUT. BASEstar Open performs the necessary validity checks when you create or modify Timer and Trigger objects on the VODB. However, if you load PODB object definitions onto the VODB, an incorrect Timer (or Trigger ON_TIMEOUT) attribute may cause an error when BASEstar Open attempts to create the corresponding VODB objects. 6.2 Hostname Length Restriction BASEstar Open Version 3.2 does not support hostnames that are greater than 32 characters in length. 6.3 Concurrent put_value Operations on Mapped_Data_Points If two applications attempt to modify simultaneously the value of two Mapped_Data_Points, the Data & Device Services server may fail to update the value of the mapped Device_ Data_Point in both cases. Consequently, the PLC memory will not be updated with the new value. A workaround exists for this problem, consisting of an alteration at configuration level or of the applications involved. Known Problems 6-1 Known Problems 6.4 Assigning a Default Value to a Data_Point 6.4 Assigning a Default Value to a Data_Point BASEstar Open does not allow you to assign a default value to a simple datatype of the F_FLOAT or D_FLOAT type. 6.5 Cannot Specify Producer in a Different Domain When creating a Data_Point, the CLI does not allow you to specify a producer Data_Point in a different Domain. If you attempt to do so, the CREATE DATA_POINT comand hangs: SET SCOPE VOLATILE CREATE DATA_POINT /D1/PROD CREATE DATA_POINT /D2/CONS -producer /D1/PROD (hangs) However, if you create the two Data_Points separately and then link them, the problem does not arise: SET SCOPE VOLATILE CREATE DATA_POINT /D1/PROD CREATE DATA_POINT /D2/CONS LINK DATA_POINT /D2/CONS -producer /D1/PROD 6.6 LOAD CONFIGURATION Command If you execute a LOAD CONFIGURATION command without specifying the version of the snapshot that you wish to load, the CLI automatically loads the first snapshot generated. Therefore, to ensure that the CLI loads the desired snapshot, specify the version number. 6.7 BASEstar Open TIME data type TIME data type can have different values in BASEstar Open distributed environment when at least one node is a VMS node. If the time is in the daylight saving range there is a difference of (+/-) 1 hour among VMS and the other systems. In the following example a put value data_point of datatype TIME is considered. 6-2 Known Problems Known Problems 6.7 BASEstar Open TIME data type On UNIX (WNT) node: BSTR> crea data_point /dp_time -datatype TIME BSTR> put value data_point /dp_time (Date - [Wday] MON DD hh:mm:ss[.usec] YYYY): Aug 10 10:20:00 1999 On VMS node: BSTR> get value data_point /dp_time Tue Aug 10 09:20:00.000000 1999 BSTR> put value data_point /dp_time (Date - [Wday] MON DD hh:mm:ss[.usec] YYYY): Aug 10 10:20:00 1999 On UNIX (WNT) node BSTR> get value data_point /dp_time Tue Aug 10 11:20:00.000000 1999 Known Problems 6-3 7 _________________________________________________________________ Documentation Release Notes This section details any errors in the BASEstar Open documentation set. 7.1 The BASEstar Open Application Programming Interface This section lists any documentation errors in the BASEstar Open Application Programming Interface manual. 7.1.1 General Some of the BASEstar Open API functions do not fully implement all the capabilities made available by the "request control block". However, these limitations are not always highlighted in the BASEstar Open Application Programming Interface manual. For example, if you use the bstr_data_point_get_value routine with a timeout value set in the request control block, BASEstar Open returns the status code "Not implemented". 7.2 BASEstar Open Messages This section lists any documentation errors in the BASEstar Open Messages manual. 7.2.1 General Purpose and Common Services Messages The list of messages in the General Purpose and Common Services sections contains an incorrect explanation for BSTR_S_READ_ONLY. The full text associated with the message should be as follows: Documentation Release Notes 7-1 Documentation Release Notes 7.2 BASEstar Open Messages BSTR_S_READ_ONLY The Data_Point cannot be written Severity: Error Explanation: The current value of the specified Data_Point can only be read (for example, in the case of a Mapped_Data_ Point that is mapped to a Data_Point which is in turn linked as producer to one or more unsolicited consumers). User Action: Examine the source program and correct the problem. 7-2 Documentation Release Notes