Job Status tab automatically opening... -- WDSCI-L

I'm now using Eric and Charles' suggestion of using the RSE view instead
of the RSE perspective when editing. It works great and saves be time as
I don't have to keep switching perspectives. But now I'm experiencing
another slowdown.
When I create an object (compile) the job status tab always opens. Is
there a way to keep this from happening?
Here is my screen before I create(compile).
([1]https://www.dropbox.com/s/md1d2oyolm8fi2d/Screenshot%202014-01-24%2012.33.58.png)
And after I create (compile).
([2]https://www.dropbox.com/s/ncmjt2n0jfi87qs/Screenshot%202014-01-24%2012.38.42.png)

It's not stopping me from doing my work but I very rarely use it. So when
I need it I can added the view. I just wonder if there's a preference
setting that I can't find to stop it automatically opening.

Thanks,

Rob
On 2014-01-19 6:43 PM, Charles Wilt wrote:

Sorry, just realized I hadn't sent this :)
No, I'm talking about the menu bar...
Charles

On Fri, Jan 17, 2014 at 2:34 PM, Robert Rogerson
<[3]rrogerson@xxxxxxxxxxx> wrote:

Thanks for sharing this Charles. As for the view I already responded
to Eric Simpson's suggestion of the view and it helps.

One last thing...When you speak of the option on the menu bar you are
not referring to the create button, correct? For me, the button does
not always create the member in the editor. For example, if I'm
editing programA and then open programB for editing and then ctl-F6 to
switch back to programA the compile button may be greyed or it may
create programB (if it is still selected in RSE). I have run into
this a number of times and so I always select the correct member in
RSE before I create the object.

Thanks Charles and have a nice weekend.

Rob
On 2014-01-17 1:52 PM, Charles Wilt wrote:

Rob,
I took the conversation off list as David doesn't partiulily approve
of having discussions of CMS software on the list :)
When I brake up development into phases like you are doing, I do it
inside seperate releases. When a phase moves to production, I use
the "Promote to parent" functionality to move it to the regular
release.
As far as having to open a new perspective, I don't use the iSeries
editing perspective as I don't find it useful; for two reasons, the
outline is not shown and I can always get a full screen simply by
double clicking the editor tab. I use a customized version of the
standard remote system explorer.
but...all you need to do is do an Window-->Show View-->Remote
Systems and you've have access to RSE. You can move it around,
detach it or minimize it. Then you can save the changes to the
perspective or save it as a new perspective with whatever name you
want.
Note that even with RSE not show in IBM i Editing, I still have an
option on the menu bar for Rocket Aldon LM that I can use for
compiles.
HTH,
Charles

On Fri, Jan 17, 2014 at 9:46 AM, Robert Rogerson
<[4]rrogerson@xxxxxxxxxxx> wrote:

Charles,

I think I understand what you mean and we do/can break larger
projects
into smaller (LM(i)) tasks. But one of the advantages we've found
is
that during development, by using a temporary ID (and setting up a
separate library for that ID) is that while testing the temporary
library can be added to the library list to only test the phase's
specific modifications. In this way (for example) the first phase
of a
project can be tested without the chance of the test results being
affected by the second phase's objects. If we used the same
developer
(and at least at our shop the developer and his/her library have a
one-to-one relationship) this would not be possible without
deleting the
phase two objects first.

This is how we currently work and the reason we do it this way.
But we
have only been using LM(i) for six months so if you see a flaw in
our
thinking or know of a better way please share it.

On another note. I take it that you also use LM(i). One of the
things
that bugs me when creating an object is that I must switch back to
the
RSE perspective, select the object to create, and then create it
(using
right click, the LM(i) menu or the create object button). Most of
the
time when I'm editing use the IBM i Editing Perspective (from the
SoftLanding plug-in). But when I want to create the object I have
to
switch back to the RSE perspective.
If I were doing a straight compile (outside LM(i)) then the editor
knows
the library/file(member) to compile and I don't need to switch
perspectives. I would think that the LM(i) plug-in should be able
to do
the same.
Do you know of a way around this or must I just accept that this
is how
it works.

Thanks,

