×
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.
Simon Coulter wrote:
On 11/05/2010, at 8:43 AM, Albert York wrote:
I have not done much work with threads and I was wondering,
does each thread get a seperate job number?
No. Threads are part of the job. They do get a separate thread
identifier.
See for example, WRKJOB JOB(*) OPTION(*THREAD) OUTPUT(*PRINT)
followed by DSPSPLF QPDSPJOB SPLNBR(*LAST), for how the list of
thread identifiers for the current job would be listed. Those
commands issued interactively [as the latter requires], there would
normally be one thread with the status RUN, per its /running/ the
WRKJOB invocation, and the spooled output would appear something
like the following with the one job number:
<xmp>
5722SS1 V5R3M0 040528 Work with Job date\time Page 1
Job . : MYWS User . : MYUSR Number . . : 123456
--- Threads ---
Total Aux Run
Thread Status CPU I/O Priority
00000001 RUN .156 97 20
* * * * * E N D O F L I S T I N G * * * * *
</xmp>
Regards, Chuck
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
