I've seen the variation where a CLIST was set up to display a message
when a user would log on that his logon authority was temporarily
suspended pending an investigation by the security department - great
fun when you were just getting back from a nice, relaxing vacation.
Also, about 20 years ago, I had a problem with my boss using my PC when
I had left for the day to snoop around on the network. I created a
little C program that would log all after-hours commands entered on it
(with time-stamps). When I allowed him to see copies of the printed
logs laying around my PC keyboard, he desisted. But that didn't stop me
from going into his office one lunch break a few days later and setting
his MFM interleaving factor to 15.
Wayne Driscoll wrote:
I once worked with a guy that wrote a VTAM app that would acquire someone's
terminal (easy in the "dumb" terminal days) and display a screen that would
look just like the USS MSG10 screen. When the person attempted to logon, it
would respond with idiotic messages, after clearing all data out of the
buffers. So you would walk into his office for help, he would kill the job
that was running, so the screen would clear with you away from it. He would
then walk over and proceed to logon as normal. Once you learned the trick,
you would first look at the operator info area of the screen to see what
type of session you where in before trying to logon.
Wayne Driscoll
Product Developer
NOTE: All opinions are strictly my own.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
