IBM VisualAge Generator V3.0 Fixpak5 Readme

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

Product Enhancements, Problem Support, and Limitations

VisualAge Generator V3.0 Fixpak5 contains enhancements, problem support, and limitations for the following:

Euro Monetary Unit Support
List of APARs

Euro Monetary Unit Support

With Fixpak5, VisualAge Generator V3.0 supports the Euro currency symbol.

Support for the Euro currency symbol in VisualAge Generator includes:

Single currency symbol support - enabling the use of the Euro as the currency symbol when displaying monetary values.
Supporting Euro symbol conversion between client and server code pages

Prerequisites

The following are prerequisites for the Euro support:

If you plan to use the Euro currency symbol, all products must be at the latest maintenance level.
OS/390 systems will require an APAR to generate COBOL that enables the use of the Euro symbol. This APAR is available only with LE COBOL, not COBOL II. If you are using the Euro, you must use LE COBOL.
Install the Euro support fixpaks for your Windows 3.1, Windows 95, or OS/2 system.
For the Host COBOL user (those using PCOMM), install the latest fixpak for PCOMM (for OS/2) to enable the following:
- The correct uploading of COBOL source containing the Euro dollar
- The correct Euro symbol to be displayed when using the emulator sessions (this assumes that you have the correct Euro support installed on the operating systems, PC, and host).
If you are a VisualAge Generator Server customer on MVS, VM, or VSE and you wish to use the Euro currency symbol in terminal map edits, you need to change your currency symbol in the NLS installation options. Refer to the Program Directory for your environment for more information. This only allows a single currency symbol to be used by the installation. At a later date, a VisualAge Generator Server PTF will be provided that will enable the currency symbol to be picked up from the generated code instead of from the NLS installation options.

Currency Symbol Support during Test

To use the Euro currency symbol while testing your programs, set the EZERCURRENCY environment variable to the currency symbol you want your programs to use. The value you specify for the currency symbol must be a single character and can be enclosed in single quotes. However, you cannot use quotes as a value for the currency symbol.

Currency Symbol Support during Generation

In VisualAge Generator, the currency symbol for each program or map is determined by the value of the /CURRENCY=x generation option. If you do not specify anything for the /CURRENCY generation option, the default currency symbol is determined by the system locale.

To specify the currency symbol from the VisualAge Generator user interface, select Set Options, then Generated Code and specify the currency symbol in the currency field. Remember, the currency symbol value must be a single character and can be enclosed in single quotes. However, you cannot use quotes as a value for the currency symbol.

Euro On OS/2 With U.S. English

Euro is not supported on U.S. English code page 437. Run OS/2 with code page 850 to use the Euro currency symbol. If you switch from 437 to 850, use the Brazilian Portuguese conversion table ELACNPTB instead of the default ELACNENU when generating programs for or calling servers on a U.S. English host system. Use conversion table ELAWI850 when generating for or calling servers on Windows systems.

Typing the Euro Currency Symbol

To type the Euro currency symbol from a keyboard that does not have a Euro keycap, do the following:

Determine the type of operating system you are using (IBM or Microsoft).
Press and hold the Alt button, type the decimal value for the Euro currency symbol using the numeric keypad (For the IBM system, specify the decimal value 0213. For the Microsoft system, specify the decimal value 0128.), then release the Alt button.

Euro Fonts Installation

For Windows NT, when you install the NT support via the Euro-only support, you must install the fonts that contain the Euro currency symbol. If you install the entire NT ServicePak, you automatically get the fonts.

For OS/2 , the only way to install the Euro support is from the fixpak. You get all the required fonts by default. In the VisualAge Generator product, you must select a font that contains the Euro for Map definition, Test Monitor, and Map Monitor. MONOTYPE.COM is a good choice.

How to Get the Euro Support

The following list describes how you can get the Euro currency symbol support for installation on the various environments.

For OS/2 Warp 3.0, you must install Fixpak35 or greater
For OS/2 Warp 4.0, you must install FixPak6 or greater
For Windows NT 4.0, you can either install the Euro-Only support from the NT ServicePak or install ServicePak3
For VisualAge for COBOL, you must install version V2R2. (2.2)
For Host LE COBOL, for MVS and VM, you must install version V1R2. (1.2) with APAR PQ16766
For Host LE COBOL, for OS/390 and VM, you must install version V2R1. (2.1) with APAR PQ16766
For IBM VisualAge for C++ for Windows, you must install Version 3.5
For the C Compiler for AIX, you must install version 3.1.4.7
For the C Set ++ Compiler for AIX, you must install version 3.1.4.6

Fixpak5 List of APARs

The following is a list of APARs in Fixpak5:

