IBM VisualAge Generator V3.1 FixPak3 Readme

This VisualAge Generator V3.1 FixPak3 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.

FixPak3

Before Installing FixPak3

Before beginning FixPak3 installation, do the following:

Please shut down the VisualAge Generator Developer and save your image.
VisualAge Generator v3.1 FixPak3 requires VisualAge for Smalltalk Enterprise FixPak4.5a. This FixPak is installed automatically when you install FixPak3 on the VisualAge Generator Developer client. The FixPak4.5a feature will also automatically be loaded when you load the VisualAge Generator Developer FixPak3 feature. No additional action is required on the VisualAge Generator Developer client machine.
If you generate printer maps for MVS or VM systems for languages other than U.S. English, do NOT install FixPak3 without also installing the host LE COBOL APAR PQ16766.
As a precaution, back up your VisualAge for Smalltalk Enterprise installation. Make a note of any features that you have currently installed because you may need to reload them once the FixPak files are installed.

Product Enhancements, Problem Support, and Limitations

VisualAge Generator V3.1 FixPak3 contain enhancements, problem support, and limitations for the following:

Additional Compiler Support:

FixPak3 of VisualAge Generator version 3.1 introduces additional compiler support for generation. You may now use IBM VisualAge C++ 3.6 on AIX, OS/2 and Windows NT platforms.
Windows NT
On Windows NT, the IBM C and C++ Compiler V3.6 is now being supported. The older compiler, IBM C++ Compiler V3.5 is being phased out. For customers that have not been able to upgrade to the V3.6 compiler, VisualAge Generator is still providing runtime support for the old compiler. This support will be removed in a later FixPak. If problems are reported that turn out to be compiler related and you are using the old compiler, fixes will not be available. Make sure that you install the appropriate version of VisualAge Generator Server and Common Services depending on which compiler is being used. The install program will make sure that the FCWCOMP environment variable is set accordingly. It should be set to one of the following values:

FCWCOMP=VAC++ if using the IBM C and C++ Compiler V3.6

FCWCOMP=VAC++35 if using the IBM VisualAge C++ Compiler V3.5

FCWCOMP=MSVC++ if using the Microsoft Visual C++ Compiler V5.0 or V6.0

If using the IBM C and C++ Compiler V3.6, then perform the following steps:

Add the compiler bin directory to the PATH environment variable in the system environment (X:\ibmcxxw\bin), where X is the drive the compiler was installed.

Set FCEOPT=1 in the system environment. This will cause the preparation step to automatically run the setenv.bat command to setup the environment.

Note: IBM VisualAge C++ Compiler V3.5 is no longer officially supported by IBM, please upgrade to the IBM C and C++ Compiler V3.6. VisualAge C++ Compiler V4.0 is not supported by VisualAge Generator.

OS/2 Warp
IBM C and C++ Compiler V3.6 is now being supported. The older compiler, IBM C++ Compiler V3.5 is being phased out. For customers that have not been able to upgrade to the V3.6 compiler, VisualAge Generator is still providing runtime support for the old compiler. This support will be removed in a later FixPak. If problems are reported that turn out to be compiler related and you are using the old compiler, fixes will not be available. Make sure that you install the appropriate version of VisualAge Generator Server and Common Services depending on which compiler is being used. The install program will make sure that the FCWCOMP environment variable is set accordingly. It should be set to one of the following values:

FCWCOMP=VAC++ if using IBM C and C++ Compiler 3.6

FCWCOMP=VAC++30 if using IBM VisualAge C++ Compiler V3.0

Note: IBM VisualAge C++ Compiler V3.0 is no longer officially supported by IBM, please upgrade to the IBM C and C++ Compiler V3.6. VisualAge C++ Compiler V4.0 is not supported by VisualAge Generator.

AIX
IBM C and C++ Compiler V3.6 is now being supported. The older compiler, IBM C Set ++ V3.1.4 is no longer supported and is being phased out. For customers that have not been able to upgrade to the V3.6 compiler, VisualAge Generator is still providing runtime support for the old compiler. This support will be removed in a later FixPak. If problems are reported that turn out to be compiler related and you are using the old compiler, fixes will not be available.
There are two additional install images that are being shipped that contain support fot the old compiler:

vgwgs31x.img - install this image on non-CICS systems that have the IBM C Set ++ compiler V3.1.4

vgwgs31y.img - install this image on CICS systems that have the IBM C Set ++ compiler V3.1.4

The 2 install images that are normally shipped with a FixPak are now built with the IBM C and C++ Compiler V3.6.

vgwgs31.img - install this image on non-CICS systems that have the IBM C and C++ Compiler V3.6 installed.

vgwgs31t.img - install this image on CICS systems that have the IBM C and C++ Compiler V3.6 installed.

Note: IBM C Set ++ Compiler V3.1.4 is no longer officially supported by IBM, please upgrade to the IBM C and C++ Compiler V3.6. VisualAge C++ Compiler V4.0 is not supported by VisualAge Generator.

VisualAge Generator and ENVY Privileges:

Privileges are set on an application edition. To change privileges, open the Application Editions Browser by selecting Browse Application Editions from the Tools menu of the System Transcript window. From the browser, select an application and edition. Privileges are then set by selecting a choice from the Editions->Privileges menus. To prevent users from viewing a VAGen part, change the Read Public Source privilege to Group. This will restrict access to the part to those users who are a group member of the application.

Note: This privilege will not be useful for Process and Statement Groups parts, as their contents will still be visible in the Statement Monitor of the Test Facility.

Arabic Character Expansion Using BIDI Conversion Tables:

BIDI attribute conversion for Arabic is modified to support expansion of some Arabic characters from one byte to two on code page conversion, provided there are enough spaces at the end of the character field to support inclusion of the expanded characters.

IC Packaging Instructions:

IC Packaging Beta Customer, please send a note to eberwein@us.ibm.com for instructions to install the IC Packaging feature.

Accessing OS/390 VSAM Files from ITF and C++ Generated Programs

Do you have VSAM files residing on OS/390 that you want to access from a VisualAge Generator program on your workstation? Now you can use the same VSAM file when testing your program that you will use in your production environment. This feature was available for ITF with VisualAge Generator Version 3.1 FixPak1. FixPak 3 introduced automatic data conversion for remote VSAM files.

Software Pre-requisites

The following table shows the list of pre-requisite software that you need to have installed to use the ITF VSAM file support:

System	Local VSAM	Remote VSAM
OS/2	Shipped with IBM VisualAge Generator	IBM Personal Communications AS/400 and 3270 Version 4.11 (or later)
Windows NT	Not Available	IBM Personal Communications AS/400 and 3270 Version 4.11 (or later)
OS/390		IBM DFSMS/MVS Version 1.2 (or later)

Setup Required to Access Remote VSAM Files on OS/390

After installing the required products, configuring APPC, and verifying that you can establish an APPC session with your OS/390 host, you are ready to configure DFM on the workstation.

Setup on OS/2 for FixPak3

Download the file vsamos2.zip from ftp://ps.software.ibm.com/ps/products/visualagegen/info/v3.1 into a temporary directory, unzip it, and follow the instructions in the install readme file.

NOTE: If you have IBM VisualAge for COBOL for OS/2 installed, specifically the SmartData Utilities component, you do not need to install the vsamos2.zip file.

Perform the following steps:

Modify the command files used to start DFM (startdfm.cmd) and indicate the drive letter that should be used for DFM.
Modify the sample configuration file (config.dfm) based on your configuration. Items such as USERID, LOCAL_LU, REMOTE_LU, and the OS/390 target system name must be changed.
If data conversion is required, add the FILE_DESCRIPTOR_MAP keywords to the configuration file. See the section below entitled DFM Data Conversion Setup on OS/2.
Start DFM using the startdfm command.

Refer to VSAM in a Distributed Environment (SC26-7063) for additional information
on configuring DFM for OS/2.

Setup on Windows NT for FixPak3

Download file vsamnt.zip from ftp://ps.software.ibm.com/ps/products/visualagegen/info/v3.1 into a temporary directory, unzip it, and follow the instructions in the install.readme file.

NOTE: If you have IBM VisualAge for COBOL for Windows NT installed, specifically the SmartData Utilities component, you do not need to install the vsamnt.zip file.

Perform the following steps:

Modify the sample configuration file (dfmcfg.rc) based on your configuration.
If data conversion is required, add the FILE_DESCRIPTOR_MAP keywords to the configuration file. See the section below entitled DFM Data Conversion Setup on Windows NT.
Run the dfmcfg command to create the formatted configuration file.
Optionally run the dfmnet command to setup 'shortcut' names.
Run the dfmlogon command to setup userid/password information.

Refer to SdU for Windows Distributed FileManager Users Guide (SC26-7134) for additional information on remote file names, shortcut names, and configuring DFM for Windows NT.

Accessing VSAM Files from ITF

To specify that you want to use VSAM files, do the following:

Select the Options menu on the VisualAge Organizer window.
Select Preferences and the VisualAge Preferences notebook displays.
Select the VAGen - Test General tab.
At the bottom of the page, select the Remote VSAM radio button and click OK.

This will cause ITF to use VSAM files for all file accesses (on Windows NT, there is only remote VSAM file support). In a later FixPak, this option will be moved to the Resource Association Editor so that the type of file accessed can be specified on a file basis. If you have changed your preferences to use Remote VSAM and you do not have the communications software setup and working, you will receive an error.

In addition to changing your preferences, you also need to specify the physical name and path in the ITF Resource Association File editor as follows:

In the Physical name field, specify the file name as it is on your OS/390 system but without the high level qualifier. If the file does not already exist on your OS/390 system, VisualAge Generator will create it for you.
On OS/2, in the Path field, specify the DFM drive letter, a colon, and the high level qualifier specified in the DFM configuration file (config.dfm).
On Windows NT, in the Path field, specify the machine name or a shortcut name using the Universal Naming Convention.

Accessing VSAM Files from C++ Generated Programs

Access to VSAM files from a C++ generated program is determined by the resource association file (RSC). Specify /FILETYPE=VSAM in the ASSOCIATE entry for a VSAM file. Because there is no local VSAM support on Windows NT, all VSAM file access is remote. If you do not have the communications software setup and working, you will get an error. To access a remote VSAM file on OS/2, preface the file name with the DFM drive letter. On Windows NT, specify the file name using the Universal Naming Convention. Refer to the VisualAge Generator Server Guide for OS/2, Windows NT, HP-UX, and AIX for more information on using VSAM and resource association files.

Diagnosing Error Conditions When Using VSAM with ITF

A trace facility has been provided to assist in diagnosing error conditions. The trace is controlled by the HPTTROPT environment variable. Specifying HPTTROPT=1 turns on the trace, specifying HPTTROPT=0 turns off the trace. The trace output is written to a file named hpttrace.out unless you change the name using the HPTTROUT environment variable.

Diagnosing Error Conditions When Using VSAM with C++ Generated Programs

The trace facility for C++ generated programs is controlled by the FCWTROPT environment varaible. Specifying FCWTROPT=31 will turn on trace for file I/O as well as other C++ program related events. The trace output is written to a file named fcwtrace.out unless you change the name using the FCWTROUT environment variable. Refer to the appendix in the VisualAge Generator Server Guide for OS/2, Windows NT, HP-UX, and AIX for more information on the trace environment variables.

Data Conversion

VisualAge Generator is now providing automatic data conversion for host VSAM files in this FixPak. VSAM files on the host systems are typically stored as EBCDIC characters although you can store ASCII data in them as well. VSAM files on the workstation are stored as ASCII characters. If you use the host system just for data storage, you do not need to convert the data to EBCDIC. If however, you want to access the data from programs on your workstation and from programs on the host system, you need to convert the data. ITF will now automatically convert the data between ASCII and EBCDIC.

Known Problems/Limitations

When issuing a SET record SCAN with a key value of x'FFFF' or a key value greater than the highest record in the file, the next-to-last record will be returned instead of the last record in the file.
When accessing variable length records, the length of the record is not returned correctly.
When scanning for an update, the first record of an indexed file is not accessible.
An error message GEN0135 is not issued when a first map is passed on an XFER to an application which is not expecting a first map.

VisualAge Generator Server Support for Oracle

FixPak3 of VisualAge Generator Server version 3.1 introduces access to Oracle databases via the native Oracle8 client for the Windows NT, CICS for Windows NT, AIX, CICS for AIX, and HP-UX platforms. VisualAge Generator Server for all platforms continues to support access to Oracle databases via the native Oracle7 client and on the aforementioned platforms can be configured to use either one. The Oracle8 client is used by default. A VisualAge Generator Server tool called orasetup is provided that allows you to configure the version of the Oracle client that VisualAge Generator Server should use. The orasetup tool is located in the samples directory of the VisualAge Generator Server product installation directory (for example on Windows NT, C:\VGSERVW\samples). For more information about the orasetup tool and configuring the VisualAge Generator Server Oracle modules for your platform, see the orasetup.readme file in the samples directory of the VisualAge Generator Server product installation directory or issue the command orasetup -h from the samples directory.

If you have migrated from the Oracle7 database client to the Oracle8 database client on your machine(s), you may need to relink existing VisualAge Generator Oracle7 applications with Oracle8, depending on the platform you are using. A VisualAge Generator Server tool called orarelink is provided to help automate the migration process. The orarelink tool is located in the samples directory of the VisualAge Generator Server product installation directory (for example on AIX, /usr/lpp/vgwgs31/samples). For instructions on using this tool and to determine possible migration paths for your VisualAge Generator Oracle7 applications for your platform, see the orarelink.readme file in the samples directory of the VisualAge Generator Server product installation directory or issue the command orarelink -h from the samples directory.

Known Limitations:

The Oracle7 and Oracle8 clients cannot be used simultaneously. For example, you cannot use the Oracle7 client for one VisualAge Generator application and the Oracle8 client for another without reconfiguring VisualAge Generator Server in between.
If you are using Oracle's ODBC Driver for Oracle version 8, you may receive the following message when testing your program in ITF. The cause of this problem has not yet been determined. However, the problem is being investigated with Oracle's support team.

The current work around for this problem is to remove all references to date columns from your SQL statement.

Note:

For the Windows NT and CICS for Windows NT platforms, you must set the environment variable FCWDBVERSION in your system or user environment variables before generating or preparing VisualAge Generator Oracle applications or before using the orasetup tool. This new environment variable is required if you are generating and/or preparing VisualAge Generator Server Oracle applications on your Windows NT or CICS for Windows NT system. It specifies the version of the database software installed on the Windows NT or CICS for Windows NT system and is used only when preparing SQL programs for execution on these platforms. It is also used by the orasetup tool when attempting to determine what version of the VisualAge Generator Server Oracle modules are being used. It is not used during runtime. It should be set to one of the following values:

FCWDBVERSION=8 if Oracle8 is installed on the Windows NT.
FCWDBVERSION=7 if Oracle7 is installed on the Windows NT.

This environment variable is not used when preparing DB2 or ODBC programs.

Note:

For the AIX and CICS for AIX platforms, the VisualAge Generator Server Oracle interface modules, fcworcl.dll and csoora.dll, are very sensitive to the version of Oracle for AIX on which they were built versus where they execute. If a VisualAge Generator SQL program is run on an AIX system with a version of Oracle for AIX at a higher release or maintenance level then that with which the VisualAge Generator Oracle interface modules were built, it could receive the following message.

"FCW0012E Load Module fcworcl.dll cannot be loaded. The return code is 2." For information on the release and maintenance levels that the VisualAge Generator Server Oracle interface modules were built with or if you receive FCW0012E during runtime, see the file linkora.readme in the samples directory of the VisualAge Generator Server product installation directory.

List of APARs

The following is a list of APARs in FixPak3:

PQ17784
PQ18146
PQ21842
PQ21989
PQ22588
PQ22827
PQ23122
PQ23564
PQ23917
PQ24533
PQ24570
PQ26819
PQ26916
PQ27296
PQ27575
PQ27708
PQ27749
PQ27894
PQ28162
PQ28600
PQ28659
PQ28946
PQ28951
PQ31358
PQ31356
PQ31456
PQ32362
PQ33051
PQ28585
PQ27748
PQ05722
PQ21932
PQ22334
PQ22776
PQ22951
PQ23103
SINGLE QUOTES AROUND CONFIGURATION MAP NAMES.
PQ23802
PQ24231
PQ24666
PQ25403
PQ25566
PQ27025
PQ27406
PQ29071
PQ29124
PQ29126
PQ30294
PQ30790
PQ31354
PQ11617
PQ23111
PQ23998
PQ307903
PQ21540
PQ22186
PQ23683
PQ27345
PQ27998
PQ10992
PQ11030
PQ13331
PQ13968
PQ17184
PQ21672
PQ23182
PQ23397
PQ23794
PQ23998
PQ25596
PQ25854
PQ26367
PQ27213
PQ27314
PQ27525
PQ27658
PQ27870
PQ28421
PQ28982
PQ29144
PQ29506
PQ30127
PQ30861
PQ31179
PQ33008
PQ09544
PQ11470
PQ15524
PQ21871
PQ22063
PQ22590
PQ22594
PQ22631
PQ22667
PQ23205
PQ25644
PQ25670
PQ25672
PQ25979
PQ27960
PQ29398
PQ30339
PQ30987
PQ31338

VisualAge Generator FixPak3 Installation Notes

The following sections provide FixPak3 installation instructions for FixPak3 on VisualAge Generator.

Obtaining FixPak3 for VisualAge Generator

You may obtain FixPak3 of VisualAge Generator in two ways: (1) download the code from the IBM software support FTP site; or (2) obtain the code in the form of a CD.

FixPak3 Availability From FTP

The address of the FTP site is ftp://ps.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files for FixPak3 are located in the directory /ps/products/visualagegen/fixes/v3.1. You may perform an anonymous logon to this FTP site.
On the FTP site, you will find self-extracting EXE files containing the compressed image of the FixPak3 CD. In order to reduce download times, the image is broken down into language-specific and language-independent files, with the language specific files further separated into the different supported languages. In order to install FixPak3, you have to download several different files depending on your installed products and the language you are using.

Downloading FixPak3 for VisualAge Generator Developer

For Windows NT

Create a temporary directory on your hard drive.
Download the self-extracting executable DVNFP3B.EXE to the temporary directory. The file is located in the BASE directory. It contains the language-independent files for FixPak3.
Download the self-extracting executable DVNFP3x.EXE to the temporary directory. The file contains the language-specific files for FixPak3. "x" stands for the 1-character NLS ID corresponding to your language. The files are located in the directory which is named by the 3-character NLS ID corresponding to your language. (For example, if you are using English, you will download DV2FP3E.EXE located in the ENU directory).
Extract the files contained in the two self-extracting EXE files to the same temporary directory by invoking them with the -d switch.

Note:

For the setup to work properly, you will need to invoke the executable from the Command Prompt with a -d in order to maintain the integrity of the directory structure of the setup files. For example:

DVNFP3x.EXE -d

"x" stands for the 1-character NLS ID corresponding to your language.

At this point you have downloaded the necessary files and created the directory structure necessary to perform the installation. For detailed installation instructions please see the VisualAge Generator Developer Installation Instructions section.

For OS/2 Warp

Create a temporary directory on your hard drive.
Download the self-extracting executable DV2FP3B.EXE to the temporary directory. The file is located in the BASE directory. It contains the language-independent files for FixPak3.
Download the self-extracting executable DV2FP3x.EXE to the temporary directory. The file contains the language-specific files for FixPak3. "x" stands for the 1-character NLS ID corresponding to your language. The files are located in the directory which is named by the 3-character NLS ID corresponding to your language. (For example, if you are using English, you will download DV2FP3E.EXElocated in the ENU directory).
Extract the files contained in the two self-extracting EXE files to the same temporary directory by invoking them with the -d switch from the command prompt.

Note:

For the setup to work properly, you will need to invoke the executable from the OS/2 Prompt with a -d in order to maintain the integrity of the directory structure of the setup files. For example:

DV2FP3x.EXE -d

"x" stands for the 1-character NLS ID corresponding to your language.

At this point you have downloaded the necessary files and created the directory structure necessary to perform the installation. For detailed installation instructions please see the VisualAge Generator Developer Installation Instructions section.

Downloading FixPak3 for VisualAge Common Services

The self-extracting EXE's for Developer and Server already contain the files for CSO. Unless you have CSO alone, you do not need to perform a separate download.

For Windows NT

