IBM VisualAge Generator V4.0 FixPak2 Readme PTF #: UQ47415

This VisualAge Generator V4.0 FixPak2 Readme file contains the latest installation instructions, product support, and limitation information. You can view the .HTM version of this Readme file using a web-browsing program.

Product Enhancements, Problem Support, and Limitations

Java Performance Improvements

• A number of enhancements have been made to VAGen Developer on Java resulting in substantial performance improvements in a number of areas.  In general, reading VAGen parts from the library will be faster.  Performance has also been improved in the following specific areas:

- Opening a program in the Program Editor
- Expanding the Program Editor structure diagram and specifications nodes
- Open a record or table containing many shared data items
- Loading a program in the Test Facility and running it for the first time

Configure VAGen Required Projects dialog

• A new dialog has been added to configure the VAGen Required Projects for a given project.  This provides an easier alternative to manually editing the Project List Part (PLP).  To configure the required projects of a project, select the project in the VAJava Workbench and choose "Manage->Configure VAGen Required Projects" from its context menu.  On the Configure dialog select the required projects and editions.  Choosing Ok will cause the Project List Part (PLP) to be created or updated.  A default package for the project will be created if necessary to contain the PLP.

New Java APIs

• The following VAGen Java APIs have been added since FixPak 1.  Unless otherwise noted, the methods below are part of the VAGenUtilityInterface class.  See the VAGen User's Guide for documentation of other APIs.

 
• public static void compareDifferences(VAGenModelDifferences diffs)
Open a comparison browser to display the differences specified by the VAGenModelDifferences instance.  The differences instance is returned from the computeDifferences method.
• public static VAGenModelDifferences computeDifferences(Model first, Model second)
Compute the difference between two workspace or repository objects. Model is either a Project, ProjectEdition, Package, PackageEdition, Type, or TypeEdition.  Return null if there are no differences.  Use the compareDifferences method to display the differences in a browser.
• public static VAGenProject[] getRequiredProjects(Model project)
Return the array of VAGen Required Projects of the given project.  The required projects are determined by reading the Project List Part.
• public static Model previousEdition(Model model)
Return the previous edition of the workspace or repository object. Model is either a Project, ProjectEdition, Package, PackageEdition, Type, or TypeEdition.  Return null if the object does not have a previous edition.
• public static boolean setRequiredProjects(Project project, VAGenProject[] reqProjects)
Set the VAGen Required Projects of the given project.  Setting the required projects will create or update the Project List Part, creating a default package in the project if necessary.  Return true if successful, and false if the default package or Project List Part could not be created or updated.

User Administration

• The following new methods provide APIs to perform user administration.

 
• public static boolean addGroupMember(Package pkg, String uniqueName)
Add the specified user to the package user group.  Return true if the user was added successfully.  Only the Administrator or Package owner may add users to the group.
• public static boolean addUser(String uniqueName, String fullName, String networkName)
Add a new user.  Return true if the user was created successfully.  Only the Administrator may create new users.
• public static String[] getGroupMembers(Package pkg)
Return the list of users in the package user group.
• public static String getUserFullName(String uniqueName)
Return the full name of the specified user, or null if the user doesn't exist.
• public static String getUserNetworkName(String uniqueName)
Return the network name of the specified user, or null if the user doesn't exist.
• public static String[] getValidUsers()
Return an array of the unique names of the currently defined users.
• public static boolean removeGroupMember(Package pkg, String uniqueName)
Remove the specified user from the package user group.  Return true if the user was removed successfully.  Only the Administrator or Package owner may add users to the group.
• public static boolean removeUser(String uniqueName)
Remove the specified user.  Return true if the user was deleted successfully. Only the Administrator can delete users.
• public static boolean setOwner(Model model, String uniqueName)
Set the owner of the specified Workspace or Repository object. Model may be a Project, ProjectEdition, Package, PackageEdition, Type, or TypeEdition.  Return true if the owner was set successfully.  Only the Administrator or the current owner of the object can set the owner.
• public static boolean updateUser(String uniqueName, String newFullName, String newNetworkName)
Update the full name and network name of the specified user.  Return true if the information was updated successfully.  Only the Administrator can update user information.

User Groups

• The following APIs provide a controlled means of changing the Workspace owner without a password.  The workspace owner can be changed without a password only if the current user and new user belong to the same User Group.  User Groups are created and maintained by the Administrator, and the Administrator cannot belong to any group.  A User Group is implicitly created when the first user is added to it.  The revertWorkspaceOwner method must be invoked between calls to changeWorkspaceOwner -- this prevents users from changing the workspace owner to a user in a different group by calling changeWorkspaceOwner twice in a row.

 
• VisualAge Java provides APIs to get and set the current Workspace Owner using a password.  See Workspace.getCurrentOwnerName() and changeOwner().

 
• public static boolean addUserGroupMember(String groupName, String uniqueName)
Add the specified user to the User Group.  Only the Administrator may perform this action, and the user being added may not be the Administrator.  Return true on success.
• public static boolean changeWorkspaceOwner(String uniqueName)
Change the Workspace owner to the specified user.  The current user and new user must belong to the same User Group.  This method cannot be invoked twice in a row without calling revertWorkspaceOwner in between.  Return true on success.
• public static String[] getUserGroupMembers(String groupName)
Return the list of users in the specified User Group.
• public static String[] getUserGroups()
Return the list of defined User Groups
• public static boolean removeUserGroupMember(String groupName, String uniqueName)
Remove the specified user from the User Group.  Only the Administrator may perform this action.  Return true on success.
• public static boolean revertWorkspaceOwner()
Revert the Workspace owner to the user that was the owner before the changeWorkspaceOwner method was called.  This method must be called in between calls to changeWorkspaceOwner.  Return true on success.

