README -- WebSphere Development Tools for iSeries, V5.1

The following README is cumulative, containing all information from the base release plus subsequent service packs.

For more information, see the WebSphere Development Tools for iSeries Web site at ibm.com/software/ad/wdt400.

Note: Service packs cannot be uninstalled.

Table of Contents

Service Pack 5

• Prerequisites
• CODE component
  • List of fixes
  • Special instructions

• VisualAge RPG component
  • List of fixes

• WebFacing Tool component
  • List of fixes
  • New features
  • Variations from 5250 behaviour
  • Special instructions

Service Pack 4

• CODE component
  • List of fixes

• VisualAge RPG component
  • List of fixes

• WebFacing Tool component
  • List of fixes
  • New features
  • Special instructions

• WebSphere Studio for iSeries
  • List of fixes
  • New features

Service Pack 3

• CODE component
  • List of fixes
  • New features

• VisualAge RPG component
  • List of fixes
  • New features

• WebFacing Tool component
  • List of fixes
  • DDS keywords now supported
  • New features
  • Restrictions

Service Pack 2

• CODE component
  • List of fixes

• WebFacing Tool component
  • List of fixes
  • DDS keywords now supported
  • New features
  • Special instructions

Base Release

• Documentation changes
  • Important: How to selectively install or remove components
  • VisualAge(R) RPG (VARPG)
  • WebSphere Studio for iSeries
  • Distributed Debugger and Object Level Trace

• Known problems and workarounds
  • JDK notes
  • VisualAge RPG GUI Designer and Java plug-in
  • VisualAge RPG IFS names
  • Problems with help
  • WebSphere Studio for iSeries: Invoking subfile DTC API
  • Using samples from Enterprise Toolkit for iSeries
  • Truncated display messages in CODE
  • Browser problems
    • Netscape search in Windows 2000
    • Netscape Navigator non-conformance
    • Internet Explorer and help for AS/400 Toolbox for Java
  • The Distributed Debugger
  • Object Level Trace
  • Norton AntiVirus

• Other sources of information
  • Web sites for information and updates
  • Links to newsgroups

• Legal Information
  • How to find your License Agreement
  • Notices
  • Programming interface information
  • Trademarks and service marks

Service Pack 5 -- February 2002

Prerequisites

Note for Windows 98 and Windows ME users:
If you have Win98 or WinME, download and run "Windows Installer 2.0 Redistributable for Windows 95, 98, & ME" before applying this service pack. "Windows Installer 2.0 Redistributable for Windows 95, 98, & ME" can be downloaded from:
ftp://ftp.software.ibm.com/as400/products/ad/wdt400/v5r1sp5/instmsi.exe

Note:
The latest WebFacing Tool PTFs and WebSphere Application Server updates are required if you are using the WebFacing Tool.

• WebFacing Tool host PTFs -- for more information, see the Host PTF section of the System requirements page at:
  http://www.ibm.com/software/ad/wds400/about/sysreq.html
• WebSphere Application Server (WAS) 3.5.x updated to 3.5.5
• WebSphere Application Server (WAS) 4.0.x updated to 4.0.2
• Fixes and updates to the Distributed Debugger can be obtained by installing Distributed Debugger - Service Pack 1 (67,521,369 bytes).

CODE component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

CODE Communications

• DBCS data is no longer corrupted when saving a file back to the AS/400.
• The Server Settings on the Communication Console are changed to reflect the use of the userID and Password fields. In the past, these fields were enabled for changes. Now, the "change" button for these fields is disabled if the server is active (and the "shutdown" button is enabled). Thus, in order to change a user ID and password, you must first make the server inactive by shutting down the server using the "shutdown" button, and then restarting the daemon once you have made the changes.

CODE Designer

• The Designer is now more flexible when moving individual fields in subfile records.

CODE Editor

