This document contains prerequisite information for the WebSphere Development Tools for AS/400 product. In addition, it includes any limitations of the product and information not included in the documentation.
Download and run service pack program V4R5M1S2.exe. Follow the instructions given by the the program.
Reboot your system after installing the service pack and before using the product.
Install the latest PTFs to your host system. PTF information can be found at ibm.com/software/ad/wdt400/support/ptfs.html
For more information, see the WebSphere Development Tools for iSeries Web site at ibm.com/software/ad/wdt400.
Note:
Service packs cannot be uninstalled.
Service Pack 2 includes fixes and changes described below. It also includes all fixes and changes originally provided in Service Pack 1, described further below under ReadMe for Service Pack 1.
Changes to VA RPG
Zoned decimal subfields in externally-described data structures are now correctly defined when a GUI part has the same name as the subfield.
Changes to CODE
CODE is now enabled to work with V5R1M0 hosts. Host PTF SI01056 is required in conjunction with this service pack.
When the host job has a CCSID for which the translation table is not shipped with the product, communications now downloads the table to the correct directory and no longer terminates the connection.
When a failed compile occurs and when prompted to look at the command shell, the default button for compile completion messages will now be No instead of Yes.
When CODE communications retrieves list of fields where a field has 10 characters, the calling application (which can include CODESRV, Verifies and the FIELDS macro in CODE Editor) no longer crashes and will return the correct data.
Communication Console Properties now appears, regardless of whether or not a JDK is installed.
Adding libraries to the Library List using server *ALL in Communication Properties Window now works.
The CODE Actions window now appears correctly on Windows 98 machines.
The Activation Group field in the CRTBNDCL compile option dialog now allows the correct number of characters (10).
The Highlight Line macro no longer jumps to the first column of a blank line when pressing the up or down arrow.
The Highlight Line macro no longer impedes use of the auto-indent feature.
The change button is now enabled when a user modifies the password fields in the Communication Properties window.
When using the recently opened file list to open a member in CODE Editor on an auto-connect server and the server is not active, the connection is automatically initiated and the user no longer receives a "Server not found or unavailable" message.
When installing on Windows 2000 as administrator, and using the product as a different user, dialogs (such as the CODE Editor's New dialog) no longer cause the product to hang.
Requests for SQL compiles with *EVENTF option and debug option *ALL now compile source twice: once with the *EVENTF option and once with DEBUG(*ALL) , thus circumventing the host SQL compiler problem which makes these options mutually exclusive.
The Filter menu now appears correctly in CODE Project Organizer on Windows 95 and 98 machines.
The MATCH macro (Alt-M) now works correctly with RPG CAS statements.
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 message EVF1165W "Changes are pending" will no longer appear.
When verifying a source member and a nested copy member (level 2 or deeper) is open in the editor, CODE Editor no longer crashes.
Note: Service Pack 2 includes all of the changes originally included in Service Pack 1, described below.
This document briefly describes service pack 1 changes.
Before you apply Service Pack 1, complete these steps to unlock all files to be replaced.
- Make sure that no WebSphere Development Tools features are in use. For example, if the CODE editor is in use, be sure to save all files and to exit the editor.
- Open a Command Prompt window.
- Enter codeedit /cm exit
- Enter codedsu exit
- Enter x:\wdt400\system\evfctcpd /exit where x: is the drive where the product is located.
If any files are locked while applying Service Pack 1, you will see a message box with three buttons: Retry, Ignore, and Exit. Do not click Exit. Make sure that no WebSphere Development Tools features are in use and then click Retry. If the message box does not close, click Ignore. You will be asked to reboot at the end and to have the locked files replaced.
After applying Service Pack 1 and if you use VisualAge for RPG, you need to repackage and reinstall the Service Pack 1 runtime. If you do not reinstall the runtime and you install user applications generated from Service Pack 1, you will get an error message that you have not installed V4R5M1 runtime. This means you must reinstall the Service Pack 1 runtime.
Up-to-Date Information
For the most up-to-date information on the PTFs and Service Packs that are available for VARPG and CODE/400, go to the WDT/400 Web site and click the "Support" link. You can download the latest Service Pack from there.
Enabling Secure Java Applications
If you plan to deploy Java applications for use on the Web, please read this:
If you plan to deploy Java applications for use on the World Wide Web, note that only AS/400 systems running on the OS/400 V4R4 release, or later, support the Secure Sockets Layer (SSL) specification. Data flow between workstation applications and AS/400 servers running on earlier OS/400 versions will not be secure.
You must apply SERVICE PACK 1 so that all of the functions in this product are available for your use.
Changes to VisualAge(R) RPG
The problem where %Index and %ColNumber of SELECT events from subfile were not correctly set when triggered by using keyboard has been fixed.
The problem where setting the title label of a window will cause the static text parts on a notebook canvas to disappear has been fixed.
A new feature has been added to the graph part: using a ColorArea of 10, the background color of the legend area can be changed.
The GUI designer problem where a Slider part's font if set to something different than the system default cannot be persisted has been fixed.
The GUI designer running on Win2000 can use the new IBM Distributed Debugger.
The VARPG java runtime properly supports Java Extension Mechanism. If the varpg.jar is put into jre\lib\ext then both the generated java applet and java application will work correctly.
The VARPG application installation has changed so that if you install an application onto an older version of the runtime, you will receive an error message indicating that the runtime should be upgraded first before installing the application.
The packaging of a Java application will not mistakenly generate an error message saying there is not enough disk space.
The problem that in some cases SUBDUR incorrectly calculates the difference between two timestamps, when the result is in hours, has been fixed.
The problem of getting incorrect conversion results after moving a time field (format *USA) to a time field (*ISO), when time is between 12:00 am and 12:59 am, has been fixed.
The problem of getting a Host services internal error when running an installed VARPG application, when both the development and run-time environments are installed on the PC, has been fixed.
Changes to WebSphere Studio for AS/400
Different versions of WAS from Studio for AS/400 are correctly configured.
More detailed diagnostic messages from servlets are provided to help developers identify the potential sources of problems.
The Web Interaction Wizard allows the user to delete the last and only one field remaining of a program definition.
The Web Interaction Wizard properly handles I/O JSP residing in a subfolder.
The Web Interaction Wizard settings of both "Invalidate session" and "No host program call" will persist when creating a new Web interaction.
Changes to CODE/400
The problem with verifies with caching indicating that the server is busy, or causing the application to hang, has been fixed.
The Check PTF function in the Communications window will work for every server.
The CODE Project Organizer will not crash when changing anything on the properties page for a file in the file list.
In CODE Project Organizer, empty project menus will no longer appear.
In CODE Actions, the help button will work on the Import and Export dialogs.
In CODE Editor, setting the interactive debug server will work.
In CODE Editor, dialogs may be canceled when prompting for the debug server or setting the default debug server.
In CODE Editor, the "Code generated successfully" message from the RPG-to-Java Smartguide will appear in the appropriate language.
In CODE Editor, the Browse button on the Pre-defined Message page from the D-Specification Smartguide is enabled in the correct situations.
In CODE Editor, printouts will have the document name and page number at the top of the page if EXTRAS is enabled.
In Program Generator, submitting an interactive compile when an interactive compile is already in progress will not cause the Program Generator to crash.
In CODE Designer, using the Design Page to move fields so that they overlap is no longer prevented.
In CODE Designer, field conditioning is now shown correctly in the details view.
In CODE Designer, the Designer is now started correctly by the Editor.
Response files not supported
Always reboot when asked
Ignore msiexec.exe errors
Wait for completion dialog
Legal Information
General Rules
Do not use response files. They are not supported.
When you are asked if you want to reboot during the installation, always reply Yes. For some languages, the reboot dialog box has only Yes and No buttons. Always reply Yes.
The application msiexec.exe may produce the following error message: "The instruction at '...' referenced memory at '...'. The memory could not be 'read'." Click OK. This does not seem to adversely affect product installation.
Installation occasionally appears to be idle for up to 5 minutes. This is normal. Installation is complete only when the completion dialog appears.
Optional Components
There are four components that might be installed, depending on your needs and what you already have installed on your machine. The installation wizard prompts you for a component when necessary.
Component Included
with productReboot
necessaryInstallation type Comments MS JVM
(msjava.dll)Yes Yes Interactive - launched from installation Required for Studio to function. J2SDK 1.2.2 Yes No Interactive - launched from installation Required for all CODE/400 and VARPG functions to work. See JDK Notes. Netscape Communicator Yes (V4.7) on a
separate CDNo Manual install by selecting CD and directory for appropriate language Microsoft Internet Explorer No, obtain
from vendorYes Manual install of version 4.0 or higher If not installed, some major Studio functions will not work.
Web Browsers
Help has been tested on Netscape Navigator 4.7 and Internet Explorer 4 and higher.
After installation, ensure that your Web browsers bypass the proxy server for the server name "localhost".
Sometimes your browser cannot connect to the local web server httpdl.exe because it tries to locate the machine named "localhost" through a proxy server. This typically happens when your browser is set up for manual or automatic proxy configuration. If you use manual proxy configuration, you can modify your browser settings to prevent the browser from trying to resolve "localhost" through a proxy server. If you use automatic proxy configuration, you will need to ask the owner of your automatic proxy configuration file to add 127.0.0.1 as a proxy exception on the proxy server.
To determine whether your browser is set up for manual proxy configuration, and to add proxy overrides if required, follow these steps. These instructions are for the browser versions indicated; if you are using a different browser version, the steps may be different:
For Netscape 4.7:
- From within Netscape Communicator, select Edit - Preferences.
- Expand the Advanced entry in the left-hand pane by clicking on the + symbol to its left.
- Select the Proxies entry beneath Advanced.
The right-hand frame should indicate whether you are set up for automatic or manual proxy, or direct connection to the internet. If you are set up for manual proxy, continue this set of steps.
- If you use automatic proxy configuration, you will need to ask the owner of your automatic proxy configuration file to add 127.0.0.1 as a proxy exception on the proxy server.
- Select the View button beside Manual proxy configuration.
- Make sure that the addresses "localhost:49213" and "127.0.0.1" both appear in the list of proxy exceptions. Also, make sure that they are separated by a semicolon, not by a comma. Omit the quotation marks. Make any required changes and close any dialogs until you are back at the main browser window.
For Internet Explorer 5.0:
- From within Internet Explorer, select Tools - Internet Options.
- From the Connections tab, click on LAN Settings.
- If "Use a proxy server" is selected, you are probably set up for manual proxy configuration. Select Advanced.
- Ensure that the entries "localhost", "localhost:49213", and "127.0.0.1" all appear in the list of proxy exceptions, and make sure that they are separated by a semicolon, not a comma. Omit the quotation marks. Make any required changes and close any dialogs until you are back at the main browser window.
You should also update the file %SystemRoot%\system32\drivers\etc\hosts by adding the line:
127.0.0.1 localhost
if that line is not already present. If you change this value you may need to exit and restart your browser for the change to take effect.If you made any changes to browser configuration or the "...\etc\hosts" file, try reloading the help home page in your browser. If you still get errors trying to connect to locahost:49213, contact IBM support.
If your automatic proxy server is not accessible when you try to view the help, your browser may be unable to resolve localhost to the local address 127.0.0.1. You can temporarily solve this problem (while the proxy server is unavailable) by changing to direct connection to the Internet in step 4 (Netscape) or step 3 (Internet Explorer) above.
There is a known Netscape problem with Help Search function in Windows 2000. See Netscape in Windows 2000 for a description. To use Internet Explorer for help, launch Internet Explorer and select Yes to the message "Would you like to make it your default browser?". You must shut down and start up a product feature before the default browser change takes effect.
Installing on Windows 95 or Windows 98
If you receive an error message indicating that NetQuestion cannot be installed, it is because the PATH statement in your autoexec.bat file is longer than 200 characters. Shorten the PATH statement to correct this problem.
Windows 95 workstations must be version 4.00.950a or later and must have Internet Explorer 5 version 5.00.2314.1003 or later installed prior to installing this product.
Installing on Windows NT or Windows 2000
Due to a change to Microsoft Installer in the use of environment variables in Windows NT and 2000, follow these rules:
An Administrator must install the product on a workstation. This is a requirement in Windows 2000 and NT.
The same Administrator must ensure that the system variables described in the table below are set.
x: refers to the drive where the product is installed.
System variable name
must include this entry
CLASSPATH
x:\wdt400\java
HELP
x:\wdt400\help
IPF_PATH32
x:\wdt400\system
LOCPATH
x:\wdt400\system
PATH
x:\wdt400
The workstation must be rebooted after the variables are set.
Logon as a PowerUser or an Administrator to use the product.
Product Uninstall
To uninstall WebSphere Development Tools for AS/400, at a command prompt run wdt4imain.exe from the original installation source and use the Remove option in the Program Maintenance screen. Do not use the Windows Add/Remove Programs method and do not remove individual features manually because they will not be removed correctly. Always reboot your machine after uninstalling the product.
Uninstall or cancelling installation might leave unwanted files, directories and registry entries. To restore the workstation to its original state, perform the following procedure.
Start a browser and go to the WDT400 Support page.
Scroll down to "Support Downloads" and click on "Cleanup".
Download the self extracting zip file wdclean.exe into a workstation directory of your choice.
Use Windows Explorer to display the zip file and double click on the file to display the Self-Extractor dialog window.
Click on the Unzip button.
Click on OK.
Delete file wdclean.exe if it will not be needed again.
Determine the path to where the product is installed, for example, c:\wdt400. Be certain that the path is correct. Use only short names in the path.
Determine the operating system: one of win95, win98, winnt or win2k.
Open a Command Prompt window.
Enter command cd %temp% to access the unzipped files. If you unzipped to a specific directory, change to that directory.
Enter command cleanup [path] [OS] where [path] is the installation path and [OS] is the operating system.
When cleanup is complete, enter command finish to delete the cleanup files.
Close the Command Prompt window.
Product Modify
To change the features that are available in this product, insert installation CD 1 into the CD drive, type x:\wdt4imain.exe at a command prompt (where x: is the CD drive letter) and use the Modify option in the Program Maintenance screen. Do not use the Windows Add/Remove Programs method and do not remove individual features manually because they will not be removed correctly. Always reboot your machine after modifying the product.
Cancelling Installation
If you click on Cancel during the installation, uninstall the product as described in the Product Uninstall section to ensure all files are removed.
National Language Installation
The product will install one language according to the system locale. If you change the locale after the installation is complete, product features and help screens might not display the correct language. To change languages, completely uninstall the product as described in the Product Uninstall section, change the locale and then install the product again.
Installing Korean or Spanish
Installation in the Korean or Spanish language might result in two WebSphere Studio entries in the Start->Programs>IBM WebSphere Development Tools for AS400 menu. You can obtain a fix for this from the WDT/400 Web site, as follows.
Start a browser and go to the WDT400 Support page.
Scroll down to "Support Downloads" and click on "Merge".
Download the self extracting zip file wsmerge.exe into a workstation directory of your choice.
Use Windows Explorer to display the zip file and double click on the file to display the Self-Extractor dialog window.
Click on the Unzip button.
Click on OK.
Determine the operating system: one of win95, win98, winnt or win2k.
Open a Command Prompt window.
Enter command cd %temp% to access the unzipped files. If you unzipped to a specific directory, change to that directory.
Enter command wsmerge [OS] where [OS] is the operating system.
Close the Command Prompt window.
Changes to WebSphere Studio Guide for AS/400
Program names referenced in Package your Web application change as follows:
CALPKGWDTP to QUOPKGWDTP
CALUNPWDTP to QUOUNPWDTP
CALXMLCFG to QDTSXCFG
Changes to WebSphere Studio Design-time Controls
The online Help description is incomplete for Operand 1 and Operand 2 for the run-time attribute properties associated with the following WebSphere Studio for AS/400 Design-time Controls (DTCs): Checkbox, Combobox, Entryfield, Label, Listbox, Pushbutton, and Radiobutton.
The description for Operand 1 should read:
Enter the field name for the operand. The field can be any unique field name on the JSP page. The name specified must match the name of the output parameter that you specify on the Specify the input and output parameters for your ILE program page in the Web Interaction wizard.
The description for Operand 2 should read:
Enter a constant value for this operand for the comparison with operand 1. You can also enter a field name for operand 2 if you select Field name operand. The field can be any unique field name on the JSP page. The name specified must match the name of the output parameter that you specify on the Specify the input and output parameters for your ILE program page in the Web Interaction wizard.
Changes to WebSphere Studio Web Interaction Wizard
The Web Interaction Wizard provides a "Servlet URL" field to prepare a template of a hypertext link to call and pass data to servlets. The dialog "Specify a name for your Web interaction" shows the URL. The final box that shows the creation of the servlet allows changes to the data.
For example, the Servlet URL might appear as:
"/servlet/NuthinServlet?Custno=#1&Custna=#2"
If the placeholders "#1" and "#2" are replaced by "12345" and "Smith", then the equivalent call is:
"servlet/NuthinServlet with Custno=12345 and Custna=Smith".
Additions to VisualAge RPG
The following Part attributes have been added to VisualAge RPG.
Part Attribute Type Description Operation
CodesOperational
at run timeSubfile EditColumn numeric Returns the column number of the cell that is opened for editing. setatr
getatrno
yesEditIndex numeric Returns the row number of the cell that is opened for editing. setatr
getatrno
yesEditText text Returns the currently edited text of the cell that is being edited.
Returns empty string if no cell is opened for editing.setatr
getatrno
yesWindow PrintAsIs text Prints the image and maintains the aspect ratio. setatr
getatryes
noImage PrintAsIs text Prints the image and maintains the aspect ratio. setatr
getatryes
no
Help Overview Sample
The name of the Subfile API Service Program for the Subfile DTC has changed from SFLIBSRV to QDTSSFL.
This change affects the Help documentation found in:Overview
Getting Started with WebSphere Development Tools for AS/400
Creating Web Applications
Sample: Creating a Web Application using WebSphere Studio for AS/400.All descriptions that read ". . . API module SFLIBSRV" should read ". . . API service program QDTSSFL".
JDK Notes
IBM WebSphere Development Tools for AS/400 is shipped with IBM's Java 2 Software Development Kit (J2SDK), Standard Edition v1.2.2. 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".
When the J2SDK installation is complete, update your PATH and CLASSPATH environment system variable to include the appropriate J2SDK directory. This allows VARPG to use Java. For example, if you installed the J2SDK in directory x:\jdk12, then add the following information to your PATH variable: x:\jdk12\bin.
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), and the HTML Converter available from JavaSoft. You can download these by following the links from The Source for Java Technology Web page from Sun's Web site at sun.com. The HTML Converter allows you to convert the HTML page with your applet tag in order to use the Java Plug-in. The conversion creates an object tag that tells the Web browser to use the Java Plug-in instead of its own Java 2 Runtime Environment.
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.
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.
DTC type Appearance problems Events problems Attribute problems Entryfield Color and Background color defaults cannot be overridden. OnSelect, OnClick, OnDblClick, OnMouseOver, OnMouseDown, OnMouseUp, and OnMouseOut are not supported. The "alignment" attribute moves the entire field, not just the text.
The "readonly" attribute is not supported, but this problem can be fixed as follows:
- select the DTC
- display the Control Properties dialog box
- select the Event tab
- click the onFocus event
- enter "this.blur();" into the script box.Checkbox No problems OnChange is not supported. No problems Combobox Color and Background color defaults cannot be overridden.
Font is ignored.No problems No problems Listbox Color and Background color defaults cannot be overridden.
Font is ignored.No problems No problems MLE Color and Background color defaults cannot be overridden.
Font is ignored.
Text incorrectly wraps to next line.OnSelect is not supported. No problems Pushbutton Background color always appears as light grey. OnKeyPress, OnKeyUp, OnKeyDown, OnMouseOut, and OnMouseOver are not supported. No problems Radiobutton No problems OnMouseOut, OnMouseOver, OnKeyUp, OnKeyDown, OnKeyPress, and OnChange are not supported. No problems
Netscape 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.
Norton AntiVirus
If Norton AntiVirus is installed on a Windows 95 or 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.
Help does not work
After installation, if Help does not work because the browser does not start, then reconfigure the Help system. You do not need the installation CDs for the following procedure.
1. Determine the operating system YY of the workstation. YY is 95 for Windows 95 98 for Windows 98 NT for Windows NT 2K for Windows 2000 2. Determine the drive W where directory WDT400\help is located. W is the drive where the product is installed. 3. Determine the drive X where directory imnnq_YY is located. X is usually the drive where the product is installed. 4. Determine the language zz_ZZ that was installed. zz_ZZ is en_US for English fr_FR for French de_DE for German pt_BR for Brazilian Portugese it_IT for Italian es_ES for Spanish ko_KR for Korean ja_JP for Japanese zh_CN for Simplified Chinese zh_TW for Traditional Chinese 5. Open a Command Prompt window. 6. Change to drive X. Replace X and enter command: X: 7. Change directory to imnnq_YY. Replace YY and enter command: cd imnnq_YY 8. To remove the help system, replace X, YY, and zz_ZZ and enter this command: vahcfgw.exe remove /p va400 /f X:\imnnq_YY /l zz_ZZ 9. To restore the help system, replace W and zz_ZZ and enter this command: vahcfgw.exe install /w W:\wdt400\help /l zz_ZZ 10. Wait for Help reconfiguration to complete and then close the Command Prompt window.
Visit our World Wide Web pages at:
You can also get to these pages by following the links from the IBM Software home page:Follow the newsgroups and post your questions at:
News server:
news.software.ibm.com
Suggested newsgroups:
ibm.software.code400
ibm.software.vajava
ibm.software.varpg
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:
Director of Licensing
Intellectual Property & Licensing
International Business Machines Corporation
North Castle Drive, MD - NC119
Armonk, New York 10504-1785
U.S.A.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:
IBM Canada Ltd. Department 071
1150 Eglinton Avenue East
Toronto, Ontario M3C 1H7
CanadaSuch 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 AS/400.
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:
400
AFP
AIX
AIXwindows
APPN
Application System/400
AS/400
AS/400e
BookManager
C Set ++
C/400
CICS
CICS/400
CICS/ESA
COBOL/2
COBOL/400
Common User Access
CUA
DB2
GDDM
IBM
IBMLink
Integrated Language Environment
Language Environment
MQSeries
Network Station
Open Class
Operating System/2
Operating System/400
OS/2
OS/390
OS/400
POWER2
PowerPC
PROFS
RPG/400
RS/6000
S/390
SAA
SQL/400
System/36
System/38
VisualAge
VTAM
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.
Lotus, Lotus Notes and Domino are trademarks or registered trademarks of Lotus Development Corporation in the United States, or other countries, or both.
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.
UNIX is a registered trademark in the United States and other countries licensed exclusively through The Open Group.
Other company, product, and service names may be trademarks or service marks of others.