Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on developerWorks

2014-03-19 Thread Victor Echavarry Diaz
This is a multi-part MIME message.

Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Gerhard:

Regarding the zdsfs command,  Its said Use the zdsfs command to mount a z/=
OS DASD as Linux file system. and no more explanation. Do you know the adv=
antage of this?

Regards,

Victor Echavarry
System Programmer, EVERTEC LLC


From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Gerha=
rd Hiller
Sent: Wednesday, March 19, 2014 8:24 AM
To: LINUX-390@VM.MARIST.EDU
Subject: 2014-01-08 Linux on System z - Kernel 3.12 related updates on deve=
loperWorks

Please refer to
http://www.ibm.com/developerworks/linux/linux390/whatsnew.html
for several updates to the 'Development stream':
 * description of upstream kernel 3.12 features that were
   contributed by Linux on System z development
 * kernel 3.12 patch for kernel message catalog
 * s390-tools 1.24.0 delivers new functionality and bugfixes
 * updated documentation
   -- Device Drivers, Features, and Commands (Kernel 3.12) SC33-8411-23
   -- Using the Dump Tools (Kernel 3.12) - SC33-8412-13
   -- Kernel Messages (Kernel 3.12) - SC34-2599-05
   as well as updated Restrictions and Technical Details
* end of message
Mit freundlichen Gr=FC=DFen / Kind regards


Gerhard Hiller



see our TechOps homepage.http://w3.boeblingen.de.ibm.com/eserver_sw_develo=
pment/TechOps







Software Management and Linux Technologies

IBM Systems  Technology Group, Software Defined Systems


[cid:image004.gif@01CF4354.763D0CA0]

Phone:

 +49-7031-16-4388

 IBM Deutschland

[cid:image005.gif@01CF4354.763D0CA0]

Fax:

 +49-7031-16-3545

 Schoenaicher Str. 220

E-Mail:

 ghil...@de.ibm.com

 71032 Boeblingen


 Germany

[cid:image004.gif@01CF4354.763D0CA0]

IBM Deutschland Research  Development GmbH / Vorsitzende des Aufsichtsrats=
: Martina Koederitz
Gesch=E4ftsf=FChrung: Dirk Wittkopp
Sitz der Gesellschaft: B=F6blingen / Registergericht: Amtsgericht Stuttgart=
, HRB 243294









WARNING: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please delete it immedi=
ately.
Please note that any views or opinions presented in this email are solely t=
hose
of the author and do not necessarily represent those of EVERTEC, Inc. or its
affiliates. Finally, the integrity and security of this message cannot be
guaranteed on the Internet, and as such EVERTEC, Inc. and its affiliates ac=
cept
no liability for any damage caused by any virus transmitted by this email.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
inline: image001.gifinline: image002.gifinline: image003.gifinline: image004.gifinline: image005.gifinline: image006.gif

Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on developerWorks

2014-03-19 Thread Neale Ferguson
From the device driver manual: (The security warning is especially important)

The zdsfs file system translates the z/OS data sets, which are stored on the 
DASDs
in records of arbitrary or even variable size, into Linux semantics.

Through the zdsfs file system, applications on Linux can read z/OS physical
sequential data sets (PS) and partitioned data sets (PDS) on the DASD. In the
Linux file system, physical sequential data sets are represented as files. 
Partitioned
data sets are represented as directories, which contain the PDS members as 
files.

Other z/OS data set formats, such as extended format data sets or VSAM data
sets, are not supported. zdsfs is optimized for sequential read access.

Attention:
- To avoid data inconsistencies, set the DASDs offline in z/OS before you mount
them in Linux.
- Through the zdsfs file system, the whole DASDs are accessible to Linux, but 
the
access is not controlled by z/OS auditing mechanisms.

To avoid security problems, you might want to dedicate the z/OS DASDs only
for providing data for Linux.

Per default, only the Linux user who mounts the zdsfs file system has access to 
it.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on developerWorks

2014-03-19 Thread Alan Altmark
On Wednesday, 03/19/2014 at 09:36 EDT, Neale Ferguson
ne...@sinenomine.net wrote:
 Attention:
 - To avoid data inconsistencies, set the DASDs offline in z/OS before
you mount
 them in Linux.
 - Through the zdsfs file system, the whole DASDs are accessible to
Linux, but
 the access is not controlled by z/OS auditing mechanisms.

 To avoid security problems, you might want to dedicate the z/OS DASDs
only
 for providing data for Linux.

In the same way a z/VM Linux guest can read CMS files, Linux can now read
MVS data for all the same reasons.  Nice if you want to keep some Linux
configuration data on z/OS (particularly IP configs).

If you do this, you should relegate the Linux data to datasets on a
separate volume that is not used for automatic dataset allocation and that
is not under SMS control.  This prevents dataset migration since they will
appear to never be used (except when you update them), and it avoids
unaudited access to datasets that are not intended for access by the Linux
server.

If you have traditional z/OS data that you want to share with Linux, copy
it to a dataset on that separate volume.

As usual, when running Linux native in an LPAR, ensure that the LPAR has
access only to the specific z/OS volumes that contain the Linux data.

All of the expected cautions about writing to the datasets while Linux is
trying to read them applies.  Hence the suggestion for the volume to be
offline to MVS since z/OS is unaware of the access.

Alan Altmark

