IBM VisualAge Generator V4.5 FixPak2 Readme PTF #: UQ53913

This VisualAge Generator V4.5 FixPak2 Readme file contains the installation instructions, product support, and limitation information.
The VisualAge Generator V4.5 FixPak2 is cummulative and includes the V4.5 changes made for FixPak1. If you did not already have the V4.5 FixPak1 installed, you may install the V4.5 FixPak2 directly.

FixPak1

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

VAGen Java API updates

• The following APIs have been replaced:
  public static boolean addPartNameValidationHandler(String handlerClassName)
  public static boolean removePartNameValidationHandler(String handlerClassName)
  public static boolean addPartsMenuItem(String itemName, String listenerClassName, int enabled)
  public static boolean addPartsMenuItem(String itemName, String listenerClassName, String enablerClassName)
  public static boolean addToolsMenuItem(String itemName, String listenerClassName)
  public static boolean addToolsMenuItem(String itemName, String listenerClassName, String enablerClassName)
  
• The new APIs are as follows:
  public static void addPartNameValidationHandler(VAGenPartNameValidationHandler handler)
  public static boolean removePartNameValidationHandler(VAGenPartNameValidationHandler handler)
  public static void addPartsMenuItem(String itemName, VAGenActionListener listener, int enabled)
  public static void addPartsMenuItem(String itemName, VAGenActionListener listener, VAGenActionEnabler enabler)
  public static void addToolsMenuItem(String itemName, VAGenActionListener listener)
  public static void addToolsMenuItem(String itemName, VAGenActionListener listener, VAGenActionEnabler enabler)
  
• Previously a class name was passed in and an instance of the class was created automatically. Now an instance of the class must be created and passed as an argument. In addition, name validation handlers and additional menu items are no longer retained between product sessions. See below for information on how the VAGenStartupClass interface can be used to execute code each time the product is started.
  
• The following APIs have been added to allow the addition of menu items to the Packages menu of the VAGen Parts Browser.
  public static void addPackagesMenuItem(String itemName, VAGenActionListener listener, int enabled)
  public static void addPackagesMenuItem(String itemName, VAGenActionListener listener, VAGenActionEnabler enabler)
  public static void addPackagesMenuSeparator(String separatorName)
  public static boolean removePackagesMenuItem(String itemName)

FixPak2

General Improvement

• PQ45177 - Provide a web application archive file to deploy the VA Generator Gateway Servlet in a J2EE enabled application server
• PQ41261 - Request for improvements in VAGen - Map Editor
• PQ44780 - Wrapper for MVS batch routines that don't force long VG run-time initialization when first VG application is called.
• PQ44170 - If a program enters a bad transaction name, right now VG will cause the program to abnormally terminate. Change is to have option whereby customer can specify the name of an error/recovery routine to transfer control to.
• PQ45178 - Remove selected restrictions on what types of VG-generated programs can call each other (e.g. IMS/BMP, MVS TSO)

Linux/390 Tier 2 Gateway Support

• VisualAge Generator now supports LINUX for S/390 as a tier 2 for web transactions if the tier 3 is CICS for MVS/ESA. To make the new LINUX for S/390 functionality available, ask IBM support to provide the PTF that is referenced by APAR PQ48463.
• In addition to following the directions specified in that PTF, you must configure WebSphere Application Server and start the Session ID Manager.
  
  To set up WebShere Application Server on LINUX for S/390, access edition 3 of the Web Transaction Development Guide, chapter 7 ("Running a Web Transaction in WebSphere Application Server"). The document is available from this web site:
  
  http://www.ibm.com/software/ad/visgen/library/v45docs.html
  
  Follow the procedure stated in chapter 7, with the following changes for LINUX:
  
  a. The section titled "Define an application server, servlet engine, and web application to WAS" includes 16 steps. In step 12, if you are using a war file, you are directed to click "Finish" and to continue your deployment process at "Use a web application archive (war) file". However, on LINUX, the "Finish" box at step 12 is greyed out. You must continue through step 16, then go to the topology tree and delete the web application ("practice_app", for example). You can use a right mouse button on the application name and click "Remove".
  
  b. Under the heading "Complete the deployment" are six steps. At the end of step 2, you are directed to click Next. On LINUX, that click does NOT take you to the frame mentioned in step 3. In between, you are on the "Application Resources"
  frame. On that frame, select "default_host", click Next, and then you will be at the frame mentioned in step 3.
  
  The mechanism for starting the Session ID Manager is also defined in Chapter 7 of the VisualAge Generator Web Transaction Development Guide, in the section "Running a web transaction in WAS," subsection "Start the Session ID Manager." Follow the directions for Solaris.
  

