IBM WebSphere Development Studio Client Advanced Edition for iSeries Interim Fix 002 - 5.1.0.2

for IBM WebSphere^(R) Development Studio Client Advanced Edition for iSeries^(TM), Version 5.1.0

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 Advanced Edition for iSeries Web site at ibm.com/software/awdtools/iseries.

Remote System Explorer

List of fixes

1. When source members contain directives /EJECT, /TITLE and /SPACE, the outline view will now position the cursor on the correct line.
2. ILE RPG Program Verify no longer fails when a /copy member name or filename on an F spec contains an underscore
3. Migration of compile commands from a version 5.0 workspace to version 5.1 no longer produces two REPLACE parameters which resulted in compile errors. This fix only helps if the user applies the service pack before doing a compile. If the user issued a compile and has encountered this problem, remove the second REPLACE param through the Work With Compile Commands dialog..
4. Editor no longer hangs for ILE RPG source members that contain a line that is just 4 characters in columns 1 to 4 in a free form section.
5. COBOL copybooks can now be opened for "Browse/Edit" from the Source menu while editing a COBOL source member.
6. When moving a source member from one source physical file to another in the RSE (right-click select "Move".), the CPYF command is run first and it will no longer be presented in a command prompt. RMVM is executed only after the CPYF is successful.
7. Pasting a member into a PF38-SRC file will no longer issue a RSEG1170E message.
8. Selecting and requesting field properties from the "iSeries Field Table View" will now include the length and alias of the field.
9. Using the ILE RPG code-assist on unnamed datastructure subfields no longer issues an error.
   

IBM WebFacing Tool

List of fixes

1. The compression runtime property can now be used with non-English applications.
2. The cursor now goes to the next input field if the previous field was hidden using Code Designer Web Settings (SE11921).
3. Clicking the "Show" radio button for "Visibility" under the CODE Designer Web Settings repeatedly, no longer creates duplicate links.
4. Conversion will no longer fail if there is a space in a file path for the Create graphic Web Setting.
5. A problem with losing some of the conversion log results on reconversion has been corrected.
6. Function keys associated with the SFLDROP/SFLFOLD keywords are now generated after re-ordering them in Web Settings.
7. WebFacing conversion and CODE Designer now successfully extract the text for message constants that are 132 characters in length.
8. The default value of "0" is now displayed for fields with EDTCDE(1) or EDTCDE(J) and a field length of (1,0).
9. Hidden (H) fields will not be sent to the browser as hidden input fields for subfile records that are inactive.
10. Provides a work around to resolve an increase in memory usage caused by an Internet Explorer memory leak problem. At least 1 display file must be re-converted for this fix to take effect.
11. Fixes errors in conversion for BiDi languages when the SFLMSG keyword is used with a response indicator.
12. Fixes a problem with losing the key label text in a WebFacing application at runtime.
13. The system date and time generated by DATE(*SYS) and TIME keywords are obtained from the system the first time one of them is used and are now subsequently calculated in the Web application (tier 2) instead of on the iSeries. This is to improve performance.
14. The job date generated by DATE(*JOB) is cached in tier 2. This is to improve performance. You can add the following to your web.xml to turn off caching of the job date that results from DATE(*JOB).

     <context-param>
         <param-name>WFCacheJobDate</param-name>
         <param-value>false</param-value>
         <description>Cache Job Date in Tier 2</description>
     </context-param>

Otherwise, WebFacing will cache the job date by default. Note that when this option is set to true, the starting job date is retrieved from the iSeries just once when you first request this value using DATE(*JOB). Also note that general job attributes such as date format are only retrieved from the iSeries once at start up time before any Web page is displayed. The caching of these other job attributes cannot be turned off.

Classic Tools : CODE and CODE Designer

List of fixes

1. The "attached" dialog no longer appears when prompting CL commands or executing commands from CODE.
2. In CODE Designer, message constants that are longer than 121 characters will now correctly display the message text from the iSeries.

This fix also includes the previous fixes:

IBM WebSphere Development Studio Client Advanced Edition for iSeries Interim Fix 001 - 5.1.0.1

for IBM WebSphere^(R) Development Studio Client Advanced Edition for iSeries^(TM), Version 5.1.0

Remote System Explorer

List of fixes

1. Editor performance enhancements.
   
2. When RSE Connection gets deleted and recreated with same name, WebFacing will now find the new connection.
   
3. The RSE will now associate the STRTCPSVR command as an interactive only command. This will stop the information message EVFC5001 from being displayed.
   
4. When an ILE RPG F-specification is changed and signature is enabled, the line will have the signature added.
   
5. Using F4 no longer causes the source line to be uppercased if auto-uppercasing is enabled for ILE RPG.
   

IBM WebFacing Tool

List of fixes

1. You can now migrate multiple V5.1 projects using the import wizard. Previously, you could only migrate one project at a time.
   
2. When you delete a WebFacing project, the delete action now removes the module references from the Enterprise Archive (EAR) file for clean deletion of all relevant files. You can now also use the delete key to perform this action. In the WebFacing projects view, click your WebFacing project to select it and then press the Delete key.
   
3. The view log now displays correct conversion statistics for DDS and UIM files.
   
4. The "Change expired password" feature now works with CL commands that contain parameters entered as variables for your Web page.
   
5. A null pointer exception error no longer occurs when a record JSP containing a command key definition fails to compile at run time.
   
6. For window records, the window size is now smaller to fit the amount of data in the window.
   
7. When you position a cursor in a window text field, the correct cursor position is now returned to the iSeries host.
   
8. Page up/Page down buttons are now disabled in records that are overlaid by an input-capable CLRL record.
   
9. Invalid command key buttons are now disabled or removed from your screen if a new CLRL window is written to the same screen.
   
