It looks like youre running into a "LONG.NAMES" problem. The "CA_CU_CUS000" handle is a truncation of "CA_CU_CUSTOMER_ACCOUNT_H". Verify that the VOC item "CA_CU_CUSTOMER_ACCOUNT_H" points to the correct Unix file; whatever field 2 of the VOC file points to should be the actual Unix name (& path, if its not in the same directory as the VOC).
Ill have to RTFM, but you probably should enable long names, so that these truncations dont occur. It looks like you create this file in your job, so just fixing the VOC would be a temporary fix, good until you run this or a similar process again.
Im just now learning DataStage ( a decade of UniVerse, though, which is from where I derive all of the above answers), so Im not sure what the ramifications are of editing a VOC, yet (Ill also RTFM on that tonight).
HTH
Dan
STANGE STATE
Ok, the disk full problem is one youll have to resolve, but the error messages youre getting dont indicate that as the problem.
Can you open a UniVerse session?
Id like you to get to the TCL prompt (an >), and do this:
CT VOC CA_CU_CUSTOMER_ACCOUNT_H
This should show you 3 lines, something like this:
0001: F
0002: CA_CU_CUS000
0003: D_CA_CU_CUS000
Now, if you do a "sh" at the TCL prompt, youll be in the Unix shell. if the CA_CU_CUS000 file is not in the directory youll find yourself within at that moment, then your VOC needs the full path to the file. If the VOC doesnt point right to it, then as far as UniVerse knows, theres no UNIX file for UniVerse to find. Since there is a VOC item already existing, you cant create a new file with the same name.
You can edit that VOC to point to CA_CU_CUS000, or you can edit the VOC item & delete it. Then youd want to delete the Unix level CA_CU_CUS000 (perhaps back it up first), where ever it is, and run the job again. This should simply create the file correctly; it looks like one error message is for a failed file create operation.
Dan
>>>more info
The problem occur when the disk was full.
At the unix level I could see the file CA_CU_CUS000.
I could I delete an entry in the VOC without deleting the file.
One solution is to export,delete,create,import the whole project but I would
like if possible avoid this solution.
In the same time whe get some job lossing their RT_CONFIG file.
(Nothing simple
)
>>>
Coud somebody help me with this strange state of the hash file.
In Datastage director I get the following error when I validate the job.
CaValiderRecordTRPrep.CU_CUSTOMER_ACC.CU_CUST: DSD.UVOpen
"CA_CU_CUSTOMER_ACCOUNT_H" is already in your VOC file as a file definition
record..
Project:DWHCSP_DEV (dwhdev)
Job name:CaValiderRecordTRPrep
Event #:49
Timestamp:06/26/2001 3:18:12 PM
Event type:Fatal
User:gsc01624
Message:
CaValiderRecordTRPrep.CU_CUSTOMER_ACC.IDENT1:
|CaValiderRecordTRPrep.CU_CUSTOMER_ACC.CU_CUST: DSD.UVOpen
"CA_CU_CUSTOMER_ACCOUNT_H" is already in your VOC file as a file definition
record..|
But, if I use the Datastage Administrator to clean the hash file I get the
following message. ( the command is CLEAR.FILE CA_CU_CUSTOMER_ACCOUNT_H )
Cannot open file"CA_CU_CUS000".
*** Processing cannot continu. ***
My feelling isan entry in the VOC file exist but for some reason (I suspect
a delete at Unix level) the file (data) is not there.
Could I delete the entry in the VOC file and how (of course if its
possible).
Can you open a UniVerse session?
Id like you to get to the TCL prompt (an >), and do this:
CT VOC CA_CU_CUSTOMER_ACCOUNT_H
This should show you 3 lines, something like this:
0001: F
0002: CA_CU_CUS000
0003: D_CA_CU_CUS000
Now, if you do a "sh" at the TCL prompt, youll be in the Unix shell. if the CA_CU_CUS000 file is not in the directory youll find yourself within at that moment, then your VOC needs the full path to the file. If the VOC doesnt point right to it, then as far as UniVerse knows, theres no UNIX file for UniVerse to find. Since there is a VOC item already existing, you cant create a new file with the same name.
You can edit that VOC to point to CA_CU_CUS000, or you can edit the VOC item & delete it. Then youd want to delete the Unix level CA_CU_CUS000 (perhaps back it up first), where ever it is, and run the job again. This should simply create the file correctly; it looks like one error message is for a failed file create operation.
Dan
>>>more info
The problem occur when the disk was full.
At the unix level I could see the file CA_CU_CUS000.
I could I delete an entry in the VOC without deleting the file.
One solution is to export,delete,create,import the whole project but I would
like if possible avoid this solution.
In the same time whe get some job lossing their RT_CONFIG file.
(Nothing simple
)>>>
Coud somebody help me with this strange state of the hash file.
In Datastage director I get the following error when I validate the job.
CaValiderRecordTRPrep.CU_CUSTOMER_ACC.CU_CUST: DSD.UVOpen
"CA_CU_CUSTOMER_ACCOUNT_H" is already in your VOC file as a file definition
record..
Project:DWHCSP_DEV (dwhdev)
Job name:CaValiderRecordTRPrep
Event #:49
Timestamp:06/26/2001 3:18:12 PM
Event type:Fatal
User:gsc01624
Message:
CaValiderRecordTRPrep.CU_CUSTOMER_ACC.IDENT1:
|CaValiderRecordTRPrep.CU_CUSTOMER_ACC.CU_CUST: DSD.UVOpen
"CA_CU_CUSTOMER_ACCOUNT_H" is already in your VOC file as a file definition
record..|
But, if I use the Datastage Administrator to clean the hash file I get the
following message. ( the command is CLEAR.FILE CA_CU_CUSTOMER_ACCOUNT_H )
Cannot open file"CA_CU_CUS000".
*** Processing cannot continu. ***
My feelling isan entry in the VOC file exist but for some reason (I suspect
a delete at Unix level) the file (data) is not there.
Could I delete the entry in the VOC file and how (of course if its
possible).