Our SMS messing is actually email being sent to the proper email-to-SMS converter address. One problem I've found with email is latency. And, again, I'm thinking that some sort of infrastructure is needed to "route" the appropriate messages to the people who want to be informed of them. Our current method, using CA-OPS/MVS to send an SNMP trap to "Orion" which sends a message, maybe, to CA-Unicenter, which then creates an email which is sent to our MS-Exchange server, which sends it out, is controlled by the admins. A person cannot decide if they want to get messages or not. Of course, the messages go (hopefully) to the appropriate on-call person. The "I'll decide what, if anything, I want to be informed of" being made dynamically by the user was what I was thinking would be "different". Also, it seems to me, that "following" a particular "user" via a twitter-like mechanism would have less latency. Sometimes our emails get delayed. The worst case I can recall was an incident! that occurred about 19:00. The SMS message about that showed up on my phone at 09:00 the next day! And guess who "caught hell" for not responding quickly enough? Not the MS-Exchange server, or the email-to-SMS server, I assure you.
But then, it is quite possible that I'm trying to "fix" something that isn't even "broken". Wouldn't be the first time. Won't be the last. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * [email protected] * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM > -----Original Message----- > From: IBM Mainframe Discussion List > [mailto:[email protected]] On Behalf Of Lizette Koehler > Sent: Friday, March 09, 2012 10:39 AM > To: [email protected] > Subject: Re: A stupid idea? Using "twitter" like service for > z/SO, et al., event notification. > > >I'll admit that my mind is not running quite right today. > But something that is bouncing around is notification of > events happening on "servers", especially z/OS. Would it be > helpful, or stupid, to set up a "twitter" type, secured, > server. Then have the appropriate people from work, who have > smartphones or even PCs, be able to "follow" specific topics, > which may be things such as individual server names, or "z/OS > product job status", or "abended jobs". Or are some companies > doing something similar using SMS? We use SMS messages via > CA-Unicenter for monitoring CA-Unicenter "tickets" assigned > to our group. But we cannot individually decide if we would > like more. And we don't generate tickets for things like > "production job .... completed successfully on 2012-03-10 at > 13:58" or "Event ... has not completed successfully yet." On > weekends, we are totally "dark" and the on-call Production > Support person must periodically logon to z/OS in order to > check statuses. I thought it migh! > t! > > be easier if they got "tweets" about things. > > > >Of course, for all I know, this may be impossible due to > software patents. > > > > Of course there could be other software to do this. > > Things like CA Spectrum, eHealth, OPS/MVS, and Automation > point, could possible handle this type of request, if set up. > I believe the magic new word is MIB MIB > > > > Description: MIB = Management Information Base > > > > a) A collection of objects that can be > accessed by means of > a network management protocol. > > > > b) A definition for management information > that specifies > the information available from a host or > gateway and the > operations allowed. > > > > c) In OSI, the conceptual repository of > management > information within an open system. > > > Then SMTP or similar could be used to "tweet". > > Lizette > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
