IBM VisualAge Generator
V4.5 FixPak3 Readme
PTF #: UQ62350

Table of Contents
Introduction

Product Enhancements, Support, & Limitations

VisualAge Generator v4.5 FixPak3 Installation Notes VisualAge Generator Templates Installation Notes

List of APARS

 
 
Introduction

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

Product Enhancements, Problem Support, and Limitations

FixPak3

VisualAge Generator V4.5 FixPak3 contains enhancements, problem support, and limitations for the following:

Known Issues

            CSO8000E The password entered to the Gateway has expired. %1
            Explanation: The VisualAge Generator GatewayServlet received an expired password exception when attempting to authenticate the user with the provided password.
            User Response: Examine the exception information returned in order to determine the cause of the problem. Correct the problem by proving a new password.

            CSO8001E The password entered to the Gateway is not valid. %1
            Explanation: The VisualAge Generator GatewayServlet received an invalid password exception when attempting to authenticate the user with the provided password.
            User Response: Examine the exception information returned in order to determine the cause of the problem. Correct the problem by providing a new password.

            CSO8002E The userid entered to the Gateway is not valid. %1
            Explanation: The VisualAge Generator GatewayServlet received an invalid userid exception when attempting to authenticate the user with the provided userid.
            User Response: Examine the exception information returned in order to determine the cause of the problem. Correct the problem by providing a new userid.

General Improvement

Provide Security exits for web transactions

        Web transaction audit exits allow a customer to write exit programs that are called whenever a user interface record (UIR) is transmitted or received by the gateway servlet or host transaction program. The exits have access to the UIR contents as well as transaction program name, UIR name, session identifier, and user identifier.
The customer can use the exits to:

Gateway Servlet Exits

        This enhancement gives users the ability to add their own information for their transactions into the gateway servlet by a user developed class and pass it to tier 3 host systems where their web transactions reside on CICS an MVS and IMS system. It also allows users to get UI Record bean, sessionId, userid and password information.
The gateway’s exit provides an interface to users to be able to:

To be able to use the functionalities:
1. User specifies hptHostExitName parameter in gateway properties file. This will provide a name for the user exit on the host system. Provided name will be send to host system by the gateway’s communication protocol which was specified as commtype parameter in serverLinkage entries.

2. User specifies hptUserExitClass parameter in gateway properties file. To deploy the SampleUserExit class, set the hptUserExitClassName parameter in Gateway Properties file as follows:

        HptUserExitClassName=com.ibm.hpt.gateway.SampleUserExit

The class that was specified for this parameter will be an implementation of the interface provided for them. Provided interface named GatewayUserExit allows users to implement the following two methods:

Ÿ void uirAuditInput(VGJUIRecordBean bean, GatewayAccess ga, HttpServletRequest request request, HttpServletResponse response);

This method allows users to:

1) Reach the UI Record bean before UI record data is sent to tier 3 by gateway servlet.

2) Work with HttpServletRequest/Response objects.

3) Set or get the user specific data into/from GatewayAcess object.

4) Work with the public GatewayAccess object methods.

NOTE: CICS requires 32K of COMMAREA length. So larger amount of user specific data set into the GatewayAccess object will cause less COMMAREA occupation for the application data.
 
 

Ÿ void uirAuditOutput(VGJUIRecordBean bean, GatewayAccess ga, HttpServletRequest request, HttpServletResponse response);

This method allows users to:

1) Reach the UI record data which was sent back from tier 3 to gateway servlet.

2) Work with HttpServletRequest/Response objects.

3) Get the user specific data in GatewayAcess object.

4) Work with the public GatewayAccess object methods.

        The interface imports GatewayAccess class including the following methods which can be used in the implementation class which was specified by the hptUserExitClass parameter:
Ÿ public String getMyInfo(); This method gets the user specific data.

Ÿ public void setMyInfo(String myInfo); This method sets the user specific data.

Ÿ public byte[] getMyInfo(); This method gets the user specific data.

Ÿ public void setMyInfo(byte[] myInfo); This method sets the user specific data.

Ÿ public String getConnectionID; This method gets the connection id

Ÿ public StringŸ getSessionId(); This method gets the sessionId.

Ÿ public String getUserId(); This method gets the userId.

Ÿ public String getProgramName(); This method gets the host program name.

Ÿ public void setErrorRC(int); This method sets the return code.

Ÿ public void setErrorMessage(String); This method sets the message.

Ÿ public void setUserState(Object); This method sets the user state.

Ÿ public Object getUserState(); This method gets the user state.

        In addition to the user specific data and UI record bean, GatewayAccess class allows users to be able to reach HttpServletRequest, sessionId, and userId information.

3. If an error code and message are returned by the exit, the transaction is terminated and the error will be displayed to the user.

You can find a sample gateway exit program, SampleUserExit.java, in the directory:

\VisualAge For Java\ide\program\samples

        The sample SampleUserExit class implements the GatewayUserExit interface. You can use that class as a model for your own. At installation, you can find the source code for the GatewayUserExit interface and the sample gateway exit program, SampleUserExit.java, in the samples directory of the VisualAge Generator Server product used on tier 3. (The samples directory is at the same hierarchical level as the file hptGateway.jar.)

Host Exits

        Host exits are supported in the CICS and IMS environments. The exit name is specified to the gateway servlet in the properties files and passed to the host by the gateway servlet.

