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? -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. ---------------------------------------------------------------------- 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
