RE: [WDSCI-L] Efficient use of WDSCi.

[Kelly Cookson <KCookson@xxxxxxxxxxxx>]

A little of both. 

Browsing:

We often develop new programs by finding previously developed programs,
copying and renaming them, then reengineering them. I sometimes want to look
at several different programs to see which would be best suited for
reengineering. Sometimes a program fails and I have to look at code in
several programs in a call stack (10 or more programs). So I need to briefly
skim through multiple programs efficiently.

I've created filters for our source physical files, but we have so many
source members that the filters just take a *long* time to resolve. I
usually get big delays and server not responding errors whenever WDSCi has
to resolve them. When the list of members appears, I have to manually scroll
and search the list rather than specifying a member name to position to.
Then I may have another delay while WDSCi opens the member in LPEX. The
green screen SEU lets me use a combination of entering member names and
paging up/down, and it quickly opens members for browsing. I can also have
two green screen sessions up to alternate searching through two source
physical files (e.g., to browse the COBOL and CL programs of a call stack).
The bottom line is I can open a green screen, search through one or more
source physical files for members, and open the members to browse them more
quickly than I can browse the same programs in WDSCi. But I'm not blaming
WDSCi at this point. It may be I need to change the way I'm using WDSCi. 
 
Manipulating objects:

I often have to create new objects by copying and renaming old ones. If it's
just one or two objects, I don't mind using WDSCi iSeries Commands. I have
some custom commands set up for these purposes. But if I have to create 4-5
program objects, 5-10 copybooks, and a few 5250 or DB2 DDS files for a
project, I'm back in the green screens to get things set up.  Again, it may
be I need to change the way I do things (e.g., not rely on iSeries Commands)
in WDSCi.

Thanks,
Kelly






There are also times when a program fails and I have to trace call stacks or
look through the programs in a call stack to see where a problem originated.
We often have relatively deep call stacks--sometimes 10 or more programs.
Again, it's just quicker for me to browse through a bunch of programs
quickly using green screens.  

-----Original Message-----
From: Mark Phippard [mailto:MarkP@xxxxxxxxxxxxxxx]
Sent: Tuesday, January 20, 2004 9:30 AM
To: Websphere Development Studio Client for iSeries
Subject: RE: [WDSCI-L] Efficient use of WDSCi.


Kelly,

Perhaps if you were more specific about some of the things you still 
prefer to do in PDM it might help answer?  For example, is the problem 
just finding and opening members to edit, or do you perform a lot of 
object/member manipulation that you find easier to do in PDM?

Mark



wdsci-l-bounces@xxxxxxxxxxxx wrote on 01/20/2004 09:16:45 AM:

> Okay. I had gotten the impression that running multiple workspaces was
> supposed to be a way of organizing projects. I therefore assumed there 
was a
> better way of using workspaces. Actually glad to hear it is typical to 
reuse
> a workspace for iSeries development for a single team/shop. :)
> 
> I, too, go back to green screens to look at database files during
> development. The DBU plugin from ProData is nice, but I doubt my 
managers
> will spring for the extra license given that we can go back to green 
screens
> to use DBU. The JFaceDbc looks interesting in that regard. Thanks for 
the
> tip. I guess I need to do more searching for plug-ins when I find an
> opportunity.
> 
> I could still use some advanced tips for efficient use of RSE and 
debugging,
> though.
> 
> Thanks,
> Kelly
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Colin Williams [mailto:colin.williams@xxxxxxxxxxxx]
> Sent: Tuesday, January 20, 2004 7:57 AM
> To: 'Websphere Development Studio Client for iSeries'
> Subject: RE: [WDSCI-L] Efficient use of WDSCi.
> 
> 
> Kelly,
> 
> Whats wrong with using the same workspace, that what I do. 
> I now do everything from WDSC apart from running applications.
> 
> The other thing that would be handy is a WDSC SQL plugin, as most of the
> time that I pop back to green screen is to query/SQL files
> 
> Cheers
> Colin.W
> 
> -----Original Message-----
> From: Kelly Cookson [mailto:KCookson@xxxxxxxxxxxx] 
> Sent: 20 January 2004 13:52
> To: 'Websphere Development Studio Client for iSeries'
> Subject: [WDSCI-L] Efficient use of WDSCi.
> 
> 
> I've been using it for about 4 months now. I generally like it. However, 
I
> have not made a complete switch.  I tend to use WDSCi as a replacement 
for
> SEU and SDA (and WebFacing, which has no equivalent in ADTS). But I tend 
not
> to use WDSCi as a replacement for green screen PDM or ISDB.  I'm still 
much
> more efficient with green screen PDM than with RSE, and I find ISDB 
simpler
> than debugging with WSDCi. I'm also not making effective use of 
workspaces.
> It takes me so long to set up and customize views, connections, filters, 
and
> commands that I frequently reuse the same workspace. 
> 
> Are there any good articles for someone who has a few months experience 
with
> WDSCi and needs some intermediate or advanced tips to get truly 
efficient
> with RSE, debugging, and workspace utilization? 
> 
> Thanks,
> Kelly
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
> mailing list 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.
> This e-mail has been sent by a company of Bertram Group Ltd, whose
> registered office is The Nest, Rosary Road Norwich NR1 1TF.
> This message, and any attachments, are intended solely for the addressee 
and
> may contain privileged or confidential information.  If you are not the
> intended recipient, any disclosure, copying, distribution or any action
> taken or omitted to be taken in reliance on it, is prohibited and may be
> unlawful.  If you believe that you have received this email in error, 
please
> contact the sender immediately.
> Opinions, conclusions and statements of intent in this e-mail are those 
of
> the sender and will not bind a Bertram Group Ltd company unless 
confirmed in
> writing by a director independently of this message.
> Although we have taken steps to ensure that this email and any 
attachments
> are free from any virus, we advise that in keeping with good computing
> practice the recipient should ensure they are actually virus free.
> 
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
> mailing list
> 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.
> _______________________________________________
> This is the Websphere Development Studio Client for iSeries  (WDSCI-
> L) mailing list
> 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.
_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
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.