Re: Post your top 10 WDSC problems ...

   1)        Library list management.  If I've changed the library list in
   RSE, this **REALLY** needs to be carried over the CODE Designer or
   oftentimes any referenced fields won't resolve.  (I've made the change to
   specify the whole library list on the connection properties, rather than
   using a command equivalent to CHGLIBL.  This helps most of the time, but
   there are times when I open a DSPF or PRTF using CODE Designer and I get
   prompted for my password (which I've already told WDSc to remember) and
   then no referenced fields are resolved.  It takes ***WAY*** too long to
   close down CODE Designer and WDSc, then shut down all servers and re-open
   the workbench to get consistent results with resolving fields.  (This
   appears to be the most certain way to get the library list correct for
   CODE Designer.)  Even so, whatever method I've used to set the library
   list should carry over to CODE Designer.  Really this should include any
   libraries added or removed by entering a command in the 'iSeries Commands
   Log', but I would settle for using what I've setup in the connection
   properties using our homegrown SETLIBL command.)

   2)        Editing CL in the LPEX editor.  I'm almost always going back to
   green-screen SEU to edit CL.  If I've got a CL command that spans more
   than one line, when I enter the command and press enter, the workbench
   tries to reformat my CL command and instead replaces the second line with
   a mis-formatted first line.  (The second line is gone.)

   3)        Editing CL in the LPEX editor.  If I format a command in CL the
   workbench always wants to reformat the line.  I need an easy way to allow
   me to specify the format of a line instead of using the workbench's
   defaults.  (Yes, I know I can turn off much of the CL formatting in the
   preferences, but this is awfully cumbersome.  Also, if I turn off
   everything what's the advantage to using the workbench over green screen
   SEU.)

   4)        Source member change dates.  (Not the change of a line of source
   code, but the change date of a source member.)

   5)        I've set the default editor to use under
   Preferences-Workbench-File associations, but this seems to be pointless.
    Everything opens using Remote Systems LPEX, no matter what.

   6)        Did I mention Library list management.

   7)        Editing CL in the LPEX editor.

   8)        A quick method to save a source member like the Ctrl-Shift-N to
   open a member.

   9)        A simple keystroke or toolbar button to compile an iSeries
   source member.  (Oftentimes, the compile options are greyed out when
   editing a member.)

   10)        Remember my choices for severity in the 'iSeries Error List'.

   There are probably more issues that I have with the workbench/RSE/WDSc or
   whatever the name prefer, but these are the ones bugging me the most
   tonight.
   Original message:
   ------------------------------

   date: Thu, 26 Feb 2004 10:29:17 -0800 (PST)
   from: Leon Kiriliuk <leonki@xxxxxxxxx>
   subject: [WDSCI-L] Post your top 10 WDSC problems ...

   I'm interested in hearing back from the members of
   this mailing list what they consider to be the top 10
   problems with WebSphere Development Studio client for
   iSeries (WDSC).

   I'm interested in conceptual, usability or any other
   type of problem that gets in your way of getting work
   done.

   I'm especially interested in things that can be
   corrected through better documentation in WDSC or the
   addition of more tutorials.

   To post a message email: WDSCI-L@xxxxxxxxxxxx
   To subscribe, unsubscribe, or change list options,
   visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
   or email: WDSCI-L-request@xxxxxxxxxxxx
   Before posting, please take a moment to review the archives
   at http://archive.midrange.com/wdsci-l.