--- On Thu, 12/9/10, Rick Fochtman <rfocht...@ync.net> wrote: -------------------SNIP-------------------------------------------------------------------------------------------- --------------------------------------<unsnip>-------------------------------------- This last comment is correct, but I have a serious problem with applications that issue system-type abend codes.
Rick Rick, I agree completely. When we were converting from MVT to MVS we had a user come down with a similar problem. He said "It says its a system abend" fix it because its not mine. It took me all of 30 second to figure it out from the dump and told the guy it was his problem and here is why... I explained the issue as simply as I could. The guy thought I was giving him a snow job and he went to his bosses boss and told him we (the system group) couldn't fix a system problem. All of a sudden we were told we had to go to a meeting and were hustled up to a huge conference room and was told to stand around in the corner. As it unfolded the meeting was a status meeting and every body was giving the status of his/her project. Then about 2/3rd's the way through one of the project managers got up and talked about all his project and then he says something to the effect that MVS was broken and the systems people had to fix it or this project xxx was going to fail. We all looked at each other and I was not sure what he was talking about so I asked him what MVS system problem was he refering to as far as I know no MVS issues (user) were outstanding. The project manager said the program was getting an S001 and an "S" meant it was a system problem. It was then I realized what was going on (I had a desk full of S/A dumps just waiting for me to look at). I turned my head and looked at my boss and I said "now I understand" to him. I looked at him and gave me the OK to go. So I said I would like to explain something so we could all be on the same understanding. So I went to the white board and explained exactly what had happen. Back then most people were conversant in assembler so I did not have to go into bits too much but I think I explained it well enough and I turned around and asked does this explain what the small problem is and the "Big" boss was a little red in the face. I steped back to the my group and the "Big" boss said OK everybody that is not part of the project could leave. We filed and closed the door behind us. Although we had rather thick doors on our conference rooms it wasn't thick enough to hear the boss screaming at the top of his lungs that in no uncertain terms he wanted that programmer gone TODAY. Well I heard about a week later the idiot programmer went to work for an insurance company in Chicago for big $$. I loss track of the guy as I was just hoping never to run into him again. That is one of the many reasons not to code it that way. Sorry to run on and a little bit late in replying. Ed ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
