×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 19-Dec-2014 09:20 -0600, Ken Killian wrote:
NOTE: Call the program again, and now debug works okay again. I can
see monitor variables again.
Don't know what happen, I guess I will attribute this some unknown
"Fluke"
I didn't even refresh my SEP, because I did not recompile the program
or anything.
Case-Closed.<Joy Joy>
Perhaps "closed", but also unresolved.?.? And maybe to come back, but
how repeatedly and\or pervasively.?
FWiW, I have no access to view the APAR SE59413 "RDI 9.0.1 MONITOR OF
VARIABLE FAILS WITH CPF7E10 DURING DEBUG" with text "After starting
debug an attempt to monitor a variable results in CPF7E10"; no idea why
they failed to record the issue with the proper\expected Symptom
"msgCPF7E10" to make the issue capable of being searched as a problem vs
merely as the message identifier as a[n otherwise meaningless] token:
<
http://www.ibm.com/support/docview.wss?crawler=1&uid=swg1SE59413>
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
