×
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.
Tasks are not objects - they are low-level - below MI - entities.
Actually, a task is the general name for things like threads and
jobs, as well. The name you see here is some routine in SLIC,
probably. The naming down there is often not at all what we are used
to in CPF, what we often THINK is the operating system. There's
actually a routine in SLIC called dataOut (IIRC) - it's intended
strictly for internal use to test DB statistics operations. Other
task names include CFINTn - where n is a processor number, as I
recall. As usual with IBM, the 2-letter abbreviations do identify a
class of functionality. Don't know this one - but looks like
something to do with ASCII, were I to make a guess.
If you have Performance Tools, you can see both jobs and tasks using
WRKSYSACT command. Also, tasks typically run at priorites less than
our zero - there are 155 priority levels that are below our 100 that
we can set on a job.
HTII (hope this is interesting!)
Vern
At 10:47 AM 8/15/2007, you wrote:
I would look to see "who" owns that object. That doesn't
seem to be IBM naming.
rob@xxxxxxxxx wrote:
> V5R4
> WRKSYSACT shows high cpu usage.
> About all of this usage is due to task SK-ASC039P.
> What is this?
>
> Rob Berendt
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
