Re: TSSO in a sysplex
I think I have answered my own question: I am only seeing messages in TSSO from other members of the JES2 plex, and no messages from members of the other JES plex. Shouldn't I see messages equally from all members of the sysplex? The hint came in the description of the WQE in the 'Using the Subsystem Interface' FM. The field WMJMFLG1, bit WMJMRISS indicates the message is an SVC reissue of a message that has already been processed by SVC WTO... Examples of using this indicator include messages that originate on one system (MVS sysplex), but are transported for display to another system. Since the systems from one of our JESplexen only route console messages to consoles on systems within the same JESplex, and the others likewise, no message traffic ever has to be passed to members of the other JESplex -- TSSO never sees them. Also, if the message is suppressed via MPF, it won't get passed to SSI function 9 on any other system other than the one it's issued on. Dana -- 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
Re: TSSO in a sysplex
So far I have made an update to TSSO to allow you to insert the system name that issued a message, into the OSCMD operand in the AOF table. That seems to be working quite well. But I've come up with another question. We have two JES2plexes running in one SYSPLEX. It appears that I am only seeing messages in TSSO from other members of the JES2 plex, and no messages from members of the other JES plex. Shouldn't I see messages equally from all members of the sysplex? In reading the FM, it talks about the order of subsystems, and cautions that one subsystem might receive a message after it has been altered by another watcher of SSI 9, could JES2 possibly be snuffing out messages from other JESplexes before poor TSSO gets to see them.The FM goes on to say that SSI 9 isn't the recommended way to process WTO's now. It offers MCSOPER and MCSOPMSG services as a more up to date way to do it. Do you think that could possibly work better in this area? Thanks Dana -- 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
Re: TSSO in a sysplex
Hi Dana, we had a similar problem and looked at both freeware and alternative low cost solutions for this. In our case we have two CEC each with four LPARs. After experimenting with TSSO our management rejected it, because we could not afford to make a system programmer resource available to update and maintain it. I believe that it may be possible to re-write some of the code to do this, but I was told to leave it and instead concentrate on looking at alternative technologies. There are some very credible programs out there that you may wish to look at which can be downloaded from the internet. You may have to do a google search to find them, but take a look for Szyzgy and Exspans AutoMan. The Szygy product is a very credible replacement for TSSO and the Exspans product is popular in Europe as a replacement for Netview. In the end we did chose one of these and have been happily using it for a couple years now. The big advantage is the level of support that we got for setup, we never technical problems, and really only needed advice on the best ways to do things. On Tue, Aug 11, 2009 at 7:59 PM, Dana Mitchell mitchd...@gmail.com wrote: Hello, We are considering replacing Netview for simple message automation with TSSO from the CBT tape. I have it up and running successfully but I have one question. Currently we have two Netview subsystems running on two members of a sysplex, each processing messages from a subset of sysplex members. Is there a way to duplicate this setup, having TSSO process only messages from a subset of sysplex members? or alternately, be able to identify what system a message was issued from in TSSO processing? thanks Dana -- 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 -- 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
Re: TSSO in a sysplex
Thanks for the compliment. The company name is Syzygy :), but it's frequently misspelled. The web site for the automation products is www.SyzygyInc.com Brian -- 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