Create a temporary directory on your hard drive.
Download the self-extracting executable CSNFP3B.EXE to the temporary directory. The file is located in the BASEdirectory. It contains the language-independent files for FixPak3.
Download the self-extracting executable CSNFP3x.EXE to the temporary directory. The file contains the language-specific files for FixPak3. "x" stands for the 1-character NLS ID corresponding to your language. The files will be located in the directory which is named by the 3-character NLS ID corresponding to your language.
Extract the files contained in the two self-extracting EXE files to the same temporary directory by invoking them with the -d switch.:

Note:

For the setup to work properly, you will need to invoke the executable from the Command Prompt with a -d in order to maintain the integrity of the directory structure of the setup files. For example:

CSNFP3x.EXE -d

"x" stands for the 1-character NLS ID corresponding to your language.

At this point you have downloaded the necessary files and created the directory structure necessary to perform the installation. For detailed installation instructions please see the VisualAge Generator Developer Installation Instructions section.

For OS/2 Warp

Create a temporary directory on your hard drive.
Download the self-extracting executable CS2FP3B.EXE to the temporary directory. The file is located in theBASE directory. It contains the language-independent files for FixPak3.
Download the self-extracting executable CS2FP3x.EXE to the temporary directory. The file contains the language-specific files for FixPak3. "x" stands for the 1-character NLS ID corresponding to your language. The files will be located in the directory which is named by the 3-character NLS ID corresponding to your language.
Extract the files contained in the two self-extracting EXE files to the same temporary directory by invoking them with the -d switch.

Note:

For the setup to work properly, you will need to invoke the executable from the OS/2 Prompt with a -d in order to maintain the integrity of the directory structure of the setup files. For example:

CS2FP3x.EXE -d

"x" stands for the 1-character NLS ID corresponding to your language.

At this point you have downloaded the necessary files and created the directory structure necessary to perform the installation. For detailed installation instructions please see the VisualAge Generator Developer Installation Instructions section.

Downloading FixPak3 for VisualAge Generator Server

For Windows NT

Create a temporary directory on your hard drive.

Download the self-extracting executable SRNFP3B.EXE to the temporary directory. The file is located in the BASE directory. It contains the language-independent files for FixPak3.

Download the self-extracting executable SRNFP3x.EXE to the temporary directory. It contains the language-specific files for FixPak3. "x" stands for the 1-character NLS ID corresponding to your language. The language specific files will be located in the directory which is named by the 3-character NLS ID corresponding to your language.

Extract the files contained in the two self-extracting EXE files to the same temporary directory by invoking them with the -d switch.

Note: For the setup to work properly, you will need to invoke the executable from the Command Prompt with a -d in order to maintain the integrity of the directory structure of the setup files. For example:
SRNFP3x.EXE -d
"x" stands for the 1-character NLS ID corresponding to your language.

At this point you have downloaded the necessary files and created the directory structure necessary to perform the installation. For detailed installation instructions please see the VisualAge Generator Developer Installation Instructions section.

For OS/2 Warp

Create a temporary directory on your hard drive.

Download the self-extracting executable SR2FP3B.EXE to the temporary directory. The file is located in the BASEdirectory. It contains the language-independent files for FixPak3 into the temporary directory you created.

Download the self-extracting executable SR2FP3x.EXEto the temporary directory. It contains the language-specific files for FixPak3. "x" stands for the 1-character NLS ID corresponding to your language. The language specific files will be located in the directory which is named by the 3-character NLS ID corresponding to your language.

Extract the files contained in the two self-extracting EXE files to the same temporary directory by invoking them with the -d switch.

Note: For the setup to work properly, you will need to invoke the executable from the OS/2 Prompt with a -d in order to maintain the integrity of the directory structure of the setup files. For example:
SR2FP3x.EXE -d
"x" stands for the 1-character NLS ID corresponding to your language.

At this point you have downloaded the necessary files and created the directory structure necessary to perform the installation. For detailed installation instructions please see the VisualAge Generator Developer Installation Instructions section.

Before Installation of FixPak3

Installation of FixPak3 on OS/2 is performed using IBM Standard Software Installer. For CSO and Workgroup Services, the command you invoke is different depending on the choice of compiler option. Please see below for details.

VisualAge Generator Developer Installation Instructions

For Windows NT

Execute Setup.exe

Using FTP Files
If you downloaded the files from the FTP site, enter the command
<temp>\xxx\HPTDEVI\INSTFIX\SETUP.EXE, where <temp> is the temporary directory you created to host FixPak3, and "xxx" is the 3-character NLS ID.

Note: For example, if you are using Brazilian Portuguese and the temporary directory you selected is called FIXDEV, you would enter the following command in the command line:
FIXDEV\PTB\HPTDEVI\INSTFIX\SETUP.EXE

Using CD
If you are installing from the CD enter the command:
<CD-ROM drive letter>\xxx\HPTDEVI\INSTFIX\SETUP.EXE, where "xxx" is the 3-character NLS ID.

Install FixPak3 for CSO

At the end of the installation, you may be prompted to install FixPak3 for CSO. If FixPak3 for CSO is already installed, choose No. Otherwise, click Yes to proceed. You will need to load the Features from the Transcript. See the Customization of VisualAge Generator Developer section for addition information to complete the install.
Delete Temporary Directory

If you downloaded the files from the FTP site, you may delete the temporary directory used to host the FixPak3 files now.
For OS/2 Warp

Execute Install.exe

Using FTP Files
If you downloaded the files from the FTP site, enter the command
<temp>\xxx\HPTDEV2\INSTALL.EXE, where <temp> is the temporary directory you created to host FixPak3, and "xxx" is the 3-character NLS ID.

Note: For example, if you are using Japanese and the temporary directory you selected is called FIXDEV, you would enter the following command in the command line:
FIXDEV\JPN\HPTDEV2\INSTFIX\INSTALL.EXE

Using CD
If you are installing from the CD, enter the command
<CD-ROM drive letter>\xxx\HPTDEV2\INSTALL.EXE where "xxx" is the 3-character NLS ID.

Install FixPak3 for CSO

You will also need to install FixPak3 for CSO. Installation instructions for FixPak3 for CSO are contained below in the VisualAge Generator Common Services Installation Instructions section. After installation of FixPak3 for CSO, see the Customization of VisualAge Generator Developer section for addition information in order to complete the install.
Delete Temporary Directory

If you downloaded the files from the FTP site, you may delete the temporary directory used to host the FixPak3 files now.
Customization of VisualAge Generator Developer
When you install FixPak3 for VisualAge Generator Developer V3.1, it becomes an available, loadable feature of VisualAge for Smalltalk. To complete the installation of VisualAge Generator V3.1 FixPak3, perform the following customization tasks:

Start VisualAge for Smalltalk.

Select Tools --> Load/Unload Features... on the System Transcript window.

On the Selection Required window, do the following:

Ensure that the Show other features check box is checked.

Select Other: VAGen Developer - FixPak3 from the Available features list. If you want to update other features included in the fixpak, please select them as well.

Click on the >> button to move Other: VAGen Developer - FixPak3 to the Loaded features list. If you selected other features, they will be moved as well.

Click on the OK button. The selected features will be imported and loaded into your image.

Once the selected features are loaded, you will be prompted to save your image. Press the Yes button. After the image is saved, you might want to make a copy of the image file just in case you need it later.

Note: 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...).

VisualAge Generator Common Services Installation Instructions

Should you have installed FixPak3 for VisualAge Generator Developer or VisualAge Generator Server using the files available from FTP, you will not need to download the seperate files for FixPak3 for CSO. These files were included in the self-extracting executables for the FixPak for these two products and will be in the temporary directory from which you installed FixPak3 for VisualAge Generator Developer or VisualAge Generator Server.
If installing FixPak3 on VisualAge Generator Developer or VisualAge Generator on Windows NT, you will be prompted to install FixPak3 for CSO at the end of the installation, should you not already have it installed. OS/2 Customers will need to follow the "Using FTP Files" instructions provided below to manually run the setup.
For Windows NT

Execute Setup.exe

Using FTP Files

<temp>\xxx\HPTCSOI\INSTFIX\SETUP.EXE

<temp>

xxx

Note:

For example, if you are using Japanese and the temporary directory you selected is called FIXDEV, you would enter the following command in the command line:

FIXDEV\JPN\HPTCSOI\INSTFIX\SETUP.EXE

Using CD

<CD-ROM drive letter>\xxx\HPTCSOI\INSTFIX\SETUP.EXE,

xxx

Delete Temporary Directory

For OS/2 Warp

Execute Install.exe

Using FTP Files

<temp>\xxx\HPTCSO2\INSTALL.EXE

<temp>

xxx

<temp>\xxx\HPTCSO2C\INSTALL.EXE

Note:

For example, if you are using Japanese and the temporary directory you selected is called FIXDEV, you would enter the following command in the command line:

FIXDEV\JPN\HPTCSO2\INSTFIX\INSTALL.EXE

Using CD

<CD-ROM drive letter>\xxx\HPTCSO2\INSTALL.EXE

xxx

<CD-ROM drive letter>\xxx\HPTCSO2C\INSTALL.EXE

Delete Temporary Directory

VisualAge Generator Server Installation Instructions

For Windows NT

Execute Setup.exe

Using FTP Files

<temp>\xxx\HPTWGSI\INSTFIX\SETUP.EXE

<temp>

xxx

Note:

For example, if you are using Japanese and the temporary directory you selected is called FIXDEV, you would enter the following command in the command line:

FIXDEV\JPN\HPTWGSI\INSTFIX\SETUP.EXE

Using CD

<CD-ROM drive letter>\<xxx\HPTWGSI\INSTFIX\SETUP.EXE

xxx

Install FixPak3 for CSO

Delete Temporary Directory

For OS/2 Warp

Execute Install.exe

Using FTP Files

<temp>\xxx\HPTWGS2\INSTALL.EXE

<temp>

xxx

Note:

For example, if you are using Japanese and the temporary directory you selected is called FIXDEV, you would enter the following command in the command line:

FIXDEV\JPN\HPTWGS2\SETUP.EXE

Using CD

<CD-ROM drive letter>\xxx\HPTWGS2\INSTALL.EXE

xxx

Install FixPak3 for CSO

VisualAge Generator Common Services Installation Instructions

Delete Temporary Directory

For AIX

Create a temporary fixpak directory called FIXAIX. (i.e. /u/user1/fixaix).
Go to the ps.software.ibm.com FTP site.
Download the image VGWGS31.IMG or VGWGS31T.IMG from the /ps/products/visualagegen/fixes/v3.1/base directory. The image environment is shown below:

