Look up table temporary Storage space

major · Post by **major** » Thu Jul 28, 2011 7:53 am

Hi,

In our job we are Creating dataset in a user defined path, to avoid size issues in the /dsProjects/Datasets path by modifying the configuration file.
our User defined path for Datasets grew to a size of 60GB. While running some of our job the temporary look up lookuptable.20110728.cso50ab is also created in the user defined path look up. This being a resource disk the job which runs for 4 Minutes when ran alone and is running for 2HRS when called from a sequence. Is there any options for creating the temporary look up table lookuptable.20110728.cso50ab in the virtual memory, so that the reading of dataset will be faster

ray.wurlod · Post by **ray.wurlod** » Thu Jul 28, 2011 4:43 pm

How, precisely, do you go about "Creating dataset in a user defined path"? If all you create there is the descriptor file, you're not accomplishing much. The data, or "segment", files that comprise the data set are stored in the directories identified as "resource disk" in your parallel execution configuration file.

major · Post by **major** » Thu Jul 28, 2011 9:25 pm

we have modified the resource disc to create the data segments in the /dsProjects/data/xxxxx/(user defined) directory by modifying the resource disk parameter in the configuration file while creating the datasets. now while reading the dataset for lookup the temporary look up lookuptable.20110728.cso50ab is also created in the /dsProjects/data/xxxxx/(user defined) directory which makes the job slow. Is there any other parameter I need to change so that this temporary storage happens in the /dsProjects/Datasets path