System Requirements

PopUp X runs on x86 hardware, for example servers running x86 processors and cloud environments.

Component PopUp Mainframe Requirements Notes
Storage 120 GB (System Disk)
1 TB (Data Disk)		 The OVA file size is 50 GB.
A minimum of 1 TB of disk space is required for the image to install.
The OVA unpacks to 293 GB along with 700 GB of DASD volumes
pre-defined.
Depending on the size of application data, the disk size can be increased.
CPUs/Cores 2 CPUs (minimum)
1 CPU for Linux O/S
1 or more for ZD&T		 Customers can allocate more CPUs for performance improvements
depending on their workloads.
Memory 16 GB Memory reservation is required
Host OS See Release Notes for list of supported platforms

PopUp Z runs on mainframes which have IFL processors.

Resource Minimum Recommended
Storage 120 GB (System Disk)
1 TB (Data Disk)		 A minimum of 1 TB of disk space is required for the image to install.
The image size is 63 GB with volumes. Depending on the size of
application data, the disk size can be increased.
IFLs 1 (dedicated or shared) 2+ for multiple guests or headroom
vCPUs 2 assigned to PopUp guest 4-6 depending on workloads
Memory 16 GB (host + guest) 32-64 GB preferred
Host OS Linux with KVM Support

Network Requirements (PopUp X and PopUp Z)

Port Number Network
Traffic Direction		 Mandatory /
Optional		 Notes
22(SSH) Inbound Mandatory SSH access to Linux host of PopUp env
for admin users (ibmsys1 or root)
3270
(Mainframe Terminal) ​		 Inbound Mandatory Port used for z/OS 3270 terminal access
1947 and 9451
(PopUp License Server)		 Outbound Mandatory Ports used by PopUp VM to connect
to license server
21 FTP
(if needed)		 Inbound/
Outbound		 Optional Port used for mainframe file transfers
(control connection) ​
50000 to 50099
FTP Data ports		 Inbound/
Outbound		 Optional Port Range for passive FTP
data transfer between PopUps
9001​ Inbound Optional Web-based log viewer interface
(e.g. http://<"PopUp-VM-IP":9001)
as part of the Linux host forwarding configuration ​
NFS Inbound /
Outbound		 Optional Enables PopUp-Delphix connectivity
through NFS mounts
10443
(z/OSMF)		 Outbound Optional Port used for accessing the z/OSMF web UI
and REST APIs securely
from PopUp Mainframe
3990 and 3991
(IBM Migration Utility)		 Inbound Optional Ports used by Migration server
to migrate DASD Volumes
4035
(IBM Developer for Z)		 Inbound Optional Port for connecting IBM Developer for Z
to PopUp Mainframe
1414
(IBM MQ Explorer)		 Inbound Optional Port for connecting IBM MQ Explorer
to PopUp Mainframe
48226
(BMC CES)		 Inbound Optional http port. Used to connect to the web UI
for BMC mainframe products
16196
(BMC HCI)		 Inbound Optional http port. Used to connect the
BMC ECC Workbench to HCI
23000 & 23001
(BMC Code Pipeline)		 Inbound Optional http port. Used to connect
BMC Workbench to BMC Code Pipeline
Miscellaneous Ports Inbound /
Outbound		 Optional Any other application ports
(If PopUp connects to external systems)

The PopUp Mainframe licensee is not authorized to use the product for purposes of code refactoring or re-engineering with the intention to re-platform existing z/OS based applications, or for processing production workloads.


ZD&T License Server Requirements

A ZD&T License Server VM is required in addition to the PopUp Mainframe VM.

Important notes about the license server

  1. There is no Z hardware (IFL) image for a license server, it can only run on an x86 VM
  2. The license server cannot run on the same VM as a PopUp Mainframe instance, a separate VM is required
  3. Once the updated license file has been applied you cannot change the device for the license server or change the underlying storage as this will invalidate the license. If you need to do this please get in touch with the PopUp Support Team.
  4. If the license server is hosted on Azure and the requirement is to stop/start when required, then Azure dedicated host is needed. This prevents the CPU id from changing and invalidating the license.

License Server Requirements

Component License Server Requirements Notes
Storage 40 GB (System Disk)
CPUs/Cores 1 CPUs Virtual Box and Azure are supported
Validation is carried out to ensure the
hardware has not changed
Memory 4 GB Memory reservation is required
Host OS Azure Marketplace, KVM (for x86)
or VirtualBox OVA


Delphix Specific Requirements

Integrating a PopUp Mainframe with Delphix for Data Masking and/or Data Virtualization will require additional hardware resources to be allocated to the PopUp Mainframe virtual machine.

Memory

It is our recommendation that you size the ZD&T server the same size as Delphix. The minimum memory size for Delphix is 64GB so we therefore recommend you size the same. We have found in tests in some instances, ZD&T does not require as much memory, depending on the workload you may be able to reduce the memory size even down to 16GB as this is the minimum for ZD&T to run.

To change the memory update devmap and IPL for settings to take effect.

vCPUs

We recommend 1 vCPU for every 2TB of data you work with. Therefore if you ingest 2TB you will need 1 vCPU whereas if you are working with 4TB you will need 2vCPUs for ZD&T.

Each vCPU you allocate will require a ZD&T license. Therefore if you allocate 2vCPU it will look to the license server for a minimum of two licenses before ZD&T will run.

Depending on the exact workload and speed requirements will determine how many licenses ZD&T will need.

To change the CPU allocation update devmap and IPL for settings to take effect.

Network

Additional ports should be allocated if using Delphix. Check the Delphix Documentation for full details. Make sure to use the correct version of Delphix documentation.

ZD&T License Usage for Delphix

Ingesting data into Delphix requires exclusive access to a PopUp Mainframe license. Once the data has been fully ingested you can shutdown the staging PopUp instance to free up the license. Whenever you replicate and provision a PopUp environment every concurrently running instance will require its own license. Branching does not require a license as it is a copy and does not change the underlying data.

For example, If you were to provision a PopUp instance into ‘Dev’ that was updating Db2 and another user wanted to read and write data, you would need to have another PopUp license available to provision and run a second copy.


Page last revised on: 2026-03-19