PQ11030: ASSOCIATE FILE NOT FOUND WHEN LANG IS SET TO TR_TR
PQ12734: MESSAGE LOG THAT IS DISPLAYED IN THE VIEW MESSAGES DIALOG IS INCORRECT WHEN GENERATING MULTIPLE VISUALAGE GENERATOR PROGRAMS
PQ13156: VAGEN EDIT MASK DOES NOT ALLOW USER TO ENTER BLANK DATE
PQ13315: ERROR 'MUST BE A BOOLEAN' WHILE GENERATING VISGEN 3.0 APPLICATION
PQ13475: INCORRECT PERFORM OF A STATEMENT GROUP CAUSES A WALKBACK
PQ13703: VG VALIDATION/GENERATION SQL CODE ERROR(DATE)
PQ13726: DATE FIELD WITH 7 BYTES PACKED FIELD
PQ14247: VISUALAGE GENERATOR'S TEST FACILITY SHOULD ALLOW TESTING OF RECURSIVE PROGRAMS.
PQ14214: ENTERING AN INCORRECT PASSWORD WHEN USING CSOPRMPT.DLL FOR VAGEN PROMPT ON CICS - ABENDUAEY7
PQ14525: TWO RECORDS POINT TO SAME FILE BUT DEFINE DIFF ORG FOR THE FILE.
PQ14380: UNABLE TO VALIDATE MULTIPLE PROGRAM PARTS AT THE SAME TIME AFTER APPLYING FIXPAK2 TO VISUALAGE GENERATOR VERSION 3.0.
PQ14497: INCORRECT VALUE IN FORMATTED TEXT PART
PQ14725: C++ WGS PERFORMANCE ENHANCEMENTS
PQ14990: WORKGROUP SERVICES PERFORMANCE PROBLEM
PQ15440: UNRESOLVED EXTERNAL ERROR WHEN THE COMMAND: IF VARIABLE IN INTERNAL TABLE OF WORKING-STORAGE WITH START OPTION, IS USED.
PQ15467: WHEN CALLING A COBOL DLL FROM ITF, THE RETURN CODE FROM EZERT8 IS COMPLETELY RANDOM.
PQ15521: LIGHTPEN DETECTION CAN NOT BE SIMULATED BY A MOUSE DOUBLE CLICK UNDER THE VISUALGEN TEST FACILITY
PQ15676: VARIABLE NAMES IN GENERATED SQL CLAUSE HAVE BEEN TRUNCATED.
PQ15804: BATCH GENERATION PROBLEM
PQ15842: INDEXED RECORD WITH RECORD ID ITEM SET TO ENTIRE RECORD
PQ15949: DATA DESCRIPTOR IS GENERATED INCORRECTLY
PQ15970: HEX COMPARE PROBLEM
PQ16315: ORGANIZER IS SLOW TO REFRESH WHEN THERE ARE A LARGE NUMBER OF DATA ITEMS IN IMAGE.
PQ16414: AN ABENDASRA (0C7) WAS RECEIVED WHEN EXECUTING A VAGEN PROGRAM.
PQ16416: MSGIGYPS2028-E ISSUED WHEN COMPILING VA GEN PROGRAM.
PQ16418: TEXT DISPLAYED ON A TURQUOISE BACKGROUND
PQ16423: ATTEMPT TO USE ALL DCE BINDINGS
PQ16539: MAP GENERATED ON OS/2 DOES NOT DISPLAY TURKISH CHARS ON ISO8859
PQ16811: CICS ERROR READING REMOTE VSAM FILE
PQ17094: CANNOT TAKE FCWTRACE ON TEST MODE
PQ17263: VA GEN SYMBOLIC PARAMETER EZEUSRID IGNORED WHEN SPECIFIED IN
PQ18332: WRONG SQLCOD AFTER APPLYING FP4
PQ18865: SET MAP ITEM TURQ, WHITE OR FULL INCORRECT IN ITF
PQ19030: MESSAGE CSO7836E RC=0 ISSUED WHEN CALLING AIX SERVER FROM VISUALAGE GENERATOR CLIENT.
PQ19232: USE OF INDICATOR VARIABLES IN WHERE CLAUSE CAN RESULT IN A DBSCAN CAUSING BAD PERFORMANCE
PQ19610: DEBUGGER STARTS WHEN USER TRYS TO GET TEST COVERAGE REPORT.
PQ19661: AFTER APPLYING VG FOR WINDOWS NT FIXPACK4, VG FOR AIX DOES NOT GENERATE PROGRAM PARTS
PQ19733: UNABLE TO CALL AIX SERVER PROGRAM FROM NT CLIENT
PQ19777: SINGLE I-MESSAGES (F.E. 626.I) SHOULD BE SHOWN DURING ONLINE
PQ20011: EZESQCOD IS NOT BEING RESET TO 0 IN ITF OR C++ ENVIRONMENTS AFTER MAP CONVERSE COMMIT WHEN EZECNVCM=1
PQ20188: EZEUSR RETURNS THE TERMINAL ID WHICH IN THE ITF IS "PC USER".
PQ20218: INVALID CALL PARAMETER
PQ20420: A BLANK ITEM IS INSERTED AS NULL COLUMN IN A ORACLE TABLE.
PQ21045: EURO SUPPORT REQUIRED FOR VISUALAGE GENERATOR DEVELOPER
PQ21047: WALKBACK: UNDEFINEDOBJECT DOES NOT UNDERSTAND SETSTATUS AFTER MODIFYING SQL PROCESS AND RESUMING TEST.
PQ21932: INCORRECT CSO ERROR MESSAGE ISSUED FOR CICS ECI ERROR -4
PQ22120: UNDEFINED SYMBOL ERROR

VisualAge Generator Developer

Product Problem Support and Limitations

VisualAge Generator V3.0 Fixpak5 contains the following problem support and limitations for VisualAge Generator Developer:

Batch Generation and Utilities
VisualAge Organizer/VAGen Parts Browser
Map Editor
VisualAge AS/400 Feature
Migration Assistance Tool
Test Linkage Preferences

Batch Generation and Utilities

The following describes the support changes for VisualAge Generator Developer batch generation and utilities:

Batch utilities added.
- You can invoke batch utilities or batch generation using the hptcmd.exe or hptcmd30.exe executable files. The former simply invokes the latter. Use the hptcmd.exe file in any scripts you write in order to avoid having to change the scripts when you upgrade to a future release of VisualAge Generator.
- The version-specific batch generation executable, hptgen30.exe, has been deleted. Modify any scripts you have written that use hptgen30.exe and change them to use hptcmd.exe instead.
- The version-independent batch generation executable, hptgen.exe, still exists in this release, but it will be deleted in the next release. The hptgen.exe file now invokes hptcmd30.exe instead of hptgen30.exe. Modify any scripts you have written that use hptgen.exe and change them to use hptcmd.exe instead.
The /DEVICE and /options are currently not supported. Parts will be printed to the device specified with "Print Setup...".
A new batch generation option has been added. The new option is /UNLOAD, along with its counter option /NOUNLOAD.
- When you specify the /UNLOAD option during a batch generation, the /UNLOAD option causes any applications that contain VAGen parts to be unloaded before unloading the configuration map that is specified on the generate command. The /UNLOAD option has been added to reduce the risk of a failure occuring while loading a configuration map for a batch generation. Specifically, this should elimate the following error:
```
Error: 330 Cannot complete the load because 'vagen part
type'>>#<'pxxxx is  defined by 'application 1' anxxxxxx
```
- If /NOUNLOAD is specified, unloading will not occur before the load of the configuration map on the generate command.
- /UNLOAD is the default.
- The /UNLOAD option has no effect if it is specified in an options file. The option must be specified on the generate command to be effective.
- The /UNLOAD option has not been added to the generation option notebook. To override the default, you must manually specify /NOUNLOAD on the generate command.
Before Fixpak2, if you saved your image after performing a batch generation, any subsequent generations using that image (even after shutting down the image and restarting) would fail. This problem has been fixed. You can now safely save your image after a batch generation and continue working.
Before FixPak2, closing the Batch Generation Monitor window caused the entire Smalltalk image to close. This is no longer the case. The Batch Generation Monitor window can now be safely shut down without affecting the image.

