> On May 25, 2018, at 12:39 PM, Jesse 1 Robinson <jesse1.robin...@sce.com> > wrote: > > I'm sympathetic to the argument that new stuff should be investigated, but > the problem is whether that really happens in practice. We've all met the > sysprog who meticulously codes parameter defaults as a kind of in-your-face > documentation so that 'we will all know' what's happening. Then years later > the defaults change, but the user-coded list does not get updated. Call me > Pollyanna, but I'm willing to trust the latest default. > > As for getting inconsistent results, I suspect that SMP/E results can be > influenced by the particular mix of elements being processed in a given run. > That is, applying SYSMOD-A and SYSMOD-B in the same step might uncover a > sinkhole that applying one sysmod or the other alone would not. This problem > is very difficult to detect in development and may require a lot of customer > activity to unearth. > > . Jess1, *YEARS* ago with a well known vendor I was trying to apply a zap (gotten in Hardcopy from the vendor) the module was right but the csect did not exist in the module flushed the zap, I called the vendor and the person I talked to started to argue with me about how I coded the zap. I was annoyed and said fine I will fax you the output. I faxed him the sheet of paper.. I did not hear back from him in an hour so I called him. He said I had coded the zap wrong, I looked at the zap again because I do not miscode zaps. I did this on the phone with him. I said the first column is blank and then the word "name” and then there is the module name and a blank and the csect name, the rest of the card out to 72 is blank. What is wrong with it? He said you must be a beginner you never code zap statements like that. I said EXCUSE me that is how a the first zap statement is coded, I do this daily with another vendor and that is by the book how its done. He told me I was wrong and not to bother him again. I said what? He hung the phone up on me. I went to the boss and explained to him what had transpired and he took a look at my zap statements and he said OK we will get him on the line. The guy hung up the phone and soon as he heard the company. My boss called the marketing rep and explained what was going on, the marketing rep followed the top-down chart as to who the guys boss was. 5 minutes later we get a call from the guys boss and explains that the guy had a bad day. We explained the situation and he said what you are telling me you are correct, let me check with another technician he puts us on hold (with lousy music on top of it). The technician gets back on the the phone and said there was a typo on the sheet and its being faxed to all the customers as we speak. I said OK, but the treatment I got from this other technician was just wrong and a customer should never be treated that way. He said he will take it up with his management. My boss was surprised at me speaking up like I did, but I was pissed. The next day I called in with a small question on a wording of a zap and what sequence it was supposed to go on. A technician got on and I asked the question and he said he was happy we had caught the issue. I said OK thank you. He said was I going to report him? I said no why should I, you handled the call correctly. He said the technician I had talked to yesterday was fired.
> . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-543-6132 Office ⇐=== NEW > robin...@sce.com <mailto:robin...@sce.com> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
