> It is basic R/W access to VSAM files to read the data into a Linux app then > write it back out > The main thing is performance. part of the process must remain on zOS so >the LOB doesn't want to > pay for 2 sets of dasd of course so we want to access the data inplace. > We're going to use zOS NFS for the flatfiles they need to NFS on RH Linux > from the sound of it your saying that i could possible fire up the VM NFS > CLIENT. > Connect to zOS NFS server right? > So does that mean i need yet another NFS connection between VM and Linux or > can I access the NFS > as a minidisk?
Depending on what VSAM access you need (it's limited to sequential access, none of the fancy stuff), that might just work fine. You could mount the VSAM file via the CMS NFS client, but that would present it as a BFS/SFS style thing, which Linux can't cope with. The z/OS NFS server presents VSAM files as just another filesystem that can be mounted by any NFS client, so if the data is going to end up in Linux, skip the step through VM and mount it directly from the Linux NFS client. You need only a way to get IP packets back and forth between the Linux NFS client and the z/OS system (which sounds like you already have). Check out the z/OS NFS server documentation for info on the restrictions with VSAM files to make sure you can live with them, and then try it directly from Linux. z/OS handles all the VSAM processing, so you should be pretty much there if all you need is simple sequential processing. Performance will be a question -- it's only going to be as good as the network connection between z/OS and the client, and you do have to do all the VSAM processing on z/OS, so it's going to cost you lots of standard engine cycles to do it. If you can live with that, OK, but they should be aware of that extra cost. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