The exit is called from at the following points:

Ÿ Initial entry to a web transaction (no UIR) - requires generation of web transaction with fix PQ53756 applied to VisualAge Generator developer; a fix test may be requested; the fix is also shipped with Fix Pack 3

Ÿ Entry to a web transaction with a UIR

Ÿ Return from a web transaction to the servlet with a UIR

Ÿ Return from a web transaction without a UIR (normal termination)

Ÿ Return from a web transaction with error messages in UIR CSOERRORUIR (abnormal termination).

        The parameters passed to the exit are the UIR buffer and the audit exit information block. The UIR buffer should be referenced only if the UIR length is greater than zero. The information block is has the following format when declared as a COBOL structure in the sample exits:

01 ELA-AUDIT-INFO.

05 AUDIT-INFO.

06 AUDIT-ID PIC X(8).

06 AUDIT-ID-LEVEL PIC X(4).

06 AUDIT-CONNECTION-KEY PIC X(8).

06 AUDIT-SESSION-KEY PIC X(8).

06 AUDIT-USER-ID PIC X(8).

06 AUDIT-TRANS-NAME PIC X(8).

06 AUDIT-PROG-NAME PIC X(8).

06 AUDIT-UIR-NAME PIC X(18).

06 AUDIT-REASON PIC X(1).

88 AUDIT-REASON-IN VALUE "I".

88 AUDIT-REASON-OUT VALUE "O".

88 AUDIT-REASON-INIT VALUE "N".

88 AUDIT-REASON-CLOSE VALUE "T".

88 AUDIT-REASON-ABTERM VALUE "A".

06 AUDIT-EXTRA-DATA-TYPE PIC X(1).

88 AUDIT-TEXT VALUE "T".

88 AUDIT-BINARY VALUE "B".

06 AUDIT-UIR-LEN PIC S9(9) COMP.

06 AUDIT-EXIT-MSG-LEN PIC S9(9) COMP.

06 AUDIT-EXTRA-DATA-LEN PIC S9(9) COMP.

06 AUDIT-EXIT-RETURN-CODE PIC S9(9) COMP.

88 AUDIT-EXIT-RC-OK VALUE 0.

06 AUDIT-RESERVED PIC X(62).

06 AUDIT-EXIT-MSG PIC X(250).

06 AUDIT-EXTRA-DATA PIC X(1000).

        The audit routines can access and set the exit return code, exit message and length, extra data, and extra data length, and any information in the UIR. The audit information block is kept around for the life of the transaction so that changes made on input are available to the return exit calls. If "extra information" is passed from the servlet to the user exit, the exit must reset the extra information length to zero if the input information should not be passed on to the return exits.

        If the exit return code has a value other than 0, the transaction is terminated. The error code is returned to the servlet, and the error message is writen to the user using the CSOERRORUIR user interface record (also used for writing the runtime services error messages).

Two sample exits are shipped with the fix:

ELACICAX for CICS

ELAIMSAX for IMS

        The source for the sample exits is the VisualAge Generator SELASAMP library. The load modules for the sample exits are in the SELALMD library. The CICS exit requires a PPT entry before it can be used.

        The sample exits write audit information to the VisualAge generator default error log (transient data queue ELAD for CICS and message queue ELADIAG for IMS). You can print the audit information with the ELAC transaction (CICS) or the ELAMQJUD BMP JCL in library SELAJCL (IMS).

CSO userid and password exits

        The userid/password user exit shipped with VisualAge/Generator middleware previously was called to provide the userid and password for calling remote programs on CICS via the CICS External Call Interface or on IMS via IMS APPC. In addition the exit is now called an SQL database (DB2, Oracle, or ODBC) connection when the developer has not specified the SQL userid and password. A future fix will also enable the exit to be called on on a generation file transfer via TCP/IP where the developer has not specified a TCP/IP userid and password.

        The VisualAge Generator function that needs a userid and password calls the exit indicating the reason why the password is needed. The customer is responsible for obtaining and storing the userid and password and providing it to VisualAge Generator when the exit is called. If the exit does not return a userid and password, VisualAge Generator looks for the userid/password as it does in the current product.

        The exit name is specified in the environment variable CSOUEXIT. The default user exit CSOUIDPW is a C language program that reads environment variables CSOUID and CSOUIDPW to obtain passwords for client server calls. If called for other reasons, or if the environment variables are not set, the exit returns null strings for the userid and password. userid password/specification will be called whenever a password is needed. The source code for CSOUIDPW is shipped with the product.

        The exit is passed the following C structure as input:

struct cmUIDPWD
{
    char loginName[20];
    char password[20];
    char systemName[20];
    long middlewareType;
    short promptType;
    short reserved;
    char* ftpHostName;
};

        The systemName is the name of the system to which we are connecting for CICS ECI, IMS/APPC, or SQL. If the middleware type is ftp, the ftpHostName is the name of the system to which the files are being transferred.

        The middleware type is a code indicating what type of login is being performed. Currently supported values are:

#define CMST_ECI_C2 7 /* CICS OS/2 ECI */
#define CMST_ECI_CM 8 /* CICS CLIENT ECI */
#define CMST_APPC_IMS 11 /* APPC/IMS */

        New types for data base and TCP/IP FTP are:

    #define CMST_CMCONCT 12 /*Database Connection */
    #define CMST_GEN_FTP 26 /* Userid/password for FTP */

        Promptype is a code indicating whether this an initial request or a request following a login that failed due the bad user id and password.

