Re: Copy Members to...

[Daniel Gross <daniel@xxxxxxxx>]

Hi Thomas,

it would be good, if the „Copy members to…“ would show the target file and member where it effectively copies - when using the „Rename existing member“ function is used. 

If you are already working on that function … ;-)

Thanks and kind regards,
Daniel 



> Am 28.10.2022 um 08:02 schrieb Thomas Raddatz <thomas.raddatz@xxxxxx>:
>
> Hi Greg,
>
> It is correct, that " Copy members to... " copies the member on the host and not the one you are editing in RDi. So that makes it possible to copy the member while you edit it.
>
> I think I will add a check box to ignore the "Member is open in editor and has unsaved changes." error.
>
> Thomas.
>
> -----Ursprüngliche Nachricht-----
> Von: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von Greg Wilburn
> Gesendet: Donnerstag, 27. Oktober 2022 20:02
> An: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
> Betreff: Re: [WDSCI-L] Copy Members to...
>
> Thomas,
> I guess I assumed the Copy members to... was copying the file member on the host.  Our source code is in Source PF members.
> If that's not the case, I could see where this would be a problem.
>
> But if I were editing a source member in SEU on one 5250 session, then used SEU to copy the member in another session, I would copy the un-saved version.
>
> My "change management" consists of creating a backup member:
>
> MYPGM
> MYPBM.B4 - before my changes
>
> -----Original Message-----
> From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Thomas Raddatz
> Sent: Thursday, October 27, 2022 1:37 AM
> To: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
> Subject: Re: [WDSCI-L] Copy Members to...
>
> Hi Greg,
>
> This message comes from the iSphere plug-in. I assume that you have updated not only RDi, but also iSphere.
>
> I changed the behavior of the "Copy Members to" dialog with iSphere 4.2.5 (January 2022):
>
> Changelog: iSphere 4.2.5.b003
> -----------------------------
> • Fixed problem that the record length of the target source file was
>   not always checked, when copying members. Not check, when the
>   target member existed.
> • Changed the "Copy Members to..." option to disallow copying dirty
>   files at all.
>
> So what can we do? I probably could add another ignore errors option next to the "Ignore data lost error".
>
> What do you guys (not only Greg) think?
>
> Thomas.
>
> -----Ursprüngliche Nachricht-----
> Von: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> Im Auftrag von Greg Wilburn
> Gesendet: Mittwoch, 26. Oktober 2022 22:16
> An: Rational Developer for IBM i <wdsci-l@xxxxxxxxxxxxxxxxxx>
> Betreff: [WDSCI-L] Copy Members to...
>
> I recently updated RDi... now for whatever reason it won't copy a member if I have the member open with unsaved changes.
>
> "Member is open in editor and has unsaved changes."
> "Validation ended with errors. Request canceled."
>
> WTH?
>
> I want to save a copy BEFORE I save the changes... so now I have to do so in SEU?
> [Logo]<https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fwww.totalbizfulfillment.com&umid=9f6404ac-fc3f-4e12-a365-1a91735bf409&auth=89805744c9623ed2b024661d92742ecf671e63bd-bf80b03231cb3805df37c53f36434b25dde08e3a>    Greg Wilburn
> Director of IT
> 301.895.3792 ext. 1231
> 301.895.3895 direct
> gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
> 1 Corporate Dr
> Grantsville, MD 21536
> https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=www.totalbizfulfillment.com&umid=9f6404ac-fc3f-4e12-a365-1a91735bf409&auth=89805744c9623ed2b024661d92742ecf671e63bd-65d843a5a190176281ea70af3fb88e58343545d8<https://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=http%3a%2f%2fwww.totalbizfulfillment.com&umid=9f6404ac-fc3f-4e12-a365-1a91735bf409&auth=89805744c9623ed2b024661d92742ecf671e63bd-712283d6fb453dfbd725e8ad3c935e401c0c3b44>
> -- 
> This is the Rational Developer for IBM i   (WDSCI-L) mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> -- 
> This is the Rational Developer for IBM i   (WDSCI-L) mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> -- 
> This is the Rational Developer for IBM i   (WDSCI-L) mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives at https://archive.midrange.com/wdsci-l.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com
> -- 
> This is the Rational Developer for IBM i   (WDSCI-L) mailing list
> To post a message email: WDSCI-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
> or email: WDSCI-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/wdsci-l.
>
> Help support midrange.com by shopping at amazon.com with our affiliate
> link: https://amazon.midrange.com