I won’t mention names, but I know of a dump where the master scheduler ASCB eye catcher got changed to aSCB. And thanks to the case switch being in upper, no one figured out why that production system crashed.
All I can say is, management said that we could not IPL that machine. But we knew that come 9AM or so the next day, well there would be a large number of unhappy TSO users. Some one had been working on a product that was leaving ASCBs as unreuseable. So the system crashed. We had to IPL. Cloud companies really shouldn’t sell time to development companies and then have them on the production system — if you get my drift. Sent from my iPhone — small keyboarf, fat fungrs, stupd spell manglr. Expct mistaks > On Nov 19, 2018, at 8:46 PM, Tom Brennan <[email protected]> wrote: > > I ran into that type of debugging on a shared IBM 3278 with that switch set > to show all caps. It probably took me 15 minutes to figure out why JES2 was > telling me "DSN=" was invalid in the JCL I just modified. It looked fine on > the screen, and of course I was 100% convinced JES2 was broken. > >> On 11/19/2018 2:57 PM, Jesse 1 Robinson wrote: >> In my first IT job, we had Raytheon clones there were serviceable enough but >> had a curious quirk. There was a rocker switch that flipped the entire >> display into upper case. Not the actual data, just the display. Made for >> some interesting debugging. Still don't understand the intention. >> . >> . >> 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 >> [email protected] >> -----Original Message----- >> From: IBM Mainframe Discussion List [mailto:[email protected]] On >> Behalf Of Pew, Curtis G >> Sent: Monday, November 19, 2018 2:39 PM >> To: [email protected] >> Subject: (External):Re: So much for THAT excuse | Computerworld SHARK TANK >>> On Nov 19, 2018, at 4:26 PM, Steve Thompson <[email protected]> wrote: >>> >>> S/360 machines I worked on had a switch in the PSW to set them in ASCII >>> mode. I don’t remember or know of any software that made use of this. So >>> that bit was eventually required to be ON to force DAT or XA. I have >>> forgotten what that bit was “stolen” for now. >>> >> Right. The expectation was that routines would check the bit and generate >> output in the appropriate codeset, and eventually everyone would be using >> ASCII. Instead, everyone ignored the bit and generated EBCDIC, so the bit >> was reused for something else (I can’t remember what either.) > > ---------------------------------------------------------------------- > 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