#define CMPR_INITIAL 0 /* Initial prompt */
#define CMPR_REPROMPT 1 /* Reprompt - bad uid or pw */
Authentication support in VisualAge Generator Gateway Servlet

This VisualAge Generator enhancement provides new options for authentication support. By using this enhancement, you can:

For a detailed explanation of this enhancement, please visit: http://www-4.ibm.com/software/ad/visgen/library/authenticate.htm

Addition of /OUTFILE to HPTCMD PRINT

        The /OUTFILE parameter specifies the name of the sequential file you want to use as the OUTFILE. You can use the OUTFILE as input for other subcommands.

        The name must be a valid file name.

        See "Sequential file formats" in VG user's guide for a description of the format. If the file specified with the /OUTFILE parameter is already exists, the file will be overwritten with the content of the current PRINT subcommand.

        PRINT subcommand example

        hptcmd print /app=HptSampleEzereampParts /outfile=d:\temp.out
 
 

ITF XFER Emulation for OS/400

        If the ITF EZESYS option is set to OS400, then DB2 and Client Access/400 connections remain in effect across an XFER from one program to another. This is consistent with the runtime behavior of generated programs on OS/400.

ITF EBCDIC Option

        The ITF EBCDIC option gives the developer the choice of running a test session in ASCII mode or EBCDIC mode. EBCDIC mode more closely emulates the internal storage of data on host systems that use EBCDIC code pages, like OS/390, VSE, VM, and OS/400.

        ASCII mode is the default. All character item values are in ASCII and all numeric items are in intel format while the test is running. Data elements must be converted to host format on calls to remote programs and accesses to remote files and databases. Character item comparisons use ASCII collating sequence.

        In EBCDIC mode, the data in records, items, and tables is in EBCDIC (character data) or host numeric format so that the data does not have to be translated to host format on remote calls or remote file and database accesses. Parameters are converted to ASCII or Intel format on calls to
local C++ routines, EZE math and string functions, and SQL calls so that the the local routines or database calls get the data in the format that they expect. Data in serial, indexed, or relative files and MQ message records is written and retrieved in EBCDIC. Character comparisons in IF and WHILE statements are performed using EBCDIC collating sequence.

        GUI programs always run in ASCII mode. If a GUI calls another program running under the test facility when the EBCDIC option is in effect, the parameters are converted from ASCII to EBCDIC on the call.

        Except for the GUI program testing described in the previous paragraph, you cannot switch back and forth between EBCDIC and ASCII mode in the same test run. You must stop test facility, change the EBCDIC option selection, and restart test facility to switch modes.

        When using MQ message records in EBCDIC mode, do not specify a conversion table in the resource association file for the message queue record. The messages will always be in the EBCDIC host format.

        EBCDIC mode is selected from the test options or preferences window. Leave the conversion table field associated with the EBCDIC option blank. The conversion table field is intended for use with bi-directional languages (Arabic and Hebrew) and double-byte languages (Chinese, Japanese, and Korean) which have special ASCII/EBCDIC translation considerations beyond simple code page translation. EBCDIC mode is not supported for these languages in FixPack 3. For other languages, code page translation is performed using Smalltalk ascii-to-ebcdic conversion based on the current locale.

Java Server Generation for Linux, OS/400 and OS390

        VisualAge Generator support for Java Server generation has been expanded to include four additional systems: Linux, AIX, OS/400 and OS/390. This new support allows users to generate main batch, called batch, and Web Transaction program parts into Java source code. The Java code is deployed to the target system and compiled for execution. After proper preparation, the compiled java server programs can be executed under VisualAge Generator Server in an e-business environment.

We have determined through our testing that the VAGen generated java code is completely portable, in most cases and can be moved between disparate systems. As such, the java code generated for a Linux or Windows system can be ported to AIX without change as long the code is supported by the respective VisualAge Generator Server product. For instance, VisualAge Generator Server for Windows and VisualAge Generator Server for AIX supports MQ file access, but not VisualAge Generator Server for Linux.

When generating java server programs for the AIX environment, choose LINUX from the target system drop-down list. The AIX option will be available in next fixpak of VAGen.

Preparing to Run Java Programs on the Target System:

Users targeting AIX for java server generation should use /SYSTEM=JAVALINUX generation option.

WebSphere Application Server Advanced Edition V4.0 Support

VisualAge Generator provides the same support for WebSphere Application Server V4 that it provided for previous versions of WebSphere. No new enhancements were made to support any new WAS V4 functionality. Users can continue to run the VAGen gateway servlet and the java classes generated for web transactions as before. The only difference users should be aware of is how web transactions are packaged and deployed.

In order to deploy VAGen web transactions to a WAS V4 system, the web transactions must be first assembled into an enterprise archive file, EAR, as a J2EE application. For information on how to package VAGen generated web transactions into an EAR file using the WebSphere Application Assembly Tool and how to deploy the EAR file from the WebSphere Advanced Administrative Console, please refer to the newsletter article Deploying VisualAge Generator Web Transactions Using WebSphere Application Server 4.0 And WebSphere Application Server Assembly Tool at http://www-3.ibm.com/software/ad/visgen/library =>

 http://www-3.ibm.com/software/ad/visgen/library