VisualAge Organizer/VAGen Parts Browser

The following describes the support changes for VisualAge Generator Developer VisualAge Organizer/VAGen Parts Browser:

SQL and DL/I statements are not currently searched or changed when using the References utility (invoked by selecting References... from either the VAGen Parts menu or the VAGen Parts Browser "Parts" menu of the VisualAge Organizer window). If you use the References utility to change part names within Records or Processes, you will have to manually update the SQL and DL/I statements. Also, the References utility does not currently operate on PSB parts.
Fixpak4 contains a fix for APAR PQ15573. This corrects a memory leak problem with the Organizer. After you loaded the fixpak, type 'System abtScrubImage' in the System Transcript window (without the quotes), select the text, then choose Edit->Execute. All open windows will be closed and the Organizer will be restarted. When this completes, save your image. This will ensure that any memory leaked from the Organizer before the fix is cleaned up.
Fixpak4 introduced a new set of VAGen Smalltalk APIs. These APIs enable you to enforce part naming conventions and to write tools that operate against VAGen parts. For more information, see Appendix D in the updated online version of the Programmer's Reference manual.

Map Editor

The following describes the support changes for VisualAge Generator Developer Map Editor:

The Map Editor was completely redesigned in VisualAge Generator Version 3.0. Some enhancements/functionality is not completely or accurately documented in the on-line help. The following changes have occurred:
- Complete DBCS enablement with the enforcement of all restrictions is implemented. However, there are two options that existed in VisualAge Generator Version 2.2 that are still unavailable: Box and Insert/Remove SO/SI. Remember to set the default device in the preferences to a DBCS display if you are planning to work in a DBCS environment mostly. You may also want to choose a different font to work with.
- The Field List dialog displays a list of all variable and/or constant fields on the map being edited.
- The Map Editor status bar indicates the mouse pointer position when dragging or sizing objects.
- The Properties dialogs pop up when inserting new fields. This enables you to choose the item definition, type the text, or set the length of the field before it is inserted.
- A function to clear empty constant fields exists to enable easy removal of any stray constant fields that might be left behind after a drag or field delete operation.
- Inheritance of field attributes when inserting fields works as it used to in version VisualAge Generator Version 2.2. That is, if you insert a field into the middle of a field, the attributes that were in effect in the original field are propagated to the field that follows the inserted field.
- Multiple field drag/drop is supported. If you have a set of selected fields and you start dragging one of them with mouse button 2, then all selected fields are dragged and positioned at the same relative positions to the primary field being dragged.
- Extended highlighting is emulated as follows:
  - If all fields on the map are defined with "mono" as their color, then each field takes on 1 of 4 different colors depending on its protection and highlighting settings (the default color is blue).
  - If any field has an extended color defined (anything other than mono), then each mono field takes on 1 of only 2 colors.
  - If all the text on your map appears blue on black (which may be hard to read), you might want to set the color of one of your fields to green and then all blue information will become green. Note that this is consistent with the actual behavior of 3270 displays.
- The Map Editor no longer needs to store unique field mark characters. This makes most of the validation that was done during import of maps for valid characters under the Field mark tags unnecessary. This validation has been removed. This means that maps will import and export out of Version 3.0 with anything you want defined under those tags in the ESF. The removal of the validation restriction could mean that your new maps might no longer import into earlier versions of the product.
Known problems:
- The Helps for the Field List dialog mentions a context menu to do sorting. This context menu does not exist. Instead, you sort by clicking on the column headers (as in the VAGen Parts Browser).
- The Helps does not mention how you would use the yellow tag in the Field Edit Order --> Show Tags mode. This tag is a quick way to set the initial cursor field. You can drag the tag to any field, but it is recommended that you put it on a variable field. The position of this tag corresponds to the setting of the Initial Cursor Field attribute for that field.
- New maps that were created using pre-refresh VisualAge Generator Version 3.0 might contain some constant fields that have the Autoskip attribute turned on but the Protected attribute turned off. This situation is invalid but should not cause significant problems. It only becomes noticeable if you use the Clear Empty Constant FIelds option, as it might not clear the invalid fields or it could cause the subsequent empty fields to not be cleared since the attributes must match exactly. If this happens, go into the properties of these fields and set their protection to Protected. Open their properties again and set them back to Autoskip. Make sure you do this for both the field that contains the text and the empty field that follows it. If this problem is prevalent in many of your maps and you wish to correct it all at once, you might wish to export (ESF) all the maps you created with pre-refresh VisualAge Generator Version 3.0 and reimport them.
- The default font used by the Map Editor and the Interactive Test Facility (ITF) Map Monitor on Japanese NT is Courier. However, Courier is an SBCS font. If you are running on Japanese, you should go into the Test Facility and choose a valid DBCS font for the Map Monitor. This font should also be inherited by the Map Editor as long as you never bring up the Font dialog from the Map Editor.
- Clipboard support for wrapping text and for field objects is still not available.
- Underscores should now display correctly in the Map editor.
- The on-line Help mentions a Record Quick Form function in the Map Editor. This function is not implemented.

VisualAge AS/400 Feature

Do not load/install any of the VisualAge AS/400 features into an image in which VisualAge Generator Version 3.0 is loaded. Likewise, do not load/install VisualAge Generator Version 3.0 into an image in which any of the VisualAge AS/400 features are loaded. Loading both could result in unpredictable or incorrect behavior. The VisualAge AS/400 features and VisualAge Generator Version 3.0 each implement methods EsString>>#asInteger and ByteArray>>#asInteger. The implementations of EsString>>#asInteger are essentially equivalent in both products. The implementations for ByteArray>>#asInteger are significantly different.

