|
On Aug 11, 2020, at 3:20 PM, mlazarus <mlazarus@xxxxxxxxxxxx> wrote:
I ran into an interesting situation that RDi could have handled better, IMHO. I was developing an RPGLE program and then decided I needed some SQL in there. Since the verifier uses the member type to determine the allowable syntax I needed to change the member type. I used RDi to change the member type to SQLRPGLE.(Remote systems > Properties > Type).
The member was still open. When I tried to save it I received a message along the lines of the local copy not existing. It proceeded to create a new, empty RSExxxxxx member in the QRPGLESRC file - each time I clicked on save. The current program open in the editor did not get saved to those members.
To resolve the immediate issue I just reversed the change type process, saved the member, exited and reopened it. There are several resulting behaviors that could be improved here.
- Ideally the change member type function can check if the member is open in the editor and do whatever it needs to do to realign the work file.
- I could have been prompted to copy/save from the original work file.
It's not a showstopper, but I thought I'd post it in case some else decides to change member types mid-stream. And maybe the RDI development team will decide it's worth fixing/implementing.
-mark
--
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.