As a tuning suggestion, I have been advised to change the VOC file type to 30 as follows:
from project2, issue command to create a pointer to VOC in project1
SETFILE ../project1/VOC TEMPVOC
RESIZE TEMPVOC 30
then delete the pointer
Easy enough to do, but I'm wondering about the benefits vs the risks. Has anyone else tried this? If this is a good thing, why isn't the product shipped this way?
Resize VOC file to type 30
Moderators: chulett, rschirm, roy
-
- Charter Member
- Posts: 4
- Joined: Mon Sep 19, 2005 3:06 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You can not resize VOC while anything is active in that project. You would need to SETFILE from a different project.
Whence did you get this suggestion? I disagree heartily with it. While it is true that VOC can be a dynamic hashed file, there is no great gain, and higher risk of corruption. Resizing to a larger static hashed file would be a safer approach.
Remember, losing the VOC is catastrophic! All your routines are cataloged there, not to mention all the commands upon which DataStage relies.
Whence did you get this suggestion? I disagree heartily with it. While it is true that VOC can be a dynamic hashed file, there is no great gain, and higher risk of corruption. Resizing to a larger static hashed file would be a safer approach.
Remember, losing the VOC is catastrophic! All your routines are cataloged there, not to mention all the commands upon which DataStage relies.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Charter Member
- Posts: 4
- Joined: Mon Sep 19, 2005 3:06 pm
Thanks Ray. I agree with you completely...just needed some affirmation.
The advice is from PS GSC, and they are handing it out to customers. It's actually an attempt to increase performance for a few server jobs that are poorly designed to handle realistic amounts of data. I would guess that the VOC is not utilized by a running job much, once it starts executing, so I'm not sure there is much performance to gain there at all. I have resized the VOC (carefully) in a development environment without any adverse results. I'm not sure I would ever take that leap on a production project.
Thanks again.
The advice is from PS GSC, and they are handing it out to customers. It's actually an attempt to increase performance for a few server jobs that are poorly designed to handle realistic amounts of data. I would guess that the VOC is not utilized by a running job much, once it starts executing, so I'm not sure there is much performance to gain there at all. I have resized the VOC (carefully) in a development environment without any adverse results. I'm not sure I would ever take that leap on a production project.
Thanks again.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: