IBM VisualAge Generator V2.2 FixPak10 Readme

V22FP10 supersedes all previous fixes for VisualAge Generator Developer for OS/2 V2.2, VisualAge Generator Workgroup Services for OS/2 and Windows NT V2.2, and VisualAge Generator Workgroup Services for AIX V2.2. There might be an instance where a fix was specifically made for you. To determine if your fix is in the fixpak, check the list of APARs in this fixpak.

Fixpak10

Fixpak Packaging

This fixpak is packaged so it is installable using Software Installer, (with the exception of the AIX images which use INSTALLP). Install this fixpak the same way you installed the product from CD. The only difference is that the files will be on a hard drive instead of a CD.

V22FP10 contians self-extracting executables and INSTALLP images, which contain the following group of fixtests:

           
DEVFP10B.EXE  - Developer for OS/2 base fixes
DEVFP10n.EXE  - Developer for OS/2 language fixes
                        (Where n is the NLS character of c, e, j, p, or k)

WGSFP10B.EXE  - Workgroup Services for OS/2 base fixes
WGSFP10n.EXE  - Workgroup Services for OS/2 language fixes
                         (Where n is the NLS character of c, e, g, j, w, s, p, or k)

WINFP10B.EXE  - GUI Runtime for Windows base fixes
WINFP10n.EXE  - GUI Runtime for Windows language fixes
                        (Where n is the NLS character of c, e, j, p, or k)

WNTFP10B.EXE  - Workgroup Services for Windows NT base fixes
WNTFP10n.EXE  - Workgroup Services for Windows NT language fixes
                         (Where n is the NLS character of c, e, j, p, or k)

GRTFP10B.EXE  - GUI Runtime for Windows NT or 95 base fixes
GRTFP10n.EXE  - GUI Runtime for Windows NT or 95 language fixes
                        (Where n is the nls char of c, e, j, p, or k)

VGWGS22.IMG  - VisualAge Generator Workgroup Services for AIX with the following:
  - AIX 3.2.5
  - DB2/6000 V1.1 or later
  - DB2/6000 PE V1.1 or later
  - DataJoiner V1.1 or later
  - Will only support native AIX applications (non-CICS)

VGWGS22T.IMG - VisualAge Generator Workgroup Services for AIX with the following:
  - AIX 4.1 or later
  - DB2/6000 V2.1 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/6000 Fixpak3 (if Transaction Server installed)
  - Will support both native and CICS applications

ReadMe Files

The following readme files are associated with V22FP10:

readme.htm - Fixpak10 Readme file in html format
readme.txt - Fixpak10 Readme file in text format
read.me2 - Summary of V2.2 Refresh enhancements
readme.tcp - TCP/IP support introduced in Fixpak4

Product Enhancements, Problem Support, and Limitations

VisualAge Generator V2.2 Fixpak10 contain enhancements, problem support, and limitations for the following:

GUI Runtime Support
Euro Monetary Unit Support
Workgroup Services for CICS for Windows NT
List of APARs

GUI Runtime Support

Memory Monitor Tool

VisualAge Generator V2.2 Fixpak10 provides a new memory monitor tool that is built into the GUI runtime imgage. To start the memory monitor tool, enter the following command from the command line:

    EZE2RUN STARTMEMMONITOR

Use the memory monitor tool to get the following information about the image:

The total memory allocated by the GUI runtime process
The amount of memory available
The amount of memory that is actually being used by the objects in the system
The number of garbage collects that have occurred.
A list that shows the GUI instances that are still not released because the instances are not destroyed or are still referenced.

You can change the delay interval used to gather these values. The memory monitor tools also provides a push-button that you can use to force a global garbage collect to occur when you suspect that a GUI should have been released but the GUI still shows up in the list.

Event-to-action Connection

Prior to this fixpak, Event-to-action connections were used to cache the result of executing the connection. This could lead to some potential memory leaks where objects that were destroyed would still be referenced by these connections and not get released. With fixpak10, this caching no longer occurs. This should not cause any problems, but if you encounter a problem that we did not foresee, contact your IBM Support Center for assistance.

Euro Monetary Unit Support

With FixPak10, VisualAge Generator V2.2 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

Workgroup Services for CICS for Windows NT

Since CICS for Windows NT Version 2.00 is no longer supported, Fixpak10 was built using IBM Transaction Server for Windows NT Version 4.0. Do NOT install this fixpak (the VisualAge Generator Workgroup Services for CICS for Windows NT component) unless you plan to upgrade your version of CICS to IBM Transaction Server for Windows NT Version 4.0. You can use VisualAge Generator Workgroup Services at the Fixpak9 level with the other VisualAge Generator components in Fixpak10.

APARs in Fixpak10

Fixpak10 contains support for the following list of APARs:

PQ05021: BTRIEVE RELATIVE FILE VALIDATION CHECK
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
PQ11030: ASSOCIATE FILE NOT FOUND WHEN LANG IS SET TO TR_TR
PQ11617: CODE CONVERSION ERROR (DATA > 256 BYTES)
PQ14214: ENTERING AN INCORRECT PASSWORD WHEN USING CSOPRMPT.DLL FOR VAGEN
PQ14476: GENERATION OF A CALLED PROGRAM WITH EZEPCB(08) PARAMETER ABENDS
PQ14497: INCORRECT VALUE IN FORMATTED TEXT PART
PQ14525: TWO RECORDS POINT TO SAME FILE BUT DEFINE DIFF ORG FOR THE FILE
PQ14906: MOVING CHAR4 TO NUM3 PRODUCES INCORRECT OUTPUT
PQ15174: STRUCTURE DECLARE PROBLEM WITH BINARY FIELDS
PQ15176: EXTRA ASSIGNMENTS GENERATED
PQ15440: UNRESOLVED EXTERNAL ERROR WHEN THE COMMAND: IF VARIABLE IN
PQ15676: VARIABLE NAMES IN GENERATED SQL CLAUSE HAVE BEEN TRUNCATED.
PQ15958: MAP FIELD NUMERIC ATTRIBUTE NOT TREATED CORRECTLY
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
PQ16811: CICS ERROR READING REMOTE VSAM FILE
PQ16839: BRIGHT FUNCTION IS NOT WORKING ON AIX TERMINAL
PQ19030: Message CSO7836E RC=0 ISSUED WHEN CALLING AIX SERVER
PQ20137: RECEIVING ERROR LNK2029: "SQLCHA::OPERATOR=(CONST INT)" :
PQ21035: SYS3175 IN C++ SERVER WHEN ERROR DETECTED
PQ21045: EURO SUPPORT REQUIRED FOR VISUALAGE GENERATOR DEVELOPER
PQ21046: EURO SUPPORT FOR VISUALAGE GENERATOR SERVER
PQ21639: IGYPS2121-S EZESYS-WINNT NOT DEFINED AS DATA-NAME DURING COBOL

Fixpak10 Installation

To install the new function for the various environments, follow the instructions below.

Installing Developer and Workgroup Services fixes on OS/2:

Create 2 temporary fixpak directories called FIXDEV and FIXWGS. (These names are examples. You can name these directories anything you wish.)
Click on DEVFP10B.EXE to download the file to the FIXDEV directory in binary. This file is very large and will take about seven minutes to download. DEVFP10B.EXE is located in /ps/products/visualagegen/fixes/v2.2/base.
Click on DEVFP10n.EXE to download the file to the FIXDEV directory in binary. DEVFP10n.EXE is located in /ps/products/visualagegen/fixes/v2.2/xxx (where xxx is the 3-character NLS id).
Click on WGSFP10B.EXE to download the file to the FIXWGS directory in binary. WGSFP10B.EXE is located in /ps/products/visualagegen/fixes/v2.2/base.
Click on WGSFP10n.EXE to download the file to the FIXWGS directory in binary. WGSFP10n.EXE is located in /ps/products/visualagegen/fixes/v2.2/xxx (where xxx is the 3-character NLS id).

Explode the EXE files to get the new product parts. This can be done in several ways depending on whether you performed a local or CID install for the original product. The following describes how to perform a local and a CID install.

If you performed a local install as described in Chapter 2 of the Installation Guide for VisualAge Generator Developer, then do the following:

Explode DEVFP10B.EXE and DEVFP10n.EXE in the FIXDEV directory as follows:

    cd \FIXDEV          (change directory to FIXDEV)
    DEVFP10B -d       (explode into parts)
    DEVFP10n -d       (explode into parts)

Explode WGSFP10B.EXE and WGSFP10n.EXE in the FIXWGS directory as follows:
```
    cd \FIXWGS         (change directory to FIXWGS)
    WGSFP10B -d      (explode into parts)
    WGSFP10n -d      (explode into parts)
```
The -d switch 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 Developer fixes, enter the following:

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

To install the Workgroup Services fixes, enter the following:

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

If you performed a CID install, as described in the Installation Guide for VisualAge Generator Developer, then do the following:

Explode DEVFP10B.EXE and DEVFP10n.EXE in the FIXDEV directory as follows:

    cd \FIXDEV          (change directory to FIXDEV)
    DEVFP10B -d       (explode into parts)
    DEVFP10n -d       (explode into parts)

Explode WGSFP10B.EXE and WGSFP10n.EXE in the FIXWGS directory as follows:
```
    cd \FIXWGS           (change directory to FIXWGS)
      WGSFP10B -d      (explode into parts)
      WGSFP10n -d      (explode into parts)
```
The -d switch enable 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 Developer fixes, do the following:
1. XCOPY the files from d:\FIXDEV to d:\proddev by entering the following:
```
XCOPY d:\FIXDEV d:\proddev /S
```
  Where proddev is the directory that the product files were XCOPYed to as described in the Installation Guide for VisualAge Generator Developer.
  The /S switch enables the files to be placed in the correct subdirectory structure. (The /S parameter is REQUIRED for the files to be loaded properly.)
2. d:\proddev\xxx\INSTALL parms (where xxx is the 3-character NLS id)
  Where parms are the CID install parms that you used for the product install. There are two changes that you might want to make to the original install parms when you install the fixpak.
  The first parm change is to change the ACTION from INSTALL to UPDATE. The second parm change is not to update CONFIG.SYS again since it was already updated during the original product install.
To install the Workgroup Services fixes, do the following:
1. XCOPY the files from d:\FIXWGS to d:\prodwgs by entering the following:
```
XCOPY d:\FIXWGS d:\prodwgs /S
```
  Where prodwgs is the directory that the product files were XCOPYed to as described in the Installation Guide for VisualAge Generator Workgroup Services for OS/2.
  The /S switch enables the files to be placed in the correct subdirectory structure. (The /S parameter is REQUIRED for the files to be loaded properly.)
2. d:\prodwgs\xxx\INSTALL parms (where xxx is the 3-character NLS id)
  Where parms are the CID install parms that you used for the product install. There are two changes that you might want to make to the original install parms when you install the fixpak.
  The first parm change is to change the ACTION from INSTALL to UPDATE. The second parm change is not to update CONFIG.SYS again since it was already updated during the original product install.
Optionally, you can delete the DEVFP10B.EXE, DEVFP10n.EXE, WGSFP10B.EXE and WGSFP10n.EXE files. These files are no longer needed once they have been exploded. The files are quite large and erasing them would save a lot of space. In addition, when everyone has installed the fixpak, you can delete the FIXDEV and FIXWGS directories and their subdirectories.
Reboot your system if you modified the CONFIG.SYS file.

Installing GUI Runtime for Windows 3.1 fixes on DOS\Windows:

On your OS/2 system, create a temporary fixpak directory called FIXWIN. (This name is an example. You can name the directory whatever you wish.)
Click on WINFP10B.EXE to download the file to the FIXWIN directory in binary. WINFP10B.EXE is located in /ps/products/visualagegen/fixes/v2.2/base.
Click on WINFP10n.EXE to download the file to the FIXWIN directory in binary. WINFP10n.EXE is located in /ps/products/visualagegen/fixes/v2.2/xxx (where xxx is the 3-character NLS id).
The WINFP10B.EXE and WINFP10n.EXE files are now on your OS/2 system. The files can be transported to other locations. This can be done in either of following ways:
- You can transport the WINFP10B.EXE and WINFP10n.EXE files to your Windows 3.1 machine. Create a FIXWIN directory on your Windows 3.1 machine to hold WINFP10B.EXE and WINFP10n.EXE.
- You can have the WINFP10B.EXE and WINFP10n.EXE files reside on a LAN drive (in directory FIXWIN) where your Windows 3.1 machine can access it.
Explode the EXE files to get the new product parts. This can be done in several ways depending on whether you performed a local or CID install for the original product. The following describes how to to perform a local and a CID installation.
If you performed a local install, as described in the Installation Guide for VisualAge Generator Developer, do the following:
1. Explode WINFP10.EXE and WINFP10n.EXE in the FIXWIN directory as follows:
```
    cd \FIXWIN          (change directory to FIXWIN)
    WINFP10B -d       (explode into parts)
    WINFP10n -d       (explode into parts)
```
  The -d switch enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)
2. To install the GUI Runtime for Windows 3.1 fixes, do the following:
  1. On Windows 3.1, go to the Program Manager window and select File, then Run from the pulldown.
  2. From the Run pulldown, enter the following:
```
    d:\FIXWIN\ENU\INSTALL
```
If you performed a CID install, as described in the Installation Guide for VisualAge Generator Developer, do the following:
1. Explode WINFP10.EXE and WINFP10n.EXE in the FIXWIN directory as follows:
```
    cd \FIXWIN          (change directory to FIXWIN)
    WINFP10B -d       (explode into parts)
    WINFP10n -d       (explode into parts)
```
  The -d switch enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)
2. To install the GUI Runtime for Windows 3.1 fixes, do the following:
  1. XCOPY the files from d:\FIXWIN to d:\prodwin by entering the following:
```
XCOPY d:\FIXWIN d:\prodwin /S
```
    Where prodwin is the directory that the product files were XCOPYed to as described in the Installation Guide for VisualAge Generator Developer.
    The /S switch enables the files to be placed in the correct subdirectory structure. (The /S parameter is REQUIRED for the files to be loaded properly.)
3. On Windows 3.1, go to the Program Manager window and select File, then Run from the pulldown.
4. From the Run pulldown, enter the following:
```
d:\prodwin\xxx\INSTALL parms
```
  Where xxx is the 3-character NLS id.
  Where parms are the CID install parms that you used for the product install. There are two changes that you might want to make to the original install parms when you install the fixpak.
  The first parm change is to change the ACTION from INSTALL to UPDATE. The second parm change is not to update AUTOEXEC.BAT again since it was already updated during the original product install.
Optionally, you can delete the WINFP10B.EXE and WINFP10n.EXE files. These files are no longer needed once they have been exploded. The files are quite large and erasing them would save a lot of space. In addition, when everyone has installed the fixpak, you can delete the FIXWIN directories and its subdirectories.
Reboot your system if you modified the AUTOEXEC.BAT file.

Installing GUI Runtime for Windows NT fixes on Windows NT:

Note: These installation instructions are only needed if you have VisualAge Generator GUI Runtime for Windows NT installed on your system. If you do not have VisualAge Generator GUI Runtime for Windows NT installed on your Windows NT system, you can skip this first part of the installation process and go to the part on uninstalling VisualAge Generator GUI Runtime for Windows NT.

On your OS/2 machine, create a temporary fixpak directory called FIXGNT. (This name is an example. You can name the directory whatever you wish.)
Click on GRTFP10B.EXE to download the file to the FIXGNT directory in binary. GRTFP10B.EXE is located in /ps/products/visualagegen/fixes/v2.2/base.
Click on GRTFP10n.EXE to download the file to the FIXGNT directory in binary. GRTFP10n.EXE is located in /ps/products/visualagegen/fixes/v2.2/xxx (where xxx is the 3-character NLS id).
The GRTFP10B.EXE and GRTFP10n.EXE files are now on your OS/2 system. The files can be transported to other locations. This can be done in either of following ways:
- You can transport the GRTFP10B.EXE and GRTFP10n.EXE files to your Windows NT machine. Create a FIXGNT directory on your Windows NT machine to hold GRTFP10B.EXE and GRTFP10n.EXE.
- You can have the WINFP10B.EXE and WINFP10n.EXE files reside on a LAN drive (in directory FIXGNT) where your Windows NT machine can access it.
Explode the EXE files to get the new product parts. This can be done in several ways depending on whether you performed a local or LAN install for the original product. The following describes how to to perform a local and a LAN installation.
If you performed a local install, do the following:
1. Explode GRTFP10.EXE and GRTFP10n.EXE in the FIXGNT directory as follows:
```
    cd \FIXGNT         (change directory to FIXGNT)
    GRTFP10B -d      (explode the file into parts)
    GRTFP10n -d      (explode the file into parts)
```
  The -d switch enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)
2. To install the GUI Runtime for Windows NT fixes, do the following:
  1. On Windows NT, click on the Start button and select Run from the pulldown.
  2. From the Run pulldown, enter the following:
```
    d:\FIXGNT\ENU\SETUP -FSETUPFP.INS 
```
If you performed a LAN install, do the following:
1. Explode GRTFP10.EXE and GRTFP10n.EXE in the FIXGNT directory as follows:
```
    cd \FIXGNT         (change directory to FIXGNT)
    GRTFP10B -d      (explode the file into parts)
    GRTFP10n -d      (explode the file into parts)
```
  The -d switch enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)
2. To install the GUI Runtime for Windows NT fixes, do the following:
  1. XCOPY the files from d:\FIXGNT to d:\prodgnt by entering the following:
```
XCOPY d:\FIXGNT d:\prodgnt /S
```
    Where prodgnt is the directory that the product files were XCOPYed to.
    The /S switch enables the files to be placed in the correct subdirectory structure. (The /S parameter is REQUIRED for the files to be loaded properly.)
3. On Windows NT, click on the Start button and select Run from the pulldown.
4. From the Run pulldown, enter the following:
```
d:\prodgnt\ENU\SETUP -FSETUPFP.INS
```
Optionally, you can delete the GRTFP10B.EXE and GRTFP10n.EXE files. These files are no longer needed once they have been exploded. The files are quite large and erasing them would save a lot of space. In addition, when everyone has installed the fixpak, you can delete the FIXGNT directories and its subdirectories.
Reboot your system if you modified the AUTOEXEC.BAT file.

Installing GUI Runtime for Windows 95 fixes on Windows 95:

Note: These installation instructions are only needed if you have VisualAge Generator GUI Runtime for Windows 95 installed on your system. If you do not have VisualAge Generator GUI Runtime for Windows 95 installed on your Windows 95 system, you can skip this first part of the installation process and go to the part on uninstalling VisualAge Generator GUI Runtime for Windows 95.

On your OS/2 machine, create a temporary fixpak directory called FIXG95. (This name is an example. You can name the directory whatever you wish.)
Click on GRTFP10B.EXE to download the file to the FIXG95 directory in binary. GRTFP10B.EXE is located in /ps/products/visualagegen/fixes/v2.2/base.
Click on GRTFP10n.EXE to download the file to the FIXG95 directory in binary. GRTFP10n.EXE is located in /ps/products/visualagegen/fixes/v2.2/xxx (where xxx is the 3-character NLS id).
The GRTFP10B.EXE and GRTFP10n.EXE files are now on your OS/2 system. The files can be transported to other locations. This can be done in either of following ways:
- You can transport the GRTFP10B.EXE and GRTFP10n.EXE files to your Windows 95 machine. Create a FIXG95 directory on your Windows 95 machine to hold GRTFP10B.EXE and GRTFP10n.EXE.
- You can have the WINFP10B.EXE and WINFP10n.EXE files reside on a LAN drive (in directory FIXG95) where your Windows 95 machine can access it.
Explode the EXE files to get the new product parts. This can be done in several ways depending on whether you performed a local or LAN install for the original product. The following describes how to to perform a local and a LAN installation.
If you performed a local install, do the following:
1. Explode GRTFP10.EXE and GRTFP10n.EXE in the FIXG95 directory as follows:
```
    cd \FIXG95         (change directory to FIXG95)
    GRTFP10B -d      (explode the file into parts)
    GRTFP10n -d      (explode the file into parts)
```
  The -d switch enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)
2. To install the GUI Runtime for Windows 95 fixes, do the following:
  1. On Windows 95, click on the Start button and select Run from the pulldown.
  2. From the Run pulldown, enter the following:
```
    d:\FIXG95\ENU\SETUP -FSETUPFP.INS 
```
If you performed a LAN install, do the following:
1. Explode GRTFP10.EXE and GRTFP10n.EXE in the FIXG95 directory as follows:
```
    cd \FIXG95         (change directory to FIXG95)
    GRTFP10B -d      (explode the file into parts)
    GRTFP10n -d      (explode the file into parts)
```
  The -d switch enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)
2. To install the GUI Runtime for Windows 95 fixes, do the following:
  1. XCOPY the files from d:\FIXG95 to d:\prodgnt by entering the following:
```
    XCOPY d:\FIXG95 d:\prodg95 /S
```
    Where prodg95 is the directory that the product files were XCOPYed to.
    The /S switch enables the files to be placed in the correct subdirectory structure. (The /S parameter is REQUIRED for the files to be loaded properly.)
3. On Windows NT, click on the Start button and select Run from the pulldown.
4. From the Run pulldown, enter the following:
```
    d:\FIXG95\ENU\SETUP -FSETUPFP.INS
```
Optionally, you can delete the GRTFP10B.EXE and GRTFP10n.EXE files. These files are no longer needed once they have been exploded. The files are quite large and erasing them would save a lot of space. In addition, when everyone has installed the fixpak, you can delete the FIXG95 directories and its subdirectories.
Reboot your system if you modified the AUTOEXEC.BAT file.

Installing VisualAge Generator Workgroup Services for Windows NT fixes on Windows NT:
Note: These installation instructions are only needed if you have VisualAge Generator Workgroup Services for Windows NT installed on your system. If you do not have VisualAge Generator Workgroup Services for Windows NT installed on your Windows NT system, you can skip this first part of the installation process and go to the part on uninstalling VisualAge Generator Workgroup Services for Windows NT.

On your OS/2 machine, create a temporary fixpak directory called FIXWNT. (This name is an example. You can name the directory whatever you wish.)
Click on WNTFP10B.EXE to download the file to the FIXWNT directory in binary. WNTFP10B.EXE is located in /ps/products/visualagegen/fixes/v2.2/base.
Click on WNTFP10n.EXE to download the file to the FIXWNT directory in binary. WNTFP10n.EXE is located in /ps/products/visualagegen/fixes/v2.2/xxx (where xxx is the 3-character NLS id).
The WNTFP10B.EXE and WNTFP10n.EXE files are now on your OS/2 system. The files can be transported to other locations. This can be done in either of following ways:
- You can transport the WNTFP10B.EXE and WNTFP10n.EXE files to your Windows NT machine. Create a FIXWNT directory on your Windows NT machine to hold WNTFP10B.EXE and WNTFP10n.EXE.
- You can have the WNTFP10B.EXE and WNTFP10n.EXE files reside on a LAN drive (in directory FIXWNT) where your Windows NT machine can access it.
Explode the EXE files to get the new product parts. This can be done in several ways depending on whether you performed a local or LAN install for the original product. The following describes how to to perform a local and a LAN installation.
If you performed a local install, do the following:
1. Explode WNTFP10.EXE and WNTFP10n.EXE in the FIXWNT directory as follows:
```
    cd \FIXWNT         (change directory to FIXWNT)
    WNTFP10B -d      (explode the file into parts)
    WNTFP10n -d      (explode the file into parts)
```
  The -d switch enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)
2. To install the Workgroup Services for Windows NT fixes, do the following:
  1. On Windows NT, click on the Start button and select Run from the pulldown.
  2. From the Run pulldown, enter the following:
```
d:\FIXWNT\ENU\SETUP -FSETUPFP.INS 
```
If you performed a LAN install, do the following:
1. Explode WNTFP10.EXE and WNTFP10n.EXE in the FIXWNT directory as follows:
```
    cd \FIXWNT         (change directory to FIXWNT)
    WNTFP10B -d      (explode the file into parts)
    WNTFP10n -d      (explode the file into parts)
```
  The -d switch enables the files to be placed in the correct subdirectory structure. (The -d parameter is REQUIRED for the files to be loaded properly.)
2. To install the VisualAge Generator Workgroup Services for Windows NT fixes, do the following:
  1. XCOPY the files from d:\FIXWNT to d:\prodwnt by entering the following:
```
XCOPY d:\FIXWNT d:\prodwnt /S
```
    Where prodwnt is the directory that the product files were XCOPYed to.
    The /S switch enables the files to be placed in the correct subdirectory structure. (The /S parameter is REQUIRED for the files to be loaded properly.)
3. On Windows NT, click on the Start button and select Run from the pulldown.
4. From the Run pulldown, enter the following:
```
d:\prodwnt\ENU\SETUP -FSETUPFP.INS
```
Optionally, you can delete the WNTFP10B.EXE and WNTFP10n.EXE files. These files are no longer needed once they have been exploded. The files are quite large and erasing them would save a lot of space. In addition, when everyone has installed the fixpak, you can delete the FIXWNT directories and its subdirectories.
Reboot your system if you modified the AUTOEXEC.BAT file.

Installing VisualAge Generator Workgroup Services for AIX fixes on AIX:
Note: These installation instructions are only needed if you have VisualAge Generator Workgroup Services for AIX installed on your system. If you do not have VisualAge Generator Workgroup Services for AIX installed on your AIX system, you can skip this first part of the installation process and go to the part on uninstalling VisualAge Generator Workgroup Services for AIX.

On your OS/2 machine, create a temporary fixpak directory called FIXAIX. (This name is an example. You can name the directory whatever you wish.)
Select one of the following images from the images listed. The image that applies to you is dependent on your system environment. To determine which image applies, view the beginning of this file, which lists the images and their descriptions.
1. Download VGWGS22.IMG as VGWGS22.IMG to FIXAIX in binary. VGWGS22.IMG is located in /ps/products/visualgen/fixes/v2.2/base.
2. Download VGWGS22T.IMG as VGWGS22T.IMG to FIXAIX in binary. VGWGS22T.IMG is found in /ps/products/visualgen/fixes/v2.2/base.
The image file is now on your OS/2 machine. It should never be installed on an OS/2 machine, since it runs on a AIX machine. You can transport the image to other locations. This can be done in one of the following ways:
- You can transport the image to your AIX machine. Create a FIXAIX directory on your AIX machine to hold the image.
- You can have the image reside on a LAN drive (in directory FIXAIX) where your AIX machine can access it.

To install the image, do the following:

Logon as a superuser (root).

Select one of the following images and ensure that it applies to you:

    installp -ad vgwgs22.img all
 
    installp -ad vgwgs22t.img all

If VisualAge Generator Workgroup Services for AIX was previously installed on your system, it must be uninstalled before you can install a new version. To uninstall it, type the following:

    installp -r vgwgs22.obj   (for AIX 3.2.5)
                            or
    installp -u vgwgs22.obj   (for AIX 4.1 or later)

Non-English users must also uninstall the .obj related to their language. This is in addition to the command above. The table below shows the command for each language.

    installp -r vgwgs22Ds_DE or installp -u vgwgs22Ds_DE  (Swiss German)
    installp -r vgwgs22De_DE or installp -u vgwgs22De_DE  (German)
    installp -r vgwgs22Es_ES or installp -u vgwgs22Es_ES  (Spanish)
    installp -r vgwgs22Ja_JP or installp -u vgwgs22Ja_JP  (Japanese)
    installp -r vgwgs22ko_KR or installp -u vgwgs22ko_KR  (Korean)
    installp -r vgwgs22pt_PB or installp -u vgwgs22pt_PB  (Brazilian-Portuguese)
    installp -r vgwgs22zh_TW or installp -u vgwgs22zh_TW  (Simplified Chinese)

Note:

Whenever you remove VisualAge Generator Workgroup Services for AIX from your system to install a fixpak and you also have one of the NLS images installed, you need to remove the NLS image and then reinstall the NLS image after you have installed the base fixpak image.

Content of Previous Fixpaks

Fixpak9

No additional instructions provided for Fixpak9.

APARs in Fixpaks9

Fixpak9 contains support for the following list of APARs:

PQ12366: WIN95 HANG WHEN KEYING KOREAN CHAR. TO THE FIELD DEFINED HIDDEN
PQ13491: INHERITSCOMMUNICATIONSSESSION DOESN'T WORK WITH DESTROYONCLOSE

Fixpak8

No additional instructions provided for Fixpak8.

APARs in Fixpak8

Fixpak8 contains support for the following list of APARs:

PQ07930: IGYDS115-S A DATA ITEM EXCEEDED THE MAXIMUM SUPPORTED LENGTH 16777215 FOR AN ITEM IN THE 'LINKAGE SECTION'.
PQ10466: SYS3175 IN FCW.DLL ON EZECONCT
PQ10992: REVERSEVIDEO NOT FUNCTIONING WITH 3153 IN 3151 EMULATION MODE
PQ11514: DROP DOWNLIST NOT CLEARED WHEN RUNNING UNDER WORKGROUP SERVICES FOR WINDOWS
PQ11666: HEX COMPARISON TAHT IS VG'S APPLICATION DOES NOT WORK CORRECTLY
PQ11669: MSGEZE3143E DURING GENERATE
PQ12463: COMMIT/ROLLBACK PROBLEM
PQ12601: BLANK PAGE WHEN FLOATING MAP IS DEFINED RIGHT AFTER HEADER AREA.
PQ12755: NEEDS TO USE ALTGR KEY TO USE TILTED VOWELS OR CEDILLED 'C'
PQ12911: LOAD MODULE FCWVSIO CANNOT BE LOADED.
PQ13090: AN ERROR APPEARS ON EXPORTING A VISUALGEN 2.X APPLICATION A VISUALGEN 3.0.
PQ13331: A SCAN PAST THE END OF FILE ON A RELATIVE FILE DOES NOT RETURN THE NRF CONDITION UNDER OS/2.
PQ13500: WHILE TESTING VISUALAGE GENERATOR PROGRAM WITH FIRST MAP DEFINED WALDKBACK DBSTRING DOES NOT UNDERSTAND PADTO:WITH:"

Fixpak7

Use of VisualAge Generator TCP/IP or DCE Middleware Servers on Windows NT

Fixpak7 corrects a previous problem of generating server applications using the VisualAge C++ compiler. If you are using this compiler, set the following environment variable prior to starting the VisualAge Generator TCP/IP or DCE server:

   
    SET CSONTVACPP=1

This change took effect in V2.2 Fixpak6 for VisualAge Generator TCP/IP servers on NT and V2.2 Fixpak7 for VisualAge Generator DCE servers on NT.

Do NOT set this environment variable unless your VisualAge Generator TCP/IP or DCE server runs on NT and your server applications are generated using the VisualAge C++ compiler. Customers using the Microsoft C++ compiler are not affected and should NOT set this environment variable.

Optional Code for C++ Workgroup Services for OS/2

Fixpak7 provides a special version of C++ Workgroup Services for OS/2 that offers a performance improvement for applications that use 3270 style maps (non-GUI). If you apply this code, you MUST regenerate all of your applications. This code is completely OPTIONAL.

This code is located in file WGS22ENH.ZIP. The instructions for this zip file are located in the file README.WGS.

APARs in Fixpak7

Fixpak7 contains support for the following list of APARs:

PQ05199: LEVEL 77 ITEM VALUES NOT RETURNED FROM SERVER (JAVA GEN)
PQ07126: COPY/PASTE OF PUSHBUTTON CAUSES LOADER ERROR
PQ07930: IGYDS115-S A DATA ITEM EXCEEDED THE MAXIMUM SUPPORTED LENGTH 16777215 FOR AN ITEM IN THE 'LINKAGE SECTION'.
PQ08536: YOU WILL GET AN INCORRECT COLUMN BACK FROM A TABLE WHEN USING THE RETRIEVE COMMAND.
PQ08674: THE 'SET FIELD NORMAL' COMMAND DOESN'T RECOGNIZE THE HIGHLIGT ATTRIBUTES FOR A VARIABLE FIELD IN A TUI MAP.
PQ08732: MSGIGYPA3007-S "EZESCHEDULE-PSB" WAS NOT DEFINED AS A PROCEDURE-NAME. THE STATEMENT WAS DISCARDED.
PQ09069: RECEIVED AN INVALID RC WHEN VG APPLICATION TERMINATES
PQ09370: BEEPING PROBLEM WITH DATE FIELD IN CDV WITHOUT A DEFAULT DATE
PQ09807: AN EXTRA BLANK LINE IS INSERTED AFTER PRINTOUT WHEN RUNNING APPL ON VISUALGEN HOST SERVICES FOR MVS
PQ09888: EZEMNO IS NOT SETTING EZEMSG
PQ10393: WE GET AN SQLCODE -519 AND SQLSATE 24506 USING DXFR AFTER AN U PDATE AND THEN OTHER OPERATION LIKE AN INQUIRY.
PQ10623: INVALID DEFAULT CODE PAGE IN ELACNKOR.CTB
PQ10832: A GENERATED COBOL APPL, CONTAINING LARGE SQL STATEMENTS,COMPILED IN MVS GIVES MSGIGYR1081-S, SQLIO AND SQLERR SPECIFIED IN /TRACE
PQ11023: SEVERAL INTERMITTEND PROBLEMS MAY OCCURE DURING RUNTIME UNDER IMS.
PQ11562: VISUALAGE GENERATOR SUPPORT FOR NEW LINKTABLE OPTION LINKTYPE=AIXLOAD.
PQ12422: NOSP OPTION CAUSES PROBLEMS WITH DXFRS AND SEGMENTED APPS

Fixpak6

No additional instructions provided for Fixpak6.

APARs in Fixpak6

Fixpak6 contains support for the following list of APARs:

PN91525: EZERT8 ALWAYS RETURNS AN 8
PQ02066: SPECIFYING '*' FOR CONTABLE FOR C++ GENERATION IS IGNORED
PQ02834: SYS3175 ACCESS VIOLATION IN EFKZGN1.DLL DURING GENERATE.
PQ03436: AFTER APAR PQ00216 APPL NEEDS A ENTRY IN LINKAGE TABLE.
PQ03734: ALLOW DL/1 AND SQL ON MVS TSO GENERATION
PQ03735: FOLDING OF CLASS NAMES
PQ04007: GETTING WALKBACK WHEN TESTING IN ITF A WINDOW THAT CONTAINS A MORPHED NOTEBOOK
PQ04200: VISUALGEN HELP MAP REDISPLAYED WHEN TRYING TO RETURN TO VISUALGEN APPLICATION MAP UNDER AIX.
PQ04811: NUMERIC MAP VARIABLES HAVE WRONG LIMIT
PQ04833: MSGEZE4318E TRYING TO GENERATE FOR VSE INCLUDING MAP
PQ04836: EVENSQL FLAG NOT SET FOR PACK EVEN LENGTH ITEM IN VAGEN
PQ04968: CICSCLI SESSION FLASHES BEFORE GUI RUNS
PQ05019: TRAP OCCURS USING "CHANGE IN LIST"
PQ05197: INCORRECT INSERT PROCESSING FOR MSGS CSO7950, CSO7953, CSO7954, CSO7957
PQ05198: OVERFLOW PROBLEMS, NUMBERS IN TRACE NOT SIGNED
PQ05201: ERROR DURING UPLOAD PHASE OF AN MVS CICS GEN FOR MULTIPLE APPLS
PQ05587: WHERE USED IN LIST FUNCTION NOT RETURNING CORRECT MEMBERS UNDER VISUALGEN 2.2.
PQ05596: SQLCODE -1024 (SQLCODE1024) RETURNED FROM DB2/2 WHEN TESTING VISUALAGE GENERATOR APPLICATION.
PQ05651: THE EVENSQL ATTRIBUTE REMAINS UNCHANGED AFTER REDIFINITION OF THE DATA TYPE IN RECORD ITEM DEFINITION.
PQ05794: AFTER FIXPACK5, THE LOCAL GENERATOR GETS STARTED WHAN LAN GENERATE IS REQUESTED.
PQ05887: UNABLE TO CALL MQ CLIENT FROM VISUALAGE GENERATOR WINDOWS 95 CLIENT.
PQ05905: SOCKET ERROR
PQ06486: MSGEZE5090E UNDEFINED OBJECT DOES NOT UNDERSTAND PROCESSMNEMONICANDACCELERATORS:EXCLUDING: IS RECEIVED
PQ06790: VG COMPILE ERROR. THE GENERATED SCRIPT FILE HAS MISSING CODE LIKE ' '
PQ06895: 1024 SQL ERROR
PQ07348: ERROR EXECUTING NMAKE COMMAND WHILE PREPARING VISUALGEN C++ CALLED BATCH APPLICATION.
PQ07955: YYYYMMDD TO BIN 9
PQ08011: DATA LOST WHEN PASSING WORKING STORAGE RECORD BETWEEN GUI APPLICATIONS.
PQ08403: /LISTING AND A MODIFIED DL/1 CALL DEFINITION
PQ08490: CLOSE WIDGET AND CDV PROBLEM
PQ08623: CANNOT START TWO TCP SERVERS ON THE SAME MACHINE
PQ09309: ROLL NEW CICS CLIENT MESSAGES BACK TO V2.2
PQ09387: SOFT ERROR CODE LOST WHEN CONVERSION IS USED
PQ09523: CELLVALUE CHANGE EVENT ERROR IN MIXED DATA (DBCS, SBCS)
PQ09526: CPD0030 COMMAND SUBMIT_CMD IS LIBRARY *LIBL NOT FOUND. DURING VAGEN APPLS GENERATION TO OS/400 SYSTEM.
PQ09628: COMPILE ERROR: " 'EZEFILE-FRELTST-REL-KEY-EXT' NOT DEFINED NAME IS RECEIVED WHEN GENERATING APPLICATIONS USING RELATIVE FILES
PQ09630: MSGLNC1409-COMPILER ERRORS ON RELATIVE RECORD I/O APPLICATION
PQ04328: ERROR ELA00024P, CONVERSION ELACNENU TABLE NOT LOADED
PQ05180: VISAULGEN WGS INCORRECTLY ROUNDS PACKED DECIMAL FIELD.
PQ05593: VISUALAGE GENERATOR WGS FOR NT SUPPORT FOR MICROSOFT VISUAL C++ VERSION 5.0.
PQ06293: UNRESOLVED EXTERNAL ERROR LNK2029 LINKING CICS/NT CALLED APPL
PQ08143: FCW0012E LOAD MODULE FCWMDB? CANNOT BE LOADED. RETURN CODE IS 2
PQ09871: NO ERROR MESSAGES PRODUCED WHEN DXFR'ING TO TRANSID
PQ09872: PACF LEVEL77 DATA TYPES PASSED INCORRECTLY ON A CALL
PQ09874: INCORRECT DATA RETURNED ON SCAN OF ALTERNATE SPEC
PQ09875: INCORRECT DATA RETURNED ON SCAN OF ALTERNATE SPEC
PQ09876: C/S APPS OS/2 GUI TO NT USING FCW.RSC AND SQL RESULT IN ERROR WITH FIXPK5 CODE.

Fixpak5

Windows 95 or Windows NT Clients Accessing AS/400

Fixpak5 provides client/server support for running Windows 95 or Windows NT clients accessing the AS/400. This support uses the new 32-bit Client Access/400 for Windows 95/NT product. You must install Windows NT Version 4.0 because it is a prerequisite of Client Access/400. You might find the following sample linkage table entry useful.

     :calllink applname=MYAPP linktype=REMOTE library=MYLIB remotecomtype=CA400
            location=MYSYSTEM contable=BINARY parmform=OSLINK

Use of TeamConnection for Library MSLs

VisualAge Generator Version 2.2 Fixpak5, TeamConnection Version 2 Fixpak 4, and DataAtlas Version 2 can now work together.

If you use TeamConnection for Library MSLs, Fixpak5 pre-reqs TeamConnection Version 2, Fixpak4. All VisualAge Generator fixpaks starting with Fixpak5 and future fixpaks will not work with any level of TeamConnection Version 1 or levels prior to TeamConnection Version 2.

Getting TeamConnection Version 2 Fixpak4 from the FTP Site

FTP from the ps.boulder.ibm.com ftp site. The directory structure is as follows:

   
    ps/products/teamconnection/fixes

If you have difficulty obtaining the TeamConnection Version 2 Fixpak4, append to the TEAMC forum on IBMPC and explain your problem.

Limiting the Number of Images Shipped of Workgroup Services for AIX

Starting with Fixpak5, we will ship only two images for VisualAge Generator Workgroup Services for AIX. We want to make it less confusing for you and also reduce our maintenance costs. Most of you will install the "T" image. If you are using DB2/6000 PE, DataJoiner, or certain versions of DB2/6000, you will probably need to relink the DB2 interface modules (fcwmdb2.dll and csodb2.dll). Instructions for relinking to the DB2 interface modules are included in the /usr/lpp/vgwgs22/samples directory. as follows:

Images for VisualAge Generator Workgroup Services for AIX V2.2

The following Workgroup Services for AIX install images are shipped in Fixpak5:

vgwgs22.img
- AIX 3.2.5
- DB2/6000 V1.1 or later
- DB2/6000 PE V1.1 or later
- DataJoiner V1.1 or later
- Will only support native AIX applications (non-CICS)
vgwgs22t.img
- AIX 4.1 or later
- DB2/6000 V2.1 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/6000 Fixpak3 (if Transaction Server installed)
- Will support both native and CICS applications

Java Support

Fixpak5 contains VisualAge Generator Java support. To install VisualAge Generator Java support, do the following:

During the installation process, the file JAVAO.CMD or JAVAW.BAT is loaded into your VisualAge Generator root directory.
Create an VAGJAVA directory anywhere on an HPFS or NTFS drive.

Change to the VisualAge Generator root directory. See the following example:

      Example1:  c:\ezerdev2 - default for VisualAge Generator Developer for OS2
      Example2:  c:\vgwgs2   - default for VisualAge Generator WGS for OS2
      Example3:  c:\vgwgsnt  - default for VisualAge Generator WGS for NT
      Example4:  c:\ezewin   - default for VisualAge Generator GUI Runtime for 
                                        NT or 95

To install Java support on OS2, enter the following:
```
    JAVAO  VAGJAVA-path
```
For example, if the VAGJAVA path is c:\mydir\vagjava, then enter the following:
```
    JAVAO C:\MYDIR\VAGJAVA
```
To install Java support on Windows NT or WIndows 95, enter the following:
```
    JAVAW  VAGJAVA-path
```
For example, if the VAGJAVA path is c:\mydir\vagjava, then enter the following:
```
    JAVAW C:\MYDIR\VAGJAVA
```
Include the VAGJAVA path in the CLASSPATH environment variable list of directories to make VisualAge Generator Java classes accessible to JAVA.
Use your favorite browser to view the csojava.html file in the VAGJAVA directory to find out how to use VisualAge Generator Java support.

GUI Definiton New and Changed Functions

#userInputConvertError Event of the Container Details View

The event #userInputConvertError of the Container Details View now provides the programmer with more information about the cell that contains invalid user input. It also allows a way for a valid value to be put in the error cell instead of the default behavior, which is the last valid value put back in that cell.

When you type an invalid value in a cell of a Container Details View, event #userInputConvertError is signalled with a cell error callback data object that contains the information about the cell that is in error. This object provides the following attributes:

#newValue: This attribute is the new string that is typed into the cell. This value is not valid for this cell. If this attribute is set to another valid string when this event occurs, the valid value is placed in the cell. If this attribute is left unchanged when this event occurs, the last valid value of this cell (#oldValue) will be put back in the cell.
#oldValue: This attribute is the last valid string committed for this cell. If attribute #newValue is not changed after the event has been processed, the #oldValue string is placed in the cell to replace the invalid value.
#oldConvertedValue: This attribute is the last converted value for this cell based on #oldValue. #oldValue is the raw string that was typed, and #oldValue is converted based on the column's data type into #oldConvertedValue.
#row: This attribute is the row number of the cell in error. Row starts from 1.
#column: This attribute is the column number of the cell in error. Column starts from 1.
#error: This attribute is the error object that was signalled with this event before the change. It is part of the interface to maintain compatibility.

#userInputConvertError Usage Examples

Connect the Container Details View event #userInputConvertError to #self attribute of a variable. When an error occurs, the variable will hold the cell error callback data object that is signalled with this event.
Connect the Container Details View event #userInputConvertError to the #prompt action of a text prompter to prompt the user for a valid value.
Connect #answerString attribute of the text prompter to #newValue attribute of the variable. (You will have to connect to an unlisted attribute of the variable and when prompted for the unlisted attribute name, type "newValue" without the "#").

These connections cause a text prompter to display when an invalid value is typed into one of the cells and focus is then moved somewhere else. If a valid value is typed into the prompter when "OK" is pressed, that valid value is entered into the error cell and committed. If an invalid value is typed, the prompter remains displayed until either a valid value is typed or "Cancel" is pressed. If "Cancel" is pressed, the last valid value in that cell is place back into the cell.

To place a valid value back into the cell, the #newValue attribute of the variable has to be set in the process of handling the event #userInputConvertError. After the event occurs, setting #newValue attribute will not have any effect.

#asOrderedCollection Action Added to Occurs Data Item (Array Data Item)

The #asOrderedCollection action returns an orderedCollection of orderedCollection of values of the Occurs Data Item, which can be viewed as a table of values. This is different from the result of the #getValues:from:to: action or the value of the #data attribute of the Occurs Data Item, since the two results in an orderedCollection of strings (1 dimension) instead of a table of values.

For example, define an Occurs Data Item as follows:

    Item name   Level
    ADDRESS     10
    STREET    15
    CITY      15
    STATE     15
    ZIP       15

The #asOrderedCollection action of ADDRESS returns an orderedCollection of orderedCollection of street, city, state, and zip as separate strings. If this result is connected to Container Details View items, the column's attribute you want displayed can be set to 1 instead of "STREET data", 2 instead of "CITY data", and so on.

The #getValues:from:to: action returns an orderedCollection of orderedCollection of concatenated strings of street, city, state, zip. There is no way to break up this result into multiple columns except to break the strings into 1 character for each column.

TCP/IP Native Support

Fixpak5 includes new support for native TCP/IP. This support replaces the existing VisualAge Generator middleware support currently being used.

The documentation for this new support is located in the README.TCP file.

CICS/6000 Pseudoconverstational AIX Image

The AIX image for CICS/6000 pseudoconversational is available upon request by contacting IBM VisualAge Generator Level2 support.

APARs in Fixpak5

Fixpak5 contains support for the following list of APARs:

PN87886: VISUALGEN ITF DOES NOT HANDLE VARGRAPHIC DATA CORRECTLY
PN88140: WRONG OUTPUT ON A MAP AFTER THE SECOND TIME OF CONVERSION IN THE ITF.
PN90770: "UNDEFINEDOBJECT DOES NOT UNDERSTAND EZEFEC" WITH CURRENT SQL ID DEFINED
PN91098: CSO7040E MESSAGE DISPLAYED WHEN PASSING EZEDLPSB
PN91786: FCWMAKE DOES NOT DETECT FAILURE OF APPLICATION PREP FOR AIX.
PN92762: VISUALAGE GENERATE BUILDS INCORRECT GEN.CMD FILE WHEN LAN BASED GENERATION OPTION IS SPECIFIED.
PQ00261: DXFRS NOT FREEING UP STORAGE IN VM.
PQ00699: FCWRUN CAUSED "ILLEGAL INSTRUCTION" WHILE EXIT FROM BATCH APPLICATION.
PQ00897: FCW0033E ISSUED ON DIVISION STATEMENT THAT HAS A TWO BYTE NUMERIC DATA ITEM DIVIDED BY A CONSTANT 4.0 VALUE.
PQ01939: AN 'IF' PROCESSING STATEMENT COMES OUT WITH DIFFERENT RESULTS IN ITF AND IN A GENERATED OS/2 C++ ENVIRONMENT
PQ02201: CLIENT/SERVER USER EXIT WILL RETURN NULLS FOR DATABASE UID/PWD
PQ02568: LAN GENERATION PROBLEMS WITH DB2 APPLS DUE TO MEMORY LEAKS
PQ02649: MESSAGE UNABLE TO LOAD TABLE RC=2
PQ02777: AIX GARBAGE IN EZEUSRID
PQ02790: AIX SQL COLUMN NAME IN DATE GENERATION
PQ02815: EZETST RETURNS ZERO VALUE IF RETR COMMAND IS NOT ISSUED
PQ02858: UNDER WINDOWS, READ-ONLY CENTER-ALIGNED TEXT CAN BE DELETED INCORRECTLY
PQ02993: LOOP OCCURS WHILE PRINTING VISUALGEN MEMBER.
PQ03027: COMPILE ERROR ON DBCS/MIXED STRING IN GENERATED COBOL PRODUCED BY VISUALAGE GENERATOR.
PQ03116: DEVELOPER HANGS WHILE TRYING TO OPEN GUI
PQ03264: DOES NOT UNDERSTAND ITFPCBS
PQ03267: CALLING MVS/CICS APPLICATION VIA DCE RESULTS IN PARAMETER ERROR
PQ03318: MEMORY LEAK CAUSES GEN TO HANG DUE TO /LISTING
PQ03390: TAKE LONG TIME TO DISPLAY GUI ON VG2.2
PQ03983: CORRECT ERROR HANDLING WHEN FCW0090 RECEIVED
PQ04095: AN IF PROCESSING STATEMENT COMPARING TWO DATA ITEMS ENDS ABNORMALLY IF ONE OF THE ITEMS ARE IN 'SET EMPTY' STATUS
PQ04105: CUSTOMER WANTS A FORM INPUT CHECKER ON THE CDV THAT SIGNALS THE END USER WHICH OBJECT THE ERROR OCCURRED IN.
PQ04174: VA GENERATOR 2.2 DEVELOPER TRAPS ON INVOCATION.
PQ04230: ERROR IN <APP>Z.CMD FILE FOR APP WITH MAP AND HELP MAP
PQ04642: MISSING LINE ON MAP IS APPLICATION ISSUES A SET MAP PAGE PRIOR TO DISPLAYING A MAP.
PQ04654: -805 ON OPEN CURSOR
PQ04693: WHERE USED TRAPS SEARCHING DL/I PROCESS
PQ04695: VG FAILS TO LOAD WITH OS/2 FIXPAK 29 ON BIDI SYSTEM
PQ04746: LOOP OCCURS WHILE PRINTING VISUALGEN MEMBER.

Fixpak4

Rebind of Database Required

Fixpak4 requires the VisualAge Generator Developer to be rebound to the database to develop, test, and generate DB2 applications. The physical file names for the bind files for VisualAge Generator are EZE2DB1.bnd and EZE2DB2.bnd. The new package name associated with EZE2DB1.bnd is DEVELOP.EZE21F4 (was DEVELOP.EZE22DB1). This bind file is used with DB2/2 Version 1. The new package name associated with EZE2DB2.bnd is DEVELOP.EZE22F4 (was DEVELOP.EZE22DB2). This bind file is used with DB2/2 Version 2.

VisualAge Generator V2.2 and TeamConnection V2 Working Together

Function has been added to VisualAge Generator Fixpak4 that enables operation between VisualAge Generator Version 2.2 and TeamConnection Version 2. This is the same function that was made available earlier as FixpakTC. Therefore, this fixpak (Fixpak4) pre-reqs TeamConnection Version 2 Fixpak3 for those customers using library MSLs. All VisualAge Generator fixpaks starting with Fixpak4 and any future fixpaks will not work with any level of TeamConnection Version 1 or earlier levels of TeamConnection Version 2, as all future VisualAge Generator Version 2 fixpaks will contain this function.

The availability of this function provides significant performance improvements in the operation between VisualAge Generator and TeamConnection Version 1, as well as raising restrictions on database size.

As Fixpak4 is cummulative, there is no need to install Fixpak3 or FixpakTC first, as was necessary with FixpakTC. If you have installed either of these, you can safely install Fixpak4 over them.

Getting TeamConnection Version 2 Fixpak3 from the FTP Site

FTP from the ps.boulder.ibm.com ftp site. The directory structure is as follows:

   
    ps/products/teamconnection/fixes

If you have difficulty obtaining the TeamConnection Version 2 Fixpak3, append to the TEAMC forum on IBMPC and explain your problem.

New Native TCP/IP Support

Fixpak4 provides new native TCP/IP support. Refer to the readme.tcp file for complete details.

Using NLS-JPN on DBCS Windows 95

GUI runtime messages incorrectly search for English language files (*E.MPR) causing error message EZE4387E to display. APAR PN91062 has been opened to address this problem and will be fixed in a future release. As a workaround, rename the *J.MPR files to *E.MPR.

APARs in Fixpak4

Fixpak4 contains support for the following list of APARs:

PN86145: OS/400 GEN0233 READ/WRITE ERROR ON SEQ FILE WHEN BOTH ADDS AND SCANS AGAINST A SEQUENTIAL FILE
PN90088: HELP MAPS NOT SHOWN AFTER GENERATING THE APPLICATION IN AIX
PN91322: WALKBACK TRYING TO CALL 32BIT MQ DLL FROM WINDOWS 3.1
PN91335: PRESS OF PF1-PF12 KEYS ARE NOT RECOGNIZED DURING HOST RUNTIME ALTHOUGH PF1-12=PF13-24 OPTION IS SET IN APPLICATION DEFINITION
PN91372: A NUMERIC MAP FIELD WITH MIN. VALUE OF '0' AND MAX. VALUE OF'1' THE MSG FCW0057E DOESN'T OCCURS IF LARGER VAL. WILL BE INSERTED.
PN91498: VISUALGEN DOES NOT HANDLE A 28 DBCS CHAR STRING CORRECTLY
PN91634: WGS ISSUES A SUPERFLOUS DB2START, SLOWING EXECUTION TIME.
PN92079: THE LIMIT FOR INPUT DBCS NUMBER OF TEXTBOX DOES NOT WORK
PN92184: VAGEN ITF: EZEUSRID IS NOT INITIALISED FROM USERID FIELD.
PN92225: "MSGEZE5090E AN ERROR HAS OCCURRED: DOES NOT UNDERSTAND" ISSUED WHEN RUNNING OS/2 GUI APPLICATION.
PN92467: MSGEZE4325E IN EZEDB2.DLL WITH PACKETING CONTAINER DETAILS
PN92713: DB2/6000 V2.1PREP PRODUCES ERROR MESSAGE SQL0010N
PN92727: SEGMENTATION VIOLATION IN FCWTRACE.__MM__3STRFI AT OFFSET 0X305C
PQ00033: DBCS DATA IS NOT GENERATED TO CORRECTLY.
PQ00070: INCORRECT VALUE FOR A FORMATTED TEXT PART WITH A FORMAT STRING O OF: FLOAT AND AN EDIT MASK OF : 999999D99
PQ00163: RUNTIME ERROR OCCURS WHEN SQL30081N IS RETURNED TO VISUALGEN DEVELOPER.
PQ00175: MULTIPLE FIRINGS ON A VARIABLE PART, PN90489 ALREADY INSTALLED.
PQ00178: MSGIGYPS2120-S DURING THE COMPILE OF SOURCE GENERATED BY VISUALGEN.
PQ00209: MIGRATING FROM CSP VSE TO VISUALGEN, PROBLEM WHEN DISPLAYING MAP THAT IS 1 LINE LONG AND BEGINS WITH A LITERAL.
PQ00211: YEAR2000 PROBLEM FOUND IN 2AD TESTING
PQ00254: ERROR PASSING EZEDLPCB
PQ00388: EDITCELLCOORDINATE ATTRIBUTE DOES NOT EXIST FOR THE TABLE PART
PQ00440: AE - APAR FIX COMPLETION FOR PN91611
PQ00545: CICS CLIENT TO CICS/6000 ELACSV PROBLEM
PQ00658: EZE2IMG ENDS ABNORMALLY WHEN CALLING VG C++ DLL
PQ00690: CANNOT OPEN CDV COLUMN'S SETTINGS ON VG 2.2
PQ00698: MIXED DATA CONVERTED INCORRECTLY FROM ASCII TO EBCDIC
PQ00715: CALL TARG (REPLY NOT RECEIVING ESCAPE MESSAGE
PQ00894: CICS CLIENT RETURNS RC=-8 INTERMITTENTLY
PQ00939: AIX- WHEN USING DB2 V1.2, USERID AND PASSWORD IGNORED ON CONNECT
PQ00951: ERRORS GENERATING A MESSAGE TABLE.
PQ01029: MEMBER LIST ASSOCIATES DOES NOT LIST EMBEDDED GUIS
PQ01395: PROVIDE COMPATIBILITY SUPPORT FOR LOCAL CICS DB2 DATABASES AND REMOTE DB2 USER DATABSES IN VISUALAGE WORKGROUP SERVICES.
PQ01480: RC101 EXCLUSIVE SEMAPHORE ALREADY OWNED
PQ01483: JOBS FAIL BECAUSE THEY DO NOT RECEIVE EXCLUSIVE USE OF VISUALGEN LIBRARIES.
PQ01621: COMPARE BETWEEN CHARACTER DATA ITEM AND NUMERIC DATA ITEM DOES NOT WORK ANYMORE AFTER INSTALL FIXPAK13 +
PQ01648: IGYPA3055-S ON COMPILING VA COBOL GENED BY VISUALGEN
PQ01649: TWO SEVERE ERRORS AROUND THE TABLE PROGRAM ON A HOST ARE DETECTE
PQ01683: MSGFCW0049E AND FCW0051E FOR LUWCONTROL=CLIENT.
PQ01807: SET RECORD SCAN THEN SCANBACK RETRIEVES WRONG RECORD
PQ01899: DYNAMIC APPLICATION PARTITIONING DOESN'T HANDLE NESTED PROCESSES
PQ02009: CHANGE HEADING ETCHING DEFAULT FOR CDV
PQ02016: SYS3175 IN EZE2LIB CREATING WORKING STORAGE RECORD
PQ02100: SYS3175 IN EZE2IMG.EXE OR SQL0900N SQLSTATE 08003 ON FIRST SQL PROCESS AFTER CHOOSING RESTART TEST OPTION FROM TEST FACILITY.
PQ02101: VISUALGEN ITF: EZERT8 NOT UPDATED WITH ZERO RETURN CODE FROM A CALLED APPLICATION.
PQ02106: THE LIMIT FOR INPUT DBCS NUMBER OF TEXTBOX DOES NOT WORK
PQ02123: ERROR BY GETTOPINDEX ON VISUALGEN V2.2
PQ02193: FMT MODULES NOT GENERATED CORRECTLY FOR DBCS CONSTANT MAP FIELDS
PQ02243: DB2 WHERE CLAUSE DISAPPEARS AFTER .ESF IMPORT
PQ02306: PRESERVE USER ID OF SOURCE MEMBER WHEN ADVANCE TO TARGET MSL
PQ02331: CANNOT CHANGE PUSH BUTTON LABELS WHEN THE DATA TYPE IS STRING
PQ02544: SYS3175 IN EZE2CMN OR EZE2UTB
PQ02549: SYSTEM ERROR EZE1UTB - SYS3170
PQ02571: WALKBACK ERROR DUE TO #REMOVESELECTEDTEXT RENAMED IN V2.2
PQ02572: MORPHING AN OS/2-WINDOWS NOTEBOOK WITH HELP CAUSES WALKBACK
PQ02575: CHANGE IN ATTRIBUTE #REFRESHENTIRELISTONCHANGE DEFAULT CAUSES COMPATIBILITY PROBLEMS
PQ02576: WALKBACK SETTING EMPTY STRING TO A TEXT VIEW WITH DATATYPE TIME
PQ02578: SIGNALLING OF #ITEMS OF A CDV CHANGED IN V2.2
PQ02580: SELECTIONINDEX OF DROPDOWN VIEW CAUSES DIFFERENT BEHAVIOR
PQ02597: CL COMPILE FAILS WHEN SEQUENCE NUMBERS EXCEED 9999
PQ02725: ON OS/400, INDEXED RECORDS ARE LOCKED DURING READ
PQ02735: AIX PERFORMANCE ENHANCEMENTS
PQ02737: RESET LENGTH ON CICS TS WRITEQ
PQ02777: AIX GARBAGE IN EZEUSRID
PQ02778: SQL -501 ON CLOSE
PQ02779: CICS/6000 PRINTING SKIPPING OUTPUT
PQ02780: PROVIDE USERID AND PASSWORD VIA ENVIRONMENT VARIABLE

Fixpak3

DCE Support

If you use the DCE communications protocol, you MUST upgrade all of your clients (GUI runtime and C++ Workgroup Services) and servers (C++ Workgroup Services) to Fixpak3 at the same time. Failure to do so will result in the following error when the client attempts to make a call to the server:

    CSO7801  An error was encountered while performing DCE API call
    rpc_ns_binding_import_next.  The DCE error string is No more bindings.

DCE to MVS CICS

Using DCE to call server applications on MVS CICS is very much like using DCE to call applications running on OS/2, Windows NT, or AIX. The differences in linkage table entries for DCE to MVS CICS are listed below. Please refer the Developing Client/Server Applications document for more details on using DCE as a communications protocol.

Remotecomtype=DCECICS
Location is same as for DCE
Serverid is transaction to be invoked on CICS
CDS directory used is /.:/Servers/VAGenerator/MVSCICS (this directory must be created in your CDS).

You can use either parmform=COMMDATA or COMMPTR. To call a VisualGen application that was generated as REMOTE, in your linkage table specify remoteapptype=vg and parmform=COMMDATA.

See APAR PN84536 for details on setup requirements for MVS.

DCE to MVS IMS

Using DCE to call server applications on MVS IMS is very much like using DCE to call applications running on OS/2, Windows NT, or AIX. The differences in linkage table entries for DCE to MVS IMS are listed below. Please refer the Developing Client/Server Applications document for more details on using DCE as a communications protocol.

Remotecomtype=DCEIMS
Location is same as for DCE
Serverid is transaction to be invoked on IMS
CDS directory used is /.:/Servers/VAGenerator/MVSIMS (this directory must be created in your CDS).

See APAR PN84536 for details on setup requirements for MVS.

DCE to VM

Using DCE to call server applications on VM is very much like using DCE to call applications running on OS/2, Windows NT, or AIX. The differences in linkage table entries for DCE to VM are listed below. Please refer the Developing Client/Server Applications document for more details on using DCE as a communications protocol.

Remotecomtype=DCEVM

See the VM Host Services APAR for details on setup requirements for VM.

Workgroup Services for AIX

C++ Workgroup Services on AIX was built using a compiler option to optimize performance. The application prepare utility was also modified so that applications are built using the same optimization option. This will improve performance of the application during execution, however, it takes a little longer to prepare (compile/link) the application. If you feel the additional overhead during the prepare phase is not worthwhile, the option can be turned off by performing the following steps:

Edit /usr/lpp/vgwgs22/bin/fcwmake
Go to the following line and remove the "-2":
```
       CCFLAGS="-D_ALL_SOURCE -O2 ...
```

Note:

You will need to have superuser authority to perform the above steps

CICS/6000 Transaction Server

CICS/6000 Transaction Server, PTF3, uses a program extension of .ibmcpp for C++ CICS applications. Transaction Server uses the program's extension to determine what programming language support to use. Prior to this, we used an extension of .dll but are now using the extension .ibmcpp. The change is to remove the extension from the script file, <app>c.scr, which is used to enter the CICS program definitions.

APARs in Fixpak3

Fixpak3 contains support for the following list of APARs:

PN84219: WRONG VALUE IN EZESQLCA, VISUALGEN V2 AND DB2/2
PN84134: RETRIEVE TABLEDEFINITION WHEN DEFINING AN SQL RECORD DOES NOT WORK CORRECTLY IF DB2/2 TABLE CONTAIN COLUMNS OF DATATYPE LOB.
PN85345: COULD NOT USE THE COMMENT IN THE CICSESAV.LKG.
PN87616: GENERATING APPL. THAT USES NO SQL STATS, BUT HAS A SQL RECORD IN THE TABLE AND ADD. RECORD LIST WILL FAIL.
PN88351: PERFORMANCE SLOW ON REFRESH OF TRACE LOG
PN89509: ITF- WALKBACK WHEN FIELD AND ARRAY ON MAP CONTAIN THE SAME NAME
PN89516: ITF KEEPING LOCKS ON MEMBERS AFTER TEST
PN89846: MSGSYS2070 TRAP OCCURS WHEN TRYING TO RETRIEVE SQL RECORD DEFINITIONS
PN90608: USERID MAY NOT BE UPDATED WHEN A MEMBER IS ADVANCED IN MSL CONCATENATION
PN90666: TEST NUMERIC RETURNS TRUE FOR FIELD WITH TRAILING BLANKS
PN90710: WRONG PRINTER CONTROL CHARACTERS IN PRINTERFILE WHEN PRINTING FROM VISUALGEN APPLICATIONS ON OS/400 SYSTEM
PN90796: EZECONCT PARAMETER LIST TO VM SHOULD ALLOW 3 PARAMETERS
PN90868: MESSAGE EZE5061E 'THE EZE2DEVG.HLP FILE CANNOT BE FOUND WHEN YOU TRY TO START THE HELP FUNCTIONS WITHIN A GUI.
PN90966: NUMERIC FIELD ERROR ASSIGNING -5000
PN91030: VISUALGEN CAN NOT HANDLE 2000 YEARS IF THEY USED DATE TYPE (YY:MM:DD).
PN91204: NOT ALL PAGES OF A NOTEBOOK WILL BE DISPLAYEDWHEN IT IS OPENDED VIA ('P-BUTTON1',#CLICKED-->'WINDOW1',#OPENWIDGET) SELECTED.
PN91322: WALKBACK TRYING TO CALL 32BIT MQ DLL FROM WINDOWS 3.1
PN91398: INCORRECT DESCRIPTOR STRUCTURE BUILT BY ITF CAUSES CONVERSION ERROR
PN91413: FIRST BYTE OF THE EZESQLCA IS TRUNCATED
PN91533: GROUP BOX DISAPPEARS WHEN RESIZING
PN91610: EZESQCOD IS RESET TO 0 AFTER A SUCCESSFULL COMMIT (CALL EZECONCT) ON ITF BUT IT IS NOT ON AS/400 ENVIRONMENT.
PN91611: MATHS RESULTS DIFFERENT BETWEEN TEST UNDER ITF AND C++ RUNTIME EXECUTION
PN91685: EZESEGTR AND EZESEGM NEED TO BE TOLERATED FOR OS/400
PN91746: "UNDEFINED OBJECT DOES NOT UNDERSTAND" MESSAGE FROM VISUALAGE GENERATOR ITF
PN91770: ABEND IN VISUALGEN GENERATION MONITOR ALTHOUGH VALIDATE PHASE COMPLETES WITH NO ERROR
PN92121: COULD NOT USE THE COMMENT IN THE CICSESAV.LKG
PN91562: TRACE FILE FCWTRACE.OUT DOES NOT CONTAIN INFORMATION ABOUT MESSAGE FCW0104E.
PN91693: DUP BRANCH NOT TAKEN
PN91982: DECIMALS GETTING TRUNCATED WHEN OVERIDDING DECIMAL SEPARATOR
PN90750: EZEDLPSB IS NOT PASSED CORRECTLY. CODE GENERATED DOES NOT SETUP THE FCWPARM BLOCK TO HANDLE THE PSB.
PN91949: LOOP USING CSOPRMPT
PN92380: EZEDLPSB NOT PASSED CORRECTLY
PN92644: NUMERIC FIELD ERROR ASSIGNING -5000
PN92859: GENERATING APPL. THAT USES NO SQL STATS, BUT HAS A SQL RECORD IN THE TABLE AND ADD. RECORD LIST WILL FAIL.
PN91562: TRACE FILE FCWTRACE.OUT DOES NOT CONTAIN INFORMATION ABOUT MESSAGE FCW0104E
PN91693: DUP BRANCH NOT TAKEN
PN91982: DECIMALS GETTING TRUNCATED WHEN OVERIDDING DECIMAL SEPARATOR
PN92173: MSGSYS2070 TRAP OCCURS WHEN TRYING TO RETRIEVE SQL RECORD DEFINITIONS
PN92863: TEST NUMERIC RETURNS TRUE FOR FIELD WITH TRAILING BLANKS

Fixpak2

VisualAge Generator and TeamConnection

If you use both VisualAge Generator and TeamConnection together, you MUST install VisualAge Generator V2.2 Fixpak2 and TeamConnection V1 Fixpak5 at the same time.

VisualAge Generator V2.2 Fixpak2 is ONLY compatible with TeamConnection V1 Fixpak5. VisualAge Generator V2.2 Fixpak2 will NOT work with TeamConnection V1 Fixpak4, or earlier levels or base version of TeamConnection.

Using VisualAge Generator Workgroup Services on AIX

The CSO message tables for non-English languages (CSOxxx.TAB) were not shipped with VisualAge Generator Workgroup Services for AIX. A workaround is to make a copy of the FCW message table (FCWxxx.TAB) and name it CSOxxx.TAB. The message tables are located in directory /usr/lpp/vgwgs22.

APARs in Fixpak2

Fixpak2 contains support for the following list of APARs:

PN86868: INCORRECT PARAMETER PASSED TO SQLPREP
PN87096: LIGHTPEN DETECTION CAN NOT BE SIMULATED BY A MOUSE DOUBLE CLICK UNDER THE VISUALGEN TESTFACILITY
PN87289: NEW VALUE OF A CELL CAN'T BE OBTAINED USING THE CELLVALUECHANGED EVENT
PN87592: WALKBACK DURING VALIDATION WITH INCORRECT SYSNAME IN RES ASSOCIA
PN87721: EZECLOS DOES NOT WORK IN MAP EDIT ROUTINES
PN88242: PROCESS LIMIT REACHED UNEXPECTEDLY
PN88270: IMPLICIT DATA FIELDS ARE NOT CREATED CORRECTLY IN ITF FOR DECIMAL DATA TYPES
PN88302: REMOVEALL: FROM A LISTBOX DOES NOT REMOVE ITEM FROM LIST.
PN88672: SCAN returns incorrect record
PN88859: ERROR CODE F217 ON VSAM FILE ACCESS ON REMOTE DRIVE
PN89429: ERRORS CALLING A MF DLL FROM A GUI EXECUTING ON WIN95
PN89515: PRESENCE OF AN OS/2 CONTAINER AFFECTS INTERACTION WITH OTHER PARTS
PN89553: WHEN WE COMPILED A PROGRAM THAT USED EZEPURGE,IT FAILED
PN89651: UNABLE TO WRITE OR READ VARIABLE LENGTH SEQUENTIAL RECORDS WHEN USING CICS TRANSIENT DATA QUEUES.
PN89685: MSGEZE4100E OCCURS AT APPLICATION VALIDATION ALTHOUGH THE SQL IS STATEMENT IS OK.
PN89956: MSGFCE0405E EZE FUNCTION WORD NOT HANDLED: WINGUI
PN89992: ITF WALKBACK WHEN REFERENCING A MEMBER THAT HAS BEEN TEMP SAVED
PN89994: WGS FOR AIX- FCWCICSINSTALL SCRIPT POINTS TO V20 INSTALL LIB
PN90026: DUP BRANCH NOT TAKEN
PN90046: SQLCODE-822 IF EXECUTION TIME STATEMENT BUILD IS ON
PN90295: VISUALGEN INITIALIZES DBCS MAPFIELD INCORRECTLY.
PN90386: WHEN WE COMPILED A PROGRAM THAT USED EZEPURGE,IT FAILED WITH 1540-013: (S) "EZELEVEL77" IS UNDEFINED.
PN90684: WHEN WE COMPILED A PROGRAM THAT USED EZEPURGE,IT FAILED WITH 1540-013: (S) "EZELEVEL77" IS UNDEFINED.
PN90749: DATA IS NOT CONVERTED CORRECTLY FROM ASCII TO EBCDIC ON A CALL TO CICS/MVS FROM THE TEST FACILITY USING CICS CLIENT
PN91049: INCORRECT DISPLAY OF DECIMAL FIELDS WHEN THE DECIMAL SEPARATOR
PN91077: MSGEZE5090E CXEZERTNSTATEMENT DOES NOT UNDERSTAND ISEMPTY ISSUED WHEN GENERATING VISUALGEN GUI MEMBER
PN91095: IMPLICIT DATA FIELDS ARE NOT CREATED CORRECTLY IN ITF FOR DECIMAL DATA TYPES
PN91096: "IN" DOESN'T WORK CORRECTLY WHEN THEY EXECUTED THE APPLICATION.
PN91260: PROCESS LIMIT REACHED UNEXPECTEDLY
PN91261: SCAN AFTER UPDATE.
PN91262: ERROR CODE F217 ON VSAM FILE ACCESS ON REMOTE DRIVE
PN91264: DUP BRANCH NOT TAKEN
PN91313: INCORRECT DISPLAY OF DECIMAL FIELDS WHEN THE DECIMAL SEPARATOR IS COMMA.

Fixpak1

Correction to the Installing VisualAge Generator Developer Document

The command to install the Library Reader/2 product was incorrect in the Installing VisualAge Generator Developer document. This information was shipped with the English and Brazillian Portuguese version of the VisualAge Generator product CD. The correct command is as follows:

  
    C:\EZERDEV2\BMGR\INSTALL

The new version of the Library reader/2 uses Software Installer for it's installation and Software Installer uses the INSTALL.EXE.

Online Product Registration Information

The VisualAge Generator Developer for OS/2 V2.2 product has a new online registration utility. The Online Registration Utility is called each time the VisualAge Generator Developer is started. The user is reminded to register approximately once a week until the registration number is entered. One year and two years after the initial registration, the user is prompted to update their registration. At any time the user can update their registration by opening the Software Registration icon in the VisualAge Generator folder.

If you do not want to register and you want to disable the online registration for VisualAge Generator, you can run ARTADMIN.EXE from the EZERDEV2 directory where the product is installed.

New Function

Fixpak1 provides new function for the VisualAge Generator product. The summary of enhancements for the new function is in file READ.ME2 ,which is found in the same internet location as this file (22readme.txt). For a details on the new function, view the EZE2SUPE.BOO file, which will be installed as part of the fixpak.

APARs in Fixpak1

Fixpak1 contains support for the following list of APARs:

PN85817: TEST MONITOR PUSH BUTTONS ARE GRAYED WHEN TESTING GUI APPLICATIONS AND BREAKPOINTS ARE ENCOUNTERED USING VGEN 2.2.0.
PN86185: OS/400 COBOL COMPILES TAKING HOURS TO COMPLETE.
PN86197: CF MAP COLORS PROBLEM
PN86569: SYSTEM ERROR EZE1UTB - SYS3170
PN86621: GUIS IMPORTED FROM VISUALGEN 2.0 TO VISUALAGENERATOR 2.2. USER RECEIVES WALKBACK LOG WHEN WORKING WITH 2 SEPAERATE GUIS.
PN86638: VG 2.0 GUIS DO NOT EXECUTE IN VISUALAGE GEN V2.2
PN86649: EZECLOS DOES NOT WORK IN MAP EDIT ROUTINES
PN86866: PROMOTED FEATURE DISAPPEARS WHEN REOPENING GUI
PN86868: INCORRECT PARAMETER PASSED TO SQLPREP
PN87178: DYNAMICALLY CHANGE EZEDEST
PN87326: WALKBACK TRYING TO OPEN GUI WITH NOTEBOOK IN ITF
PN87665: INCORRECT GEN OUTPUT FOR TABLE GEN FOR WINNT AND NTCICS
PN87960: APPLICATION PREPARATION COMPLETES WITH RC4 BECAUSE OF WARNING MESSAGE LNK4030 IN THE LINKSTEP.
PN87961: MAP GENERATED FOR AIX SHOWS 9999.8 INSTEAD OF 9999.9 IN A FIX DECIMAL(5,1) DATA ITEM
PN88481: A WAY IS NEEDED TO SET EZEUSR AND EZEUSRID WHEN RUNNING C++ APPLICATIONS IN OS/2 AND WHEN CALLING THEM FROM ITF.
PN89410: GUI CLIENT APPLICATION ACCESSING VSAM RRDS ON THE HOST RECEIVES ABENDASRA IN THE INITIALIZATION SESSION OF THE COBOL SERVER APP.
PN89412: SET RECORD SCAN / SCANBACK DIFFERENCES
PN89413: CICS/6000 NEEDS TO USE X38 TO DENOTE DBCS FIELDS INSTEAD OF XF8
PN89414: EZELTERM DOES NOT GET INITIALIZED WITH THE CICS TERM IDENTIFIER
PN89415: APPLICATION PREPARATION COMPLETES WITH RC4 BECAUSE OF WARNING MESSAGE LNK4030 IN THE LINKSTEP.
PN90385: DYNAMICALLY CHANGE EZEDEST
PQ00545: VA C++ APPS CALLING CICS WORKSTATION APPS USING CICS CLIENT AND GENERATION TIME BINDING OF LINKAGE TABLE PARAMETERS.

Getting Help

If you need help with a problem, U.S. customers can call our support number at 1-800-237-5511. Non-US customers can contact their local support representatives or support centers.