In the mid-70's, two programmers discovered TSO SEND, and they were madly exchanging explicit love notes. Neither the operators or sysprogs let them know the notes were showing up on the console. Must have worked - they eventually happily married...
-----Original Message----- From: Bob Bridges <robhbrid...@gmail.com> To: IBM-MAIN@LISTSERV.UA.EDU Sent: Tue, Jan 18, 2022 8:31 pm Subject: Re: What not to do on a z/OS system... Not the same thing, but it reminds me that I once caused a panic inadvertently in my office. Users would occasionally ask the owner of a process or dataset for permission to access it, get the ok from the owner, and forward it to me saying "please set this up; as you see, he said it was ok". I, naturally, would insist that the owner email me directly. (In case it isn't obvious why, it's easy to construct an email in which "he" says it's ok; but if it comes directly from the owner, I can trust it. Not that I think anyone's lying, but someday it'll happen and I want to get all my customers used to doing it right. My boss didn't thoroughly understand my objection to accepting second-hand permissions. So one night it occurred to me that a demonstration might be educational. Before I went home I sent him an email bringing up the subject again, explained my position, and said "...as you can see by the below email". Below I fadged up an email ostensibly from my boss to HIS boss, saying something uncomplimentary. When I got in the next morning, the department was in an uproar. Apparently my boss had completely missed the point of my email; all he could see was that someone had hacked his account, and he was on the verge of going to his boss to deny that he'd sent any such email. I talked him down and explained again what I'd done. But I don't think I'll try any such realistic demonstration again in future, not at least without more emphatic disclaimers surrounding it. --- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* Being famous has its benefits, but fame isn't one of them. -Larry Wall */ -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Roger Bolan Sent: Tuesday, January 18, 2022 19:43 Well, mine was just silly and did not involve games or using unauthorized CPU time. I was just doing my normal code development job and running PL/I compiles, links, and tests. The systems I normally used restricted the jobnames to userid + a character. Then one of the systems I was working on allowed the jobname to be whatever I wanted. So I took one of my ordinary jobs that didn't use any more time or resources than normal, and "just for fun" I gave it a jobname of "COREHOGG". OMG!! When I submitted that my phone immediately blew up with people yelling at me about what did I think I was doing? Not the operators. They could see what it was. But other users who just reacted to the name COREHOGG without knowing anything else about the job. So I learned not to give jobnames "just for fun". :) --- On Tue, Jan 18, 2022 at 3:41 PM Robert Prins <robert.ah.pr...@gmail.com> wrote: > OK, it's not the silly season, but have you ever used your employers > equipment to do something silly? And are not afraid to admit it? > > Well, I have in the early 1990'ies, and I actually got away with it, > without losing my job. > > And talking about jobs, if anyone of you know of any companies looking > for someone with 36+ years of PL/I, and a bit less Db2 and CICS, feel > free to drop me a line. > > So what did I do? Let's go back a few years… > https://prino.neocities.org/blog/2022-01-19-setting-the-record-straight.html ---------------------------------------------------------------------- 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