Parts Browser Menus

• The following new methods provide APIs for adding items to and removing items from the VAGen Part Browser menus.
• public static boolean addPackagesMenuItem(String itemName, String listenerClassName, int enabled)
• public static boolean addPackagesMenuItem(String itemName, String listenerClassName, String enablerClassName);
• public static void addPackagesMenuSeparator(String separatorName)
• public static boolean addPartsMenuItem(String itemName, String listenerClassName, String enablerClassName)
• public static boolean addToolsMenuItem(String itemName, String listenerClassName, String enablerClassName);
• public static boolean removePackagesMenuItem(String itemName)
• listenerClassName is the name of a class which implements the VAGenActionListener interface.  enablerClassName is the name of a class which implements the VAGenActionEnabler interface.  Class names must be qualified with their package name.  See the MENU_ENABLED constants in the the VAGenConstants class for valid values for the enabled parameter.

 
• If enablerClassName is specified, an instance of the class will be created, and its actionEnabled method will be invoked to determine if the menu item should be enabled.  In the case of items added to the Packages and Parts menus, calling getActionData() on the VAGenActionEvent instance will return a vector of Package or VAGenPartInformation instances, representing the current selection in the Parts Browser.

Performing Actions at Startup

• It is now possible to execute methods when VisualAge Generator is first started.  A new interface, VAGenStartupClass, has been added, which specifies one method, startUp.  Classes which implement this interface will have an instance of the class created when VisualAge Generator is started, and the startUp method of the instance will be invoked.  This can be used in conjunction with other VAJava and VAGen APIs to prompt the user or perform a series of actions on startup.

VAGenPartInformation class additions

• The following methods have been added to the VAGenPartInformation class, and allow querying and loading of the editions of VAGen parts.  Use the VAGenUtilityInterface.partInfo methods to get a VAGenPartInformation instance.

 
• public Date getPreviousTimeStamp()
Return the timestamp of the previous edition of the part.  If no previous edition exists, return null.
• public Date[] getTimeStamps()
Return an array of timestamps representing the editions of the part.
• public boolean loadEdition(Date timestamp)
Load the edition of the part specified by the timestamp.  Return true if the operation succeeded.

Database binding in DB2 applications

VisualAge Generator V4.0 FixPak2 requires the developer to rebind to the database to develop, test and generate DB2 applications.  VisualAge Generator prompts the developer when a rebind is required.  If the developer selects YES to the prompt, VisualAge Generator rebinds as required.   If NO is selected to the prompt, the developer can rebind using the DB2 BIND command.   The physical file name for the bind file for VisualAge Generator V4.0 is hptdb240.bnd.  The new package name associated with hptdb240.bnd is DEVELOP.HPT2O402 for OS/2 and DEVELOP.HPT2W402 for Windows NT .
V4 to V4 Migration
 
Previously, only V3 to V4 migrations were possible (in the V3 to V4 Migration Tool). Now V4 to V4 migrations are possible.  A possible scenario would be if a customer migrates from MSL's to VAGen V4.x Smalltalk. Later, they can migrate from VAGen V4.x Smalltalk toVAGen 4.x in Java using the V3 to V4 Migration tool.

List of APARs

 
JAVA GEN:
• PQ40904 WHEN .FTP FILE IS CREATED SOME OF THE FILENAMES DO NOT HAVE SPA

Developer:
• PQ15177 ITF GPF ON NT USING ALTERNATE INDEX

