|
Charles,
I use RDi exclusively for development. For each task I create (or reuse
on old) LMi filter so for me there is never any confusion. But our
administrator uses the green screen and sometimes has difficulties which
specific objects are to be promoted for a developer..
You mention that
Aldon has tasks you can use to segregate filters
Are you referring to the green screen? The idea for temporary ids was
suggested to me by the administrator after Aldon suggested it to her.
Do you know of another way? (I don't mind looking it up in the manuals if
you can provide the keywords to search on).
Thanks,
Rob
On 2014-01-16 4:19 PM, Charles Wilt wrote:
Rob,rrogerson@xxxxxxxxxxx
Seems very strange to create temporary IDs...
Especially when you have both RDi and Aldon.
Aldon has tasks you can use to segregant filters and RDi (and the Aldon
plugin) have filters that you can use.
Charles
On Thu, Jan 16, 2014 at 3:21 PM, Robert Rogerson <rrogerson@xxxxxxxxxxx
wrote:
Thanks for the suggestion Charles. I (being an outside consultant) was
surprised that the production source files weren't locked down and only
editable if checked out and in the development environment. When I
mentioned this to the administrator she said that she would add this to
her list of things to do.
I will confirm this when the authorities have been changed. But I think
your suggestion will work. In order to break large projects down to
smaller tasks we create a temporary developer for only the task's
objects. So if you forget the change your developer id to the temporary
id and try to edit a member the member always opens in browse mode. I
think the same will happen when the authority to the production source
files is revoked.
Thanks,
Rob
On 2014-01-16 2:18 PM, Charles Wilt wrote:
Robert,browse
I don't know...
However, you may want to consider removing your write access to the
production source files in which case RDi will offer to open them in
mode when you try to open them in edit.
Charles
On Thu, Jan 16, 2014 at 1:38 PM, Robert Rogerson <
timewrote:
Hi folks, we use Aldon LMi for change management to when a member is
open to edit we always use the LMi connection.
But if just want to browse a member I'll typically use Ctl-Shft-A to
open the member. The default is to Open for Edit. Almost all the
extraI only want to browse so to select to Open for Browse is a couple
preferenceViolainekey strokes.
Searching the archives I found this thread
(http://archive.midrange.com/wdsci-l/200704/msg00372.html) from
(now there's a name from the past). Does anyone know if the
Studioever got added?
Thanks,
Rob
--
This is the Rational Developer for IBM i / Websphere Development
--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.
--
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.
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.