IBM VisualAge Generator V4.5 Fix Pack 4 Readme Effective Date: 29 October 2003

This VisualAge Generator V4.5 Fix Pack 4 Readme file contains the installation instructions, product support, and limitation information.

The VisualAge Generator V4.5 fix pack 4 is cumulative and includes the V4.5 changes made for FixPak1, FixPak2 and FixPak3. If you did not already have the V4.5 FixPak1, FixPak2 or FixPak3 installed, you may install the V4.5 fix pack 4 directly. Please note we now use the term 'fix pack' whereas previously we used the term 'FixPak'.

Fix Pack 4

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

• Ongoing Information

  The following information is added to inform users of post fix pack 4 actions which they should be aware of after applying fix pack 4.

  PQ78138 - Documentation Apar Invalid Index keys are now being validated correctly.

  Messages hpt.CM.514.e and hpt.CM.740.e are thrown when trying to validate invalid Index Key's in the "Database PCB Update Box". Validation of VAGenerator 4GL, Validation of PSB and PCB information has been enhanced. This change can result in code that passed validation prior to 17/4/2002 failing with the following messages. Hpt.CM.514.e - PCB is not defined in the called parameter list. Hpt.CM.740.e - Parameter EZEDLPCB is not valid on a call or transfer. These messages can indicate that a data item declared as a PCB Index Key is not found in the program.

