WebSphere^TM Development Tools for iSeries V5.1 Release Notes

This document provides information that is specific to this release of the WebSphere Development Tools for iSeries product. This release integrates components that were previously available only as separate products. Hardware requirements (memory and disk space), software requirements (at development and run time), and migration scenarios are provided.

The README document contains prerequisite information, limitations of the product, and information not included in the documentation.

The Installation Notes document contains all installation notes and procedures. This includes the use of response files and how to uninstall, and how to add or remove product components.

Table of Contents

• Components
• Workstation Requirements
• Hardware
• Software
• Migration Process
• VisualAge(R) for Java(TM) Version 3.5.3 Enterprise Toolkit for AS/400(R) RELEASE NOTES

Components of Release V5.1

The five components are:

1. WebFacing Tool allows you to display on the Web traditional programs that use DDS display files. Custom-generated JSP files and Java beans substitute for DDS code and make Web access possible.
2. WebSphere Studio for iSeries contains wizards for creating JavaBeans^TM, Java servlets, and deploying e-business applications easily.
3. VisualAge for Java for iSeries provides a powerful environment for Java development. You can optionally install ET/400 which provides tools, wizards, java beans, and AS/400 Toolbox for Java classes. This makes the job of developing Java client and server programs that target iSeries much easier.
4. Cooperative Development Environment (CODE) allows you to edit, compile, and debug RPG, COBOL, C, C++, CL, DDS, and Java (includes the CODE Designer, a WYSIWYG DDS tool).
5. VisualAge RPG supports applications with Windows GUI, transparent access to iSeries resources, and generates Java applications and applets.

Integration between WebSphere Studio and VisualAge for Java enables teams to communicate and work together to:

• Create new e-business applications
• Port existing e-business applications from other servers
• Enable existing applications for the Web.

In addition, the installation of WebSphere Development Tools for iSeries has been simplified with:

• Automatically launched menu-driven install procedures
• A Host and Server Configuration wizard for setting up communications between workstations and servers.

Workstation Requirements

Hardware Requirements

• Processor - Intel Pentium II (or faster compatible processor recommended)
• Display - SVGA 800x600 (1024x768 recommended)
• CD or DVD drive
• A mouse or other pointing device
• Appropriate communications adapters (as supported by the workstation operating system)
• Memory and disk requirements are:

  Component	Memory		Disk
  	Minimum	Recommended	Minimum	Recommended
  WebFacing Tool (First Edition)	128 MB		200 MB
  WebSphere Studio for iSeries (V3.5)	96 MB	128 MB	385 MB	500 MB
  VisualAge for Java for iSeries (V3.5)	128 MB	192 MB	495 MB	550 MB
  CODE	64 MB	96 MB	235 MB
  VisualAge RPG	64 MB	96 MB	285 MB
  TOTAL for products	128 MB	256 MB	1.2 GB	1.5 GB

System requirements decrease if you choose to install only the components that you require.

Software Requirements

Migration Process

VisualAge(R) for Java(TM)

Version 3.5.3

Enterprise Toolkit for AS/400(R)

RELEASE NOTES

Table of contents

1.0 Introduction
2.0 Prerequisites
3.0 Limitations and known problems
     3.1 Convert Display File SmartGuide
     3.2 AS400eList Bean Performance
     3.3 Code generation in DFU beans
4.0 Hints and Tips
      4.1 Run time files
      4.2 Deployment of a VCE application that has DFU beans
      4.3 Debugging
5.0 AS/400 Java Web sites
6.0 Documentation

1.0 Introduction

These Release Notes contain prerequisite information for the VisualAge for Java Enterprise Toolkit for AS/400. In addition, they include any limitations of the product and information not included in the documentation.

The AS/400 server is now referred to as the IBM eServer iSeries. However, for this release of VisualAge for Java, all reference made to the server will be by its former name, "AS/400".

2.0 Prerequisites

• In general, we recommend that you load the latest cumulative fixes (PTFs) onto your AS/400.
• The Distributed Debugger requires that the following PTFs be applied to the appropriate release:
  

  OS/400  Release	LPP Number	PTF Number
  V4R3M0	5769SS1*	SF49975*
  V4R3M0	5769999	MF19487
  V4R4M0	5769999	MF24806
  V4R4M0	5769SS1	SF54570
  V4R4M0	5769SS1	SF56682
  V4R4M0	5769SS1	SF56281
  V4R4M0	5769SS1	SF63732
  V4R5M0	5769SS1	SF63034

