Regarding VOC File
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 58
- Joined: Thu Feb 15, 2007 3:42 pm
Regarding VOC File
Hi all,
I am beginer in Datastage.I Dont know about VOC,Q-Pointer. What it does in datastage.
AND
I had given like this I got below output,Really i dont know what happend here.I know that uvsh is used to give ds.tools command here.thats why i had issued this command.But i got this output.
please educate me regarding this concept.
$ uvsh
This directory is not set up for DataStage.
Would you like to set it up (Y/N)?y
0. Ideal compatibility
1. IN2 compatibility
2. Prime Information compatibility
3. PICK compatibility
4. PI/open compatibility
5. Microdata Reality compatibility
Which way do you wish to configure your VOC ?
Your VOC is configured for Ideal compatibility
Creating file "VOC" as Type 3, Modulo 23, Separation 4.
Creating file "D_VOC" as Type 3, Modulo 2, Separation 1.
Loading your "VOC" file. (Each "*" = 10 records.)
***************************************************************************
Loading your "D_VOC" file. (Each "*" = 10 records.)
*
Creating file "&SAVEDLISTS&" as Type 1.
Creating file "D_&SAVEDLISTS&" as Type 3, Modulo 1, Separation 2.
Added "@ID", the default record for Retrieve, to "D_&SAVEDLISTS&".
Creating file "VOCLIB" as Type 2, Modulo 7, Separation 4.
Creating file "D_VOCLIB" as Type 3, Modulo 1, Separation 2.
Added "@ID", the default record for Retrieve, to "D_VOCLIB".
DataStage Command Language 7.5
Copyright (c) 1997 - 2004 Ascential Software Corporation. All Rights Reserved
bin logged on: Saturday, December 15, 2007 00:11
I am beginer in Datastage.I Dont know about VOC,Q-Pointer. What it does in datastage.
AND
I had given like this I got below output,Really i dont know what happend here.I know that uvsh is used to give ds.tools command here.thats why i had issued this command.But i got this output.
please educate me regarding this concept.
$ uvsh
This directory is not set up for DataStage.
Would you like to set it up (Y/N)?y
0. Ideal compatibility
1. IN2 compatibility
2. Prime Information compatibility
3. PICK compatibility
4. PI/open compatibility
5. Microdata Reality compatibility
Which way do you wish to configure your VOC ?
Your VOC is configured for Ideal compatibility
Creating file "VOC" as Type 3, Modulo 23, Separation 4.
Creating file "D_VOC" as Type 3, Modulo 2, Separation 1.
Loading your "VOC" file. (Each "*" = 10 records.)
***************************************************************************
Loading your "D_VOC" file. (Each "*" = 10 records.)
*
Creating file "&SAVEDLISTS&" as Type 1.
Creating file "D_&SAVEDLISTS&" as Type 3, Modulo 1, Separation 2.
Added "@ID", the default record for Retrieve, to "D_&SAVEDLISTS&".
Creating file "VOCLIB" as Type 2, Modulo 7, Separation 4.
Creating file "D_VOCLIB" as Type 3, Modulo 1, Separation 2.
Added "@ID", the default record for Retrieve, to "D_VOCLIB".
DataStage Command Language 7.5
Copyright (c) 1997 - 2004 Ascential Software Corporation. All Rights Reserved
bin logged on: Saturday, December 15, 2007 00:11
Arunkumar..
Forget about VOCs and Q-Pointers, they are far from beginner topics and not something a beginner really needs to be concerned about or should be having to deal with. And a 'beginner in DataStage' really has no business being in DS.TOOLS.
Secondly, when you type 'uvsh' (or more properly 'dssh' nowadays) if you are not currently parked in what I can only think to call an 'account directory' - $DSHOME or a Project, typically - you will get asked that question. If you are asked that question, it means you are in the wrong directory and the correct answer to 'Would you like to set it up?' is NO. You haven't done any damage, per se, by answering yes but you've created all this 'stuff' wherever you are for no good reason, stuff that will never be used.
So, back to what brought you here - why in the world do you think you need to be accessing the DS.TOOLS menu? What problem are you trying to solve?
Secondly, when you type 'uvsh' (or more properly 'dssh' nowadays) if you are not currently parked in what I can only think to call an 'account directory' - $DSHOME or a Project, typically - you will get asked that question. If you are asked that question, it means you are in the wrong directory and the correct answer to 'Would you like to set it up?' is NO. You haven't done any damage, per se, by answering yes but you've created all this 'stuff' wherever you are for no good reason, stuff that will never be used.
So, back to what brought you here - why in the world do you think you need to be accessing the DS.TOOLS menu? What problem are you trying to solve?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 58
- Joined: Thu Feb 15, 2007 3:42 pm
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
cd to the directory where you first executed the uvsh command and there execute the following UNIX command
This will clean up the unneeded account.
DO NOT - ever - execute these commands in the DataStage engine directory or in a DataStage project directory. You would irretrievably corrupt them.
Code: Select all
rm -rf VOC D_VOC VOCLIB D_VOCLIB \&SAVEDLISTS\& D_\&SAVEDLISTS\&
DO NOT - ever - execute these commands in the DataStage engine directory or in a DataStage project directory. You would irretrievably corrupt them.
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.
-
- Participant
- Posts: 58
- Joined: Thu Feb 15, 2007 3:42 pm
Regarding VOC File
Hi
I am sorry You misunderstood my words.I know Mr.Ray is great person, So many of my issues were solved with his suggestions.I feel him as my "Master".Just i want learn what is VOC,Q-pointer.My intension is not to doubt him.Please see the topic from the starting.It is purely miscommunication between us.
Once again I am Sorry for this.
Thanks for your suggestion.
I am sorry You misunderstood my words.I know Mr.Ray is great person, So many of my issues were solved with his suggestions.I feel him as my "Master".Just i want learn what is VOC,Q-pointer.My intension is not to doubt him.Please see the topic from the starting.It is purely miscommunication between us.
Once again I am Sorry for this.
Thanks for your suggestion.
Arunkumar..
-
- Participant
- Posts: 58
- Joined: Thu Feb 15, 2007 3:42 pm
Regarding VOC File
Hi
I am sorry You misunderstood my words.I know Mr.Ray is great person, So many of my issues were solved with his suggestions.I feel him as my "Master".Just i want learn what is VOC,Q-pointer.My intension is not to doubt him.Please see the topic from the starting.It is purely miscommunication between us.
Once again I am Sorry for this.
Thanks for your suggestion.
I am sorry You misunderstood my words.I know Mr.Ray is great person, So many of my issues were solved with his suggestions.I feel him as my "Master".Just i want learn what is VOC,Q-pointer.My intension is not to doubt him.Please see the topic from the starting.It is purely miscommunication between us.
Once again I am Sorry for this.
Thanks for your suggestion.
Arunkumar..
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
VOC is a database table in the Repository database that contains the vocabulary (all the command names, routine names, table names and so on) used in that project. Each project has a separate VOC.
Q-pointers are a way of referring to a table in a different project. They are not, in general, used in DataStage but are a hangover from the UniVerse database product on which DataStage used to be built.
Q-pointers are a way of referring to a table in a different project. They are not, in general, used in DataStage but are a hangover from the UniVerse database product on which DataStage used to be built.
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.