On Thu, 23 Feb 2006 14:13:29 -0800, Edward E. Jaffe
<[EMAIL PROTECTED]> wrote:
>Mark Zelden wrote:
>> You can't expect to have a separate LPAR for every small client
>> in all service-bureau environments. Too expensive, too much overhead.
>>
>
>That's why "God" invented VM.
>
That still would no
>You can't expect to have a separate LPAR for every small client
in all service-bureau environments. Too expensive, too much overhead.
I disagree.
Especially, with the unnatural acts you guys have to perform due to SOX.
We never set up multiple customers on the same LPAR at IGS, Canada.
Our Canad
Mark Zelden wrote:
You can't expect to have a separate LPAR for every small client
in all service-bureau environments. Too expensive, too much overhead.
That's why "God" invented VM.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
On Thu, 23 Feb 2006 00:00:00 GMT, Ted MacNEIL
<[EMAIL PROTECTED]> wrote:
>>> In other cases, it may be a real confidentiality concern. For example,
>> in a service-bureau setting, data set names may contain customer names
>> or acronyms.
>
>That does not make sense at all!
>It's not best practice
>> In other cases, it may be a real confidentiality concern. For example,
> in a service-bureau setting, data set names may contain customer names
> or acronyms.
That does not make sense at all!
It's not best practice to have different customers on the same LPAR, or sharing
the same UCATs!
So
One fellow who worked here many moons ago had a file named something along the
lines of "SYSXXX.AUDITORS.PLEASE.DONT.LOOK." I think it was just a backup of
something else he was working with, but it was still amusing.
Jon
Fortunately, naming MVS datasets is so ugly, that very little
inform
Gilbert Saint-Flour wrote:
On Thursday 23 February 2006 10:24, Edward E. Jaffe wrote:
Just curious. How much of an exposure exists if a user knows
the name of a data set [s]he can't open?
In certain environments, it may just be "security through obscurity".
In other cases, it may be
Gilbert Saint-Flour wrote:
On Thursday 23 February 2006 10:24, Edward E. Jaffe wrote:
Just curious. How much of an exposure exists if a user knows
the name of a data set [s]he can't open?
In certain environments, it may just be "security through obscurity".
In other cases, it may be a re
On Thursday 23 February 2006 10:24, Edward E. Jaffe wrote:
> Just curious. How much of an exposure exists if a user knows
> the name of a data set [s]he can't open?
In certain environments, it may just be "security through obscurity".
In other cases, it may be a real confidentiality concern. F
9 matches
Mail list logo