10. If one of your display file names contains the associated subfile control record name, you no longer receive an error.
    
11. For fields containing EDTMSK and EDTWRD keywords:
    
    • A screen converted by the WebFacing Tool no longer issues an unexpected validation error when the character protected by EDTMSK is "1" to "9", or ".", or blank.
      
    • Numeric fields with EDTMSK are now right justified instead of left justified, so that the number is represented properly in your WebFacing application.
      
    • For example, if you enter "5" in the subfield with a length of 2, within an EDTMSK field, the number passed back to the iSeries server is now "05" instead of "50". OR For example, a field like " 1/ 5/2003" is interpreted as "01/05/2003" instead of "10/50/2003".
      
    • If the edit word has a leading "0", the related EDTMSK will no longer produce an error when you load the display file DDS source member in CODE Designer.
      
12. The DFT or DFTVAL values for G fields will no longer be padded with spaces when the DDS member is converted.
    
13. The appearance of the arrow style is no longer altered when the mouse cursor hovers over an unclickable hyperlink.
    
14. The Enter data field no longer incorrectly inherits the value of the field name when the Enter data field should be empty.
    
15. Hyperlinks containing "id=", for example, "http://www.mysite.com?id=1020", are now generated correctly. Previously, the "id=" string conflicted with the "id=" HTML attribute.
    
16. The Insert field value button has been moved up so that it is next to the List of fields combo box in the Create hyperlink Web setting. The size of the URL and JavaScript hyperlink entry fields has also been increased.
    
17. If you choose to replace an output field or text constant in a subfile record with the buttons conversion option, an incorrect SFLCTL record bean name is no longer generated.
    
18. For CLRL windows:
    
    • Incorrect messages no longer appear in this window.
      
    • A message no longer appears in the first layer of the CLRL window if the last layer is non-windowed CLRL and the middle layer is windowed.
      
    • Command key buttons are now disabled or removed from your screen if a new CLRL window is written to the same screen.
19. A JavaScript error no longer occurs when you refer to a field with unconditional ND and PR display attributes. Fields with these attributes enabled will now be sent to the browser and use the wf_nd_pr{visibility:hidden} style.
    
20. If you select an ASCII key as a field exit key, for example, "+" from the number pad, or code 107, when you press the key, the ASCII character is no longer incorrectly entered into the field.
    
21. For CODE Designer:
    
    • When saving source, CODE Designer previously sorted the keywords so that COLOR keywords would be generated together. This action created problems when you simply updated WebFacing Web settings using CODE Designer. The order that indicators were found in the record could be changed by this behavior and this changed the buffer definition that was used at WebFacing run time. CODE Designer now saves the COLOR keywords in the same order that they are loaded.
      
    • When working on a DDS member, CODE Designer no longer closes if you specify a secondary display size without specifying a secondary display size name.
      
    • If the edit word has a leading "0", the related EDTMSK will no longer produce an error when you load the display file DDS source member in CODE Designer.
      
    • Graphic file names can now contain spaces, when saving graphic Web Settings with CODE Designer.
      
    • CODE Designer now checks for the correct decimal separator for VALUES keyword parameters.
      
    • CODE Designer now ensures that the order of the panel group and module names are correct when editing an H specification with a HLPPNLGRP keyword.
      
22. An array index out of bounds exception no longer displays when a subfile page is less than the subfile size and RSTDSP(*YES) is specified on the display file containing the subfile.
    

New Features

1. The iSeries Connection wizard is now automatically launched if the WebFacing Tool requires you to be connected to your iSeries server. For example, when you convert a migrated WebFacing project, the connection wizard is invoked automatically.
   
2. If you select the Text buttons style for your WebFacing project, the Replace text with buttons for all records conversion option is now automatically selected.
   
3. You can now open UIM files using the Remote System Explorer LPEX editor.
   
4. Text constants can now be split in CODE Designer. To do so, place your cursor on the text constant where you want to split the text constant and hit Ctrl+F5, or right-click to use the context menu.
   

iSeries Web development tools

List of fixes

1. After you complete the iSeries Web Interaction wizard or the iSeries Web Tools Migration wizard, you no longer encounter any validation errors with the struts-config.xml file.
   
2. When you run your logon.jsp file, used for the iSeries sign-on prompt, you no longer encounter any run-time exceptions.
   
3. When you migrate your version of Development Studio Client, the migration no longer overwrites your existing logon.jsp, error.jsp, and changePassword.jsp files.
   
4. The Web Interaction wizard input page field created from the Web Diagram now functions correctly, so that you have control over the field properties for Name in Session, Save to Session, and Message ID.
   
5. For migration of V5.x iSeries Web projects, links previously were lost in the Web interaction wizard .wit file if the names for the Web components did not follow the name conventions outlined in the iSeries Web Development Tools documentation. This problem is now fixed. However, links may still be broken inside a Web component table; thus, you need to insert the proper links by re-opening the wizard by double-clicking the Web interaction wizard .wit file.
   

New Features

1. You can now encode your run-time password. An Enable password-encoding check box is now provided in the iSeries Web Tools Run-time Configuration wizard, enabled by default.
   
2. When you invoke the Web Interaction wizard for the first time from a given Web project, you can now select your error.jsp file as part of the web interaction. Previously, error.jsp was not available for the first interaction.
   
3. When you create a Web application using the Web Interaction wizard, the feature to prompt for a user ID and password is now compliant with Struts version 1.1, (no longer limited to version 1.0.2).
   

iSeries Java development tools

List of fixes

1. You no longer encounter a run-time exception if you need to re-invoke a Web service built from a program call bean. (You use the iSeries Program Call wizard to generate this bean.)