HI Wayne, > > <I've been reading the notes for MFNETDISK for a while and it complements > Hercules emulated disk as one of the functions. > > Yes, MFNetDisk emulates 3390 the same as Hercules. the difference is that > MFNetDisk uses the MVS STARTIO to do the Emulation. Hercules emulate the > 3390 using its MF emulation code which can work only with Hercules. > > <the disk emulation would be useful where the disk is remotely located > from the > processor complex or emulated processor (Hercules etc.). > > Yes, if you need local 3390 it is faster to use directly connect > FICON/ESCON real 3390. Using TCP with MFNetDIsk is a feature which nobody > have and I really do not like to be one of a many OEM which use the real > 3390 and by that have limitation which i do not have, like remote 3390 disk, > DR, uses all PC features, PC backup and more. > > <Obviously > performance would suffer depending on the > available bandwidth for remote TCPIP transmission of IO but for an > absolute DR capability, the product has many facets I can visualise. > > Yes, TCP is a problem like the Hard disk in the past was a problem when > try to use it in EMC, IBM and more to emulate 3390 disks but now everyone > use Hardisk to do the emulation. I know that TCP is faster and faster > everyday. IBM must do more to make the TCP the same faster as the open > system do to be accepted in the client/server enviroment and I know that IBM > do. Do not forget that Open system use the net disk (NFS) for long time and > it is work great and faster then ever. > About TCPIP bandwidth, Yes if you have slower TCP lines, MFNetDisk > will work slowly, But in today cost everyone can have faster TCP connection. > > <but for an > absolute DR capability, the product has many facets I can visualise. > > Thanks. > > <If a mainframe complex was taken out, the mirrored emulated disk could > be distibruted across multiple locations on multiple PCs or just a > single remote location. It might take some time to get your disk > "re-assembled" into usable status but it would mean you have a fairly > hot backup available ay any point in time. > > If you put every MFNetDisk PC device in remote PC distrubute all over the > country then you might have a small problem but that is not true. The PC > Devices can be in one or two PC Servers and then you have physical control > on them. But do not forget that MVS have pointer (the parameters files) > which points to all your PC and of course you can have backup of this file > in another location MVS or another PC. And beside the connection is with the > IP of the PC. That mean that accessing the PC can be done using the IP > with MFNetDisk PCTOOL or any remote MVS with the MFNetDisk parameters which > point to all the PCs. > About taking time, That is true if you do not have DR plan. Of course DR > plan mean that the MVS parameter file must be duplicate in the remote MVS to > be able to make the DR in no time. > > <The product isn't actually much use on Hercules other than to test the > functionality. To my knowledge, nobody is running modern o/s or TCPIP on > Hercules since they can't be licensed. I don't believe there is a TCPIP > for > MVS 3.8, but I could be wrong here. > > MFNetDisk can share its 3390 emulation easily only if MVS in Hercules can > access its local PC IP. that mean that if MVS MFNetDisk run on Hercules and > can access the locally MFNetDisk PC Server (all MS windows have TCP) which > emulate the 3390 disk then MFNetDisk can share its 3390 disk with remote > real MF which surely can access the PC with the Hercules and with the > MFNetDisk PC and use the 3390 emulation in that PC (I hope that it is clear > what I explained, if not I will put a falsh movie (the same as i have in my > site) which explain how to share MFNetDisk between MF emulation and real > MF). > > <Nice job, Shai. I hope you get some traction in the mainstream market. > > Thanks, > Shai > > On 1/2/08, Wayne Bickerdike <[EMAIL PROTECTED]> wrote: > > > > I've been reading the notes for MFNETDISK for a while and it complements > > Hercules emulated disk as one of the functions. Unless I'm mistaken, the > > > > disk emulation would be useful where the disk is remotely located from > > the > > processor complex or emulated processor (Hercules etc.). Obviously > > performance would suffer depending on the > > available bandwidth for remote TCPIP transmission of IO but for an > > absolute DR capability, the product has many facets I can visualise. > > > > If a mainframe complex was taken out, the mirrored emulated disk could > > be distibruted across multiple locations on multiple PCs or just a > > single remote location. It might take some time to get your disk > > "re-assembled" into usable status but it would mean you have a fairly > > hot backup available ay any point in time. > > > > The product isn't actually much use on Hercules other than to test the > > functionality. To my knowledge, nobody is running modern o/s or TCPIP on > > Hercules since they can't be licensed. I don't believe there is a TCPIP > > for > > MVS 3.8, but I could be wrong here. > > > > Nice job, Shai. I hope you get some traction in the mainstream market. > > > > > > -- > > Wayne V. Bickerdike > > > > ---------------------------------------------------------------------- > > 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 > > > >
---------------------------------------------------------------------- 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
