Main Menu

KB#00707-Release Notes for Data Server NT REV 2.02

Title:

Release Notes for Data Server NT REV 2.02

Description:

================================================================== 

"relnotes.txt" for PRO/5 Data Server(R) 2.02 

================================================================== 

Copyright 1998 BASIS International Ltd. 


================================================================== 
CONTENTS 
================================================================== 

1. OPERATING SYSTEM NOTES 
2. WHAT'S NEW 
3. NOTES 
4. KNOWN PROBLEMS 
5. SUPPORT 

================================================================== 
1. OPERATING SYSTEM NOTES 
================================================================== 

===UNIX SUPPORTED PLATFORMS=== 

This release of PRO/5 Data Server 2.02 runs on: 
o AIX 4.1.4 and 4.2 
o DG/UX R4.20MU02 
o DIGITAL UNIX 4.0B 
o HP-UX B.10.10 and B.10.20 
o Motorola System V R40V4.4 
o Red Hat Linux V5.0 Kernel 2.0.32 
o SCO UNIX SysV Rel 3.2v4.2 and Rel 3.2v5.0.4 
o Solaris 2.5, 2.6 for SPARC 
o UnixWare System V R4.2MP v2.1 

===WINDOWS SUPPORTED PLATFORMS=== 

This release of PRO/5 Data Server 2.02 runs on: 
o Windows NT 3.51 Service Pack 5 
o Windows NT 4.0 Service Pack 3 

===NOVELL NETWARE SUPPORTED PLATFORMS=== 

This release of PRO/5 Data Server 2.02 runs on: 
o Novell NetWare 3.2 
o intraNetWare 4.11 


================================================================== 
2. WHAT'S NEW 
================================================================== 

===UNIX, WINDOWS NT, NOVELL NETWARE=== 

* STRING FILE READ SPEEDUP 
Some improvement in the performance of READs from a string file 
has been gained by using a new buffering scheme within the 
string file type driver of PRO/5(R). A two-to-seven time 
performance improvement can be seen. The level of performance 
improvement is highly dependent on the access patterns and the 
length of the data retrieved from a string file with the READ 
verb. This enhancement does not affect the performance of the 
READ RECORD verb. 

* MAXIMUM SIZE OF PREFIX EXPANDED TO 1024 BYTES 
The maximum length of the PREFIX has been changed from 256 to 
1024 bytes. 

===UNIX=== 

* SELECTED CHANNEL 
The SELECT implementation in the Data Server has been enhanced 
to support the use of a SELECTed channel, where the channel is 
SELECTed via a Data Server by the Visual PRO/5(R) data-aware 
grid. 

* READ ONLY 
The Setopts byte can be configured to byte 7 bit $04$ to be 
read only. Turning on the setopts bit for a Data Server causes 
the Data Server to return an error on any attempt to WRITE, 
RENAME, ERASE, FILE, INITFILE, or use any verb that causes the 
creation of a file (i.e. MKEYED, etc). 

===WINDOWS NT=== 

* READ ONLY 
The Setopts byte can be configured to byte 7 bit $04$ to be 
read only. Turning on the setopts bit for a Data Server causes 
the Data Server to return an error on any attempt to WRITE, 
RENAME, ERASE, FILE, INITFILE, or use any verb that causes the 
creation of a file (i.e. MKEYED, etc). 

===NOVELL NETWARE=== 

* LARGE READS AND WRITES 
It is now possible to read and write buffers greater than 64K 
bytes via one READ/WRITE statement. 

* LONG FILE NAMES 
Enable long file name support by placing the following line in 
the Data Server's config.bbx file: 

LONGNAMES 

On Servers that have the long name space installed on all 
volumes, place the following line in the Data Server's 
config.bbx file to maximize performance: 

NO_MIXED_NAME_SPACES 

It is recommended that ALL volumes on the Data Server be 
configured for long name space when using LONGNAMES in 
config.bbx. 

* SERVICE NAME CUSTOMIZATION 
It is now possible to customize the NLM's service name by 
putting a line similar to SERVICENAME=somename in config.bbx. 

===DOCUMENTATION=== 

* HTML versions of the newly revised Data Server Guide and the 
PRO/5 2.0 Supplement to the PRO/5 manual set are included in 
this release. 


================================================================== 
3. NOTES 
================================================================== 

===UNIX, WINDOWS NT, NOVELL NETWARE=== 

When parsing MODE= on an OPEN, PRO/5 now checks to ensure mode 
array bounds are not exceeded. An OPEN() verb now has 40 modes. 

-------------------- 
PRO/5 can now create files with a Data Server path in the prefix, 
without generating an error. 

-------------------- 
For more information on enhancements specific to the Visual PRO/5 
Novell Client, see the online Help version of the Installation 
and Configuration Guide in the PRO/5 Under Novell NetWare section. 


================================================================== 
4. KNOWN PROBLEMS 
================================================================== 

===UNIX=== 

When using UNIX clients with the Windows NT Data Server, the 
clients cannot access files based on Windows NT drive letter 
designations (C:/, D:/, etc). The correct method is to have 
clients prefix to the Data Server, and configure the Data Server 
to handle pathing information via its config.bbx file. 

-------------------- 
UNIX clients can only create files through the Windows NT Data 
Server if the Windows NT Data Server is limited via DSKSYN or 
prefix to the single drive that the Data Server is installed on. 

