×
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 27/04/2010, at 4:54 AM, MWHopkins@xxxxxxxxxxxxxxx wrote:
Are you using the green screen debugger or RDi? If using RDi, you
might be
getting a cached version of the source. If so you need to clear the
cache
so it will re-load the source.
I wasn't going to comment on this but I see someone else seems to find
this behaviour (of RDi) acceptable (or at least a given). Why is it
necessary to manually refresh the cache for debug? Given that OS/400
objects all have creation date and last changed date information, and
that all such information is accessible via public APIs, the debug
tool itself should be detecting that:
a) The program or service program has been updated
b) That the source in the cache no longer matches the modules
c) That the debugger should load a fresh copy of the current source
(at least for changed modules)
I don't use RDi so I don't know if this is documented/expected
behaviour but it seems wrong to me. Is there an option in RDi settings
that controls whether fresh source is retrieved for the debugger? If
so does it need to be enabled? If the debugger does behave as
described (requires manual intervention to refresh source) and
provides no configuration control over that behaviour then it seems to
me that is a defect and should be reported and fixed instead of
tolerated or worked around.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
midrange.com
