At VirtualZ™, we are committed to creating software solutions that are not only innovative but also easy to install and manage. One such product is Lozen™, which enables real-time, read-write data access across platforms.
Recently, Jerry Edgington, a Senior Solutions and Innovation Consultant at Mainline Information Systems, shared his firsthand experience installing Lozen, offering valuable insights for those considering the product.
Jerry was able to deploy Lozen quickly, with minimal disruption to their environment. His experience reaffirmed Lozen’s flexibility, ease of installation, and straightforward ongoing management.
We highlight some portions of our discussion below; watch the full video here.
Mainline’s Lozen Experience
Preparing for the Installation
According to Jerry, preparing for Lozen’s installation was straightforward. The most significant pre-installation task involved setting up a ZFS (z/OS file system) for the service and production environments. This step was simple and took minimal time. For systems running on z/OS 2.5 with Java 8 or Java 11, the process was seamless.
Disk Space and Setup Considerations
Lozen’s installation required around 200 MB of ZFS space. Jerry noted that the space requirement doubles for each additional LPAR (logical partition), making it scalable for organizations managing multiple LPARs.
For optimal performance, Jerry recommended sharing a single ZFS across all LPARs within a sysplex. This approach simplifies maintenance, ensures updates are reflected across the board, and enhances overall efficiency.
He also shared a best practice: separating log files into local LPAR directories while keeping the environment read-only.
Security, Networking, and Automation
While Lozen integrates smoothly into mainframe environments, some minor adjustments were necessary to incorporate it into Jerry’s existing infrastructure. This included setting up RACF permissions for security and reserving TCP/IP ports for networking. Although these steps were routine, they demonstrated Lozen’s adaptability to different setups.
Once the system was running, Jerry automated the Lozen startup process. By using Unix scripts and JCL (Job Control Language), they integrated Lozen into existing automation tools like OPS/MVS, making the startup seamless and efficient.
Final Thoughts: A Smooth Installation Experience
Jerry’s experience reaffirmed Lozen’s flexibility, ease of installation, and straightforward ongoing management.
He was able to deploy Lozen quickly, with minimal disruption to their environment.
By applying best practices (such as using shared ZFS structures and automating the startup process), Lozen proved to be an excellent fit for mainframe ecosystems.
Watch the Full Conversation
Want to learn more about Lozen’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.
