Changing the resource disk/resourcescratchdisk over the time

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
koti9
Participant
Posts: 52
Joined: Wed Nov 09, 2005 10:51 am

Changing the resource disk/resourcescratchdisk over the time

Post by koti9 »

Hi all,

Will it be a problem, if we change the path of resource disk/resource scratchdisk in the configuration file over the time? If we can change, then what happens to the files in the old path? Can we play around the scratch disk like deleting files as they were temporary when ds is down to free up space??(ofcourse in Development box)?

Thanks in advance

Koti
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Scratch disk should be empty if no jobs are running.

Disk is used for persistent Data Sets and File Sets (including Lookup File Sets); pathnames for their Lfiles are stored in their control files, so they should be findable.

That said, recommended best practice is always to use the same configuration file as the one with which it was created when dealing with a Data Set or File Set.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
csrazdan
Participant
Posts: 127
Joined: Wed May 12, 2004 6:03 pm
Location: Chicago IL

Post by csrazdan »

Hi,

Question 1: Changing configuration file:
You can change resource and scratch location in configuration file at any time without any problem. After the change, DataStage will use the new directories for resource and scratch. However, I would advice you to create a new configuration file rather than changing the current one. Reason is in answer for question 2.

Question 2: Deleting resource files:
You should use orchadmin utility to delete DataSet/FileSet. While creating DataSet/FileSet, DataStage stores configuration file name in DataSet descriptor file. Orchadmin uses this configuration file to delete resource files for DataSet. Consider, you have changed the resource and scratch path in the configuration file, you will not be able to delete the files from the old directory. You will have to use orchadmin options to delete the files form the old location. Follow following steps:

1. Create a temporary configuration file with resource and scratch pointing to old directories.
2. At UNIX prompt export APT_CONFIG_FILE to temporary configuration file.
3. Invoke orchadmin with following options:
orchadmin rm -fx file1.ds file2.ds file3.ds
Option -x will direct orchadmin to ignore configuration file from DataSet descriptor file and use the current defined by APT_CONFIG_FILE

Hope it helps.

Take care...
Shekhar
Assume everything I say or do is positive
koti9
Participant
Posts: 52
Joined: Wed Nov 09, 2005 10:51 am

Post by koti9 »

Hi Sekhar,

Thanks a lot for the valueable information.

Thanks & Regards
Koti
csrazdan wrote:Hi,

Question 1: Changing configuration file:
You can change resource and scratch location in configuration file at any time without any problem. After the change, DataStage will use the new directories for resource and scratch. However, I would advice you to create a new configuration file rather than changing the current one. Reason is in answer for question 2.

Question 2: Deleting resource files:
You should use orchadmin utility to delete DataSet/FileSet. While creating DataSet/FileSet, DataStage stores configuration file name in DataSet descriptor file. Orchadmin uses this configuration file to delete resource files for DataSet. Consider, you have changed the resource and scratch path in the configuration file, you will not be able to delete the files from the old directory. You will have to use orchadmin options to delete the files form the old location. Follow following steps:

1. Create a temporary configuration file with resource and scratch pointing to old directories.
2. At UNIX prompt export APT_CONFIG_FILE to temporary configuration file.
3. Invoke orchadmin with following options:
orchadmin rm -fx file1.ds file2.ds file3.ds
Option -x will direct orchadmin to ignore configuration file from DataSet descriptor file and use the current defined by APT_CONFIG_FILE

Hope it helps.

Take care...
Shekhar
Post Reply