WebSphere(TM) Development Studio Client for iSeries(R)
V4.0 README file
This document contains prerequisite information
for the WebSphere Development Studio Client
for iSeries Version 4.0. In addition, it
includes any limitations of the product and
information not included in the documentation.
It is cumulative, containing all information
from the base release plus subsequent service
packs.
For more information, see the WebSphere Development Studio Client for
iSeries Web site at ibm.com/software/ad/wds400.
Note: Service packs cannot be uninstalled.
Table of Contents
Service Pack 4
Service Pack 3
Service Pack 2
Service Pack 1
Base release
Legal information
Service Pack 4 -- March, 2003
IBM WebFacing Tool
Notes
- An existing project needs to have at least one DDS member reconverted in
order to gain the updated runtime support provided by this service pack.
A new project will have this support automatically.
- Changed web application initialization parameters will only be picked up
when the web application is started.
List of fixes
- Fixed subfile visibility problem related to DDS keywords used for subfile
control
- Conversion no longer hangs when a hyperlink WebSetting has an '&' character
as a parameter separator
- Corrected the problem where the message line does not show up until the user moves the mouse or presses a key
- Fix for the WebSetting "insert into script" not working due to using delayed setAttr for implementing WebSettings in JavaScript
- Fixed JavaScript error when messages from CHKMSGID contain double quotes
- Fixed JavaScript error caused by a missing ID for empty rows generated
for subfiles with field selection
- Fixed JavaScript error when the ID used for row/column positioning of windows
is missing
- Cursor positioning and SFL page operation now work properly for PROTECT records
- Correct a problem with selection of fields at the beginning and end of
the tabbing order
- Support for response to SNDPGMMSG function. This support was introduced
in the following PTFs:
V5R1 PTFs: SI07975 and SI07976
V5R2 PTFs: SI08676 and SI08677
For the latest WebFacing PTF information, see the document:
http://www-1.ibm.com/support/docview.wss?rs=0&uid=swg27002213
- Fixed autotabbing problem with IME input method and DBCS fields. Validation of DBCS fields now done on keystroke or when IME data is committed.
- DBCS wrapped output fields are now wrapped and displayed properly
- Fix for the problem of error messages being cleared too soon
- JavaScript performance improvement for data validation on keystroke in SBCS fields
- Corrected the problem of a new Project display file not showing up in directory
- Fix problem with deleting CL command, DDS file, or UIM file folders in
WebFacing projects using pop-up menu
- The Style "Save as" dialog no longer crashes when there are no
user-defined styles in the "styles" directory.
- A field placed at position 1,1 with WebSettings no longer causes the JSP
content not to be generated.
Enhancements
CODE Designer
List of fixes
- Remove 50 character restriction in the GUI for the ERRMSG keyword
- Verifying an invalid CCSID no longer crashes the communications layer
- Fix for edit word formatting with leading zeros (corrected display length)
- Fix for an unexpected DDS7816 message (SFLLIN keyword not allowed when more than one row in record.)
- Loss of conditioning for the first field after a help spec no longer occurs
- Corrected problem with the Logical File verifier issuing DDS7975 when PFILE
not found
- The load/save dialogue is now dismissed when load or save is complete
- Preserve leading and trailing spaces in the VALUES keyword
- Corrected problem where REFFLD was not generated or modified correctly
- Records are no longer deleted if &field parameters are created and
deleted -- as in RTNCSRLOC
- Fix for crash when tabbing through SFLSIZ &field while Design Page
is visible
- Field names for starting line and position are now recognized in the WINDOW
properties dialog
- Fields can now be positioned on row 1 column 1 for records with WINDOW
and SLNO
- Properly constrain fields from being positioned on a window's message line
in the secondary display size
- Sizing a window on the design page in "Move in current display size
only" mode no longer causes errors in the validation of field positions
- It is possible to move a field on the design page so that it will be in
a different order with respect to the other fields in the two display sizes.
This used to cause an infinite loop when laying out subfile fields. Now,
the subfile fields will not be replicated until the fields are in the same
sorted order in both display sizes.
- %%TS timestamp comments now use the Windows user name rather than QUSER
when connected to the iSeries with an auto-connect server definition
- Fix for crash when modifying a field with a user-defined editcode through
the properties dialog
Service Pack 3 -- November, 2002
General notes
- The installation directories you use for
CODE, Distributed Debugger, and NetQuestion
cannot contain spaces. For example, you can
use c:\ibmdebug, but not c:\Program Files\ibmdebug
or c:\ibm debug.
iSeries development tools and the Remote
System Explorer
List of Fixes
- You can now download and edit files from
the V5R2 iSeries host using the workbench
LPEX editor.
- You no longer receive a "File system
error" when Editing files from a V5R2
iSeries host when using Development Studio
Client.
VisualAge RPG
List of fixes
- You no longer experience a JPEG image memory
leak when using the image part.
Enhancements
- You can now launch the VARPG GUI designer
from the workbench.
- The main application and its components can
now access the same ActiveX part.
IBM WebFacing Tool
List of fixes
- You no longer need to position the cursor
in the subfile area in order to page through
a subfile using the PgUp or PgDn keys. Paging
through a single line message subfile using
the PgUp or PgDn keys is now supported.
- Cursor positioning is now enabled for a named
output-only field defined with a blank
entry
for usage (position 38).
- The cursor is changed to an hour glass after
you submit a page and before the next page
is displayed.
- A problem with SFLPGMQ field in a subfile
control record has been fixed.
- CHECK(ER) and DSPATR(SP) parameters now function
correctly with the VALUES keyword.
- The data in all numeric fields and fields
with CHECK(RZ) and CHECK(RB) are now right
justified.
- A problem with CHECK(ME) validation has been
corrected so that the checking is turned
off for record formats protected by the display
of a window record.
- Extra blank lines in some situations with
the CLRL keyword have been eliminated.
- EDTWRD and EDTMSK keyword formatting problems
have been corrected. Data now includes
edit
mask characters when EDTMSK is used with
the VALUES keyword.
- The CHECK(FE) and CHNGINPDFT(FE) keywords
are now supported. The cursor will automatically
tab to the next field when the field data
is full, except when using CHECK(FE) and
CHGINPDFT(FE).
- Fixed a problem with the same window or
a
blank window being overlayed on the screen.
- Web Settings for hidden function or command
keys have been changed so that they are not
displayed in the button area; however, they
are still enabled for keyboard entry.
- DBCS characters can now be specified as defaults
for command key button labels in the project
properties.
- A conversion problem has been corrected for
missing DBCS text constants. The problem
occurred for a DBCS text constant that
wrapped
over more than one line on the display.
Enhancements
- Support has been added to end the job associated
with the Web application immediately if the
user exits the application by closing the
browser window. This support requires the
latest WebFacing server PTFs available for
download on the product Web page at ibm.com/software/ad/wds400.
- "Back" button handling in WebFacing
has been supported. Web browsers allow the
user to go back and revisit Web pages they
had viewed before. Previously, if a user
would back up to an earlier page and interact
with it an error would result. With SP3 interacting
with these pages will only result in the
browser being refreshed and the last page
that was presented in the WebFaced application
will be redisplayed. For example, if a user
goes back two pages and either presses enter,
or clicks on a non-external link or command
key button, the WebFaced application will
ignore the user's last action and redisplay
the last page presented by the application.
- The insert and overwrite mode that is selected
by the user when pressing the Insert key
is now retained when a new page is displayed
in a WebFacing application. In insert mode,
data in a field is now selected when you
tab into the field.
- Programmatic invocation support has been
added for programmers who are writing Web
applications that will call WebFacing applications
running in the same Web session. The calling
application can forward the following parameters
to the WFLogon named servlet:
- clcmd - CL command to be called
- host - iSeries host name or IP address
- port - port number that the WebFacing
server
is listening to
- userid - user ID on the iSeries
- password - password on the iSeries
- inv - CL command .invocation properties file
For example, the above parameters can be
forwarded by constructing a URI as follows:
WFLogon?clcmd=call%20ordentr&host=server1&port=4004&userid=myname&password=mypwd
where:
%20 - is used to represent a space in the
URI.
The clmd, host, port, userid, and password
properties will override those specified
in the .invocation and WFApp.properties files.
If you specify an invocation file name, you
do not need to specify the other properties.
If you do not specify an invocation file
name, the CL command must be specified and
any missing properties will be retrieved
from the WFApp.properties file for the project.
- Command key recognition patterns can now
be used without removing the command key
text in the application area. In this way
you can still have proper labels on you
command
key buttons and still keep your command
key
descriptions in the application screen
area.
To do this you need to manually change
the
corresponding <TextConstant> entry
in the "<project_name>config\conversion.rules"
xml file as follows:
Change from:
<TextConstant option="blanks"></TextConstant>
To:
<TextConstant option="text"></TextConstant>
- User-defined edit codes (5-9) are not supported
in WebFacing. However, you can now map
them
to one of the available system edit codes
(1-4, A-D, J-Q, W-Z). To do this you need
to modify the following <EDTCDE>
entry
in "<project_name>config\conversion.rules"
xml file as follows:
<EDTCDE>
<Mapping userDefined="5"systemCode="5"></Mapping>
</EDTCDE>
To map a user defined edit code "5"
to the system edit code "A",
you
need to change the XML in the above example
to:
<EDTCDE>
<Mapping userDefined="5" systemCode="A"></Mapping>
</EDTCDE>
If you want to add some additional mappings,
you can change the XML to:
<EDTCDE>
<Mapping userDefined="5" systemCode="A"></Mapping>
<Mapping userDefined="7" systemCode="C"></Mapping>
</EDTCDE>.
Service Pack 2 -- August 2002
CODE
List of fixes
The WebFacing Tool
List of fixes
- The CL command and CL label entry fields
have been reversed so that a default label
is automatically created if nothing is entered.
- The data length for the O field and DBCS
character validation is now correct.
- The SFLRCDNBR(CURSOR) now functions properly.
- For the records kept on the display because
of the KEEP keyword, their input-capable
fields are now protected.
- Negative shift Y fields with EDTCDE(A-D)
and CR (at the end), are now formatted correctly.
- If you are using the CLRL(nn) or CLRL(*END)
keyword with the SLNO(N|*VAR) keyword, then
lines on the display are now cleared beginning
with the starting line number specified by
the SLNO keyword.
- The ERRMSG and ERRSFL keywords now have correct
active subfile messages.
- Horizontal subfiles are now displayed properly.
- You can now use the RTNCSRLOC keyword with
parameter values that contain variant characters.
- A problem with a delay in the data displayed
on the screen when the EDTMSK and EDTWRD
keywords are in use has been fixed.
- If you have used the HTML anchor tag to create
hypertext links, you might have experienced
a problem with a frozen screen where the
display can no longer submit requests back
to the iSeries applications. This is caused
by clicking more than once on the link while
the screen is being submitted. This problem
has been corrected so that only one submission
is possible.
Enhancements
- If you have selected DDS members of type
MNUDDS for conversion, you can convert the
menu options into hypertext links. The command
option number and any text included in the
same field where that number is found will
be converted into a hypertext link. To change
the properties, right-click the name of the
WebFacing project in the Projects view and
select Properties. Select or de-select the Convert menu command options into hypertext
links check box, and click OK.
- The insert mode for keyboard text entry controls
text entry on input fields in the browser.
The default behavior for Web browsers is
insert mode ON. However, the default insert
mode is unchecked in the run-time properties
for your converted Web application, to match
the behavior of the green screen application,
which is in overwrite mode by default. This
will facilitate data entry on input fields
with pre-filled data. You can enter data
using the overwrite mode without first having
to select or delete the text. If you want
to change the default setting, right-click
the WebFacing project and select Properties. In the properties dialog, select Runtime > Project and select the Use insert mode for keyboard text entry check box (at the bottom of the window).
- The message line for validation errors has
been enhanced. Messages are now displayed
in an error box next to the field that is
in error. This enhancement does not apply
to program errors and message subfiles.
Special instructions
- To control the writing of records to the
device, DSPF objects can be compiled with
DFRWRT(*NO), which means that all records
written by the application are immediately
written to the device. This can be a more
time-intensive process than in the green
screen application, and therefore the IBM
WebFacing Tool, by default, ignores this
compilation setting. Instead, it writes
only
when the application reads a record, or
writes
a record that has the FRCDTA keyword. If
you still do not want to defer the writing
of records, you can clear the check box,
either in the properties page for a specified
CL command or in the properties for the
project.
The setting for the CL command overrides
the setting for the project. To change
the
properties, right-click the name of the
WebFacing
project in the Projects view and select
Properties. Select or de-select the Handle as if file is compiled with DFRWRT(*YES)
option check box, and click OK.
Service Pack 1 -- May 2002
CODE
List of fixes
- When CODE presents the following CL dialogs:
CRTLIB, CRTDUPOBJ, ADDPFM, CRTSRCPF, ADDLIBLE,
CPYLIB, CPYSRCF, and CALL, online help is
only available when the STRCODE command is
running. Therefore, the help button is enabled
only when a STRCODE server is available.
- When mnemonics are in parenthesis and three
dots are at the end of the text '...', indicating
more to come , the mnemonic is placed before
the '...' .
- The TurnOver interface now invokes the program
verifier with the "prompt" and
"no prompt" options.
- Local files with sequence numbers are now
opened correctly, and the "Has sequence
number" property is added to the file
properties.
- IFS files are now saved correctly when you
click File > Save or the save icon.
- Procedures using long name support now appear
when you click View > Procedures in the editor.
- All references to the obsolete registry key
EVFCCODE.INI have been removed.
- Prompting in the Editor has been fixed so
that the following field names are not
truncated
in the Korean language:
- Input and Field Description, in the Data
Format field
- Definition, in the Type of Data Structure
field
- When editing source in CODE editor, pressing
F5 now clears the prefix area.
- When in the Communications Console, clicking
Check PTFs now invokes the hostprereqs.xml file.
- The ILE RPG verify function has been modified
so that externally described data structures
now use the correct record format.
- FIELDS.LX no longer issues errors when the
data retrieved (text description of a field
or record) exceeds the record length. It
now truncates.
- When "ADM" is the first filter
selected in Code Project Organizer, the
program
no longer issues an error or freezes the
interface.
- Turning signatures on no longer causes the
Smart Enter to malfunction.
iSeries development tools and the Remote
Systems Explorer
List of fixes
- For the iSeries Project Perspective:
- When downloading a source physical file using
the Import action on an iSeries Project,
if you happen to select a source physical
file to which you have insufficient authority,
you now receive a more informative error
messages indicating that the download failed
due to insufficient authority.
- If you change the CCSID of a SRCPF and you
select "Push Selected" or "Push
Changes," the CSSID is now correctly
updated on the host with the new value.
- If you deselect "Show Remote Objects"
on one of the projects in the perspective,
all other iSeries Project perspectives that
happen to be open will also be correctly
updated.
- You can now create a source physical file
with the Source Physical File wizard that
includes DBCS data. (This is the ICGDTA parameter
in the CRTSRCPF command.)
- When you create and open a new source member
in the JLPEX editor, it will have correct
sequence numbers and the proper record length
set.
- If you have already used the iSeries Project
perspective before installing Service Pack
1, and created source physical file folders
locally , you will see a red x tagged onto
each source folder. This is not an error,
but to resolve the marks:
- Right-click the source physical file and
select Properties.
- Change the CCSID to any value and click OK. This will regenerate the required data
and remove the red x.
- Go back to Properties and re-set the CCSID to its original value.
- For user-defined actions:
- You can now use more than one user-defined
action at a time (on a single selected object).
If you select multiple items in the Remote
Systems Explorer tree-view, the user-actions
are no longer disabled.
- The RPG file type action is no longer missing
a space between RPT* and SQLRPG.
- File Type names and values are automatically
converted to uppercase when entered.
- User-defined action changes (through the
work-with dialog) are now propagated to other
connections in the same file.
- User-defined-type names can now have embedded
blanks in file-type names used with user-defined-actions.
- User-defined-actions defined for specific
file subtypes are now correctly shown for
those objects.
- For running commands:
- Cancelling a prompted command no longer adds
a line to the Commands view or executes SBMJOB
if the command was of type batch.
- When running a batch command, the RSE now
prompts the SBMJOB command with the command
pre-filled.
- Messages issued by a command run in batch
mode are now shown in the Commands view.
- Using File > Close All now correctly closes all members including
ones open in the LPEX Editor.
- Source members are no longer locked when
you open more than one member in the LPEX
editor and then attempt to close them.
- Starting and restarting of the communications
daemon is now automated.
- The LPEX editor no longer assumes that new
local files have sequence numbers, or that
local files with fewer than five lines and
with sequence numbers do not have sequence
numbers.
- If you edit a CL source file and press F4
to request a prompt for the current line,
the display area occupied by the prompt dialog
is no longer white if you move the dialog.
- If you query your jobs, disconnect from your
connection, and then query your jobs again,
they no longer fail with a null pointer exception.
- You are now able to name an RSE connection
as a substring of an existing connection
name to the same host, without experiencing
problems when the host table updates for
the code alias.
- Using the Enter key in an SEU base profile
no longer creates a newLine instead.
- The Remote Systems Explorer now has more
file extensions; i.e., parser associations
such as sclle, cicscblle, sqlcblle, cicsc
(parser cppCics), cicscbl, cicssqlcbl, and
sqlcbl (parser cobolSqlCics), cpple (parser
cpp), sqlc (associated with parser cppSql),
and sqlcpple (parser cppSql).
- Entering an interactive command in the Commands
view no longer requires that the "*inter"
prefix be uppercase.
- Displaying help for a prompted command now
creates files in the WSSD\workspace\.metadata
directory instead of the root WSSD directory.
- The Navigator view in the Remote Systems
Explorer now correctly reflects whether or
not files still exist. In essence, you are
no longer able to delete a file in the tree-view
if you have the file locked or open in the
LPEX or CODE editor.
- After cancelling the iSeries Objects query
that retrieves items from the tree-view,
the information message "Operation cancelled"
no longer displays in the tree.
- When you select a job, the status line now
displays "*JOB" instead of "iseries.job.descriptor".
Prerequisites
The latest Remote Systems Explorer PTF is
required for Remote Systems Explorer support
in iSeries development tools.
iSeries development tools host PTF
OS version |
Product |
PTF |
V5R1 |
5722WDS |
SI05145 |
Limitations
- You need to close and restart CODE communications
for any changes made to the communications
properties for an RSE connection (library
list, sign-on command and current library)
to take effect. To close CODE communications,
right-click the CODE communication daemon
and select Close from the pop-up menu.
- Because the iSeries host only supports user
IDs of 10 characters or less, you will receive
an error message of "Invalid userid"
if you try to sign on with a user ID over
10 characters.
Special instructions
- Server code is now shipped in the following
Integrated File System (IFS) directory: /QIBM/ProdData/Devtools/
, rather than /QIBM/ProdData/rseserver. You
will need the latest WDS host PTF to obtain
the server code. See our web site for details:
ibm.com/software/ad/wds400/.
- The WDS host PTF is also needed to provide
extra Remote Systems Explorer functions such
as batch command support, interactive job
support, etc.
- If you tried to remove a compile commands
entry (from Compile > Work with commands, displayed in the right-click menu of a
source element) with Windows 98, before installing
Service pack 1, you might have received an
internal error. To rectify, delete the file
x:\WDSC\WSSD\workspace\RemoteSystemsConnections\profileName\compileNames.xml. This problem is fixed
in Service pack 1.
- When you try to copy or move Universal and
IFS files containing special characters
in
the name (such as an "&"),
an error occurs. To rectify, enclose the
path in quotation marks. If the special
character
is an apostrophe, make sure to use two
apostrophes
to enclose the name.
Java development tools
List of fixes
- When an incorrect Program Call Markup Language
(PCML) file fails to restore, the name
of
the PCML file in the second page of the
Program
Call wizard is no longer renamed to the
incorrect
PCML file.
- Using the up and down arrow keys to traverse
the PCML file tree in the Program Call
wizard
no longer freezes the wizard.
- The RecordIOManager bean from the Java Bean
Example wizard has been improved with more
detail.
- Invoking the updateRecord(int[], DefaultTableModel)
method directly in the RecordIOManager
class
no longer produces a java.lang.ArrayIndexOutOfBoundsException
error.
- Specifying "00000" and an edit
word " / / " for the edit word
formatting in an EditcodeEditwordFormatter
bean no longer returns the incorrect format
of "0". Instead, it now correctly
returns the value of " " with
extra
space in between the quotation marks.
- The Program Call wizard now supports nested
structures.
Limitations
- The Java application bean generated by the
Program Call wizard supports a single-dimensional
array of any data types, but not multi-dimensional
data such as nested structure arrays.
- The Web Services bean generated by the Program
Call wizard does not support arrays.
Special instructions
- If you have created a Web project that has
Java beans generated from the Program Call
wizard, prior to Service Pack 1 installation,
you need to:
- delete webApplication\lib\wdt400rt.jar
- select the .pcml file and recreate the Java
beans using the Program Call wizard in
order
to copy a new wdt400rt.jar to webApplication\lib.
VisualAge RPG
List of fixes
- Message searching performance at run time
has been improved.
- In the past, "WRITE window" operation
in an EntryField part's CHANGE event action
subroutine caused an infinite loop if the
user entered the "&" character
in the entry field part. This has been fixed.
- The run-time environment has been changed
to dynamically load the short-cut keys for
menu items.
- The Container part's performance is improved.
Web development tools
List of fixes
- Check box and combo box DTC run-time attributes
now work properly.
- Beans are now properly generated when you
specify a nested structure for your application.
- The Web Interaction wizard now generates
correct parts for array output.
- DTC lengths are now correct for generated
input pages.
- Numeric entry fields no longer cause an exception
error.
- The table DTC now functions correctly.
Limitations
- If the properties of a table design-time
control (DTC) in any JSP file are modified
and saved, the interaction that uses that
file needs to be updated. Open the Web Interaction
wizard by double-clicking the .wit file that
identifies the interaction. Make any necessary
changes to the options specified in the wizard
pages, and then click Finish to regenerate the Web interaction with the
changes made
- Distributed debugger support is not available.
Special instructions
- After installing Service pack 1, you should
update any web applications generated by
the Web Interaction Wizard. You need to
remove
the following files and re-run the Web
Interaction
Wizard on any existing web interaction
projects:
- webapplication\lib\wdt400rt.jar
- webapplication\error.jsp
- webapplication\setdebug.jsp
The new set of files will be copied to the
corresponding directories. If you used JSPs
with design-time-controls for your application,
you need to re-save the page to force the
JSP code regeneration.
- If you choose to delete a DTC column and
then cancel the deletion, the action is not
cancelled. To rectify, cancel the JSP page
instead.
- Use the following procedure to debug a Web
application that uses an ILE host program:
- Enter the following command in a command
prompt window to start the debugger daemon
on the client machine:
idebug -qdaemon -quiport=8001
The uiport is any unused port on the client
machine. The default port is 8001
- In your Web project, right-click setdebug.jsp in your Web application, and select Run on Server.
- On the page that opens in the browser:
- Enter the IP address of the debugger client.
(You may need to ping the client machine
to obtain its IP address.)
- Enter the port number if it is different
than 8001.
- Select the enable debugging radio button.
- Select Submit to start the session.
- Right-click the first page of your Web application
and select Run on Server.
- As you navigate through your Web application,
when it invokes the host program, the
distributed
debugger client is launched. You can
use
the debugger window to control the execution
of your program by setting breakpoints,
stepping
through program instructions, examining
variables,
and examining the call stack.
Note: The ILE program needs to be compiled with
the debug option set to ensure that the program
source is displayed in the debugger window.
- To stop debugging, select the Halt icon on the Toolbar in the distributed debugger
window.
IBM WebFacing Tool
List of fixes
- The style wizard has been removed, and the
style properties pages from the style wizard
have been merged into the Project Properties
for modifying styles. The User Interface
controls on these pages have been enhanced
accordingly.
- The "Use project settings" check
box in CL properties is changed to "Override
project settings."
- You can now run a WebFacing application with
JSP 1.0 in WAS 3.5.x, and JSP 1.1 with WAS
3.5.6, without receiving a "IScrollbarBean
can't be instantiated" error in the
browser.
- The tool no longer returns a SFLRCDNBR error
when you write a subfile control record with
the SFLDLT keyword in effect.
- The tool no longer encounters an "out
of memory" exception error.
Enhancements
- The generated JavaScript is more compact,
and performs better as well. In particular,
loading a WebFacing page is much faster.
- Multiple conversions are now done in the
same Java Virtual Machine, which speeds
up
the conversion of multiple DSPFs.
- The tool now uses relative paths for URLs.
Therefore, you can use it in conjunction
with the Policy Director and other products
that add to the URL.
- The tool now supports clustering.
- A user-defined sign-on page is now an option
in the Properties wizard. webApplication/logon.html
is supplied as a user-defined sign-on sample
page, for customization.
- Command key labels are conditioned on or
off if the fields are overlapping. An indicator
can also condition the fields on or off.
- To create a hyperlink in the IBM WebFacing
Tool's Web settings, a new check box has
been added to override the browser's hyperlink
appearance with a DDS appearance instead.
- The DATFMT, DATSEP, TIMFMT, anad TIMSEP keywords
are now supported.
Limitations
- WebFacing Tool (First Edition) projects created
for WebSphere Development Tools version 5.1.0
are not compatible with WebFacing Tool projects
in WebSphere Development Studio Client 4.0.
If you want to maintain deployed WebFacing
Tool (First Edition) projects in a production
environment, use Development Tools 5.1.0
(Service Pack 5). If you have already installed
Development Studio Client 4.0 on top of Development
Tools 5.1.0, WebFacing Tool (First Edition)
you can recover projects by uninstalling
the new product and reinstalling the old
product in the same location.
- When working in the WebFacing perspective
of the Development Studio Client IDE, deleted
and closed projects are not automatically
removed from the application.xml file of
the associated EAR file. You must edit this
file manually to remove any deleted or closed
projects. To edit the application.xml file,
go to the Navigator view and double-click
the file name, then select the modules tab
to edit the war file list. This resolves
deployment problems that might be encountered
when running in the WebSphere Test Environment.
For example you may receive an error indicating
that the "Publishing Failed", with
the following message:
"IWAJ0095E Problems exist in project
mappings for one or more modules in Application.
Use Application editor to correct. Project:
DefaultEAR"
Special instructions
- NL considerations: Depending on your requirements, you can
translate the messages.js file. The file
contains messages from the iSeries object
QCPFMSG in the QSYS library. These messages
primarily concern field validation. To work
with this file, from within the WebFacing
perspective of the Development Studio Client
IDE:
- Click the Navigator tab. Locate the folder
for your WebFacing project.
- Expand webApplication > ClientScript > usr.
messages.js is in the usr folder. This file contains a JavaScript
array of messages with a format such as:
msg[8] = "Check digit error";
The text between the quotation marks can
be translated if necessary. Save translated
versions of the file with the same file
name,
messages.js, in the usr folder.
Note: the WebFacing documentation incorrectly
refers to messages.js as being in the ClientScript folder.
- For web applications containing help information
in the Development Studio Client 4.0 Test
Environment, you need to either:
- Open Window > Preferences (before launching the web application).
- Select Web browser and then select Use external Web browser.
- Specify the location of Internet Explorer
on your local workstation.
or
- Without changing the preferences, launch
the web application and click Launch in a new browser window.
- By default, the IBM WebFacing Tool defers
the write of a record. This means that even
a DDS file compiled with the DFRWRT(*NO)
command, which would normally require an
immediate write, is deferred. If you do not
want the forced defer write of a record,
you can manually add either "{InvocationForceDFRWRT}
= false" in the invocation properties
file, or "{WFForceDFRWRT} = false"
in the wfapp.properties file. If {InvocationForceDFRWRT}
and {WFForceDFRWRT} conflict, then {InvocationForceDFRWRT}
prevails and there will be a forced defer
write of a record if {InvocationForceDFRWRT}
= true.
Note: FRCDTA still causes an immediate write.
Base release
Components of Release Version 4.0
The components are:
- iSeries extensions for the Workbench IDE
- CODE and the IBM(R) Toolbox for Java(TM)
- WebSphere Studio Site Developer advanced
- VisualAge(R) RPG
- IBM Distributed Debugger
- NetQuestion
- IBM SDK 1.3 sr10
- Microsoft Java Virtual Machine
Notes:
- If you have a version of WebSphere Development
Tools for iSeries older than version 5.1.0,
make sure to uninstall it before installing
IBM WebSphere Development Studio Client version
4.0 (WDSC).
- Make sure to close the workbench IDE before
uninstallation.
- Upon migration to version 4.0, REXX objects
that used to reside under x:\wdt400 (where
x is the drive upon which you installed the
product), now reside under x:\wdsc\.
- If you are using Windows 98, you need to
shut down Norton Anti-virus for CODE to function
properly.
- When you search the help contents for the
first time (by clicking the Search tab from the help perspective, and entering
an item), the system creates a search index
file. This file is approximately 12 MB and
takes approximately 15 minutes to create.
- The ILE C/C++ language level for V5R2 is
equivalent to the V5R1 language level.
- The installation directories you use for
CODE, Distributed Debugger, and NetQuestion
cannot contain spaces. For example, you can
use c:\ibmdebug, but not c:\Program Files\ibmdebug
or c:\ibm debug.
Documentation changes
The Remote Systems Explorer
- When you use the Remote Systems Explorer,
you define a connection and give it a name
(as detailed in the regular documentation).
However, please do not use double-byte
characters
in the connection name, because CODE tools
do not support such characters in the connection
name. If you use double-byte characters
in
the connection name, you cannot launch
any
CODE tools from the Remote Systems Explorer.
Java development tools
- When you create Java beans for Web Services
using the Program Call wizard, you must
specify
a package name. Otherwise, when you attempt
to use the created Java beans as input
to
the Web Services wizard, the classes generated
by the wizard will have compilation errors.
Additionally, appropriate import statements
need to be added in the proxy and JSP file.
Known problems and limitations
Generating a Web Services Description Language
(WSDL) document from a Java bean
- A method with an input argument list containing
a mixture of Document Object Model (DOM)
Element and Simple bean types requires
the
entry of one or more custom mappings. The
WSDL Version 1.1 specification supports
one
encoding style for all input parts (parameters).
The Simple Object Access Protocol (SOAP)
Version 2.2 run time does not have default
mapping support for DOM Elements with SOAP
encoding for primitive types, and for beans
with Literal XML encoding.
- The "char" and "java.lang.Character"
elements require you to enter custom mappings,
because default mappings from char or java.lang.Character
to WSDL XSD do not exist. The primitive
wrapper
types (java.lang.Boolean, java.lang.Byte,
java.lang.Short, java.lang.Integer, java.lang.Long,
java.lang.Float, and java.lang.Double)
cannot
co-exist with their corresponding individual
primitive types (boolean, byte, short,
int,
long, float, and double) across all the
input
parameters of a service bean. For example,
a service bean cannot be turned into a
complete
Web service if java.lang.Integer and int
both appear as input parameter types.
- Beans with parameters or return types that
involve beans with property cycles are
not
supported.
- Beans with overloaded methods are not supported.
Generating a Java artifact from a WSDL document
- When generating a Java client proxy from
a WSDL document, you should begin with
the
WSDL service document. If you generate
a
proxy from a WSDL binding document, you
must
call the setEndPoint() method to set an
endpoint
URL before you call any other method on
the
proxy. The proxy generated from a WSDL
binding
document is not automatically equipped
with
an endpoint URL. Support is limited to
one
part per input or output element. Multiple
logical parts in an input or output message
are not supported. The first such part
is
processed and the remaining ones are ignored.
In WSDL documents with inline schemas,
support
is limited to at most one schema element
in the types element. If a WSDL document
contains more than one inline schema, you
might need to relocate the schemas to their
own XSD files and then import those files
from the WSDL document. If the generated
proxy Java path name contains invalid characters,
modify the path name to ensure the proxy
Java file compiles successfully.
- In the SOAP binding of a WSDL document, encodings
other than Literal XML and SOAP are not
supported.
- When defining custom mappings, ensure that
the bean, serializer, and deserializer
classes
are on the build path of the Web project,
otherwise the wizard cannot accept their
class names.
- Beans with property cycles are not supported.
For example, Web Service tools do not support
a situation in which bean X contains bean
Y and bean Y contains bean X.
- Both the Web Service wizard for creating
a Java skeleton and the Web Service Client
wizard process WSDL documents. In order
to
process a WSDL document, any import statements
must point to valid, accessible URLs.
- If you get the error message "IWAB0222E
Error encountered while analyzing WSDL
file"
with no additional details, ensure that
the
URLs specified in the location attributes
of the import elements in the WSDL are
accessible.
This error message often occurs if one
or
more of the URL locations cannot be opened
and read by the wizard.
EJB Web Services
- When creating a Web Service from a stateless
session enterprise bean that depends on
classes
in another project, you must add the project
as a dependency of the Web project that
holds
the Web Service, otherwise the generated
proxy might fail to compile.
Sample application and the embedded Web browser
- Indexed properties that result from WSDL
XSD complexTypes involving more than one
occurrence of DOM Elements are not supported
by the sample. SOAP encoded methods using
indexed properties are not available for
invocation. Literal XML encoded methods
using
indexed properties are available for invocation;
however, the inputs and outputs must be
specified
as Literal XML. Only the following types
are supported by the sample application:
- Members that use getters and setters
- All primitive types and corresponding Java
types
- Java type String
- org.w3c.dom.Element
- Java beans
- BigDecimal, GregorianCalendar, and Date
UDDI Explorer
- UDDI occasionally fails to open in the browser
when launched through the Import or Export
wizard. Close the browser and launch the
wizard again.
- When performing a query for owned service
interfaces, an unpublished service interface
might display. This does not affect the
publishing
of a Web Service that references the service
interface or the republishing of the service
interface.
- An error might not be flagged when an invalid
category is specified for a publish or
update
operation in the IBM(R) UDDI Test and Production
Registries.
- The taxonomy categories in the UDDI Explorer
are not translated because they must match
those in the standards adhered to by UDDI
(ISO, UNSPSC, NAICS).
- On some systems, the "Import to File
System" operation might result in
saving
the HTML file rather than the WSDL files
that you want. The workaround and fix for
this problem is documented in Microsoft(R)
Knowledge Base article Q281119. A dialog
box might ask if you want to save "WSDLFileDownloader";
however, the message is incorrect and does
not affect the actual name of the file
saved.
If the file extension displays XML when
selecting
the save location for the WSDL document,
ignore the incorrect extension and continue
to save. The file is saved with the WSDL
extension.
DADX Web Services
- The sample application tests the methods
that return DOM Elements.
- DB2_installdir\SQLLIB\java\db2java.zip and
WS_installdir\plugins\com.ibm.etools.webservice\runtime\worf.jar
are automatically added to the ws.ext.dirs
path variable for the local WebSphere Application
Server. DB2_installdir is the directory
where
DB2(R) is installed. WS_installdir is the
directory where WebSphere Studio is installed.
- If you are using the local Tomcat server,
you must add worf.jar and db2java.zip to
the server class path. To add worf.jar
and
db2java.zip to the server class path:
- Switch to the Server perspective by clicking
Perspective > Open > Other > Server.
- In the Server Configuration pane, expand Server Instances.
- Double-click the Tomcat server instance to
open the Instance editor.
- In the Instance editor, click the Paths tab.
- Click Add External JARs to add "DB2_install\java12\db2java.zip" to the class path,
where "<DB2_install>"
is
the directory where DB2 is installed.
- Click Add External JARs to add WS_installdir\plugins\com.ibm.etools.webservice\runtime\worf.jar
to the class path. WS_installdir is the
directory
where WebSphere Studio is installed.
- Select File > Save <name of file> to save your changes,
and then exit the Instance editor.
- When testing DADX Web Services on a remote
WebSphere Application Server:
- Enter the location of db2java.zip in the
DB2 driver location field.
- Edit the remote WebSphere server instance
and add the location of db2java.zip and
worf.jar
to the ws.ext.dirs variable.
- Ensure the IBM Agent Controller Log On As field has the same logon account ID and
password as the DB2 administrator. To
change
the logon account ID and password:
- Click Start > Settings > Control Panel >
Administrative Tools > Services to open the Services window.
- Right-click IBM Agent Controller, and then select Properties.
- Click the Log On tab, and then select This account.
- Click Browse to select the account ID and password to
use.
- In the Select User window, select your DB2 log on name, and
then click OK. Click OK again.
- dateTime XML Schema Simple Type is valid only when
the DADX statement of the DADX file contains
the XML type namespace http://www.w3.org/2001/XMLSchema.
- timeInstant XML Schema Simple Type is valid only when
the DADX statement of the DADX file contains
the XML type namespace http://www.w3.org/1999/XMLSchema.
- The generation of a Java proxy for DADX call
operations with multiple output parameters
is not supported.
- When a combined date and time parameter is
required, use WSDL part type http://www.w3.org/1999/XMLSchema:timeInstant.
Run-time considerations (WebSphere Application
Server, Apache Tomcat)
- Adding a Web project that contains a Web
Service to both the WebSphere Application
Server and the Apache Tomcat server is
not
supported. The deployment artifacts generated
into the Web project differ according to
the server environment. For information
on
running the EJB test client on Apache Tomcat,
refer to "Using EJB test client -
overview"
in the online help.
- To deploy a Web Service to Tomcat, ensure
that the Web project is added to the Apache
Tomcat server configuration. If you receive
the message "Server port port_number
is in use," the server process from
a previous WebSphere Studio session might
not have stopped when WebSphere Studio
was
closed. Find and terminate the server process
(javaw.exe) in the Task Manager before
starting
the server instance or before using the
Web
service wizards.
- Ensure Apache Tomcat is not running in debug
mode when creating and deploying a Web
Service.
For more information on the debug mode,
refer
to "Testing and Publishing Web and
EJB
projects" in the online help.
Publishing and updating limitations
- When publishing or updating business entities,
business services, and service interfaces,
use only ISO-8859-1 (Latin 1) characters
for names and descriptions.
Workstation requirements
Workstation hardware
WebSphere Development Studio Client for iSeries
has the following hardware requirements:
- Processor - Intel Pentium II (600 MHZ or
faster processor recommended)
- Display - VGA 800x600 (1024x768 recommended)
- CD or DVD drive
- A mouse or other pointing device
- Appropriate communications adapters (as supported
by the workstation
operating system)
- The following memory and disk requirements:
|
Minimum |
Recommended |
Memory |
256 MB |
512 MB (required when using the WAS
test environment) |
Disk |
1.4 GB + 500 MB temporary space needed during
product installation. |
1.6 GB + 500 MB temporary space needed during
product installation. |
Workstation software
WebSphere Development Studio Client for
iSeries has the following software requirements:
Development Time |
Run Time |
- Windows 98/NT/2000/Me/XP
- OS/400 V5R1 or later
- Internet Explorer 5.0 or later
- WebSphere Application Server V3.5.2 or later
|
- OS/400 V5R1 or later
- Internet Explorer 5.0 or later
- WebSphere Application Server V3.5.2 or later
- JRE V1.3 or later (is automatically installed
on the Client but not the Server)
|
Other sources of information
Visit the product Web page at ibm.com/software/ad/wds400/. Click Support, then select an item under Support Downloads for Web Updates
You can also get to this page by following
the links in the IBM Software home page at
ibm.com/software/.
To post your questions on the newsgroups,
use:
News server:
Suggested newsgroups:
- ibm.software.code400
- ibm.software.varpg
- ibm.software.websphere.studio400
How to find your License Agreement
License Agreement files for this product
are in C:\Program Files\IBM\WDSC\license.
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 might
not apply to you.
This information could include technical
inaccuracies or typographical errors. Changes
are periodically made to the information
herein; these changes are 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 want to have
information about it for the purpose of enabling:
(i) the exchange of information among 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 870
8200 Warden
Avenue
Markham, Ontario L6G 1C7
Canada
Such information might 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
among us.
Special Notice -- WebSphere Host On-Demand
WebSphere Host On-Demand (HOD) is shipped
in WebSphere Development Studio Client for
iSeries. HOD provides connectivity to the
iSeries host. You can use HOD for WebSphere
Development Studio Client for iSeries development
purposes only. By accepting Service Pack
1, you have accepted this usage restriction.
Programming interface information
This documentation describes General-Use
Programming Interface and Associated Guidance
Information provided by IBM WebSphere Development
Studio Client 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.