In
<[EMAIL PROTECTED]>,
on 06/21/2007
at 02:58 PM, Tom Savor <[EMAIL PROTECTED]> said:
>Funny how it's ok for SYSPROGs to cruise Applications and "tell" us
>what needs to be changed or how to tune our application (when we
>didn't ask for their opinion), but it's not ok for us to cruise your
>PARMLIB settings ???? Never heard of a PARMLIB setting getting
>screwed-up by looking at it. Unbelieveable !!!
"But never forget that the original Dilbert strips were nature
studies."
IMHO there should be transparency in both directions, subject to
security issues. However, don't keep long ENQ's on the datasets that
you want to view. Similarly, don't waste people's time suggesting
"improvements" that aren't; learn what it actually does, and why,
before suggesting changes.
>Another pet-peave, why do companies buy tools, then SYSPROG decides
>that "only they" get to use it.
Sometimes it's an ego trip, sometimes it's due to management decree.
I've been at shops where I was allowed to build my own tools and to
install tools from, e.g., the CBT tape, but I was *not* allowed to
make them available to the users, on the grounds that anything we made
available had to be supported and that we weren't authorized to commit
to the support.
>I asked them "why can't we both use it ??", answer...because none of
>the applications asked for it.
ROTF,LMAO! The correct answer was "Whoops! It was an oversight." It
was their job to determine who needed access and to convince people to
use it when it was to the company's benefit. Of course, given that
they were your customer you needed to be diplomatic.
>More and more SYSPROGs like to "hide" their stuff, even from
>viewing.
My guess is that either they are not sysprogs or the decision was
imposed from above.
>If your system security is setup properly, I can see no harm in
>browsing anything on the system.
One problem, which has been discussed here before, is users who
allocate systems data sets and don't free them when they're done
browsing. In a shop where you're not allowed to cancel their sessions,
the easiest fix is to remove the read access.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
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