NOTE: VAGen does not currently make use of the J2C connectors to access CICS. VAGen v4.5 continues to use CICS Transaction Gateway classes to connect to CICS.

The following table shows the combinations of software products and versions that have been tested and verified for VisualAge Generator support ofWebSphere Application Server Advanced Edition 4. 


 
Supported WebSphere Platforms
Prerequisite Software 
WAS 4.01 for Linux/390 
-SUSE 2.4.7 kernel - Enterprise Edition 7
-DB2 7.2 fix pack 5
-Websphere GA level - a0150.05 build
WAS 4.01 for Linux/Intel
-SUSE 2.4.4-64gb-smp Kernal Versoin
-redhat 2.4.2-2 Kernal Version
-DB2 v 7.1.0.41 solo426 u475381
-WebSphere 4.01 
WAS 4.01 for AIX
-AIXVersion 5
-DB2 V7.1.0.43
-WAS4.01
WAS 4.0 for iSeries
-iSeries V5R1

 

MQSeries

        If you are working with MQSeries queues and your code ends a unit of work, VisualAge Generator commits or rolls back all recoverable resources being accessed by your program, including databases, message queues, and recoverable files. This outcome occurs whether you use the eze words (EZECOMIT, EZEROLLB) or the calls to MQSeries (MQCMIT, MQBACK); the appropriate eze word is invoked in either case. A rollback occurs if a VisualAge Generator program terminates early because of an error detected by VisualAge Generator run-time services, even in non-transactional environments.

FixPak2

VisualAge Generator V4.5 FixPak2 contains enhancements, problem support, and limitations for the following:

General Improvement

Linux/390 Tier 2 Gateway Support

FixPak1

VisualAge Generator V4.5 FixPak1 contains enhancements, problem support, and limitations for the following:

Java Performance Improvements

VAGen Java API updates

With this FixPak, the signatures of several VAGenUtilityInterface APIs have changed. Current users of the APIs will need to change their code. In addition, new APIs to add menu items to the Packages menu of the VAGen Parts Browser have been added, and a new interface has been added which provides a means for executing code when the product is started.


VisualAge Generator Templates

 

Product Enhancements

VisualAge Generator V4.5 fixpak 3 contains VisualAge Generator Templates (VAGT) enhancements, problem support, or limitations for the following:
Various bugs have been fixed (see the APAR section). The main improvements are listed below:
 

Fixpak 1
Performance enhancements

Manipulation of the VAGT components is faster. Opening an editor is faster too.

Generated Web Client


Fixpak 2
Enhancement of the browsers

Generated Web Client Generated Java GUI Client Generation New with Fixpak 3

Generated Java GUI Application

Generated Smalltalk application

Limitations and Known Problems with VAGT

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

VisualAge Generator 4.5 FixPak3 Installation Notes

Important Information

Installing VisualAge Generator Developer on VA Java

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

Important: If you have an existing repository and want to continue using it, please make sure you back it up before you perform any migration. Before you install FixPak3, you must first install or upgrade to VisualAge for Java 3.5.3 or VisualAge for Java 4.0. Please refer to the Java 3.5.3 or 4.0 Installation and Migration Guide for information on how to migrate to VisualAge for Java 3.5.3 or VisualAge for Java 4.0. There are sections in that guide on migrating an existing shared repository.

The VisualAge for Java 3.5.3 updates can be found at: http://www.software.ibm.com/vadd

Installing VisualAge Generator Developer on VA Java

Installing VisualAge Generator Developer on VA Smalltalk

Installing VisualAge Generator Common Services

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

Installation Troubleshooting

VisualAge Generator Templates Installation Notes

VisualAge Generator Templates Installation

VisualAge Generator Templates (Standard Functions) is installed with VisualAge Generator Developer.
 
List of APARS

FixPak3

