On Mon, 23 Oct 2006 15:55:09 -0500, McKown, John
<[EMAIL PROTECTED]> wrote:
>A recent post caught my attention about a Java program being run from
>from a UNIX shell "getting tired" after the first execution. TSO is set
>up so that each TSO transaction is known to WLM, so that it "resets" to
>first period. Does anybody know if the UNIX shell does the same? If not,
>doesn't that indicate that the more you do in a UNIX shell, accumulating
>service, the futher down your "periods" you go and likely response "get
>worse". Just like batch. But if you make UNIX higher priority or only
>have a single period, then batch UNIX will likewise fail to "degrade" in
>performance as it accumulates service. That that last statement true or
>false?
>
>In my opinion, IBM should consider that UNIX work is not all identical.
>And we need some way to have multiple types of UNIX work. Such as
>invoked from BATCH, invoked from TSO, invoked from an interactive shell
>(telnet, rsh, ssh, etc). Or am I full of it again?
>
Whether invoked via TSO, ISHELL, TELNET, a pid is a pid is a pid.
WLM is very flexible. You don't have to clasify all work in
the OMVS subsystem in an "OMVS" service class. You can classify it
into other appropriate service class(es) with similar work.
I have an "OMVS" service class set up with 2 periods similar to how you
might set up TSO (so you could even use the "TSO" service class as a
default if you wanted to and it was close enough to how you would
set up the "OMVS" service class). This gets all the interactive
shell work ... and we have lots with WAS and SAP on System Z. But
I have other classifications also. For example:
==============================================================
Classification:
Default service class is OMVS
Default report class is OMVS
Qualifier Qualifier Starting Service Report
# type name position Class Class
- ---------- -------------- --------- -------- --------
1 TN CTGP* ONLPRDHI CTGP
1 TN FTP* SYSSTC NETWORK
1 TN OMII* SYSSTC MONITOR
<remainder snipped>
==============================================================
My default service is OMVS.
CTGP* is CICS Transaction Gateway... in the same service class
as other production CICS work. FTP* is for the FTP daemon,
OMII* is for Omegamon unix processes, etc.
So given the different work qualifiers you can use, you should
be able to do what you need within the current WLM controlls.
Regards,
Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - GITO
mailto:[EMAIL PROTECTED]
z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
Mark
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
