Page 1 of 1

Configuration File - Scratchdisk allocation

Posted: Wed Mar 29, 2017 8:33 am
by PeteM
Below is the current configuration file that has the RAM disk as the first entry in the scratch disk resource pool.

For some reason data stage is using the hard disk entries (/opt/scratch1, /opt/dataset2/scratch, etc.) first and then once they are fully utilised, the RAM disk is being used.

Can anyone state how to amend the configuration entries to ensure that the RAM disk is used first?

Code: Select all

        node "node1"
        {
                fastname "baspc234u1"
                pools ""
                resource disk "/opt/dataset1" {pools ""}
                resource disk "/opt/dataset2" {pools ""}
                resource disk "/opt/dataset3" {pools ""}
                resource disk "/opt/dataset4" {pools ""}
                resource disk "/opt/dataset5" {pools ""}
                resource scratchdisk "/ramdisks/ramdisk0" {pools ""}
                resource scratchdisk "/opt/scratch1" {pools ""}
                resource scratchdisk "/opt/dataset1/scratch" {pools ""}
                resource scratchdisk "/opt/dataset2/scratch" {pools ""}
                resource scratchdisk "/opt/dataset3/scratch" {pools ""}
                resource scratchdisk "/opt/dataset4/scratch" {pools ""}
                resource scratchdisk "/opt/dataset5/scratch" {pools ""}
        }
        node "node2"
        {
                fastname "baspc234u1"
                pools ""
                resource disk "/opt/dataset2" {pools ""}
                resource disk "/opt/dataset3" {pools ""}
                resource disk "/opt/dataset4" {pools ""}
                resource disk "/opt/dataset5" {pools ""}
                resource disk "/opt/dataset1" {pools ""}
                resource scratchdisk "/ramdisks/ramdisk0" {pools ""}
                resource scratchdisk "/opt/scratch1" {pools ""}
                resource scratchdisk "/opt/dataset2/scratch" {pools ""}
                resource scratchdisk "/opt/dataset3/scratch" {pools ""}
                resource scratchdisk "/opt/dataset4/scratch" {pools ""}
                resource scratchdisk "/opt/dataset5/scratch" {pools ""}                
                resource scratchdisk "/opt/dataset1/scratch" {pools ""}
        }
        node "node3"
        {
                fastname "baspc234u1"
                pools ""
                resource disk "/opt/dataset3" {pools ""}
                resource disk "/opt/dataset4" {pools ""}
                resource disk "/opt/dataset5" {pools ""}
                resource disk "/opt/dataset1" {pools ""}
                resource disk "/opt/dataset2" {pools ""}
                resource scratchdisk "/ramdisks/ramdisk0" {pools ""}
                resource scratchdisk "/opt/scratch1" {pools ""}
                resource scratchdisk "/opt/dataset3/scratch" {pools ""}
                resource scratchdisk "/opt/dataset4/scratch" {pools ""}
                resource scratchdisk "/opt/dataset5/scratch" {pools ""}                
                resource scratchdisk "/opt/dataset1/scratch" {pools ""}
                resource scratchdisk "/opt/dataset2/scratch" {pools ""}
        }
        node "node4"
        {
                fastname "baspc234u1"
                pools ""
                resource disk "/opt/dataset4" {pools ""}
                resource disk "/opt/dataset5" {pools ""}
                resource disk "/opt/dataset1" {pools ""}
                resource disk "/opt/dataset2" {pools ""}
                resource disk "/opt/dataset3" {pools ""}
                resource scratchdisk "/ramdisks/ramdisk0" {pools ""}
                resource scratchdisk "/opt/scratch1" {pools ""}
                resource scratchdisk "/opt/dataset4/scratch" {pools ""}
                resource scratchdisk "/opt/dataset5/scratch" {pools ""}                
                resource scratchdisk "/opt/dataset1/scratch" {pools ""}
                resource scratchdisk "/opt/dataset2/scratch" {pools ""}                
                resource scratchdisk "/opt/dataset3/scratch" {pools ""}
        }
        node "node5"
        {
                fastname "baspc234u1"
                pools ""
                resource disk "/opt/dataset5" {pools ""}
                resource disk "/opt/dataset1" {pools ""}
                resource disk "/opt/dataset2" {pools ""}
                resource disk "/opt/dataset3" {pools ""}
                resource disk "/opt/dataset4" {pools ""}
                resource scratchdisk "/ramdisks/ramdisk0" {pools ""}
                resource scratchdisk "/opt/scratch1" {pools ""}
                resource scratchdisk "/opt/dataset5/scratch" {pools ""}                
                resource scratchdisk "/opt/dataset1/scratch" {pools ""}
                resource scratchdisk "/opt/dataset2/scratch" {pools ""}                
                resource scratchdisk "/opt/dataset3/scratch" {pools ""}
                resource scratchdisk "/opt/dataset4/scratch" {pools ""}
        }

Posted: Wed Mar 29, 2017 3:16 pm
by Mike
Try putting your ramdisk into its own non-default pool.

Mike

Posted: Wed Mar 29, 2017 4:25 pm
by PaulVL
According to IBM, I would have expected your ram disk to be targeted first, then it would spill over to the other scratch disk entries.



http://www-01.ibm.com/support/docview.w ... wg21651831


Does your job execution user id have rwx access to that ram disk path?

Posted: Thu Mar 30, 2017 5:54 am
by PeteM
thanks for the reply

Posted: Thu Mar 30, 2017 6:45 am
by chulett
So... what was the resolution?