*Note: This PTF will soon be superseded by another.

For information about the most recent PTFs for the Distributed Debugger, please refer to http://www-1.ibm.com/support/search.wss?rs=715&tc=SSZND2&dc=DA400.

• Editing code support for the Convert Display File SmartGuide has been improved. To take advantage of this, you need to apply the appropriate PTF:
  

  OS/400 Release	LPP Number	PTF Number
  V3R1M0	5763PW100	SF47783
  V3R2M0	5763PW100	SF47784
  V3R6M0	5716PW100	SF47785
  V3R7M0	5716PW100	SF47786
  V4R2M0	5769PW100	SF47774

• The ET/400 Run action requires the following PTF:
  

  OS/400 Release	LPP Number	PTF Number
  V4R3M0	5769SS100*	SF49975*
  V4R4M0	5769SS100	SF63732
  V4R5M0	5769SS100	SF63034

*Note: This PTF will soon be superseded by another.

• Several of the examples make use of updated AS/400 files in the ADTSLAB library. To be able to run these examples, you need to apply the appropriate PTF listed below for the "Application Development ToolSet/400" product:
  

  OS/400 Release	LPP Number	PTF Number
  V4R2M0	5769PW100	SF63545
  V4R4M0	5769PW100	SF63703

For more up to date PTFs, please refer to: http://www.software.ibm.com/ad/as400/vajava/

• For any IBM(R) AS/400 Toolbox for Java(TM) PTFs, refer to the following Web site: http://www.as400.ibm.com/Toolbox
• Before you can connect to as AS/400 server, you must start all host servers on the AS/400 (by issuing STRHOSTSVR *ALL) and you must start TCP/IP on the server (by issuing the command STRTCPSVR *DDM).

3.0 Limitations and known problems

3.1 Convert Display File SmartGuide

On systems which have earlier versions of IBM Personal Communications, it may not be possible to start an IBM Personal Communications session while the Convert Display File SmartGuide is running. Once the SmartGuide is finished running, an IBM Personal Communications session may be started.  

A bean generated by this Smartguide can be opened in the VCE, and saved after undergoing Construct Visuals from Source. The resulting bean may not look or behave as the original.

3.2 AS400eList Bean Performance

When extracting lists from an AS/400 server, data conversion may require a longer period of time to complete, if the list is very large, or if binary or date fields are selected. To achieve the best performance, follow these recommendations:

1. Use the OBJL0100 or OBJL0200 formats, which allow for translation of data in one step.
2. If OBJL0300 format or higher is selected, try to avoid selecting the binary or date fields listed below, unless necessary. If a binary field or date field is selected, the translation of the field attributes must be performed individually for each item. This slows the overall process, especially for larger lists.

Binary fields
getInclude0300AuxiliaryStoragePool()
getInclude0500SaveSize()
getInclude0500SaveSizeMultiplier()
getInclude0500SaveSequenceNumber()
getInclude0600DaysUsedCount()
getInclude0700Size()
getInclude0700SizeMultiplier()

Date fields
getInclude0300CreateDateTime()
getInclude0300ChangeDateTime()
getInclude0500SavedDateTime()
getInclude0500RestoredDateTime()
getInclude0500SaveActiveDateTime()
getInclude0600LastUsedDateTime()
getInclude0600ResetDateTime() 

3.3 Code generation in DFU beans

When the FormManager, ListManager, or RecordIOManager beans generate code, the progress indicator may appear several times, depending on the number of methods that are generated for the condition class. 

Do not attempt to close the bean's Property window during code generation, as this will cause the Visual Composition Editor to hang. For FormManager or ListManager, the value of the recordIOManager property will change accordingly when code generation is complete, and the Property window can be closed at that time.

4.0 Hints and Tips

4.1 Run time files

The following .jar and .zip files are available for running examples and applications outside of VisualAge for Java. These files are available in the 'eab\runtime30' directory:

• JT400.JAR (AS/400 Toolbox for Java)
• JT400MRI.ZIP (translated text for the AS/400 Toolbox for Java classes)
• AS400UT.JAR (classes provided in package com.ibm.ivj.et400.util and
  com.ibm.ivj.et400.util.awt)

