×
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.
Am using WDSC Advanced V5.1 - yesterday I was working in the RSE lab for
RPG tutorial. Had a member open in RSE editor, then tried to open the same
member in CODE. I got the "downloading" dialog box, just hung there. I
tried to kill it by taking the "X" box to exit - it kept coming back. I
finally killed off WDSC.
Looking at the log for the Communications Daemon, I see the messages that
it could not resolve to EVFDSPCH. However, the object is there, in
QDEVTOOLS (a V5R2 box), and *PUBLIC has *USE authority.
I had, as suggested in that tutorial, changed *CURLIB to RSELAB, as well as
adding RSELAB to the library list. This may be bad advice. There never was
a STRCODE *USRSPC created in RSELAB.
Next time I started WDSC, I got an error I don't remember, but it had
something to do with not being able to initialize the workspace. I'd had a
number of items open in WDSC for some weeks - I didn't have WDSC open, but
when I started it, the open editor sessions would still be there. They're
now gone. The sources on the 400 are OK, however. Whew!
Finally, I've been getting the "host server is busy" stuff.
I then ran STRCODE on the V5R2 box and used a PDM option to get a CODE
session up - worked fine - I can't believe I said the CODE server worked well!
Is there a problem opening members in both RSE and CODE at the same time?
Even different members?
I have since replaced the corrupt (I think) workspace with the one I had
before upgrading. We'll see what happens. At least things started better.
Vern
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
