Allocating Temporary Files

How to:

Reference:

Temporary files are transient files that disappear after you end a session. By default, all temporary data files (for HOLD and FOCSORT files) and temporary metadata files, such as temporary Master Files and Access Files, are created in the temporary area of an agent, which corresponds to your TSCOM ID. For example, if your TSCOM ID is TS000001, your temporary files are located in //edatemp/ts000001.

For z/OS, you can control the size and location of these temporary metadata files and data files. You can specify that the temporary files reside in the hierarchical file system, MVS data sets, or in hiperspace.

Syntax: How to Allocate Temporary Files

To specify the allocation of your temporary files, issue the following command 

DYNAM SET TEMP[ALLOC] {HFS|MVS|HIPER}

where:

HFS

Allocates temporary files to the hierarchical file system. HFS is the default value.

MVS

Allocates temporary files to MVS data sets.

HIPER

Allocates temporary files to hiperspace.

Reference: Usage Notes for Allocating Temporary Files

For z/OS, temporary metadata files can be allocated using a similar procedure to allocating permanent metadata files:

  • If DYNAM allocation for HOLDMAST or HOLDACC is present, temporary files are stored in the designated PDSs.
  • If DYNAM SET TEMP[ALLOC] MVS is issued; in the default temporary PDSs.
  • If DYNAM SET TEMP[ALLOC] HIPER is issued; in the HIPERSPACE.

Syntax: How to Allocate Temporary Files to MVS Data Sets

To alter the default allocation parameters for temporary files for MVS data sets, issue the following command 

DYNAM SET TEMP[ALLOC] FOR type dynam_parms

where:

type

Is one of the following: HOLDACC, HOLDMAST, HOLD SAVE, REBUILD, FOCUS, FOCSORT, OFFLINE, or FOC$HOLD.

dynam_parms

Are regular DYNAM ALLOC parameters to be used as default for that type. Note that DCB parameters, if provided here, will be ignored, since they must be compatible with the file type being written.

This is similar to the functionality of IBITABLA in the SSCTL Server. The defaults should be overwritten for all cases when, in older versions, a private copy of IBITABLA existed containing different values.

Reference: System Defaults for Allocating Temporary Files to MVS Data Sets

System defaults for HOLDMAST and HOLDACC are: 

TRKS 5  5 DSORG PO DIR 36 NEW REU

System defaults for all other types are: 

CYLS 5 10 DSORG PS NEW REU

Syntax: How to Support Long Synonym Names Using DYNAM SET LONGSYNM

The server supports synonym names up to 64 characters. However, PDS member names cannot exceed eight characters. The server accounts for this operating environment limitation with the command DYNAM SET LONGSYNM.

A synonym comprises a Master File and, usually, an Access File. When you create a synonym with a name exceeding eight characters, the LONGSYNM setting currently in effect determines how the long name of the Master File and of the Access File will be handled.

You can issue DYNAM SET LONGSYNM anywhere SET commands are valid, including the global server profile (edasprof.prf) and a stored procedure (FOCEXEC).

DYNAM SET LONGSYNM, on servers running on z/OS, corresponds functionally to the server configuration file keyword LONGSYNM on servers running on MVS.

The syntax is

DYNAM SET LONGSYNM {HFS|MVS|MATCH}

where:

HFS

Specifies that each synonym whose name is longer than eight characters will be created in an HFS directory. This is the default.

MVS

Specifies that when you save a synonym with a name exceeding eight characters, the server truncates the name, preserving up to the first six characters, followed by a left curly brace ({) and a suffix number that ensures the name is unique. (The server preserves the original long name within the synonym files.)

For example, if you create a Master File named VERYLONGNAMETEST, it will be saved as VERYLO{0. If you then create a Master File named VERYLONGNAMEPROD, it will be saved as VERYLO{1.

The server chooses a suffix number by taking the next unused number in the sequence for that truncation of a Master File or Access File name. If the next number available for the Master File is different than that available for the Access File, the files will be created with different numbers. For example, if the highest Master File name truncated to VERYLO is VERYLO{8, and the highest Access File name truncated to VERYLO is VERYLO{5, and you create a synonym specifying the name VERYLONGNAMEAGAIN, the new Master File will be saved as VERYLO{9, and the new Access File will be saved as VERYLO{6.

MATCH

Works the same as the MVS setting, except that it ensures that the truncated names of a Master File and Access File synonym will always match. That is, they will be named using the same suffix number.

In the example provided for the MVS setting, if SET LONGSYNM had instead been set to MATCH, both the new Master File and the new Access File would have been named VERYLO{9.

Matching names may be a convenience for some people if they manually manage synonym files. It is less efficient than the MVS setting, however.