|
On Oct 31, 2015, at 1:11 PM, Ken Killian <kkillian@xxxxxxxxxxxx> wrote:
Jon,
Thanks!
Did Green Screen bring up old source that was over 3-years old????????? I doubt that! Even though the code was updated and compiled from a different source file? Once again doubt that!
Green screen warns you if the source is not in synch.
And recently, at least RDI added a Record count check on debug, which I have found very helpful!
Now, if you change a line of code, and the count remains the same. It won't warning you, because it checks the counts, not the timestamp. :(
But, this is better than no check at all! <cool!>
Oh well, I like just like Green Screen Debug, I can toggle between *SOURCE/*LISTING mode. But, on this program, it was NOT compiled with *LISTING. To save space! <what a joke!>
Regardless, RDI burned me bad! They still talk about that...
<Big Frown>
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Saturday, October 31, 2015 1:01 PM
To: Wdsci-L
Subject: Re: [WDSCI-L] RDi 9.5 "not responding"
Just to make you feel better - I have had green screen debug show me the wrong source too!
On Oct 31, 2015, at 10:42 AM, Ken Killian <kkillian@xxxxxxxxxxxx> wrote:
I am working from home, and using a VPN connection. So "sort of" different...
I often leave my tabs open with RDI, so I can continue where I left
off! <Awesome>
Even though I started RDI, it did not seem to lock my member, until I
saved it. <Puzzled-Look>
I have gotten burned too many times using iProjects, so I "NORMALLY" avoid iProjects.
I had a HUGE system Error, and I proudly said "NO PROBLEM! I have RDI to save me!!!"
Long story short, RDI open an old member in "iProjects" from 3-years ago! When I tried to debug it!!!!!!
Not the current SOURCE!!!! UNACCEPTABLE!!!!!!!
So, I avoid iProjects because of that huge BLUNDER. Once again I was forced to use RELIABLE GREEN-SCREEN Debug...
Because I COULD NOT TRUST RDI!!!!
The "SEU-Pukes" had fun laughing at my beloved RDI... <frown> See, they chuckled, that is why we use SEU & GREEN-Screen DEBUG! IT ALWAYS WORKS!!!
It just works! And it NEVER FAILS! Unlike your "RDI" junk...
<Head hung down low in SHAME>
I love RDI, but it needs to be STABLE & PREDICTABLE!!!!!!!!!!
<rant over>
-Ken Killian-
-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of
CRPence
Sent: Saturday, October 31, 2015 10:33 AM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] RDi 9.5 "not responding"
On 31-Oct-2015 08:30 -0500, Ken Killian wrote:
Gee, I thought RDI & SEU handled member locks...
1.) Open the member in RDI for EDIT
2.) Open the SAME MEMBER in SEU for EDIT
It now allows this???? <shock!>
The SEU first attempts to get an Exclusive-Allow-No-Others (*EXCL) lock on the member when first loading, then if successful, obtains and holds an Exclusive-Allow-Readers (*EXCLRD) lock and then drops the Exclusive lock, while maintaining the *EXCLRD lock while the SEU on that member persists. Thus any thread that wants to access the data from the unsaved-changes can obtain a copy; that is why EDTF, CPYSRCF, RDi, or any other feature just requesting the data can get a copy of that data.
Each feature has the option of doing what SEU does, and prevent all but exclusive access, but any client editor effecting that requirement would be quite the deviant.
When I try to save it RDI, I get this message: CPF3156E ("...in use")
presumably correlating with the server msg CPF3156 "File &1 in library
&3 in use."
1.) Close SEU
2.) Save source in RDI
3.) try to reopen source edit mode in SEU, I get this:
EDT0221 - "...in use."
<<SNIP>>
AIUI the RDi holds an *EXCLRD lock like SEU [though I've no idea why given the concept is anathema for typical client-based editors AFaIK; an attempt to effect a conceptual difference between that as online-edit vs typical offline-edit, I suppose], and if so, the msg EDT0221 in that case would just reflect the inability of the STRSEU request to obtain that first Exclusive lock. And just a /save/ from the RDi vs the similar action of a /save and exit/ of the SEU, presumably has the RDi maintaining the lock, just as SEU would in a Save-with-return-to-edit.
I've no idea what\when RDi would drop their lock, if indeed held as I understand; what I found in a doc on the web for RSE LPEX editor was that "Locks released when editor is closed or the RSE connection is disconnected" but when using iProjects and LPEX editor "No RSE job needed on IBM i server Member PAYROLL is not locked" [noting that their example was editing SRCMBR(PAYROLL)] in a document entitled "Rational Developer for IBM i (RDi) Working offline using i Projects".
--
Regards, Chuck
--
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.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
--
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.
midrange.com
