Skip to main content

Techdocs Library > Hints, tips & Technotes >

WebSphere for z/OS V6 -- Overcoming Temp Space Shortage When Installing Large Applications



Document Author:

Don Bagwell


Document ID:

TD102662


Doc. Organization:

Washington Systems Center


Document Revised:

10/19/2005


Product(s) covered:

WebSphere







Abstract: When installing applications into a WebSphere for z/OS Network Deployment configuration, the Deployment Manager's servant region JVM will -- by default -- use the /tmp directory as a staging area for application files. In most cases this works perfectly well. But there are cases when a large application may exhaust the available space in /tmp. Then you have two options: 1) increase the size of /tmp (which may require an IPL, depending on your conditions), or 2) tell WebSphere to use a different directory.

This Techdoc explains how to do the second of the two. It explains first how to check for the available space in /tmp and to determine what userid is presently using the space, then it explains how to take one of two approaches to changing the temporary directory WebSphere will use -- the -Djava.io.tmpdir= property in the DMGR's servant region JVM, or the TMPDIR variable. Both achieve the same result.

TD102662 - Overcoming Temp Space Shortage When Installing Large Apps.pdf



Classification:

Software

Category:

Operational Management




Platform(s):

IBM System z Family

S/W Pillar(s):

WebSphere

O/S:

z/OS

Keywords:

tmp temp temporary TMPDIR JVM staging

The Techdocs Library
Is this your first visit to Techdocs (the Technical Sales Library)?

Learn more


Techdocs QuickSearch

: