On Fri, 22 Sep 2006 08:09:02 -0400, Gabriel Tully <[EMAIL PROTECTED]> wrote:
>On 9/21/06, Ted MacNEIL <[EMAIL PROTECTED]> wrote: >> I recently discovered the SYSNAME command. >> It's great for monitoring activity on one system from another. > >One caveat I've noticed when monitoring jobs and tasks running on >another system in a JES2 MAS is the job log can sometime lag behind. >So, when I am waiting for an important message or troubleshooting an >outage, I tend to go directly where the trouble is. Also, 'set >display on' is very helpful, especially if you get into setting >sysname, filters, owners, and the like. > If you are running in a parallel sysplex, implementing and using operlog will elminate this issue. It's really a great tool to have in a sysplex regardless. >Maybe you guys could comment on the 'delay' and let me know if I am >crazy or if there is a technical reason for this behavior. > The delay is buffers. You can't see output from another system if it hasn't been written to the spool yet. However, since OS/390 2.10, if you are willing to set up MQ for use with SDSF you don't have to live with this little annoyance (and you get a few other sysplex wide panels like INIT and PR and a few other related panels in z/OS 1.2). Bon't don't get me started on the SDSF + MQ subject... Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group mailto: [EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
