>John McKown wrote: > ... because NOBODY reallys wants the >responsibility for this. It is one of those things that crosses >functional barriers. The mainframers don't really want to deal with a >server issue. And the server/Windows people don't want to be bothered >with what they consider a mainframe issue. This is another of those >"finger pointing" exercises. Someday something will cause upper >management to issue a fiat as to what is to be done. Last time this >happened, Tech Services (me) got saddled with "doing something". In the >interim, everybody just complains.
I guess until you solve the "us and them" issue and no $$$$ to spare, you'll just get a bunch of whiners <grin> I agree with someone's suggestion to use either MVS NFS or SMB, which depends on what the receiving end can support. You provide the NFS Server on the mainframe and export the HLQ to your clients. Your mainframe pgmrs create the data set under the exported HLQ, the clients see it on their side, copy and delete from their mountpoint and it gets deleted on the mainframe. I can only attest to MVS NFS as a file server. Maybe someone else here has a similarly good experience with SMB. I know MVS NFS is available, if not already configured at your shop, at no new $$$s (Only true if you work for free). ---------------------------------------------------------------------- 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