• Known Issues

  • When printing a part from the Parts Browser, this Walkback > Runtime error may occur:

    (ExCLDTIndexOutofRange) Index Out of Range.

    A simple workaround is to shut down VAJava and delete a file called printSetup.txt, which is under <installed directory>\ide\program, then restart VAJava. As soon as you print anything from the Parts Browser it will recreate the file. It does mean you will lose any print settings you had saved, but you should be able to continue working as usual after that.

  • Customers who have installed this fix pack 4, and who use web transactions on OS/390 or z/OS or java applications on OS/390 or z/OS, should apply service supplied in APAR PQ75643 to their OS/390 or z/OS system. This provides updated jar files to bring them up to fix pack 4 level.

  • Customers who have installed this fix pack 4, and who use web transactions on i/Series or AS/400 or java applications on i/Series or AS/400, should apply service supplied in APAR SA96178 to their i/Series or AS/400 system. This provides updated jar files to bring them up to fix pack 4 level. This APAR is supplied in PTF SF67742.

  • PQ76524 - Import and export performance problems, large references search on XP giving partial results

    APAR PQ76524 covers the following aspects

    • Import and Export (especially Export with Associates) does not display the busy cursor. This is more noticeable with larger operation requests, and in Export with Associates can result in the user being given no indication that the request is still being processed. This is both confusing to the user and potentially allows them to take actions in the IDE that might conflict with the request being processed.
    • The Import and Export utility (especially Export with Associates) can have performance problems when a large number of parts is being processed. The performance of the Export with Associates (on XP) was observed to be slow in testing.
    • Large References searches carried out on XP were observed to occasionally report partial results. This problem was tested on Windows 2000 and the same problem was not observed.

  • PQ62283 - Documentation APAR for Web Transactions SUBMIT VALUE items

    The VisualAge Generator Web Transaction Development Guide should have the following information added to clarify the behavior of submit value items and the passing of values between UI records:

    Information regarding which push button was clicked on a defined FORM is passed to a receiving UI record, the same as for other user input. You must create data items in the receiving UI Record with the same name as the sending submit data items. Do NOT specify these data items representing the submit buttons on the Link Parameters in the UI properties of the FORM data item. The receiving UI Record must be specified in the UI Properties of the FORM data item. The UI type of the receiving data items could be:

    • SUBMIT: If you do this you must specify on each one a label which matches up with the label of the sending data item. You must also assign it a default value. Then the default value of the receiving data item which corresponds to the sending data item which was clicked is looked up and that default value is set as the actual value of that receiving data item (the submit value item). All the other receiving data items corresponding to other submit buttons will be blank.
    • Anything else, for example HIDDEN or NONE: When control passes to the receiving Web Transaction the LABEL (not the VALUE) of the button you clicked is passed into the corresponding receiving data item. All the other receiving data items which represent the other submit buttons remain blank.

  • PQ68022 - CICS ECI enhancement to support calling CICS from Java applications

    VisualAge Generator for Java and VisualAge Generator Server for Windows are enhanced to enable users to call a CICS program from a Java client using CICS Transaction Gateway (CTG) middleware. The Java client may be either a VisualAge Generator program generated for Java or a Java class, a servlet for example, that uses a generated Java wrapper. Java classes provided by CTG use the CICS ECI to start the program. CICS Transaction Gateway can be configured to use either TCP/IP or APPC to communicate between the Java client and CICS transactions.

    VisualAge Generator Developer is enhanced to allow users to specify in a linkage table entry a TCP/IP address and port for a CICS Transaction Gateway server to be used to communicate with CICS. If a linkage table with such an entry is used when:

    • generating a program for Java that calls a CICS program specified by the entry, or when:
    • generating a Java wrapper for a CICS program specified by the entry

    … code is generated to cause the VisualAge Generator runtime to use CTG middleware to start the called program. Information from the linkage table entry is passed to the CTG middleware so that it can locate the program.

    The VisualAge Generator Client/Server Communication Guide contains documentation for using Java wrappers to call VisualAge Generator programs from a Java class such as a servlet. See Chapter 18 - VisualAge Generator JavaBeans Wrappers and Enterprise Beans. The example for calling a session bean using a program wrapper can be used as a sample for calling a program from a servlet even if not using a session bean. (In this case you just would not need the EJB import java.rmi.RemoteException.)

    To call a CICS program from a Java client using CTG, do the following:

    1. Develop a linkage table containing an entry for the program to be called. The linkage table entry should specify the following attributes:

       linktype=REMOTE
       parmform=COMMPTR, or parmform=COMMDATA	Matching the linkage used when the called program was generated.
       remotecomtype=CICSCLIENT
       contable=CSOE037	Assuming an ASCII client to an EBCDIC server in English.
       location=CICS region
       serverid=transactionID	Defaults to CPMI.
       ctglocation='tcp alias/address'	TCP alias or address of CTG server. Enclose in single quotes if it contains periods.
       ctgport=port	Port on which CTG server is listening.
       luwcontrol=SERVER	Client unit of work is not available in this FixTest.
       remotebind=GENERATION	More efficient as long as program location is fixed. Note: If using remotebind=RUNTIME, save the linkage table part to a file before step 2. Name the file the same as the linkage table. When performing the save, a ".lkg" extension is appended at the end.

    2. Generate the Java wrapper or the VisualAge Generator program calling the CICS program, specifying generation option:

       /linkage=<name of linkage table from step 1>

    3. Decide on how user IDs and passwords for invoking the CICS program are to be handled. Options are:
       • Configure CTG and the invoked transaction so that user ID and password are not required
       • If using a wrapper to make the call, your servlet would gather the necessary user ID and password information and would set the user ID and password in the callOptions variable of the wrapper. See "Specifying a User ID and Password" in the Client/Server Communications Guide for details.
       • If developing a client application instead of using Java classes and wrappers, create a Java properties file named csouidpwd.properties with the following properties specified: CSOUID=user ID CSOPWD=password

       Include this properties file along with the client application in the classpath of the client execution environment.

    4. Deploy the client code to the client execution environment.

       If the client is a servlet using generated wrappers to call the CICS program, you must package the wrapper classes, the VisualAge generator middleware jar file, hpt.jar, and the CTG jar file, ctgclient.jar, in the Web Application .war file. The linkage table file and the csouidpwd.properties files must be at the root of the .war file. This .war file is subsequently packaged in the .ear file used to deploy the client web application to the application server.

       If the client is a generated Java program, the generated classes, VisualAge Generator runtime jar files hpt.jar and vgjwgs.jar, and CTG jar file ctgclient.jar, (and the csouidpwd.properties file if used) must be included in the classpath of the client execution environment.

    VisualAge Generator Support for Web Transactions Using the SSL Protocol

    These instructions are for the scenario where a self-signed certificate is used. You can paste the example statements and test this, since they have been extracted from a working sample.

    1. Create the server keystore and a self-signed certificate.

       keytool is a tool that is supplied by Java. It resides in the <JAVA_HOME>/bin directory.

       Following is an example in which keytool is used to create a server keystore called ServerKeyStore.jks, and a self-signed certificate. In this example the same password is used for both the keystore and the key, and the keystore is stored in a directory called /u/vguser/ctg500/keys. You will need to specify this directory in Step 3, when updating the CTG.INI file. You should create your own directory where you can keep your keys.

       Note: If you don't specify a full path the keystore file is created in the current directory.

       Example:

       This example creates a server keystore that contains a self-signed certificate. You may need to put this example statement in a script file.

       keytool -genkey -alias ServerCertificate -keysize 1024
       -dname "cn=hostname.raleigh.ibm.com,o=IBM,ou=VAGen,l=RTP,s=NC,c=US"
       -keystore ServerKeyStore.jks -storepass storepassword -keypass storepassword
       

       Explanation of the options:

       cn=<any unique name; the host name is sufficiently unique>
       o=<Organization>
       ou=<Organizational Unit>
       l=<Location>
       s=<State>
       c=<Two letter country identifier>
       ServerCertificate can be any alias you like
       ServerKeyStore.jks is the name of the file to be used for your keystore
       

    2. Export the self-signed certificate from the keystore.

       Use the following command to export the certificate from the keystore created above to a file called ServerCertificate.der

       Example:

       keytool -export -alias ServerCertificate -keystore ServerKeyStore.jks
       -file ServerCertificate.der -storepass storepassword
       

       This certificate will be needed later.

    3. Activate the CTG SSL handler on the host.

       Update the /<CTG install directory>/bin/CTG.INI file to add the following entries (which may already exist, but might be commented out).

       The first entry is:

       protocol@ssl.handler=com.ibm.ctg.server.SslHandler
       

       which activates the SSL handler.

    The second entry is:

    protocol@ssl.parameters
    

    which contains parameters that will be used by the SSL handler. The relevant parameters are:

    port:	Port number where the SSL handler will be listening for requests. Keep note of the port number since this will need to be entered into the csogw.properties file on the client. Port number 8050 is the default.
    keyring:	Enter the fully qualified path of the server keystore from Step 1. In our example, this is /u/vguser/ctg500/keys/ServerKeyStore.jks.
    keyringpw:	Enter the keystore password used when creating the server keystore in Step 1. In our example, this is storepassword.

    Example:

    protocol@ssl.handler=com.ibm.ctg.server.SslHandler
    protocol@ssl.parameters=port=8050;sotimeout=1000;connecttimeout=2000;
    idletimeout=600000;pingfrequency=60000;keyring=/u/vguser/ctg500/keys/ServerKeyStore.jks;
    keyringpw=storepassword;clientauth=off;
    

    4. Start CTG on the host.

       Submit the job to start CTG on the host. Check ctg.trc file for a log entry such as this:

       03/25/03 : 12:45:04:739 : CCL6524I: Successfully started handler for the ssl: protocol.
       

       Now that the host is ready to receive requests, we need to prepare the client.

    5. Copy the self-signed certificate to the client.

       From the client, ftp into the host and get the certificate file from the host. In the example, the name of the certificate file was ServerCertificate.der. Make sure to use the binary mode of transfer.

    6. Create the client keystore and import the server’s self-signed certificate.

       Once you have the certificate on the client you must create the client keystore. Below is an example of how to create a client keystore. You can replace ServerCertificate, ClientKeyStore.jks, and storepassword with any name and password you like. The certificate file name should be the same as the name of the certificate file received from the host (ServerCertificate.der in the example).

       Issue the following command to create a client keystore that contains the server’s self-signed certificate.

       Example:

       keytool -import -alias ServerCertificate -file ServerCertificate.der
       -keystore ClientKeyStore.jks -storepass storepassword
       

       When asked:

       Trust this certificate? [no]:
       

       Type yes

       Because ClientKeyStore.jks does not exist, a keystore with this name will be created in the working directory. Remember the full path to the client keystore, as you will need to enter this into csogw.properties in the next step.

    7. Update csogw.properties.

       Update the csogw.properties file by adding the following entries with the client keystore file name and the password for the client keystore

       serverLinkage.<applicationname>.keyring=<path to keystore> serverLinkage.<applicationname>.keyringpassword=<password>

       Example:

       serverLinkage.UITEST.keyring=D:/SSLKeys/ClientKeyStore.jks serverLinkage.UITEST.keyringpassword=storepassword

       Make sure two entries for CTG, serverLinkage.<applicationname>.ctgLocation and serverLinkage.<applicationname>.ctgPort, exist in the properties file. The entry serverLinkage.<applicationname>.ctgPort should be the port number that was entered in the CTG.INI file on the host. If this entry is missing, the port number defaults to 8050 if the serverLinkage.<applicationname>.keyring entry is specified.

    8. Use the new hptgateway.jar file

       Make sure the new version of hptgateway.jar file is in the classpath at deployment.

    9. Use ctgclient.jar file that is distributed with CICS Transaction Gateway V5.0

       Make sure that ctgclient.jar is in the classpath at deployment.

  • PQ76667 - HANG ON CICS SCREEN USING VAGEN C++ AIX 5.1 RUNTIME

    If hangs are experienced during the converse of CICS maps on the VAGen AIX 5.1 runtime, add the following line into the environment file for your CICS region:

    MALLOCTYPE=buckets

    Your CICS region will need to be stopped and started for the change to take effect.

  FixPak3

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

  Known Issues

  • If any comments contain an invalid host variable, the parser will attempt to validate it.  To avoid this, do not place any invalid host variables in any comments.
  • EFKSND.REX Modifications:

            The EFKSND Rexx command file has been modified to support calling the userid/password exit if the developer did not specify the TCP/IP userid and password as generation options.

            If you have made modifications to efksnd.rex and do not want to use this new function, you may continue to use your modified copy of efksnd.rex. Otherwise you will need to add your modifications to the new version of efksnd.rex.

  • APAR PQ48221: In the syntax diagram on page 428 of the Programmer's Reference, UI record should be replaced with UI record item.
  • On page 52 of the Server Guide for Workstation Platforms, the first paragraph of "Calling 3GL Programs from a VisualAge Generator C++ Program" is incorrect.  Sentence 3 should read: "The 3GL program must be linked as a DLL and must return an integer return code, as shown  in the sample below."  The sample called program on pages 52-53 is incorrect. It should read as follows:

    /********************************************************************/

  
  /*Sample program that is called from a VG program.Character */
  /*and binary parameters are passed.A binary parameter must be returned.*/
  /********************************************************************/
  #include <stdio.h>
  extern int _System NVGAPP(char*buffer,int*len,int*rc);
  extern int _System NVGAPP(char*buffer,int*len,int*rc)
  {
  printf("Parm1 =%s \n",buffer);
  printf("Parm2 =%ld \n",*len);
  printf("Parm3 =%ld \n",*rc);
  *rc =99;
  return(0);
  }
  • APAR PQ52353: On page 385 of the Programmer's Reference, add these sentences below the table: "IF and WHILE are reserved words and cannot be used as part names. COBOL reserved words cannot be used as part names when generating for COBOL."
  • APAR PQ51125: On page 228 of the Migration Guide, the last bulleted paragraph is incorrect. It should read: "The visual table part from the Data Entry category on the parts palette is now obsolete. The visual table part is not migrated by VisualAge Generator and no longer appears on the parts palette. To migrate these tables, follow the VisualAge Smalltalk migration path. For new views, use the Container Details part, which provides function similar to the visual table part."
  • APAR PQ54104: In the Programmer's Reference, add the following text to the definition considerations for IF (page 432) and the "Uses" section for WHILE (page 464):
  
          Due to Smalltalk's algorithm for sorting strings, the results of string comparison operations may be inconsistent with regard to case-sensitivity. String comparison results in ITF may differ from those in runtime environments.
  • The following messages are added to Message and Problem Determination Guide:
              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.

  • APAR PQ48489: A new version of Appendix B from the Generation Guide was created to address this. View the new Appendix B by clicking here.
  • When testing a web transaction and hitting the SUBMIT BYPASS key, if the UI record does not have a SUBMIT VALUE ITEM specified, an error will occur.  Work around this by specify a SUBMIT VALUE ITEM for the UI Record.

  General Improvement

  • PQ51940 - Print listing will now have line number for each function statement and cross references with line numbers in program structure.
  • Verify compatibility with Windows/XP
  • Generation of Java for OS/390, OS/400, all Linux platforms
  • Provide "find" function in table content editor
  • Print listing will now have line number for each function statement and cross references with line numbers in program structure.
  • ITF: Initialize EZEUSR and EZELTERM
  • Support Linux/xSeries as a Web Application Server for VAG web transactions (Red Hat & SuSe distributions)
  • Support use of VAG with WebSphere Application Server 4.0 and VA Java 4.0
  • Provide new APIs for users who want to modify their VA Java-based VAG repositories
  • Improve the performance of generated programs on Windows NT, AIX, and Solaris servers (9x on WinNT)
  • Support FORMFD=NO on CICS AIX
  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:

  • Perform customer specific authorization of users running transactions
  • Log information about the transaction
  • Pass additional information beyond the UIR between the servlet and host system.

  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:

  • Access a buffer areafor the exit to add data and send it to host systems running CICS or IMS
  • Access UI Record bean,HttpServletRequest, connectionID, sessionID and userid information
  • Set an error returncode and message.

  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:

  \VGWGS45\

          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:

  • Perform authentication immediately after a user logs on, instead of the first time the user invokes a Web transaction.
  • Provide more useful feedback to the user when authentication fails.
  • Bypass the logon page and make the Web transactions available to all users, even if your tier 3 server requires a user ID and password.
  For a detailed explanation of this enhancement, please visit: http://www.ibm.com/software/awdtools/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 fix pack 4 of VAGen.

  • Support for Relational Database Access via the JDBC Interface

    With this fixpak, VisualAge Generator supports accessing relational database access via the JDBC interface for the following systems: LINUX, AIX, OS/400 and OS/390.

  • Support for Sequential File Access and MQ File Access

    The official support for Sequential file access and MQ file access will be available in the next fixpak of VAGen. At which time, you will be able to generate programs that access MQ files for the following systems: WINNT and AIX. You will also be able to generate programs accessing Sequential files for these systems: LINUX, AIX, OS/400 and OS/390.

    If you are generating programs that mixes relational database calls with sequential file access, VAGen prevents you from generating the programs and ends with an error message indicating that sequential file access is not supported. Until the official support is delivered in the next fixpak, you can bypass this restriction by generating and compiling the java code on a Windows system. Then, use the java "JAR" command to assemble the class files for transport and ftp the jar file to the target system.

  Preparing to Run Java Programs on the Target System:

  • Ensure you have the minimum software requirements for executing the generated java server program on the target system. For information on software requirements, refer to the respective VisualAge Generator Server platform at: http://www-3.ibm.com/software/ad/visgen/about/preqms03.htm
  • If you are targeting Linux/Intel or Linux/390 as the server system, at least one VisualAge Generator Server for AIX license is required to access the VisualAge Generator runtime jar files. These jar files can then be uploaded to the Linux system.
  • Use chapters 11-14 of the VisualAge Generator Server Guide for Workstation Platforms as a guide. Although these chapters refer to the Windows system, it contains relevant information on setting up and running Java Server programs (ie. vgj.properties, etc) for the other target system.
  • Before compiling and executing the java generated program, make sure the CLASSPATH points to VisualAge Generator runtime jar files and to any other required jar files, such as the java runtime jar file. For example,

  export CLASSPATH=$CLASSPATH:$JAVA_HOME/jre/lib/rt.jar
  export CLASSPATH=$CLASSPATH:/home/vagen/vg45/hpt.jar
  export CLASSPATH=$CLASSPATH:/home/vagen/vg45/hptGateway.jar
  export CLASSPATH=$CLASSPATH:/home/vagen/vg45/vgjwgs.jar
  export CLASSPATH=$CLASSPATH:/home/vagen

  • For VAGen Web Transactions, make sure the HPTCLASSDIR and HPTJSPDIR environment variables are set before generating and compiling your Web transaction UI records. For instance these were the environment variables that were used for targeting WebSphere Application Server 4.0 installation.

  export HPTCLASSDIR=/home/vagen/WEB-INF/classes
  export HPTJSPDIR=/home/vagen/WEB-INF

  • When generating Java server programs for Web Transactions (tier 3), VisualAge Generator has three new options for the "/SYSTEM" generation option: JAVALINUX, JAVAOS390 and JAVAOS400. Here is an example of a batch command file that was used to generate a VAGen web transaction to a Linux WebSphere Application Server 4.0 (tier2) and to a Linux Java Server program (tier 3)

  HPTCMD GENERATE MINTEST /GENOUT=e:\genout45\webtran\javalinux /JAVASYSTEM=LINUX /JAVADESTDIR='/home/vguser/genout/vg45fp3/web' /JAVADESTPASSWORD=vguser /JAVADESTUID=vguser /JAVADESTHOST=ctflin03.raleigh.ibm.com /SYSTEM=JAVALINUX /DESTDIR='/home/vguser/genout/vg45fp3/server' /DESTPASSWORD=vguser /DESTUID=vguser /DESTHOST=ctflin03.raleigh.ibm.com /PACKAGENAME=my.pkg /NOUNLOAD

  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 transactions the WebSphere way' at:

   http://www.ibm.com/software/awdtools/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 of WebSphere 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

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

  Linux/390 Tier 2 Gateway Support

  • VisualAge Generator now supports LINUX for S/390 as a tier 2 for web transactions if the tier 3 is CICS for MVS/ESA. To make the new LINUX for S/390 functionality available, ask IBM support to provide the PTF that is referenced by APAR PQ48463.
  • In addition to following the directions specified in that PTF, you must configure WebSphere Application Server and start the Session ID Manager.
  
  To set up WebShere Application Server on LINUX for S/390, access edition 3 of the Web Transaction Development Guide, chapter 7 ("Running a Web Transaction in WebSphere Application Server"). The document is available from this web site:

  http://www.ibm.com/software/awdtools/visgen/library/v45docs.html

  Follow the procedure stated in chapter 7, with the following changes for LINUX:

  a. The section titled "Define an application server, servlet engine, and web application to WAS" includes 16 steps. In step 12, if you are using a war file, you are directed to click "Finish" and to continue your deployment process at "Use a web application archive (war) file". However, on LINUX, the "Finish" box at step 12 is greyed out. You must continue through step 16, then go to the topology tree and delete the web application ("practice_app", for example). You can use a right mouse button on the application name and click "Remove".

  b. Under the heading "Complete the deployment" are six steps. At the end of step 2, you are directed to click Next. On LINUX, that click does NOT take you to the frame mentioned in step 3. In between, you are on the "Application Resources"
  frame. On that frame, select "default_host", click Next, and then you will be at the frame mentioned in step 3.

  The mechanism for starting the Session ID Manager is also defined in Chapter 7 of the VisualAge Generator Web Transaction Development Guide, in the section "Running a web transaction in WAS," subsection "Start the Session ID Manager." Follow the directions for Solaris.

  ---

  FixPak1

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

  Java Performance Improvements

  • A number of enhancements have been made to VAGen Developer on Java resulting in substantial performance improvements in a number of areas.  In general, reading VAGen parts from the library will be faster.  Performance has also been improved in the following specific areas:
  
  - Opening a program in the Program Editor
  - Expanding the Program Editor structure diagram and specifications nodes
  - Open a record or table containing many shared data items
  - Loading a program in the Test Facility and running it for the first time

  VAGen Java API updates

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

  
  

  ---

  VisualAge Generator Templates

  Product Enhancements

  VisualAge Generator V4.5 fix pack 4 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

  • New Naming Policy of the items in the UI-Record
  
  The generated item names are more easy to read and take into account muliple displays in one single interface unit.
  • New Hooks
  
  Several new hooks are available in the web transaction to customize the initialization of the program, the server calls and the display.
  • Concurrency management (timestamp or counter) is available in XFER & Converse.

  
  Fixpak 2
  Enhancement of the browsers

  • Data Element, Value Table editing. The tabbing between the cells works correctly
  • package and project names in the parameters editors are larger and fully visible
  • Relational Import: Temporary Tables (DB2/MVS) can now be imported
  Generated Web Client
  • Error Handling is improved.
  • Value table management is improved. No duplicate of the current value.
  • Help List display is improved. The current item position in the list is preserved.
  • Column Labels are used in lists instead of default labels
  • Access Level is taken into account in the lists. The definition of the UI-Record is thus optimized (less fields)
  Generated Java GUI Client
  • The last page of the Help List is always accessible (sometimes, the next button was grayed too soon)
  • Naming of the Java Classes: Naming Policy & layout suffix parameters are taken into account.
  Generation
  • Generation of 4GL components is faster.
  • Display Names of the GUI generators is clarified (they are called GUI instead of Java)
  • Display Names of the Generators in an unsupported Locale : The english display name is used, instead of the class name.
  Fixpak 3

  Generated Java GUI Application

  • Extract and sort criteria in list are initialized properly for all sort and extraction criteria (less than, descending). Refresh does not reset the sort criteria.
  • Letter width parameter is taken into account
  • Read-only combo boxes behave correctly
  Generated Smalltalk application
  • Concurrency management is handled correctly

  Limitations and Known Problems with VAGT

  • Common Limitations
  • VAGT Workbench:
  • SQL low value and SQL high value (Workspace definition) are not exhaustively checked; these attributes should not be empty (space is a valid value).
  • Web Generators:
  • You may have to customize the code if you use more than one business object in one interface unit. Various hooks are available.
  • The updatable lists are not available.
  • GUI Generators:
  •  The '4GL' Client Logic Style (Workspace Parameter) is not implemented.
  • Templates on Java Limitations
  • GUI Generators:
  • On VisualAge for Java, you need to check 'Inherit BeanInfo of Bean superclass' in the panel 'Options', under 'Visual Composition' to have your generated GUI work properly.
  • Relational Table: The 'read' concurrency management is not supported by the client.
  • Templates on Smalltalk Limitations
  • Installation:
  
  After the load of the VAGT feature, the VisualAge Organizer may have lost the current user. Ensure to set a current user before using the VAGT feature (otherwise the menu items of the VAGT Tools menu will stay disabled).
  • Generation:
  • If you use a workspace that was not defined with the QuickStart, it is better to unload MdlQSRuntimeApp.
  • Workspace: 'Target Services Application' and  'Target Visual Application'  parameters are not taken into account. Only 'Target Logic Application' is used.
  • Bidi:
  
  Although VAGT is able to provide right-to-left organized views and subviews, it depends on the abilities of VisualAge Smalltalk BiDi feature for internal positionings:
  • menus inside a menu bar
  • columns inside a container
  • tabs inside a notebook
  • Database Management:
  
  When connecting to the database, you may have database connections  left open (an error -1445 appears), you should clean up SQL database connections so you can execute the following code to clean up the SQL interface:SQLRequester disconnectAll

  Note:

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

  Fix Pack 4 Service Supplied

  See Templates APARS Included in Fix Pack 4

  ---

  
  

  VisualAge Generator 4.5 Fix Pack 4 Installation Notes

  ---

  Important Information

  Installing VisualAge Generator Developer on VA Java

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

  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 fix pack 4, 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.

  Installing VisualAge Generator Developer on VA Java

  • Follow these instructions if you DO NOT have VisualAge for Java currently installed.
  • First install VisualAge for Java 3.5.3 or 4.0 depends on your needs.
  • Make a connection to the FTP site at ftp://ftp.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files InstallOnVAJava353_40.exe, RemoveJava35key.exe and those of fix pack 4 are located in the directory   ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/windows. You may perform an anonymous logon to this FTP site.
  • Download InstallOnVAJava353_40.exe, RemoveJava35key.exe and fix pack 4 files from the FTP site to the machine where you will be installing VisualAge Generator 4.5 on Java.
  • Run InstallOnVAJava353_40.exe. You should not receive any message.
  • Install VisualAge Generator Developer for Java 4.5 and VisualAge Generator Common Services 4.5 when prompted.
  • You may also install VisualAge Generator Server 4.5 at this time, if required for your installation.
  • To install fix pack 4:
  • Install Common Services fix pack 4 by running CSONT45FP4.exe; when asked if want to overwrite files, type "a" to continue.
  • Install Server fix pack 4 by running ServerNT45FP4.exe; when asked if want to overwrite files, type "a" to continue.
  • Install VAGen V4.5 fix pack 4 by running DevJavaNT45FP4.exe; when asked if want to overwrite files, type "a" to continue.
  • Start VisualAge Generator Developer on Java, and load VAGen 4.5 + FP4 features. Do this by select File -> Quick Start. Select Features on the left panel, and double click Add Feature on the right panel.
  • Add all features with + FP4 appended to it. Or only add the features you wish.
  • Run RemoveJava35key.exe now.  You should not receive any messages.
  • Follow these instructions if you currently have VisualAge Generator 4.5 AND VAJava 3.5.3 or VAJava 4.0 installed on your machine and wish to keep that configuration.
  • Silent Install.
  • Silent install is designed to simplify installation of fix pack 4 for VisualAge Generator 4.5.
  • ***Important***
    • Version and Release all projects/packages currently loaded in your workspace
    • Shutdown VA Java
  • Create a temporary directory (i.e. c:\vg45fp4)
  • Download the following from the FTP site into the temporary directory
  • DevJavaNT45FP4.exe -- Generator Developer
  • CSONT45FP4.exe -- Common Services
  • ServerNT45FP4.exe -- Generator Server
  • ide.icx -- Clean image file
  • instvgfp.cmd -- Silent Install Command File
  • InstallOnVAJava353_40.exe
  • RemoveJava35key.exe
  • Run instvgfp.cmd to install fix pack 4:
    instvgfp <directory for VAJava> <temporary directory>
    For example:

    instvgfp c:\IBMJava c:\vg45fp4

    If the installation was successful this message will be displayed:

    "fix pack 4 installation completed"

  • The instvgfp command automatically backs up the following files to the VagenFP4 temporary directory before installing fix pack 4:
  • ide.icx
  • ide.ini
  • hpt.ini
  • features.sav
  • projects.sav

  The name of the temporary directory is created by appending VAGenFP4 to the contents of the TEMP variable. If the TEMP variable is not set the directory C:\TEMP\VAGenFP4 is used.

  • Clean Reinstall

  • Backup your workspace or make sure it's in a safe place.
  • Uninstall IBM VisualAge Generator Common Service, IBM VisualAge Generator Server, IBM VisualAge Generator Developer on Java and then VisualAge for Java in this order.
  • Make a connection to the FTP site at ftp://ftp.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files InstallOnVAJava353_40.exe, RemoveJava35key.exe and those of fix pack 4 are located in the directory   ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/windows. You may perform an anonymous logon to this FTP site.
  • Download InstallOnVAJava353_40.exe, RemoveJava35key.exe and fix pack 4 files from the FTP site to the machine where you will be installing VisualAge Generator 4.5 on Java.
  • Run RemoveJava35key.exe.  You should not receive any messages.
  • Restart the computer.  Then go to the directories where these programs are installed and physically remove these directories.
  • Now follow the instructions for a New Install: Installing VisualAge Generator Developer on VA Java

  • Follow these instructions if you had installed VisualAge Generator 4.5 AND VAJava 3.5.3 on your machine and now wish to use VisualAge for Java 4.0.
  • Backup your workspace or make sure it's in a safe place.
  • Follow instructions on how to upgrade from VisualAge Java 3.5.3 to VisualAge Java 4.0
  • Make a connection to the FTP site at ftp://ftp.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files InstallOnVAJava353_40.exe, RemoveJava35key.exe and those of fix pack 4 are located in the directory   ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/windows. You may perform an anonymous logon to this FTP site.
  • Download InstallOnVAJava353_40.exe, RemoveJava35key.exe and fix pack 4 files from the FTP site to the machine where you will be installing VisualAge Generator 4.5 on Java.
  • Run InstallOnVAJava353_40.exe. You should not receive any message.
  • Install VisualAge Generator Developer for Java 4.5 and VisualAge Generator Common Services 4.5 when prompted.
  • You may also install VisualAge Generator Server 4.5 at this time, if required for your installation.
  • To install fix pack 4:
  • Install Common Services fix pack 4 by running CSONT45FP4.exe; when asked if want to overwrite files, type "a" to continue.
  • Install Server fix pack 4 by running ServerNT45FP4.exe; when asked if want to overwrite files, type "a" to continue.
  • Install VAGen V4.5 fix pack 4 by running DevJavaNT45FP4.exe; when asked if want to overwrite files, type "a" to continue.
  • Start VisualAge Generator Developer on Java, and load VAGen 4.5 + FP4 features. Do this by select File -> Quick Start. Select Features on the left panel, and double click Add Feature on the right panel.
  • Add all features with + FP4 appended to it. Or only add the features you wish.
  • Run RemoveJava35key.exe now.  You should not receive any messages.
  • Follow these instructions if you have VisualAge for Java 3.5 or VisualAge for Java 3.5.2 and VisualAge Generator Developer on Java 4.5 installed and you wish to upgrade to VisualAge for Java 3.5.3.
  • Upgrade your VisualAge for Java 3.5 or 3.5.2 to 3.5.3. Instruction for this procedure should be with the Upgrade package.
  • Installation of VisualAge for Java 3.5.3. It will post a warning about migration during the install. If you have followed the VisualAge for Java 3.5.3 migration instructions, click "Yes". Otherwise, click "No".
  • Let VisualAge for Java 3.5.3 install and migrate automatically. When installing, the repository server and directories should be the same as that for your VisualAge for Java 3.5.
  • Make a connection to the FTP site at ftp://ftp.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files InstallOnVAJava353_40.exe, RemoveJava35key.exe and those of fix pack 4 are located in the directory  ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/windows. You may perform an anonymous logon to this FTP site.
  • Download InstallOnVAJava353_40.exe, RemoveJava35key.exe and fix pack 4 files from the FTP site to the machine where you will be installing VisualAge Generator 4.5 on Java.
  • Run InstallOnVAJava353_40.exe. You should not receive any message.
  • Install VisualAge Generator 4.5, VisualAge CSO, and VisualAge Server.
  • Install fix pack 4:
  • Install Common Services fix pack 4 by running CSONT45FP4.exe; when asked if want to overwrite files, type "a" to continue.
  • Install Server fix pack 4 by running ServerNT45FP4.exe; when asked if want to overwrite files, type "a" to continue.
  • Install VAGen V4.5 fix pack 4 by running DevJavaNT45FP4.exe; when asked if want to overwrite files, type "a" to continue.
  • Start VisualAge Generator Developer on Java, and load VAGen 4.5 + FP4 features. Do this by select File -> Quick Start. Select Features on the left panel, and double click Add Feature on the right panel.
  • Add all features with + FP4 appended to it. Or only add the features you wish.
  • Run RemoveJava35key.exe now; you will not receive any message.

  Installing VisualAge Generator Developer on VA Smalltalk

  • For Windows NT
  • Download DEVSTNT45FP4.EXE from the FTP site and run it. During the install, if prompted to overwrite existing files, please type "y" or "a". The address of the FTP site is ftp://ftp.software.ibm.com. This site contains information and fixes for a wide variety of other IBM products. The files for fix pack 4 are located in the directory ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/windows. You may perform an anonymous logon to this FTP site.
  • Fix pack 4 for Common Services V4.5 is a prerequisite for running Developer with fix pack 4. If you have not installed fix pack 4 for Common Services yet, you must download CSONT45FP4.EXE from the FTP site and run it. Read Installing VisualAge Generator Common Services section for details.
  • After you install fix pack 4 for VisualAge Generator Developer on Smalltalk V4.5, you need to load the fix pack 4 features by performing the following customization tasks:
  1. Start VisualAge for Smalltalk.
  2. Select Tools --> Load/Unload Features... on the System Transcript window.
  3. On the Selection Required window, do the following:
  4. Ensure that the Show other features check box is checked.
  5. Select the features with FP4 suffix from the Available features list. If you want to update other features included in fix pack 4, please select them as well.
  6. Click on the >> button to move the feature to the Loaded features list. If you selected other features, they will be moved as well.
  7. Click on the OK button. The selected features will be imported and loaded into your image.
  8. Once the selected features are loaded, you will be prompted to save your image. Press the Yes button. After the image is saved, you might want to make a copy of the image file just in case you need it later.

  Note: There is a known issue with the Load / Unload Features window:

  In the right-hand pane under Loaded features, the following feature may already be shown as loaded, even if it has not explicitly been loaded, or it has been replaced with the FP4 feature:

  Other: VAGen GUI Settings – FixPak3

  This is a cosmetic error only and can be ignored. However, it is important that you do not try to select and remove this feature, as a debugger or walkback window may appear.

  Installing VisualAge Generator Server

  • For Windows NT
  • It is strongly recommended that you either:
    • back up your entire Server directory ..\VGWGS45\, or
    • back up the following files from this ..\VGWGS45\ directory, as they may contain modified data that may be needed to be retained:

      csogw.properties
      gw.properties

  • Download ServerNT45FP4.exe from the FTP site, and run it. The address of the FTP site is ftp://ftp.software.ibm.com.  This site contains information and fixes for a wide variety of other IBM products.  The files for fix pack 4 are located in the directory ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/windows. You may perform an anonymous logon to this FTP site.
  • Fix pack 4 for Common Services V4.5 is a prerequisite for running Server with fix pack 4. If you have not installed fix pack 4 for Common Services yet, you need to download CSONT45FP4.EXE from the FTP site and run it. Read Installing VisualAge Generator Common Services section for details.
  • You can now restore the csogw.properties and gw.properties files if required.
  
  
  • For AIX 4.3
  • To install:
  1. Login to your AIX machine and create a directory named vgfixes (i.e. /home/user1/vgfixes).
  2. Change to that directory.
  3. Download the appropriate install image from the FTP site. The files for fix pack 4 are located in the directory ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/aix.
  • vgaix45.fp04 for systems that do NOT have CICS installed.
  • vgaix45t.fp04 for systems that DO have CICS installed.
  4. SU to root.
  5. Remove the previous version of VisualAge Generator Server with the following command:
  • installp -u vgwgs45.obj
  6. Whenever you remove VisualAge Generator Server for AIX from your system to install a fix pack and you also have an NLS image installed, you must do the following:
  • Remove the NLS image
  • Install the base fix pack image
  • Re-install the NLS image. Instructions for removing and installing an NLS image are documented in the VisualAge Generator Installation Guide.
  7. Install fix pack 4 using the appropriate command:
  • installp -ad vgaix45.fp04 all   (non-CICS systems)
  • installp -ad vgaix45t.fp04 all   (CICS systems)
  Note: The Common Services component is automatically installed when you install the Server component on AIX.
  
  
  • For AIX 5.1
  • To install:
  1. Login to your AIX machine and create a directory named vgfixes (i.e. /home/user1/vgfixes).
  2. Change to that directory.
  3. Download the appropriate install image from the FTP site. The files for fix pack 4 are located in the directory ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/aix.
  • vgaix545.fp04 for systems that do NOT have CICS installed.
  • vgaix545t.fp04 for systems that DO have CICS installed.
  4. SU to root.
  5. Remove the previous version of VisualAge Generator Server with the following command:
  • installp -u vgwgs45.obj
  6. Whenever you remove VisualAge Generator Server for AIX from your system to install a fix pack and you also have an NLS image installed, you must do the following:
  • Remove the NLS image
  • Install the base fix pack image
  • Re-install the NLS image. Instructions for removing and installing an NLS image are documented in the VisualAge Generator Installation Guide.
  7. Install fix pack 4 using the appropriate command:
  • installp -ad vgaix545.fp04 all   (non-CICS systems)
  • installp -ad vgaix545t.fp04 all   (CICS systems)
  Note: The Common Services component is automatically installed when you install the Server component on AIX.
  
  
  • For Solaris (versions before Solaris 2.8)
  • To install:
  1. Login to your Solaris machine and create a directory named vgfixes (i.e. /home/user1/vgfixes).
  2. Change to that directory.
  3. Download the install image from the FTP site.The files for fix pack 4 are located in the directory ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/sun.
  • vgsol45.fp4.tar
  4. SU to root.
  5. Change your current working directory to /opt.
  6. Whenever you remove VisualAge Generator Server for Solaris from your system to install a fix pack and you also have an NLS image installed, you must do the following:
  • Install the base fix pack image
  • Re-install the NLS image. Instructions for installing an NLS image are documented in the VisualAge Generator Installation Guide.
  7. Remove the previous version of VisualAge Generator Server for Solaris with the following command:
  • rm -rf /opt/vgwgs45
  8. Install fix pack 4 using the following command:
  • tar -xvf /home/user1/vgfixes/vgsol45.fp4.tar
  Note: The Common Services component is automatically installed when you install the Server component on Solaris.
  
  
  • For Solaris 2.8
  • To install:
  1. Login to your Solaris machine and create a directory named vgfixes (i.e. /home/user1/vgfixes).
  2. Change to that directory.
  3. Download the install image from the FTP site.The files for fix pack 4 are located in the directory ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/sun.
  • vgsol845.fp4.tar
  4. SU to root.
  5. Change your current working directory to /opt.
  6. Whenever you remove VisualAge Generator Server for Solaris from your system to install a fix pack and you also have an NLS image installed, you must do the following:
  • Install the base fix pack image
  • Re-install the NLS image. Instructions for installing an NLS image are documented in the VisualAge Generator Installation Guide.
  7. Remove the previous version of VisualAge Generator Server for Solaris with the following command:
  • rm -rf /opt/vgwgs45
  8. Install fix pack 4 using the following command:
  • tar -xvf /home/user1/vgfixes/vgsol845.fp4.tar
  Note: The Common Services component is automatically installed when you install the Server component on Solaris.

  Installing VisualAge Generator Common Services

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

  • For Windows NT
  • Download CSONT45FP4.EXE from the FTP site, and run it. The address of the FTP site is ftp://ftp.software.ibm.com.  This site contains information and fixes for a wide variety of other IBM products.  The files for fix pack 4 are located in the directory ftp://ftp.software.ibm.com/ps/products/visualagegen/fixes/v4.5/FixPack4/windows. You may perform an anonymous logon to this FTP site.

  ---

  Installation Troubleshooting

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

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

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

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

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

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

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

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

  • Problems installing fix pack 4 on VisualAge Generator Developer on VA Smalltalk:

    If the following error message or a similar message is displayed during the FP4 installation, it may be necessary to load FP4 on top of a V4.5 Base with a clean image:

    Error: 356

    Cannot complete the load because the source is missing for ITFGuiTestFacility>>#testComplete and it must be compiled.

    Please take the following steps:

    1. Version any open editions or scratch editions you want kept, then rename your existing abt.icx image file (located in C:\Vast\image drive and path on a typical installation).
    2. From the C:\Vast\newimage\ directory, copy the clean image abt.icx to the C:\Vast\image (or wherever your abt.icx image file normally resides).
    3. Restart VA Generator, select Load / Unload Features from the Tools drop-down list in the System Transcript, ensuring that the Show Other Features check box is selected, and select the Other: VAGen 45 features from the left-hand pane (there should be three of them: Developer, GUI Settings, and Partitioning Support). These are the V4.5 Base features, and they must be loaded before installing FP4 on a clean image. Move these to the right-hand pane and click OK to perform the load.
    4. Once these features are successfully loaded, select Load / Unload Features from the Tools drop-down list in the System Transcript, ensuring that the Show Other Features check box is selected.

    Note: At this point you will notice that the right-hand pane shows Other: VAGen GUI Settings – FixPak3 and Fix Pack 4 as being loaded. This is a known issue and will not cause any errors or problems, and thus can be ignored. However, it is important to note that you should not attempt to remove either of these features, as they have other dependencies that require them to remain loaded. Attempting to remove them may cause a debugger window or walkback to occur.

    5. Select the features with FP4 suffix from the Available Features list. As stated in the above point, Other: VAGen GUI Settings – Fix Pack 4 has already been loaded. If you want to update other features included in fix pack 4, select those as well. Move your selections to the right-hand pane and click OK to perform the load.
    6. Once these features are successfully loaded you will be prompted to save your image, Click the Yes button. After the image is saved you might want to make a backup copy of the abt.icx image file in case you need it later.
    7. Note also that you must reload your development applications from the manager once you have completed the above steps. This can be done from the Applications pane of the Organizer window, or the Applications drop-down list. Load >> Available Applications…
  
  

  ---

  
  

  VisualAge Generator Templates Installation Notes

  ---

  VisualAge Generator Templates Installation

  VisualAge Generator Templates (Standard Functions) is installed with VisualAge Generator Developer.
  • Adding the VisualAge Generator Templates feature on Java:If you already have VAGT 'standard' feature loaded (4.5 or 4.5 Fixpak 1), then you should install an empty image. You can find an original ide.icx in the VisualAge for Java CD, in ivj353\backup directory.
  
  The IBM VisualAge Generator feature is a prerequisite of VisualAge Generator Templates. If it is not already loaded, loading The VAGT standard feature will also load the IBM VisualAge Generator feature.
  1. On the Workbench, select File>>Quick Start.
  2. On the Quick Start dialog, select Features on the left. Add Feature on the right, and then select OK.
  3. Select IBM VisualAge Generator Templates 4.5 + FP4, and select OK (this will take a few minutes).
  4. Close the Workbench, and, then, close the Log. You will be prompted to save the workspace. Select OK to save the workspace.
  • Loading the VisualAge Generator Templates feature on Smalltalk:
  1. Before starting the workspace, you should consider saving a copy of the VisualAge Smalltalk image named abt.icx.
  2. Start VisualAge for Smalltalk.
  3. Select Tools>>Load/Unload Features... on the System Transcript.
  4. In the Selection Required window:
  1. Make sure that "Show other features" is checked.
  2. Select Other: VAGTemplates 4.5 + FP4 from the Available features list.
  3. Click on the OK button. VisualAge Generator Templates will be imported and loaded into your workspace. The load function will also ensure loading of the prerequisites, VisualAge ODBC Database and DB2 CLI Database. This could take up to half an hour to finish.
  
  Once VisualAge Generator Templates is loaded, you will be prompted to save your image. Click the Yes button so you won't have to load VisualAge Generator Templates the next time you start VisualAge for Smalltalk. By default, the image is saved as filename abt.icx. After the image is saved, you might consider making a copy of the image file.

  VisualAge Generator Templates Customizer Installation

  Hardware/Software Requirements

  VisualAge Generator Templates Customizer Version 4.5 fix pack 4 requires the following software and hardware:

  • To install VisualAge Generator Templates Customizer on Java : VisualAge Generator Developer 4.5 fix pack 4 on Java.

  • Software and hardware that are required by VisualAge Generator Developer V4.5 fix pack 4.

  Note: VisualAge Generator Templates Customizer 4.5 fix pack 4 will not install if VisualAge Generator Templates Customizer 4.5 has not been installed previously on the machine.
  

  ---

  Installing VisualAge Generator Templates Customizer on Java

  ---

  To download from FTP site:

  ---

  1. Create a temporary directory on your hard drive.

  2. Download the self-extracting executable MDL45V4N.EXE to a temporary directory on your hard drive.

  3. Extract the files contained in the self-extracting EXE file to the same temporary directory

  ---

  
  To install VisualAge Generator Templates Customizer on Java:

  1. Set the current directory to the temporary directory you created to store the FixPak files.

  2. Run 'setup'.

  3. When prompted, select VAGT Customizer on Java.

  4. Once Customizer has been installed, reboot.

  5. From the Start menu, select Programs, then select IBM VisualAge for Java for Windows, and then select IBM VisualAge for Java to bring up the product.

  6. For Workspace owner, select Administrator, and then specify your network name.

  
  Installing the VisualAge Generator Templates Customizer feature: You should load the VAGT Customizer feature in a Java workspace that does not contain VAGT 'standard' feature. If you already have VAGT 'standard' feature loaded, then you should unload the feature or install an empty image. You can find an original ide.icx in the VisualAge For Java CD, in ivj353\backup directory.

  1. On the Workbench, select File>>Quick Start.

  2. On the Quick Start dialog, select Features on the left. Add Feature on the right, and then select OK.

  3. Select IBM VisualAge Generator Templates Customizer 4.5 + FP4, and select OK (this will take a few minutes).

  4. Close the Workbench, and, then, close the Log. You will be prompted to save the workspace. Select OK to save the workspace.

  ---

  Installing VisualAge Generator Templates Customizer on Smalltalk

  To download from FTP site:

  • Create a temporary directory on your hard drive.

  • Download the following self-extracting executable to a temporary directory on your hard drive:

    1. for OS/2: MDL45V42.EXE

    2. for Windows/NT: MDL45V4N.EXE

    The address of the FTP site is ftp://ftp.software.ibm.com.  This site contains information and fixes for a wide variety of other IBM products.  The files for this fix pack are located in the directory /ps/products/visualagegen/fixes/v4.5/FixPack4/vagtcustomizer. You may perform an anonymous logon to this FTP site.

  • Extract the files contained in the self-extracting EXE file to the same temporary directory.

  To install VisualAge Generator Templates Customizer on Smalltalk:

  • Set the current directory to the temporary directory you created to store the fix pack files.

  • Run 'setup' (for Windows/NT) or 'install' (for OS/2).

  • When prompted, select VAGT Customizer on Smalltalk.

  • Once Customizer has been installed, reboot.

  To load the VisualAge Generator Templates Customizer features after installing VisualAge Generator Developer on Smalltalk:

  • Before starting the workspace, you should consider saving a copy of the VisualAge for Smalltalk image named abt.icx.

  • Start VisualAge for Smalltalk.

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

  • In the Selection Required window:

    1. Make sure that "Show other features" is checked.

    2. Select Other: VAGTemplates Customizer 45 - Fixpak 4 from the Available features list.

    3. Click on the OK button. VisualAge Generator Templates Customizer will be imported and loaded into your workspace. The load function will also ensure loading of the prerequisites, VisualAge ODBC Database and DB2 CLI Database. This could take up to half an hour to finish.

    4. Once VisualAge Generator Templates Customizer is loaded, you will be prompted to save your image. Click the Yes button so you won't have to load VisualAge Generator Templates Customizer the next time you start VisualAge for Smalltalk. By default, the image is saved as filename abt.icx. After the image is saved, you might consider making a copy of the image file.
        
       

       Note:

       If you get a walkback (VisualAge Debugger) window while saving the image, it probably means that you have run out of disk space. If this happens, close the VisualAge Debugger window and either free some space on your workstation and retry saving in the same place or save the image on another drive by selecting File>>Save Image As....

  
  

  ---

  
  

  List of APARS

  Fix Pack 4

  Developer

  PQ28607	Table variable not defined in generated UI Bean for Web-side edit function
  PQ52578	VA C++ folding functions are not sensitive to the current locale in Windows development environments.
  PQ52967	BATCH GENERATION OF WEB TRANSACTION FAILS IF VAJAVA AND VAGEN BATCH MONITOR ISN'T ACTIVE
  PQ53021	IMPLEMENTATION OF APP REUSE FOR C++ GENERATED PROGRAMS
  PQ53268	"HANG" SITUATION WHEN RUNNING HPTCMD LOADING AND UNLOADING
  PQ54515	WB WHEN COPY PASTE DATAITEM IN UI REC WHEN DBCS CHARS EXIST
  PQ55594	VAGEN OUTPUT INCONSISTENT BETWEEN ITF AND RUNTIME
  PQ55714	VALIDATE WORKS AND GEN FAILS WHEN accessing msg table from web trans logic
  PQ56033	VISUALAGE GENERATOR PARTS BROWSER DOES NOT SELECT COLLAPSED
  PQ56547	VAGEN V4.5 FP3 - HPTCMD SEEMS TO HAVE A MEMORY LEAK WHEN
  PQ56870	HEBREW CHARACTERS BEING DROPPED FROM THE LITERAL WHICH INCLUDES EXTRA SINGLE QUOTES
  PQ57069	ANYNUM PARMS GEN IN JAVA DIFFERENTLY
  PQ57273	VAGEN V4.5 FP3 - PERFORMANCE PROBLEM WHEN EXECUTING HPTCMD
  PQ57703	UNABLE TO GENERATE JAVA WRAPPER FOR EXISTING VAGEN CICS
  PQ57722	WALKBACK WHEN PERFORMING REFERENCES SEARCH FOR A PART.
  PQ57908	ITF does not issue warning message, HPT.CM.455.W when using EBCDIC mode
  PQ57935	WALKBACK USING VISUALAGE GENERATOR MSL MIGRATION TOOL
  PQ58231	ITF incorrectly setting length fields on maps
  PQ58318	WALKBACK USING MIGRATION TOOL WHEN MOVING PROGRAM FROM PARTS
  PQ58531	Debugger window opened after msg hpt.cm.207.e
  PQ59063	ITF OPENS FILES INCORRECTLY
  PQ59084	WALKBACK ENCOUNTERED AFTER APPLYING FP3 FOR VISUALAAGE GENERATO
  PQ59315	EXTRANEOUS VARIABLE DECLARATIONS INCLUDED IN VISUALAGE GENERATOR COBOL PROGRAMS. Customer can specify following SYMPARM option when generating: /SYMPARM=EZONEAS2,'YES' When the option is specified, the generated COBOL includes copybook VGNAHAS2 once in the linkage section and generates code to set the address of the copybook everytime the variables in the copybook are referenced. This causes a small increase in execution time, but allows the program to compile.
  PQ59350	Code for setting SOSI edit present was copied from data item to UI record data item. A flag for SOSI for the data item overlays the flag for TRANSACT attribute for records.
  PQ59482	TCP/IP Communications Limitation between images
  PQ59545	HPT.CM.158.E issued when validating pgm with /LISTING option
  PQ59557	JAVA SERVER PROGRAM GENERATION FAILS WITH LINKTYPE=REMOTE ENTRY
  PQ59579	PREPROCESSOR FOR OS/400 IS DOING SOME SPECIAL CHECKS THAT ARE
  PQ59628	resident shared tables wipe out on call when EBCDIC
  PQ59744	EBCDIC value incorrectly used for EZEDEST files names instead of ASCII
  PQ59914	WalkBack when PRINTING TO DBCS PRINTER
  PQ60003	JDBC NOT VALID FOR DBMS OPTION
  PQ60051	references on applications from parts browser
  PQ60054	Garbage in table contents when generating
  PQ60124	PGM FAILS VALIDATION IF CALL TO PGM USING EZEDLPCB PARAMETER
  PQ60165	GENERATING JAVA WRAPPERS WHEN REC CONTAINS ITEM NAMED DESCRIPTION
  PQ60258	SET map CLEAR AND EZESCOPY
  PQ60305	Data conversion attempt on Alternate file causes WB
  PQ60411	COMMITS AND DLI (ST and JAVA)
  PQ60584	ITF IF STATEMENT RESULT IS INCORRECT WHEN "RUN IN EBCDIC MODE"
  PQ60678	HPTCMD does not support UNC format for /OUTFILE
  PQ60744	WB GENERATING PROGRAM THAT CONTAINS TABLES WHEN IN EBCDIC
  PQ61022	PASSING A LITERAL ON A EZE FUNCTION CAUSES WB WHEN SIGNALLING TESTPOINTS
  PQ61069	SQL RETRIEVE OF NOT NULLABLE GRAPHIC ITEM
  PQ61073	RECORD WITH ONLY LEVEL77 ITEMS
  PQ61170	NO MSG WHEN INPUT NOT RECEIVED FOR A REQUIRED FIELD
  PQ61299	VALIDATING SQL STATEMENT WITH ; AT BEGINNING
  PQ61499	CPP GENERATION CAUSES RUNTIME FAILURE
  PQ61936	SETTING EZETST ON MOVEA WITH ARRAYS
  PQ61944	SELECTED INDEX DOES NOT WORK CORRECTLY FOR UI RECORD IN ITF
  PQ62092	WB WHEN LOCAL STORAGE OR LEVEL77 ON DLI CALL
  PQ62228	EBCIDC W/NO CONVERSION TABLE CAUSES INVALID RESULTS WITH FRACTIONS
  PQ62598	TEST NUMERIC FOR SQL ITEMS WHEN BLANKS EXIST
  PQ62644	CHA DATAITEM COMPARED TO NUM LITERAL IN EBCDIC
  PQ62728	SQLCODE -313 ON UPDATE WHEN DYNAMIC EXECUTION TIME STMT BIND
  PQ62786	XFER w/ UIRECORD when ERRORS EXIST
  PQ62832	SORTING OF PACKAGES ON IMPORT
  PQ63133	PRINTING A PROGRAM WHICH USES INDEX FILES
  PQ63144	JAVA IDE MAY HANG WHEN A JAVA METHOD EXECUTES A TOOL SERVER API AND THE VISUALAGE GENERATOR FEATURE IS LOADED WITHIN IDE.
  PQ63164	INCORRECT PACKAGES LISTED IN PARTS BROWSER
  PQ63167	ADD SUPPORT FOR NEW JAVA STARTUP PARMS
  PQ63265	VAG server for Z/OS, Java puts not serialized in session.
  PQ63296	VALIDATION OF VAR LENGTH RECORDS TO HOST ENVIRONMENTS
  PQ63383	VALIDATION OF PROGRAMS CAUSES PERFORMANCE PROBLEMS
  PQ63578	ADD TO FILE AFTER INQUIRY WHEN LOCAL FILE ACCESS
  PQ63661	INITIALIZATION OF FCWPARMBLOCK FOR CICS CALLED APPS
  PQ65219	PRINTING WHEN MOVEA EXISTS
  PQ65342 & PQ54431	5Meg limit on Image Component communication between Java and Smalltalk. This had been causing problems with Parts Browser (General Protection Fault) when listing large numbers of Vagen parts, and various other errors.
  PQ65711	GENERATED SOURCE FOR MFS MAPS DOES NOT INCLUDE THE OUTL'HH' STATEMENT WHEN MULTIPLE OUTLINE CHARACTERISTICS ARE SELECTED.
  PQ65804	LOGIC TO OPEN AND CLOSE SEQUENTIAL FILES IN GENERATED COBOL DOES NOT WORK PROPERLY WHEN RECURSIVELY CALLING SUBPROGRAMS.
  PQ65907	MAP ATTRIBUTES ARE NOT BEING SET CORRECTLY IN ITF AFTER INITIAL CONVERSE OF THE MAP.
  PQ65994	VAGEN USERS GENERATING SEGMENTED CICS TRANSACTIONS USING MQ/SERIES WILL HAVE MISSING WORKING STORAGE DATA ITEM.
  PQ66111	NEW "Commit without XFER" TEST OPTION
  PQ66161	Too many CTG connections opened.
  PQ66384	DATA RETURNED TO ITF FROM A REMOTE PGM IS CORRUPTED
  PQ66593	HOURGLASS ON IMPORT WINDOW
  PQ66871	CALCULATE RECORD OFFSET INCORRECT WHEN PRINTING
  PQ66881	TRAILING SPACES AND HIDDEN FILES ON UI RECORDS
  PQ66882	Leading blanks stripped from hidden fields in UI rec.
  PQ67435	BLANKING OUT NUMERIC FIELDS ON A MAP
  PQ67778	DBCS /LISTING print does not pad lines with correct number of spaces when used in a DBCS environment
  PQ67840	Incorrect number formatting when testing web transactions in ITF.
  PQ67934	Trace output out of sync with command line after calling assignment functions.
  PQ67935	Commented SQL code is incorrectly generated into C++ source code
  PQ68002	References utility hangs when run on Windows XP platforms
  PQ68022	CICS ECI enhancement to support calling CICS from Java applications
  PQ68096	DXFR WITH ARGUMENTS (ON UI RECORD) FAILS IN W\STORAGE RECORD.
  PQ68222	After applying VAG 4.5 FP3 FT18 and FIX for PQ59350, the "SHIFT-IN/SHIFT-OUT" option no longer functions.
  PQ68280	Walkback in ITF using EBCDIC mode with conversion table - due to not enough memory
  PQ68376	Walkback during Java Gen - String does not understand hptJavaResolveType
  PQ68694	MAKE SQL RECD DEFINITIONS UNIQUE FOR EACH APPLICATION BY ADDING PROGRAM TO SQL RECORD PREFIX IN GENERATED C++
  PQ68743	Stack overflow in ITF when setting testpoints and executing functions containing statements that assign negative literals to working or local storage variables
  PQ68745	The length of UI DBCS fields had double the correct length when the create UI record from map function was used.
  PQ68748	1. SQL subscripted host variable did not work when generated on a DBCS machine. 2. Long DBCS host variables where not faked for SQL names but caused a WB.
  PQ68798	Walkback in ITF when trying to display un-initialized local dataitems after being used in a function call.
  PQ68817	APPREUSE FOR THE CICS PLATFORM ON AIX 5.1 IS CAUSING SEGMENTATION VIOLATIONS.
  PQ68834	ITF does not show floating map as per set attributes after the first converse of a map
  PQ69376	IS MODIFIED function not working correctly with generated Web Transactions
  PQ69484	ITF Map fields of datatype Mixed are not justified correctly
  PQ70177	Session ID manager abends with 9999 active sessions.
  PQ70401	MODIFYING VAGEN TABLE FORCES USER TO REGENERATE THE PROGRAM
  PQ70435	ForUpdateOf Clause in SQL Update and SetUpd functions does not remove commented code from generated C++
  PQ70524	GetSecureGatewayURL has missing index.
  PQ70587	Index is missing from JSP for subscripted drop down lists
  PQ70976	TEST CURSOR STATEMENT RETURNS FALSE WHEN MAP ITEM IS PASSED AS PARAMETER TO A VISUALAGE GENERATOR FUNCTION.
  PQ71524	Numeric UIRecords show fill to the right of data
  PQ71538	Walkback when validating during ITF test run in EBCDIC mode
  PQ71751	4GL fillers not generated correctly into Java Wrapper source
  PQ71835	Remote variable length record item defined outside of record structure.
  PQ72254	Server loop when SessionIDManager no available.
  PQ73079	Package name missing from generated Java
  PQ73196	CPP Generation of Map Items incorrect when passing to functions for update
  PQ73739	XFER ON UI RECORDS WHEN EZEAPP IS SET TO BLANK, FAILS IN GENERATION.
  PQ74413	LNR7200 CAUSING MCH3601 IN VAGEN COBOL PRINT PROGRAM POINTER NOT SET
  PQ75012	Walkback occurs when generating java editables
  PQ76065	Compile errors in a generated COBOL program on AS/400 due to field EZEHAST-SMOD.

  Server Runtime

  PQ60878	COMPILE ERROR WHEN PREPARING VISUALAGE GENERATOR COBOL PROGRAM THAT PERFORMS MQ CALLS.
  PQ65531	AN INVALID MEMORY LOCATION ERROR IS ISSUED WHEN CALLING A C++ PROGRAM W/ APPREUSE TURNED ON.
  PQ67068	USER GETS COMPILE ERRORS WHILE TRYING TO GENERATE A VG GENERATED C++ PROGRAM ON AIX 5.1.
  PQ68540	LEFT JUSTIFY ON DBCS FIELDS DOES NOT DROP THE LEADING SPACE ON AIX-CICS, IT TREATS ANY LEADING SPACES AS VALID.
  PQ68541	WHEN JUSTIFICATION "NONE" IN DBCS FIELD, BLANK CHARACTERS ARE SAVED AS SBCS CHARACTERS.
  PQ68592	EZEMSG FIELD MAY OVERFLOW INTO AN ADJACENT FIELD IF THE MESSAGE CONTAINS DBCS FIELDS.
  PQ68941	MBCS FIELDS NOT DROPPING LEADING BLANK SPACES WHEN LEFT JUSTIFIED.
  PQ69125	FCWTRACE FILE STOPS LOGGING TRACE INFORMATION
  PQ69340	VAGEN CICS APPLICATIONS ON AIX5L PRODUCE INTERMITTENT ABENDS
  PQ69431	VAGEN FAILS TO CONNECT TO DB2 ON AIX 5.1
  PQ69463	AFTER A VALIDATION ERROR, THE CURSOR IS NOT RETURNED TO THE FIRST CHARACTER POSITION OF THE FIELD IN ERROR.
  PQ69561	WEB TRANS X ERROR USING IS MODIFIED FUNCTION
  PQ69864	ACCESS VIOLATION UNDER WINDOWS WHEN VAGEN APP RUN MULTIPLE TIMES
  PQ71528	PROBLEM CONNECTING VAGEN 4.5 ON AIX TO CTG 5.0
  PQ71857	CALLING A CICS PROGRAM USING NOMAPS WILL NOT UPDATE SCREEN ON RETURN WHEN MAP IS CHANGED.
  PQ72103	RIGHT JUSTIFICATION OF A MAP FIELD WITH NULL FILL RESULTS IN GARBAGE CHARACTERS IN FIELD
  PQ72469	SQL OPERATIONS FAIL WITH ERROR FCW0045E, RC=100. USING AIX 4.3.3 & CICS 5.0
  PQ72642	VISUALAGE GENERATOR SERVER 4.5 MSGFCW0008E FOR FILE NAME DEFINED IN UPPER CASE RC=2
  PQ73696	AIX CICS PROGRAM CALLING A NATIVE AIX PROGRAM, IS UNABLE TO WRITE TO A SEQUENTIAL FILE.
  PQ74803	C++ RUNTIME DOES NOT SET EZEAID CORRECTLY WHEN A UI RECORD IS CONVERSED IN A DXFRED WEB TRANSACTION
  PQ75194	TRAP IN FCW.DLL WHEN EZEUIERR USES NO INSERTS
  PQ75280	OVERFLOW OCCURS WHEN MULTIPLYING AND DIVIDING NUMBERS IN A VAGEN CALCULATION.
  PQ75418	MEMORY LEAK IN VAGEN C++ RUNTIME ON AIX 5.1
  PQ75829	SQL NUMBERS ARE ROUNDED IF SELECTED INTO A SHORTER DATA ITEM

  Common Services

  PQ56988	Decimals moved to pack displays incorrectly
  PQ60975	MACHINE HANGS AND PRODUCES INVALID MEMORY ERROR MESSAGES WHEN TRYING TO CALL A VG PROGRAM IN ITF VIA JAVA WRAPPER.
  PQ64219	TRAP WHEN USING CSOPOWERSERVER APIS TO CALL ITF
  PQ65545	MISSING C++ DLL ON SERVER CAUSES ACCESS VIOLATION ON JAVA CLIENT.
  PQ65955	WHEN USING EZEPOW TO RAISE TO THE POWER OF ZERO THE AIX RUNTIME PRODUCES AN ABEND/RC16
  PQ70088	VAGEN V4.5 FP3: HANDLE COUNT CONTINUES TO BUILD WITH EACH ACCESS TO THE GATEWAY SERVLET.

  Templates APARS

  PQ70631	Generator throws exception on setFillCharacter method. This has changed to PQ75004 (from PQ70631), as the original APAR was raised under the wrong component ID.
  PQ71651	Import of views from DB2 v7 on AIX results in SQL error.
  PQ75004	Generator throws exception on setFillCharacter method
  PQ75174	FO-REQ-CHK function in data control program has incorrect value for number of messages variable
  PQ75178	FE-CTRL function not generated if 'control location' set to 'server'
  PQ75223	Duplicate values in web application drop-down list
  PQ75225	Unnecessary database access when BO logical key has numeric data type
  PQ75226	CONTROL-DATA-ELEMENT should be set to an uppercase value in function FO-N-MAIN
  PQ75227	Data Element column label field not taken into account by Smalltalk Web UI Generator
  PQ75228	FW-ENTRY-INIT function not correctly generated when ExtractCriteriaDisplayed parameter = false.
  PQ75229	Generation error when target interface unit does not contain any business object
  PQ75230	Java GUI with updateable list does not properly refresh interface if all rows on a page are deleted.
  PQ75231	Reverse of a complete or whole package stops with ArrayIndexOutOfBoundsException.
  PQ75234	Text is truncated in error messages displayed in GUI error window.
  PQ75379	Map numeric variable field length > 18 with numeric edits are truncated to length = 18

  Other Product APARs

  PQ69928

  Accessing plugins is possible although a previous logon was not successful. This for example allows access to DL/I resources even if a invalid userid or password has been entered. This APAR concerns remote DL/I access to VSE systems.

  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

  • PQ47717 INCORRECT VALUES DISPLAYED FOR DECIMAL RETURNED VIA JDBC
  • PQ47719 DECIMAL SEPARATOR OTHER THAN '.' NOT HANDLED CORRECTLY
  • PQ49317 DB2 PASSWORDS EXPOSED WHEN PREPPARING A GENERATED VISUALAGE GENERATOR C++ PROGRAM
  • PQ48174 THE I/O ERROR VALUE ERR IS NOT BEING SET
  • PQ49680 CUSTOMER RECEIVING HPT.CG.13.I WHEN TRYING TO GENERATE
  • PQ50386 MIGRATING 4GL MAPS VIA ESF PRODUCED BY CSP 3.3.0
  • PQ49672 HPT.CM.249.E ISSUED WHEN GENERATING A VISUALAGE GENERATOR
  • PQ49468 SECURITY ISSUES USING VAGENGATEWAY LOGIN PROCESS
  • PQ44221 AR-SA LOCALE DOES NOT DISPLAY STRINGS CORRECTLY IN UIREC
  • PQ45584 INCORRECT NUMERIC VALUE DISPLAYED IN BROWSER
  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

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

  ---

  FixPak1

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

  ---

  VisualAge Generator Generation Guide

  ---

  Appendix B. Implementing a generation server

  Because generation is a resource-intensive operation, you may wish to generate on a system other than the workstation on which you normally run VisualAge Generator Developer. You can set up a generation server to handle your generation jobs or the generation jobs of multiple programmers.

  To implement a LAN generation server, you must customize the VisualAge Generator Developer configuration on the generation server and on the client. On the server, most of the customization is handled automatically. On the client, more manual customization is required.

  When you are installing VisualAge Generator Developer on a LAN generation server, shared files are placed in a directory on a shared drive that is used for communication between the client and the server. Before you begin installation, you need to know what type of network you will be using and which drive will be shared.

  Sample files

  VisualAge Generator Developer provides sample REXX programs to help you implement a generation server. During installation, these sample files are placed in the installation directory (by default, C:\Program Files\IBM\VisualAge for Java or C:\Program Files\Vast). You must customize these files for your specific LAN server and operating system environment to provide the required processing support. These sample programs are command-driven and are not directly available on the graphical user interface.

  You can use the user interface for generation to create generation command files that invoke the EFKREQ.CMD or EFKREQ.REX client code if the following criteria are true:

  • CALL EFKREQ is selected on the Batch generation command portion of the VisualAge Generator Options window when Generation is selected in the left pane.
  • Batch Generation is selected on the Generate window.

  Note:

  The sample REXX programs are the recommended method for running VisualAge Generator Developer on a generation server. It is recommended that you do not use the NET RUN service.

  To run these REXX programs on Windows NT you will need to obtain and install REXX support; this is provided by the product IBM Object REXX for Windows NT and Windows 95 (5801-AAR). You need the interpreter edition (Feature 1569, part number 10J9392).

  Figure B-1 shows the names of the sample files provided for OS/2 and Windows NT.
  

  Figure B-1. Sample files provided for LAN generation on for OS/2 and Windows NT
  

  File name	Description
  EFKSERV.CMD (OS/2) or EFKSERV.REX (Windows NT)	This REXX file contains commands that receive server requests. The EFKSERV.CMD or EFKSERV.REX program runs on the LAN server and continually checks the server input queue for generation requests. The server input queue is specified in the EFKGEN.INI file.
  EFKREQ.CMD (OS/2) or EFKREQ.REX (Windows NT)	This REXX file contains commands that submit server requests. The EFKREQ.CMD or EFKREQ.REX program runs on the client, gathers generation option information, and places the generate request on the server input queue. EFKREQ also supports command options of PAUSE, STOP, and START. These command options control the processing of EFKSERV.
  EFKLIST.CMD (OS/2) or EFKLIST.REX (Windows NT)	This REXX file contains commands that list the contents of the server input queue. The EFKLIST program runs on the client and displays a list of all requests waiting to be processed by the EFKSERV program.
  EFKGEN.INI	This file defines the locations for different files. This file also defines other parameters used by the REXX command files. This file is installed on the client and server.
  LANGEN.TXT	This file contains additional configuration guidance for the implementation of generation clients and generation servers.

  Setting up Object REXX support on Windows NT

  The tasks described in this section are required only on Windows NT. OS/2 provides integrated support for REXX. The tasks on Windows NT are as follows:

  • Install Object REXX.
  • Customize Windows NT so that REXX command files, which have a file extension of .REX, are recognized as a REXX command and invoked under the control of the REXX interpreter. To fully implement this level of REXX support in Windows NT you must complete the following steps:
    1. Check that the Object REXX installation process sets up an association for the .REX filetype. You can check the existing associations using the assoc .rex command.

       If the association does not exist, you can add it from the command line by running the following command:

       assoc .rex=REXXscript
       

    2. Make sure the Object REXX command processor is somewhere in the PATH environment variable (or enter it fully qualified in this step) and use ftype to link it to the file type, if this has not been done by your command processor setup. You can check the existing file-type association by using the ftype REXXscript command. Ensure that the file type association for REXXscript has the following value:

       REXXscript="C:\ObjRexx\rexx.exe" %1 %*
       

       where C:\ObjRexx is the path name of the directory where Object REXX is installed. If the ftype definition does not exist, or does not match the value shown above, you can create the definition from the command line using the following command:

       ftype REXXscript="C:\ObjRexx\rexx.exe" %1 %* >.REX
       

       Note:

       A file association may have been set up automatically when you installed REXX. However, you must modify the ftype definition for REXXscript to ensure parameters are passed as expected.

    3. On Windows, make sure that .REX is included in the PATHEXT environment variable on each LAN generation server system and each on each client system. This lets you to use the command file without typing the file-name extension. To set it permanently, use the Environment tab of the Windows NT System Properties window or the Environment Variables page of the Advanced tab of the Windows 2000 System Properties window. If the variable does not already exist (it has a default value when PATHEXT is not set), create PATHEXT with the the following value:

       .REX;.COM;.EXE;.BAT;.CMD
       

  Setting up the generation server

  This section describes how to set up a LAN generation server. Before you begin, you need to know what type of network you are using, which directory on each generation server will be shared, and which drive on the generation clients will be used to access the shared directory.

  To set up a LAN generation server, complete the following steps on each system that you want to use for remote generation:

  1. Install the VisualAge for Java or VisualAge Smalltalk client.
  2. For Windows NT, install and tailor Object REXX. See Setting up Object REXX support on Windows NT.
  3. Install VisualAge Generator Developer.
     1. In the Setup Type window, select Configure LAN Generation Server.
     2. In the LAN Generation Server window, be sure that the shared drive you specify supports long names. If the file system does not support long file names, you must modify the long file names in the sample REXX programs to use file names each with a base name no longer then eight characters and an extension no longer than three characters.

     The installation software completes the following steps:

     • Creates the following directories (C:\LANGENSVR is the default; you can change the value when you are installing VisualAge Generator Developer on the generation server):
       • C:\LANGENSVR
       • C:\LANGENSVR\cmd for command files
       • C:\LANGENSVR\inputGen for the input queue
       • C:\LANGENSVR\outlist for output listings and the generation log
       • C:\LANGENSVR\template for generation template files
       • C:\LANGENSVR\working for temporary files
     • Copies the following files from the installation directory to the cmd directory:
       • EFKGEN.INI
       • EFKLIST.REX or EFKLIST.CMD
       • EFKNETRC.REX or EFKNETRC.CMD
       • EFKREQ.REX or EFKREQ.CMD
       • EFKSERV.REX or EFKSERV.CMD
       • EFKSND.REX or EFKSND.CMD
       • LANGEN.TXT
     • Copies the EFKGEN.INI file in the cmd directory to files EFKGENCL.INI and EFKGENSV.INI.
     • Modifies EFKGENSV.INI to reflect the drives that the generation server uses. It sets the working_dir parameter to a directory located on the server and sets the server_input_dir and gen_listing_dir parameter values to directories located on a shared file system that can be accessed by both generation clients and generation servers. For example, it may produce the following settings: /server_input_dir=C:\LANGENSVR\inputGen and /gen_listing_dir=C:\LANGENSVR\outlist
     • Sets the environment variable GENERATE_INI to the path name of the directory containing the EFKGENSV.INI file.
  4. If you are running the Smalltalk version of VisualAge Generator, copy the following files from the VisualAge Generator Developer installation directory to C:\LANGENSVR\cmd:
     • abt.cnf
     • hpt.ini

       This file has been tailored to include the VisualAge Generator environment variables and to point to the repository.

     • abt.icx

       This is a workspace/image that already has the VisualAge Generator Developer feature loaded.

  5. Edit the EFKSERV and EFKREQ scripts to point to the appropriate input and working directories. Do this in C:\LANGENSVR\cmd, not in the VisualAge Generator Developer installation directory. This ensures that any fixpak changes to EFKSERV and EFKREQ do not destroy your changes.
  6. Copy the VisualAge Generator Developer templates (*.TPL files) to C:\LANGENSVR\template and modify the copied files in C:\LANGENSVR\template as needed. Be sure to point your generation options to the modified version of the templates. The directory that contains the original version of the templates depends on whether you are running the Java or Smalltalk version of the product:
     • Java: C:\Program Files\IBM\VisualAge for Java\IDE\program
     • Smalltalk: C:\Program Files\Vast\bin
  7. Share the C:\LANGENSVR directory. On Windows do not accept the default share name, LANGENSVR shorten it to eight or fewer characters, for example, LANGEN.
  8. Set the PATH environment variable to include C:\LANGENSVR\cmd before the VisualAge Generator Developer installation directory cited at the end of Step 6.
  9. If you are running on a Novell Netware LAN environment, set the EZERUSRID environment variable to the LAN user ID of the generation server.
  10. Reboot your system for the changes to take effect.
  11. Start EFKSERV from a command prompt.
      • The EFKSERV program runs continuously. To stop the EFKSERV program, press Ctrl-C or issue the EFKREQ STOP command.
      • The EFKSERV program writes a log listing the generated programs. This log file is called Gen_Server.log and is located in the directory specified for the gen_listing_dir parameter in the EFKGEN.INI file.
      • For additional information, see the LANGEN.TXT file.
  12. For Windows NT, if the repository is not on the generation server system, ensure that the date style and time style in the regional settings on the generation server system match the corresponding information on the system where the repository is located.

  Setting up the generation client

  This section describes how to set up a LAN generation client. Before you begin, you need to fulfill the following prerequisites:

  • A LAN generation server has been set up.
  • You know what type of network you are using.
  • You know which drive on the generation clients will be used to access the shared directory on the generation server. All clients of a particular LAN generation server must use the same drive for sharing the shared directory.
  • You have read and write access to the directory on the server where the input queue is located to submit requests. The location of this directory is defined by the value of the server_input_dir parameter in the EFKGEN.INI file.

  To set up a LAN generation client, complete the following steps on each system that you want to be able to use a generation server:

  1. Install the VisualAge for Java or VisualAge Smalltalk client.
  2. For Windows NT, install and tailor Object REXX. See Setting up Object REXX support on Windows NT.
  3. Install VisualAge Generator Developer. The generation client should use the same repository that the generation server uses.
  4. Map the generation server drive so that drive h: on the client workstation points to C:\LANGENSVR on the server machine.
  5. Set the GENERATE_INI environment variable to point to h:\cmd\EFKGENCL.INI.
  6. Modify the EFKGENCL.INI file on the generation server system as follows:
     • Set the working_dir parameter to the path name of a local directory located on each generation client.
     • Set the server_input_dir and gen_listing_dir parameter values as follows:

       /server_input_dir=h:\inputGen
       /gen_listing_dir=h:\outlist
       

  7. Set the PATH environment variable to include h:\cmd and the path name of the VisualAge Generator Developer installation directory. The former directory must be included before the latter so that you can use EFKREQ from the generation server.
  8. If you are running on a Novell Netware LAN environment, set the EZERUSRID environment variable to the LAN user ID of the client workstation.

     For Windows NT, this should be a user environment variable, because it varies depending on which user is logged in.

  9. On each generation client system, specify EFKREQ for generation, as follows:
     1. From the VAGen Parts Browser window, select Window then Options.
     2. In the VisualAge Generator Options window, in the left pane select Generation.
     3. In the right pane select the CALL EFKREQ radio button and Apply.
  10. Exit from VisualAge Generator Developer and reboot your system for the changes to take effect.
  11. For Windows NT, ensure that the date style and time style in the regional settings on the client system match the corresponding information on the system where the repository is located.

  After setting up the generation client

  You can submit server requests even if the EFKSERV program is not running. The EFKREQ program places the generation request in input queue of the server.

  The HPTCMD command output listings are placed in the directory specified by the gen_listing_dir parameter in the EFKGEN.INI file. The generated source and related program objects are placed on the server machine in the directory specified by the /GENOUT generation option.

  When you specify a value for the /GENOUT generation option, use symbolic parameters to avoid conflicts with other generation requests. Figure B-2 shows how to use a symbolic parameter.

  Figure B-2. Example showing the use of symbolic parameters
  
  

  /GENOUT=F:\OUTPUT\%EZEPID%\%EZEENV%
  

  If your target system is CICS for OS/2 and your project is USERA, the generated output is placed in the directory F:\OUTPUT\USERA\OS2CICS. If the directory you specify does not exist, it is created for you.

  
  

  ---

  Useful Websites:

  IBM VisualAge Generator http://www.ibm.com/software/awdtools/visgen IBM VisualAge Smalltalk http://www.ibm.com/software/awdtools/smalltalk IBM VisualAge Java http://www.ibm.com/software/awdtools/vajava IBM Application & Web Development Tools http://www.ibm.com/software/awdtools IBM Software Homepage http://www.ibm.com/software IBM Corporation Homepage http://www.ibm.com