Job Sequence Compilation Error
Moderators: chulett, rschirm, roy
Job Sequence Compilation Error
Hello,
While compiling a Job Sequencer, I am getting the below mentioned error.
<JobSeqGenError>
<Code>2017</Code>
<Desc>XML parser error on input line 0: source='', reason='The system cannot locate the resource specified.
'</Desc>
<LineNum>0</LineNum>
<Line></Line>
<Ref></Ref>
<Version>7.5.1.18</Version>
</JobSeqGenError>
Any idea on this.
While compiling a Job Sequencer, I am getting the below mentioned error.
<JobSeqGenError>
<Code>2017</Code>
<Desc>XML parser error on input line 0: source='', reason='The system cannot locate the resource specified.
'</Desc>
<LineNum>0</LineNum>
<Line></Line>
<Ref></Ref>
<Version>7.5.1.18</Version>
</JobSeqGenError>
Any idea on this.
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
You need write access to your c:\Program Files\Ascential\DataStage directory (or whatever equivelent directory your DataStage Client is installed to). Do a search through the archives for other threads on this error.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
But I used compile this Sequencer till date and this sequencer used to run everyday. But all of a sudden I got this problem when I tried to compile this.
vmcburney wrote:You need write access to your c:\Program Files\Ascential\DataStage directory (or whatever equivelent directory your DataStage Client is installed to). Do a search through the archives for other threads on this error.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
What's changed? "Nothing" is not the correct answer. Are you using a different/changed PC?bapajju wrote:But I used compile this Sequencer till date and this sequencer used to run everyday. But all of a sudden I got this problem when I tried to compile this.
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.
No nothing was changed. Only due to a wrong parameter value the Sequencer got aborted. So after changing the parameter value I had to recompile again.
ray.wurlod wrote:What's changed? "Nothing" is not the correct answer. Are you using a different/changed PC?bapajju wrote:But I used compile this Sequencer till date and this sequencer used to run everyday. But all of a sudden I got this problem when I tried to compile this.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
"Nothing" is not the correct answer. Either you've run out of disk space on your client PC or you don't have write permission where you need it on that machine.
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: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
The sequence job will run for any user who has a Director since it runs on the server. Compilation however occurs on the client. Therefore a sequence that has run successfully for weeks but wont compile indicates a problem on your client machine, ie no write access to the DataStage client directory.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Exactly. Somehow my access to the required project directory was removed due to some confusion and that created all this problem
Thanks a lot for the suggestion
Thanks a lot for the suggestion
ray.wurlod wrote:"Nothing" is not the correct answer. Either you've run out of disk space on your client PC or you don't have write permission where you need it on that machine.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
This is a fairly common problem in sites where there is an SOE environment; that is, software is pushed out to PCs rather than allowing staff to install anything on their own PCs. "They" need to be informed that write permission is required to the DataStage installation folder, not just for job sequence compiling, but also for job template storage, generation of COBOL and JCL (mainframe jobs) and a few other odds and ends.
And you definitely have to have write permission to the Registry!
And you definitely have to have write permission to the Registry!
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: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
I once had the DataStage client break on every desktop in a training room halfway through a training course due to a dll file pushed onto the computers overnight. Had to reinstall the client on all machines. After that we shut down the machines at the end of each day instead of leaving them on but logged off and at the mercy of overnight updates.
Certus Solutions
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
Blog: Tooling Around in the InfoSphere
Twitter: @vmcburney
LinkedIn:Vincent McBurney LinkedIn
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Been there done that. I must say, however, that I have found most IT departments who "push" software to be amenable to cogent discussion about DataStage clients' requirements, and usually happy to oblige in getting it right within their SOE procedures.
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.