IBM
WDSc for iSeries Updates


How is the product updated?

WebSphere products are updated using the Update Manager feature. This feature receives updates to your particular product, such as WebSphere Development Studio Client for iSeries, directly from the IBM servers.

The IBM Update Manager can be accessed by the following two methods:

1 - Automated Update:
  • The automated update will compare the current product with the available fixes on the IBM servers.
  • Missing updates are then downloaded and installed.
  • To access this support, select Help > Software Updates > New Updates
  • To access the IBM Update Manager through a proxy, select Window > Preferences > Internet and enter the appropriate proxy information, including the proxy host, port, and any authentication information that is required.
2 - Manual download:
It is recommended that you install updates using the automated update method, but this downloadable version of the fix is available for users who meet the following criteria:
  • Have slow or unstable Internet connections and would like use a download manager with resume capability
  • Have trouble accessing the live IBM server from behind firewalls
  • Would rather download the fixes and install at a later time
  • Are site administrators for a group of developers who do not have direct access to the Internet

The manual install is a multi-step process that requires the user to have an understanding of the current configuration. (Refer to the Current Configuration section for more details)

If no updates have been installed, refer to Step 1 to begin.


What is being fixed?

This refresh contains the following fixes and enhancements as described below. In addition, it includes any limitations of the product and information not included in the documentation.
For more information, see the WebSphere Development Studio Client for iSeries Web site at ibm.com/software/awdtools/iseries.

iSeries Web development tools

List of fixes

  1. APAR - SE17663:
    • Support Apache Tomcat v4.1 with JDK 1.4.
  2. Field values are not restored from session variables after message control displays a message. This can occur if the input page is the same as the output page.
  3. The Web interaction wizard ignores the usage type of a program parameter if it is a structure.
  4. Enhance the Table Web component to allow styles to be applied to individual columns.
  5. Page up/down of a subfile does not work if the subfile mode is write a page at a time and the subfile has editable fields such as a text entry.
  6. When the "Use Java Bean" option is selected in the Web interaction wizard, changing bean methods and/or properties results in an exception in the wizard, and/or changes are not saved.
  7. When a code generation template has been customized by the user, iSeries Web tools migration cannot determine if the customized template is an old version of the template, or the latest one available. Migration will always result in a warning code associated with the modified template.
  8. APAR - SE18348:
    • When a field is modified in the subfile, the corresponding record in the subfile user space may not get updated.
    • If a table has a select column, in-line cell styles are not applied to the last column.
    • The subfile is refreshed even though there is no change to any records. Simply tabbing from field to field can cause the subfile to refresh many times unnecessarily.
    • Paging causes previously selected records to lose their selection when the subfile is in the page as requested mode.
    • Text entries and text areas in a subfile always have trailing spaces that fill up the entire field. This makes it difficult for the user to edit  those fields. The trailing spaces must be manually deleted every time. 
    • Paging, selecting records, and editing the subfile can cause intermittent exceptions.
    • Subfile gets MCH0601 after a large number of records is written to it. The number of records that actually cause this exception depends on the length of the record also.  Records that are very long can trigger this exception after a small number of records is written to the subfile.

iSeries Java development tools

List of fixes

  1. The program call wizard ignores the usage type of a program parameter if it is a structure and incorrect code is generated. Existing programs that previously relied on the incorrectly generated code may have compile errors after the application of this fix. 

Integrated iSeries debugger

List of fixes

  1. APAR - SE18446:
    • The multi-threaded debug launch configuration does not handle parameters properly if there is embedded quote or ')'.

Remote System Explorer

List of fixes

  1. The following ILE RPG editing problem is fixed: Ctrl+M in ILE RPG source will no longer 'match' comment lines.
  2. The following CL parser and prompter problems are fixed:
    • APAR - SE17233: The CL prompter will no longer incorrectly parse command parameters as comments.  For example, the following will be correctly tokenized and reformatted such that LIB/*ALL  remains a parameter and is not interpreted as a comment, and prompting the command will no longer cause the parameter to be dropped:
      DSPOBJ LIB/*ALL OUTFILE(*OUTFILE) OUTFILE(QTEMP/OBJLIST)
    • APAR SE18053: The CL prompter will now correctly parse a positional parameter that is a command type parameter.  For example, the following will no longer cause an error message:
      IF &ERRORSW SNDPGMMSG MSGID(CPF9999) MSGF(QCPFMSG) MSGTYPE(*ESCAPE)
    • APAR SE18732:  The CL parser will no longer incorrectly indent source when previous statements contain the text DO enclosed in quotes.

    • Specifying positional parameters wrapped in brackets, will no longer cause erroneous errors.  For example the following command will no longer generate an invalid error when prompted, or syntax checked:
      IF &error (goto endpgm)
    • Parameter lists specified as positional parameters will no longer unnecessarily quote items.  For example, the following will no longer have additional quotes added to the parameter list when prompted:
      CALL QUSLFLD ('FLDOO1US  QTEMP' 'FLDL0100' &file &rcdfmt '0')
    • The following command when prompted or syntax checked, will no longer cause message EVFCL0081E to be issued:
      PGM (&file &rcdfmt)
    • When specifying 'blank' as a parameter value (whether by entering it, or when it is provided to the CL prompter as a result of a prompt override program), the parameter will no longer appear in the command preview area, nor when pressing the Ok button.  For example, prompting the following command will no longer cause the EDGESTITCH and SADLSTITCH parameters to appear:
      OVRPRTF    FILE(QPDSPSTS) OUTQ(QUSRSYS/BACKUP)
  3. The following ILE RPG program verifier problem is fixed: subfield created from LIKEREC on a data structure, where the external record contains an indicator, is incorrectly created with the type A instead of type N.
  4. APAR SE17718: If a user right clicked on an iSeries project and moved it to a different location on the file system, it would no longer be possible to create a new source physical file or member in the project. This showed up when a project was shared to a ClearCase VOB in the file system. The problem is now fixed.
  5. APAR SE17501: The Remote Commands view now provides correct output for iSeries machines running in the Japanese environment.
  6. The following ILE COBOL copybook problem is fixed: ILE COBOL copybook members are now searched in QLBLSRC in addition to QCBLLESRC file.
  7. The following COBOL outline view problem is fixed: Outline view now handles COBOL source that does not contain any COBOL Divisions.

This fix also includes the previous fixes:

IBM WebSphere Development Studio Client for iSeries Interim Fix - 5.1.2.3 for IBM WebSphere(R) Development Studio Client for iSeries(TM), Version 5.1.2

This document describes the fixes and enhancements delivered in IBM WebSphere Development Studio Client for iSeries Interim Fix - 5.1.2.3. In addition, it includes any limitations of the product and information not included in the documentation.

For more information, see the WebSphere Development Studio Client for iSeries Web site at ibm.com/software/awdtools/iseries.

Remote System Explorer

List of fixes

  1. Remote System Explorer caching memory leak is fixed.

This fix also includes the previous fixes:

IBM WebSphere Development Studio Client for iSeries Interim Fix - 5.1.2.2 for IBM WebSphere(R) Development Studio Client for iSeries(TM), Version 5.1.2

This document describes the fixes and enhancements delivered in IBM WebSphere Development Studio Client for iSeries Interim Fix - 5.1.2.2. In addition, it includes any limitations of the product and information not included in the documentation.

For more information, see the WebSphere Development Studio Client for iSeries Web site at ibm.com/software/awdtools/iseries.

Remote System Explorer

List of fixes

  1. APAR - SE16818: CL commands with qualified parameters will no longer have special values interpreted as single value parameters, and will no longer disable any qualified fields. For example, if the user specifies *ALL for the OBJ parameter for the SAVOBJ command, the library field will no longer be disabled.
  2. APAR - SE16352: When editing Japanese members the backslash key will now save as Yen character except for source types C, CPP, CLD, SQLC and CICSC. For these source types the backslash character still saves as a backslash.
  3. APAR - SE16958: Application hang is fixed when running an iSeries remote search before the corresponding iSeries connection is expanded or connected in the Remote Systems view.
  4. APAR - SE17231:
    • The CL prompter will now correctly recognize built in functions as being valid parameters when variables are specified. For example, the following will no longer give an error:
      CHGVAR VAR(%BIN(&RCVRLEN)) VALUE(60)
    • The prompter will now recognize when a user enters values in a field, even if the value is the same as the default, and specify the parameter as appropriate in the preview area as well as output from the command dialog.
    • The CL prompter will no longer incorrectly parse commands where a positional parameter is also a command. For example the following will no longer issue an error:
       ELSE IF COND(%BIN(&PERIOD 1 2) = 2) THEN(DO)
  5. APAR - SE17606: RSE "Compare With > Each Other" action now works if one of the members was previously opened in an editor and the editor was closed.
  6. APAR - SE17620: COBOL outline view now handles source that does not contain an "Identification Division" line.

IBM WebFacing Tool

WebFacing Server-side PTFs

For a list of the latest server-side PTFs, see the following Web site: www.ibm.com/support/docview.wss?rs=0&uid=swg27002213.

Information

  1. Conversion of one or more files is required to update an existing project to this Interim Fix Level.

List of fixes

  1. Running of a migrated WebFacing project that includes a user defined style will no longer fail with a 404 page not found error or HTTP 500 error. The required CmdKey.jsp and PageBuilder.jsp files are now correctly copied in to the WebContent/webfacing/styles/chrome/html directory. Once you have completed the migration, follow the steps as documented in \WDSC\install\help\migrate.htm which is referenced in the install README \WDSC\install\help\readme.htm of your existing IBM WebFacing Tool and attempt to run it in the integrated test environment of WDSC or deploy it to WebSphere Application Server.
    Complete the following steps, if you have customized your PageBuilder.jsp or CmdKeys.jsp files. You will find copies of your original PageBuilder.jsp and CmdKeys.jsp in your migrated project in the WebContent/webfacing/styles/chrome directory, with _5122_bak appended to the name. You need to integrate the changes you made into the new PageBuilder.jsp and CmdKeys.jsp files. To do this, in your migrated project select the PageBuilder.jsp file and the PageBuilder.jsp_5122_bak file, right click and select Compare with -> Each Other. This should help you to manually integrate any changes that you have made.
    In addition, if you have renamed the css file in the WebContent/webfacing/styles/chrome directory, you should edit your css file in the WebContent/webfacing/styles/chrome directory of your migrated project and add:
    	.launchbutton
    {
    border-color:#333399;
    border-width:1;
    text-align:center;
    }
    This will ensure that the Launch button in the index.jsp file is displayed correctly.
  2. Using the syntax &{FIELD} in the create graphic Web Setting would cause an error during conversion. Now this syntax is valid for conversion and is equivalent to using the syntax &{FIELD.value}, which gives you the initial value of the field from the program at runtime.
  3. Setting the cursor to a field using the action hyperlink Web Setting was not returning the correct cursor location to the application. This has been corrected, but requires a reconversion of the DDS.
  4. If an action hyperlink was defined prior to WDSC Version 5.1.2, and the data specified was non-numeric, a JavaScript error would occur when clicking the hyperlink. This has been corrected by adding single quotes to the non-numeric values. Reconversion is required.
  5. In some cases, the command key button labels were not being displayed when there were many record formats on the page. This has been corrected.
  6. If there was an HP2 tag (bold) in the UIM, the help was not always displayed correctly. This has been fixed and requires a reconversion of the UIM.
  7. The method for changing the command key width and height should now be done by modifying the CmdKeys.jsp file. This file is located in the WebContent\webfacing\styles\chrome\html directory. To change the width and height modify the bHeight and bWidth variables in the CmdKeys.jsp file. For more information refer to the comment at the top of the CmdKeys.jsp in the source view. These changes will apply to buttons displayed in the DDS records/application area when using the conversion project property "Replace text with buttons for window records" or "Replace text with buttons for all records". The changes also apply to any buttons displayed in the button area of your WebFacing page. The option to change the size of keys using the project Style properties for Command Keys is no longer available.
  8. In some cases when a subfile was displayed, the PageUp or PageDown keys may have been enabled when there were no other records to display. This would result in message CPF5218. Now the PageUp and PageDown keys are only enabled when there are more records.
  9. If the job decimal format (JOBDECFMT) is changed before an application is invoked, the wrong data and decimal format could be displayed when using the EDTCDE or EDTWRD keywords. Now the correct data is displayed along with the correct decimal format.
  10. If a field is defined with EDTCDE 1 and QDECFMT of 'J', then the incorrect formatted value was displayed if the value was less than 1. Now the correct formatted value is displayed.
  11. If the job decimal format (JOBDECFMT) differs from what is specified for the decimal point for numeric values in the COMP/CMP, VALUES, and RANGE keywords, validation errors would occur. Now the correct job decimal format is used for validation.
  12. If an application error caused the error page to be displayed, it was not possible to reinvoke the application from within the same Web browser session. Now you can return to the index page and restart the application once the error condition has been corrected.
  13. If the Web browser is closed before the first page of the application is displayed, the iSeries job did not always end. Now the iSeries job will end, however, there are still some conditions where the timing would result in the job not ending, although it is less likely.
  14. When invoking a WebFaced application programmatically and using an empty CL command (clcmd) parameter the application would hang. Now an appropriate error page will be displayed.
  15. If an unsupported browser is used a blank page was being displayed when the WebFacing application was invoked. Now an appropriate error page is displayed.
  16. If there is more than one validation or runtime error message, only one message was displayed when the message line drop down was selected. Now all messages in the message line are displayed and can be selected to position the cursor to the corresponding error. The message line will disappear when all errors have been corrected.
  17. Fixes a problem where the message line was not being cleared when the ERASE keyword was used to remove a subfile record from the display and the SFLDSPCTL keyword was optioned off.
  18. Field replacement variables are now allowed in the Insert HTML and User Defined HTML Web Settings in addition to the JavaScript Hyperlink Web Settings. The possible replacement variables are:
      &{FIELD}
      HTML field ID in the current record.
      &{RECORD.FIELD}
      HTML field ID in the specified record.
      &{FIELD.initialValue}
      Initial value from the webfacing runtime in the current record.
      &{RECORD.FIELD.initialValue}
      Initial value from the webfacing runtime in the specified record.
      &{FIELD.value} or &{FIELD.currentValue}
      Current value of HTML field object for an input-capable field in the current record, which can be modified by user input on the browser.
      Or:
      Initial value from the webfacing runtime in the current record for an output-only field.
      &{RECORD.FIELD.value} or &{RECORD.FIELD.currentValue}
      Current value of HTML field object for an input-capable field in the specified record, which can be modified by user input on the browser.
      Or:
      Initial value from the webfacing runtime in the specified record for an output-only field.
  19. If you have modified the rtmessage.properies file in order to translate text that is used in the logon page (logon.jsp file), the logon page would be redisplayed after input and not allow you to sign on. You can now translate the text in the rtmessage.properties file and the logon will work.
  20. If the CLRL keyword was used on a WINDOW record format that references another WINDOW record, a null pointer exeption would occur. This has been fixed by treating the CLRL as an OVERLAY.
  21. If a display file was created with a WAITRCD value specified, a timeout dialog would be displayed when the timeout occurred. This dialog can now be optionally turned off by modifying the web.xml file. This file is located in the <project_name>WebContent\Web-INF directory. The following lines in web.xml control if the timeout dialog should be displayed. The default is set to true and can be changed to false to disable the timeout dialog:
     <context-param>
    <param-name>WFShowTimeoutDialog</param-name>
    <param-value>true</param-value>
    <description>Show timeout dialog for INVITE</description>
    </context-param>
    You need to restart the Web application or the application server for this change to take effect.


iSeries Web development tools

List of fixes

  1. When invoking the Web Interaction wizard on an existing .wit file, where one of the JSPs defined for the interaction has been renamed or removed, this could result in an error where the wizard could not complete.
  2. APAR - SE16529:
    • The Web interaction wizard generates incorrect code when a program parameter is an array of structure.
    • A subfile that is sorted or filtered can not be selected. The record that is actually selected is one that is based on an unsorted or unfiltered subfile.
    • There is no validation if unsupported Java bean properties are selected in the Web interaction wizard. This leads to incorrect code  generation.
  3. APAR - SE17227:
    •  After the RPG program returns an error message id to a message control, input fields previously filled with data are cleared.
    • Substitution variables in subfile hyperlink does not work if the field is numeric.
    • The OK button is not disabled when the message controller dialog is in error.
    • Text entry fields and text area fields embedded in a subfile cannot be used for input. The user can enter in data but the changes are not reflected in the subfile user space.
  4. If the data in the text entry field is less than 1, then the formatted value is incorrect when edit code is '1', and the host system value QDECFMT is set to 'J'.
  5. Space characters are converted to HTML equivalent " ", which results in reduced performance when Label data contained a large number of spaces. Users wishing to continue showing the spaces in Labels can change the "DOCTYPE" of JSP/HTML pages from "-//W3C//DTD HTML 4.01 Transitional//EN" to "-//W3C//DTD HTML 4.01 STRICT//EN".
  6. Inline styles have no effect when WTable has single or multiple selection mode.
  7. If the wdt400br.js finds errors in a text entry field, it is still possible that the bad data is sent to the servlet.
  8. Migration updates code generation templates to the latest versions. If the user has made changes to any of the templates, a migration warning is given- the user is then required to merge their modified version with the latest version.
  9. There are certain EIM (Enterprise Identity Mapping) configurations that prevent Webtools SSO (Single SignOn) mapping from working. For example, if your SSO scenario includes a remote V5R3 iSeries registry joined to an EIM domain in a V5R2 server, then EIM identifier mappings to the V5R3 server will not work. The connector should be recreated once the interim fix is applied.


This fix also includes the previous fixes:

IBM WebSphere Development Studio Client for iSeries Interim Fix - 5.1.2.1 for IBM WebSphere(R) Development Studio Client for iSeries(TM), Version 5.1.2

Remote System Explorer

List of fixes

  1. Import and export of files with accented characters and saved using a non-LPEX editor now works.
  2. An API has been added for Business Partners to open an events file in the iSeries Error List view.
  3. When running a batch command, a message is logged in the iSeries Commands Log view if the required PTF is not installed on the iSeries.
  4. SE15599 - The CL prompter correctly recognizes special values that do not begin with *.
    i.e. The following command will no longer generate an error:
                 JAVA       CLASS(TEST) +
    OPTIMIZE(30)
  5. The CL prompter allows users to enter data exceeding the length specified for the field when the value specified is a value which is mapped to.
    i.e. For the CRTBNDCBL command a user will now be able to type *LINENUMBER in the OPTION parameter.
  6. In the Editor, the iSeries parsers now properly recognize line number prefix commands.
  7. In the Editor, selecting 'Filter view>Code' from the popup menu in the iSeries parser shows all lines with code, regardless if the line has comments on it or not.
  8. When editing DDS source in the Editor, the syntax checker no longer complains about plus and minus signs in the data length, decimal position, location line and location position fields when they are valid. Also the syntax checker no longer complains about location positions that are greater than 99 when they are valid.
  9. When editing ILE RPG source in the Editor, content assist has been updated for V5R3 changes.

IBM WebFacing Tool

WebFacing Server-side PTFs

For a list of the latest server-side PTFs, see the following Web site: www.ibm.com/support/docview.wss?rs=0&uid=swg27002213.

Information

  1. Conversion of one or more files is required to update an existing project to this Interim Fix Level.
  2. If you want to use a special character or a space character in you project name, you must ensure that the context root of your project does not contain a special character or space. To do this select the navigator view in the WebFacing perspective, right click on the project and select properties and edit the context root in the Web properties page. This is required if you want to run in the WebSphere v5.1 Test Environment.
  3. If you have a problem with WebFacing projects not running in the WebSphere Test Environment and you see an error in the console similar to:
    	6cb33777 SystemOut O Exception in generateFieldAttributes :
    java.io.FileNotFoundException:
    ...
    ...
    ...
    (The system cannot find the path specified)
    You have run into a limitation of the server to handle long directory names. If you use a workspace in a directory with a long path or choose long names for your projects, you may get this error when starting a server, or when testing files on a server. If you receive this error, you may take any of the following actions:
    • Move your workspace to a location with a shorter path, for example C:/workspace.
    • Rename your Enterprise Application project or other projects with a shorter name.
  4. Manual tabbing is no longer handled by WebFacing. It is handled directly by the browser, which means that the cursor will go to the next tabbable element on the whole Web page. Manual tabbing is no longer restricted to wrapping on elements within the WebFacing application area.


List of fixes

  1. A problem with the VALNUM keyword not being handled properly when specified at the file or record level has been fixed.
  2. An enhancement to the DSPATR(p-field) keyword has been made so that it now correctly handles protected attributes for all CCSIDs. It also handles invalid p-field values properly.
  3. References to replacement field names in JavaScript Hyperlink WebSetting will now work using the format &{field_name} or &(record_name.field_name}.
  4. Create hyperlink Web Setting now works properly on screens in the KEEP layer such as those of type MNUDDS.
  5. Clicking on the Logon or Cancel button multiple times in the logon page will no longer lead to an application error page.
  6. INVITE keyword support has been added to the WebFacing product. You must have the following PTFs installed on the iSeries server where your application is running to get this support:
    • V5R3 PTFs (SI14209, SI14210, and SI14211)
    • V5R1 PTFs (SI14732, SI14733, and SI14734)
    • V5R2 PTFs (SI14729, SI14730, and SI14731)
    The known problems that remain unresolved for INVITE keyword support are as follows:
    1. When the INVITE DDS keyword is specified at the file-level, option indicators specified on the INVITE keyword are not propagated to underlying SFL record formats. As a result, when SFL records are displayed by writing their corresponding SFLCTL record, application errors WF0096, WF0100 and WF0036 are presented on the browser, ending the WebFacing application. Circumvention: Move the INVITE DDS keyword and its option indicators to the appropriate record formats (i.e., move the optioned INVITE keyword from the file-level to the record-level). Note that INVITE cannot be specified at both the file- and record-level and cannot be specified with the subfile keyword (SFL).
    2. Reading an existing, but inactive, window record format does not cancel an outstanding INVITE, but rather fails with MSGCPF5023 (GET NOWAIT pending.). Circumvention: None.
    3. When paging up or down in already-existing SFL records of an INVITEd SFLCTL record format, where SFLPAG < SFLSIZ for the SFL, if a READ-FROM-INVITED-DEVICES (RFID) request times out, MSGMCH0601-F/QWSGET and MSGCPF5257-F/QWSGET-T/application will be signalled instead of MSGCPF4742 or MSGCPF4743. Circumvention: Either (1) do not allow the RFID request to time out, or (2) do not page among already-existing SFL records (i.e., only page down into portions of the SFL which must still be populated by the application)


iSeries Web development tools

List of fixes

  1. Validation on the second page of the iSeries Web Tools Run-time Configuration wizard no longer results in the finish button being disabled without an appropriate error message.
  2. No longer allowed to select JSPs in the iSeries Web Interaction wizard existing at a higher level than the Web content folder, resulting in run-time exceptions.
  3. When selecting "Use a Java Bean" and "No Program call" radio buttons in iSeries Web Interaction wizard, an empty Java source package is no longer created and no longer referenced in the generated Java source.

iSeries Java development tools

List of fixes

  1. Enhanced validation of user-defined authentication values has been added to the Program Call wizard, to help prevent exceptions at runtime.
  2. For Java projects the Program Call wizard now adds xmlParserAPIs.jar to the classpath, to help prevent exceptions at runtime.