>however, if i wanted to browse/see through the >JESYSMSG/sysprint of the STC, when i am unable to logon to the affected >LPAR(session HUNG due to high CPU.
If you cannot logon, use the operator reset command to reset your TSO userid into SYSSTC. That may (or may not) allow you to logon. Every other tool you are going to use in a cpu starved environment will also need it's dispatching priority adjusted by resetting it into a higher service class. Keep in mind that you may not even be aware which tools need to be reset, depending on *where* (i.e. in which address space) the code for a command executes (example: If VTAM and/or TCPIP don't get enough cpu, they cannot show you the output from the tool you have just used). Also keep in mind that resetting something into a higher service class distorts the results. Regards, Barbara Nitz ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
