RE: File sharing between V5R4 system and W2K3 server

Mike,
Are the folks across the pond part of your organization? If so, why not
just put it out on the IFS and let the ones who need the file map to it
as they need it?



Terry Anderson
Programming Manager
Citation Corporation
Switchboard 1.251.867.5481 ext 212
Direct Line 1.251.809.2312
Fax 251.867.0525
Cell 1.251.363.4975

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Crump, Mike
Sent: Friday, July 31, 2009 2:24 PM
To: Midrange Systems Technical Discussion
Subject: File sharing between V5R4 system and W2K3 server

I have a need to share a file between our server (v5R4) and a W2K3
server on the other side of the pond that is well beyond my ability to
support.

I've been reading the archives and trying to determine the best
approach. We used to do this via QNTC but we moved the target
application to an AS/400 so it's been a while for us. I'm trying to
grasp the issue of SMB signing and QNTC and other avenues to move a file
from our V5R4 system to this windows server. We currently FTP the file
but the target system wants to get away from this. The volume is low in
frequency and size. My concern is stability and ease to implement.
This is a Windows server that I will have very little input into how it
is managed....

Recommendations? Experiences?

Michael Crump

Manager, Computing Services
Saint-Gobain Containers, Inc.
1509 S. Macedonia Ave.
Muncie, IN 47302

765.741.7696
765.741.7012 f




Pressure
It can turn a lump of coal into a flawless diamond, or an average person
into a perfect basketcase.

This email and its attachments may be confidential and are intended
solely for the use of the individual to whom it is addressed. Any view
or opinions expressed are solely those of the author and do not
necessarily represent those of Saint-Gobain. If you are not the
intended recipient of this email and its attachments, you must take no
action based upon them, nor must you copy or show them to anyone.
Please contact the sender if you believe you have received this email in
error.