× 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.



Not really. The only Google hits right now are still my blog and the
midrange-l archives.

(Insert rant about documentation)

I've found that QESECARE usually runs longer after applying PTFs, or
changing the hardware configuration. So I would assume that it gathers
statistics and information about the system, which is then sent to IBM
together with the PTF order (the batching-together of this is probably
done because some legacy installations are still using a modem to
connect their ESA to ECS).

I've never had any issues with it, except that when it ran it consumed
all the IO and CPU the 520/515 machines had - I figured that was only an
issue because we're running the low end of IBMs spectrum.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
ChadB@xxxxxxxxxxxxxxxxxxxx
Sent: Tuesday, June 12, 2007 4:31 PM
To: Midrange Systems Technical Discussion
Subject: Re: QESECARE job


Yeah, that's the only mention i've found about it... I think his posting
mentions it, but he hadn't found out what the job was all about.

Did you ever find out anymore info on the QESECARE job Lukas?





Jerry Adams

<jerry@bwwholesal

e.com>
To
Sent by: Midrange Systems Technical

midrange-l-bounce Discussion

s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>


cc


06/12/2007 10:27
Subject
AM Re: QESECARE job





Please respond to

Midrange Systems

Technical

Discussion

<midrange-l@midra

nge.com>









Check the archives, Chad. Lukas posted something about this awhile
back.


* Jerry C. Adams
*IBM System i Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>



ChadB@xxxxxxxxxxxxxxxxxxxx wrote:
We just recently updated our V5R3 cume to C7121, and soon after doing
so noticed that SNDPTFORD is behaving differently. We now have a job
that kicks off and runs at a high CPU usage for over 5 minutes called
'QESECARE'
- the SNDPTFORD seems to hang until this job has run for a while.

While testing the situation I ended the QESECARE job and found that
the SNDPTFORD picked up and completely quickly at the point the
QESECARE job ended.

I can't find mention of QESECARE anywhere on IBM's knowledge base...
does anyone know what it does?



--
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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.