Hi Ken,
I don't suspect you'll find SEP related messages in QHST. What I'd look for are CL commands acting on your 1) Library - ie SAVLIB or 2) Object (*PGM) - SAVCHGOBJ, SAVOBJ, CRTDUPOBJ, CHKOBJITG (etc).
I can't guarantee it's a back end issue, but when you see CPF* messages, it's generally a host side issue.
It could be the reconnect to vendor services caused a quick SAVCGHOBJ to save your library for High Availability (HA). Next time a SEP issues occurs, do a quick WRKOBJLCK command for the *PGM object, or the library you are running in. If you see a SAV* command running, you know you'll want to wait until that is completed before trying a SEP.
Another option is to ask for a walled off Library for test where the HA software ignores your library of test programs.
Thanks for submitting a PMR. They do help us to continually improve the product.
Steve Ferrell
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Ken Killian
Sent: Wednesday, August 21, 2019 7:39 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.6.0.6 SEP not working...
Steve,
I did not use the command: ENDDBGSVR. Because that knocks off the other developers.
Normally, I select my >Jobs >My active jobs. Then I open subsystem: QUSRWRK. And then I kill all those jobs. Which it then tells that I cannot kill my current job. That usually takes care of the CPF7102. I don't think I did that yesterday...
Because overall, SEP "generally" works good. But, yesterday it did not work. But, I forgot to kill my jobs running QUSRWRK.
Good to hear that it is on the back-end, not on the client software.
Looking at the history log, I did not find any "SEP" messages. But, I saw issues with TCP & journal. Apparently, they were trying to Reconnect to our vendor services.
Maybe that cause my SEP issues?
Oh well, I will open a case with PMR, and insert in my Error-Log in the Off-chance, that might find some useful information in my error log.
-Ken Killian-
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Steve Ferrell via WDSCI-L
Sent: Wednesday, August 21, 2019 7:01 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Cc: Steve Ferrell <Steve.Ferrell@xxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.6.0.6 SEP not working...
Hi Ken,
Did you try Justin's suggestion of bouncing the debug server? When SEP fails, it's generally a server side issue.
I found a great blog post from 2015 on SEP. One tidbit in there speaks to the CPF7102 and the possibility of a CL command issued during the SEP. You can look at the IBM i Log file for the time of day you were running into SEP issues and look for any of the following commands that were running:
CHKOBJITG
CPROBJ
CPYLIB
CRTDUPOBJ
RSTLIB
RSTOBJ
SAVLIB
SAVOBJ
SAVSYS
SAVCHGOBJ
Some HA software may be running in the background (doing a SAVLIB) and that could cause the SEP to fail. Don't reinstall RDi, get a green screen session fired up and do a DSPLOG command and filter for the time of day when you started having issues with SEP. I generally look about 5 to 10 minutes prior to the issue. If you see any odd SEP messages in the LOG, send them to IBM support so we can help them improve this process.
Here's a link to the Blog Post:
http://as400corner.blogspot.com/2015/11/debugging-programs.html
Thanks!
Steve Ferrell
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Ken Killian
Sent: Wednesday, August 21, 2019 5:27 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.6.0.6 SEP not working...
Surprise! New Day! Now SEP works again...
Good to know that SEP is unreliable, and unpredictable. Since it has issues and is NOT STABLE for whatever reason...
I should have reboot my whole PC yesterday. Instead of just rebooting RDI. This is reboot software to get it work. Strange, even creating a new workspace did not work.
This weekend, I will uninstall and then Re-install RDI. And hopefully, it might work better. And of course a BRAND New work space. So, that way I cannot blame a corrupt workspace.
I hope they are able to make SEP reliable in the future. I need to stop using SEP, since it has issues...
Cheers,
Ken
-----Original Message-----
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jon Paris
Sent: Tuesday, August 20, 2019 6:20 PM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.6.0.6 SEP not working...
In my experience it is only SEPs that can have issues - RDi debugger works fine in the same environment as a green screen debug. And SEPs have the same issues in green screen debug.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Aug 20, 2019, at 5:43 PM, Ken Killian <kkillian@xxxxxxxxxxxx> wrote:
What good is a debugger, if it is not reliable? Green Screen Debug works every single time without fail. Just have to scroll up and down more. Maybe that uses less memory, since it only loads approximately 20-lines of code. That must be it!
It supposed to be an I.D.D.E. (Integrated Debug/Development
Environment). I guess that is why it only has one “D”… <LOL> IDE
versus IDDE
Cheers to Green Screen debugger! It also allows me to change “VARCHAR” variable. RDI 9.6.0.6. cannot handle that. Yeah open a ticket on that too. I got too greedy, using RDI debugger. Oh well, green screen does work EVERYTIME TIME!
Cheers,
Ken
________________________________
From: WDSCI-L <wdsci-l-bounces@xxxxxxxxxxxxxxxxxx> on behalf of Lorne
<lorne.sturgeoff@xxxxxxxxx>
Sent: Tuesday, August 20, 2019 5:21:07 PM
To: Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries <wdsci-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: [WDSCI-L] RDi 9.6.0.6 SEP not working...
For what it's worth, we've been having the same issue with SEPs
sometimes failing to break since the days of WDSC. I've opened tickets
with IBM in the past. I've even spoken to some of the RDi developers
at our local user group. No solution as far as I know. IBM was unable
to recreate the problem on my last ticket.
For me, if is critical that the debug breaks when I need it, I don't
trust it to the RDi debugger. Other developers in our shop have had
similar experiences and most refuse to use the RDi debugger because
they can't trust it. Some use the Java debugger. Some use the green screen debugger.
Cheers,
Lorne
On Tue, 20 Aug 2019 at 14:25, Ken Killian <kkillian@xxxxxxxxxxxx> wrote:
Hi,
Trying to use RDI 9.6.0.6 and the SEP is not working...
I add the SEP for my program, and it does not pop-up in debug...
I scratched my head, and ask myself, what would IBM say to me... Oh
yeah, check the error Log, and I found this:
eclipse.buildId=unknown
java.fullversion=8.0.5.25 - pwa6480sr5fp25-20181030_01(SR5 FP25) JRE
1.8.0 Windows 10 amd64-64-Bit Compressed References 20181029_400846
(JIT enabled, AOT enabled)
OpenJ9 - c5c78da
OMR - 3d5ac33
IBM - 8c1bdc2
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product
com.ibm.rational.developer.ibmi.product.ide
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product
com.ibm.rational.developer.ibmi.product.ide
This is a continuation of log file
C:\Users\kkillian\IBM\rationalsdp\workspace-2019-07-24\.metadata\.bak
_0.log Created Time: 2019-08-20 09:23:56.536
org.eclipse.core.resources
Error
Tue Aug 20 14:10:35 EDT 2019
Marker id 374292 not found.
What the heck does that mean? How do I fix that?
I guess trying rebooting, as typical with this software...
-Ken Killian-
--
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@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
--
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@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
--
--
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@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
--
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@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
--
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@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
midrange.com
