Mike, What was the "software product" that suffered a "hardware failure" ... and how were they related? Do you mean something like COM-10 or 3745 over VTAM replacement?
JR Imler JR (Steven) Imler Computer Associates Senior Software Engineer Work: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] [EMAIL PROTECTED] -----Original Message----- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, January 03, 2006 07:02 PM To: [email protected] Subject: Best practices for z/VM file transfers? We're (pretty urgently) looking for a replacement product for one which just suffered hardware failure. It's unlikely that it can be resurrected - very old hardware. Requirements: - Batch file transfers between VM and z/OS (initiated either by a VM:Batch job or a z/OS batch job), performed by permission rather than passwords. - Interactive file transfers, in the same manner (again, initiated by VM users or TSO users, by permission rather than passwords). - Transfer from VM to MVS must be to dataset (RACF authorized), or to JES2 SPOOL (allowing class, forms, destination, etc.) - Transfer to VM must be to a target user minidisk or SFS directory. Can anyone recommend a good solution? If it's Linux-based, we're going to need a consultant: a Linux on zSeries proof of concept is scheduled to begin in a couple weeks. Happy New Year! Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
