standardize error
standardize error
can anyone help me with this error,
Standardize_385: Unable to open control file ./RT_QS32/V0S385/Controls/CopyOfUSNAME.DCT for input, reason code 2
No such file or directory
thanks,
Rahul
Standardize_385: Unable to open control file ./RT_QS32/V0S385/Controls/CopyOfUSNAME.DCT for input, reason code 2
No such file or directory
thanks,
Rahul
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
ray.wurlod wrote:Usually this message stems from failure to provision all files in the rule set. ...
Thanks Ray,
Yes it is the problem of provisioning....
I have this message
Unable to link rule file, CopyOfUSNAME1.UPO, file may need provisioning
How can I provision the file can you please help me with that?
-
- Participant
- Posts: 40
- Joined: Thu Apr 17, 2008 1:52 pm
- Location: Huntsville, AL
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Right click on the SET icon in the Repository toolbar and choose Provision All. Or, as you're selecting the rule set within a design you can do the same thing.
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: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Version 8.7
I experienced exactly this problem today, but provisioning the rule set did not solve the problem.
stanEmail: Unable to open control file ./RT_QS5/V0S17/Controls/FLTREMAIL.DCT for input, reason code 2
A file or directory in the path name does not exist.
Instead we had to delete the process from the Standardize stage and add it there afresh, then re-compile the job.
We deduce that this re-emplaces the control file on the engine machine.
stanEmail: Unable to open control file ./RT_QS5/V0S17/Controls/FLTREMAIL.DCT for input, reason code 2
A file or directory in the path name does not exist.
Instead we had to delete the process from the Standardize stage and add it there afresh, then re-compile the job.
We deduce that this re-emplaces the control file on the engine machine.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Unable to link rule file, USADDR.SET, file may need provisio
Hi,
I have experienced the similar problem today.
We are using a shared container in a job which is performing the address validations and it has been called by the same parallel job multiple times. When i try to run the job, i am getitng the below error.
"Unable to link rule file, USADDR.SET, file may need provisioning"
I tried to do the provision all per the earlier comments and it hasn't worked.
Job worked when i use the shared container once. But when I use multiple times in the same job, it's throwing the above error. Please suggest.
Thanks
I have experienced the similar problem today.
We are using a shared container in a job which is performing the address validations and it has been called by the same parallel job multiple times. When i try to run the job, i am getitng the below error.
"Unable to link rule file, USADDR.SET, file may need provisioning"
I tried to do the provision all per the earlier comments and it hasn't worked.
Job worked when i use the shared container once. But when I use multiple times in the same job, it's throwing the above error. Please suggest.
Thanks