VisualAge Generator Templates

Product Enhancements

Performance Enhancements

Enhancement of the Browsers

• Data Element, Value Table editing. The tabbing between the cells works correctly
• package and project names in the parameters editors are larger and fully visible
• Relational Import: Temporary Tables (DB2/MVS) can now be imported

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.

New with Fixpak 2

• Error Handling is improved.
• Value table management is improved. No duplicate of the current value.
• Help List display is improved. The current item position in the list is preserved.
• Column Labels are used in lists instead of default labels
• Access Level is taken into account in the lists. The definition of the UI-Record is thus optimized (less fields)

Generated GUI client

• The last page of the Help List is always accessible (sometimes, the next button was grayed too soon)
• Naming of the Java Classes: Naming Policy & layout suffix parameters are taken into account.

Generation Improvement
 

• Generation of 4GL components is faster.
• Display Names of the GUI generators is clarified (they are called GUI instead of Java)
• Display Names of the Generators in an unsupported Locale : The english display name is used, instead of the class name.

Limitations and Known Problems with VAGT

• Common Limitations

• 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 may have to customize the code if you use more than one business object in one interface unit. Various hooks are available.
  • The updatable lists are not available.
• GUI Generators:
  •  The '4GL' Client Logic Style (Workspace Parameter) is not implemented.

• Templates on Java Limitations

• 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.
  • Relational Table: The 'read' concurrency management is not supported by the client.

• Templates on Smalltalk Limitations

• 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 inside 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

FixPak1

• PQ43226 - PERFORMANCE IMPROVEMENTS FOR VISUALAGE GENERTOR DEVELOPER 4.5
• PQ42011 - VISUALAGE GENERATOR COBOL PROGRAMS USING MQ DO NOT CALL THE CORRECT RUNTIME MODULES.
• PQ43227 - MSL Migration on Java - you can save the sandbox, but when restored status info is lost
• PQ42561 - EXECMODE ESF ATTRIBUTE NOT EXPORTED FOR VISUALAGE GENERATOR PROGRAM.
• PQ43228 - Import of duplicate parts using the Defined option causes Image and Parts Browser to become out of sync.
• PQ42091 - User gets a KSH not found error when trying to start the prep on OS390.
• PQ43235 - COMMAND FILE TO EXECUTE VISUALAGE GENERATOR LAN AND BATCH GENERATIONS CONTAINS ERRORS.
• PQ42906 - EXECUTING HPTCNV45 RESULTS IN DLL NOT FOUND ERROR FOR PROGRAM CSO40API.
• PQ42637 - CALL CREATX and AUDIT FAIL VALIDATION WITH error 753.E.
• PQ42096 - COBOL Generation fails when a first UI or first map contains an edit routine invoking other functions
• PQ43352 - Incorrect EZERTN behavior for I/O option

FixPak2