Senior Managing z/VM and Linux Consultant
IBM System Lab Services and Training
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on developerWorks

2014-03-19 Thread Victor Echavarry Diaz
Thanks Neale:

Victor Echavarry 
System Programmer, EVERTEC LLC

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Neale 
Ferguson
Sent: Wednesday, March 19, 2014 9:36 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on 
developerWorks

From the device driver manual: (The security warning is especially important)

The zdsfs file system translates the z/OS data sets, which are stored on the 
DASDs
in records of arbitrary or even variable size, into Linux semantics.

Through the zdsfs file system, applications on Linux can read z/OS physical
sequential data sets (PS) and partitioned data sets (PDS) on the DASD. In the
Linux file system, physical sequential data sets are represented as files. 
Partitioned
data sets are represented as directories, which contain the PDS members as 
files.

Other z/OS data set formats, such as extended format data sets or VSAM data
sets, are not supported. zdsfs is optimized for sequential read access.

Attention:
- To avoid data inconsistencies, set the DASDs offline in z/OS before you mount
them in Linux.
- Through the zdsfs file system, the whole DASDs are accessible to Linux, but 
the
access is not controlled by z/OS auditing mechanisms.

To avoid security problems, you might want to dedicate the z/OS DASDs only
for providing data for Linux.

Per default, only the Linux user who mounts the zdsfs file system has access to 
it.
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/



WARNING: This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please delete it 
immediately.
Please note that any views or opinions presented in this email are solely those
of the author and do not necessarily represent those of EVERTEC, Inc. or its
affiliates. Finally, the integrity and security of this message cannot be
guaranteed on the Internet, and as such EVERTEC, Inc. and its affiliates accept
no liability for any damage caused by any virus transmitted by this email.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on developerWorks

2014-03-19 Thread Neale Ferguson
Wow, there are more caveats than a viagra commercial.

 If you do this, you should relegate the Linux data to datasets on a
 separate volume that is not used for automatic dataset allocation and that
 is not under SMS control.  This prevents dataset migration since they will
 appear to never be used (except when you update them), and it avoids
 unaudited access to datasets that are not intended for access by the Linux
 server.
 
 If you have traditional z/OS data that you want to share with Linux, copy
 it to a dataset on that separate volume.
 
 As usual, when running Linux native in an LPAR, ensure that the LPAR has
 access only to the specific z/OS volumes that contain the Linux data.
 
 All of the expected cautions about writing to the datasets while Linux is
 trying to read them applies.  Hence the suggestion for the volume to be
 offline to MVS since z/OS is unaware of the access.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on developerWorks

2014-03-19 Thread Alan Altmark
On Wednesday, 03/19/2014 at 10:30 EDT, Neale Ferguson
ne...@sinenomine.net wrote:
 Wow, there are more caveats than a viagra commercial.

I suppose I should have warned that you should not use zdsfs if your
auditors have high blood pressure as it may cause their heads to explode.

Alan Altmark

Senior Managing z/VM and Linux Consultant
IBM System Lab Services and Training
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on developerWorks

2014-03-19 Thread Peter Oberparleiter
On 19.03.2014 15:43, Alan Altmark wrote:
 On Wednesday, 03/19/2014 at 10:30 EDT, Neale Ferguson
 ne...@sinenomine.net wrote:
 Wow, there are more caveats than a viagra commercial.

 I suppose I should have warned that you should not use zdsfs if your
 auditors have high blood pressure as it may cause their heads to explode.

While I agree that the list of restrictions is long, I think it is still
fair to point out that once all necessary precautions are taken, zdsfs
might provide an opportunity to transfer data from a z/OS instance to a
Linux on System z instance faster (given sequential access) and with
lower CPU overhead than traditional NFS or FTP transfer methods.


Regards,
  Peter Oberparleiter

--
Peter Oberparleiter
Linux on System z Development - IBM Germany

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on developerWorks

2014-03-19 Thread Neale Ferguson
Totally agree. It should prove very useful for big data type processing. Just 
need to write thing in large bold font in red to make sure people understand 
that practicing safe-sectors is required.

On Mar 19, 2014, at 11:04 AM, Peter Oberparleiter wrote:

 On 19.03.2014 15:43, Alan Altmark wrote:
 On Wednesday, 03/19/2014 at 10:30 EDT, Neale Ferguson
 ne...@sinenomine.net wrote:
 Wow, there are more caveats than a viagra commercial.
 
 I suppose I should have warned that you should not use zdsfs if your
 auditors have high blood pressure as it may cause their heads to explode.
 
 While I agree that the list of restrictions is long, I think it is still
 fair to point out that once all necessary precautions are taken, zdsfs
 might provide an opportunity to transfer data from a z/OS instance to a
 Linux on System z instance faster (given sequential access) and with
 lower CPU overhead than traditional NFS or FTP transfer methods.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/


Re: 2014-01-08 Linux on System z - Kernel 3.12 related updates on developerWorks

2014-03-19 Thread Mark Post
 On 3/19/2014 at 10:28 AM, Neale Ferguson ne...@sinenomine.net wrote: 
 Wow, there are more caveats than a viagra commercial.

And I think most, if not all of them, are going to go into the user 
confirmation message that will come up when someone tries to install the 
package on SLES.  And probably some more.

I was told that I couldn't package this as shootmeinthefoot.rpm, so I have to 
come up with a different name for it.  Darn.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/