On Mar 3, 2006, at 1:12 PM, McKown, John wrote:
---------------------SNIP---------------------
NFS/SMB has been mentioned in another post. I have done an NFS
import of
a UNIX subdirectory onto the z/OS system. It works quite well.
However,
the same problem occurs. If the job terminates trying to copy to the
NFS/SMB share, the programmer would get called and they don't want to
be. They would still want "someone else" to do the NFS/SMB copy
function
and be responsible for any problems with it. So, ftp or NFS/SMB it is
basically all the same to them. They don't want anything related to
the
copying in any process for which they are responsible. And they really
don't want to set up a second job to do the ftp/NFS work either.
I know that sounds like they are being lazy, but they have had such
problems with this - again due mainly to server problems - that
they are
frustrated and just want OUT! It is one thing to get called about a
problem you can fix. It is another thing to get calls for a problem
that
is outside your ability to fix or even diagnose properly.
Well - off to the annual company meeting. Such fun.
John,
I have seen this same issue through the years. There is no perfect
answer, IMO. FTP (and other like programs) run async.
OEM said there answer is to do a TSO send to X users when the
transmission fails. The original FTP concept was not thought about
for batch (IMO).
This might be a way to get IBM to support something like this if you
want to wait for IBM to implement it (don't wait).
There *MAYBE* a message that shows up on the console to indicate a
failure, you might trigger off the message. I resisted this for
political reasons, IIRC.
´d
----------------------------------------------------------------------
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