COBOL Generation

COBOL Generation changes are as follows:

When doing a table-only generation for OS2CICS, the .TAB file that is produced will not be transferred to the appropriate machine if TCP/IP transfer type is specified in the generations options. You need to transfer the .TAB file manually.
When generating for the VSEBATCH and VSECICS environments on a Chinese or Korean workstation, the job that is uploaded to do the preparation is not being translated correctly. A workaround is to specify ASCII for the generation option /SENDTRANSLATIONCMDBCS. The default for this generation option is set in the file hptrules.nls file. Refer the documentation on how to modify the htptrules.nls file.

Migration Assistance Tool

On some OS/2 systems, in the initial stage of importing a very large ESF file into an MSL, you might get an "Out of PM Resources" message and be forced to reboot. If this happens, split the large ESF file into multiple files and import each smaller ESF file into the MSL individually.

Test Linkage Preferences

Programs are not being added to the list of programs to bypass when you attempt to add them through the VAGen Test Linkage notebook tab of the Preference Notebook. When you are using ITF to test linkage by selecting -Options, -Preference from the menu pulldown, if you select the VAGen Test Linkage notebook tab, then type in a program name in the box titled Select Program in library to bypass, the program is not added to the list when add is clicked.

If this happens, click OK, which exits from the Preference Notebook. Come back into the notebook again (-Options, -Preference, VAGen Test Linkage tab), type in the program name, and click on Add. The program will now be added.

Installation Instructions

The following sections describe the installation of VisualAge Generator Developer in VisualAge Generator V3.0 Fixpak5.

OS/2 Installation

To install VisualAge Generator Developer on OS/2, do the following:

On your OS2 machine, create a temporary fixpak directory called FIXDEV.
Click on DV2FP5B.EXE to download the file in binary to the FIXDEV directory. DV2FP5B.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.
Click on DV2FP5n.EXE to download the file in binary to the FIXDEV directory. DV2FP5n.EXE is found in /ps/products/visualagegen/fixes/v3.0/xxx (where xxx is the 3-character NLS id).
Explode DV2FP5B.EXE and DV2FP5n.EXE in the FIXDEV directory as follows:
```
    cd \FIXDEV           -  changes directory to FIXDEV
    DV2FP5B -d          -  explodes the file into parts
    DV2FP5n -d          -  explodes the file into parts
```
The -d parameter enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)

To install the VisualAge Generator Developer fixes, enter the following:

    d:\FIXDEV\xxx\HPTDEV2\INSTALL    (where xxx is the 3-character NLS id)

Optionally, you can now delete DV2FP5B.EXE and DV2FP5n.EXE. In addition, when everyone has installed the fixpak you can delete the FIXDEV directory and its subdirectories.
Reboot your machine if you modified CONFIG.SYS.
See Customization of VisualAge Generator Developer for additional information to complete the installation.

Windows Installation

To install VisualAge Generator Developer on Windows NT, do the following:

On your Windows NT machine, create a temporary fixpak directory called FIXDEV.
Click on DVNFP5B.EXE to download the file in binary to the FIXDEV directory. DVNFP5B.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.
Click on DVNFP5n.EXE to download the file in binary to the FIXDEV directory. DVNFP5n.EXE is found in /ps/products/visualagegen/fixes/v3.0/xxx (where xxx is the 3 char nls id).
Explode DVNFP5B.EXE and DVNFP5n.EXE in the FIXDEV directory as follows:
```
    cd \FIXDEV             -  changes the directory to FIXDEV
    DVNFP5B -d           -   explodes the file into parts
    DVNFP5n -d           -   explodes the file into parts
```
The -d parameter enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)

To install the VisualAge Generator Developer fixes, enter the following:

    d:\ WINDOWS\xxx\HPTDEVI\INSTFIX\SETUP    (where xxx is the 3-character NLS id)

Optionally, you can now delete DVNFP5B.EXE and DVNFP5n.EXE. In addition, when everyone has installed the fixpak you can delete the FIXDEV directory and its subdirectories.
See Customization of VisualAge Generator Developer for additional information to complete the installation.

Customization of VisualAge Generator Developer

To complete installation of VisualAge Generator Developer V3.0 Fixpak5, do the following:

Installing VisualAge Generator Developer fixes make VisualAge Generator Developer V3.0 Fixpak5 an available loadable feature of VisualAge for Smalltalk. Another feature containing fixes to the Interactive Test Facility dynamic partitioning support is a loadable feature called VAGen Partitioning Support. A third feature for notebook style settings is a loadable feature called VAGen GUI Settings. To apply VisualAge Generator Developer V3.0 Fixpak5, do the following:
1. Start VisualAge for Smalltalk.
2. Select Tools --> Load/Unload Features... on the System Transcript.
3. On the Selection Required window, do the following:
  1. Ensure that the Show other features check box is checked.
  2. Select Other: VAGen Developer - Fixpak5 from the Available features list. If you want to use ITF partitioning, select Other: VAGen Partitioning Support - Fixpak5 also. If you want to use notebook style settings, select Other: VAGen GUI Settings - Fixpak5.
  3. Click on the >> button to move Other: VAGen Developer - Fixpak5 to the Loaded features list. If you selected the Other: VAGen Partitioning Support - Fixpak5 feature, it will move as well. If you selected the Other: VAGen GUI Settings - Fixpak5, it will also move.
  4. Click on the OK button. The selected features will be imported and loaded into your image.
  5. 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 to come back to it later.
  6. Note that 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...).

After Installation Task

Fixpak5 requires the developer to rebind to the database to develop, test, and generate DB2 applications. The physical file name for the bind file for VisualAge Generator is hptdb230.bnd. The new package name associated with hptdb230.bnd is DEVELOP.HPT2O305 for OS/2 (was DEVELOP.HPT2O304) and DEVELOP.HPT2W305 for Windows NT (was DEVELOP.HPT2W304).

VisualAge Generator Templates

Product Problem Support and Limitations

V3.0 Fixpak5 contains the following problem support or limitations for VisualAge Generator Templates:

