> Yes, that would work, we have tested NFS before.
> The amount data is quite huge, for that reason ftp is not interesting, and
> that
> why NFS also has been out of scope. So far.
> Maybee that transfer time is acceptable/better than ftp for example ?
Well, NFS will transfer only the data you ac
On Thursday, November 10, 2011 02:55:58 am you wrote:
> Yes, that would work, we have tested NFS before.
> The amount data is quite huge, for that reason ftp is not interesting, and
> that why NFS also has been out of scope. So far. Maybee that transfer time
> is acceptable/better than ftp for exam
tore.agb...@volvo.com
http://www.volvo.com/volvoit/global/en-gb/
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Eddie Chen
Sent: den 9 november 2011 18:45
To: LINUX-390@VM.MARIST.EDU
Subject: Re: mvsdasd
I know the z/OS USS can NFS mount LINUX F
390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of RPN01
Sent: Wednesday, November 09, 2011 10:27 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: mvsdasd
Is there a reason that zOS NFS won't work? Then you'd have direct access to
the file, without copying via FTP or to z/VM, via a
;s network time involved, but there would be with any of the
solutions. There's no additional disk space involved as there would be with
an FTP store and forward type solution.
I think NFS would be a much cleaner solution to your problem than mvsdasd.
And, it has the advantage of being unders
tsaving is eaten up by ftp-cpucycles in
z/OS :(
And it takes time.
If we could access the actual disks or files directly from zLinux it would
really cut the cost here.
In that case it is some dedicated volumes, scheduled and documented z/OS jobs.
And about the mvsdasd program, it works like th
On Wed, Nov 9th, 2011 at 3:44 PM, Alan Altmark wrote:
> > Just because the current crop of security weebles don't "get it" does
> > not a true problem make.
>
> Eh?
LOL.
Should it come to pass that Alan and I are once again in the same bar
imbibing the best of Aussie brews/wine, I must remember
e
specifically constructed for Linux's use, e.g. as a pre-boot configuration
manager (a la CMS), then the audit issue may be able to be ignored. This
is an example of a having a problem (Linux pre-configuration management
without z/VM) that mvsdasd can solve.
Alan Altmark
Senior Managing z/V
bert - the read-only seemed harmless and as far as security that
>> could get ugly, We sue CA TSS thru PAM calls and I would not want even
>> ask what that would cause. really thank you for taking the time
>
> The bottom line is that unless you have a problem on z/OS that is solv
m line is that unless you have a problem on z/OS that is solved
by mvsdasd, don't use it, as it adds problems of its own that don't have
good solutions. The security issues pretty much kill it. Definitely
read those old posts.
Alan Altmark
Senior Managing z/VM and Linux Consultant
IBM
On Mon, Nov 7, 2011 at 3:48 PM, RPN01 wrote:
> Since you got no replies, I took a quick look at the site. Since it creates
> a read-only mount, I don't see how you're going to hurt anything, so that
> would eliminate any of the "scary" portion, in terms of Sysplex membership
> concerns.
Mounting
to
any order or other contract unless pursuant to explicit written agreement
or government initiative expressly permitting the use of e-mail for such
purpose.
From:
RPN01
To:
LINUX-390@vm.marist.edu
Date:
11/07/2011 10:54 AM
Subject:
Re: mvsdasd
Since you got no replies, I took a quick look
om a z/VM standpoint, in that if
you don't want the Linux image to see it, don't give it a link to the disk.
If you're worried about a rogue z/VM administrator, he's got CMS, which
could do far more damage than a Linux image.
The mvsdasd driver doesn't support pdse or vsam,
Google mvsdasd and Linux-390
There has been discussion here.
Yes, consensus was it could be scary.
Your z/OS security folks will not like it (not auditable).
http://www.mail-archive.com/linux-390@vm.marist.edu/msg59728.html
Marcy
This message may contain confidential and/or privileged
Going to ask again since the first message was so popular I received no
responses. has anyone used this driver from mvsdasd.org? Interested in
any experience comments and gotcha's. Seems scary to open up z/VM access
to z/OS DASD which is a member of a sysplex.
This is a PRIVATE message. If you a
On Friday, 06/10/2011 at 10:19 EDT, Scott Rohling
wrote:
> If that's the case - you don't grant access. I am objecting to the
> automatic assumption that there's a security problem because someone
wants
> to use a driver to read a z/OS volume. Just as if I have a
confidential
> file on my 191
If that's the case - you don't grant access. I am objecting to the
automatic assumption that there's a security problem because someone wants
to use a driver to read a z/OS volume. Just as if I have a confidential
file on my 191 disk.. I don't grant access even if the rest of the files
are com
On Thursday, 06/09/2011 at 04:15 EDT, Scott Rohling
wrote:
> Implementing the driver isn't an auditable offense.. gaining access to
the
> volume through a DEDICATE or LINK, etc is another story - but that
shouldn't
> discourage use of the driver. I see little difference between this and
the
>
011 21:56
To: LINUX-390@VM.MARIST.EDU
Subject: Re: mvsdasd working for SLES11 someone ?
On Thursday, 06/09/2011 at 01:10 EDT, Mark Post wrote:
> >>> On 6/9/2011 at 11:23 AM, Agblad Tore wrote:
> > Anyone having tried the mvsdad driver for read z/OS dasd directly ?
>
>
Implementing the driver isn't an auditable offense.. gaining access to the
volume through a DEDICATE or LINK, etc is another story - but that shouldn't
discourage use of the driver. I see little difference between this and the
cmsfs driver... access to a z/OS or CMS disk is auditable (or shoul
On Thursday, 06/09/2011 at 01:10 EDT, Mark Post wrote:
> >>> On 6/9/2011 at 11:23 AM, Agblad Tore wrote:
> > Anyone having tried the mvsdad driver for read z/OS dasd directly ?
>
> For anyone that has, I hope their auditors never find out.
(shudder) Indeed. Reading an MVS volume that has not b
>>> On 6/9/2011 at 11:23 AM, Agblad Tore wrote:
> Anyone having tried the mvsdad driver for read z/OS dasd directly ?
For anyone that has, I hope their auditors never find out.
Mark Post
--
For LINUX-390 subscribe / signoff /
included from /home/userid1/mvsdasd-source-0.85/mvsfs.c:27:
/home/userid1/mvsdasd-source-0.85/vtoc.h:141: error: redefinition of ‘struct
node’
I have mailed the maintainer as well, but I try a question here as well :)
Cordialement / Vriendelijke Groeten / Best Regards / Med Vänliga Hälsningar
Hi Sergey,
Unfortunately, this is not possible yet. Mvsdasd is currently read-only,
so even if 'myfile' could have been created (and it can not[1]), then
you would not have been able to restore (write) the volume back in the
same manner.
Best wis
Hello Jacob.
Is it possible to use your driver for dumping MVS disks, something like
dd if=/dev/mvsdasdc of=/myfile
and then restore them back with another dd command?
Thank you.
WBR, Sergey
--
For LINUX-390 subscribe
Hi all,
This is to let anyone interested know that mvsdasd has added support for
RHEL 4 Update 4 (and hence CentOS 4.4), and slack390 (kernel 2.6 option).
Regards,
Jacob.
-
http://www.mvsdasd.org
26 matches
Mail list logo