PQ34581 WALKBACK EXCLDTKEYNOTFOUND WHEN USING VISUALAGE GENERATOR 4.0
PQ34699 ITF/PREPROCESSOR SHOULD CHECK THE RESULT FIELD LENGTH TO ENSURE
PQ35195 EDIT OF TABLE CONTENTS WHEN USING THE SCROLL BAR TO GET TO THE
PQ35561 BACK OUT CHANGES MADE IN APAR PQ31338 FOR VSE DL/1 ONLY
PQ35765 CUSTOMER CANNOT CHANGE THE NAME OF A TEAR OFF ATTRIBUTE OF
PQ35962 RECORDS DESC FIELD DOESNT ACCEPT DBCS CHARS CORRECTLY
PQ35983 ERRORS WHEN LOADING CONFIG MAP THAT HAS INCLUDED THE DATE
PQ36013 BATCH GENERATION ON JAVA FAILS WITH WALKBACK
PQ36145 RC0 RECEIVED EVEN WHEN BATCH GENERATE FAILS USING HPTCMD
PQ36593 VG 3.1+FP3+FCEOPT=1 DOESNT CALL SETENV.BAT
PQ36617 PERFOMANCE PROBLEMS USING THE EXPORT COMMAND ON VAG 4.0 COMPAR
PQ36769 THE CANCEL BUTTON ON THE CSOPRMPT WINDOW DOES NOT HAVE ANY
PQ37209 QUICK FORM FOR PACK AND NUMERIC VISUALAGE GENERATOR DATA ITEMS
PQ37275 ERROR HPT.CM.215E RECEIVED WHEN TRYING TO PRINT TO A NETWORK
PQ37349 INCORRECT OUTPUT AFTER APPLY APAR PQ35561
PQ37422 WALKBACK DEBUGGER WHEN MIGRATING VISUALAGE GENERATOR ESF INTO
PQ37442 NETWORK PROTOCOL IS NOT SUPPORTED BY VAGEN CSO HPTGATEWAY.JAR
PQ37498 $ SIGN RECONIZED AS END OF MEMBER NAME WHEN DOUBLE CLICKING ON
PQ37696 INSTANCES REFERENCE CXTESTPOINTMANAGER
PQ37703 VISUALAGE GENERATOR DATA ITEM NAME THAT CONTAINS DBCS CHARACTER
PQ37760 WALKBACK EXCEPTION IS NOT RESUMABLE WHEN CALLING LOCAL DLL F
PQ37849 LINKAGE TABLE REQUIRED INCONSISTENT BETWEEN ITF AND RUNTIME
PQ37852 CSOCHT.TAB AND CSOCHT.ESF MISSING FROM VISUALAGE GENERATOR 4.0
PQ37906 MIGRATION TOOL UNABLE TO PROCESS ESF FILE THAT CONTAINS A
PQ38168 SUBSCRIPTED EZEDLPCB FAILS VALIDATION WITH WALKBACK
PQ38371 VAGEN JAVA CLIENTS NOT ABLE TO CHANGE USERID ON SUBSEQUENT CALL
PQ38383 WALKBACK WHEN USING VALIDATE FUNCTION ON A VISUALAGE GENERATOR
PQ38385 WALKBACK WHEN MIGRATING VA GEN 2.2 ESF TO VA GEN 4.0.
PQ38388 CHECKBOXES NOT CLEARED FOR CONVERSED UI RECORDS
PQ38412 CANNOT CREATE NEW VG PARTS IN PKG IF YOU'RE NOT THE OWNER OF PK
PQ38415 SERVER GENERATION OPTIONS NOT PICKED UP FROM HPT.INI FILE
PQ38432 INCONSISTENT RESULTS WHEN USING LOCAL STORAGE ITEMS WITH
PQ38449 HPT.CG.62.E IF LOCAL STORAGE NAME IS CHANGED THEN GEN'D ON JAVA
PQ38515 USING MIGRATION TOOL V3 TO V4 MIGRATION RESULTS IN ERROR
PQ38541 CUST STATES HE IS HAVING VSAM PROBLEMS WHEN HE ACCESSES THE
PQ38567 COMPILED ERROR OCCURS SAVING A VAGEN JAVA GUI.
PQ38669 EXECUTEDEFERRED: DOES NOT SETUP ARGUMENTS CORRECTLY AND CAUSES
PQ38894 MESSAGE TABLE DOES NOT WORK IN RUNTIME FOR WEB TRANSACTION.
PQ38903 LAN GENERATION OUTPUT .LISTING FILE EXPOSES PASSWORDS THAT
PQ39116 FILE 'PROGRAM' CREATED DURING PREPARATION CONTAINING PREP MSGS
PQ39204 LINK ERRORS WHEN USING ORACLE 8I ON NT
PQ39310 VERSION DESCREPENCY FOR IMPLICIT CLOSE SQL CURSOR STATEMENTS
PQ39359 WALKBACK OPENING PROPERTIES FOR VAGEN FILE ACCESSOR PART IN
PQ39381 DATA ASSOCIATED WITH A VISUALAGE GENERATOR NUMERIC DATA ITEM
PQ39455 FILE IN USE CONDITION RETURNED WHEN ATTEMPTING TO PERFORM
PQ39582 EFKSND REXX PROGRAM INCLUDES CRLF PARAMETERS WHEN PASSING BINAR
PQ39653 VALIDATION FOR SEGMENT FIELD NAMES IN DL/I CALL DEFINITIONS
PQ39892 INCORRECT OUTPUT WHEN PASSING PARAMETERS TO A FUNCTION AND THE
PQ39983 ZERO VALUES INCORRECTLY DISPLAYED IN CDV USING PACKETING.
PQ40053 'ABTERROR DOES NOT UNDERSTAND SIGNAL' WALKBACK ON STARTUP
PQ40199 CUSTOMER IS GETTING ERROR IN ITF WHEN USING A WEB TRANSACTION T
PQ40611 VISUALAGE GENERATOR COBOL GENERATOR FAILS TO RECOGNIZE VALUES
PQ40619 INVALID COBOL GENERATED FOR VISUALAGE GENERATOR PROGRAM THAT
PQ40620 CPMI BEING USED TO START THE VISUALAGE GENERATOR WEB TRANSACTIO
PQ40756 RECEIVER MUST BE A BOOLEAN WALKBACK IF VG PART NOT DEFINED
PQ40759 VALIDATION FAILS AFTER CHANGING VG PART EVEN IF PART IS VALID
PQ40869 EXCLDTKEYNOTFOUND ERROR IN HPTADVISEREGISTRAR USING PLP FOR GEN
 
C++ GEN:
• PQ15379 MSGFCE0421E DOES NOT GIVE MEANINGFUL MESSAGE

