Okay, here's the scenario. We are migrating from iSeries/ACMS to RDi/SVN, thus we want to make sure that the sources are migrated/uploaded correctly in SVN. The process goes like this;
1. determine (next) release library to upload
2. add change control information to the source
3. upload the sources to RDi
4. push back the sources to iSeries (using Push Changes)
5. perform compare of source members and produce reports for verification/checking
6. goto step1
For #4, we are expecting only the last uploaded sources will be pushed back to the iSeries since the initial release library sources were pushed already.
For #5, we expect no differences to be generated. Reports are crucial and this will also be used as the basis for declaring the upload a success.
Using remote reconciler will mean comparing the whole of the iProject against the remote release library sources which will most likely display lots of differences, one cause of which is the mismatched number of sources between the iProject (cumulative releases) and the remote library (single release). I understand that remote reconciler can still determine whether the upload is complete if none of the remote sources are missing or have any difference.
There may be a better way to do it and I'd appreciate any inputs but right now this is what we have. This is also the reason why I asked regarding how "push changes" work internally as I've encountered situations where 'push changes' do not push a particular source pf and its sources. However, when I changed the associated library and retried the 'push changes' action the same source PF got pushed.
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Edmund Reinhardt
Sent: Thursday, November 27, 2014 2:44 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: Re: [WDSCI-L] Pushing changed sources multiple times
There is another mechanism for keeping i Project in sync with an associated library.
Open the Remote Reconciler view.
It is better at detecting changes to the member's contents on the host but it does not look at member description or CCSID changes.
Regards,
Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i
Phone: 1-905-413-3125 | Home: 1-905-854-6195
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200 Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham, ON L6G 1C7
Find me on: Canada
From:"Fajardo, Eduardo" <eduardo.fajardo@xxxxxxxxx>
To:"WDSCI-L@xxxxxxxxxxxx" <WDSCI-L@xxxxxxxxxxxx>
Date:26/11/2014 06:27 AM
Subject:[WDSCI-L] Pushing changed sources multiple times
Sent by:"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx>
Is there a way to push changed sources a second time?
I pushed the changed sources and it worked well. I then cleared the associated library, tried pushing the changed sources again and nothing happened. I understand RDi uses a timestamp to determine the changed sources, I'm just not sure how it does it internally.
Initially, I thought RDi checks the source member timestamp against those in the associated library and pushes those that differ. It's not the case as per my test so I'd like to know how RDi determines the "changed sources"
in the hope that I can somehow tweak it to be able to push these changed sources multiple times if need be.
Thanks.
"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.
midrange.com
