Ray Mullins wrote:
-----Original Message-----
From: IBM Mainframe Discussion List
[mailto:[EMAIL PROTECTED] On Behalf Of R.S.
Sent: Wednesday May 24 2006 00:10
I think it's typical for IBM. Examples:
<snip>
2. DB2 doesn't (wasn't) check RACF profile when
started/closed. Effect:
everybody (who can issue operator commands) can kill DB2. The
same person can be strictly controlled when i.e. using
DISPLAY command, he could be authorized to D SMF, but not D
IPLINFO. But not -dsn STOP DB2.
This sort of makes sense, though, if you think about how the command is
being processed.
[...]
No, it doesn't. I know more or less how it's being processed. Simply I
don't care. I bought z/OS, RACF and DB2 from same company. It's not safe
(disclaimer: I was told it's fixed in v8). For example JES commands are
processed in similar way, but RACF protected. OK, I don't insist on
RACF, let it be interally (in DB2) protected, via some GRANT. But it's
not. It's open for everyone.
3. IND$FILE also uses BLKSIZE of 3200/6160.
There are more examples like the above.
At one time, the linkage editor was very touchy about block sizes > 3200
unless you played games with PARM SIZE= and REGION.
Yes, at one time. 20 years ago ? Is there anything to add here ?
Regards
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
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