VGWGS31.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)

VGWGS31T.IMG - AIX 4.14 or later

DB2 for AIX 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 for AIX with PTF set 3
Will support both native and CICS applications

VGWGS31X.IMG

non-CICS systems
IBM C Set ++ Compiler v3.1.4

VGWGS31Y.IGM

CICS systems
IBM C Set ++ Compiler v3.1.4

Login as root.
Change your current working directory to the directory created in step 1.
If VisualAge Generator Server for AIX was previously installed on the machine, you must uninstall it before you can install a new version. To uninstall VisualAge Generator Server for AIX, type the following:

installp -u vgwgs31.obj (for AIX 4.1 or later)

Non-English users must also uninstall the .obj file related to your 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 vgwgs31Ds_DE.obj (Swiss German)
installp -u vgwgs31De_DE.obj (German)
Installp -u vgwgs31Es_ES.obj (Spanish)
Installp -u vgwgs31Ja_JP.obj (Japanese)
Installp -u vgwgs31ko_KR.obj (Korean)
Installp -u vgwgs31pt_PB.obj (Brazukuab-Portuguese)
Installp -u vgwgs31zh_TW.obj (Simplified Chinese)

Remove the NLS image that is already installed
Install the base fixpak image
Re-install the NLS image

Enter one of the following commands:

Installp -ad vgwgs31.img all

Installp -ad vgwgs31t.img all

For HP-UX

Create a temporary fixpak directory called FIXHP in the /home/user1/fixhp directory.
Go to the ps.software.ibm.com FTP site.
Download the tar file VGWGS31.TAR or VGWGS31X.TAR from the /ps/products/visualagegen/fixes/v3.1/base directory. The image environment is shown below:

VGWGS31.TAR - HP-UX version 10.10

VGWGS31X.TAR - HP-UX version 10.20

Login as root.
Change your current working directory to /opt.
Enter one of the following commands:

tar -xvf /home/user1/fixhp/vgwgs31.tar

tar -xvf /home/user1/fixhp/vgwgs31x.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, enter the following:

rm -rf /opt/vgwgs31

After Installation Tasks and Information

The following are tasks or information you should be aware of after installing the FixPak.

VisualAge Generator

After installing a VisualAge Generator FixPak and loading the FixPak feature, both the FixPak feature and the base product feature will appear in the Available features list instead for the Loaded features list in the Load/Unload Feature window. This is misleading as the features are actually loaded in the Smalltalk image.

VisualAge Smalltalk Enterprise FixPak4.5a

VisualAge Generator v3.1 FixPak3 requires VisualAge for Smalltalk Enterprise FixPak4.5a. This FixPak is installed automatically when you install FixPak3 on the VisualAge Generator Developer client. The FixPak4.5a feature will also automatically be loaded when you load the VisualAge Generator Developer FixPak3 feature. No additional action is required on the VisualAge Generator Developer client machine.

The following are the after installation tasks and information for VisualAge for Smalltalk Enterprise FixPak4.5a:

45a_*.dat

If you have installed the VisualAge for Smalltalk Enterprise Manager Library, you need to also install three files into the root directory where the Manager Library was installed. You can get the Manager Library portion of FixPak45a from the same location where you got VisualAge Generator V3.1 FixPak3 by doing the following:

From the CD, go to the vast45a directory on the CD root directory and copy the ENVY Manager Library file for the environment you want.
From the FTP site, go to the vast45a directory from the same location you got this readme and download the appropriate ENVY Manager Library file in binary format.

Follow the instructions below based on the operating system on which the ENVY Manager Library is installed. You must stop Emserv before updating the files. Note that the FixPak files for AIX, HP_UX, and Solaris are packaged as compressed tar files.

On OS2: Copy mgr45ao.exe into the directory where the ENVY Manager Library is installed and run the mgr45ao.exe with the -o option. For example::

mgr45ao -o

On Windows NT: Copy mgr45aw.exe into the directory where the ENVY Manager Library is installed and run the mgr45aw.exe with the -o option. For example:

mgr45aw -o

On AIX: Copy m_v45a_a.tar into the installation directory, /opt/IBMvast and uncompress and untar the file as follows:

zcat m_v45a_a.tar | tar -xvf -

On HP-UX: Copy m_v45a_h.tar into the installation directory, /opt/IBMvast and uncompress and untar the file as follows:

zcat m_v45a_h.tar | tar -xvf -

On SUN: Copy m_v45a_s.tar into the installation directory, /opt/IBMvast and uncompress and untar the file as follows:

zcat m_v45a_s.tar | tar -xvf -

The FixPak files will overlay files in the file directory tree structure where your current VisualAge installation resides.

For additional information, see the VisualAge Smalltalk web page .

VisualAge Generator Templates

Product Enhancements, Problem Support, and Limitations

VisualAge Generator V3.1 FixPak3 contain VisualAge Generator Templates (VAGT) enhancements, problem support, or limitations for the following:

Relational import
Information Model and User Interface
Generated Servers
Generated Smalltalk GUI Client
Generate Layout
Generated TUI
Generation

Relational Import

DB2/VSE Import
DB2/Sun-Solaris Import
DB2/400:

Escape characters ('_', '%') in DB2 names are properly managed.

Information Model and User Interface

Business Object Definition:

Data Element Definition:

DBCS:

It is now allowable to map a concurrency management column (same behavior in the generated app as for the read-only field).

Generated Servers

The atomic srervers are not called by the umbrella when the corresponding option cannot be performed (3-tier generation).
The numeric value of the empty rows that are returned by a list are set to 0.
Update process exits when an error is detected in the server control hook.
DBCS High and Low Value are generated properly.
Concurrency management on the Insert atomic server:

The record that contains the key of the target table of a join condition is generated, even for n-column keys.
The message table is now generated as 'RAD'
ROWID type is taken into account and generated as CHAR(18)
New hooks after the SQL Process to process/cancel a SQL error

Generated Smalltalk GUI Client

Business Object, Resource Object and List Manager are generated with a different icon
The error handling field description includes a new attribute: isReadOnly That allows to dynamically turn a field updatable or read-only.
key: method is renamed isKey: (key: method becomes obsolete).
Timestamps are displayed and stored correctly.
Updatable list:

Instance Register:

Zoom method: Becomes customizable ('HOOK').
Help List: The client classes take into account the additionalHelpField parameter. The corresponding collections, getter and setter are generated.
MdlIsUpdated flag is properly managed when filling a list.
The 'Control Location' is taken into account appropriately (it makes it possible not to generate checks on the client).

Generated Layout

The New action is always laid-out.
System error view: The "application name" label is renamed "program name".
The releaseWidget method becomes generic to include all user-added menu items.
DBCS characters in menu labels are ignored when computing mnemonics.

Generated TUI

'Top' invokes correctly SETINQ1 (instead of SETINQ).

Generation

The assignments of sub-parts to instance variables are preserved when the part is re-generated.

VisualAge Generator Templates Standard Functions Installation

To install VAGT Standard Functions, select the corresponding option in the VisualAge Generator 3.1 install.

Installation:

Open the Control Panel
Open the System icon
In the opened System Properties notebook, select the Environment page.
In the User Variables list, select MDLROOT.
Activate the appropriate push-button to delete it.

Load and Start VAGT Standard Functions FixPak Feature:

Visual Age Organizer

Options

Load/Unload Features

VAGTemplates Standard Functions + FixPak3.

Upgrading VAGT 2.2 Refresh to VAGT Standard Functions 3.x:

Ensure that the VAGT 2.2 configuration file, MDL.CNF, is located in the VASTROOT directory: if it is located elsewhere, copy it into the VASTROOT directory
Launch the Migration tool: VA Organizer -> Tools -> VAGT Tools -> Migrate Workspace

Caution:

If you migrate several workspaces that contain instances with the same identifier but identifiying different objects, and if you want to preserve each description, you must after migration of the first workspace in an application, make a version of this application and unload it. Then, you can migrate the second workspace specifying a new application.

Parameterizing DB2 database Import:

Use the SYSSCHEMA keyword (DB2CLI.INI in your DB2 directory) as follows:

SYSSCHEMA = sysschema
This keyword indicates an alternative schema to be searched in place of the SYSIBM (or SYSTEM, QSYS2) schemas when the DB2 CLI and ODBC Catalog Function calls are issued to obtain system catalog information.

Using this schema name, the system administrator can define a set of views consisting of a subset of the rows for each of the following system catalog tables:

DB2 for Common Server DB2 for MVS/ESA DB2 for VSE and VM OS/400 DB2 for OS/400

SYSTABLES SYSTABLES SYSCATALOG SYSTABLES SYSTABLES

SYSCOLUMNS SYSCOLUMNS SYSCOLUMNS SYSCOLUMNS SYSCOLUMNS

SYSINDEXES SYSINDEXES SYSINDEXES SYSINDEXES SYSINDEXES

SYSTABAUTH SYSTABAUTH SYSTABAUTH SYSCST

SYSRELS SYSRELS SYSKEYCOLS SYSKEYCST

SYSDATATYPES SYSSYNONYMS SYSSYNONYMS SYSCSTCOL

SYSKEYS SYSKEYS SYSKEYS

SYSCOLAUTH SYSCOLAUTH SYSREFCST

SYSFOREIGNKEYS

SYSPROCEDURES (1)

SYSDATABASE

Note: The (1) means that this applies to DB2 for MVS/ESA 4.1 only.

For example, if the set of views for the system catalog tables are in the ACME schema, then the view for SYSIBM.SYSTABLES is ACME.SYSTABLES; and SYSSCHEMA should then be set to ACME.

Defining and using limited views of the system catalog tables reduces the number of tables listed by the application, which reduces the time it takes for the application to query table information.

If no value is specified, the default is as follows:

SYSCAT or SYSIBM on version 2.1 of DB2 for common server
SYSIBM on versions prior to 2.1 of DB2 for common server, DB2 for MVS/ESA and OS/400
SYSTEM on DB2 for VSE and VM
QSYS2 on DB2 for OS/400

Use of the VAGTSys variable (DB2 for MVS/ESA only)

The VAGT Relational Import function is able to use such parameterized names: you just have to initialize VAGTSys variable in the DB2CLI.INI file, according to your parameterization (that is, VAGTSys = DSN).

If no value is specified, the default is, SYS.

