Re: Compile commands and iProject property file

Well, SVN is foreign to me.  We use a server based source management tool,
however, its ability to categorize things into projects is pretty poor, so
I use Rdi's connection, filter pools, and filters to manage it.  It has
some shortcomings, in that I haven't found a slick way to add individual
members to a filter without typing the name of each one out, but other than
that, it gives a decent way to manage projects of source where they reside.

Here is an overview:

Setup:
1. Define a connection to your development system that defines a library
list including your development, test, and production object levels.  Don't
include the upper levels of source in the development connection, just the
objects....well, that's a suggestion, so that your development level
doesn't get cluttered with the upper level source members.  Our Change
Management tool includes the source in its library list during the compile,
so that assumption may make your environment setup different.
2. Create at least a couple filter pools in the "Team" tab of the RSE, and
call them something like "Active" and "Closed".  This is how I separate
projects I'm working on and those that are completed for myself.
3. Create a filter pool reference to those filter pools on the above #1
development, test, and production connection.

Daily Use:
4. Create a member filter on your development connection that uses *USRLIBL
as the library, your source file, and the name of the member you're
developing.  Do this for each member explicitly, because that gives you
some record of what members were part of the project.  Name the member
filter by the project name, and a short description of it.
5. When the project is complete, right click on the member filter, and move
it to the "Closed" filter pool.

Notes:
You can have a number of connections, like Development, Test, Production,
and they all have the filter pool references (Active,Closed) in them, so
you can go to each level of development by using the different connections,
and opening the filter pools within them.  Because of the library list
setup, you don't see lower levels.  I also like to use the Object Table
view Unlocked, because this auto-refreshes with the filter contents as I
click on the filters in RSE.





From:	"Fajardo, Eduardo" <eduardo.fajardo@xxxxxxxxx>
To:	"Rational Developer for IBM i / Websphere Development Studio
            Client for	System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date:	05/18/2015 05:57 AM
Subject:	Re: [WDSCI-L] Compile commands and iProject property file
Sent by:	"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



Yes, it is the latter. We have multiple application releases and each
release is grouped in SVN as branches. Each branch/release is effectively
checked out into an iProject by developers before editing and compiling
then onto the server

I'm sure there must be a better way to handle this (RDi plugin?, scripts?)
but I don't have the answer yet. Let me know how you worked through it and
maybe we can use that too.


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
darren@xxxxxxxxx
Sent: Friday, May 15, 2015 11:52 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for
System i & iSeries
Subject: Re: [WDSCI-L] Compile commands and iProject property file

Are your developers using iProject for working on source offline, or are
you using it to group source together in a named project?  If its the
latter, as I tried to do sometime back, I found some methods that were
better at grouping source together rather than using iProject to do it.





From:"Fajardo, Eduardo" <eduardo.fajardo@xxxxxxxxx>
To:"Rational Developer for IBM i / Websphere Development Studio
            Client forSystem i & iSeries" <wdsci-l@xxxxxxxxxxxx>
Date:05/15/2015 09:43 AM
Subject:Re: [WDSCI-L] Compile commands and iProject property file
Sent by:"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>



Yeah, user action would've been okay but the extra step of pushing the
source to the iSeries before running the utilities/commands will not appeal
to developers. Flimsy excuse, I know but that's a sad fact.

I do hope an iProject based property file materializes in the future
though.

Thanks Buck & Michael.


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
MichaelQuigley@xxxxxxxxxx
Sent: Wednesday, May 13, 2015 1:04 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Compile commands and iProject property file

Eduardo/Buck,

My mistake. You are correct as I don't do a lot with iProjects, I missed
that. Using the Compile Commands to do Eduardo's processing is a clever way
to upload the source and process it.

I could be wrong about this (like I said, I don't do much with iProjects),
but I think Eduardo's use is not that common. Hence, I doubt there would be
much traction to rename the process from Compile Commands.

Michael


"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 05/12/2015 09:55:45 AM:
> ----- Message from Buck Calabro <kc2hiz@xxxxxxxxx> on Tue, 12 May
> 2015 07:38:39 -0400 -----
>
> To:
>
> "Rational Developer for IBM i / Websphere Development Studio Client
> for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>
>
> Subject:
>
> Re: [WDSCI-L] Compile commands and iProject property file
>
> On 11 May 2015 at 22:36,  <MichaelQuigley@xxxxxxxxxx> wrote:
> > Sounds like you should be using "User Actions" rather than Compile
> > Commands.
>
> I think Eduardo is using iProjects.  There isn't a 'User Actions'
> choice for iProjects.  I guess the idea is that is one is working
> offline, one doesn't need to do things on the server.
>   -buck
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.
"Misys" is the trade name of the Misys group of companies. This email and
any attachments have been scanned for known viruses using multiple
scanners. This email message is intended for the named recipient only. It
may be privileged and/or confidential. If you are not the named recipient
of this email please notify us immediately and do not copy it or use it for
any purpose, nor disclose its contents to any other person. This email does
not constitute the commencement of legal relations between you and Misys.
Please refer to the executed contract between you and the relevant member
of the Misys group for the identity of the contracting party with which you
are dealing.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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 Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.
"Misys" is the trade name of the Misys group of companies. This email and
any attachments have been scanned for known viruses using multiple
scanners. This email message is intended for the named recipient only. It
may be privileged and/or confidential. If you are not the named recipient
of this email please notify us immediately and do not copy it or use it for
any purpose, nor disclose its contents to any other person. This email does
not constitute the commencement of legal relations between you and Misys.
Please refer to the executed contract between you and the relevant member
of the Misys group for the identity of the contracting party with which you
are dealing.
--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & 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.