Re: Custom compiler commands not being saved.

Hello Mike and everyone.

Over the weekend I recreated my workspace and no longer have this issue.

Thanks everyone for your help.

Rob
On 2013-02-02 12:02 PM, Mike Hockings wrote:

Can you expand all the steps used in the "I created the command" macro ?

Mike



Mike Hockings, M.Eng., P.Eng.
IBM Rational Developer for System z and Power Systems Software Technical
Support
IBM Canada Ltd. Laboratory
[1]hockings@xxxxxxxxxx
voice 1-905-413-3199 T/L 313-3199 ITN 23133199


[2]wdsci-l-bounces@xxxxxxxxxxxx wrote on 2013-02-02 11:00:32:


From: Robert Rogerson [3]<rogersonra@xxxxxxxxx>
To: Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries [4]<wdsci-l@xxxxxxxxxxxx>,
Date: 2013-02-02 11:01
Subject: Re: [WDSCI-L] Custom compiler commands not being saved.
Sent by: [5]wdsci-l-bounces@xxxxxxxxxxxx

Hi Ken, I apologize for the length of time responding but as another
poster so eloquently put it, "work got in the way".

I tried your suggestion. I created the command, compiled an RPGLE

program

(which had errors) and was returned the error list. I then exited

with

File->Exit.
When I repoened RDp my custom command was no longer there.

I'm still stumped...

Rob
On 2013-01-31 9:58 AM, Ken Killian wrote:

Rob,

I have discovered that I have to successfully close RDP, to save my
settings...

Were you able to compile once with the new custom compile command?

Try that again, and then close RDP & re-open, and it should be there.

For me, once in a while, my RDP session locks up, when I have 20-
windows open... Go figure!
<LOL>

Oh well, just a suggestion, what has worked for me.

PS. I assume that you are using a Private Team, versus a "Group-
Team" locked on a network, which you might not rights to change. I
usually change my "Team" to my profile name, instead of the default,
which the name of my computer. Open the "TEAM" window to view...

-Ken Killian-
(423) 510-3129

-----Original Message-----
From: [[6]1]wdsci-l-bounces@xxxxxxxxxxxx [[2]

[7]mailto:wdsci-l-bounces@xxxxxxxxxxxx

] On Behalf Of Robert Rogerson
Sent: Thursday, January 31, 2013 9:35 AM
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Custom compiler commands not being saved.

Hi all,

I created a custom compile command thought Compile->Compile->Work

with

Compile Commands. When I first create the command it is available

and I

can use it. But when I close and reopen Rdp it has disappeared.

I still see the default commands CRTBNDPGM and CRTRPGMOD but my

customer

command is no longer there.

I am creating it in the correct place am I not?

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: [[8]3]WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: [4][9]http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: [[10]5]WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at [6]
[11]http://archive.midrange.com/wdsci-l.

References

Visible links
1. [12]mailto:wdsci-l-bounces@xxxxxxxxxxxx
2. [13]mailto:wdsci-l-bounces@xxxxxxxxxxxx
3. [14]mailto:WDSCI-L@xxxxxxxxxxxx
4. [15]http://lists.midrange.com/mailman/listinfo/wdsci-l
5. [16]mailto:WDSCI-L-request@xxxxxxxxxxxx
6. [17]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: [18]WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [19]http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: [20]WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [21]http://archive.midrange.com/wdsci-l.

References

Visible links
1. mailto:hockings@xxxxxxxxxx
2. mailto:wdsci-l-bounces@xxxxxxxxxxxx
3. mailto:rogersonra@xxxxxxxxx
4. mailto:wdsci-l@xxxxxxxxxxxx
5. mailto:wdsci-l-bounces@xxxxxxxxxxxx
6. mailto:1]wdsci-l-bounces@xxxxxxxxxxxx
7. mailto:wdsci-l-bounces@xxxxxxxxxxxx
8. mailto:3]WDSCI-L@xxxxxxxxxxxx
9. http://lists.midrange.com/mailman/listinfo/wdsci-l
10. mailto:5]WDSCI-L-request@xxxxxxxxxxxx
11. http://archive.midrange.com/wdsci-l
12. mailto:wdsci-l-bounces@xxxxxxxxxxxx
13. mailto:wdsci-l-bounces@xxxxxxxxxxxx
14. mailto:WDSCI-L@xxxxxxxxxxxx
15. http://lists.midrange.com/mailman/listinfo/wdsci-l
16. mailto:WDSCI-L-request@xxxxxxxxxxxx
17. http://archive.midrange.com/wdsci-l
18. mailto:WDSCI-L@xxxxxxxxxxxx
19. http://lists.midrange.com/mailman/listinfo/wdsci-l
20. mailto:WDSCI-L-request@xxxxxxxxxxxx
21. http://archive.midrange.com/wdsci-l