PQ39119 NLS CHARACTERS NOT FOLDED TO UPPERCASE
PQ42119 VISUALAGE GENERATOR PRINT SETUP SETTINGS NOT SAVED WHEN USER EXITS OUT OF THE IDE.
PQ42636 C++ GEN SHOULD NOT SPLIT STRINGS WHEN MAX LINE LENGTH EXCEEDED
PQ42786 COBOL COMPILE ERROR, IGYPS2121-S, <DATA ITEM> WAS NOT DEFINED AS A DATA-NAME.
PQ42786 COBOL COMPILE ERROR, IGYPS2121-S, <DATA ITEM> WAS NOT DEFINED AS A DATA-NAME
PQ42938 DROPDOWN LIST INCLUDED IN FORM INSTEAD OF PLAIN PARAGRAPH TEXT WHEN USING VISUALAGE GENERATOR UIRECORD PART TO BUILD HTML PAGE.
PQ44450 ERROR RECEIVED DURING VALIDATE OF A CONVERSE FUNCTION REFERENCING A MAP WHOSE NAME HAS CHANGED
PQ44587 AN IMAGE COMMUNICATIONS ERROR OCCURS WHEN MIGRATING A CONFIG MAP FROM V3.1 TO V4.5
PQ44628 GUI MIGRATION DOES NOT HANDLE PROMOTED EXECUTE OF PROGRAMS
PQ44849 WALKBACK CREATING VAGEN VARIABLE WHICH HOLD A PROGRAM
PQ45042 GENERATION ERROR WHEN MAP ITEM PARM IS ANYCHAR
PQ45721 TRAP IN EFKAYZ45.DLL IF /SPZERO GENOPT USED W/ NUM RETURN VALUE
PQ45839 GENERATED COBOL FAILS TO COMPILE WITH MSGIGYPS0037-S. STATEMENT REFERENCES AN UNQUALIFIED NON-UNIQUE DEFINED NAME.
PQ46576 TAB Character identification Utility - The "Tabs" utility is in V4.5. The Smalltalk code is released in map "VAGen Java Interop" and the Java code is released in Project "IBM VisualAge Generator Utilities" and this project is released in solution "IBM VisualAge Generator Solution"
PQ46825 SQL RETURN CODE -519 RECEIVED WHEN RUNNING
PQ46916 WALKBACK WHEN PERFORMING 'ASSOCIATES' ON MAP GROUP
PQ47330 MQ ON IMS FAILS WITH ABEND S0C4.
PQ47402 IMPORT COMMAND ISSUES RETURN CODE 8 (RC=8) EVEN THOUGH THE IMPORT COMMAND WAS SUCCESSFUL.
PQ47502 USER GETS AN IMAGE COMMUNICATIONS ERROR WHEN EXPORTING W/ ASSOC
PQ47661 VAGEN: WALKBACK CREATED WHEN MIGRATING FROM V3.1 TO V4.5 IF THE APPLICATION BEING MIGRATED HAS SUBAPPLICATIONS
PQ47718 WALKBACK SAVING VISUALAGE GENERATOR SQLROW RECORD PART AFTER ADDING ADDITIONAL SHARED DATA ITEMS
PQ47753 DATA FILE CONVERSION TOOL CONVERTS FILE INCORRECTLY
PQ47797 HOST VARIABLE IN VISUALAGE GENERATOR SQL CLAUSE SHOULD NOT HAVE
PQ47853 VALUE OF EZEDEST IS RESET AFTER SEGMENT BREAK WHEN TESTING
PQ47888 PROGRAM EXECUTING ON CICS FILLS TEMPORY STORAGE AND THEN ABENDS WITH SHORT ON STORAGE CONDITION.
PQ47961 USER RECEIVES ERROR ON PREPARE FOR WEB TRANS DUE TO INCOR. PERMISSION.
PQ48083 PERFORM STATEMENT GENERATED FOR A MOVE CORRESPONDING IS NOT CORRECT WHEN THE ITEM IS A MULTIPLE OCCURING FIELD
PQ48087 JAVA PROJECTS CONTAINER DOES NOT DISPLAY THE SELECTED PROJECT WHEN DEFINING VISUALAGE GENERATOR BATCH SETTINGS.
PQ48184 CONVERSION TABLE NAME INCORRECT ON SUBSEQUENT CALLS FROM JAVA PROGRAM
PQ48221 validate of UIREC is MODIFIED not resulting in error msg
PQ48223 MESSAGE HPT.CG.62.E ISSUED WHEN GENERATING WEB TRANSACTION PROGRAM.
PQ48230 WALKBACK ISSUED WHEN TESTING OR VALIDATING WEB TRANSACTION PROGRAM
PQ48287 MESSAGE FROM BROWSER INDICATING DOCUMENT CONTAINED NO DATA WHEN DATA WITH VISUALAGE GENERATOR TESTPOINT DATA IS MODIFIED
PQ48291 ERROR SETTING EZEUIERR FOR DROPDOWN LIST OF UIRECORD.
PQ48373 ABENDELAE CALLING REMOTE CICS VAGEN PROGRAM FROM GUI CLIENT USING ELACNKOR CONVERSION TABLE
PQ48443 RESOURCE BUNDLE GENERATED FOR UIRECORD WITH /NOGENRESOURCEBUNDL PQ48476 GENERATED FILES NOT DELETED EVEN IF DELETE_FILES=Y
PQ48488 SEARCH OF A PART FROM VAGEN PARTS BROWSER REFERENCES RESULTS IN FATAL APPLICATION ERROR - EXIT DUE TO ERROR: 53
PQ48491 GENERATING WEBTRANSATION PROGRAM RESULTS IN WALKBACK, HPTJSPREPEATELEMENT D/N/U SCRIPTLETVARIABLEDECLARATIONCLASS
PQ48525 VAGEN V4.5 - HPT.CM.107.E RECEIVED IN ITF AFTER SETTING A BREAKPOINT ON AN ARGUMENT
PQ48555 ITF MONITOR STARTS WHEN EDITING A VAJAVA VISUAL CLASS IF
PQ48576 GW ERROR MESSAGE FOR IMS ABEND ERROR SHOWS INDEX OUT OF RANGE
PQ48656 QUIET OPTION ON EFKSND.REX DOES NOT WORK WHEN USING TEMPLATES
PQ48659 HPT.INI CONTENTS ARE LOST WHEN WALKBACK OCCURS DURING THE UPDATE TO THE FILE ON PRODUCT SHUTDOWN
PQ48730 WHEN USING EZEUIERR THE DATA ITEM IN ERROR IS NOT DISPLAYED
PQ48981 RECORD EDITOR WILL SAVE RECORD > 32000 BYTES
PQ48988 PASTING DATA ITEM INTO RECORD DEFINITION CREATES NEW EDITION OF THE DATA ITEM IN REPOSITORY.
PQ49155 AFTER FP2, WHEN STARTING THE PRODUCT, ERROR MSG IS RECEIVED
PQ49156 GETTING A COMPILER ERROR WHEN USING LOCAL STORAGE ON DXFR
PQ49235 WALKBACK GENERATING REDEFINED RECORD WITH UNDEFINED SHARED DATA ITEM
PQ49282 SUBMIT BYPASS NOT IGNORING UI RECORD EDITS
PQ49341 INSERT LEVEL77/PARENT/SUBSTRUCT NOT AVAILABLE FROM MENU OPTIONS
PQ49345 WALKBACK 'HPT40MIGRATOR CLASS DOES NOT UNDERSTAND MIGRATIONERROR.' MIGRATING APPLICATION FROM 3.1 TO 4.5.
PQ49441 PASSWORD EXPOSED IN ITF TRACE
PQ49445 VISUALAGE GENERATOR REFERENCES TOOL NOT HANDLING SQL CLAUSE CORRECTLY
PQ49449 INDEX OUT OF RANGE WALKBACK WHEN USING VISUALAGE GENERATOR IMPORT UTILITY
PQ49462 VAGEN V4.5: HPT.CM.375.E - USERID DOES NOT HAVE A VALID PART TYPE FOR THIS USAGE, WHEN SAVING PART IN MAP EDITOR
PQ49551 When remote VSAM and relative, convert NUM record ID to BIN
PQ49672 HPT.CM.249.E ISSUED WHEN GENERATING A VISUALAGE GENERATOR
PQ49676 DBSTRING D/N/U SSTURLENCODE WALKBACK WHEN BIN ITEM IN PGM LINK>
PQ49680 CUSTOMER RECEIVING HPT.CG.13.I WHEN TRYING TO GENERATE.
PQ49684 UI RECORD IS USING THE VALUE OF THE SUBMIT BUTTON LABEL RATHER THAN THE SUBMIT VALUE.
PQ49854 INCORRECT DATA IS BEING MOVED INTO MAP ARRAY ON A MOVE CORRESPONDING.
PQ49943 ERROR RETURNING FUNCTION VALUE TO DATA ITEM TOO SMALL
PQ50142 PERFORM CHANGES ON PART CAUSES DUPLICATE FUNCTION OPTION LINES
PQ50164 HPT.CM.646.E ( MSGHPTCM646E ) ISSUED WHEN PERFORMING A BATCH
PQ50313 EZELOC/EZECONVT NOT PICKED UP USING GUI RUNTIME
PQ50386 MIGRATING 4GL MAPS VIA ESF PRODUCED BY CSP 3.3.0
PQ50426 REMOVE OBSOLETE REFERENCES TO VISUALAGE GENERATOR DATA ITEMS DEFINED AS PIC A IN THE GENERATED COBOL
PQ50434 LINK ERROR "REDEFINEDRECORD::SETUP(VOID*)" UNRESOLVED EXTERNAL
PQ50435 V3 TO V4 MIGRATION TOOL DOES NOT HANDLE CONFIGURATION MAPS WITH TWO CHARACTER NAMES
PQ50517 RUNTIME ERROR: HPTFLOWMODEL DOES NOT UNDERSTAND FINDOPTIONTEXT
PQ50583 INCORRECT COBOL GENERATED FOR MOVE CORRESPONDING
PQ50744 INCOMPATIBLE TYPE FOR METHOD. CAN'T CONVERT JAVA.LANG.STRING TO COM.IBM.VGJ.WGS.VGJNUMERICITEM
PQ50823 COMPILE ERROR PREPARING VISUALAGE GENERATOR COBOL PROGRAM THAT CONTAINS FUNCTIONS USING LOOSE TYPING IN PARAMETER LIST
PQ50828 VALIDATION FAILS INTERMITTENTLY WITH HPT.CM.782.E
PQ50830 EZECONV DOES NOT CONVERT DATA AS EXPECTED AFTER GENERATING THE
PQ51125 THE VG MIGRATION GUIDE STATES THAT "THE VISUAL TABLE PART FROM THE DATA ENTRY CATEGORY ON
PQ51160 WB when validating when undefined functions exists in pgm
PQ51177 DIFFERENT MATH RESULTS BETWEEN ITF AND C++ WGS
PQ51198 WALKBACK WHEN PROGRAM IS VALIDATED AND A SQL WHERE STATEMENT CONTAINS A SEMI-COLON.
PQ51402 DECIMAL POINT SET TO X'00' WHEN LOCALE IS SET TO 'C' IN CICS
PQ51788 IGYDS0023-E COBOL COMPILE ERROR GENERATED DUE TO RECORD LENGTH MORE THAN 30 CHARACTERS.
PQ51800 EZEAID VALUE IS NOT RESET ACROSS A DXFER IN A WEB TRANSACTION
PQ51940 VISUALAGE GENERATOR PROGRAM LISTING ENHANCEMENTS
PQ51992 "PACKAGE NAME" INFORMATION WINDOW DOES NOT REMEMBER PREVIOUS PACKAGE NAME ENTERED AND INSTEAD DEFAULTS TO MSL NAME.
PQ52240 EZERT8 NOT RESET AFTER CALL TO ANOTHER CICS PROGRAM
PQ52358 VisualAge Generator Test Facility Enhancement to Allow Testing
PQ52448 INCORRECT JAVA GENERATED FOR LOCAL STORAGE RECORD
PQ52618 VAGEN V4.0 FP3 - FP3 DID NOT INCLUDE THE JAVA TAB UTILITY
PQ52670 INCORRECT VALIDATION OF PCB SEGMENTS
PQ52786 GARBAGE CODE INSERTED DURING C++ GENERATION ON DBCS.
PQ52862 ADD CAPABILITY TO SEARCH A LARGE VAGEN TABLE CONTENTS
PQ52928 MISSING HELP CAUSES WALKBACK.LOG TO BE GENERATED.
PQ53007 VAGEN DISPLAYS INVALID DBCS IN MAP VARIABLE
PQ53011 CORRELATION NAME SHOULD BE REMOVED FOR DELETE CLAUSE
PQ53021 IMPROVE PERFORMANCE ON REPEATED CALLS TO THE SAME VG C++ PROGAM
PQ53165 SUBMIT VALUE ITEM NOT UPDATED WHEN A SUBMIT BYPASS PUSH BUTTON
PQ53177 MAP FIELD CURSOR IS INCORRECT IF SET IN CALLED FUNCTION.
PQ53205 MSGFCW0015EWHEN PROCESSING HEX DATA RETRIVED FROM VISUALAGE
PQ53210 INCORRECT COBOL GENERATED FOR MOVE CORRESPONDING.
PQ53309 APAR TO CHANGE THE BEHAVIOR OF HPTLOGOUT
PQ53323 VAGEN V4.5 FP2: HPT.CM.435.E FOLLOWED BY WALKBACK.LOG WHEN
PQ53473 SUBMIT ITEM VALUE NOT MOVED TO UIRECORD SUBMIT ITEM DATA ITEM.
PQ53751 FUNCTIONS LOCAL STORAGE IS NOT UPDATED WHEN USED IN A VISUALAGE
PQ53756 VAGEN V4.5: DEVELOPMENT APAR TO CREATE A WEB TRANSACTION AUDIT
PQ53757 VAGEN V4.5 FP2: WHEN USING EZETST IN SUBSCRIPT OF A WHILE LOOP
PQ53819 VAGEN WALKBACK WHEN PROMOTING BYTECHARACTER DATA WITH TYPE PACK
PQ53860 INCORRECT SEARCH PATH FOR CALLED APPLICATION ON AIX
PQ54010 USING VALIDATE & FORMAT FROM THE FUNCTION EDITOR WILL INSERT A
PQ54021 VAGEN V4.5 FP2: SCAN, UPDATE, DELETE, SCAN DOESN'T WORK FOR
PQ54394 WB WHEN USING A RETURN VALUE AND EZERTN
PQ54407 WALKBACK TRYING TO OPEN THE VISUALAGE GENERATOR RESOURCE
PQ54676 A representative defect for PQ54676
PQ54738 HPT.CM.218.E IN ITF TESTING SQLEXEC STMT W/O ETSB
PQ54744 CROSS REFERENCE INFORMATION NEEDS TO BE ADDED TO PRINT FOR PART
PQ55169 FILL CHARACTER DOES NOT SHOW ON UI RECORD WHEN USING ITF
PQ55221 CANNOT REPOSITION CURSOR IN ITF WHEN USING CALLABLE ITF.
PQ55390 WALKBACK UNDEFINED OBJECT ODES NOT UNDERSTAND CANBERUN WHILE
PQ55391 WALKBACK UNDEFINED OBJECT DOES NOT UNDERSTAND ADDSERIAL TESTING
PQ55428 WALKBACK OCCURS IN ITF AFTER EDITING A MEMBER ASSOCIATED WITH THE PROGRAM BEING TESTED
PQ55429 WALKBACK TESTING PROGRAM UNDER ITF
PQ55430 BATCH GENERATION OF VISUALAGE GENERATOR PROGRAM RESULTS IN WALKBACK.
PQ55431 USING VISUALAGE GENERATOR FILE CONVERSION UTILITY RESULTS IN WALKBACK
PQ55435 WALKBACK VALIDATING VISUALAGE GENERATOR PROGRAM.
PQ55500 /OUTFILE OPTION ADDED FOR HPTCMD PRINT
PQ55537 VISUALAGE GENERATOR COMPLICATION FAILS WITH MSG IGYPS2121-S.
PQ55651 HPT.CM.143.E WHEN RECORD IS A REDEFINE AND INCLUDES AN OCCURS
PQ55666 WALKBACK WHEN SORTING CXSTRING VALUES
PQ55715 WIDGET ALREADY DESTROYED WALKBACK ISSUED RUNNING VISUALAGE
PQ55716 MESSAGE WRITE FAILED, RC = 232 WALKBACK ISSUED RUNNING VISUALAGE
PQ55721 VARIOUS INDEX OUT OF RANGE WALKBACKS OCCURRING WITHIN VISUALAGE GENERATOR DEVELOPER
PQ55722 TRANSCRIPTTTY DOES NOT UNDERSTAND SHELL WALKBACK RECEIVED
PQ55723 OBJECT>>#AT: DUE TO INDEX OUT OF RANGE IN ARGUMENT 1 WALKBACK RUNNING VISUALAGE GENERATOR DEVELOPER
PQ55724 UNDEFINEDOBJECT DOES NOT UNDERSTAND TYPE WALKBACK RUNNING
PQ55725 EBADF (9) BAD FILE DESCRIPTOR WALKBACK ISSUED RUNNING VISUALAGE
PQ55726 UNDEFINEDOBJECT DOES NOT UNDERSTAND STATEMENTASSTACKLEVEL: WALKBACK RUNNING VISUALAGE GENERATOR DEVELOPER
PQ55727 UNDEFINEDOBJECT DOES NOT UNDERSTAND ISVISIBLE WALKBACK RUNNING
PQ55728 UNDEFINEDOBJECT DOES NOT UNDERSTNAD HELPMAPKEY RUNNING VISUALAGE GENERATOR DEVELOPER
PQ55729 UNDEFINEDOBJECT DOES NOT UNDERSTAND RELEASECACHEDIVS WALKBACK RUNNING VISUALAGE GENERATOR DEVELOPER
PQ55730 RECEIVER MUST BE A BOOLEAN WALKBACK RUNNING VISUALAGE GENERATOR DEVELOPER
PQ55731 UNDEFINEDOBJECT DOES NOT UNDERSTAND WALKBACK ISSUED FROM VISUALAGE GENERATOR DEVELOPER
PQ55732 UNDEFINEDOBJECT DOES NOT UNDERSTAND ASDICTIONARY WALKBACK RUNNING VISUALAGE GENERATOR DEVELOPER
PQ55733 WALKBACK UNDEFINEDOBJECT DOES NOT UNDERSTAND REFERENCE ISSUED IN VISUALAGE GENERATOR DEVELOPER
PQ55734 UNDEFINEDOBJECT DOES NOT UNDERSTAND CLOSE.
PQ55735 UNDEFINEDOBJECT DOES NOT UNDERSTAND ISMAPPED WALKBACK ISSUED.
PQ55736 UNDEFINEDOBJECT DOES NOT UNDERSTAND CANCELLED WALKBACK ISSUED.
PQ55892 PGM FAILS VALIDATION FOR CICS IF INDEX FILENAME CONTAINS @#$
PQ55898 VAGEN V4.5: GENERATE ERROR: HPT.CM.255.E AN ERROR OCCURRED IN DLL EFKAYZ45.DLL. THE RETURN CODE IS 1008.
PQ55899 VAGEN V4.5 FP2: WALKBACK OCCURED IN ITF, IN CGDRAWABLE CLASS
PQ56038 COMMON USER EXIT FOR USERID/PASSWORD SPECIFICATION IN
PQ56107 UNDEFINEDOBJECT DOES NOT UNDERSTAND DUPLICATENAME
PQ56108 (EXCLDTOBJECTNOTFOUND) OBJECT NOT FOUND WALKBACK USING VISUALAGE GENERATOR PROGRAM EDITOR
PQ56168 Negative port number
PQ56240 EZEPRINT TO FILE SHOULD REPLACE ATTRIBUTE MARKERS WITH SPACES
PQ56659 MQGET MQGMO_WAIT OPTION IS IGNORED BY VAGEN C++ WGS
PQ56780 INCORRECT COBOL GENERATED FOR ASSIGNMENT STATEMENT WHEN COMMA IS USED AS DECIMAL SYMBOL IN REGIONAL SETTINGS.
PQ56940 WALKBACK ITFREDEFINEDRECORD DOES NOT UNDERSTAND BYTEOFFSET
PQ57221 EZERT8 NOT SET WHEN EOF OCCURS ON A SEQUETIAL READ
PQ57304 VAGEN V4.5 FP2 - GENERATOR ERROR, WALKBACK HANGS LAN SERVER