• PQ33754 - MIGRATION OF VISUALAGE GENERATOR 3.1 APPLICATION FAILS WHEN
• PQ34169 - NIL VALUE SENT TO A FORMATTED TEXT FIELD FROM A VARIABLE
• PQ35098 - USING CAST SPECIFICATION WE RECEIVE SQLCODE -501
• PQ35385 - WHEN GENERATING A TUI PART TO A DLL, THE CUSTOMER IS RECEIVING
• PQ35833 - BLANK ERROR PROMPT DISPLAYED FOR TRAP AFTER CSOTROUT ERROR
• PQ37422 - WALKBACK DEBUGGER WHEN MIGRATING VISUALAGE GENERATOR ESF INTO
• PQ37906 - MIGRATION TOOL UNABLE TO PROCESS ESF FILE THAT CONTAINS A
• PQ38022 - LIKE predicate gets invalid data when a host variable is used
• PQ38380 - DEFAULT DB CONNECTION ATTEMPTED EVEN IF EZERSQLDB IS NOT SET
• PQ38385 - WALKBACK WHEN MIGRATING VA GEN 2.2 ESF TO VA GEN 4.0.
• PQ38515 - USING MIGRATION TOOL V3 TO V4 MIGRATION RESULTS IN ERROR
• PQ38809 - STARTING VGPARTS BROWSER CAUSES WALKBACK AND IMG MUST BE RESTAR
• PQ39119 - NLS characters not folded to uppercase
• PQ39164 - CONNECTIONS DO NOT SWITCH IF FCWDBNOOP=YES FOR NT/CICS
• PQ39206 - CONNECTIONS DO NOT SWITCH IF FCWDBNOOP=YES FOR NT/CICS
• PQ39326 - IDE.EXE NOT STOPPED AFTER THE HPTCMD STOP COMMAND IS ISSUED.
• PQ39892 - INCORRECT OUTPUT WHEN PASSING PARAMETERS TO A FUNCTION AND THE
• PQ40185 - SQLCODE -805 WHEN VISUALAGE GENERATOR C++ PROGRAM ATTEMPTS
• PQ40607 - COMPILE FAILURE WHEN ASSIGNING CHA TO SQLHEX
• PQ40609 - CUSTOMER FAILS ON GENERATION WHEN SQL STATEMENT IS INVALID.
• 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
• PQ40759 - VALIDATION FAILS AFTER CHANGING VG PART EVEN IF PART IS VALID
• PQ40869 - EXCLDTKEYNOTFOUND ERROR IN HPTADVISEREGISTRAR USING PLP FOR GEN
• PQ41180 - WALKBACK WHEN OPENING MSL MIGRATION WINDOW W/ EMPTY SAND.BOX
• PQ41261 - WALKBACK WHEN USING CTRL+3 TO INSERT A FIELD IN MAP EDITOR
• PQ41751 - PIC S9(19) GENERATED FOR TEMP HOST VAR FOR PACK(18) DATA ITEM
• PQ42136 - CALL STATEMENT PASSING EZEDLPCB(0) AS A PARAMETER RESULTS IN
• PQ42483 - ORACLE OS/390 PRECOMPILER FAILS WHEN PROCESSING COBOL PROGRAM
• PQ42636 - C++ gen should not split strings when max line length exceeded
• PQ42645 - TEST FACILITY DOES NOT RECEIVE FOCUS WHEN TESTING PROGRAM
• PQ42745 - MSGDFH7037I ISSUED WHEN USING CICS TRANSLATOR TO PREPARE A
• PQ42793 - COMPILE ERROR IGYPS2011-E ISSUED WHEN COMPILING VISUALAGE
• PQ42796 - DATA FROM UNICODE CLIENT PASSED TO EBCDIC SERVER NOT TRANSLATTE
• PQ42866 - WHEN CUSTOMER SETS SQL RECORD EMPTY, NULLS OUT FIELDS.
• PQ42914 - FILE IN USE CONDITION RETURNED WHEN ATTEMPTING TO PERFORM
• PQ43103 - DOC APAR FOR ERRORS IN WEB TRANSACTION MANUAL
• PQ43150 - PACKAGES NOT REFRESHED IN PARTS BROWSER WHEN PARTS COPIED
• PQ43227 - MSL Migration on Java -- you can save the sandbox, but
• PQ43228 - Import of duplicate parts using the Defined option causes Image
• PQ43319 - HPT.CG.62.E MESSAGE GENERATING WITH LOCAL RECORD ITEMS
• PQ43352 - Incorrect EZERTN behavior for I/O option
• PQ43365 - WHEN USING EZESCMPR IN ITF WITH AN INVALID DBCS INDEX THE RC IS
• PQ43445 - NULLPOINTEREXCEPTION IF TRAILING SPACES IN PROPERTIES FILE
• PQ43523 - EMSRV50.DLL NOT SHIPPED WITH PRODUCT - REQUIRED FOR MIGRATION
• PQ43593 - REMOTE VSAM FOR VSE DOES NOT WORK
• PQ43594 - A PACKAGING PROBLEM PREVENTS THE NEW ONLINE HELP GUI GENERATORS FROM WORKING
• PQ43595 - LOCKING PROBLEM WHICH CAUSES GUI UPDATE TO BE LOST.
• PQ43605 - EZEWAIT CREATES ERROR FOR ITF IF MQSERIES SAMPLE PROGRAM ALTERS
• PQ43606 - CSOSessionManager should search CLASSPATH for properties file.
• PQ43609 - Java servers can't be called using the CSOSessionManager over T
• PQ43613 - CSOUILISTENER AND TCPLISTENER DO NOT SEEM TO RECOGNIZE -D
• PQ43615 - CSOUILISTENER AND TCPLISTENER ERROR MESSAGE DOES NOT DISTINGUIS
• PQ43616 - CSOUILISTENER AND TCPLISTENER: DOC SHOWS C:\\XXX\... WHICH DOE
• PQ43618 - WEBSPHERE ISSUES A SECURITY ERROR IN CONNECTION WITH
• PQ43619 - TEMPLATED GENERATE OF GUI RESULTS IN AN ERROR
• PQ43620 - GENERATE OF GUI (LIST,DETAIL), OVERWRITE, ASSOCIATES+PREDEFINED, VISUALS+CLIENT RESULTS IN "INTROSPECTION ERROR ON GETBEANINFO
• PQ43621 - VISUALAGE GENERATOR 4.0 MIGRATION TOOL FAILS TO MIGRATE MAP PAR
• PQ43624 - TEMPLATES SHOWS HRSTASERRORVIEWBEANINFO ON ERROR PAGE FROM WORKSTATION BROWSER
• PQ43625 - GUI ZOOM DOES NOT WORK
• PQ43651 - NRF RETURNED WHEN PERFORMING INQUIRY AGAINST REMOTE RRDS
• PQ43655 - PROGRAM HANGS ON TCPIP CALL
• PQ43666 - WALKBACK IN GENERATION WHEN USING PGMNAME.BND NEEDS TO CONTAIN
• PQ43668 - README AND ANNOUNCEMENT LETTER FOR HW/SW REQUIREMENTS FOR VAGEN
• PQ43673 - EZEAID NOT SET CORRECTLY IN JAVA WEB TRANSACTIONS
• PQ43674 - JAVA GENERATED FROM ITEM1[ITEM2] DOESN'T COMPILE IF ITEM2 IS AN
• PQ43675 - GENERATE AN INDEX WHEN THE SUBSCRIPT METHOD IS USED.
• PQ43676 - ERROR IF . APPEARS AFTER A QUOTES VALUE IN LINKAGE TABLE FILES.
• PQ43678 - CALLABLE ITF: WILL NOT REPOSITION, BUTTON APPEARS BUT DOES
• PQ43680 - CALLABLE ITF: SUBMIT VALUES NOT BEING INITIALIZED IN RECEIVING
• PQ43683 - IF THE PACKAGE WHEN DEFINING A NEW VAGEN PART, IS A SCRATCH
• PQ43688 - TEMPLATES - LIST PREFILL AND AUTOSCROLL OPTIONS CANNOT BE USED TOGETHER FOR GUIS
• PQ43689 - NEED TO INVESTIGATE SCENARIO 5 OF EJB'S IN THE CLIENT SERVER
• PQ43690 - IN AN MQSERIES PROGRAM, WHEN RETURN CODE 2058 OR 2059 IS RECVD,
• PQ43693 - VAGT'S OS/2 HELP SEARCH FUNCTION DOES NOT WORK BECAUSE THE
• PQ43911 - WALKBACK IN V3 TO V4 MIGRATION IF CLASS OWNER HAD BEEN DELETED
• PQ43947 - Templates generation hangs in VAGen library save
• PQ44156 WALKBACK WHEN CALLING EXTERNAL PGM AND PASSING EZEDLPCB
• PQ44165 - MAP NUMERIC FIELD DEFAULT VALUE FOR SIGN CHANGED TO LEADING
• PQ44170 - If a program enters a bad transaction name, right now VG will cause the program to abnormally terminate. Change is to have option whereby customer can specify the name of an error/recovery routine to transfer control to.
• PQ44170 - REQUEST AGAINST COBOL GENERATOR
• PQ44184 - VALUE GENERATED FOR FILLER ITEMS FOR OS/400 CAN BE greater 16 CHARS
• PQ44246 - DATA CONNECTIONS DON'T FIRE AFTER PROGRAM HAS EXECUTED
• PQ44376 - HELP MAP GROUP NOT REMOVED WHEN CHANGING PROGRAM TYPE
• PQ44427 - ALLOW VISUALAGE GENERATOR PROGRAMS TO HANDLE A TRANSFER TO AN
• PQ44450 - VISUALGENERATOR V4.0: ERROR RECEIVED DURING VALIDATE OF A
• PQ44482 - RETURN CODE = -1 IS RETURNED ON FTPPUT WHEN TRANSFERRING FROM
• PQ44574 - Fix EZEDEST Processing
• PQ44582 - OS/400 VSAM IS NOT A VALID OPTION FOR RELATIVE RECORDS IN RAF
• PQ44633 - ARRAYINDEXOUTOFBOUNDS ERROR IF SERVERID IS BLANK
• PQ44735 - USER RECEIVES A DUPLICATE RC WHEN USING VSAM ACCESS.
• PQ44740 - ERROR SUBMITTING REXX PROGRAM TO COMPILE and LINK VISUALAGE
• PQ44780 - Wrapper for MVS batch routines that don't force long VG run-time initialization when first VG application is called.
• PQ44823 - WHEN A REFERENCE IS CHANGED VIA VAGEN PARTS BROWSER, IE AA TO B
• PQ44959 - MIGRATION TOOL INDICATES MIGRATION STATUS IS "MIGRATED" EVEN
• PQ45106 - VAGENDATAITEM NEW EDITION CREATED WHEN SHARED ITEM SAVED AS PAR
• PQ45154 - AFTER APPLYING PATCH2 FOR VAJAVA V3.5 AND FixPak2 FOR VAGEN AND VAGT CUSTOMIZER, THE VAG TEMPLATES BROWSER HANGS CLOSING WINDOW
• PQ45177 - Provide a web application archive file to deploy the VA Generator Gateway Servlet in a J2EE enabled application server
• PQ45178 - Remove selected restrictions on what types of VG-generated programs can call each other (e.g. IMS/BMP, MVS TSO)
• PQ45217 - VAGEN V3 TO V4 MIGRATION TOOL IGNORES PROJECT NAME USER SELECTS
• PQ45396 - DEFAULT LINKAGE VALUES NOT ASSUMEDFORINKTYPE=REMOTE ON CICS
• PQ45434 - Fix generated Java code for num literal/char item comparison
• PQ45436 - CONTABLE=CSOI1252 (CSOCALL, TCPIP) IS REQUIRED FOR VAGT GUI BUT
• PQ45472 - VAGEN TEMPLATES: WORKBENCH DATA ELEMENT VALUE TABLES. TABBING DOES NOT WORK
• PQ45473 - VAGEN TEMPLATES: WORKBENCH RELATIONAL TABLE PARAMETER. TABLE QUALIFIER DEFAULT VALUE SHOULD BE EDITABLE
• PQ45474 - VAGEN TEMPLATES: WORKBENCH PARAMETERS. TARGET PACKAGES AND PROJECTS ARE NOT FULLY VISIBLE
• PQ45474 - VAGEN TEMPLATES: WORKBENCH PARAMETERS. TARGET PACKAGES AND PROJECTS ARE NOT FULLY VISIBLE.
• PQ45475 - VAGEN TEMPLATES: VAGT IMPORT. CANNOT IMPORT TEMPORARY TABLES (DB2/MVS)
• PQ45476 - VAGEN TEMPLATES: SELECT GENERATOR WINDOW. ERGONOMICS TO IMPROVE
• PQ45478 - VAGEN TEMPLATES: MULTIPLE GENERATION OF SAME COMPONENT NOT DETECTED
• PQ45479 - VAGEN TEMPLATES: GENERATION. MISSING API IN THE BUILDERS GETSTORESTATUS SETSTORESTATUS
• PQ45480 - VAGEN TEMPLATES: JAVA GENERATED APPLICATION. HELP LIST READ NEXT SHOULD BE DISABLED AT THE BOTTOM OF THE LIST
• PQ45481 - VAGEN TEMPLATES: JAVA GENERATED APPLICATION PARAMETER NAMING POLICY NOT USED FOR CLASSES
• PQ45482 - VAGEN TEMPLATES: WEB GENERATED APPLICATION ORDER WAS NOT KEPT IN HELP LIST FOR CURRENT ITEM
• PQ45483 - VAGEN TEMPLATES: WEB GENERATED APPLICATION ERROR AND INFORMATION DISPLAY TO IMPROVE
• PQ45484 - VAGEN TEMPLATES: WEB GENERATED APPLICATION: PARAMETER COLUMN LABEL NOT USED IN LISTS
• PQ45486 - VAGEN TEMPLATES: WEB GENERATED APPLICATION: CASE CONTROL UPPERCASE NOT USED
• PQ45487 - VAGEN TEMPLATES: WEB GENERATED APPLICATION. VALUE TABLE. THE CURRENT ITEM IS DISPLAYED TWICE IN THE LIST
• PQ45489 - Record names being generated in templates.
• PQ45491 - Cobol generation calls module CMMIEND
• PQ45500 - WHEN AN ERROR OCCURS SAVING CHANGES, THE EDITOR WINDOW CLOSES AND ALL CHANGES ARE LOST.
• PQ45638 - QUICKFORM OF VISUALAGE GENERATOR VARIABLE PART CREATES THE GUI
• PQ45687 - Remove table label from UPDATE clause
• PQ45767 - CICS Y2K Fix
• PQ45864 - C++ COMPILER ERRORS WHEN USING EZEFLO
• PQ45903 - VAGEN: UI RECORD CONTAINING 0.00 VALUE DISPLAYS 0.0 UNDER V4.5
• PQ45940 - SQLCODE100 WHEN USING LIKE PREDICATE IN WHERE CLAUSE DEFINED IN SQLROW RECORD DEFAULT SELECTION CONDITIONS
• PQ46089 - ESF Export incorrectly handles the tab character
• PQ46184 - User receives and error when saving a part that has a call
• PQ46290 - EZELTERM AS APP CONSTRUCTOR PARM CAUSES ILLEGAL MEMORY ACCESS
• PQ46293 - Key stroke combination of ALT+F does not produce the correct output
• PQ46491 - SUPPORT FOR OS/2 AS MID-TIER FOR WEB TRXN
• PQ46574 - Poor performace when Test Facility calls another VAGEN program
• PQ46739 - VAGEN V4.5: PART LIST SELECTION CRITERIA VIEW WINDOW DOES NOT
• PQ46780 - MIGRATION TOOL GETS A GPF WHEN A LARGE NUMBER OF PARTS ARE MI
• PQ46802 - Walkback (HptTpPcbNodeModel does not understand segmentModelNamed:)
• PQ46841 - MSGFCW0079E ISSUED WHEN RUNNING VISUALAGE GENERATOR C++ PROGRAM
• PQ46872 - VAGEN TEMPLATES: WALKBACK: APPLICATION CLASS DOES NOT UNDERSTAND PREREQUISITE WHEN MIGRATING APPLICATION/SUBAPPLICATIONS FROM 3.1

