™ GENEXUS
Installation Manual
Copyright Ó ARTech Consultores 1988-1999. All rights reserved.
Table of Contents
INTRODUCTION ...... 1
A NOTE FOR ALL GENEXUS USERS ...... 2
GENEXUS TUTORIAL...... 2
GETTING STARTED...... 3
SETUP OPTIONS ...... 3 SHOULD I KEEP MY EARLIER GENEXUS VERSIONS? ...... 4 CONVERTING GENEXUS APPLICATIONS FROM DOS TO WINDOWS ...... 4 What files can be deleted once the conversion has been carried out? ...... 6 CONVERTING MODELS FROM PRIOR GENEXUS FOR WINDOWS VERSIONS TO GENEXUS VERSION 6 EVOLUTION 1 ...... 7 COPY PROTECTION SCHEME...... 7 REQUIREMENTS ...... 11
GENEXUS STAND-ALONE SETUP ...... 13
USING GENEXUS AUTHORIZER ...... 20 Information...... 21 Authorize ...... 21 Authorizing Generators...... 23 Direct Transfer...... 23 Uninstall...... 24 GENEXUS Authorizer Log ...... 24 Remote License Transfer ...... 24 Sharing one License between Two Different Sites...... 26
STARTING GENEXUS ...... 28
GENEXUS NETWORK SETUP...... 30
AUTHORIZING GENEXUS ON A "SHARED INSTALLATION" ...... 31 NOVELL NETWARE NETWORKS ...... 32 Configuration Requirements ...... 33 License Related Issues...... 34 WINDOWS NT NETWORKS ...... 35 Manual Installation of the License Driver ...... 36 Configuration Program...... 37 GENEXUS installed on a Windows NT Server ...... 39 Uninstalling...... 39 Windows NT Known Problems...... 40 GENEXUS NETWORK WORKSTATION SETUP ...... 40 TIPS AND LICENSE ERROR MESSAGES ...... 43
INSTALLATION AND CONFIGURATION TIPS ...... 43 Changing the Workstation's Date...... 43 Synchronizing Workstations Time and Date ...... 43 How to re-authorize a site in case the date of the license is incorrect ...... 44 New Site Codes...... 45 CKSERVE and CKSERVER ...... 45 COMMON LICENSE ERROR MESSAGES ...... 45 Error Messages when entering a New Site Key...... 45 Error Messages when querying the License:...... 45
GENEXUS AS/400 LIBRARY INSTALLATION...... 47
ABOUT THE INSTALLATION IF VERSION 2.2 IS USED ...... 47 REQUIREMENTS...... 48 NORMAL INSTALLATION PROCESS FOR VERSION 2.2 ...... 48 ABOUT THE INSTALLATION FOR VERSION 2.3 AND HIGHER...... 50 PROBLEMS INSTALLING GENEXUS FOR WINDOWS LIBRARY...... 53 ERROR DESCRIPTION AND RECOVERY PROCEDURES...... 54 List of Errors ...... 54 INSTALLING A PATCH ...... 57
INTRODUCTION...... 57 INSTALLING A PATCH ...... 57 WHICH WAS THE LAST PATCH RELEASE I INSTALLED?...... 59 DIFFERENCES BETWEEN PATCHES ...... 59 USER NOTES...... 62
INDEX...... 64
0 Introduction
INTRODUCTION
This manual provides all the information you need to know about how to install GENEXUS. You will first come across a "Getting Started" section which briefs you on a few very important points worth knowing before you actually install/setup GENEXUS. You may also go over the minimum requirements needed to successfully install and run GENEXUS in your working environment by referring to the "Requirements" section. If your target environment is a stand-alone computer then you can turn to the specific setup option that directly interests you. If you are a network administrator, you will find information on how to setup GENEXUS on a shared directory or a network file server, under the "GENEXUS Network Setup" section. There is also a specific section covering "GENEXUS Network Workstation Setup". Before running your installed version of GENEXUS you will have to authorize it. The authorizing process is explained in detail under the section titled "Using GENEXUS Authorizer". Users who make use of a particular generator will need to follow the setup instructions and check in the list of generators that require authorization to see if the generator they have chosen to use need to be authorized. When you request site keys from your distributors it is compulsory that you fill-in the 'Request License Authorization Form'. This form is included with every purchase of GENEXUS. Do not forget to read the section titled "Tips and License Error Messages" because it surely broadens your knowledge and helps you avoid nasty errors. There is also a section that covers "GENEXUS AS/400 Library Installation" for those users who are using RPG/400 or COBOL/400 generators.
We have also included a section that explains how to Install GENEXUS Patches. This has been incorporated to the manual as it, in itself, is an entire installation process.
1 Installation Manual
COPYRIGHT Ó ARTech 1988 - 1999. All rights reserved. This document may not be duplicated in any way without the expressed written consent of ARTech Consultores S.R.L.. The information contained herein is for the personal use of the reader.
TRADEMARKS All product names mentioned in this document are the trademarks of their respective holders.
A NOTE FOR ALL GENEXUS USERS
We strongly recommend that you do not install this GENEXUS version over any prior GENEXUS version. It is good practice to keep your prior version untouched until you are satisfied that your applications run as desired on the newer version. Not only do we suggest that you back up your older GENEXUS versions but also your applications.
GENEXUS TUTORIAL
A Tutorial on a Sales Application is included with GENEXUS and is automatically installed in the SAMPLES subdirectory of the directory where GENEXUS was installed. It is contained in a compressed file called SALESZIP.EXE. To decompress it you must be positioned over the samples subdirectory and execute the SALES.BAT program. Once decompressed it occupies less than 3 MB of disk space. If you have limited disk space, you may want to delete this file or the uncompressed application after completing the tutorial lessons. The Tutorial Manual will guide you through the steps taken to build the Tutorial Sales Application.
2 Getting Started
GETTING STARTED
This section briefly discusses the several setup options that can be performed, it suggests you backup your old version, explains the copy protection scheme being used and informs you of the distribution of a Tutorial available with every purchased license. Setup Options
There are three different options used to set up GENEXUS. The option you choose depends on your needs which in turn determines the type of license you will solicit from your GENEXUS Distributor:
· Stand-alone Setup: This option is a local installation and it may only be used on a fixed site. So, GENEXUS is run without the need of any network connection. If this is the type of installation you require then you will need to request for a license enabling a "stand-alone" installation, denominated as a "fixed license".
· Network Setup: This option will install GENEXUS on a shared directory or on a network file server achieving a "shared installation" of GENEXUS. A "shared installation" can be used locally or remotely by more than one network workstation at a time. After executing the network workstation setup (see below), you will be able to run GENEXUS on any workstation that is properly connected to the "shared installation". If this is the type of installation you require then you will need to request for a license enabling a "network" installation, denominated as a "floating license". This means, the same license can be used by different workstations. The only restriction is: if you purchase "n" network licenses then the maximum number of users that can simultaneously work with GENEXUS on a network is n.
· Network Workstation Setup: This option modifies your network workstation system in order to run GENEXUS from a "shared installation". A "shared installation" (see above) will only be achieved if you have included the “workstation setup” component on your server before installing GENEXUS. Please check this with your network administrator or with the person in charge of these types of installations.
Two clear advantages will be experienced when you combine the second and third setup options correctly: your local disk space will not be affected by the installation of GENEXUS programs and the network workstation setup will be quick because there is no need to copy all the files again from installation diskettes.
3 Installation Manual
Another advantage regards the maintenance of GENEXUS versions, the execution of upgrades or the application of patches because you will only have to carry it out on the "shared installation" site and not on all your workstation sites. There are two disadvantages: GENEXUS may run a little slower for some operations and if the network server or shared directory becomes unavailable you will not be able to run GENEXUS at all. Important: Every GENEXUS user must have a GENEXUS license. You receive a license when you buy GENEXUS. The installation you require will determine the kind of license you will purchase. Consult your network administrator in case you already have performed a network workstation setup.
Should I keep my earlier GENEXUS versions?
If you modify applications created by older GENEXUS versions with a newer version be sure you back them up beforehand. If you maintain an application which is shared by users who have not yet upgraded to the newer version then you will still need your previous version to perform the necessary modifications. You can use a newer GENEXUS version to work with applications created by previous GENEXUS versions.
Converting GENEXUS Applications from DOS to Windows
The conversion procedure will be carried out in two very different steps.
The first step needs to be executed at the DOS command prompt line and the final step must be executed under GENEXUS Windows.
STEP 1:
To perform the conversion the following command must be executed in DOS mode:
TOGXW
where:
for example:
D:\GXW\TOGXW D:\GXW
4 Getting Started
Note: When executing this command you must be positioned over the directory with the model you will convert. For example:
C:\GXDOS>D:\GXW\TOGXW D:\GXW
STEP 2:
Once the model is opened by GENEXUS Windows you will come across the Knowledge Base Conversion Wizard.
The Knowledge Base Conversion Wizard consists of 6 steps in its own right. Six quick steps that ease the task of converting applications from GENEXUS DOS to GENEXUS Windows.
Steps 2 through to 5 are steps that let you establish the following:
· the modes (graphic or text) you wish to convert your reports and procedures to. · the modes (graphic, text or both) you wish to convert your transactions and work panels to.
5 Installation Manual
· if you select "graphic" or "both" mode in the previous step for transactions and work panels you will be asked how you wish the buttons and toolbars to be arranged on your graphic forms. You also will be asked to select the desired fonts for labels and attributes.
· the final step informs the user that the conversion process will take some time, the time it takes depends on the size of the model that will be converted. The conversion of the Knowledge base will consider the options selected in the previous steps.
NOTE: Graphic characters like lines, frames, etc. are converted to hyphens, dashes, etc. What files can be deleted once the conversion has been carried out?
*.GX (except for the CONFIG.GX)
The CONFIG.GX file is not converted. You must manually set Model Preferences to achieve the same effect indicated by CONFIG.GX. You must never delete CONFIG.GX if it stores generator configuration information.
Directory GXDOS001 is created from the old DOS GXMDL001 directory.
This directory is quite large because it contains all screens/rules/events etc. of the model that will be converted and it is this information that is converted. During the conversion there may be objects that trigger conversion errors and you have the opportunity to convert them later.
Note: this directory will be renamed once the conversion process has completed, except, if for some reason, the process cancels.
The files *.SP2, *.SP5 and *.SP7 that are in the Model Directory (if the environment variable DOS GXUSER = ... is not used) must be moved to their corresponding directories:
*.SP2 must be moved to directory GXSPC251\GEN
6 Getting Started
where
Converting Models from prior GENEXUS for Windows versions to GENEXUS version 6 evolution 1
If you open a model originally designed with a prior GENEXUS Windows version with version 6 evolution 1 a dialog is displayed where you are asked if you want to convert the Knowledge Base to version 6 evolution 1. If you click the OK button another window is opened displaying the rebuild of the knowledge base.
Converting the knowledge base has an advantage, the converted knowledge base will occupy less space than the original one (sometimes a 30% increase in disk space is noted).
ATTENTION: version 6 evolution 1 is not backward compatible, that is, if you try to open a Knowledge Base that operates under version 6 evolution 1 with a GENEXUS Windows version prior to this one you will come across a c-tree error message similar to “Error #52 in file #46”.
IMPORTANT: Whether you are a new GENEXUS user or not you must authorize your GENEXUS product. Refer to the section called 'Using GENEXUS Authorizer' for more details. Copy Protection Scheme
There are two kinds of licenses for running GENEXUS:
· Fixed license (mono-user) copies can only be used by the computer on which they have been installed. Licenses can be transferred to other computers if more than one copy is purchased but only those computers that have received a transferred fixed license will be able to run GENEXUS. Example: If you have purchased 5 fixed license copies, 4 of them could be distributed via transfer functions to the other 4 computers. So in the end you will have 5 computers each of them with 1 fixed license copy. (Refer to the 'Remote License Transfer' section for more information on transferring fixed license copies).
7 Installation Manual
· Floating licenses (multi-user) allow a certain number of users to run GENEXUS concurrently from a single "shared installation". Example: if you have purchased a floating license for 5 users that resides on a "shared installation" then there will be up to 5 workstations connected to it and running GENEXUS simultaneously.
8 Getting Started
9
Requirements
REQUIREMENTS
Below is a list of the minimum requirements you will need in order to run GENEXUS:
· An IBM compatible personal computer, with an 80486 or higher microprocessor · 24 megabytes of RAM (64 is recommended). · A hard disk with at least 14 megabytes of free space is required for a stand-alone installation plus an average of 1.5 megabytes for each generator you choose to install. If installing on a network file server you will need 26 megabytes of free space to install GENEXUS development environment plus an average of 2 megabytes for each generator you wish to install and if a network workstation installation is to be carried out you will need 5 megabytes of free space since the necessary dlls are copied to \windows\system permitting the execution of GENEXUS development environment and generators. In all cases you will require additional hard disk space or a shared drive to be able to create GENEXUS applications. You must also consider the extra space you will require for interpreters/compilers. NOTE: The space required by each generator you have chosen to install depends on the generator that is why we have given you an average approximation. · A mouse or other compatible pointing devices. · An EGA, VGA or compatible display (VGA or higher recommended). · Microsoft Windows 95/98 or Microsoft Windows NT. · A Target Language Interpreter/Compiler for prototype and/or production execution. This depends on which generators have been purchased: FoxPro for Windows, Visual FoxPro, Visual Basic, RPG, etc.
11 Installation Manual
12 Stand-Alone Installation
GENEXUS STAND-ALONE SETUP
This section explains how to use the Setup program to install GENEXUS on a stand- alone computer as described in the "Setup Options" section. Once you have met up with all the necessary requirements to install GENEXUS follow the instructions specified below. The Setup program includes a wizard to help you make the correct choices.
How to start the GENEXUS Stand-alone Setup program:
1. Start Windows. 2. Insert the CD-ROM in the CD player. 3. Follow the Setup Wizard instructions to install the selected products (Development Environment, Generators, etc.). Important: from version 6 evolution 1 there is a new Setup program that lets you select the products you want to install, there is no need to execute a different installation for each generator. The following section explains how the Setup Wizard works.
Setup Wizard
The first screen you will come across is the setup wizard greeting display, click over the next button if you wish to continue with the installation. Then you will displayed another with a list of recommendations if you wish to continue with the installation click over the next button. The next dialog asks you to register your name and the name of the company your working at. Once you have entered that information press next to come across the following:
13 Installation Manual
In this dialog you must choose the type of setup you wish to perform, the options are:
· Typical: the most common options are installed (Development Environment, Samples Files, Workstation Setup and Visual Basic generator).
· Compact: only the minimum required options are installed (Workstation Setup and Samples Files are not installed).
· Custom: you may choose the products you want to install. If you select this option the following dialog will be displayed and you must select the components you want to install:
14 Stand-Alone Installation
Once you have selected the type of setup you want to perform you will be asked to enter the name of the program folder where you will include GENEXUS (a folder named “GeneXus 6 evolution 1” is suggested). You may choose any existing folder or create a new one.
Then a window is displayed showing all the previous selected options, if the user confirms these options the installation process begins and the program files are copied.
Visual Basic Generator The setup wizard looks for the installed version of Visual basic in the machine and displays the following window:
15 Installation Manual
The check boxes will be marked according to what was found in the machine but you may change it. The necessary files will be copied and register for the Visual Basic version(s) selected.
What happens if I already have an old GENEXUS installation?
Below we detail a very common situation, "what happens if I already have an old GENEXUS installation?". The information we have provided will require the user (installer) to take a decision that best suites his/her situation:
16 Stand-Alone Installation
Destination Directory:
You may have been developing your application with a prior GENEXUS version installation as for example, a version installed on directory c:\gxw. If we decide to use it as our target directory for the installation process then we will encounter the following difficulties:
· The installation program will override all files in the target directory. If by any chance the installation process were to fail (it had not completed) then the target directory will have a mixture of old and new files and this is not desirable.
On the other hand, all files that are no longer installed by the new version or they are installed in other directories, will reside forever as rubbish in the target directory. The installation process does not delete all files belonging to prior versions.
· The registration of the specifier and generators, only when Windows NT is used is carried out in absolute form (meaning the entire path is specified) and not relatively as in Windows 95. This means that the actual registration executed by the setup process and stored in registry files (stored in your windows directory) actually overrides the information that was previously stored there, therefore the prior version of GENEXUS will cease to operate correctly.
To avoid these problems we recommend you assign a new directory as the target directory for your installation, for example, c:\gxw61. This measure keeps your old version in the same working order but it does not apply if you are running under Windows NT, in this case you can only have one installed and operating GENEXUS version on each computer. How can this restriction be overcome if I make use of a network, install all my GENEXUS versions on the server and all my workstations operate under Windows NT? You can not as we have explained immediately above, so you will only be able to execute the last GENEXUS version from the server after having executed the corresponding workstation setup. Once you have used your new version after the installation was successfully carried out and you are sure it works without any problems you may delete your old version, this frees more disk space as it removes obsolete files. Attention: before you delete the directory containing the old version first make sure it does not have a license otherwise you will loose it. Refer to the section discussing "Using GENEXUS Authorizer" for more information.
17 Installation Manual
If the Setup program must modify a file that is currently in use then a message will be displayed indicating this situation, it will also ask you to close all programs in order to continue with the setup.
Once all the files you need have been copied to your system, the Setup program places GENEXUS icons in a GENEXUS group that will be automatically incorporated to your Program Manager's window. You can use the same diskettes and run Setup at any other time to install it on other computers.
Important: In order to be able to run GENEXUS from a local hard disk it is necessary to authorize it. For instructions on how to do this read "Using GENEXUS Authorizer".
18 Stand-Alone Installation
19 Installation Manual
USING GENEXUS AUTHORIZER
IMPORTANT: Whether you are a new GENEXUS user or not you must authorize your GENEXUS product (development environment and generators).
Once you have finished installing any GENEXUS product that needs authorization you must execute GENEXUS Authorizer to obtain the rights to use the products.
To execute this program you must select the icon named GENEXUS Authorizer from GENEXUS group window in your Program Manager or Run GXAUTHOR.EXE that is located in the directory where GENEXUS has been installed.
In case you have performed a network workstation setup you will not have such an icon because it is the network administrator's responsibility to perform the authorization.
A similar GENEXUS Authorizer dialog as displayed below will be displayed:
20 Authorizer
GENEXUS Authorizer is an external program that lets you select one or several programs, such as: Information
Displays the selected program's actual License information. It also includes information concerning the number of fixed license copies (mono-user) and the number of network users that have been authorized. The date and time the authorization was carried out will be displayed, as well as possible license restrictions. These restrictions can either be a time restriction (days) or number of program executions (runs) restriction. Authorize
This option will actually authorize your license. Please read it very carefully. If you select the Authorize option and the site has already been authorized then the following message is displayed:
If you enter a new valid Site Code you will lose this site's actual License. Are you sure you want to continue ?
If your intention is to reauthorize the site or just get a new Site Code then select "Yes" in any other case select "No". The message indicates the possible loss of a previous license only if you enter a new valid Site Key. A valid Site Key is any correct key entry, that is, its CRC checks out to be okay. This does not mean a valid Site Key will enable you to use GENEXUS.
You will need to confirm the system's date and time:
Current System date : 98-10-10 15:50:20 Please check the system date and modify it if necessary. Any changes made to it after authorization takes place may withdraw your license. Are you sure you want to continue ?
In case you are not sure about the date please answer "No" and correct it before trying again. The date and time of the license will depend on the settings of the PC that carries out the authorization. It is because of this that you should synchronize your PC's date and time with that of the Server (if you happen to make use of one) or all other PCs (in case no server is used).
Refer to the section discussing "Changing the Workstation's Date".
21 Installation Manual
Once you have established the system date the actual selected program's Site Code is displayed. If this program is yet to be authorized or you wish to change the type of authorization you must transmit the Site Code to your distributor. In return, you will receive the necessary Site Key that will authorize the selected program. If the Site Key is accepted the program will be authorized and you will be informed of the number of licenses and restrictions your distributor imposed when this Site Key was generated.
Note: Be sure you transmit your Site Code to your distributor BEFORE your license period expires, this precaution avoids problems you may have if the license expires because you will have your new Site Key at hand before it actually does expire. To do so, select the Authorize option in order to obtain a new site code, ignore the message that warns you about the loss of your current license and the messages on system date synchronization. After copying the code select cancel.
As licenses can either be fixed or floating type licenses, you will need to notify your distributor of the type of license you will require. Look for a file called license.txt in your GENEXUS CD-ROM. This file, when opened, displays the Request License Authorization Form, it is a fill-in form ensuring you provide your distributor with the necessary information and thus guarantee the correct site key authorization.
You should not transfer a fixed license installation (Network Users Allowed=0) to a floating license installation because YOU WILL LOSE YOUR LICENSE.
Is the Authorization affected by disk compression and defragmentation programs such as DriveSpace or Norton Utilities Speed Disk? The authorization is generally immune to these sorts of programs. However, in the case of Speed Disk, steps must be taken in order to ensure that the authorizer licensing files remain unaffected. The Authorizer uses three special files GXW.ENT, GXW.KEY, GXW.RST in order to control the licensing of your product. These files are declared as hidden system files and reside in the same directory as the protected application, GXW.EXE. So, in the case of Norton Utilities you will open Speed Disk and choose File/Options/Customize/Unmovable Files. Specify that *.ENT, *.KEY, *.RST files cannot be moved and then Speed Disk can be run without having any effect on Authorizer licensing. Remember to do a File/Options/Optimization/Save in order to save the new profile.
In case these protection files are deleted or physically moved the authorization will be lost.
22 Authorizer
IMPORTANT
Only if you have a local installation of GENEXUS, lets say on your C drive, will you be able to rename the directory containing the authorized programs but you cannot copy them to another directory without also transferring the license. Do not move protected files to a new directory unless you are sure that the method you choose to use does not physically move the files (by copying and deleting).
For example, if GENEXUS is installed on c:\gxw\ you could MOVE the directory to c:\tools\gxw\
Points which should be kept in mind: · You should not, under any circumstance, rename the directory containing a GENEXUS installation on a NOVELL or Windows NT Server Disk ! Authorizing Generators
GENEXUS requires the authorization of certain generators. This means that when you enter the authorizer to authorize GENEXUS you will also be displayed the list of generators that need to be authorized, that is, the list of generators you have installed and that require authorization. The authorization process used to authorize GENEXUS is the same one used to authorize generators. Direct Transfer
GENEXUS Authorizer lets you transfer licenses from one site to another via the Direct Transfer option.
This option may be used when multiple fixed license copies have been purchased, hence they can be distributed between different installations.
This transfer licenses method does not copy programs all it does is transfer licenses from one site to another, note: the target site must store an identical copy of the program. So, both source and target directories must store a copy of the program but only the source directory can be authorized. You will not be able to transfer a license to a program that has already been authorized.
Direct Transfer can only be used if the source directory and the target directory are located on the same computer or are on the same network. It will let you transfer licenses to any local directory. If the target happens to be a network directory then
23 Installation Manual
make sure that you have installed the necessary driver on the server's target disk. For more information read Authorizing GENEXUS on a "Shared Installation".
You should not transfer a fixed license installation (Network Users Allowed=0) to a floating license installation because YOU WILL LOSE YOUR LICENSE.
Another way to transfer a license is to use the Remote License Transfer option that we have detailed below. Uninstall
You may uninstall any of the previously installed and authorized products (development environment or generators). Once you have selected the product you want to uninstall the following message will appear:
If you continue you will lose this site’s actual license. Are you sure you want to continue?
If you confirm the action, the confirmation code for the selected license is displayed. You must send this code to your GENEXUS dealer. GENEXUS Authorizer Log
GENEXUS authorizer saves a file called KEY.LOG for each product (development and generators) that was authorized. The purpose is to keep a history of the authorizations executed for each product. What the authorization does is save the Site Code before it is authorized and once authorized it also saves the Site Key. If license upgrades are executed then newer data will be added to the log file. If you uninstall a license, the code generated by this process is also saved by KEY.LOG. If you authorize a product that was not authorized (either because it did not require authorization or because you lost it) the contents of the KEY.LOG file vanishes and the whole process of recording authorizations starts again. The KEY.LOG file is stored in GENEXUS’ directory (when authorizing development) and in each directory corresponding to generators requiring authorizations. Remote License Transfer
This method is used to transfer a license via floppy disks. It does not copy installation programs, all it does is transfer the license from one site to an other that already has an identical copy of the necessary programs. You must follow the three basic steps we have detailed below but first take a look at the table
24 Authorizer indicating whether or not all remote license transfers are possible.
Transferring license from Transfer Receiving transferred license Any version prior to 5.5 Not possible Version 6 evolution 1 Version 6 evolution 1 Not possible Any version prior to 5.5 Version 5.5 Not possible Version 6 evolution 1 Version 6 evolution 1 Successful Version 5.5 Version 5.6 Successful Version 6 evolution 1 Version 6.0 Successful Version 6 evolution 1 Version 6 evolution 1 Successful Version 5.6 Version 6 evolution 1 Successful Version 6.0
You should not transfer a fixed license installation (Network Users Allowed=0) to a floating license installation because YOU WILL LOSE YOUR LICENSE.
Register Transfer
Execute GENEXUS Authorizer over the target directory (i.e. where you want to install the license). Select the program for example GENEXUS and choose the Register Transfer option. Insert the diskette, enter the path as solicited by the dialog for example A: and press Enter. If everything proceeds normally a message will be displayed indicating that the transfer has been correctly registered.
Remove the diskette from the target computer and insert it in the source computer. Transfer Out
Execute GENEXUS Authorizer over the source directory containing the authorized program. Select the program and choose the Transfer Out option. After having inserted the diskette used in the previous step enter the path as solicited by the dialog and press Enter. If everything proceeds normally a message will be displayed indicating that the license has been correctly transferred to the diskette. This process will withdraw the license from the source computer and if there happens to be more than one fixed license copy then the number indicating the number of copies will be decreased by one.
Remove the diskette and insert it again in the target computer.
25 Installation Manual
Transfer In
Execute GENEXUS Authorizer over the target directory select the program that will accept the transfer and choose the Transfer In option after having inserted the diskette used in the two previous steps. Enter the path solicited by the dialog and press Enter. If everything proceeds normally a message will be displayed indicating that the license was successfully transferred.
NOTE: if your license stipulates the possibility of three users working on a network simultaneously and you transfer this license to a PC's local disk, what you are actually doing is transferring the entire license and not just the user's license. Meaning the network has no record of any license and the PC has a license for three users. This license can be used by other PCs if the DOS or Windows network driver is loaded onto the PC; this will depend on whether the PC executes DOS or not. Sharing one License between Two Different Sites
Supposing you wish to work at home and at work with just one license (just supposing, of course!), meaning, you want to be able to carry the license around with you depending on your needs. Then, you will have to follow the steps specified below making sure you have two diskettes clearly labeled as for example, Disk 1 and Disk 2:
1. Install GENEXUS at work. 2. Authorize it at work. 3. Install GENEXUS at home. 4. Execute a Register Transfer with Disk 2 at home.
Everything at this point has been installed but you will only be able to run GENEXUS at work.
Now you want to be able to work at home.
5. While at work you will have to execute a Transfer Out onto Disk 2 (the license is now on Disk 2) 6. After this, while you are still at work, execute a Register Transfer with Disk 1. 7. Go home (this shouldn’t have to be too difficult). 8. When at home use Disk 2 to perform a Transfer In. 9. You are now able to work at home (and we consider you very brave!).
Returning the license back to work.
26 Authorizer
10. While you are still at home execute a Transfer Out onto Disk 1 (the license is now on Disk 1). 11. After this, while you are still at home, execute a Register Transfer with Disk 2. 12. Go to work. (Sorry, if that sounds too harsh!) 13. Once you’re at work use Disk 1 to perform a Transfer In. 14. You are now able to work at your work site.
The idea is quite simple: make sure you have prepared a diskette (i.e. Register Transfer has been executed onto it) for the place where you wish to work at since it avoids having to take two extra trips to achieve the same goal. You have to be consistent and not forget to execute a Register Transfer each time a Transfer Out is executed, this ensures you that you will always have a pocket license (on a diskette) for your work site.
NOTE: The same steps can be taken if you transfer generator authorizations (if the generator you use needs to be authorized).
27 Installation Manual
STARTING GENEXUS
Before you start GENEXUS you must have it authorized. Refer to Using GENEXUS Authorizer for more information on this point. An opened GENEXUS group with its icons is displayed after a successful GENEXUS Setup was carried out (as shown below).
You can start GENEXUS with either a click of the mouse or pressing ENTER.
Note: To start GENEXUS that has been setup to run from a network server connect to the network drive where GENEXUS has been installed before performing the following procedures.
28 Starting GENEXUS
29 Installation Manual
GENEXUS NETWORK SETUP
This option is for network administrators who will perform a "shared installation" on a shared directory or a network file server. Users on networks can share the GENEXUS executable file and files created by GENEXUS. Once you have installed GENEXUS on a shared directory or a network file server, a workstation user performs a Network Workstation Setup to run GENEXUS from the "shared installation".
Below is the list of possible systems on which you could have a "shared installation" of GENEXUS :
· NOVELL 3.x and 4.x servers · Windows NT servers
Note: A Windows NT server can also be a PC with the Workstation version of Windows NT operating system emulating as a GENEXUS file server, you are not required to use the actual server version of Windows NT.
Before you run GENEXUS Network Setup program check the following:
· The network must be operational and you must have read, write and delete privileges on the network directory where you will install GENEXUS and on the Windows System directory. For more information refer to your network software documentation. · Check if you have enough hard disk space. Refer to the 'Requirements' section at the beginning of this manual for details. The setup process will let you know if you do not have enough hard disk space. · You must install Microsoft Windows or similar as described in Requirements on the workstation where GENEXUS will be installed (from the network file server) and on all other workstations that will run GENEXUS. · You should determine on which network file server directory GENEXUS will be installed. The setup process will suggest that GENEXUS be installed in directory GXW61. If you want you can specify another path.
The setup procedure that installs GENEXUS on a network file server or a shared directory is similar to the one used by GENEXUS Stand-Alone Setup procedure but you must remember to select the option “Workstation Setup” from the corresponding dialog. After GENEXUS has been installed on a shared directory or a network file server where you must have included the Workstation Setup option, you can install GENEXUS on a network workstation. To do so execute the program setup.exe located in a sub-
30 Network Setup directory called nsetup created under the directory where GENEXUS was installed (refer to the section “GENEXUS network workstation setup”). Important: before running the program setup.exe you must create a map to the network drive where GENEXUS was installed. Once the installation process has completed you will have to authorize GENEXUS before running it. Refer to Authorizing GENEXUS on 'Shared Installation' below.
Note: As the design process involves permanent file creations/modifications, the designers must have the appropriate rights over model directories.
Authorizing GENEXUS on a "Shared Installation"
There are some considerations that must be taken into account before you follow the instructions on how to authorize GENEXUS and generators. You will need to load the corresponding driver onto the network server containing a protected program such as GENEXUS before you authorize it. This driver or "license server" is a program that runs in background on the server as well as handles floating licenses. Once this driver is running the licensing system will be able to operate on the server and authorize the protected program. The driver is located in the LANSRV\target_platform subdirectory of the network server or shared directory where GENEXUS has been setup.
Important: The server must grant READ and WRITE permissions to its clients on the directory where the protected software will reside. If the WRITE permission is NOT GRANTED ALL NETWORK ACCESS REQUESTS WILL BE DENIED.
You must not rename the GENEXUS network directory (whether it be NOVELL or Windows NT) once your GENEXUS version has been authorized.
You must never transfer a local license to a NOVELL or Windows NT server unless it is a (floating) network license because it is not possible to transfer the license back to a local disk.
At present there are 4 license servers for 4 different platforms. Below is a description of the files each one of these platforms need. These files are located in the LANSRV\target_platform subdirectory hanging from the directory where GENEXUS was installed.
31 Installation Manual
NOVELL Netware Networks
The following is a list of supported server versions:
1. NOVELL 3.x 2. NOVELL 4.x
The CKSERVER.NLM is used for NetWare 3.x or 4.x servers. CKSERVER.NLM must be given READ, WRITE and FILESCAN permissions for the server machine it will be servicing. CKSERVER.NLM can only service the local file server that it is installed on and this includes the SYS volume and all other volumes on the server. CKSERVER.NLM is self-configuring and will detect any protected program on the server it is running on. CKSERVER.NLM does not require any interaction or configuration from the administrator once it has been loaded.
NOTE: CKSERVER.NLM can be referenced in the AUTOEXEC.NCF file for automatic startup when the server is rebooted.
When using CKSERVER.NLM in a NetWare 3.x you must have installed at least the LIBUP5 patch (you can get this from Kenonic or NOVELL).
CKSERVER.NLM will work on any NetWare 3.x or 4.x server.
Other NLMs used by CKSERVER.NLM are included in the LANSVR subdirectory. They are auto-loaded when you load CKSERVER.NLM. In case your system already has NLMs that come with CKSERVER.NLM, we recommend that you try using them first if they don’t match, you will get an error message when loading CKSERVER. If this takes place you should apply a NOVELL Patch to synchronize your NLMs or you could copy the other NLMs that come with CKSERVER.NLM.
The next example assumes that you have a 4.x system:
Example:
Load sys:system/ckserver where sys:system is the directory where the drivers reside (it is recommended that they be copied to a directory where the other NLM's reside).
32 Network Setup
Once you have loaded CKSERVER.NLM onto your system, you will be displayed the following screen:
Loading module CKSERVER.NLM default Version 4.03 December 4, 1997 (C) Copyright 1996 Kenonic Controls, Calgary, Canada
At this point, the License Server is operational and you will be able to use GENEXUS. If you want to unload CKSERVER do it by executing the following from the NOVELL prompt:
Unload ckserver Configuration Requirements
There are some requirements concerning configuration and user rights that must be considered if GENEXUS is to be used with NOVELL Netware. Rights
GENEXUS users must have the following rights over the GENEXUS Installation Directory and its corresponding subdirectories:
· Read · Write · Create · Erase · Modify · File Scan
The design process involves permanent file creations/modifications so designers must have the appropriate rights over model directories. Shareable Files
The files with extensions *.IDB must make use of the Shared attribute. Network Workstation Configuration
The workstations that will execute GENEXUS from a NOVELL server must be connected to it and operate under Windows 95 or Windows NT.
33 Installation Manual
License Related Issues
· We recommend you transfer your license if you are going to update your current NOVELL version, once the upgrade has finalized, have it transferred back again. If you are to change the disk it is obvious that you will also have to execute a transfer.
· You may receive a message stating that there are no available licenses left when you try to load GENEXUS:
GENEXUS is authorized but all licenses are in use! Press OK.
All licenses were in use and when you tried to load it either you were not aware of the situation or GENEXUS was not aware that a user had ceased to work with it. In this last case, it is convenient that you make sure that no-one is executing the particular GENEXUS version you wish to execute and delete the file called gxw._tb located in the same directory were you wish to execute GENEXUS from. By deleting this file you will set the user counter to zero. If there happens to be users who are working with GENEXUS while this file is being deleted they will automatically be registered by GENEXUS as it queries whether they are authorized to work with it. Therefore, in a couple of minutes the active users will be registered and the free token can now be used. If you have decided to delete this file you should wait a few minutes (2 or 3) before trying to enter GENEXUS otherwise GENEXUS may dismiss the current users but not before asking them if they wish to save their work first. In case it does not work then you should try to unload CKSERVER.NLM and reload it again. If this is a frequent occurrence then we recommend you create an icon within the GENEXUS group that is mapped to a DELGXWTB.BAT and deletes file gxw._tb when selected.
· It is convenient that you add the command that loads the License Server to the AUTOEXEC.NCF file, so that it will be executed each time the server is booted. NOVELL Trouble-Shooting
1. "Network Driver appears not to be serving this directory" error message If a user attempts to execute a protected program from a NOVELL server an error similar to the error message shown above will be displayed. Solution: There first two solutions are alternatives depending on the type of network you are working on:
34 Network Setup
1. Check if CKSERVER is running on the NOVELL network.
2. Check if GENEXUS is being executed from within a mapped network drive and not directly from the server's disk (this only applies to network environments). 3. Check if the System User has full access rights over the GENEXUS directory (this applies if Windows NT is used).
2. "Undefined symbol: __CHK" error message The NOVELL CLIB.NLM library is outdated. Referenced library routines cannot be located within the current Network Loadable Module. Solution: Install at least from Patch NOVELL "LB312F.EXE" (Sept/94) on. Note: You cannot just simply unload CLIB.NLM and load it again separately, you must shutdown the Server and restart it (Loads new CLIB.NLM).
3. There are no users logged on to the network executing the protected program but it still displays an error message indicating logged users. Refer to "License Related Issues" for more information on this topic. Solution: Delete the "gxw._TB" file from network or Stop/Start CKSERVER on the Network. Start the program again. Windows NT Networks
Supported versions are Windows NT 3.5 (build 807), Windows NT 3.51 (build 1057) and Windows NT 4.0 on. Both NT Server or NT Workstation act as a files and licenses server.
Installations on computers with Windows NT version 3.1 or lower is not recommended. Nor has it been planned to support these older versions in the future.
License drivers must be installed and configured on each NT computer acting as a GENEXUS server. If not GENEXUS returns an error message -102 (Network Driver appears to not be serving this directory).
CRYPSERV.EXE and CKLDRV.SYS
These are Microsoft Windows NT 3.5x binaries (only Intel binaries are shipped, please contact us regarding other platforms). These two files form a Service/Driver pair for servicing requests. They also are used to service requests from DOS/Windows/Win32
35 Installation Manual programs running locally on Windows NT.
The SETUP program must be executed on the NT server (you must have administrator rights to do so) if you don’t the setup will install GENEXUS but it will not automatically add the Crypkey driver and the user will have to do so manually. You can install GENEXUS on the NT server from a workstation but we do not recommend it because the installation of the driver will have to be done manually on the server.
NOTE: The workstations that will execute GENEXUS from the NT computer must be connected to it, have defined a mapping to the GENEXUS directory on the server and run under Windows 95 or Windows NT.
IMPORTANT: If your are using Windows NT the SYSTEM USER or SYSTEM ACCOUNT must have Full Access rights over the GENEXUS "shared installation". Otherwise, the License Server will not be able to create the necessary files enabling operation.
Manual Installation of the License Driver
The GENEXUS setup (if it is executed from a windows NT server) automatically incorporates the “Crypkey License” server which lets it act as GENEXUS server. However, if the user installs it on the server’s hard disk but from a Windows 95 workstation then the automatic installation mentioned above will not be carried out and the user will have to perform it manually. The steps below indicate how to perform a manual installation:
This document assumes you have installed NT onto the 'c:\winnt' sub-directory. If not substitute the appropriate installation path wherever you see 'c:\winnt'.
It also assumes that you have installed GENEXUS onto the 'c:\gxw' sub-directory. If not substitute the appropriate installation path wherever you see 'c:\gxw'.
The steps that need to be taken in order to execute GENEXUS from an NT computer are the following:
1. Copy the following files to their corresponding target locations within the NT computer:
c:\gxw\lansrv\WinNT\ckconfig.exe in c:\winnt\ckconfig.exe c:\gxw\lansrv\WinNT \setup_ck.exe in c:\winnt\setup_ck.exe
36 Network Setup
c:\gxw\lansrv\WinNT \crypserv.exe in c:\winnt\system32\crypserv.exe c:\gxw\lansrv\WinNT \ckldrv.sys in c:\winnt\system32\ckldrv.sys
2. Execute the setup_ck.exe program on the NT computer via the run function.
3. Execute the ckconfig.exe program on the NT computer via the run function to be able to choose the directories where GENEXUS can be located. To do so you will need to browse the server's disks and directories, find and select the gxw.exe program and press OK. Remove unnecessary directories.
4. Execute on either the NT computer or on one of the workstations, the gxauthor.exe program located in the directory where GENEXUS has been installed in order to authorize GENEXUS. Configuration Program
The License Server will service requests only in directories specified in CRYPKEY.INI. The file must exist in the directory specified by the environment variable WINDIR. This environment variable is defined during the installation of Windows NT as the root of the NT installation (typically C:\WINNT35). The CRYPKEY.INI file follows the standard Window initialization file format. The crypkey.ini file is automatically updated by the Development Environment and generator setups only if it is executed on the Windows NT server.
CKCONFIG.EXE is the configuration program that provides a graphical interface to manage the directories for all protected programs. It allows the user to add and remove the servicing of directories. CKCONFIG.EXE will create CRYPKEY.INI if it does not exist.
The License Server is not notified of any changes until the configuration program is closed. The user is warned of this when the CKCONFIG.EXE is executed by the next dialog box.
Once you acknowledge this dialog, the main dialog opens displaying all directories
37 Installation Manual
specified in the CRYPKEY.INI file.
You may select an entry from the list box and press the 'Remove' button to delete it from the list box and the INI file. Pressing 'Add' brings up the file Open dialog box to select the directory to be serviced. Only the directory is saved, an easy way to verify that you are in the correct directory is to type “gxw.exe” in the file name field.
If the selected directory already exists in the CRYPKEY.INI file the user is notified
38 Network Setup as follows. A duplicate entry does not occur in the list box or the INI file.
GENEXUS installed on a Windows NT Server
If you install GENEXUS on an NT server (named serverNT) in for example, c:\gxw61 then you must remember to map directly to disk c (that is, the highest level) otherwise you will not be able to authorize GENEXUS’ development environment from a workstation. This is because root directory authorizations are not permitted. This concept is clearly explained in the following example:
For example you have defined the following map:
X:=\\serverNT\gxw61 WRONG !
If you were to execute the authorizer to authorize the development environment from a workstation you will come across the following:
"Please check existence of the x: directory. There might be a problem with the installation of GENEXUS ".
This is because the authorizer considers the logical mapping X: to be a root directory because it is directly executed from X.
If you don’t want to map the entire c: disk install GENEXUS one more directory level down, for example, c:\program\gxw61 and share \\serverNT\program. Uninstalling
Once the drivers have been installed they automatically load during reboot unless they have been uninstalled by executing 'SETUP_CK /UNINSTALL'. Thus, the files copied during the installation process may then be deleted. After the License Driver has been uninstalled you will have to reboot your system in order to be able to install it again by running SETUP_CK. Note: Uninstalling can invalidate authorized license programs including licenses of
39 Installation Manual
products, other than GENEXUS, that use the same protection scheme. Windows NT Known Problems
· Kernel driver error conditions that should contain variable data are reported as printf() type strings.
· On a dual boot DOS/NT system or systems with multiple NT installations: if a program is authorized while running on one operating system, its authorization is invalid while running on the second operating system. If the program is then authorized in the same directory while running under the second operating system the authorization of the first operating system is invalidated. There are no current plans to change this behavior. To work around this the user must transfer the license to another computer, reboot to the second operating system, then transfer the license back. GENEXUS Network Workstation Setup
This section explains how to use the Setup program to install GENEXUS on a network workstation in order to be able to run GENEXUS from a "shared installation". You will not be able to perform a network workstation setup if GENEXUS has not yet been setup on a shared directory or on a network file server via the Network Setup option. Check this with your network administrator. Follow the instructions specified below once you have met up with all the necessary requirements to install GENEXUS. The Setup program includes the display of specific messages on the screen to help you take the right decision.
How to start GENEXUS Network Workstation Setup:
1. Start Windows 2. Connect to the network server or shared directory where the "shared installation" of GENEXUS resides (check with your network administrator if you do not know where GENEXUS has been setup). 3. Map a logical drive letter to the disk or directory of the "shared installation". Be sure this logical drive reference (letter) does not change, otherwise your icons will cease to operate. For example, if GENEXUS is installed in the following place:
\\SERVER\DISK\GXW61
Lets say you assigned 'N' as your MAP drive in such a way that N:=\\SERVER\DISK. You have installed GENEXUS on N:\GXW61. So, from now
40 Network Setup
on, all execution will be done with respect to this logical reference (N:\GXW61). 4. Choose the Run option from the File menu of the Program Manager, File Manager or Start Menu. Type the letter of the mapped drive that stores the "shared installation" on the "Command line", followed by a colon (':'), a back-slash ('\'), the path to the NSETUP subdirectory of the GENEXUS "shared installation", another back-slash ('\') and the word SETUP at the end. Then press enter. For example, type
N:\GXW61\NSETUP\SETUP
During the setup process you will have to follow the setup instructions on the screen and once the setup program has completed click over the OK button or press ENTER.
Once all the files have been installed, the Setup program places GENEXUS icons in a GENEXUS group that are automatically incorporated to your Program Manager's window. You can run the network workstation setup program at any other time to install it on other workstations.
Important: If you are setting GENEXUS to run from a "shared installation" remember to use the logical drive letter when you connect to the "shared installation" and run Setup (such as "N" in the previous example). Whenever you run GENEXUS, you must connect to the "shared installation" via the same logical drive letter to avoid any type of execution problems.
In order to be able to run GENEXUS from a "shared installation" it is necessary to have it authorized. Check with your network administrator to see if GENEXUS has been already authorized on the "shared installation".
41 Installation Manual
42 Tips and License Error Messages
TIPS AND LICENSE ERROR MESSAGES
Installation and Configuration Tips
Changing the Workstation's Date
Do not change the date of the workstation once you start to use GENEXUS because you are sure to have problems. Changing the date of the workstation is critical for GENEXUS. There are two different ways a change in the date can affect it:
1. You may lose the rights to use GENEXUS if you set the date of the machine forward. This type of modification will be registered as if it were any other normal days work. When this is done you will not be able to set the date back again because GENEXUS displays a message stating the setback in time is not possible. If you are working on a network be sure that all workstations are correctly synchronized to avoid problems with the network license protection schema.
2. Many optimizations can be achieved manipulating the date and time of a workstation. For example: each time a table has been modified a "touch" (a time stamp is recorded) is performed. So, when an impact analysis is executed, only those tables whose time stamp is greater than the date of the last executed impact will be analyzed (rephrasing this, all tables modified since the last impact analysis will be analyzed). This clearly optimizes the impact analysis. The generation of programs (check spec) and other GENEXUS features also use a similar mechanism to the one mentioned above. Synchronizing Workstations Time and Date
We highly recommend you synchronize all workstations because it is not possible to work with PCs whose dates differ among themselves; due to the type of protection being used. Although this is a very important restriction, it is not the only reason why all workstations should be set to the same date. A model may be used by different workstations and if it happened to be updated by a workstation with a more updated 'date' GENEXUS will inform you of this abnormality because its Check Specification considers the date and time each object was last saved. So make sure all workstations have synchronized their dates and time settings with respect to the server.
43 Installation Manual
If you are using Windows '95 and you wish to synchronize all workstations with the server you must define a batch file that will be triggered by the StartUp group. The batch file must contain the following:
NET TIME \\SERVERNAME /SET /YES
where SERVERNAME is the name of the server. This command can also be used for NT server synchronization. How to re-authorize a site in case the date of the license is incorrect
First you must execute the Authorizer and press the Authorize button. A dialog will display a message stating the license already exists for that directory and it will be lost if a valid site key is entered, press YES. Another dialog will appear asking you to confirm the date, press YES again even though it is incorrect. Note down the new site code.
Send this new site code to your distributor indicating whether you require a fixed or floating license (indicate the number of users) in order to obtain your new site key.
Once you get your new site key make sure the following is done:
All workstations must exit GENEXUS.
Correct the dates of all workstations and server (the second tip explains how to do this).
Execute the Authorizer again and press the Authorize button. A dialog will display a message stating the license already exists for that directory and it will be lost if a valid site key is entered, press YES. Another dialog will appear asking you to confirm the date, press YES after you have corrected it. Enter the new site key and press OK. Now you are ready to start again!
44 Tips and License Error Messages
New Site Codes
It is highly recommended you obtain your new site code from your distributor before your license expires. This will avoid any possible delay. How to obtain your new site code is explained in the "Authorize" section. CKSERVE and CKSERVER
Licenses generated with CKSERVE (this is the NLM used by prior GENEXUS versions) cannot be used by CKSERVER and vice versa. Refer to NOVELL Netware Networks for more information. Common License Error Messages
Error Messages when entering a New Site Key
SITE KEY CRC FAILURE This message is displayed by the authorizer when you enter an invalid key (it was probably due to a typing error).
Save Site Key ERROR Once this message is displayed the License Information Dialog will offer you more information about the problem. You could be displayed the following message:
PROGRAM MOVED OR SITEKEY BAD PASSWORD You may be trying to enter a Key that corresponds to a different version. Error Messages when querying the License:
RESTRICTION FILE IS MOVED This error message is displayed when the license is lost due to the corruption of some of the protection files. Motives: 1. You have been meddling with them. 2. Your PC halted when these files were being saved. 3. These files were either being moved manually or via a disk reorganizer program.
45 Installation Manual
PROGRAM MOVED OR PROGRAM BAD PASSWORD This message may also be displayed after you have renamed a directory containing an authorized GENEXUS version on a network. Refer to Authorizing GENEXUS on a "Shared Installation" for more information.
Initialization Failure: could not get file location information (-100) If you get this message when entering GENEXUS it is probably because you are trying to directly execute it from a network disk instead of executing it via a map link.
46 AS/400 Library Installation
GENEXUS AS/400 LIBRARY INSTALLATION
This section details the requirements and procedures needed to install GENEXUS' AS/400 Library. This library is used to compile and execute RPG/400 or COBOL/400 programs generated by GENEXUS.
There are two different setup versions used to install the AS/400 Library. The setup version will depend on the OS/400 version you are using.
GXWLIB 2.2: is for all OS/400 versions up to and including version 2.2 GXWLIB 2.3 and higher: is for version 2.3 and higher OS/400 versions
Be sure to solicit the correct setup version. Then you may proceed with the normal installation process. About the Installation if version 2.2 is used
Distribution disks will be unpacked in the first drive that has enough free space under the gxlib.tmp directory; this directory is automatically created in the chosen drive. These unpacked installation files actually install GENEXUS library on your AS/400 system.
The installation process will ask you to select the compiler you have installed on your AS/400. GENEXUS library works with both COBOL and RPG GENEXUS generators. If you have both of them select any of them. The installation process only requires one selection.
Once the installation process ends you will have the chance to install it again. This is in case you have had installation problems, once fixed, you need only try again with the second part of the process.
47 Installation Manual
Requirements
You need one of the following AS/400 communications software:
· Client Access 95/NT · NetSoft Midrange Bundle · if you use TCP/IP then be sure you are using OS/400 V3R1 or higher
The following Client Access functions must be available to install the GENEXUS library:
· Submit Remote Command · Transfer Function
You must also have enough authority to:
· Delete the GENEXUS library (GX) (DLTLIB command) · Create a library (CRTLIB command) · Create a CL program (CRTCLPGM command) · Create a COBOL or RPG program (CRTCBLPGM or CRTRPGPGM commands) · Create a command (CRTCMD command) · Create a source physical file (CRTSRCPF command) · Create a physical file (CRTPF command) · Create a save file (CRTSAVF command) · Restore objects (RSTOBJ command) Normal Installation Process for version 2.2
1. Start Windows. 2. Make sure you are connected to the AS/400 computer 3. Choose the Run option from the File menu of the Program Manager, File Manager or Start Menu. 4. Insert the GENEXUS AS/400 Library disk in the appropriate high-density floppy disk drive. 5. Type the letter of the drive where the AS/400 Library disk has been placed followed by a colon (':'), back-slash ('\') and the word setup in the "Command line" box.
For example, type a:\setup Then press ENTER.
48 AS/400 Library Installation
You will be reminded of the minimum requirements that guarantee a successful installation, see below.
Following the instructions displayed on the Setup Window you can easily carry out the Setup.
One of the Setup Windows you will come across will require the selection of the compiler you will use, see below.
6. Once the Setup has completed, click over the OK button or press ENTER.
49 Installation Manual
About the Installation for version 2.3 and higher
In previous versions, during the setup process the user was prompted for the OS/400 version, the transfer mode (TCP/IP or Client Access), the language for compiling (RPG or Cobol), etc. Now these options are set in the transfer program.
The setup prompts for: installation directory (the default is GeneXus installation directory), folder to create the transfer icon and type of installation. The components to install are the ones shown in the bitmap above. Minimal and typical type of installation installs all components. Custom installation allows marking and unmarking options. If one option is unmarked (e.g.: V3R6M0) and then this operating system is selected, the transfer program will issue an error because the necessary files cannot be found. An option should be unmarked only if you want to save disk space and you are sure you'll never use that operating system version.
This is AS/400 transfer main window:
50 AS/400 Library Installation
You are prompted for: · Type of installation (full or partial), you can select the options from the combo box · Compiler: RPG or Cobol · OS/400 version · Transfer: this button begins the transfer · Options: clicking this button you'll be displayed the following dialog:
51 Installation Manual
The available transfer modes are: · FTP over TCP/IP · ODBC over Client/Access · Client/Access Native
52 AS/400 Library Installation
Problems Installing GENEXUS for Windows Library
If GENEXUS for Windows Library installation gives you problems you may modify the GXW.INI file by adding the following lines:
[AS/400 GXLib Install] Trace=1 Tracefile=c:\win95\gxlib.txt TraceLevel=1 StopMessages=1
So, the following results are:
1. Trace, clarifies if it is done or not. 2. Tracefile is the file where the trace results will be placed (log), the file will be created in this directory (it must exist). 3. TraceLevel has three levels, 1 to 3, where 1 is the minimum log level. 4. StopMessages=1 indicates whether for each command the execution will be paused (for example, the source is transferred to the AS/400 and it will wait until the user presses a key to indicate the go ahead of the following installation step).
53 Installation Manual
ERROR DESCRIPTION AND RECOVERY PROCEDURES
When an error occurs the installation procedure stops and displays, for example, a message with the following information:
Error in Transfer 0x0035. Label: 00001. Message: Conversation allocation failed. Doing: CRTLIB LIB(GX) TEXT('GeneXus/400 5.0 5.0') AUT(*USE).
In this example 0x0035 is the Client/Access error number displaying its respective error message. The last line displays the command the installation was trying to execute when the error occurred. The label number 00001 can be found in the errors.lbl file, this file contains a description of the error and an error recovery procedure. List of Errors
Label Error Description Points to be considered 00001 GENEXUS library (GX) could Make sure the communications software is correctly not be created/deleted. installed and the submit remote command function is available. If you are a new GENEXUS customer: · you have not been authorized to create a library. If you are upgrading from a previous GENEXUS version: · someone else is using the GENEXUS library. Use the CHKOBJLCK command to see who is using the library. · you are not authorized to delete the GENEXUS library. · you are not authorized to create a library. 00002 Unable to create the physical Probable cause: file named GXUPDSRC in · you are probably not authorized to use the the GENEXUS Library CRTSRCPF command. Check with your system administrator and retry the operation.
54 List of Errors
Label Error Description Points to be considered 00004 Could not transfer program Probable cause: GXCVTSAVF. · the transfer function is not available. 00005 Could not create program Probable cause: GXCVTSAVF. · you are not authorized to create a COBOL or RPG program (CRTCBLPGM or CRTRPGPGM commands). · check with your system administrator and retry the operation. 00006 Could not transfer program Probable cause: GXTOSAVF. · file TOSAVF.CLP does not exist in the temporary gxlib.tmp directory. · check the directory to see if the above file exists. If it does not exist contact your distributor and solicit another installation disk. 00007 Could not compile program Probable cause: GXTOSAVF. · you are not authorized to create a CL program (CRTCLPGM command). · check with your system administrator and retry the operation. 00008 Could not transfer the Probable cause: GXTOSAVF command. · file TOSAVF.CMD does not exist in the temporary gxlib.tmp directory. · check the directory to see if the above file exists. If it does not exist contact your distributor and solicit another installation disk. 00009 Could not compile the Probable cause: GXTOSAVF command. · you are not authorized to create a command (CRTCMD command). · check with your system administrator and retry the operation. 00010 Could not create the Probable cause: GXUPDPF file. · you are not authorized to create a physical file (CRTPF command). · check with your system administrator and retry the operation. 00011 Could not transfer the Probable cause: GXUPDPF file. · File GXUPDPF.SAV does not exist in the temporary gxlib.tmp directory. · Check the directory for the above file. If it does not exist contact your distributor and solicit another installation disk. 00012 Could not create the Probable cause: GXUPDSAVF save file. · You are not authorized to create a save file (CRTSAVF command). · Check with your system administrator and retry the operation.
55 Installation Manual
Label Error Description Points to be considered 00013 Errors converting file This error should not occur. Please contact your GXUPDPF to save file distributor. GXUPDSAVF. 00014 Could not delete file This error should not occur. Please contact your GXUPDPF. distributor. 00015 Errors restoring objects in the This error should not occur. Please contact your GX library. distributor. 00016 Could not delete save file This error should not occur. Please contact your GXUPDSAVF. distributor.
56 Installing a Patch
INSTALLING A PATCH
This section will provide you with all the information you need to know on how to install GENEXUS patches. Introduction
There are two types of patch files, one of them corresponds to the Development Environment patch release and the other corresponds to the generator you are using to develop your applications.
Here is the list of the possible patch files you may receive:
DExxxPy.EXE (Development Environment) CBxxxPy.EXE (COBOL/400 Generator) CSxxxPy.EXE (FoxPro Client/Server Generator) FXxxxPy.EXE (FoxPro Generator) RPxxxPy.EXE (RPG/400 Generator) XDxxxPy.EXE (Xbase Generator) VFxxxPy.EXE (Visual FoxPro Generator) VCxxxPy.EXE (Visual FoxPro C/S Generator) VBxxxPy.EXE (Visual Basic Generator) SQxxxPy.EXE (C/SQL Generator) SWxxxPy. EXE (Setup Wizard)
Where 'xxx' will indicate the GENEXUS version over which the patch will be applied and 'y' is the patch number identifier (for example: DE60P1.EXE is patch 1 of the Development Environment for GENEXUS version 6 evolution 1).
There need not necessarily be a patch release for every generator, in other words, a patch for a generator will be released only if changes have been made to the generator. Installing a Patch
In order to improve the performance of the patch installation process we suggest that you create a directory in your hard disk (for example you may name it GXPATCH) where all patch contents will be copied when executed.
You must execute the EXE corresponding to the Development Environment and all
57 Installation Manual generator patch EXEs corresponding to the generators you possess.
You will encounter the following window when you execute the Development Environment patch:
Once you confirm the installation you will be asked to indicate where your GENEXUS version has been stored so it will be updated:
Now the actual patch installation will take place.
Once finalized you must repeat an analogous process for each one of the patch generators you need to install.
All patches are accumulative, meaning it is sufficient to apply the last patch release because it will make sure you are up to date with all prior patches as well.
58 Installing a Patch
Which was the last Patch Release I Installed?
Each installed patch saves a file in your GENEXUS version root directory.
Here is the list of the possible files:
GXWxxxDE.00y (Development Environment) GXWxxxCB.00y (COBOL/400 Generator) GXWxxxCS.00y (FoxPro Client/Server Generator) GXWxxxFX.00y (FoxPro Generator) GXWxxxRP.00y (RPG/400 Generator) GXWxxxXD.00y (Xbase Generator) GXWxxxVB.00y (Visual Basic Generator) GXWxxxVF.00y (Visual FoxPro Generator) GXWxxxVC.00y (Visual FoxPro C/S Generator) GXWxxxSQ.00y (C/SQL Generator) GXWxxxSW.00y(Setup Wizard)
Where 'xxx' will indicate the GENEXUS version and 'y' is the patch number identifier (for example: if the root directory of your GENEXUS version has the following file GXW61CS.001 then the last patch you installed was patch 1 of the Client/Server generator for GENEXUS version 6 evolution 1).
So, if you query all GXW*.00? files you will know which was the last patch you applied to your GENEXUS version.
It is important you provide this and other data when soliciting support. Differences between Patches
If you already have installed patch 1 you will not want to install all of patch 2 once released. You can install just the differences between the two patches and thus update patch 1.
This mechanism consists of the distribution of an EXE that patches over the prior patch.
EXAMPLE:
Development Environment Patch 1: DE60P1.EXE Development Environment Patch 2: DE60P2.EXE
59 Installation Manual
A file called GXWDE12.EXE will be distributed and it will need to be executed over DE60P1.EXE. This file will apply a patch on patch 1 transforming it into DE60P2.EXE.
The difference in size between DE60P2.EXE and GXWDE12.EXE is that the latter is a lot smaller as it only updates patch 1 to patch 2.
60 Installing a Patch
61 Installation Manual
USER NOTES
62 Index
63 Installation Manual
INDEX
gxw._tb...... 33 A I A NOTE FOR ALL GENEXUS WINDOWS USERS...... 2 Installation Tips ...... 42 AS/400 communications software ..... 47 Installing a Patch...... 55 Authorize...... 20 K Authorizing Generators ...... 22 KEY.LOG...... 23 C Known Problems for Windows NT.... 39 CKSERVE and CKSERVER ...... 44 L common license errors...... 42 Configuration Requirements for License Error Messages ...... 44 NOVELL Netware...... 32 License Information ...... 20 Copy Protection Scheme ...... 9 M D map ...... 38 Destination Directory...... 16 N Differences between Patches ...... 57 Direct Transfer ...... 22 Network Server or Shared Directory.. 30 Network Workstation Configuration.. 32 E Network Workstation Setup...... 39 Error Description and Recovery New Site Codes...... 44 Procedures ...... 52 NOVELL Netware Networks...... 31 NOVELL Trouble-Shooting ...... 33 F P Fixed license...... 9 Floating license...... 9 patch files...... 55 patch installation process ...... 55 G Problems Installing GENEXUS for GENEXUS AS/400 LIBRARY Windows Library ...... 50 INSTALLATION...... 46 PROGRAM MOVED OR BAD GENEXUS Authorizer...... 19 PASSWORD...... 45 GENEXUS installed on a Windows NT R Server ...... 38 GENEXUS Network SETUP ...... 29 Re-authorizing a site ...... 43 GENEXUS on a stand-alone computer 13 Register Transfer...... 24 GENEXUS Tutorial...... 2 registration of the specifier and GXW*.00? files...... 57 generators...... 16
64 Index
Remote License Transfer...... 24 Workstations Time and Date...... 42 Requirements...... 11 systems on which you could have a shared installation of GENEXUS..... 29 S T Setup Options ...... 3 Shareable Files ...... 32 Tips...... 42 Stand-Alone Setup...... 13 Transfer In ...... 25 Starting GENEXUS...... 27 Transfer Out...... 24 steps which need to be taken in order W to execute GENEXUS from an NT computer...... 35 Windows NT Networks ...... 34 Synchronizing NOVELL Windows NT Server ...... 38
65