Escolar Documentos
Profissional Documentos
Cultura Documentos
Version 3.2
for
DOS/UNIX/Win32
COPYRIGHT NOTICE
Copyright 1998-2001 DATA ACCESS CORPORATION. All rights reserved. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated into any human or computer language, in any form or by any means, electronic, mechanical, magnetic, manual, or otherwise, or disclosed to third parties without the express written permission of Data Access Corporation, Miami, Florida, USA. DISCLAIMER Data Access Corporation makes no representation or warranties, express or implied, with respect to this publication, or any Data Access Corporation product, including but not limited to warranties of merchantability or fitness for any particular purpose. Data Access Corporation reserves to itself the right to make changes, enhancements, revisions and alterations of any kind to this publication or the product(s) it covers without obligation to notify any person, institution or organization of such changes, enhancements, revisions and alterations. TRADEMARKS DataFlex is a registered trademark and Flex-Keys is a trademark of Data Access Corporation. All other brand and product names are trademarks or registered trademarks of their respective companies. All other company, brand, and product names are registered trademarks or trademarks of their respective holders.
Contents
CONTENTS ........................................................................................................ 3 PLATFORMS SUPPORTED ............................................................................ 5 UNIX ............................................................................................................... 5 SCO Unix .................................................................................................... 5 IBM AIX 4.2 ................................................................................................ 5 Linux ........................................................................................................... 5 Sun Solaris 2 ............................................................................................... 5 UnixWare .................................................................................................... 6 Hewlett-Packard HP-UX 10.20 .................................................................. 6 DOS ................................................................................................................. 6 Minimum System Requirements .................................................................. 6 Recommended System Configuration ......................................................... 7 WIN32 .............................................................................................................. 7 INSTALLING DATAFLEX .............................................................................. 7 CD DELIVERY MEDIUM ................................................................................... 7 IMPORTANT NOTES FOR CURRENT DATAFLEX USERS ...................................... 8 BEFORE YOU BEGIN ....................................................................................... 10 DOS/WIN32 INSTALLATION ........................................................................... 10 Registering DataFlex ................................................................................ 12 Configuring DataFlex ............................................................................... 13 User Counting System............................................................................... 15 Use of the SHARE Command for Windows, Single-User DOS, Peer-toPeer Networks, and Other Networks......................................................... 17 Windows NT Networks .............................................................................. 19 Sharing DataFlex Files on NT Servers ..................................................... 21 Microsoft Redirectors for a Novell Network ............................................. 23 NetWare Transaction Tracking System..................................................... 24 UNIX INSTALLATION ..................................................................................... 25 Installing from CD-ROM .......................................................................... 25 Installation, Registration, and Setup ........................................................ 26 Modifying Terminal Information .............................................................. 28 INCREASING THE NUMBER OF USERS .................................................. 28 THE SAMPLE APPLICATIONS ................................................................... 29
Installation and Environment Guide 3
RELEASE NOTES ........................................................................................... 29 INSTALLING AND USING THE ELECTRONIC DOCUMENTATION . 29 ADOBE ACROBAT READER ............................................................................. 29 INSTALLING THE ADOBE ACROBAT READER .................................................. 30 INSTALLING THE DOCUMENTATION ................................................................ 30 USING THE DOCUMENTATION ......................................................................... 30 GETTING STARTING WITH DATAFLEX (UNIX) ................................... 33 GETTING STARTING WITH DATAFLEX (DOS & WIN32) ................... 33 BUG REPORTING GUIDELINES ................................................................ 34 OBTAINING TECHNICAL SUPPORT ........................................................ 36 WHO IS ELIGIBLE FOR TECHNICAL SUPPORT? ................................................. 36 WHAT AREAS DOES TECHNICAL SUPPORT COVER? ......................................... 36 GETTING TECHNICAL SUPPORT ...................................................................... 36 WHERE TO FIND US ON-LINE ........................................................................... 37 WHERE TO WRITE TO US ................................................................................. 37 WHERE TO FAX US ........................................................................................ 37
Platforms Supported
UNIX
The CD-ROM may contain one ore more installation programs for the platforms listed. The Software License will indicate the appropriate platform and license (Full Development or Runtime Only) to install. If the license you purchased is runtime only, you may upgrade this software to a full development package merely by purchasing a full development upgrade license either from your runtime supplier or Data Access Corporation. Neither package can be used direct from the distribution media; they must be installed. SCO Unix This version is ported and tested using SCO 3.2v5.0.4, and tested on SCO 3.2v4.0. It is intended for use on systems running SCO 3.2v4 and higher. If you are using UnixWare 7.0.1 or higher, we recommend the using the UnixWare port instead of the SCO port. IBM AIX 4.2 This version is ported and tested on IBM AIX 4.2. It is intended for use systems running IBM AIX 4.2 and higher. Linux This version is ported and tested on Red Hat kernel 2.2.14. It was also tested on Caldera kernel 2.2.14. It is intended for use on systems running any Linux system with a kernel of 2.2.14 or higher. Sun Solaris 2 This version is ported and tested using SunOS 5.6 Generic. It is intended for use on systems running Solaris 2.1 or higher.
UnixWare This version is ported and tested on (SCO) UnixWare 7.0.1 using CCS 3.2. It is intended for use on systems running UnixWare 7.0.1 and higher. Hewlett-Packard HP-UX 10.20 This version is ported and tested on HP-UX 10.20. It is intended for use systems running HP-UX 10.20 and higher.
DOS
To run the DOS runtime (DFRUN) or any of DataFlexs other executables (utilities), DOS Version 6.2 with EMM386 (included with your DOS) or QEMM 386 Version 7.0, or higher are required. SHARE may have to be loaded. The recommended settings are SHARE /F:8192 /L:500. Note: this revision of DataFlex is not supported for use under OS/2. Minimum System Requirements This revision of DataFlex cannot be expected to perform well the following minimum requirements: A 386-class PC or better. 512 Kilobytes of base RAM. A hard disk drive, with at least 30 Megabytes of available disk space. The DataFlex documentation will consume approximately 20 Megabytes of additional disk space. 3 Megabytes of free EMS or XMS. Note that you cannot add EMS and XMS memory together to yield the required amount. For larger applications, this memory requirement may be greater.
Recommended System Configuration For optimum performance, we recommend the following system configuration: A Pentium PC or better. 512 Kilobytes of base RAM. A hard disk drive, with at least 30 Megabytes of available disk space. The DataFlex documentation will consume approximately 20 Megabytes of additional disk space. 5 Megabytes of Windows memory above any required by the operating system for other processes running.
Win32
To run the Windows console-mode runtime (DFRUNCON), Windows 95/98/ME, Windows NT 4.0 or Windows 2000 are required. The Windows registry must also be changed as described in Windows NT Networks starting on Page 19. To use the Novell TTS capabilities you must have the Novell client software installed.
Installing DataFlex
This information will assist you in the installation of DataFlex 3.2 and its electronic documentation.
CD Delivery Medium
The software for all the supported platforms is present on the media. If you install DataFlex for a platform other than that for which you are licensed, it will install, but every attempt to run it will trigger a DataFlex not Installed error, and it will not run.
CD Directory Structure
Directory ACROBAT DACDOC DACDOC\DF32 Contains, in Acrobat format, the complete documentation set for DataFlex. Note that the PDF files are not compressed. Contents Contains the Acrobat Readers
PRODUCTS PRODUCTS\DF32 PRODUCTS\DF32\DOS-CM Contains all the files to install DataFlex 3.2 for DOS 386 Protected Mode and Console Mode. Contains all the files to install DataFlex 3.2 for Sun Solaris 2.3. Contains all the files to install DataFlex 3.2 for Linux Contains all the files to install DataFlex 3.2 for Hewlett-Packard HP-UX.10.20. Contains all the files to install DataFlex 3.2 for IBM AIX 4.2. Contains all the files to install DataFlex 3.2 for SCO UNIX System V. Contains all the files to install DataFlex 3.2 for SCO UnixWare (SCO 7.0.1).
PRODUCTS\DF32\Aix4 PRODUCTS\DF32\SCO5
PRODUCTS\DF32\UnixWare
This revision of DataFlex can run only programs compiled with the current compiler and flex.cfl (fmac). If you wish to run any program that relied on a modified fmac, you must replicate those modifications in the current fmac and repack it to a new flex.cfl before recompiling. Do not install or use the DataFlex Application Framework with this revision. Improved Framework capabilities are integrated in this revision of DataFlex. Where you must retain the Flex-Key mappings of Rev. 2.3 for an application, you may add a read_dfini statement to the beginning of the program(s) naming \DF32\USR\DFINI23.CFG, a file supplied for this purpose. If you wish to change the mapping in this file, use the Configuration Utility (DFCONFIG) to edit this file. .FLX files compiled in Revision 3.2 cannot be run by earlier revisions of DataFlex! DataFlex 3.05 and 3.1 source code is fully compatible with Revision 3.2 (when used in non-DD mode) and should compile and operate without problem. If you use the current File Definition Utility to modify (e.g., to add a field or turn header-integrity checking on), a data file created under an earlier revision of DataFlex, the data file will be saved in the new format. As a result, you will thereafter not be able to access the data file with any runtime earlier than Rev. 3.01b or programs compiled under such revisions. Where you must retain the ability to use the earlier revision, modify such files only with the utilities of the earlier revision. Files created using extended filelist are only accessible by DataFlex 3.2, Visual DataFlex 7 and WebApp Server 3 (or higher). Data files created in the format of the current revision will be accessible by all revisions 3.01b or later, unless you use the extended filelist capabilities of DataFlex 3.2. Files created using extended filelist are only accessible by DataFlex 3.2, Visual DataFlex 7 and WebApp Server 3 (or higher).
9
This version of DataFlex no longer supports DataFlex graphics. User counting is maintained in: UNIX Systems: /usr/tmp in a file named serial_num.dfr, where serial_num is the serial number of the DataFlex runtime.
The serial_num.dfr file is created whenever DFSETUP is run and the changes are saved. Except for when user rights are insufficient, problems are normally corrected by re-running DFSETUP.
DOS/Win32 Installation
The following steps will install DataFlex on your system. 1. Start up your computer or network server (log in as the system administrator or most-privileged user) as you
10 DataFlex for DOS/UNIX/Win32
normally do. 2. Place the CD-ROM disk in your CD-ROM drive, log on to that drive, and change to the \PRODUCTS\DF32\DOS-CM subdirectory. 3. At the operating-system command line, type INSTALL (and press Enter). 4. You will be asked to verify the target drive letters and directory name. If they are not correct, or if one or more were omitted, you may change them at this point. 5. The installation program will display details about the version of DataFlex you are installing. Read this description carefully so as to avoid installing the wrong version of DataFlex. Follow the succeeding screen prompts carefully. If at any time you need to stop installation, press Ctrl+C. 6. If the installation program displays one or more operating system error messages, you should take note of them, correct their cause, and then rerun the installation program. Examples of errors are: "disk full"; "can't create directory"; "drive not ready"; "write protected"; or "invalid drive". 7. To install the Novell TTS software, you will have to accept the Novell client license that will be displayed. If necessary, check with your applications developer to determine whether such support is used in your application. 8. The DataFlex files are copied onto your hard drive in a logically designed directory structure under the main directory you specified at the beginning of the installation (or under the default, \DF32). You may change the location of the files, but it is suggested you do not, unless you have particular reasons to do so. The installation process includes the writing of a batch file, which you can call to set the environment variables PATH, and DFENV, so that DataFlex can find all the correct files when they are needed. This batch file, named SETPATH.BAT, is located in the USR directory under the main directory where you installed DataFlex. You can either run it manually each time you want
Installation and Environment Guide 11
to run DataFlex, or you can add its commands to your AUTOEXEC.BAT file so that the environment variables are set automatically each time you boot your computer. The DFENV environment variable allows you to specify the full path of an ASCII file containing environment settings. For example, you may create a file named DFENV.CFG under the \DF32\USR sub-directory. In this file you may include a string value for the DFPATH environment variable, which contains the name of the directories searched on your disk drive(s) when you are opening, creating, deleting, renaming, or copying DataFlex files. To actually use the string value, you must set the new environment variable, DFENV, to the name of the configuration file (i.e., DFENV.CFG). One of the benefits of using this mechanism is that you can specify an extremely long DFPATH value without worrying about operating system limitations. Furthermore, you may include any number of DataFlex environment variables in this configuration file. By default, DataFlex installs a configuration file named DFENV.CFG in your USR directory. It is important to note that the values defined in this file for DataFlex environment variables will supersede any settings you may have set at the O/S level directly in the same variables. 9. After all of the files are placed onto the hard disk, a message will appear, informing you that the installation process has been completed. The installation program will ask you whether you want to start the setup program DFSETUP. This program is used to install your registration code. The registration instructions displayed will take you through this process step by step. Note: Runtime installations may require extra installation steps, as provided by the application vendor. Registering DataFlex The Setup Utility DFSETUP will start at the end of the installation process if you confirm that you wish it to. This utility is discussed
12 DataFlex for DOS/UNIX/Win32
in more detail in the Setup and Configuration chapter of the DataFlex User's Guide. Its purpose is to register your license and create the user-counting file. Configuring DataFlex Using DFCONFIG The Configuration Utility (DFCONFIG) allows you to optionally set certain attributes such as screen colors and function keys to use, which characters to use to represent money amounts, and how to format dates.
Notes:
In previous revisions of DataFlex 3, the Setup Utility allowed you to modify the DataFlex screen colors. In 3.2, you must use the DFCONFIG utility instead. The Windows Operating System does not support the blinking screen attribute and therefore, is not supported by DataFlex.
Default Function-Key Assignments Your DataFlex package comes with certain function keys already assigned. If you wish to change any of these assignments, then you must run the DataFlex Configuration Utility (DFCONFIG). Refer to the DataFlex User's Guide for more information about DFCONFIG. See the paragraph under "The Installation Program" about Flex-Key functionality of programs compiled under earlier revisions of DataFlex and running under the current revision. The default function key assignments are shown in the following tables, with those defined in Data Access packages followed by an asterisk (*):
13
Shift + KEY
Ctrl + KEY
User Key 2
Exit Applicatio n Clear All Panels Switch to Prev Panel* Calculate Switch to Next Panel*
F5 F6
Clear Area Switch to Next Area Find Previous Find Next Find Switch to Action Bar Accept Next Item Insert/Overty pe Toggle Delete Character Cursor Left Cursor Right Cursor Up
Refresh Screen Switch to Prev Area Superfind Previous Superfind Next Superfind Add Mode On/Off*
F7 F8 F9 F10 Enter Tab Insert Delete left arrow right arrow up arrow
Trace On/Off*
Zoom
14
KEY down arrow spacebar Backspac e Home End Page Up Page Down Esc \ + Cursor Down Selection Toggle Destructive Backspace Begin of Line End of Line Scroll Page Up Scroll Page Down Escape (Cancel)
Shift + KEY
Alt + KEY
Erase to End of Line Begin of Data End of Data Scroll Page Left Scroll Page Right
Non-WP backspace
User Counting System Upon execution of the DFSETUP program, a file will be created to count concurrent users of DataFlex on a LAN. This is usually stored in the directory where DFSETUP was executed and will have a root name equivalent to your serial number and an extension of .DFR. For example, if your serial number is 440,000, then the .DFR file will be named 440000.DFR. (UNIX: .440000.DFR) Only one copy of the .DFR file should exist for any one serial number and that file must be accessible, via DFPATH, to all users who use that serial number. (UNIX: The location is \usr\tmp A .DFR file should not be moved or copied. It may only be
15
created with DFSETUP. Attempting to move the file or having more than one .DFR file for the same serial number may cause the file to be rejected. If the .DFR file is damaged in any way, you will receive an appropriate error message when you try to run DataFlex. You may re-create the .DFR file by running the DFSETUP program and selecting Option 3. Each invocation of DFRUN consumes one authorized user, regardless of whether this is on the same computer or another using the runtime. Only the first invocation of DFRUNCON is counted on each machine. When the maximum number of users accessing DataFlex and another user attempts to start it, that user will receive a message explaining the condition and will be unable to start DataFlex successfully. The user will be able to start DataFlex as soon as one or more of the current users exits DataFlex. You may purchase additional user licenses from your dealer or Data Access Corporation.
16
Use of the SHARE Command for Windows, Single-User DOS, Peer-to-Peer Networks, and Other Networks When to Load SHARE You only need to load SHARE if you are not using an operating system which has SHARE's functionality built in (like Novell's NetWare) and you are accessing files in a multi-user manner. Accessing files in a multi-user manner could mean actually having multiple users open and accessing the file (i.e. Lantastic), and/or having multiple tasks accessing the same files (i.e. Windows or DesqView), or running DataFlex programs (whether single or multi-user) that open the same file more than once concurrently. How can you determine whether such a condition applies to your system? Check for any of the following conditions: 1. If you use the chain wait command to invoke a second DataFlex program, and that program opens one of the same files in use by the original program, SHARE is needed. Note: If you use the export_files option SHARE is not needed, since both programs will share the same file buffer and handles. 2. If you use file aliases, you need SHARE loaded. This is the process of defining multiple files in FILELIST.CFG with different DataFlex names but using the same physical rootname. 3. If you are using the File Definition Utility open a file, and then execute a maintenance option. This invokes the File Maintenance Utility, a separate program, which could access the same files that File Definition already has opened. SHARE is needed in this case. This is of concern only for users with development licenses, since File Definition is not part of the runtime license. 4. The following test fails. THE FOLLOWING TEST SHOULD NOT BE PERFORMED ON LIVE DATA! This test consists of two machines, named A and B, which are running DataFlex and accessing the same data file(s). Machine "A"
Installation and Environment Guide 17
finds a record and performs a lock on that record. Machine "B" Finds, Edits, and attempts to save the same record. If Machine B can save the record, the test fails (SHARE is required). The test succeeds if Machine "B" waits indefinitely for Machine A to release the lock. If you are using an operating system, which does not have, SHARE support built in (the test described above fails) and you are doing one of the above three items, you need to load SHARE. If SHARE happens already to be active on any computer that is using DataFlex, you must check to make sure it is loaded with at least the command-line parameters shown below. How do you load SHARE? Simply add the line SHARE to your AUTOEXEC.BAT file. This loads SHARE with the default parameters. There are two parameters used when loading SHARE: the L and F parameters. They define the size of two separate tables that SHARE maintains. The first, L, is the size of the SHARE LOCK table. The L parameter defines the number of locks that SHARE can access. The default L parameter is 60. Set the L parameter to a number equal to the number of locks you expect plus a bit of extra space. Note that DataFlex will issue a maximum of one lock per data file. The F parameter specifies how many bytes are allocated to the file handle table. This table stores the complete pathname of the file plus 11 bytes of overhead per file. Thus C:\DATAFLEX\DATA\DOUG.DAT would require 36 bytes in the file handle table. The default for the F parameter is 2048, which will allow you to approximately 20 files with large file paths. Increase this number as needed for your application. Keep in mind that SHARE is not a per-process setting, but a permachine setting. Thus, if you want to run 5 different programs at the same time on the same machine, each one opening 30 files, the F parameter in SHARE would need to be large enough for 150 files. Also, the L parameter would need to be able to handle
18 DataFlex for DOS/UNIX/Win32
the 150 potential locks. Here is an example of loading SHARE, increasing the F parameter to 8192 and the L parameter to 500:
SHARE /F:8192 /L:500
If SHARE is not loaded and you attempt multi-user access (and you are not using an operating system with SHARE capabilities built in) file corruption can occur. If you install SHARE with insufficient settings for the F or L parameters, a variety of DataFlex errors may result such as: "Can't open datafile", "Too many locks"," Read error on index file", "Seek to unwritten extent", etc. The corruption can occur due to DOS keeping a separate buffer and file handle for the same file in two different applications. When records are added or edited in one file, the other (really the same physical file) does not get updated. With SHARE, all files opened with the same physical name share the same buffers, regardless of which application opened them. Note that the above setting would use 11692 bytes: 8192 for the
F parameter and 3500 for the L parameter (each lock requires 7
bytes of overhead). For more information on SHARE, consult your DOS documentation or contact your DOS manufacturer. Windows NT Networks Windows 95 Workstation Clients Using Microsoft Network redirectors that open files stored on Windows NT machines results in buffering, which causes data corruption. Microsoft has now provided a replacement, Microsoft Network Redirectors VREDIR.VXD for Windows 95 that does disable the buffering of files shared on Windows NT. The redirector executable is a self-installing program provided by Microsoft. Run it under Windows 95 and it installs itself and makes the needed changes to your Windows registry. You then need to restart Windows 95 for the changes to take effect. This new redirector removes the local caching that the old redirector included. The local caching would cause data errors
Installation and Environment Guide 19
when retrieving data from an NT server. The new redirector has been extensively tested by Data Access Corporation and does indeed solve the problems with data reliability between a Windows 95 workstation and an NT server. This redirector is not needed if accessing data on a NetWare server. However, installing the new redirector will have no detrimental effects on sites not using NT servers. Thus, our general recommendation would be to use the new redirector at all customer sites. You may find the VREDIR executable on your disk after the installation process of DataFlex if you installed from CD media. The new OSR2 version of Windows 95 (generally shipped with new machines in the last quarter of 1996 and into 1997) comes pre-installed with the new redirector. This is the same version of Windows 95 with the new FAT32 file system. Note: When you search for VREDIR.VXD on a machine that has not had either the patch or the OSR2 revision installed, the first entry found is simply the component name and its associated data (displayed in hex). On any machine which was shipped with the OSR2 release, or had the patch installed, the first entry that is found displays a comment about Samba UNIX and the revision number 4.00.955 beneath the comment (the screen with the hex data will be the second one found). Warning: Even if your machine came with the new VREDIR.VXD (Version 4.00.955) installed, you will still experience corruption problems if the registry key DiscardCacheOnOpen is not set to true (1 hex). This key is not defined as part of standard Windows 95 installations, but will automatically be defined and set if you use the patch provided to us by Microsoft. (You may download this patch from ftp://ftp.dataaccess.com/anonymous/pub/redir), or install it from the DataFlex CD from the directory \MISC\REDIR). You may verify (and correct, if necessary) this setting with Regedit by querying this key in HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/V xD/VREDIR DiscardCacheOnOpen = (1 hex). If you have OSR2, you must enter it yourself. Start the program:
20 DataFlex for DOS/UNIX/Win32
Regedit.exe Choose: HKey_Local_Machine -> System -> Current Control Set -> Services -> VxD -> VREDIR -> Right-click or pull down Edit -> New -> Binary Value -> Rename value -> Value name: DiscardCacheOnOpen Data type : BINARY Modify -> Parameter value: 00 01 (type in the zeroes)
Sharing DataFlex Files on NT Servers You will experience data and index file corruption (or at least an apparent lack of synchronization between the data at various workstations) when using DataFlex in configurations, where the shared-files are stored on a Windows NT Server. These problems were verified in-house. It was also reported that Microsoft Access had similar problems and required that opportunistic locking (an NT feature) be disabled at the server, for the Access application to function correctly. This information is covered in the Microsoft Knowledge Base article Q165351. If you examine the Knowledge Base article, references are made
Installation and Environment Guide 21
to NT Workstation settings, as well as the server settings. It is important to note that the updated VREDIR.VXD workstation fix is also required for stable operations, when using Windows 95 workstations. There are actually two different operating system level functions at work. Using combinations of Windows 95 and Windows NT workstations and Windows NT server: local buffering of data at the Windows 95 workstations. Controlled by VREDIR.VXD and its registry settings at the workstation, and opportunistic-locking buffering at the Windows NT workstations (controlled by combinations of settings at the workstation and server) are supported by disabling it at the server level. Verify (and correct, if necessary) these NT Server parameters:
This is done by starting the program with: "Start" | "Run" | "Regedit" OR ...\WinNT\Regedit.exe Choose: HKEY_Local_Machine -> System -> Current Control Set -> Services -> LanmanServer -> Parameters -> If the Value EnableOpLockForceClose exists -> Double-click on it OR
22 DataFlex for DOS/UNIX/Win32
Select it, then pull down "Edit" and choose DWORD -> In DWORD Editor, Hex selected, enter the value 1 If it does not exist, pull down Edit -> Add value -> Value name: EnableOpLockForceClose Data type: REG_DWORD OK - > In DWORD Editor, Hex selected, enter the value 1 If Value EnableOpLocks exists -> Double-click it OR Select it, then pull down "Edit" and choose DWORD -> In DWORD Editor, Hex selected, enter the value 0 If it does not exist, pull down Edit -> Add value -> Value name: EnableOpLocks Data type: OK -> In DWORD Editor, Hex selected, enter the value 0 Microsoft Redirectors for a Novell Network When running Windows 95 with Microsoft redirectors for a Novell network, programs that open files read only may not have access to updates to that file made by other users while the program
Installation and Environment Guide 23
REG_DWORD
runs. You can overcome this behavior by having your read-only program perform a write to the file from time to time, which will flush the Windows VCACHE buffer. An alternative that requires no changes to your program code are to edit your Windows SYSTEM.INI file. Search for the [NWREDIR] section, adding it if there is none. Place the line ReadCaching=0. End result: [NWREDIR] ReadCaching=0 NetWare Transaction Tracking System Server-based transaction control permits complete backing-out of an incomplete transaction upon failure of the program or the workstation from which the transaction is being entered. This occurs automatically upon such failure. If this feature is in use, no reindexing should be required after such a failure. In fact, other workstations, even those with incomplete transactions at the time, can continue normal operations through such an event. The DataFlex database driver uses NetWare's Transaction Tracking System to support transaction control at the server. You must use a NetWare shell in order to make use of this feature, and TTS must be enabled in your installation of the shell. The Microsoft drivers for NetWare are not supported; only those from Novell are. Use of this feature entails no special provisions in the source code of the program other than those required for transaction control generally. It is, however, necessary to set the DF_FILE_TRANSACTION attribute of every file involved to DF_FILE_TRANSACTION_SERVER_ATOMIC to use it. This can be done either from your program or with DFADMIN.
Setting a file server-atomic causes the NetWare "transaction flag" to be set on the .DAT, .VLD, and .K## files. When a DataFlex transaction is started, a NetWare TTS transaction start is sent to every NetWare server on which any of these files resides. At the end of the transaction, a TTS transaction end is
24 DataFlex for DOS/UNIX/Win32
sent to the same servers. If a DataFlex transaction exceeds the size limits imposed by your local version of TTS, the network administrator will receive a NetWare error report of it. The DataFlex program itself, however, will function normally, but without TTS protection for such transaction. If you try to delete a TTS flagged file through the operating system, you will receive an error message. You would have to reset the flag with the NetWare FLAG command before deletion. If you perform such manipulations through DataFlex, however, the flag will be reset as necessary to permit the desired operations. If you attempt to set a file to server-atomic that is not on a TTS capable NetWare volume, Error 4288 "File not on TTS volume" will be reported. If a DataFlex program opens a file flagged for TTS that is not on a TTS capable volume, the same error will be reported at that time. Similarly, the same error will be reported if the file is set to SERVER_ATOMIC and the NetWare redirector drivers are not installed.
UNIX Installation
Prior to installing DataFlex, be sure that you have your serial number, registration name, and registration code. You must be logged on as the root user prior to installing DataFlex. Installing from CD-ROM 1. Place the CD in the appropriate drive and type: 2. List the sub-directories and identify the directory containing the DataFlex version for your platform (refer to your DataFlex License). Note: Your CD-ROM must be mounted as a file system before you can use it. Please consult the system
Installation and Environment Guide 25
administrator's guide that came with your system for details. Typically, the CD-ROM is mounted as /cdrom or /CDROM. 3. On the target drive create a new temporary directory and then change (cd) to that directory. This step places all the files into the selected temp directory. 4. Type the following command:
tar -xvf filename substitute the filename with the CD-ROM file name (as described in step 2). Below is a typical example command line for AIX. tar -xvf /CDROM/products/df32/aix/df32aix.tar
In some systems, the file names may appear with a semicolon (;) and a number appended to it. In this case, enclose the filename in quotes, as displayed in the example below. Tar -xvf "/CDROM/products/df32/aix/df32aix.tar;1" Installation, Registration, and Setup Use the Bourne or Korn shell, not the 'C' shell. The Install procedure aborts if it detects insufficient disk space unless you use the -c option. If the drive onto which you are installing has more than 2 Gigabytes of space, use this option to keep the procedure from aborting erroneously. Using this option, however, does not guarantee that an interrupted installation can be completed without starting over. You can specify both options (the order of the commands is irrelevant.)
./Install [- [d] [c] ]
Where devicename is that supplied by the manufacturer of the drive or your operating system for the drive you are using. The installation program will ask you to enter the directory where the DataFlex system should be installed, offering the default of /usr/local/df32. If the directory used contains an existing DataFlex 3.x installation, the installation of DataFlex 3.2 is completed without
26 DataFlex for DOS/UNIX/Win32
overwriting the existing menu.*, query.*, flexerrs.*, and *.cfg files. If the directory contains a previous revision of DataFlex, a warning against overwriting a previous revision is displayed. If this warning is overridden, a directory named backup is created under df31d/usr and the existing menu.*, query.*, flexerrs.*, and *.cfg files are copied into it before they are overwritten in their original location along with all the other existing DataFlex system files. The installation shell script should adequately guide you through the rest of the installation. New installation only: Once the installation process has finished, the installation program will automatically execute the Setup Utility (dfsetup). Proceed to register your DataFlex license. Do not exit DFSetup without fully registering your license. Change the current directory to /df32/usr. Execute the setpath script by typing
. ./setpath
Note:
This script sets the value of the DFPATH environment variable. DFPATH (and the other DataFlex environment variables) can alternatively be set by means of a text file, described in the documentation, named DFENV.CFG. This alternative was created to deal with limitations to which UNIX is not subject. If you do choose to use DFENV.CFG, you must set an environment variable called DFENV to the directory path in which the file resides (df32/usr by default from the install procedure). For example, your DFENV.CFG could contain: DFPATH= .:/usr/local/df32/bin:/usr/local/df32/usr The example below assumes that the files are located in the default directory, substitute the default directory with the installed directory name.
DFENV= /usr/local/df32/usr Installation and Environment Guide 27
export DFENV
At this point, DataFlex can be run, but modification of its terminal information (described in Modifying Terminal Information) may be required for full keyboard functionality on your terminals. Modifying Terminal Information If you are not modifying the terminfo entry, refer to Section 2.1 of the DataFlex UNIX System Administrator's Guide for specific information on your terminal. If you want to modify an existing terminal entry or create a new one, see Section 2.2. You can change the directory in which DataFlex searches for your terminal entries by changing the DataFlex DFTERMINFO environment variable (i.e.DFTERMINFO=/usr/lib/terminal would force DataFlex to search that directory for the appropriate terminal entry).
28
Release Notes
Be sure to read the various readme files for the newer revisions of DataFlex. They contain important information on program, feature, and command changes and additions. They are supplied on disk and may be read in the same manner as the rest of the on-line documentation.
may choose to open the file here, or select File from the Main Menu; both methods are valid. The documentation files are: DF32.PDF This document contains the DataFlex 3.2 Installation and Environment Guide. 3.2_Language_Changes This document contains information on the changes in the DataFlex language when using the new Data Dictionary capabilities of DataFlex 3.2. Using_DDOs_in_3.2.PDF This document contains instructions on how to invoke the use of the new Data Dictionary capabilities of DataFlex 3.2. Data_Dictionary_Guide.PDF This document contains the complete reference information on Data Dictionaries and their use. 3.2_on_WinNT_and_2000.PDF This document contains important information about the requirements and limitations of using the DOS components of DataFlex 3.2 on Windows NT and 2000. 3.2_Fixed_Bug_List.pdf This document contains the list of bugs that were fixed in DataFlex 3.2. Updating_to_3.01.pdf This document contains important information on upgrading applications to DataFlex 3.01 from DataFlex 3.0. Updating_to_3.05.pdf This document contains important information on upgrading applications to DataFlex 3.05 from DataFlex 3.01.
31
Updating_to_3.1.pdf This document contains important information on upgrading applications to DataFlex 3.1 from DataFlex 3.05. Developing_Applications.pdf This document contains the Developing Applications with DataFlex manual. User_Guide.pdf This document contains the DataFlex 3 User's Guide. Class_Reference.pdf This document contains the DataFlex 3 UIMS Reference. UIMS_Handbook.pdf This document contains the DataFlex 3 UIMS Handbook. Command_Reference.pdf This document contains the DataFlex 3 Encyclopedia. 3.1_ReadMe.pdf This document contains important release notes from DataFlex 3.1. 3.1c_ReadMe.pdf This document contains important release notes from DataFlex 3.1c. 3.1d_ReadMe.pdf This document contains important release notes from DataFlex 3.1d.
32
33
state what was wrong with the original feature and why your suggestion is better. This first point is very important. You may discover a valid failing in a feature, which needs attention, but your suggested correction may be inappropriate for technical reasons. You can report bugs and suggestions from the Support section of our Web site: http://www.dataaccess.com/support
35
International customers should contact their local distributor or Data Access subsidiary for support (our web site: http://www.dataaccess.com, lists contact information for worldwide distributors and subsidiaries). Our hours of operation are 10:00 AM - 5:30 PM EST MondayFriday. Have your product information, serial number, and SupportNet contract number available. Give a complete concise account of the trouble you are experiencing and try to be at the machine with the problem so that our support representatives can work with you to resolve the problem.
Where to write to us
support@dataaccess.com Data Access Corporation 14000 SW 119 Avenue Miami, FL 33186
Where to FAX us
305.238.0017
37