Important Information

Installing VisualAge Generator Developer on VA Java

The following sections provide detailed instructions for downloading and installing FixPak2 for VisualAge Generator V4.5. Please be sure to read the sections carefully before you install this FixPak. 

Important: If you have an existing repository and want to continue using it, please make sure you back it up before you perform any migration. Before you install FixPak2, you must first install VisualAge for Java 3.5.3. Please refer to the Java 3.5.3 Installation and Migration Guide for information on how to migrate to VisualAge for Java 3.5.3. There are sections in that guide on migrating an existing shared repository.
The VisualAge for Java 3.5.3 updates can be found at: http://www.software.ibm.com/vadd

Installing VisualAge Generator Developer on VA Java

• Upgrade Install
  • If you have VisualAge for Java 3.5 and VisualAge Generator Developer on Java 4.5 installed, and you have also loaded VAGen features, you need to do an Upgrade install.
  • To install FixPak2:
    • FixPak2 for Common Services V4.5 is a prerequisite for running Server with FixPak2. If you have not installed FixPak2 for Common Services yet, you need to download CSONT.EXE from the FTP site and run it. Read Installing VisualAge Generator Common Services section for details.
    • Install VisualAge for Java 3.5.3. It will post a warning about migration during the install. If you have followed the VisualAge for Java 3.5.3 migration instructions, click "Yes". Otherwise, click "No".
    • Let VisualAge for Java 3.5.3 install and migrate automatically. When installing, the repository server and directories should be the same as that for your VisualAge for Java 3.5.
    • Start VisualAge Generator Developer on Java. Delete VAGen features in the following order:
      1. Delete VisualAge Generator Templates QuickStart (if it was loaded)
      2. Delete VisualAge Generator Templates (if it was loaded)
      3. Delete VisualAge Generator Utilities
      4. Exit VisualAge Generator Developer on Java, and restart it
      5. Delete VisualAge Generator
      6. Exit VisualAge Generator Developer on Java.
    • Install VAGen V4.5 FixPak2 by downloading DEVJAVANT.EXE from the FTP site and run it. 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.5/fixpak2/nt. You may perform an anonymous logon to this FTP site. During the install, if prompted to overwrite existing files, please type "a" to continue.
    • Start VisualAge Generator Developer on Java, and load VAGen 4.5 + FP2 features.

