My first stop would be to better understand the upload (sever to MF)
process. From your description, the MF is just a repository. It has no
idea what is in the files. 

In other words, server 'a' is FTP'ing to the MF with instructions to
stow data in X.Y.Z(+1). 

I would ask why server 'a' is sometimes storing data in server 'b'
files. 

I would also look into making it impossible for server 'a' to access
server 'b' files via MF security. 
  

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Mike Liberatore
Sent: Thursday, February 28, 2008 6:05 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: FTP question

I have several Open systems servers each running windows 2003. having 
unique IP addresses and each running their own scripts to capture data. 
This data is then being sent via ftp and stored on  mainframe lpar as 
GDGs. Each file being sent to the mainframe is unique and is being 
stored in their own GDGs. However in some cases data from Server A is 
being stored into Server Bs GDG on the mainframe and vice versa. Doesn't

happen consistently. Any idea as to how data from one Server A can be 
getting stored on Server Bs files? Again, each Sever has it's own IP 
address and its on Mainframe GDG data sets.  Thanks in advance!!

 
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

----------------------------------------------------------------------
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

Reply via email to