WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Disk space requirements on z/OS

The installation of WebSphere® Message Broker for z/OS® uses approximately 400 MB of disk space; plan on using 500 MB to allow for the component directories, and for new service fixes to be applied.

When you apply service, if you do not replace your existing installation (for example, you apply the new fix pack level alongside your existing installation), you must plan the same amount of disk space for the higher service level libraries.

If you are transferring the files by using tar to package them, you need approximately 200 MB of space for the .tar file.

You can check how much space is used and how much is free in a file system by using the OMVS command:
 df -P /pathname
100 MB is 3 276 800 512 byte sectors.
The following table gives guidance on the space required for a minimum installation (base installation and verification test) of WebSphere Message Broker for each component implemented on z/OS.
Component Space required Purpose
Component directory 20 MB Holds the runtime-deployed configuration information and output directories for the component.

This information includes all deployment information, such as ESQL, JAR files, message sets, XSLT files, and so on.

This information also includes WebSphere Message Broker trace files and other user problem determination data, which might become large.

Consideration must be given to the potential size of deployments to the WebSphere Message Broker runtime environment and, therefore, the size of this directory (including sub directories).

Component PDSE 1 MB Holds the customization and administration jobs, procedures, and data for the component.

The data set must be allocated with a fixed record length of 80 (LRECL=80) and a format of FB 80. Reserve directory space for 50 members, or use a PDSE if possible.

Started task user ID home directory 8 GB Collects diagnostic materials: for example, dumps. Dumps are usually more than 500 MB in size.

8 GB of space must be available in the file system, but many user IDs can have their home directory in the file system.

The Component directory and the Started task user ID home directory must be separate to ensure that, when dumps are taken in the Started task user ID home directory, they do not cause problems with the runtime broker that still has to write to the Component directory.

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:46:59


Reference topicReference topic | Version 8.0.0.7 | ae22210_