• New Install
  • If you do not have VisualAge for Java 3.5 and VisualAge Generator Developer on Java 4.5 installed, you need to do a new install.
  • To install FixPak2:
    • Install VisualAge for Java 3.5.3.
    • Download INSTALLONVAJ353.EXE from the FTP site to the machine where you will be installing VisualAge Generator 4.5 on Java.
    • 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. This file (INSTALLONVAJ353.EXE) and those for FixPak2 are located in the directory /ps/products/visualagegen/fixes/v4.5/fixpak2/nt. You may perform an anonymous logon to this FTP site. During the install, if prompted to overwrite existing files, please type "a" to continue.
    • Run INSTALLONVAJ353.EXE.
    • Install VisualAge Generator 4.5.
    • Install VAGen v4.5 FixPak2 by downloading DEVJAVANT.EXE from the FTP site and run it.
    • Start VisualAge Generator Developer on Java, and load VAGen 4.5 + FP2 features.

Installing VisualAge Generator Developer on VA Smalltalk

• For Windows NT
  • Download DEVSTNT.EXE from the FTP site and run it. During the install, if prompted to overwrite existing files, please type "y" or "a". 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.5/fixpak2/nt. You may perform an anonymous logon to this FTP site.
  • FixPak2 for Common Services V4.5 is a prerequisite for running Developer with FixPak2. If you have not installed FixPak2 for Common Services yet, you must download CSONT.EXE from the FTP site and run it. Read Installing VisualAge Generator Common Services section for details.
  • After you install FixPak2 for VisualAge Generator Developer on Smalltalk V4.5, you need to load the fixpak2 features by performing 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 the features with FP2 suffix 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 the feature 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.