===WINDOWS NT=== 

An Intel Pentium processor, or equivalent, is highly recommended. 
IMPORTANT: Do not run the PRO/5 Data Server with Windows NT on 
any hardware that has BIOS POWER SAVING (DPMS) enabled. 

-------------------- 
This release does not allow the Data Server to be started 
automatically at system boot time. With Windows NT, there is NOT 
an initialization script file that is executed at operating system 
boot time as with most UNIX platforms. The Data Server can be 
started at user login time by putting its Icon in the Start-up 
Program Manager group. 

-------------------- 
This version of the PRO/5 Data Server does not support the Windows 
NT or UNIX style ".rhost" form of user authentication. There is no 
remote-to-local user authentication in the PRO/5 Data Server for 
Windows NT. 

===NOVELL NETWARE=== 

With long file name support enabled, only long file names can be 
used to access files on volumes that have a long name space. Use 
of the alias MSDOS file names results in an !ERROR=12. 

--------------------- 
The RENAME verb does not currently work on volumes configured for 
long name space. !ERROR=60 is the result of attempting RENAME 
on a volume with long name space configured. 

--------------------- 
If LONGNAMES is specified in the Data Server's config.bbx, but the 
SYS volume does NOT have a long name space, prefixes specified in 
the Data Server's config.bbx for volumes that DO have long name 
spaces do not work. This problem does not apply to prefixes used 
by the client. 

NOTE: It is recommended that ALL volumes on the Data Server be 
configured for long name space when using LONGNAMES in config.bbx. 

--------------------- 
If LONGNAMES is specified in the data server's config.bbx, and the 
SYS volume DOES have a long name space, prefixes specified in the 
Data Server's config.bbx file for volumes that do NOT have long 
name spaces do not work. Again, this problem does not apply to 
prefixes specified by the client. 

NOTE: It is recommended that ALL volumes on the Data Server be 
configured for long name space when using LONGNAMES in config.bbx. 

--------------------- 
On NetWare 4, the work station using the Data Server must have a 
licensed connection to the NetWare Server that is running the data 
server NLM. This can be accomplished by mapping a drive to any 
volume on the Server. Attempting to access the Data Server with a 
client that has only an authenticated connection obtained from the 
NetWare directory services to the server results in an !ERROR=60 
(tcb(10)=-251). 

--------------------- 
The INFO() function has several items that are different. 

INFO(2,...) does not return the user slot information because 
user slot license checking is not performed. 

(Items labeled as "NDS and Bindery" are obtained from NetWare 
Directory Services, if the connection supports it. If NDS is not 
available, the items are read from the bindery or emulated 
bindery before a failure is reported.) 

INFO(3,2) returns the user name (NDS and Bindery) 
INFO(3,3) returns the user description (NDS and Bindery) 

-------------------- 
When using NDS to access a remote-spooled printer, it may be 
necessary to specify the server= mode option if an !ERROR=60 
occurs with TCB(10) equal to -35228. 


================================================================== 
5. SUPPORT 
================================================================== 

===INTERNATIONAL=== 
International users should contact their authorized BASIS 
Distributor for technical support. German, Austrian, and Swiss 
users should contact BASIS International Software GmbH, BASIS' new 
subsidiary, or HERE for details. 

===UNITED STATES=== 
Technical support is available to all U.S. customers directly from 
BASIS International Ltd. Search the extensive support materials
HERE.



All domestic customers who purchase products from BASIS 
automatically receive thirty days of free telephone support per 
product serial number, activated upon the first phone call. BASIS 
analysts are available Monday through Friday, 8:00AM-5:00PM MST. 
Free technical support is available via fax or e-mail. However, 
fax and email support receives a lower priority than telephone 
calls or voice mail messages. 

PHONE - 505.345.5021 
FAX --- 505.344.9057 
EMAIL - support@basis.com 

Also, check HERE for 
additional information on how to contact technical support or 
download a Technical Support Fax Request form. 

When calling or sending a technical support question, users should 
provide the following information: 

o The product serial number. 
o The name of the product, and the product's revision number. 
o A complete description of the problem, including the PRO/5 
error and the TCB(10) value, if available. 

Other pertinent information includes: 

- The operating system name, level, and revision. 
- Is the error consistently reproducible, or is it sporadic? 
- Is the error isolated to a specific machine or user? 
- Is this a new installation, or has the system been in place 
and operating normally? 
- Is the problem network related/specific? 


------------------------------------------------------------------ 

Copyright 1998 BASIS International Ltd. All rights reserved. 
BBx(R), BBxPROGRESSION/4(R), BBxPROGRESSION/4 Data Server(R), 
Visual PRO/5(R), PRO/5(R), PRO/5 Data Server(R), BASIS ODBC 
Driver(R), DDBuilder(R), and TAOS: The Developer's Workbench(R) 
are registered trademarks of BASIS International Ltd. 
ResBuilder(TM), and GUIBuilder(TM) are trademarks of BASIS 
International Ltd. All other product names and brand names are 
service marks and/or trademarks or registered trademarks of their 
respective companies. 


[end of file] 



Last Modified: 01/17/2011 Product: PRO/5 Data Server Operating System: N/A Windows NT

BASIS structures five components of their technology into the BBx Generations.

  Google+ View BASIS LinkedIN ProfileVisit our Twitter Feed Check out our Facebook Public Profile Click to View the BASIS youTube channel