VisualAge Generator Templates Functions Documentation

Instructions for new functions in VisualAge Generator Developer V3.1 FixPak2 were not included with the FixPak2 Release. These instructions are located in the HPTBOOKS directory on the CD for VisualAge Generator Developer V3.1 FixPak3 CD as VGTFIX3.HTM

Notes Limitations and Know Problems

Installation:

Bidi:

menus inside a menu bar
columns insude a container
tabs inside a notebook

Generators:

Database Management:

Note: Be aware that this will also roll back all units of work.

Troubleshooting Installation

Problem with Loading GA feature

In FixPak2 and FixPak3 of VisualAge Generator V3.1, VisualAge Smalltalk 4.5 FixPak A is automatically installed. As a result, you may experience difficulties loading the GA level of the Generator Feature onto a blank ST image afterwards. If this is the case, a Smalltalk image (abt.icx) with the GA level of the VisualAge Generator Developer feature preloaded has been provided from the FTP site and on the CD.
To resolve such difficulties, follow these instructions:

Copy the appropriate file to the same directory as th abt.icx file:

NTIMG.EXE - Self extracting executable containing the Smalltalk image for Windows NT

OS2IMG.EXE - Self extracting executable containing the Smalltalk Image for OS/2 Warp

FTP Users: Download the appropriate file from the Readme directory:

ftp://ps.software.ibm.com/ps/products/visualagegen/fixes/v3.1

CD Users: The files are located in the root directory of the FixPak3 CD

Extract the preloaded image contained in NTIMG.EXE (or OS2IMG.EXE) by invoking it. This will overwrite the preexisting abt.icx file.
For DBCS Customers Only:

These images are built on SBCS (Single Byte Character Set) machines, saved and put into a self-extracting file format. When any image is saved, it is always saved with the default font information from the local machine. Once this information is saved, it is not updated, but merely referenced. This will result in invalid displays of DBCS characters.

To resolve this, it is necessary to update the image with the default font information from the DBCS machine, and save it again.

To update the default font information, you must do the following:

Bring up the product with the image provided in the previous step.
Execute the following code in the System Transcript window:

AbtCWAdditionsApp
removeAllSymbolicallyNamedFonts;
resetNamedFonts.

Close the product and save the image.
Restart the product.

VisualAge Generator Documents

In VisualAge Generator V3.1 FixPak3, three additional documents have been added to the VisualAge Generator's list of online documents. They are followings:

hpthse31.pdf - VisualAge Generator Server Guide for MVS, VSE, and VM (SH23-0256)
hptese31.pdf - VisualAge Generator External Source Format Reference (SH23-6609)
hptcme31.pdf - Migrating Cross System Product Applications to VisualAge Generator (SH23-0244)

If you installed the online documemtation component, you can access these documents in the directory c:\vast\hptbooks. Where c:\vast is the directory where VisualAge Generator Developer was installed.

Content of Previous FixPak

FixPak1

Introduction

This is the "read me" file for IBM VisualAge Generator Version 3.1 Fixpak1. It contains installation instructions and late breaking news for IBM VisualAge Generator Version 3.1 Fixpak1.

VisualAge Generator Developer

Fixpak1 Installation Instructions

OS2 Install

On your OS2 machine, insert the CD.

Change directory to OS2\xxx\HPTDEV2 (where xxx is the 3 character nls id)

INSTALL

Change directory to OS2\xxx\HPTCSO2 (where xxx is the 3 character nls id)

INSTALL

To complete the Developer Fixpak1 installation, go to the customization section.

Windows Install

On yourWindows NT machine, insert the CD.

Change directory to WINDOWS\xxx\HPTDEVI\INSTFIX (where xxx is the 3 char nls id)

SETUP

To complete the Developer Fixpak1 installation, go to the customization section.

Customization

To complete installation of VisualAge Generator Developer 3.1 Fixpak1 you will need to do the following:

Installing VisualAge Generator Developer 3.1 Fixpak1 makes VisualAge Generator Developer 3.1 Fixpak1 an available loadable "feature" of VisualAge for Smalltalk. To apply VisualAge Generator Developer 3.1 Fixpak1, do the following:

Start VisualAge for Smalltalk.
Select Tools --> Load/Unload Features.." on the System Transcript.
On the Selection Required window:

Make sure the Show other features check box is checked.
Select Other: VAGen Developer - Fixpak1 from the Available features list. If you want to use the templates support select VAGTemplates Standard Functions.
Click on the >> button to move Other: VAGen Developer - Fixpak1 to the Loaded features list. If you selected any other features they will move as well.
Click on the OK button. The selected features will be imported and loaded into your image.
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.
Note: If you get a walkback (VisualAge Debugger) window while saving the image it probably means that you've run out of disk space. Close the VisualAge Debugger window. You'll need to either free some space and retry the save (File --> Save Image... on the System Transcript) or save the image on another drive (File --> Save Image As...).

Notes, Limitations, and Known Problems

VisualAge Generator Documentation

