PropelZ Case Study: From Installation to Operation in 24 Hours

At VirtualZ™, we take pride in creating software solutions that are not only innovative but also user-friendly and efficient.

PropelZ™, our no-code data integration software, exemplifies this commitment by streamlining the process of extracting, transforming, and loading data from mainframe systems.

Mainline recently installed PropelZ in their environment and shared their experience with us.  It reaffirmed PropelZ’s flexibility, ease of installation, and straightforward ongoing management.

We highlight some portions below; watch the full video here.

Mainline’s PropelZ Experience

In a recent discussion, Jerry Edgington, Senior Solutions and Innovation Consultant at Mainline Information Systems, shared his insights on the quick and effective installation of PropelZ.

He successfully deployed PropelZ while minimizing any disruptions to their existing environment.  And by adhering to best practices — such as utilizing shared ZFS structures and automating the startup — PropelZ seamlessly integrated into their mainframe ecosystem.

Preparing for the Installation

According to Jerry, the preparation for PropelZ’s installation was straightforward.

The most critical pre-installation step involved setting up a ZFS (z/OS file system) for both service and production environments.

This setup was completed quickly, ensuring a smooth transition for systems running on z/OS 2.5 with Java 8 or Java 11.

Disk Space and Setup Considerations

The installation of PropelZ required approximately 200 MB of ZFS space.

Jerry noted that as organizations scale their operations across multiple LPARs (logical partitions), the space requirement would double for each additional environment.  This flexibility is particularly advantageous for businesses looking to enhance their data management capabilities.

For optimal performance, Jerry recommended sharing a single ZFS across all LPARs within a sysplex.  This strategy not only simplifies maintenance but also ensures that updates are consistently applied across all environments.  Additionally, he suggested keeping log files in local LPAR directories while maintaining the environment as read-only to improve efficiency.

Security, Networking, and Automation

While integrating PropelZ into an existing mainframe environment, some minor adjustments were necessary.  This included establishing RACF (Resource Access Control Facility) permissions for security and reserving TCP/IP ports for networking.  These routine tasks highlighted PropelZ’s adaptability to various mainframe setups.

Once the system was operational, Jerry focused on automating the startup process.  By utilizing Unix scripts and JCL (Job Control Language), they seamlessly integrated PropelZ into their existing automation tools, such as OPS/MVS, facilitating an efficient startup.

Final Thoughts: A Smooth Installation Experience

Jerry’s experience with PropelZ reaffirmed the software’s flexibility, ease of installation, and straightforward ongoing management.  He successfully deployed PropelZ while minimizing any disruptions to their existing environment.

By adhering to best practices — such as utilizing shared ZFS structures and automating the startup — PropelZ seamlessly integrated into their mainframe ecosystem.

Watch the Full Conversation

Want to learn more about PropelZ’s installation process and best practices?

Watch the full interview with Jerry Edgington, Vince Re, and James Hoadley for deeper insights into how PropelZ can transform your mainframe data management.

Learn More

 

Latest Blog Posts

Unlocking the Power of Mainframe Data with Power BI Using PropelZ

Unlocking the Power of Mainframe Data with Power BI Using PropelZ

In today’s fast-paced business environment, the ability to access and analyze data in real time is crucial for informed decision-making. For organizations that rely on IBM Z mainframes, this can often present significant challenges.  Moving data from mainframe systems...

Loading...