• For OS/2
  • To download from FTP site:
    1. Create a temporary directory on your hard drive.
    2. Download the self-extracting executable DEVSTOS2.EXE to the 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.5/fixpak2/os2. 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 -dswitch from the command prompt.
       For example:Type in DEVSTOS2.EXE -d c:\temp\FIXDEV on the command line.
  • To install:
    • 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.5 is a prerequisite for running Developer FixPak. you need to download CSOOS2.exe and run it separately.  Installation instructions for FixPak2 for CSO are contained below.
    • After 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.5, it becomes an available, loadable feature of VisualAge for Smalltalk. To complete the installation of VisualAge Generator V4.5 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 (abt.icx) just in case you need it later.

  Installing VisualAge Generator Server

  • For Windows NT
    • Download SERVERNT.EXE from the FTP site, and run it. 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.5/fixpak2/nt. You may perform an anonymous logon to this FTP site.
    • FixPak2 for Common Services V4.5 is a prerequisite for running Server with FixPak2. If you have not installed FixPak2 for Common Services yet, you need to download CSONT.EXE from the FTP site and run it. Read Installing VisualAge Generator Common Services section for details.
  • For OS/2 Warp
    • To download from FTP site:
      1. Create a temporary directory on your hard drive.
      2. Download the self-extracting executable SERVEROS2.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.5/fixpak2/os2. 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 -dswitch from the command prompt.
         For example:Type in SERVEROS2.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.5 is a prerequisite for running Developer with FixPak2. you need to download CSOOS2.EXE from the FTP site and run it. Read Installing VisualAge Generator Common Services section for details.
    • 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. The files for FixPak2 are located in the directory ftp://ps.software.ibm.com/ps/products/visualagegen/fixes/v4.5/fixpak2/aix.
         • vgaix45.fp02 for systems that do NOT have CICS installed.
         • vgaix45t.fp02 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 vgwgs45.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 vgaix45.fp02 all   (non-CICS systems)
         • installp -ad vgaix45t.fp02 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.
         • vghp45.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/vgwgs45
      8. Install FixPak2 using the following command:
         • tar -xvf /home/user1/vgfixes/vghp45.fp2.tar
      Note: The Common Services component is automatically installed when you install the Server component on HP-UX.
  • For SCO
    • To install:
      1. Login to your SCO 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.
         • vgsco45.fp2.tar
      4. SU to root.
      5. Change your current working directory to /opt.
      6. Whenever you remove VisualAge Generator Server for SCO 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 SCO with the following command:
         • rm -rf /opt/vgwgs45
      8. Install FixPak2 using the following command:
         • tar -xvf /home/user1/vgfixes/vgsco45.fp2.tar
      Note: The Common Services component is automatically installed when you install the Server component on SCO.