Templates Features

Templates Features

The following support was added for VisualAge Generator Templates Features that are in V3.0 Fixpak5:

An enhanced VisualAge QuickStart window that works with both VisualAge Smalltalk and VisualAge Generator parts.
The Application System Wizard, which lets you easily create a complete working application system that access and display data from your database.
VisualAge Generator Templates, a rapid application development tool aimed at automating the develpment of business components, enabling developers to build client/server systems easliy.

Installation Instructions

OS/2 Installation

To install VisualAge Generator Templates, do the following:

On your OS2 machine, create a temporary fixpak directory called FIXTMP.
Click on MDL3V3S2.EXE to download the file in binary to the FIXTMP directory. MDL3V3S2.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.

Explode MDL3V3S2.EXE in the FIXTMP directory as follows:

    cd \FIXTMP       -  changes the directory to FIXTMP
    MDL3V3S2        -  explodes the file into parts

Refer to the READ.ME and README.TXT files for installation and other information.
To install the VisualAge Generator Templates fixes, enter the following:
```
    d:\FIXTMP\INSTALL
```
Optionally, you can now delete MDL3V3S2.EXE. In addition, when everyone has installed the fixpak you can delete the FIXTMP directory.
To view the VisualAge Generator Templates online books, you need to use Library Reader/2. If you do not have Library Reader/2, follow these steps to install it:
1. Make a temporary directory called TMPLIB2.
2. Click on ILRENU2.EXE to download the file in binary to the TMPLIB2 directory. ILRENU2.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.
3. Execute ILRENU2.EXE from the TMPLIB2 directory.
4. Execute INSTALL.EXE from the TMPLIB2 directory.
5. After the installation is complete, you can delete the directory TMPLIB2.

Windows Installation

To install VisualAge Generator Templates, do the following:

On your Windows NT machine, create a temporary fixpak directory called FIXTMP.
Click on MDL3V3SN.EXE to download the file in binary to the FIXTMP directory. MDL3V3SN.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.

Explode MDL3V3SN.EXE in the FIXTMP directory as follows:

       cd \FIXTMP       -  change directory to FIXTMP
       MDL3V3SN        -  explodes the file into parts

Refer to the READ.ME and README.TXT files for installation and other information.
To install the VisualAge Generator Templates fixes, do the following:
```
    d:\FIXTMP\SETUP
```
Optionally, you can now delete MDL3V3SN.EXE. In addition, when everyone has installed the fixpak you can delete the FIXTMP directory.
To view the Templates online books, you need to use Library Reader/2. If you do not have Library Reader/2 then follow these steps to install it:
1. Make a temporary directory called TMPLIBW.
2. Click on ILRENUW.EXE to download the file in binary to the TMPLIBW directory. ILRENUW.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.
3. Execute ILRENUW.EXE from TMPLIBW.
4. Execute INSTALL.EXE from TMPLIBW.
5. After the installation is complete, you can delete directory TMPLIBW.

VisualAge Generator Server

Product Problem Support and Limitations

V3.0 Fixpak5 contains the following problem support or limitations for VisualAge Generator Server:

HP-UX Operating System

HP-UX Operating System

