WDSC 6.0.1 iFix 1 is now available

Hey Folks,

WDSC iFix 1 is now available
For RSE, iFix 1 = 6.0.1.1

The list of included fixes are as follows:
      RSE:
            [SE22323]  Issuing the STRRSESVR command on the iSeries to
            connect to the RSE daemon running in WDSC fails with error
            message RSE2011 if the iSeries connection node in RSE is not
            expanded after WDSC is started.
            [SE24189]  Remote Systems Explorer freezes when selecting many
            objects.
            [SE24281]  No page appears for export to remote file system.
            [SE24368]  ?Remote Servers > Debug > Start? action is not
            disabled if debug server has been started from job subsystem
            other than QUSRWRK.

      Remote Systems LPEX Editor:
            [SE21011]  Verifying ILE RPG source with a /COPY of an IFS file
            that has no extension fails because the IFS file is not found.
            [SE21026]  'Save All' action for Local/Linux/Windows files in
            Remote Systems LPEX Editor causes errors and/or logged
            exceptions when there is at least one project in the workspace.
            [SE23011]  In Japanese environment, when the backslash key is
            entered in the Remote Systems LPEX Editor, it is not stored on
            the iSeries as the Yen character, unlike when using SEU. The
            fix applies to sources of all types except C, CICSC, CLD, CLE,
            CPP, CPPLE, SQLC and SQLCPPLE. To disable the conversion of the
            backslash key to the Yen character, add the line
                  com.ibm.etools.iseries.core.preferences.jpnConvToYen=false

            to the file .
            
metadata\.plugins\org.eclipse.core.runtime\.settings\com.ibm.etools.iseries.core.prefs
             in the workspace, and restart WDSC. To revert to the original
            behavious, set the line to
                  com.ibm.etools.iseries.core.preferences.jpnConvToYen=true
            or remove the line from the file, and restart WDSC.
            [SE23290]  Verifying ILE RPG source, which references a display
            file that uses the keyword INDARA, causes a communication error
            and an error indicating that the file is not found to appear in
            the error list.  Refreshing the outline view for the same
            member, causes a file not found message to appear when
            expanding the file in the outline view.
            [SE23821]  Refreshing the outline view for ILE RPG source or
            switching between open ILE RPG source after disabling, and
            re-enabling the ILE RPG parser will give unexpected errors.
            [SE24193]  Verification of RPG or COBOL source produces
            incorrect errors when a /COPY member, or a copy book is open
            for edit or browse in Remote Systems LPEX Editor and errors
            have already been inserted into the source.
            [SE24216]  Specifying a text value for DIM in the D
            Specification wizard causes an invalid error to appear and user
            is subsequently unable to press Finish.
            [SE24224]  Editing an empty CL source, inserting a command with
            a label, when auto-formatting is enabled and the option to have
            labels on a separate line is selected, causes the workbench to
            hang.
            [SE24339]  Performing a Save as for CL source causes the Select
            connection dialog to incorrectly appear three times.
            [SE24344]  Defining a field like another qualified name in a
            sub-procedure, which is unresolved during verification of ILE
            RPG source, will cause the verifier and the outline view to
            hang the workbench.
            [SE24321]  After a Save As of an ILE RPG member, parser actions
            (e.g. Verify) are not always available.

      CL:
            [SE24329]  Specifying a label greater than 10 characters causes
            message EVFCL0074E to appear instead of EVFCL0038E.
            Incorrectly specifying a qualified value for a parameter causes
            message EVFCL0018E to appear instead of EVFCL0049E.
            [SE24329]  Specifying a generic value in a CL command that
            includes a number causes the CL syntax checker and prompter to
            issue an incorrect error.


thanks,

Violaine Batthish
WebSphere Development Studio Client, IBM Toronto Lab
(905)413-2750                          tie line: 969-2750         Fax:
(905)413-4850

You know you've achieved perfection in design, not when you have nothing
more to add, but when you have nothing more to take away. - Antoine de
Saint-Exupéry