"NOT IN VOC" Error

koti9 · Post by **koti9** » Tue Aug 18, 2009 7:28 am

Hi all,

We get 'Job not in VOC Error' on our unix box once in a while. The same job runs perfectly alright most of the days...Did anyone get this even after DSHOME is set up perfectly...Unix was up and running perfectly when it failed. Please let me know. Thanks in Advance.

Thanks
Koti

chulett · Post by **chulett** » Tue Aug 18, 2009 8:31 am

Can you please post the full, unedited error? And explain when/where exactly it is that you get this error 'once in a while'?

ray.wurlod · Post by **ray.wurlod** » Tue Aug 18, 2009 4:56 pm

Do you perhaps mis-type (mis-spell or mis-case) the job name in dsjob commands? Job names are not recorded in VOC in any case, so we really do need to know the exact error message.

koti9 · Post by **koti9** » Wed Aug 19, 2009 7:34 am

chulett wrote:Can you please post the full, unedited error? And explain when/where exactly it is that you get this error 'once in a while'?

Hi all,

Sorry it wasn't the job, it couldn't find the dsproject home.Though the file .dsproject is available. Here is the error below.

Cannot find DataStage project directory.Unmatched quotation marks.
Verb "/unixbox/ASCENTIAL/DATASTAGE/DSENGINE/.DSPROJECT"" is not in your VOC.

Thanks
Koti

ArndW · Post by **ArndW** » Wed Aug 19, 2009 7:39 am

I think we are still unclear as to where this is happening and what is triggering it. It seems to be a executing a TCL shell command but using a UNIX type path.

chulett · Post by **chulett** » Wed Aug 19, 2009 7:43 am

We are still unclear as to the where and what. Is this coming from a script, custom routine, TCL command, something else entirely?? Can you post it, whatever it is?

ray.wurlod · Post by **ray.wurlod** » Wed Aug 19, 2009 6:06 pm

The reference to VOC may be a complete "red herring". If there were a SH verb followed by a command with mismatched quotes, or containing the same quote character as the one with which the command were delimited, then this error might arise. If this is in your software, then you need to fix it; if it is in IBM's, you need to generate a support call with them.

koti9 · Post by **koti9** » Thu Aug 20, 2009 7:34 am

ArndW wrote:I think we are still unclear as to where this is happening and what is triggering it. It seems to be a executing a TCL shell command but using a UNIX type path. ...

Hi all,
Sorry for not being clear, the very first time.
I am running the batch job control. Inside the batch i am using the DSExecute to execute the OS Command. Thats where its faling mentioning the below in my job log.

Cannot find DataStage project directory.Unmatched quotation marks.
Verb "/unixbox/ASCENTIAL/DATASTAGE/DSENGINE/.DSPROJECT"" is not in your VOC.

Thanks
Koti

chulett · Post by **chulett** » Thu Aug 20, 2009 7:38 am

Post your code.

ArndW · Post by **ArndW** » Thu Aug 20, 2009 8:36 am

Yes, please post your code. Somewhere you have a badly formed EXECUTE or PERFORM command.

jgreve · Post by **jgreve** » Thu Aug 20, 2009 8:48 am

The unmatched quote part caught my eye.

koti9 wrote:Cannot find DataStage project directory.Unmatched quotation marks.
Verb "/unixbox/ASCENTIAL/DATASTAGE/DSENGINE/.DSPROJECT"" is not in your VOC.
Koti

Possible that you have a typo on your path setup?
It looks like there is a trailing quote on the 'verb' thing.

Are you declaring /unixbox/ASCENTIAL/DATASTAGE/DSENGINE/.DSPROJECT
as a string value anywhere in your scripts?
Look to see if you have a trailing quote one it.
I do that in windows batch files once in a while, e.g. set x="foo"
forgetting that unix shell scripting is smarter about quotes (e.g. windos
batch assigns x a 5 char string, including the quote-values, whereas
unix shells like bash would only do 3 chars, the foo part).

Anyway, whatever you're scripting in seems unhappy about quoting.
Good luck.

DSXchange

"NOT IN VOC" Error

"NOT IN VOC" Error

"NOT IN VOC" Error

unmatched quote?