Due to a problem with the HP-UX Operating System, VisualAge Generator Server programs running on HP-UX are limited to function keys 1 through 10. A call id (problem report) has been opened with HP (#W3701478) to provide support for function keys 11 through 24.

Installation Instructions

The following sections describe the installation of VisualAge Generator Server in VisualAge Generator V3.0 Fixpak5.

OS/2 Installation

To install VisualAge Generator Server on OS/2, do the following:

On your OS2 machine, create a temporary fixpak directory called FIXSER.
Click on SR2FP5B.EXE to download the file in binary to the FIXSER directory. SR2FP5B.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.
Click on SR2FP5n.EXE to download the file in binary to the FIXSER directory. SR2FP5n.EXE is found in /ps/products/visualagegen/fixes/v3.0/xxx (where xxx is the 3- character NLS id).
Explode SR2FP5B.EXE and SR2FP5n.EXE in the FIXSER directory as follows:
```
       cd \FIXSER                      change directory to FIXSER
       SR2FP5B -d                     explode the file into parts
       SR2FP5n -d                      explode the file into parts
 
```
The -d parameter enables the files to be placed in the correct subdirectory structure. (The -d paramater is REQUIRED for the files to be loaded properly.)

To install the VisualAge Generator Server fixes, enter the following:

    d:\FIXSER\xxx\HPTWGS2\INSTALL   ( where xxx is the 3-character NLS id )

Optionally, you can now delete SR2FP5B.EXE and SR2FP5n.EXE. In addition, when everyone has installed the fixpak you can delete the FIXSER directory and its subdirectories.
Reboot the machine if you modified CONFIG.SYS.

Windows Installation

To install VisualAge Generator Server on Windows NT, do the following:

On your Windows NT machine, create a temporary fixpak directory called FIXSER.
Click on SRNFP5B.EXE to download the file in binary to the FIXSER directory. SRNFP5B.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.
Click on SRNFP5n.EXE to download the file in binary to the FIXSER directory. SRNFP5n.EXE is found in /ps/products/visualagegen/fixes/v3.0/xxx (where xxx is the 3-character NLS id)
Explode SRNFP5B.EXE and SRNFP5n.EXE in the FIXSER directory as shown:
```
      cd \FIXSER                      change directory to FIXSER
      SRNFP5B -d                    explode the file into parts
      SRNFP5n -d                     explode the file into parts
 
```
The -d parameter allows the files to be placed in the correct subdirectory structure. The -d paramater is REQUIRED for the files to be loaded properly.

To install the VisualAge Generator Server fixes, enter the following:

    d:\ WINDOWS\xxx\HPTWGSI\INSTFIX\SETUP   (where xxx is the 3-character NLS id )

Optionally, you can now delete SRNFP5B.EXE and SRNFP5n.EXE. In addition, when everyone has installed the fixpak you can delete the FIXSER directory and its subdirectories.

AIX Installation

To install VisualAge Generator Server on AIX, do the following:

On your AIX machine, create a temporary fixpak directory called FIXAIX.
Download image VGWGS30.IMG or VGWGS30T.IMG. The image environment is shown below:
- VGWGS30.IMG
  - AIX 4.14 or later
  - DB2 for AIX v2.1 or later
  - DataJoiner v1.2 or later
  - Will only support native AIX applications (non-CICS)
- VGWGS30T.IMG
  - AIX 4.14 or later
  - DB2/6000 PE v1.2 or later
  - DataJoiner v1.2 or later
  - Transaction Server v1.1 or later
  - Built with the thread-safe compiler
  - Requires CICS for AIX with PTF set 3
  - Will support both native and CICS applications
Logon as superuser (root)

Type one of the following commands:

    installp -ad vgwgs30.img all
    installp -ad vgwgs30t.img all

If VisualAge Generator Server for AIX was previously installed on the machine, you must uninstalled it before you can install a new version. To uninstall VisualAge Generator Server for HP_UX, type the following:
```
    installp -u vgwgs30.obj  (for AIX 4.1 or later)
```
Non-English users must also reject the obj related to their language. This is in addition to the command shown above to uninstall the base obj file. The list below shows the command for each language.
```
    installp -u vgwgs30Ds_DE.obj  (Swiss German)
    installp -u vgwgs30De_DE.obj  (German)
    installp -u vgwgs30Es_ES.obj   (Spanish)
    installp -u vgwgs30Ja_JP.obj    (Japanese)
    installp -u vgwgs30ko_KR.obj  (Korean)
    installp -u vgwgs30pt_PB.obj   (Brazukuab-Portuguese)
    installp -u vgwgs30zh_TW.obj  (Simplified Chinese)
```
Whenever you remove VisualAge Generator Server for AIX from your system to install a fixpak and you also have one of the NLS images installed, do the following:
- Remove the NLS image that is already installed
- Install the base fixpak image
- Re-install the NLS image

HP-UX Installation

To install VisualAge Generator Server on HP-UX, do the following:

On your HP-UX machine, create a temporary fixpak directory called FIXHP.

Download image VGWGS30.TAR or VGWGS30X.TAR. The image environment is shown below:

    VGWGS30.TAR    - HP-UX version 10.10
 
    VGWGS30X.TAR - HP-UX version 10.20

Type one of the following commands:

       tar -xvf  vgwgs30.tar
       tar -xvf vgwgs30x.tar

If VisualAge Generator Server for HP_UX was previously installed on the machine, you must uninstall it before you can install a new version. To uninstall VisualAge Generator Server for HP_UX, type the following:
```
    rm -rf /opt/vgwgs30   (for HP-UX 10.10 or HP-UX 10.20)
```

VisualAge Generator Common Services

Product Problem Support and Limitations

V3.0 Fixpak5 contains the following problem support or limitations for VisualAge Generator Common Services:

Java Enhancements

Java Enhancements

VisualAge Generator V3.0 Fixpak5 contains the following enhancements to the Java wrapper generation support:

Support is added for DBCS and mixed data types. New conversion tables are added for the double byte languages.
The beans generated have been enhanced to make it easier to use them on the VisualAge Java free form surface. The most useful of these enhancements is the setUnitOfWork method that has been added to the server program wrapper.
A graphical user interface has been added to the UnitOfWorkServer that runs on the web server and calls the PowerServer API. This user interface is brought up when you start the UnitOfWorkServer. It enables you to do the following:
- Display a list all sessions currently active on the web server,
- Display performance statistics for all calls requested through the UnitOfWorkServer, or for all calls of any session
- Trace activity of a given session
- Close any session
- Automatically close any session that is inactive for a given amount of time
- Log activity on the web server

To get details on the enhancements, use a web browser to browse the html page csojava.html after running the javaw.bat (for Windows) or javao.cmd (for OS/2) commands to install the Java wrapper support. The csojava.html file is located in the root directory where you install VisualAge Generator Common Services.

Installation Instructions

The following sections describe the installation of VisualAge Generator Common Services in VisualAge Generator V3.0 Fixpak5.

OS/2 Installation

Use these instructions to install VisualAge Generator Common Services fixes on OS2 if you did not install VisualAge Generator Common Services through VisualAge Generator Developer or VisualAge Generator Server. Otherwise, you can omit this section.

On your OS2 machine, create a temporary fixpak directory called FIXCSO.
Click on CS2FP5B.EXE to download the file in binary to the FIXCSO directory. CS2FP5B.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.
Click on CS2FP5n.EXE to download the file in binary to the FIXCSO directory. CS2FP5n.EXE is found in /ps/products/visualagegen/fixes/v3.0/xxx (where xxx is the 3-character NLS id).
Explode CS2FP5B.EXE and CS2FP5n.EXE in the FIXCSO directory as shown below:
```
       cd \FIXCSO                     change directory to FIXCSO
       CS2FP5B -d                     explode the file into parts
       CS2FP5n -d                      explode the file into parts
 
```
The -d parameter allows the files to be placed in the correct subdirectory structure. The -d parameter is REQUIRED for the files to be loaded properly.

To install the VisualAge Generator Common Services fixes, enter the following:

     d:\FIXCSO\xxx\HPTCSO2\INSTALL   ( where xxx is the 3-character NLS id )

Optionally, you can now delete CS2FP5B.EXE and CS2FP5n.EXE. In addition, when everyone has installed the fixpak you can delete the FIXCSO directory and its subdirectories.
Reboot the machine if you have modified CONFIG.SYS.

Windows Installation

To install VisualAge Generator Common Services on Windows NT, do the following:

On your Windows NT machine, create a temporary fixpak directory called FIXCSO.
Click on CSNFP5B.EXE to download the file in binary to the FIXCSO directory. CSNFP5B.EXE is found in /ps/products/visualagegen/fixes/v3.0/base.
Click on CSNFP5n.EXE to download the file in binary to the FIXCSO directory. CSNFP5n.EXE is found in /ps/products/visualagegen/fixes/v3.0/xxx (where xxx is the 3-character NLS id)
Explode CSNFP5B.EXE and CSNFP5n.EXE in the FIXCSO directory as shown below:
```
       cd \FIXCSO                     change directory to FIXCSO
       CSNFP5B -d                    explode the file into parts
       CSNFP5n -d                     explode the file into parts
 
```
The -d parameter allows the files to be placed in the correct subdirectory structure. The -d parameter is REQUIRED for the files to be loaded properly.

To install the VisualAge Generator Common Services fixes, enter the following:

    d:\ WINDOWS\xxx\HPTCSOI\INSTFIX\SETUP   (where xxx is the 3-character NLS id )

Optionally, you can now delete CSNFP5B.EXE and CSNFP5n.EXE. In addition, when everyone has installed the fixpak you can delete the FIXCSO directory and its subdirectories.

VisualAge Generator Documentation

When viewing the product documentation using the Acrobat Reader, you can now link from the table of contents to a section, link from a cross-reference to a section, and you can link directly from an index entry to the page.

The redbook VisualAge Generator System Development Guide (SG24-4230) is available on the web.

Fixpak4 List of APARs

The following is a list of APARs in Fixpak4:

PQ07029: GENERATION FAILS WHEN DBCS CHARACTERS ARE USED IN MEMBER_NAMES (ITEM, STATEMENT GROUP, RECORD,PROCESS).
PQ10388: SQLCODE=0 IN ITF TRACE, WHILE EZESQCOD=100 IN ITF SHOW DATA
PQ11617: CODE CONVERSION ERROR (DATA > 256 BYTES)
PQ11675: PROJECTID GENERATION OPTION IGNORED WHEN USING FTP TO SEND VISUALAGE GENERATOR OUTPUT TO MVS.
PQ11793: INCORRECT MODIFICATION OF SQL STATEMENTS AFTER PROCESS UPDATE.
PQ12423: GENERATION FAILS WHEN DBCS CHARACTERS ARE USED IN MEMBER_NAMES
PQ13222: LEVEL77 ITEM ARE NOT GENERATED CORRECTLY BY VISUALAGE GENERATOR V3.0.
PQ13315: ERROR MUST BE A BOOLEAN WHILE GENERATING VISGEN 3.0 APPLICATION.
PQ13809: VMDISKADDR A USER-DEFINED SYMBOLIC PARAMETER THAT VA GENERATOR SHIPS IS 10 CHARACTERS LONG.
PQ14219: UNDEFINED OBJECT DOES NOT UNDERSTAND EZEFEC.
PQ14247: VISUALAGE GENERATOR'S TEST FACILITY SHOULD ALLOW TESTING OF RECURSIVE PROGRAMS.
PQ14476: GENERATION OF A CALLED PROGRAM WITH EZEPCB(08) PARAMETER ABENDS WITH EZE4316E.
PQ14497: INCORRECT TRUNCATION IN FORMATTED TEXT FIELD.
PQ14659: DEFAULT DATE TRUNCATED UNDER NT WHEN USING COBOL
PQ14761: Z.SCR FILE IS GENERATED INCORRECTLY FOR HP AND AIX.
PQ15051: WRONG EZESQCOD WHEN DATA IS NOT FOUND.
PQ15174: STRUCTURE DECLARE PROBLEM WITH BINARY FIELDS
PQ15176: EXTRA ASSIGNMENTS GENERATED
PQ15371: VISUALAGE GENERATOR INCORECTLY BUILDS THE CONTENTS OF THE .SCR PREP FILE USED ON AIX.
PQ15467: WHEN CALLING A COBOL DLL FROM ITF, THE RETURN CODE FROM EZERT8 IS COMPLETELY RANDOM.
PQ15521: LIGHTPEN DETECTION CANNOT BE SIMULATED BY A MOUSE DOUBLE CLICK.
PQ15573: IMAGE SIZE PROBLEM
PQ15800: GENERAL PROTECTION FAULT DURING FORMAT OF STATEMENTS
PQ15802: VARIOUS PROBLEMS CORRECTED USING VISUALAGE GENERATOR 3.0 MSL MIGRATION TOOL.
PQ15803: ADDITIONAL PROBLEMS USING THE VISUALAGE GENERATOR MSL
PQ15805: BATCH GENERATION PROBLEM
PQ15842: INDEXED RECORD WITH RECORD ID ITEM SET TO ENTIRE RECORD
PQ15958: MAP FIELD NUMERIC ATTRIBUTE NOT TREATED CORRECTLY.
PQ15970: HEX COMPARE PROBLEM
PQ16318: PARTADDER SAMPLE PROGRAM DOES NOT PERFORM CORRECTLY.
PQ16423: ATTEMPT TO USE ALL DCE BINDINGS BEFORE RETURNING ERROR
PQ16461: RECORD DEFINITION PERFORMANCE IS POOR.
PQ16539: MAP GENERATED ON OS/2 DOES NOT DISPLAY TURKISH CHARS ON ISO8859-9 AIX.
PQ16597: CAN'T USE SINGLE ROW SELECT
PQ16752: VAG 3.0 GENERATES A WRONG PCB STATEMENT IN THE COBOL SOURCE WHEN YOU USE DIFFERENT PCBs IN THE PROGRAM.
PQ16857: FIXES FOR VARIOUS SQL PROBLEMS USING VISUALAGEN GENERATOR 3.0

Fixpak3 List of APARs

The following is a list of APARs in Fixpak3:

PQ10992: REVERSEVIDEO NOT FUNCTIONING WITH 3153 IN 3151 EMULATION MODE
PQ11283: IGYDS115-S A DATA ITEM EXCEEDED THE MAXIMUM SUPPORTED LENGTH 16777215 FOR AN ITEM IN THE 'LINKAGE SECTION'.
PQ12423: GENERATION FAILS WHEN DBCS CHARACTERS ARE USED IN MEMBER_NAMES (ITEM, STATEMENT GROUP, RECORD,PROCESS)
PQ12628: RC0 RECEIVED EVEN WHEN GENERATE FAILS RC8 IS EXPECTED
PQ12911: LOAD MODULE FCWVSIO CANNOT BE LOADED.
PQ13090: AN ERROR APPEARS ON EXPORTING A VISUALGEN 2.X APPLICATION A VISUALGEN 3.0.
PQ13289: PARSING OF APPL.FTP FILE
PQ13298: WALKBACK VALIDATING APPLICATION FOR OS400 CONTAINING EZESEGTR OR EZESEGM.
PQ13299: WHILE TESTING VISUALAGE GENERATOR PROGRAM WITH FIRST MAP DEFINED WALDKBACK DBSTRING DOES NOT UNDERSTAND PADTO:WITH:"
PQ13331: A SCAN PAST THE END OF FILE ON A RELATIVE FILE DOES NOT RETURN THE NRF CONDITION UNDER OS/2.
PQ13429: BLANK PAGE WHEN FLOATING MAP IS DEFINED RIGHT AFTER HEADER AREA.
PQ13430: HEX COMPARISON TAHT IS VG'S APPLICATION DOES NOT WORK CORRECTLY
PQ13451: EZEDESTP PRINTING TO A TRANSIENT DATA QUEUE DIFFERENCES
PQ13689: "SHARED" ATTRIBUTE OF VISUALAGE GENERATOR TABLE PART NOT SAVED WHEN EDITING A TABLE PART.
PQ13690: SQL INFO IS NOT DISCARDED WHEN SWITCHING FROM SQLROW TO ANOTHER TYPE OF VISUALAGE GENERATOR RECORD PART.
PQ13703: VG VALIDATION/GENERATION SQL CODE ERROR(DATE)
PQ14264: UNDEFINED OBJECT DOES NOT UNDERSTAND BIT AND ISSUED WHEN TESTING SQL APPLICATION USING VA GEN ODBC SUPPORT.
PQ14363: ERROR STRING: 'PRIMITIVE FAILED IN: OBJECT>>#AT: DUE TO INDEX OUT OF RANGE IN ARGUEMENT 1' ON EXPORT OF PROCESS PART.
PQ14380: UNABLE TO VALIDATE MULTIPLE PROGRAM PARTS AT THE SAME TIME AFTER APPLYING FIXPAK2 TO VISUALAGE GENERATOR VERSION 3.0.
PQ14725: CPP WGS PERFORMANCE ENHANCEMENTS

Fixpak2 List of APARs

The following is a list of APARs in Fixpak2:

PQ09069: RECEIVED AN INVALID RC WHEN VG APPLICATION TERMINATES.
PQ11217: WE GET AN SQLCODE -519 AND SQLSATE 24506 USING DXFR AFTER AN UPDATE AND THEN OTHER OPERATION LIKE AN INQUIRY.
PQ11218: SEVERAL INTERMITTEND PROBLEMS MAY OCCURE DURING RUNTIME UNDER IMS.
PQ11221: YOU WILL GET AN INCORRECT COLUMN BACK FROM A TABLE WHEN USING THE RETRIEVE COMMAND.
PQ11283: IGYDS115-S A DATA ITEM EXCEEDED THE MAXIMUM SUPPORTED LENGTH 16777215 FOR AN ITEM IN THE 'LINKAGE SECTION'.
PQ11451: NOSP OPTION CAUSES PROBLEMS WITH DXFRS AND SEGMENTED APPS
PQ11573: AN EXTRA BLANK LINE IS INSERTED AFTER PRINTOUT WHEN RUNNING APPL ON VISUALGEN HOST SERVICES FOR MVS.
PQ11643: MESSAGE 'EXCPMSTACKOVERFLOW' WHILE TRYING TO SOLVE AN 'ADD NO FOUND PART' PROBLEM.
PQ11644: ERROR GENERATING TWICE A VISGEN 3.0 PROGRAM
PQ11670: 'EXCLDTKEYNOTFOUND' ERROR
PQ11680: NUMBER OF OCCURANCES ITEM CANNOT BE SAVED WITH VISUALAGE GENERATOR RECORD.
PQ11681: WALKBACK ISSUED WHEN CONVERTING VARIABLE LENGTH INDEX FILE.
PQ12203: A GENERATED COBOL APPL, CONTAINING LARGE SQL STATEMENTS, COMPILED IN MVS GIVES MSGIGYR1081-S, SQLIO AND SQLERR SPECIFIED IN /TRACE.
PQ12204: THE 'SET FIELD NORMAL' COMMAND DOESN'T RECOGNIZE THE HIGHLIGHT ATTRIBUTES FOR A VARIABLE FIELD IN A TUI MAP.
PQ12205: MSGIGYPA3007-S "EZESCHEDULE-PSB" WAS NOT DEFINED AS A PROCEDURE-NAME. THE STATEMENT WAS DISCARDED.
PQ12433: WALKBACK OCCURS WHEN UNLOADING ENVY APPLICATION CONTAINING DL/I PARTS WHILE TESTING A DL/I PROGRAM.
PQ12434: THE CLUSTERING VIEW, REACHED FROM THE TEST MONITOR, SOMETIMES DOES NOT PAINT ICONS WHEN USING PARTITIONING SUPPORT.
PQ12435: WALKBACK OCCURS WHEN ATTEMPTING TO CONVERSE A MAP IN ITF THAT DOES NOT HAVE A DEVICE OF SIZE 24X80 SELECTED.
PQ12463: COMMIT/ROLLBACK PROBLEM.
PQ12497: EVEN SQL NOT SET TO Y WHEN LENGTH CHANGED TO EVEN IN SQL RECORD.
PQ12627: I/O STATES UNQ, DUP AND HRD NOT SET WHEN TESTING APPLICATIONS USING VISUALAGE GENERATOR VERSION 3.0.
PQ12829: CLOSE OPTION FOR A MAP IS WRONGLY INTERPRETED AS A CLOSE FOR A VISUALAGE GENERATOR RECORD.
PQ12941: VISUALAGE GENERATOR MESSAGE TABLE NOT LISTED AS ASSOCIATE OF A VISUALAGE GENERATOR PROGRAM PART.
PQ12942: HANDLE PSB IN APP SPECS AND EZEDLPSB/EZEDLPCB CALLED PARMS.
PQ12946: VISUALAGE GENERATOR MIGRATION TOOL NOT HANDLING ASSOCIATES FOR PSB PARTS CORRECTLY.
PQ12957: REPLACE/DELETE FAILS DUE TO BAD CSO HANDLE.