That's pretty much what we do. Except that our Prod Control people simply can't do "if I am not told otherwise, then everything is OK.". So they continue to logon to do a quick look to make sure that the cycle is running. Because if something goes wrong, and Exchange is down, they won't get notified in time to fix it before the people coming in early start screaming about "where's my report?". We don't actually print anything (no print operators at all any more), but keep our sysout on a Web based platform called Redwood. The users come in and logon to it to read their morning reports. And some of them do raise the roof if the report is not waiting for them.
Anyway, I was thinking that a "twitter" like service to which they could connect their home PC or smartphone would make it easier for them to track the activity on the system without the need to bring up a VPN connection and logon to TSO. Then go to CA-7 and do commands to see where the cycle is. Or use DA OJOB to check on running jobs. They'd just get a series of tweets like: SCRJ-12 JOB jobname (0884) COMPLETED NORMALLY. *** COMPLETED ***. HIGHEST CONDITION CODE = 0000. Hum, you know what? We have CA-OPS/MVS. I may write up a rule which will "log" those messages to a UNIX file, which would be read from a Web page served up on our z/OS HTTPD server. I'd date & time stamp them, so I could subset to the last "n" hours. That might be of interest to the Production Control people, rather than logging onto TSO and/or CA-7. I'll ask. -- 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 David Andrews > Sent: Friday, March 09, 2012 11:02 AM > To: [email protected] > Subject: Re: A stupid idea? Using "twitter" like service for > z/SO, et al., event notification. > > On Fri, 2012-03-09 at 11:29 -0500, McKown, John wrote: > > notification of events happening on "servers", especially z/OS > > We're small like you, lights-out after 9:00pm, and the operations > automation we have is all homebrew. > > I have a console monitor application, written in REXX, that > watches for > specific messages such as ABENDs. It also watches for messages with > MDBGHOLD=YES that remain un-DOMed for longer than a set > period. Normal > action is to send email via Lionel's XMITIP, and then to escalate to > another email address if the first recipient doesn't acknowledge (by > simply hitting 'reply' on their email client) within ten minutes. > > We have another application which runs as a final step of most of our > production jobs, and emails the responsible programmer(s) in the event > of ABEND or untoward return codes. An MPF exit backs up that > application in case the failed job had a JCL error or otherwise could > not continue to the last step. > > A third application analyzes our IDMS transaction log and filters for > unusual activity, emailing some of us who care about that > sort of thing. > > Automated email works great, mostly, and can include more diagnostic > information than a tweet (say) can include. When email doesn't work - > and it isn't foolproof - we rely on our users to call. > "Press 1 to wake > somebody up." > > -- > David Andrews > A. Duda & Sons, Inc. > [email protected] > > ---------------------------------------------------------------------- > 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
