HP3000-L Archives

February 2006, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Greg Stigers <[log in to unmask]>
Reply To:
Greg Stigers <[log in to unmask]>
Date:
Thu, 9 Feb 2006 11:16:14 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
When I was invited to find my way into a 3000, I went for the operator. My 
first guess was "OPERATOR", which was wrong. My second guess was right, 
because they made it easy, and unlikely to ever be changed.

Unfortunately for all involved, the 3000 operators I've worked with seemed 
to merit being treated like second-class citizens. The mainframe operators 
at least understood what they did know how to do, and the tools that they 
used, more or less. They still were innovative scripters or sys admins. But 
when I did novel things with temp files, that they had to ask me to explain, 
they followed my explanation well enough not to tell me I couldn't do it 
that way. I've had 3000 support staff, some operators, some not, complain 
that some CI scripting was too complicated to support, which is kind of sad.

But the assumption of the lowest common denominator, instead of insisting 
that operators rise to at least the best common denominator, makes operators 
a good bet for relative ease of penetration and a more than adequate level 
of access. And I can't see why crackers would not take much the same 
approach as lions use with their prey. Go for the weak and slow moving.

Greg Stigers 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2