Re: HMC hardware messages
I wish we would have had this feature 40 years ago. At that time we shut the entire data center down on Sundays. Some time Sunday morning we had a consultant from a well known company came into the DS and IPL’d one of our system and turned off SMF recording and EREP and ran a bunch of jobs. Come Monday morning I was casually walking through the DS and went over to an out of sight 3215 (hard copy console) and while I was looking through the HC I saw the IPL and the operator (consultant) turning off SMF and EREP. I went over to the manager and asked what was going on Sunday and I explained to him what I saw on the HC and he said no-one was working and I took him over and showed him the log. He quickly looked at the security system and saw that a consultant had been there. I asked him if we shout tell the VP or not. He told me to go up there and explain what had happened. The VP managed to let me see him after I explained to his secretary what had happened. The VP told the consulting company that if the person had updated any DS they would be marched off the premises that morning. If I hadn’t chanced looked at the hidden console we would not have known. Ed > On Nov 28, 2023, at 3:04 PM, Tom Brennan wrote: > > That reminded me of Skip Robinson testing out autoipl parameters when that > was new, and one morning maybe 4am our Dev system died and IPL'd itself. No > notification, no complaints, and we only saw it by chance. I think we added > emails to ourselves via startup task after that. > > On 11/28/2023 12:46 PM, Radoslaw Skorupka wrote: >> W dniu 28.11.2023 o 05:09, Bhum Muth pisze: >> Of course ticket creation is another topic. But it cannot be simply >> automatic creation of ticket for every message, because many of them are >> just notification. >> Example: REIPL. > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HMC hardware messages
We use Broadcom's OPS/MVS as an automation tool. This allows us to register for hardware events through the OPSBCPII server to get the messages in the syslog/opslog and write some automation on it, including sending out tickets. If you don't have OPS, maybe you can do something with HWIEVENT, which you can use to register for BCPII events. I have an additional question, if you would allow me. Does somebody know of a list which contains all the possible z hardware events? Dries. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HMC hardware messages
This thread has got me thinking about services like IFTTT and Pushcut to handle notifications etc from the HMC. But then I guess none of you would be allowed to build anything around them. Cheers, Martin From: IBM Mainframe Discussion List on behalf of Grant Taylor <023065957af1-dmarc-requ...@listserv.ua.edu> Date: Tuesday, 28 November 2023 at 23:43 To: IBM-MAIN@LISTSERV.UA.EDU Subject: [EXTERNAL] Re: HMC hardware messages On 11/28/23 2:46 PM, Radoslaw Skorupka wrote: > Of course ticket creation is another topic. But it cannot be simply > automatic creation of ticket for every message, because many of them are > just notification. > Example: REIPL. I don't know about ticketing systems, but with email, I create rules to detect things that are known okay; REIPL, and mark the message as read. That way it's there and I can got to the folder if I want to see it. But it's not unread and vying for my attention. Our old ticketing system had the ability to do similar. There were multiple macros set up to assign the ticket to me / my group, add comments, and mark the ticket as resolved. I'm still trying to figure out if our new ticketing system can do anything like that. Ideally don't send notifications that are largely noise. If you can't avoid that, automate resolving them. -- Grant. . . . unix || die -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Unless otherwise stated above: IBM United Kingdom Limited Registered in England and Wales with number 741598 Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HMC hardware messages
On 11/28/23 2:46 PM, Radoslaw Skorupka wrote: Of course ticket creation is another topic. But it cannot be simply automatic creation of ticket for every message, because many of them are just notification. Example: REIPL. I don't know about ticketing systems, but with email, I create rules to detect things that are known okay; REIPL, and mark the message as read. That way it's there and I can got to the folder if I want to see it. But it's not unread and vying for my attention. Our old ticketing system had the ability to do similar. There were multiple macros set up to assign the ticket to me / my group, add comments, and mark the ticket as resolved. I'm still trying to figure out if our new ticketing system can do anything like that. Ideally don't send notifications that are largely noise. If you can't avoid that, automate resolving them. -- Grant. . . . unix || die -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HMC hardware messages
That reminded me of Skip Robinson testing out autoipl parameters when that was new, and one morning maybe 4am our Dev system died and IPL'd itself. No notification, no complaints, and we only saw it by chance. I think we added emails to ourselves via startup task after that. On 11/28/2023 12:46 PM, Radoslaw Skorupka wrote: W dniu 28.11.2023 o 05:09, Bhum Muth pisze: Of course ticket creation is another topic. But it cannot be simply automatic creation of ticket for every message, because many of them are just notification. Example: REIPL. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: HMC hardware messages
W dniu 28.11.2023 o 05:09, Bhum Muth pisze: Did anyone in this group automated HMC hardware messages to send an email alerts or create a ticket internally to track other than IBM tickets? Any pointers to automate this would be great help - Thank You This is built-in feature of HMC. Note: ANY hardware msg will be sent, despite on its importance. IMHO it is better to get notification of every message than to miss any. Of course ticket creation is another topic. But it cannot be simply automatic creation of ticket for every message, because many of them are just notification. Example: REIPL. -- Radoslaw Skorupka Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
HMC hardware messages
Did anyone in this group automated HMC hardware messages to send an email alerts or create a ticket internally to track other than IBM tickets? Any pointers to automate this would be great help - Thank You -BM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
