Chuck could the delay be a result of a too low activity level for the subsystem?


--
Bryan Dietz

On Dec 3, 2015, at 8:01 PM, CRPence <crpbottle@xxxxxxxxx> wrote:

On 03-Dec-2015 16:07 -0600, CRPence wrote:
<<SNIP>> 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.

Wow! Over eight seconds in /wall-clock time/, measured using a stopwatch, for the prompt to appear after the command line appeared on the IBM i 7.1 system. On each of the earlier releases I tried, the appearance is fast enough to be described as /presently/; effectively, appearing immediately-after the command line appears. I doubt the configuration on that one system is so ridiculously different or constrained, as compared with the other systems, so as to explain that huge delay.

Anyone know, and could share, what I should check to ensure an appropriate work management setup for starting the BCI job for QSH; i.e. what I can compare for conspicuous differences, beyond the following already investigated? The allocation (*ALC) and System Control (*SYSCTL) system values are near identical, and the maximum activity levels seem reasonable, the job priorities are equal [RUNPTY(20)], none are set to utilize prestart jobs [no PJE is defined for the PGM(QSYS/QP0ZSPWP) nor any environment variable named QSH_USE_PRESTART_JOBS on any system, so none setup to ensure the better performance], and all run in the *INTERACT pool... *but* the QZSHSH job on the v7r1 system seems to remain in a status of TIMA for an unusually long time, as compared to the other earlier releases.

I made a variety of attempts to find a PERFM APAR, including searching each of the job names, with the suspect job status and without, but all were fruitless.

Huh. Had I been doing much more than grep as my first request in QSH, I probably would have noticed that the effect I was concerned with when I first noticed a couple weeks ago, was _not just_ with the grep utility; e.g. the output from an ls request looks just as confusing with that long delay. Just happens, that I've had access to the system only for a very short time, and a good part of that time was spent away on holiday, and I have only barely begun /using/ the system other than some customizations; thus why my use of QSH had mostly been limited to performing a grep request, searching to find whether what I wanted to find, might be available, or if I needed to copy the data from elsewhere. I suppose also, typically I just use the QSH CMD('grep...') such that I never even see the prompt; but being early-on in what is effectively a transition to using that system primarily, has me operating differently, somewhat necessarily, until I get more /settled/.

--
Regards, Chuck

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].