VOC file and commands

[dsdev601]

Hi,

Would like to have more information on the VOC file and the commands available for the VOC file. Of late, have been having problems with the RT_STATUSxxxx AND RT_CONFIGxxxx, e.g. tried to delete a job but couldn't because of issues with the RT_CONFIG etc.

[tonystark622]

Make sure you have your permissions and umask set right...

Tony

[dsdev601]

Thanks for the quick reply. could you please explain what umask and other permissions need to be set.

[ray.wurlod]

Recommended umask is 002. This means that everyone in the same group as the user who creates an object (such as an RT_CONFIGxxx file) will have all access to that object.

Permissions on the VOC file should be -rw-rw-r-- for similar reasons.

Permissions on the project directory should be drwxrwxr-x which allows the group to create (and delete) objects in the directory.

[tonystark622]

I'm not sure if this is normal, something specific to HP, or something we're not smart enough to figure out a way around, but we had to set the 's' permission on the group for the project directory and any directories where we wrote hash files or data. This is supposed to make any directories or files created within a directory belong to the same group as that directory (the parent). Our permissions ended up being
rwxrwsr.x

Good Luck,
Tony

[ray.wurlod]

If all your DataStage developers have the same primary group, the setgid bit ought not to be required.

[tonystark622]

Good point, Ray. Most of them did, but not all, and the primary group wasn't 'dstage', but a department group. We made all the files and directories that we access through DataStage owned by the dstage group. That explains why we had to set the 's' bit on the group.

Thanks,
Tony

[dsdev601]

Thanks guys for the useful info.