×
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 03-Dec-2015 15:28 -0600, Dean Eshleman wrote:
Good observation. So, I thought I would check out your theory.
STRQSH
$
Cd /production/goanywhere/logs/2014-03-03
$
find . -type f | xargs grep QSYSOPR4
it lists 5 files that contain this text, then it just sits there
awhile. Probably at least a minute or two and the $ finally returns.
Interesting since there are only 5 files in the directory. What is
taking so long for the $ to appear?
As you can tell, I don't use QSHELL very much and forgot to pay
attention to the $.
My first reaction was... But that is quite near the opposite of what
I was experiencing!
So I just now tested using a typical grep request that I might make.
What I noticed this time, is that my issue was my own _confusion_,
based on how long the _initial shell prompt_ takes to appear after I
first enter QSH; my prompt is not the $, but reverting back to $ makes
no difference.
The effect merely *appears* to be that grep ran asynchronously,
because the initial prompt from *before* issuing the grep had not yet
been presented. Thus when eventually the prompt is presented, that text
appears to prefix the returned data; i.e. making the grep seem to have
returned control to the shell, whilst the grep work was still being
performed. That combined with the next prompt also being presented
slowly, allowed me to misinterpret the effects.
So I guess my only concern is why the initial prompt is taking such a
ridiculously long time to appear on v7r1, as compared to earlier releases.
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.