On Wed, Apr 17, 2013 at 8:33 AM, MG <marcogb at xs4all.nl> wrote:
On 16-apr-2013 22:10, David Riley wrote:
I logged in today and quickly discovered I have
no idea what
to do. Time to read up...
Too bad that you can't do anything there. Also, why can't they
restrict things you can't (or aren't 'supposed' to) do? That
makes no sense, well, outside of that niche world anyway.
- MG
I think this was an honest question of yours not bait although I did find
the popcorn comments funny. I didn't see much explanation for you if you
were really seeking which would have been nice. I've only done minor
admin/system administration on a mainframe and I was using tools/commands
that were written by the other security admin and some minor commands in
"Top Secret" (tss) so my experience probably doesn't add up to much. But
yes, you can pretty much secure any user down to the command or subsystem
they're allowed to access. It's quite granular and well put together if
you understand the logic of the mainframe environment.
https://www.cms.gov/Research-Statistics-Data-and-Systems/CMS-Information-Te…
a guide but grab some Jolt or something before trying to sit down and
actually read through it. These guides are a discipline of their own to
sit through lol.
It's much easier to get through the MTS manuals...the commands for it
actually seem logical and like they weren't written using a spinning
dartboard and a random number generator. (I know I exaggerated, but MVS is
a bit strange, you gotta admit that)
The HELP system is useful, too! It's menu driven. It's far, far superior
to UNIX/Linux man pages.
Linux man pages are also inferior to BSD man pages...I like man pages on
all the drivers. ;)
--
--
Cory Smelosky