Temporary Disk Space Usage for Non-PDS Deployment

How to:

Temporary space, by default, is created under the configuration directory (ffs, wfs, or dm) in the file system used to install the product. The edatemp directory is two levels deep.

The first level directory is used for trace files if tracing is active. By default, the directory is named edatemp and is also generally referred to as the edatemp directory of EDACONF.

The subdirectory is used for temporary files and traces created by various processes, such as the TCP and HTTP listeners, the Workspace Manager, and the end-user agent processes. Each connecting user is assigned to a private data agent directory to isolate their work from other users, and that directory is cleaned up upon disconnect. The agent subdirectories are named tsnnnnnn, where nnnnnn is the ID number assigned to the data agent.

The edatemp directory can be configured to use a separate file system by setting the EDATEMP variable to point at the alternate location. The steps and syntax vary by platform, and may be done as an operating system variable or as a variable in the server configuration file (edaserve.cfg) before server start up.

If you are using the server configuration file, the best method is to edit edaserve.cfg from the Reporting Server browser interface Workspace folder, adding the line:

edatemp = directory

where

directory

Is a full path directory name, using the appropriate platform syntax. After saving, restart the server.

Note: Editing the server configuration file (edaserve.cfg) is the only method available for Windows.

Syntax: How to Specify the EDATEMP Variable

For UNIX and Linux, the edatemp variable can be coded in the edastart.sh file:

export EDATEMP=/u/iway/edatemp

Note: This also applies to IBM i and Windows.

DEFINE EDATEMP TMP:[TMP.EDATEMP]

For UNIX System Services, it can be coded in the ISTART JCL member under the EDAENV dd statement:

//EDAENV      DD   *
EDATEMP=/u/iway/edatemp

For z/OS UNIX System Services only, you can set the temporary area to MVS by using the following command in edasprof.prf or user profile.

DYNAM SET TEMPALLOC MVS

The above are global settings which affect temporary file allocations for all users.

It can be specified in the edaserve.cfg file.

edatemp=/u1/home/temp

Syntax: How to Pre-Allocate Temporary Files

You can pre-allocate an individual file for a user, using the following techniques:

  • For UNIX and Linux:
    FILEDEF XXX DISK /u/another/area/xxx.dat

    where:

    /u/another/area

    Has enough free space to hold the file.

  • For Windows:
    FILEDEF XXX DISK C:\tmp\another\area\xxx.dat

    where:

    tmp\another\area

    Has enough free space to hold the file.

  • For z/OS UNIX System Services:

    You can use the same FILEDEF syntax indicated for UNIX, or you can use the DYNAM command to direct the temporary file to MVS.

    DYNAM ALLOC FILE XXX SPACE

    Note that, for the DYNAM command, you must specify the amount of space required.

  • For FOCUS files:

    You can use the FILEDEF and USE commands to create a FOCUS file outside the edatemp area.

    FILEDEF NAME DISK /{pathname}{filename}.foc ......
    USE NAME NEW
    END

Syntax: How to Dynamically Allocate FOCUS Files on z/OS

You can dynamically allocate FOCUS files on z/OS with the USE command. The command is

DYNAM ALLOC FILE ddname SPACE
USE ddname AS masterfile 
END

where:

ddname

Is the DDNAME.

masterfile

Is the Master File name.

If the DDNAME and Master File name are the same, use just the command:

DYNAM ALLOC