1 Mar 2004 03:25
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.)(Continue reading)
RSS Feed