| |
The incredible reduction in file transfer time allows for quicker data processing time, which improves customer service. In addition,
the ease of scheduling reduces the amount of administrator monitoring time for file transfers.
The Challenge
This particular customer has an operational need to replace multiple inefficient, troublesome storage array-based data sharing software applications that copied data from the
z/OS server environment, via a number of storage arrays, to open systems applications located on Sun and pSeries platforms, and after further processing on those platforms,
to copy data back to the z/OS server.
The customer already had in place a high-speed Ethernet environment (GbE), and wished to use that existing network for data sharing between the z/OS and open systems environment.
The data is mission critical; the data volume has and continues to grows, to a volume that is causing significant problems in attempting to transfer the data in the “time
window” available over the existing solution using the storage arrays. Failure to copy the data on a timely, multiple times a day, in turn causes the data bases on the open systems
servers to be dated, thus affecting the end users of the data.
In addition, the customer has been encountering significant support and maintenance time, thus reducing time
available for other support functions.
The customer has a number of established processes on both the z/OS system and the open systems platforms that performed data extraction from OS/390 databases, and one of their prime
considerations was minimal impact on development work to modify those batch JCL jobs. The customer also desired to minimize development efforts on existing scripts on the open systems
platforms, and to be able to transfer data from application to application
The Solution
Using the piping mechanism (SSI) within PDM, the customer was able to minimize their development efforts on the z/OS JCL jobs
by having to only change one DD statement and minimal scripting effort on the open systems to identify where the data was coming from (PDM). This provided the existing z/OS server
batch jobs to extract the data and transmit it directly to the open system platforms, without intermediate storage on the z/OS, to a script that invoked database loader programs.
Solutions Analysis
This customer’s main goal was to eliminate the use of storage array data sharing software, and
develop a flexible, efficient, storage neutral system to enhance the movement and loading of open systems servers databases. After looking at a variety of technologies, it selected
Alebra’s Parallel Data Mover. PDM met the company's primary goal because of its performance, its ability to move data between data centers, its monitoring capabilities, ease
of use, and its flexibility.
Solution Analysis Benefits
The incredible reduction in file transfer time allows for quicker data
processing time, which improves customer service. In addition, the ease of scheduling reduces the amount of administrator monitoring time for file transfers. The staff that previously
monitored, supported, maintained this procedure is more productive and free to take on more challenging and satisfying assignments.
Overall, this customer saved using PDM because:
- Diminished file transfer time creates room for further growth and improves the bank's ability to respond to customer
requests
- Reduction in support costs associated with the previous data sharing solution
- Elimination of obsolete applications (now covered by PDM)
cuts immediate costs.
|
|
|