• 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.
       • vgsol45.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/vgwgs45
    8. Install FixPak2 using the following command:
       • tar -xvf /home/user1/vgfixes/vgsol45.fp2.tar
    Note: The Common Services component is automatically installed when you install the Server component on Solaris.

Installing VisualAge Generator Common Services

FixPak2 for Common Service is a prerequisite for running the other VisualAge Generator products with FixPak2. You will have to follow the steps below to install the FixPak2 for Common Services.

• For Windows NT
  • Download CSONT.EXE from the FTP site, and run it. 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.5/fixpak2/nt. 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 CSOOS2.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.5/fixpak2/os2. 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 -dswitch from the command prompt.
       For example:Type in CSOOS2.EXE -d c:\temp\FIXCSO on the command line.
  • To install:
    • 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.

Installation Troubleshooting

• If you install VisualAge for Java 3.5.3 for remote repository, when loading VAGen 4.5 features, The following messages will appear in the Log panel. These messages can be ignored:

  Message in Log when IBM VisualAge Generator 4.5 + FP2 feature added:

  No resources were retrieved for IBM VisualAge Generator Runtime V4.5 FP2 because the store path ..\ivj.dat.pr\IBM VisualAge Generator Runtime\20000912.143817 does not exist on the server ...

  Message in Log when IBM VisualAge Generator Utilities 4.5 + FP2 feature added:

  No resources were retrieved for IBM VisualAge Generator Runtime V4.5 FP2 because the store path x:\xxxx\ivj.dat.pr\IBM VisualAge Generator Runtime\20000912.143817 does not exist on the server ...

  Messages in Log when IBM VisualAge Generator Templates 4.5 + FP2 feature added:

  No resources were retrieved for IBM VisualAge Generator Runtime V4.5 FP2 because the store path x:\xxxx\ivj.dat.pr\IBM VisualAge Generator Runtime\20000912.143817 does not exist on the server ...
  No resources were retrieved for IBM VAGT Emitting Services V4.5.V02a because the store path x:\xxxx\ivj.dat.pr\IBM VAGT Emitting Services\20010223.112515 does not exist on the server ...
  No resources were retrieved for IBM VAGT Model Services V4.5.V02a because the store path x:\xxxx\ivj.dat.pr\IBM VAGT Model Services\20010223.110835 does not exist on the server ...
  No resources were retrieved for IBM VAGT Runtime V4.5.V02a because the store path x:\xxxx\ivj.dat.pr\IBM VAGT Runtime\20010223.111743 does not exist on the server ...

  Messages in Log when IBM VisualAge Generator Templates Quickstart 4.5 + FP2 feature added:

  No resources were retrieved for IBM VisualAge Generator Runtime V4.5 FP2 because the store path x:\xxxx\ivj.dat.pr\IBM VisualAge Generator Runtime\20000912.143817 does not exist on the server ...
  No resources were retrieved for IBM VAGT Emitting Services V4.5.V02a because the store path x:\xxxx\ivj.dat.pr\IBM VAGT Emitting Services\20010223.112515 does not exist on the server ...
  No resources were retrieved for IBM VAGT Model Services V4.5.V02a because the store path x:\xxxx\ivj.dat.pr\IBM VAGT Model Services\20010223.110835 does not exist on the server ...
  No resources were retrieved for IBM VAGT Runtime V4.5.V02a because the store path x:\xxxx\ivj.dat.pr\IBM VAGT Runtime\20010223.111743 does not exist on the server ...
  No resources were retrieved for IBM VAGT QuickStart Runtime V4.5.V02a because the store path x:\xxxx\ivj.dat.pr\IBM VAGT QuickStart Runtime\20010223.115618 does not exist on the server ...

VisualAge Generator Templates Installation

• Adding the VisualAge Generator Templates feature on Java:If you already have VAGT 'standard' feature loaded (4.5 or 4.5 Fixpak 1), then you should install an empty image. You can find an original ide.icx in the VisualAge for Java CD, in ivj353\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.5 + 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.5 + 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.