The redbook VisualAge Generator v3.0 Development Guide (http://www.redbooks.ibm.com/SG244230/sg244230.htm) is available on the web.

VisualAge Organizer / VAGen Parts Browser

New Function in Fixpak1:

Parts

View menu

The VAGen Parts Browser now displays the number of selected parts and the total number of parts in the list in the right-hand corner of the status bar.

The References utility has been enhanced to search parts for an arbitrary text string. This can be used, for example, to search for EZE words or to search comments and prologs.

The font settings throughout the product are now written to hpt.ini so they can be saved between images. The Parts Browser default settings and the Organizer VAGen Parts pane view settings are also written to hpt.ini.

Several VAGen Smalltalk APIs have been added to allow parts to be copied, moved, deleted, or printed. Also, APIs have been added to retrieve a part subtype. See the updated online version of the Programmer's Reference for complete API documentation.

Map Editor

Fixpak1 has corrected the problem with underscores not displaying while typing in an underscored field in the Map editor. Also a problem with the mouse pointer not resetting after certain operations in the Map editor has been corrected.

Other

hptdb231.bnd

Available features

Loaded feature

VisualAge Generator Server

Fixpak1 Installation Instructions

OS2 Install

On your OS2 machine, insert the CD.

Change directory to OS2\xxx\HPTWGS2 (where xxx is the 3 character nls id)

INSTALL

Change directory to OS2\xxx\HPTCSO2 (where xxx is the 3 character nls id)

INSTALL

Windows Install

On yourWindows NT machine, insert the CD.

Change directory to WINDOWS\xxx\HPTWGSI\INSTFIX (where xxx is the 3 char nls id)

SETUP

AIX Install

On your AIX machine, create a temporary fixpak directory called FIXAIX. (i.e. /u/user1/fixaix)

Download image VGWGS31.IMG or VGWGS31T.IMG from the AIX directory. The image environment is shown below:

VGWGS31.IMG

VGWGS31T.IMG - AIX 4.14 or later
                              - DB2 for AIX 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 for AIX with PTF set 3
                              - Will support both native and CICS applications

change your current working directory to the directory created in step 1

Select one of the following:

installp -ad vgwgs31.img all

installp -ad vgwgs31t.img all

If VisualAge Generator Server for AIX was previously installed on the machine it must be rejected before you can install a new version. To reject it, type:

installp -u vgwgs31.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 reject the base obj. The list below shows the command for each language.

   installp -u vgwgs31Ds_DE.obj (Swiss German)
   installp -u vgwgs31De_DE.obj (German)
   installp -u vgwgs31Es_ES.obj   (Spanish)
   installp -u vgwgs31Ja_JP.obj    (Japanese)
   installp -u vgwgs31ko_KR.obj (Korean)
   installp -u vgwgs31pt_PB.obj   (Brazukuab-Portuguese)
   installp -u vgwgs31zh_TW.obj (Simplified Chinese)

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

HP-UX Install

On your HP-UX machine, create a temporary fixpak directory called FIXHP. (i.e. /home/user1/fixhp)

VGWGS31.TAR

VGWGS31X.TAR

VGWGS31.TAR - HP-UX version 10.10

VGWGS31X.TAR - HP-UX version 10.20

Change your current working directory to /opt.

Select one of the following:
type: tar -xvf /home/user1/fixhp/vgwgs31.tar

type: tar -xvf /home/user1/fixhp/vgwgs31x.tar

If VisualAge Generator Server for HP_UX was previously installed on the machine it must be rejected before you can install a new version. To reject it, type:

rm -rf /opt/vgwgs31 (for HP-UX 10.10 or HP-UX 10.20)

Notes, Limitations, and Known Problems

HP-UX

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 11 through 24.

VisualAge Generator Common Services

Installation Instructions

OS2 Install

FixPak Installation Instructions for VisualAge Generator Common Services fixes on OS2.

On your OS2 machine, insert the CD.

Change directory to OS2\xxx\HPTCSO2 (where xxx is the 3 character nls id)

Type: INSTALL

Windows Install

On yourWindows NT, Windows 95 or Windows 3.1 machine, insert the CD.

Change directory to WINDOWS\xxx\HPTCSOI\INSTFIX (where xxx is the 3 char nls id)

Type: SETUP

Notes, Limitations, and Known Problems

IPC and DIRECT protocol support for AIX, which were not available at time of general available, are being added with fixpack1.

APAR List for FixPak1

PN83210 MAP EDIT TABLE ROUTINES ARE BEING IGNORED
PQ10388 SQLCODE=0 IN ITF TRACE, WHILE EZESQCOD=100 IN ITF SHOW DATA
PQ14219 UNDEFINED OBJECT DOES NOT UNDERSTAND EZEFEC
PQ14497 INCORRECT VALUE IN FORMATTED TEXT PART
PQ15970 HEX COMPARE PROBLEM
PQ16461 RECORD DEFINITION PERFORMANCE IS POOR
PQ16416 MSGIGYPS2028-E ISSUED WHEN COMPILING VA GEN PROGRAM.
PQ16414 AN ABENDASRA (0C7) WAS RECEIVED WHEN EXECUTING A VAGEN
PROGRAM IN MVS/CICS.
PQ16857 FIXES FOR VARIOUS SQL PROBLEMS USING VISUALAGEN GENERATOR 3.0
DEVELOPER FEATURE.

FixPak2

Introduction

This VisualAge Generator V3.1 Fixpak2 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.

FixPak2

Before Installing Fixpak2

Before beginning Fixpak2 installation, read the following:

Please shut down the VisualAge Generator Developer and save your image.

VisualAge Generator v3.1 fixpak2 requires VisualAge for Smalltalk Enterprise Fixpak45a. This fixpak is installed automatically when you install Fixpak2 on the VisualAge Generator Developer client. The Fixpak45a feature will also automaticaly be loaded when you load the VisualAge Generator Developer Fixpak2 feature. No additional action is required on the VisualAge Generator Developer client machine.

If you generate printer maps for MVS or VM systems for languages other than U.S. English, do NOT install Fixpak2 without also installing the host LE COBOL APAR PQ16766.

As a precaution, back up your VisualAge for Smalltalk Enterprise installation. Make a note of any features that you have currently installed because you will need to re-load them once the fixpack files are installed.

Product Enhancements, Problem Support, and Limitations

VisualAge Generator V3.1 Fixpak2 contain enhancements, problem support, and limitations for the following:

Map Editor

EMSRV on the AIX Environment

Oracle Support

Euro Monetary Unit Support

ITF Access to OS/390 VSAM files

List of APARs

Map Editor

VisualAge Generator V3.1 Fixpak2 has support which enables you to create a record definition from a map definition. To access this function, do the following:

Select Define, then Record from the Map Editor's menu pulldown. You will be prompted with the Save As dialog.

Enter the name you want to name the record and the ENVY application in which you want to add the record to.

This function is useful because it enables the translation of a 3270 map definition into a graphical user interface view. This is done by dropping the newly created record on the free-form surface of the GUI definition and using the QuickForm function to layout a default view.

In addition, changes have been made to correct problems that occur while typing in Preview mode, making selections, using the Sticky option, and resetting the mouse pointer shape after various operations.

EMSRV on the AIX Envioronment

When you install Fixpak2 from the CD or the web, you need to also copy the following files from the x:\vast\import directory of the machine on which you installed Fixpak2:

VGDEVFP.dat
VGGSFP.dat
VGPSFP.dat These files must be copied to the AIX machine on which you are running EMSRV. Copy the files from the ImportDirectory listed in the abt.ini file. Because AIX is case sensitive, you need to specify the names exactly as they are listed above.

If you are loading the feature image and the load feature fails with a message indicating that it cannot find one of the .dat files, ensure that the name specified in the corresponding .ctl file matches the name and case of the files you copied to the AIX machine. For example, VGDEVFP.dat has a corresponding VGDEVFP.ctl file. The .ctl file exists in the x:\vast\feature directory of the machine on which you installed Fixpak2. In the .ctl file, you will find many references to the VGDEVFP.dat file.

Oracle Support

The pre-requisite for the Oracle support shipped in VisualAge Generator V3.1 is Oracle V7.3.4 or later (both native and ODBC).

Euro Monetary Unit Support

With FixPak 2, VisualAge Generator V3.1 supports the Euro currency symbol.

VisualAge Smalltalk 4.x also supports the Euro currency symbol. See the VisualAge Smalltalk webpage for information on how to specify the Euro currency to Smalltalk http://www.software.ibm.com/ad/smalltalk/about/euro.html

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 NT or OS/2 system.

For the Host COBOL user (those using PCOMM), install the latest fixpak for PCOMM (for OS/2 and Windows) 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, select Preferences > Test General from the Options menu. Then, specify the currency symbol you want your programs to use.

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.

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

Accessing OS/390 VSAM Files from ITF and C++ Generated Programs

Do you have VSAM files residing on OS/390 that you want to access from a VisualAge Generator program on your workstation? Now you can use the same VSAM file when testing your program that you will use in your production environment. This feature is available for ITF with VisualAge Generator Version 3.1 Fixpak2.

Software Prerequisites

The following table shows the list of pre-requisite software that you need to have installed to use the ITF VSAM file support:

System	Local VSAM	Remote VSAM
OS/2	Shipped with IBM VisualAge Generator	IBM Personal Communications AS/400 and 3270 Version 4.11 (or later)
Windows NT	Not Available	IBM Personal Communications AS/400 and 3270 Version 4.11 (or later)
OS/390		IBM DFSMS/MVS Version 1.2 (or later)

Setup Required to Access Remote VSAM Files on OS/390

After installing the required products, configuring APPC, and verifying that you can establish an APPC session with your OS/390 host, you are ready to configure DFM on the workstation.

Setup on OS/2

Download the file vsamos2.zip from ftp://ps.software.ibm.com/ps/products/visualagegen/info/v31 into a temporary directory, unzip it, and follow the instructions in the install.readme file.

NOTE: If you have IBM VisualAge for COBOL for OS/2 installed, specifically the SmartData Utilities component, you do not need to install the vsamos2.zip file.

Perform the following steps:

Modify the command files used to start DFM (startdfm.cmd) and indicate the drive letter that should be used for DFM.

Modify the sample configuration file (config.dfm) based on your configuration. Items such as USERID, LOCAL_LU, REMOTE_LU, and the OS/390 target system name must be changed.

If data conversion is required, add the FILE_DESCRIPTOR_MAP keywords to the configuration file. See the section below entitled DFM Data Conversion Setup on OS/2.

Start DFM using the startdfm command.

Refer to VSAM in a Distributed Environment (SC26-7063) for additional information
on configuring DFM for OS/2.

Setup on Windows NT

Download file vsamnt.zip from ftp://ps.software.ibm.com/ps/products/visualagegen/info/v31 into a temporary directory, unzip it, and follow the instructions in the install.readme file.

NOTE: If you have IBM VisualAge for COBOL for Windows NT installed, specifically the SmartData Utilities component, you do not need to install the vsamnt.zip file.

Perform the following steps:

Modify the sample configuration file (dfm.rc) based on your configuration.

If data conversion is required, add the FILE_DESCRIPTOR_MAP keywords to the configuration file. See the section below entitled DFM Data Conversion Setup on Windows NT.

Run the dfmcfg command to create the formatted configuration file.

Optionally run the dfmnet command to setup 'shortcut' names.

Run the dfmlogon command to setup userid/password information.

Refer to SdU for Windows Distributed FileManager Users Guide (SC26-7134) for additional information on remote file names, shortcut names, and configuring DFM for Windows NT.

Accessing VSAM Files from ITF

To specify that you want to use VSAM files, do the following:

Select the Options menu on the VisualAge Organizer window.

Select Preferences and the VisualAge Preferences notebook displays.

Select the VAGen - Test General tab.

At the bottom of the page, select either the Local VSAM or Remote VSAM radio button and click OK.

This will cause ITF to use VSAM files for all file accesses (on Windows NT, there is only remote VSAM file support). In a later fixpak, this option will be moved to the Resource Association Editor so that the type of file accessed can be specified on a file basis. If you have changed your preferences to use Remote VSAM and you do not have the communications software setup and working, you will receive an error.

In addition to changing your preferences, you also need to specify the physical name and path in the ITF Resource Association File editor as follows:

In the Physical name field, specify the file name as it is on your OS/390 system but without the high level qualifier. If the file does not already exist on your OS/390 system, VisualAge Generator will create it for you.

On OS/2, in the Path field, specify the DFM drive letter, a colon, and the high level qualifier specified in the DFM configuration file (config.dfm).

On Windows NT, in the Path field, specify the machine name or a shortcut name using the Universal Naming Convention.

Accessing VSAM Files from C++ Generated Programs

Diagnosing Error Conditions When Using VSAM with ITF

Diagnosing Error Conditions When Using VSAM with C++ Generated Programs

Data Conversion

VisualAge Generator is not providing automatic data conversion for host VSAM files in this FixPak. It will be provided in the next V3.1 FixPak. In the meantime, you can use the facilities provided by DFM to convert data from ASCII to EBCDIC and vice-versa. VSAM files on the host systems are typically stored as EBCDIC characters although you can store ASCII data in them as well. VSAM files on the workstation are stored as ASCII characters. If you use the host system just for data storage, you do not need to convert the data to EBCDIC. If however, you want to access the data from programs on your workstation and from programs on the host system, you need to convert the data. DFM uses the IBM A Data Language (ADL) to define how the data is converted.

DFM Data Conversion Setup on OS/2

Perform the following steps if you want DFM to do the data conversion:

Create an ADL description of the record as it is stored on the host system. This is called the Base sequence. Use a text editor to create the ADL description.

Translate the Base sequence into a DFM internal format called Data Description File (DDF). Use the ADLTRANS command to do the translation.

Create an ADL description of the record as it is stored on the workstation. This is called the View sequence.

Translate the View sequence into DFM internal format (DDF) using the ADLTRANS command.

Update the config.dfm file to specify the FILE_DESCRIPTOR_MAP keywords. Data conversion is controlled by the FILE_DESCRIPTOR_MAP keywords.

Restart DFM on the workstation.

Refer to VSAM in a Distributed Environment (SC26-7063) for additional
information on configuring DFM for data conversion.

DFM Data Conversion Setup on Windows NT

Perform the following steps if you want DFM to do the data conversion:

Create an ADL description of the record as it is stored on the host system. This is called the Base sequence. Use a text editor to create the ADL description.

Create an ADL description of the record as it is stored on the workstation. This is called the View sequence.

Update the config.dfm file to specify the FILE_DESCRIPTOR_MAP keywords. Data conversion is controlled by the FILE_DESCRIPTOR_MAP keywords.

Run the dfmcfg command to create the formatted configuration file.

Optionally run the dfmnet command to setup 'shortcut' names.

Run the dfmlogon command to setup userid/password information.

Refer to SdU for Windows Distributed FileManager Users Guide (SC26-7134) for
additional information on configuring DFM for data conversion.

Known Problems/Limitations

You cannot create sequential VSAM files on a remote OS/390 system. An APAR has been opened against DFM/MVS.

When issuing a SET record SCAN with a key value of x'FFFF' or a key value greater than the highest record in the file, the behavior of a subsequent SCANBACK differs between local and remote VSAM. If accessing local VSAM, an I/O error will be returned instead of the last record. If accessing remote VSAM, the last record in the file will be returned.

List of APARs

The following is a list of APARs in Fixpak2:

PQ05021: BTRIEVE RELATIVE FILE VALIDATION CHECK
PQ14214: ENTERING AN INCORRECT PASSWORD, WHEN USING CSOPRMPT.DLL FOR VAGENPROMPT ON CICS, THEN AN ABENUAEY7 IS ISSUED.
PQ14380: UNABLE TO VALIDATE MULTIPLE PROGRAM PARTS AT THE SAME TIME.
PQ14906: MOVING CHAR4 TO NUM3 PRODUCES INCORRECT OUTPUT.
PQ15676: VARIABLE NAMES IN GENERATED SQL CLAUSE HAVE BEEN TRUNCATED.
PQ15949: DATA DESCRIPTOR IS GENERATED INCORRECTLY.
PQ16418: TEXT DISPLAYED ON A TURQUOISE BACKGROUND.
PQ16539: MAP GENERATED ON OS/2 DOES NOT DISPLAY TURKISH CHARS ON ISO8859.
PQ16811: CICS ERROR READING REMOTE VSAM FILE.
PQ16839: BRIGHT FUNCTION IS NOT WORKING ON AIX TERMINAL.
PQ17094: CANNOT TAKE FCWTRACE ON TEST MODE.
PQ17263: VA GEN SYMBOLIC PARAMETER EZEUSRID IGNORED WHEN SPECIFIED IN JOB CARD TEMPLATE FILE.
PQ18228: CONVERSE CAUSES PROGRAM TO LOCK UP IF TRACING IS VIEWED IN ITF.
PQ18387: ODBC - TRAP ON SCAN OF TABLE ORATYPE IN ITF ON NT FOR ODBC-ORACLE.
PQ18865: SET MAP ITEM TURQ, WHITE or FULL INCORRECT IN ITF
PQ19030: MESSAGE CSO7836E RC=0 ISSUED WHEN CALLING AIX SERVER.
PQ19113: Undefined symbol error.
PQ19232: USE OFF INDICATOR VARIABLES IN WHERE CLAUSE CAN RESULT IN A DBSCAN IN A VM/DB2 5.1 ENVIRONMENT CAUSING BAD PERFORMANCE.
PQ19487: VA GEN C++ PROGRAM RECEIVES COMPILE ERROR EDC3224 FOR CALL.
PQ19777: SINGLE I-MESSAGES (F.E. 626.I) SHOULD BE SHOWN DURING ONLINE VALIDATION, NOT ONLY DURING BATCH VALIDATION.
PQ20011: RETURN SQLCODE ON COMMIT AND ROLLBACK.
PQ20188: EZEUSR RETURNS THE TERMINAL ID WHICH IN THE ITF IS "PC USER".
PQ20217: PROBLEMS USING EZELOC WITH REMOTE BIND = RUN TIME.
PQ20218: INVALID CALL PARAMETER.
PQ20229: RECORD/TABLE EDITOR: COPY/PASTE DOES NOT COPY LOCAL SCOPE.
PQ20395: GEN.CMD NOT EXECUTED USING BATCH GENERATE ON NT.
PQ20420: A BLANK ITEM IS INSERTED AS NULL COLUMN IN A ORACLE TABLE.
PQ20585: DEBUGGER COMES UP ON GENERATION OF SPECIFIC APPLICATION.
PQ20721: "TRUE DOES NOT UNDERSTAND COLLECT" WALKBACK ENCOUNTERED WHEN DEFINING VISUALAGE GENERATOR RECORD WITH OCCURRENCES ITEM.
PQ20911: INSERTING BLANK VALUE IN ORACLE DOES NOT PRODUCE NULL ROW.
PQ21020: SUBSTRUCTURED HEX FIELDS CAUSE LOOPING.
PQ21045: EURO SUPPORT REQUIRED FOR VISUALAGE GENERATOR DEVELOPER.
PQ21046: EURO SUPPORT FOR VISUALAGE GENERATOR SERVER.
PQ21047: WALKBACK: UNDEFINED OBJECT DOES NOT UNDERSTAND SETSTATUS AFTER MODIFYING SQL PROCESS OBJECT AND RESUMING TEST.
PQ21109: "N" STATEMENT RETURNS INCORRECT IF INDEX IS LARGER THAN ARRAY.
PQ21162: RUNTIME COMPARISON OF CXCHASTRING'S RETURNS INCORRECT RESULTS.
PQ21186: WHILE LOOP CONDITION IGNORED IN ITF WHEN CALLED FROM A GUI.
PQ21203: PROVIDE VSAM SUPPORT FOR VISUALAGE GENERATOR INTERACTIVE TEST.
PQ22120: UNDEFINED SYMBOL ERROR.

VisualAge Generator Developer Installation

The following sections provide Fixpak2 installation instructions for the VisualAge Generator Developer.

OS/2 Installation

Insert Fixpak2 installation CD into the CD drive.

Change the directory to OS2\xxx\HPTDEV2 (where xxx is the 3-character NLS id), then type "install" to install ViauslAge Generator Developer fixes.

Change the directory to OS2\xxx\HPTCSO2 (where xxx is the 3-character NLS id), then type "install" to install VisualAge Generator Developer fixes.

See Customization of VisualAge Generator Developer for additional information to complete the installation.

Windows Installation

Insert Fixpak2 installation CD into the CD drive.

Change the directory to WINDOWS\xxx\HPTDEVI\INSTFIX (where xxx is the 3-character NLS id), then type "setup".

See Customization of VisualAge Generator Developer for additional information to complete the installation.

Customization of VisualAge Generator Developer

When you install Fixpak2 for VisualAge Generator Developer V3.1, it become an available, loadable feature of VisualAge for Smalltalk. To complete the installation of VisualAge Generator V3.1 Fixpak2, perform the following customization tasks:

Start VisualAge for Smalltalk.

Select Tools --> Load/Unload Features... on the System Transcript window.

On the Selection Required window, do the following:

Ensure that the Show other features check box is checked.
Select Other: VAGen Developer - Fixpak2 from the Available features list. If you want to update other features included in the fixpak, please select them as well.
Click on the >> button to move Other: VAGen Developer - Fixpak2 to the Loaded features list. If you selected other features, they will be moved as well.
Click on the OK button. The selected features will be imported and loaded into your image.
Once the selected features are loaded, you will be prompted to save your image. Press the Yes button. After the image is saved, you might want to make a copy of the image file just in case you need it later.

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

VisualAge Generator Server Installation

The following sections provide Fixpak2 installation instructions for the VisualAge Generator Server.

OS/2 Installation

Insert Fixpak2 installation CD into the CD drive.

Change the directory to OS2\xxx\HPTWGS2 (where xxx is the 3- character NLS id), then type "install" to install VisualAge Generator Server fixes.

Change the directory to OS2\xxx\HPTCSO2 (where xxx is the 3- character NLS id), then type "install" to install VisualAge Generator Server fixes.

Windows Installation

Insert Fixpak2 installation CD into the CD drive.

Change directory to WINDOWS\xxx\HPTWGSI\INSTFIX (where xxx is the 3-character NLS id), then type "setup".

AIX Installation

Create a temporary fixpak directory called FIXAIX. (i.e. /u/user1/fixaix).

Download the image VGWGS31.IMG or VGWGS31T.IMG from the AIX directory. The image environment is shown below:

VGWGS31.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)

