> I was paying attention, and there's no reason to be insulting. Whoops. Sorry, that was not my intention!
> Are you saying that WLM recognizes these started tasks as running > under the TSO subsystem, and therefore recognizing commands > issued as transactions? WLM does not recognize that without any help. The started tasks are simply started tasks and therefore, absent any other criteria, they end up in SYSSTC. You can see "transactions" coming from those address spaces just as you would from TSO. It's just that WLM has no way of knowing what to do with them. See below. > A transaction for a job or a started task is a step, not a TSO command. > TSO response time goals are only meaningful when the TMP is run > under the TSO subsystem. TSO transactions are reported to SRM via SYSEVENT, not some hidden WLM interface. The transactional nature of the work is the same as real TSO because it is the real TSO TMP. It just happens to be running in a STC instead of a TSO address space. So SYSEVENTS get issued in the normal course of user interaction and those are what SRM (and WLM) "see" as transactions. BTW, TSO doesn't get any special case help from WLM. If you don't create a service class (and classification rules) for your TSO work, the work will go to SYSOTHER by default. The SUBSYS qualifier is the obvious way to direct classification rules for TSO work, but it is by no means set in stone. CC ---------------------------------------------------------------------- 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