• When opening an IFS file, you can now enter the server name defined with an IP address in the Communication Console Server Settings of your AS/400 in the Server field. In the past, you were only able to enter your CODE/400 server name, which must be the same as the AS/400 IP name (APAR #SE03803 ).
• COBOL cross-references can now find paragraphs starting with a numeric character (APAR #SE03091).
• The window invoked from View > Cross Reference no longer has missing fields.

CODE Program Generator

• Program Generator now correctly parses IFS files when you use the "&M" compile command (APAR #SE03035).
• The CRTBNDCPP compile option dialog now automatically wraps values specified for the INCDIR parameter in quotation marks, so that you do not experience errors in compilation (APAR #SE03036 ).

CODE Project Organizer

• The "Modified Date at time of Copy" now correctly shows the year as "20xx" rather than "19xx" (APAR #SE03721).
• If you define a type as "*BLANK", the AS/400 will no longer insert a zero or a random character in front of the PDM member text when the source member is uploaded to the host (APAR# SE03742).

ILE RPG

• The Smart Enter feature can now properly detect whether or not signatures are activated, so that the user can see when a signature is being added without having to directly call the signature macro or use the IS (insert skeleton) prefix area command. Signature macro documentation is updated to more accurately reflect its function (APAR #SE03157).

Special instructions

• It is important that you shut down the Communications daemon before installing service pack 5.

VisualAge RPG component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

• The Numeric Entryfield now functions correctly.
• For the subfile open-edit cell: the combobox can now handle spaces at the end of an entry.
• The subfile open-edit cell no longer has a colour problem.
• The Java version of the subfile no longer generates two pop-up events when you right-click the subfile.
• The Java version of the EntryField no longer produces an unrecoverable error if you try to use the "Text" attribute when auto-format is on.

WebFacing Tool component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

• JavaScript errors that occurred with the COMP keyword have been fixed.
• Numeric fields will now be validated correctly when you use decimal separators other than periods, and thousands separators other than commas.
• Validity checking of fields is now bypassed when you press a command attention key.
• When a record is written with MDTOFF, on-screen fields with DSPATR(MDT) will now have their MDT cleared.
• The WebFacing Tool has fixed the problem where only bottom subfile records were showing when you used the SFLDROP keyword.
• The WebFacing Tool has fixed the problem where an incorrect SFLSCROLL value might have been returned to the high-level language program when you use the SFLEND(*SCRBAR) keyword.
• You can now write two records with the same name without encountering problems in the browser.
• Generated JSPs and Java Beans now contain the version of tooling that generated them. This allows for enhanced backward compatibility in the future.
• Problems with embedded double quotation marks have been fixed for the following keywords: ERRMSG, SFLMSG, DFT, DFTVAL, VALUES, EDTWRD, and WDWTITLE.
• Errors in the error log have been eliminated when the commandkey.keyname file can not be created.
• When ERRMSG is in effect, command and function keys are now conditioned by the state of the option indicators at the last write.
• The SLNO(*VAR) keyword can now be used with the CLRL keyword.
• Two cursor problems have been fixed. Now, the cursor remains in the same location when the device is reinvited for a second read on a record. Also, the cursor is now positioned to the first input-capable field on a record.
• When using the CNTFLD keyword (for certain cases), the page no longer has missing rows.
• Input field size has been adjusted in two ways:
  • In the past, if the input fields were for only one or two characters, the browser drew the field too wide, which interfered with the alignment of other fields on the screen. The width of these fields is now overridden to a pixel width that is narrower.
  • For longer input fields, the field was not wide enough to allow all the characters to be shown at once. The width of these fields has been increased to alleviate this problem.
• Problems with the colour browser and the generation of user-defined styles in the Style Creation wizard have been fixed.
• The communication code will now correctly handle DBCS characters in iSeries object descriptions.
• Fields that extend beyond the edge of the screen will now wrap to the following line.
• Windows 98 can now properly handle the generation of command key recognition XML files.
• Focus is now set to wizard pages when they are first displayed.

New features

• Enhancements to the DSPF Source Selection page; a default push button has been added to process the Enter key correctly.
• New web settings now enable the use of "H" (hidden) fields, and let you customize client code and retrieve information from the browser without visual interference.
• Web settings now has support for copy, paste, cut, and delete operations for MLE or entry fields.
• WebFacing now supports the WDWTITLE keyword, with the following parameters: WDWTITLE([title-text] [*CENTER| *LEFT| *RIGHT]). The *TOP, *BOTTOM, and *COLOR parameters are not yet supported.
• Support for the DSPATR(SP) keyword.
• More error messages are available in the WAR file generation wizard.
• Mnemonic keys have been added to all wizard push buttons.
• The WebFacing Tool now generates a log event for the record when function key labels are detected and replaced with blanks.
• A "Use fixed height" check box has been added to the project and invocation properties. The feature enforces all rows to be a certain height to solve alignment problems, which is ideal for complex records and CLRL keyword use.
• Support for the CLRL keyword and CLRL window recognition. See "Variations from 5250 behaviour" below for more information about CLRL keyword usage.
• The Style Creation wizard now supports more IBM styles.
• You can now delete a user-defined style using the right-click menu on the Style Selection page.
• The WebFacing Tool supports DDS application help which includes support for the following help keywords:
  • HLPRCD
  • HLPARA
  • HLPSEQ
  • HLPBDY
  • HLPCLR
  At run-time, the help record that contains the help information is displayed in a new window when you press F1 or the help button.
  Note: Make sure to reconvert the display files to which you have added help.

Variations from 5250 behaviour

To make the browser version of your WebFaced application more intuitive, the WebFacing Tool implements the following variations:

• For the CLRL keyword:
  • CLRL records are supported as overlapping layers on the screen with opaque backgrounds. Although this is non-standard behaviour, it should be satisfactory in a browser environment. The background color of the CLRL layers will be the same as the background color of your selected style. You must use a style with an opaque background color otherwise the text in underlying records will show through and may be displayed in the same location as data from the overlapping layer. The WebFacing styles all use opaque backgrounds except for the Spiffy Blue style, which uses a transparent background.
  • The CLRL keyword is not yet supported for record formats with the WINDOW keyword and will be ignored.
  • Window Simulation with CLRL:
    • If the CLRL(*NO) or CLRL(nn) keywords are used to implement a window-like record in DDS, WebFacing will attempt to construct a window for that record format to support this common usage. For CLRL(nn), nn must be less than the record length for it to be recognized as a window.
    • In order for a record to be recognized as a window it must not have any fields outside of the rectangular area intended to be the window. A work-around for developers that have defined function key labels (or other nonessential constants) outside the window area, is to hide these fields using web settings in CODE Designer. WebFacing will respect these Web Settings and detect the rectangle properly.
    • The CLRL window recognition algorithm is based on commonly used CLRL window patterns. The following rules for the top and side borders of the simulated window must be true for the detection to succeed:
      1. For the top border, WebFacing checks for a constant field or an output field occupying the space from (first row, first column) to (first row, last column) and uses it as the window title. If a constant field is used, and the same character is used repeatedly from (first row, first column+1) to (first row, last column-1), the characters used to form the top border will not be used as a title and will simply be removed.
      2. For the side borders, WebFacing checks for a constant field from the record's second row to the second last row. The same string must be used for the left and right border for the simulated window. If this is true, the strings used to form the side borders will be removed.
      Note: The bottom border of the simulated window will not be altered because this row is sometimes used to display message information.

• Output-only DBCS fields that wrap to the following line might appear different than on the 5250; i.e., the splitting of field text into screen lines may be done at a different character positions. This is because the displayed length of a field in the WebFacing Tool is based on the number of Unicode characters in the field. On the 5250, however, the displayed length of the field is determined by the way the EBCDIC data is stored. For example :
  1. The 5250 considers each DBCS character to have a displayed length of 2 single-byte characters. The WebFacing tool considers each DBCS character to have a displayed length of 1, since it is a single Unicode character, just like any other character.
  2. On the 5250, shift out and shift in characters may increase the displayed length of a DBCS field. In the WebFacing Tool, these control characters have no effect on the displayed length.
  For these reasons, the browser is able to accommodate more DBCS characters on a line than the 5250 and in some cases wrapping will not even be necessary. In most cases, this will be an improvement to the readability of the screen.
  

Special instructions

• User level password protection is available in the WebFacing tool.
  If you would like to prompt users to enter a user ID and password when accessing a WebFacing application:
  1. In the Workbench IDE, right-click the project and select Properties.
  2. Click Project.
  3. Set the user ID and password to blank.
  4. Re-export the project.
  
  Now, when users access the application through a browser, they will be prompted for their User ID and password.
  Note: Their user ID and password must be valid on the system where the original iSeries application is running.
  
  
• UTF-8 support:

  The WebFacing Tool creates Web applications with multiple language support. Because languages use different character sets, data streams between the browser and WebSphere Application Server (WAS) are UTF-8 encoded. For WebFacing to work correctly, UTF-8 support must be configured in the WAS Administrative Console. See the steps below, pertaining to the version of WAS you are using, to configure UTF-8 support.
  Note:Only use WAS instances or servers configured for UTF-8 support with Web applications that use UTF-8 encoding. UTF-8 and non-UTF-8 applications cannot be run on the same instance or server.

• Configuring UTF-8 support in WAS 3.5
  
  1. Start the WebSphere Administrative Console.
  2. Drill down to the Default Server icon and in the Command line arguments field in the pane on the right, add the value:
     -Ddefault.client.encoding=UTF-8
  3. Click Apply.
  4. For this change to go into effect for your WebSphere applications, stop the Default Server and then restart it. To stop the server, right-click Default Server and select Stop. After this process has completed, right-click Default Server and select Start.

• Configuring UTF-8 support in WAS 4.0 Advanced Edition
  
  1. Start the WebSphere Administrative Console. Information on starting the Administrative Console is available at the WAS 4.0 AE documentation site at:
     http://publib.boulder.ibm.com/was400/40/AE/english/docs/index.html
     Follow the links for:
     Home > Site Map > Start the WebSphere Administrative Console on your workstation
  2. Expand the Nodes icon and drill down to Node name > Application Servers > Default Server.
  3. Select the JVM Settings tab then click the Advanced JVM Settings button. The Advanced JVM Settings dialog opens.
  4. In the Command line arguments field for the Advanced JVM Settings, add the value:
     -Dclient.encoding.override=UTF-8
  5. Click OK in the Advanced JVM Settings dialog and then click the Apply button under the JVM Settings tab.
  6. For this change to go into effect for your WebSphere applications, stop the Default Server and then restart it. To stop the server, right-click Default Server and select Stop. After this process has completed, right-click Default Server and select Start.
     
     
• Configuring UTF-8 support in WAS 4.0 Advanced Single Server Edition
  
  1. Start the WebSphere Administrative Console. Information on starting the Administrative Console is available at the WAS 4.0 AES documentation site at:
     http://publib.boulder.ibm.com/was400/40/AEs/english/docs/index.html
     Follow the links for:
     Home > Site Map > Starting the WebSphere Administrative Console on your workstation
  2. In the browser-based Administrative Console, expand the Nodes icon and drill down to Node name > Application Servers > Default Server > Process Definition > JVM Settings.
  3. In the JVM Settings page in the right frame, scroll down to the field Generic Command Line Arguments. Add the command line argument:
     -Dclient.encoding.override=UTF-8
  4. Click OK at the bottom of the JVM Settings page. If you receive a Configuration needs to be saved message and link at the top of the JVM Settings page, click the Configuration needs to be saved link to go to the Save Configuration page and then click Save.
  5. For this change to go into effect for your WebSphere applications, stop the application server and then restart it. The method for stopping and starting the application server can vary depending the platform you have installed WAS on. Refer to the WAS documentation for your platform for information on stopping and starting the application server. For iSeries server specific information, follow the links for:
     Home > Site Map > Starting and stopping WebSphere Application Server
     
     

• There are changes in the way the WebFacing Tool works with the VisualAge for Java WebSphere Test Environment. Refer to the VisualAge for Java WebSphere Test Environment section of the WebFacing Guide for the most recent information. In particular, refer to the sections:
  • Modifying the WFWTE property in the wfapp.properties file
  • Checking the language settings for your browser
  • Checking the .webapp file
  The WebFacing Guide can be found under the Components section of the Help Home Page. Access the Help Home Page by clicking:
  Start > Programs > IBM WebSphere Development Tools for iSeries > Documentation > Help Home Page.

Service Pack 4 -- November 2001

CODE component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

CODE Communications

• VisualAge RPG communications can now correctly determine when your server job terminates. In accordance with this fix, CODE auto-connect servers are now able to automatically reconnect when your server job ends, without having to shut down.
• When using the CODESRV GET command, you are now able to enter a directory name that contains an imbedded blank or is less than eight characters.
• STRCODE servers will no longer prompt for a current library if the current library setting is blank in the Communication Console (APAR #SE02987).
• EHLLAPI support, with the following dlls included:

  dll	description	additional information
  pcshll32.dll	Enables IBM Enhanced 32-bit EHLLAPI interfaces, using recent IBM-defined structures.	Use IBM Personal Communications or Client Access Express to install.
  ehlapi32.dll	Enables industry-standard 32-bit EHLLAPI interfaces, using older structures similar to 16-bit.	(No additional information.)
  whlapi32.dll	Enables industry-standard 32-bit WinHllapi interfaces, using older structures similar to 16-bit.	(No additional information.)
  EEHLLAPI.dll	The 16-bit dll version installed from Rumba.	This dll is no longer supported.

CODE Editor

• At times, CODE Editor would copy, delete or print, only one line when the user entered Cx, Dx, and LPx commands. This problem has been fixed (APAR #SE02860).
• The Open IFS is modified to accept server names with angle brackets, for example: "<system name>" (APAR #SE02644).

CODE Project Organizer

• Object filters will no longer indicate that objects are not found when you input a multi-generic filter with a complete object name and OBJTYPE(*) -- a condition meant to return all files, rather than none. (APAR #SE02626).
• French and German action files are no longer incorrectly translated; that is, the program no longer interprets all actions as local when some of them are remote. Complete the following steps in order to migrate the updates to the user versions of the action files in WDT400:
  1. Open the CODE Actions window.
  2. Click Import.
  3. In the Open dialog, specify the following location for imported files:
     x:\WDT400\SYSTEM
  4. Click OK.
  Review all actions contained in the Import Actions window, ensuring that all are selected for import as required. By default, all actions should be selected for import. If, however, you have modified an IBM shipped action, you need to manually indicate that the action must be imported; i.e., the list will be marked as user modified and will not be imported; therefore, you must select the import action manually. However, this will override any previous customization. To preserve customization, either rename the imported IBM actions, or edit the action command itself instead of using the action file shipped with the service pack. (APAR #SE02774 and APAR #SE02780.)

VisualAge RPG component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

• When in open-edit mode, a subfile cell will now maintain the background and foreground colors.
• You can now paste a value into the Entry Field part.
• Subfile column sorting can now handle a decimal symbol that is not necessarily "."; thus, the European decimal symbol (",") will no longer cause difficulties.
• VisualAge RPG communications can now correctly determine when your server job terminates. In accordance with this fix, CODE auto-connect servers are now able to automatically reconnect when your server job ends, without having to shut down.
• VisualAge RPG now allows you to leave blank spaces in a path when building to a Java version, and ensures that the ".properties" file is generated.
• The *Component part's MSGTEXT attribute now works correctly in the Java version.
• When you click Create in the Edit User Subroutines dialog, the user subroutine is no longer inserted in the wrong position.
• The Subfile part now allows you to paste a value into an open-edit cell.
• The Subfile part of the Java version is no longer missing the following attributes: COLBGMIX, COLBGCLR, COLFGMIX, and COLFGCLR.
• In an applet, the Subfile part's PAGESIZE attribute no longer returns an incorrect value.
• When building a project, you will no longer see the following error message:
  \WDT400\TEST\.. is locked
• You will no longer experience difficulties when building a large project with many action links.

Webfacing Tool component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following :

• Problems with the ERRMSG and ERRMSGID keywords have been fixed. After you update a screen using these keywords:
  • Response indicators for the CHANGE keyword are now triggered correctly.
  • Subfiles will display correctly and allow paging that is consistent with the 5250.
• For the SFLFOLD and SFLDROP keywords:
  • They now respect conditioning.
  • WebFacing Tool now presents only one command key for each keyword, even if you specify the same key for both SFLFOLD and SFLDROP.
  • The cursor position now determines which subfile these keywords will act upon.
  • WebFacing Tool now maintains the cursor position when you fold or truncate a subfile using the these keywords.
• The Project and Command Line property dialogs now let you submit a blank password field.
• The Property view now displays asterisks instead of an encrypted password.
• The MSGID, ERRMSGID, SFLMSGID, and CHKMSGID keywords now handle variant characters (i.e., @, #, and $ for CCSID 37) used in field-name parameters correctly. Also, records that contain an SFLMSGID keyword can now handle a variant character in the record name.
• Problems with variant characters (i.e @, #, and $ for CCSID 37) used in field-name parameters of keywords MSGID, ERRMSGID, SFLMSGID, and CHKMSGID have been resolved. Also, a problem with a variant character being used in the record name of a record that contains a SFLMSGID keyword has been fixed.
• Response indicators for keys retained using the RETKEY and RETCMDKEY keywords are now activated correctly.
• The field in the I/O Feedback area that contains the lowest subfile record number in the uppermost subfile on the screen will now be updated correctly.

New features

• Documentation updates
• New WebFacing Tool IDE -- Eclipse.
  • The Eclipse platform provides the core frameworks and services upon which all plug-in extensions are created. It also provides the runtime in which plug-ins are loaded, integrated, and executed. Thus, the platform enables tool developers to easily build and deliver integrated tools. The IDE gives you a common user interface model for working with tools, designed to run on multiple operating systems while providing seamless integration for development. Eclipse lets plug-in tools program to the portable Application Program Interface yet run unchanged on any of the supported operating systems. Thus, the architecture discovers these plug-ins and integrates them all into the new base environment, providing a standard user navigation model that lets you build integrated web and application development tooling projects. The tool also provides automatic migration of projects. See the WebFacing Tool documentation and eclipse.org for more information.
• WebFacing WAR file support and deployment for WebSphere Application Server version 4.0.
• For users of WAS 3.5, the trace subdirectory has moved from the root of the WebFacing application to web/WEB-INF/trace. This was done to provide compatibility with WAS 4.0 systems. See the WebFacing Tool documentation for assistance in setting up tracing.
• Support for DBCS applications such that the browser validates input of data in the 4 DBCS data types (J, E, O, and G), ensuring that DBCS is not entered in any of the other data types
• IDE now interprets DBCS DDS files for conversion
• Previously deployed web applications are compatible with the updated WebFacing server.
• Upon first conversion to Service Pack 4, WebFacing loads a new WFRun.jar file into your project. Additionally:
  • WebFacing Tool updates every PageBuilder.jsp in your associated project upon first conversion of a display file.
  • The "charset" value in your display file will change from "ISO-8859-1" to "UTF-8".
• You can configure the WebFacing server port number in the .invocation file or the WFAPP.properties file using the following keywords:

file	keyword
.invocation	{HostPort} = <portnumber>
wfapp.properties	{WFAppPortName} = <portnumber>

Note: The value in the invocation file overrides the value in the WFAPP file.

Special instructions

• When you create a WebSphere application with the WebSphere Administrative Console, the application must be enabled for JSP 1.1.
  Note: This is the default for WAS 4.0.
• WebFacing sends all form data back from the browser using the UTF-8 character encoding. Since most browsers do not indicate the encoding of the form data, you must configure the application server to expect the correct encoding. The expected client encoding is configured with a command line parameter in the administrative console. On the general page for your application server enter the appropriate value from the table below into the "Command line arguments" field. After entering the correct value click Apply, then stop and restart your application server. Below are the command line arguments:
  
  

  Version of WAS	Command line argument
  4.0	-Dclient.encoding.override=UTF-8
  3.5	-Ddefault.client.encoding=UTF-8

• There is a known problem with the the File Export wizard when using the File system option. The setting for the check box labeled "Create directory structure for files" is being ignored and behaves as if it is checked whether or not it actually is. This will cause a subdirectory with the same name as the project to be created under the directory specified for the export destination directory. Therefore, if prior to installing this service pack, you specified the following destination directory for a project called "My_Project" in the Export dialog:
  

  x:\QIBM\UserData\WebASAdv\default\hosts\\default_host\My_Project 

  you would now only need to specify:

x:\QIBM\UserData\WebASAdv\default\hosts\\default_host

WebSphere Studio for iSeries

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

• If you choose a server version higher than 3.0 in the Properties > Advanced > Application Server Version dialog of a WebSphere Studio project (from the right-click menu of the project), or if you alter the same setting in the Initial Project Settings tab from Tools > Preferences, the Servlet code generation process will no longer issue a warning message that deprecated codes will be produced.
• Selecting "None" as the editing code/word parameter for a numeric field of a SubfileDTC will no longer produce a runtime error.

New Features

• Support for WebSphere Application Server (WAS), version 4.0.
  • WebSphere Studio for iSeries is enhanced to generate an .EAR file so that projects can be deployed onto WAS version 4.0. While an EAR file can be deployed onto WAS 4.0, a WAR file can be deployed onto Apache Tomcat. To generate the EAR and WAR files, complete the following steps:
    1. While in the WebSphere Studio for iSeries IDE, right-click your project and select Create Web Archive file.
    2. In the resulting dialog, click create next to the Web Configuration Descriptor filename field if this field is empty.
    3. Click create on the bottom of the dialog and then click ok in the next dialog.
    4. A Create Web Archive file dialog will prompt you to choose a location to save the .WAR file. Choose either a local location, or a location on a mapped IFS drive, and then click Save. This will initiate a Create an EAR file dialog, asking you where the created WAR file is and where to put the generated EAR file.
    5. Use the Select buttons to navigate to the newly created WAR file and to where you would like to place the EAR file.
    6. Transfer the generated EAR file to your target iSeries machine, if the file is not already generated to the target machine's IFS location.
    7. Use the WAS administrative process to deploy the .EAR file.
    Important note: Make sure to specify the same name for both your .EAR and .WAR file.

Service Pack 3 -- October 2001

CODE component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

CODE Communications

• When entering a blank user name and password in the logon dialog, the user is no longer denied server access, but is now prompted for a correct user ID and password.
• Member lists from hosts that include the text description that contains DBCS will no longer terminate before the CODE tool (i.e., Open dialog, CODE Project Organizer) displays the complete list (APAR #SE02216).
• When connecting to a V5R1M0 host that is missing PTF SI01056, error message EVF4020E correctly indicates that PTF SI01056 and not SE01056 should be applied (APAR #SE02404).
• Random problems where saving files caused CODE Editor to freeze and the progress dialog to never be dismissed, have been fixed.
• When disconnecting and reconnecting modem connections, CODE communications will now be able to recover.
• Connecting to V5R1M0 hosts where the user portion of the library list exceeds 15 libraries will no longer abort the connection.
• When no servers are defined, the error log will no longer displays the following message: evfCons.java:ccGetCODEServerDftLocalList:Unexpected error. java.lang.NullPointerException.
• When the Communications Daemon automatically starts, the icon no longer appears in the tool tray before initialization of all communication settings. CODE has also fixed the problem where on slower machines, some communication requests occurred before initialization completed.
• A blank entry in the Current library field in the Communication Properties window will no longer cause the CHGCURLIB command to be prompted on the host for STRCODE servers.

CODE Designer

• When cutting and pasting fields, CODE Designer will now paste fields in absolute records at the cursor position rather than one line lower (APAR #SE02627).
• The DDS verifies in CODE Designer no longer gives an error for the following fields: date, time, time stamp. Additionally, the Designer will no longer drop the field source (APAR #SE02654).

CODE Program Generator

• On the Generation page of the CRTBNDCL compile dialog in CODE Program Generator, the Activation group field now allows ten characters, rather than seven (APAR #SE02403).

CODE Project Organizer

• Clicking the date column field in the file list now sorts properly by date rather than alphabetically (APAR #SE02411).
• When issuing an action against a large number of items in the file list, the results in the monitor window are no longer truncated (APAR #SE02593).

ILE RPG

• C-Specifications containing expressions that are continued on more than one line will no longer incorrectly issue a RNF5272E message. This was a syntax error (APAR #SE02399).
• The extended factor 2 prompt will no longer display when using the following fixed form operation codes: DOUxx, DOWxx, IFxx, WHENxx, FORCE.
• When converting the RPGLE source using Action > Convert all to C Free-Form, the last source record is no longer lost.

New Features

• CODE Communications has added shutdown capability to auto-connect servers. Shutdown menu items have been changed to shut down both STRCODE servers and auto-connect servers.
• When using SEU key behavior in CODE Editor -- for the RPGLE source type, the following F and P prefix commands have been added: F, Fxx, F?, IF, IFn, IFxx, IFxxn, IF?, IF?n, IP, IPxx, IP?, P, Pxx, P?. These commands function much like how they do in SEU with the following differences:
  • When using Pxx to prompt a line as a different specification type, the line will display in the specified prompt. When you press OK to commit the line, it will reformat to match the specified prompt. This is different from SEU and may cause unexpected changes. Use Edit > Undo if the changed line is not what you intended.
  • When using F on a compile-time data line, the "**" format line displays. When using P, the Full line prompt displays. The values in column six and seven are not considered, since they are not relevant in compile-time data. This is different from SEU, which uses column six and seven to determine which format line or prompt to use.
  • The following new format types/prompts have been added:
    • FK -- File description continuation
    • DK -- Definition continuation
    • IA -- Input record (AND/OR)
    • CC -- Extended factor 2 continuation
    • CF -- Free form calculation
    • OA -- Output record (AND/OR)
    • PC -- Output field continuation
  Note: To process the prefix commands, either press Enter with the cursor in the prefix area, or use Alt+Enter. To remove the format lines, press F5 or select Actions > Delete Messages.

VisualAge RPG component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

• VisualAge RPG now returns an error message if you try to open a project from a shared drive when another user is already working with the project.
• The Java version of Subfile scrollbars are no longer in the wrong position.
• In the Windows runtime of VisualAge RPG, the separator style menu item now works.
• The GUI builder no longer freezes when you right-click on menu items on the BiDirectional enabled system.
• Subfile open-editing now allows input of ".NNN" in a numeric field instead of only "0.NNN."
• If zoned decimal subfields in externally-described data structures have the same name as a GUI part name, they will no longer be incorrectly stored in packed decimal format.
• The Java runtime of VisualAge RPG no longer fires the SELECT event when adding an item to an empty combobox.
• The VARPG runtime will no longer malfunction if you enter value in a numeric entry field with edit-code when auto-select is active.

New features

The following new features have been added to VisualAge RPG.

• Support for MS Access "Yes/No" data type.
  • Description: Allows you to specify properties of a numeric data type.
  • Type: numeric, i.e., 1=yes, 0=no
  • source code:

        DYesNo     S    1S    0        
        *Bind column: YESNO
        C    'ODBC'  SetAtr   16       'Column'
        C    'ODBC'  SetAtr   1        'BufferLen'
        C    'ODBC'  SetAtr   0        'BufferDec'
        C    'ODBC'  SetAtr   0        'BufferType'
        C            Eval     P016=%Addr(YESNO)
        C    'ODBC'  SetAtr   P016     'BufferPtr'

• new attribute: DELETERCD
  • Description: Deletes records, letting you specify an individual record or all records.
  • Part: Container
  • Type: numeric
  • Gettable/Settable: Settable only
  • Allowed Values: 0 deletes every record and sets the NextID to 1; N deletes the N^th record.

• new attribute: RETURNVAL
  • Description: Lets you use this value to obtain the return value of a method call.
  • Part: ActiveX
  • Type: string
  • Gettable/Settable: Gettable only
  • Special Instructions: You must call the method of an ActiveX part before trying to obtain the return value with RETURNVAL. Use the following code when you are trying to get the return value of an ActiveX method call:

    C    EVAL   %setatr(%window:'ocxname':'method')='ReturnPtr'
    C    EVAL    ptrstr=%getatr(%window:'ocxname':'ReturnVal')

  _____i.e., ptrstr=ocxname.ReturnPtr():

• new attribute: OCXPROPIDX
  • part: ActiveX
  • type: string
  • Gettable/Settable: Settable only
  • To GET or SET an element of an array type property:
    1. Set OCXPROP to the property name.
    2. Set OCXPROPIDX to the index value in the array.
    3. Set/Get OCXVALUE
  • Example of code to set the first element of property "DataFiles" to "C:\Temp\sample.mdb"

          C      EVAL  %SETATR('WINNEWJOB':ocxname:'OCXPROP')='DataFiles'          
          C      EVAL  %SETATR('WINNEWJOB':ocxname:'OCXPROPIDX')='0' 
          C      EVAL  %SETATR('WINNEWJOB':ocxname:'OCXVALUE')='C:\Temp\sample.mdb'

  • To set an element of a multi-dimensional property, users need to pass the index values in a string with only digits 0 - 9. Spaces are allowed. For example: "2 4 7". Example of code:

          C      EVAL  %SETATR('WINNEWJOB':ocxname:'OCXPROP')='3DImageData'  
          C      EVAL  %SETATR('WINNEWJOB':ocxname:'OCXPROPIDX')='2 4 7' 
          C      EVAL  %SETATR('WINNEWJOB':ocxname:'OCXVALUE')='200'

    Note: In the information tab of the properties dialog box for ActiveX, string arrays appear as thus: "String[]" or "String [][]". The number of squares indicates the number of dimensions for the array, i.e., two squares indicates two dimensions.

• The Windows version of Image part now supports the following JPEG formats:
  • Baseline
  • Extended sequential, Huffman
  • Progressive, Huffman

WebFacing Tool component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

• The application area is now more compact.
• The setting of response indicators has been revisited and made more faithful to 5250 behavior.
• If keywords such as WINDOW and RTNCSRLOC reference a field and that field has special characters in it, the field will now be found at run time.
• You can now press the Enter key on the browser to simulate pressing the 5250 ENTER key, even if there are no input-capable fields on the browser
• Fields in subfiles with the VALUES keyword and DSPATR(ND) or DSPATR(PR) could previously be altered, but this has now been fixed.
• Screens with multiple WINDOWs showing perform better now.
• Fixed the problem where a display file name was specified on a read operation instead of a record format name. (See "Restrictions.")
• Field alignment problems are much better; i.e., closer to what you see on the 5250 screen.
• SFLMSGID errors will no longer appear when rolling up or down.
• VALUEs keyword fields will no longer be combo-boxes that disrupt the display of WINDOWs. They will now have pop-up radio buttons when you more your cursor over them.
• The subtitle scrollbar will not show up if there is less data than the SFLPAG.
• Suspended records from a previous DSPFs will no longer be cleared. (This problem was causing some WINDOW backgrounds to be mistakenly cleared.)
• WebFacing now has better error handling when you are unable launch conversion due to incorrect setup.
• The IO Feedback area should now receive the correct hex codes for the Roll Up and Roll Down AID keys.
• Single quotation marks in application data will no longer cause problems.
• If exceptions occur when obtaining object or members lists from the AS/400, WebFacing displays an error dialog. In addition, the IDE lists detailed messages in an error log file, i.e., the log file located in Webfacing\itp\.metadata.
• WebFacing has fixed the problem with combo boxes and fly-over radio buttons when you use the user-defined generated styles.
• When the "Inherit foreground font" checkbox is selected in the Style wizard's Window Page, WebFacing will no longer produce an unrecoverable error.
• Minor fixes in the Pagebuilder.jsp.

DDS keywords now supported

• EDTMSK
• FRCDTA
• MDTOFF
• RETCMDKEY (See "Restrictions")
• RETKEY
• RMVWDW
• SFLCSRRRN
• SLNO (*VAR)

New features

• Documentation updates
• Support for 0 as SFLROLVAL in a hidden field
• Records written immediately due to either a FRCDTA or a DSPF that is compiled with DFTWRT(*NO) will now show up right away.
• You can invoke the Style wizard from the New > Other... wizard page.
• A Cancel button is available during project conversion. However, all files converted before cancellation will be populated in the IDE.
• WebFacing has added user level password protection:
  If you would like to prompt users to enter a User ID and password when accessing a WebFacing application, edit your project's wfapp.properties file. This file is located in the root folder of your Web application.
  1. On your workstation, look for the file in a path similar to: X:\WDT400\Webfacing\itp\<mywebfacingproject>\wfapp.properties.
  2. Look in wfapp.properties for the lines that begin with "{WFAppHostUID} = <userid>" and
     "{WFAppHostPWD} = password". These lines will have the ID and encrypted password you used when converting your source members.
  3. Edit this file so that each of these lines is blank after the "=" sign. For example, change:
     • "{WFAppHostUID} = <myuserid>" to "{WFAppHostUID}= " and
     • "{WFAppHostPWD} = <myencryptedpassword>" to "{WFAppHostPWD}= "
  4. Once you make these changes, upload the file to your Web application's root directory in the application server and then restart your Web application in the WebSphere Administrative Console.
  Now, when users access the application through a browser, they will be prompted for their User ID and password.
  Note: Their ID and password must be valid on the system where the original iSeries application is running.

Restrictions

• When BLANKS is specified on a field on a subfile record and the field is written to the screen as blank, but no fields on subfile record are changed, the BLANKS response indicator will not be turned on. On the 5250, however, the response indicator would be turned on. This is only a problem if (1), BLANKS is specified on a subfile field and (2), no fields in the subfile record are changed.
• Currently, the RETKEY and RETCMDKEY keywords specified on a record allow the current active keys to be retained on the screen when the record is written. However, the response indicators specified on the retained keys will not be communicated back to the RPG program as they would on the 5250.
• WebFacing does not support the reading of a display file (with ASSUME specified) right after the display file is opened.

Service Pack 2 -- July 2001

Code component

List of fixes

This service pack is a cumulative service pack containing all fixes from earlier service packs, plus the following fixes:

ILE RPG

• When verifying an ILE RPG source member and a nested copy member (level 2 or deeper) is open in the editor, CODE Editor will no longer crash.
• When verifying an ILE RPG source member containing H-specs which specify OPTION(*SRCSTMT) or OPTION(*SECLVL), CODE Editor will no longer crash.
• ILE RPG procedures will now appear in the navigator.
• The ILE RPG listing file generated by the program verifier will be opened in read-only mode. The EVF1165W "Changes are pending" message will no longer appear. 

CODE Designer

• Handles stop-zero-suppress character when it is the first in an editword
• Updates how indicators are recognized for some keywords
• Fixes how the verify listing is opened in the editor for the DDS verifier
• Fixes a crash when changing record window parms when using two display sizes
• Fixes a crash with the create and rename of groups
• Adds in missing keywords in the keyword list for date, time, timestamp fields

 CODE Designer WebSettings (used by WebFacing Tool)

• Uses output-capable field in create graphic and create hyperlink
• Selects the first field as default for hyperlink
• Web settings are saved after the last panel is deleted
• Data in entry field is now caught when switching settings
• New line "\r\n" is changed into "\\r\\n" when writing %%WB comment
• Shows field visibility setting when switching back from 'H' to 'B', 'I' o 'O' types
• Adds or removes web setting page when CA/CF keys are added or rem
• Updates command key label determination
• Copy graphic file to web image directory
• Adds web setting to allow creating dynamic graphic definition
• Height for graphic is now shown
• Conditioning field web setting property page fixed
• Image border for websetting fixed

WebFacing Tool component

List of fixes

This service pack is cumulative, containing all fixes from earlier service packs plus the following:

• fixes to subfile scrolling and the SFLEND keyword
• writing records from multiple display files using ASSUME, KEEP, and RSTDSP

DDS keywords now supported

• CHKMSGID
• DATE
• DSPATR(MDT)
• ERRMSGID
• PROTECT
• SFLMSGID
• SFLMSG
• SYSNAME
• TIME
• USER

New features

• CODE Designer Web Settings
• CL parameter passing
• System menu support for menus that use DDS display files
• Documentation updates

Special Instructions

• Sometimes after a service pack update is applied to the WebFacing Tool and a new project is exported to the WebSphere Application Server where existing WebFacing projects have already been deployed, there can be a ClassNotFoundException when the converted application is run. The error occurs because the WebFacing run-time file, WFRun.jar, is cached by the WebSphere Application Server causing the new version not to be loaded. To fix this problem, stop then start the application server. Note that restarting the Web application itself without restarting the application server may not fix this problem.
• WebFacing projects created with the GA or Service Pack 1 level of WebFacing need to be re-created and re-converted to work with Service Pack 2.

Base Version

This document contains prerequisite information for the WebSphere Development Tools for iSeries product. In addition, it includes any 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.

The Release Notes document describes product components, detailed system requirements, and migration scenarios, as well as the VisualAge(R) for Java(TM) Version 3.5.3 Enterprise Toolkit for AS/400(R) Release Notes.

Documentation changes

Important: How to selectively install or remove components
The Modify wizard allows you to add or remove components. The page with the text "Select components to be modified" should include this description:

To add a missing component, ensure its check box is selected.
To remove a component, clear its check box.

A complete description is in Installation Notes in section How to add or remove components after installation.

VisualAge RPG (VARPG)

For V5.1, the VARPG GUI Designer help has been updated to include new help information for:

• The SelPending event
• Using string Aliases for message IDs
• Communication console choice from the GUI Designer menu

No other updates have been made to this online help.

The HTML and PDF versions of the VARPG publications have not been updated. As such, they contain the following inaccuracies:

• References to the now obsolete "Installing VisualAge RPG and CODE/400 for AS/400", SC09-2446 publication.
• References to previous product names
• The now obsolete "What's New this Release" section.

The DLL and LINKAGE keywords are not in the list of keywords for the following Language Sensitive help:

• Definition of Prototype or Procedure Interface
• Prototype and Procedure Interface Keywords
• Definition of Prototyped Parameter
• Prototyped Parameter Keywords

These keywords are also not in Table 33. Prototype, Procedure Interface, and Parameter Keywords in the VisualAge RPG Language Reference publication.

The following Part attributes have been added to VisualAge RPG.

Part	Attribute	Type	Description	Valid Operation Code
Subfile	EditColumn	numeric	Returns the column number of the cell that is opened for editing.	getatr
	EditIndex	numeric	Returns the row number of the cell that is opened for editing.	getatr
	EditText	text	Returns the currently edited text of the cell that is being edited. Returns empty string if no cell is opened for editing.	getatr
	The following Subfile attributes are used for changing the order in which Subfile data columns are displayed. "data columns" refers to the order of the columns as specified at design time in the Field List page of the properties Notebook (a "data column" is specified with the ColNumber attribute). "view columns" refers to the order of the columns as they are displayed (a "view column" is specified with the new ViewColumn attribute). By default, the data columns and view columns are the same. If a user moves the display position of a column, only view columns change.
	MapViewCol	numeric	When set to 1, this will display the subfile with columns re-arranged according to attributes ColNumber and ViewColumn. ColNumber is set to the data column number to move and ViewColumn is set to the destination column. Note that columns are not switched. View columns are shifted right or left as needed.	setatr
	ViewColumn	numeric	Set to the MapViewCol destination column.	setatr
	Example of code to map data column 2 to view column 4			C Eval %Setatr('FRA000000B':'SUBF':'ColNumber')=2 C Eval %Setatr('FRA000000B':'SUBF':'ViewColumn')=4 C Eval %Setatr('FRA000000B':'SUBF':'MapViewCol')=1
	DColFRVCol	numeric	Returns the data column that corresponds to the column specified by ViewColumn.	getatr
	Example of code to get the data column of view column 4			C Eval %Setatr('WIN':'SBF':'ViewColumn')=4 C Eval DataCol4 = %Getatr('WIN':'SBF':'DCOLFRVCOL')
	VColFRDCol	numeric	Returns the view column that corresponds to the column specified by ColNumber.	getatr
	Example of code to get the view column of data column 4			C Eval %Setatr('WIN':'SBF':'ColNumber')=4 C Eval ViewCol4 = %Getatr('WIN':'SBF':'VCOLFRDCOL')
	SortAsc	numeric	Set to a data column for ascending sort of subfile data.	setatr
	Example of code to sort the 3rd column ascending			C Eval %Setatr('WIN':'SBF':'SortAsc')=3
	SortDesc	numeric	Set to a data column for descending sort of subfile data.	setatr
	Example of code to sort the 3rd column descending			C Eval %Setatr('WIN':'SBF':'SortDesc')=3
Window	PrintAsIs	text	Prints the image and maintains the aspect ratio.	setatr
Image	PrintAsIs	text	Prints the image and maintains the aspect ratio.	setatr
Static-text	DropValue	numeric	Set to 1 to allow the label value to be changed by a drop operation. Set to 0 to prevent the value from changing after a drop. The default is 1. For example, a static-text part has a label "Send Mail" and users are instructed to drag and drop an e-mail address onto the label to start a dialog to send e-mail. Set DropValue to 0 so that the label does not change to the e-mail address.	setatr
Notebook Page	OnTop	numeric	Set to 1 to change the specified page into the current page. Previously, users set the "PageNumber" of a notebook part to be N in order to make the N-th page the current page. This method can cause confusion when a page has been set to invisible because the runtime will delete the page from the notebook part. (When the page is set to visible again, the runtime will add it back into the notebook.) For example, if the following code is executed: C EVAL %SetAtr('frame':'page3':'visible')=0 C EVAL %SetAtr('frame':'notebook':'PageNumber')=3 then the current page is the 4th page (which is now the 3rd because the original 3rd page has been deleted). Users can now use this line to set the 4th page the current page: C EVAL %SetAtr('frame':'page4':'OnTop')=1 Without using the index number, it is clearer which page is the current one. GETATR can be used to get the value of the OnTop attribute of a notebook page. It will return 1 if the page is the current page, otherwise it will return 0.	setatr getatr

The following Part events have been added to VisualAge RPG.

 C     NBP_1         BEGACT    SELPENDING    FRA_1
 C                   if        %getatr('FRA_1':'cusno':'text')=*blank
 C     *msg0001      dsply                   rc1               9 0      Display an error message;
 C                   eval      RC='*NODEFAULT  '
 C                   else
 C                   eval      RC='*DEFAULT    '
 C                   endif
 C                   ENDACT    RC

WebSphere Studio for iSeries

For information about prerequisite information and limitations specific to the IBM WebSphere Studio for iSeries, please refer to the WebSphere Studio README and README 3.5 FixPack 2 files. These notes can be viewed from the Windows Start Menu by selecting Programs> IBM WebSphere Development Tools for iSeries> IBM WebSphere Studio for iSeries.

About BiDi support
Each DTC in WebSphere Studio for iSeries now has a directionality attribute property that specifies direction of text. This property is in the General page of the control properties. The choices are:

LTR	Text direction is Left to Right
RTL	Text direction is Right to Left
NONE	Text direction is the default for the language

In addition, Subfile also has the 'directionality' attribute for each field under the'Fields Properties' page. The 'directionality' attribute under 'General' property page of Subfile defines how the columns/fields are arranged. The 'directionality' attribute under 'Fields Properties' property page defines how the text of the field is rendered.

In the Program Call Definition page of the Web Interactions Wizard, a new attribute bidistringtype, has been added. The choices are described below.

String Type	Type of text	Orientation	Symmetric swapping	Numeral shape	Text shapes
Default	The default string type for non BiDi data (LTR)
ST4	Visual	LTR	No	Nominal	Shaped
ST5	Implicit	LTR	Yes	Nominal	Nominal
ST6	Implicit	RTL	Yes	Nominal	Nominal
ST7	Visual	Contextual LTR	No	Nominal	Nominal
ST8	Visual	RTL	No	Nominal	Shaped
ST9	Visual	RTL	Yes	Nominal	Shaped
ST10	Implicit	Contextual LTR	Yes	Nominal	Nominal
ST11	Implicit	Contextual LTR	Yes	Nominal	Nominal

Note: Each CCSID has a default CDRA string type which defines a set of BiDi flags. When using these constants while performing conversions on BiDi strings, the parameter string type should always be either ST5 (LTR), ST6 (RTL), ST10 (Contextual LTR), or ST11 (Contextual RTL).

About two new fields
The first page of the Publishing Wizard has two new fields, WAS application server name and WAS servlet engine name. They have default values Wdt400AppServer and Wdt400ServletEngine that were previously hard coded.

About a field label change
The first page of the Publishing Wizard has a field labeled WAS Node name that was previously labeled XML node name. When specifying the WAS node name in the publishing wizard, use the node name you see in the administrative console.

Distributed Debugger and Object Level Trace

For information about prerequisite information and limitations specific to the IBM Distributed Debugger and Object Level Trace, please refer to the IBM Distributed Debugger and Object Level Trace Release Notes. These release notes can be viewed from the Windows Start Menu by selecting Programs> IBM WebSphere Development Tools for iSeries> IBM Distributed Debugger> README.

Known problems and workarounds

JDK notes
IBM's Java 2 Software Development Kit (J2SDK), Standard Edition v1.2.2 is included with this product. J2SDK includes JavaDocs. If you choose to use a different JDK, then it must be version 1.2 or higher to ensure the functionality of all pieces of Java code.

To use a different JDK, determine its JRE (Java Runtime Environment) home directory. In the CODE Editor, enter the command "SET GLOBAL.JREHOME x:\dir" where x:\dir is the JRE home directory. For example, "SET GLOBAL.JREHOME C:\JDK1.2\JRE".

If you plan to use the VisualAge RPG Media component, then install the Java Media Framework API.

VisualAge RPG GUI Designer and Java plug-in
Netscape Navigator and Microsoft's Internet Explorer do not currently support the same level of the J2SDK that VisualAge RPG uses. Therefore, applets created with the VisualAge RPG GUI Designer will not run directly with these browsers. To run VisualAge RPG applets in either of these browsers, you must have the Java Plug-in 1.2 installed (included with J2SDK). You can download the J2SDK from The Source for Java Technology Web page site at java.sun.com.

VisualAge RPG IFS names
Always use IFS directory names that are 1 to 8 characters long and have no spaces.

Problems with help
WebSphere Development Tools for iSeries uses the VisualAge Help System to deliver its online help information through your web browser. If you are having trouble launching, using, or searching the help, a problem solving document is available on the installation media. Put CD 1 or the DVD into its drive and use Windows Explorer to go to file x:\install\help\helpyyy\helpTroubleshooting.htm, where x is the drive letter, and yyy is your language code as shown below:

Language	Code	Language	Code	Language	Code	Language	Code	Language	Code
German	deu	English	enu	Spanish	esp	French	fre	Italian	ita
Japanese	jpn	Korean	kor	Portugese (Brazilian)	bra	Chinese (Simplified)	chs	Chinese (Traditional)	cht

After installation, the troubleshooting document is located in the product directory install\help.

WebSphere Studio for iSeries: Invoking subfile DTC API
The host service program, QGPL/QDTSSFL.SRVPGM, is required when the user host program needs to invoke the Websphere Studio for iSeries Subfile DTC API.

For installation:

1. A host ID with *ALLOBJ and *SAVSYS authorities is required for the installation steps.
2. Transfer the qdtssfl.sav savefile from your workstation to iSeries host QGPL library:
   1. Open a command prompt window
   2. Change to the source directory of qdtssdfl.sav, x:\WDT400\Studio35\Affinity where x:\WDT400 is the installation drive and directory of the product
   3. Enter these commands:
      ftp iSeriesHost
cd QGPL
binary
      put qdtssfl.sav QDTSSFL (assuming the QDTSSFL SAVFILE has been created, e.g. CRTSAVF FILE(QGPL/QDTSSFL))
3. Restore the QDTSSFL SRVPGM to QGPL library from the savefile:
   RSTOBJ OBJ(*ALL) SAVLIB(QGPL) DEV(*SAVF) SAVF(QGPL/QDTSSFL) RSTLIB(QGPL)

For development environment

1. Ensure the QGPL library is in the library list.
2. Bind the user program that makes the Subfile DTC API call to QGPL\QDTSSFL.SRVPGM

For Runtime environment, ensure the QGPL library is in the library list.

Notes for pre-V5.1 users:

1. All existing programs that are bound to the QSYS\QDTSSFL.SRVPGM have to be rebound to the new QGPL\QDTSSFL.SRVPGM.
2. After all the existing programs mentioned above have been rebound to the new SRVPGM, it is safe to remove the pre-V5.1 version of QDTSSFL.SRVPGM in QSYS library.

Using samples from Enterprise Toolkit for iSeries
In order to use samples provided in ET/400, you must restore the ADTSLAB library. For WebSphere Development Studio for iSeries V5R1, this library is located in QPDA.

Truncated display messages in CODE
Long messages in CODE Editor are sometimes truncated. Select the message and click Help or press F1 to see the entire message.

Browser problems

Certain components of WebSphere Development Tools require Internet Explorer as browser (see Software Requirements in Release Notes). Some Netscape problems are described below. Use Internet Explorer as your default browser to avoid these constraints and problems.

Netscape search in Windows 2000
There is a known problem with Netscape (versions 4.5 to 4.74 and possibly others) on some Windows 2000 machines that may make searching the online help extremely slow. When you submit a form from these versions of Netscape, the Netscape application uses most available processor cycles on your machine until a response is received from the remote system. This is not normally a problem when doing a remote search (e.g. on a website). However, because the product's search program is running on your own local machine, the fact that Netscape takes so much CPU time means that there is very little CPU time left over for the search program to perform its search. As a result, a search action that should return a result within a second may take several minutes on Windows 2000.

You can avoid this performance problem by selecting a different, non-Netscape window after each time you submit a search. This typically causes Netscape to stop using excessive CPU cycles while waiting for a response and search results are usually displayed within a second after doing this window switch.

Alternatively, you can use Microsoft Internet Explorer to view the help. The performance problem does not occur with this browser.

Netscape Navigator non-conformance
Netscape Navigator does not conform to standards for HTML 4. Web pages generated from WebSphere Studio for AS/400 and displayed by Netscape Navigator have DTC problems described in the following table. These problems do not occur when Internet Explorer is used.

Internet Explorer and help for AS/400 Toolbox for Java
Some Toolbox for Java help pages do not use the correct character set when displayed with Internet Explorer. The correct character sets for each language are:

Language		Name of character set
Simplified Chinese		Chinese Simplified(GB2312)
Traditional Chinese		Chinese Traditional(Big5)
Korean		Korean
Japanese		Japanese(Shift-JIS)

Use these steps in the browser window to select the correct character set for your language.

1. Click View on the menu bar to open a drop down list.
2. Put the cursor over Encoding to open a list of character sets.
   1. If the required character set is on this list, click on it.
   2. If the required character set is not listed, put the cursor over More to open a longer list of character sets.
   3. Click the required character set.

This must be done each time a help page is opened with an incorrect character set.

The Distributed Debugger
When you are debugging a Program or Service Program that was launched from a Web page generated by the WebSphere Studio for AS/400, Program completion or Service Program entry point completion does not cause the debugger to terminate. This prevents subsequent debug sessions. To be able to debug again, use the Halt button to close the outstanding debug session.

Object Level Trace
If Object Level Trace on Windows 95 or Windows 98 does not start, make sure that your environment space is set to the maximum value. In your CONFIG.SYS find the SHELL directive and make sure that the /E value is set to 32768. For example: SHELL=C:\WINDOWS\COMMAND.COM /p /E:32768

The OLT viewer will fail if environment files in directory DbgProf are corrupted. If this happens, delete all files in the DbgProf directory. There is a separate directory for each user. When the OLT viewer starts, it will create the files again.

The OLT viewer displays the error "Cannot open input stream for dertrdfl." when it is started the first time or after environment files in directory DbgProf are deleted. This error does not affect how the OLT viewer performs.

Norton AntiVirus
If Norton AntiVirus is installed on a Windows 98 machine and any parts of WebSphere Development Tools, such as Debugger or Object Level Trace, do not function, then disable Norton AntiVirus and try again.

Other sources of information

Visit our World Wide Web pages at:

ibm.com/software/ad/wdt400/ Click Support, then select an item under Support Downloads for Web Updates.

You can also get to these pages by following the links from the IBM Software home page ibm.com/software

The Redpaper REDP0503 provides a excellent overview of this product. Go to the Redbooks site, click Redpapers in the left frame and click the title "IBM WebSphere Development Tools for AS/400: An Introduction". You will see an abstract of the document. Click View Online to read a PDF version of the paper.

Follow the newsgroups and post your questions:

News server:

news.software.ibm.com

Suggested newsgroups:

ibm.software.code400

ibm.software.vajava

ibm.software.varpg

ibm.software.websphere.studio400

How to find your License Agreement

License Agreement files for this product are in the subdirectory license in the root product directory.

Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

Department 870
8200 Warden Avenue
Markham, Ontario L6G 1C7
Canada

Such information may be available, subject to appropriate terms and conditions, including in some cases payment of a fee.

The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us.

Programming interface information

This documentation describes General-Use Programming Interface and Associated Guidance Information provided by IBM WebSphere Development Tools for iSeries.

Trademarks and service marks

The following terms are trademarks or registered trademarks of the International Business Machines Corporation in the United States or other countries or both:

AIX AIXwindows AS/400 AS/400e

IBM Integrated Language Environment iSeries

Operating System/400 OS/400

RPG/400 VisualAge WebSphere

InstallShield is a trademark of InstallShield Corporation.

Intel and Pentium are registered trademarks of Intel Corporation.

Java and all Java-based trademarks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries.

Netscape Navigator is a trademark of Netscape Communications Corporation.

ActiveX, Microsoft, SourceSafe, Visual C++, Visual SourceSafe, Windows, Windows NT, Win32, Win32s and the Windows logo are trademarks or registered trademarks of Microsoft Corporation in the United States, or other countries, or both.

Other company, product, and service names may be trademarks or service marks of others.