Server 4.5 APARs Included in FixPak3

Template APARs Included in FixPak3 
PQ57278 - Import error when acessing Korean DB2 on MVS
PQ57279 - Import of database tables from AS400 does not work.
PQ57281 - Quick Reverse - smalltalk field converter setting is correctly reversed
PQ57282 - Java GUI. Generation Technology. Parameter from property connection not generated properly
PQ57283 - Java GUI. Generation Technology. BeanInfo incomplete  action.actionPerformed(java.awt.event.ActionEvent) is not valid.
PQ57285 - Generator Registry Browser. Sort order of classes does not work
PQ57284 - Generated applications - server: Empty function should use MoveA instead of Move.
Pq57288 - Generated applications - web: FILL UI Function should not reset control-error flag
PQ57287 - Generated applications - Java GUI: Extract and sort criteria not initialized properly (less than, descending)
PQ57290 - Generated applications - Java GUI: Refresh does not reset sort criteria.
PQ57291 - Generated applications - Java GUI: Read Only combo boxes are not disabled properly
PQ57292 - Generated applications - Java GUI: Setting ws GUI letter width to minimum or maximum has no effect
PQ57293 - Generated applications - Java GUI: Busy cursor remains after submit
PQ57294 - Generated applications - Java GUI: Redundant connection to repaint
PQ57295 - Generated applications - Java GUI: Dynamic change of readOnly property not handled properly
PQ57296 - Generated applications - Java GUI: autoResizeMode - java GUI list columns not sized properly
PQ57297 - Java Generation - NLS. Labels should default to english when language is not supported
PQ57299 - Java Generators Launching Business Object Server Generator with server layers = 3-tiers results in generation failed.
PQ57300 - Smalltalk Generators: Concurrency column are using an old API.

FixPak2

FixPak1


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 VisualAge Developer Domain Homepage

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

IBM Corporation Homepage

http://www.ibm.com