Rob
On 2014-01-17 8:51 AM, Charles Wilt wrote:
> Rob,
>
> When I say task, I mean the Aldon task, ie. option 5 - Work
with tasks,
> from the main Aldon menu.
>
> In the LM(i) RDi filter, task is one of the filter criteria you
can use.
>
> Charles
>
>
> On Thu, Jan 16, 2014 at 4:47 PM, Robert Rogerson
<[5]rrogerson@xxxxxxxxxxx>wrote:
>
>> 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,
>>>
>>> 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
<[6]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,
>>>>>
>>>>> 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
>>>> browse
>>>>> mode when you try to open them in edit.
>>>>>
>>>>> Charles
>>>>>
>>>>>
>>>>> On Thu, Jan 16, 2014 at 1:38 PM, Robert Rogerson <
>> [7]rrogerson@xxxxxxxxxxx
>>>>> wrote:
>>>>>
>>>>>> 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
>> time
>>>>>> I only want to browse so to select to Open for Browse is a
couple
>> extra
>>>>>> key strokes.
>>>>>>
>>>>>> Searching the archives I found this thread
>>>>>>
([8]http://archive.midrange.com/wdsci-l/200704/msg00372.html) from
>>>> Violaine
>>>>>> (now there's a name from the past). Does anyone know if
the
>> preference
>>>>>> ever got added?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Rob
>>>>>> --
>>>>>> 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: [9]WDSCI-L@xxxxxxxxxxxx
>>>>>> To subscribe, unsubscribe, or change list options,
>>>>>> visit:
[10]http://lists.midrange.com/mailman/listinfo/wdsci-l
>>>>>> or email: [11]WDSCI-L-request@xxxxxxxxxxxx
>>>>>> Before posting, please take a moment to review the archives
>>>>>> at [12]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: [13]WDSCI-L@xxxxxxxxxxxx
>>>> To subscribe, unsubscribe, or change list options,
>>>> visit: [14]http://lists.midrange.com/mailman/listinfo/wdsci-l
>>>> or email: [15]WDSCI-L-request@xxxxxxxxxxxx
>>>> Before posting, please take a moment to review the archives
>>>> at [16]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: [17]WDSCI-L@xxxxxxxxxxxx
>> To subscribe, unsubscribe, or change list options,
>> visit: [18]http://lists.midrange.com/mailman/listinfo/wdsci-l
>> or email: [19]WDSCI-L-request@xxxxxxxxxxxx
>> Before posting, please take a moment to review the archives
>> at [20]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: [21]WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [22]http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: [23]WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [24]http://archive.midrange.com/wdsci-l.

References

Visible links
1. https://www.dropbox.com/s/md1d2oyolm8fi2d/Screenshot%202014-01-24%2012.33.58.png
2. https://www.dropbox.com/s/ncmjt2n0jfi87qs/Screenshot%202014-01-24%2012.38.42.png
3. mailto:rrogerson@xxxxxxxxxxx
4. mailto:rrogerson@xxxxxxxxxxx
5. mailto:rrogerson@xxxxxxxxxxx
6. mailto:rrogerson@xxxxxxxxxxx
7. mailto:rrogerson@xxxxxxxxxxx
8. http://archive.midrange.com/wdsci-l/200704/msg00372.html
9. mailto:WDSCI-L@xxxxxxxxxxxx
10. http://lists.midrange.com/mailman/listinfo/wdsci-l
11. mailto:WDSCI-L-request@xxxxxxxxxxxx
12. http://archive.midrange.com/wdsci-l
13. mailto:WDSCI-L@xxxxxxxxxxxx
14. http://lists.midrange.com/mailman/listinfo/wdsci-l
15. mailto:WDSCI-L-request@xxxxxxxxxxxx
16. http://archive.midrange.com/wdsci-l
17. mailto:WDSCI-L@xxxxxxxxxxxx
18. http://lists.midrange.com/mailman/listinfo/wdsci-l
19. mailto:WDSCI-L-request@xxxxxxxxxxxx
20. http://archive.midrange.com/wdsci-l
21. mailto:WDSCI-L@xxxxxxxxxxxx
22. http://lists.midrange.com/mailman/listinfo/wdsci-l
23. mailto:WDSCI-L-request@xxxxxxxxxxxx
24. http://archive.midrange.com/wdsci-l