These Toolbox .jar files can also be found in the 'eab\runtime30' directory:

• DATA400.JAR
• JT400PROXY.JAR
• JT400SERVLET.JAR
• JUI400.JAR
• UITOOLS.JAR
• UTIL400.JAR
• X4J400.JAR
• JT400ACCESS.ZIP
• UTILITIES.ZIP

Please check out the Frequently Asked Questions on how to use AS/400 Toolbox for Java on OS/400 from http://www-1.ibm.com/servers/eserver/iseries/toolbox/faq.htm.

4.2 Deployment of a VCE application that has DFU beans

4.3 Debugging

The Distributed Debugger is installed separately from VisualAge for Java. To install it rerun the VisualAge for Java setup program and select to install the Distributed Debugger.

5.0 AS/400 Java Web Sites

To learn more about the IBM AS/400 Toolbox for Java, visit the following web site:
http://www-1.ibm.com/servers/eserver/iseries/toolbox/index.html

6.0 Documentation

1. The majority of the Enterprise Toolkit for AS/400 (ET/400) help has changed since it was translated. Please refer to the English help for the most recent version of the help.
2. Features of ET/400 that have only been documented in English include:
   • The DFU beans: FormManager, ListManager, and RecordIOManager. The DFU beans are a set of classes that extend the support of code to access one or more AS/400 database files. These beans allow you to map GUI forms, tables, and lists to AS/400 databases and manipulate (retrieve, add, update, and delete) database records.
   • The Object List beans: ET400List and AS400eList. The Object List beans provide a method for accessing AS/400 object names. These beans allow you to set listing properties for selecting the desired type of object list. Object list types include a list of libraries, a list of files within a library, or a list of user IDs on the system. The property settings can be used to access many different type of object lists.
   • New JFormatted beans (in addition to existing JFormatted beans): JFormattedTable, JFormattedTableColumn, JFormattedTextFieldCellEditor,
     JFormattedComboBoxCellEditor, and JFormattedLabelCellRenderer.
   • A new Logon dialog.
   • New options in the Compile and Run dialogs.
   • The ET/400 Daemon, which can be started so that you avoid signing onto the same AS/400 more than once while accessing and using the SmartGuides, actions dialogs, or property dialogs.
3. The following concepts have been added since the ET/400 help was last translated:
   • "Data File Utility (DFU) beans"
   • "Object List beans"
4. The following tasks have been added:
   • "Starting and stopping the ET/400 Daemon"
   • "Launching the OLT Viewer for debugging"
5. The following references have been added:
   • "FormManager bean"
   • "ListManager bean"
   • "RecordIOManager bean"
   • "RecordIOManager properties"
   • "Program call considerations"
   • "JFormattedTable bean"
   • "JFormattedTableColumn bean"
   • "JFormattedTextFieldCellEditor bean"
   • "JFormattedComboBoxCellEditor bean"
   • "JFormattedLabelCellRenderer bean"
   • "ET400List bean"
   • "AS400eList bean"
6. Any samples pertaining to the new DFU, Object List, and JFormatted beans have been added.
7. The following concepts have been changed:
   • In "JFormatted beans", information about the JFormattedTable, JFormattedTableColumn, JFormattedTextFieldCellEditor, JFormattedComboBoxCellEditor, and JFormattedLabelCellRenderer beans has been added.
8. The following references have been changed:
   • "Display file considerations"
   • "Display file keywords"
9. The following feature has been removed since the ET/400 help was last translated:
   • There is no longer a Create Subfile SmartGuide and all references to creating subfiles or using the Create Subfile SmartGuide have been removed.
10. The following tasks have been removed since the ET/400 help was last translated:
    • "Creating a subfile class"
11. The following references have been removed since the ET/400 help was last translated:
    • "Record I/O considerations for subfiles"
12. The following samples have been removed since the ET/400 help was last translated:
    • "Create a Java client/server application"
    • "Display a list of names and phone numbers"
    • "Get and display data in a subfile"
    • "Populate a subfile"
    • "Hide a column in a subfile"
    • "Get a record in a subfile"
    • "Get field names and descriptions for a database file"
    • "Set subfile presentation"
    • "Add, remove and insert subfile records"
    • "Set subfile selection mode"
    • "AS/400 Toolbox for Java (demo)"