×
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.
Paul Nelson wrote:
When I type wrklnk '/QNTC' I see the QNTC directory immediately. When I put
a 5 to display the contents, nothing happens except input inhibited. I left
one request going for 20 minutes before I killed the session. Sys req 2
didn't even work. I had to kill the job and disconnect my session.
Paul:
I wouldn't be at all surprised at this under various circumstances.
1. The older the release, the more likely it'll take more time.
2. The fewer Netserver PTFs have been applied, the more likely it'll
take more time. Last time I really looked, a _lot_ of Netserver PTFs
were not part of cumes and had to be sought out individually. It's
been a while, but I'd still ensure I had every one I could find.
3. If /QNTC linkage to Windows Network servers isn't established at
system startup time and there's a significant number of Windows PCs
in the domain/workgroup/whatever it is in your network for your
releases, the more likely it'll take more time.
Without recent OS/400, or better, i5/OS, without proper PTFs,
without pre-established linkage, _each_ PC might be contacted
serially, with some kind of timeout for each one. Twenty PCs with a
1-minute timeout apiece could hit 20 minutes easy. Thirty PCs? A
hundred?
But usually, once established, things work better until the next
system startup (IPL or restricted state, AFAIK).
Just some comments. YMMV. Caveat emptor. Carpe diem and "Arrrr!"
Tom Liotta
midrange.com