VGWGS31T.IMG - AIX 4.14 or later

DB2 for AIX 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 for AIX with PTF set 3
Will support both native and CICS applications

Change your current working directory to the directory created in step 1.

If VisualAge Generator Server for AIX was previously installed on the machine, you must uninstall it before you can install a new version. To uninstall VisualAge Generator Server for AIX, type the following:

installp -u vgwgs31.obj (for AIX 4.1 or later)

installp -u vgwgs31Ds_DE.obj (Swiss German)
installp -u vgwgs31De_DE.obj (German)
Installp -u vgwgs31Es_ES.obj (Spanish)
Installp -u vgwgs31Ja_JP.obj (Japanese)
Installp -u vgwgs31ko_KR.obj (Korean)
Installp -u vgwgs31pt_PB.obj (Brazukuab-Portuguese)
Installp -u vgwgs31zh_TW.obj (Simplified Chinese)

Whenever you remove VisualAge Generator Server for AIX from your system to install a fixpak and you also have an NLS image already installed, do the following:

Remove the NLS image that is already installed
Install the base fixpak image
Re-install the NLS image

Enter one of the following commands:

Installp -ad vgwgs31.img all

Installp -ad vgwgs31t.img all

HP-UX Installation

Create a temporary fixpak directory called FIXHP (that is, /home/user1/fixhp).

Download the tar file VGWGS31.TAR or VGWGS31X.TAR from the HP directory. The image environment is shown below:

VGWGS31.TAR - HP-UX version 10.10

VGWGS31X.TAR - HP-UX version 10.20

Change your current working directory to /opt.

Enter one of the following commands:

tar -xvf /home/user1/fixhp/vgwgs31.tar

tar -xvf /home/user1/fixhp/vgwgs31x.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, enter the following:

rm -rf /opt/vgwgs31 (for HP-UX 10.10 or HP-UX 10.20)

VisualAge Generator Common Services Installation

The following sections provide Fixpak2 installation instructions for the VisualAge Generator Common Services. If you have already installed VisualAge Generator Common Services along with the Devleoper or Server product, you may skip this section.

OS/2 Installation

Insert Fixpak2 installation CD into the CD drive.

Change the directory to OS2\xxx\HPTCSO2 (where xxx is the 3-character NLS id), then type "install" to install VisualAge Generator Common Services fixes.

Windows Installation

Insert Fixpak2 installation CD into the Windows NT, Windows 95, or Windows 3.1 CD drive.

Change the directory to WINDOWS\xxx\HPTCSOI\INSTFIX (where xxx is the 3-character NLS id), then type "setup".

After Installation Tasks and Information

The following are tasks or information you should be aware of after installing the fixpak.

VisualAge Generator

After installing a VisualAge Generator fixpak and loading the fixpak feature, both the fixpak feature and the base product feature will appear in the Available features list instead for the Loaded features list in the Load/Unload Feature window. This is misleading as the features are actually loaded in the Smalltalk image.

VisualAge Smalltalk Enterprise Fixpak45a

The following are the after installation tasks and information for VisualAge for Smalltalk Enterprise Fixpak45a:

If you originally did a VisualAge Client installation, then copy the fixpack DAT files (45a_*.dat) from the import subdirectory on your machine to the import directory on the Manager Server.

If you have installed the VisualAge for Smalltalk Enterprise Manager Library, you need to also install three files into the root directory where the Manager Library was installed. You can get the Manager Library portion of fixpak45a from the same location where you got VisualAge Generator V3.1 Fixpak2 by doing the following:

From the CD, go to the vast45a directory on the CD root directory and copy the ENVY Manager Library file for the environment you want.
From the FTP site, go to the vast45a directory from the same location you got this readme and download the appropriate ENVY Manager Library file in binary format.

Follow the instructions below based on the operating system on which the ENVY Manager Library is installed. You must stop Emserv before updating the files. Note that the fixpack files for AIX, HP_UX, and Solaris are packaged as compressed, tar files.

On OS2: Copy mgr45ao.exe into the directory where the ENVY Manager Library is installed and run the mgr45ao.exe with the -o option. For example::

mgr45ao -o

On Windows NT: Copy mgr45aw.exe into the directory where the ENVY Manager Library is installed and run the mgr45aw.exe with the -o option. For example:

mgr45aw -o

On AIX: Copy m_v45a_a.tar into the installation directory, /opt/IBMvast and uncompress and untar the file as follows:

zcat m_v45a_a.tar | tar -xvf -

On HP-UX: Copy m_v45a_h.tar into the installation directory, /opt/IBMvast and uncompress and untar the file as follows:

zcat m_v45a_h.tar | tar -xvf -

On SUN: Copy m_v45a_s.tar into the installation directory, /opt/IBMvast and uncompress and untar the file as follows:

zcat m_v45a_s.tar | tar -xvf -

The fixpack files will overlay files in the file directory tree structure where your current VisualAge installation resides.

For additional information, see the VisualAge Smalltalk web page .

VisualAge Generator Templates

Product Enhancements, Problem Support, and Limitations

VisualAge Generator V3.1 Fixpak2 contain VisualAge Generator Templates (VAGT) enhancements, problem support, or limitations for the following:

New parameters and new functions in the generated applications

Relational database import via IXF files

VAGT UI

Relational database import function

QuickStart

Setting a current user after installation

BiDi support

Generators

Database management

New Parameters and Functions in the Generated Applications

VisualAge Generator Templates has added support for new parameters and new functions in generated applications. For information on these new parameters and new functions, see the V31fix.htm file in the mdlbooks subdirectory.

Relational Database Import via IXF Files

VisualAge Generator Templates has added support for relational database import via IXF files. For information on this new support see the V31fix.htm in the mdlbooks subdirectory.

VisualAge Generator Templates User Interface

VisualAge Generator Templates has added the following VAGT UI support:

New menu items for VAGT Workspace: 'Load' and 'Editions...' (same functions as VAGT entities)

New menu item for VAGT Entities and Workspace: 'Move...' (in another application)

BusinessObject mapping: The column name is now displayed.

Error management: "*** error ***" is displayed in erroneous fields.

Error messages: Each message has an associated code that is displayed in the Transcript window.

Relational Database Import Function

VisualAge Generator Templates has added the following relational database import function support:

The Import window enables you to create a new application.

Import from DBCS Database: Strings are imported and stored in the appropriate format (SBCS or DBCS).

The following SQL types are now imported and taken into account at generation time:

RAW
LONG RAW
LONG VARGRAPHIC
LONG VARG

The REAL SQL type (Oracle) is now imported but is not taken into account at generation time.

QuickStart

VisualAge Generator Templates has added the following QuickStart support:

It takes into account the DBMS corresponding to VAGen preferences

It checks the workspace identifier

Setting a Current User After Installation

After the load of the VisualAge Generator Templates feature, the VisualAge Organizer might have lost the current user. Ensure that you set a current user before using VAGT feature (otherwise, the VAGT Tools menu items will remain disabled).

BiDi Support

Although VAGT is able to provide right-to-left organized views and subviews, VAGT depends on the abilities of VisualAge Smalltalk BiDi feature for internal positionings such as the following:

Menus inside a menu bar

Columns inside a container

Tabs inside a notebook

Generators

The 4GL Client Logic Style (Workspace parameter) is not implemented in Smalltalk-oriented generators.

Database Management

When connecting to the database, you might have database connections left open (error message1445 appears). You should clean up the SQL database connections, then execute the following code to clean up the SQL interface:

SQLRequester disconnectAll Note that doing this will also roll back all units of work.

VisualAge Generator Templates Standard Functions Installation

To install VAGT Standard Functions, select the corresponding option in the VisualAge Generator V3.1 Fixpak2 installation and do the following;

On Windows/NT, if you previously set the MDLROOT variable as a user variable, remove it. It is now initialized automatically as a system variable. To remove the variable, do the following:

Click on Start, then Settings, then select Control Panel.
Double-click on the System icon and the System Properties notebook displays.
Select the Environment tab and in the User Variables list, select the MDLROOT variable.
Click on the Delete push-button to delete the variable.

To load the VisualAge Generator Templates, from the VisualAge Organizer window, click on Options, then Load/Unload Features, then select VAGTemplates Standard Functions + Fixpak 2.

The load function ensures the loading of the prerequisites, the VisualAge ODBC Database and the DB2 CLI Database.

The VisualAge Generator Templates (VAGT) V3.x repository is stored in the VisualAge Generator library. The migration tool enables you to upgrade VAGT V2.2 Refresh (and 3.0 alpha), with specifications stored in files, to VAGT V3.x (with specifications stored in VisualAge Generator library). To migrate to VAGT Standard Functions V3.1, do the following:

Ensure that the VAGT 2.2 configuration file, MDL.CNF, is located in the VASTROOT directory. If it is located elsewhere, copy it into the VASTROOT directory.

VisualAge Organizer

Tools

VAGT Tools

Migrate Workspace

Caution: If you migrate several workspaces that contain instances with the same identifier but the instances are identifiying different objects, and you want to preserve each description, then after the migration of the first workspace in an application, you must make a version of second workspace specifying a new application.

To set the parameters for DB2 database import, involves the following:

Use the SYSSCHEMA keyword (DB2CLI.INI in your DB2 directory) as follows:

SYSSCHEMA = sysschema

This keyword indicates an alternative schema to be searched in place of the SYSIBM (or SYSTEM, QSYS2) schemas when the DB2 CLI and ODBC Catalog Function calls are issued to obtain system catalog information.

Using this schema name, the system administrator can define a set of views consisting of a subset of the rows for each of the following system catalog tables:

DB2 for Common Server	DB2 for MVS/ESA	DB2 for VSE and VM	OS/400	DB2 for OS/400
SYSTABLES	SYSTABLES	SYSCATALOG	SYSTABLES	SYSTABLES
SYSCOLUMNS	SYSCOLUMNS	SYSCOLUMNS	SYSCOLUMNS	SYSCOLUMNS
SYSINDEXES	SYSINDEXES	SYSINDEXES	SYSINDEXES	SYSINDEXES
SYSTABAUTH	SYSTABAUTH	SYSTABAUTH		SYSCST
SYSRELS	SYSRELS	SYSKEYCOLS		SYSKEYCST
SYSDATATYPES	SYSSYNONYMS	SYSSYNONYMS		SYSCSTCOL
	SYSKEYS	SYSKEYS		SYSKEYS
	SYSCOLAUTH	SYSCOLAUTH		SYSREFCST
	SYSFOREIGNKEYS
	SYSPROCEDURES (1)
	SYSDATABASE

Note:

The (1) means that this applys to DB2 for MVS/ESA 4.1 only.

Defining and using limited views of the system catalog tables reduces the number of tables listed by the application, which reduces the time it takes for the application to query table information.

If no value is specified, the default is as follows:

SYSCAT or SYSIBM on version 2.1 of DB2 for common server
SYSIBM on versions prior to 2.1 of DB2 for common server, DB2 for MVS/ESA and OS/400
SYSTEM on DB2 for VSE and VM
QSYS2 on DB2 for OS/400

Use of the VAGTSys variable (DB2 for MVS/ESA only)

If no value is specified, the default is, SYS.

VisualAge Generator Documents

In VisualAge Generator V3.1 Fixpak2, three additional documents have been added to the VisualAge Generator's list of online documents. They are followings:

hpthse31.pdf - VisualAge Generator Server Guide for MVS, VSE, and VM (SH23-0256)

hptese31.pdf - VisualAge Generator External Source Format Reference (SH23-6609)

hptcme31.pdf - Migrating Cross System Product Applications to VisualAge Generator (SH23-0244)

VisualAge Generator Redbook

For additional information on developing VisualAge Generator applications, you can access the redbook VisualAge Generator System Development Guide (SG24-4230) on the web.

Online Documentation

For additional information on developing VisualAge Generator applications, you can access the redbook VisualAge Generator System Development Guide (SG24-4230) on the web.

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

Useful Websites:

IBM VisualAge Generator

http://www.software.ibm.com/ad/visgen/

IBM VisualAge Smalltalk

http://www.software.ibm.com/ad/smalltalk

IBM VisualAge Java

http://www.software.ibm.com/vajava

IBM VisualAge Resource Catalog

http://www.software.ibm.com/ad/visage/rc

IBM Software Applicaiton Development

http://www.software.ibm.com/ad

IBM Software Homepage

http://www.software.ibm.com

IBM Corporation Homepage

http://www.ibm.com

Table of Contents

Software Pre-requisites

Setup Required to Access Remote VSAM Files on OS/390

Setup on OS/2 for FixPak3

Setup on Windows NT for FixPak3

Accessing VSAM Files from ITF

Accessing VSAM Files from C++ Generated Programs

Diagnosing Error Conditions When Using VSAM with ITF

Diagnosing Error Conditions When Using VSAM with C++ Generated Programs

Data Conversion

Known Problems/Limitations

Known Limitations:

Prerequisites

Currency Symbol Support during Test

Currency Symbol Support during Generation

Euro On OS/2 With U.S. English

Typing the Euro Currency Symbol

Euro Fonts Installation

How to Get the Euro Support

Software Prerequisites

Setup Required to Access Remote VSAM Files on OS/390

Setup on OS/2

Setup on Windows NT

Accessing VSAM Files from ITF

Accessing VSAM Files from C++ Generated Programs

Diagnosing Error Conditions When Using VSAM with ITF

Diagnosing Error Conditions When Using VSAM with C++ Generated Programs

Data Conversion

Known Problems/Limitations

New Parameters and Functions in the Generated Applications

Relational Database Import via IXF Files

VisualAge Generator Templates User Interface

Relational Database Import Function

QuickStart

Setting a Current User After Installation

BiDi Support

Generators

Database Management

IBM VisualAge Generator

IBM VisualAge Smalltalk