Hi Ed, Do you have access to login to the HMC? I had a similar situation and couldn't logon to TSO or even CA-SYSVIEW or another product we have named BimEdit (From CSI Inc.), which both have authority to issue Commands and see the SYSLOG. Since I couldn't use those products, I signed into the HCM and selected the LPAR and clicked on System Messages and, Bingo, I was in and able to cancel the offender and get the System back running as it should. Even though I was at home, this was an LPAR running our EURO branches and it was during their Primetime and had to be fixed as fast as I could. If I couldn't get it running quickly, I would have had to go into the office to fix the issue as this was a period that we did not have an operator onsite for me to talk to.
Don't get me wrong, When I am at work, I prefer to be able to go into the Computer room, but I am always interested in ways to work on and fix problems once I am at home, without having to get up and dressed and go into the office. I have been doing System Programmer work for over 30 years and I remember times before remote login where we did go into the office, even for issues that only took 5-10 minutes to get things going again. I am very happy that those times are in the past and not something I have to do today. Thanks...Guy M. Gates Jr. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Edward Gould Sent: Wednesday, September 28, 2016 11:10 AM To: [email protected] Subject: Re: remote system support (i.e. the data center is 2 states away from you). > On Sep 28, 2016, at 12:28 AM, Brian Westerman <[email protected]> > wrote: > > Hi John, > > Our company (Syzygy Incorporated) fully supports more than 70 sites remotely, > all over the world. On top of that we provide partial support for another 60 > to 70 sites. Some are large (300+MSU) and some are quite small (8 to 10 > MSU), but they all need our expertise and not being "on-site" has never been > an issue. We also have a suite of system automation products that we > maintain at several hundred sites. > > Even 10 to 12 years ago, it was very unusual to be "at" a site or if you were > physically there, to be anywhere near the actual computer room. Once a site > realizes that the systems programmer doesn't need to be in that room, it's > only a small jump for them to understand that you get just as much support > from the next floor, or the next building, or the next city, etc. I can > still remember some knock-down drag out fights between the systems > programmers and the operations group on whether or not the systems > programmers should ever be allowed into the computer room. We (systems > programmers) always won that argument, but now I wonder why I fought it for > so long. :) ——————————SNIP——————————————— I will disagree with you on this one. Our data center is on 2 floors and running upstairs is still needed as consoles (except the master) is still needed to this day. Just last week all consoles (except the master) were locked out (TSO was dead as were other possibilities). We were able to get the system back (and working in good order) by a combination of operator commands. Ed ---------------------------------------------------------------------- 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