PQ35046 MULTIPLE PRINTFILES ON AIX
PQ35098 USING CAST SPECIFICATION WE RECEIVE SQLCODE -501
PQ35385 WHEN GENERATING A TUI PART TO A DLL, THE CUSTOMER IS RECEIVING
PQ36391 (REPLY OPTION DOES NOT WORK IF FCW0096E OR FCW0012E OCCURS ON
PQ36769 THE CANCEL BUTTON ON THE CSOPRMPT WINDOW DOES NOT HAVE ANY
PQ37021 MEMORY LEAK WHEN CALLING VG CALLED BATCH APPLICATION
PQ37021 MEMORY LEAK WHEN CALLING VG CALLED BATCH APPLICATION
PQ37255 PERFORMANCE ENHANCEMENT FOR THE SEARCH PATH WHEN LOADING LIBS
PQ37577 EZELTERM AS APP CONSTRUCTOR PARM CAUSES ILLEGAL MEMORY ACCESS
PQ37593 ORACLE HINT CLAUSE SUPPORT ON VG40+FP1
PQ38022 LIKE predicate gets invalid data when a host variable is used
PQ38380 DEFAULT DB CONNECTION ATTEMPTED EVEN IF EZERSQLDB IS NOT SET
PQ38715 POOR PERFORMANCE CALLING VISUALAGE GENERATOR C++ PROGRAMS
PQ39164 CONNECTIONS DO NOT SWITCH IF FCWDBNOOP=YES FOR NT/CICS
PQ39204 LINK ERRORS WHEN USING ORACLE 8I ON NT
PQ39312 COMPILE ERROR WHEN PREPPING THE VISUALAGE GENERATOR 4.0 SAMPLE
PQ40098 DXFR TO WEB TRANSACTION WITH A 1ST UI DEFINED RESULTS IN A TRAP
PQ40185 SQLCODE -805 WHEN VISUALAGE GENERATOR C++ PROGRAM ATTEMPTS
PQ40607 COMPILE FAILURE WHEN ASSIGNING CHA TO SQLHEX
PQ40822 DATA STORED IN SESSION OBJECT MUST BE SERIALIZABLE
PQ41093 PROBLEM USING HPTSECUREGATEWAYURL BEAN
PQ41357 CSOERRORUIR.JSP ON AIX CONTAINS "IMPORTS" INSTEAD OF "IMPORT"
TEMPLATES:
• PQ37929 Various problems using EZEUIERR EZE word

PQ38107 Hourglass not displayed when closing VAGT workspace
PQ38108 Vertical scroll bar not always produced for list layout
PQ38109 Error view and system error view parts overlap
PQ38110 VisualAge Generator record part not created by VAGT
PQ38111 Walkback performing VAGT import/export
PQ38112 Field of business object added more than once
PQ38113 Install error when adding or deleting the VAGT feature
PQ38115 Poor performance of VAGT Browser
PQ38117 Connections to deleted methods are not removed
PQ38119 Unable to view last column in a list
PQ38122 Walkback migrating from Smalltalk V3 to Java V4
PQ38123 Improvements to VAGT class MdlInstanceRegister
PQ38124 Generation errors when duplicate target identifies are generated
PQ38125 Default decimal separator is always used
PQ38126 Online help is not launched when the help button is clicked
PQ38127 Warning message indicating Java is not responding while using VAGT to generate
PQ38129 Modifications to form and notebook parts are not recognized
PQ38131 "ZOOM ON DOUBLE CLICK" Generation parameter not working
PQ38135 VisualAge Generator TUI program created by VAGT references a field that was not created on the map
PQ38136 VAGT interface unit Java generator creates windows that are not properly sized
PQ38137 Date and numeric data type elements function incorrectly
PQ38138 Errors using VAGT generated web transaction program that uses the XFER transaction model
PQ38141 VAGT Browser not refreshed
PQ38143 Hourglass not displayed when expanding the tree view
PQ40063 VAGT: Timestamp format in TUI is incorrect
PQ40841 VAGT: Several fields in the worksatation produced garbage text for DBCS contents
PQ40843 VAGT Web: Help list can read more than 20 rows per page
PQ40844 VAGT Web: Extraction item is generated correctly for non alpha-numeric fields
PQ40845 VAGT Web: Communication Record is RAD and becomes main working storage in the Web program
PQ40846 VAGT Web: areSecondaryTablesUpdatable is taken into account
PQ40847 VAGT Web: Save action is taken into account
PQ40848 VAGT: Help list don't use the concurrency management fields and ignore the additional field for the extraction
PQ40849 VAGT TUI: case is kept for the labels.
PQ40850 VAGT Server: Missing "end" in the update function (3 tiers & partial Business Object)
PQ41551 Generators: Some default value types are not taken into account
PQ41552 Generators: Inconsistent naming of the items in the UI Record for web transactions
PQ41553 Generators: Missing Hook in web transactions
PQ41554 Generators: Missing entry point generators : Tui & Web Relational Table generators
PQ41555 Generators: Concurrency management in XFer Web applications
PQ41556 Generators: Inconsistents default actions in web applications
PQ41557 Generators: Paging with numeric keys don't work for lists in web applications
PQ41558 Generators: AreSecondaryTablesUpdatable parameter to take into account in web applications
PQ41559 Generators: Save action to take into account in web applications
PQ41560 Workstation: Scroll in the package/application fields in the instance browsers (Definition et Generation Parameters)
PQ41561 Workstation: Instance menu is sometimes enabled when it should not be
PQ41562 Workstation: Date and Time are displayed in an inconsistent format for DBCS characters

Other fixes

• MVS COBOL Generation
COBOL generation to all MVS platform now results in the creation of an APPNAME.LED file. During preparation this file will be uploaded to the HLQ.*.EZELINK library (where * is the target platform). This file contains the Binder instructions required to link edit the generated program and will not be needed by most users.
To prevent the upload of this part, modify template EFK2OPPM.TPL. Change the following line:

:TYPE PART_TYPE='EZELED' WORKSTATION_EXT='.LED'
                     MVS_EXT='EZELINK'

to look like this:

:TYPE PART_TYPE='EZELED' WORKSTATION_EXT='.LED'
                     MVS_EXT='EZELINK' UPLOAD='N'
 

Product Limitations

• Generating with the LISTING option
There is a known problem when generating with the LISTING option turned on and no DBPASSWORD has been set. This will result in a walkback. There are two work arounds, either turn LISTING off ( this is the default setting ) or specify a DBPASSWORD ( i.e /DBPASSWORD=FRED ). If you are using the online generation options dialog the DBPASSWORD setting is found on the Preparation page.
• Validating and generating ODBC programs
If you're having problems validating and generating ODBC programs, you may need to turn on syntax checking to catch your errors.

The results of validation of SQL statements via ODBC is dependent on the ODBC driver implementation of the SQLPrepare ODBC API. This API is used by VisualAge Generator to validate SQL statements when using ODBC. However, according to the ODBC 2.0 standard (which VisualAge Generator conforms to), syntax checking of the SQL statement does not have to be done by the ODBC driver during a call to this API function. Some drivers do syntax checking and return errors on a call to this API while some defer it until a corresponding SQLExecute API call is made.

When using the DB2 ODBC driver, syntax checking can be turned on by setting the DEFERREDPREPARE environment variable to 0. The Oracle ODBC driver defers all syntax checking until the SQLExecute API. There is no way to alter this behavior.

Check with your ODBC vendor to determine the behavior of the SQLPrepare ODBC API in regards to syntax checking for your ODBC driver.

• Using ITF to Access Remote VSAM Relative Files on MVS
If you are accessing VSAM Relative files on MVS using ITF, there is a known problem when scanning the file sequentially. An EOF condition will be returned prematurely. The problem is under investigation.
 

VisualAge Generator FixPak2 Installation Notes

Installing VisualAge Generator Developer on VA Java

Important: Special steps to do before installation of Fixpak2 for Developer on Java:

VisualAge Generator Developer on Java FixPak1 is the pre-requisite for FixPak2. Please make sure you have installed FixPak1 of Developer on Java and FixPak1 for Common Services for NT. You may go to the FTP site ftp://ps.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files for FixPak1 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site. The readme.htm file in the directory has detailed instructions on FixPak1 installation.

• Please make sure you do not have VisualAge Generator Templates features loaded with your existing VisualAge Generator Developer on Java:
• Before installing FixPak2, you must first unload ALL of the VisualAge Generator features from your workspace and close the product saving the workspace.
• To install FixPak2:
• To install VAGen v4.0 FixPak2, download and run VAGenDevJavaFP2.EXE from the FTP site. The address of the FTP site is ftp://ps.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files for FixPak2 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site.
• FixPak2 for Common Services V4.0 is a prerequisite for running Developer with FixPak2. If you have not installed FixPak2 for Common Services yet, you will be able to install it by checking "Launch CSO installation" at the very last dialog box of Developer for Java installation. The files for installing FixPak2 for Common Services are already included in the package, so you do not have to download it separately.
• After installation, you need to add the VisualAge Generator V4.0 features. Then close the product and bring it back up.
• Sometimes after the installation of VisualAge for Java v3.02, if you bring up the product, an error message appears saying: Exit due to error: 34 - Read error occured while loading workspace. If you see this, your workspace IDE.icx is corrupted (you may verify this by checking if the IDE.icx's file size goes down to 0). To work around this, find the IDE.ZIP file on the VisualAge for Java installation CD in directory ivj30\backup, unzip the IDE.ICX file to IDE\program directory under the VisaualAge for Java install directory (e.g, if you installed VAJava in c:\IBMVJAVA, then unzip it to c:\IBMVJAVA\IDE\Program). This should restore a clean workspace.

Installing VisualAge Generator Developer on VA Smalltalk

Important: Special steps to do before installation of Fixpak2 for Developer on Smalltalk:

VisualAge Generator Developer on Smalltalk FixPak1 is the pre-requisite for FixPak2. Please make sure you have installed FixPak1 of Developer on Smalltalk and FixPak1 for Common Services, AND have loaded the VAGen features for 4.0 + FP1, before installing FixPak2. You may go to the FTP site ftp://ps.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files for FixPak1 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site. The readme.htm file in the directory has detailed instructions on FixPak1 installation.

• For Windows NT
• Download and run VAGenDevSmalltalkNTFP2.EXE from the FTP site. The address of the FTP site is ftp://ps.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files for FixPak2 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site.
• FixPak2 for Common Services V4.0 is a prerequisite for running Developer with FixPak2. If you have not installed FixPak2 for Common Services yet, you will be able to install it by checking "Launch CSO Installation" at the very last dialog box of Developer for Smalltalk installatin. The code for FixPak2 for Common Services is already included in the package, so you do not have to download it separately.
• After you install FixPak2 for VisualAge Generator Developer on Smalltalk V4.0, it becomes an available, loadable feature of VisualAge for Smalltalk. To complete the installation of VisualAge Generator V4.0 FixPak2, perform the following customization tasks:
1. Start VisualAge for Smalltalk.
2. Select Tools --> Load/Unload Features... on the System Transcript window.
3. On the Selection Required window, do the following:
4. Ensure that the Show other features check box is checked.
5. Select Other: VAGen Developer - FixPak2 from the Available features list. If you want to update other features included in the fixpak, please select them as well.
6. Click on the >> button to move Other: VAGen Developer - FixPak2 to the Loaded features list. If you selected other features, they will be moved as well.
7. Click on the OK button. The selected features will be imported and loaded into your image.
8. Once the selected features are loaded, you will be prompted to save your image. Press the Yes button. After the image is saved, you might want to make a copy of the image file just in case you need it later.
If you get a walkback (VisualAge Debugger) window while saving the image, it probably means that you have run out of disk space. Close the VisualAge Debugger window. You will need to either free some space and retry the save (File --> Save Image... on the System Transcript window) or save the image on another drive (File --> Save Image As...).
• For OS/2
• To download from FTP site:
1. Create a temporary directory on your hard drive.
2. Download the self-extracting executable VAGenDevSmalltalkOS2FP2.EXE to a temporary directory on your hard drive. The address of the FTP site is ftp://ps.software.ibm.com.  This site contains information and fixes for a wide variety of other IBM products.  The files for FixPak2 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site.
3. Extract the files contained in the self-extracting EXE files to a temporary directory by invoking with the -d switch from the command prompt.

For example: Type in VAGenDevSmalltalkOS2FP2.EXE -d c:\temp\FIXDEV on the command line.
• To install:
1. Run INSTALL.EXE from the directory <temp>\xxx\HPTDEVS2, where <temp> is the temporary directory you created to store FixPak2 files, and "xxx" is the 3-character NLS ID for your language.

For example: If your language is Japanese and the temporary directory you selected is called c:\temp\FIXDEV, you would enter the following command on the command line: c:\temp\FIXDEV\JPN\HPTDEVS2\INSTALL.EXE
• FixPak2 for Common Services V4.0 is a prerequisite for running Developer FixPak. The files for FixPak2 for Common Services are already included in the files you downloaded, so you do not have to donwload it separately.  Installation instructions for FixPak2 for CSO are contained below.
• After all the installation is completed, you may remove the temporary directory holding the installation files.
• After you install FixPak2 for VisualAge Generator Developer on Smalltalk V4.0, it becomes an available, loadable feature of VisualAge for Smalltalk. To complete the installation of VisualAge Generator V4.0 FixPak2, perform the following customization tasks:
1. Start VisualAge for Smalltalk.
2. Select Tools --> Load/Unload Features... on the System Transcript window.
3. On the Selection Required window, do the following:
4. Ensure that the Show other features check box is checked.
5. Select Other: VAGen Developer - FixPak2 from the Available features list. If you want to update other features included in the fixpak, please select them as well.
6. Click on the >> button to move Other: VAGen Developer - FixPak2 to the Loaded features list. If you selected other features, they will be moved as well.
7. Click on the OK button. The selected features will be imported and loaded into your image.
8. Once the selected features are loaded, you will be prompted to save your image. Press the Yes button. After the image is saved, you might want to make a copy of the image file just in case you need it later.


If you get a walkback (VisualAge Debugger) window while saving the image, it probably means that you have run out of disk space. Close the VisualAge Debugger window. You will need to either free some space and retry the save (File --> Save Image... on the System Transcript window) or save the image on another drive (File --> Save Image As...).

Installing VisualAge Generator Server

Important: Special steps to do before installation of Fixpak2 for Server:

VisualAge Generator Server FixPak1 is the pre-requisite for FixPak2. Please make sure you have installed FixPak1 of Server and FixPak1 for Common Services. You may go to the FTP site ftp://ps.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files for FixPak1 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site. The readme.htm file in the directory has detailed instructions on FixPak1 installation.

• For Windows NT
• Download and run VAGenServerNTFP2.EXE from the FTP site. The address of the FTP site is ftp://ps.software.ibm.com.  This site contains information and fixes for a wide variety of other IBM products.  The files for FixPak2 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site.
• FixPak2 for Common Services V4.0 is a prerequisite for running Server with FixPak2. If you have not installed FixPak2 for Common Services yet, you will be able to install it by checking "Launch CSO Installation" at the very last dialog box of Server installation. The files for FixPak2 for Common Services are already included in the package, so you do not have to download it separately.
• For OS/2 Warp
• To download from FTP site:
1. Create a temporary directory on your hard drive.
2. Download the self-extracting executable VAGenServerOS2FP2.EXE to a temporary directory on your hard drive. The address of the FTP site is ftp://ps.software.ibm.com.  This site contains information and fixes for a wide variety of other IBM products.  The files for FixPak2 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site.
3. Extract the files contained in the self-extracting EXE file to a temporary directory by invoking with the -d switch from the command prompt.

For example: Type in VAGenServerOS2FP2.EXE -d c:\temp\FIXWGS on the command line.
• To install:
1. Run INSTALL.EXE from the directory <temp>\xxx\HPTWGS2, where <temp> is the temporary directory you created to store FixPak2 files, and "xxx" is the 3-character NLS ID for your language.

For example: If you are using Brazilian Portuguese and the temporary directory you selected is called c:\temp\FIXWGS, you would enter the following command in the command line: c:\temp\FIXWGS\PTB\HPTWGS2\INSTALL.EXE
• FixPak2 for Common Services V4.0 is a prerequisite for running Developer with FixPak2. The files for FixPak2 for Common Services are already included in the files you downloaded, so you do not have to donwload it separately. Installation instructions for FixPak2 for CSO are contained below.
• After all the installation is completed, you may remove the temporary directory holding the installation files.
• For AIX
• To install:
1. Login to your AIX machine and create a directory named vgfixes (i.e. /home/user1/vgfixes).
2. Change to that directory.
3. Download the appropriate install image from the FTP site.
• vgwgs40.fp2 for systems that do NOT have CICS installed.
• vgwgs40t.fp2 for systems that DO have CICS installed.
4. SU to root.
5. Remove the previous version of VisualAge Generator Server with the following command:
• installp -u vgwgs40.obj
6. Whenever you remove VisualAge Generator Server for AIX from your system to install a FixPak and you also have an NLS image installed, you must do the following:
• Remove the NLS image
• Install the base FixPak image
• Re-install the NLS image. Instructions for removing and installing an NLS image are documented in the VisualAge Generator Installation Guide.
7. Install FixPak2 using the appropriate command:
• installp -ad vgwgs40.fp2 all   (non-CICS systems)
• installp -ad vgwgs40t.fp2 all   (CICS systems)
Note: The Common Services component is automatically installed when you install the Server component on AIX.
• For HP-UX
• To Install:
1. Login to your HP-UX machine and create a directory named vgfixes (i.e. /home/user1/vgfixes).
2. Change to that directory.
3. Download the install image from the FTP site.
• vgwgs40x.fp2.tar
4. SU to root.
5. Change your current working directory to /opt.
6. Whenever you remove VisualAge Generator Server for HP-UX from your system to install a FixPak and you also have an NLS image installed, you must do the following:
• Install the base FixPak image
• Re-install the NLS image. Instructions for installing an NLS image are documented in the VisualAge Generator Installation Guide.
7. Remove the previous version of VisualAge Generator Server for HP-UX with the following command:
• rm -rf /opt/vgwgs40
8. Install FixPak2 using the following command:
• tar -xvf /home/user1/vgfixes/vgwgs40x.fp2.tar
Note: The Common Services component is automatically installed when you install the Server component on HP-UX.
• For Solaris
• To install:
1. Login to your Solaris machine and create a directory named vgfixes (i.e. /home/user1/vgfixes).
2. Change to that directory.
3. Download the install image from the FTP site.
• vgwgs40t.fp2.tar
4. SU to root.
5. Change your current working directory to /opt.
6. Whenever you remove VisualAge Generator Server for Solaris from your system to install a FixPak and you also have an NLS image installed, you must do the following:
• Install the base FixPak image
• Re-install the NLS image. Instructions for installing an NLS image are documented in the VisualAge Generator Installation Guide.
7. Remove the previous version of VisualAge Generator Server for Solaris with the following command:
• rm -rf /opt/vgwgs40
8. Install FixPak2 using the following command:
• tar -xvf /home/user1/vgfixes/vgwgs40t.fp2.tar
Note: The Common Services component is automatically installed when you install the Server component on Solaris.

Installing VisualAge Generator Common Services

Important: Special steps to do before installation of Fixpak2 for Common Services:

VisualAge Generator Common Services FixPak1 is the pre-requisite for FixPak2. Please make sure you have installed FixPak1 of Common Services. You may go to the FTP site ftp://ps.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files for FixPak1 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site. The readme.htm file in the directory has detailed instructions on FixPak1 installation.

FixPak2 for Common Service is a prerequisite for running the other VisualAge Generator products with FixPak2. The FixPaks of the other VisualAge Generator products contain the files to install FixPak2 for Common Services. Therefore, you do not have to download the FixPak for Common Services separately if you have already downloaded the FixPak for any other VisualAge Generator product.

On Windows NT, you will be able to install FixPak2 for Common Services at the end of the installation of any other FixPak for VisualAge Generator when the Common Services FixPak2 hasn't been installed, by checking "Launch CSO installation", and the installation of FixPak2 for Common Services will launch automatically.

On OS/2, you will have to follow the steps below to install the FixPak2 for Common Services.

• For Windows NT
• Download and run VAGenCSONTFP2.EXE from the FTP site. The address of the FTP site is ftp://ps.software.ibm.com.  This site contains information and fixes for a wide variety of other IBM products.  The files for FixPak2 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site.
• For OS/2 Warp
• To download from FTP site:
1. Create a temporary directory on your hard drive.
2. Download the self-extracting executable VAGenCSOOS2FP2.EXE to a temporary directory on your hard drive. The address of the FTP site is ftp://ps.software.ibm.com.  This site contains information and fixes for a wide variety of other IBM products.  The files for FixPak2 are located in the directory /ps/products/visualagegen/fixes/v4.0. You may perform an anonymous logon to this FTP site.
3. Extract the files contained in the self-extracting EXE files to the temporary directory by invoking them with the -d switch from the command prompt.

For example: Type in VAGenCSOOS2FP2.EXE -d c:\temp\FIXCSO on the command line.
• To install:
1. Run INSTALL.EXE from the directory <temp>\xxx\HPTCSO2, where <temp> is the temporary directory you created to store FixPak2 files, and "xxx" is the 3-character NLS ID for your language.

For example: If you are using Korean and the temporary directory you selected is called FIXCSO, you would enter the following command in the command line: c:\temp\FIXCSO\KOR\HPTCSO2\INSTALL.EXE
• After all the installation is completed, you may remove the temporary directory holding the installation files.

VisualAge Generator Templates

Product Enhancements

Enhancements of the Browsers

Performance improvement.

Generated Web client

• New Naming Policy of the items in the UI-Record

The generated item names are more easy to read and take into account muliple displays in one single interface unit.
• New Hooks

Several new hooks are available in the web transaction to customize the initialization of the program, the server calls and the display.
• Concurrency management (timestamp or counter) is available in XFer & Converse.


Generation Improvement

Generation of 4GL components is faster.

Installation

 
• Adding the VisualAge Generator Templates feature on Java:
If you already have VAGT 'standard' feature loaded (4.0 or 4.0 Fixpak 1), then you should install an empty image. You can find an original ide.icx in the VisualAge for Java CD, in ivj30\backup directory.
The IBM VisualAge Generator feature is a prerequisite of VisualAge Generator Templates. If it is not already loaded, loading The VAGT standard feature will also load the IBM VisualAge Generator feature.
1. On the Workbench, select File>>Quick Start.
2. On the Quick Start dialog, select Features on the left. Add Feature on the right, and then select OK.
3. Select IBM VisualAge Generator Templates 4.0 + FP2, and select OK (this will take a few minutes).
4. Close the Workbench, and, then, close the Log. You will be prompted to save the workspace. Select OK to save the workspace.
• Loading the VisualAge Generator Templates feature on Smalltalk:
1. Before starting the workspace, you should consider saving a copy of the VisualAge Smalltalk image named abt.icx.
2. Start VisualAge for Smalltalk.
3. Select Tools>>Load/Unload Features... on the System Transcript.
4. In the Selection Required window:
1. Make sure that "Show other features" is checked.
2. Select Other: VAGTemplates 4.0 + FP2 from the Available features list.
3. Click on the OK button. VisualAge Generator Templates will be imported and loaded into your workspace. The load function will also ensure loading of the prerequisites, VisualAge ODBC Database and DB2 CLI Database. This could take up to half an hour to finish.

Once VisualAge Generator Templates is loaded, you will be prompted to save your image. Click the Yes button so you won't have to load VisualAge Generator Templates the next time you start VisualAge for Smalltalk. By default, the image is saved as filename abt.icx. After the image is saved, you might consider making a copy of the image file.

Limitations and Known Problems with VAGT

• VAGT Workbench:
• SQL low value and SQL high value (Workspace definition) are not exhaustively checked; these attributes should not be empty (space is a valid value).
• Web Generators:
• You will have to customize the code if you use more than one business object in one interface unit.
• The updatable lists are not available.
• GUI Generators:
•  The '4GL' Client Logic Style (Workspace Parameter) is not implemented.

• Generation:
• If you don't use the QuickStart or a VAGT workspace produced by the QuickStart, unload the project 'IBM VAGT QuickStart Runtime'.
• GUI Generators:
• On VisualAge for Java, you need to check 'Inherit BeanInfo of Bean superclass' in the panel 'Options', under 'Visual Composition' to have your generated GUI work properly.
• GUI online help generators are not available.
• Relational Table: The 'read' concurrency management is not supported by the client.
• No BiDi support.

• Installation:

After the load of the VAGT feature, the VisualAge Organizer may have lost the current user. Ensure to set a current user before using the VAGT feature (otherwise the menu items of the VAGT Tools menu will stay disabled).
• Generation:
• If you use a workspace that was not defined with the QuickStart, it is better to unload MdlQSRuntimeApp.
• Workspace: 'Target Services Application' and  'Target Visual Application'  parameters are not taken into account. Only 'target Logic Application' is used.
• Bidi:

Although VAGT is able to provide right-to-left organized views and subviews, it depends on the abilities of VisualAge Smalltalk BiDi feature for internal positionings:
• menus inside a menu bar
• columns insude a container
• tabs inside a notebook
• Database Management:

When connecting to the database, you may have database connections  left open (an error -1445 appears), you should clean up SQL database connections so you can execute the following code to clean up the SQL interface:
SQLRequester disconnectAll

Installation Troubleshooting

• If you get a installation error -115 during the installation, please reboot the machine and try the installation again. This condition occurs in isolated cases where there are stray processes running in the system.
• On NT, towards the end of the installation of Developer on Java or Smalltalk, a small command prompt window will come up with an empty screen. This is normal behavior. The installation program is configurating the Net Question help system on your behalf.
• After installing a VisualAge Generator FixPak and loading the FixPak feature, both the FixPak feature and the base product feature will appear in the Available features list instead for the Loaded features list in the Load/Unload Feature window. This is misleading as the features are actually loaded in the Smalltalk image. The FixPak files will overlay files in the file directory tree structure where your current VisualAge installation resides.

VisualAge Generator Redbook

Most of the VisualAge Generator manuals are installed with the online help in HTML format. They are also available in PDF format on the product CD. Updates for these books will be made periodically. The search capability has been enabled for Japanese online help. The most up-to-date versions are available for download at no cost from our website: http://www.ibm.com/software/ad/visgen/library/v4docs.html.
 

Useful Websites:

IBM VisualAge Generator http://www.software.ibm.com/ad/visgen/ IBM VisualAge Smalltalk http://www.software.ibm.com/ad/smalltalk IBM VisualAge Java http://www.software.ibm.com/vajava IBM VisualAge Resource Catalog http://www.software.ibm.com/ad/visage/rc IBM Software Applicaiton Development http://www.software.ibm.com/ad IBM Software Homepage http://www.software.ibm.com IBM Corporation Homepage http://www.ibm.com